Professional Documents
Culture Documents
4h0
Uploaded by
Ck HolyOriginal Description:
Original Title
Copyright
Available Formats
Share this document
Did you find this document useful?
Is this content inappropriate?
Report this DocumentCopyright:
Available Formats
4h0
Uploaded by
Ck HolyCopyright:
Available Formats
1
3GPP TS 29.002 V4.17.0 (2006-06)
Technical Specification
3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification; (Release 4)
GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS
The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organizational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organizational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organizational Partners' Publications Offices.
2 3 4
3 Release 4 4 5
3GPP TS 29.002 V4.17.0 (2006-06)
Keywords
GSM, UMTS, MAP, SS7, network
3GPP Postal address 3GPP support office address
650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Internet
http://www.3gpp.org
Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media.
2006, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TTA, TTC). All rights reserved.
7 Release 4 8 9
3GPP TS 29.002 V4.17.0 (2006-06)
Contents
7 Contents....................................................................................................................................................3 8 Foreword.................................................................................................................................................25 9 1 Scope....................................................................................................................................................26 10 2 References............................................................................................................................................26 11 3 Abbreviations.......................................................................................................................................31 12 4 Void.....................................................................................................................................................31 13 5 Overload and compatibility overview..................................................................................................31
14 15 16 17 18 19 20 21 22 23 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58
5.1 Overload control...................................................................................................................................................31 5.1.1 Overload control for MSC (outside MAP)........................................................................................................31 5.1.2 Overload control for MAP entities....................................................................................................................32 5.1.3 Congestion control for Signalling System No. 7..............................................................................................36 5.2 Compatibility........................................................................................................................................................36 5.2.1 General 36 5.2.2 Strategy for selecting the Application Context (AC) version...........................................................................36 5.2.2.1 Proposed method............................................................................................................................................36 5.2.2.2 Managing the version look-up table...............................................................................................................37 5.2.2.3 Optimising the method...................................................................................................................................38 6.1 Use of SCCP........................................................................................................................................................38 6.1.1 SCCP Class.......................................................................................................................................................38 6.1.2 Sub-System Number (SSN)..............................................................................................................................38 6.1.3 SCCP addressing...............................................................................................................................................39 6.1.3.1 Introduction....................................................................................................................................................39 6.1.3.2 The Mobile-services Switching Centre (MSC)..............................................................................................41 6.1.3.2.1 MSC interaction during handover or relocation..........................................................................................41 6.1.3.2.2 MSC for short message routing...................................................................................................................41 6.1.3.2.3 MSC for location request routing................................................................................................................41 6.1.3.2.4 MSC for LMU Control................................................................................................................................41 6.1.3.3 The Home Location Register (HLR)..............................................................................................................41 6.1.3.3.1 During call set-up........................................................................................................................................41 6.1.3.3.2 Before location updating completion..........................................................................................................42 6.1.3.3.3 After location updating completion............................................................................................................42 6.1.3.3.4 VLR restoration...........................................................................................................................................43 6.1.3.3.5 During Network-Requested PDP Context Activation.................................................................................43 6.1.3.3.6 Before GPRS location updating completion...............................................................................................43 6.1.3.3.7 After GPRS location updating completion.................................................................................................44 6.1.3.3.8 Query for a Location Request.....................................................................................................................44 6.1.3.4 The Visitor Location Register (VLR)............................................................................................................44 6.1.3.4.1 Inter-VLR information retrieval..................................................................................................................44 6.1.3.4.2 HLR request................................................................................................................................................44 6.1.3.5 The Interworking MSC (IWMSC) for Short Message Service......................................................................44 6.1.3.6 The Equipment Identity Register (EIR).........................................................................................................44 6.1.3.7 The Shared Inter Working Function (SIWF).................................................................................................45 6.1.3.8 The Serving GPRS Support Node (SGSN)....................................................................................................45 6.1.3.9 The Gateway GPRS Support Node (GGSN).................................................................................................45 6.1.3.10 The Gateway MSC (GMSC) for Short Message Service.............................................................................45 6.1.3.10A Void 45 6.1.3.10A.1 Void 45 6.1.3.10A.2 Void 45 6.1.3.10B The Gateway Mobile Location Centre (GMLC).......................................................................................45 6.1.3.11 Summary table.............................................................................................................................................45 6.2 Use of TC.............................................................................................................................................................49
24 6 Requirements concerning the use of SCCP and TC.............................................................................38
10
59 7 General on MAP services.....................................................................................................................49
60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119
11 Release 4 12 13
3GPP TS 29.002 V4.17.0 (2006-06)
7.1 Terminology and definitions................................................................................................................................49 7.2 Modelling principles............................................................................................................................................49 7.3 Common MAP services.......................................................................................................................................50 7.3.1 MAP-OPEN service..........................................................................................................................................51 7.3.2 MAP-CLOSE service........................................................................................................................................54 7.3.3 MAP-DELIMITER service...............................................................................................................................54 7.3.4 MAP-U-ABORT service...................................................................................................................................54 7.3.5 MAP-P-ABORT service...................................................................................................................................55 7.3.6 MAP-NOTICE service......................................................................................................................................56 7.3.7 void 57 7.3.8 void 57 7.3.9 void 57 7.3.10 void 57 7.4 Sequencing of services.........................................................................................................................................57 7.5 General rules for mapping of services onto TC...................................................................................................58 7.5.1 Mapping of common services...........................................................................................................................58 7.5.2 Mapping of user specific services.....................................................................................................................59 7.6 Definition of parameters......................................................................................................................................60 7.6.1 Common parameters.........................................................................................................................................62 7.6.1.1 Invoke Id 62 7.6.1.2 Linked Id 62 7.6.1.3 Provider error.................................................................................................................................................62 7.6.1.4 User error63 7.6.2 Numbering and identification parameters.........................................................................................................66 7.6.2.1 IMSI 66 7.6.2.2 TMSI 66 7.6.2.3 IMEI 66 7.6.2.4 Previous location area Id................................................................................................................................66 7.6.2.5 Stored location area Id...................................................................................................................................66 7.6.2.6 Current location area Id..................................................................................................................................66 7.6.2.7 Target location area Id...................................................................................................................................66 7.6.2.8 Target cell Id..................................................................................................................................................66 7.6.2.8A Target RNC Id.............................................................................................................................................67 7.6.2.9 Void 67 7.6.2.10 Originating entity number............................................................................................................................67 7.6.2.11 MSC number................................................................................................................................................67 7.6.2.12 Target MSC number.....................................................................................................................................67 7.6.2.13 HLR number.................................................................................................................................................67 7.6.2.14 VLR number.................................................................................................................................................67 7.6.2.15 HLR Id 67 7.6.2.16 LMSI 67 7.6.2.17 MS ISDN......................................................................................................................................................67 7.6.2.18 OMC Id 67 7.6.2.19 Roaming number..........................................................................................................................................67 7.6.2.19A Relocation Number List............................................................................................................................67 7.6.2.20 Void 67 7.6.2.21 Handover number.........................................................................................................................................67 7.6.2.22 Forwarded-to number...................................................................................................................................68 7.6.2.22A Long forwarded-to number.......................................................................................................................68 7.6.2.22B Long FTN Supported.................................................................................................................................68 7.6.2.23 Forwarded-to subaddress.............................................................................................................................68 7.6.2.24 Called number..............................................................................................................................................68 7.6.2.25 Calling number.............................................................................................................................................68 7.6.2.26 Originally dialled number............................................................................................................................68 7.6.2.27 Service centre address..................................................................................................................................68 7.6.2.28 Zone Code....................................................................................................................................................68 7.6.2.29 MSIsdn-Alert................................................................................................................................................68 7.6.2.30 Location Information...................................................................................................................................68 7.6.2.31 GMSC Address............................................................................................................................................68 7.6.2.32 VMSC Address............................................................................................................................................68
14
120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180
15 Release 4 16 17
3GPP TS 29.002 V4.17.0 (2006-06)
7.6.2.33 Group Id.......................................................................................................................................................69 7.6.2.34 North American Equal Access preferred Carrier Id.....................................................................................69 7.6.2.35 SIWFS Number............................................................................................................................................69 7.6.2.36 B-subscriber address....................................................................................................................................69 7.6.2.37 Serving cell Id..............................................................................................................................................69 7.6.2.38 SGSN number..............................................................................................................................................69 7.6.2.39 SGSN address...............................................................................................................................................69 7.6.2.40 GGSN address..............................................................................................................................................69 7.6.2.41 GGSN number..............................................................................................................................................69 7.6.2.42 APN 69 7.6.2.43 Network Node number.................................................................................................................................69 7.6.2.44 PDP-Type.....................................................................................................................................................69 7.6.2.45 PDP-Address................................................................................................................................................70 7.6.2.46 Additional number.......................................................................................................................................70 7.6.2.47 P-TMSI 70 7.6.2.48 B-subscriber number....................................................................................................................................70 7.6.2.49 B-subscriber subaddress...............................................................................................................................70 7.6.2.50 LMU Number ..............................................................................................................................................70 7.6.2.51 MLC Number ..............................................................................................................................................70 7.6.2.52 Multicall Bearer Information.......................................................................................................................70 7.6.2.53 Multiple Bearer Requested...........................................................................................................................70 7.6.2.54 Multiple Bearer Not Supported....................................................................................................................70 7.6.2.55 PDP-Charging Characteristics.....................................................................................................................70 7.6.2.56 Selected RAB ID..........................................................................................................................................70 7.6.2.57 RAB ID 70 7.6.3 Subscriber management parameters..................................................................................................................70 7.6.3.1 Category 70 7.6.3.2 Equipment status............................................................................................................................................71 7.6.3.3 Extensible Bearer service...............................................................................................................................71 7.6.3.4 Extensible Teleservice...................................................................................................................................71 7.6.3.5 Extensible Basic Service Group.....................................................................................................................71 7.6.3.6 GSM bearer capability...................................................................................................................................71 7.6.3.7 Subscriber Status............................................................................................................................................71 7.6.3.8 CUG Outgoing Access indicator....................................................................................................................71 7.6.3.9 Operator Determined Barring General Data..................................................................................................71 7.6.3.10 ODB HPLMN Specific Data........................................................................................................................73 7.6.3.11 Regional Subscription Data..........................................................................................................................74 7.6.3.12 Regional Subscription Response..................................................................................................................74 7.6.3.13 Roaming Restriction Due To Unsupported Feature.....................................................................................74 7.6.3.14 Extensible SS-Info.......................................................................................................................................74 7.6.3.15 Extensible forwarding information..............................................................................................................74 7.6.3.16 Extensible forwarding feature......................................................................................................................74 7.6.3.17 Extensible SS-Status....................................................................................................................................75 7.6.3.18 Extensible Forwarding Options....................................................................................................................75 7.6.3.19 Extensible No reply condition timer............................................................................................................75 7.6.3.20 Extensible Call barring information.............................................................................................................75 7.6.3.21 Extensible Call barring feature.....................................................................................................................75 7.6.3.22 CUG info......................................................................................................................................................75 7.6.3.23 CUG subscription.........................................................................................................................................76 7.6.3.24 CUG interlock..............................................................................................................................................76 7.6.3.25 CUG index...................................................................................................................................................76 7.6.3.26 CUG feature.................................................................................................................................................76 7.6.3.27 Inter CUG options........................................................................................................................................76 7.6.3.28 Intra CUG restrictions..................................................................................................................................76 7.6.3.29 Extensible SS-Data.......................................................................................................................................77 7.6.3.30 Subscriber State............................................................................................................................................77 7.6.3.31 Requested Info.............................................................................................................................................77 7.6.3.32 Suppression of Announcement....................................................................................................................77 7.6.3.33 Suppress T-CSI............................................................................................................................................77 7.6.3.34 GMSC CAMEL Subscription Info...............................................................................................................77 7.6.3.35 VLR CAMEL Subscription Info..................................................................................................................77
18
181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241
19 Release 4 20 21
3GPP TS 29.002 V4.17.0 (2006-06)
7.6.3.36 Supported CAMEL Phases in the VLR.......................................................................................................77 7.6.3.36A Supported CAMEL Phases in the SGSN..................................................................................................77 7.6.3.37 CUG Subscription Flag................................................................................................................................77 7.6.3.38 CAMEL Subscription Info Withdraw..........................................................................................................77 7.6.3.39 Voice Group Call Service (VGCS) Data.....................................................................................................78 7.6.3.40 Voice Broadcast Service (VBS) Data..........................................................................................................78 7.6.3.41 ISDN bearer capability.................................................................................................................................78 7.6.3.42 Lower layer Compatibility...........................................................................................................................78 7.6.3.43 High Layer Compatibility............................................................................................................................78 7.6.3.44 Alerting Pattern............................................................................................................................................78 7.6.3.45 GPRS Subscription Data Withdraw.............................................................................................................78 7.6.3.46 GPRS Subscription Data..............................................................................................................................78 7.6.3.47 QoS-Subscribed............................................................................................................................................78 7.6.3.48 VPLMN address allowed.............................................................................................................................78 7.6.3.49 Roaming Restricted In SGSN Due To Unsupported Feature.......................................................................78 7.6.3.50 Network Access Mode.................................................................................................................................78 7.6.3.51 Mobile Not Reachable Reason.....................................................................................................................78 7.6.3.52 Cancellation Type........................................................................................................................................79 7.6.3.53 All GPRS Data.............................................................................................................................................79 7.6.3.54 Complete Data List Included.......................................................................................................................79 7.6.3.55 PDP Context Identifier.................................................................................................................................79 7.6.3.56 LSA Information..........................................................................................................................................79 7.6.3.57 SoLSA support indicator..............................................................................................................................79 7.6.3.58 LSA Information Withdraw.........................................................................................................................79 7.6.3.59 LMU Indicator.............................................................................................................................................79 7.6.3.60 LCS Information..........................................................................................................................................79 7.6.3.61 GMLC List...................................................................................................................................................79 7.6.3.62 LCS Privacy Exception List.........................................................................................................................79 7.6.3.63 LCS Privacy Exception Parameters.............................................................................................................80 7.6.3.64 External Client List .....................................................................................................................................80 7.6.3.65 Internal Client List ......................................................................................................................................80 7.6.3.65A MO-LR List...............................................................................................................................................80 7.6.3.65B Privacy Notification to MS User...............................................................................................................80 7.6.3.65C GMLC List Withdraw...............................................................................................................................80 7.6.3.66 IST Alert Timer............................................................................................................................................80 7.6.3.67 Call Termination Indicator...........................................................................................................................80 7.6.3.68 IST Information Withdraw...........................................................................................................................80 7.6.3.69 IST Support Indicator...................................................................................................................................81 7.6.3.70 Super-Charger Supported In HLR...............................................................................................................81 7.6.3.71 Super-Charger Supported In Serving Network Entity.................................................................................81 7.6.3.72 Age Indicator................................................................................................................................................81 7.6.3.73 GPRS enhancements support indicator........................................................................................................81 7.6.3.74 Extensible QoS-Subscribed..........................................................................................................................81 7.6.3.75 SGSN Camel Subscription Info...................................................................................................................81 7.6.3.76 SMS-CSI......................................................................................................................................................81 7.6.3.77 GPRS-CSI....................................................................................................................................................81 7.6.3.78 CAMEL subscription info............................................................................................................................81 7.6.3.83 Call Barring Data.........................................................................................................................................82 7.6.3.84 Call Forwarding Data...................................................................................................................................82 7.6.3.85 ODB Data.....................................................................................................................................................82 7.6.3.86 Requested Subscription Info........................................................................................................................82 7.6.3.87 CS Allocation/Retention priority.................................................................................................................82 7.6.3.88 ODB Info......................................................................................................................................................82 7.6.4 Supplementary services parameters..................................................................................................................82 7.6.4.1 SS-Code 82 7.6.4.2 SS-Status 83 7.6.4.3 SS-Data 83 7.6.4.4 Override Category..........................................................................................................................................83 7.6.4.5 CLI Restriction Option...................................................................................................................................84 7.6.4.6 Forwarding Options.......................................................................................................................................84 7.6.4.7 No reply condition timer................................................................................................................................84
22
242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302
23 Release 4 24 25
3GPP TS 29.002 V4.17.0 (2006-06)
7.6.4.8 - 7.6.4.14 Void...............................................................................................................................................84 7.6.4.15 Forwarding information...............................................................................................................................84 7.6.4.16 Forwarding feature.......................................................................................................................................84 7.6.4.17 Void 85 7.6.4.18 Call barring information...............................................................................................................................85 7.6.4.19 Call barring feature......................................................................................................................................85 7.6.4.20 New password..............................................................................................................................................85 7.6.4.21 Current password.........................................................................................................................................85 7.6.4.22 Guidance information...................................................................................................................................85 7.6.4.23 Void 85 7.6.4.24 SS-Info 85 7.6.4.25 - 7.6.4.35 Void.............................................................................................................................................86 7.6.4.36 USSD Data Coding Scheme.........................................................................................................................86 7.6.4.37 USSD String.................................................................................................................................................86 7.6.4.38 Bearer service...............................................................................................................................................86 7.6.4.39 Teleservice...................................................................................................................................................86 7.6.4.40 Basic Service Group.....................................................................................................................................86 7.6.4.41 eMLPP information......................................................................................................................................86 7.6.4.42 SS-event.......................................................................................................................................................86 7.6.4.43 SS-event data................................................................................................................................................87 7.6.4.44 LCS Privacy Exceptions .............................................................................................................................87 7.6.4.45 Mobile Originating Location Request (MO-LR).........................................................................................87 7.6.4.46 NbrUser 87 7.6.4.47 MC Subscription Data..................................................................................................................................87 7.6.4.48 MC Information...........................................................................................................................................87 7.6.4.49 CCBS Request State.....................................................................................................................................88 7.6.5 Call parameters..................................................................................................................................................88 7.6.5.1 Call reference number....................................................................................................................................88 7.6.5.2 Interrogation type...........................................................................................................................................88 7.6.5.3 OR interrogation.............................................................................................................................................88 7.6.5.4 OR capability.................................................................................................................................................88 7.6.5.5 Forwarding reason..........................................................................................................................................88 7.6.5.6 Forwarding interrogation required.................................................................................................................88 7.6.5.7 O-CSI 88 7.6.5.7A D-CSI 89 7.6.5.7B T-CSI 89 7.6.5.7C VT-CSI 89 7.6.5.8 Call Direction.................................................................................................................................................89 7.6.5.9 Channel Type.................................................................................................................................................89 7.6.5.10 Chosen Channel...........................................................................................................................................89 7.6.5.11 CCBS Feature...............................................................................................................................................89 7.6.5.12 UU Data89 7.6.5.14 Number Portability Status............................................................................................................................89 7.6.5.15 Pre-paging supported...................................................................................................................................89 7.6.6 Radio parameters...............................................................................................................................................90 7.6.6.1 - 7.6.6.4 Void................................................................................................................................................90 7.6.6.5 BSSMAP Service Handover.........................................................................................................................90 7.6.6.5A BSSMAP Service Handover List...............................................................................................................90 7.6.6.6 RANAP Service Handover...........................................................................................................................90 7.6.6.7 HO-Number Not Required.............................................................................................................................90 7.6.6.8 Integrity Protection Information....................................................................................................................90 7.6.6.9 Encryption Information..................................................................................................................................90 7.6.6.10 Radio Resource Information........................................................................................................................90 7.6.6.10A Radio Resource List..................................................................................................................................90 7.6.6.10B Chosen Radio Resource Information.........................................................................................................90 7.6.6.11 Key Status....................................................................................................................................................90 7.6.6.12 Selected UMTS Algorithms.........................................................................................................................90 7.6.6.13 Allowed GSM Algorithms...........................................................................................................................90 7.6.6.14 Allowed UMTS Algorithms.........................................................................................................................91 7.6.6.15 Selected GSM Algorithm.............................................................................................................................91 7.6.7 Authentication parameters................................................................................................................................91
26
303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363
27 Release 4 28 29
3GPP TS 29.002 V4.17.0 (2006-06)
7.6.7.1 Authentication set list.....................................................................................................................................91 7.6.7.2 Rand 91 7.6.7.3 Sres 91 7.6.7.4 Kc 91 7.6.7.5 Xres 91 7.6.7.5A Ck 91 7.6.7.5B Ik 91 7.6.7.5C Autn 91 7.6.7.6 Cksn 91 7.6.7.6A Ksi 91 7.6.7.6B Auts 91 7.6.7.7 Ciphering mode..............................................................................................................................................92 7.6.7.8 Current Security Context................................................................................................................................92 7.6.7.9 Failure cause...................................................................................................................................................92 7.6.7.10 Re-attempt....................................................................................................................................................92 7.6.7.11 Access Type.................................................................................................................................................92 7.6.8 Short message parameters.................................................................................................................................92 7.6.8.1 SM-RP-DA.....................................................................................................................................................92 7.6.8.2 SM-RP-OA.....................................................................................................................................................92 7.6.8.3 MWD status...................................................................................................................................................93 7.6.8.4 SM-RP-UI......................................................................................................................................................93 7.6.8.5 SM-RP-PRI....................................................................................................................................................93 7.6.8.6 SM Delivery Outcome...................................................................................................................................93 7.6.8.7 More Messages To Send................................................................................................................................93 7.6.8.8 Alert Reason...................................................................................................................................................93 7.6.8.9 Absent Subscriber Diagnostic SM.................................................................................................................93 7.6.8.10 Alert Reason Indicator.................................................................................................................................93 7.6.8.11 Additional SM Delivery Outcome...............................................................................................................93 7.6.8.12 Additional Absent Subscriber Diagnostic SM.............................................................................................93 7.6.8.13 Delivery Outcome Indicator.........................................................................................................................93 7.6.8.14 GPRS Node Indicator...................................................................................................................................94 7.6.8.15 GPRS Support Indicator...............................................................................................................................94 7.6.8.16 SM-RP-MTI.................................................................................................................................................94 7.6.8.17 SM-RP-SMEA.............................................................................................................................................94 7.6.9 Access and signalling system related parameters.............................................................................................94 7.6.9.1 AN-apdu 94 7.6.9.2 CM service type.............................................................................................................................................94 7.6.9.3 Access connection status................................................................................................................................94 7.6.9.4 External Signal Information...........................................................................................................................94 7.6.9.5 Access signalling information........................................................................................................................95 7.6.9.6 Location update type......................................................................................................................................95 7.6.9.7 Protocol ID.....................................................................................................................................................95 7.6.9.8 Network signal information...........................................................................................................................95 7.6.9.9 Call Info 96 7.6.9.10 Additional signal info...................................................................................................................................96 7.6.10 System operations parameters.........................................................................................................................96 7.6.10.1 Network resources........................................................................................................................................96 7.6.10.2 Trace reference.............................................................................................................................................97 7.6.10.3 Trace type.....................................................................................................................................................97 7.6.11 Location Service Parameters ..........................................................................................................................97 7.6.11.1 Age of Location Estimate.............................................................................................................................97 7.6.11.2 Deferred MT-LR Response Indicator .........................................................................................................97 7.6.11.3 Deferred MT-LR Data..................................................................................................................................97 7.6.11.4 LCS Client ID..............................................................................................................................................97 7.6.11.5 LCS Event....................................................................................................................................................97 7.6.11.7 LCS Priority.................................................................................................................................................97 7.6.11.8 LCS QoS......................................................................................................................................................97 7.6.11.9 Void 98 7.6.11.10 Void 98 7.6.11.11 Location Estimate.......................................................................................................................................98 7.6.11.12 Location Type............................................................................................................................................98
30
364 365 366 367 368 369 370 371 372 373 374 375 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423
31 Release 4 32 33
3GPP TS 29.002 V4.17.0 (2006-06)
7.6.11.13 NA-ESRD..................................................................................................................................................98 7.6.11.14 NA-ESRK..................................................................................................................................................98 7.6.11.15 Void 98 7.6.11.16 Privacy Override........................................................................................................................................99 7.6.11.17 Supported LCS Capability Sets..................................................................................................................99 7.6.11.18 Void 99 7.6.11.19 NA-ESRK Request.....................................................................................................................................99 7.6.11.20 Supported GAD Shapes.............................................................................................................................99 7.6.11.21 Additional Location Estimate....................................................................................................................99 7.6.11.22 LCS-Reference Number.............................................................................................................................99 7.6.12 void 99 7.7 Representation of a list of a basic parameter in service-primitives.....................................................................99 8.1 Location management services..........................................................................................................................100 8.1.1 Void 100 8.1.1.1 Void 100 8.1.1.2 Void 100 8.1.1.3 Void 100 8.1.2 MAP_UPDATE_LOCATION service............................................................................................................100 8.1.2.1 Definition.....................................................................................................................................................100 8.1.2.2 Service primitives.........................................................................................................................................100 8.1.2.3 Parameter definitions and use......................................................................................................................100 8.1.3 MAP_CANCEL_LOCATION service...........................................................................................................102 8.1.3.1 Definition.....................................................................................................................................................102 8.1.3.2 Service primitives.........................................................................................................................................102 8.1.3.3 Parameter definitions and use......................................................................................................................103 8.1.4 MAP_SEND_IDENTIFICATION service.....................................................................................................103 8.1.4.1 Definition.....................................................................................................................................................103 8.1.4.2 Service primitives.........................................................................................................................................103 8.1.4.3 Parameter definitions and use......................................................................................................................103 8.1.5 Void 104 8.1.5.1 Void 104 8.1.5.2 Void 104 8.1.5.3 Void 104 8.1.6 MAP_PURGE_MS service.............................................................................................................................104 8.1.6.1 Definition.....................................................................................................................................................104 8.1.6.2 Service primitives.........................................................................................................................................105 8.1.6.3 Parameter definitions and use......................................................................................................................105 8.1.7 MAP_UPDATE_GPRS_LOCATION service................................................................................................106 8.1.7.1 Definition.....................................................................................................................................................106 8.1.7.2 Service primitives.........................................................................................................................................106 8.1.7.3 Parameter definitions and use......................................................................................................................106 8.1.8 MAP-NOTE-MM-EVENT.............................................................................................................................107 8.1.8.1 Definition.....................................................................................................................................................108 8.1.8.2 Service primitives.........................................................................................................................................108 8.1.8.3 Parameter use...............................................................................................................................................108 8.2 Paging and search...............................................................................................................................................109 8.2.1 MAP_PAGE service.......................................................................................................................................109 8.2.1.1 Definition.....................................................................................................................................................109 8.2.1.2 Service primitives.........................................................................................................................................109 8.2.1.3 Parameter definitions and use......................................................................................................................109 8.2.2 MAP_SEARCH_FOR_MS service................................................................................................................110 8.2.2.1 Definition.....................................................................................................................................................110 8.2.2.2 Service primitives.........................................................................................................................................110 8.2.2.3 Parameter definitions and use......................................................................................................................110 8.3 Access management services.............................................................................................................................111 8.3.1 MAP_PROCESS_ACCESS_REQUEST service...........................................................................................111 8.3.1.1 Definition.....................................................................................................................................................111 8.3.1.2 Service primitives.........................................................................................................................................111 8.3.1.3 Parameter definitions and use......................................................................................................................111
376 8 Mobility services................................................................................................................................100
34
424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484
35 Release 4 36 37
10
3GPP TS 29.002 V4.17.0 (2006-06)
8.4 Handover services..............................................................................................................................................112 8.4.1 MAP_PREPARE_HANDOVER service........................................................................................................112 8.4.1.1 Definition.....................................................................................................................................................113 8.4.1.2 Service primitives.........................................................................................................................................113 8.4.1.3 Parameter use...............................................................................................................................................113 8.4.2 MAP_SEND_END_SIGNAL service............................................................................................................116 8.4.2.1 Definition.....................................................................................................................................................116 8.4.2.2 Service primitives.........................................................................................................................................116 8.4.2.3 Parameter use...............................................................................................................................................116 8.4.3 MAP_PROCESS_ACCESS_SIGNALLING service.....................................................................................116 8.4.3.1 Definition.....................................................................................................................................................116 8.4.3.2 Service primitives.........................................................................................................................................117 8.4.3.3 Parameter use...............................................................................................................................................117 8.4.4 MAP_FORWARD_ACCESS_SIGNALLING service..................................................................................117 8.4.4.1 Definition.....................................................................................................................................................117 8.4.4.2 Service primitives.........................................................................................................................................117 8.4.4.3 Parameter use...............................................................................................................................................118 8.4.5 MAP_PREPARE_SUBSEQUENT_HANDOVER service............................................................................119 8.4.5.1 Definition.....................................................................................................................................................119 8.4.5.2 Service primitives.........................................................................................................................................119 8.4.5.3 Parameter use...............................................................................................................................................119 8.4.6 MAP_ALLOCATE_HANDOVER_NUMBER service.................................................................................120 8.4.6.1 Definition.....................................................................................................................................................120 8.4.6.2 Service primitives.........................................................................................................................................120 8.4.6.3 Parameter use...............................................................................................................................................120 8.4.7 MAP_SEND_HANDOVER_REPORT service..............................................................................................120 8.4.7.1 Definition.....................................................................................................................................................120 8.4.7.2 Service primitives.........................................................................................................................................121 8.4.7.3 Parameter use...............................................................................................................................................121 8.5 Authentication management services.................................................................................................................121 8.5.1 MAP_AUTHENTICATE service...................................................................................................................121 8.5.1.1 Definition.....................................................................................................................................................121 8.5.1.2 Service primitives.........................................................................................................................................121 8.5.1.3 Parameter use...............................................................................................................................................122 8.5.2 MAP_SEND_AUTHENTICATION_INFO service.......................................................................................122 8.5.2.1 Definition.....................................................................................................................................................122 8.5.2.2 Service primitives.........................................................................................................................................122 8.5.2.3 Parameter use...............................................................................................................................................123 8.5.3 MAP_AUTHENTICATION_FAILURE_REPORT service..........................................................................124 8.5.3.1 Definition.....................................................................................................................................................124 8.5.3.2 Service primitives.........................................................................................................................................124 8.5.3.3 Parameter use...............................................................................................................................................124 8.6 Security management services...........................................................................................................................125 8.6.1 MAP_SET_CIPHERING_MODE service......................................................................................................125 8.6.1.1 Definitions....................................................................................................................................................125 8.6.1.2 Service primitives.........................................................................................................................................125 8.6.1.3 Parameter use...............................................................................................................................................125 8.7 International mobile equipment identities management services......................................................................126 8.7.1 MAP_CHECK_IMEI service..........................................................................................................................126 8.7.1.1 Definition.....................................................................................................................................................126 8.7.1.2 Service primitives.........................................................................................................................................126 8.7.1.3 Parameter use...............................................................................................................................................126 8.7.2 MAP_OBTAIN_IMEI service........................................................................................................................127 8.7.2.1 Definition.....................................................................................................................................................127 8.7.2.2 Service primitives.........................................................................................................................................127 8.7.2.3 Parameter use...............................................................................................................................................127 8.8 Subscriber management services.......................................................................................................................127 8.8.1 MAP-INSERT-SUBSCRIBER-DATA service..............................................................................................127 8.8.1.1 Definition.....................................................................................................................................................127 8.8.1.2 Service primitives.........................................................................................................................................128 8.8.1.3 Parameter use...............................................................................................................................................129
38
485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 534 535 536 537 538 539 540 541 542 543 544
39 Release 4 40 41
11
3GPP TS 29.002 V4.17.0 (2006-06)
8.8.1.4 Basic service information related to supplementary services......................................................................137 8.8.2 MAP-DELETE-SUBSCRIBER-DATA service.............................................................................................138 8.8.2.1 Definition.....................................................................................................................................................138 8.8.2.2 Service primitives.........................................................................................................................................138 8.8.2.3 Parameter use...............................................................................................................................................138 8.9 Identity management services............................................................................................................................141 8.9.1 MAP-PROVIDE-IMSI service.......................................................................................................................141 8.9.1.1 Definition.....................................................................................................................................................141 8.9.1.2 Service primitives.........................................................................................................................................141 8.9.1.3 Parameter use...............................................................................................................................................141 8.9.2 MAP-FORWARD-NEW-TMSI service.........................................................................................................141 8.9.2.1 Definition.....................................................................................................................................................142 8.9.2.2 Service primitives.........................................................................................................................................142 8.9.2.3 Parameter use...............................................................................................................................................142 8.10 Fault recovery services.....................................................................................................................................142 8.10.1 MAP_RESET service....................................................................................................................................142 8.10.1.1 Definition...................................................................................................................................................142 8.10.1.2 Service primitives.......................................................................................................................................142 8.10.1.3 Parameter definition and use......................................................................................................................142 8.10.2 MAP_FORWARD_CHECK_SS_INDICATION service............................................................................142 8.10.2.1 Definition...................................................................................................................................................143 8.10.2.2 Service primitives.......................................................................................................................................143 8.10.2.3 Parameter definition and use......................................................................................................................143 8.10.3 MAP_RESTORE_DATA service.................................................................................................................143 8.10.3.1 Definition...................................................................................................................................................143 8.10.3.2 Service primitives.......................................................................................................................................143 8.10.3.3 Parameter definitions and use....................................................................................................................143 8.11 Subscriber Information services.......................................................................................................................145 8.11.1 MAP-ANY-TIME-INTERROGATION service...........................................................................................145 8.11.1.1 Definition...................................................................................................................................................145 8.11.1.2 Service primitives.......................................................................................................................................145 8.11.1.3 Parameter definition and use......................................................................................................................145 8.11.2 MAP-PROVIDE-SUBSCRIBER-Info service.............................................................................................146 8.11.2.1 Definition...................................................................................................................................................146 8.11.2.2 Service primitives.......................................................................................................................................146 8.11.2.3 Parameter definition and use......................................................................................................................146 8.11.3 MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION service.............................................................146 8.11.3.1 Definition...................................................................................................................................................146 8.11.3.2 Service primitives.......................................................................................................................................147 8.11.3.3 Parameter definition and use......................................................................................................................147 8.11.4 MAP-ANY-TIME-MODIFICATION service..............................................................................................147 8.11.4.1 Definition...................................................................................................................................................147 8.11.4.2 Service primitives.......................................................................................................................................148 8.11.4.3 Parameter definition and use......................................................................................................................148 8.11.5 MAP-NOTE-SUBSCRIBER-DATA-MODIFIED service...........................................................................148 8.11.5.1 Definition...................................................................................................................................................149 8.11.5.2 Service primitives.......................................................................................................................................149 8.11.5.3 Parameter definition and use......................................................................................................................149 9.1 Subscriber tracing services.................................................................................................................................150 9.1.1 MAP-ACTIVATE-TRACE-MODE service...................................................................................................150 9.1.1.1 Definition.....................................................................................................................................................150 9.1.1.2 Service primitives.........................................................................................................................................150 9.1.1.3 Parameter use...............................................................................................................................................150 9.1.2 MAP-DEACTIVATE-TRACE-MODE service..............................................................................................151 9.1.2.1 Definition.....................................................................................................................................................151 9.1.2.2 Service primitives.........................................................................................................................................151 9.1.2.3 Parameter use...............................................................................................................................................151 9.1.3 MAP-TRACE-SUBSCRIBER-ACTIVITY service.......................................................................................152 9.1.3.1 Definition.....................................................................................................................................................152
533 9 Operation and maintenance services..................................................................................................150
42
545 546 547 548 549 550 551 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604
43 Release 4 44 45
12
3GPP TS 29.002 V4.17.0 (2006-06)
9.1.3.2 Service primitives.........................................................................................................................................152 9.1.3.3 Parameter use...............................................................................................................................................152 9.2 Other operation and maintenance services.........................................................................................................152 9.2.1 MAP-SEND-IMSI service..............................................................................................................................152 9.2.1.1 Definition.....................................................................................................................................................152 9.2.1.2 Service primitives.........................................................................................................................................153 9.2.1.3 Parameter use...............................................................................................................................................153 10.1 MAP_SEND_ROUTING_INFORMATION service......................................................................................153 10.1.1 Definition......................................................................................................................................................153 10.1.2 Service primitives..........................................................................................................................................153 10.1.3 Parameter use................................................................................................................................................154 10.2 MAP_PROVIDE_ROAMING_NUMBER service.........................................................................................158 10.2.1 Definition......................................................................................................................................................158 10.2.2 Service primitives..........................................................................................................................................158 10.2.3 Parameter use................................................................................................................................................159 10.3 MAP_RESUME_CALL_HANDLING service...............................................................................................161 10.3.1 Definition......................................................................................................................................................161 10.3.2 Service primitives..........................................................................................................................................161 10.3.3 Parameter use................................................................................................................................................161 10.4 MAP_PREPARE_GROUP_CALL service.....................................................................................................162 10.4.1 Definition......................................................................................................................................................162 10.4.2 Service primitives..........................................................................................................................................163 10.4.3 Parameter definitions and use.......................................................................................................................163 10.5 MAP_PROCESS_GROUP CALL_SIGNALLING service............................................................................164 10.5.1 Definitions.....................................................................................................................................................164 10.5.2 Service primitives..........................................................................................................................................164 10.5.3 Parameter definitions and use.......................................................................................................................164 10.6 MAP_FORWARD_GROUP_CALL_SIGNALLING service.........................................................................164 10.6.1 Definitions.....................................................................................................................................................165 10.6.2 Service primitives..........................................................................................................................................165 10.6.3 Parameter definitions and use.......................................................................................................................165 10.7 MAP_SEND_GROUP_CALL_END_SIGNAL service.................................................................................165 10.7.1 Definitions.....................................................................................................................................................166 10.7.2 Service primitives..........................................................................................................................................166 10.7.3 Parameter definitions and use.......................................................................................................................166 10.8 MAP_Provide_SIWFS_Number......................................................................................................................166 10.8.1 Definition......................................................................................................................................................166 10.8.2 Service primitive...........................................................................................................................................166 10.8.3 Parameter use................................................................................................................................................167 10.9 MAP_SIWFS_Signalling_Modify...................................................................................................................168 10.9.1 Definition......................................................................................................................................................168 10.9.2 Service primitive...........................................................................................................................................168 10.9.3 Parameter use................................................................................................................................................168 10.10 MAP_SET_REPORTING_STATE service...................................................................................................169 10.10.1 Definition....................................................................................................................................................169 10.10.2 Service primitives........................................................................................................................................169 10.10.3 Parameter use..............................................................................................................................................169 10.11 MAP_STATUS_REPORT service................................................................................................................170 10.11.1 Definition....................................................................................................................................................170 10.11.2 Service primitives........................................................................................................................................170 10.11.3 Parameter use..............................................................................................................................................170 10.12 MAP_REMOTE_USER_FREE service........................................................................................................171 10.12.1 Definition....................................................................................................................................................171 10.12.2 Service primitives........................................................................................................................................171 10.12.3 Parameter use..............................................................................................................................................171 10.13 MAP_IST_ALERT service............................................................................................................................172 10.13.1 Definition....................................................................................................................................................172 10.13.2 Service primitives........................................................................................................................................172 10.13.3 Parameter use..............................................................................................................................................172
552 10 Call handling services......................................................................................................................153
46
605 606 607 608 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664
47 Release 4 48 49
13
3GPP TS 29.002 V4.17.0 (2006-06)
10.14 MAP_IST_COMMAND service...................................................................................................................173 10.14.1 Definition....................................................................................................................................................173 10.14.2 Service primitives........................................................................................................................................173 10.14.3 Parameter use..............................................................................................................................................173 11.1 MAP_REGISTER_SS service.........................................................................................................................173 11.1.1 Definition......................................................................................................................................................173 11.1.2 Service primitives..........................................................................................................................................174 11.1.3 Parameter use................................................................................................................................................174 11.2 MAP_ERASE_SS service................................................................................................................................175 11.2.1 Definition......................................................................................................................................................175 11.2.2 Service primitives..........................................................................................................................................175 11.2.3 Parameter use................................................................................................................................................175 11.3 MAP_ACTIVATE_SS service........................................................................................................................176 11.3.1 Definition......................................................................................................................................................176 11.3.2 Service primitives..........................................................................................................................................176 11.3.3 Parameter use................................................................................................................................................177 11.4 MAP_DEACTIVATE_SS service...................................................................................................................178 11.4.1 Definitions.....................................................................................................................................................178 11.4.2 Service primitives..........................................................................................................................................178 11.4.3 Parameter use................................................................................................................................................178 11.5 MAP_INTERROGATE_SS service................................................................................................................179 11.5.1 Definitions.....................................................................................................................................................179 11.5.2 Service primitives..........................................................................................................................................179 11.5.3 Parameter use................................................................................................................................................180 11.6 MAP_INVOKE_SS service.............................................................................................................................181 11.6.1 Definitions.....................................................................................................................................................181 11.6.2 Service primitives..........................................................................................................................................181 11.6.3 Parameter use................................................................................................................................................182 11.7 MAP_REGISTER_PASSWORD service........................................................................................................182 11.7.1 Definitions.....................................................................................................................................................182 11.7.2 Service primitives..........................................................................................................................................182 11.7.3 Parameter use................................................................................................................................................183 11.8 MAP_GET_PASSWORD service...................................................................................................................183 11.8.1 Definitions.....................................................................................................................................................183 11.8.2 Service primitives..........................................................................................................................................183 11.8.3 Parameter use................................................................................................................................................184 11.9 MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service.....................................................................184 11.9.1 Definitions.....................................................................................................................................................184 11.9.2 Service primitives..........................................................................................................................................184 11.9.3 Parameter use................................................................................................................................................184 11.10 MAP_UNSTRUCTURED_SS_REQUEST service......................................................................................185 11.10.1 Definitions...................................................................................................................................................185 11.10.2 Service primitives........................................................................................................................................185 11.10.3 Parameter use..............................................................................................................................................185 11.11 MAP_UNSTRUCTURED_SS_NOTIFY service..........................................................................................186 11.11.1 Definitions...................................................................................................................................................186 11.11.2 Service primitives........................................................................................................................................187 11.11.3 Parameter use..............................................................................................................................................187 11.12 MAP_SS_INVOCATION_NOTIFY.............................................................................................................188 11.12.1 Definition....................................................................................................................................................188 11.12.2 Service primitives........................................................................................................................................188 11.12.3 Parameter use..............................................................................................................................................188 11.13 MAP_REGISTER_CC_ENTRY service.......................................................................................................188 11.13.1 Definition....................................................................................................................................................188 11.13.2 Service primitives........................................................................................................................................189 11.13.3 Parameter use..............................................................................................................................................189 11.14 MAP_ERASE_CC_ENTRY service.............................................................................................................190 11.14.1 Definition....................................................................................................................................................190 11.14.2 Service primitives........................................................................................................................................190
609 11 Supplementary services related services..........................................................................................173
50
665 11.14.3 Parameter use..............................................................................................................................................190
51 Release 4 52 53
14
3GPP TS 29.002 V4.17.0 (2006-06)
666 12 Short message service management services....................................................................................191
667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 704 705 706 707 708 709 710 711 712 713 714 715 717 718 719 720 721 722 723
12.1 MAP-SEND-ROUTING-INFO-FOR-SM service...........................................................................................191 12.1.1 Definition......................................................................................................................................................191 12.1.2 Service primitives..........................................................................................................................................191 12.1.3 Parameter use................................................................................................................................................191 12.2 MAP-MO-FORWARD-SHORT-MESSAGE service.....................................................................................193 12.2.1 Definition......................................................................................................................................................193 12.2.2 Service primitives..........................................................................................................................................193 12.2.3 Parameter use................................................................................................................................................193 12.3 MAP-REPORT-SM-DELIVERY-STATUS service.......................................................................................194 12.3.1 Definition......................................................................................................................................................194 12.3.2 Service primitives..........................................................................................................................................194 12.3.3 Parameter use................................................................................................................................................194 12.4 MAP-READY-FOR-SM service.....................................................................................................................195 12.4.1 Definition......................................................................................................................................................195 12.4.2 Service primitives..........................................................................................................................................196 12.4.3 Parameter use................................................................................................................................................196 12.5 MAP-ALERT-SERVICE-CENTRE service....................................................................................................196 12.5.1 Definition......................................................................................................................................................196 12.5.2 Service primitives..........................................................................................................................................197 12.5.3 Parameter use................................................................................................................................................197 12.6 MAP-INFORM-SERVICE-CENTRE service.................................................................................................197 12.6.1 Definition......................................................................................................................................................197 12.6.2 Service primitives..........................................................................................................................................198 12.6.3 Parameter use................................................................................................................................................198 12.7 MAP-SEND-INFO-FOR-MT-SMS service.....................................................................................................198 12.7.1 Definition......................................................................................................................................................198 12.7.2 Service primitives..........................................................................................................................................198 12.7.3 Parameter use................................................................................................................................................198 12.8 MAP-SEND-INFO-FOR-MO-SMS service....................................................................................................199 12.8.1 Definition......................................................................................................................................................199 12.8.2 Service primitives..........................................................................................................................................199 12.8.3 Parameter use................................................................................................................................................199 12.9 MAP-MT-FORWARD-SHORT-MESSAGE service......................................................................................200 12.9.1 Definition......................................................................................................................................................200 12.9.2 Service primitives..........................................................................................................................................200 12.9.3 Parameter use................................................................................................................................................200 13.1 MAP_SEND_ROUTING_INFO_FOR_GPRS service...................................................................................201 13.1.1 Definition......................................................................................................................................................201 13.1.2 Service primitives..........................................................................................................................................202 13.1.3 Parameter definition and use.........................................................................................................................202 13.2 MAP_FAILURE_REPORT service.................................................................................................................203 13.2.1 Definition......................................................................................................................................................203 13.2.2 Service primitives..........................................................................................................................................203 13.2.3 Parameter definition and use.........................................................................................................................203 13.3 MAP_NOTE_MS_PRESENT_FOR_GPRS service.......................................................................................203 13.3.1 Definition......................................................................................................................................................203 13.3.2 Service primitives..........................................................................................................................................204 13.3.3 Parameter definition and use.........................................................................................................................204 13A.1 MAP-SEND-ROUTING-INFO-FOR-LCS Service......................................................................................204 13A.1.1 Definition...................................................................................................................................................204 13A.1.2 Service Primitives......................................................................................................................................205 13A.1.3 Parameter Use............................................................................................................................................205 13A.2 MAP-PROVIDE-SUBSCRIBER-LOCATION Service...............................................................................206 13A.2.1 Definition...................................................................................................................................................206 13A.2.2 Service Primitives......................................................................................................................................206
703 13 Network-Requested PDP Context Activation services.....................................................................201
716 13A Location Service Management Services........................................................................................204
54
724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 754 755 756 757 759 760 761 762 763 764 765 766 767 768 769 770 771 773 774 775 776 777 778 779 780 781 782
55 Release 4 56 57
15
3GPP TS 29.002 V4.17.0 (2006-06)
13A.2.3 Parameter Definition and Use....................................................................................................................206 13A.3 MAP-SUBSCRIBER-LOCATION-REPORT Service.................................................................................208 13A.3.1 Definition...................................................................................................................................................208 13A.3.2 Service Primitives......................................................................................................................................208 13A.3.3 Parameter Definition and Use....................................................................................................................208 13A.4 Void...............................................................................................................................................................210 13A.4.1 Void 210 13A.4.2 Void 210 13A.4.3 Void 210 13A.5 Void...............................................................................................................................................................210 13A.5.1 Void 210 13A.5.2 Void 210 13A.5.3 Void 210 13A.6 Void...............................................................................................................................................................210 13A.6.1 Void 210 13A.6.2 Void 210 13A.6.3 Void 210 13A.7 Void...............................................................................................................................................................211 13A.7.1 Void 211 13A.7.2 Void 211 13A.7.3 Void 211 13A.8 Void...............................................................................................................................................................211 13A.8.1 Void 211 13A.8.2 Void 211 13A.8.3 Void 211 13A.9 Void...............................................................................................................................................................211 13A.9.1 Void 211 13A.9.2 Void 211 13A.9.3 Void 211 14.1 Overview..........................................................................................................................................................211 14.2 Underlying services..........................................................................................................................................211 14.3 Model...............................................................................................................................................................211 14.4 Conventions......................................................................................................................................................212 15.1 Handling of unknown operations.....................................................................................................................212 15.2 Dialogue establishment....................................................................................................................................213 15.2.1 Behaviour at the initiating side.....................................................................................................................213 15.2.2 Behaviour at the responding side..................................................................................................................214 15.3 Dialogue continuation......................................................................................................................................215 15.4 Load control.....................................................................................................................................................215 15.5 Procedures for MAP specific services.............................................................................................................215 15.5.1 Service invocation ........................................................................................................................................215 15.5.2 void 215 15.5.3 Service invocation receipt ............................................................................................................................215 15.5.4 void 216 15.5.5 Handling of components received from TC..................................................................................................216 15.6 SDL descriptions..............................................................................................................................................216 16.1 Dialogue control...............................................................................................................................................249 16.1.1 Directly mapped parameters.........................................................................................................................249 16.1.2 Use of other parameters of dialogue handling primitives.............................................................................249 16.1.2.1 Dialogue Id.................................................................................................................................................249 16.1.2.2 Application-context-name..........................................................................................................................249 16.1.2.3 User information........................................................................................................................................249 16.1.2.4 Component present.....................................................................................................................................249 16.1.2.5 Termination................................................................................................................................................249 16.1.2.6 P-Abort-Cause............................................................................................................................................249 16.1.2.7 Quality of service.......................................................................................................................................249
753 14 General.............................................................................................................................................211
758 15 Elements of procedure......................................................................................................................212
772 16 Mapping on to TC services..............................................................................................................249
58
783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842
59 Release 4 60 61
16
3GPP TS 29.002 V4.17.0 (2006-06)
16.2 Service specific procedures..............................................................................................................................250 16.2.1 Directly mapped parameters.........................................................................................................................250 16.2.2 Use of other parameters of component handling primitives.........................................................................250 16.2.2.1 Dialogue Id.................................................................................................................................................250 16.2.2.2 Class 250 16.2.2.3 Linked Id....................................................................................................................................................250 16.2.2.4 Operation....................................................................................................................................................251 16.2.2.5 Error 252 16.2.2.6 Parameters..................................................................................................................................................252 16.2.2.7 Time out.....................................................................................................................................................252 16.2.2.8 Last component..........................................................................................................................................252 16.2.2.9 Problem code..............................................................................................................................................252 16.2.2.9.1 Mapping to MAP User Error...................................................................................................................252 16.2.2.9.2 Mapping to MAP Provider Error parameter...........................................................................................252 16.2.2.9.3 Mapping to diagnostic parameter............................................................................................................253 17.1 General.............................................................................................................................................................254 17.1.1 Encoding rules...............................................................................................................................................254 17.1.2 Use of TC......................................................................................................................................................254 17.1.2.1 Use of Global Operation and Error codes defined outside MAP...............................................................255 17.1.3 Use of information elements defined outside MAP......................................................................................255 17.1.4 Compatibility considerations........................................................................................................................256 17.1.5 Structure of the Abstract Syntax of MAP.....................................................................................................256 17.1.6 Application Contexts.....................................................................................................................................258 17.2 Operation packages..........................................................................................................................................259 17.2.1 General aspects..............................................................................................................................................259 17.2.2 Packages specifications.................................................................................................................................260 17.2.2.1 Location updating.......................................................................................................................................260 17.2.2.2 Location cancellation.................................................................................................................................260 17.2.2.3 Roaming number enquiry...........................................................................................................................261 17.2.2.4 Information retrieval..................................................................................................................................261 17.2.2.5 Inter-VLR information retrieval.................................................................................................................261 17.2.2.6 IMSI retrieval.............................................................................................................................................261 17.2.2.7 Call control transfer....................................................................................................................................262 17.2.2.8 void 262 17.2.2.9 Void 262 17.2.2.10 Interrogation.............................................................................................................................................262 17.2.2.11 Void 262 17.2.2.12 Handover Control.....................................................................................................................................262 17.2.2.13 Subscriber Data management stand alone................................................................................................263 17.2.2.14 Equipment management...........................................................................................................................263 17.2.2.15 Subscriber data management....................................................................................................................263 17.2.2.16 Location register restart............................................................................................................................263 17.2.2.17 Tracing stand-alone..................................................................................................................................263 17.2.2.18 Functional SS handling............................................................................................................................264 17.2.2.19 Tracing.....................................................................................................................................................264 17.2.2.20 Binding.....................................................................................................................................................264 17.2.2.21 Unstructured SS handling........................................................................................................................264 17.2.2.22 MO Short message relay services............................................................................................................265 17.2.2.23 Short message gateway services..............................................................................................................265 17.2.2.24 MT Short message relay services.............................................................................................................265 17.2.2.25 Void 266 17.2.2.26 Message waiting data management..........................................................................................................266 17.2.2.27 Alerting....................................................................................................................................................266 17.2.2.28 Data restoration........................................................................................................................................266 17.2.2.29 Purging.....................................................................................................................................................266 17.2.2.30 Subscriber information enquiry................................................................................................................267 17.2.2.31 Any time information enquiry..................................................................................................................267 17.2.2.32 Group Call Control...................................................................................................................................267 17.2.2.33 Provide SIWFS number...........................................................................................................................267
798 17 Abstract syntax of the MAP protocol...............................................................................................254
62
843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903
63 Release 4 64 65
17
3GPP TS 29.002 V4.17.0 (2006-06)
17.2.2.34 SIWFS Signalling Modify........................................................................................................................267 17.2.2.35 Gprs location updating.............................................................................................................................268 17.2.2.36 Gprs Interrogation....................................................................................................................................268 17.2.2.37 Failure reporting.......................................................................................................................................268 17.2.2.38 GPRS notifying........................................................................................................................................268 17.2.2.39 Supplementary Service invocation notification.......................................................................................269 17.2.2.40 Set Reporting State...................................................................................................................................269 17.2.2.41 Status Report............................................................................................................................................269 17.2.2.42 Remote User Free.....................................................................................................................................269 17.2.2.43 Call Completion.......................................................................................................................................269 17.2.2.44 Location service gateway services...........................................................................................................269 17.2.2.45 Location service enquiry..........................................................................................................................270 17.2.2.45A Location service reporting.....................................................................................................................270 17.2.2.46 Void 270 17.2.2.47 Void 270 17.2.2.48 Void 270 17.2.2.49 IST Alerting.............................................................................................................................................270 17.2.2.50 Service Termination.................................................................................................................................270 17.2.2.51 Mobility Management event notification.................................................................................................271 17.2.2.53 Subscriber Data modification notification...............................................................................................271 17.2.2.54 Authentication Failure Report..................................................................................................................271 17.3 Application contexts.........................................................................................................................................271 17.3.1 General aspects..............................................................................................................................................271 17.3.2 Application context definitions.....................................................................................................................272 17.3.2.1 Void 272 17.3.2.2 Location Updating......................................................................................................................................272 17.3.2.3 Location Cancellation................................................................................................................................273 17.3.2.4 Roaming number enquiry...........................................................................................................................273 17.3.2.5 Void 273 17.3.2.6 Location Information Retrieval..................................................................................................................273 17.3.2.7 Call control transfer....................................................................................................................................274 17.3.2.8 void 274 17.3.2.9 - 17.3.2.10 Void.........................................................................................................................................274 17.3.2.11 Location registers restart..........................................................................................................................274 17.3.2.12 Handover control......................................................................................................................................274 17.3.2.13 IMSI Retrieval..........................................................................................................................................274 17.3.2.14 Equipment Management..........................................................................................................................275 17.3.2.15 Information retrieval................................................................................................................................275 17.3.2.16 Inter-VLR information retrieval...............................................................................................................275 17.3.2.17 Stand Alone Subscriber Data Management.............................................................................................276 17.3.2.18 Tracing.....................................................................................................................................................276 17.3.2.19 Network functional SS handling..............................................................................................................276 17.3.2.20 Network unstructured SS handling..........................................................................................................277 17.3.2.21 Short Message Gateway...........................................................................................................................277 17.3.2.22 Mobile originating Short Message Relay.................................................................................................277 17.3.2.23 Void 278 17.3.2.24 Short message alert..................................................................................................................................278 17.3.2.25 Short message waiting data management................................................................................................278 17.3.2.26 Mobile terminating Short Message Relay................................................................................................278 17.3.2.27 MS purging...............................................................................................................................................279 17.3.2.28 Subscriber information enquiry................................................................................................................279 17.3.2.29 Any time information enquiry..................................................................................................................279 17.3.2.30 Group Call Control...................................................................................................................................279 17.3.2.31 Provide SIWFS Number..........................................................................................................................279 17.3.2.32 Gprs Location Updating...........................................................................................................................280 17.3.2.33 Gprs Location Information Retreival.......................................................................................................280 17.3.2.34 Failure Reporting.....................................................................................................................................280 17.3.2.35 GPRS Notifying.......................................................................................................................................280 17.3.2.36 Supplementary Service invocation notification.......................................................................................280 17.3.2.37 Reporting..................................................................................................................................................281 17.3.2.38 Call Completion.......................................................................................................................................281
66
904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 943 944 945 946 947 948 949 950 951 952 953 954 955 957 958 959 960 961 962 963
67 Release 4 68 69
18
3GPP TS 29.002 V4.17.0 (2006-06)
17.3.2.39 Location Service Gateway.......................................................................................................................282 17.3.2.40 Location Service Enquiry.........................................................................................................................282 17.3.2.41 Void 282 17.3.2.42 Void 282 17.3.2.43 Void 282 17.3.2.44 IST Alerting.............................................................................................................................................282 17.3.2.45 Service Termination.................................................................................................................................282 17.3.2.46 Mobility Management event notification.................................................................................................283 17.3.2.48 Subscriber Data modification notification...............................................................................................283 17.3.2.49 Authentication Failure Report..................................................................................................................283 17.3.3 ASN.1 Module for application-context-names.............................................................................................283 17.4 MAP Dialogue Information.............................................................................................................................286 17.5 MAP operation and error codes.......................................................................................................................288 17.6 MAP operation and error types........................................................................................................................294 17.6.1 Mobile Service Operations............................................................................................................................294 17.6.2 Operation and Maintenance Operations........................................................................................................300 17.6.3 Call Handling Operations..............................................................................................................................302 17.6.4 Supplementary service operations.................................................................................................................304 17.6.5 Short message service operations..................................................................................................................308 17.6.6 Errors 310 17.6.7 Group Call operations...................................................................................................................................316 17.6.8 Location service operations...........................................................................................................................317 17.6.9 void 319 17.7 MAP constants and data types.........................................................................................................................319 17.7.1 Mobile Service data types.............................................................................................................................319 17.7.2 Operation and maintenance data types..........................................................................................................346 17.7.3 Call handling data types................................................................................................................................347 17.7.4 Supplementary service data types.................................................................................................................353 17.7.5 Supplementary service codes........................................................................................................................357 17.7.6 Short message data types..............................................................................................................................360 17.7.7 Error data types.............................................................................................................................................363 17.7.8 Common data types.......................................................................................................................................368 17.7.9 Teleservice Codes.........................................................................................................................................375 17.7.10 Bearer Service Codes..................................................................................................................................376 17.7.11 Extension data types....................................................................................................................................378 17.7.12 Group Call data types..................................................................................................................................379 17.7.13 Location service data types.........................................................................................................................381 17.7.14 void 388 18.1 Introduction......................................................................................................................................................388 18.2 Common aspects of user procedure descriptions.............................................................................................388 18.2.1 General conventions......................................................................................................................................388 18.2.2 Naming conventions......................................................................................................................................388 18.2.3 Convention on primitives parameters...........................................................................................................389 18.2.3.1 Open service...............................................................................................................................................389 18.2.3.2 Close service..............................................................................................................................................390 18.2.4 Version handling at dialogue establishment.................................................................................................390 18.2.4.1 Behaviour at the initiating side..................................................................................................................390 18.2.4.2 Behaviour at the responding side...............................................................................................................390 18.2.5 Abort Handling..............................................................................................................................................390 18.2.6 SDL conventions...........................................................................................................................................390 18.3 Interaction between MAP Provider and MAP Users.......................................................................................391 19.1 Location management Procedures...................................................................................................................391 19.1.1 Location updating..........................................................................................................................................394 19.1.1.1 General 394 19.1.1.3 Detailed procedure in the VLR..................................................................................................................399 19.1.1.4 Detailed procedure in the HLR..................................................................................................................408 19.1.1.5 Send Identification.....................................................................................................................................415 19.1.1.5.1 General 415
942 18 General on MAP user procedures.....................................................................................................388
956 19 Mobility procedures.........................................................................................................................391
70
964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023
71 Release 4 72 73
19
3GPP TS 29.002 V4.17.0 (2006-06)
19.1.1.5.2 Detailed procedure in the VLR...............................................................................................................415 19.1.1.5.3 Detailed procedure in the PVLR.............................................................................................................415 19.1.1.6 Process Update Location VLR...................................................................................................................420 19.1.1.8 Detailed procedure in the SGSN................................................................................................................422 19.1.2 Location Cancellation...................................................................................................................................425 19.1.2.1 General 425 19.1.2.2 Detailed procedure in the HLR..................................................................................................................425 19.1.2.3 Detailed procedure in the VLR..................................................................................................................425 19.1.2.4 Detailed procedure in the SGSN................................................................................................................428 19.1.3 Void 431 19.1.3.1 Void 432 19.1.3.2 Void 432 19.1.3.3 Void 432 19.1.4 Purge MS.......................................................................................................................................................432 19.1.4.1 General 432 19.1.4.2 Void 432 19.1.4.3 Void 432 19.1.4.4 Detailed procedure in the SGSN................................................................................................................432 19.2 Handover procedure.........................................................................................................................................437 19.2.1 General..........................................................................................................................................................438 19.2.2 Handover procedure in MSC-A....................................................................................................................441 19.2.2.1 Basic handover...........................................................................................................................................441 19.2.2.2 Handling of access signalling.....................................................................................................................441 19.2.2.3 Other procedures in stable handover situation...........................................................................................442 19.2.2.4 Subsequent handover.................................................................................................................................442 19.2.2.5 SDL Diagrams............................................................................................................................................442 19.2.3 Handover procedure in MSC-B....................................................................................................................455 19.2.3.1 Basic handover...........................................................................................................................................456 19.2.3.2 Allocation of handover number.................................................................................................................456 19.2.3.3 Handling of access signalling.....................................................................................................................456 19.2.3.4 Other procedures in stable handover situation...........................................................................................456 19.2.3.5 Subsequent handover.................................................................................................................................456 19.2.3.6 SDL Diagrams............................................................................................................................................456 19.2.4 Handover error handling macro....................................................................................................................468 19.2.5 Handover procedure in VLR.........................................................................................................................470 19.2.5.1 Allocation of handover number.................................................................................................................470 19.2.5.2 SDL Diagrams............................................................................................................................................470 19.3 Fault recovery procedures................................................................................................................................473 19.3.1 VLR fault recovery procedures.....................................................................................................................473 19.3.2 HLR fault recovery procedures.....................................................................................................................475 19.3.3 VLR restoration: the restore data procedure in the HLR..............................................................................483 19.4 Macro Insert_Subs_Data_Framed_HLR..........................................................................................................485 19.5 Mobility Management Event notification procedure.......................................................................................488 19.5.1 General..........................................................................................................................................................488 19.5.2 Process in the VLR........................................................................................................................................488 19.5.3 Process in the gsmSCF..................................................................................................................................490 20.1 General.............................................................................................................................................................492 20.1.1 Tracing Co-ordinator for the VLR................................................................................................................492 20.1.2 Subscriber Data Management Co-ordinator for the VLR.............................................................................494 20.1.3 Tracing Co-ordinator for the SGSN..............................................................................................................496 20.1.4 Subscriber Data Management Co-ordinator for the SGSN...........................................................................498 20.2 Tracing procedures...........................................................................................................................................500 20.2.1 Procedures in the HLR..................................................................................................................................502 20.2.1.1 Subscriber tracing activation procedure.....................................................................................................502 20.2.1.2 Subscriber tracing deactivation procedure.................................................................................................507 20.2.2 Procedures in the VLR..................................................................................................................................512 20.2.2.1 Subscriber tracing activation procedure.....................................................................................................512 20.2.2.2 Subscriber tracing deactivation procedure.................................................................................................514 20.2.2.3 Subscriber tracing procedure......................................................................................................................516
1010 20 Operation and maintenance procedures............................................................................................492
74
1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083
75 Release 4 76 77
20
3GPP TS 29.002 V4.17.0 (2006-06)
20.2.3 Procedures in the MSC..................................................................................................................................516 20.2.3.1 Subscriber tracing procedure......................................................................................................................516 20.2.4 Procedures in the SGSN................................................................................................................................516 20.2.4.1 Subscriber tracing activation procedure.....................................................................................................516 20.2.4.2 Subscriber tracing deactivation procedure in SGSN..................................................................................516 20.3 Subscriber data management procedures.........................................................................................................519 20.3.1 Procedures in the HLR..................................................................................................................................520 20.3.1.1 Subscriber deletion procedure....................................................................................................................520 20.3.1.2 Subscriber data modification procedure.....................................................................................................522 20.3.2 Procedures in the VLR..................................................................................................................................527 20.3.2.1 Subscriber deletion procedure....................................................................................................................527 20.3.2.2 Subscriber data modification procedure.....................................................................................................527 20.3.3 Procedures in the SGSN................................................................................................................................530 20.3.3.1 Subscriber deletion procedure....................................................................................................................530 20.3.3.2 Subscriber data modification procedure.....................................................................................................530 20.4 Subscriber Identity procedure..........................................................................................................................533 20.4.1 Subscriber identity procedure in the HLR....................................................................................................533 20.4.2 Subscriber identity procedure in the VLR....................................................................................................535 21.1 General.............................................................................................................................................................537 21.2 Retrieval of routing information......................................................................................................................537 21.2.1 General..........................................................................................................................................................537 21.2.2 Process in the GMSC....................................................................................................................................539 21.2.3 Procedures in the HLR..................................................................................................................................543 21.2.4 Process in the VLR to provide a roaming number........................................................................................549 21.2.5 Process in the VLR to restore subscriber data..............................................................................................551 21.2.6 Process in the VLR to provide subscriber information.................................................................................553 21.2.7 Process in the HLR for Any Time Interrogation...........................................................................................555 21.2.7.1 Process in the gsmSCF...............................................................................................................................555 21.2.7.2 Process in the HLR.....................................................................................................................................555 21.2.8 Process in the GMLC for Any Time Interrogation.......................................................................................559 21.2.8.1 Process in the gsmSCF...............................................................................................................................559 21.2.8.2 Process in the GMLC.................................................................................................................................559 21.3 Transfer of call handling..................................................................................................................................562 21.3.1 General..........................................................................................................................................................562 21.3.2 Process in the VMSC....................................................................................................................................562 21.3.3 Process in the GMSC....................................................................................................................................565 21.4 Inter MSC Group Call Procedures...................................................................................................................567 21.4.1 General..........................................................................................................................................................567 21.4.2 Process in the Anchor MSC..........................................................................................................................567 21.4.3 Process in the Relay MSC.............................................................................................................................573 21.5 Allocation and modifications of resources in an SIWFS.................................................................................578 21.5.1 General..........................................................................................................................................................578 21.5.2 Process in the VMSC....................................................................................................................................581 21.5.2.1 Allocation of SIWFS resources..................................................................................................................581 21.5.2.2 Modification of SIWFS resources initiated by the user.............................................................................582 21.5.2.3 Modification of SIWFS resources initiated by the SIWFS........................................................................582 21.5.3 Process in the SIWFS....................................................................................................................................590 21.5.3.1 Procedures for allocation of SIWFS resources..........................................................................................590 21.5.3.2 Process for modification of SIWFS resources initiated by the user...........................................................591 21.5.3.3 Process for modification of SIWFS resources initiated by the SIWFS.....................................................591 21.6 Setting of Reporting State................................................................................................................................597 21.6.1 General..........................................................................................................................................................597 21.6.2 Process in the HLR for Set Reporting State stand-alone..............................................................................597 21.6.3 Reporting co-ordinator process in the VLR..................................................................................................600 21.6.4 Process in the VLR to set the reporting state................................................................................................602 21.7 Status Reporting...............................................................................................................................................605 21.7.1 General..........................................................................................................................................................605 21.7.2 Process in the VLR for Status Reporting......................................................................................................605 21.7.3 Process in the HLR for Status Reporting......................................................................................................609
1042 21 Call handling procedures..................................................................................................................537
78
1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143
79 Release 4 80 81
21
3GPP TS 29.002 V4.17.0 (2006-06)
21.8 Remote User Free.............................................................................................................................................614 21.8.1 General..........................................................................................................................................................614 21.8.2 Process in the HLR for Remote User Free....................................................................................................614 21.8.3 Process in the VLR for Remote User Free....................................................................................................617 21.9 IST Alert...........................................................................................................................................................620 21.9.1 General..........................................................................................................................................................620 21.9.2 Procedure in the MSC...................................................................................................................................620 21.9.3 Procedure in the HLR....................................................................................................................................622 21.10 IST Command................................................................................................................................................624 21.10.1 General........................................................................................................................................................624 21.10.2 Procedure in the HLR..................................................................................................................................624 21.10.3 Procedure in the MSC.................................................................................................................................626 22.1 Functional supplementary service processes...................................................................................................628 22.1.1 Functional supplementary service process co-ordinator for MSC................................................................628 22.1.2 Functional supplementary service process co-ordinator for VLR................................................................630 22.1.3 Functional supplementary service process co-ordinator for HLR................................................................632 22.1.4 Call completion supplementary service process co-ordinator for HLR........................................................634 22.2 Registration procedure.....................................................................................................................................636 22.2.1 General..........................................................................................................................................................636 22.2.2 Procedures in the MSC..................................................................................................................................636 22.2.3 Procedures in the VLR..................................................................................................................................639 22.2.4 Procedures in the HLR..................................................................................................................................641 22.3 Erasure procedure.............................................................................................................................................644 22.3.1 General..........................................................................................................................................................644 22.3.2 Procedures in the MSC..................................................................................................................................644 22.3.3 Procedures in the VLR..................................................................................................................................645 22.3.4 Procedures in the HLR..................................................................................................................................645 22.4 Activation procedure........................................................................................................................................645 22.4.1 General..........................................................................................................................................................645 22.4.2 Procedures in the MSC..................................................................................................................................646 22.4.3 Procedures in the VLR..................................................................................................................................648 22.4.4 Procedures in the HLR..................................................................................................................................651 22.5 Deactivation procedure....................................................................................................................................653 22.5.1 General..........................................................................................................................................................653 22.5.2 Procedures in the MSC..................................................................................................................................654 22.5.3 Procedures in the VLR..................................................................................................................................654 22.5.4 Procedures in the HLR..................................................................................................................................654 22.6 Interrogation procedure....................................................................................................................................654 22.6.1 General..........................................................................................................................................................654 22.6.2 Procedures in the MSC..................................................................................................................................655 22.6.3 Procedures in the VLR..................................................................................................................................655 22.6.4 Procedures in the HLR..................................................................................................................................660 22.7 Invocation procedure........................................................................................................................................662 22.7.1 General..........................................................................................................................................................662 22.7.2 Procedures in the MSC..................................................................................................................................662 22.7.3 Procedures in the VLR..................................................................................................................................666 22.8 Password registration procedure......................................................................................................................668 22.8.1 General..........................................................................................................................................................668 22.8.2 Procedures in the MSC..................................................................................................................................669 22.8.3 Procedures in the VLR..................................................................................................................................669 22.8.4 Procedures in the HLR..................................................................................................................................669 22.9 Mobile Initiated USSD procedure....................................................................................................................672 22.9.1 General..........................................................................................................................................................672 22.9.2 Procedures in the MSC..................................................................................................................................672 22.9.3 Procedures in the VLR..................................................................................................................................676 22.9.4 Procedures in the HLR..................................................................................................................................681 22.9.5 Procedures in the gsmSCF/secondary HLR..................................................................................................685 22.10 Network initiated USSD procedure...............................................................................................................688 22.10.1 General........................................................................................................................................................688
1096 22 Supplementary services procedures..................................................................................................628
82
1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1195 1196 1197 1198 1199 1200 1201
83 Release 4 84 85
22
3GPP TS 29.002 V4.17.0 (2006-06)
22.10.2 Procedure in the MSC.................................................................................................................................688 22.10.3 Procedure in the VLR..................................................................................................................................693 22.10.4 Procedure in the HLR..................................................................................................................................700 22.10.5 Procedure in the gsmSCF and secondary HLR...........................................................................................706 22.11 Common macros for clause 22.......................................................................................................................710 22.11.1 SS Password handling macros....................................................................................................................710 22.11.2 SS Error handling macros...........................................................................................................................713 22.12 Supplementary Service Invocation Notification procedure...........................................................................719 22.12.1 General........................................................................................................................................................719 22.12.2 Procedures in the MSC................................................................................................................................719 22.12.3 Procedures in the gsmSCF..........................................................................................................................721 22.13 Activation of a CCBS request........................................................................................................................723 22.13.1 General........................................................................................................................................................723 22.13.2 Procedure in the VLR..................................................................................................................................723 22.13.3 Procedure in the HLR..................................................................................................................................725 22.14 Deactivation of a CCBS request....................................................................................................................727 22.14.1 General........................................................................................................................................................727 22.14.2 Procedure in the VLR..................................................................................................................................727 22.14.3 Procedure in the HLR..................................................................................................................................729 23.1 General.............................................................................................................................................................731 23.1.1 Mobile originated short message service Co-ordinator for the MSC...........................................................731 23.1.2 Short message Gateway Co-ordinator for the HLR......................................................................................733 23.1.3 Mobile originated short message service Co-ordinator for the SGSN..........................................................735 23.2 The mobile originated short message transfer procedure................................................................................737 23.2.1 Procedure in the servicing MSC...................................................................................................................737 23.2.2 Procedure in the VLR....................................................................................................................................744 23.2.3 Procedure in the interworking MSC.............................................................................................................747 23.2.4 Procedure in the SGSN.................................................................................................................................749 23.3 The mobile terminated short message transfer procedure................................................................................754 23.3.1 Procedure in the Servicing MSC...................................................................................................................756 23.3.2 Procedures in the VLR..................................................................................................................................765 23.3.3 Procedures in the HLR..................................................................................................................................769 23.3.4 Procedures in the gateway MSC...................................................................................................................778 23.3.5 Procedure in the Servicing SGSN.................................................................................................................788 23.4 The Short Message Alert procedure.................................................................................................................796 23.4.1 Procedures in the Servicing MSC.................................................................................................................798 23.4.2 Procedures in the VLR..................................................................................................................................800 23.4.2.1 The Mobile Subscriber is present...............................................................................................................800 23.4.2.2 The Mobile Equipment has memory available..........................................................................................800 23.4.3 Procedures in the HLR..................................................................................................................................802 23.4.4 Procedures in the Interworking MSC............................................................................................................805 23.4.5 Procedures in the Servicing SGSN...............................................................................................................807 23.4.5.1 The Mobile Subscriber is present...............................................................................................................807 23.4.5.2 The Mobile Equipment has memory available..........................................................................................807 23.5 The SM delivery status report procedure.........................................................................................................809 23.5.1 Procedures in the HLR..................................................................................................................................809 23.5.2 Procedures in the gateway MSC...................................................................................................................811 23.6 Common procedures for the short message clause..........................................................................................813 23.6.1 The macro Report_SM_Delivery_Stat_HLR................................................................................................813 24.1 General.............................................................................................................................................................815 24.1.1 Process in the HLR for Send Routing Information for GPRS......................................................................815 24.1.2 Process in the GGSN for Send Routing Information for GPRS...................................................................817 24.2.1 Process in the HLR for Failure Report..........................................................................................................819 24.2.2 Process in the GGSN for Failure Report.......................................................................................................821 24.3.1 Process in the GGSN for Note Ms Present For Gprs....................................................................................823 24.3.2 Process in the HLR for Note Ms Present For Gprs.......................................................................................825
1163 23 Short message service procedures....................................................................................................731
1194 24 GPRS process description................................................................................................................815
86
1202 24A CSE control of subscriber data......................................................................................................827
1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261
87 Release 4 88 89
23
3GPP TS 29.002 V4.17.0 (2006-06)
24A.1 Any Time Subscription Interrogation procedure..........................................................................................827 24A.1.1 General.......................................................................................................................................................827 24A.1.2 Process in the gsmSCF...............................................................................................................................827 24A.1.3 Process in the HLR.....................................................................................................................................827 24A.2 Any Time Modification procedure................................................................................................................830 24A.2.1 General.......................................................................................................................................................830 24A.2.2 Process in the gsmSCF...............................................................................................................................830 24A.2.3 Process in the HLR.....................................................................................................................................830 24A.3 Subscriber Data Modification Notification procedure..................................................................................833 24A.3.1 General.......................................................................................................................................................833 24A.3.2 Processes in the MAP Entities...................................................................................................................833 24A.3.2.1 Process in the HLR..................................................................................................................................833 24A.3.2.2 Process in the gsmSCF............................................................................................................................836 24B.1 Routeing information retrieval procedure for LCS.......................................................................................837 24B.1.1 General.......................................................................................................................................................838 24B.1.2 Process in the GMLC.................................................................................................................................839 24B.1.3 Process in the HLR.....................................................................................................................................840 24B.2 Provide Subscriber Location procedure........................................................................................................841 24B.2.1 General.......................................................................................................................................................841 24B.2.2 Process in the GMLC.................................................................................................................................842 24B.2.3 Process in the MSC....................................................................................................................................843 24B.2.4 Process in the SGSN...................................................................................................................................843 24B.3 Subscriber Location Report procedure..........................................................................................................845 24B.3.1 General.......................................................................................................................................................845 24B.3.2 Process in the GMLC.................................................................................................................................846 24B.3.3 Process in the MSC....................................................................................................................................847 24B.3.4 Process in the SGSN...................................................................................................................................848 25.1 MAP open macros............................................................................................................................................849 25.1.1 Macro Receive_Open_Ind............................................................................................................................849 25.1.2 Macro Receive_Open_Cnf............................................................................................................................849 25.2 Macros to check the content of indication and confirmation primitives..........................................................854 25.2.1 Macro Check_Indication...............................................................................................................................854 25.2.2 Macro Check_Confirmation..........................................................................................................................854 25.3 The page and search macros............................................................................................................................857 25.3.1 Macro PAGE_MSC......................................................................................................................................857 25.3.2 Macro Search_For_MS_MSC.......................................................................................................................858 25.4 Macros for handling an Access Request..........................................................................................................861 25.4.1 Macro Process_Access_Request_MSC........................................................................................................861 25.4.2 Macro Process_Access_Request_VLR.........................................................................................................866 25.4.3 Macro Identification Procedure.....................................................................................................................868 25.5 Authentication macros and processes..............................................................................................................873 25.5.1 Macro Authenticate_MSC............................................................................................................................873 25.5.2 Macro Authenticate_VLR.............................................................................................................................873 25.5.3 Process Obtain_Authentication_Sets_VLR..................................................................................................873 25.5.4 Macro Obtain_Authent_Para_VLR..............................................................................................................873 25.5.5 Process Obtain_Auth_Sets_HLR..................................................................................................................874 25.5.6 Process Obtain_Authent_Para_SGSN..........................................................................................................884 25.5.7 Process Authentication_Failure_Report........................................................................................................889 25.5.7.1 General 889 25.5.7.2 Process in the VLR.....................................................................................................................................889 25.5.7.3 Process in the SGSN..................................................................................................................................891 25.5.7.4 Process in the HLR.....................................................................................................................................892 25.6 IMEI Handling Macros....................................................................................................................................893 25.6.1 Macro Check_IMEI_MSC............................................................................................................................893 25.6.2 Macro Check_IMEI_VLR............................................................................................................................893 25.6.3 Process Check_IMEI_EIR............................................................................................................................894 25.6.4 Macro Obtain_IMEI_MSC...........................................................................................................................894
1216 24B Location Service process description.............................................................................................837
1231 25 General macro description................................................................................................................849
90
1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284
91 Release 4 92 93
24
3GPP TS 29.002 V4.17.0 (2006-06)
25.6.5 Macro Obtain_IMEI_VLR............................................................................................................................894 25.6.6 Process Check_IMEI_SGSN........................................................................................................................901 25.7 Insert Subscriber Data Macros.........................................................................................................................904 25.7.1 Macro Insert_Subs_Data_VLR.....................................................................................................................904 25.7.2 Process Insert_Subs_Data_Stand_Alone_HLR............................................................................................906 25.7.3 Macro Wait_for_Insert_Subs_Data_Cnf......................................................................................................912 25.7.4 Process Send_Insert_Subs_Data...................................................................................................................914 25.7.5 Macro Insert_Subs_Data_SGSN...................................................................................................................914 25.7.6 Macro Wait_for_Insert_GPRS_Subs_Data_Cnf..........................................................................................916 25.8 Request IMSI Macros......................................................................................................................................918 25.8.1 Macro Obtain_IMSI_MSC............................................................................................................................918 25.8.2 Macro Obtain_IMSI_VLR............................................................................................................................918 25.9 Tracing macros.................................................................................................................................................920 25.9.1 Macro Trace_Subscriber_Activity_MSC......................................................................................................920 25.9.2 Macro Trace_Subscriber_Activity_VLR......................................................................................................920 25.9.3 Macro Activate_Tracing_VLR.....................................................................................................................921 25.9.4 Macro Control_Tracing_HLR.......................................................................................................................923 25.9.5 Macro Trace_Subscriber_Activity_SGSN....................................................................................................926 25.9.6 Macro Activate_Tracing_SGSN...................................................................................................................926 25.10 Short Message Alert procedures....................................................................................................................928 25.10.1 Subscriber_Present_VLR process...............................................................................................................928 25.10.2 Macro Alert_Service_Centre_HLR............................................................................................................930 25.10.3 The Mobile Subscriber is present................................................................................................................932
1285 Annex A (informative): 1286 1287 Annex B (informative): 1288
Cross-reference for abstract syntaxes of MAP.................................934 Fully expanded ASN.1 sources for abstract syntaxes of MAP.......1155
1289 B.1 Fully Expanded ASN.1 Source of MAP-Protocol/TCAPMessages..............................................1155 1290 B.2 Fully Expanded ASN.1 Source of MAP-DialogueInformation.....................................................1258 1291 Annex C : 1292 1293 Annex D (informative): 1294 1296 Annex E (informative): 1297 1298
Void....................................................................................................1262 Clause mapping table........................................................................1263
1295 D.1 Mapping of Clause numbers.........................................................................................................1263
Change History..................................................................................1264
94
95 Release 4 96 97
25
3GPP TS 29.002 V4.17.0 (2006-06)
1299
Foreword
1300 This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). 1301 The present document specifies the Mobile Application Part (MAP), the requirements for the signalling system and 1302 procedures within the 3GPP system at application level. 1303 The contents of the present document are subject to continuing work within the TSG and may change following formal 1304 TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an 1305 identifying change of release date and an increase in version number as follows: 1306 1307 1308 1309 1310 1311 1312 1313 1314
Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document.
98
99 Release 4 100 101
26
3GPP TS 29.002 V4.17.0 (2006-06)
1330
1 Scope
1331 It is necessary to transfer between entities of a Public Land Mobile Network (PLMN) information specific to the PLMN 1332 in order to deal with the specific behaviour of roaming Mobile Stations (MS)s. The Signalling System No. 7 specified 1333 by CCITT is used to transfer this information. 1334 The present document describes the requirements for the signalling system and the procedures needed at the application 1335 level in order to fulfil these signalling needs. 1336 Clauses 1 to 6 are related to general aspects such as terminology, mobile network configuration and other protocols 1337 required by MAP. 1338 MAP consists of a set of MAP services that are provided to MAP service-users by a MAP service-provider.
M A P s e r v ic e - u s e r S e r v ic e In te r f a c e M A P S e r v ic e - p r o v id e r
M A P s e r v ic e - u s e r
1339
1340
Figure 1.1/1: Modelling principles
1341 Clauses 7 to 13A of the present document describe the MAP services. 1342 Clauses 14 to 17 define the MAP protocol specification and the behaviour of service provider (protocol elements to be 1343 used to provide MAP services, mapping on to TC service primitives, abstract syntaxes, etc.). 1344 Clauses 18 to 25 describe the MAP user procedures that make use of MAP services.
1345
2 References
References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] [2] [3] [4] [5] [6] [7] 3GPP TS 21.905: "3G Vocabulary". 3GPP TS 22.001: "Digital cellular telecommunications system (Phase 2+); Principles of telecommunication services supported by a Public Land Mobile Network (PLMN)". 3GPP TS 22.002: "Bearer Services Supported by a Public Land Mobile Network (PLMN)". 3GPP TS 22.003: "Circuit Teleservices Supported by a Public Land Mobile Network (PLMN)". 3GPP TS 22.004: "General on Supplementary Services". 3GPP TS 42.009: "Digital cellular telecommunications system (Phase 2+); Security aspects". 3GPP TS 22.016: "International Mobile station Equipment Identities (IMEI)".
1346 The following documents contain provisions which, through reference in this text, constitute provisions of the present 1347 document.
1348
1349
1350 1351
1352 1353 1354 1355 1356 1357 1358 1359 1360 1361
102
1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397
103 Release 4 104 105
27
3GPP TS 29.002 V4.17.0 (2006-06)
[8] [9]
3GPP TS 22.041: "Operator Determined Barring". 3GPP TS 22.081: "Line identification supplementary services - Stage 1". 3GPP TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1". 3GPP TS 22.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Services - Stage 1". 3GPP TS 22.084: "Multi Party (MPTY) Supplementary Services - Stage 1". 3GPP TS 22.085: "Closed User Group (CUG) supplementary services - Stage 1". 3GPP TS 22.086: "Advice of charge (AoC) Supplementary Services - Stage 1". 3GPP TS 22.088: "Call Barring (CB) supplementary services - Stage 1". 3GPP TS 22.090: "Unstructured Supplementary Service Data (USSD); - Stage 1". 3GPP TS 23.003: "Numbering, addressing and identification". GSM 03.04: "Digital cellular telecommunications system (Phase 2+); Signalling requirements relating to routeing of calls to mobile subscribers". 3GPP TS 23.007: "Restoration procedures". 3GPP TS 23.008: "Organisation of subscriber data". 3GPP TS 23.009: "Handover procedures". 3GPP TS 23.011: "Technical realization of Supplementary Services - General Aspects". 3GPP TS 23.012: "Location registration procedures". 3GPP TS 43.020: "Security related network functions". 3GPP TS 23.038: "Alphabets and language". 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS) Point to Point (PP)". 3GPP TS 23.271: "Functional stage2 description of LCS (Release 4)". 3GPP TS 23.081: "Line Identification Supplementary Services - Stage 2". 3GPP TS 23.082: "Call Forwarding (CF) Supplementary Services - Stage 2". 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Services - Stage 2". 3GPP TS 23.084: "Multi Party (MPTY) Supplementary Services - Stage 2". 3GPP TS 23.085: "Closed User Group (CUG) Supplementary Services - Stage 2". 3GPP TS 23.086: "Advice of Charge (AoC) Supplementary Services - Stage 2". 3GPP TS 23.088: "Call Barring (CB) Supplementary Services - Stage 2". 3GPP TS 23.090: "Unstructured Supplementary Services Data (USSD) - Stage 2". 3GPP TS 33.200: "3G Security; Network domain security; MAP application layer security". 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols - Stage 3". 3GPP TS 24.010: "Mobile radio interface layer 3 Supplementary Services specification - General aspects". 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface".
[10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [26a] [27] [28] [29] [30] [31] [32] [33] [34] [34a] [35] [36] [37]
106
1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439
107 Release 4 108 109
28
3GPP TS 29.002 V4.17.0 (2006-06)
[37a] [38] [39] [40] [41] [42] [43] [44] [45] [46] [47] [48] [49]
3GPP TS 44.071: "Location Services (LCS) stage 3". 3GPP TS 24.080: "Mobile radio interface layer 3 supplementary services specification - Formats and coding". 3GPP TS 24.081: "Line identification supplementary services - Stage 3". 3GPP TS 24.082: "Call Forwarding (CF) Supplementary Services - Stage 3". 3GPP TS 24.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 3". 3GPP TS 24.084: "Multi Party (MPTY) Supplementary Services - Stage 3". 3GPP TS 24.085: "Closed User Group (CUG) Supplementary Services - Stage 3". 3GPP TS 24.086: "Advice of Charge (AoC) Supplementary Services - Stage 3". 3GPP TS 24.088: "Call Barring (CB) Supplementary Services - Stage 3". 3GPP TS 24.090: "Unstructured Supplementary Services Data - Stage 3". 3GPP TS 48.002: " Base Station System - Mobile-services Switching Centre (BSS - MSC) interface principles". 3GPP TS 48.006: "Signalling transport mechanism specification for the Base Station System Mobile-services Switching Centre (BSS - MSC) interface". 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification". 3GPP TS 48.031: "Location Services (LCS); Serving Mobile Location Centre (SMLC) Serving Mobile Location Centre (SMLC); SMLC Peer Protocol (SMLCPP)". 3GPP TS 48.071: "Location Services (LCS); Serving Mobile Location Centre - Base Station System (SMLC - BSS) interface Layer 3 specification". 3GPP TS 49.001: "General network interworking scenarios". 3GPP TS 29.002: "Mobile Application Part (MAP) specification". GSM 09.03: "Digital cellular telecommunications system (Phase 2+); Signalling requirements on interworking between the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) and the Public Land Mobile Network (PLMN)". GSM 09.04: "Digital cellular telecommunications system (Phase 2+); Interworking between the Public Land Mobile Network (PLMN) and the Circuit Switched Public Data Network (CSPDN)". GSM 09.05: "Digital cellular telecommunications system (Phase 2+); Interworking between the Public Land Mobile Network (PLMN) and the Packet Switched Public Data Network (PSPDN) for Packet Assembly/Disassembly facility (PAD) access". 3GPP TS 29.006: "Interworking between a Public Land Mobile Network (PLMN) and a Packet Switched Public Data Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of Packet Switched data transmission services". 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". 3GPP TS 29.008: "Application of the Base Station System Application Part (BSSAP) on the Einterface". 3GPP TS 29.010: "Information element mapping between Mobile Station - Base Station System and BSS - Mobile-services Switching Centre (MS - BSS - MSC) Signalling procedures and the Mobile Application Part (MAP)".
[49a1] [49b] [50] [51] [52]
[53] [54]
[55]
[56]
[57] [58]
110
1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482
111 Release 4 112 113
29
3GPP TS 29.002 V4.17.0 (2006-06)
[59]
3GPP TS 29.011: "Signalling interworking for Supplementary Services". 3GPP TS 49.031: "Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE)". GSM 09.90: "Digital cellular telecommunications system (Phase 2+); Interworking between Phase 1 infrastructure and Phase 2 Mobile Stations (MS)". GSM 12.08: "Digital cellular telecommunications system (Phase 2); Subscriber and Equipment Trace". ETS 300 102-1 (1990): "Integrated Services Digital Network (ISDN); User-network interface layer 3 specifications for basic call control". ETS 300 136 (1992): "Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service description". ETS 300 138 (1992): "Integrated Services Digital Network (ISDN); Closed User Group (CUG) supplementary service Digital Subscriber Signalling System No.one (DSS1) protocol". ETS 300 287: "Integrated Services Digital Network (ISDN); Signalling System No.7; Transaction Capabilities (TC) version 2". ETR 060: "Signalling Protocols and Switching (SPS); Guide-lines for using Abstract Syntax Notation One (ASN.1) in telecommunication application protocols". ITU-T Recommendation E.164: "Numbering plan for the ISDN era". ITU-T Recommendation E.212: "Identification plan for land mobile stations". ITU-T Recommendation E.213: "Telephone and ISDN numbering plan for land mobile stations". ITU-T Recommendation E.214: "Structuring of the land mobile global title for the signalling connection control part". CCITT Recommendation Q.699: "Interworking between the Digital Subscriber Signalling System Layer 3 protocol and the Signalling System No.7 ISDN User part". ITU-T Recommendation Q.711: "Specifications of Signalling System No.7; Functional description of the Signalling Connection Control Part". ITU-T Recommendation Q.712: "Definition and function of SCCP messages". ITU-T Recommendation Q.713: "Specifications of Signalling System No.7; SCCP formats and codes". ITU-T Recommendation Q.714: "Specifications of Signalling System No.7; Signalling Connection Control Part procedures". ITU-T Recommendation Q.716: "Specifications of Signalling System No.7; Signalling connection control part (SCCP) performances". ITU-T Recommendation Q.721 (1988): "Specifications of Signalling System No.7; Functional description of the Signalling System No.7 Telephone user part". ITU-T Recommendation Q.722 (1988): "Specifications of Signalling System No.7; General function of Telephone messages and signals". ITU-T Recommendation Q.723 (1988): "Specifications of Signalling System No.7; Formats and codes". ITU-T Recommendation Q.724 (1988): "Specifications of Signalling System No.7; Signalling procedures". ITU-T Recommendation Q.725 (1988): "Specifications of Signalling System No.7; Signalling performance in the telephone application".
[59a] [60] [61] [62] [63] [64] [65] [66] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76] [77] [78] [79] [80] [81]
114
1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524
115 Release 4 116 117
30
3GPP TS 29.002 V4.17.0 (2006-06)
[82] [83] [84] [85] [86] [87] [88] [89] [90] [91] [92] [93] [94] [95] [97] [98] [99]
ITU-T Recommendation Q.761 (1988): "Specifications of Signalling System No.7; Functional description of the ISDN user part of Signalling System No.7". ITU-T Recommendation Q.762 (1988): "Specifications of Signalling System No.7; General function of messages and signals". ITU-T Recommendation Q.763 (1988): "Specifications of Signalling System No.7; Formats and codes". ITU-T Recommendation Q.764 (1988): "Specifications of Signalling System No.7; Signalling procedures". ITU-T Recommendation Q.767: "Specifications of Signalling System No.7; Application of the ISDN user part of CCITT signalling System No.7 for international ISDN interconnections". ITU-T Recommendation Q.771: "Specifications of Signalling System No.7; Functional description of transaction capabilities". ITU-T Recommendation Q.772: "Specifications of Signalling System No.7; Transaction capabilities information element definitions". ITU-T Recommendation Q.773: "Specifications of Signalling System No.7; Transaction capabilities formats and encoding". ITU-T Recommendation Q.774: "Specifications of Signalling System No.7; Transaction capabilities procedures". ITU-T Recommendation Q.775: "Specifications of Signalling System No.7; Guide-lines for using transaction capabilities". ITU-T Recommendation X.200: "Reference Model of Open systems interconnection for CCITT Applications". ITU-T Recommendation X.208 (1988): "Specification of Abstract Syntax Notation One (ASN.1)". ITU-T Recommendation X.209 (1988): "Specification of basic encoding rules for Abstract Syntax Notation One (ASN.1)". ITU-T Recommendation X.210: "Open systems interconnection layer service definition conventions". 3GPP TS 23.018: "Basic Call Handling". 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 3 - Stage 2". 3GPP TS 23.079: "Support of Optimal Routeing (SOR) - Stage 2". 3GPP TS 43.068: "Voice Group Call Service (VGCS) - Stage 2". 3GPP TS 43.069: "Voice Broadcast service (VBS) - Stage 2". ANSI T1.113: "Signaling System No. 7 (SS7) - ISDN User Part". GSM 03.54 "Shared Inter Working Function (SIWF) - Stage 2". 3GPP TS 23.060: "General Packet Radio Service (GPRS) Description; Stage 2". 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface". 3GPP TS 29.018: "General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) Visitors Location Register (VLR); Gs interface layer 3 specification". 3GPP TS 23.093: "Technical Realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2".
[100] [101] [102] [103] [104] [105] [106] [107]
118
1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549
119 Release 4 120 121
31
3GPP TS 29.002 V4.17.0 (2006-06)
[108] [109] [110] [111] [112] [113] [114] [115] [116] [117] [118] [119] [120] [121] [122] [123]
3GPP TS 23.066: "Support of Mobile Number Portability (MNP); Technical Realisation Stage 2". ANSI T1.112 (1996): "Telecommunication Signalling No. 7 - Signaling Connection Control Part (SCCP)". 3GPP TS 23.116: "Super-Charger Technical Realisation; Stage 2." ITU-T Recommendation Q.711: "Specifications of Signalling System No.7; Signalling System No. 7 Functional Description of the Signalling Connection Control Part". ITU-T Recommendation Q.712: "Specifications of Signalling System No.7; Signalling System No. 7 Definition and Function of SCCP Messages". ITU-T Recommendation Q.713: "Specifications of Signalling System No.7; Signalling System No. 7 SCCP formats and codes". ITU-T Recommendation Q.714: "Specifications of Signalling System No.7; Signalling System No. 7 Signalling Connection Control Part Procedures". ITU-T Recommendation Q.716: "Specifications of Signalling System No.7; Signalling System No. 7 Signalling Connection Control Part (SCCP) Performance". ITU-T Q.850, May 1998: "Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part". 3GPP TS 22.135: "Multicall; Service description; Stage 1". 3GPP TS 23.135: "Multicall supplementary service; Stage 2". 3GPP TS 24.135: "Multicall supplementary service; Stage 3". 3GPP TS 25.413: "UTRAN Iu Interface RANAP Signalling". 3GPP TS 29.202: "SS7 signalling transport in core network" 3GPP TS 23.032: "Universal Geographical Area Description (GAD)" 3GPP TS 32.215: "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; Charging data description for the Packet Switched (PS) domain".
1550
3 Abbreviations
1551 Abbreviations used in the present document are listed in 3GPP TS 21.905.
1552 1553 1554
4 Void 5 Overload and compatibility overview
5.1 Overload control
1555 There is a requirement for an overload/congestion control for all entities of the Public Land Mobile Network and the 1556 underlying Signalling System No. 7.
1557
5.1.1 Overload control for MSC (outside MAP)
1558 For the entity MSC the following two procedures (outside MAP) may be applied to control the processor load:
122
1559 1560 1561 1562 1563
123 Release 4 124 125
32
3GPP TS 29.002 V4.17.0 (2006-06)
ISDN CCITT Recommendation Q.764 (Automatic Congestion Control), applicable to reduce the mobile terminating traffic; BSSAP 3GPP TS 48.008 [49] (A-interface Flow Control), applicable to reduce the mobile originating traffic.
1564
5.1.2 Overload control for MAP entities
1565 For all MAP entities, especially the HLR, the following overload control method is applied. 1566 If overload of a MAP entity is detected requests for certain MAP operations (see tables 5.1/1, 5.1/2, 5.1/3 and 5.1/4) 1567 may be ignored by the responder. The decision as to which MAP Operations may be ignored is made by the MAP 1568 service provider and is based upon the priority of the application context. 1569 Since most of the affected MAP operations are supervised in the originating entity by TC timers (medium) an additional 1570 delay effect is achieved for the incoming traffic. 1571 If overload levels are applicable in the Location Registers the MAP operations should be discarded taking into account 1572 the priority of their application context (see table 5.1/1 for HLR, table 5.1/2 for MSC/VLR, table 5.1/3 for the SGSN 1573 and table 5.1/4 for the SMLC; the lowest priority is discarded first). 1574 The ranking of priorities given in the tables 5.1/1, 5.1/2, 5.1/3 and 5.1/4 is not normative. The tables can only be seen as 1575 a proposal that might be changed due to network operator/implementation matters.
126
1576
127 Release 4 128 129
33
3GPP TS 29.002 V4.17.0 (2006-06)
Table 5.1/1: Priorities of Application Contexts for HLR as Responder
Responder = HLR Mobility Management networkLocUp (updateLocation), (restoreData/v2), (sendParameters/v1) gprsLocationUpdate (updateGPRSLocation/v3), infoRetrieval (sendAuthenticationInfo/v2/v3), (sendParameters/v1) istAlerting (istAlert/v3) (purgeMS/v2/v3) msPurging (purgeMS/v3) Short Message Service shortMsgGateway (sendRoutingInfoforSM), (reportSM-DeliveryStatus) mwdMngt VLR/SGSN (readyForSM/v2/v3), (noteSubscriberPresent/v1) Mobile Terminating Traffic locInfoRetrieval (sendRoutingInfo) anyTimeEnquiry (anyTimeInterrogation) reporting (statusReport) Initiating Entity VLR
1577 1578 Priority high 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607
SGSN VLR/SGSN MSC msPurging SGSN GMSC
VLR
GMSC gsmSCF VLR
1608 1609 1610
1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 Priority low
Location Services locationSvcGateway (sendRoutingInfoforLCS/v3)
Subscriber Controlled Inputs (Supplementary Services) networkFunctionalSs (registerSS), (eraseSS), (activateSS), (deactivateSS), (interrogateSS), (registerPassword), (processUnstructuredSS-Data/v1), (beginSubscriberActivity/v1) callCompletion (registerCCEntry), (eraseCCEntry) networkUnstructuredSs (processUnstructuredSS-Request/v2) imsiRetrieval (sendIMSI/v2) gprsLocationInfoRetrieval (sendRoutingInfoForGprs/v3/v4) failureReport (failureReport/v3) authenticationFailureReport (authenticationFailureReport/v3)
GMLC
VLR
VLR VLR VLR GGSN/SGSN GGSN/SGSN VLR/SGSN
1635 1636
NOTE:
The application context name is the last component but one of the object identifier. Operation names are given in brackets for information with "/vn" appended to vn only operations.
130
1637
131 Release 4 132 133
34
3GPP TS 29.002 V4.17.0 (2006-06)
Table 5.1/3: Priorities of Application Contexts for SGSN as Responder
Initiating Entity HLR HLR HLR HLR
1638 Responder = SGSN 1639 Priority high 1640 Mobility and Location Register Management 1641 locationCancel 1642 (cancelLocation v3) 1643 reset 1644 (reset) 1645 subscriberDataMngt 1646 (insertSubscriberData v3), 1647 (deleteSubscriberData v3) 1648 tracing 1649 (activateTraceMode), 1650 (deactivateTraceMode) 1651 1652 Short Message Service 1653 shortMsgMT-Relay 1654 (MT-ForwardSM v3) 1655 (forwardSM v1/v2) 1656 1657 Location Services 1658 1659 locationSvcEnquiry 1660 (provideSubscriberLocation v3) 1661 1662 Network-Requested PDP context activation 1663 gprsNotify HLR 1664 (noteMsPresentForGprs v3), 1665 1666 Priority low
MSC
GMLC
1667 1668
NOTE:
The application context name is the last component but one of the object identifier. Operation names are given in brackets for information with "/vn" appended to vn.
134
1669
135 Release 4 136 137
35
3GPP TS 29.002 V4.17.0 (2006-06)
Table 5.1/2: Priorities of Application Contexts for MSC/VLR as Responder
Initiating Entity MSC
Responder = MSC/VLR Priority high Handover handoverControl (prepareHandover/v2/v3), (performHandover/v1)
Group call and Broadcast call groupCallControl (prepareGroupCall/v3)
Mobility and Location Register Management locationCancel (cancelLocation) reset (reset) immediateTermination (istCommand/v3) interVlrInfoRetrieval (sendIdentification/v2/v3), (sendParameters/v1) subscriberDataMngt (insertSubscriberData), (deleteSubscriberData) tracing (activateTraceMode), (deactivateTraceMode) Short Message Service shortMsgMO-Relay (MO-ForwardSM v3) (forwardSM v1/v2) shortMsgMT-Relay (MT-ForwardSM v3) (forwardSM v1/v2) shortMsgAlert (alertServiceCentre/v2), (alertServiceCentreWithoutResult/v1) Mobile Terminating Traffic roamingNbEnquiry (provideRoamingNumber) callControlTransfer (resumeCallHandling) subscriberInfoEnquiry (provideSubscriberInformation) HLR (remoteUserFree) (SetReportingState)
MSC
HLR HLR HLR VLR HLR HLR
MSC/SGSN MSC HLR
HLR MSC HLR reporting
Location Services locationSvcEnquiry (provideSubscriberLocation v3)
Network-Initiated USSD networkUnstructuredSs (unstructuredSS-Request/v2), (unstructuredSS-Notify/v2) Priority low
GMLC
HLR
1671 1672
NOTE:
The application context name is the last component but one of the object identifier. Operation names are given in brackets for information with "/vn" appended to vn only operations.
138
1673
139 Release 4 140 141
36
3GPP TS 29.002 V4.17.0 (2006-06)
5.1.3 Congestion control for Signalling System No. 7
1674 The requirements of SS7 Congestion control have to be taken into account as far as possible. 1675 Means that could be applied to achieve the required traffic reductions are described in clauses 5.1.1 and 5.1.2.
1676 1677
5.2 Compatibility
5.2.1 General
1678 The present document of the Mobile Application Part is designed in such a way that an implementation which conforms 1679 to it can also conform to the Mobile Application Part operational version 1 specifications, except on the MSC-VLR 1680 interface. 1681 A version negotiation mechanism based on the use of an application-context-name is used to negotiate the protocol 1682 version used between two entities for supporting a MAP-user signalling procedure. 1683 1684 1685 1686
When starting a signalling procedure, the MAP-user supplies an application-context-name to the MAP-provider. This name refers to the set of application layer communication capabilities required for this dialogue. This refers to the required TC facilities (e.g. version 1 or 2) and the list of operation packages (i.e. set of operations) from which operations can be invoked during the dialogue.
1687 A version one application-context-name may only be transferred to the peer user in a MAP-U-ABORT to an entity of 1688 version two or higher (i.e. to trigger a dialogue which involves only communication capabilities defined for MAP 1689 operational version 1). 1690 1691 1692 1693 1694 1695 1696 1697
If the proposed application-context-name can be supported by the responding entity the dialogue continues on this basis otherwise the dialogue is refused and the initiating user needs to start a new dialogue, which involves another application-context-name which requires less communication capabilities but provides similar functionality (if possible). When a signalling procedure can be supported by several application contexts that differ by their version number, the MAP-User needs to select a name. It can either select the name that corresponds to the highest version it supports or follow a more specific strategy so that the number of protocol fallbacks due to version compatibility problems is minimised.
1698
5.2.2 Strategy for selecting the Application Context (AC) version
1699 A method should be used to minimise the number of protocol fall-backs which would occur sometimes if the highest 1700 supported AC-Name were always the one selected by GSM entities when initiating a dialogue. The following method is 1701 an example that can be used mainly at transitory phase stage when the network is one of mixed phase entities.
1702 5.2.2.1
1703 1704 1705 1706 1707 1708 1709
Proposed method
A table (table 1) may be set up by administrative action to define the highest application context (AC) version supported by each destination; a destination may be another node within the same or a different PLMN, or another PLMN considered as a single entity. The destination may be defined by an E.164 number or an E.214 number derived from an IMSI or in North America (World Zone 1) by an E.164 number or an IMSI (E.212 number). The table also includes the date when each destination is expected to be able to handle at least one AC of the latest version of the MAP protocol. When this date is reached, the application context supported by the node is marked as "unknown", which will trigger the use of table 2.
1710 A second table (table 2) contains an entry for each destination that has an entry in table 1. For a given entity, the entry 1711 in table 2 may be a single application context version or a vector of different versions applying to different application 1712 contexts for that entity. Table 2 is managed as described in clause 5.2.2.2. 1713 The data for each destination will go through the following states: 1714 1715
a) the version shown in table 1 is "version n-1", where 'n' is the highest version existing in this specification; table 2 is not used;
142
1716 1717 1718 1719
143 Release 4 144 145
37
3GPP TS 29.002 V4.17.0 (2006-06)
b) the version shown in table 1 is "unknown"; table 2 is used, and maintained as described in clause 5.2.2.2; c) when the PLMN operator declares that an entity (single node or entire PLMN) has been upgraded to support all the MAP version n ACs defined for the relevant interface, the version shown in table 1 is set to "version n" by administrative action; table 2 is no longer used, and the storage space may be recovered.
1720 5.2.2.2
Managing the version look-up table
1721 WHEN it receives a MAP-OPEN ind the MAP-User determines the originating entity number either using the 1722 originating address parameter or the originating reference parameter or retrieving it from the subscriber data using the 1723 IMSI or the MSISDN. 1724 IF the entity number is known: 1725 1726 1727 1728
THEN It updates (if required) the associated list of highest supported ACs. ELSE It creates an entry for this entity and includes the received AC-name in the list of highest supported ACs.
1729 WHEN starting a procedure, the originating MAP-user looks up its version control table. 1730 IF the destination address is known and not timed-out. 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752
THEN It retrieves the appropriate AC-name and uses it IF the dialogue is accepted by the peer THEN It does not modify the version control table ELSE (this should never occur) It starts a new dialogue with the common highest version supported (based on information implicitly or explicitly provided by the peer). It replaces the old AC-name by the new one in the list of associated highest AC supported. ELSE It uses the AC-name that corresponds to the highest version it supports. IF the dialogue is accepted by the peer. THEN It adds the destination node in its version control table and includes the AC-Name in the list of associated highest AC supported. ELSE It starts a new dialogue with the common highest version supported (based on information implicitly or explicitly provided by the peer). IF the destination node was not known THEN It adds the destination node in its version control table and includes the new AC-Name in the list of associated highest AC supported.
146
1753 1754
147 Release 4 148 149
38
3GPP TS 29.002 V4.17.0 (2006-06)
ELSE It replaces the old AC-name by the new one in the list of highest supported AC and reset the timer.
1755 5.2.2.3
Optimising the method
1756 A table look-up may be avoided in some cases if both the HLR and the VLR or both the HLR and the SGSN store for 1757 each subscriber the version of the AC-name used at location updating. Then: 1758 1759 1760 1761 1762 1763 1764 1765 1766
for procedures which make use of the same application-context, the same AC-name (thus the same version) can be selected (without any table look-up) when the procedure is triggered; for procedures which make use of a different application-context but which includes one of the packages used by the location updating AC, the same version can be selected (without any table look-up) when the procedure is triggered; for HLR: Subscriber data modification (stand alone);
for VLR: Data Restoration.
1767 1768
6 Requirements concerning the use of SCCP and TC
6.1 Use of SCCP
1769 The Mobile Application Part (MAP) makes use of the services offered by the Signalling Connection Control Part 1770 (SCCP). 1771 MAP supports the following SCCP versions:
1772 1773
1774 1775 1776 1777 1778 1779 1780
Signalling Connection Control Part, Signalling System no. 7 CCITT (Blue Book SCCP); Signalling Connection Control Part, Signalling System no. 7 ITU-T Recommendation (07/96) Q.711 to Q.716 (White Book SCCP). Support of White Book SCCP at the receiving side shall be mandated from 00:01hrs, 1st July 2002(UTC). However, for signalling over the MAP E-interface to support inter-MSC handover/relocation, the support of White Book SCCP shall be mandated with immediate effect. A White Book SCCP message will fail if any signalling point used in the transfer of the message does not support White Book SCCP. Therefore it is recommended that the originator of the White Book SCCP message supports a drop back mechanism or route capability determination mechanism to interwork with signalling points that are beyond the control of GSM/UMTS network operators.
1781 In North America (World Zone 1) the national version of SCCP is used as specified in ANSI T1.112. Interworking 1782 between a PLMN in North America and a PLMN outside North America will involve an STP to translate between 1783 ANSI SCCP and ITU-T/CCITT SCCP. 1784 The SCCP is identified as an MTP3-user and the transport of SCCP messages between two entities shall be 1785 accomplished according to the 3GPP TS 29.202 [121].
1786
6.1.1 SCCP Class
1787 MAP will only make use of the connectionless classes (0 or 1) of the SCCP.
1788
6.1.2 Sub-System Number (SSN)
1789 The Application Entities (AEs) defined for MAP consist of several Application Service Elements (ASEs) and are 1790 addressed by sub-system numbers (SSNs). The SSNs for MAP are specified in 3GPP TS 23.003 [17].
150
1791 When the SGSN emulates MSC behaviour for processing messages (MAP-MO-FORWARD-SHORT-MESSAGE, 1792 MAP_CHECK_IMEI, MAP_SUBSCRIBER_LOCATION_REPORT) towards entities which do not support 1793 interworking to SGSNs, it shall use the MSC SSN in the calling party address instead of the SGSN SSN.
151 Release 4 152 153
39
3GPP TS 29.002 V4.17.0 (2006-06)
1794 1795 6.1.3.1
6.1.3 SCCP addressing
Introduction
1796 Within the GSM System there will be a need to communicate between entities within the same PLMN and in different 1797 PLMNs. Using the Mobile Application Part (MAP) for this function implies the use of Transaction Capabilities (TC) 1798 and the Signalling Connection Control Part (SCCP) of CCITT Signalling System No. 7. 1799 Only the entities that should be addressed are described below. If the CCITT or ITU-T SCCP is used, the format and 1800 coding of address parameters carried by the SCCP for that purpose shall comply with CCITT Recommendation Q.713 1801 with the following restrictions: 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823
1) Intra-PLMN addressing For communication between entities within the same PLMN, a MAP SSN shall always be included in the called and calling party addresses. All other aspects of SCCP addressing are network specific. 2) Inter-PLMN addressing a) Called Party Address SSN indicator = 1 (MAP SSN always included); Global title indicator = 0100 (Global title includes translation type, numbering plan, encoding scheme and nature of address indicator); the translation type field will be coded "00000000" (Not used). For call related messages for non-optimal routed calls (as described in 3GPP TS 23.066 [108]) directed to another PLMN the translation type field may be coded "10000000" (CRMNP); Routing indicator = 0 (Routing on global title);
b) Calling Party Address SSN indicator = 1 (MAP SSNs always included); Point code indicator = 0; Global title indicator = 0100 (Global title includes translation type, numbering plan, encoding scheme and nature of address indicator); Numbering Plan = 0001 (ISDN Numbering Plan, E.164; In Case of Inter-PLMN Signalling, the dialogue initiating entity and dialogue responding entity shall always include its own E.164 Global Title as Calling Party Address); the translation type field will be coded "00000000" (Not used); Routing indicator = 0 (Routing on Global Title).
1824 If ANSI T1.112 SCCP is used, the format and coding of address parameters carried by the SCCP for that purpose shall 1825 comply with ANSI specification T1.112 with the following restrictions: 1826 1827 1828 1829 1830
1) Intra-PLMN addressing For communication between entities within the same PLMN, a MAP SSN shall always be included in the called and calling party addresses. All other aspects of SCCP addressing are network specific. 2) Inter-PLMN addressing a) Called Party Address
154
1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847
155 Release 4 156 157
40
3GPP TS 29.002 V4.17.0 (2006-06)
SSN indicator = 1 (MAP SSN always included); Global title indicator = 0010 (Global title includes translation type); the Translation Type (TT) field will be coded as follows: TT = 9, if IMSI is included; TT = 14, if MSISDN is included; Or TT = 10, if Network Element is included. (If TT=10, then Number Portability GTT is not invoked, if TT=14, then Number Portability GTT may be invoked).
Routing indicator = 0 (Routing on global title);
b) Calling Party Address SSN indicator = 1 (MAP SSNs always included); Point code indicator = 0; Global Title indicator = 0010 (Global title includes translation type); TT = 9, if IMSI is included; TT = 14, if MSISDN is included; Or TT = 10, if Network Element is included. (If TT=10, then Number Portability GTT is not invoked, if TT=14, then Number Portability GTT may be invoked). Routing indicator = 0 (Routing on Global Title).
1848 If a Global Title translation is required for obtaining routeing information, one of the numbering plans E.164, E.212 and 1849 E.214 is applicable. 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870
E.212 numbering plan. When CCITT or ITU-T SCCP is used, an E.212 number must not be included as Global Title in an SCCP UNITDATA message. The translation of an E.212 number into a Mobile Global Title is applicable in a dialogue initiating VLR, SGSN or GGSN if the routeing information towards the HLR is derived from the subscriber's IMSI. In World Zone 1 when ANSI SCCP is used, the IMSI (E.212 number) is used as a Global Title to address the HLR. When an MS moves from one VLR service area to another, the new VLR may derive the address of the previous VLR from the Location Area Identification provided by the MS in the location registration request. The PLMN where the previous VLR is located is identified by the E.212 numbering plan elements of the Location Area Identification, i.e. the Mobile Country Code (MCC) and the Mobile Network Code (MNC).
E.214 and E.164 numbering plans. When CCITT or ITU-T SCCP is used, only address information belonging to either E.214 or E.164 numbering plan is allowed to be included as Global Title in the Called and Calling Party Address. In World Zone 1 when ANSI SCCP is used, the IMSI (E.212 number) is used as a Global Title to address the HLR. If the Calling Party Address associated with the dialogue initiating message contains a Global Title, the sending network entity shall include its E.164 entity number. When receiving an SCCP UNITDATA message, SCCP shall accept either of the valid numbering plans in the Called Party Address and in the Calling Party Address. When CCITT or ITU-T SCCP is used and an N-UNITDATA-REQUEST primitive from TC is received, SCCP shall accept an E.164 number or an E.214 number in the Called Address and in the Calling Address. In World Zone 1 when ANSI SCCP is used, the IMSI (E.212 number) is used instead of E.214 number.
1871 The following clauses describe the method of SCCP addressing appropriate for each entity both for the simple 1872 intra-PLMN case and where an inter-PLMN communication is required. The following entities are considered:
158
1873 1874 1875 1876 1877 1878 1879 1880 1881 1882
159 Release 4 160 161
41
3GPP TS 29.002 V4.17.0 (2006-06)
the Mobile-services Switching Centre (MSC); the Home location Register (HLR); the Visitor Location Register (VLR); the Gateway Mobile-services Switching Centre (GMSC); the GSM Service Control Function (gsmSCF); the Interworking Mobile-services Switching Centre (IWMSC); the Shared Inter Working Function (SIWF); the Serving GPRS Support Node (SGSN); the Gateway GPRS Support Node (GGSN); the Gateway Mobile Location Centre (GMLC).
1883 6.1.3.2
The Mobile-services Switching Centre (MSC)
1884 There are several cases where it is necessary to address the MSC.
1885 6.1.3.2.1
MSC interaction during handover or relocation
1886 The address is derived from the target Cell id or from the target RNC id.
1887 6.1.3.2.2
MSC for short message routing
1888 When a short message has to be routed to an MS, the GMSC addresses the VMSC by an MSC identity received from 1889 the HLR that complies with E.164 rules. 1890 For MS originating short message, the IWMSC address is derived from the Service Centre address.
1891 6.1.3.2.3
MSC for location request routing
1892 When a location request for a particular MS needs to be sent to the MSs VMSC, the GMLC addresses the VMSC using 1893 an E.164 address received from the MSs HLR.
1894 6.1.3.2.4
MSC for LMU Control
1895 When a control message has to be routed to an LMU from an SMLC, the SMLC addresses the serving MSC for the 1896 LMU using an E.164 address.
1897 6.1.3.3
The Home Location Register (HLR)
1898 There are several cases where the HLR has to be addressed.
1899 6.1.3.3.1
1900 1901 1902 1903
During call set-up
When a call is initiated the HLR of the called mobile subscriber will be interrogated to discover the whereabouts of the MS. The addressing required by the SCCP will be derived from the MSISDN dialled by the calling subscriber. The dialled number will be translated into either an SPC, in the case of communications within a PLMN, or a Global Title if other networks are involved (i.e. if the communication is across a PLMN boundary).
1904 If the calling subscriber is a fixed network subscriber, the interrogation can be initiated from the Gateway MSC of the 1905 home PLMN in the general case. If the topology of the network allows it, the interrogation could be initiated from any 1906 Signalling Point that has MAP capabilities, e.g. local exchange, outgoing International Switching Centre (ISC), etc.
162
1907 6.1.3.3.2
1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918
163 Release 4 164 165
42
3GPP TS 29.002 V4.17.0 (2006-06)
Before location updating completion
When an MS registers for the first time in a VLR, the VLR has to initiate the update location dialogue with the MS's HLR and a preceding dialogue for authentication information retrieval if the authentication information must be retrieved from the HLR. When initiating either of these dialogues, the only data for addressing the HLR that the VLR has available is contained in the IMSI, and addressing information for SCCP must be derived from it. When continuing the established update location dialogue (as with any other dialogue), the VLR must derive the routeing information towards the HLR from the Calling Party Address received with the first responding CONTINUE message until the dialogue terminating message is received. This means that the VLR must be able to address the HLR based on: an E.214 Mobile Global Title originally derived by the VLR from the IMSI (when CCITT or ITU-T SCCP is used), or an E.212 number originally derived from IMSI (when ANSI SCCP is used, an IMSI); or an E.164 HLR address; or in the case of intra-PLMN signalling, an SPC.
1919 When answering with Global Title to the VLR, the HLR shall insert its E.164 address in the Calling Party Address of 1920 the SCCP message containing the first responding CONTINUE message. 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932
If the HLR is in the same PLMN as the VLR, local translation tables may exist to derive an SPC. For authentication information retrieval and location updating via the international PSTN/ISDN signalling network that requires the use of CCITT or ITU-T SCCP, the Global Title must be derived from the IMSI, using the principles contained in CCITT Recommendation E.214 and the Numbering Plan Indicator (NPI) value referenced by the SCCP Specifications. In World Zone 1 where the ANSI SCCP is used, IMSI (E.212 number) is used as Global Title. A summary of the translation from the IMSI (CCITT Recommendation E.212) to Mobile Global Title (described in CCITT Recommendation E.214) is shown below: E.212 Mobile Country Code translates to E.164 Country Code; E.212 Mobile Network Code translates to E.164 National Destination Code; E.212 Mobile Subscriber Identification Number (MSIN) is carried unchanged if within the E.164 number maximum length (15 digits). If the Mobile Global Title is more than 15 digits the number is truncated to 15 by deleting the least significant digits.
1933 This translation will be done either at the application or at SCCP level in the VLR. The Mobile Global Title thus 1934 derived will be used to address the HLR. 1935 If location updating is triggered by an MS that roams from one MSC Area into a different MSC Area served by the 1936 same VLR, the VLR shall address the HLR in the same way as if the MS registers for the first time in the VLR.
1937 6.1.3.3.3
1938 1939 1940 1941 1942 1943
After location updating completion
In this case, the subscriber's basic MSISDN has been received from the HLR during the subscriber data retrieval procedure as well as the HLR number constituting a parameter of the MAP message indicating successful completion of the update location dialogue. From either of these E.164 numbers the address information for initiating dialogues with the roaming subscriber's HLR can be derived. Also the subscriber's IMSI may be used for establishing the routeing information towards the HLR. This may apply in particular if the dialogue with the HLR is triggered by subscriber controlled input.
1944 Thus the SCCP address of the roaming subscriber's HLR may be an SPC, or it may be a Global title consisting of the 1945 E.164 MSISDN or the E.164 number allocated to the HLR or either the E.214 Mobile Global Title derived from the 1946 IMSI if CCITT or ITU-T SCCP is used, or the IMSI if ANSI SCCP is used (ANSI SCCP is used in World Zone 1).
166
1947 6.1.3.3.4
1948 1949 1950 1951 1952 1953 1954 1955 1956
167 Release 4 168 169
43
3GPP TS 29.002 V4.17.0 (2006-06)
VLR restoration
If a roaming number is requested by the HLR for an IMSI that has no data record in the interrogated VLR, the VLR provides the roaming number in the dialogue terminating message. Subsequently the VLR must retrieve the authentication data from the MS's HLR, if required, and must then trigger the restore data procedure. For this purpose, the VLR has to initiate in succession two independent dialogues with the MS's HLR. The MTP and SCCP address information needed for routeing towards the HLR can be derived from the IMSI received as a parameter of the MAP message requesting the roaming number. In this case, the IMSI received from the HLR in the roaming number request shall be processed in the same way as the IMSI that is received from an MS that registers for the first time within a VLR. Alternatively to the IMSI, the Calling Party Address associated with the roaming number request may be used to obtain the routeing information towards the HLR.
1957 6.1.3.3.5
1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974
During Network-Requested PDP Context Activation
When receiving a PDP PDU the GGSN may interrogate the HLR of the MS for information retrieval. When initiating such a dialogue, the only data for addressing the HLR that the GGSN has available is contained in the IMSI, and addressing information must be derived from it. The IMSI is obtained from the IP address or the X.25 address in the incoming IP message by means of a translation table. This means that the GGSN shall be able to address the HLR based on an E.214, (if CCITT or ITU-T SCCP is used), or E.212 (if ANSI SCCP is used), Mobile Global Title originally derived by the GGSN from the IMSI in the case of inter-PLMN signalling. In the case of intra-PLMN signalling, an SPC may also be used. If the HLR is in the same PLMN as the GGSN, local translation tables may exist to derive an SPC. For information retrieval via the international PSTN/ISDN signalling network, the Global title must be derived from the IMSI, using the principles contained in CCITT Recommendation E.214 and the Numbering Plan Indicator (NPI) value referenced by the SCCP Specifications. A summary of the translation from the IMSI (CCITT Recommendation E.212) to Mobile Global Title (described in CCITT Recommendation E.214) is shown below: E.212 Mobile Country Code translates to E.164 Country Code; E.212 Mobile Network Code translates to E.164 National Destination Code; E.212 Mobile Subscriber Identification Number (MSIN) is carried unchanged if within the E.164 number maximum length (15 digits). If the Mobile Global Title is more than 15 digits the number is truncated to 15 by deleting the least significant digits.
1975 This translation will be done either at the application or at SCCP level in the GGSN. The Mobile Global Title thus 1976 derived will be used to address the HLR.
1977 6.1.3.3.6
1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994
Before GPRS location updating completion
When an MS registers for the first time in an SGSN, the SGSN has to initiate the update location dialogue with the MS's HLR and a preceding dialogue for authentication information retrieval if the authentication information must be retrieved from the HLR. When initiating either of these dialogues, the only data for addressing the HLR that the SGSN has available is contained in the IMSI, and addressing information for SCCP must be derived from it. When continuing the established update location dialogue (as with any other dialogue), the SGSN must derive the routeing information towards the HLR from the Calling Party Address received with the first responding CONTINUE message until the dialogue terminating message is received. This means that the SGSN must be able to address the HLR based on: an E.214 (if CCITT or ITU-T SCCP is used) or E.212 (if ANSI SCCP is used) Mobile Global Title originally derived by the SGSN from the IMSI; or an E.164 HLR address; or in the case of intra-PLMN signalling, an SPC.
If the HLR is in the same PLMN as the SGSN, local translation tables may exist to derive an SPC. For authentication information retrieval and location updating via the international PSTN/ISDN signalling network, the Global title must be derived from the IMSI, using the principles contained in CCITT Recommendation E.214 and the Numbering Plan Indicator (NPI) value referenced by the SCCP Specifications. A summary of the translation from the IMSI (CCITT Recommendation E.212) to Mobile Global Title (described in CCITT Recommendation E.214) is shown below: E.212 Mobile Country Code translates to E.164 Country Code;
170
1995 1996 1997 1998
171 Release 4 172 173
44
3GPP TS 29.002 V4.17.0 (2006-06)
E.212 Mobile Network Code translates to E.164 National Destination Code; E.212 Mobile Subscriber Identification Number (MSIN) is carried unchanged if within the E.164 number maximum length (15 digits). If the Mobile Global Title is more than 15 digits the number is truncated to 15 by deleting the least significant digits.
1999 This translation will be done either at the application or at SCCP level in the SGSN. The Mobile Global Title thus 2000 derived will be used to address the HLR.
2001 6.1.3.3.7
2002 2003 2004 2005 2006
After GPRS location updating completion
In this case, the subscriber's Basic MSISDN has been received from the HLR during the subscriber data retrieval procedure as well as the HLR number constituting a parameter of the MAP message indicating successful completion of the update location dialogue. From either of these E.164 numbers the address information for initiating dialogues with the roaming subscriber's HLR can be derived. Also the subscriber's IMSI may be used for establishing the routeing information towards the HLR.
2007 Thus the SCCP address of the roaming subscriber's HLR may be an SPC, or it may be a Global title consisting of the 2008 E.164 MSISDN or the E.164 number allocated to the HLR or the E.214 Mobile Global Title derived from the IMSI.
2009 6.1.3.3.8
2010 2011 2012 2013
Query for a Location Request
For a location request from an external client, the GMLC needs to address the home HLR of the target MS to obtain the address of the target MSs serving MSC. The GMLC uses either the international E.164 MSISDN, the international E.214 number (if CCITT or ITU-T SCCP is used) or the international E.212 number (if ANSI SCCP is used) of the MS as means to route a query to the HLR.
2014 6.1.3.4
The Visitor Location Register (VLR)
2015 There are several cases when the VLR needs to be addressed.
2016 6.1.3.4.1
Inter-VLR information retrieval
2017 When an MS moves from one VLR service area to another, the new VLR may request the IMSI and authentication sets 2018 from the previous VLR. The new VLR derives the address of the previous VLR from the Location Area Identification 2019 provided by the MS in the location registration request.
2020 6.1.3.4.2
HLR request
2021 The HLR will only request information from a VLR if it is aware that one of its subscribers is in the VLR service area. 2022 This means that a location updating dialogue initiated by the VLR has been successfully completed, i.e. the HLR has 2023 indicated successful completion of the update location procedure to the VLR. 2024 2025 2026 2027 2028
When initiating dialogues towards the VLR after successful completion of location updating, the routeing information used by the HLR is derived from the E.164 VLR number received as a parameter of the MAP message initiating the update location dialogue. If the VLR is in the same PLMN as the HLR, the VLR may be addressed directly by an SPC derived from the E.164 VLR number. For dialogues via the international PSTN/ISDN signalling network, presence of the E.164 VLR number in the Called Party Address is required.
2029 6.1.3.5
The Interworking MSC (IWMSC) for Short Message Service
2030 The IWMSC is the interface between the mobile network and the network to access to the Short Message Service 2031 Centre. This exchange has an E.164 address known in the SGSN or in the MSC.
2032 6.1.3.6
The Equipment Identity Register (EIR)
2033 The EIR address is either unique or could be derived from the IMEI. The type of address is not defined.
174
2034 6.1.3.7
175 Release 4 176 177
45
3GPP TS 29.002 V4.17.0 (2006-06)
The Shared Inter Working Function (SIWF)
2035 When the Visited MSC detects a data or fax call and the IWF in the V-MSC cannot handle the required service an 2036 SIWF can be invoked. The SIWF is addressed with an E.164 number.
2037 6.1.3.8
2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050
The Serving GPRS Support Node (SGSN)
The HLR will initiate dialogues towards the SGSN if it is aware that one of its subscribers is in the SGSN serving area. This means that a GPRS location updating has been successfully completed, i.e., the HLR has indicated successful completion of the GPRS location update to the SGSN. The routeing information used by the HLR is derived form the E.164 SGSN number received as parameter of the MAP message initiating the GPRS update location procedure. If the SGSN is in the same PLMN as the HLR, the SGSN may be addressed directly by an SPC derived from the E.164 SGSN number. For dialogues via the international PSTN/ISDN signalling network, the presence of the E.164 SGSN number in the Called Party Address is required. When the GMSC initiates dialogues towards the SGSN the SGSN (MAP) SSN (See 3GPP TS 23.003 [17]) shall be included in the called party address. The routeing information used by the GMSC is derived from the E.164 SGSN number received as a parameter of the MAP message initiating the forward short message procedure. If the GMSC does not support the GPRS functionality the MSC (MAP) SSN value shall be included in the called party address. NOTE: Every VMSC and SGSN shall have uniquely identifiable application using E.164 numbers, for the purpose of SMS over GPRS when the GMSC does not support the GPRS functionality.
2051 6.1.3.9
2052 2053 2054 2055
The Gateway GPRS Support Node (GGSN)
The GGSN provides interworking with external packet-switched networks, network screens and routing of the Network-Requested PDP Context activation. If a Network-Requested PDP Context activation fails, the HLR will alert the GGSN when the subscriber becomes reachable. The HLR will use the E.164 GGSN number received as parameter of the MAP message reporting the failure.
2056 6.1.3.10
The Gateway MSC (GMSC) for Short Message Service
2057 The GMSC provides interworking with the network to access the Short Message Service Centre, the mobile network 2058 and routing of Send Routing Info For SM. The GMSC has on E.164 address known in the HLR, SGSN or MSC.
2059 6.1.3.10A 2060 6.1.3.10A.1 2061 6.1.3.10A.2 2062 6.1.3.10B
2063 2064 2065 2066
Void
Void Void
The Gateway Mobile Location Centre (GMLC)
The GMLC initiates location requests on behalf of external clients. The E.164 address of the GMLC is provided to an HLR when the GMLC requests a serving MSC address or SGSN address from the HLR for a target MS. The E.164 address of the GMLC is also provided to a serving MSC or SGSN when the GMLC requests the location of a target MS served by this MSC or SGSN.
2067 6.1.3.11
Summary table
2068 The following tables summarise the SCCP address used for invoke operations. As a principle, within a PLMN either an 2069 SPC or a GT may be used (network operation option), whereas when addressing an entity outside the PLMN the GT 2070 must be used. The address type mentioned in the table (e.g. MSISDN) is used as GT or to derive the SPC. 2071 For a response, the originating address passed in the invoke is used as SCCP Called Party Address. For extra-PLMN 2072 addressing the own E.164 entity address is used as SCCP Calling Party Address; for intra-PLMN addressing an SPC 2073 derived from the entity number may be used instead. When using an SPC, the SPC may be taken directly from MTP.
178
2074
179 Release 4 180 181
46
3GPP TS 29.002 V4.17.0 (2006-06)
Table 6.1/1
182
183 Release 4 184 185 to from
47 fixed net work
-----
3GPP TS 29.002 V4.17.0 (2006-06) EIR
-----
HLR
E:GT T:MSISDN ---
VLR
--I:SPC/GT E:GT T:VLR NUMBER I:SPC/GT E:GT T:VLR NUMBER
MSC
-----
gsmSCF
--I:SPC/GT E:GT T:gsmSCF NUMBER I:SPC/GT E:GT T:gsmSCF NUMBER
SIWF
-----
SGSN
--I:SPC/GT E:GT T:SGSN NUMBER ---
GGSN
--I:SPC/GT E:GT T:GGSN NUMBER ---
fixed network Home Location Register Visitor Location Register
---
mobileservices switching centre gsm Service Control Function Shared Inter Working Function Serving GPRS Support Node Gateway GPRS Support Node Gateway Mobile Location Centre
---
I:SPC/GT E:GT T:MGT (outside World Zone 1)/MSISDN (World Zone 1/)HLR NUMBER (note) I:SPC/GT E:GT T:MSISDN I:SPC/GT E:GT T:MSISDN ---
---
---
---
I:SPC/GT E:GT T:VLR NUMBER ---
I:SPC/GT E:GT T:MSC NUMBER ---
I:SPC/GT E:GT T:EIR NUMBER ---
I:SPC/GT E:GT T:gsmSCF NUMBER ---
I:SPC/GT E:GT T:SIWF NUMBER ---
I:SPC/GT E:GT T:SGSN NUMBER ---
---
---
---
---
---
I:SPC/GT E:GT T:MSC NUMBER I:SPC/GT E:GT T:MSC NUMBER ---
---
---
---
---
---
---
I:SPC/GT E:GT T:MGT/ MSISDN/HL R NUMBER I:SPC/GT E:GT T:MGT I:SPC/GT
---
I:SPC/GT E:GT T:EIR NUMBER ---
---
---
---
---
---
---
---
---
---
---
---
---
I:SPC/GT
---
---
---
I:SPC/GT
---
E:GT
T:MSISDN, MGT (outside World Zone 1) or IMSI (World Zone 1) (note)
E:GT
T:MSC NUMBER
E:GT
T:SGSN NUMBER
186
187 Release 4 48 3GPP TS 29.002 V4.17.0 (2006-06) 188 189 I: Intra-PLMN. E: Extra (Inter)-PLMN. T: Address Type. GT: Global Title. MGT: E.214 Mobile Global Title. SPC: Signalling Point Code. NOTE: For initiating the location updating procedure and an authentication information retrieval from the HLR preceding it, the VLR has to derive the HLR address from the IMSI of the MS. The result can be an SPC or an E.214 Mobile Global Title if CCITT or ITU-T SCCP is used, or IMSI itself if ANSI SCCP is used (ANSI SCCP is used in World Zone 1). When continuing the established update location dialogue (as with any other dialogue) the VLR must derive the routeing information towards the HLR from the Calling Party Address received with the first responding CONTINUE message until the dialogue terminating message is received. For transactions invoked by the VLR after update location completion, the VLR may derive the information for addressing the HLR from addresses received in the course of the update location procedure (MSISDN or HLR number) or from the IMSI. When invoking the Restore Data procedure and an authentication information retrieval from the HLR preceding it, the VLR must derive the information for addressing the HLR from the address information received in association with the roaming number request. This may be either the IMSI received as a parameter of the MAP message requesting the Roaming Number or the Calling Party Address associated with the MAP message requesting the Roaming Number. The gsmSCF shall be addressed using more than one Global Title number. The first Global Title number is used to address a gsmSCF for MAP. The second Global Title number is used to address a gsmSCF for CAP. For querying the HLR to obtain the VMSC address to support location services, the GMLC has to derive the HLR address from either the MSISDN or IMSI of the target MS. When using the IMSI, the result can be an SPC or an E.214 Mobile Global Title if CCITT or ITU-T SCCP is used, or IMSI itself if ANSI SCCP is used (ANSI SCCP is used in World Zone 1).
2075 2076
to from fixed network Home Location Register Visitor Location Register Mobile-services Switching Centre gsm Service Control Function Shared Inter Working Function Serving GPRS Support Node Gateway GPRS Support Node Gateway Mobile Location Centre I: Intra-PLMN. E: Extra (Inter)-PLMN. T: Address Type. GT: Global Title. MGT: E.214 Mobile Global Title. SPC: Signalling Point Code.
Table 6.1/2
GMLC
------I:SPC/GT E:GT T:MLC Number I:SPC/GT E:GT T:MSISDN ---
I:SPC/GT E:GT T:MLC Number ---
2077
190
191 Release 4 192 193
49
3GPP TS 29.002 V4.17.0 (2006-06)
2078
6.2 Use of TC
2079 The Mobile Application part makes use of the services offered by the Transaction Capabilities (TC) of Signalling 2080 System No. 7. ETS 300 287, which is based on CCITT White Book Recommendations Q.771 to Q.775, should be 2081 consulted for the full specification of TC. 2082 The MAP uses all the services provided by TC except the ones related to the unstructured dialogue facility. 2083 From a modelling perspective, the MAP is viewed as a single Application Service Element. Further structuring of it is 2084 for further study. 2085 Transaction Capabilities refers to a protocol structure above the network layer interface (i.e., the SCCP service 2086 interface) up to the application layer including common application service elements but not the specific application 2087 service elements using them. 2088 TC is structured as a Component sub-layer above a Transaction sub-layer. 2089 The Component sub-layer provides two types of application services: services for the control of end-to-end dialogues 2090 and services for Remote Operation handling. These services are accessed using the TC-Dialogue handling primitives 2091 and TC-Component handling primitives respectively. 2092 Services for dialogue control include the ability to exchange information related to application-context negotiation as 2093 well as initialisation data. 2094 2095 2096 2097 2098 2099 2100
Services for Remote Operation handling provide for the exchange of protocol data units invoking tasks (operations), and reporting their outcomes (results or errors) plus any non-application-specific protocol errors detected by the component sub-layer. The reporting of application-specific protocol errors by the TC user, as distinct from application process errors, is also provided. The Transaction sub-layer provides a simple end-to-end connection association service over which several related protocol data units (i.e. built by the Component Sub-Layer) can be exchanged. A Transaction termination can be prearranged (no indication provided to the TC user) or basic (indication provided).
2101 2102
7 General on MAP services
7.1 Terminology and definitions
2103 The term service is used in clauses 7 to 12 as defined in CCITT Recommendation X.200. The service definition 2104 conventions of CCITT Recommendation X.210 are also used.
2105
7.2 Modelling principles
2106 MAP provides its users with a specified set of services and can be viewed by its users as a "black box" or abstract 2107 machine representing the MAP service-provider. The service interface can then be depicted as shown in figure 7.2/1.
M A P s e r v ic e - u s e r S e r v ic e In te r f a c e M A P S e r v ic e - p r o v id e r
M A P s e r v ic e - u s e r
2108
2109
Figure 7.2/1: Modelling principles
2110 The MAP service-users interact with the MAP service-provider by issuing or receiving MAP service-primitives at the 2111 service interface.
194
2112 A MAP service-user may receive services from several instances of the MAP service-provider at the same time. In such 2113 cases the overall procedure is synchronised by the service-user. 2114 The MAP service-primitives are named using the following notation: 2115
195 Release 4 196 197
50
3GPP TS 29.002 V4.17.0 (2006-06)
MAP-ServicePrimitiveName type
2116 where type can be any of: request (req), indication (ind), response (rsp) or confirm (cnf). (In the user arrow diagrams 2117 type is not indicated in the case of req/ind and indicated as "ack" in the case of rsp/cnf). 2118 The services are further classified as unconfirmed-service, confirmed-service and provider-initiated-service where the 2119 first two categories refer to whether or not the service is confirmed by the service-provider. The confirmation may or 2120 may not correspond to a response provided by the other service-user. 2121 MAP services are also classified as common MAP services that are available to all MAP service-users, and MAP 2122 service-user specific services, which are services available to one or several, but not all, MAP service-users. 2123 A MAP dialogue is defined as an exchange of information between two MAP users in order to perform a common task. 2124 A MAP dialogue will consist of one or several MAP services.
2125
7.3 Common MAP services
for establishing and clearing MAP dialogues between peer MAP service-users; for accessing functions supported by layers below the applications layer; for reporting abnormal situations; for handling of different MAP versions; for testing whether or not a persistent MAP dialogue is still active at each side.
2126 All MAP service-users require access to services for performing basic application layer functions: 2127 2128 2129 2130 2131
2132 For these purposes the following common services are defined: 2133 2134 2135 2136 2137 2138
MAP-OPEN service; MAP-CLOSE service; MAP-DELIMITER service; MAP-U-ABORT service; MAP-P-ABORT service; MAP-NOTICE service.
2139 In defining the service-primitives the following convention is used for categorising parameters: 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150
M O U C -
the inclusion of the parameter is mandatory. The M category can be used for any primitive type and specifies that the corresponding parameter must be present in the indicated primitive type; the inclusion of the parameter is a service-provider option. The O category can be used in indication and confirm type primitives and is used for parameters that may optionally be included by the service-provider; the inclusion of the parameter is a service-user option. The U category can be used in request and response type primitives. The inclusion of the corresponding parameter is the choice of the service-user; the inclusion of the parameter is conditional. The C category can be used for the following purposes: to indicate that if the parameter is received from another entity it must be included for the service being considered; to indicate that the service user must decide whether to include the parameter, based on the context on which the service is used;
198
2151 2152 2153 2154 2155 2156 2157 2158
199 Release 4 200 201
51
3GPP TS 29.002 V4.17.0 (2006-06)
to indicate that one of a number of mutually exclusive parameters must be included (e.g. parameters indicating a positive result versus parameters indicating a negative result); to indicate that a service user optional parameter (marked "U") or a conditional parameter (marked "C") presented by the service user in a request or response type primitive is to be presented to the service user in the corresponding indication or confirm type primitive; when appended to one of the above, this symbol means that the parameter takes the same value as the parameter appearing immediately to its left;
(=)
blank the parameter is not present.
2159 A primitive type may also be without parameters, i.e. no parameter is required with the primitive type; in this case the 2160 corresponding column of the table is empty.
2161
7.3.1 MAP-OPEN service
2162 This service is used for establishing a MAP dialogue between two MAP service-users. The service is a confirmed 2163 service with service primitives as shown in table 7.3/1. 2164
Parameters Application context name Destination address Destination reference Originating address Originating reference Specific information Responding address Result Refuse-reason Provider error
Table 7.3/1: Service-primitives for the MAP-OPEN service
Request M M U U U U Indication M(=) M(=) C(=) O C(=) C(=) Response U Confirm C(=)
U U M C
C(=) C(=) M(=) C(=) O
2165 2166 Application context name: 2167 This parameter identifies the type of application context being established. If the dialogue is accepted the received 2168 application context name shall be echoed. In case of refusal of dialogue this parameter shall indicate the highest version 2169 supported. 2170 Destination address: 2171 A valid SCCP address identifying the destination peer entity (see also clause 6). As an implementation option, this 2172 parameter may also, in the indication, be implicitly associated with the service access point at which the primitive is 2173 issued. 2174 Destination-reference: 2175 This parameter is a reference that refines the identification of the called process. It may be identical to Destination 2176 address but its value is to be carried at MAP level. Table 7.3/2 describes the MAP services using this parameter. Only 2177 these services are allowed to use it.
202
2178
203 Release 4 204 205
52
3GPP TS 29.002 V4.17.0 (2006-06)
Table 7.3/2: Use of the destination reference Reference type IMSI IMSI IMSI IMSI IMSI IMSI IMSI (note 1) IMSI (note 2) IMSI (note 2) IMSI (note 3) IMSI IMSI Use of the parameter Subscriber identity Subscriber identity Subscriber identity Subscriber identity Subscriber identity Subscriber identity Subscriber identity Subscriber identity Subscriber identity Subscriber identity Subscriber identity Subscriber identity
MAP service MAP-REGISTER-SS MAP-ERASE-SS MAP-ACTIVATE-SS MAP-DEACTIVATE-SS MAP-INTERROGATE-SS MAP-REGISTER-PASSWORD MAP-PROCESS-UNSTRUCTUREDSS-REQUEST MAP-UNSTRUCTUREDSS-REQUEST MAP-UNSTRUCTURED-SS-NOTIFY MAP-FORWARD-SHORT-MESSAGE MAP-REGISTER-CC-ENTRY MAP-ERASE-CC-ENTRY
2179 2180 2181 2182 2183 2185 2186
2184
NOTE 1: On the HLR - HLR interface and on the HLR - gsmSCF interface the Destination reference shall be either IMSI or MSISDN. NOTE 2: On the gsmSCF - HLR interface and on the HLR - HLR interface the Destination reference shall be either IMSI or MSISDN. NOTE 3: Only when the IMSI and the LMSI are received together from the HLR in the mobile terminated short message transfer.
2187 Originating address: 2188 A valid SCCP address identifying the requestor of a MAP dialogue (see also clause 6). As an implementation option, 2189 this parameter may also, in the request, be implicitly associated with the service access point at which the primitive is 2190 issued. 2191 Originating-reference: 2192 2193 2194 2195 2196
This parameter is a reference that refines the identification of the calling process. It may be identical to the Originating address but its value is to be carried at MAP level. Table 7.3/3 describes the MAP services using the parameter. Only these services are allowed to use it. Processing of the Originating-reference shall be performed according to the supplementary service descriptions and other service descriptions, e.g. operator determined barring. Furthermore the receiving entity may be able to use the value of the Originating-reference to screen the service indication.
206
2197
207 Release 4 208 209
53
3GPP TS 29.002 V4.17.0 (2006-06)
Table 7.3/3: Use of the originating reference Reference type ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String ISDN-Address-String (note) ISDN-Address-String (note) ISDN-Address-String ISDN-Address-String Use of the parameter Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address Originated entity address
MAP service MAP-REGISTER-SS MAP-ERASE-SS MAP-ACTIVATE-SS MAP-DEACTIVATE-SS MAP-INTERROGATE-SS MAP-REGISTER-PASSWORD MAP-PROCESS-UNSTRUCTUREDSS-REQUEST MAP-UNSTRUCTUREDSS-REQUEST MAP-UNSTRUCTUREDSS-NOTIFY MAP-REGISTER-CC-ENTRY MAP-ERASE-CC-ENTRY
2198 2199
NOTE:
The Originating reference may be omitted.
2200 Specific information: 2201 This parameter may be used for passing any user specific information. Establishment and processing of the Specific 2202 information is not specified by GSM and shall be performed according to operator specific requirements. 2203 Responding address: 2204 An address identifying the responding entity. The responding address is included if required by the context (e.g. if it is 2205 different from the destination address). 2206 Result: 2207 This parameter indicates whether the peer accepts the dialogue. 2208 Refuse reason: 2209 This parameter is present only if the Result parameter indicates that the dialogue is refused. It takes one of the following 2210 values:
2211 2212 2213 2214 2215 2216
-Application-context-not-supported; -Invalid-destination-reference; -Invalid-originating-reference; -No-reason-given; -Remote node not reachable; -Potential version incompatibility.
210
2217
211 Release 4 212 213
54
3GPP TS 29.002 V4.17.0 (2006-06)
7.3.2 MAP-CLOSE service
2218 This service is used for releasing a previously established MAP dialogue. The service may be invoked by either MAP 2219 service-user depending on rules defined within the service-user. The service is an unconfirmed service with parameters 2220 as shown in table 7.3/4. 2221
Table 7.3/4: Service-primitives for the MAP-CLOSE service
Parameters Release method Specific Information Request M U Indication C(=)
2222 2223 Release method: 2224 This parameter can take the following two values: 2225 2226 2227
normal release; in this case the primitive is mapped onto the protocol and sent to the peer; prearranged end; in this case the primitive is not mapped onto the protocol. Prearranged end is managed independently by the two users, i.e. only the request type primitive is required in this case.
2228 Specific information: 2229 This parameter may be used for passing any user specific information. Establishment and processing of the Specific 2230 information is not specified by GSM GSM and shall be performed according to operator specific requirements.
2231
7.3.3 MAP-DELIMITER service
2232 This service is used to explicitly request the transfer of the MAP protocol data units to the peer entities. 2233 See also clause 7.4 and 7.5 for the detailed use of the MAP-DELIMITER service. 2234 The service is an unconfirmed service with service-primitives as shown in table 7.3/5. 2235
Table 7.3/5: Service-primitives for the MAP-DELIMITER service
Parameters Request Indication
2236
2237
7.3.4 MAP-U-ABORT service
2238 This service enables the service-user to request the MAP dialogue to be aborted. The service is an unconfirmed service 2239 with service-primitives as shown in table 7.3/6. 2240
Table 7.3/6: Service-primitives for the MAP-U-ABORT service
Parameters User reason Diagnostic information Specific information Request M U U Indication M(=) C(=) C(=)
2241 2242 User reason: 2243 This parameter can take the following values: 2244 2245 2246
resource limitation (congestion); the requested user resource is unavailable due to congestion;
resource unavailable;
214
2247 2248 2249 2250 2251
215 Release 4 216 217
55
3GPP TS 29.002 V4.17.0 (2006-06)
the requested user resource is unavailable for reasons other than congestion; application procedure cancellation; the procedure is cancelled for reasons detailed in the diagnostic information parameter;
procedure error; processing of the procedure is terminated for procedural reasons.
2252 Diagnostic information: 2253 This parameter may be used to give additional information for some of the values of the user-reason parameter: 2254
Table 7.3/7: User reason and diagnostic information
User reason Resource limitation (congestion) Resource unavailable Application procedure cancellation Diagnostic information Short term/long term problem Handover cancellation/ Radio Channel release/ Network path release/ Call release/ Associated procedure failure/ Tandem dialogue released/ Remote operations failure -
Procedure error
2255 2256 Specific information: 2257 This parameter may be used for passing any user specific information. Establishment and processing of the Specific 2258 information is not specified by GSM and shall be performed according to operator specific requirements.
2259
7.3.5 MAP-P-ABORT service
2260 This service enables the MAP service-provider to abort a MAP dialogue. The service is a provider-initiated service with 2261 service-primitives as shown in table 7.3/8. 2262
Table 7.3/8: Service-primitives for the MAP-P-ABORT service
Parameters Provider reason Source Indication M M
2263 2264 Provider reason: 2265 This parameter indicates the reason for aborting the MAP dialogue: 2266 2267 2268 2269 2270 2271
provider malfunction; supporting dialogue/transaction released; resource limitation; maintenance activity; version incompatibility; abnormal MAP dialogue.
2272 Source: 2273 This parameter indicates the source of the abort. For Transaction Capabilities (TC) applications the parameter may take 2274 the following values:
218
2275 2276 2277
219 Release 4 220 221
56
3GPP TS 29.002 V4.17.0 (2006-06)
MAP problem; TC problem; network service problem. Table 7.3/9: Values of provider reason and source parameters and examples of corresponding events
Provider reason Provider malfunction Source MAP TC Corresponding event Malfunction at MAP level at peer entity "Unrecognised message type" or "Badly formatted transaction portion" or "Incorrect transaction portion" received in TC-P-ABORT "Abnormal dialogue" Malfunction at network service level at peer entity
2278 2279
Network service Supporting dialogue/ transaction released Resource limitation Maintenance activity Abnormal MAP dialogue Version incompatibility TC MAP TC MAP Network service MAP TC
"Unrecognised transaction ID" received in TC-ABORT Congestion towards MAP peer service-user "Resource limitation" received in TC-P-ABORT Maintenance at MAP peer service-user Maintenance at network peer service level MAP dialogue is not in accordance with specified application context A Provider Abort indicating "No common dialogue portion" is received in the dialogue initiated state
2280
2281
7.3.6 MAP-NOTICE service
2282 This service is used to notify the MAP service-user about protocol problems related to a MAP dialogue not affecting the 2283 state of the protocol machines. 2284 The service is a provider-initiated service with service-primitive as shown in table 7.3/10. 2285
Table 7.3/10: Service-primitive for the MAP-NOTICE service
Parameters Problem diagnostic Indication M
2286 2287 Problem diagnostic: 2288 This parameter can take one of the following values: 2289 2290 2291 2292
abnormal event detected by the peer; response rejected by the peer; abnormal event received from the peer; message cannot be delivered to the peer.
222
2293 2294 2295 2296 2297
223 Release 4 224 225
57
3GPP TS 29.002 V4.17.0 (2006-06)
7.3.7 void 7.3.8 void 7.3.9 void 7.3.10 void
7.4 Sequencing of services
Opening: The MAP-OPEN service is invoked before any user specific service-primitive is accepted. The sequence may contain none, one or several user specific service-primitives. If no user specific service-primitive is contained between the MAP-OPEN and the MAP-DELIMITER primitives, then this will correspond to sending an empty Begin message in TC. If more than one user specific service-primitive is included, all are to be sent in the same Begin message. The sequence ends with a MAP-DELIMITER primitive. Continuing: This sequence may not be present in some MAP dialogues. If it is present, it ends with a MAP-DELIMITER primitive. If more than one user specific service-primitive is included, all are to be included in the same Continue message. Closing: The sequence can only appear after an opening sequence or a continuing sequence. The sequence may contain none, one or several user specific service-primitives if the MAP-CLOSE primitive specifies normal release. If no user specific service-primitive is included, then this will correspond to sending an empty End message in TC. If more than one user specific service-primitive is included, all are to be sent in the same End message. If prearranged end is specified, the sequence cannot contain any user specific service-primitive. The MAP-CLOSE primitive must be sent after all user specific service-primitives have been delivered to the MAP service-provider. Aborting: A MAP service-user can issue a MAP-U-ABORT primitive at any time after the MAP dialogue has been opened or as a response to an attempt to open a MAP dialogue.
2298 The sequencing of services is shown in figure 7.4/1 and is as follows: 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319
2320 The MAP service-provider may issue at any time a MAP-P-ABORT primitive towards a MAP service-user for which a 2321 MAP dialogue exists. 2322 MAP-U-ABORT primitives and MAP-P-ABORT primitives terminate the MAP dialogue.
M A P -O P E N M A P -D E L IM IT E R
U s e r s p e c ific s e r v ic e p r im itiv e
2323
2324
a) Opening
226
227 Release 4 228 229
58
3GPP TS 29.002 V4.17.0 (2006-06)
U s e r s p e c ific s e r v ic e p r im itiv e
M A P -D E L IM IT E R
2325
2326
b) Continuing
M A P -C L O S E
U s e r s p e c ific s e rv ic e p r im itiv e
2327
2328
c) Closing
M A P -U -A B O R T M A P -P -A B O R T
2329
2330 2331
d) Aborting Figure 7.4/1: Sequencing of services
2332 If the reason "resource unavailable (short term problem)" is indicated in the MAP-U-ABORT indication primitive, the 2333 MAP service-user may decide to attempt a new MAP dialogue establishment immediately. 2334 Sequencing of user specific service-primitives is done by the MAP service-user and based on rules applicable for each 2335 MAP service-user instance. 2336 A MAP-NOTICE indication primitive may be received at any time during the active period of a MAP dialogue.
2337 2338
7.5 General rules for mapping of services onto TC
7.5.1 Mapping of common services
2339 Table 7.5/1 gives an overview of the mapping rules for mapping of common services onto TC-services. Table 7.5/2 2340 gives the mapping rules for mapping of TC-services onto common services. 2341 Protocol machine description is given in clauses 14 to 17. 2342
Table 7.5/1: Mapping of common services onto TC services MAP service-primitive MAP-OPEN request (+ any user specific service primitives) + MAP-DELIMITER request MAP-OPEN response (+ any user specific service primitives) + MAP-DELIMITER request (any user specific service primitives) + MAP-DELIMITER request (any user specific service primitives) + MAP-CLOSE request TC service-primitive TC-BEGIN request (+ component handling primitives) TC-CONTINUE request (note) (+ component handling primitives) TC-CONTINUE request (+ component handling primitives) TC-END request (+ component handling primitives)
230
231 Release 4 232 233
59
3GPP TS 29.002 V4.17.0 (2006-06)
MAP-U-ABORT request
NOTE:
TC-U-ABORT request
Or TC-END if the MAP-CLOSE request has been received before the MAP-DELIMITER request.
2343 2344
Table 7.5/2: Mapping of TC services onto common service TC service-primitive TC-BEGIN indication (+ component handling primitives) TC-CONTINUE indication (+ component handling primitives) MAP service-primitive MAP-OPEN indication (+ user specific service primitives) + MAP-DELIMITER indication (note 1) First time: MAP-OPEN confirm (+ user specific service primitives) + MAP-DELIMITER indication (note 1) Subsequent times: (user specific service primitives) + MAP-DELIMITER indication (note 1) MAP-OPEN confirm (note 6) (user specific service primitives) + MAP-CLOSE indication MAP-U-ABORT indication or MAP-P-ABORT indication (note 2) MAP-OPEN confirmation (note 3) MAP-P-ABORT indication (note 4) MAP-OPEN confirmation (note 5)
TC-END indication (+ component handling primitives) TC-U-ABORT indication TC-P-ABORT indication
NOTE 1: It may not be necessary to present this primitive to the user for MAP version 2 applications. NOTE 2: The mapping depends on whether the TC-U-ABORT indication primitive contains a MAP-abort-PDU from the remote MAP service-provider or a MAP-user-abort-PDU from the remote MAP service-user. NOTE 3: Only if the opening sequence is pending and if the "Abort Reason" in the TC-U-ABORT indication is set to "Application Context Not Supported". NOTE 4: If the "Abort Reason" in the TC-P-ABORT indication is set to a value different from "Incorrect Transaction Portion". NOTE 5: Only if the opening sequence is pending and if the "Abort Reason" in the TC-P-ABORT indication is set to "Incorrect Transaction Portion". NOTE 6: Only if opening sequence is pending.
2345
2346
7.5.2 Mapping of user specific services
2347 Table 7.5/3 gives the general mapping rules which apply to mapping of MAP user specific services onto TC services 2348 and table 7.5/4 gives the similar rules for mapping of TC services onto MAP user specific services. Detailed mapping is 2349 given in clauses 14 to 17. 2350
Table 7.5/3: Mapping of MAP user specific services onto TC services
MAP service-primitive MAP-xx request MAP-xx response (note 1) TC-service-primitive TC-INVOKE request TC-RESULT-L request TC-U-ERROR request TC-U-REJECT request TC-INVOKE request (note 2)
2351 2352
Table 7.5/4: Mapping of TC services onto MAP user specific services
TC-service-primitive TC-INVOKE indication TC-RESULT-L indication (note 4) TC-U-ERROR indication TC-INVOKE indication (note 2) MAP service-primitive MAP-xx indication MAP-xx confirm
234
235 Release 4 236 237
60 TC-L-CANCEL indication TC-U-REJECT indication TC-L-REJECT indication TC-R-REJECT indication
3GPP TS 29.002 V4.17.0 (2006-06)
MAP-xx confirm or MAP-NOTICE indication (note 3)
2353 2354 2355 2356 2357 2358 2359
Notes to tables 7.5/3 and 7.5/4: NOTE 1: The mapping is determined by parameters contained in the MAP-xx response primitive. NOTE 2: This applies only to TC class 4 operations where the operation is used to pass a result of another class 2 or class 4 operation. NOTE 3: The detailed mapping rules are given in clause 16. NOTE 4: If RESULT-NL components are present they are mapped onto the same MAP-xx confirm.
2360
7.6 Definition of parameters
2361 Following is an alphabetic list of parameters used in the common MAP-services in clause 7.3: 2362
Application context name Destination address Destination reference Diagnostic information Originating address Originating reference Problem diagnostic Provider reason 7.3.1 7.3.1 7.3.1 7.3.4 7.3.1 7.3.1 7.3.6 7.3.5 Refuse reason Release method Responding address Result Source Specific information User reason 7.3.1 7.3.2 7.3.1 7.3.1 7.3.5 7.3.1/7.3.2/7.3.4 7.3.4
2363 2364 Following is an alphabetic list of parameters contained in this clause: 2365
Absent Subscriber Diagnostic SM Access connection status 7.6.8.9 7.6.9.3 Invoke Id ISDN Bearer Capability IST Alert Timer IST Information Withdrawn IST Support Indicator Kc LCS-Reference Number Linked Id LMSI Location Information Location update type Long Forwarded-to Number Long FTN Supported Lower Layer Compatibility LSA Information LSA Information Withdraw MC Information MC Subscription Data Mobile Not Reachable Reason Modification request for CSI Modification request for SS Information More Messages To Send MS ISDN MSC number MSIsdn-Alert Multicall Bearer Information Multiple Bearer Requested Multiple Bearer Not Supported 7.6.1.1 7.6.3.41 7.6.3.66 7.6.3.68 7.6.3.69 7.6.7.4 7.6.11.22 7.6.1.2 7.6.2.16 7.6.2.30 7.6.9.6 7.6.2.22A 7.6.2.22B 7.6.3.42 7.6.3.56 7.6.3.58 7.6.4.48 7.6.4.47 7.6.3.51 7.6.3.81 7.6.3.82 7.6.8.7 7.6.2.17 7.6.2.11 7.6.2.29 7.6.2.52 7.6.2.53 7.6.2.54
Access signalling information Additional Absent Subscriber Diagnostic SM Additional Location Estimate Additional number Additional signal info Additional SM Delivery Outcome Age Indicator Alert Reason Alert Reason Indicator Alerting Pattern All GPRS Data All Information Sent AN-apdu APN Authentication set list B-subscriber Address B subscriber Number B subscriber subaddress Basic Service Group
7.6.9.5 7.6.8.12 7.6.11.21 7.6.2.46 7.6.9.10 7.6.8.11 7.6.3.72 7.6.8.8 7.6.8.10 7.6.3.44 7.6.3.53 7.6.1.5 7.6.9.1 7.6.2.42 7.6.7.1 7.6.2.36 7.6.2.48 7.6.2.49 7.6.4.40
238
239 Release 4 240 241 Bearer service BSSMAP Service Handover BSSMAP Service Handover List Call Barring Data Call barring feature Call barring information Call Direction Call Forwarding Data Call Info Call reference Call Termination Indicator Called number
61 7.6.4.38 7.6.6.5 7.6.6.5A 7.6.3.83 7.6.4.19 7.6.4.18 7.6.5.8 7.6.3.84 7.6.9.9 7.6.5.1 7.6.3.67 7.6.2.24 7.6.2.25 7.6.3.78 7.6.3.38 7.6.3.52 7.6.3.1 7.6.5.8 7.6.4.49 7.6.5.9 7.6.5.10 7.6.6.10B 7.6.7.7 7.6.7.5 7.6.4.5 7.6.9.2 7.6.3.54 7.6.3.87 7.6.3.26 7.6.3.25 7.6.3.22 7.6.3.24 7.6.3.8 7.6.3.23 7.6.3.37 7.6.2.6 7.6.4.21 7.6.11.3 7.6.11.2 7.6.4.41 7.6.6.9 7.6.3.2 7.6.3.5 7.6.3.3 7.6.3.21 7.6.3.20 7.6.3.79 7.6.3.16 7.6.3.15 7.6.3.80 7.6.3.18 7.6.3.19 7.6.3.74 7.6.3.29 7.6.3.14 7.6.3.17 7.6.3.4 7.6.9.4 7.6.7.9 MWD status
3GPP TS 29.002 V4.17.0 (2006-06) 7.6.8.3 7.6.4.45 7.6.3.50 7.6.2.43 7.6.10.1 7.6.9.8 7.6.4.20 7.6.4.7 7.6.2.34 7.6.5.14 7.6.3.85 7.6.3.9 7.6.3.10 7.6.2.18 7.6.2.26 7.6.2.10 7.6.4.4 7.6.2.47 7.6.2.45 7.6.3.55 7.6.2.44 7.6.5.15 7.6.2.4 7.6.9.7 7.6.1.3 7.6.3.47 7.6.6.10 7.6.6.10A 7.6.6.6 7.6.7.2 7.6.3.11 7.6.3.12 7.6.2.19A 7.6.3.31 7.6.3.86 7.6.2.19 7.6.3.49 7.6.3.13 7.6.7.8 7.6.2.56 7.6.2.27 7.6.2.37 7.6.2.39 7.6.3.75 7.6.2.38 7.6.2.35 7.6.3.57 7.6.8.6 7.6.8.1 7.6.8.16 7.6.8.2 7.6.8.5 7.6.8.17 7.6.8.4 7.6.7.3 7.6.4.1 7.6.4.3 7.6.4.42 7.6.4.43 7.6.4.24
NbrUser Network Access Mode Network node number Network resources Network signal information New password No reply condition timer North American Equal Access preferred Carrier Id Number Portability Status ODB Data ODB General Data ODB HPLMN Specific Data OMC Id Originally dialled number Originating entity number Override Category P-TMSI PDP-Address PDP-Context identifier PDP-Type Pre-paging supported Previous location area Id Protocol Id Provider error QoS-Subscribed Radio Resource Information Radio Resource List RANAP Service Handover Rand Regional Subscription Data Regional Subscription Response Relocation Number List Requested Info Requested Subscription Info Roaming number Roaming Restricted In SGSN Due To Unsupported Feature Roaming Restriction Due To Unsupported Feature Current Security Context Selected RAB ID Service centre address Serving Cell Id SGSN address SGSN CAMEL Subscription Info SGSN number SIWF Number SoLSA Support Indicator SM Delivery Outcome SM-RP-DA SM-RP-MTI SM-RP-OA SM-RP-PRI SM-RP-SMEA SM-RP-UI Sres SS-Code SS-Data SS-Event SS-Event-Data SS-Info
Calling number CAMEL Subscription Info CAMEL Subscription Info Withdraw Cancellation Type Category CCBS Feature CCBS Request State Channel Type Chosen Channel Chosen Radio Resource Information Ciphering mode Cksn CLI Restriction CM service type Complete Data List Included CS Allocation Retention priority CUG feature CUG index CUG info CUG interlock CUG Outgoing Access indicator CUG subscription CUG Subscription Flag Current location area Id Current password Deferred MT-LR Data Deferred MT-LR Response Indicator eMLPP Information Encryption Information Equipment status Extensible Basic Service Group Extensible Bearer service Extensible Call barring feature Extensible Call barring information Extensible Call barring information for CSE Extensible Forwarding feature Extensible Forwarding info Extensible Forwarding information for CSE Extensible Forwarding Options Extensible No reply condition timer Extensible QoS-Subscribed Extensible SS-Data Extensible SS-Info Extensible SS-Status Extensible Teleservice External Signal Information Failure Cause
242
243 Release 4 244 245 Forwarded-to number Forwarded-to subaddress Forwarding feature Forwarding information Forwarding Options GGSN address
62 7.6.2.22 7.6.2.23 7.6.4.16 7.6.4.15 7.6.4.6 7.6.2.40 7.6.2.41 7.6.3.34 7.6.3.73 7.6.8.14 7.6.3.46 7.6.3.45 7.6.8.15 7.6.2.33 7.6.3.6 7.6.4.22 7.6.2.21 7.6.3.43 7.6.2.15 7.6.2.13 7.6.6.7 7.6.2.3 7.6.2.1 7.6.6.8 7.6.3.27 7.6.3.28
3GPP TS 29.002 V4.17.0 (2006-06) 7.6.4.2 7.6.2.5 7.6.3.30 7.6.3.7 7.6.3.70 7.6.3.71 7.6.3.36 7.6.3.36A 7.6.11.20 7.6.11.17 7.6.3.33 7.6.3.32 7.6.2.8 7.6.2.7 7.6.2.8A 7.6.2.12 7.6.4.39 7.6.2.2 7.6.10.2 7.6.10.3 7.6.1.4 7.6.4.36 7.6.4.37 7.6.5.12 7.6.5.13 7.6.3.40 7.6.3.39 7.6.3.35 7.6.2.14 7.6.3.48 7.6.2.28
GGSN number GMSC CAMEL Subscription Info GPRS enhancements support indicator GPRS Node Indicator GPRS Subscription Data GPRS Subscription Data Withdraw GPRS Support Indicator Group Id GSM bearer capability Guidance information Handover number High Layer Compatibility HLR Id HLR number HO-Number Not Required IMEI IMSI Integrity Protection Information Inter CUG options Intra CUG restrictions
SS-Status Stored location area Id Subscriber State Subscriber Status Super-Charger Supported in HLR Super-Charger Supported in Serving Network Entity Supported CAMEL Phases in VLR Supported CAMEL Phases in SGSN Supported GAD Shapes Supported LCS Capability Sets Suppress T-CSI Suppression of Announcement Target cell Id Target location area Id Target RNC Id Target MSC number Teleservice TMSI Trace reference Trace type User error USSD Data Coding Scheme USSD String UU Data UUS CF Interaction VBS Data VGCS Data VLR CAMEL Subscription Info VLR number VPLMN address allowed Zone Code
2366
2367
7.6.1 Common parameters
2368 The following set of parameters is used in several MAP service-primitives.
2369 7.6.1.1
Invoke Id
2370 This parameter identifies corresponding service primitives. The parameter is supplied by the MAP service-user and 2371 must be unique over each service-user/service-provider interface.
2372 7.6.1.2
Linked Id
2373 This parameter is used for linked services and it takes the value of the invoke Id of the service linked to.
2374 7.6.1.3
-
Provider error
2375 This parameter is used to indicate a protocol related type of error: 2376 2377 2378 2379
duplicated invoke Id; not supported service; mistyped parameter; resource limitation;
246
2380 2381 2382 2383 2384
247 Release 4 248 249
63
3GPP TS 29.002 V4.17.0 (2006-06)
initiating release, i.e. the peer has already initiated release of the dialogue and the service has to be released; unexpected response from the peer; service completion failure; no response from the peer; invalid response received.
2385 7.6.1.4
NOTE:
User error
2386 This parameter can take values as follows: 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414
The values are grouped in order to improve readability; the grouping has no other significance.
a) Generic error: system failure, i.e. a task cannot be performed because of a problem in another entity. The type of entity or network resource may be indicated by use of the network resource parameter; data missing, i.e. an optional parameter required by the context is missing; unexpected data value, i.e. the data type is formally correct but its value or presence is unexpected in the current context; resource limitation; initiating release, i.e. the receiving entity has started the release procedure; facility not supported, i.e. the requested facility is not supported by the PLMN with detailed reasons as follows: Shape of location estimate not supported;
incompatible terminal, i.e. the requested facility is not supported by the terminal.
b) Identification or numbering problem: unknown subscriber, i.e. no such subscription exists; number changed, i.e. the subscription does not exist for that number any more; unknown MSC; unidentified subscriber, i.e. if the subscriber is not contained in the database and it has not or cannot be established whether or not a subscription exists; unallocated roaming number; unknown equipment; unknown location area.
c) Subscription problem: roaming not allowed, i.e. a location updating attempt is made in an area not covered by the subscription; illegal subscriber, i.e. illegality of the access has been established by use of authentication procedure; bearer service not provisioned; teleservice not provisioned; illegal equipment, i.e. the IMEI check procedure has shown that the IMEI is blacklisted or not whitelisted.
250
2415
251 Release 4 252 253
64
3GPP TS 29.002 V4.17.0 (2006-06)
d) Handover problem: -no handover number available, i.e. the VLR cannot allocate a number for handover or cannot allocate the required amount of numbers for relocation; -subsequent handover failure, i.e. handover to a third MSC failed for some reason; -target cell outside group call area. e) Operation and maintenance problem: tracing buffer full, i.e. tracing cannot be performed because the tracing capacity is exceeded.
2416
2417
2418 2419
2420 2421 2422 2423 2424
f) Call set-up problem: no roaming number available, i.e. a roaming number cannot be allocated because all available numbers are in use; absent subscriber, i.e. the subscriber has activated the detach service or the system detects the absence condition. This error may be qualified to indicate whether the subscriber was IMSI detached, in a restricted area or did not respond to paging; busy subscriber. This error may be qualified to indicate that the subscriber was busy due to CCBS and that CCBS is possible; no subscriber reply; forwarding violation, i.e. the call has already been forwarded the maximum number of times that is allowed; CUG reject, i.e. the call does not pass a CUG check; additional information may also be given in order to indicate rejection due to e.g. incoming call barred or non-CUG membership; call barred. Optionally, additional information may be included for indicating either that the call meets a barring condition set by the subscriber or that the call is barred for operator reasons. In the case of barring of Mobile Terminating Short Message, the additional information may indicate a barring condition due to "Unauthorised Message Originator"; optimal routeing not allowed, i.e. the entity which sends the error does not support optimal routeing, or the HLR will not accept an optimal routeing interrogation from the GMSC, or the call cannot be optimally routed because it would contravene optimal routeing constraints; forwarding failed, i.e. the GMSC interrogated the HLR for forwarding information but the HLR returned an error.
2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451
g) Supplementary services problem: call barred; illegal SS operation; SS error status; SS not available; SS subscription violation; SS incompatibility; negative password check; password registration failure; Number of Password Attempts; USSD Busy; Unknown Alphabet;
254
2452 2453
255 Release 4 256 257
65
3GPP TS 29.002 V4.17.0 (2006-06)
short term denial; long term denial.
2454 For definition of these errors see 3GPP TS 24.080 [38]. 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477
h) Short message problem: SM delivery failure with detailed reason as follows: memory capacity exceeded; MS protocol error; MS not equipped; unknown service centre (SC); SC congestion; invalid SME address; subscriber is not an SC subscriber; and possibly detailed diagnostic information, coded as specified in 3GPP TS 23.140, under SMSSUBMIT-REPORT and SMS-DELIVERY-REPORT. If the SM entity that returns the SM Delivery Failure error includes detailed diagnostic information, it shall be forwarded in the MAP_MO_FORWARD_SHORT_MESSAGE and in the MAP_MT_FORWARD_SHORT_MESSAGE response.
message waiting list full, i.e. no further SC address can be added to the message waiting list. Subscriber busy for MT SMS, i.e. the mobile terminated short message transfer cannot be completed because: another mobile terminated short message transfer is going on and the delivery node does not support message buffering; or another mobile terminated short message transfer is going on and it is not possible to buffer the message for later delivery; or the message was buffered but it is not possible to deliver the message before the expiry of the buffering time defined in 3GPP TS 23.140;
Absent Subscriber SM, i.e. the mobile terminated short message transfer cannot be completed because the network cannot contact the subscriber. Diagnostic information regarding the reason for the subscriber's absence may be included with this error.
2478
i) Location services problem: -Unauthorised Requesting Network -Unauthorised LCS Client with detailed reasons as follows: Unauthorised Privacy Class Unauthorised Call/Session Unrelated External Client Unauthorised Call/Session Related External Client
2479 2480 2481 2482 2483 2484 2485 2486 2487
-Privacy override not applicable -Position method failure with detailed reasons as follows: Congestion Insufficient resources
258
2488 2489 2490 2491 2492 2493
2494 2495 2496 2497 2498 2499
259 Release 4 260 261
66
3GPP TS 29.002 V4.17.0 (2006-06)
Insufficient Measurement Data Inconsistent Measurement Data Location procedure not completed QoS not attainable Position Method Not Available in Network Position Method Not Available in Location Area Unknown or unreachable LCS Client.
j) Problem detected by an application using secure transport: Secure transport error. This error indicates that the application using secure transport returned an error. The parameter of the error indicates: The protected payload, which carries the result of applying the protection function specified in 3GPP TS 33.200 to the encoding of the parameter of the original error.
2500 7.6.1.5
All Information Sent
2501 This parameter indicates to the receiving entity when the sending entity has sent all necessary information.
2502 2503 7.6.2.1
7.6.2 Numbering and identification parameters
IMSI
2504 This parameter is the International Mobile Subscriber Identity defined in 3GPP TS 23.003 [17].
2505 7.6.2.2
TMSI
2506 This parameter is the Temporary Mobile Subscriber Identity defined in 3GPP TS 23.003 [17].
2507 7.6.2.3
IMEI
2508 This parameter is the International Mobile Equipment Identity defined in 3GPP TS 23.003 [17].
2509 7.6.2.4
Previous location area Id
2510 This parameter refers to the identity of the location area from which the subscriber has roamed.
2511 7.6.2.5
Stored location area Id
2512 This parameter refers to the location area where the subscriber is assumed to be located.
2513 7.6.2.6
Current location area Id
2514 This parameter is used to indicate the location area in which the subscriber is currently located.
2515 7.6.2.7
Target location area Id
2516 This parameter refers to the location area into which the subscriber intends to roam.
2517 7.6.2.8
Target cell Id
2518 This parameter refers to the identity of the cell to which a call has to be handed over.
262
2519 7.6.2.8A
263 Release 4 264 265
67
3GPP TS 29.002 V4.17.0 (2006-06)
Target RNC Id
2520 This parameter refers to the identity of the RNC to which a call has to be relocated.
2521 7.6.2.9 2522 7.6.2.10
Void Originating entity number
2523 This parameter refers to an application layer identification of a system component in terms of its associated ISDN 2524 number.
2525 7.6.2.11
MSC number
2526 This parameter refers to the ISDN number of an MSC.
2527 7.6.2.12
Target MSC number
2528 This parameter refers to the ISDN number of an MSC to which a call has to be handed over.
2529 7.6.2.13
HLR number
2530 This parameter refers to the ISDN number of an HLR.
2531 7.6.2.14
VLR number
2532 This parameter refers to the ISDN number of a VLR.
2533 7.6.2.15
HLR Id
2534 This parameter refers to the identity of an HLR derived from the IMSI defined in CCITT Recommendation E.212.
2535 7.6.2.16
LMSI
2536 This parameter refers to a local identity allocated by the VLR to a given subscriber for internal management of data in 2537 the VLR. LMSI shall not be sent to the SGSN.
2538 7.6.2.17
MS ISDN
2539 This parameter refers to one of the ISDN numbers assigned to a mobile subscriber in accordance with CCITT 2540 Recommendation E.213.
2541 7.6.2.18
OMC Id
2542 This parameter refers to the identity of an Operation and Maintenance Centre.
2543 7.6.2.19
Roaming number
2544 This parameter refers to the roaming number as defined in CCITT Recommendation E.213.
2545 7.6.2.19A
Relocation Number List
2546 This parameter refers to the number(s) used for routing one call or several calls between MSCs during relocation.
2547 7.6.2.20 2548 7.6.2.21
Void Handover number
266
2549 This parameter refers to the number used for routing a call between MSCs during handover.
267 Release 4 268 269
68
3GPP TS 29.002 V4.17.0 (2006-06)
2550 7.6.2.22
Forwarded-to number
2551 This parameter refers to the address to which a call is to be forwarded. A subaddress may be appended. For subscribers 2552 having an originating CAMEL Phase 2 or higher subscription, this address need not be in E.164 international format.
2553 7.6.2.22A
Long forwarded-to number
2554 This parameter refers to the address to which a call is to be forwarded. A subaddress may be appended. For subscribers 2555 having an originating CAMEL Phase 2 or higher subscription this address need not be in international format.
2556 7.6.2.22B
Long FTN Supported
2557 This parameter indicates that the sending entity supports Long Forwarded-to Numbers.
2558 7.6.2.23
Forwarded-to subaddress
2559 This parameter refers to the sub-address attached to the address to which a call is to be forwarded.
2560 7.6.2.24
Called number
2561 This parameter refers to a called party number as defined in CCITT Recommendation Q.767.
2562 7.6.2.25
Calling number
2563 This parameter refers to a calling party number as defined in CCITT Recommendation Q.767.
2564 7.6.2.26
Originally dialled number
2565 This parameter refers to the number dialled by the calling party in order to reach a mobile subscriber.
2566 7.6.2.27
Service centre address
2567 This parameter represents the address of a Short Message Service Centre.
2568 7.6.2.28
Zone Code
2569 This parameter is used to define location areas into which the subscriber is allowed or not allowed to roam (regional 2570 subscription). With a complete list of Zone Codes the VLR or the SGSN is able to determine for all its location areas 2571 whether roaming is allowed or not.
2572 7.6.2.29
MSIsdn-Alert
2573 This parameter refers to the MSISDN stored in a Message Waiting Data File in the HLR. It is used to alert the Service 2574 Centre when the MS is again attainable.
2575 7.6.2.30
Location Information
2576 This parameter indicates the location of the served subscriber as defined in 3GPP TS 23.018 [97].
2577 7.6.2.31
GMSC Address
2578 This parameter refers to the E.164 address of a GMSC.
2579 7.6.2.32
VMSC Address
2580 This parameter refers to the E.164 address of a VMSC.
270
2581 7.6.2.33
271 Release 4 272 273
69
3GPP TS 29.002 V4.17.0 (2006-06)
Group Id
2582 This parameter is used to describe groups a subscriber can be a member of. A subscriber can partake in all group calls 2583 (VBS/VGCS) where he subscribed to the respective groups.
2584 7.6.2.34
North American Equal Access preferred Carrier Id
2585 This parameter refers to the carrier identity preferred by the subscriber for calls requiring routing via an inter-exchange 2586 carrier. This identity is used at: 2587 2588 2589
outgoing calls: when the subscriber does not specify at call set-up a carrier identity; forwarded calls: when a call is forwarded by the subscriber; incoming calls: applicable to the roaming leg of the call.
2590 7.6.2.35
SIWFS Number
2591 This parameter refers to the number used for routing a call between the MSC and the SIWFS (used by ISUP).
2592 7.6.2.36
B-subscriber address
2593 This parameter refers to the address used by the SIWFS to route the outgoing call from the SIWFS to either the B2594 subscriber in case of the non-loop method or back to the VMSC in case of the loop method.
2595 7.6.2.37
Serving cell Id
2596 This parameter indicates the cell currently being used by the served subscriber.
2597 7.6.2.38
SGSN number
2598 This parameter refers to the ISDN number of a SGSN.
2599 7.6.2.39
SGSN address
2600 This parameter refers to the IP-address of a SGSN. This parameter is defined in 3GPP TS 23.003 [17].
2601 7.6.2.40
GGSN address
2602 This parameter refers to the IP-address of a GGSN. This parameter is defined in 3GPP TS 23.003 [17].
2603 7.6.2.41
GGSN number
2604 This parameter refers to the ISDN number of a GGSN or the ISDN number of the protocol-converter if a 2605 protocol-converting GSN is used between the GGSN and the HLR.
2606 7.6.2.42
APN
2607 This parameter refers to the DNS name of a GGSN. This parameter is defined in 3GPP TS 23.060 [104].
2608 7.6.2.43
Network Node number
2609 This parameter refers either to the ISDN number of SGSN or to the ISDN number of MSC.
2610 7.6.2.44
PDP-Type
2611 This parameter indicates which type of protocol is used by the MS as defined in 3GPP TS 23.060 [104].
274
2612 7.6.2.45
275 Release 4 276 277
70
3GPP TS 29.002 V4.17.0 (2006-06)
PDP-Address
2613 This parameter indicates the address of the data protocol as defined in 3GPP TS 23.060 [104].
2614 7.6.2.46
Additional number
2615 This parameter can refer either to the SGSN number or to the MSC number.
2616 7.6.2.47
P-TMSI
2617 This parameter is the Packet Temporary Mobile Subscriber Identity defined in 3GPP TS 23.003 [17].
2618 7.6.2.48
B-subscriber number
2619 This parameter refers to the number of the destination B dialled by the A user. This may include a subaddress.
2620 7.6.2.49
B-subscriber subaddress
2621 This parameter refers to the sub-address attached to the destination B dialled by the A user.
2622 7.6.2.50
LMU Number
2623 This parameter refers to a local number assigned to an LMU by an SMLC.
2624 7.6.2.51
MLC Number
2625 This parameter refers to the ISDN (E.164) number of an MLC.
2626 7.6.2.52
Multicall Bearer Information
2627 This parameter refers to the number of simultaneous bearers supported per user by the serving network.
2628 7.6.2.53
Multiple Bearer Requested
2629 This parameter indicates whether multiple bearers are requested for a relocation.
2630 7.6.2.54
Multiple Bearer Not Supported
2631 This parameter indicates whether multiple bearers are supported.
2632 7.6.2.55
PDP-Charging Characteristics
2633 This parameter indicates the charging characteristics associated with a specific PDP context as defined in 3GPP 2634 TS 32.015.
2635 7.6.2.56
Selected RAB ID
2636 The selected radio access bearer to be kept at subsequent inter-MSC handover from UMTS to GSM.
2637 7.6.2.57
RAB ID
2638 This parameter indicates the radio access bearer identifier as defined in 3GPP TS 25.413. This parameter is used to 2639 relate the radio resources with the radio access bearers.
2640 2641 7.6.3.1
7.6.3 Subscriber management parameters
Category
278
2642 This parameter refers to the calling party category as defined in CCITT Recommendation Q.767.
279 Release 4 280 281
71
3GPP TS 29.002 V4.17.0 (2006-06)
2643 7.6.3.2
Equipment status
2644 This parameter refers to the status of the mobile equipment as defined in 3GPP TS 22.016 [7].
2645 7.6.3.3
Extensible Bearer service
2646 This parameter may refer to a single bearer service, a set of bearer services or to all bearer services as defined in 3GPP 2647 TS 22.002 [3]. This parameter is used only for subscriber profile management. Extensible Bearer service values include 2648 all values defined for a Bearer service parameter (7.6.4.38).
2649 7.6.3.4
Extensible Teleservice
2650 This parameter may refer to a single teleservice, a set of teleservices or to all teleservices as defined in 3GPP TS 22.003 2651 [4]. This parameter is used only for subscriber profile management. Extensible Teleservice values include all values 2652 defined for a Teleservice parameter (7.6.4.39).
2653 7.6.3.5
2654 2655 2656 2657
Extensible Basic Service Group
This parameter refers to the Basic Service Group either as an extensible bearer service (see clause 7.6.3.3) or an extensible teleservice (see clause 7.6.3.4). This parameter is used only for subscriber profile management. The null value (i.e. neither extensible bearer service nor extensible teleservice) is used to denote the group containing all extensible bearer services and all extensible teleservices.
2658 7.6.3.6
GSM bearer capability
2659 This parameter refers to the GSM bearer capability information element defined in 3GPP TS 24.008 [35].
2660 7.6.3.7
-
Subscriber Status
2661 This parameter refers to the barring status of the subscriber: 2662 2663
service granted; Operator Determined Barring.
2664 7.6.3.8
CUG Outgoing Access indicator
2665 This parameter represents the Outgoing Access as defined in ETS 300 136.
2666 7.6.3.9
Operator Determined Barring General Data
2667 This parameter refers to the set of subscriber features that the network operator or the service provider can regulate. 2668 This set only includes those limitations that can be 2669 2670 2671 2672 2673
a) controlled in the VLR, b) controlled in the SGSN, c) controlled in the SGSN applied for short message transfer only, d) interrogated or modified by the gsmSCF:
ODB category
Controlled in the VLR Controlled in the SGSN
Controlled in the Interrogatable and SGSN applied for modifyable by the short message transfer gsmSCF only
282
283 Release 4 284 285
72
3GPP TS 29.002 V4.17.0 (2006-06)
All outgoing calls barred International outgoing calls barred International outgoing calls except those to the home PLMN country barred Interzonal outgoing calls barred Interzonal outgoing calls except those to the home PLMN country barred Interzonal outgoing calls AND international outgoing calls except those directed to the home PLMN country barred Premium rate (information) outgoing calls barred Premium rate (entertainment) outgoing calls barred Supplementary service access barred Invocation of call transfer barred Invocation of chargeable call transfer barred Invocation of internationally chargeable call transfer barred Invocation of interzonally chargeable call transfer barred Invocation of call transfer where both legs are chargeable barred Invocation of call transfer if there is already an ongoing transferred call for the served subscriber in the serving MSC/VLR
X X X
X X X
X X X
X X
X X
X X
X X X
X X X
286
287 Release 4 288 289
73
3GPP TS 29.002 V4.17.0 (2006-06)
barred
All packet Oriented Services barred Roamer Access to HPLMN-AP barred Roamer Access to VPLMN-AP barred Outgoing calls when roaming outside the home PLMN country All incoming calls Incoming calls when roaming outside the home PLMN country Incoming calls when roaming outside the zone of the home PLMN country Roaming outside the home PLMN Roaming outside the home PLMN country Registration of any call forwarded-to number Registration of any international call forwarded-to number Registration of any international call forwarded-to number except to a number within the HPLMN country Registration of any inter-zone call forwarded-to number Registration of any inter-zone call forwarded-to number except to a number within the HPLMN country
2674 2675 2676
X X X
X X X X
X X
X X X X
2677 7.6.3.10
ODB HPLMN Specific Data
290
2678 This parameter refers to the set of subscriber features that the network operator or the service provider can regulate only 2679 when the subscriber is registered in the HPLMN. This set only includes those limitations that can be controlled in the 2680 VLR or in the SGSN: 2681 2682 2683 2684
291 Release 4 292 293
74
3GPP TS 29.002 V4.17.0 (2006-06)
Operator Determined Barring Type 1; Operator Determined Barring Type 2; Operator Determined Barring Type 3; Operator Determined Barring Type 4.
2685 7.6.3.11
Regional Subscription Data
2686 This parameter defines the regional subscription area in which the subscriber is allowed to roam. It consists of a list of 2687 Zone Codes (see clause 7.6.2.28).
2688 7.6.3.12
Regional Subscription Response
2689 This parameter indicates either that the regional subscription data cannot be handled or that the current MSC or SGSN 2690 area is entirely restricted because of regional subscription.
2691 7.6.3.13
Roaming Restriction Due To Unsupported Feature
2692 This parameter defines that a subscriber is not allowed to roam in the current MSC area. It may be used by the HLR if a 2693 feature or service is indicated as unsupported by the VLR.
2694 7.6.3.14
-
Extensible SS-Info
2695 This parameter refers to all the information related to a supplementary service and is a choice between: 2696 2697 2698 2699
extensible forwarding information (see clause 7.6.3.15); extensible call barring information (see clause 7.6.3.20); CUG info extensible SS-Data (see clause 7.6.3.22); (see clause 7.6.3.29).
2700 7.6.3.15
-
Extensible forwarding information
(see clause 7.6.4.1); (see clause 7.6.3.16).
2701 This parameter represents the information related to each call forwarding service: 2702 2703 2704
the SS-Code of the relevant call forwarding service if required, a list of extensible forwarding feature parameters The list may contain one item per Basic Service Group.
2705 7.6.3.16
Extensible forwarding feature
2706 This parameter applies to each combination of call forwarding service and Basic Service Group and contains the 2707 following information, as required: 2708 2709 2710 2711 2712
extensible Basic Service Group extensible SS-Status forwarded-to number forwarded-to subaddress extensible forwarding options
(see clause 7.6.3.5); (see clause 7.6.3.17); (see clause 7.6.2.22); (see clause 7.6.2.23); (see clause 7.6.3.18);
294
2713 2714 2715 2716 2717 2718 2719
295 Release 4 296 297
75
3GPP TS 29.002 V4.17.0 (2006-06)
extensible no reply condition timer long forwarded-to number
(see clause 7.6.4.19); (see clause 7.6.2.22A).
If a number is required to define the forwarded-to destination then: If the VLR supports Long Forwarded-to Numbers then the long forwarded-to number shall be present and the forwarded-to number shall be absent; If the VLR does not support Long Forwarded-to Numbers then the forwarded-to number shall be present and the long forwarded-to number shall be absent.
2720 7.6.3.17
Extensible SS-Status
2721 This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011 [22].
2722 7.6.3.18
Extensible Forwarding Options
2723 This parameter refers to a set of forwarding options attached to a supplementary service. It contains the following 2724 information: 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734
notification to forwarding party parameter); redirection notification to the forwarded-to party parameter); notification to calling party parameter); redirecting presentation parameter); forwarding reason parameter).
(see 3GPP TS 22.082 [10] for the meaning of this (see 3GPP TS 22.082 [10] for the meaning of this (see 3GPP TS 22.082 [10] for the meaning of this (see 3GPP TS 22.082 [10] for the meaning of this (see 3GPP TS 22.082 [10] for the meaning of this
2735 7.6.3.19
Extensible No reply condition timer
2736 This parameter refers to the extensible no reply condition timer for call forwarding on no reply.
2737 7.6.3.20
SS-Code
Extensible Call barring information
2738 This parameter contains for each call barring service: 2739 2740 2741
(see clause 7.6.4.1); (see clause 7.6.3.21).
a list of extensible call barring feature parameters The list may contain one item per Basic Service Group.
2742 7.6.3.21
Extensible Call barring feature
2743 This parameter gives the status of call barring services as applicable to each Basic Service Group. The parameter 2744 contains the following information: 2745 2746
Extensible Basic Service Group provisioned SS-Status
(see clause 7.6.3.5); (see clause 7.6.3.17).
2747 7.6.3.22
CUG info
2748 This parameter refers to the overall information required for operation for each CUG:
298
2749 2750
299 Release 4 300 301
76
3GPP TS 29.002 V4.17.0 (2006-06)
CUG subscriptionList; CUG featureList.
2751 7.6.3.23
CUG subscription
2752 This parameter refers to the set of basic information for each CUG defined in that subscription. The following 2753 information is stored: 2754 2755 2756 2757
CUG index; CUG interlock; Intra CUG restrictions; Basic Service Group List.
2758 7.6.3.24
CUG interlock
2759 This parameter represents the CUG interlock code defined in ETS 300 138.
2760 7.6.3.25
CUG index
2761 This parameter represents the CUG index defined in ETS 300 138.
2762 7.6.3.26
CUG feature
2763 This parameter contains two parameters that are associated with the Basic Service Group. If the Basic Service Group 2764 Code is not present the feature applies to all Basic Services. The following parameters are included: 2765 2766 2767 2768 2769 2770
Preferential CUG indicator: indicates which CUG index is to be used at outgoing call set-up using the associated Basic Service Group;
Inter CUG Option: describes whether it for the associated Basic Service Group is allowed to make calls outside the CUG and whether incoming calls are allowed;
Basic Service Group.
2771 See 3GPP TS 22.085 [13] for meaning of this parameter.
2772 7.6.3.27
Inter CUG options
2773 This parameter indicates the subscribers' ability to make and receive calls outside a specific closed user group. It takes 2774 any of the following values: 2775 2776 2777 2778
CUG only facility (only calls within CUG are allowed); CUG with outgoing access (calls outside CUG allowed); CUG with incoming access (calls from outside CUG into CUG allowed); CUG with both incoming and outgoing access (all calls allowed).
2779 7.6.3.28
Intra CUG restrictions
2780 This parameter describes whether or not the subscriber is allowed to originate calls to or to receive calls from within the 2781 CUG. It can take any of the following values: 2782
no CUG restrictions;
302
2783 2784
303 Release 4 304 305
77
3GPP TS 29.002 V4.17.0 (2006-06)
CUG incoming calls barred; CUG outgoing calls barred.
2785 7.6.3.29
SS-Code
Extensible SS-Data
(see clause 7.6.4.1); (see clause 7.6.3.17); (see clause 7.6.3.30); (see clause 7.6.3.31); (see clause 7.6.3.5).
2786 This parameter refers to the necessary set of information required in order to characterise one supplementary service: 2787 2788 2789 2790 2791
Extensible SS-Status (if applicable) Extensible Override subscription option (if applicable) Extensible CLI Restriction (if applicable) Extensible Basic Service Group Code
2792 7.6.3.30
Subscriber State
2793 This parameter indicates the state of the MS as defined in 3GPP TS 23.018 [97].
2794 7.6.3.31
Requested Info
2795 This parameter indicates the subscriber information being requested as defined in 3GPP TS 23.018 [97].
2796 7.6.3.32
Suppression of Announcement
2797 This parameter indicates if the announcement or tones shall be suppressed as defined in 3GPP TS 23.078.
2798 7.6.3.33
Suppress T-CSI
2799 This parameter is used to suppress the invocation of terminating CAMEL services.
2800 7.6.3.34
GMSC CAMEL Subscription Info
2801 This parameter contains CAMEL subscription information, i.e. O-CSI and/or D-CSI and/or T-CSI, which indicates to 2802 the GMSC that originating and/or terminating CAMEL services shall be invoked for the incoming call.
2803 7.6.3.35
VLR CAMEL Subscription Info
2804 This parameter identifies the subscriber as having CAMEL services that are invoked in the MSC or VLR.
2805 7.6.3.36
Supported CAMEL Phases in the VLR
2806 This parameter indicates which phases of CAMEL are supported in the VLR.
2807 7.6.3.36A
Supported CAMEL Phases in the SGSN
2808 This parameter indicates which phases of CAMEL are supported in the SGSN.
2809 7.6.3.37
CUG Subscription Flag
2810 This parameter indicates a that a subscriber with a T-CSI also has a CUG subscription. It is defined in 3GPP TS 23.078.
2811 7.6.3.38
CAMEL Subscription Info Withdraw
2812 This parameter indicates that CAMEL Subscription Info shall be deleted from the VLR or SGSN.
306
2813 7.6.3.39
307 Release 4 308 309
78
3GPP TS 29.002 V4.17.0 (2006-06)
Voice Group Call Service (VGCS) Data
2814 This parameter refers to one or more groups a subscriber may be a member of for voice group calls.
2815 7.6.3.40
Voice Broadcast Service (VBS) Data
2816 This parameter refers to one or more groups a subscriber may be a member of for the voice broadcast service. Per group 2817 it is further indicated whether the subscriber is only allowed to listen to respective group calls or whether he is in 2818 addition entitled to initiate respective voice broadcast calls.
2819 7.6.3.41
ISDN bearer capability
2820 This parameter refers to the ISDN bearer capability information element defined in 3GPP TS 29.007 [56].
2821 7.6.3.42
Lower layer Compatibility
2822 This parameter refers to the lower layer compatibility information element defined in 3GPP TS 24.008 [35].
2823 7.6.3.43
High Layer Compatibility
2824 This parameter refers to the high layer compatibility information element defined in 3GPP TS 24.008 [35].
2825 7.6.3.44
Alerting Pattern
2826 This parameter is an indication that can be used by the MS to alert the user in a specific manner in case of mobile 2827 terminating traffic (switched call or USSD). That indication can be an alerting level or an alerting category.
2828 7.6.3.45
GPRS Subscription Data Withdraw
2829 This parameter indicates that GPRS Subscription Data shall be deleted from the SGSN.
2830 7.6.3.46
GPRS Subscription Data
2831 This parameter refers to the list of PDP-Contexts that subscriber has subscribed to.
2832 7.6.3.47
QoS-Subscribed
2833 This parameter indicates the quality of service subscribed for a certain service. It is defined in 3GPP TS 23.060 [104].
2834 7.6.3.48
VPLMN address allowed
2835 This parameter specifies whether the MS is allowed to use a dynamic address allocated in the VPLMN. It is defined in 2836 3GPP TS 23.060 [104].
2837 7.6.3.49
Roaming Restricted In SGSN Due To Unsupported Feature
2838 This parameter defines that a subscriber is not allowed to roam in the current SGSN area. It may be used by the HLR if 2839 a feature or service is indicated as unsupported by the SGSN.
2840 7.6.3.50
Network Access Mode
2841 This parameter is defined in 3GPP TS 23.108.
2842 7.6.3.51
Mobile Not Reachable Reason
2843 This parameter stores the reason for the MS being absent when an attempt to deliver a short message to an MS fails at 2844 the MSC, SGSN or both. It is defined in 3GPP TS 23.140.
310
2845 7.6.3.52
311 Release 4 312 313
79
3GPP TS 29.002 V4.17.0 (2006-06)
Cancellation Type
2846 This parameter indicates the reason of location cancellation. It is defined in 3GPP TS 23.060 [104].
2847 7.6.3.53
All GPRS Data
2848 This parameter indicates to the SGSN that all GPRS Subscription Data shall be deleted for the subscriber.
2849 7.6.3.54
Complete Data List Included
2850 This parameter indicates to the SGSN that the complete GPRS Subscription Data stored for the Subscriber shall be 2851 replaced with the GPRS Subscription Data received.
2852 7.6.3.55
PDP Context Identifier
2853 This parameter is used to identify a PDP context for the subscriber.
2854 7.6.3.56
LSA Information
2855 This parameter refers to one or more localised service areas a subscriber may be a member of, together with the priority, 2856 the preferential access indicator, the active mode support indicator and active mode indication of each localised service 2857 area. The access right outside these localised service areas is also indicated.
2858 7.6.3.57
SoLSA support indicator
2859 This parameter indicates that the VLR or the SGSN supports SoLSA subscription.
2860 7.6.3.58
LSA Information Withdraw
2861 This parameter indicates that LSA information shall be deleted from the VLR or the SGSN.
2862 7.6.3.59
LMU Indicator
2863 This parameter indicates the presence of an LMU.
2864 7.6.3.60
-
LCS Information
2865 This parameter defines the LCS related information for an MS subscriber and contains the following components: 2866 2867 2868
GMLC List LCS Privacy Exception List MO-LR List
(see clause 7.6.3.61). (see clause 7.6.3.62). (see clause 7.6.3.65A).
2869 7.6.3.61
GMLC List
2870 This parameter contains the addresses of all GMLCs that are permitted to issue a call/session unrelated or call/session 2871 related MT-LR location request for this MS. Usage of this parameter is defined in 3GPP TS 23.271.
2872 7.6.3.62
LCS Privacy Exception List
2873 This parameter defines the classes of LCS Client that are allowed to locate any target MS. For each class, the following 2874 information is provided: 2875 2876
SS-Code a list of LCS privacy exception parameters
(see clause 7.6.4.1); (see clause 7.6.3.63).
314
2877 7.6.3.63
315 Release 4 316 317
80
3GPP TS 29.002 V4.17.0 (2006-06)
LCS Privacy Exception Parameters
2878 This parameter gives the status of each LCS privacy exception class and any additional parameters relevant to this class. 2879 The parameter contains the following information: 2880 2881 2882 2883
provisioned SS-Status privacy notification to MS user external client List internal client List
(see clause 7.6.3.17); (see clause 7.6.3.65B); (see clause 7.6.3.64); (see clause 7.6.3.65).
2884 7.6.3.64
2885 2886 2887 2888 2889 2890
External Client List
This parameter is only applicable to the call/session unrelated privacy class and call/session related privacy class, and gives the identities of the external clients that are allowed to locate a target MS for a MT-LR. Each identity is an international (e.g.E.164) address. For each identified external client, GMLC restrictions may be defined. It may also be indicated if the MS shall be notified of a non-restricted MT-LR from each identified LCS client and, if so, whether notification only or notification with privacy verification shall apply. Usage of this parameter is defined in 3GPP TS 23.271.
2891 7.6.3.65
Internal Client List
2892 This parameter is only applicable to the PLMN operator privacy class and gives the identities of the internal PLMN 2893 operator clients that are allowed to locate a target MS for an NI-LR or MT-LR. Usage of this parameter is defined in 2894 3GPP TS 23.271.
2895 7.6.3.65A
MO-LR List
2896 This parameter defines the classes of MO-LR for which a subscription exists for a particular MS. For each class, the 2897 following information is provided: 2898
SS-Code
(see clause 7.6.4.1).
2899 7.6.3.65B
2900 2901 2902 2903
Privacy Notification to MS User
This parameter is applicable to the call/session unrelated privacy class and call/session related privacy class. For each privacy class it indicates whether the MS user shall be notified for athat class MT-LR from any value added LCS client when the MT-LR is restricted and be enabled to accept or override the restriction. Usage of this parameter is defined in 3GPP TS 23.271.
2904 7.6.3.65C
GMLC List Withdraw
2905 This parameter indicates whether the subscribers LCS GMLC list shall be deleted from the VLR or SGSN.
2906 7.6.3.66
IST Alert Timer
2907 This parameter indicates the IST Alert Timer value that must be used in the MSC to inform the HLR about the call 2908 activities that the subscriber performs. Units are minutes.
2909 7.6.3.67
Call Termination Indicator
2910 This parameter indicates whether the MSC shall terminate a specific ongoing call, or all the call activities related to a 2911 specified subscriber.
2912 7.6.3.68
IST Information Withdraw
2913 This parameter indicates that IST information shall be deleted from the VMSC.
318
2914 7.6.3.69
319 Release 4 320 321
81
3GPP TS 29.002 V4.17.0 (2006-06)
IST Support Indicator
2915 This parameter indicates the degree of IST functionality supported by the MSC (Visited MSC or Gateway MSC). It can 2916 take one of the following values: 2917 2918 2919
Basic IST functionality; IST command service (in addition to the basic IST functionality and including the ability to terminate all calls being carried for the identified subscriber).
2920 7.6.3.70
Super-Charger Supported In HLR
2921 This parameter is used by the HLR to indicate support of the Super-Charger functionality and an indication of the age of 2922 the subscription data stored in the HLR.
2923 7.6.3.71
Super-Charger Supported In Serving Network Entity
2924 This parameter is used to indicate support of the Super-Charger functionality by the originating entity and to indicate 2925 either that subscription data is required or the date and time of the last know subscriber data modification.
2926 7.6.3.72
Age Indicator
2927 This parameter is used by the HLR to determine the validity of the subscription data retained by the serving network 2928 entity in a Super-Charged network.
2929 7.6.3.73
GPRS enhancements support indicator
2930 This parameter indicates to the HLR that the SGSN supports GPRS enhancements.
2931 7.6.3.74
Extensible QoS-Subscribed
2932 This parameter indicates the enhanced QoS subscribed for a certain service. It is defined in 3GPP TS 23.060. This 2933 parameter is an extension to QoS-Subscribed.
2934 7.6.3.75
SGSN Camel Subscription Info
2935 This parameter identifies the subscriber as having CAMEL services that are invoked in the SGSN.
2936 7.6.3.76
SMS-CSI
2937 This parameter identifies the subscriber as having SMS CAMEL services as defined in 3GPP TS 23.078.
2938 7.6.3.77
GPRS-CSI
2939 This parameter identifies the subscriber as having GPRS CAMEL services as defined in 3GPP TS 23.078.
2940 7.6.3.78
CAMEL subscription info
2941 This parameter indicates the CSI that can be controlled by CSE.
2942 7.6.3.79
SS-Code;
Extensible Call barring information for CSE
2943 This parameter contains for each call barring service for CSE: 2944 2945 2946
a list of extensible call barring feature parameters. The list may contain one item per Basic Service Group.
322
2947 2948 2949
323 Release 4 324 325
82
3GPP TS 29.002 V4.17.0 (2006-06)
password; wrong password attempt counter; notification-to-CSE flag.
2950 7.6.3.80
-
Extensible Forwarding information for CSE
2951 This parameter represents the information for CSE related to each call forwarding service: 2952 2953 2954 2955
the SS-Code of the relevant call forwarding service; if required, a list of extensible forwarding feature parameters; the list may contain one item per Basic Service Group; notification-to-CSE flag.
2956 7.6.3.81
Modification Request for CSI
2957 This parameter indicates the CAMEL subscription information to be modified by CSE.
2958 7.6.3.82
Modification Request for SS Information
2959 This parameter indicates the call forwarding and call barring supplementary service data to be modified by CSE.
2960 7.6.3.83
Call Barring Data
2961 This parameter contains the extensible call barring feature list (see clause 7.6.3.21) and Notification to CSE flag.
2962 7.6.3.84
Call Forwarding Data
2963 This parameter contains the extensible call forwarding feature list (see clause 7.6.3.16) and Notification to CSE flag.
2964 7.6.3.85
ODB Data
2965 This parameter contains the ODB general data, ODB HPLMN specific data .
2966 7.6.3.86
Requested Subscription Info
2967 This parameter indicates the subscription information being requested.
2968 7.6.3.87
CS Allocation/Retention priority
2969 This parameter indicates the allocation/retention priority for Circuit Switched (CS). It corresponds to the 2970 allocation/retention priority that is defined in 3GPP TS 23.107.
2971 7.6.3.88
ODB Info
2972 This parameter contains the ODB data and Notification to CSE flag. 2973
2974 2975 7.6.4.1
7.6.4 Supplementary services parameters
SS-Code
2976 This parameter may refer to one supplementary service or a set of supplementary services as defined in 3GPP TS 2977 22.004. For this includes:
326
2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996
327 Release 4 328 329
83
3GPP TS 29.002 V4.17.0 (2006-06)
Calling Line Identification Presentation service (CLIP); Calling Line Identification Restriction service (CLIR); Connected Line Identification Presentation service (COLP); Connected Line Identification Restriction service (COLR); Calling Name Presentation (CNAP); All Call Forwarding services; Call Waiting (CW); Call Hold (HOLD); Multi-Party service (MPTY); Closed User Group (CUG); All Charging services; All Call Restriction services; Explicit Call Transfer service (ECT); enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Completion of Calls to Busy Subscriber, originating side (CCBS-A); Completion of Calls to Busy Subscriber, destination side (CCBS-B); All LCS privacy exceptions (see clause 7.6.4.44); (see clause 7.6.4.45);
Mobile Originating Location Request (MO-LR) Multicall (MC).
2997 7.6.4.2
SS-Status
2998 This parameter refers to the state information of individual supplementary services as defined in 3GPP TS 23.011.
2999 7.6.4.3
SS-Code
SS-Data
(see clause 7.6.4.1); (see clause 7.6.4.2); (see clause 7.6.4.4); (see clause 7.6.4.5); (see clause 7.6.4.40).
3000 This parameter refers to the necessary set of information required in order to characterise one supplementary service: 3001 3002 3003 3004 3005
SS-Status (if applicable) Override subscription option CLI Restriction Basic Service Group Code
3006 7.6.4.4
Override Category
3007 This parameter refers to the subscription option Override Category attached to a supplementary service. It can take the 3008 following two values: 3009 3010
Enabled; Disabled.
330
3011 7.6.4.5
331 Release 4 332 333
84
3GPP TS 29.002 V4.17.0 (2006-06)
CLI Restriction Option
3012 This parameter refers to the subscription option Restriction mode attached to the CLIR supplementary service. It can 3013 take the following three values: 3014 3015 3016
Permanent; Temporary (Default Restricted); Temporary (Default Allowed).
3017 7.6.4.6
Forwarding Options
3018 This parameter refers to a forwarding option attached to a supplementary service. It can take one of the following 3019 values: 3020 3021 3022 3023
notification to forwarding party notification to calling party redirecting presentation Forwarding reason
(see 3GPP TS 22.082 [10] for the meaning of this parameter); (see 3GPP TS 22.082 [10] for the meaning of this parameter); (see 3GPP TS 22.082 [10] for the meaning of this parameter); (see 3GPP TS 22.082 [10] for the meaning of this parameter).
3024 7.6.4.7
No reply condition timer
3025 This parameter refers to the no reply condition timer for call forwarding on no reply.
3026 7.6.4.8 - 7.6.4.14 Void 3027 7.6.4.15
-
Forwarding information
(see clause 7.6.4.1); (see clause 7.6.4.16).
3028 This parameter represents the information related to each call forwarding service: 3029 3030 3031
the SS-Code of the relevant call forwarding service if required, a list of forwarding feature parameters the list may contain one item per Basic Service Group.
3032 7.6.4.16
Forwarding feature
3033 This parameter applies to each combination of call forwarding service and Basic Service Group and contains the 3034 following information, as required: 3035 3036 3037 3038 3039 3040 3041
Basic Service Group SS-Status forwarded-to number forwarded-to subaddress forwarding options no reply condition timer long forwarded-to number
(see clause 7.6.4.40); (see clause 7.6.4.2); (see clause 7.6.2.22); (see clause 7.6.2.23); (see clause 7.6.4.6); (see clause 7.6.4.7); (see clause 7.6.2.22A).
3042 If a number is required to define the forwarded-to destination then: 3043 3044
If the VLR supports Long Forwarded-to Numbers then the long forwarded-to number shall be present and the forwarded-to number shall be absent.
334
3045 3046
335 Release 4 336 337
85
3GPP TS 29.002 V4.17.0 (2006-06)
If the VLR does not support Long Forwarded-to Numbers then the forwarded-to number shall be present and the long forwarded-to number shall be absent.
3047 7.6.4.17 3048 7.6.4.18
SS-Code
Void Call barring information
(see clause 7.6.4.1); (see clause 7.6.4.19).
3049 This parameter contains for each call barring service: 3050 3051 3052
a list of call barring feature parameters The list may contain one item per Basic Service Group.
3053 7.6.4.19
Call barring feature
3054 This parameter gives the status of call barring services as applicable to each Basic Service Group. The parameter 3055 contains the following information: 3056 3057
Basic Service Group SS-Status
(see clause 7.6.4.40); (see clause 7.6.4.2).
3058 7.6.4.20
New password
3059 This parameter refers to the password which the subscriber just registered in the network. 3060 This parameter refers to a password used by the subscriber for supplementary service control.
3061 7.6.4.21
Current password
3062 This parameter refers to a password used by the subscriber for supplementary service control.
3063 7.6.4.22
Guidance information
3064 This parameter refers to guidance information given to a subscriber who is requested to provide a password. One of the 3065 following information may be given: 3066 3067 3068 3069 3070 3071
"enter password"; this information is used for checking of the old password;
"enter new password"; this information is used during password registration for the request of the first new password;
"enter new password again"; this information is used during password registration for the request of the new password again for verification.
3072 7.6.4.23 3073 7.6.4.24
-
Void SS-Info
3074 This parameter refers to all the information related to a supplementary service and is a choice between: 3075 3076 3077
forwarding information call barring information CUG info
(see clause 7.6.4.15); (see clause 7.6.4.18); (see clause 7.6.4.8);
338
3078 3079
339 Release 4 340 341
86
3GPP TS 29.002 V4.17.0 (2006-06)
SS-Data eMLPP information
(see clause 7.6.4.3). (see clause 7.6.4.41).
3080 7.6.4.25 - 7.6.4.35 Void 3081 7.6.4.36 USSD Data Coding Scheme
3082 This parameter contains the information of the alphabet and the language used for the unstructured information in an 3083 Unstructured Supplementary Service Data operation. The coding of this parameter is according to the Cell Broadcast 3084 Data Coding Scheme as specified in 3GPP TS 23.038 [25].
3085 7.6.4.37
USSD String
3086 This parameter contains a string of unstructured information in an Unstructured Supplementary Service Data operation. 3087 The string is sent either by the mobile user or the network. The contents of a string sent by the MS are interpreted by the 3088 network as specified in 3GPP TS 22.090 [16].
3089 7.6.4.38
Bearer service
3090 This parameter may refer to a single bearer service, a set of bearer services or to all bearer services as defined in 3GPP 3091 TS 22.002 [3]. This parameter is used only for supplementary service management.
3092 7.6.4.39
Teleservice
3093 This parameter may refer to a single teleservice, a set of teleservices or to all teleservices as defined in 3GPP TS 22.003 3094 [4]. This parameter is used only for supplementary service management.
3095 7.6.4.40
Basic Service Group
3096 This parameter refers to the Basic Service Group either as a bearer service (see clause 7.6.4.38) or a teleservice (see 3097 clause 7.6.4.39). This parameter is used only for supplementary service management. The null value (i.e. neither bearer 3098 service nor teleservice) is used to denote the group containing all bearer services and all teleservices.
3099 7.6.4.41
eMLPP information
3100 This parameter contains two parameters which are associated with the eMLPP service. The following two parameters 3101 are included: 3102 3103 3104 3105
maximum entitled priority: indicates the highest priority level the subscriber is allowed to apply for an outgoing call set-up;
default priority: defines the priority level which shall be assigned to a call if no explicit priority is indicated during call set-up.
3106 7.6.4.42
SS-event
3107 This parameter indicates the Supplementary Service for which an invocation notification is sent towards the gsmSCF. It 3108 can indicate one of the following services: 3109 3110 3111 3112
Explicit Call Transfer (ECT) Call Deflection (CD) Multi-Party call (MPTY) Completion of Calls to Busy Subscriber (CCBS)
342
3113 7.6.4.43
343 Release 4 344 345
87
3GPP TS 29.002 V4.17.0 (2006-06)
SS-event data
3114 This parameter contains additional information related to Supplementary Service invocation. Depending on the service 3115 invoked it can contain the following information: 3116 3117
ECT A list with all Called Party Numbers involved. CD The called Party number involved.
3118 7.6.4.44
-
LCS Privacy Exceptions
3119 Distinct SS codes are assigned to the following classes of LCS client in a target MS subscribers privacy exception list. 3120 3121 3122 3123
Universal Class; Call/session related value added class; Call/session unrelated value added class; PLMN operator class.
3124 7.6.4.45
-
Mobile Originating Location Request (MO-LR)
3125 Distinct SS codes are assigned to the following classes of MO-LR: 3126 3127 3128
Basic Self Location; Autonomous Self Location; Transfer to Third Party.
3129 7.6.4.46
NbrUser
3130 This parameter indicates the maximum number of parallel bearers that may be used as defined by the user at registration 3131 of the MC SS.
3132 7.6.4.47
MC Subscription Data
3133 This parameter contains two parameters which are associated with the MC service. The following two parameters are 3134 included:
3135
3136 3137
NbrUser: indicates the maximum number of parallel bearers that may be used as defined by the user at registration of the MC SS NbrSB: indicates the maximum number of parallel bearers that may be used as defined by the users subscription.
3138
3139
3140 7.6.4.48
MC Information
3141 This parameter contains three parameters which are associated with the MC service. The following parameters are 3142 included: 3143 3144 3145
NbrSB; NbrUser; NbrSN.
3146 Definitions of these parameters are provided in 3GPP TS 23.135.
346
3147 7.6.4.49
request; recall; active;
347 Release 4 348 349
88
3GPP TS 29.002 V4.17.0 (2006-06)
CCBS Request State
3148 This parameter indicates the current state of the CCBS request. It can take one of seven values: 3149 3150 3151 3152 3153 3154 3155
completed; suspended; frozen; deleted.
3156 3157 7.6.5.1
7.6.5 Call parameters
Call reference number
3158 This parameter refers to a call reference number allocated by a call control MSC.
3159 7.6.5.2
Interrogation type
3160 This parameter refers to the type of interrogation for routing information which is sent from a GMSC to an HLR. It can 3161 take either of two values: 3162 3163 3164
basic call (for information to route a call before the call has been extended to the VMSC of the called party); forwarding (for information to route the call to the forwarded-to destination after the VMSC of the forwarding party has requested the GMSC to resume handling of the call.
3165 7.6.5.3
OR interrogation
3166 This parameter indicates that the GMSC which interrogated the HLR for routeing information is not in the same PLMN 3167 as the HLR, and therefore that the call will potentially be optimally routed.
3168 7.6.5.4
OR capability
3169 This parameter indicates the phase of OR which the GMSC supports.
3170 7.6.5.5
-
Forwarding reason
3171 This parameter indicates the reason for which the call is to be forwarded. It can take one of three values: 3172 3173 3174
busy subscriber; mobile subscriber not reachable; no subscriber reply.
3175 7.6.5.6
Forwarding interrogation required
3176 This parameter indicates that if the VMSC of the forwarding subscriber requests the GMSC to resume handling of the 3177 call the GMSC shall interrogate the HLR for forwarding information.
3178 7.6.5.7
O-CSI
3179 This parameter identifies the subscriber as having originating CAMEL services as defined in 3GPP TS 23.078.
350
3180 7.6.5.7A
351 Release 4 352 353
89
3GPP TS 29.002 V4.17.0 (2006-06)
D-CSI
3181 This parameter identifies the subscriber as having originating CAMEL dialled services as defined in 3GPP TS 23.078.
3182 7.6.5.7B
T-CSI
3183 This parameter identifies the subscriber as having terminating CAMEL services in the GMSC, as defined in 3184 TS 3G 23.078.
3185 7.6.5.7C
VT-CSI
3186 This parameter identifies the subscriber as having terminating CAMEL services in the VMSC, as defined in 3GPP 3187 TS 23.078.
3188 7.6.5.8
Call Direction
3189 This parameter is used to indicate the direction of the call.
3190 7.6.5.9
Channel Type
3191 This parameter is the result of a Channel Mode Modification for TS 61/62. It contains the changed Air Interface User 3192 Rate. The information is sent from the SIWFS to the MSC to assign the correct radio resource. This parameter is 3193 defined in 3GPP TS 48.008 [49].
3194 7.6.5.10
Chosen Channel
3195 This parameter is sent from the MSC to the SIWFS to adjust the interworking unit to the assigned radio resources. This 3196 parameter is defined in 3GPP TS 48.008 [49].
3197 7.6.5.11
CCBS Feature
3198 This parameter corresponds to the 'CCBS Description' parameter in 3GPP TS 23.093. It refers to the necessary set of 3199 information required in order to characterise a certain CCBS request. The parameter may contain the following 3200 information: 3201 3202 3203 3204
CCBS Index B-subscriber number B-subscriber subaddress Basic Service Group Code
(see 3GPP TS 23.093 for the use of this parameter); (see clause 7.6.2.48); (see clause 7.6.2.49); (see clause 7.6.4.40).
3205 7.6.5.12
UU Data
3206 This parameter includes User-To-User Data. It is defined in 3GPP TS 23.087.
3207 7.6.5.13
UUS CF Interaction
3208 This parameter indicates if the call forwarding or call deflection has been activated after UUS1 request has been 3209 accepted . It is defined in 3GPP TS 23.087.
3210 7.6.5.14
Number Portability Status
3211 This parameter indicates the number portability status of subscriber. See 3GPP TS 23.066 [108].
3212 7.6.5.15
Pre-paging supported
3213 This parameter indicates that the entity which sent it supports pre-paging.
354
3214
355 Release 4 356 357
90
3GPP TS 29.002 V4.17.0 (2006-06)
7.6.6 Radio parameters
Void
3215 7.6.6.1 - 7.6.6.4 3216 7.6.6.5
BSSMAP Service Handover
3217 This parameter refers to the Service Handover information element defined in 3GPP TS 48.008
3218 7.6.6.5A
BSSMAP Service Handover List
3219 This parameter refers to the list of Service Handover information elements defined in 3GPP TS 48.008. This parameter 3220 shall be used when there are multiple bearers and at least one of the bearers has an associated BSSMAP Service 3221 Handover parameter.
3222 7.6.6.6
RANAP Service Handover
3223 This parameter refers to the Service Handover information element defined in 3GPP TS 25.413.
3224 7.6.6.7
HO-Number Not Required
3225 This parameter indicates that no handover or relocation number allocation is necessary.
3226 7.6.6.8
Integrity Protection Information
3227 This parameter refers to the Integrity Protection Information element defined in 3GPP TS 25.413.
3228 7.6.6.9
Encryption Information
3229 This parameter refers to the Encryption Information element defined in 3GPP TS 25.413.
3230 7.6.6.10
Radio Resource Information
3231 This parameter refers to the Channel Type information element defined in 3GPP TS 48.008 [49].
3232 7.6.6.10A
Radio Resource List
3233 This parameter refers to list of RAB-id's and their associated Channel Type information elements defined in 3GPP TS 3234 48.008. This parameter shall be used when there are multiple bearers and at least one of the bearers has an associated 3235 Radio Resource Information parameter.
3236 7.6.6.10B
Chosen Radio Resource Information
3237 This parameter refers to the Chosen Channel and Speech Version information elements defined in 3GPP TS 48.008.
3238 7.6.6.11
Key Status
3239 This parameter refers to the Key Status element defined in 3GPP TS 25.413.
3240 7.6.6.12
Selected UMTS Algorithms
3241 This parameters identifies the UMTS integrity and optionally encryption algorithms selected by MSC-B. Coding of this 3242 parameter is defined in 3GPP TS 25.413.
3243 7.6.6.13
Allowed GSM Algorithms
3244 This parameters identifies the allowed GSM algorithms in MSC-B. Coding of this parameter is defined in 3GPP TS 3245 48.008.
358
3246 7.6.6.14
359 Release 4 360 361
91
3GPP TS 29.002 V4.17.0 (2006-06)
Allowed UMTS Algorithms
3247 This parameters identifies the allowed UMTS algorithms in MSC-B. Coding of this parameter is defined in 3GPP TS 3248 25.413.
3249 7.6.6.15
Selected GSM Algorithm
3250 This parameter identifies the GSM algorithm selected by GSM BSC controlled by MSC-B. Coding of this parameter is 3251 defined in 3GPP TS 48.008.
3252 3253 7.6.7.1
7.6.7 Authentication parameters
Authentication set list
3254 This parameter represents a list of sets of authentication parameters for a given subscriber. 3255 The list either contains Authentication Triplets (Rand, Sres, Kc) or Authentication Quintuplets (Rand, Xres, Ck, Ik, 3256 Autn). If the list contains Authentication Quintuplets, the order of sequence in this list is chronological, the first 3257 quintuplet in the list is the oldest one.
3258 7.6.7.2
Rand
3259 This parameter represents a random number used for authentication.
3260 7.6.7.3
Sres
3261 This parameter represents the response to an authentication request.
3262 7.6.7.4
Kc
3263 This parameter refers to a key used for ciphering purposes.
3264 7.6.7.5
Xres
3265 This parameter represents the response to an UMTS authentication request.
3266 7.6.7.5A
Ck
3267 This parameter refers to a key used for UMTS ciphering purposes.
3268 7.6.7.5B
Ik
3269 This parameter refers to the Integrity Key.
3270 7.6.7.5C
Autn
3271 This parameter refers to the Authentication Token.
3272 7.6.7.6
Cksn
3273 This parameter refers to a ciphering key sequence number.
3274 7.6.7.6A
Ksi
3275 This parameter refers to a key set identifier.
3276 7.6.7.6B
Auts
362
3277 This parameter refers to the resynchronisation token.
363 Release 4 364 365
92
3GPP TS 29.002 V4.17.0 (2006-06)
3278 7.6.7.7
-
Ciphering mode
3279 This parameter refers to the ciphering mode which is associated with a radio channel. It may take values as follows: 3280 3281
no encryption; identification of specific ciphering algorithm.
3282 7.6.7.8
Current Security Context
3283 This parameter represents a list of security context parameters for a given subscriber. 3284 The list either contains GSM Security Context data (Kc, Cksn) or UMTS Security Context Data (Ck, Ik, Ksi).
3285 7.6.7.9
-
Failure cause
3286 This parameter refers to an authentication failure which has occurred. It may take values as follows: 3287 3288
wrong user response; wrong network signature.
3289 7.6.7.10
Re-attempt
3290 It indicates whether the failure ocurred in a normal authentication attempt or in an authentication reattempt (there was a 3291 previous unsuccessful authentication).
3292 7.6.7.11
Access Type
3293 It indicates whether the authentication procedure was initiated due to a call, an emergency call, a location updating, a 3294 supplementary service procedure, a short message transfer, a GPRS attach procedure, a routing area updating, a service 3295 request, a MS initiated Detach in GPRS, a PDP context activation or a PDP context deactivation procedure.
3296 3297 7.6.8.1
7.6.8 Short message parameters
SM-RP-DA
3298 This parameter represents the destination address used by the short message service relay sub-layer protocol. It can be 3299 either of the following: 3300 3301 3302 3303 3304
IMSI LMSI MS-ISDN roaming number service centre address
(see clause 7.6.2.1); (see clause 7.6.2.16); (see clause 7.6.2.17); (see clause 7.6.2.19); (see clause 7.6.2.27).
3305 7.6.8.2
SM-RP-OA
3306 This parameter refers to the originating address used by the short message service relay sub-layer protocol. It can be 3307 either of the following: 3308 3309
MS-ISDN service centre address
(see clause 7.6.2.17); (see clause 7.6.2.27).
366
3310 7.6.8.3
3311 3312 3313 3314
367 Release 4 368 369
93
3GPP TS 29.002 V4.17.0 (2006-06)
MWD status
This parameter indicates whether or not the address of the originator service centre is already contained in the Message Waiting Data file. In addition, it contains the status of the Memory Capacity Exceeded Flag (MCEF), the status of the Mobile subscriber Not Reachable Flag (MNRF) and the status of the Mobile station Not Reachable for GPRS flag (MNRG).
3315 7.6.8.4
SM-RP-UI
3316 This parameter represents the user data field carried by the short message service relay sub-layer protocol.
3317 7.6.8.5
SM-RP-PRI
3318 This parameter is used to indicate whether or not delivery of the short message shall be attempted when a service centre 3319 address is already contained in the Message Waiting Data file.
3320 7.6.8.6
-
SM Delivery Outcome
3321 This parameter indicates the cause for setting the message waiting data. It can take one of the following values: 3322 3323 3324
Absent subscriber; MS memory capacity exceeded; Successful transfer.
3325 7.6.8.7
More Messages To Send
3326 This parameter is used to indicate whether or not the service centre has more short messages to send.
3327 7.6.8.8
-
Alert Reason
3328 This parameter is used to indicate the reason why the service centre is alerted. It can take one of the following values: 3329 3330
MS present; Memory Available.
3331 7.6.8.9
Absent Subscriber Diagnostic SM
3332 This parameter is used to indicate the reason why the subscriber is absent. For the values for this parameter see 3GPP 3333 TS 23.140.
3334 7.6.8.10
Alert Reason Indicator
3335 This parameter indicates that the alert reason is sent to the HLR due to GPRS activity.
3336 7.6.8.11
Additional SM Delivery Outcome
3337 This parameter is used to indicate the GPRS delivery outcome in case a combination between delivery outcome for 3338 GPRS and non-GPRS are sent to the HLR.
3339 7.6.8.12
Additional Absent Subscriber Diagnostic SM
3340 This parameter indicates the reason of the additional SM Delivery Outcome.
3341 7.6.8.13
Delivery Outcome Indicator
3342 This parameter indicates that the delivery outcome sent to the HLR is for GPRS.
370
3343 7.6.8.14
371 Release 4 372 373
94
3GPP TS 29.002 V4.17.0 (2006-06)
GPRS Node Indicator
3344 This parameter indicates that the Network Node Number sent by the HLR is the SGSN number.
3345 7.6.8.15
GPRS Support Indicator
3346 This parameter indicates that the SMS-GMSC supports GPRS specific procedure of combine delivery of Short Message 3347 via MSC and/or via the SGSN.
3348 7.6.8.16
SM-RP-MTI
3349 This parameter represents the RP-Message Type Indicator of the Short Message. It is used to distinguish a SM sent to 3350 the mobile station in order to acknowledge an MO-SM initiated by the mobile from a normal MT-SM. This parameter is 3351 formatted according to the formatting rules of address fields as described in 3GPP TS 23.140.
3352 7.6.8.17
SM-RP-SMEA
3353 This parameter represents the RP-Originating SME-address of the Short Message Entity that has originated the SM. 3354 This parameter is used by the short message service relay sub-layer protocol and is formatted according to the 3355 formatting rules of address fields as described in 3GPP TS 23.140.
3356 3357 7.6.9.1
3358 3359 3360 3361
7.6.9 Access and signalling system related parameters
AN-apdu
This parameter includes one or two concatenated complete 3GPP TS 25.413 or 3GPP TS 48.006 [48] messages, as described in 3GPP TS 23.009 and 3GPP TS 29.010. The access network protocol ID indicates that the message or messages are according to either 3GPP TS 48.006 [48] or 3GPP TS 25.413. For the coding of the messages see 3GPP TS 25.413, 3GPP TS 48.006 [48] and 3GPP TS 48.008 [49].
3362 7.6.9.2
-
CM service type
3363 This parameter identifies the service category being requested by the subscriber: 3364 3365 3366 3367 3368 3369 3370 3371
mobile originating call; emergency call establishment; short message service; mobile originating call re-establishment; mobile terminating call; SS request; Voice group call set-up; Voice broadcast set-up.
3372 7.6.9.3
-
Access connection status
3373 This parameter represents the following access connection status information: 3374 3375 3376
RR-connection status (established/not established); ciphering mode (on/off); authentication status (authenticated/not authenticated).
3377 7.6.9.4
External Signal Information
374
3378 This parameter contains concatenated information elements (including tag and length) which are defined by a common 3379 protocol version, preceded by the associated protocol ID. It is used to transport information of the indicated protocol via 3380 MAP interfaces.
375 Release 4 376 377
95
3GPP TS 29.002 V4.17.0 (2006-06)
3381 7.6.9.5
Access signalling information
3382 This parameter refers to any set of information elements imported from 3GPP TS 24.008 [35].
3383 7.6.9.6
Location update type
3384 This parameter refers to the location update type (normal, periodic or IMSI attach) contained in the 3GPP TS 24.008 3385 [35] LOCATION REGISTRATION REQUEST message.
3386 7.6.9.7
Protocol ID
3387 This parameter refers to the protocol to which the coding of the content of the associated External Signal Information 3388 conforms. 3389 The following values are defined: 3390 3391 3392
04.08; 08.06; ETS 300 102-1.
3393 This value indicates the protocol defined by ETS 300 102-1 (EDSS1).
3394 7.6.9.8
Network signal information
3395 This parameter is transported as external signal information. The protocol ID shall be set to "ETS 300 102-1". 3396 The network signal information may include the following information elements as defined in 3GPP TS 29.007 [56]: 3397 3398 3399 3400 3401 3402
ISDN BC; the tag and length are defined by ETS 300 102-1. For the content, see 3GPP TS 29.007 [56].
HLC; the tag and length are defined by ETS 300 102-1. For the content, see 3GPP TS 29.007 [56].
LLC; the tag and length are defined by ETS 300 102-1. For the content, see 3GPP TS 29.007 [56].
3403 They are contained in the Signal Information parameter according to figure 7.6/1 (irrespective of the order):
378
379 Release 4 380 381
96
3GPP TS 29.002 V4.17.0 (2006-06)
IS D N B C T A G LEN G TH C O N TEN T H LC TAG LEN G TH C O N TEN T LLC TAG LEN G TH C O N TEN T
3404
3405
Figure 7.6/1: Network signal information parameter
3406 7.6.9.9
Call Info
3407 This parameter is transported as external signal information. The protocol ID shall be set to "3GPP TS 24.008 [35]". 3408 The Call Info includes the set of information elements from the original SETUP message and is imported from 3GPP 3409 TS 24.008 [35].
3410 7.6.9.10
Additional signal info
3411 This parameter is transported as external signal information. The protocol ID shall be set to "ETS 300 356". 3412 The additional signal information may include the following information elements: 3413 3414
Calling Party Number as defined by ETS 300 356. Generic Number as defined by ETS 300 356.
3415 They are contained in the Signal Information parameter according to figure 7.6/2 (irrespective of the order):
CALLING PARTY NUMBER TAG
LENGTH CONTENT
GENERIC NUMBER TAG
3416
3417
LENGTH CONTENT
Figure 7.6/2: Additional signal information parameter
3418 3419 7.6.10.1
-
7.6.10 System operations parameters
Network resources
3420 This parameter refers to a class or type of network resource: 3421
PLMN;
382
3422 3423 3424 3425 3426
383 Release 4 384 385
97
3GPP TS 29.002 V4.17.0 (2006-06)
HLR; VLR (current or previous); MSC (controlling or current); EIR; radio sub-system.
3427 7.6.10.2
Trace reference
3428 This parameter represents a reference associated with a tracing request. The parameter is managed by OMC.
3429 7.6.10.3
Trace type
3430 This parameter identifies the type of trace. Trace types are fully defined in GSM 12.08.
3431 3432 7.6.11.1
7.6.11 Location Service Parameters
Age of Location Estimate
3433 This parameter indicates how long ago the location estimate was obtained.
3434 7.6.11.2
Deferred MT-LR Response Indicator
3435 This parameter shows that this is a response to a deferred mt-lr request.
3436 7.6.11.3
3437 3438 3439 3440 3441 3442 3443 3444
Deferred MT-LR Data
This parameter is used to report the deferred location event type, the location information and reason why the serving node aborted monitoring the event to the GMLC. The termination cause mt-lrRestart shall be used to trigger the GMLC to restart the location procedure in all the cases where the sending node detects that the location procedure cannot be successfully performed anymore by the sending node and that it could be successfully performed by another node (as for example when. Cancel Location or Send Identification has been received). The location information shall be included only if the termination cause is mt-lrRestart. The network node number contained in the location information refers to the node where the MS/UE has moved to and shall be included if available, like in case Send Identification has been received.
3445 7.6.11.4
LCS Client ID
3446 This parameter provides information related to the identity of an LCS client.
3447 7.6.11.5
3449 7.6.11.6
LCS Event
3448 This parameter identifies an event associated with the triggering of a location estimate.
Void
3450 7.6.11.7
LCS Priority
3451 This parameter gives the priority of the location request.
3452 7.6.11.8
LCS QoS
3453 This parameter defines the Quality of Service (QoS) for any location request. It is composed of the following elements. 3454 3455
1) Response Time Indicates the category of response time low delay or delay tolerant.
386
3456 3457 3458 3459 3460 3461
387 Release 4 388 389
98
3GPP TS 29.002 V4.17.0 (2006-06)
2) Horizontal Accuracy Indicates the required horizontal accuracy of the location estimate. 3) Vertical Coordinate Indicates if a vertical coordinate is required (in addition to horizontal coordinates). 4) Vertical Accuracy Indicates the required vertical accuracy of the location estimate (inclusion is optional).
3462 7.6.11.9 3463 7.6.11.10 3464 7.6.11.11
3465 3466 3467 3468 3469 3470 3471 3472 3473
Void Void Location Estimate
This parameter gives an estimate of the location of an MS in universal coordinates and the accuracy of the estimate. The estimate is expressed in terms of the geographical shapes defined by 3GPP TS 23.032. and is composed of the type of shape plus the encoding of the shape itself. Any type of shape defined in 3GPP TS 23.032 can be filled in in the Location Estimate parameter, but only the encoding of the following shapes shall be carried by Location Estimate: - Ellipsoid point with uncertainty circle - Ellipsoid point with uncertainty ellipse - Ellipsoid point with altitude and uncertainty ellipsoid - Ellipsoid arc - Ellipsoid point
3474 The encoding for the remaining types of shape, defined in the 3GPP TS 23.032, shall be filled in in the Additional 3475 Location Estimate parameter. 3476
3477 7.6.11.12
Location Type
3478 This parameter indicates the type of location estimate required by the LCS client. Possible location estimate types 3479 include:
3480 3481 3482 3483
current location; current or last known location; initial location for an emergency services call; deferred location event type.
3484 7.6.11.13
NA-ESRD
3485 This parameter only applies to location for an emergency services call in North America and gives the North American 3486 Emergency Services Routing Digits.
3487 7.6.11.14
NA-ESRK
3488 This parameter only applies to location for an emergency services call in North America and gives the North American 3489 Emergency Services Routing Key.
3490 7.6.11.15
Void
390
3491 7.6.11.16
391 Release 4 392 393
99
3GPP TS 29.002 V4.17.0 (2006-06)
Privacy Override
3492 This parameter indicates if MS privacy is overridden by the LCS client when the GMLC and VMSC/SGSN for an MT3493 LR are in the same country.
3494 7.6.11.17
Supported LCS Capability Sets
3495 This parameter indicates which capability sets of LCS are supported in the VLR or SGSN.
3496 7.6.11.18
Void
3497 7.6.11.19 NA-ESRK Request
3498 This parameter allows the MSC to indicate that it requires the GMLC to allocate a NA-ESRK based on the target MS 3499 location estimate. This parameter only applies to emergency services calls in North America.
3500 3501 7.6.11.20 Supported GAD Shapes
3502 This parameter indicates which of the shapes defined in 3GPP TS 23.032 are supported. If the parameter is not provided 3503 then the receiving node shall assume that the sending entity supports the following shapes: 3504 3505 3506 3507 3508
- Ellipsoid point with uncertainty circle - Ellipsoid point with uncertainty ellipse - Ellipsoid point with altitude and uncertainty ellipsoid - Ellipsoid arc - Ellipsoid point
3509 7.6.11.21
Additional Location Estimate
3510 This parameter gives an estimate of the location of an MS/UE in universal coordinates and the accuracy of the estimate. 3511 This parameter allows the location estimate to be expressed in any of the geographical shapes defined in 3GPP TS 3512 23.032
3513 7.6.11.22
LCS-Reference Number
3514 This parameter represents a reference between a request and a responce of a deferred mt-lr procedure as deccribed in 3515 3GPP TS 23.271 [26a]. 3516
3517
3518
7.6.12 void
3519 3520
7.7 Representation of a list of a basic parameter in serviceprimitives
3521 In some service-primitives several instances of a basic parameter of clause 7.6 are required. In the service descriptions 3522 such cases will be represented as 3523
ParameterNameLIST
394
3524 in the tables where ParameterName refers to one of the parameters defined in clause 7.6. This corresponds to the 3525 following construction rule:
395 Release 4 396 397
100
3GPP TS 29.002 V4.17.0 (2006-06)
3526
3527
P a ra m e te r
Figure 7.7/1: Construction of Lists
3528 3529 3530
8 Mobility services
8.1 Location management services
8.1.1 Void
Void Void Void
3531 8.1.1.1 3532 8.1.1.2 3533 8.1.1.3 3534 3535 8.1.2.1
8.1.2 MAP_UPDATE_LOCATION service
Definition
3536 This service is used by the VLR to update the location information stored in the HLR. 3537 The MAP_UPDATE_LOCATION service is a confirmed service using the service primitives given in table 8.1/2.
3538 8.1.2.2
3539
Service primitives
Table 8.1/2: MAP_UPDATE_LOCATION
Parameter name Invoke Id IMSI MSC Address VLR number LMSI Supported CAMEL Phases SoLSA Support Indicator IST Support Indicator Super-Charger Supported in Serving Network Entity Long FTN Supported Supported LCS Capability Sets Inform Previous Network Entity HLR number User error Provider error
Request M M M M U C C C C C C C
Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=)
Response M(=)
Confirm M(=)
C C
C(=) C(=) O
3540
3541 8.1.2.3
3542 Invoke Id
Parameter definitions and use
398
3543 See definition in clause 7.6.1. 3544 IMSI 3545 See definition in clause 7.6.2. 3546 MSC Address 3547 See definition for MSC number in clause 7.6.2. The MSC address is used for short message delivery only and for each 3548 incoming call set-up attempt the MSRN will be requested from the VLR. 3549 VLR number 3550 See definition in clause 7.6.2. 3551 LMSI 3552 See definition in clause 7.6.2. It is an operator option to provide the LMSI from the VLR; it is mandatory for the HLR 3553 to support the LMSI handling procedures. 3554 Supported CAMEL Phases 3555 This parameter indicates which phases of CAMEL are supported. Must be present if a CAMEL phase different from 3556 phase 1 is supported. Otherwise may be absent. 3557 HLR number 3558 See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful HLR updating. 3559 SoLSA Support Indicator 3560 3561 3562 3563
399 Release 4 400 401
101
3GPP TS 29.002 V4.17.0 (2006-06)
This parameter is used by the VLR to indicate to the HLR in the Update Location indication that SoLSA is supported. If this parameter is not included in the Update Location indication and the Subscriber is marked as only allowed to roam in Subscribed LSAs, then the HLR shall reject the roaming and indicate to the VLR that roaming is not allowed to that Subscriber in the VLR.
3564 This SoLSA Support Indicator shall be stored by the HLR per VLR where there are Subscribers roaming. If a 3565 Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a VLR and no SoLSA Support 3566 indicator is stored for that VLR, the location status of that Subscriber shall be set to Restricted. 3567 IST Support Indicator 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578
This parameter is used to indicate to the HLR that the VMSC supports basic IST functionality, that is, the VMSC is able to terminate the Subscriber Call Activity that originated the IST Alert when it receives the IST alert response indicating that the call(s) shall be terminated. If this parameter is not included in the Update Location indication and the Subscriber is marked as an IST Subscriber, then the HLR may limit the service for the subscriber (by inducing an Operator Determined barring of Roaming, Incoming or Outgoing calls), or allow service assuming the associated risk of not having the basic IST mechanism available. This parameter can also indicate that the VMSC supports the IST Command service, including the ability to terminate all calls being carried for the identified subscriber by using the IMSI as a key. If this additional capability is not included in the Update Location indication and the HLR supports the IST Command capability, then the HLR may limit the service for the subscriber (by inducing an Operator Determined barring of Roaming, Incoming or Outgoing calls), or allow service assuming the associated risk of not having the IST Command mechanism available.
3579 Long FTN Supported 3580 This parameter indicates that the VLR supports Long Forwarded-to Numbers. 3581 Super-Charger Supported in Serving Network Entity 3582 This parameter is used by the VLR to indicate to the HLR that the VLR supports the Super-Charger functionality and 3583 whether subscription data has been retained by the VLR. If subscription data has been retained by the VLR the age 3584 indicator shall be included. Otherwise the VLR shall indicate that subscriber data is required. 3585 If this parameter is absent then the VLR does not support the Super-Charger functionality.
402
3586 Supported LCS Capability Sets 3587 This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no 3588 capability set is marked as supported then the VLR does not support LCS at all. 3589 If this parameter is absent then the VLR may support at most LCS capability set 1, that is LCS Release98 or Release99 3590 version. 3591 Inform Previous Network Entity
403 Release 4 404 405
102
3GPP TS 29.002 V4.17.0 (2006-06)
3592 3593 3594 3595
This parameter is used by the VLR to ask the HLR to inform the previous network entity about the update by sending the previous network entity a Cancel Location message. It is used in case Super-Charger is supported in the network and the serving network entity has not been able to inform the previous network entity that MS has moved, that is if it has not sent Send Identification to the previous serving entity.
3596 User error 3597 In case of unsuccessful updating, an error cause shall be returned by the HLR. The following error causes defined in 3598 clause 7.6.1 may be used, depending on the nature of the fault: 3599 3600 3601 3602 3603 3604 3605 3606
unknown subscriber; roaming not allowed; This cause will be sent if the MS is not allowed to roam into the PLMN indicated by the VLR number. The cause is qualified by the roaming restriction reason "PLMN Not Allowed" or "Operator Determined Barring". If no qualification is received (HLR with MAP Version 1), "PLMN Not Allowed" is taken as default.
system failure; unexpected data value.
3607 Provider error 3608 For definition of provider errors see clause 7.6.1.
3609 3610 8.1.3.1
8.1.3 MAP_CANCEL_LOCATION service
Definition
3611 This service is used between HLR and VLR to delete a subscriber record from the VLR. It may be invoked 3612 automatically when an MS moves from one VLR area to another, to remove the subscriber record from the old VLR, or 3613 by the HLR operator to enforce a location updating from the VLR to the HLR, e.g. on withdrawal of a subscription. 3614 Also this service is used between HLR and SGSN to delete a subscriber record from the SGSN. It may be invoked 3615 automatically when an MS moves from one SGSN area to another, to remove the subscriber record from the old SGSN, 3616 or by the HLR operator to enforce a location updating from the SGSN to the HLR. 3617 The MAP_CANCEL_LOCATION service is a confirmed service using the primitives defined in table 8.1/3.
3618 8.1.3.2
3619
Service primitives
Table 8.1/3: MAP_CANCEL_LOCATION
Parameter name Invoke Id IMSI LMSI Cancellation Type User error Provider error
Request M M C C
Indication M(=) M(=) C(=) C(=)
Response M(=)
Confirm M(=)
C(=) O
3620
406
3621 8.1.3.3
407 Release 4 408 409
103
3GPP TS 29.002 V4.17.0 (2006-06)
Parameter definitions and use
3622 Invoke Id 3623 See definition in clause 7.6.1. 3624 IMSI 3625 See definition in clause 7.6.2. 3626 LMSI 3627 See definition in clause 7.6.2. The LMSI shall be included if it has been received from VLR. LMSI is not applicable 3628 between SGSN and HLR. 3629 Value 0000 0000 can be used to indicate that the LMSI is not in use. 3630 Cancellation Type 3631 See definition in clause 7.6.3. The presence of this parameter is mandatory when the Cancel Location is sent to the 3632 SGSN. If the VLR receives this parameter and do not understand it the VLR shall ignore it. 3633 User error 3634 If the cancellation fails, an error cause is to be returned by the VLR or by the SGSN. One of the following error causes 3635 defined in clause 7.6.1 shall be used: 3636 3637
unexpected data value; data missing.
3638 Provider error 3639 For definition of provider errors see clause 7.6.1.
3640 3641 8.1.4.1
8.1.4 MAP_SEND_IDENTIFICATION service
Definition
3642 The MAP_SEND_IDENTIFICATION service is used between a VLR and a previous VLR to retrieve IMSI and 3643 authentication data for a subscriber registering afresh in that VLR. 3644 The MAP_SEND_IDENTIFICATION service is a confirmed service using the service primitives defined in table 8.1/4.
3645 8.1.4.2
3646
Service primitives
Table 8.1/4: MAP_SEND_IDENTIFICATION
Parameter name Invoke Id TMSI Number of requested vectors Segmentation prohibited indicator IMSI Authentication set Current Security Context User error Provider error
Request M M M C
Indication M(=) M(=) M(=) C (=)
Response M(=)
Confirm M(=)
C U U C
C(=) C(=) C(=) C(=) O
3647
3648 8.1.4.3
3649 Invoke Id
Parameter definitions and use
410
3650 See definition in clause 7.6.1. 3651 TMSI 3652 See definition in clause 7.6.2. 3653 If multiple service requests are present in a dialogue then this parameter shall be present in every service request. 3654 Number of requested vectors 3655 A number indicating how many authentication vectors the new VLR is prepared to receive. The previous VLR shall not 3656 return more vectors than indicated by this parameter. 3657 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 3658 dialogue then this parameter shall not be present in any service request other than the first one 3659 Segmentation prohibited indicator 3660 This parameter indicates if the new VLR or SGSN allows segmentation of the response at MAP user level. 3661 This parameter may be present only in the first request of the dialogue. 3662 IMSI 3663 See definition in clause 7.6.2. The IMSI is to be returned if the service succeeds. 3664 If multiple service requests are present in a dialogue and the service succeeds then this parameter shall not be present in 3665 any service response other than the first one. 3666 Authentication set 3667 See definition in clause 7.6.7. If the service succeeds a list of up to five authentication sets is returned, if there are any 3668 available. 3669 Current Security Context 3670 See definition in clause 7.6.7. If the service succeeds, a list of either GSM or UMTS Security Context parameters can be 3671 returned. 3672 User error 3673 This parameter is mandatory if the service fails. The following error cause defined in clause 7.6.1 may be used, 3674 depending on the nature of the fault: 3675
411 Release 4 412 413
104
3GPP TS 29.002 V4.17.0 (2006-06)
unidentified subscriber.
3676 Provider error 3677 For definition of provider errors see clause 7.6.1.
3678 3679 8.1.5.1 3680 8.1.5.2 3681 8.1.5.3 3682 3683 8.1.6.1
8.1.5 Void
Void Void Void
8.1.6 MAP_PURGE_MS service
Definition
414
3684 3685 3686 3687 3688 3689 3690 3691 3692 3693
415 Release 4 416 417
105
3GPP TS 29.002 V4.17.0 (2006-06)
This service is used between the VLR and the HLR to cause the HLR to mark its data for an MS so that any request for routing information for a mobile terminated call or a mobile terminated short message will be treated as if the MS is not reachable. It is invoked when the subscriber record for the MS is to be deleted in the VLR, either by MMI interaction or automatically, e.g. because the MS has been inactive for several days. This service shall not be used if both the VLR and HLR support the Super-Charger functionality. Also this service is used between the SGSN and the HLR to cause the HLR to mark its data for an MS so that any request for routing information for a mobile terminated short message or a network requested PDP-context activation will be treated as if the MS is not reachable. It is invoked when the subscriber record for the MS is to be deleted in the SGSN, either by MMI interaction or automatically, e.g. because the MS has been inactive for several days. This service shall not be used if both the SGSN and HLR support the Super-Charger functionality.
3694 The MAP_PURGE_MS service is a confirmed service using the primitives defined in table 8.1/6.
3695 8.1.6.2
3696
Service primitives
Table 8.1/6: MAP_PURGE_MS
Parameter name Invoke Id IMSI VLR number Freeze TMSI Freeze P-TMSI SGSN number User error Provider error
Request M M C C
Indication M(=) M(=) C(=) C(=)
Response M(=) C C C
Confirm M(=) C(=) C(=) C(=) O
3697
3698 8.1.6.3
3699 Invoke ID
Parameter definitions and use
3700 See definition in clause 7.6.1. 3701 IMSI 3702 See definition in clause 7.6.2. 3703 VLR number 3704 Shall be present if the sender is VLR. See definition in clause 7.6.2. 3705 SGSN number 3706 Shall be present if the sender is SGSN. See definition in clause 7.6.2. 3707 Freeze TMSI 3708 This parameter is sent to the VLR to indicate that the TMSI has to be frozen. It shall be present if the received VLR 3709 number matches the stored VLR number. 3710 Freeze P-TMSI 3711 This parameter is sent to the SGSN to indicate that the P-TMSI has to be frozen. It shall be present if the received 3712 SGSN number matches the stored SGSN number. 3713 User error 3714 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 3715 3716
Data Missing; Unexpected Data Value;
418
3717
419 Release 4 420 421
106
3GPP TS 29.002 V4.17.0 (2006-06)
Unknown Subscriber.
3718 Provider error 3719 See definition of provider errors in clause 7.6.1.
3720 3721 8.1.7.1
8.1.7 MAP_UPDATE_GPRS_LOCATION service
Definition
3722 This service is used by the SGSN to update the location information stored in the HLR. 3723 The MAP_UPDATE_GPRS_LOCATION service is a confirmed service using the service primitives given in 3724 table 8.1/7.
3725 8.1.7.2
3726
Service primitives
Table 8.1/7: MAP_UPDATE_GPRS_LOCATION
Parameter name Invoke Id IMSI SGSN number SGSN address Supported CAMEL Phases SoLSA Support Indicator Super-Charger Supported in Serving Network Entity GPRS enhancements support indicator Supported LCS Capability Sets Inform Previous Network Entity HLR number User error Provider error
Request M M M M C C C C C C
Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=)
Response M(=)
Confirm M(=)
C C
C(=) C(=) O
3727
3728 8.1.7.3
3729 Invoke Id
Parameter definitions and use
3730 See definition in clause 7.6.1. 3731 IMSI 3732 See definition in clause 7.6.2. 3733 SGSN number 3734 See definition in clause 7.6.2. 3735 SGSN address 3736 See definition in clause 7.6.2. 3737 Supported CAMEL Phases 3738 This parameter indicates which phases of CAMEL are supported. The SGSN can only support CAMEL phase 3 or 3739 greater. 3740 SoLSA Support Indicator 3741 This parameter is used by the SGSN to indicate to the HLR in the Update GPRS Location indication that SoLSA is 3742 supported. If this parameter is not included in the Update GPRS Location indication and the Subscriber is marked as
422
3743 only allowed to roam in Subscribed LSAs, then the HLR shall reject the roaming and indicate to the SGSN that roaming 3744 is not allowed to that Subscriber in the SGSN. 3745 This SoLSA Support Indicator shall be stored by the HLR per SGSN where there are Subscribers roaming. If a 3746 Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a SGSN and no SoLSA Support 3747 indicator is stored for that SGSN, the location status of that Subscriber has to be set to Restricted. 3748 Super-Charger Supported in Serving Network Entity 3749 This parameter is used by the SGSN to indicate to the HLR that the SGSN supports the Super-Charger functionality and 3750 whether subscription data has been retained by the SGSN. If subscription data has been retained by the SGSN the age 3751 indicator shall be included. Otherwise the SGSN shall indicate that subscriber data is required. 3752 If this parameter is absent then the SGSN does not support the Super-Charger functionality. 3753 GPRS enhancements support indicator 3754 This parameter is used by the SGSN to indicate to the HLR in the Update GPRS Location indication that GPRS 3755 enhancements are supported. If this parameter is included in the Update GPRS Location indication the HLR may send 3756 the extensible QoS in the PDP contexts to the SGSN. 3757 HLR number 3758 See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful HLR updating. 3759 Supported LCS Capability Sets 3760 This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no 3761 capability set is marked as supported then the SGSN does not support LCS at all. 3762 The SGSN is not allowed to indicate support for LCS capability set 1. 3763 If this parameter is absent then the SGSN does not support LCS at all. 3764 Inform Previous Network Entity
423 Release 4 424 425
107
3GPP TS 29.002 V4.17.0 (2006-06)
3765 3766 3767 3768
This parameter is used by the SGSN to ask the HLR to inform the previous network entity about the update by sending the previous network entity a Cancel Location message. It is used in case Super-Charger is supported in the network and the serving network entity has not been able to inform the previous network entity that MS has moved, that is if it has not sent SGSN Context Request to the previous serving entity.
3769 User error 3770 In case of unsuccessful updating, an error cause shall be returned by the HLR. The following error causes defined in 3771 clause 7.6.1 may be used, depending on the nature of the fault: 3772 3773 3774 3775 3776 3777 3778 3779
unknown subscriber; roaming not allowed. This cause will be sent if the MS is not allowed to roam into the PLMN indicated by the SGSN number. The cause is qualified by the roaming restriction reason "PLMN Not Allowed" or "Operator Determined Barring".
system failure; unexpected data value.
The diagnostic in the Unknown Subscriber may indicate Imsi Unknown or Gprs Subscription Unknown.
3780 Provider error 3781 For definition of provider errors see clause 7.6.1.
3782
8.1.8 MAP-NOTE-MM-EVENT
426
3783 8.1.8.1
427 Release 4 428 429
108
3GPP TS 29.002 V4.17.0 (2006-06)
Definition
3784 This service is used between the VLR and the gsmSCF when for a subscriber a mobility management event has been 3785 processed successfully, that subscriber is provisioned with M-CSI and the relevant mobility management event is 3786 marked for reporting.
3787 8.1.8.2
Service primitives
3788 The service primitives are shown in table 8.1/8. 3789
Table 8.1/8: MAP_NOTE_MM_EVENT parameters
Parameter name Invoke id Event Met Service Key IMSI Basic MSISDN Location Information LSA Identity Supported CAMEL Phases User error Provider error Request M M M M M C C M Indication M(=) M(=) M(=) M(=) M(=) C(=) C(=) M(=) Response M(=) Confirm M(=)
C(=) O
3790
3791 8.1.8.3
Parameter use
3792 Event Met 3793 This parameter indicates the mobility management event that has lead to the notification. It shall have one of the 3794 following values: 3795 3796 3797 3798 3799
Location update in the same VLR service area; Location update to another VLR service area; IMSI attach; MS initiated IMSI detach (explicit detach); Network initiated IMSI detach (implicit detach).
3800 Service Key 3801 See clause 7.6.x. 3802 IMSI 3803 See clause 7.6.x. 3804 Basic MSISDN 3805 See clause 7.6.x. 3806 Location Information 3807 See clause 7.6.x. This information shall be sent, if available. 3808 LSA Identity 3809 See clause 7.6.x. This information shall be sent, if available. 3810 Supported CAMEL Phases 3811 See clause 7.6.x. This information shall always be sent.
430
3812 User error
431 Release 4 432 433
109
3GPP TS 29.002 V4.17.0 (2006-06)
3813 This parameter is sent by the receiving entity when an error is detected. It shall have one of the following values: 3814 3815 3816 3817
Data Missing; Unexpected Data Value; Unknown Subscriber; MM-EventNotSupported.
3818 Provider error 3819 This is defined in clause 7.6.1.
3820 3821 3822 8.2.1.1
8.2 Paging and search
8.2.1 MAP_PAGE service
Definition
3823 This service is used between VLR and MSC to initiate paging of an MS for mobile terminated call set-up, mobile 3824 terminated short message or unstructured SS notification. 3825 The MAP_PAGE service is a confirmed service using the primitives from table 8.2/1.
3826 8.2.1.2
3827
Service primitives
Table 8.2/1: MAP_PAGE
Parameter name Invoke Id IMSI Stored location area Id TMSI User error Provider error Request M M M U Indication M(=) M(=) M(=) C(=) Response M(=) Confirm M(=)
C(=) O
3828
3829 8.2.1.3
3830 Invoke Id
Parameter definitions and use
3831 See definition in clause 7.6.1. 3832 IMSI 3833 See definition in clause 7.6.2. The IMSI is used to define the paging subgroup. If the TMSI is not supplied, paging on 3834 the radio path uses the IMSI as an identifier. 3835 Stored location area Id 3836 See definition in clause 7.6.2. 3837 TMSI 3838 See definition in clause 7.6.2. The TMSI is included if paging on the radio channel is to use the TMSI as an identifier. 3839 User error 3840 The following error causes defined in clause 7.6.1 may be sent by the user in case of a paging error, depending on the 3841 failure reason:
434
3842 3843 3844 3845 3846 3847 3848
435 Release 4 436 437
110
3GPP TS 29.002 V4.17.0 (2006-06)
absent subscriber; unknown location area; busy subscriber; system failure; this corresponds to the case where there is no call associated with the MAP_PAGE service, i.e. if the call has been released but the dialogue to the VLR has not been aborted; unexpected data value.
3849 Provider error 3850 See definition in clause 7.6.1.
3851 3852 8.2.2.1
8.2.2 MAP_SEARCH_FOR_MS service
Definition
3853 This service is used between VLR and MSC to initiate paging of an MS in all location areas of that VLR. It is used if 3854 the VLR does not hold location area information confirmed by radio contact. 3855 The MAP_SEARCH_FOR_MS service is a confirmed service using the primitives from table 8.2/2.
3856 8.2.2.2
3857
Service primitives
Table 8.2/2: MAP_SEARCH_FOR_MS
Parameter name Invoke Id IMSI Current location area Id User error Provider error Request M M Indication M(=) M(=) Response M(=) C C Confirm M(=) C(=) C(=) O
3858
3859 8.2.2.3
3860 Invoke Id
Parameter definitions and use
3861 See definition in clause 7.6.1. 3862 IMSI 3863 See definition in clause 7.6.2. The IMSI is used to identify the subscriber when paging on the radio path. 3864 Current location area Id 3865 See definition in clause 7.6.2. In case of successful outcome of the service, i.e. if the MS responds to paging, the 3866 Location Area Id of the area in which the MS responded is given in the response. 3867 User error 3868 The following error causes defined in clause 7.6.1 shall be sent by the user if the search procedure fails, depending on 3869 the failure reason: 3870 3871 3872
absent subscriber; this error cause is returned by the MSC if the MS does not respond to the paging request;
system failure;
438
3873 3874 3875 3876
439 Release 4 440 441
111
3GPP TS 29.002 V4.17.0 (2006-06)
this corresponds to the case where there is no call associated with the MAP_SEARCH_FOR_MS service, i.e. if the call has been released but the dialogue to the VLR has not been aborted; busy subscriber; unexpected data value.
3877 Provider error 3878 See definition in clause 7.6.1.
3879 3880 3881 8.3.1.1
8.3 Access management services
8.3.1 MAP_PROCESS_ACCESS_REQUEST service
Definition
3882 This service is used between MSC and VLR to initiate processing of an MS access to the network, e.g. in case of 3883 mobile originated call set-up or after being paged by the network. 3884 The MAP_PROCESS_ACCESS_REQUEST service is a confirmed service using the primitives from table 8.3/1.
3885 8.3.1.2
3886
Service primitives
Table 8.3/1: MAP_PROCESS_ACCESS_REQUEST
Parameter name Invoke Id CM service type Access connection status Current Location Area Id Serving cell Id TMSI Cksn IMSI IMEI MSISDN User error Provider error Request M M M M M C C C C Indication M(=) M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)
C C U C
C(=) C(=) C(=) C(=) O
3887
3888 8.3.1.3
3889 Invoke Id
Parameter definitions and use
3890 See definition in clause 7.6.1. 3891 CM service type 3892 See definition in clause 7.6.9. 3893 Access connection status 3894 See definition in clause 7.6.9. 3895 Current Location Area Id 3896 See definition in clause 7.6.2. This parameter is used to update the VLR in case of previous VLR failure. 3897 Serving cell Id 3898 See definition in clause 7.6.2.
442
3899 TMSI
443 Release 4 444 445
112
3GPP TS 29.002 V4.17.0 (2006-06)
3900 See definition in clause 7.6.2. Either TMSI or IMSI as received from the MS are included in the Request/Indication, but 3901 one shall be present. In case of CM Service Type "Emergency Call Establishment", the IMEI may replace IMSI/TMSI. 3902 Cksn 3903 See definition in clause 7.6.7. In case of access with TMSI, the Cksn shall be present. 3904 IMSI 3905 See definition in clause 7.6.2. Either TMSI or IMSI as received from the MS are included in the Request/Indication, but 3906 one shall be present. In case of CM Service Type "Emergency Call Establishment", the IMEI may replace IMSI/TMSI. 3907 In the Response/Confirmation, the IMSI is to be sent in case of successful outcome of the service. In case of CM 3908 Service Type "Emergency Call Establishment", IMEI may replace IMSI. 3909 IMEI 3910 See definition in clause 7.6.2. The IMEI may replace IMSI/TMSI in the Request/Indication and IMSI in the 3911 Response/Confirmation only in case the CM Service Type indicates "Emergency Call Establishment". 3912 MSISDN 3913 See definition in clause 7.6.2. The MSISDN is included in case of successful outcome of the service as an operator 3914 option, e.g. if it is needed at the MSC for charging purposes in case of call forwarding. 3915 User error 3916 One of the following error causes defined in clause 7.6.1 shall be sent by the user if the access request fails, depending 3917 on the failure reason: 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928 3929
unidentified subscriber; illegal subscriber; this error is sent if a correlated authentication procedure has not authenticated the subscriber;
illegal equipment; this error is sent if an IMEI check failed, i.e. the IMEI is blacklisted or not white-listed;
roaming not allowed; this cause is used after VLR restart if the subscriber has no subscription for the current location area, e.g. due to regional subscription. The cause will be qualified by "location area not allowed" or "national roaming not allowed", respectively; unknown location area; system failure; unexpected data value.
3930 Provider error 3931 For definition of provider errors see clause 7.6.1.
3932
8.4 Handover services
3933 It should be noted that the handover services used on the B-interface have not been updated for Release 99. The B3934 interface is not fully operational specified. It is strongly recommended not to implement the B-interface as an external 3935 interface.
3936
8.4.1 MAP_PREPARE_HANDOVER service
446
3937 8.4.1.1
447 Release 4 448 449
113
3GPP TS 29.002 V4.17.0 (2006-06)
Definition
3938 This service is used between MSC-A and MSC-B (E-interface) when a call is to be handed over or relocated from 3939 MSC-A to MSC-B. 3940 The MAP_PREPARE_HANDOVER service is a confirmed service using the primitives from table 8.4/1.
3941 8.4.1.2
3942
Service primitives
Table 8.4/1: MAP_PREPARE_HANDOVER
Parameter name Invoke Id Target Cell Id Target RNC Id HO-NumberNotRequired IMSI Integrity Protection Information Encryption Information Radio Resource Information AN-APDU Allowed GSM Algorithms Allowed UMTS Algorithms Radio Resource List RAB ID BSSMAP Service Handover BSSMAP Service Handover List RANAP Service Handover ASCI Call Reference Handover Number Relocation Number List Multicall Bearer Information Multiple Bearer Requested Multiple Bearer Not Supported Selected UMTS Algorithms Chosen Radio Resource Information User error Provider error Request M C C C C C C C C C C C C C C C C Indication M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C C C C C(=) C C C C C(=) C(=) C(=) C(=) O C(=) C(=) C(=) Response M(=) Confirm M(=)
C(=)
3943
3944 8.4.1.3
3945 Invoke Id
Parameter use
3946 For definition of this parameter see clause 7.6.1. 3947 Target Cell Id 3948 For definition of this parameter see clause 7.6.2. This parameter is only included if the service is not in an ongoing 3949 transaction. This parameter shall also be excluded if the service is a part of the Inter-MSC SRNS Relocation procedure 3950 or the inter-system handover GSM to UMTS procedure described in 3GPP TS 23.009. 3951 Target RNC Id 3952 For definition of this parameter see clause 7.6.2. This parameter shall be included if the service is a part of the Inter3953 MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS 3954 23.009. 3955 HO-Number Not Required 3956 For definition of this parameter see clause 7.6.6.
450
3957 IMSI
451 Release 4 452 453
114
3GPP TS 29.002 V4.17.0 (2006-06)
3958 For definition of this parameter see clause 7.6.2. This UMTS parameter shall be included if:
3959 3960 3961
available and if the access network protocol is BSSAP and there is an indication that the MS also supports UMTS.
3962 Integrity Protection Information 3963 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the access 3964 network protocol is BSSAP. 3965 Encryption Information 3966 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the access 3967 network protocol is BSSAP. 3968 Radio Resource Information 3969 For definition of this parameter see clause 7.6.6. This GSM parameter shall be included if the access network protocol 3970 is RANAP and there is an indication that the UE also supports GSM. If the parameter Radio Resource List is sent , the 3971 parameter Radio Resource Information shall not be sent. 3972 AN-APDU 3973 For definition of this parameter see clause 7.6.9. 3974 Allowed GSM Algorithms 3975 For definition of this parameter see clause 7.6.6. This parameters includes allowed GSM algorithms. This GSM 3976 parameter shall be included if:
3977 3978 3979
the service is a part of the Inter-MSC SRNS Relocation procedure and Ciphering or Security Mode Setting procedure has been performed.and there is an indication that the UE also supports GSM.
3980 Allowed UMTS Algorithms 3981 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if all of the following 3982 conditions apply:
3983 3984
access network protocol is BSSAP and Integrity Protection Information and Encryption Information are not available and
3985 Ciphering or Security Mode Setting procedure has been performed. 3986 Radio Resource List 3987 3988 3989 3990
For definition of this parameter see clause 7.6.6. This parameter shall be included if the access network protocol is RANAP and there is an indication that the UE also supports GSM. This parameter shall be sent when MSC-A requests multiple bearers to MSC-B. If the parameter Radio Resource Information is sent , the parameter Radio Resource List shall not be sent.
3991 RAB ID 3992 For definition of this parameter see subclause 7.6.2. This parameter shall be included when MSC-A supports multiple 3993 bearers and access network protocol is BSSAP and the RAB ID has a value other than 1. 3994 BSSMAP Service Handover
454
3995 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is 3996 RANAP. If the parameter BSSMAP Service Handover List is sent, the parameter BSSMAP Service Handover shall not 3997 be sent. 3998 BSSMAP Service Handover List 3999 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is 4000 RANAP. This parameter shall be sent when MSC-A requests multiple bearers to MSC-B. If the parameter BSSMAP 4001 Service Handover is sent, the parameter BSSMAP Service Handover List shall not be sent. 4002 RANAP Service Handover 4003 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the access network protocol is 4004 BSSAP. 4005 ASCI Call Reference 4006 This parameter contains either the broadcast call reference or group call reference. It shall be included if a subscriber is 4007 undergoing handover during a VGCS or VBS call, where MSC-B already has a Bearer established, so that MSC-B can 4008 determine the Group or Broadcast Call to which it shall attach the subscriber, see 3GPP TS 48.008 [49]. 4009 4010 Handover Number 4011 For definition of this parameter see clause 7.6.2. This parameter shall be returned at handover, unless the parameter 4012 HO-NumberNotRequired is sent. If the parameter Handover Number is returned, the parameter Relocation Number List 4013 shall not be returned. 4014 Relocation Number List 4015 For definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation, unless the parameter 4016 HO-NumberNotRequired is sent. If the parameter Relocation Number List is returned, the parameter Handover Number 4017 shall not be returned. 4018 Multicall Bearer Information 4019 For a definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation in the case that MSC-B 4020 supports multiple bearers. 4021 4022 Multiple Bearer Requested 4023 For a definition of this parameter see clause 7.6.2. This parameter shall be sent when MSC-A requests multiple bearers 4024 to MSC-B. 4025 Multiple Bearer Not Supported 4026 For a definition of this parameter see clause 7.6.2. This parameter shall be returned at relocation when MSC-B receives 4027 Multiple Bearer Requested parameter and MSC-B does not support multiple bearers. 4028 Selected UMTS Algorithms 4029 For definition of this parameter see clause 7.6.6. This parameters includes the UMTS integrity and optionally 4030 encryption algorithms selected by RNC under the control of MSC-B. This UMTS parameter shall be included if the 4031 service is a part of the inter MSC inter system handover from GSM to UMTS. 4032 Chosen Radio Resource Information 4033 For definition of this parameter see clause 7.6.6. This parameter shall be returned at relocation if the encapsulated PDU 4034 is RANAP RAB Assignment Response and MS is in GSM access.
455 Release 4 456 457
115
3GPP TS 29.002 V4.17.0 (2006-06)
458
4035 User error
459 Release 4 460 461
116
3GPP TS 29.002 V4.17.0 (2006-06)
4036 For definition of this parameter see clause 7.6.1. The following errors defined in clause 7.6.1 may be used, depending 4037 on the nature of the fault: 4038 4039 4040 4041 4042
No handover number available. Target cell outside group call area; System failure. Unexpected data value. Data Missing.
4043 Provider error 4044 See definition of provider errors in clause 7.6.1.
4045 4046 8.4.2.1
8.4.2 MAP_SEND_END_SIGNAL service
Definition
4047 This service is used between MSC-B and MSC-A (E-interface) indicating that the radio path has been established by 4048 MSC-B to the MS. MSC-A retains then the main control of the call until it clears. 4049 The response is used by MSC-A to inform MSC-B that all resources for the call can be released in MSC-B, either 4050 because the call has been released in MSC-A or because the call has been successfully handed over or relocated from 4051 MSC-B to another MSC. 4052 The MAP_SEND_END_SIGNAL service is a confirmed service using the primitives from table 8.4/2.
4053 8.4.2.2
4054
Service primitives
Table 8.4/2: MAP_SEND_END_SIGNAL
Parameter name Invoke Id AN-APDU Provider error Request M M Indication M(=) M(=) Response M(=) Confirm M(=) O
4055
4056 8.4.2.3
4057 Invoke Id
Parameter use
4058 For definition of this parameter see clause 7.6.1. 4059 AN-APDU 4060 For definition of this parameter see clause 7.6.9. 4061 Provider error 4062 For definition of this parameter see clause 7.6.1.
4063 4064 8.4.3.1
8.4.3 MAP_PROCESS_ACCESS_SIGNALLING service
Definition
4065 This service is used between MSC-B and MSC-A (E-interface) to pass information received on the A-interface or Iu4066 interface in MSC-B to MSC-A.
462
4067 The MAP_PROCESS_ACCESS_SIGNALLING service is a non-confirmed service using the primitives from 4068 table 8.4/3.
463 Release 4 464 465
117
3GPP TS 29.002 V4.17.0 (2006-06)
4069 8.4.3.2
4070
Service primitives
Table 8.4/3: MAP_PROCESS_ACCESS_SIGNALLING
Parameter name Invoke Id AN-APDU Selected GSM Algorithm Selected UMTS Algorithms Chosen Radio Resource Information Selected RAB id Request M M C C C C Indication M(=) M(=) C(=) C(=) C(=) C(=)
4071
4072 8.4.3.3
4073 Invoke Id
Parameter use
4074 For definition of this parameter see clause 7.6.1. 4075 AN-APDU 4076 For definition of this parameter see clause 7.6.9. 4077 Selected GSM algorithm 4078 For definition of this parameter see clause 7.6.6. This parameter shall be present if the encapsulated PDU is Security 4079 Mode Complete and MS is in GSM access. 4080 Selected UMTS Algorithms 4081 4082 4083 4084
For definition of this parameter see clause 7.6.6. This parameters includes the UMTS integrity and optionally encryption algorithms selected by RNC under the control of MSC-B. This UMTS parameter shall be included if the encapsulated PDU is BSSMAP Cipher Mode Complete and the MS is in UMTS, or an interystem handover to UMTS is performed in MSC-B, or in the case of intra MSC-B intra UMTS relocation.
4085 Chosen Radio Resource Information 4086 For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB 4087 Assignment Response and MS is in GSM access. 4088 Selected RAB ID 4089 The selected radio access bearer that was kept at subsequent intra-MSC handover from UMTS to GSM after multiple 4090 bearers were used.
4091 4092 8.4.4.1
8.4.4 MAP_FORWARD_ACCESS_SIGNALLING service
Definition
4093 This service is used between MSC-A and MSC-B (E-interface) to pass information to be forwarded to the A-interface 4094 or Iu-interface of MSC-B. 4095 The MAP_FORWARD_ACCESS_SIGNALLING service is a non-confirmed service using the primitives from 4096 table 8.4/4.
4097 8.4.4.2
4098
Service primitives
Table 8.4/4: MAP_FORWARD_ACCESS_SIGNALLING
466
467 Release 4 468 469
118 Parameter name Invoke Id Integrity Protection Information Encryption Information Key Status AN-APDU Allowed GSM Algorithms Allowed UMTS Algorithms Radio Resource Information Radio Resource List BSSMAP Service Handover BSSMAP Service Handover List RANAP Service Handover Request M C C C M C C C C C C C
3GPP TS 29.002 V4.17.0 (2006-06) Indication M(=) C(=) C(=) C(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=)
4099
4100 8.4.4.3
4102 Invoke Id
Parameter use
4101 For the definition and use of all parameters and errors, see clause 7.6.1.
4103 For definition of this parameter see clause 7.6.1. 4104 Integrity Protection Information 4105 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the 4106 encapsulated PDU is BSSMAP Cipher Mode Command. 4107 Encryption Information 4108 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the 4109 encapsulated PDU is BSSMAP Cipher Mode Command. 4110 Key Status 4111 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if available and if the 4112 encapsulated PDU is BSSMAP Cipher Mode Command. 4113 AN-APDU 4114 For definition of this parameter see clause 7.6.9. 4115 Allowed GSM Algorithms 4116 This parameters includes allowed GSM algorithms. This GSM parameter shall be included if the encapsulated PDU is 4117 RANAP Security Mode Command and there is an indication that the UE also supports GSM. 4118 Allowed UMTS Algorithms 4119 For definition of this parameter see clause 7.6.6. This UMTS parameter shall be included if Integrity Protection 4120 Information and Encryption Information are not available and the encapsulated PDU is BSSMAP Cipher Mode 4121 Command. 4122 Radio Resource Information 4123 For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB 4124 Assignment Request. If the parameter Radio Resource List is sent, the parameter Radio Resource Information shall not 4125 be sent. 4126 Radio Resource List 4127 For definition of this parameter see clause 7.6.6. This parameter shall be sent if the encapsulated PDU is RANAP RAB 4128 Assignment Request and MSC-A requests modification of multiple bearers. If the parameter Radio Resource 4129 Information is sent, the parameter Radio Resource List shall not be sent. 4130 BSSMAP Service Handover
470
4131 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the encapsulated PDU is 4132 RANAP RAB Assignment Request. If the parameter BSSMAP Service Handover List is sent, the parameter BSSMAP 4133 Service Handover shall not be sent. 4134 BSSMAP Service Handover List 4135 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the encapsulated PDU is 4136 RANAP RAB Assignment Request and MSC-A requests modification of multiple bearers. If the parameter BSSMAP 4137 Service Handover is sent, the parameter BSSMAP Service Handover List shall not be sent. 4138 RANAP Service Handover 4139 For definition of this parameter see clause 7.6.6. It shall be present if it is available and the encapsulated PDU is 4140 BSSMAP Assignment Request. 4141
471 Release 4 472 473
119
3GPP TS 29.002 V4.17.0 (2006-06)
4142 4143 8.4.5.1
8.4.5 MAP_PREPARE_SUBSEQUENT_HANDOVER service
Definition
4144 This service is used between MSC-B and MSC-A (E-interface) to inform MSC-A that it has been decided that a 4145 handover or relocation to either MSC-A or a third MSC (MSC-B') is required. 4146 The MAP_PREPARE_SUBSEQUENT_HANDOVER service is a confirmed service using the primitives from 4147 table 8.4/5.
4148 8.4.5.2
4149
Service primitives
Table 8.4/5: MAP_PREPARE_SUBSEQUENT_HANDOVER
Parameter name Invoke Id Target Cell Id Target RNC Id Target MSC Number Selected RAB ID AN-APDU User error Provider error Request M C C M C M Indication M(=) C(=) C(=) M(=) C(=) M(=) Response M(=) Confirm M(=)
C C
C(=) C(=) O
4150
4151 8.4.5.3
4152 Invoke Id
Parameter use
4153 For definition of this parameter see clause 7.6.1. 4154 Target Cell Id 4155 For definition of this parameter see clause 7.6.2. This parameter shall be excluded if the service is a part of the Inter4156 MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS 4157 23.009. 4158 Target RNC Id 4159 For definition of this parameter see clause 7.6.2. This parameter shall be included if the service is a part of the Inter4160 MSC SRNS Relocation procedure or the inter-system handover GSM to UMTS procedure described in 3GPP TS 4161 23.009. 4162 Target MSC Number 4163 For definition of this parameter see clause 7.6.2.
474
4164 Selected RAB ID 4165 For definition of this parameter see clause 7.6.2. 4166 AN-APDU 4167 For definition of this parameter see clause 7.6.9. 4168 User error 4169 For definition of this parameter see clause 7.6.1. The following error causes defined in clause 7.6.1 may be used, 4170 depending on the nature of the fault: 4171 4172 4173 4174
475 Release 4 476 477
120
3GPP TS 29.002 V4.17.0 (2006-06)
Unknown MSC; Subsequent handover failure; Unexpected data value; Data Missing.
4175 Provider error 4176 For definition of this parameter see clause 7.6.1.
4177 4178 8.4.6.1
8.4.6 MAP_ALLOCATE_HANDOVER_NUMBER service
Definition
4179 This service is used between MSC and VLR (B-interface) to request a handover number. 4180 The MAP_ALLOCATE_HANDOVER_NUMBER service is a confirmed service using the primitives from table 8.4/6.
4181 8.4.6.2
4182
Service primitives
Table 8.4/6: MAP_ALLOCATE_HANDOVER_NUMBER
Parameter name Invoke Id User error Provider error Request M Indication M(=) Response M(=) C Confirm M(=) C(=) O
4183
4184 8.4.6.3
4185 Invoke Id
Parameter use
4186 For definition of this parameter see clause 7.6.1. 4187 User error 4188 For definition of this parameter see clause 7.6.1. The following errors defined in clause 7.6.1 may be used, depending 4189 on the nature of the fault: 4190
No handover number available.
4191 Provider error 4192 For definition of this parameter see clause 7.6.1.
4193 4194 8.4.7.1
8.4.7 MAP_SEND_HANDOVER_REPORT service
Definition
478
4195 This service is used between VLR and MSC-B (B-interface) to transfer the handover number to be forwarded to and 4196 used by MSC-A. 4197 The MAP_SEND_HANDOVER_REPORT service is a confirmed service using the primitives from table 8.4/7.
479 Release 4 480 481
121
3GPP TS 29.002 V4.17.0 (2006-06)
4198 8.4.7.2
4199
Service primitives
Table 8.4/7: MAP_SEND_HANDOVER_REPORT
Parameter name Invoke Id Handover Number Linked Id Provider error
Request M M M
Indication M(=) M(=) M(=)
Response M(=)
Confirm M(=) O
4200
4201 8.4.7.3
4202 Invoke Id
Parameter use
4203 For definition of this parameter see clause 7.6.1. 4204 Handover Number 4205 For definition of this parameter see clause 7.6.2. 4206 Linked Id 4207 For definition of this parameter see clause 7.6.1. This service is linked with 4208 MAP_ALLOCATE_HANDOVER_NUMBER. 4209 Provider error 4210 For definition of this parameter see clause 7.6.1.
4211 4212
8.5 Authentication management services
8.5.1 MAP_AUTHENTICATE service
4213 The MAP_AUTHENTICATE service is used on the MAP B interface. This interface is not fully operational specified. 4214 It is strongly recommended not to implement the B-interface as an external interface.
4215 8.5.1.1
Definition
4216 This service is used between the VLR and the MSC when the VLR receives a MAP service indication from the MSC 4217 concerning a location registration, call set-up, operation on a supplementary service or a request from the MSC to 4218 initiate authentication. 4219 The service is a confirmed service and consists of four service primitives.
4220 8.5.1.2
Service primitives
4221 The service primitives are shown in table 8.5/1. 4222
Parameter name Invoke id RAND CKSN SRES
Table 8.5/1: MAP_AUTHENTICATE parameters
Request M M M Indication M(=) M(=) M(=) Response M(=) Confirm M(=)
M(=)
482
483 Release 4 484 485 Provider error
122
3GPP TS 29.002 V4.17.0 (2006-06) O
4223
4224 8.5.1.3
4225 Invoke id
Parameter use
4226 See clause 7.6.1 for the use of this parameter. 4227 RAND 4228 See clause 7.6.7 for the use of this parameter. 4229 CKSN 4230 See clause 7.6.7 for the use of this parameter. 4231 SRES 4232 See clause 7.6.7 for the use of this parameter. 4233 Provider error 4234 See clause 7.6.1 for the use of this parameter.
4235 4236 8.5.2.1
8.5.2 MAP_SEND_AUTHENTICATION_INFO service
Definition
4237 This service is used between the VLR and the HLR for the VLR to retrieve authentication information from the HLR. 4238 The VLR requests up to five authentication vectors. 4239 Also this service is used between the SGSN and the HLR for the SGSN to retrieve authentication information from the 4240 HLR. The SGSN requests up to five authentication vectors. 4241 If the user is a UMTS subscriber, the HLR shall return authentication quintuplets. If the user is a GSM subscriber, the 4242 HLR shall return authentication triplets. 4243 If the HLR cannot provide the VLR or the SGSN with triplets, an empty response is returned. The VLR or the SGSN 4244 may then re-use old authentication triplets, except where this is forbidden under the conditions specified in 3GPP TS 4245 43.020 [24]. 4246 If the HLR cannot provide the VLR or the SGSN with quintuplets, an empty response is returned. The VLR or the 4247 SGSN shall not re-use old authentication quintuplets. 4248 If the VLR or SGSN receives a MAP_SEND_AUTHENTICATION_INFO response containing a User Error parameter 4249 as part of the handling of an authentication procedure, the authentication procedure in the VLR or SGSN shall fail. 4250 Security related network functions are further described in 3GPP TS 43.020 [24] and 3GPP TS 33.200. 4251 The service is a confirmed service and consists of four service primitives.
4252 8.5.2.2
Service primitives
4253 The service primitives are shown in table 8.5/2. 4254
Table 8.5/2: MAP_SEND_AUTHENTICATION_INFO parameters
Parameter name Invoke id IMSI Number of requested vectors Requesting node type Re-synchronisation Info Request M C C C C Indication M(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)
486
487 Release 4 488 489 Segmentation prohibited indicator Immediate response preferred indicator AuthenticationSetList User error Provider error
123 C U C (=) C (=)
3GPP TS 29.002 V4.17.0 (2006-06)
C C
C(=) C(=) O
4255
4256 8.5.2.3
4257 Invoke id
Parameter use
4258 See clause 7.6.1 for the use of this parameter. 4259 IMSI 4260 See clause 7.6.2 for the use of this parameter. 4261 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 4262 dialogue then this parameter shall not be present in any service request other than the first one. 4263 Number of requested vectors 4264 A number indicating how many authentication vectors the VLR or SGSN is prepared to receive. The HLR shall not 4265 return more vectors than indicated by this parameter. 4266 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 4267 dialogue then this parameter shall not be present in any service request other than the first one. 4268 Requesting node type 4269 The type of the requesting node (SGSN or VLR). 4270 This parameter shall be present in the first (or only) request of the dialogue. If multiple service requests are present in a 4271 dialogue then this parameter shall not be present in any service request other than the first one. 4272 Re-synchronisation Info 4273 For definition and use of this parameter see 3GPP TS 33.200. 4274 If multiple service requests are present in a dialogue then this parameter shall not be present in any service request other 4275 than the first one. 4276 Segmentation prohibited indicator 4277 This parameter indicates if the VLR or SGSN allows segmentation of the response at MAP user level. 4278 This parameter may be present only in the first request of the dialogue. 4279 Immediate response preferred indicator 4280 4281 4282 4283
This parameter indicates that one of the requested authentication vectors is requested for immediate use in the VLR or SGSN. It may be used by the HLR together with the number of requested vectors and the number of vectors stored in the HLR to determine the number of vectors to be obtained from the AuC. It shall be ignored if the number of available vectors is greater than the number of requested vectors.
4284 If multiple service requests are present in a dialogue then this parameter shall not be present in any service request other 4285 than the first one. 4286 AuthenticationSetList 4287 A set of one to five authentication vectors are transferred from the HLR to the VLR or from the HLR to the SGSN, if 4288 the outcome of the service was successful. 4289 User error
490
4290 One of the following error causes defined in clause 7.6.1 shall be sent by the user in case of unsuccessful outcome of 4291 the service, depending on the respective failure reason: 4292 4293 4294 4295
491 Release 4 492 493
124
3GPP TS 29.002 V4.17.0 (2006-06)
unknown subscriber; unexpected data value; system failure; data missing.
4296 Provider error 4297 See clause 7.6.1 for the use of this parameter.
4298 4299 8.5.3.1
8.5.3 MAP_AUTHENTICATION_FAILURE_REPORT service
Definition
4300 This service is used between the VLR and the HLR or between the SGSN or HLR for reporting of authentication 4301 failures.
4302 8.5.3.2
Service primitives
4303 The service primitives are shown in table 8.5/3. 4304
Table 8.5/3: MAP_AUTHENTICATION_FAILURE_REPORT parameters
Parameter name Invoke id IMSI Failure cause Re-attempt Access Type Rand VLR number SGSN number User error Provider error Request M M M M M M C C Indication M(=) M(=) M(=) M(=) M(=) M(=) C(=) C(=) Response M(=) Confirm M(=)
C(=) O
4305
4306 8.5.3.3
4307 Invoke id
Parameter use
4308 See clause 7.6.1 for the use of this parameter. 4309 IMSI 4310 See clause 7.6.2 for the use of this parameter. 4311 Failure Cause 4312 See clause 7.6.7 for use of this parameter. 4313 4314 Re-attempt 4315 See clause 7.6.7 for use of this parameter. 4316 Access Type 4317 See clause 7.6.7 for use of this parameter.
494
4318 Rand
495 Release 4 496 497
125
3GPP TS 29.002 V4.17.0 (2006-06)
4319 This parameter identifies the specific AV that failed authentication. 4320 See clause 7.6.7 for use of this parameter. 4321 VLR number 4322 Shall be present if the sender is VLR. See definition in clause 7.6.2. 4323 SGSN number 4324 Shall be present if the sender is SGSN. See definition in clause 7.6.2. 4325 User error 4326 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 4327 values defined in clause 7.6.1: 4328 4329 4330
Unknown Subscriber; System Failure; Unexpected Data Value.
4331 Provider error 4332 These are defined in clause 7.6.
4333 4334 4335 8.6.1.1
8.6 Security management services
8.6.1 MAP_SET_CIPHERING_MODE service
Definitions
4336 This service is used between the VLR and the MSC to set the ciphering mode and to start ciphering if applicable. It is 4337 called when another service requires that information is to be sent on the radio path in encrypted form. 4338 The service is a non-confirmed service and consists of two service primitives.
4339 8.6.1.2
Service primitives
4340 The service primitives are shown in table 8.6/1. 4341
Table 8.6/1: MAP_SET_CIPHERING_MODE parameters
Parameter name Invoke id Ciphering mode Kc Request M M C Indication M(=) M(=) C(=)
4342
4343 8.6.1.3
4344 Invoke id
Parameter use
4345 See clause 7.6.1 for the use of this parameter. 4346 Ciphering mode 4347 See clause 7.6.7 for the use of this parameter. 4348 Kc
498
4349 The Kc parameter should be included when the ciphering mode parameter indicates that ciphering must be performed.
499 Release 4 500 501
126
3GPP TS 29.002 V4.17.0 (2006-06)
4350 4351 4352 4353 8.7.1.1
8.7 International mobile equipment identities management services
8.7.1 MAP_CHECK_IMEI service
Definition
4354 This service is used between the VLR and the MSC and between the MSC and the EIR and between the SGSN and EIR 4355 to request check of IMEI. If the IMEI is not available in the MSC or in the SGSN, it is requested from the MS and 4356 transferred to the EIR in the service request. 4357 The service is a confirmed service and consists of four service primitives.
4358 8.7.1.2
Service primitives
4359 The service primitives are shown in table 8.7/1. 4360
Parameter name Invoke id IMEI Equipment status User error Provider error
Table 8.7/1: MAP_CHECK_IMEI parameters
Request M C Indication M(=) C(=) Response M(=) C C C Confirm M(=) C(=) C(=) C(=) O
4361
4362 8.7.1.3
4363 Invoke id
Parameter use
4364 See clause 7.6.1 for the use of this parameter. 4365 IMEI 4366 4367 4368 4369
See clause 7.6.2 for the use of this parameter. The parameter shall not be included in the service request between the VLR and the MSC, but is mandatory in the service request from the MSC to the EIR and from the SGSN to the EIR. It is not included in the service response from the EIR to the MSC or to the SGSN, but is mandatory in the service response from the MSC to the VLR on successful outcome.
4370 Equipment status 4371 See clause 7.6.4 for the use of this parameter. This parameter is sent by the responder in case of successful outcome of 4372 the service. 4373 User error 4374 One of the following error causes defined in clause 7.6.1 shall be sent by the user in case of unsuccessful outcome of 4375 the service, depending on the respective failure reason: 4376 4377 4378 4379
unknown equipment; this error is returned by the responder when the IMEI is not known in the EIR;
system failure; unexpected data value.
4380 Provider error
502
4381 See clause 7.6.1 for the use of this parameter.
503 Release 4 504 505
127
3GPP TS 29.002 V4.17.0 (2006-06)
4382 4383 8.7.2.1
8.7.2 MAP_OBTAIN_IMEI service
Definition
4384 This service is used between the VLR and the MSC to request the IMEI. If the IMEI is not available in the MSC, it is 4385 requested from the MS. 4386 The service is a confirmed service and consists of four service primitives.
4387 8.7.2.2
Service primitives
4388 The service primitives are shown in table 8.7/2. 4389
Parameter name Invoke id IMEI User error Provider error
Table 8.7/2: MAP_OBTAIN_IMEI parameters
Request M Indication M(=) Response M(=) C C Confirm M(=) C(=) C(=) O
4390
4391 8.7.2.3
4392 Invoke id
Parameter use
4393 See clause 7.6.1 for the use of this parameter. 4394 IMEI 4395 See clause 7.6.2 for the use of this parameter. The parameter is included in the service response from the MSC to the 4396 VLR on successful outcome of the service. 4397 User error 4398 If the service fails, the VLR sends the user error System Failure (see clause 7.6.1) to the MSC. 4399 Provider error 4400 See clause 7.6.1 for the use of this parameter.
4401 4402 4403 8.8.1.1
-
8.8 Subscriber management services
8.8.1 MAP-INSERT-SUBSCRIBER-DATA service
Definition
4404 This service is used by an HLR to update a VLR with certain subscriber data in the following occasions: 4405 4406 4407 4408 4409 4410 4411
the operator has changed the subscription of one or more supplementary services, basic services or data of a subscriber. Note that in case of withdrawal of a Basic or Supplementary service this primitive shall not be used; the operator has applied, changed or removed Operator Determined Barring; the subscriber has changed data concerning one or more supplementary services by using a subscriber procedure; the HLR provides the VLR with subscriber parameters at location updating of a subscriber or at restoration. In this case, this service is used to indicate explicitly that a supplementary service is not provisioned, if the supplementary service specification requires it. The only supplementary services which have this requirement
506
4412 4413 4414
507 Release 4 508 509
128
3GPP TS 29.002 V4.17.0 (2006-06)
are the CLIR and COLR services. Network access mode is provided only in restoration. If the Super-Charger functionality is supported the HLR may not need to provide the VLR with subscriber parameters at location updating of a subscriber. See TS 23.116.
4415 Also this service is used by an HLR to update an SGSN with certain subscriber data in the following occasions: 4416 4417 4418 4419 4420 4421 4422
if the GPRS subscription has changed; if the network access mode is changed; the operator has applied, changed or removed Operator Determined Barring; the subscriber has changed data concerning one or more supplementary services by using a subscriber procedure; the HLR provides the SGSN with subscriber parameters at GPRS location updating of a subscriber. If the Super-Charger functionality is supported the HLR may not need to provide the SGSN with subscriber parameters. See 3GPP TS 23.116.
4423 It is a confirmed service and consists of the primitives shown in table 8.8/1.
4424 8.8.1.2
4425
Service primitives
Table 8.8/1: MAP-INSERT-SUBSCRIBER-DATA
Parameter name Invoke Id IMSI MSISDN Category Subscriber Status Bearer service List Teleservice List Forwarding information List Call barring information List CUG information List SS-Data List eMLPP Subscription Data MC-Subscription Data Operator Determined Barring General data Operator Determined Barring HPLMN data Roaming Restriction Due To Unsupported Feature Regional Subscription Data VLR CAMEL Subscription Info Voice Broadcast Data Voice Group Call Data Network access mode GPRS Subscription Data Roaming Restricted In SGSN Due To Unsupported Feature North American Equal Access preferred Carrier Id List SGSN Camel Subscription Info LSA Information IST Alert Timer SS-Code List LMU Identifier LCS Information CS Allocation/Retention priority Super-Charger Supported In HLR Subscribed Charging Characteristics Regional Subscription Response Supported CAMEL Phases User error Provider error
Request M C C C C C C C C C C C C C C C C C C C C C C U C C C C C C C C
Indication M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=)
Response M(=)
Confirm M(=)
C C
C(=) C(=)
C(=)
C C(=) C(=) C(=) C(=) C(=) C C U
C(=)
C(=) C (=) C(=) O
510
4426
511 Release 4 512 513
129
3GPP TS 29.002 V4.17.0 (2006-06)
4427 8.8.1.3
Parameter use
4428 All parameters are described in clause 7.6. The following clarifications are applicable: 4429 Network access mode 4430 4431 4432 4433
This parameter defines if the subscriber has access to MSC/VLR and/or to SGSN. This parameter is used by SGSN and MSC/VLR. In VLR, the parameter is used only as part of Restore Data Procedure and the parameter is not stored in the VLR. This parameter shall always be sent to the SGSN as part of the GPRS subscriber data at GPRS location updating. It shall be sent to the SGSN if it is changed as a result of administrative action.
4434 IMSI 4435 It is only included if the service is not used in an ongoing transaction (e.g. location updating). This parameter is used by 4436 the VLR and the SGSN. 4437 MSISDN 4438 It is included either at location updating or when it is changed. The MSISDN sent shall be the basic MSISDN. This 4439 parameter is used by the VLR and the SGSN. 4440 Category 4441 It is included either at location updating or when it is changed. This parameter is used only by the VLR and if the SGSN 4442 receives this parameter it shall ignore it. 4443 Subscriber Status 4444 It is included either at location updating or when it is changed. 4445 4446 4447 4448
To apply, remove or update Operator Determined Barring Categories the Subscriber Status is set to Operator Determined Barring. In this case ODB General Data shall also be present. If the Operator Determined Barring applies and the subscriber is registered in the HPLMN and HPLMN specific Operator Determined Barring applies then ODB HPLMN Specific Data shall also be present.
4449 To remove all Operator Determined Barring Categories the Subscriber Status shall be set to "Service Granted". This 4450 parameter is used by the VLR and the SGSN. 4451 Bearer service List 4452 A list of Extensible Bearer service parameters (Extensible Bearer service is defined in clause 7.6). An Extensible Bearer 4453 service parameter must be the code for an individual Bearer service, except in the cases described below. 4454 4455 4456 4457
The codes for the Bearer service groups "allAlternateSpeech-DataCDA" and "allAlternateSpeech-DataCDS" shall, if applicable, be sent from the HLR to the VLR as a pair. The codes for the Bearer service groups "allSpeechFollowedByDataCDA" and "allSpeechFollowedByDataCDS" shall, if applicable, be sent from the HLR to the VLR as a pair.
4458 If it is included in the Request/Indication, it includes either all Extensible Bearer services subscribed (at location 4459 updating or at restoration) or only the ones added (at subscriber data modification). 4460 If the VLR receives an Indication containing any Extensible Bearer service parameters which it does not 4461 support/allocate it returns them in the response to the HLR and discards the unsupported Extensible Bearer services (no 4462 error is sent back), except in the cases described below. 4463 4464 4465 4466 4467 4468 4469 4470
If the VLR receives the codes for the Bearer service groups "allSpeechFollowedByDataCDA" and "allSpeechFollowedByDataCDS" and supports one or more of the circuit-switched synchronous or asynchronous data rates specified for simple data bearer services, it shall accept the bearer service codes, and not return them in the response to the HLR. If the VLR does not support any of the circuit-switched synchronous or asynchronous data rates specified for simple data bearer services, and receives the pair of codes for "allAlternateSpeech-DataCDA" and "allAlternateSpeech-DataCDS" or the pair of codes for "allSpeechFollowedByDataCDA" and "allSpeechFollowedByDataCDS", it shall reject the pair of codes by returning them in the response to the HLR. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore it.
514
4471 Teleservice List 4472 A list of Extensible Teleservice parameters (Extensible Teleservice is defined in clause 7.6). An Extensible Teleservice 4473 parameter must be the code for an individual Teleservice. 4474 If it is included in the Request/Indication, it contains either all Extensible Teleservices subscribed (at location updating 4475 or at restoration) or the ones added (at subscriber data modification). Only the Extensible Teleservices that are relevant 4476 to the node at which the message is received should be included in the Teleservice List. 4477 If the VLR or the SGSN receives an Indication containing any Extensible Teleservice parameters which it does not 4478 support/allocate it returns them in the response to the HLR and discards the unsupported Extensible Teleservices (no 4479 error is sent back). This parameter is used by the VLR and the SGSN. 4480 Forwarding information List 4481 A list of Extensible Forwarding information parameters (Extensible Forwarding information is defined in clause 7.6). It 4482 includes Call Forwarding services either at location updating or at restoration or when they are changed. Each 4483 Extensible Forwarding information parameter shall be treated independently of all other parameters in the primitive. 4484 The Extensible Forwarding information shall include the SS-Code for an individual call forwarding supplementary 4485 service. The Extensible Forwarding information shall contain one or more Extensible Forwarding Features (Extensible 4486 Forwarding Feature is defined in clause 7.6). 4487 The Extensible Forwarding Feature may include an Extensible Basic Service Group. This shall be interpreted according 4488 to the rules in clause 8.8.1.4. 4489 The Extensible Forwarding Feature shall contain an Extensible SS-Status parameter. 4490 4491 4492 4493 4494 4495
515 Release 4 516 517
130
3GPP TS 29.002 V4.17.0 (2006-06)
If the Extensible SS-Status indicates that call forwarding is registered then (except for call forwarding unconditional) the Extensible Forwarding Feature shall contain a number to define the forwarded-to destination and, if available, the forwarded-to subaddress. In other states the forwarded-to number and, if applicable, the forwarded-to subaddress shall not be included. For call forwarding unconditional the forwarded-to number and, if applicable, the forwarded-to subaddress shall not be included. If the VLR does not receive a forwarded-to subaddress then it shall assume that a forwarded-to subaddress has not been registered.
4496 The Extensible Forwarding Feature shall contain the extensible forwarding options (except for call forwarding 4497 unconditional where the extensible forwarding options shall not be included). Bits 3 and 4 of the extensible forwarding 4498 options shall be ignored by the VLR, and may be set to any value by the HLR. 4499 For call forwarding on no reply: If the extensible SS-Status indicates that call forwarding is registered then the 4500 Extensible Forwarding Feature shall contain an extensible no reply condition timer. In other states the no reply 4501 condition timer shall not be included. 4502 For call forwarding services other than call forwarding on no reply: The Extensible Forwarding Feature shall not 4503 contain a no reply condition timer. 4504 4505 4506 4507
If the VLR receives an Indication containing any Call Forwarding service codes which it does not support/allocate it returns them to the HLR in the parameter SS-Code List and discards the unsupported Call Forwarding service codes (no error is sent back). This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore it.
4508 Call barring information List 4509 A list of Extensible Call barring information parameters (Extensible Call barring information is defined in clause 7.6). It 4510 includes Call Barring services either at location updating or at restoration or when they are changed. Each Extensible 4511 Call barring information parameter shall be treated independently of all other parameters in the primitive. 4512 The Extensible Call barring information shall include the SS-Code for an individual call barring supplementary service. 4513 The Extensible Call barring information shall contain one or more Extensible Call Barring Features (Extensible Call 4514 Barring Feature is defined in clause 7.6). 4515 The Extensible Call Barring Feature may include an Extensible Basic Service Group. This shall be interpreted 4516 according to the rules in clause 8.8.1.4. 4517 The Extensible Call Barring Feature shall contain an extensible SS-Status parameter.
518
4518 4519 4520 4521
519 Release 4 520 521
131
3GPP TS 29.002 V4.17.0 (2006-06)
If the VLR receives an Indication containing any Extensible Call Barring service codes which it does not support/allocate it returns them to the HLR in the parameter SS-Code List and discards the unsupported Extensible Call Barring service codes (no error is sent back). This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore it.
4522 CUG information List 4523 A list of CUG information list parameters (CUG information is defined in clause 7.6). It includes CUG information 4524 either at location updating or at restoration or when it is changed. 4525 At location updating, restoration or when there is a change in CUG data, the HLR shall include the complete 4526 CUG-SubscriptionList and, if there are options per basic group, it shall also include the complete CUG-FeatureList. If 4527 there are not options per extensible basic service group the CUG-FeatureList shall not be included. 4528 In any dialogue, the first insertSubscriberData message which contains CUG information shall include a non-empty 4529 CUG-SubscriptionList. 4530 When the VLR receives CUG data it shall replace the stored CUG data with the received data set. 4531 If CUG-FeatureList is omitted in the Insert Subscriber Data operation VLR shall interpret that no options per extensible 4532 basic service group exist, and then it shall apply the default values i.e. no outgoing access, no incoming access, no 4533 preferential CUG exists. 4534 If CUG-Feature is received without preferential CUG, the VLR shall interpret that no preferential CUG applies. 4535 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error 4536 Unexpected Data Value. 4537 Note that data consistency between CUG subscription data and CUG feature data is the responsibility of the HLR. 4538 If the VLR does not support the CUG service it returns its code to the HLR in the parameter SS-Code List and discards 4539 the received information (no error is sent back). This parameter is used only by the VLR and if the SGSN receives this 4540 parameter it shall ignore it. 4541 SS-Data List 4542 4543 4544 4545
A list of Extensible SS-Data parameters (Extensible SS-Data is defined in clause 7.6). It is sent for any other supplementary service than Call Forwarding, Call Barring, CUG and eMLPP either at location updating or at restoration or when they are changed. Each SS-Data parameter shall be treated independently of all other parameters in the primitive.
4546 The Extensible SS-Data shall include the SS-Code for an individual supplementary service. 4547 The Extensible SS-Data shall contain an Extensible SS-Status parameter and any subscription options that are 4548 applicable to the service defined by the SS-Code. 4549 The SS-Data may include a Basic Service Group List. This shall be interpreted according to the rules in clause 8.8.1.4. 4550 If the VLR receives an Indication containing any supplementary service codes which it does not support/allocate it 4551 returns them to the HLR in the parameter SS-Code List and therefore discards the unsupported service codes received 4552 (no error is sent back). 4553 4554 4555 4556
This parameter is used by the SGSN only for LCS. If the SGSN receives an Indication containing any LCS related supplementary service codes which it does not support/allocate then it returns them to the HLR in the parameter SSCode List and therefore discards the unsupported service codes received (no error is sent back). SS-codes not related to the supported LCS capability set shall be discarded.
4557 Operator Determined Barring General data 4558 4559 4560 4561
If it is included in a Request/Indication, it includes all the Operator Determined Barring categories that may be applied to a subscriber registered in any PLMN. This parameter is only included in a Request/Indication when the parameter Subscriber Status is set to the value Operator Determined Barring. Note that all General Operator Determined Barring Categories shall be set to their actual status.
522
4562 4563 4564 4565
523 Release 4 524 525
132
3GPP TS 29.002 V4.17.0 (2006-06)
If the VLR or the SGSN receives an Indication containing Operator Determined Barring General Data which shows that the subscriber is subject to barring not supported / not allocated by the VLR or by the SGSN, it returns Operator Determined Barring General Data in the response to the HLR to show the barring categories which are not supported / not allocated by the VLR or by the SGSN. This parameter is used by the VLR and the SGSN.
4566 Operator Determined Barring HPLMN data 4567 4568 4569 4570
It includes all the Operator Determined Barring categories that may be applied only to a subscriber registered in the HPLMN. Therefore, it shall only be transferred to the VLR or to the SGSN when the subscriber is roaming into the HPLMN and when the parameter Subscriber Status is set to the value Operator Determined Barring. Note that all HPLMN Operator Determined Barring Categories shall be set to their actual status.
4571 If Subscriber Status is set to the value Operator Determined Barring and no Operator Determined Barring HPLMN data 4572 is present then the VLR or the SGSN shall not apply any HPLMN specific ODB services to the subscriber. This 4573 parameter is used by the VLR and the SGSN. 4574 eMLPP Subscription Data 4575 If included in the Insert Subscriber Data request this parameter defines the priorities the subscriber might apply for a 4576 call (as defined in clause 7.6). It contains both subparameters of eMLPP. 4577 If the VLR does not support the eMLPP service it returns its code to the HLR in the parameter SS-Code List and 4578 therefore discards the received information (no error is sent back). 4579 4580 4581 4582
eMLPP subscription data that have been stored previously in a subscriber data record in the VLR are completely replaced by the new eMLPP subscription data received in a MAP_INSERT_SUBSCRIBER_DATA during either an Update Location or Restore Data procedure or a stand alone Insert Subscriber data procedure. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore it.
4583 MC Subscription Data 4584 If included in the Insert Subscriber Data request, this parameter provides the MC Subscription Data as defined in 4585 clause 7.6. 4586 If the VLR does not support the MC service, it returns its code to the HLR in the parameter SS-Code List and therefore 4587 discards the received information (no error is sent back). 4588 4589 4590 4591
MC subscription data that have been stored previously in a subscriber data record in the VLR are completely replaced by the new MC subscription data received in a MAP_INSERT_SUBSCRIBER_DATA during either an Update Location or Restore Data procedure or a stand alone Insert Subscriber data procedure. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore it.
4592 Roaming Restriction Due To Unsupported Feature 4593 The HLR may decide to include this parameter in the request if certain services or features are indicated as not 4594 supported by the MSC/VLR (e.g. Advice of Charge Charging Level). 4595 If this parameter is sent to the VLR the MSC area is restricted by the HLR and the VLR. This parameter is used only by 4596 the VLR and if the SGSN receives this parameter it shall ignore it. 4597 Regional Subscription Data 4598 4599 4600 4601 4602 4603
If included in the Insert Subscriber Data request this parameter defines the subscriber's subscription area for the addressed VLR or for the addressed SGSN (as defined in clause 7.6). It contains the complete list of up to 10 Zone Codes that apply to a subscriber in the currently visited PLMN. The HLR shall send only those Zone Codes which are stored against the CC and NDC of the VLR or the CC and NDC of the SGSN to be updated. NOTE: Support of this parameter is a network operator option and it will not be sent to networks which do not support Regional Subscription.
4604 Regional subscription data that have been stored previously in a subscriber data record in the VLR or in the SGSN are 4605 completely replaced by the regional subscription data received in an Insert Subscriber Data indication during either an 4606 Update Location or Restore Data procedure or a stand alone Insert Subscriber data procedure.
526
4607 After the regional subscription data are inserted the VLR or the SGSN shall derive whether its location areas are 4608 allowed or not. If the whole MSC or SGSN area is restricted it will be reported to HLR by returning the Regional 4609 Subscription Response. 4610 The VLR or the SGSN returns a Regional Subscription Response indicating that a problem with the Zone Code has 4611 been detected in one of the following cases: 4612 4613 4614 4615
527 Release 4 528 529
133
3GPP TS 29.002 V4.17.0 (2006-06)
Too Many Zone Codes: more than 10 Zone Codes are to be stored in the VLR or in the SGSN. Regional Subscription Not Supported by the VLR or the SGSN. Zone Codes Conflict: the VLR or the SGSN detects that the zone codes indicate conflicting service permission for a location area.
4616 Zone codes which have no mapping to location areas shall be ignored. 4617 If a sequence of MAP_INSERT_SUBSCRIBER_DATA services is used during a dialogue, Regional Subscription Data 4618 shall be accepted only in one service. Regional Subscription Data received in a subsequent service shall be rejected with 4619 the error Unexpected Data Value. 4620 If Regional Subscription Data are not included in any MAP_INSERT_SUBSCRIBER_DATA service, there is no 4621 restriction of roaming due to Regional Subscription. This parameter is used by the VLR and the SGSN. 4622 Voice Broadcast Data 4623 This parameter contains a list of group id's a user might have subscribed to; (VBS-Data is defined in clause 7.6). It 4624 includes VBS information either at location updating or at restoration or when it is changed. 4625 At location updating, restoration or when there is a change in VBS data, the HLR shall include the complete VBS-Data. 4626 When the VLR receives VBS-Data within a dialogue it shall replace the stored VBS-data with the received data set. All 4627 subsequent VBS-data received within this dialogue shall be interpreted as add-on data. 4628 If VBS-data is omitted in the Insert Subscriber Data operation the VLR shall keep the previously stored VBS data. 4629 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error 4630 Unexpected Data Value. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore 4631 it. 4632 Voice Group Call Data 4633 This parameter contains a list of group id's a user might have subscribed to; see clause 7.6. 4634 At location updating, restoration or when there is a change in VGCS data, the HLR shall include the complete 4635 VGCS-Data. 4636 When the VLR receives VGCS-Data within a dialogue it shall replace the stored VGCS-Data with the received data set. 4637 All VGCS-Data received within this dialogue shall be interpreted as add-on data. 4638 If VBCS-Data is omitted in the Insert Subscriber Data operation the VLR shall keep the previously stored VGCS-Data. 4639 If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error 4640 Unexpected Data Value. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore 4641 it. 4642 North American Equal Access preferred Carrier Id List 4643 A list of the preferred carrier identity codes that are subscribed to. 4644 4645 4646 4647
When the VLR receives this parameter from the HLR, it shall replace the previously stored preferred carrier identity codes with the received ones. It is not possible to delete all the preferred carrier identity codes from the VLR using this service. To delete all the preferred carrier identity codes from the VLR, the HLR shall use the MAP_CANCEL_LOCATION service.
530
4648 LSA Information 4649 4650 4651 4652 4653 4654 4655
531 Release 4 532 533
134
3GPP TS 29.002 V4.17.0 (2006-06)
If included in the ISD request, this parameter contains a list of localised service area identities a user might have subscribed to together with the priority, the preferential access indicator, the active mode support indicator and active mode indication of each localised service area; see clause 7.6. The access right outside these localised service areas is also indicated. In all cases mentioned below, the LSA information shall only include LSA Data applicable to the VPLMN where the Subscriber is located. The VLR number, received in the MAP-UPDATE_LOCATION primitive, or the SGSN number, received in the MAP_UPDATE_GPRS_LOCATION primitive, can be used, alongside data stored in the HLR, to determine the LSA Data applicable to the VPLMN.
4656 At restoration, location updating or GPRS location updating the HLR shall include the complete set of applicable LSA 4657 Information. 4658 When there is a change in LSA data the HLR shall include at least the new and/or modified LSA data. 4659 When there is a change in the access right outside the localised service areas the HLR shall include the LSA only access 4660 indicator. 4661 4662 4663 4664
When the SGSN or the VLR receives LSA information within a dialogue it shall check if the received data has to be considered as the entire LSA information. If so, it shall replace the stored LSA information with the received data set, otherwise it shall replace the data only for the modified LSA data (if any) and/or access right, and add the new LSA data (if any) to the stored LSA Information.
4665 If the entire LSA information is received, it shall always include the LSA only access indicator value together with the 4666 LSA data applicable for the PLMN (if any). 4667 If LSA Information is omitted in the Insert Subscriber Data operation the SGSN or the VLR shall keep the previously 4668 stored LSA Information. 4669 If the SGSN or the VLR detects that there is overlapping in the information received within a dialogue, it shall send the 4670 error Unexpected Data Value. This parameter is used by the VLR and the SGSN. 4671 IST Alert Timer 4672 This parameter contains the IST Alert timer value that must be used to inform the HLR about the call activities that the 4673 subscriber performs. 4674 At Location Updating, restoration, or when there is a change in the IST data defined for the Subscriber, the HLR shall 4675 include the IST Alert timer. 4676 LMU Identifier 4677 This parameter indicates the presence of an LMU. This parameter is used only by the VLR and shall be ignored if 4678 received by an SGSN. 4679 LCS Information 4680 This parameter provides the following LCS related information for an MS subscriber: 4681 4682 4683
list of GMLCs in the HPLMN; privacy exception list; MO-LR list.
4684 At restoration and location updating, the HLR shall include the complete LCS data of the subscriber. 4685 When there is a change in LCS subscriber data the HLR shall include at least the new and/or modified LCS data. LCS 4686 data that is not modified need not be included. 4687 The VLR/SGSN shall keep any previously stored LCS Information that is not included in an Insert Subscriber Data 4688 operation. 4689 If the VLR/SGSN detects that there is overlapping in the LCS information received within a dialogue, it shall send the 4690 error Unexpected Data Value. However, if the VLR receives the LCS code in both the LCS Information and the 4691 SS-Data List, then the VLR shall not interpret this as overlapping data.
534
4692 Super-Charger Supported In HLR 4693 This parameter is used by the HLR to indicate support for the Super-Charger functionality. If this parameter is present it 4694 shall include an indication of the age of the subscription data stored in the HLR. 4695 If this parameter is absent then the HLR does not support the Super-Charger functionality. 4696 Subscribed Charging Characteristics 4697 This parameter refers to the Subscribed Charging Characteristics as defined in 3GPP TS 32.215 [123]. 4698 For a detailed description of the use of the parameter, see 3GPP TS 32.215 [123x]. 4699 This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore it. 4700 SS-Code List 4701 4702 4703 4704 4705
535 Release 4 536 537
135
3GPP TS 29.002 V4.17.0 (2006-06)
The list of SS-Code parameters for the services that are provided to a subscriber but are not supported/allocated by the VLR (SS-Code is defined in clause 7.6). The list can only include individual SS-Codes that were sent in the service request. For the VLR, this list can also include SS-Codes for the eMLPP and/or CUG services if the above mentioned conditions, as described in eMLPP Subscription Data and/or CUG information List, are met (that is, eMLPP Subscription Data and/or CUG information List are received). This parameter is used only by the VLR.
4706 Regional Subscription Response 4707 If included in the response this parameter indicates one of: 4708 4709 4710 4711 4712
MSC Area Restricted entirely because of regional subscription; SGSN Area Restricted entirely because of regional subscription; Too Many Zone Codes to be inserted; Zone Codes Conflict; Regional Subscription not Supported by the VLR or by the SGSN.
4713 If the VLR determines after insertion of Regional Subscription Data that the entire MSC area is restricted, the VLR 4714 shall respond with a Regional Subscription Response indicating MSC Area Restricted. Otherwise MSC Area Restricted 4715 is not sent. The HLR shall check whether the current MSC area is no longer restricted. 4716 4717 4718 4719
If the SGSN determines after insertion of Regional Subscription Data that the entire SGSN area is restricted, the SGSN shall respond with a Regional Subscription Response indicating SGSN Area Restricted. Otherwise SGSN Area Restricted is not sent. The HLR shall check whether the current SGSN area is no longer restricted. This parameter is used by the VLR and by the SGSN.
4720 VLR CAMEL Subscription Info 4721 4722 4723 4724 4725 4726
This parameter is sent for subscribers who have CAMEL services which are invoked in the MSC. In CAMEL phase 1, this parameter contains only the O-CSI. In CAMEL Phase 2, this parameter may contain OCSI, SS-CSI and TIF-CSI. In CAMEL Phase 3, this parameter may contain O-CSI, D-CSI, SS-CSI, VT-CSI, SMS-CSI, M-CSI and TIF-CSI. In CAMEL Phase 2 TDP-Criteria for O-CSI may be associated with O-CSI. In CAMEL Phase 3, additionally, TDPCriteria for VT-CSI may be associated with VT-CSI.. The VLR CAMEL Subscription Info is sent at location updating or when any information in the applicable CAMEL Subscription Info in the HLR has been changed.
4727 At location updating, the complete set of VLR CAMEL Subscription Info is sent in one dialogue. 4728 When CAMEL Subscription Information is changed in the HLR and changed data have to be sent to the VLR, then: 4729 4730 4731
for CAMEL Phase 1 and CAMEL Phase 2, the complete set of VLR CAMEL Subscription Info is sent in one dialogue; for CAMEL Phase 3, one or more specific elements of VLR CAMEL Subscription Info are sent in one dialogue.
4732 When the VLR receives a specific element of VLR CAMEL Subscription Info, it shall overwrite the corresponding 4733 specific element of VLR CAMEL Subscription Info (if any) which it has stored for that subscriber.
538
4734 For CAMEL Phase 1 and CAMEL Phase 2 , the VLR CAMEL Subscription Info consists of any one or more of: 4735 4736 4737 4738
539 Release 4 540 541
136
3GPP TS 29.002 V4.17.0 (2006-06)
O-CSI (irrespective of the value of the CAMEL Capability Handling inside O-CSI),TDP-Criteria for OCSI,SS-CSI and TIF-CSI. (The complete set of above shall be sent even if only one CSI has changed in case of stand alone ISD. The omitted elements of above list will be withdrawn in the VLR.)
4739 From CAMEL phase 3 onwards, the specific elements of VLR CAMEL Subscription Info which may be sent are:
4740
4741 4742 4743 4744 4745 4746 4747 4748 4749 4750 4751 4752 4753
-O-CSI (irrespective of the value of the CAMEL Capability Handling inside O-CSI), TDP criteria for OCSI, SS-CSI and TIF-CSI; (The complete set of above shall be sent even if only one CSI has changed in case of stand alone ISD. The omitted elements of above list will be withdrawn in the VLR.) D-CSI; VT-CSI; TDP-Criteria for VT-CSI; SMS-CSI; M-CSI.
If the VLR CAMEL Subscription Info is omitted in the Insert Subscriber Data operation the VLR shall keep the previously stored VLR CAMEL Subscription Info. Within one dialogue subsequent received data are interpreted as add-on data. If the VLR detects that there is overlapping in the information received within a dialogue, it shall send the error Unexpected Data Value. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore it.
4754 The VLR CAMEL Subscription Info may contain the TIF-CSI (Translation Information Flag) for CAMEL Phase 2 and 4755 3. See 3GPP TS 23.072 for the use of this parameter and the conditions for its presence. 4756 Supported CAMEL Phases 4757 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. This parameter is used 4758 by the VLR and SGSN. 4759 A VLR or SGSN not supporting any CAMEL Phase may omit this parameter. 4760 GPRS Subscription Data 4761 This parameter contains a list of PDP-contexts a user has subscribed to; see clause 7.6. 4762 At GPRS location updating the HLR shall include the complete GPRS Subscription Data. 4763 When there is a change in GPRS subscriber data the HLR shall include only the new and/or modified PDP contexts. 4764 4765 4766 4767
When the SGSN receives GPRS Subscription Data within a dialogue it shall check if the received data has to be considered as the entire GPRS subscription data. If so, it shall replace the stored GPRS Subscription Data with the received data set, otherwise it shall replace the data only for the modified PDP contexts (if any) and add the new PDP contexts (if any) to the stored GPRS Subscription Data.
4768 If GPRS Subscription Data is omitted in the Insert Subscriber Data operation the SGSN shall keep the previously stored 4769 GPRS Subscription Data. 4770 If the SGSN detects that there is overlapping in the information received within a dialogue, it shall send the error 4771 Unexpected Data Value. This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore 4772 it. 4773 SGSN CAMEL Subscription Info
542
4774 The SGSN CAMEL Subscription Info is sent at GPRS location updating or when any information in the applicable 4775 SGSN CAMEL Subscription Info in the HLR has been changed. In CAMEL Phase 3, this parameter may contain one or 4776 both of GPRS-CSI and SMS-CSI. 4777 At GPRS location updating the complete set of SGSN CAMEL Subscription Info is sent. 4778 When CAMEL Subscription Information is changed in the HLR and changed data have to be sent to the SGSN, then 4779 one or more specific elements of SGSN CAMEL Subscription Info are sent in one dialogue. 4780 When the SGSN receives a specific element of SGSN CAMEL Subscription Info, it shall overwrite the corresponding 4781 specific element of SGSN CAMEL Subscription Info (if any) which it has stored for that subscriber. 4782 The specific elements of SGSN CAMEL Subscription Info which may be sent are: 4783 4784
543 Release 4 544 545
137
3GPP TS 29.002 V4.17.0 (2006-06)
SMS-CSI; GPRS-CSI.
4785 This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore it. 4786 Roaming Restricted In SGSN Due To Unsupported Feature 4787 The HLR may decide to include this parameter in the request if certain services or features are indicated as not 4788 supported by the SGSN. This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore 4789 it. 4790 CS Allocation/Retention priority 4791 The CS Allocation/Retention priority is used only for Circuit Switched (CS). This parameter specifies relative 4792 importance to compare with other bearers about allocation and retention of bearer. This parameter is used only by the 4793 VLR and if the SGSN receives this parameter it shall ignore it. 4794 User error 4795 Only one of the following values is applicable: 4796 4797 4798
Unidentified subscriber; Data missing; Unexpected data value.
4799 8.8.1.4
4800 4801 4802 4803
Basic service information related to supplementary services
A number of parameters that relate to supplementary services can be qualified by a Basic Service Group (or a Basic Service Group List). This clause explains how this information is to be interpreted. Supplementary service parameters to which this clause is applicable only apply to the basic service groups described in this clause, and only those basic service groups shall be overwritten at the VLR.
4804 The Basic Service Group (or Basic Service Group List) is optional. 4805 If present the Basic Service Group (or the elements of the Basic Service Group List) shall be one of: 4806 4807 4808 4809 4810 4811 4812 4813
an Elementary Basic Service Group for which the supplementary service is applicable to at least one basic service in the group; and to which the subscriber has a subscription to at least one basic service in the group; the group "All Teleservices" provided that the service is applicable to at least one teleservice and that the subscriber has a subscription to at least one teleservice that is in the same Elementary Basic Service Group as a teleservice to which the service is applicable; the group "All Bearer Services" provided that the service is applicable to at least one bearer service and that the subscriber has a subscription to at least one bearer service that is in the same Elementary Basic Service Group as a basic service to which the service is applicable.
4814 If the Basic Service Group (or Basic Service Group List) is not present then the parameter shall apply to all Basic 4815 Service Groups.
546
4816 If the basic service information is not a single Elementary Basic Service Group then the parameter shall be taken as 4817 applying individually to all the Elementary Basic Service Groups for which: 4818 4819
547 Release 4 548 549
138
3GPP TS 29.002 V4.17.0 (2006-06)
the supplementary service is applicable to at least one basic service in the Basic Service Group; and the subscriber has a subscription to at least one basic service in the Basic Service Group.
4820 The VLR is not required to store supplementary services data for Basic Service Groups that are not supported at the 4821 VLR.
4822 4823 8.8.2.1
8.8.2 MAP-DELETE-SUBSCRIBER-DATA service
Definition
4824 This service is used by an HLR to remove certain subscriber data from a VLR if the subscription of one or more 4825 supplementary services or basic services is withdrawn. Note that this service is not used in case of erasure or 4826 deactivation of supplementary services. 4827 Also this service is used by an HLR to remove GPRS subscription data from a SGSN. 4828 It is a confirmed service and consists of the primitives shown in table 8.8/2.
4829 8.8.2.2
4830
Service primitives
Table 8.8/2: MAP-DELETE-SUBSCRIBER-DATA
Parameter name Invoke Id IMSI Basic service List SS-Code List Roaming Restriction Due To Unsupported Feature Camel Subscription Info Withdraw Specific CSI Withdraw Regional Subscription Data VBS Group Indication VGCS Group Indication GPRS Subscription Data Withdraw Roaming Restricted In SGSN Due To Unsupported Feature LSA Information Withdraw IST Information Withdraw Regional Subscription Response GMLC List Withdraw Subscribed Charging Characteristics Withdraw User error Provider error
Request M M C C C C C C C C C C C C C C
Indication M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=)
Response M(=)
Confirm M(=)
C C(=) C(=) C
C(=)
C(=) O
4831
4832 8.8.2.3
Parameter use
4833 All parameters are described in clause 7.6. The following clarifications are applicable: 4834 Basic service List 4835 4836 4837 4838
A list of Extensible Basic service parameters (Extensible Basic service is defined in clause 7.6). It is used when one, several or all basic services are to be withdrawn from the subscriber. If the VLR or the SGSN receives a value for an Extensible Basic Service which it does not support, it shall ignore that value. This parameter is used by the VLR and by the SGSN.
4839 SS-Code List
550
4840 A list of SS-Code parameters (SS-Code is defined in clause 7.6). It is used when several or all supplementary services 4841 are to be withdrawn from the subscriber. 4842 There are three possible options: 4843 4844 4845 4846 4847 4848
551 Release 4 552 553
139
3GPP TS 29.002 V4.17.0 (2006-06)
deletion of basic service(s); The parameter Basic service List is only included.
deletion of supplementary service(s); The parameter SS-Code List is only included.
deletion of basic and supplementary services; Both Basic service List and SS-Code List are included.
4849 This parameter is used by the VLR and SGSN for LCS. Otherwise, this parameter is used only by the VLR and if the 4850 SGSN receives this parameter it shall ignore it. 4851 Roaming Restriction Due To Unsupported Feature 4852 This parameter is used if Roaming Restriction Due To Unsupported Feature is deleted from the subscriber data. This 4853 may occur if unsupported features or services are removed from the subscriber data in the HLR. 4854 If this parameter is sent the VLR shall check if the current Location Area is possibly allowed now. This parameter is 4855 used only by the VLR and if the SGSN receives this parameter it shall ignore it. 4856 CAMEL Subscription Info Withdraw 4857 This parameter is used to indicate that CAMEL Subscription Info shall be deleted from the VLR or from the SGSN. All 4858 CAMEL Subscription Info for the subscriber shall be deleted. This parameter is used by the VLR and by the SGSN. 4859 This parameter should not be sent in the same message as the Specific CSI Withdraw parameter. 4860 Specific CSI Withdraw 4861 This parameter is used to indicate that one or more specific elements of CAMEL Subscription Info shall be deleted from 4862 the VLR or from the SGSN. 4863 The specific elements of CAMEL Subscription Info which may be withdrawn are: 4864 4865 4866 4867 4868 4869 4870 4871
O-CSI with TDP criteria for O-CSI; SS-CSI; TIF-CSI; D-CSI; VT-CSI with TDP criteria for VT-CSI; SMS-CSI; M-CSI; GPRS-CSI.
4872 This parameter is used by the VLR and by the SGSN. It shall not be sent to VLRs that do not support CAMEL phase 3. 4873 This parameter should not be sent in the same message as the CAMEL Subscription Info Withdraw parameter. 4874 Regional Subscription Identifier 4875 4876 4877 4878 4879
Contains one single Zone Code (as defined in clause 7.6) and is used if all Zone Codes shall be deleted from the subscriber data. When all the Zone Codes are deleted, the VLR or the SGSN shall check for its location areas whether they are allowed or not. If the whole MSC area is restricted, VLR will report it to HLR by returning the Regional Subscription Response "MSC Area Restricted". If the whole SGSN area is restricted, SGSN will report it to HLR by returning the Regional Subscription Response "SGSN Area Restricted".
554
4880 The binary coding of the Zone Code value received in a Delete Subscriber Data request shall not be checked by the 4881 VLR or by the SGSN. 4882 Note that support of this parameter is a network operator option and it shall not be sent to networks which do not 4883 support Regional Subscription. 4884 If Regional Subscription is not supported by the VLR or by the SGSN, the request for deletion of Zone Codes is refused 4885 by sending the Regional Subscription Response "Regional Subscription Not Supported" to the HLR. 4886 If no Zone Codes are stored in the respective subscriber data record, the request for deleting all Zone Code information 4887 shall be ignored and no Regional Subscription Response shall be returned. This parameter is used by the VLR and by 4888 the SGSN. 4889 VBS Group Indication 4890 Contains an indication (flag) which is used if all Group Ids shall be deleted from the subscriber data for the Voice 4891 Broadcast teleservice. 4892 If VBS is not supported in the VLR or no Group Ids are stored for VBS in the respective subscriber record, the request 4893 for deletion of all Group Ids shall be ignored. This parameter is used only by the VLR and if the SGSN receives this 4894 parameter it shall ignore it. 4895 VGCS Group Indication 4896 Contains an indication (flag) which is used if all Group Id's shall be deleted from the subscriber data for the Voice 4897 Group Call teleservice. This parameter is used only by the VLR and if the SGSN receives this parameter it shall ignore 4898 it. 4899 If VGCS is not supported in the VLR or no Group Ids are stored for VGCS in the respective subscriber record, the 4900 request for deletion of all Group Ids shall be ignored. 4901 GPRS Subscription Data Withdraw 4902 4903 4904 4905
555 Release 4 556 557
140
3GPP TS 29.002 V4.17.0 (2006-06)
This parameter is used to indicate whether all GPRS Subscription Data for the subscriber shall be deleted or if only a subset of the stored GPRS Subscription Data for the subscriber shall be deleted. In the latter case only those PDP contexts whose identifiers are included in the subsequent identifier list will be deleted. This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore it.
4906 Roaming Restricted In SGSN Due To Unsupported Feature 4907 This parameter is used if Roaming Restricted In SGSN Due To Unsupported Feature is deleted from the GPRS 4908 subscriber data. This may occur if unsupported features or services are removed from the GPRS subscriber data in the 4909 HLR. 4910 If this parameter is sent the SGSN shall check if the current Location Area is possibly allowed now. This parameter is 4911 used only by the SGSN and if the VLR receives this parameter it shall ignore it. 4912 LSA Information Withdraw 4913 4914 4915 4916
This parameter is used to indicate whether all LSA Information for the subscriber shall be deleted or if only a subset of the stored LSA Information for the subscriber shall be deleted. In the latter case only the LSA data whose LSA identities are included in the subsequent LSA data list will be deleted. This parameter is used by the VLR and the SGSN.
4917 IST Information Withdraw 4918 This parameter is used to indicate that the IST condition has been removed for the subscriber. See 3GPP TS 43.035 for 4919 the use of this parameter. 4920 Regional Subscription Response 4921 If included in the Delete Subscriber Data response this parameter indicates one of: 4922 4923
MSC Area Restricted; SGSN Area Restricted;
558
4924
559 Release 4 560 561
141
3GPP TS 29.002 V4.17.0 (2006-06)
Regional Subscription Not Supported.
4925 This parameter is used by the VLR and by the SGSN. 4926 GMLC List Withdraw 4927 This parameter indicates that the subscriber's LCS GMLC List shall be deleted from the VLR or SGSN. 4928 Subscribed Charging Characteristics Withdraw 4929 This parameter indicates that the Subscribed Charging Characteristics shall be replaced with a local default value in the 4930 SGSN (see 3GPP TS 32.215 [123]). 4931 This parameter is used only by the SGSN and if the VLR receives this parameter it shall ignore it. 4932 User error 4933 Only one of the following values is applicable: 4934 4935 4936
Unidentified subscriber; Data missing; Unexpected data value.
4937 4938 4939 8.9.1.1
8.9 Identity management services
8.9.1 MAP-PROVIDE-IMSI service
Definition
4940 This service is used by a VLR in order to get, via the MSC, the IMSI of a subscriber (e.g. when a subscriber has 4941 identified itself with a TMSI not allocated to any subscriber in the VLR). 4942 It is a confirmed service and consists of the primitives shown in table 8.9/1.
4943 8.9.1.2
4944
Service primitives
Table 8.9/1: MAP-PROVIDE-IMSI
Parameter name Invoke Id IMSI User error Provider error Request M Indication M(=) Response M(=) C C Confirm M(=) C(=) C(=) O
4945
4946 8.9.1.3
4948 IMSI
Parameter use
4947 All parameters are described in clause 7.6. The following clarifications are applicable:
4949 This parameter is received when the request is successfully carried out. It contains the requested IMSI. 4950 User error 4951 Only one of the following values is applicable: 4952
Absent subscriber.
4953
8.9.2 MAP-FORWARD-NEW-TMSI service
562
4954 8.9.2.1
563 Release 4 564 565
142
3GPP TS 29.002 V4.17.0 (2006-06)
Definition
4955 This service is used by a VLR to allocate, via MSC, a new TMSI to a subscriber during an ongoing transaction (e.g. call 4956 set-up, location updating or supplementary services operation). 4957 It is a confirmed service and consists of the primitives shown in table 8.9/2.
4958 8.9.2.2
4959
Service primitives
Table 8.9/2: MAP-FORWARD-NEW-TMSI
Parameter name Invoke Id TMSI Provider error Request M M Indication M(=) M(=) Response M(=) Confirm M(=) O
4960
4961 8.9.2.3
Parameter use
4962 The parameter TMSI is described in clause 7.6.
4963 4964 4965 8.10.1.1
8.10 Fault recovery services
8.10.1 MAP_RESET service
Definition
4966 This service is used by the HLR, after a restart, to indicate to a list of VLRs or SGSNs that a failure occurred. 4967 The MAP_RESET service is a non-confirmed service using the service primitives defined in table 8.10/1.
4968 8.10.1.2
4969
Service primitives
Table 8.10/1: MAP_RESET
Parameter name Invoke Id HLR number HLR Id LIST Request M M U Indication M(=) M(=) C(=)
4970
4971 8.10.1.3
4972 Invoke Id
Parameter definition and use
4973 See definition in clause 7.6.1. 4974 HLR number 4975 See definition in clause 7.6.2. 4976 HLR Id LIST 4977 4978 4979 4980
The HLR Id List is a list of HLR Ids. If the parameter is present in the indication, the VLR or SGSN may base the retrieval of subscribers to be restored on their IMSI: the subscribers affected by the reset are those whose IMSI leading digits are equal to one of these numbers. If the parameter is absent, subscribers to be restored are those for which the OriginatingEntityNumber received at location updating time matches the equivalent parameter of the Reset Indication.
4981
8.10.2 MAP_FORWARD_CHECK_SS_INDICATION service
566
4982 8.10.2.1
4983 4984 4985 4986 4987
567 Release 4 568 569
143
3GPP TS 29.002 V4.17.0 (2006-06)
Definition
This service may be used by an HLR as an implementation option, to indicate to a mobile subscriber that supplementary services parameters may have been altered, e.g. due to a restart. If received from the HLR, the VLR shall forward this indication to the MSC, which in turn forwards it to the MS. The HLR only sends this indication after successful completion of the subscriber data retrieval from HLR to VLR that ran embedded in a MAP_UPDATE_LOCATION procedure.
4988 The MAP_FORWARD_CHECK_SS_INDICATION service is a non-confirmed service using the service primitives 4989 defined in table 8.10/2.
4990 8.10.2.2
4991
Service primitives
Table 8.10/2: MAP_FORWARD_CHECK_SS_INDICATION
Parameter name Invoke Id Request M Indication M(=)
4992
4993 8.10.2.3
4994 Invoke Id
Parameter definition and use
4995 See definition in clause 7.6.1.
4996 4997 8.10.3.1
4998 4999 5000 5001
8.10.3 MAP_RESTORE_DATA service
Definition
This service is invoked by the VLR on receipt of a MAP_PROVIDE_ROAMING_NUMBER indication for an unknown IMSI, or for a known IMSI with the indicator "Confirmed by HLR" set to "Not confirmed". The service is used to update the LMSI in the HLR, if provided, and to request the HLR to send all data to the VLR that are to be stored in the subscriber's IMSI record.
5002 The MAP_RESTORE_DATA service is a confirmed service using the service primitives defined in table 8.10/3.
5003 8.10.3.2
5004
Service primitives
Table 8.10/3: MAP_RESTORE_DATA
Parameter name Invoke Id IMSI LMSI Supported CAMEL phases SoLSA Support Indicator IST Support Indicator Super-Charger Supported in Serving Network Entity Long FTN Supported Supported LCS Capability Sets HLR number MS Not Reachable Flag User error Provider error Request M M U C C C C C C Indication M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C C C C(=) C(=) C(=) O Response M(=) Confirm M(=)
5005
5006 8.10.3.3
5007 Invoke Id
Parameter definitions and use
570
5008 See definition in clause 7.6.1. 5009 IMSI 5010 See definition in clause 7.6.2. 5011 LMSI 5012 See definition in clause 7.6.2. It is an operator option to provide the LMSI from the VLR; it is mandatory for the HLR 5013 to support the LMSI handling procedures. 5014 Supported CAMEL Phases 5015 This parameter indicates which phases of CAMEL are supported. Must be present if a CAMEL phase different from 5016 phase 1 is supported. Otherwise may be absent. 5017 SoLSA Support Indicator 5018 This parameter is used by the VLR to indicate to the HLR in the Restore Data indication that SoLSA is supported. If 5019 this parameter is not included in the Restore Data indication then the HLR shall not perform any specific error handling. 5020 This SoLSA Support Indicator shall be stored by the HLR per VLR where there are Subscribers roaming. If a 5021 Subscriber is marked as only allowed to roam in Subscribed LSAs while roaming in a VLR and no SoLSA Support 5022 indicator is stored for that VLR, the location status of that Subscriber shall be set to Restricted. 5023 IST Support Indicator 5024 5025 5026 5027 5028 5029 5030 5031 5032 5033 5034
571 Release 4 572 573
144
3GPP TS 29.002 V4.17.0 (2006-06)
This parameter is used to indicate to the HLR that the VMSC supports basic IST functionality, that is, the VMSC is able to terminate the Subscriber Call Activity that originated the IST Alert when it receives the IST alert response indicating that the call(s) shall be terminated. If this parameter is not included in the Restore Data indication and the Subscriber is marked as an IST Subscriber, then the HLR may limit the service for the subscriber (by inducing an Operator Determined barring of Outgoing calls), or allow service assuming the associated risk of not having the basic IST mechanism available. This parameter can also indicate that the VMSC supports the IST Command service, including the ability to terminate all calls being carried for the identified subscriber by using the IMSI as a key. If this additional capability is not included in the Restore Data indication and the HLR supports the IST Command capability, then the HLR may limit the service for the subscriber (by inducing an Operator Determined barring of Outgoing calls), or allow service assuming the associated risk of not having the IST Command mechanism available.
5035 Long FTN Supported 5036 This parameter indicates that the VLR supports Long Forwarded-to Numbers. 5037 Super-Charger Supported in Serving Network Entity 5038 This parameter is used by the VLR to indicate to the HLR that the VLR supports the Super-Charger functionality and 5039 that subscriber data is required. 5040 If this parameter is absent then the VLR does not support the Super-Charger functionality. 5041 Supported LCS Capability Sets 5042 This parameter indicates, if present, the capability sets of LCS which are supported. If the parameter is sent but no 5043 capability set is marked as supported then the VLR does not support LCS at all. 5044 If this parameter is absent then the VLR may support at most LCS capability set 1, that is LCS Release98 or Release99 5045 version. 5046 HLR number 5047 See definition in clause 7.6.2. The presence of this parameter is mandatory in case of successful outcome of the service. 5048 MS Not Reachable Flag
574
5049 See definition in clause 7.6.8. This parameter shall be present in case of successful outcome of the service, if the "MS 5050 Not Reachable flag" was set in the HLR. 5051 User error 5052 In case of unsuccessful outcome of the service, an error cause shall be returned by the HLR. The following error causes 5053 defined in clause 7.6.1 may be used, depending on the nature of the fault: 5054 5055 5056 5057
575 Release 4 576 577
145
3GPP TS 29.002 V4.17.0 (2006-06)
unknown subscriber; system failure; unexpected data value; data missing.
5058 Provider error 5059 For definition of provider errors see clause 7.6.1.
5060 5061 5062 8.11.1.1
8.11 Subscriber Information services
8.11.1 MAP-ANY-TIME-INTERROGATION service
Definition
5063 This service is used by the gsmSCF, to request information (e.g. subscriber state and location) from the HLR or the 5064 GMLC at any time. 5065 When this service is used to the HLR, the subscriber state or location may be requested. 5066 When this service is used to the GMLC, only the location may be requested. 5067 The MAP-ANY-TIME-INTERROGATION service is a confirmed service using the service primitives defined in 5068 table 8.11/1.
5069 8.11.1.2
5070
Service primitives
Table 8.11/1: Any_Time_Interrogation
Parameter name Invoke id Requested Info gsmSCF-Address IMSI MSISDN Location Information Subscriber State User error Provider error Request M M M C C Indication M(=) M(=) M(=) C(=) C(=) Response M(=) Confirm M(=)
C C C
C(=) C(=) C(=) O
5071
5072 8.11.1.3
Parameter definition and use
5073 All parameters are described in clause 7.6. 5074 The HLR or GMLC may be able to use the value of the parameter gsmSCF-address to screen a 5075 MAP_Any_Time_Interrogation indication. 5076 The use of the parameters and the requirements for their presence are specified in 3GPP TS 23.078. 5077 User error
578
5078 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5079 5080 5081 5082 5083
579 Release 4 580 581
146
3GPP TS 29.002 V4.17.0 (2006-06)
System Failure; Any Time Interrogation Not Allowed; Data Missing; Unexpected Data Value; Unknown Subscriber.
5084 Provider error 5085 These are defined in clause 7.6.1.
5086 5087 8.11.2.1
8.11.2 MAP-PROVIDE-SUBSCRIBER-Info service
Definition
5088 This service is used to request information (e.g. subscriber state and location) from the VLR at any time. 5089 The MAP-PROVIDE-SUBSCRIBER-Info service is a confirmed service using the primitives defined in table 8.11/2.
5090 8.11.2.2
5091
Service primitives
Table 8.11/2: Provide_Subscriber_Information
Parameter name Invoke id Requested Info IMSI LMSI Location Information Subscriber State User error Provider error Request M M M U Indication M(=) M(=) M(=) O Response M(=) Confirm M(=)
C C C
C(=) C(=) C(=) O
5092
5093 8.11.2.3
Parameter definition and use
5094 All parameters are defined in clause 7.6. The use of these parameters and the requirements for their presence are 5095 specified in 3GPP TS 23.018 [97]. 5096 User error 5097 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5098 5099
Data Missing; Unexpected Data Value.
5100 Provider error 5101 These are defined in clause 7.6.1.
5102 5103 8.11.3.1
8.11.3 MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION service
Definition
5104 This service is used by the gsmSCF, to request subscription information (e.g. call forwarding supplementary service 5105 data or CSI) from the HLR at any time.
582
5106 8.11.3.2
5107
583 Release 4 584 585
147
3GPP TS 29.002 V4.17.0 (2006-06)
Service primitives
Table 8.11/3: Any_Time_Subscription_Interrogation
Parameter name Invoke id Requested Subscription Info GsmSCF-Address IMSI MSISDN Long FTN Supported Call Forwarding Data Call Barring Data ODB Info CAMEL Subscription Info Supported CAMEL phases in VLR Supported CAMEL phases in SGSN User error Provider error
Request M M M C C C
Indication M(=) M(=) M(=) C(=) C(=) C(=)
Response M(=)
Confirm M(=)
C C C C C C C
C(=) C(=) C(=) C(=) C(=) C(=) C(=) O
5108
5109 8.11.3.3
Parameter definition and use
5110 All parameters are described in clause 7.6. 5111 The HLR may be able to use the value of the parameter gsmSCF-address to screen a 5112 MAP_Any_Time_Subscription_Interrogation indication. 5113 The use of the parameters and the requirements for their presence are specified in 3GPP TS 23.078. 5114 User error 5115 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5116 5117 5118 5119 5120 5121 5122 5123 5124 5125
Unexpected Data Value; Unknown Subscriber; BearerServiceNotProvisioned; TeleserviceNotProvisioned; CallBarred; IllegalSS-Operation; SS-NotAvailable; InformationNotAvailable; Any Time Subscription Interrogation Not Allowed; Data Missing.
5126 Provider error 5127 These are defined in clause 7.6.1.
5128 5129 8.11.4.1
8.11.4 MAP-ANY-TIME-MODIFICATION service
Definition
5130 This service is used by the gsmSCF, to modify information of the HLR at any time.
586
5131 8.11.4.2
5132
587 Release 4 588 589
148
3GPP TS 29.002 V4.17.0 (2006-06)
Service primitives
Table 8.11/4: Any_Time_Modification
Parameter name Invoke id gsmSCF-Address IMSI MSISDN Modification request for SS information Modification request for CSI Long FTN Supported Ext Forwarding information-for-CSE Ext Call barring information-for-CSE CAMEL subscription info User error Provider error
Request M M C C C C C
Indication M(=) M(=) C(=) C(=) C(=) C(=) C(=)
Response M(=)
Confirm M(=)
C C C C
C(=) C(=) C(=) C(=) O
5133
5134 8.11.4.3
Parameter definition and use
5135 All parameters are described in clause 7.6. 5136 The HLR may be able to use the value of the parameter gsmSCF-address to screen a MAP_Any_Time_Modification 5137 indication. 5138 The use of these parameters and the requirements for their presence are specified in 3GPP TS 23.078. 5139 User error 5140 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5141 5142 5143 5144 5145 5146 5147 5148 5149 5150 5151 5152 5153 5154
Any Time Modification Not Allowed; Data Missing; Unexpected Data Value; Unknown Subscriber; Bearer service not provisioned; This error is returned only if not even a subset of the requested bearer service group has been subscribed to;
Teleservice not provisioned; This error is returned only if not even a subset of the requested teleservice group has been subscribed to;
Call Barred; Illegal SS operation; SS error status; SS incompatibility; SS subscription violation; Information Not Available.
5155 Provider error 5156 These are defined in clause 7.6.1.
5157
8.11.5 MAP-NOTE-SUBSCRIBER-DATA-MODIFIED service
590
591 Release 4 592 593
149
3GPP TS 29.002 V4.17.0 (2006-06)
8.11.5.1
Definition
This service is used by the HLR to inform the gsmSCF that subscriber data have been modified.
8.11.5.2
Service primitives
Table 8.11/5: Note_Subscriber_Data_Modified
Parameter name Invoke id IMSI MSISDN Ext Forwarding information-for-CSE Ext Call barring information-for-CSE ODB Info CAMEL subscription info All Information Sent User error Provider error Request M M M C C C C C Indication M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C C(=) O Response M(=) Confirm M(=)
8.11.5.3
Invoke id
Parameter definition and use
See clause 7.6.1 for the use of this parameter. IMSI See clause 7.6.2 for the use of this parameter. MSISDN See clause 7.6.2 for the use of this parameter. Ext Forwarding information-for-CSE See clause 7.6.3 for the use of this parameter. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078. Ext Call barring information-for-CSE See clause 7.6.3 for the use of this parameter. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078. ODB Info See clause 7.6.3 for the use of this parameter. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078. CAMEL subscription info See clause 7.6.3 for the use of this parameter. The use of this parameter and the requirements for their presence are specified in 3GPP TS 23.078.
5158 All Information Sent 5159 This parameter is set when the HLR has sent all information to gsmSCF.
User error
594
595 Release 4 596 597
150
3GPP TS 29.002 V4.17.0 (2006-06)
This parameter is sent by the responder when an error is detected and if present, takes one of the following values: Data Missing; Unexpected Data Value; Unknown Subscriber.
5160 5161 5162
Provider error These are defined in clause 7.6.1. The use of the parameters and the requirements for their presence are specified in 3GPP TS 23.078.
5163 5164 5165
9 Operation and maintenance services
9.1 Subscriber tracing services
9.1.1 MAP-ACTIVATE-TRACE-MODE service
Definition
5166 9.1.1.1
5167 This service is used between the HLR and the VLR to activate subscriber tracing in the VLR. 5168 Also this service is used between the HLR and the SGSN to activate subscriber tracing in the SGSN. 5169 The MAP-ACTIVATE-TRACE-MODE service is a confirmed service using the primitives from table 9.1/1.
5170 9.1.1.2
5171
Service primitives
Table 9.1/1: MAP-ACTIVATE-TRACE-MODE
Parameter name Invoke id IMSI Trace reference Trace type OMC Id User error Provider error Request M C M M U Indication M(=) C(=) M(=) M(=) C(=) Response M(=) Confirm M(=)
C(=) O
5172
5173 9.1.1.3
5174 Invoke id
Parameter use
5175 See definition in clause 7.6.1. 5176 IMSI 5177 See definition in clause 7.6.2. The IMSI is a mandatory parameter in a stand-alone operation. 5178 Trace reference 5179 See definition in clause 7.6.10. 5180 Trace type 5181 See definition in clause 7.6.10.
598
5182 OMC Id
599 Release 4 600 601
151
3GPP TS 29.002 V4.17.0 (2006-06)
5183 See definition in clause 7.6.2. The use of this parameter is an operator option. 5184 User error 5185 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 5186 5187 5188 5189 5190 5191
Unidentified Subscriber; Facility Not Supported; Tracing Buffer Full; System Failure; Unexpected Data Value; Data missing.
5192 Provider error 5193 For definition of provider errors see clause 7.6.1.
5194 5195 9.1.2.1
9.1.2 MAP-DEACTIVATE-TRACE-MODE service
Definition
5196 This service is used between the VLR and the HLR for deactivating subscriber tracing in the VLR. 5197 Also this service is used between the SGSN and the HLR for deactivating subscriber tracing in the SGSN. 5198 The MAP-DEACTIVATE-TRACE-MODE service is a confirmed service using the primitives from table 9.1/2.
5199 9.1.2.2
5200
Service primitives
Table 9.1/2: MAP-DEACTIVATE-TRACE-MODE
Parameter name Invoke id IMSI Trace reference User error Provider error Request M C M Indication M(=) C(=) M(=) Response M(=) C Confirm M(=) C(=) O
5201
5202 9.1.2.3
5203 Invoke id
Parameter use
5204 See definition in clause 7.6.1. 5205 IMSI 5206 See definition in clause 7.6.2. The IMSI is a mandatory parameter in a stand-alone operation. 5207 Trace reference 5208 See definition in clause 7.6.10. 5209 User error 5210 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 5211
Unidentified Subscriber;
602
5212 5213 5214 5215
603 Release 4 604 605
152
3GPP TS 29.002 V4.17.0 (2006-06)
Facility Not Supported; System Failure; Unexpected Data Value; Data missing.
5216 Provider error 5217 For definition of provider errors see clause 7.6.1.
5218 5219 9.1.3.1
9.1.3 MAP-TRACE-SUBSCRIBER-ACTIVITY service
Definition
5220 This service is used between the VLR and the MSC to activate the subscriber tracing in the MSC. 5221 The MAP-TRACE-SUBSCRIBER-ACTIVITY service is a non-confirmed service using the primitives from table 9.1/3.
5222 9.1.3.2
5223
Service primitives
Table 9.1/3: MAP-TRACE-SUBSCRIBER-ACTIVITY
Parameter name Invoke id IMSI Trace reference Trace type OMC Id Request M C M M U Indication M(=) C(=) M(=) M(=) C(=)
5224
5225 9.1.3.3
5226 Invoke id
Parameter use
5227 See definition in clause 7.6.1. 5228 IMSI 5229 See definition in clause 7.6.2. The controlling MSC shall provide either the IMSI or the IMEI to the servicing MSC. 5230 Trace reference 5231 See definition in clause 7.6.10. 5232 Trace type 5233 See definition in clause 7.6.10. 5234 OMC Id 5235 See definition in clause 7.6.2. The use of this parameter is an operator option.
5236 5237 5238 9.2.1.1
9.2 Other operation and maintenance services
9.2.1 MAP-SEND-IMSI service
Definition
606
5239 This service is used by a VLR in order to fetch the IMSI of a subscriber in case of some Operation & Maintenance 5240 procedure where subscriber data are needed in the Visited PLMN and MSISDN is the only subscriber's identity known. 5241 It is a confirmed service and consists of the primitives shown in table 9.2/1.
607 Release 4 608 609
153
3GPP TS 29.002 V4.17.0 (2006-06)
5242 9.2.1.2
5243
Service primitives
Table 9.2/1: MAP-SEND-IMSI
Parameter name Invoke Id MSISDN IMSI User error Provider error Request M M Indication M(=) M(=) Response M(=) C C Confirm M(=) C(=) C(=) O
5244
5245 9.2.1.3
5247 User error
Parameter use
5246 All parameters are described in clause 7.6. The following clarifications are applicable.
5248 Only one of the following values is applicable: 5249 5250 5251
Unknown subscriber; Unexpected data value; Data missing.
5252 5253 5254
10
Call handling services
10.1 MAP_SEND_ROUTING_INFORMATION service
10.1.1 Definition
5255 This service is used between the Gateway MSC and the HLR. The service is invoked by the Gateway MSC to perform 5256 the interrogation of the HLR in order to route a call towards the called MS. 5257 This is a confirmed service using the primitives listed in table 10.1/1. 5258 This service is also used between the GMSC and the NPLR.
5259
5260
10.1.2 Service primitives
Table 10.1/1: MAP_SEND_ROUTING_INFORMATION parameters
Parameter name Invoke Id Interrogation Type GMSC Address MSISDN OR Interrogation OR Capability CUG Interlock CUG Outgoing Access Number of Forwarding Network Signal Info Supported CAMEL Phases Request M M M M C C C C C C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) C C C Confirm M(=) C(=) C(=) C(=)
610
611 Release 4 612 613
154 Request C C C C C C C C C C C C C Indication C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=)
3GPP TS 29.002 V4.17.0 (2006-06) Response Confirm
Parameter name Suppress T-CSI Suppression of Announcement Call Reference Number Forwarding Reason Basic Service Group Alerting Pattern CCBS Call Supported CCBS Phase Additional Signal Info IST Support Indicator Pre-paging supported Call Diversion Treatment Indicator Long FTN Supported IMSI MSRN Forwarding Data Forwarding Interrogation Required VMSC address GMSC Camel Subscription Info Location Information Subscriber State Basic Service Code CUG Subscription Flag North American Equal Access preferred Carrier Id User error SS-List CCBS Target Keep CCBS Call Indicator IST Alert Timer Number Portability Status Provider error
C C C C C C C C C C U C U C C C U
C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) O
5261
5262
10.1.3 Parameter use
a conditional parameter whose use is defined only in 3GPP TS 23.078 shall be absent if the sending entity does not support CAMEL; a conditional parameter whose use is defined only in 3GPP TS 23.079 [99] shall be absent if the sending entity does not support optimal routeing; a conditional parameter whose use is defined only in 3GPP TS 23.078 & 3GPP TS 23.079 [99] shall be absent if the sending entity supports neither CAMEL nor optimal routeing.
5263 See clause 7.6 for a definition of the parameters used in addition to the following. Note that: 5264 5265 5266 5267 5268 5269
5270 Interrogation Type 5271 See 3GPP TS 23.079 [99] for the use of this parameter. 5272 GMSC address 5273 The E.164 address of the GMSC. 5274 MSISDN 5275 This is the Mobile Subscriber ISDN number assigned to the called subscriber. In the Request & Indication it is the 5276 number received by the GMSC in the IAM. If the call is to be forwarded and the HLR supports determination of the 5277 redirecting number, the HLR inserts the basic MSISDN in the Response. 5278 See 3GPP TS 23.066 [108] for the use of this parameter and the conditions for its presence in the response. 5279 OR Interrogation 5280 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence.
614
5281 OR Capability 5282 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5283 CUG Interlock 5284 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5285 CUG Outgoing Access 5286 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5287 Number of Forwarding 5288 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5289 Network Signal Info 5290 See 3GPP TS 23.018 [97] for the conditions for the presence of the components of this parameter. 5291 Supported CAMEL Phases 5292 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5293 T-CSI Suppression 5294 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5295 Suppression Of Announcement 5296 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5297 Call Reference Number 5298 The use of this parameter and the conditions for its presence are specified in 3GPP TS 23.078 [98] and 3GPP TS 23.079 5299 [99]. 5300 Forwarding Reason 5301 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5302 Basic Service Group 5303 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5304 Alerting Pattern 5305 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5306 CCBS Call 5307 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5308 Supported CCBS Phase 5309 This parameter indicates by its presence that CCBS is supported and the phase of CCBS which is supported. 5310 Additional Signal Info 5311 See 3GPP TS 23.081 [27] for the conditions for the presence of the components of this parameter. 5312 IST Support Indicator 5313 5314 5315 5316
615 Release 4 616 617
155
3GPP TS 29.002 V4.17.0 (2006-06)
This parameter is used to indicate to the HLR that the GMSC supports basic IST functionality, that is, the GMSC is able to terminate the subscriber call activity that originated the IST Alert when it receives the IST Alert response indicating that the call(s) shall be terminated. If this parameter is not included in the Send Routing Information indication and the subscriber is marked as an IST subscriber, then the HLR may limit the service for the call (by barring the incoming call
618
5317 if it is not subject to forwarding, or suppressing Call Forwarding from the GMSC), or allow the call assuming the 5318 associated risk of not having the basic IST mechanism available. 5319 5320 5321 5322 5323 5324
619 Release 4 620 621
156
3GPP TS 29.002 V4.17.0 (2006-06)
This parameter can also indicate that the GMSC supports the IST Command, including the ability to terminate all calls being carried for the identified subscriber by using the IMSI as a key. If this additional capability is not included in the Send Routing Information indication and the subscriber is marked as an IST subscriber, then the HLR may limit the service for the subscriber (by barring the incoming calls if they are not subject to forwarding, or suppressing Call Forwarding from the GMSC), or allow the incoming calls assuming the associated risk of not having the IST Command mechanism available.
5325 Pre-paging supported 5326 See 3GPP TS 23.018 for the use of this parameter and the conditions for its presence. 5327 Call Diversion Treatment Indicator 5328 This parameter indicates whether or not call diversion is allowed. 5329 IMSI 5330 See 3GPP TS 23.018 [97] and 3GPP TS 23.066 [108] for the use of this parameter and the conditions for its presence. 5331 MSRN 5332 See 3GPP TS 23.018 [97], 3GPP TS 23.066 [108] and 3GPP TS 23.079 [99] for the use of this parameter and the 5333 conditions for its presence. If the NPLR returns only the MSISDN-number without Routeing Number to the GMSC, the 5334 MSISDN-number shall be returned as MSRN. 5335 Forwarding Data 5336 This parameter includes a number to define the forwarded-to destination, the forwarding reason and the forwarding 5337 options Notification to calling party and Redirecting presentation, and can include the forwarded-to subaddress. See 5338 3GPP TS 23.018 [97] and 3GPP TS 23.079 [99] for the conditions for the presence of its components. 5339 Forwarding Interrogation Required 5340 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5341 Long FTN Supported 5342 This parameter indicates that the GMSC supports Long Forwarded-to Numbers. 5343 VMSC address 5344 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5345 GMSC CAMEL Subscription Info 5346 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5347 Location Information 5348 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5349 Subscriber State 5350 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5351 CUG Subscription Flag 5352 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5353 North American Equal Access preferred Carrier Id 5354 This parameter is returned to indicate the preferred carrier identity to be used to set-up the call (i.e. forwarding the call 5355 or establishing the roaming leg).
622
5356 SS-List 5357 5358 5359 5360
623 Release 4 624 625
157
3GPP TS 29.002 V4.17.0 (2006-06)
This parameter includes SS-codes and will be returned as an operator option. The HLR shall not send PLMN-specific SS-codes across PLMN boundaries. However if the GMSC receives PLMN-specific SS-codes from a foreign PLMN's HLR the GMSC may ignore it. If the GMSC attempts to process the PLMN- specific SS- codes, this may lead to unpredictable behaviour but the GMSC shall continue call processing.
5361 Basic Service Code 5362 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5363 5364 5365 5366 5367
If the CAMEL service is not involved, this parameter includes the basic service code and will be returned as an operator option. The HLR shall not send a PLMN-specific Basic Service Code across PLMN boundaries. However if the GMSC receives a PLMN-specific Basic Service Code from a foreign PLMN's HLR the GMSC may ignore it. If the GMSC attempts to process the PLMN specific Basic Service codes, this may lead to unpredictable behaviour but the GMSC shall continue call processing.
5368 CCBS Target 5369 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5370 Keep CCBS Call Indicator 5371 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5372 IST Alert Timer 5373 It includes the IST Alert timer value that must be used to inform the HLR about the call activities that the subscriber 5374 performs. This parameter is only sent to the GMSC in response to a Send Routing Information request which indicates 5375 the the GMSC supports IST. 5376 Number Portability Status 5377 This parameter indicates the number portability status of the subscriber. This parameter may be present if the sender of 5378 SRIack is NPLR. 5379 User error 5380 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5381 5382 5383 5384 5385 5386 5387 5388 5389 5390 5391 5392 5393 5394 5395
Unknown Subscriber; The diagnostic for the Unknown Subscriber error may indicate NPDB Mismatch.
Number changed; Call Barred; This error will indicate that either incoming calls are barred for this MS or that calls are barred due to Operator Determined Barring (see 3GPP TS 22.041 [8] for a definition of this network feature);
CUG Reject; The value of this error cause will indicate the reason for CUG Reject;
Bearer Service Not Provisioned; Teleservice Not Provisioned; A subscription check has been performed and the call has not passed the check due to incompatibility with regard to the requested service. Depending on the nature of the incompatibility, either of these messages will be returned;
Facility Not Supported; Absent Subscriber;
626
5396 5397 5398 5399 5400 5401 5402 5403 5404 5405 5406 5407 5408 5409 5410 5411 5412 5413 5414
627 Release 4 628 629
158
3GPP TS 29.002 V4.17.0 (2006-06)
This indicates that the location of the MS is not known (either the station is not registered and there is no location information available or the Provide Roaming Number procedure fails due to IMSI detached flag being set), or the GMSC requested forwarding information with a forwarding reason of not reachable, and the call forwarding on MS not reachable service is not active; Busy Subscriber; This indicates that Call Forwarding on Busy was not active for the specified basic service group when the GMSC requested forwarding information with a forwarding reason of busy; The error may also indicate that the subscriber is busy due to an outstanding CCBS recall. In the error data it may then be specified that CCBS is possible for the busy encountered call;
No Subscriber Reply; This indicates that Call Forwarding on No Reply was not active for the specified basic service group when the GMSC requested forwarding information with a forwarding reason of no reply;
OR Not Allowed; This indicates that the HLR is not prepared to accept an OR interrogation from the GMSC, or that calls to the specified subscriber are not allowed to be optimally routed;
Forwarding Violation; System Failure; Data Missing; Unexpected Data Value.
5415 See clause 7.6 for a definition of these errors. 5416 Provider error 5417 These are defined in clause 7.6.
5418 5419
10.2 MAP_PROVIDE_ROAMING_NUMBER service
10.2.1 Definition
5420 This service is used between the HLR and VLR. The service is invoked by the HLR to request a VLR to send back a 5421 roaming number to enable the HLR to instruct the GMSC to route an incoming call to the called MS. 5422 This is a confirmed service which uses the primitives described in table 10.2/1.
5423
5424
10.2.2 Service primitives
Table 10.2/1: MAP_PROVIDE_ROAMING_NUMBER parameters
Parameter name Invoke Id IMSI MSC Number MSISDN LMSI GSM Bearer Capability Network Signal Info Suppression Of Announcement Call Reference Number GMSC Address OR Interrogation OR Not Supported in GMSC Request M M M U C C C C C C C C Indication M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)
630
631 Release 4 632 633
159 Request C C C C C C Indication C(=) C(=) C(=) C(=) C(=) C(=) C C
3GPP TS 29.002 V4.17.0 (2006-06) Response Confirm
Parameter name Alerting Pattern CCBS Call Supported CAMEL Phases in GMSC Additional Signal Info Pre-paging supported Long FTN Supported Roaming Number User error Provider error
C(=) C(=) O
5425
5426
10.2.3 Parameter use
a conditional parameter whose use is defined only in 3GPP TS 23.078 shall be absent if the sending entity does not support CAMEL; a conditional parameter whose use is defined only in 3GPP TS 23.079 [99] shall be absent if the sending entity does not support optimal routeing; a conditional parameter whose use is defined only in 3GPP TS 23.078 & 3GPP TS 23.079 [99] shall be absent if the sending entity supports neither CAMEL nor optimal routeing.
5427 See clause 7.6 for a definition of the parameters used, in addition to the following. Note that: 5428 5429 5430 5431 5432 5433
5434 IMSI 5435 This is the IMSI of the called Subscriber. 5436 MSC Number 5437 This is the ISDN number assigned to the MSC currently serving the MS. The MSC number will have been stored in the 5438 HLR as provided at location updating. 5439 MSISDN 5440 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5441 LMSI 5442 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5443 GSM Bearer Capability 5444 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5445 This information is passed according to the rules specified in TS 3GPP TS 29.007 [56]. 5446 There may be two GSM Bearer Capabilities supplied. 5447 Network Signal Info 5448 See 3GPP TS 23.018 [97] for the conditions for the presence of the components of this parameter. 5449 Suppression Of Announcement 5450 The use of this parameter and the requirements for its presence are specified in 3GPP TS 23.078. 5451 Call Reference Number 5452 The use of this parameter and the conditions for its presence are specified in 3GPP TS 23.078 [98] and 3GPP TS 23.079 5453 [99]. 5454 GMSC Address
634
5455 The use of this parameter and the conditions for its presence are specified in 3GPP TS 23.078 [98] and 3GPP TS 23.079 5456 [99]. 5457 OR Interrogation 5458 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5459 OR Not Supported in GMSC 5460 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5461 Supported CAMEL Phases in GMSC 5462 See 3GPP TS 23.078 [98] for the use of this parameter and the conditions for its presence. 5463 Alerting Pattern 5464 See 3GPP TS 23.078 [98] for the use of this parameter and the conditions for its presence. 5465 CCBS Call 5466 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5467 Additional Signal Info 5468 See 3GPP TS 23.081 [27] for the conditions for the presence of the components of this parameter. 5469 Pre-paging supported 5470 See 3GPP TS 23.018 for the use of this parameter and the conditions for its presence. 5471 Long FTN supported 5472 See 3GPP TS 23.082 for the use of this parameter and the conditions for its presence. 5473 Roaming Number 5474 See 3GPP TS 23.018 [97] for the use of this parameter and the conditions for its presence. 5475 User error 5476 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5477 5478 5479 5480 5481 5482 5483 5484 5485 5486
635 Release 4 636 637
160
3GPP TS 29.002 V4.17.0 (2006-06)
Absent Subscriber; This error will be returned if the IMSI detach flag is set.
No Roaming Number Available; OR Not Allowed; This indicates that the MAP_PROVIDE_ROAMING_NUMBER indication included the OR interrogation indicator, but the VLR does not support optimal routeing.
Facility Not Supported; System Failure; Data Missing; Unexpected Data Value.
5487 See clause 7.6 for a definition of these reasons. 5488 Provider error 5489 These are defined in clause 7.6.
638
639 Release 4 640 641
161
3GPP TS 29.002 V4.17.0 (2006-06)
5490 5491
10.3 MAP_RESUME_CALL_HANDLING service
10.3.1 Definition
5492 This service is used between the terminating VMSC and the GMSC. The service is invoked by the terminating VMSC 5493 to request the GMSC to resume handling the call and forward it to the specified destination. 5494 This is a confirmed service which uses the Primitives listed in table 10.3/1.
5495
5496
10.3.2 Service primitives
Table 10.3/1: MAP_RESUME_CALL_HANDLING parameters
Parameter name Invoke Id Call Reference Number Basic Service Group IMSI Forwarding Data CUG Interlock CUG Outgoing Access O-CSI D-CSI CCBS Target UU Data UUS CF Interaction All Information Sent MSISDN User error Provider error Request M C C C C C C C C C C C C C Indication M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)
C(=) O
5497
5498
10.3.3 Parameter use
5499 Information received in subsequent segment of a segmented dialogue shall not overwrite information received in an 5500 earlier segment. 5501 See clause 7.6 for a definition of the parameters used, in addition to the following. 5502 Call Reference Number 5503 See 3GPP TS 23.079 [99] for the use of this parameter. This parameter shall be present in a first segment of the 5504 dialogue. 5505 Basic Service Group 5506 See 3GPP TS 23.079 [99] for the use of this parameter. This parameter shall be present in a first segment of the 5507 dialogue. 5508 IMSI 5509 This is the IMSI of the forwarding Subscriber. This parameter shall be present in a first segment of the dialogue. 5510 Forwarding Data 5511 5512 5513 5514
This parameter includes a number to define the forwarded-to destination, the forwarding reason and the forwarding options Notification to calling party and Redirecting presentation, and can include the forwarded-to subaddress. See 3GPP TS 23.079 [99] for the conditions for the presence of its components. This parameter shall be present in a first segment of the dialogue.
5515 CUG Interlock
642
5516 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5517 CUG Outgoing Access 5518 See 3GPP TS 23.079 [99] for the use of this parameter and the conditions for its presence. 5519 O-CSI 5520 See 3GPP TS 23.078 for the use of this parameter and the conditions for its presence. 5521 For CAMEL phases 1 & 2, the O-CSI shall contain only one set of O-BCSM TDP data. 5522 D-CSI 5523 The Dialled Services-CSI. 5524 See 3GPP TS 23.078 for the use of this parameter and the conditions for its presence. 5525 CCBS Target 5526 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5527 UU Data 5528 See 3GPP TS 23.087 for the use of this parameter and the conditions for its presence. 5529 UUS CF Interaction 5530 See 3GPP TS 23.087 for the use of this parameter and the conditions for its presence. 5531 All Information Sent 5532 This parameter is set when the VMSC has sent all information to GMSC. 5533 MSISDN 5534 This parameter is the basic MSISDN of the forwarding subscriber. It shall be present if the VMSC supports 5535 determination of the redirecting number. 5536 User error 5537 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5538 5539 5540 5541
643 Release 4 644 645
162
3GPP TS 29.002 V4.17.0 (2006-06)
Optimal Routeing not allowed; Forwarding failed; Unexpected Data Value; Data Missing.
5542 Provider error 5543 These are defined in clause 7.6.
5544 5545
10.4 MAP_PREPARE_GROUP_CALL service
10.4.1 Definition
5546 This service is used by the Anchor_MSC to inform the Relay_MSC about a group call set-up. 5547 The MAP_PREPARE_GROUP_CALL service is a confirmed service using the service primitives given in table 10.4/1.
646
5548
647 Release 4 648 649
163
3GPP TS 29.002 V4.17.0 (2006-06)
10.4.2 Service primitives
Table 10.4/1: MAP_PREPARE_GROUP_CALL service
Request M M M M C C C M M Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) M(=) M(=) Response M(=) Confirm M(=)
5549
Parameter name Invoke Id Teleservice ASCI Call Reference Ciphering Algorithm Group Key Number Group Key Priority CODEC-Information Uplink Free Indicator Group Call Number User Error Provider Error
M C
M(=) C(=) O
5550
5551
5552 Invoke Id
10.4.3 Parameter definitions and use
5553 See definition in clause 7.6.1. 5554 Teleservice 5555 Voice Broadcast Service or Voice Group Call Service. 5556 ASCI Call Reference 5557 Broadcast call reference or group call reference. This item is used to access the VBS-GCR or VGCS-GCR within the 5558 Relay_MSC. 5559 Ciphering Algorithm 5560 The ciphering algorithm to be used for the group call. 5561 Group Key Number 5562 This number has to be broadcasted and is used by the mobile station to select the chosen group key. 5563 Shall be present if the ciphering applies. 5564 Group Key 5565 This key is used for ciphering on the radio interface. 5566 Shall be present if the ciphering applies. 5567 Priority 5568 Default priority level related to the call if eMLPP applies. 5569 CODEC-Information 5570 Information on the codecs allowed for this call. 5571 Uplink Free Indicator 5572 A flag indicating whether the call is initiated from a dispatcher. 5573 Group Call Number 5574 This temporary allocated E.164 number is used for routing the call from the Anchor MSC to the Relay MSC.
650
5575 User Error 5576 For definition of this parameter see clause 7.6.1 The following errors defined in clause 7.6.1 may be used, depending on 5577 the nature of the fault: 5578 5579 5580
651 Release 4 652 653
164
3GPP TS 29.002 V4.17.0 (2006-06)
No Group Call Number available; System Failure; Unexpected Data Value.
5581 Provider Error 5582 See definition of provider error in clause 7.6.1.
5583 5584 5585
10.5 MAP_PROCESS_GROUP CALL_SIGNALLING service
10.5.1 Definitions
5586 This service is used between Relay MSC and Anchor MSC for transmission of Group Call notifications. 5587 The MAP_PROCESS_GROUP_CALL_SIGNALLING service is a non-confirmed service using the service primitives 5588 given in table 10.5/1.
5589
5590
10.5.2 Service primitives
Table 10.5/1: MAP_PROCESS_GROUP_CALL_SIGNALLING service
Parameter name Invoke Id Uplink Request Uplink Release Indication Release Group Call Request M C C C Indication M(=) C(=) C(=) C(=)
5591
5592
5593 Invoke Id
10.5.3 Parameter definitions and use
5594 See definition in clause 7.6.1 5595 Uplink Request 5596 This information element indicates to the anchor MSC that a service subscriber roaming in the relay MSC area requests 5597 access to the uplink. 5598 Uplink Release Indication 5599 This information element if included by the Relay MSC indicates to the Anchor MSC that the uplink has become free. 5600 Release Group Call 5601 This information element if included by the Relay MSC indicates to the Anchor MSC that the service subscriber who 5602 has initiated the call and who currently has access to the uplink terminates the call.
5603 5604
10.6 MAP_FORWARD_GROUP_CALL_SIGNALLING service
654
5605
655 Release 4 656 657
165
3GPP TS 29.002 V4.17.0 (2006-06)
10.6.1 Definitions
5606 This service is used between Anchor MSC and Relay MSC for transmission of Group Call notifications. 5607 The MAP_FORWARD_GROUP_CALL_SIGNALLING service is a non-confirmed service using the service 5608 primitives given in table 10.6/1.
5609
5610
10.6.2 Service primitives
Table 10.6/1: MAP_FORWARD_GROUP_CALL_SIGNALLING service
Parameter name Invoke Id IMSI Uplink Request Acknowledgement Uplink Release Indication Uplink Reject Command Uplink Seized Command Uplink Release Command State Attributes Request M C C C C C C C Indication M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=)
5611
5612
5613 IMSI
10.6.3 Parameter definitions and use
5614 Identity of the service subscriber who has established the call and who is allowed to terminate the call. 5615 Invoke Id 5616 See definition in clause 7.6.1. 5617 Uplink Request Acknowledgement 5618 This information element is used for positive acknowledgement of an uplink request. 5619 Uplink Release Indication 5620 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink has become free. 5621 Uplink Reject Command 5622 This information element is used for negative acknowledgement of an uplink request. 5623 Uplink Seized Command 5624 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink is no longer free. 5625 Uplink Release Command 5626 This information element if included by the Anchor MSC indicates to the Relay MSC that the uplink which is granted 5627 to a MS in the relay MSC area shall be released. 5628 State Attributes 5629 This information element is used to allow service logic running in an Anchor MSC to mute a VGCS talker even when 5630 the talker is served on a Relay MSC. The IE is used to build a GCC message that provides a mechanism to induce the 5631 VGCS talker terminal to mute/unmute the downlink at the Anchor MSC, as defined in 3GPP TS 44.068.
5632
10.7 MAP_SEND_GROUP_CALL_END_SIGNAL service
658
5633
659 Release 4 660 661
166
3GPP TS 29.002 V4.17.0 (2006-06)
10.7.1 Definitions
5634 This service is used between the Relay MSC and the Anchor MSC indicating that VGCS / VBS channels have been 5635 established in the Relay MSC area. The response is used by the Anchor MSC to inform the Relay MSC that all 5636 resources for the call can be released in the Relay MSC because the call has been released in the Anchor MSC. 5637 The MAP_SEND_GROUP_CALL_END_SIGNAL service is a confirmed service using the service primitives given in 5638 table 10.7/1.
5639
5640
10.7.2 Service primitives
Table 10.7/1: MAP_SEND_GROUP_CALL_END_SIGNAL service
Parameter name Invoke Id IMSI Provider Error Request M C Indication M(=) C(=) Response M(=) Confirm M(=) O
5641
5642
5643 IMSI
10.7.3 Parameter definitions and use
5644 Identity of the service subscriber who has established the call and who is allowed to terminate the call. 5645 Shall be present if the call was established by a service subscriber roaming in the relay MSC area. 5646 Invoke Id 5647 See definition in clause 7.6.1 5648 Provider Error 5649 See definition of provider error in clause 7.6.1.
5650 5651
10.8 MAP_Provide_SIWFS_Number
10.8.1 Definition
5652 This service is used between an MSC and SIWFS. It is invoked by an MSC receiving an incoming call (call to or from 5653 MS) to request the SIWFS to allocate IWU resources. The service is defined in GSM 03.54. 5654 This is a confirmed service using the primitives described in table 10.8/1.
5655
5656
10.8.2 Service primitive
Table 10.8/1: MAP_Provide_SIWFS_Number service
Parameter name Invoke ID GSM Bearer Capability ISDN Bearer Capability Call Direction B-subscriber address Chosen Channel Lower Layer Compatibility High Layer Compatibility SIWFS number User error Provider error Request M M M M M M C C Indication M(=) M(=) M(=) M(=) M(=) M(=) C(=) C(=) Response M(=) Confirm M(=)
C C
C(=) C(=) O
662
5657
663 Release 4 664 665
167
3GPP TS 29.002 V4.17.0 (2006-06)
5658
10.8.3 Parameter use
5659 See clause 7.6 for a definition of the parameters used, in addition to the following. 5660 GSM Bearer Capability 5661 This information is the result from the negotiation with the mobile station. The information is sent from the MSC to the 5662 SIWFS to allocate the correct IWU. 5663 ISDN Bearer Capability 5664 5665 5666 5667
This parameter refers to the ISDN Bearer Capability information element. For the MTC this parameter is received in the ISUP User Service Information parameter. For the MOC call this parameter is mapped from the GSM BC parameter according to 3GPP TS 29.007 [56]. The parameter is used by the SIWFS to route the call and to allocate the outgoing circuit.
5668 Call Direction 5669 This parameter indicates the direction of the call (mobile originated or mobile terminated) at call set-up. 5670 B-subscriber address 5671 5672 5673 5674
This parameter is sent from the MSC to the SIWFS to inform the SIWFS where to route the call i.e. where to send the IAM. If the loop method is used this parameter will indicate the address to the VMSC. This address is allocated by the VMSC in the same way as a MSRN and is used to correlate the incoming IAM to the corresponding MAP dialogue. If the non-loop method is used this parameter will indicate the address to the B-subscriber.
5675 Chosen Channel 5676 This parameter is sent from the MSC to the SIWFS to adjust the interworking unit to the assigned radio resources. This 5677 parameter is defined in 3GPP TS 48.008 [49]. 5678 Lower Layer Compatibility 5679 This parameter is sent from the MSC to the SIWF to allow the interworking unit to perform a compatibility check. This 5680 parameter is handled as specified in 3GPP TS 29.007 [56]. This parameter is defined in 3GPP TS 24.008 [35]. 5681 High Layer Compatibility 5682 This parameter is sent from the MSC to the SIWF to allow the interworking unit to perform a compatibility check. This 5683 parameter is handled as specified in 3GPP TS 29.007 [56]. This parameter is defined in 3GPP TS 24.008 [35]. 5684 SIWFS number 5685 5686 5687 5688
This parameter is sent from the SIWFS to the MSC. This address is used by the visited MSC to route the call, i.e. the IAM to the SIWFS (similar to MSRN) and will be used by the SIWFS to correlate the incoming IAM to the corresponding MAP message. This parameter must always be sent from the SIWFS when a successful allocation of SIWFS resources has been made.
5689 User error 5690 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5691 5692 5693 5694
Resource limitation; Facility Not Supported; Unexpected Data Value; System Failure.
5695 See clause 7.6 for a definition of these reasons. 5696 Provider error
666
5697 These are defined in clause 7.6.
667 Release 4 668 669
168
3GPP TS 29.002 V4.17.0 (2006-06)
5698 5699
10.9 MAP_SIWFS_Signalling_Modify
10.9.1 Definition
5700 This service is used to transport signalling information between an MSC and an SIWFS in the case of a request to 5701 modify the configuration (e.g. HSCSD). It is invoked either by an MSC or by the SIWFS. The service is defined in 5702 GSM 03.54. 5703 This is a confirmed service using the primitives described in table 10.9/1.
5704
5705
10.9.2 Service primitive
Table 10.9/1: MAP_SIWFS_Signalling_Modify service
Parameter name Invoke ID Channel Type Chosen Channel User error Provider error Request M C C Indication M(=) C(=) C(=) Response M(=) C(=) C Confirm M(=) C(=) C(=) O
5706
5707
10.9.3 Parameter use
5708 See clause 7.6 for a definition of the parameter used, in addition to the following. 5709 Channel Type 5710 This parameter is the result of a Channel Mode Modification for TS61/62. It contains the changed Air Interface User 5711 Rate. The information is sent from the SIWFS to the MSC to assign the correct radio resource. This parameter is 5712 defined in 3GPP TS 48.008 [49]. 5713 Chosen Channel 5714 This parameter is sent from the MSC to the SIWFS to adjust the interworking unit to the assigned radio resources. This 5715 parameter is defined in 3GPP TS 48.008 [49]. 5716 User error 5717 This parameter is sent by the responder when an error is detected and if present , takes one of the following values: 5718 5719 5720 5721 5722
Resource limitation; Facility Not Supported; Data Missing; Unexpected Data Value; System Failure.
5723 See clause 7.6 for a definition of these reasons. 5724 Provider error 5725 These are defined in clause 7.6.
670
671 Release 4 672 673
169
3GPP TS 29.002 V4.17.0 (2006-06)
5726 5727
10.10 MAP_SET_REPORTING_STATE service
10.10.1 Definition
5728 This service is used between the HLR and the VLR to set the reporting state for a requested service. It is a confirmed 5729 service using the service primitives shown in table 10.10/1.
5730
5731
10.10.2 Service primitives
Table 10.10/1: MAP_SET_REPORTING_STATE parameters
Parameter name Invoke id IMSI LMSI CCBS Monitoring CCBS Subscriber Status User error Provider error Request M C C C Indication M(=) C(=) C(=) C(=) Response M(=) Confirm M(=)
C C
C(=) C(=) O
5732
5733
10.10.3 Parameter use
5734 See clause 7.6 for a definition of the parameters used, in addition to the following. 5735 IMSI 5736 The IMSI is a mandatory parameter if the service is used as the only one in a dialogue. 5737 CCBS Monitoring 5738 This parameter indicates whether monitoring for CCBS shall be started or stopped. If it indicates that monitoring shall 5739 be started this service corresponds to the message 'Start Reporting' in 3GPP TS 23.093 [107]; if it indicates that 5740 monitoring shall be stopped this service corresponds to the message 'Stop Reporting' in 3GPP TS 23.093 [107]. 5741 CCBS Subscriber Status 5742 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5743 User error 5744 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5745 values defined in clause 7.6.1: 5746 5747 5748 5749 5750 5751 5752
System Failure; Unidentified Subscriber; Unexpected Data Value; Data Missing; Resource Limitation; Facility Not Supported. This error is reserved for future use.
NOTE:
5753 Provider error 5754 These are defined in clause 7.6.
674
675 Release 4 676 677
170
3GPP TS 29.002 V4.17.0 (2006-06)
5755 5756
10.11 MAP_STATUS_REPORT service
10.11.1 Definition
5757 This service is used by the VLR to report an event or call outcome to the HLR. It is a confirmed service using the 5758 service primitives shown in table 10.11/1.
5759
5760
10.11.2 Service primitives
Table 10.11/1: MAP_STATUS_REPORT parameters
Parameter name Invoke id IMSI CCBS Subscriber Status Monitoring Mode Call Outcome User error Provider error Request M M C C C Indication M(=) M(=) C(=) C(=) C(=) Response M(=) Confirm M(=)
C(=) O
5761
5762
10.11.3 Parameter use
5763 See clause 7.6 for a definition of the parameters used, in addition to the following. 5764 CCBS Subscriber Status 5765 If this parameter is present without Monitoring Mode and Call Outcome this service corresponds to the message 'Event 5766 Report' in 3GPP TS 23.093 [107]. See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its 5767 presence. 5768 Monitoring Mode 5769 If this parameter is present with CCBS Call Outcome this service corresponds to the message 'CCBS Call Report' in 5770 3GPP TS 23.093 [107]. See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5771 Call Outcome 5772 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5773 User error 5774 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5775 values defined in clause 7.6.1: 5776 5777 5778 5779
Unknown Subscriber; System Failure; Unexpected Data Value; Data Missing.
5780 Provider error 5781 These are defined in clause 7.6.
678
679 Release 4 680 681
171
3GPP TS 29.002 V4.17.0 (2006-06)
5782 5783
10.12 MAP_REMOTE_USER_FREE service
10.12.1 Definition
5784 This service is used between the HLR and the VLR to report that the B subscriber is now idle and that the A subscriber 5785 can be notified. It is a confirmed service using the service primitives shown in table 10.12/1.
5786
5787
10.12.2 Service primitives
Table 10.12/1: MAP_REMOTE_USER_FREE parameters
Parameter name Invoke id IMSI Call Info CCBS Feature Translated B Number Replace B Number Alerting Pattern RUF Outcome User error Provider error Request M M M M M C C Indication M(=) M(=) M(=) M(=) M(=) C(=) C(=) Response M(=) Confirm M(=)
C C
C(=) C(=) O
5788
5789
10.12.3 Parameter use
5790 See clause 7.6 for a definition of the parameters used, in addition to the following. 5791 Call Info 5792 See 3GPP TS 23.093 [107] for the use of this parameter. 5793 CCBS Feature 5794 See 3GPP TS 23.093 [107] for the conditions for the presence of the parameters included in the CCBS feature. 5795 Translated B Number 5796 See 3GPP TS 23.093 [107] for the use of this parameter. 5797 Replace B Number 5798 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5799 Alerting Pattern 5800 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5801 RUF Outcome 5802 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 5803 User error 5804 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5805 values defined in clause 7.6.1: 5806 5807 5808
Unexpected Data Value; Data Missing; Incompatible Terminal;
682
5809 5810 5811 5812 5813
683 Release 4 684 685
172
3GPP TS 29.002 V4.17.0 (2006-06)
This error is returned by the responder when the terminal used for CCBS activation is not compatible with the terminal used for the CCBS recall. For details refer to 3GPP TS 24.008 [35]; Absent Subscriber (IMSI Detach; Restricted Area; No Page Response); System Failure; Busy Subscriber (CCBS Busy).
5814 Provider error 5815 These are defined in clause 7.6.
5816 5817
10.13 MAP_IST_ALERT service
10.13.1 Definition
5818 This service is used between the MSC (Visited MSC or Gateway MSC) and the HLR, to report that the IST timer 5819 running for a call for the Subscriber has expired. It is a confirmed service using the service primitives shown in 5820 table 10.13/1.
5821
5822
10.13.2 Service primitives
Table 10.13/1: MAP_IST_ALERT parameters
Parameter name Invoke Id IMSI IST Alert Timer IST Information Withdraw Call termination Indicator User error Provider error Request M M Indication M(=) M(=) Response M(=) C C C C Confirm M(=) C(=) C(=) C(=) C(=) O
5823
5824
10.13.3 Parameter use
5825 All parameters are described in clause 7.6. The following clarifications are applicable: 5826 IST Alert Timer 5827 If included in the IST Alert response, it includes the new IST Alert timer value that must be used to inform the HLR 5828 about the call activities that the subscriber performs. 5829 IST Information Withdraw 5830 If included in the IST Alert response, this parameter is used to indicate that the IST condition has been removed for the 5831 subscriber. When the MSC receives this parameter, IST control for that call shall be terminated. 5832 Call termination Indicator 5833 5834 5835 5836 5837
If included in the IST Alert response, this parameter is used to indicate whether the MSC shall terminate the call activity that had previously triggered the IST Alert procedure, or it shall also release all other call activities for the specified subscriber (outgoing call activities if the IST Alert is initiated by the VMSC, or incoming call activities if the IST Alert is initiated by the GMSC). Release of all other call activities is possible only if the MSC has the capability to link the call activities for the Subscriber by using the IMSI as key.
5838 User error 5839 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5840
System Failure;
686
5841 5842 5843 5844
687 Release 4 688 689
173
3GPP TS 29.002 V4.17.0 (2006-06)
Unexpected Data Value; Resource Limitation; Facility Not Supported; Unknown Subscriber.
5845 5846
10.14 MAP_IST_COMMAND service
10.14.1 Definition
5847 This service is used by the HLR to instruct the MSC (Visited MSC or Gateway MSC) to terminate ongoing call 5848 activities for a specific subscriber. It is a confirmed service using the service primitives shown in table 10.14/1.
5849
5850
10.14.2 Service primitives
Table 10.14/1: MAP_IST_COMMAND parameters
Parameter name Invoke Id IMSI User error Provider error Request M M Indication M(=) M(=) Response M(=) C Confirm M(=) C(=) O
5851
5852
10.14.3 Parameter use
5853 All parameters are described in clause 7.6. The following clarifications are applicable: 5854 User error 5855 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 5856 5857 5858 5859 5860
System Failure; Unexpected Data Value; Resource Limitation; Facility Not Supported; Unknown Subscriber.
5861 5862 5863
11
Supplementary services related services
11.1 MAP_REGISTER_SS service
11.1.1 Definition
5864 This service is used between the MSC and the VLR and between the VLR and the HLR to register data related to a 5865 supplementary service. The VLR will relay the message to the HLR. 5866 The service is a confirmed service and uses the service primitives shown in table 11.1./1.
690
5867
691 Release 4 692 693
174
3GPP TS 29.002 V4.17.0 (2006-06)
11.1.2 Service primitives
Table 11.1/1: MAP_REGISTER_SS parameters
Request M M C C C C C C Indication M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)
5868
Parameter name Invoke id SS-Code Basic service Forwarded-to number with subaddress No reply condition time EMLPP default priority Long FTN Supported NbrUser Forwarding information User error Provider error
C C C C
C(=) C(=) C(=) C(=) O
5869
5870
5871 Invoke id
11.1.3 Parameter use
5872 See clause 7.6.1 for the use of this parameter. 5873 SS-Code 5874 This parameter indicates the supplementary service which the mobile subscriber wants to register. 5875 Basic service 5876 This parameter indicates for which basic service group the supplementary service is to be registered. If it is not 5877 included, the registration request applies to all basic services. 5878 Forwarded-to number with subaddress 5879 This parameter is obligatory if the registration applies to one or more call forwarding supplementary services. It can 5880 optionally include a sub-address. 5881 No reply condition time 5882 This parameter is included if the registration applies to the Call Forwarding on No Reply supplementary service (or a 5883 superset of this service) and the mobile subscriber supplies a value for this time. 5884 EMLPP default priority 5885 This parameter is sent by the initiator to register the eMLPP default priority level and is returned by the responder at 5886 successful outcome of the service. 5887 Long FTN Supported 5888 This parameter indicates that the mobile station supports Long Forwarded-to Numbers. 5889 NbrUser 5890 This parameter is sent by the initiator to register the MC maximum number of user defined circuit switched bearers to 5891 be used. 5892 Forwarding information 5893 This parameter is returned by the responder at successful outcome of the service, if the registration request concerned 5894 one or a group of Call Forwarding supplementary services.
694
5895 User error
695 Release 4 696 697
175
3GPP TS 29.002 V4.17.0 (2006-06)
5896 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5897 values defined in clause 7.6.1: 5898 5899 5900 5901 5902 5903 5904 5905 5906 5907 5908
System failure; Data missing; Unexpected data value; Call Barred; Bearer service not provisioned; This error is returned only if not even a subset of the requested bearer service group has been subscribed to; Teleservice not provisioned; This error is returned only if not even a subset of the requested teleservice group has been subscribed to;
Illegal SS operation; SS error status; SS incompatibility.
5909 Provider error 5910 See clause 7.6.1 for the use of this parameter.
5911 5912
11.2 MAP_ERASE_SS service
11.2.1 Definition
5913 This service is used between the MSC and the VLR and between the VLR and the HLR to erase data related to a 5914 supplementary service. The VLR will relay the message to the HLR. 5915 The service is a confirmed service and uses the service primitives shown in table 11.2/1.
5916
5917
11.2.2 Service primitives
Table 11.2/1: MAP_ERASE_SS parameters
Parameter name Invoke id SS-Code Basic service Forwarding information User error Provider error Request M M C Indication M(=) M(=) C(=) Response M(=) Confirm M(=)
C C
C(=) C(=) O
5918
5919
5920 Invoke id
11.2.3 Parameter use
5921 See clause 7.6.1 for the use of this parameter. 5922 SS-Code 5923 This parameter indicates the supplementary service which the mobile subscriber wants to erase.
698
5924 Basic service 5925 This parameter indicates for which basic service group the supplementary service should be erased. If it is not included, 5926 the erasure request applies to all basic services. 5927 Forwarding information 5928 This parameter is returned by the responder at successful outcome of the service, if the erasure request concerned one or 5929 a group of Call Forwarding supplementary services. 5930 User error 5931 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5932 values, defined in clause 7.6.1: 5933 5934 5935 5936 5937 5938 5939 5940 5941 5942
699 Release 4 700 701
176
3GPP TS 29.002 V4.17.0 (2006-06)
System failure; Data Missing; Unexpected data value; Bearer service not provisioned; This error is returned only if not even a subset of the requested bearer service group has been subscribed to;
Teleservice not provisioned; This error is returned only if not even a subset of the requested teleservice group has been subscribed to;
Call Barred; Illegal SS operation; SS error status.
5943 Provider error 5944 See clause 7.6.1 for the use of this parameter.
5945 5946
11.3 MAP_ACTIVATE_SS service
11.3.1 Definition
5947 This service is used between the MSC and the VLR and between the VLR and the HLR to activate a supplementary 5948 service. The VLR will relay the message to the HLR. 5949 The service is a confirmed service and uses the service primitives shown in table 11.3/1.
5950
5951
11.3.2 Service primitives
Table 11.3/1: MAP_ACTIVATE_SS parameters
Parameter name Invoke id SS-Code Long FTN Supported Basic service Forwarding information Call barring information SS-Data User error Provider error Request M M C C Indication M(=) M(=) C(=) C(=) Response M(=) Confirm M(=)
C C C C
C(=) C(=) C(=) C(=) O
5952
702
5953
703 Release 4 704 705
177
3GPP TS 29.002 V4.17.0 (2006-06)
11.3.3 Parameter use
5954 Invoke id 5955 See clause 7.6.1 for the use of this parameter. 5956 SS-Code 5957 This parameter indicates the supplementary service which the mobile subscriber wants to activate. 5958 Basic service 5959 This parameter indicates for which basic service groups the requested supplementary service(s) should be activated. If it 5960 is not included, the activation request applies to all basic services. 5961 Forwarding information 5962 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned 5963 Call Forwarding. 5964 Long FTN Supported 5965 This parameter indicates that the mobile station supports Long Forwarded-to Numbers. 5966 Call barring information 5967 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned 5968 Call Barring. 5969 SS-Data 5970 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned for 5971 example Call Waiting. 5972 User error 5973 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 5974 values, defined in clause 7.6.1: 5975 5976 5977 5978 5979 5980 5981 5982 5983 5984 5985 5986 5987 5988
System failure; Data Missing; Unexpected data value; Bearer service not provisioned; This error is returned only if not even a subset of the requested bearer service group has been subscribed to. Teleservice not provisioned; This error is returned only if not even a subset of the requested teleservice group has been subscribed to. Call Barred; Illegal SS operation; SS error status; SS subscription violation; SS incompatibility; Negative PW check; Number Of PW Attempts Violation.
706
5989 Provider error 5990 See clause 7.6.1 for the use of this parameter.
707 Release 4 708 709
178
3GPP TS 29.002 V4.17.0 (2006-06)
5991 5992
11.4 MAP_DEACTIVATE_SS service
11.4.1 Definitions
5993 This service is used between the MSC and the VLR and between the VLR and the HLR to deactivate a supplementary 5994 service. The VLR will relay the message to the HLR. 5995 The service is a confirmed service and uses the service primitives shown in table 11.4/1.
5996
5997
11.4.2 Service primitives
Table 11.4/1: MAP_DEACTIVATE_SS parameters
Parameter name Invoke id SS-Code Basic service Forwarding information Call barring information SS-Data User error Provider error Request M M C Indication M(=) M(=) C(=) Response M(=) Confirm M(=)
C C C C
C(=) C(=) C(=) C(=) O
5998
5999
6000 Invoke id
11.4.3 Parameter use
6001 See clause 7.6.1 for the use of this parameter. 6002 SS-Code 6003 This parameter indicates the supplementary service which the mobile subscriber wants to deactivate. 6004 Basic service 6005 This parameter indicates for which basic service group the requested supplementary service(s) should be deactivated. If 6006 it is not included the deactivation request applies to all basic services. 6007 Forwarding information 6008 This parameter is returned by the responder at successful outcome of the service, if the deactivation request concerned 6009 one or a group of Call Forwarding supplementary services. 6010 Call barring information 6011 This parameter is returned by the responder at successful outcome of the service, if the activation request concerned one 6012 or a group of Call Barring supplementary services. 6013 SS-Data 6014 This parameter is returned by the responder at successful outcome of the service, for example if the deactivation request 6015 concerned the Call Waiting supplementary service.
710
6016 User error
711 Release 4 712 713
179
3GPP TS 29.002 V4.17.0 (2006-06)
6017 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6018 values, defined in clause 7.6.1: 6019 6020 6021 6022 6023 6024 6025 6026 6027 6028 6029 6030 6031
System failure; Data Missing; Unexpected data value; Bearer service not provisioned; This error is returned only if not even a subset of the requested bearer service group has been subscribed to;
Teleservice not provisioned; This error is returned only if not even a subset of the requested teleservice group has been subscribed to;
Call Barred; Illegal SS operation; SS error status; SS subscription violation; Negative PW check; Number Of PW Attempts Violation.
6032 Provider error 6033 See clause 7.6.1 for the use of this parameter.
6034 6035
11.5 MAP_INTERROGATE_SS service
11.5.1 Definitions
6036 This service is used between the MSC and the VLR and between the VLR and the HLR to retrieve information related 6037 to a supplementary service. The VLR will relay the message to the HLR if necessary. 6038 The service is a confirmed service and consists of four service primitives.
6039
11.5.2 Service primitives
Table 11.5/1: MAP_INTERROGATE_SS parameters
Parameter name Invoke id SS-Code Basic service Long FTN Supported SS-Status Basic service Group LIST Forwarding feature LIST CLI restriction Info EMLPP Info MC Information CCBS Feature LIST User error Provider error Request M M C C Indication M(=) M(=) C(=) C(=) Response M(=) Confirm M(=)
6040 The service primitives are shown in table 11.5/1. 6041
C C C C C C C C
C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) O
714
6042
715 Release 4 716 717
180
3GPP TS 29.002 V4.17.0 (2006-06)
6043
11.5.3 Parameter use
6044 For additional information on parameter use refer to the GSM 04.8x and 04.9x-series of technical specifications. 6045 Invoke id 6046 See clause 7.6.1 for the use of this parameter. 6047 SS-Code 6048 The mobile subscriber can only interrogate a single supplementary service per service request. 6049 Basic service 6050 This parameter indicates for which basic service group the given supplementary service is interrogated. If it is not 6051 included, the interrogation request applies to all basic services. 6052 SS-Status 6053 This parameter is included by the responder if: 6054 6055 6056 6057 6058
the interrogated supplementary service can only be subscribed for all applicable basic services simultaneously; or the interrogated supplementary service is not active for any of the interrogated basic services, or the interrogation was for the CCBS supplementary service and no CCBS request is active or the service is not provisioned.
6059 Basic service group LIST 6060 This parameter LIST is used to include one or a series of basic service groups for which the interrogated supplementary 6061 service is active. If the interrogated supplementary service is not active for any of the interrogated (and provisioned) 6062 basic service groups, the SS-Status parameter is returned. 6063 Long FTN Supported 6064 This parameter indicates that the mobile station supports Long Forwarded-to Numbers. 6065 Forwarding feature LIST 6066 The forwarding feature parameter is described in clause 7.6.4. A list of one or more forwarding features is returned by 6067 the responder when the interrogation request applied to Call Forwarding supplementary service. 6068 If no basic service code parameter is provided within this sequence, the forwarding feature parameter applies to all 6069 provisioned basic services. 6070 CLI restriction Info 6071 The CLI-RestrictionInfo parameter is returned by the responder when the interrogation request applies to the CLIR 6072 supplementary service. 6073 EMLPP Info 6074 The eMLPP info (maximum entitled priority and default priority) is returned by the responder if the interrogation 6075 request applies to the eMLPP supplementary service. 6076 MC Information 6077 The MC information (NbrSB, NbrUser and NbrSN) is returned by the responder if the interrogation request applies to 6078 the MC supplementary service. For a definition of these 3 components, refer to 3GPP TS 23.135 and 3GPP TS 24.135.
718
6079 CCBS Feature LIST 6080 The CCBS feature parameter is described in clause 7.6. A list of one or more CCBS features is returned by the 6081 responder when the interrogation request applied to the CCBS supplementary service. See 3GPP TS 23.093 [107] for 6082 the conditions for the presence of the parameters included in the CCBS feature. 6083 User error 6084 This error is sent by the responder upon unsuccessful outcome of the interrogation service, and then takes one of the 6085 following values, defined in clause 7.6.1: 6086 6087 6088 6089 6090 6091 6092 6093 6094 6095
719 Release 4 720 721
181
3GPP TS 29.002 V4.17.0 (2006-06)
System failure; Data Missing; Unexpected data value; Bearer Service not provisioned; This error is returned only if not even a subset of the interrogated bearer services are provided;
Teleservice not provisioned; This error is returned only if not even a subset of the interrogated teleservices are provided;
Call Barred; Illegal SS operation; SS not available.
6096 Provider error 6097 See clause 7.6.1 for the use of this parameter.
6098 6099
11.6 MAP_INVOKE_SS service
11.6.1 Definitions
6100 This service is used between the MSC and the VLR to check the subscriber's subscription to a given supplementary 6101 service in the VLR, in connection with in-call invocation of that supplementary service, i.e. after the call set-up phase is 6102 finished. For supplementary service invocation during call set-up phase, please refer to the call handling descriptions. 6103 The service is a confirmed service and consists of four service primitives.
6104
11.6.2 Service primitives
Table 11.6/1: MAP_INVOKE_SS parameters
Parameter name Invoke id SS-Code Basic service User error Provider error Request M M C Indication M(=) M(=) C(=) Response M(=) C Confirm M(=) C(=) O
6105 The service primitives are shown in table 11.6/1. 6106
6107
722
6108
723 Release 4 724 725
182
3GPP TS 29.002 V4.17.0 (2006-06)
11.6.3 Parameter use
6109 Invoke id 6110 See clause 7.6.1 for the use of this parameter. 6111 SS-Code 6112 This SS-Code can only refer to a single supplementary service, e.g. the Call Hold or Multi Party supplementary 6113 services. 6114 Basic service 6115 This parameter indicates for which basic service the supplementary service invocation is required. 6116 User error 6117 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6118 values: 6119 6120 6121 6122 6123 6124 6125
System Failure; Data Missing; Unexpected data value; Call Barred; Illegal SS operation; SS error status; SS not available.
6126 Provider error 6127 See clause 7.6.1 for the use of this parameter.
6128 6129
11.7 MAP_REGISTER_PASSWORD service
11.7.1 Definitions
6130 This service is used between the MSC and the VLR and between the VLR and the HLR if the mobile subscriber 6131 requests to register a new password. The VLR will relay the message to the HLR. 6132 The service is a confirmed service and consists of four service primitives.
6133
11.7.2 Service primitives
Table 11.7/1: MAP_REGISTER_PASSWORD parameters
Parameter name Invoke id SS-Code New password User error Provider error Request M M Indication M(=) M(=) Response M(=) C C Confirm M(=) C(=) C(=) O
6134 The service primitives are shown in table 11.7/1. 6135
6136
726
6137
727 Release 4 728 729
183
3GPP TS 29.002 V4.17.0 (2006-06)
11.7.3 Parameter use
6138 Invoke id 6139 See clause 7.6.1 for the use of this parameter. 6140 SS-Code 6141 This parameter indicates for which supplementary service(s) the password should be registered. 6142 New Password 6143 See clause 7.6.4 for the use of this parameter. 6144 User error 6145 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6146 values, defined in clause 7.6.1: 6147 6148 6149 6150 6151 6152 6153 6154
System failure; Data Missing; Unexpected data value; Call Barred; SS subscription violation; Password registration failure; Negative PW check; Number Of PW Attempts Violation.
6155 Provider error 6156 See clause 7.6.1 for the use of this parameter.
6157 6158
11.8 MAP_GET_PASSWORD service
11.8.1 Definitions
6159 This service is used between the HLR and the VLR and between the VLR and the MSC when the HLR receives a 6160 request from the mobile subscriber for an operation on a supplementary service which requires a password from the 6161 subscriber. The VLR will relay the message to the MSC. 6162 The service is a confirmed service and uses the service primitives shown in table 11.8/1.
6163
6164
11.8.2 Service primitives
Table 11.8/1: MAP_GET_PASSWORD parameters
Parameter name Invoke id Linked id Guidance info Current password Provider error Request M C M Indication M(=) C(=) M(=) Response M(=) Confirm M(=)
M(=) O
6165
730
6166
731 Release 4 732 733
184
3GPP TS 29.002 V4.17.0 (2006-06)
11.8.3 Parameter use
6167 Invoke id 6168 See clause 7.6.1 for the use of this parameter. 6169 Linked Id 6170 See clause 7.6.1 for the use of this parameter. If the MAP_GET_PASSWORD service is used in conjunction with the 6171 MAP_REGISTER_PASSWORD service, this parameter must be present; otherwise it must be absent. 6172 Guidance info 6173 See clause 7.6.4 for the use of this parameter. 6174 Current password 6175 See clause 7.6.4 for the use of this parameter. 6176 Provider error 6177 See clause 7.6.1 for the use of this parameter.
6178 6179 6180
11.9 MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service
11.9.1 Definitions
6181 This service is used between the MSC and the VLR, between the VLR and the HLR, between the HLR and gsmSCF 6182 and between the HLR and HLR to relay information in order to allow unstructured supplementary service operation. 6183 The MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service is a confirmed service using the primitives from 6184 table 11.9/1.
6185
6186
11.9.2 Service primitives
Table 11.9/1: MAP_PROCESS_UNSTRUCTURED_SS_REQUEST parameters
Parameter name Invoke id USSD Data Coding Scheme USSD String MSISDN User error Provider error Request M M M U Indication M(=) M(=) M(=) C(=) Response M(=) C C C Confirm M(=) C(=) C(=) C(=) O
6187
6188
6189 Invoke id
11.9.3 Parameter use
6190 See clause 7.6.1 for the use of this parameter. 6191 USSD Data Coding Scheme 6192 See clause 7.6.4 for the use of this parameter. The presence of the parameter in the response is dependent on the 6193 unstructured supplementary service application. If this parameter is present, then the USSD String parameter has to be 6194 present.
734
6195 USSD String 6196 See clause 7.6.1 for the use of this parameter. The presence of the parameter in the response is dependent on the 6197 unstructured supplementary service application. If this parameter is present, then the USSD Data Coding Scheme 6198 parameter has to be present. 6199 MSISDN 6200 The subscribers basic MSISDN. 6201 See definition in clause 7.6.2. The MSISDN is included as an operator option, e.g. to allow addressing the subscribers 6202 data in the gsmSCF with the MSISDN. 6203 User error 6204 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6205 values defined in clause 7.6.1: 6206 6207 6208 6209 6210 6211
735 Release 4 736 737
185
3GPP TS 29.002 V4.17.0 (2006-06)
System failure; Data missing; Unexpected data value; This error is returned by the responder if it is not able to deal with the contents of the USSD string.
Call Barred; Unknown Alphabet.
6212 Provider error 6213 See clause 7.6.1 for the use of this parameter.
6214 6215
11.10 MAP_UNSTRUCTURED_SS_REQUEST service
11.10.1 Definitions
6216 This service is used between the gsmSCF and the HLR, the HLR and the VLR and between the VLR and the MSC 6217 when the invoking entity requires information from the mobile user, in connection with unstructured supplementary 6218 service handling. 6219 The MAP_UNSTRUCTURED_SS_REQUEST service is a confirmed service using the primitives from table 11.10/1.
6220
6221
11.10.2 Service primitives
Table 11.10/1: MAP_UNSTRUCTURED_SS_REQUEST parameters
Parameter name Invoke id USSD Data Coding Scheme USSD String Alerting Pattern User error Provider error Request M M M C Indication M(=) M(=) M(=) C(=) Response M(=) C C C Confirm M(=) C(=) C(=) C(=) O
6222
6223
6224 Invoke id
11.10.3 Parameter use
6225 See clause 7.6.1 for the use of this parameter.
738
6226 USSD Data Coding Scheme 6227 See clause 7.6.4 for the use of this parameter. The presence of the parameter in the response is dependent on the mobile 6228 user's MMI input. If this parameter is present, then the USSD String parameter has to be present. 6229 USSD String 6230 See clause 7.6.1 for the use of this parameter. The presence of the parameter in the response is dependent on the mobile 6231 user's MMI input. If this parameter is present, then the USSD Data Coding Scheme parameter has to be present. 6232 Alerting Pattern 6233 See clause 7.6.3 for the use of this parameter. 6234 User error 6235 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6236 values defined in clause 7.6.1: 6237 6238 6239 6240 6241 6242 6243 6244 6245 6246 6247
739 Release 4 740 741
186
3GPP TS 29.002 V4.17.0 (2006-06)
System failure; Data missing; Unexpected data value; This error is returned by the responder if it is not able to deal with the contents of the USSD string;
Absent Subscriber; Illegal Subscriber; This error indicates that delivery of the unstructured supplementary service data failed because the MS failed authentication;
Illegal Equipment; USSD Busy; Unknown Alphabet.
6248 Provider error 6249 See clause 7.6.1 for the use of this parameter.
6250 6251
11.11 MAP_UNSTRUCTURED_SS_NOTIFY service
11.11.1 Definitions
6252 This service is used between the gsmSCF and the HLR, the HLR and the VLR and between the VLR and the MSC 6253 when the invoking entity requires a notification to be sent to the mobile user, in connection with unstructured 6254 supplementary services handling. 6255 The MAP_UNSTRUCTURED_SS_NOTIFY service is a confirmed service using the primitives from table 11.11/1.
742
6256
743 Release 4 744 745
187
3GPP TS 29.002 V4.17.0 (2006-06)
11.11.2 Service primitives
Table 11.11/1: MAP_UNSTRUCTURED_SS_NOTIFY parameters
Request M M M C Indication M(=) M(=) M(=) C(=) Response M(=) Confirm M(=)
6257
Parameter name Invoke id USSD Data Coding Scheme USSD String Alerting Pattern User error Provider error
C(=) O
6258
6259
6260 Invoke id
11.11.3 Parameter use
6261 See clause 7.6.1 for the use of this parameter. 6262 USSD Data Coding Scheme: 6263 See clause 7.6.4 for the use of this parameter. 6264 USSD String: 6265 See clause 7.6.1 for the use of this parameter. 6266 Alerting Pattern 6267 See clause 7.6.3 for the use of this parameter. 6268 User error 6269 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6270 values defined in clause 7.6.1: 6271 6272 6273 6274 6275 6276 6277 6278 6279 6280 6281
System failure; Data missing; Unexpected data value; This error is returned by the responder if it is not able to deal with the contents of the USSD string.
Absent Subscriber; Illegal Subscriber; This error indicates that delivery of the unstructured supplementary service data failed because the MS failed authentication.
Illegal Equipment; USSD Busy; Unknown Alphabet.
6282 Provider error 6283 See clause 7.6.1 for the use of this parameter.
746
747 Release 4 748 749
188
3GPP TS 29.002 V4.17.0 (2006-06)
6284 6285
11.12 MAP_SS_INVOCATION_NOTIFY
11.12.1 Definition
6286 This service is used between the MSC and the gsmSCF when the subscriber invokes one of the following 6287 supplementary services; Call Deflection (CD), Explicit Call Transfer (ECT) or Multi Party (MPTY). 6288 This service is used between the HLR and the gsmSCF when the subscriber invokes the CCBS supplementary service.
6289
11.12.2 Service primitives
Table 11.12/1: SS_INVOCATION_NOTIFY parameters
Parameter name Invoke id MSISDN IMSI SS- event SS- event data B-subscriber Number CCBS Request State User error Provider error Request M M M M C C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) Response M(=) Confirm M(=)
6290 The service primitives are shown in table 11.12/1. 6291
C(=) O
6292
6293
11.12.3 Parameter use
6294 All parameters are described in clause 7.6. The use of these parameters and the requirements for their presence are 6295 specified in 3GPP TS 23.078. 6296 User error 6297 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6298 6299 6300
Data Missing; Unexpected Data Value; Unknown Subscriber.
6301 Provider error 6302 This is defined in clause 7.6.1.
6303 6304
11.13 MAP_REGISTER_CC_ENTRY service
11.13.1 Definition
6305 This service is used between the MSC and the VLR and between the VLR and the HLR to register data for a requested 6306 call completion supplementary service. The VLR will relay the message to the HLR. 6307 The service is a confirmed service and uses the service primitives shown in table 11.13/1.
750
6308
751 Release 4 752 753
189
3GPP TS 29.002 V4.17.0 (2006-06)
11.13.2 Service primitives
Table 11.13/1: MAP_REGISTER_CC_ENTRY parameters
Parameter name Invoke id SS Code CCBS Feature Translated B number Service Indicator Call Info Network Signal Info User error Provider error Request M M C C C C C Indication M(=) M(=) C(=) C(=) C(=) C(=) C(=) Response M(=) C Confirm M(=) C(=)
6309
C(=) O
6310
6311
11.13.3 Parameter use
6312 See clause 7.6 for a definition of the parameters used, in addition to the following. 6313 SS-Code 6314 This parameter indicates the call completion supplementary service for which the mobile subscriber wants to register an 6315 entry. 6316 CCBS Feature 6317 See 3GPP TS 23.093 [107] for the conditions for the presence of the parameters included in the CCBS feature. 6318 Translated B Number 6319 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6320 Service Indicator 6321 This parameter corresponds to the parameters 'Presentation Indicator' and 'CAMEL Invoked' in 3GPP TS 23.093 [107]. 6322 It indicates which services have been invoked for the original call (e.g. CLIR, CAMEL). See 3GPP TS 23.093 [107] for 6323 the use of this parameter and the conditions for its presence. 6324 Call Info 6325 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6326 Network Signal Info 6327 See 3GPP TS 23.093 [107] for the use of this parameter and the conditions for its presence. 6328 User error 6329 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6330 values, defined in clause 7.6.1: 6331 6332 6333 6334 6335 6336 6337
System failure; Data missing; Unexpected data value; Call Barred; Illegal SS operation; SS error status; SS incompatibility.
754
6338 6339 6340 6341
755 Release 4 756 757
190
3GPP TS 29.002 V4.17.0 (2006-06)
Short Term Denial; Long Term Denial; Facility Not Supported; This error is reserved for future use.
NOTE:
6342 Private Extensions shall not be sent with these user errors for this operation. 6343 Provider error 6344 See clause 7.6.1 for the use of this parameter.
6345 6346
11.14 MAP_ERASE_CC_ENTRY service
11.14.1 Definition
6347 This service is used between the MSC and the VLR and between the VLR and the HLR to erase data related to a call 6348 completion supplementary service. The VLR will relay the message to the HLR. 6349 The service is a confirmed service and uses the service primitives shown in table 11.14/1.
6350
6351
11.14.2 Service primitives
Table 11.14/1: MAP_ERASE_CC_ENTRY parameters
Parameter name Invoke id SS-Code CCBS Index SS-Status User error Provider error Request M M C Indication M(=) M(=) C(=) Response M(=) C(=) C C Confirm M(=) C(=) C(=) C(=) O
6352
6353
11.14.3 Parameter use
6354 See clause 7.6 for a definition of the parameters used, in addition to the following. 6355 SS-Code 6356 This parameter indicates the call completion supplementary service for which the mobile subscriber wants to erase an 6357 entry/entries. 6358 CCBS Index 6359 See 3GPP TS 23.093 [107] for the use of this parameter and the condition for its presence. 6360 SS-Status 6361 Depending on the outcome of the service request this parameter may indicate either provisioned and active or not 6362 provisioned. 6363 User error 6364 This parameter is sent by the responder upon unsuccessful outcome of the service, and then takes one of the following 6365 values, defined in clause 7.6.1: 6366 6367
System failure; Data Missing;
758
6368 6369 6370 6371
759 Release 4 760 761
191
3GPP TS 29.002 V4.17.0 (2006-06)
Unexpected data value; Call Barred; Illegal SS operation; SS error status.
6372 Private Extensions shall not be sent with these user errors for this operation. 6373 Provider error 6374 See clause 7.6.1 for the use of this parameter.
6375 6376 6377
12
Short message service management services
12.1 MAP-SEND-ROUTING-INFO-FOR-SM service
12.1.1 Definition
6378 This service is used between the gateway MSC and the HLR to retrieve the routing information needed for routing the 6379 short message to the servicing MSC. 6380 The MAP-SEND-ROUTING-INFO-FOR-SM is a confirmed service using the primitives from table 12.1/1.
6381
6382
12.1.2 Service primitives
Table 12.1/1: MAP-SEND-ROUTING-INFO-FOR-SM
Parameter name Invoke Id MSISDN SM-RP-PRI Service Centre Address SM-RP-MTI SM-RP-SMEA GPRS Support Indicator IMSI Network Node Number LMSI GPRS Node Indicator Additional Number User error Provider error Request M M M M C C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) Response M(=) Confirm M(=)
C C C C C C
C(=) C(=) C(=) C(=) C(=) C(=) O
6383
6384
6385 Invoke id
12.1.3 Parameter use
6386 See definition in clause 7.6.1. 6387 MSISDN 6388 See definition in clause 7.6.2. 6389 SM-RP-PRI 6390 See definition in clause 7.6.8.
762
6391 Service Centre Address 6392 See definition in clause 7.6.2. 6393 SM-RP-MTI 6394 See definition in clause 7.6.8. This parameter shall be present when the feature SM filtering by the HPLMN is 6395 supported by the SMS-GMSC and when the equivalent parameter is received from the short message service relay sub6396 layer protocol. 6397 SM-RP-SMEA 6398 See definition in clause 7.6.8. This parameter shall be present when the feature SM filtering by the HPLMN is 6399 supported by the SMS-GMSC and when the equivalent parameter is received from the short message service relay sub6400 layer protocol. 6401 GPRS Support Indicator 6402 See definition in clause 7.6.8. The presence of this parameter is mandatory if the SMS-GMSC supports receiving of the 6403 two numbers from the HLR. 6404 IMSI 6405 See definition in clause 7.6.2. The presence of this parameter is mandatory in a successful case. 6406 Network Node Number 6407 See definition in clause 7.6.2. This parameter is provided in a successful response. 6408 LMSI 6409 See definition in clause 7.6.2. It is an operator option to provide this parameter from the VLR; it is mandatory for the 6410 HLR to include the LMSI in a successful response, if the VLR has used the LMSI. 6411 GPRS Node Indicator 6412 See definition in clause 7.6.8. The presence of this parameter is mandatory if only the SGSN number is sent in the 6413 Network Node Number. 6414 Additional Number 6415 See definition in clause 7.6.2. This parameter is provided in a successful response. 6416 User error 6417 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6418 6419 6420 6421 6422 6423 6424 6425
763 Release 4 764 765
192
3GPP TS 29.002 V4.17.0 (2006-06)
Unknown subscriber; Call Barred; Teleservice Not Provisioned; Absent Subscriber_SM; Facility Not Supported; System failure; Unexpected Data Value; Data missing.
6426 Provider error 6427 For definition of provider errors see clause 7.6.1.
766
767 Release 4 768 769
193
3GPP TS 29.002 V4.17.0 (2006-06)
6428 6429
12.2 MAP-MO-FORWARD-SHORT-MESSAGE service
12.2.1 Definition
6430 This service is used between the serving MSC or the SGSN and the SMS Interworking MSC to forward mobile 6431 originated short messages. 6432 The MAP-MO-FORWARD-SHORT-MESSAGE service is a confirmed service using the service primitives given in 6433 table 12.2/1.
6434
6435
12.2.2 Service primitives
Table 12.2/1: MAP-MO-FORWARD-SHORT-MESSAGE
Parameter name Invoke Id SM RP DA SM RP OA SM RP UI IMSI User error Provider error Request M M M M C Indication M(=) M(=) M(=) M(=) C(=) Response M(=) C C Confirm M(=) C(=) C(=) O
6436
6437
6438 Invoke id
12.2.3 Parameter use
6439 See definition in clause 7.6.1. 6440 SM RP DA 6441 See definition in clause 7.6.8. 6442 In the mobile originated SM transfer this parameter contains the Service Centre address received from the mobile 6443 station. 6444 SM RP OA 6445 See definition in clause 7.6.8. 6446 The MSISDN received from the VLR or from the SGSN is inserted in this parameter in the mobile originated SM 6447 transfer. 6448 SM RP UI 6449 See definition in clause 7.6.8. The short message transfer protocol data unit received from the Service Centre is inserted 6450 in this parameter. 6451 IMSI 6452 See definition in clause 7.6.2.1. The IMSI of the originating subscriber is inserted in this parameter in the mobile 6453 originated SM transfer. 6454 This parameter shall be included if the sending entity, whether MSC or SGSN, supports mobile number portability. 6455 User error 6456 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6457 6458
Facility Not Supported; System Failure;
770
6459 6460 6461 6462 6463 6464 6465 6466
771 Release 4 772 773
194
3GPP TS 29.002 V4.17.0 (2006-06)
SM Delivery Failure; The reason of the SM Delivery Failure can be one of the following in the mobile originated SM: unknown Service Centre address; Service Centre congestion; invalid Short Message Entity address; subscriber not Service Centre subscriber; protocol error.
Unexpected Data Value
6467 Provider error 6468 For definition of provider errors see clause 7.6.1.
6469 6470
12.3 MAP-REPORT-SM-DELIVERY-STATUS service
12.3.1 Definition
6471 This service is used between the gateway MSC and the HLR. The MAP-REPORT-SM-DELIVERY-STATUS service is 6472 used to set the Message Waiting Data into the HLR or to inform the HLR of successful SM transfer after polling. This 6473 service is invoked by the gateway MSC. 6474 The MAP-REPORT-SM-DELIVERY-STATUS service is a confirmed service using the service primitives given in 6475 table 12.3/1.
6476
6477
12.3.2 Service primitives
Table 12.3/1: MAP-REPORT-SM-DELIVERY-STATUS
Parameter name Invoke Id MSISDN Service Centre Address SM Delivery Outcome Absent Subscriber Diagnostic SM GPRS Support Indicator Delivery Outcome Indicator Additional SM Delivery Outcome Additional Absent Subscriber Diagnostic SM MSIsdn-Alert User error Provider error Request M M M M C C C C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)
C C
C(=) C(=) O
6478
6479
6480 Invoke id
12.3.3 Parameter use
6481 See definition in clause 7.6.1. 6482 MSISDN 6483 See definition in clause 7.6.2. 6484 Service Centre Address 6485 See definition in clause 7.6.2.
774
6486 SM Delivery Outcome 6487 See definition in clause 7.6.8. This parameter indicates the status of the mobile terminated SM delivery. 6488 Absent Subscriber Diagnostic SM 6489 See definition in clause 7.6.8. 6490 GPRS Support Indicator 6491 See definition in clause 7.6.8. The presence of this parameter is mandatory if the SMS-GMSC supports handling of two 6492 delivery outcomes. 6493 Delivery Outcome Indicator 6494 See definition in clause 7.6.8. 6495 Additional SM Delivery Outcome 6496 See definition in clause 7.6.8. 6497 Additional Absent Subscriber Diagnostic SM 6498 See definition in clause 7.6.8. 6499 MSIsdn-Alert 6500 See definition in clause 7.6.2. This parameter shall be present in case of unsuccessful delivery, when the MSISDN 6501 received in the operation is different from the stored MSIsdn-Alert; the stored MSIsdn-Alert is the value that is returned 6502 to the gateway MSC. 6503 User error 6504 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6505 6506 6507 6508
775 Release 4 776 777
195
3GPP TS 29.002 V4.17.0 (2006-06)
Unknown Subscriber; Message Waiting List Full; Unexpected Data Value; Data missing.
6509 Provider error 6510 For definition of provider errors see clause 7.6.1.
6511 6512
12.4 MAP-READY-FOR-SM service
12.4.1 Definition
6513 This service is used between the MSC and VLR as well as between the VLR and the HLR. The MSC initiates this 6514 service if a subscriber indicates memory available situation. The VLR uses the service to indicate this to the HLR. 6515 The VLR initiates this service if a subscriber, whose message waiting flag is active in the VLR, has radio contact in the 6516 MSC. 6517 Also this service is used between the SGSN and the HLR. The SGSN initiates this service if a subscriber indicates 6518 memory available situation. The SGSN uses the service to indicate this to the HLR. 6519 The SGSN initiates this service if a subscriber, whose message waiting flag is active in the SGSN, has radio contact in 6520 the GPRS. 6521 The MAP-READY-FOR-SM service is a confirmed service using the primitives from table 12.4/1.
778
6522
779 Release 4 780 781
196
3GPP TS 29.002 V4.17.0 (2006-06)
12.4.2 Service primitives
Table 12.4/1: MAP-READY-FOR-SM
Parameter name Invoke Id IMSI TMSI Alert Reason Alert Reason Indicator User error Provider error Request M C C M C Indication M(=) C(=) C(=) M(=) C(=) Response M(=) Confirm M(=)
6523
C(=) O
6524
6525
6526 Invoke id
12.4.3 Parameter use
6527 See definition in clause 7.6.1. 6528 IMSI 6529 See definition in clause 7.6.2. The IMSI is used always between the VLR and the HLR and between the SGSN and the 6530 HLR. Between the MSC and the VLR the identification can be either IMSI or TMSI. 6531 TMSI 6532 See definition in clause 7.6.2. The identification can be either IMSI or TMSI between MSC and VLR. 6533 Alert Reason 6534 See definition in clause 7.6.8. This parameter indicates if the mobile subscriber is present or the MS has memory 6535 available. 6536 Alert Reason Indicator 6537 See definition in clause 7.6.8. 6538 User error 6539 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6540 6541 6542 6543 6544
Unknown Subscriber; Facility Not Supported; System Failure; Unexpected Data Value; Data missing.
6545 Provider error 6546 For definition of provider errors see clause 7.6.1.
6547 6548
12.5 MAP-ALERT-SERVICE-CENTRE service
12.5.1 Definition
6549 This service is used between the HLR and the interworking MSC. The HLR initiates this service, if the HLR detects 6550 that a subscriber, whose MSISDN is in the Message Waiting Data file, is active or the MS has memory available.
782
6551 The MAP-ALERT-SERVICE-CENTRE service is a confirmed service using the primitives from table 12.5/1.
783 Release 4 784 785
197
3GPP TS 29.002 V4.17.0 (2006-06)
6552
6553
12.5.2 Service primitives
Table 12.5/1: MAP-ALERT-SERVICE-CENTRE
Parameter name Invoke Id MSIsdn-Alert Service Centre Address User error Provider error Request M M M Indication M(=) M(=) M(=) Response M(=) C Confirm M(=) C(=) O
6554
6555
6556 Invoke id
12.5.3 Parameter use
6557 See definition in clause 7.6.1. 6558 MSIsdn-Alert 6559 See definition in clause 7.6.2. The provided MSISDN shall be the one which is stored in the Message Waiting Data file. 6560 Service Centre Address 6561 See definition in clause 7.6.2. 6562 User error 6563 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6564 6565 6566
System Failure; Unexpected Data Value; Data missing.
6567 Provider error 6568 For definition of provider errors see clause 7.6.1.
6569 6570
6571 6572 6573 6574
12.6 MAP-INFORM-SERVICE-CENTRE service
12.6.1 Definition
This service is used between the HLR and the gateway MSC to inform the Service Centre which MSISDN number is stored in the Message Waiting Data file. If the stored MSISDN number is not the same as the one received from the gateway MSC in the MAP-SEND-ROUTING-INFO-FOR-SM service primitive the stored MSISDN number is included in the message.
6575 Additionally the status of MCEF, MNRF and MNRG flags and the inclusion of the particular Service Centre address in 6576 the Message Waiting Data list is informed to the gateway MSC when appropriate. 6577 If the HLR has stored a single MNRR, the value is included in the Absent Subscriber Diagnostic SM parameter. 6578 If the HLR has stored a second MNRR, the value of the MNRR for the MSC is included in the Absent Subscriber 6579 Diagnostic SM parameter and the value of the MNRR for the SGSN is included in the Additional Absent Subscriber 6580 Diagnostic SM parameter. 6581 The MAP-INFORM-SERVICE-CENTRE service is a non-confirmed service using the primitives from table 12.6/1.
786
6582
787 Release 4 788 789
198
3GPP TS 29.002 V4.17.0 (2006-06)
12.6.2 Service primitives
Table 12.6/1: MAP-INFORM-SERVICE-CENTRE
Parameter name Invoke Id MSIsdn-Alert MWD Status Absent Subscriber Diagnostic SM Additional Absent Subscriber Diagnostic SM Request M C C C C Indication M(=) C(=) C(=) C(=) C(=)
6583
6584
6585
6586 Invoke id
12.6.3 Parameter use
6587 See definition in clause 7.6.1. 6588 MSIsdn-Alert 6589 See definition in clause 7.6.2. This parameter refers to the MSISDN stored in a Message Waiting Data file in the HLR. 6590 MWD Status 6591 See definition in clause 7.6.8. This parameter indicates the status of the MCEF, MNRF and MNRG flags and the status 6592 of the particular SC address presence in the Message Waiting Data list. 6593 Absent Subscriber Diagnostic SM 6594 See definition in clause 7.6.8. 6595 Additional Absent Subscriber Diagnostic SM 6596 See definition in clause 7.6.8.
6597 6598
12.7 MAP-SEND-INFO-FOR-MT-SMS service
12.7.1 Definition
6599 This service is used between the MSC and the VLR. The service is invoked by the MSC receiving an mobile terminated 6600 short message to request subscriber related information from the VLR. 6601 The MAP-SEND-INFO-FOR-MT-SMS service is a confirmed service using the primitives from table 12.7/1.
6602
6603
12.7.2 Service primitives
Table 12.7/1: MAP-SEND-INFO-FOR-MT-SMS
Parameter name Invoke Id SM RP DA MSISDN User error Provider error Request M M Indication M(=) M(=) Response M(=) C C Confirm M(=) C(=) C(=) O
6604
6605
12.7.3 Parameter use
790
6606 Invoke id
791 Release 4 792 793
199
3GPP TS 29.002 V4.17.0 (2006-06)
6607 See definition in clause 7.6.1. 6608 SM RP DA 6609 See definition in clause 7.6.8. This parameter shall contain either an IMSI or a LMSI. 6610 MSISDN 6611 See definition in clause 7.6.2. 6612 User error 6613 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6614 6615 6616 6617 6618 6619 6620 6621 6622
Unknown subscriber; Unidentified Subscriber; Absent subscriber; Unexpected Data Value; Data Missing; Illegal subscriber; Illegal equipment; Subscriber busy for MT SMS; System Failure.
6623 Provider error 6624 For definition of provider errors see clause 7.6.1.
6625 6626
12.8 MAP-SEND-INFO-FOR-MO-SMS service
12.8.1 Definition
6627 This service is used between the MSC and the VLR. The service is invoked by the MSC which has to handle a mobile 6628 originated short message request to request the subscriber related information from the VLR. 6629 The MAP-SEND-INFO-FOR-MO-SMS service is a confirmed service using the primitives from table 12.8/1.
6630
6631
12.8.2 Service primitives
Table 12.8/1: MAP-SEND-INFO-FOR-MO-SMS
Parameter name Invoke Id Service Centre Address MSISDN User error Provider error Request M M Indication M(=) M(=) Response M(=) C C Confirm M(=) C(=) C(=) O
6632
6633
6634 Invoke id
12.8.3 Parameter use
794
6635 See definition in clause 7.6.1. 6636 Service Centre Address 6637 See definition in clause 7.6.2. 6638 MSISDN 6639 See definition in clause 7.6.2. 6640 User error 6641 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6642 6643 6644 6645
795 Release 4 796 797
200
3GPP TS 29.002 V4.17.0 (2006-06)
Teleservice Not Provisioned; Call Barred; Unexpected Data Value; Data Missing.
6646 Provider error 6647 For definition of provider errors see clause 7.6.1.
6648 6649
12.9 MAP-MT-FORWARD-SHORT-MESSAGE service
12.9.1 Definition
6650 This service is used between the gateway MSC and the servicing MSC or the SGSN to forward mobile terminated short 6651 messages. 6652 The MAP-MT-FORWARD-SHORT-MESSAGE service is a confirmed service using the service primitives given in 6653 table 12.9/1.
6654
6655
12.9.2 Service primitives
Table 12.9/1: MAP-MT-FORWARD-SHORT-MESSAGE
Parameter name Invoke Id SM RP DA SM RP OA SM RP UI More Messages To Send User error Provider error Request M M M M C Indication M(=) M(=) M(=) M(=) C(=) Response M(=) Confirm M(=)
C C
C(=) C(=) O
6656
6657
6658 Invoke id
12.9.3 Parameter use
6659 See definition in clause 7.6.1. 6660 SM RP DA 6661 See definition in clause 7.6.8. This parameter can contain either an IMSI or a LMSI. The use of the LMSI is an operator 6662 option. The LMSI can be provided if it is received from the HLR. The IMSI is used if the use of the LMSI is not 6663 available. 6664 This parameter is omitted in the mobile terminated subsequent SM transfers.
798
6665 SM RP OA 6666 See definition in clause 7.6.8. The Service Centre address received from the originating Service Centre is inserted in 6667 this parameter. 6668 This parameter is omitted in the mobile terminated subsequent SM transfers. 6669 SM RP UI 6670 See definition in clause 7.6.8. The short message transfer protocol data unit received from the Service Centre is inserted 6671 in this parameter. A short message transfer protocol data unit may also be inserted in this parameter in the message 6672 delivery acknowledgement from the MSC or from the SGSN to the Service Centre. 6673 More Messages To Send 6674 See definition in clause 7.6.8. The information from the MMS indication received from the Service Centre is inserted in 6675 this parameter. 6676 User error 6677 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6678
799 Release 4 800 801
201
3GPP TS 29.002 V4.17.0 (2006-06)
Unidentified subscriber; Absent Subscriber_SM; Subscriber busy for MT SMS; Facility Not Supported; Illegal Subscriber indicates that delivery of the mobile terminated short message failed because the mobile station failed authentication; Illegal equipment indicates that delivery of the mobile terminated short message failed because an IMEI check failed, i.e. the IMEI was blacklisted or not white-listed; System Failure; SM Delivery Failure: The reason of the SM Delivery Failure can be one of the following in the mobile terminated SM: memory capacity exceeded in the mobile equipment; protocol error; mobile equipment does not support the mobile terminated short message service.
6679 6680 6681 6682 6683 6684 6685 6686 6687 6688 6689 6690 6691 6692
Unexpected Data Value; Data Missing.
6693 Provider error 6694 For definition of provider errors see clause 7.6.1.
6695 6696 6697
13
Network-Requested PDP Context Activation services
13.1 MAP_SEND_ROUTING_INFO_FOR_GPRS service
13.1.1 Definition
6698 This service is used by the GGSN to request GPRS routing information from the HLR.
802
6699
803 Release 4 804 805
202
3GPP TS 29.002 V4.17.0 (2006-06)
13.1.2 Service primitives
Table 13.1/1: MAP_SEND_ROUTING_INFO_FOR_GPRS
Parameter name Invoke id IMSI GGSN address GGSN number SGSN address Mobile Not Reachable Reason User error Provider error Request M M C M Indication M(=) M(=) C(=) M(=) Response M(=) C C C C Confirm M(=) C(=) C(=) C(=) C(=) O
6700
6701
6702
6703 Invoke Id
13.1.3 Parameter definition and use
6704 See definition in clause 7.6.1. 6705 IMSI 6706 See definition in clause 7.6.2. 6707 GGSN address 6708 This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. 6709 GGSN number 6710 See definition in clause 7.6.2. 6711 SGSN address 6712 This parameter shall be present if the outcome of the Send Routing Info For GPRS request to the GPRS application 6713 process in the HLR is positive. 6714 Mobile Not Reachable Reason 6715 This parameter shall be present if the outcome of the Send Routing Info For GPRS request to the GPRS application 6716 process in the HLR is positive and the MNRG flag in the HLR is set. See definition in clause 7.6.3.51. 6717 User error 6718 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6719 6720 6721 6722 6723
Absent Subscriber; System Failure; Data Missing; Unexpected Data Value; Unknown Subscriber.
6724 The diagnostic in the Unknown Subscriber may indicate Imsi Unknown or Gprs Subscription Unknown. 6725 6726 6727
Call Barred; This error will indicate that the received PDP PDUs in the GGSN shall be barred for this MS due to Operator Determined Barring. (The CallBarringCause must be the operatorBarring.)
6728 Provider error
806
6729 These are defined in clause 7.6.1.
807 Release 4 808 809
203
3GPP TS 29.002 V4.17.0 (2006-06)
6730 6731
13.2 MAP_FAILURE_REPORT service
13.2.1 Definition
6732 This service is used by the GGSN to inform the HLR that network requested PDP-context activation has failed.
6733
6734
13.2.2 Service primitives
Table 13.2/1: MAP_FAILURE_REPORT
Parameter name Invoke id IMSI GGSN address GGSN number User error Provider error Request M M C M Indication M(=) M(=) C(=) M(=) Response M(=) C C Confirm M(=) C(=) C(=) O
6735
6736
6737 Invoke Id
13.2.3 Parameter definition and use
6738 See definition in clause 7.6.1. 6739 IMSI 6740 See definition in clause 7.6.2. 6741 GGSN address 6742 This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. 6743 GGSN number 6744 See definition in clause 7.6.2. 6745 User error 6746 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6747 6748 6749 6750
System Failure; Data Missing; Unexpected Data Value; Unknown Subscriber.
6751 Provider error 6752 These are defined in clause 7.6.1.
6753 6754
13.3 MAP_NOTE_MS_PRESENT_FOR_GPRS service
13.3.1 Definition
6755 This service is used by the HLR to inform the GGSN that the MS is present for GPRS again.
810
6756
811 Release 4 812 813
204
3GPP TS 29.002 V4.17.0 (2006-06)
13.3.2 Service primitives
Table 13.3/1: MAP_NOTE_MS_PRESENT_FOR_GPRS
Parameter name Invoke id IMSI GGSN address SGSN address User error Provider error Request M M C M Indication M(=) M(=) C(=) M(=) Response M(=) Confirm M(=)
6757
C(=) O
6758
6759
6760 Invoke Id
13.3.3 Parameter definition and use
6761 See definition in clause 7.6.1. 6762 IMSI 6763 See definition in clause 7.6.2. 6764 GGSN address 6765 This parameter shall be present if the protocol-converting GSN is used between the GGSN and the HLR. 6766 SGSN address 6767 See definition in clause 7.6.2. 6768 User error 6769 This parameter is sent by the responder when an error is detected and if present, takes one of the following values: 6770 6771 6772 6773
System Failure; Data Missing; Unexpected Data Value; Unknown Subscriber.
6774 Provider error 6775 These are defined in clause 7.6.1.
6776 6777 6778
13A
Location Service Management Services
13A.1MAP-SEND-ROUTING-INFO-FOR-LCS Service
13A.1.1 Definition
6779 This service is used between the GMLC and the HLR to retrieve the routing information needed for routing a location 6780 service request to the servicing VMSC or SGSN. The MAP-SEND-ROUTING-INFO-FOR-LCS is a confirmed service 6781 using the primitives from table 13A.1/1.
814
6782
815 Release 4 816 817
205
3GPP TS 29.002 V4.17.0 (2006-06)
13A.1.2 Service Primitives
Table 13A.1/1: MAP-SEND-ROUTING-INFO-FOR-LCS
Parameter name Invoke Id MLC Number MSISDN IMSI LMSI Network Node Number GPRS Node Indicator Additional Number User error Provider error Request M M C C Indication M(=) M(=) C(=) C(=) Response M(=) C C C C C C C Confirm M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) O
6783
6784
6785
6786 Invoke id
13A.1.3 Parameter Use
6787 See definition in clause 7.6.1. 6788 MLC Number 6789 See definition in clause 7.6.2. 6790 MSISDN 6791 See definition in clause 7.6.2. The request shall carry either the IMSI or MSISDN. The response shall carry whichever 6792 of these was not included in the request (see 3GPP TS 23.271 for details). 6793 IMSI 6794 See definition in clause 7.6.2. 6795 LMSI 6796 See definition in clause 7.6.2. It is an operator option to provide this parameter from the VLR; it is mandatory for the 6797 HLR to include the LMSI in a successful response, if the VLR has used the LMSI. 6798 Network Node Number 6799 See definition in clause 7.6.2. This parameter is provided in a successful response. If the Network Node Number and 6800 Additional Number are received in the GMLC, the "Network Node Number" is used in preference to the "Additional 6801 Number". 6802 GPRS Node Indicator 6803 See definition in clause 7.6.8. The presence of this parameter is mandatory only if the SGSN number is sent in the 6804 Network Node Number. 6805 Additional Number 6806 See definition in clause 7.6.2. This parameter is provided in a successful response. If the Network Node Number and 6807 Additional Number are received in the GMLC, the "Network Node Number" is used in preference to the "Additional 6808 Number". 6809 User error 6810 The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault: 6811 6812 -
Unknown subscriber; Absent Subscriber;
818
6813 6814 6815 6816 6817 -
819 Release 4 820 821
206
3GPP TS 29.002 V4.17.0 (2006-06)
Facility Not Supported; System failure; Unexpected Data Value; Data missing; Unauthorised requesting network.
6818 Provider error 6819 For definition of provider errors see clause 7.6.1.
6820 6821
13A.2MAP-PROVIDE-SUBSCRIBER-LOCATION Service
13A.2.1 Definition
6822 This service is used by a GMLC to request the location of a target MS from the visited MSC or SGSN at any time. This 6823 is a confirmed service using the primitives from table 13A.2/1.
6824
6825
13A.2.2 Service Primitives
Table 13A.2/1: Provide_Subscriber_Location
Parameter name Invoke id Location Type MLC Number LCS Client ID Privacy Override IMSI MSISDN LMSI LCS Priority LCS QoS IMEI Supported GAD Shapes LCS-Reference Number Location Estimate Age of Location Estimate Additional Location Estimate Deferred MT-LR Response Indicator User error Provider error Request M M M M U C C C C C U C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)
M C C C C
M(=) C(=) C(=) C(=) C(=) O
6826
6827
13A.2.3 Parameter Definition and Use
6828 All parameters are defined in clause 7.6. The use of these parameters and the requirements for their presence are 6829 specified in. 3GPP TS 23.271 6830 Location Type 6831 This parameter identifies the type of location information requested. 6832 MLC Number 6833 This is the E.164 number of the requesting GMLC.
822
6834 LCS Client ID 6835 This parameter provides information related to the identity of an LCS client. 6836 Privacy Override 6837 This parameter indicates if MS privacy is overridden by the LCS client when the GMLC and VMSC or SGSN for an 6838 MT-LR are in the same country. 6839 IMSI 6840 The IMSI is provided to identify the target MS. At least one of the IMSI or MSISDN is mandatory. 6841 MSISDN 6842 The MSISDN is provided to identify the target MS. At least one of the IMSI or MSISDN is mandatory. 6843 LMSI 6844 The LMSI shall be provided if previously supplied by the HLR. This parameter is only used in the case of the MT-LR 6845 for CS domain. 6846 LCS Priority 6847 This parameter indicates the priority of the location request. 6848 LCS QoS 6849 This parameter indicates the required quality of service in terms of response time and accuracy. 6850 IMEI 6851 Inclusion of the IMEI is optional. 6852 Supported GAD Shapes 6853 This parameter indicates which of the shapes defined in 3GPP TS 23.032 are supported. 6854 LCS-Reference Number 6855 This parameter shall be included if a deferred mt-lr procedure is performed. 6856 Location Estimate 6857 This parameter provides the location estimate if this is encoded in one of the supported geographical shapes. Otherwise 6858 this parameter shall consist of one octet, which shall be discarded by the receiving node. 6859 Age of Location Estimate 6860 This parameter indicates how long ago the location estimate was obtained. 6861 Additional Location Estimate 6862 This parameter provides the location estimate when not provided by the Location Estimate parameter. It may be sent 6863 only if the parameter Supported GAD Shapes has been received in the Provide Subscriber Location indication and the 6864 shape to be included is supported by the GMLC. 6865 Deferred MT-LR Response Indicator 6866 See definition in clause 7.6.11.2. 6867 User error 6868 This parameter is sent by the responder when the location request has failed or cannot proceed and if present, takes one 6869 of the following values defined in clause 7.6.1. 6870 -
823 Release 4 824 825
207
3GPP TS 29.002 V4.17.0 (2006-06)
System Failure;
826
6871 6872 6873 6874 6875 6876 6877 6878 6879 6880 -
827 Release 4 828 829
208
3GPP TS 29.002 V4.17.0 (2006-06)
Data Missing; Unexpected Data Value; Facility Not Supported; Unidentified Subscriber; Illegal Subscriber; Illegal Equipment; Absent Subscriber (diagnostic information may also be provided); Unauthorised requesting network; Unauthorised LCS Client with detailed reason; Position method failure with detailed reason.
6881 Provider error 6882 These are defined in clause 7.6.1.
6883 6884
13A.3MAP-SUBSCRIBER-LOCATION-REPORT Service
13A.3.1 Definition
6885 This service is used by a VMSC or SGSN to provide the location of a target MS to a GMLC when a request for location 6886 is either implicitly administered or made at some earlier time. This is a confirmed service using the primitives from 6887 table 13A.3/1.
6888
6889
13A.3.2 Service Primitives
Table 13A.3/1: Subscriber_Location_Report
Parameter name Invoke id LCS Event LCS Client ID Network Node Number IMSI MSISDN NA-ESRD NA-ESRK IMEI Location Estimate Age of Location Estimate LMSI GPRS Node Indicator Additional Location Estimate Deferred MT-LR Data LCS-Reference Number NA-ESRK Request User error Provider error Request M M M M C C C C U C C U C C C C C Indication M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) C(=) Response M(=) Confirm M(=)
C(=)
C(=) O
6890
6891
13A.3.3 Parameter Definition and Use
6892 All parameters are defined in clause 7.6. The use of these parameters and the requirements for their presence are 6893 specified in. 3GPP TS 23.271
830
6894 LCS Event 6895 This parameter indicates the event that triggered the Subscriber Location Report. 6896 LCS Client ID 6897 This parameter provides information related to the identity of the recipient LCS client. 6898 Network Node Number 6899 See definition in clause 7.6.2. This parameter provides the address of the sending node. 6900 IMSI 6901 The IMSI shall be provided if available to the VMSC or SGSN. 6902 MSISDN 6903 The MSISDN shall be provided if available to the VMSC or SGSN. 6904 NA-ESRD 6905 If the target MS has originated an emergency service call in North America, the NA-ESRD shall be provided by the 6906 VMSC if available. 6907 NA-ESRK 6908 If the target MS has originated an emergency service call in North America, the NA-ESRK shall be provided by the 6909 VMSC if assigned. 6910 If the target MS has originated an emergency service call in North America and NA-ESRK Request is included in 6911 Subscriber_Location_Report-Arg, NA-ESRK may also be included in the response to the MSC, see 3GPP TS 23.271 6912 [26a]. 6913 IMEI 6914 Inclusion of the IMEI is optional. 6915 Location Estimate 6916 This parameter provides the location estimate. The absence of this parameter implies that a location estimate was not 6917 available or could not be successfully obtained. If the obtained location estimate is not encoded in one of the supported 6918 geographical shapes then this parameter shall consist of one octet, which shall be discarded by the receiving node. 6919 6920 Age of Location Estimate 6921 This parameter indicates how long ago the location estimate was obtained. 6922 LMSI 6923 The LMSI may be provided if assigned by the VLR. 6924 GPRS Node Indicator 6925 See definition in clause 7.6.8. This presence of this parameter is mandatory only if the SGSN number is sent in the 6926 Network Node Number. 6927 Additional Location Estimate 6928 This parameter provides the location estimate when not provided by the Location Estimate parameter.. 6929 Deferred MT-LR Data 6930 See definition in clause 7.6.11.3. 6931 LCS-Reference Number
831 Release 4 832 833
209
3GPP TS 29.002 V4.17.0 (2006-06)
834
6932 This parameter shall be included if the Subscriber Location Report is the reponse to a deferred MT location request. 6933 NA-ESRK Request 6934 If the target MS has originated an emergency service call in North America, NA-ESRK Request may be included to 6935 indicate that the MSC is able to accept NA-ESRK in the Response message, see section 7.6.11.19. 6936 User error 6937 This parameter is sent by the responder when the received message contains an error, cannot be forwarded or stored for 6938 an LCS client or cannot be accepted for some other reason and if present, takes one of the following values defined in 6939 clause 7.6.1. 6940 6941 6942 6943 6944 6945 6946 -
835 Release 4 836 837
210
3GPP TS 29.002 V4.17.0 (2006-06)
System Failure; Data Missing; Unexpected Data Value; Resource Limitation; Unknown Subscriber; Unauthorised requesting network; Unknown or unreachable LCS Client.
6947 Provider error 6948 These are defined in clause 7.6.1.
6949 6950 6951 6952 6953 6954 6955 6956 6957 6958 6959 6960
13A.4Void
13A.4.1 Void 13A.4.2 Void 13A.4.3 Void
13A.5Void
13A.5.1 Void 13A.5.2 Void 13A.5.3 Void
13A.6Void
13A.6.1 Void 13A.6.2 Void 13A.6.3 Void
838
839 Release 4 840 841
211
3GPP TS 29.002 V4.17.0 (2006-06)
6961 6962 6963 6964 6965 6966 6967 6968 6969 6970 6971 6972
13A.7Void
13A.7.1 Void 13A.7.2 Void 13A.7.3 Void
13A.8Void
13A.8.1 Void 13A.8.2 Void 13A.8.3 Void
13A.9Void
13A.9.1 Void 13A.9.2 Void 13A.9.3 Void
6973 6974
14
General
14.1 Overview
6975 Clauses 14 to 17 specify the protocol elements to be used to provide the MAP services described in clause 7. 6976 Clause 15 specifies the elements of procedures for the MAP protocol. Clause 16 specifies the mapping onto TC service 6977 primitives. Clause 17 specifies the application contexts, operation packages and abstract syntaxes for the MAP protocol 6978 as well as the encoding rules to be applied.
6979
14.2 Underlying services
6980 The MAP protocol relies on the services provided by the Transaction Capabilities (TC) of Signalling System Number 6981 No. 7, as referenced in clause 6.
6982
6983 6984 6985 6986
14.3 Model
The MAP Protocol Machine (MAP PM) can be modelled as a collection of service state machines (SSMs) - one per MAP specific service invoked - coordinated by a MAP dialogue control function with its one state machine: MAP dialogue state machine (DSM). There are two types of Service State Machines: Requesting Service State Machines (RSM) and Performing Service State Machines (PSM).
842
6987 A new invocation of a MAP PM is employed on the receipt of a MAP-OPEN request primitive or a TC-BEGIN 6988 indication primitive. Each invocation controls exactly one MAP dialogue. For each MAP specific service invoked 6989 during a dialogue, a MAP RSM is created at the requestor's side and a MAP PSM is created at the performer's side. 6990 This modelling is used only to facilitate understanding and the MAP behaviour descriptions and is not intended to 6991 suggest any implementation. SDL descriptions are organised according to this model. 6992 How the MAP-service-user and the MAP refer to a MAP dialogue (i.e. a MAP PM invocation) is a local 6993 implementation matter. 6994 How TC dialogue identifiers are assigned to a MAP PM invocation is also a local implementation matter.
843 Release 4 844 845
212
3GPP TS 29.002 V4.17.0 (2006-06)
6995
14.4 Conventions
6996 The behaviour of the MAP PM depends on the application-context-name associated with the dialogue. One major 6997 difference is that the MAP requests the transfer of the application-context-name by TC only for those contexts which do 6998 not belong to the so-called "version one context set". 6999 The "version one context set" is a set of application-contexts which model the behaviour of a MAP V1 implementation 7000 according to the latest phase 1 version of GSM 09.02. This set is defined in clause 15. 7001 The procedures described in clause 15 are used when the application-context-name does not refer to a dialogue between 7002 an MSC and its VLR. When the application-context-name refers to a dialogue between an MSC and its VLR the MAP 7003 PM procedures are a local implementation matter.
7004 7005
7006 7007 7008 7009 7010 7011 7012 7013 7014 7015 7016 7017 7018 7019 7020
15
Elements of procedure
15.1 Handling of unknown operations
Unknown operations (i.e. a standard operation introduced in a later version of the MAP specification, or a private operation) can be introduced into MAP in a backwards compatible way. This means that the receiver of an unknown operation shall, if the dialogue state allows it, send a TC-REJECT component to the sender of the operation indicating 'unrecognised operation' and continue with the processing of further components or messages exchanged within the dialogue as if the unknown operation had not been received. The standardised structure of a MAP dialogue shall not be affected by the invocation of unknown operations, i.e. if a dialogue uses only a TC-BEGIN message which is acknowledged by a TC-END message, a TC-CONTINUE message shall not be used to invoke an unknown operation. However the standardised structure of a MAP dialogue may be affected by the rejection of unknown operations, i.e. if a dialogue uses only a TC-BEGIN message which is acknowledged by a TC-END message, a TC-CONTINUE message followed by a TC-END message may be used to carry the rejection of an unknown operation and the response to the standardised operation. The entity which initiated a dialogue whose standardised structure is a TC-BEGIN message which is acknowledged by a TC-END message shall not send any messages in that dialogue after the TC-BEGIN. Note that if the dialogue structure is affected as described in this paragraph the TC-CONTINUE shall include the dialogue portion required to confirm the acceptance of the dialogue.
7021 Unknown operations may be invoked in the following types of message (there is no restriction as to how many 7022 unknown operations can be invoked in a message): 7023 7024 7025 7026 7027 7028 7029
TC-BEGIN: the component to invoke the unknown operation shall follow the component of the standard operation which is included in this message. TC-CONTINUE: the component to invoke the unknown operation may be transported as the only component in a stand-alone message or may be grouped with existing operations. In the latter case a specific sequencing of components is not required. TC-END: if the component to invoke the unknown operation is grouped with an existing operation a specific sequencing of components is not required
846
7030 The TC-REJECT component may be sent in the following messages: 7031 7032 7033 7034 7035 7036 7037 7038 7039
847 Release 4 848 849
213
3GPP TS 29.002 V4.17.0 (2006-06)
TC-CONTINUE or TC-END: either as the only component of the message or grouped with an existing component. The choice is up to the MAP-Service User. If the received message contains only unknown operations the MAP-Service User shall send the TC-REJECT components in a TC-CONTINUE message to the peer entity, if the dialogue state allows it. If the received message contains unknown operations and standard operations and the standardised structure of the dialogue requires the response to the standard operation to be sent within a TC-END message, then the MAP-Service User may send the response to the standard operations and the TC-REJECT components for the unknown operations in a TC-CONTINUE message followed by a TC-END message. Neither a specific distribution of the components to the TC messages nor a specific sequencing of components is required.
7040 Note that the SDL diagrams of clauses 19 - 25 do not show the report to the MAP-Service User about the reception of 7041 the unknown operation. This has been done for simplicity of description; the MAP PM may inform the MAP-Service 7042 User. 7043 The sender of the unknown operation shall ensure that there is enough room in the used message for the unknown 7044 operation.
7045
15.2 Dialogue establishment
7046 The establishment of a MAP dialogue involves two MAP-service-users: the dialogue-initiator and the dialogue7047 responder. 7048 This procedure is driven by the following signals: 7049 7050 7051 7052
a MAP-OPEN request primitive from the dialogue-initiator; a TC-BEGIN indication primitive occurring at the responding side; a MAP-OPEN response primitive from the dialogue-responder; the first TC-CONTINUE indication primitive occurring at the initiating side;
7053 and under specific conditions: 7054 7055 7056
a TC-END indication primitive occurring at the initiating side; a TC-U-ABORT indication primitive occurring at the initiating side; a TC-P-ABORT indication primitive occurring at the initiating side.
7057 One instance of the MAP dialogue state machine runs at the initiating side, and one at the responding side.
7058
15.2.1 Behaviour at the initiating side
7059 The behaviour of the MAP dialogue state machine at the initiating side is defined in sheets 1 8 of the process 7060 MAP_DSM (fugure 15.6/3). 7061 Sheet 3: When the MAP dialogue state machine at the initiating side is waiting for a response from the responding side, 7062 a TC-END indication which echoes the AC name which was sent in the TC-BEGIN indicates acceptance of the 7063 dialogue. 7064 Sheet 3: If the dialogue opening is accepted, any components included in the TC-END are processed and passed to the 7065 MAP-Service User. The dialogue is closed by sending a MAP-CLOSE to the MAP-Service User. 7066 Sheet 3, sheet 4, sheet 5, sheet 6, sheet 7, sheet 8: when a dialogue is terminated, the MAP dialogue state machine 7067 terminates all instances of the Requesting_MAP_SSM which are active for this dialogue. 7068 Sheet 4: A TC-P-ABORT with an abort parameter Incorrect_Transaction_Portion indicates that the responding side 7069 does not support a MAP version higher than 1. This triggers a MAP-OPEN confirm indicating that the dialogue is 7070 refused, with a refuse reason potential version incompatibility. The MAP-Service User may then decide to retry the
850
7071 dialogue at MAP version 1. If secure transport is required and fallback to unsecured transport is acceptable, the dialogue 7072 machine retries the dialogue with unsecured transport. 7073 7074 Sheet 8: When the MAP dialogue state machine at the initiating side is waiting for a response from the responding side, 7075 a TC-CONTINUE indication which echoes the AC name which was sent in the TC-BEGIN indicates acceptance of the 7076 dialogue. 7077 Sheet 8: If the dialogue opening is accepted, any components included in the TC-CONTINUE are processed and passed 7078 to the MAP-Service User. The dialogue has then reached the established state.
851 Release 4 852 853
214
3GPP TS 29.002 V4.17.0 (2006-06)
7079
15.2.2 Behaviour at the responding side
7080 The behaviour of the MAP dialogue state machine at the responding side is defined in sheets 9 14 of the process 7081 MAP_DSM (figure 15.6/3). 7082 Sheet 9: If no application context information is included in the TC-BEGIN indication, this implies a MAP version 1 7083 dialogue. An explicit application context indicating version 1 is treated as abnormal behaviour. 7084 Sheet 11: The v1 application context name which corresponds to a v1 operation is derived using the information in table 7085 15.2/1. 7086
Table 15.2/1: Mapping of V1 operation codes on to application-context-names
Operation updateLocation cancelLocation provideRoamingNumber insertSubscriberData deleteSubscriberData sendParameters beginSubscriberActivity sendRoutingInfo performHandover reset activateTraceMode deactivateTraceMode sendRoutingInfoForSM forwardSM reportSM-deliveryStatus noteSubscriberPresent alertServiceCentreWithoutResult checkIMEI Application-context-name (note 1) networkLocUpContext-v1 locationCancellationContext-v1 roamingNumberEnquiryContext-v1 subscriberDataMngtContext-v1 subscriberDataMngtContext-v1 infoRetrievalContext-v1 networkLocUpContext-v1 (note 2) networkFunctionalSsContext-v1 locationInfoRetrievalContext-v1 handoverControlContext-v1 resetContext-v1 tracingContext-v1 tracingContext-v1 shortMsgGatewayContext-v1 shortMsgRelayContext-v1 shortMsgGatewayContext-v1 mwdMngtContext-v1 shortMsgAlertContext-v1 EquipmentMngtContext-v1
7087
7092 Sheet 12: If the dialogue is accepted, each component present in the TC-BEGIN is forwarded to an instance of a 7093 Performing_MAP_SSM, by executing the procedure Process_Components. 7094 Sheet 13: If the MAP dialogue state machine receives a MAP-OPEN response with a result accepted, it waits for any 7095 MAP specific service request or response primitives or a MAP-DELIMITER request. 7096 Sheet 13, sheet 14: When a dialogue is terminated, the MAP dialogue state machine terminates all instances of the 7097 Requesting_MAP_SSM or Performing_MAP_SSM which are active for this dialogue. 7098 Sheet 14: A MAP-DELIMITER request triggers a TC-CONTINUE request to accept the dialogue. The dialogue has 7099 then reached the established state.
7088 7089 7090 7091
NOTE 1: These symbolic names refer to the object identifier value defined in clause 17 and allocated to each application-context used for the MAP. NOTE 2: The choice between the application contexts is based on the parameters received in the operation.
854
855 Release 4 856 857
215
3GPP TS 29.002 V4.17.0 (2006-06)
7100
15.3 Dialogue continuation
7101 Once established the dialogue is said to be in a continuation phase. The behaviour of the MAP dialogue state machine in 7102 this phase is defined in sheets 15 17 of the process MAP_DSM (figure 15.6/3). 7103 Both MAP users can request the transfer of MAP APDUs until one of them requests the termination of the dialogue. 7104 Normal closure of an established dialogue is shown on sheet 16; abnormal termination is shown on sheet 17.
7105
15.4 Load control
7106 If an entity which should respond to a MAP dialogue opening request is overloaded, it uses the AC of the request to 7107 determine whether to discard the request. 7108 The priority level allocated to each application-context is described in clause 5, tables 5.1/1, 5.1/2 and 5.1/3.
7109
15.5 Procedures for MAP specific services
7110 This clause describes the MAP procedures for MAP specific services. These procedures are driven by the following 7111 types of event: 7112 7113
a MAP specific request or a MAP specific response primitive; a component handling primitive from TC.
7114 A Service State Machine is activated when of one of the following signals is received: 7115 7116
a MAP request primitive, which activates a requesting SSM; a TC-INVOKE indication primitive without a linked identifier, which activates a performing SSM.
7117 For component handling primitives there are two types of event: 7118 7119
events which activate a Service State Machine or which can be related to an existing one; events which cannot be related to a Service State Machine.
7120
7121 7122 7123 7124 7125 7126 7127 7128 7129 7130
15.5.1 Service invocation
The behaviour of the requesting SSM which handles a service is defined by the SDL for the process Requesting_MAP_SSM. The requesting SSM receives a MAP service request from the MAP-Service User via the MAP dialogue state machine and sends a TC-INVOKE request to TCAP. When a confirm is received from TCAP via the MAP dialogue state machine, the requesting SSM forwards a MAP service confirm to the MAP-Service User. The response to a MAP service invocation may come in the form of a linked request. If the linked request corresponds to a class 4 operation, this is handled by the requesting SSM. If the linked request corresponds to a class 1, 2 or 3 operation, the MAP dialogue state machine sends a notification to the requesting SSM and creates an instance of a performing SSM to handle the linked request. The test "Linked_Operation_Allowed" on sheet 3 of the process Requesting_MAP_SSM takes the (TRUE) exit if the definition of the parent operation includes the received linked operation as a permitted linked operation; otherwise the test takes the (FALSE) exit.
7131 The mapping of MAP specific services on to remote operations is given in table 16.2/1.
7132 7133
15.5.2 void 15.5.3 Service invocation receipt
7134 The behaviour of the performing SSM which handles a service is defined by the SDL for the process 7135 Performing_MAP_SSM. The performing SSM receives a TC-INVOKE component from TCAP via the MAP dialogue 7136 state machine and sends a MAP service indication to the MAP-Service User. When a MAP service response is received
858
7137 from the MAP-Service User via the MAP dialogue state machine, the performing SSM forwards a TC-RESULT or TC7138 U-ERROR component to TCAP.
859 Release 4 860 861
216
3GPP TS 29.002 V4.17.0 (2006-06)
7139 7140
15.5.4 void 15.5.5 Handling of components received from TC
7141 The procedure Process_Components shows the handling of components received in a TC-BEGIN, TC-CONTINUE or 7142 TC-END message. 7143 7144 7145 7146
Sheet 2: If a linked invoke component corresponds to a class 4 operation, the MAP dialogue state machine sends it to the requesting SSM instance identified by the linked invoke ID. If a linked invoke component corresponds to any other class of operation, the MAP dialogue state machine sends a notification to the requesting SSM instance identified by the linked invoke ID, creates an instance of a performing SSM and sends the invoke component to it.
7147
15.6 SDL descriptions
7148 The following SDL specification describes a system which includes three blocks: MAP-user, MAP-provider and TC. 7149 Such a system resides in each network component supporting MAP and communicates with its peers via the lower 7150 layers of the signalling network which are part of the environment. 7151 Only the MAP-provider is fully described in this clause. The various types of processes which form the MAP-User 7152 block and the TC block are described respectively in clauses 18 to 25 of the present document and in CCITT 7153 Recommendation Q.774. 7154 The MAP-Provider block communicates with the MAP_USER via two channels U1 and U2. Via U1 the MAP-provider 7155 receives the MAP request and response primitives. Via U2 it sends the MAP indication and confirm primitives. 7156 The MAP-Provider block communicates with TC via two channels P1 and P2. Via P1 the MAP-Provider sends all the 7157 TC request primitives. Via P2 it receives all the TC indication primitives. 7158 The MAP-Provider block is composed of the four following types of process: 7159 7160 7161 7162 7163 7164 7165 7166 7167 7168
a) MAP_DSM: This type of process handles a dialogue for transport of MAP messages. There exists one process instance per MAP dialogue. b) Load_Ctrl: This type of process is in charge of load control. There is only one instance of this process in each system. c) Requesting_MAP_SSM: This type of process handles a MAP service requested during a dialogue. An instance of this process is created by the instance of the Secure_MAP_DSM process for each requested MAP service. d) Performing_MAP_SSM: This type of process handles a MAP service performed during a dialogue. An instance of this process is created by the instance of the Secure_MAP_DSM process for each MAP service to be performed.
7169 A process MAP_DSM exchanges external signals with other blocks as well as internal signals with the other processes 7170 of the MAP-Provider block. The external signals are either MAP service primitives or TC service primitives. 7171 The signal routes used by the various processes are organised as follows: 7172 7173 7174 7175 7176 7177
a) A process MAP_DSM receives and sends events from/to the MAP_user via signal route User1/User2. These routes use channels U1 and U2 respectively. b) A process MAP_DSM receives and sends events from/to the TCAP via signal route TC1/TC2. These routes use channels P1 and P2 respectively. c) A process MAP_DSM receives and sends events from/to the LOAD_CTRL process via signal route Load1/Load2. These routes are internal.
862
7178 7179 7180 7181 7182 7183 7184 7185 7186 7187 7188 7189
863 Release 4 864 865
217
3GPP TS 29.002 V4.17.0 (2006-06)
d) A process MAP_DSM sends events to the Performing_MAP_SSM processes via signal route Intern1. This route is internal. e) A process MAP_DSM sends events to the Requesting_MAP_SSM processes via signal route Intern2. This route is internal. f) A process Performing_MAP_SSM sends events to the MAP_USER via signal route User3. This route uses channel U2. g) A process Performing_MAP_SSM sends events to the TCAP via signal route TC3. This route uses channel P1. h) A process Requesting_MAP_SSM sends events to the MAP_USER via signal route User4. This route uses channel U2. i) A process Requesting_MAP_SSM sends events to the TCAP via signal route TC4. This route uses channel P1.
866
867 Release 4 868 869
218
3GPP TS 29.002 V4.17.0 (2006-06)
System MAP_Stack
Map_Stack1(1)
MAP_USER
U2
(MAP_REQ_SM)
U1
MAP_IND_SP
MAP_ Provider
P2
TC_REQ_SP
P1
TC_IND_SP
TCAP
7190
7191
Figure 15.6/1: System MAP_Stack
870
871 Release 4 872 873
219
3GPP TS 29.002 V4.17.0 (2006-06)
Block MAPProvider
MAP_Provider1(1)
TC2 TC1 Intern2
MAP_DSM
User1 User2 Intern1
Load2 Load1 Load_Ctrl
TC4
Requesting_ _MAP_SSM
Performing_ _MAP_SSM
User3
TC3
User4
7192
7193
Figure 15.6/2: Block MAP_Provider
874
875 Release 4 876 877
220
3GPP TS 29.002 V4.17.0 (2006-06)
Process MAP_DSM
Process to manage a MAP dialogue Comment 'MAP Dialogue State Machine'; DCL Components_Present, AC_Name_Unchanged, AC_Included, AC_Supported, Invoke_ID_Active, Last_Component, Operation_Exists, Alternative_Name_Exists, User_Info_Included BOOLEAN, Op_Code INTEGER;
MAP_DSM1(17)
IDLE
MAP_OPEN_ req
Store_AC_and_ user_data
For dialogue portion of TC-BEGIN
WAIT_FOR_ USER_ REQUESTS
7194
7195
Figure 15.6/3a: Process MAP_DSM (sheet 1)
878
879 Release 4 880 881
221
3GPP TS 29.002 V4.17.0 (2006-06)
Process MAP_DSM
Process to manage a MAP dialogue
MAP_DSM2(17)
WAIT_FOR_ USER_ REQUESTS
Any MAP specific request primitive
MAP_req
MAP_ DELIMITER_ req
MAP_U_ ABORT_ req
Set_Abort_ Reason:User_ Specific
Set_User_Info: MAP_User_ Abort_PDU
TC_U_ABORT_ req_VIA_TC1
Requesting_ MAP_SSM
Service_ Invoked_ VIA_Intern2
TC_BEGIN_ req_VIA_TC1
Terminated_ VIA_Intern2
To all active RSSMs
WAIT_FOR_ USER_ REQUESTS
DIALOGUE_ INITIATED
IDLE
7196
7197
Figure 15.6/3b: Process MAP_DSM (sheet 2)
882
883 Release 4 884 885
222
3GPP TS 29.002 V4.17.0 (2006-06)
Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED
MAP_DSM3(17)
TC_END_ ind
TC_ NOTICE_ ind
(FALSE) AC_Name_ Unchanged (TRUE) Set_Provider_ Reason: Abnormal_ MAP_Dialogue Set_Refuse_ Reason: Node_ Not_Reachable Set_Result: Dialogue_Refused
MAP_P_ABORT_ ind_VIA_User2 Set_Result: Dialogue_ Accepted
MAP_OPEN_ cnf_VIA_User2
MAP_OPEN_ cnf_VIA_User2
(FALSE) Components_ Present (TRUE)
Process_ Components
MAP_CLOSE_ ind_VIA_User2
Terminated_ VIA_Intern1
To all active PSSMs
Terminated_ VIA_Intern2
To all active RSSMs
Terminated_ VIA_Intern2
To all active RSSMs
IDLE
IDLE
7198
7199
Figure 15.6/3c: Process MAP_DSM (sheet 3)
886
887 Release 4 888 889
223
3GPP TS 29.002 V4.17.0 (2006-06)
Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED
MAP_DSM4(17)
TC_P_ ABORT_ind
Incorrect_ Transaction_ Portion P-Abort_ Parameter No_Common_ Dialogue_Portion
Else
Set_Provider_ Reason: Version_ Incompatibility
Set_Result: Dialogue_Refused
MAP_P_ABORT ind_VIA_User2
Set_Refuse_Reason: Potential_Version_ Incompatibility
MAP_OPEN_ cnf_VIA_User2
Terminated_ VIA_Intern2
To all active RSSMs
To all active RSSMs
Terminated_ VIA_Intern2
IDLE IDLE
7200
7201
Figure 15.6/3d: Process MAP_DSM (sheet 4)
890
891 Release 4 892 893
224
3GPP TS 29.002 V4.17.0 (2006-06)
Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED
MAP_DSM5(17)
TC_U_ ABORT_ind
TC_L_ CANCEL_ind
AC_Not_Supported Abort_Reason User_Specific MAP_OPEN_ cnf_VIA_User2
Accepted. The dialogue is considered implictly accepted when something is received
(FALSE) Invoke_ID_ Active (TRUE)
Timer_Expiry_ VIA_Intern2
Set_Result: Dialogue_Refused
DIALOGUE_ INITIATED
Set_Refuse_ Reason: AC_ Not_Supported
MAP_OPEN_ cnf_VIA_User2
Terminated_ VIA_Intern2
To all active RSSMs
IDLE
7202
7203
Figure 15.6/3e: Process MAP_DSM (sheet 5)
894
895 Release 4 896 897
225
3GPP TS 29.002 V4.17.0 (2006-06)
Process MAP_DSM
Process to manage a MAP dialogue 4
MAP_DSM6(17)
User_ Information
User_Abort_PDU
Provider_Abort_PDU
Dialogue_Refused Set_Result: Dialogue_ Refused
No_User_Info Set_Result: Dialogue_ Refused
MAP_ Refuse_PDU_ Error
Invalid_ Destination_ Reference Set_Refuse_Reason: Invalid_Destination_ Reference
Invalid_ Originating_ Reference Set_Refuse_Reason: Invalid_Originating_ Reference
No_ Reason_ Given
Set_Refuse_Reason: No_Reason_Given
Set_Refuse_Reason: Potential_Version_ Incompatibility
MAP_P_ABORT_ ind_VIA_User2
MAP_P_ABORT_ ind_VIA_User2
MAP_OPEN_ cnf_VIA_User2
Terminated_ VIA_Intern2
To all active RSSMs
IDLE
7204
7205
Figure 15.6/3f: Process MAP_DSM (sheet 6)
898
899 Release 4 900 901
226
3GPP TS 29.002 V4.17.0 (2006-06)
Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED
MAP_DSM7(17)
MAP_U_ ABORT_req
MAP_CLOSE_ req
Set_Abort_Reason: User_Specific
Set_User_Info: MAP_User_ Abort_Info
Local
TC_U_ABORT_ req_VIA_TC1
Pre-arranged
TC_END_ req_VIA_TC1
Terminated_ VIA_Intern2
To all active RSSMs
IDLE
7206
7207
Figure 15.6/3g: Process MAP_DSM (sheet 7)
902
903 Release 4 904 905
227
3GPP TS 29.002 V4.17.0 (2006-06)
Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ INITIATED
MAP_DSM8(17)
TC_ CONTINUE_ ind
The first one
(FALSE) AC_Name_ Unchanged (TRUE)
Set_MAP_Provider_ Abort_Reason: Abnormal_Dialogue
MAP_P_ABORT_ ind_VIA_User2
Set_Result: Dialogue_ Accepted
Set_Abort_Reason_ User_Specific
MAP_OPEN_ cnf_VIA_User2
Set_User_Information: MAP_Provider_ Abort_Info
MAP_Provider_ Abort_Reason:= Abnormal_Dialogue
(FALSE) Components_ Present (TRUE) TC_U_ABORT_ req_VIA_TC1
Process_ Components
MAP_ DELIMITER_ req_VIA_User2
Terminated_ VIA_Intern2
To all active RSSMs
DIALOGUE_ ESTABLISHED
IDLE
7208
7209
Figure 15.6/3h: Process MAP_DSM (sheet 8)
906
907 Release 4 908 909
228
3GPP TS 29.002 V4.17.0 (2006-06)
Process MAP_DSM
Process to manage a MAP dialogue IDLE
MAP_DSM9(17)
TC_BEGIN_ ind
(FALSE) AC_ Included (TRUE)
AC_Vession =1 (FALSE) (TRUE)
(FALSE)
MAP_ Dialogue_PDU_ included
(TRUE)
Extract_User_ Information
MAP-OPEN dialogue PDU? Yes Yes User_Info required for AC? No No Invalid Parameter?
No
Yes
(FALSE) Components_ Present (TRUE) Check_Load_ VIA_Load1 TC_U_ABORT_ req_VIA_TC1
WAIT_FOR_ LOAD_CHECK_ RESULT1
IDLE
WAIT_FOR_ INIT_DATA
7210
7211
Figure 15.6/3i: Process MAP_DSM (sheet 9)
910
911 Release 4 912 913
229
3GPP TS 29.002 V4.17.0 (2006-06)
Process MAP_DSM
Process to manage a MAP dialogue
MAP_DSM10(17)
Set_MAP_Provider_ Abort_Reason: Abnormal_Dialogue
Set_User_Info: MAP_Provider_ Abort_Info
Set_Abort_Reason: User_Specific
TC_U_ABORT_ req_VIA_TC1
IDLE
7212
7213
Figure 15.6/3j: Process MAP_DSM (sheet 10)
914
915 Release 4 916 917
230
3GPP TS 29.002 V4.17.0 (2006-06)
Process MAP_DSM
Process to manage a MAP dialogue
MAP_DSM11(17)
WAIT_FOR_ INIT_DATA
WAIT_FOR_ LOAD_CHECK_ RESULT2
TC_INVOKE_ ind (Op_Code)
TC_L_ REJECT_ ind
Any_ OTHER_ ind
Load_OK
Overload
(FALSE) Operation_ Exists (TRUE) IDLE
ELSE Derive_ V1_AC Op_Code begin_ subscriber_ activity (FALSE) Last_ Component (TRUE)
Check_Load_ VIA_Load1
TC_U_ ABORT_req VIA_TC1
TC_U_ ABORT_req VIA_TC1
Build_ MAP_OPEN_ind_ Primitive
WAIT_FOR_ LOAD_CHECK_ RESULT2
IDLE
MAP_OPEN_ ind_VIA_ User2
Perform_ version_1_ protocol
IDLE
7214
7215
Figure 15.6/3k: Process MAP_DSM (sheet 11)
918
919 Release 4 920 921
231
3GPP TS 29.002 V4.17.0 (2006-06)
Process MAP_DSM
Process to manage a MAP dialogue WAIT_FOR_ LOAD_CHECK_ RESULT1
MAP_DSM12(17)
Load_OK
Overload
IDLE (FALSE) AC_ Supported (TRUE)
AC_Name:= Received_ AC_Name
(FALSE)
Alternative_ Name_ Exists (TRUE)
Set_ User_Data
AC_Name:= Received_ AC_Name
AC_Name:= Alternative_ AC_Name
MAP_OPEN_ ind_VIA_User2
(FALSE) Components_ Present (TRUE)
Process_ Components
Set_Abort_ Reason: AC_Not_ Supported
MAP_ DELIMITER_ ind_VIA_User2
TC_U_ABORT_ req_VIA_TC1
DIALOGUE_ PENDING
IDLE
7216
7217
Figure 15.6/3l: Process MAP_DSM (sheet 12)
922
923 Release 4 924 925
232
3GPP TS 29.002 V4.17.0 (2006-06)
Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ PENDING
MAP_DSM13(17)
MAP_OPEN_ rsp
MAP_U_ ABORT_ req
Refused Result Accepted
Set_Abort_ Reason: User_Specific
Set_Abort_ Reason: User_Specific
Build_MAP_ Refuse_PDU
Set_User_Info: MAP_User_ Abort_Info
TC_U_ ABORT_ req_VIA_TC1
Terminated_ VIA_Intern1
To all active PSSMs
DIALOGUE_ ACCEPTED
IDLE
7218
7219
Figure 15.6/3m: Process MAP_DSM (sheet 13)
926
927 Release 4 928 929
233
3GPP TS 29.002 V4.17.0 (2006-06)
Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ ACCEPTED
MAP_DSM14(17)
MAP_req
Any MAP specific request primitive
MAP_rsp
Any MAP specific response primitive
MAP_ DELIMITER_ req
Requesting_ MAP_SSM
Service_ Invoked_ VIA_Intern2
Response_ Issued_ VIA_Intern1
TC_ CONTINUE_ req_VIA_TC1
DIALOGUE_ ACCEPTED
DIALOGUE_ ESTABLISHED
MAP_CLOSE_ req
MAP_U_ ABORT_ req
Set_Abort_ Reason: User_Specific
User_Info:= MAPUserAbortInfo
TC_END_ req_VIA_TC1
TC_U_ ABORT_ req_VIA_TC1
Terminated_ VIA_Intern1
To all active PSSMs
Terminated_ VIA_Intern2
To all active RSSMs
IDLE
7220
7221
Figure 15.6/3n: Process MAP_DSM (sheet 14)
930
931 Release 4 932 933
234
3GPP TS 29.002 V4.17.0 (2006-06)
Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ ESTABLISHED
MAP_DSM15(17)
MAP_req
Any MAP specific request primitive
MAP_rsp
Any MAP specific response primitive
MAP_ DELIMITER_ req
Requesting_ MAP_SSM
Service_ Invoked_ VIA_Intern2
Response_ Issued_ VIA_Intern1
TC_ CONTINUE_ req_VIA_TC1
DIALOGUE_ ESTABLISHED
DIALOGUE_ ESTABLISHED
TC_L_ CANCEL_ ind
TC_ NOTICE_ ind
TC_ CONTINUE_ ind
(FALSE) And SSM active Invoke_ ID_Active (TRUE) Components_ Present (TRUE)
(FALSE)
Process_ Components
Timer_Expiry_ VIA_Intern2
MAP_ NOTICE_ ind_VIA_User2
MAP_ DELIMITER_ ind_VIA_User2
DIALOGUE_ ESTABLISHED
7222
7223
Figure 15.6/3o: Process MAP_DSM (sheet 15)
934
935 Release 4 936 937
235
3GPP TS 29.002 V4.17.0 (2006-06)
Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ ESTABLISHED
MAP_DSM16(17)
TC_END_ ind
MAP_ CLOSE_ req
(FALSE) Components_ Present (TRUE)
Process_ Components
MAP_CLOSE_ ind_VIA_User2
TC_END_ req_VIA_TC1
Terminated_ VIA_Intern1
To all active PSSMs
Terminated_ VIA_Intern2
To all active RSSMs
IDLE
7224
7225
Figure 15.6/3p: Process MAP_DSM (sheet 16)
938
939 Release 4 940 941
236
3GPP TS 29.002 V4.17.0 (2006-06)
Process MAP_DSM
Process to manage a MAP dialogue DIALOGUE_ ESTABLISHED
MAP_DSM17(17)
TC_U_ ABORT_ ind
TC_P_ ABORT_ ind
MAP_U_ ABORT_ req
Provider_Abort_PDU User_Info User_Abort_PDU
Set_Abort_ Reason: User_Specific
Set_User_Info: MAP_User_ Abort_Info
MAP_U_ ABORT_ ind_VIA_User2
MAP_P_ ABORT_ ind_VIA_User2
TC_U_ ABORT_ req_VIA_TC1
Terminated_ VIA_Intern1
To all active PSSMs
Terminated_ VIA_Intern2
To all active RSSMs
IDLE
7226
7227
Figure 15.6/3q: Process MAP_DSM (sheet 17)
942
943 Release 4 944 945
237
3GPP TS 29.002 V4.17.0 (2006-06)
Procedure Process_Components
Procedure to process components received in a TC message
Proc_Comp1(5)
Comment: 'Components from TCAP' DCL Op_Code, Operation_Class INTEGER, Operation_Exists, Last_Component, Invoke_ID_Present, Invoke_ID_Assigned, Linked_ID_Present, Linked_ID_Assigned, Linked_Operation_Allowed, v3_Or_Higher_Dialogue BOOLEAN;
WAIT_FOR_ COMPONENTS
TC_INVOKE_ ind(Op_Code)
Invoke_ ID_ Assigned (TRUE)
(FALSE)
(TRUE) For this AC Operation_ Exists (FALSE) Linked_ ID_ Present (TRUE)
(FALSE) Set_Problem_ Code: Duplicated_ Invoke_ID Set_Problem_ Code: Unrecognised_ Operation 1
TC_U_ REJECT_ req_VIA_TC1
TC_U_ REJECT_ req_VIA_TC1
Performing_ MAP_SSM
(FALSE)
v3_Or_ Higher_ Dialogue (TRUE)
Service_ Invocation_ Received_ VIA_Intern1
Set_Diagnostic: Abnormal_Event_ Received_ From_Peer
MAP_NOTICE_ ind_VIA_User2
(FALSE) Last_ Component (TRUE)
WAIT_FOR_ COMPONENTS
7228
7229
Figure 15.6/4a: Procedure Process_Components (sheet 1)
946
947 Release 4 948 949
238
3GPP TS 29.002 V4.17.0 (2006-06)
Procedure Process_Components
Procedure to process components received in a TC message
Proc_Comp2(5)
(FALSE)
Linked_ ID_ Assigned (TRUE)
Set_Problem_ Code: Linked_ID_ Not_Assigned
(4) Operation_ Class (1,2,3)
TC_U_REJECT_ req_VIA_TC1
Linked_ Service_ Invoked_ VIA_Intern2
Linked_ Request_ Received_ VIA_Intern2
Set_Diagnostic: Abnormal_Event_ Received_ From_Peer
Performing_ MAP_SSM
MAP_NOTICE_ ind_VIA_User2
Service_ Invocation_ Received_ VIA_Intern1
(FALSE) Last_ Component (TRUE)
WAIT_FOR_ COMPONENTS
7230
7231
Figure 15.6/4b: Procedure Process_Components (sheet 2)
950
951 Release 4 952 953
239
3GPP TS 29.002 V4.17.0 (2006-06)
Procedure Process_Components
Procedure to process components received in a TC message WAIT_FOR_ COMPONENTS
Proc_Comp3(5)
TC_ RESULT_L_ ind
TC_ RESULT_NL_ ind
TC_U_ ERROR_ ind
(FALSE) Invoke_ID_ Assigned (TRUE) Invoke_ID_ Assigned (TRUE)
(FALSE) Invoke_ID_ Assigned (TRUE)
(FALSE)
Set_Problem_ Code: Invoke_ID_ Not_Assigned
TC_U_REJECT_ req_VIA_TC1
Set_Diagnostic: Abnormal_Event_ Received_ From_Peer
Result_ Received_ VIA_Intern2
Partial_ Result_ Received_ VIA_Intern2
Negative_ Result_ Received_ VIA_Intern2
MAP_NOTICE_ ind_VIA_User2
(FALSE) Last_ Component (TRUE)
WAIT_FOR_ COMPONENTS
7232
7233
Figure 15.6/4c: Procedure Process_Components (sheet 3)
954
955 Release 4 956 957
240
3GPP TS 29.002 V4.17.0 (2006-06)
Procedure Process_Components
Procedure to process components received in a TC message WAIT_FOR_ COMPONENTS
Proc_Comp4(5)
TC_L_ REJECT_ ind
TC_R_ REJECT_ ind
(FALSE) Invoke_ID_ Present (TRUE) rr_problem, re_problem, general_problem Problem Type invoke_problem Problem Type invoke_problem rr_problem, re_problem, general_problem
(FALSE) Invoke_ID_ Assigned (TRUE) Invoke_ID_ Assigned (TRUE)
(FALSE)
Provider_ Reject_ Received_ VIA_Intern2
MAP_ NOTICE_ind_ VIA_User2
Provider_ Reject_ Received_ VIA_Intern2
MAP_ NOTICE_ind_ VIA_User2
(FALSE) Last_ Component (TRUE)
WAIT_FOR_ COMPONENTS
7234
7235
Figure 15.6/4d: Procedure Process_Components (sheet 4)
958
959 Release 4 960 961
241
3GPP TS 29.002 V4.17.0 (2006-06)
Procedure Process_Components
Procedure to process components received in a TC message WAIT_FOR_ COMPONENTS
Proc_Comp5(5)
TC_U_ REJECT_ ind
rr_problem, re_problem Problem Type invoke_problem
(FALSE) Invoke_ID_ Assigned (TRUE)
User_Reject_ Received_ VIA_Intern2
MAP_ NOTICE_ind_ VIA_User2
(FALSE) Last_ Component (TRUE)
WAIT_FOR_ COMPONENTS
7236
7237
Figure 15.6/4e: Procedure Process_Components (sheet 5)
962
963 Release 4 964 965
242
3GPP TS 29.002 V4.17.0 (2006-06)
Process Load_Ctrl
Process to verify whether offered dialogue should be discarded because of overload Comment 'LOAD CONTROL'; DCL Congestion, Dialogue_Acceptable BOOLEAN
Load_Ctrl1(1)
IDLE
Check_Load
(FALSE) Congestion
(TRUE)
(FALSE) Dialogue_ Acceptable (TRUE)
Load_OK_ VIA_Load2
Overload_ VIA_Load2
Load_OK_ VIA_Load2
IDLE
7238
7239
Figure 15.6/5: Process Load_Ctrl
966
967 Release 4 968 969
243
3GPP TS 29.002 V4.17.0 (2006-06)
Process Requesting_MAP_SSM
Process to handle MAP service requests and the responses from the distant entity
MAP_RSSM1(4)
Comment 'Requesting MAP Service State Machine': DCL Argument_Correct, Error_Code_Correct, Linked_Request_Defined, Syntax_Correct, MAP_Iinitiated, Unexpected_Data, Implicit_Cnf, Linked_Operation_Allowed, W ait_For_Cnf, Service_Parameter_Available BOOLEAN, Operation_Class INTEGER;
IDLE
Service_ Invoked
A service has been invoked by the MAP user
Set_Operation__ Code_and_TCAP_ Parameters
TC_INVOKE_ req_VIA_TC4
(FALSE) W ait_ For_Cnf (TRUE)
W AIT_FOR_ CONFIRM
7240
7241
Figure 15.6/6a: Process Requesting_MAP_SSM (sheet 1)
970
971 Release 4 972 973
244
3GPP TS 29.002 V4.17.0 (2006-06)
Process Requesting_MAP_SSM
Process to handle MAP service requests and the responses from the distant entity WAIT_FOR_ CONFIRM
MAP_RSSM2(4)
Result_ Received
Partial_ Result_ Received
Negative_ Result_ Received
(FALSE) Syntax_ Correct (TRUE)
(FALSE) Syntax_ Correct (TRUE) Error_Code_ Correct (TRUE)
(FALSE)
Partial_ Result_ Correct (TRUE)
(FALSE)
TC_U_ CANCEL_ req_VIA_TC4
Store_ Partial_ Info
(FALSE) Syntax_ Correct (TRUE) 1
Append_ Partial_ Info
WAIT_FOR_ CONFIRM
Service_ Parameters_ Available (TRUE)
(FALSE)
Service_ Parameter_ Available (TRUE)
(FALSE)
Set_Provider_ Error: Invalid_ Response_ Received
(TRUE) Unexpected_ Data_Value (FALSE)
(TRUE) Unexpected_ Data (FALSE) MAP_cnf_ VIA_User4
Set_Provider_ Error: Invalid_ Response_ Received
Set_Problem_ Code: Mistyped_ Parameter'
Set_User_ Error
Set_Provider_ Error: Invalid_ Response_ Received
MAP_cnf_ VIA_User4
TC_U_REJECT_ req_VIA_TC4
MAP_cnf_ VIA_User4
7242
7243
Figure 15.6/6b: Process Requesting_MAP_SSM (sheet 2)
974
975 Release 4 976 977
245
3GPP TS 29.002 V4.17.0 (2006-06)
Process Requesting_MAP_SSM
Process to handle MAP service requests and the responses from the distant entity W AIT_FOR_ CONFIRM
MAP_RSSM3(4)
Linked_ Request_ Received
Terminated
User_ Reject_ Received
Linked_ Service_ Invoked
Find_Parent_ Operation_ Code
Implicit_Cnf:= TRUE
Linked_ Operation_ Allowed (TRUE)
(FALSE) W AIT_FOR_ CONFIRM
1 (FALSE)
Argument_ Correct (TRUE) (TRUE) (FALSE) MAP_ Initiated (TRUE) (FALSE)
Service_ Parameters_ Available
Set_ Problem_ Code
Set_Provider_ Error: Data_ Missing
TC_U_ REJECT_ req_VIA_TC4
Set_Provider_ Error
Set_User_ Error
MAP_cnf_ VIA_User4
MAP_cnf_ VIA_User4
7244
7245
Figure 15.6/6c: Process Requesting_MAP_SSM (sheet 3)
978
979 Release 4 980 981
246
3GPP TS 29.002 V4.17.0 (2006-06)
Process Requesting_MAP_SSM
Process to handle MAP service requests and the responses from the distant entity WAIT_FOR_ CONFIRM
MAP_RSSM4(4)
Provider_ Reject_ Received
Timer_ Expiry
(4) Associated with the service Operation_ Class (1,3)
(2)
'A linked operation should have been invoked'
Linked_ Request_ Defined (TRUE)
(FALSE)
(FALSE) Implicit_ Cnf (TRUE)
Set_Provider_ Error
Set_Provider_ Error
MAP_cnf_ VIA_User4
MAP_cnf_ VIA_User4
MAP_cnf_ VIA_User4
7246
7247
Figure 15.6/6d: Process Requesting_MAP_SSM (sheet 4)
982
983 Release 4 984 985
247
3GPP TS 29.002 V4.17.0 (2006-06)
Process Performing_MAP_SSM
Process to handle an invoke component received from the peer and the response from the user
MAP_PSSM1(2)
Comment 'Performing MAP Service State Machine': DCL Argument_Correct, Service_Identifiable, Service_Parameters_Available, Unexpected_Data, Length_OK, User_Error_Present, Linked_Request, Specific_Error, More_Data, Cnf_Required BOOLEAN, Operation_Class INTEGER, TIMER Guard_Timer COMMENT 'expires if MAP user does not respond';
IDLE
Service_ Invocation_ Received
(FALSE) Is the syntax correct ? Argument_ Correct (TRUE) (TRUE) Service_ Identifiable (FALSE) Service_ Parameters_ Available (TRUE) (FALSE) Discard_ Invocation
Discard_ Invocation
Operation_ Class
Associated with the service
(1,2) Operation_ Class Associated with the service 1
(3,4)
(3,4)
(1,2) Set_Error: Unexpected_ Data_Value
Set_Error: Data_Missing
(TRUE) Unexpected_ Data (FALSE) Set_Problem_ Code: Mistyped_ Parameter
MAP_ind_ VIA_User3
Discard_ Invocation
(FALSE) Cnf_ Required (TRUE) (1,2) Set_ (Guard_Timer) (3,4) MAP_NOTICE_ ind_VIA_User3 MAP_NOTICE_ ind_VIA_User3 Operation_ Class Associated with the service TC_U_ERROR_ req_VIA_TC3 TC_U_REJECT_ req_VIA_TC3
WAIT_FOR_ RESPONSE
7248
7249
Figure 15.6/8a: Process Performing_MAP_SSM (sheet 1)
986
987 Release 4 988 989
248
3GPP TS 29.002 V4.17.0 (2006-06)
Process Performing_MAP_SSM
Process to handle an invoke component received from the peer and the response from the user WAIT_FOR_ RESPONSE
MAP_PSSM2(2)
Guard_ Timer_ Expired
Response_ Issued
by the MAP user or the Secure_ Performing_MAP_SSM
Terminated
(TRUE) User_Error_ Present (FALSE)
(FALSE) Linked_ Request (TRUE) Specific_ Error (TRUE)
(FALSE)
(TRUE) Length_ O.K. (FALSE)
Split_ info
TC_ RESULT_NL_ req_VIA_TC3
(FALSE) more_ data (TRUE)
Set_Operation_ Code_and_ TCAP_Param
Set_Error_ Code
Set_Problem_ Code
TC_ RESULT_L_ req_VIA_TC3
TC_INVOKE_ req_VIA_TC3
TC_U_ERROR_ req_VIA_TC3
TC_U_REJECT_ req_VIA_TC3
7250
7251
Figure 15.6/8b: Process Performing_MAP_SSM (sheet 2)
990
991 Release 4 992 993
249
3GPP TS 29.002 V4.17.0 (2006-06)
7252 7253
16
Mapping on to TC services
16.1 Dialogue control
7254 Dialogue control services are mapped to TC dialogue handling services. The TC-UNI service is not used by the MAP 7255 PM.
7256
16.1.1 Directly mapped parameters
7257 The following parameters of the MAP-OPEN request and indication primitives are directly mapped on to the 7258 corresponding parameters of the TC-BEGIN primitives: 7259 7260
destination address; originating address.
7261 7262 16.1.2.1
16.1.2 Use of other parameters of dialogue handling primitives
Dialogue Id
7263 The value of this parameter is associated with the MAP PM invocation in an implementation dependent manner.
7264 16.1.2.2
Application-context-name
7265 The application-context-name parameter of a MAP primitive is mapped to the application-context-name parameter of 7266 TC dialogue handling primitives according to the rules described in clause 15.1.
7267 16.1.2.3
User information
7268 The user information parameter of TC dialogue primitives is used to carry the MAP dialogue APDUs.
7269 16.1.2.4
Component present
7270 This parameter is used by the MAP PM as described in CCITT Recommendation Q.771. It is not visible to the MAP 7271 user.
7272 16.1.2.5
Termination
7273 The value of this parameter of the TC-END request primitive is set by the MAP PM on the basis of the release method 7274 parameter of the MAP-CLOSE request primitive, except when the dialogue state machine is in the state DIALOGUE 7275 INITIATED, in which case the Termination parameter shall always indicate "pre-arranged end".
7276 16.1.2.6
7277 7278 7279 7280 7281
P-Abort-Cause
Values of the P-abort-cause parameter are mapped to the values of the provider-reason parameter of the MAP-P-ABORT indication primitive according to table 16.1/1, except in the dialogue initiated phase for the "incorrectTransactionPortion" and "noCommonDialoguePortion" values which are mapped to the "potential incompatibility problem" value of the refuse-reason parameter of the MAP-OPEN cnf primitive. The source parameter in the MAP-P-ABORT ind takes the value "TC problem".
7282 16.1.2.7
-
Quality of service
7283 The quality of service of TC request primitives is set by the MAP as shown below. 7284
Return option: "Return message on error" or "Discard message on error" as required by the network operator;
994
7285 7286 7287 7288 7289
995 Release 4 996 997
250
3GPP TS 29.002 V4.17.0 (2006-06)
Sequence control: "Sequence guaranteed" or "Sequence result not guaranteed" as required by the network operator; "Sequence guaranteed" shall be used when a segmented result is to be transferred (e.g. subscriber data in response to SendParameters). It may also be appropriate to use Sequence guaranteed when a series of InsertSubscriberData, ProcessAccessSignalling or ForwardAccessSignalling operations is used.
7290 It is essential that the TC message which indicates acceptance of a dialogue opening request is received by the dialogue 7291 initiator before any subsequent message in that dialogue; otherwise the dialogue opening will fail. The dialogue 7292 responder shall ensure that this requirement is met by: 7293 7294 7295 7296 7297 7298
Sending the dialogue acceptance message in a TC-END, if the dialogue structure requires it; or Using "Sequence guaranteed", if the dialogue acceptance message is sent in a TC-CONTINUE; or Waiting until the dialogue acceptance message has been acknowledged by the dialogue initiator before sending a subsequent message, if the dialogue acceptance message is sent in a TC-CONTINUE. Table 16.1/1: Mapping of P-Abort cause in TC-P-ABORT indication on to provider-reason in MAP-P-ABORT indication
TC P-Abort cause MAP provider-reason unrecognised message type provider malfunction unrecognised transaction Id supporting dialogue released badlyFormattedTransactionPortion provider malfunction incorrectTransactionPortion provider malfunction (note) resourceLimitation resource limitation abnormalDialogue provider malfunction noCommonDialoguePortion version incompatibility NOTE: Or version incompatibility in the dialogue initiated phase.
7299
7300
16.2 Service specific procedures
16.2.1 Directly mapped parameters
7301 Specific services are mapped to TC component handling services.
7302
7303 The Invoke Id parameter of the MAP request and indication primitive is directly mapped on to the Invoke Id parameter 7304 of the component handling primitives.
7305 7306 16.2.2.1
16.2.2 Use of other parameters of component handling primitives
Dialogue Id
7307 The value of this parameter is associated with the MAP PM invocation in an implementation dependent manner.
7308 16.2.2.2
Class
7309 The value of this parameter is set by the MAP PM according to the type of the operation to be invoked.
7310 16.2.2.3
7311 7312 7313 7314
Linked Id
When a service response is mapped to a class 4 operation, the value of this parameter is set by the MAP PM and corresponds to the value assigned by the user to the initial service request (i.e. the value of the invoke ID parameter of the request primitive). Otherwise if such a parameter is included in MAP request/indication primitives it is directly mapped to the linked ID parameter of the associated TC-INVOKE request/indication primitives.
998
7315 16.2.2.4
999 Release 4 1000 1001
251
3GPP TS 29.002 V4.17.0 (2006-06)
Operation
7316 When mapping a request primitive on to a Remote Operations PDU (invoke), the MAP PM shall set the operation code 7317 according to the mapping described in table 16.2/1. 7318 When mapping a response primitive on to a Remote Operations service, the MAP PM shall set the operation code of the 7319 TC-RESULT-L/NL primitive (if required) to the same value as the one received at invocation time. 7320
Table 16.2/1: Mapping of MAP specific services on to MAP operations
MAP-SERVICE MAP-ACTIVATE-SS MAP-ACTIVATE-TRACE-MODE MAP-ALERT-SERVICE-CENTRE MAP-ANY-TIME-INTERROGATION MAP_AUTHENTICATION_FAILURE_REPORT MAP-ANY-TIME-MODIFICATION MAP-ANY-TIME-SUBSCRIPTION-INTERROGATION MAP-CANCEL-LOCATION MAP-CHECK-IMEI MAP-DEACTIVATE-SS MAP-DEACTIVATE-TRACE-MODE MAP-DELETE-SUBSCRIBER-DATA MAP-ERASE-CC-ENTRY MAP-ERASE-SS MAP-FAILURE-REPORT MAP-FORWARD-ACCESS-SIGNALLING MAP-FORWARD-CHECK-SS-INDICATION MAP-FORWARD-GROUP-CALL-SIGNALLING MAP-MT-FORWARD-SHORT-MESSAGE MAP-MO-FORWARD-SHORT-MESSAGE MAP-GET-PASSWORD MAP-INFORM-SERVICE-CENTRE MAP-INSERT-SUBSCRIBER-DATA MAP-INTERROGATE-SS MAP-IST-ALERT MAP-IST-COMMAND MAP-NOTE-MS-PRESENT-FOR-GPRS MAP-NOTE-SUBSCRIBER-DATA-MODIFIED MAP-PREPARE-GROUP-CALL MAP-PREPARE-HANDOVER MAP-PREPARE-SUBSEQUENT-HANDOVER MAP-PROCESS-ACCESS-SIGNALLING MAP-PROCESS-GROUP-CALL-SIGNALLING MAP-PROCESS-UNSTRUCTURED-SS-REQUEST MAP-PROVIDE-ROAMING-NUMBER MAP-PROVIDE-SIWFS-NUMBER MAP-PROVIDE-SUBSCRIBER-LOCATION MAP-PROVIDE-SUBSCRIBER-INFO MAP-PURGE-MS MAP-READY-FOR-SM MAP-REGISTER-CC-ENTRY MAP-REGISTER-PASSWORD MAP-REGISTER-SS MAP-REMOTE-USER-FREE MAP-REPORT-SM-DELIVERY-STATUS MAP-RESET MAP-RESTORE-DATA MAP-SEND_GROUP-CALL_END_SIGNAL MAP-SEND-END-SIGNAL MAP-SEND-AUTHENTICATION-INFO MAP-SEND-IMSI MAP-SEND-IDENTIFICATION MAP-SEND-ROUTING-INFO-FOR-SM MAP-SEND-ROUTING-INFO-FOR-GPRS operation activateSS activateTraceMode alertServiceCentre anyTimeInterrogaton authenticationFailureReport anyTimeModification anyTimeSubscriptionInterrogation cancelLocation checkIMEI deactivateSS deactivateTraceMode deleteSubscriberData eraseCC-Entry eraseSS failureReport forwardAccessSignalling forwardCheckSsIndication forwardGroupCallSignalling mt-forwardSM mo-forwardSM getPassword informServiceCentre insertSubscriberData interrogateSs istAlert istCommand noteMsPresentForGprs noteSubscriberDataModified prepareGroupCall prepareHandover prepareSubsequentHandover processAccessSignalling processGroupCallSignalling processUnstructuredSS-Request provideRoamingNumber provideSIWFSNumber provideSubscriberLocation provideSubscriberInfo purgeMS readyForSM registerCC-Entry registerPassword registerSS remoteUserFree reportSmDeliveryStatus reset restoreData sendGroupCallEndSignal sendEndSignal sendAuthenticationInfo sendIMSI sendIdentification sendRoutingInfoForSM sendRoutingInfoForGprs
1002
1003 Release 4 252 1004 1005 MAP-SEND-ROUTING-INFO-FOR-LCS MAP-SEND-ROUTING-INFORMATION MAP-SET-REPORTING-STATE MAP-SIWFS-SIGNALLING-MODIFY MAP-STATUS-REPORT MAP-SUBSCRIBER-LOCATION-REPORT MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION MAP-UNSTRUCTURED-SS-NOTIFY MAP-UNSTRUCTURED-SS-REQUEST MAP-UPDATE-GPRS-LOCATION MAP-UPDATE-LOCATION MAP-NOTE-MM-EVENT 7321
3GPP TS 29.002 V4.17.0 (2006-06) sendRoutingInfoForLCS sendRoutingInfo setReportingState SIWFSSignallingModify statusReport subscriberLocationReport ss-Invocation-Notification unstructuredSS-Notify unstructuredSS-Request updateGprsLocation updateLocation NoteMM-Event
7322 16.2.2.5
Error
7323 The error parameter in a TC-U-ERROR indication primitive is mapped to the user error parameter in the MAP confirm 7324 primitive of the service associated with the operation to which the error is attached. 7325 The user error parameter in MAP response primitives is mapped to the error parameter of the TC-U-ERROR request 7326 primitive, except for "initiating-release" and "resource-limitation" which are mapped to the problem code parameter of 7327 the TC-U-REJECT request primitive.
7328 16.2.2.6
Parameters
7329 The parameters of MAP specific request and indication primitives are mapped to the argument parameter of TC7330 INVOKE primitives. 7331 The parameters of MAP specific response and confirm primitives are mapped to the result parameter of TC-RESULT-L 7332 primitives, the parameter of TC-U-ERROR primitives or the argument of TC-INVOKE primitives when mapping on 7333 linked class 4 operations is used.
7334 16.2.2.7
Time out
7335 The value of this parameter is set by the MAP PM according to the type of operation invoked.
7336 16.2.2.8
Last component
7337 This parameter is used by the MAP PM as described in CCITT Recommendation Q.711. It is not visible from the MAP 7338 user.
7339 16.2.2.9 7340 16.2.2.9.1
Problem code
Mapping to MAP User Error
7341 The following values of the user error parameter are mapped as follows to values of the TC problem code parameter. 7342 These values are generated by the MAP user. This mapping is valid from the TC-U-REJECT indication primitive to the 7343 MAP confirm service primitive and from the MAP response service primitive to the TC-U-REJECT request primitive. 7344 7345
Table 16.2/2: Mapping of MAP User Error parameter on to TC problem code in TC-U-REJECT primitives
MAP User Error resource limitation initiating release TC problem code resource limitation initiating release
7346
7347 16.2.2.9.2
Mapping to MAP Provider Error parameter
7348 The following values of the TC problem code parameter of the TC-U-REJECT indication primitive are mapped as 7349 follows to values of the MAP Provider Error parameter of the MAP confirm primitive.
1006
7350
1007 Release 4 1008 1009
253
3GPP TS 29.002 V4.17.0 (2006-06)
Table 16.2/3: Mapping of TC problem code in TC-U-REJECT on to MAP Provider Error parameter
TC problem code duplicated invoke Id unrecognised operation mistyped parameter MAP Provider Error duplicated invoke id service not supported mistyped parameter
7351 7352 The following values of the problem code parameters of the TC-L-REJECT primitive are mapped to values of the 7353 provider error parameter of the MAP confirm primitive as follows. 7354
Table 16.2/4: Mapping of TC problem code in TC-L-REJECT on to MAP Provider Error parameter
TC problem code return result unexpected return error unexpected MAP Provider Error unexpected response from the peer unexpected response from the peer
7355
7356 16.2.2.9.3
Mapping to diagnostic parameter
7357 The following values of the problem code parameter of the TC-R-REJECT and TC-U-REJECT primitive are mapped to 7358 values of the diagnostic parameter of the MAP-NOTICE indication primitive as follows: 7359 7360
Table 16.2/5: Mapping of TC problem code of TC-R-REJECT and TC-U-REJECT on to diagnostic parameter
TC problem code General problem Invoke problem - unrecognised linked ID - linked response unexpected - unexpected linked operation Return result problem - unrecognised invoke ID - return result unexpected - mistyped parameter Return error problem - unrecognised invoke ID - return error unexpected - unrecognised error - unexpected error - mistyped parameter MAP diagnostic - abnormal event detected by the peer - abnormal event detected by the peer - response rejected by the peer - response rejected by the peer - response rejected by the peer - response rejected by the peer - response rejected by the peer - response rejected by the peer - response rejected by the peer - response rejected by the peer - response rejected by the peer - response rejected by the peer
7361 7362 The following values of the problem code parameter of the TC-L-REJECT primitive are mapped to values of the 7363 diagnostic parameter of the MAP-NOTICE indication primitive as follows. 7364
Table 16.2/6: Mapping of TC problem code of TC-L-REJECT on to diagnostic parameter
TC problem code General problems Invoke problem - unrecognised linked ID Return result problem - unrecognised invoke ID Return error problem - unrecognised invoke ID MAP diagnostic - abnormal event received from the peer - abnormal event received from the peer - abnormal event received from the peer - abnormal event received from the peer
7365
1010
1011 Release 4 1012 1013
254
3GPP TS 29.002 V4.17.0 (2006-06)
7366 7367
7368 7369 7370 7371
17
Abstract syntax of the MAP protocol
17.1 General
This clause specifies the Abstract Syntaxes for the Mobile Application Part as well as the associated set of Operations and Errors, using the Abstract Syntax Notation One (ASN.1), defined in CCITT Recommendation X.208 (1988) or X.680 (1994) with additions as defined in clause 17.1.4 on Compatibility Considerations and the OPERATION and ERROR external MACROs, defined in CCITT Recommendation Q.773.
7372 The Abstract Syntax is defined for all interfaces specified in clause 4.4 except for the A- and B-interfaces. 7373 The Mobile Application Part protocol is defined by two Abstract Syntaxes: 7374 7375 7376 7377 7378 7379 7380 7381 7382 7383 7384 7385
one Abstract Syntax which encompass all Operations; and Errors identified by the various MAP subsystem numbers.
This Abstract Syntax represents the set of values each of which is a value of the ASN.1 type TCAPMessages. MessageType as defined in CCITT Recommendation Q.773 with the ANY DEFINED BY sections resolved by the operation and error codes included in the ASN.1 module MAP-Protocol. However, only the subset of this abstract syntax which is required by the procedures defined for an entity needs to be supported: one Abstract Syntax identified by the OBJECT IDENTIFIER value MAP-DialogueInformation.mapDialogueAS.
This Abstract Syntax represents the set of values each of which is a value of the ASN.1 type MAPDialogueInformation.MAP-DialoguePDU. Such a value of the ASN.1 single-ASN.1-type element is contained within the user-information element of the TCAPMessages.DialoguePortion ASN.1 type. This Abstract Syntax name is to be used as a direct reference.
7386
17.1.1 Encoding rules
7387 The encoding rules which are applicable to the defined Abstract Syntaxes are the Basic Encoding Rules for Abstract 7388 Syntax Notation One, defined in CCITT Recommendation X.690 with the same exceptions as in CCITT 7389 Recommendation Q.773 clause 4 Message Representation. 7390 When the definite form is used for length encoding, a data value of length less than 128 octets must have the length 7391 encoded in the short form. 7392 When the long form is employed to code a length, the minimum number of octets shall be used to code the length field. 7393 OCTET STRING values and BIT STRING values must be encoded in a primitive form. 7394 There is no restriction to the use of empty constructors (e.g. an empty SEQUENCE type). That is, the encoding of the 7395 content of any data value shall consist of zero, one or more octets.
7396
17.1.2 Use of TC
7397 The mapping of OPERATION and ERROR to TC components is defined in ETS 300 287 (version 2) which is based on 7398 CCITT Recommendation Q.773 (1992). 7399 7400 7401 7402 7403 7404
NOTE 1: The class of an operation is not stated explicitly but is specified as well in the ASN.1 operation type definition. Class 1: RESULT and ERROR appear in ASN.1 operation type definition. Class 2: only ERROR appears in ASN.1 operation type definition. Class 3: only RESULT appears in ASN.1 operation type definition. Class 4: both RESULT and ERROR do not appear in ASN.1 operation type definition.
1014
7405 7406 7407 7408
1015 Release 4 1016 1017
255
3GPP TS 29.002 V4.17.0 (2006-06)
The ASN.1 data type which follows the keywords "ARGUMENT", "PARAMETER" or "RESULT" (for OPERATION and ERROR) is always optional from a syntactic point of view. However, except when specifically mentioned with the ASN.1 comment -- optional , the parameter part of a component has to be considered as mandatory from a semantic point of view.
7409 When an optional element is missing in an invoke component or in an inner data structure while it is required by the 7410 context, an error component is returned if specified in the operation type; the associated type of error is DataMissing. 7411 This holds also when the entire parameter of an invoke component is missing while it is required by the context. 7412 7413
NOTE 2: When a mandatory element is missing in the parameter or inner data structure of any component, a reject component is returned (if the dialogue still exists). The problem code to be used is "Mistyped parameter".
7414 The Timer Values used in the operation type definitions are indicated as ASN.1 comments. The Timer Value Ranges 7415 are: 7416 7417 7418 7419
= from 3 seconds to 10 seconds;
m = from 15 seconds to 30 seconds; ml = from 1 minute to 10 minutes; l = from 28 hours to 38 hours.
7420 17.1.2.1
7421 7422 7423 7424 7425 7426 7427 7428 7429
Use of Global Operation and Error codes defined outside MAP
An entity supporting an application context greater than 2 shall be capable of receiving an operation or error code, within an application context defined in GSM 09.02, encoded as either an Object Identifier (as defined in CCITT Recommendation X.690 (1994)) or an integer value (as defined in clause 17.5). Related restrictions regarding the use of Object Identifiers are as follows: The length of the Object Identifier shall not exceed 16 octets and the number of components of the Object Identifier shall not exceed 16. Object Identifiers shall be used only for operations or errors defined outside of GSM 09.02. Global error codes may be sent only in response to a global operation. If a standard operation is received then a global error code shall not be sent in response.
7430 Handling of an unknown operation codes by the receiving entity is defined in clause 15.1.1.
7431
17.1.3 Use of information elements defined outside MAP
7432 An information element or a set of information elements (messages) transparently carried in the Mobile Application 7433 Part but defined in other recommendations/technical specifications are handled in one of the following ways: 7434 7435 7436 7437 7438 7439 7440 7441 7442 7443
i) The contents of each information element (without the octets encoding the identifier and the length in the recommendation/technical specification where it is defined unless explicitly stated otherwise) is carried as the value of an ASN.1 NamedType derived from the OCTET STRING data type. Additionally, the internal structure may be explained by means of comments. In case of misalignment the referred to recommendation/technical specification takes precedence. ii) The complete information element (including the octets encoding the identifier and the length in the recommendation/technical specification where it is defined) or set of information elements and the identity of the associated protocol are carried as the value of the ExternalSignalInfo data type defined in the present document. Where more than one information element is carried, the information elements are sent contiguously with no filler octets between them.
1018
7444
1019 Release 4 1020 1021
256
3GPP TS 29.002 V4.17.0 (2006-06)
17.1.4 Compatibility considerations
7445 The following ASN.1 modules conform to CCITT Recommendation X.208 (1988) or X.680 (1994) (the only module 7446 which makes use of X.680 is MAP-ExtensionDataTypes), but in addition Ellipsis Notation ("..." - notation) is used as 7447 described in ITU-T Recommendation X.680 Amendment 1 (1995) wherever future protocol extensions are foreseen. 7448 7449 7450 7451
The "..." construct applies only to SEQUENCE and ENUMERATED data types. An entity supporting a version greater than 1 shall not reject an unsupported extension following "..." of that SEQUENCE or ENUMERATED data type. The Encoding Rules from clause 17.1.1 apply to every element of the whole Transfer Syntax especially to the ASN.1 type EXTERNAL.
7452 The extension container "privateExtensionList" is defined in this specification in order to carry extensions which are 7453 defined outside this specification. Private extensions can be defined by, for example, network operators, manufacturers, 7454 and regional standardisation bodies. 7455 Private extensions shall: 7456 7457 7458 7459 7460 7461
1) if included in operations of an AC of V2, follow the extension marker and be tagged using PRIVATE tags up to and including 29. NOTE: This type of extension is in most cases used only within a PLMN. 2) if included in operations of an AC of V3 or higher: be included only in the Private Extension Container that is defined in the specification. NOTE: This type of extension can be used between PLMNs.
7462 Private extensions shall not be included in v2 supplementary service operations. 7463 Private extensions shall not be included within user error for RegisterCCEntry and EraseCCEntry operations. 7464 PCS extensions shall be included in the PCS Extension Container that is defined in this specification. 7465 7466 7467 7468
In order to improve extensibility, a few error parameters have been defined as a CHOICE between the version 2 description and a SEQUENCE including the version 2 description and an extension container. Operations used in a v2application-context must consider only the first alternative while operations used in a vn-application-context (n>2) must consider only the second alternative.
7469
7470 7471 7472 7473 7474 7475 7476 7477 7478 7479 7480 7481 7482 7483 7484 7485
17.1.5 Structure of the Abstract Syntax of MAP
For each MAP parameter which has to be transferred by a MAP Protocol Data Unit (MAP message), there is a PDU field (an ASN.1 NamedType) whose ASN.1 identifier has the same name as the corresponding parameter, except for the differences required by the ASN.1 notation (blanks between words are removed or replaced by hyphen, the first letter of the first word is lower-case and the first letter of the following words are capitalised, e.g. "no reply condition time" is mapped to "noReplyConditionTime"). Additionally some words may be abbreviated as follows: bs basic service ch call handling cug closed user group
ho handover ic incoming call id identity info mm information mobility management
lcs location services ms mobile service oc outgoing call
1022
7486 7487 7488 7489 7490 7491 7492 7493 7494 7495
1023 Release 4 1024 1025
257
3GPP TS 29.002 V4.17.0 (2006-06)
om operation & maintenance pw Password sm short message service ss supplementary service
The MAP protocol is composed of several ASN.1 modules dealing with either operations, errors, data types, and, if applicable, split into those dealing with mobile services, call handling services, supplementary services and short message services. For operations and errors no values are assigned, but only the operation and error types in order to allow use of the defined types also by other protocols (e.g. 3GPP TS 24.080 [38]). The values (operation codes and error codes) are defined in a separate module. The ASN.1 source lines are preceded by line-numbers at the left margin in order to enable the usage of the cross-reference in annex A.
7496 The module containing the definition of the operation packages for MAP is: 7497
1. MAP-OperationPackages.
7498 The module containing the definition of the application contexts for MAP is: 7499
2. MAP-ApplicationContexts.
7500 The module containing the data types for the Abstract Syntax to be used for TCAPMessages.DialoguePortion for MAP 7501 is: 7502
3. MAP-DialogueInformation.
7503 The module containing the operation codes and error codes for MAP is: 7504
4. MAP-Protocol.
7505 The modules containing all operation type definitions for MAP are: 7506 7507 7508 7509 7510 7511 7512
5. MAP-MobileServiceOperations; 6. MAP-OperationAndMaintenanceOperations; 7. MAP-CallHandlingOperations; 8. MAP-SupplementaryServiceOperations; 9. MAP-ShortMessageServiceOperations; 10. MAP-Group-Call-Operations; 11. MAP-LocationServiceOperations
7513 The module containing all error type definitions for MAP is: 7514
12. MAP-Errors.
7515 Modules containing all data type definitions for MAP are: 7516 7517 7518 7519 7520 7521 7522
13. MAP-MS-DataTypes; 14. MAP-OM-DataTypes; 15. MAP-CH-DataTypes; 16. MAP-SS-DataTypes; 17. MAP-SS-Code; 18. MAP-SM-DataTypes; 19. MAP-ER-DataTypes;
1026
7523 7524 7525 7526 7527 7528
1027 Release 4 1028 1029
258
3GPP TS 29.002 V4.17.0 (2006-06)
20. MAP-CommonDataTypes; 21. MAP-TS-Code; 22. MAP-BS-Code; 23. MAP-ExtensionDataTypes; 24. MAP-GR-DataTypes; 25. MAP-LCS-DataTypes.
7529 References are made also to modules defined outside of the present document. They are defined in the technical 7530 specification Mobile Services Domain and technical specification Transaction Capability respectively: 7531 7532 7533
MobileDomainDefinitions; TCAPMessages; DialoguePDUs.
7534
17.1.6 Application Contexts
7535 The following informative table lists the latest versions of the Application Contexts used in this specification, with the 7536 operations used by them and, where applicable, whether or not the operation description is exactly the same as for 7537 previous versions. Information in 17.6 & 17.7 relates only to the ACs in this table. 7538
AC Name
locationCancellationContext equipmentMngtContext imsiRetrievalContext infoRetrievalContext interVlrInfoRetrievalContext handoverControlContext
AC Version
v3 v2 v2 v3 v3 v3
Operations Used
cancelLocation checkIMEI sendIMSI sendAuthenticationInfo sendIdentification prepareHandover forwardAccessSignalling sendEndSignal processAccessSignalling prepareSubsequentHandover readyForSM purgeMS alertServiceCentre reset processUnstructuredSS-Request unstructuredSS-Request unstructuredSS-Notify activateTraceMode deactivateTraceMode registerSS eraseSS activateSS deactivateSS registerPassword interrogateSS getPassword mo-forwardSM mt-forwardSM sendRoutingInfoForSM reportSM-DeliveryStatus InformServiceCentre updateLocation forwardCheckSs-Indication
Comments
the syntax of this operation has been extended in comparison with release 98 version
mwdMngtContext msPurgingContext shortMsgAlertContext resetContext networkUnstructuredSsContext tracingContext networkFunctionalSsContext
v3 v3 v2 v2 v2 v3 v2
shortMsgMO-RelayContext shortMsgMT-RelayContext shortMsgGatewayContext
v3 v3 v3
networkLocUpContext
v3
the syntax of this operation has been extended in comparison with release 96 version the syntax is the same in v1 & v2
1030
1031 Release 4 1032 1033
259
3GPP TS 29.002 V4.17.0 (2006-06)
AC Name
AC Version
Operations Used
restoreData insertSubscriberData activateTraceMode updateGprsLocation insertSubscriberData activateTraceMode insertSubscriberData deleteSubscriberData provideRoamingNumber sendRoutingInfo noteMsPresentForGprs sendRoutingInfoForGprs failureReport resumeCallHandling provideSubscriberInfo anyTimeInterrogation anyTimeSubscriptionInterrogation anyTimeModification ss-InvocationNotification provideSIWFSNumber sIWFSSignallingModify prepareGroupCall processGroupCallSignalling forwardGroupCallSignalling sendGroupCallEndSignal setReportingState statusReport remoteUserFree registerCC-Entry eraseCC-Entry istAlert istCommand provideSubscriberLocation subscriberLocationReport sendRoutingInfoForLCS
Comments
gprsLocationUpdateContext subscriberDataMngtContext roamingNumberEnquiryContext locationInfoRetrievalContext gprsNotifyContext gprsLocationInfoRetrievalContext failureReportContext callControlTransferContext subscriberInfoEnquiryContext anyTimeEnquiryContext anyTimeInfoHandlingContext ss-InvocationNotificationContext sIWFSAllocationContext groupCallControlContext
v3 v3 v3 v3 v3 v4 v3 v4 v3 v3 v3 v3 v3 v3
reportingContext callCompletionContext istAlertingContext ImmediateTerminationContext locationSvcEnquiryContext locationSvcGatewayContext
v3 v3 v3 v3 v3 v3
mm-EventReportingContext
v3
noteMM-Event
noteSubscriberDataModified authenticationFailureReport
subscriberDataModificationNotificati v3 onContext authenticationFailureReportContext v3
7539 7540
NOTE (*):
The syntax of the operations is not the same as in previous versions unless explicitly stated
7574 7575
17.2 Operation packages
17.2.1 General aspects
7576 This clause describes the operation-packages which are used to build the application-contexts defined in clause 17.3. 7577 Each operation-package is a specification of the roles of a pair of communicating objects (i.e. a pair of MAP-Providers), 7578 in terms of operations which they can invoke of each other. 7579 The grouping of operations into one or several packages does not necessarily imply any grouping in terms of 7580 Application Service Elements. 7581 The following ASN.1 MACRO is used to describe operation-packages in this clause:
1034
1035 Release 4 1036 1037
7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7595 7596 7597
260
3GPP TS 29.002 V4.17.0 (2006-06)
OPERATION-PACKAGE MACRO ::= BEGIN TYPE NOTATION ::= Symmetric | ConsumerInvokes SupplierInvokes | empty VALUE NOTATION ::= value(VALUE OBJECT IDENTIFIER) Symmetric ::= "OPERATIONS" "{" OperationList "}" ConsumerInvokes ::= "CONSUMER INVOKES" "{" OperationList "}" SupplierInvokes ::= "SUPPLIER INVOKES" "{" OperationList "}" | empty OperationList ::= Operation | OperationList "," Operation Operation ::= value(OPERATION) END
7598 Since the application-context definitions provided in clause 17.3 use only an informal description technique, only the 7599 type notation is used in the following clauses to define operation-packages. 7600 The following definitions are used throughout this clause (n>=2): 7601 7602 7603 7604 7605 7606 7607 7608
v1-only operation: An operation which shall be used only in v1 application-contexts; vn-only operation: An operation which shall be used only in vn application-contexts; v(n-1)-operation: An operation whose specification has not been modified since the MAP v(n-1) specifications or if the modifications are considered as not affecting v(n-1) implementations; v(n-1)-equivalent operation: The version of an operation which excludes all the information elements and errors which have been added since the MAP v(n-1) specification; vn-only package: An operation package which contains only vn-only operations; v(n-1)-package: An operation package which contains only v(n-1)- operations.
7609 The names of vn-packages are suffixed by "-vn" where n>=2. 7610 For each operation package which is not vn-only (n>=2) and which does not include only v(n-1)-operations, there is a 7611 v(n-1)-equivalent package. Except when a definition is explicitly provided in the following clauses, the 7612 v(n-1)-equivalent package includes the v(n-1)-equivalent operations of the operations which belong to this package.
7613 7614 17.2.2.1
17.2.2 Packages specifications
Location updating
7615 This operation package includes the operations required for location management procedures between HLR and VLR.
7616 7617 7618 7619 7620 7621 7622
LocationUpdatingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { updateLocation} SUPPLIER INVOKES { forwardCheckSs-Indication}
7623 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.
7624 17.2.2.2
Location cancellation
7625 This operation package includes the operations required for location cancellation and MS purging procedures between 7626 HLR and VLR and between HLR and SGSN.
7627 7628 7629 7630 7631
LocationCancellationPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { cancelLocation}
7632 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.
1038
7633 17.2.2.3
1039 Release 4 1040 1041
261
3GPP TS 29.002 V4.17.0 (2006-06)
Roaming number enquiry
7634 This operation package includes the operations required for roaming number enquiry procedures between HLR and 7635 VLR.
7636 7637 7638 7639 7640
RoamingNumberEnquiryPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { provideRoamingNumber}
7641 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.
7642 17.2.2.4
Information retrieval
7643 This operation package includes the operation required for the authentication information retrieval procedure between 7644 HLR and VLR and between HLR and SGSN.
7645 7646 7647 7648 7649 7650
InfoRetrievalPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { sendAuthenticationInfo}
7651 The v2-equivalent package is defined as follows:
7652 7653 7654 7655 7656 7657
InfoRetrievalPackage-v2 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { sendAuthenticationInfo}
7658 The v1-equivalent package is defined as follows:
7659 7660 7661 7662 7663 7664
InfoRetrievalPackage-v1 ::= OPERATION-PACKAGE -- Supplier is HLR or VLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { sendParameters}
7665 17.2.2.5
Inter-VLR information retrieval
7666 This operation package includes the operations required for inter VLR information retrieval procedures.
7667 7668 7669 7670 7671
InterVlrInfoRetrievalPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR if Consumer is VLR CONSUMER INVOKES { sendIdentification}
7672 The v2-equivalent package is defined as follows:
7673 7674 7675 7676 7677
InterVlrInfoRetrievalPackage-v2 ::= OPERATION-PACKAGE -- Supplier is VLR if Consumer is VLR CONSUMER INVOKES { sendIdentification}
7678 The v1-equivalent package is : InfoRetrievalPackage-v1.
7679 17.2.2.6
IMSI retrieval
7680 This operation package includes the operation required for the IMSI retrieval procedure between HLR and VLR.
7681 7682 7683 7684 7685
IMSIRetrievalPackage-v2 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { sendIMSI}
7686 This package is v2 only.
1042
7687 17.2.2.7
1043 Release 4 1044 1045
262
3GPP TS 29.002 V4.17.0 (2006-06)
Call control transfer
7688 This operation package includes the operation required for the call control transfer procedure between VMSC and 7689 GMSC.
7690 7691 7692 7693 7694
CallControlTransferPackage-v4 ::= OPERATION-PACKAGE -- Supplier is GMSC if Consumer is VMSC CONSUMER INVOKES { resumeCallHandling}
7695 The v3-equivalent package can be determined according to the rules described in clause 17.2.1.
7696 17.2.2.8 7697 17.2.2.9 7698 17.2.2.10
void Void Interrogation
7699 This operation package includes the operations required for interrogation procedures between MSC and HLR or NPLR.
7700 7701 7702 7703 7704
InterrogationPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR or NPLR if Consumer is MSC CONSUMER INVOKES { sendRoutingInfo}
7705 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.
7706 17.2.2.11 7707 17.2.2.12
Void Handover Control
7708 This operation package includes the operations required for handover procedures between MSCs.
7709 7710 7711 7712 7713 7714 7715 7716 7717 7718
HandoverControlPackage-v3 ::= OPERATION-PACKAGE -- Supplier is MSCB if Consumer is MSCA CONSUMER INVOKES { prepareHandover, forwardAccessSignalling} SUPPLIER INVOKES { sendEndSignal, processAccessSignalling, prepareSubsequentHandover}
7719 The v2-equivalent package can be determined according to the rules described in clause 17.2.1. 7720 The v1-equivalent package is defined as follows.
7721 7722 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732
HandoverControlPackage-v1 ::= OPERATION-PACKAGE -- Supplier is MSCB if Consumer is MSCA CONSUMER INVOKES { performHandover, forwardAccessSignalling, traceSubscriberActivity} SUPPLIER INVOKES { sendEndSignal, noteInternalHandover, processAccessSignalling, performSubsequentHandover}
1046
7733 17.2.2.13
1047 Release 4 1048 1049
263
3GPP TS 29.002 V4.17.0 (2006-06)
Subscriber Data management stand alone
7734 This operation package includes the operations required for stand alone subscriber data management procedures 7735 between HLR and VLR or between HLR and SGSN.
7736 7737 7738 7739 7740 7741
SubscriberDataMngtStandAlonePackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { insertSubscriberData, deleteSubscriberData}
7742 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.
7743 17.2.2.14
Equipment management
7744 This operation package includes the operations required for equipment management procedures between EIR and MSC 7745 or between EIR and SGSN.
7746 7747 7748 7749 7750 7751
EquipmentMngtPackage-v2 ::= OPERATION-PACKAGE -- Supplier is EIR if Consumer is MSC -- Supplier is EIR if Consumer is SGSN CONSUMER INVOKES { checkIMEI}
7752 The v1-equivalent package can be determined according to the rules described in clause 17.2.1.
7753 17.2.2.15
Subscriber data management
7754 This operation package includes the operations required for subscriber data management procedures between HLR and 7755 VLR or between HLR and SGSN.
7756 7757 7758 7759 7760
SubscriberDataMngtPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { insertSubscriberData}
7761 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.
7762 17.2.2.16
Location register restart
7763 This operation package includes the operations required for location register restart procedures between HLR and VLR 7764 or between HLR and SGSN.
7765 7766 7767 7768 7769
ResetPackage-v2 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { reset}
7770 The v1-equivalent package can be determined according to the rules described in clause 17.2.1.
7771 17.2.2.17
Tracing stand-alone
7772 This operation package includes the operations required for stand alone tracing procedures between HLR and VLR or 7773 between HLR and SGSN.
7774 7775 7776 7777 7778 7779
TracingStandAlonePackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { activateTraceMode, deactivateTraceMode}
7780 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.
1050
7781 17.2.2.18
1051 Release 4 1052 1053
264
3GPP TS 29.002 V4.17.0 (2006-06)
Functional SS handling
7782 This operation package includes the operations required for functional supplementary services procedures between VLR 7783 and HLR.
7784 7785 7786 7787 7788 7789 7790 7791 7792 7793 7794 7795
FunctionalSsPackage-v2 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { registerSS, eraseSS, activateSS, deactivateSS, registerPassword, interrogateSS} SUPPLIER INVOKES { getPassword}
7796 The v1-equivalent package can be determined according to the rules described in clause 17.2.1.
7797 17.2.2.19
Tracing
7798 This operation package includes the operations required for tracing procedures between HLR and VLR or between HLR 7799 and SGSN.
7800 7801 7802 7803 7804
TracingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is VLR or SGSN if Consumer is HLR CONSUMER INVOKES { activateTraceMode}
7805 The v1-equivalent and v2-equivalent packages can be determined according to the rules described in clause 17.2.1.
7806 17.2.2.20
Binding
7807 This operation package includes the operation required to initialise a supplementary service procedure between VLR 7808 and HLR or between gsmSCF and HLR.
7809 7810 7811 7812 7813
BindingPackage-v1 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { beginSubscriberActivity}
7814 This package is v1 only.
7815 17.2.2.21
Unstructured SS handling
7816 This operation package includes the operations required for unstructured supplementary services procedures between 7817 VLR and HLR, between the HLR and the gsmSCF, and between HLR and HLR.
7818 7819 7820 7821 7822 7823 7824 7825 7826
UnstructuredSsPackage-v2 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is gsmSCF or HLR if Consumer is HLR CONSUMER INVOKES { processUnstructuredSS-Request} SUPPLIER INVOKES { unstructuredSS-Request, unstructuredSS-Notify}
7827 The v1-equivalent package is defined as follows:
7828 7829 7830 7831 7832 7833
UnstructuredSsPackage-v1 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { processUnstructuredSS-Data}
1054
7834 17.2.2.22
1055 Release 4 1056 1057
265
3GPP TS 29.002 V4.17.0 (2006-06)
MO Short message relay services
7835 This operation package includes the operations required for short message relay service procedures between IWMSC 7836 and VMSC or between GMSC and MSC or between SGSN and IWMSC.
7837 7838 7839 7840 7841 7842 7843 7844 7845 7846 7847 7848 7849 7850
MOShortMsgRelayPackage-v3 ::= OPERATION-PACKAGE -- Supplier is IWMSC if Consumer is MSC -- Supplier is IWMSC if Consumer is SGSN CONSUMER INVOKES { MO-forwardSM} The v2-equivalent package is defined as follows: ShortMsgRelayPackage-v2 ::= OPERATION-PACKAGE -- Supplier is IWMSC if Consumer is MSC -- Supplier is MSC or SGSN if Consumer is GMSC -- Supplier is IWMSC if Consumer is SGSN CONSUMER INVOKES { forwardSM}
7851 The v1-equivalent package can be determined according to the rules described in clause 17.2.1.
7852 17.2.2.23
Short message gateway services
7853 This operation package includes the operations required for short message service gateway procedures between MSC 7854 and HLR.
7855 7856 7857 7858 7859 7860 7861 7862 7863
ShortMsgGatewayPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GMSC CONSUMER INVOKES { sendRoutingInfoForSM, reportSM-DeliveryStatus} SUPPLIER INVOKES { informServiceCentre}
The v2-equivalent package can be determined according to the rules described in clause 17.2.1.
7864 The v1-equivalent package is defined as follows:
7865 7866 7867 7868 7869 7870
ShortMsgGatewayPackage-v1 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GMSC CONSUMER INVOKES { sendRoutingInfoForSM, reportSMDeliveryStatus}
7871 17.2.2.24
MT Short message relay services
7872 This operation package includes the operations required for short message relay service procedures between GMSC and 7873 MSC or between GMSC and SGSN.
7874 7875 7876 7877 7878
MTShortMsgRelayPackage-v3 ::= OPERATION-PACKAGE -- Supplier is MSC or SGSN if Consumer is GMSC CONSUMER INVOKES { MT-forwardSM}
7879 The v2-equivalent package is: ShortMsgRelayPackage-v2
1058
7880 17.2.2.25 7881 17.2.2.26
1059 Release 4 1060 1061
266
3GPP TS 29.002 V4.17.0 (2006-06)
Void Message waiting data management
7882 This operation package includes the operations required for short message waiting data procedures between HLR and 7883 VLR, between HLR and SGSN.
7884 7885 7886 7887 7888 7889
MwdMngtPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is SGSN -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { readyForSM}
7890 The v2-equivalent package can be determined according to the rules described in clause 17.2.1.
7891
7892 The v1-equivalent package is defined as follows:
7893 7894 7895 7896 7897
MwdMngtPackage-v1 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { noteSubscriberPresent}
7898 17.2.2.27
Alerting
7899 This operation package includes the operations required for alerting between HLR and IWMSC.
7900 7901 7902 7903 7904
AlertingPackage-v2 ::= OPERATION-PACKAGE -- Supplier is IWMSC if Consumer is HLR CONSUMER INVOKES { alertServiceCentre}
7905 The v1-equivalent package is defined as follows.
7906 7907 7908 7909 7910
AlertingPackage-v1 ::= OPERATION-PACKAGE -- Supplier is IWMSC if Consumer is HLR CONSUMER INVOKES { alertServiceCentreWithoutResult}
7911 17.2.2.28
Data restoration
7912 This operation package includes the operations required for VLR data restoration between HLR and VLR.
7913 7914 7915 7916 7917
DataRestorationPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { restoreData}
7918 The v2-equivalent package can be determined according to the rules described in clause 17.2.1. 7919 The v1-equivalent package is: InfoRetrievalPackage-v1
7920 17.2.2.29
Purging
7921 This operation package includes the operations required for purging between HLR and VLR or between HLR and 7922 SGSN.
7923 7924 7925 7926 7927 7928
PurgingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { purgeMS}
7929 The v2-equivalent package can be determined according to the rules described in clause 17.2.1.
1062
7930 17.2.2.30
1063 Release 4 1064 1065
267
3GPP TS 29.002 V4.17.0 (2006-06)
Subscriber information enquiry
7931 This operation package includes the operations required for subscriber information enquiry procedures between HLR 7932 and VLR.
7933 7934 7935 7936 7937
SubscriberInformationEnquiryPackage-v3 ::= OPERATION-PACKAGE
-- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { provideSubscriberInfo}
7938 This package is v3 only.
7939 17.2.2.31
Any time information enquiry
7940 This operation package includes the operations required for any time information enquiry procedures between gsmSCF 7941 and HLR or GMLC.
7942 7943 7944 7945 7946
AnyTimeInformationEnquiryPackage-v3 ::= OPERATION-PACKAGE
-- Supplier is HLR or GMLC if Consumer is gsmSCF CONSUMER INVOKES { anyTimeInterrogation}
7947 This package is v3 only.
7948 17.2.2.32
Group Call Control
7949 This operation package includes the operations required for group call and broadcast call procedures between MSCs.
7950 7951 7952 7953 7954 7955 7956 7957 7958
GroupCallControlPackage-v3 ::= OPERATION-PACKAGE -- Supplier is relay MSC if Consumer is anchor MSC CONSUMER INVOKES { prepareGroupCall, forwardGroupCallSignalling} SUPPLIER INVOKES { sendGroupCallEndSignal, processGroupCallSignalling}
7959 This package is v3 only.
7960 17.2.2.33
Provide SIWFS number
7961 This operation package includes the operations required between VMSC and SIWF for requesting resources from an 7962 SIWF.
7963 7964 7965 7966 7967
ProvideSIWFSNumberPackage-v3 ::= OPERATION-PACKAGE
-- Supplier is SIWF if Consumer is VMSC CONSUMER INVOKES { provideSIWFSNumber}
7968 This package is v3 only.
7969 17.2.2.34
SIWFS Signalling Modify
7970 This operation package includes the operations required for the modification of the resources in an SIWF between the 7971 VMSC and SIWF.
7972 7973 7974 7975 7976
SIWFSSignallingModifyPackage-v3 ::= OPERATION-PACKAGE
-- Supplier is SIWF if Consumer is VMSC CONSUMER INVOKES { sIWFSSignallingModify}
7977 This package is v3 only.
1066
7978 17.2.2.35
1067 Release 4 1068 1069
268
3GPP TS 29.002 V4.17.0 (2006-06)
Gprs location updating
7979 This operation package includes the operations required for the gprs location management procedures between HLR 7980 and SGSN.
7981 7982 7983 7984
GprsLocationUpdatingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { updateGprsLocation}
7985 7986 This package is v3 only.
7987 17.2.2.36
Gprs Interrogation
7988 This operation package includes the operations required for interrogation procedures between HLR and GGSN.
7989 7990 7991 7992
GprsInterrogationPackage-v4 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GGSN CONSUMER INVOKES { sendRoutingInfoForGprs}
7993 7994 The v3-equivalent package is defined as follows. 7995
7996 7997 7998 7999
GprsInterrogationPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GGSN CONSUMER INVOKES { sendRoutingInfoForGprs}
8000
8001 17.2.2.37
Failure reporting
8002 This operation package includes the operations required for failure reporting between HLR and GGSN.
8003 8004 8005 8006
FailureReportingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GGSN CONSUMER INVOKES { failureReport}
8007 8008 This package is v3 only.
8009 17.2.2.38
GPRS notifying
8010 This operation package includes the operations required for notifying that GPRS subscriber is present between HLR and 8011 GGSN.
8012 8013 8014 8015
GprsNotifyingPackage-v3 ::= OPERATION-PACKAGE -- Supplier is GGSN if Consumer is HLR CONSUMER INVOKES { noteMsPresentForGprs}
8016 8017 This package is v3 only.
1070
8018 17.2.2.39
1071 Release 4 1072 1073
269
3GPP TS 29.002 V4.17.0 (2006-06)
Supplementary Service invocation notification
8019 This operation package includes the operations required for Supplementary Service invocation notification procedures 8020 between the MSC and the gsmSCF and between the HLR and the gsmSCF.
8021 8022 8023 8024 8025 8026
SS-InvocationNotificationPackage-v3 ::= OPERATION-PACKAGE
-- Supplier is gsmSCF if Consumer is MSC -- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { ss-InvocationNotification}
8027 This package is v3 only.
8028 17.2.2.40
Set Reporting State
8029 This operation package includes the operation required for procedures between HLR and VLR to set the reporting state.
8030 8031 8032 8033 8034
SetReportingStatePackage-v3 ::= OPERATION-PACKAGE
-- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { setReportingState}
8035 This package is v3 only.
8036 17.2.2.41
Status Report
8037 This operation package includes the operation required for procedures between VLR and HLR to report call results and 8038 events.
8039 8040 8041 8042 8043
StatusReportPackage-v3 ::= OPERATION-PACKAGE
-- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { statusReport}
8044 This package is v3 only.
8045 17.2.2.42
Remote User Free
8046 This operation package includes the operation required by the HLR to indicate to the VLR that the remote user is free.
8047 8048 8049 8050 8051
RemoteUserFreePackage-v3 ::= OPERATION-PACKAGE
-- Supplier is VLR if Consumer is HLR CONSUMER INVOKES { remoteUserFree}
8052 This package is v3 only.
8053 17.2.2.43
Call Completion
8054 This operation package includes the operations required for procedures between VLR and HLR for subscriber control of 8055 call completion services.
8056 8057 8058 8059 8060 8061
CallCompletionPackage-v3 ::= OPERATION-PACKAGE
-- Supplier is HLR if Consumer is VLR CONSUMER INVOKES { registerCC-Entry, eraseCC-Entry}
8062 This package is v3 only.
8063 17.2.2.44
Location service gateway services
8064 This operation package includes the operations required for location service gateway procedures between GMLC and 8065 HLR.
1074
1075 Release 4 1076 1077
8066 8067 8068 8069 8070 8071
270
3GPP TS 29.002 V4.17.0 (2006-06)
LocationSvcGatewayPackage-v3 ::= OPERATION-PACKAGE -- Supplier is HLR if Consumer is GMLC CONSUMER INVOKES { sendRoutingInfoForLCS}
This package is v3 only.
8072 17.2.2.45
Location service enquiry
8073 This operation package includes the operations required for the location service enquiry procedures between GMLC and 8074 MSC and between GMLC and SGSN.
8075 8076 8077 8078 8079
LocationSvcEnquiryPackage-v3 ::= OPERATION-PACKAGE
-- Supplier is MSC or SGSN if Consumer is GMLC CONSUMER INVOKES { provideSubscriberLocation}
8080 This package is v3 only.
8081 17.2.2.45A
Location service reporting
8082 This operation package includes the operations required for the location service enquiry procedures between MSC and 8083 GMLC and between SGSN and GMLC.
8084 8085 8086 8087 8088
LocationSvcReportingPackage-v3 ::= OPERATION-PACKAGE
-- Supplier is GMLC if Consumer is MSC -- Supplier is GMLC if Consumer is SGSN CONSUMER INVOKES { subscriberLocationReport}
8089 8090 17.2.2.46 8091 17.2.2.47 8092 17.2.2.48 8093 17.2.2.49 Void Void Void IST Alerting
8094 This operation package includes the operation required for alerting procedures between the MSC (Visited MSC or 8095 Gateway MSC) and HLR.
8096 8097 8098 8099 8100 8101
IST-AlertingPackage-v3 ::= OPERATION-PACKAGE
-- Supplier is HLR if Consumer is VMSC -- Supplier is HLR if Consumer is GMSC CONSUMER INVOKES { istAlert}
8102 This package is v3 only.
8103 17.2.2.50
Service Termination
8104 This operation package includes the operation required for immediate service termination procedures between the HLR 8105 and the Visited MSC or between the HLR and the Gateway MSC.
8106 8107 8108 8109 8110
ServiceTerminationPackage-v3 ::= OPERATION-PACKAGE
-- Supplier is VMSC or GMSC if Consumer is HLR CONSUMER INVOKES { istCommand}
8111 This package is v3 only.
1078
8112 17.2.2.51
1079 Release 4 1080 1081
271
3GPP TS 29.002 V4.17.0 (2006-06)
Mobility Management event notification
8113 This operation package includes the operations required for Mobility Management event notification procedures 8114 between VLR and gsmSCF.
8115 8116 8117 8118
MM-EventReportingPackage-v3 ::= OPERATION-PACKAGE
-- Supplier is gsmSCF if Consumer is VLR CONSUMER INVOKES { noteMM-Event}
8119 This package is v3 only.
8120 17.2.2.52
Any time information handling
8121 This operation package includes the operations required for any time information handling procedures between gsmSCF 8122 and HLR.
8123 8124 8125 8126 8127 8128
AnyTimeInformationHandlingPackage-v3 ::= OPERATION-PACKAGE
-- Supplier is HLR if Consumer is gsmSCF CONSUMER INVOKES { anyTimeSubscriptionInterrogation, anyTimeModification}
8129 This package is v3 only.
17.2.2.53
Subscriber Data modification notification
This operation package includes the operations required for Subscriber Data modification notification procedures between HLR and gsmSCF.
SubscriberDataModificationNotificationPackage-v3 ::= OPERATION-PACKAGE
-- Supplier is gsmSCF if Consumer is HLR CONSUMER INVOKES { noteSubscriberDataModified}
This package is v3 only.
8130 17.2.2.54
Authentication Failure Report
8131 This operation package includes the operation required for procedures between VLR and HLR or the SGSN and the 8132 HLR for reporting of authentication failures.
8133 8134 8135 8136 8137 8138
AuthenticationFailureReportPackage-v3 ::= OPERATION-PACKAGE
-- Supplier is HLR if Consumer is VLR -- Supplier is HLR if Consumer is SGSN CONSUMER INVOKES { authenticationFailureReport}
8139 This package is v3 only.
8140 8141
17.3 Application contexts
17.3.1 General aspects
8142 An application-context is assigned for each dialogue established by a MAP-user. In the present document each 8143 application-context is assigned a name which is supplied in the MAP-OPEN Req primitive by the MAP-User and 8144 transmitted to the peer under certain circumstances.
1082
8145 The following ASN.1 MACRO is used to describe the main aspects of application-contexts in the following clauses:
8146 8147 8148 8149 8150 8151 8152 8153 8154 8155 8156 8157 8158 8159 8160 8161 8162 8163 8164 8165 8166 8167
1083 Release 4 1084 1085
272
3GPP TS 29.002 V4.17.0 (2006-06)
APPLICATION-CONTEXT MACRO ::= BEGIN TYPE NOTATION ::= Symmetric | InitiatorConsumerOf ResponderConsumerOf | empty VALUE NOTATION ::= value(VALUE OBJECT IDENTIFIER) Symmetric ::= "OPERATIONS OF" "{" PackageList "}" InitiatorConsumerOf ::= "INITIATOR CONSUMER OF" "{" PackageList "}" ResponderConsumerOf ::= "RESPONDER CONSUMER OF" "{" PackageList "}" | empty PackageList ::= Package | PackageList "," Package Package ::= value(OPERATION-PACKAGE) | type -- shall reference a package type END
8168 8169 The following definitions are used throughout this clause: 8170 8171 8172
v1-application-context: An application-context which contains only v1-packages and uses only TC v1 facilities; v1 context set: the set of v1-application-contexts defined in the present document. vn-application-context (n>=2): An application-context which contains only vn-packages;
8173 The names of v1-application-contexts are suffixed by "-v1" while other names are suffixed by "-vn" where n>=2. 8174 Application-contexts which do not belong to the v1 context set use v2 TC facilities. 8175 The last component of each application-context-name (i.e. the last component of the object identifier value) assigned to 8176 an application-context which belongs to the v1 context set indicates explicitly "version1". 8177 For each application-context which does not belong to the "v1 context set" there is a v1-equivalent application context. 8178 This is a v1-application-context which includes the v1-equivalents of the packages included in the original context. 8179 Each application-context uses the abstract-syntax associated with the operation-packages it includes and uses the 8180 transfer-syntax derived from it by applying the encoding rules defined in clause 17.1.1. 8181 ACs which do not belong to the v1 context set require the support of the abstract-syntax identified by the object 8182 identifier value: MAP-DialogueInformation.map-Dialogue-AS defined in clause 17.4.
8183 8184 17.3.2.1 8185 17.3.2.2
17.3.2 Application context definitions
Void Location Updating
8186 This application context is used between HLR and VLR for location updating procedures.
8187 8188 8189 8190 8191 8192 8193 8194 8195 8196
networkLocUpContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { LocationUpdatingPackage-v3, DataRestorationPackage-v3} RESPONDER CONSUMER OF { SubscriberDataMngtPackage-v3 TracingPackage-v3} ::= {map-ac networkLocUp(1) version3(3)}
1086
8197 The following application-context-name is assigned to the v2-equivalent application-context:
8198 8199
1087 Release 4 1088 1089
273
3GPP TS 29.002 V4.17.0 (2006-06)
{map-ac networkLocUp(1) version2(2)}
8200 The following application-context-name is assigned to the v1-equivalent application-context:
8201 8202
{map-ac networkLocUp(1) version1(1)}
8203 17.3.2.3
Location Cancellation
8204 This application context is used between HLR and VLR or between HLR and SGSN for location cancellation 8205 procedures. For the HLR - SGSN interface only version 3 of this application context is applicable.
8206 8207 8208 8209 8210 8211
locationCancellationContext-v3 APPLICATION-CONTEXT -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER OF { LocationCancellationPackage-v3} ::= {map-ac locationCancel(2) version3(3)}
8212 The following application-context-name is assigned to the v2-equivalent application-context:
8213
map-ac locationCancel(2) version2(2)
8214 8215 The following application-context-name is assigned to the v1-equivalent application-context:
8216 8217
map-ac locationCancel(2) version1(1)
8218 17.3.2.4
Roaming number enquiry
8219 This application context is used between HLR and VLR for roaming number enquiry procedures.
8220 8221 8222 8223 8224 8225
roamingNumberEnquiryContext-v3 APPLICATION-CONTEXT -- Responder is VLR if Initiator is HLR INITIATOR CONSUMER OF { RoamingNumberEnquiryPackage-v3} ::= {map-ac roamingNbEnquiry(3) version3(3)}
8226 The following application-context-name is assigned to the v2-equivalent application-context:
8227 8228
{map-ac roamingNbEnquiry(3) version2(2)}
8229 The following application-context-name is assigned to the v1-equivalent application-context:
8230 8231
{map-ac roamingNbEnquiry(3) version1(1)}
8232 17.3.2.5 8233 17.3.2.6
Void Location Information Retrieval
8234 This application-context is used between GMSC and HLR or between GMSC and NPLR when retrieving location 8235 information. For the GMSC - NPLR interface version 1, version 2 and version 3 of this application context are 8236 applicable.
8237 8238 8239 8240 8241 8242
locationInfoRetrievalContext-v3 APPLICATION-CONTEXT -- Responder is HLR or NPLR if Initiator is GMSC INITIATOR CONSUMER OF { InterrogationPackage-v3} ::= {map-ac locInfoRetrieval(5) version3(3)}
8243 The following application-context-name is assigned to the v2-equivalent application-context:
8244 8245 8246
{map-ac locInfoRetrieval(5) version2(2)}
8247 The following application-context-name is assigned to the v1-equivalent application-context:
8248
{map-ac locInfoRetrieval(5) version1(1)}
1090
1091 Release 4 1092 1093
8249
274
3GPP TS 29.002 V4.17.0 (2006-06)
8250 17.3.2.7
Call control transfer
8251 This application context is used for the call control transfer procedure between the VMSC and the GMSC.
8252 8253 8254 8255 8256 8257
callControlTransferContext-v4 APPLICATION-CONTEXT -- Responder is GMSC if Initiator is VMSC INITIATOR CONSUMER OF { CallControlTransferPackage-v4} ::= {map-ac callControlTransfer(6) version4(4)}
8258 The following application-context-name is assigned to the v3-equivalent application-context:
8259
{map-ac callControlTransfer(6) version3(3)}
8260 17.3.2.8
void
8261 17.3.2.9 - 17.3.2.10 Void 8262 17.3.2.11 Location registers restart
8263 This application context is used between HLR and VLR or between HLR and SGSN for location register restart 8264 procedures. For the HLR - SGSN interface version 1 and version 2 of this application context are applicable.
8265 8266 8267 8268 8269 8270
resetContext-v2 APPLICATION-CONTEXT -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER OF { ResetPackage-v2} ::= {map-ac reset(10) version2(2)}
8271 The following application-context-name is assigned to the v1-equivalent application-context:
8272 8273
{map-ac reset(10) version1(1)}
8274 17.3.2.12
Handover control
8275 This application context is used for handover procedures between MSCs.
8276 8277 8278 8279 8280
handoverControlContext-v3 APPLICATION-CONTEXT -- Responder is MSCB if Initiator is MSCA INITIATOR CONSUMER OF { HandoverControlPackage-v3} ::= {map-ac handoverControl(11) version3(3)}
8281 8282 The following application-context-name is assigned to the v2-equivalent application-context:
8283
{map-ac handoverControl(11) version2(2)}
8284
8285
8286 The following application-context-name is assigned to the v1-equivalent application-context:
8287 8288
{map-ac handoverControl(11) version1(1)}
8289 17.3.2.13
IMSI Retrieval
8290 This application context is used for IMSI retrieval between HLR and VLR.
8291 8292 8293 8294 8295 8296
imsiRetrievalContext-v2 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { IMSIRetrievalPackage-v2} ::= {map-ac imsiRetrieval(26) version2(2)}
8297 This application-context is v2 only.
1094
8298 17.3.2.14
1095 Release 4 1096 1097
275
3GPP TS 29.002 V4.17.0 (2006-06)
Equipment Management
8299 This application context is used for equipment checking between MSC and EIR or between SGSN and EIR. For the 8300 SGSN - EIR interface version 1 and version 2 of this application context are applicable:
8301 8302 8303 8304 8305 8306 8307
equipmentMngtContext-v2 APPLICATION-CONTEXT -- Responder is EIR if Initiator is MSC -- Responder is EIR if Initiator is SGSN INITIATOR CONSUMER OF { EquipmentMngtPackage-v2} ::= {map-ac equipmentMngt(13) version2(2)}
8308 The following application-context-name is assigned to the v1-equivalent application-context:
8309 8310
{map-ac equipmentMngt(13) version1(1)}
8311 17.3.2.15
Information retrieval
8312 This application context is used for authentication information retrieval between HLR and VLR or between HLR and 8313 SGSN. For the HLR - SGSN interface version 1 and version 2 and version 3 of this application context are applicable.
8314 8315 8316 8317 8318 8319 8320
infoRetrievalContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR -- Responder is HLR if Initiator is SGSN INITIATOR CONSUMER OF { InfoRetrievalPackage-v3} ::= {map-ac infoRetrieval(14) version3(3)}
8321 The following application-context-name is assigned to the v2-equivalent application-context:
8322 8323 8324 8325 8326 8327 8328
infoRetrievalContext-v2 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR -- Responder is HLR if Initiator is SGSN INITIATOR CONSUMER OF { InfoRetrievalPackage-v2} ::= {map-ac infoRetrieval(14) version2(2)}
8329 The following application-context-name is assigned to the v1-equivalent application-context:
8330 8331
{map-ac infoRetrieval(14) version1(1)}
8332 17.3.2.16
Inter-VLR information retrieval
8333 This application context is used for information retrieval between VLRs.
8334 8335 8336 8337 8338 8339
interVlrInfoRetrievalContext-v3 APPLICATION-CONTEXT -- Responder is VLR if Initiator is VLR INITIATOR CONSUMER OF { InterVlrInfoRetrievalPackage-v3} ::= {map-ac interVlrInfoRetrieval(15) version3(3)}
8340 The v2-equivalent application-context is:
8341 8342 8343 8344 8345 8346
interVlrInfoRetrievalContext-v2 APPLICATION-CONTEXT -- Responder is VLR if Initiator is VLR INITIATOR CONSUMER OF { InterVlrInfoRetrievalPackage-v2} ::= {map-ac interVlrInfoRetrieval(15) version2(2)}
8347 The v1-equivalent application-context is:
8348 8349
{map-ac infoRetrieval(14) version1(1)}
1098
8350 17.3.2.17
1099 Release 4 1100 1101
276
3GPP TS 29.002 V4.17.0 (2006-06)
Stand Alone Subscriber Data Management
8351 This application context is used for stand alone subscriber data management between HLR and VLR or between HLR 8352 and SGSN. For the HLR - SGSN interface only version 3 of this application context is applicable:
8353 8354 8355 8356 8357 8358
subscriberDataMngtContext-v3 APPLICATION-CONTEXT -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER OF { SubscriberDataMngtStandAlonePackage-v3} ::= {map-ac subscriberDataMngt(16) version3(3)}
8359 The following application-context-name is assigned to the v2-equivalent application-context:
8360 8361
{map-ac subscriberDataMngt(16) version2(2)}
8362 The following application-context-name is assigned to the v1-equivalent application-context:
8363 8364
{map-ac subscriberDataMngt(16) version1(1)}
8365 17.3.2.18
Tracing
8366 This application context is used between HLR and VLR or between HLR and SGSN for stand alone tracing control 8367 procedures. For the HLR - SGSN interface version 1, version 2 and version 3 of this application context are applicable.
8368 8369 8370 8371 8372
tracingContext-v3 APPLICATION-CONTEXT -- Responder is VLR or SGSN if Initiator is HLR INITIATOR CONSUMER OF { TracingStandAlonePackage-v3} ::= {map-ac tracing(17) version3(3)}
8373 8374 The following application-context-name is assigned to the v2-equivalent application-context:
8375 8376
{map-ac tracing(17) version2(2)}
8377 The following application-context-name is assigned to the v1-equivalent application-context:
8378 8379
{map-ac tracing(17) version1(1)}
8380 17.3.2.19
Network functional SS handling
8381 This application context is used for functional-like SS handling procedures between VLR and HLR.
8382 8383 8384 8385 8386 8387
networkFunctionalSsContext-v2 APPLICATION-CONTEXT -- Responder is HLR, Initiator is VLR INITIATOR CONSUMER OF { FunctionalSsPackage-v2} ::= {map-ac networkFunctionalSs(18) version2(2)}
8388 The v1-equivalent application-context is defined as follows:
8389 8390 8391 8392 8393 8394 8395 8396
networkFunctionalSsContext-v1 APPLICATION-CONTEXT -- Responder is HLR, Initiator is VLR INITIATOR CONSUMER OF { FunctionalSsPackage-v1, UnstructuredSsPackage-v1, BindingPackage-v1} ::= {map-ac networkFunctionalSs(18) version1(1)}
1102
8397 17.3.2.20
1103 Release 4 1104 1105
277
3GPP TS 29.002 V4.17.0 (2006-06)
Network unstructured SS handling
8398 This application context is used for handling stimuli-like procedures between HLR and VLR, between the HLR and 8399 gsmSCF, and between HLR and HLR.
8400 8401 8402 8403 8404 8405 8406 8407 8408 8409
networkUnstructuredSsContext-v2 APPLICATION-CONTEXT -- Responder is HLR, Initiator is VLR -- Responder is VLR, Initiator is HLR -- Responder is gsmSCF, Initiator is HLR -- Responder is HLR, Initiator is gsmSCF -- Responder is HLR, Initiator is HLR OPERATIONS OF { UnstructuredSsPackage-v2} ::= {map-ac networkUnstructuredSs(19) version2(2)}
8410 The following application-context-name is assigned to the v1-equivalent application-context:
8411 8412
{map-ac networkFunctionalSs(18) version1(1)}
8413 17.3.2.21
Short Message Gateway
8414 This application context is used for short message gateway procedures.
8415 8416 8417 8418 8419 8420
shortMsgGatewayContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is GMSC INITIATOR CONSUMER OF { ShortMsgGatewayPackage-v3} ::= {map-ac shortMsgGateway(20) version3(3)}
8421 The following application-context-name is assigned to the v2-equivalent application-context:
8422 8423
{map-ac shortMsgGateway(20) version2(2)}
8424 The following application-context-name is assigned to the v1-equivalent application-context:
8425 8426
{map-ac shortMsgGateway(20) version1(1)}
8427 17.3.2.22
Mobile originating Short Message Relay
8428 This application context is used between MSC and IWMSC or between SGSN and IWMSC for mobile originating short 8429 message relay procedures. For the SGSN - IWMSC interface version 1, version 2 and version 3 of this application 8430 context are applicable.
8431 8432 8433 8434 8435 8436 8437
shortMsgMO-RelayContext-v3 APPLICATION-CONTEXT -- Responder is IWMSC if Initiator is MSC -- Responder is IWMSC if Initiator is SGSN INITIATOR CONSUMER OF { MOShortMsgRelayPackage-v3} ::= {map-ac shortMsgMO-Relay(21) version3(3)}
8438 The following application-context-name is assigned to the v2-equivalent application-context:
8439 8440
{map-ac shortMsgMO-Relay(21) version2(2)}
8441 The following application-context-name is assigned to the v1-equivalent application-context:
8442 8443
{map-ac shortMsg-Relay(21) version1(1)}
1106
8444 17.3.2.23 8445 17.3.2.24
1107 Release 4 1108 1109
278
3GPP TS 29.002 V4.17.0 (2006-06)
Void Short message alert
8446 This application context is used for short message alerting procedures.
8447 8448 8449 8450 8451 8452
shortMsgAlertContext-v2 APPLICATION-CONTEXT -- Responder is IWMSC if Initiator is HLR INITIATOR CONSUMER OF { AlertingPackage-v2} ::= {map-ac shortMsgAlert(23) version2(2)}
8453 The following application-context-name is symbolically assigned to the v1-equivalent application-context:
8454 8455
{map-ac shortMsgAlert(23) version1(1)}
8456 17.3.2.25
Short message waiting data management
8457 This application context is used between VLR and HLR or between SGSN and HLR for short message waiting data 8458 management procedures. For the SGSN - HLR interface only version 3 of this application context is applicable.
8459 8460 8461 8462 8463 8464
mwdMngtContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is SGSN -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { MwdMngtPackage-v3} ::= {map-ac mwdMngt(24) version3(3)}
8465 8466 The following application-context-name is assigned to the v2-equivalent application-context:
8467
{map-ac mwdMngt(24) version2(2)}
8468 8469 The following application-context-name is assigned to the v1-equivalent application-context:
8470 8471
{map-ac mwdMngt(24) version1(1)}
8472 17.3.2.26
Mobile terminating Short Message Relay
8473 This application context is used between GMSC and MSC or between GMSC and SGSN for mobile terminating short 8474 message relay procedures. For the GMSC - SGSN interface version 2 and version 3 of this application context and the 8475 equivalent version 1 application context are applicable.
8476 8477 8478 8479 8480 8481
shortMsgMT-RelayContext-v3 APPLICATION-CONTEXT -- Responder is MSC or SGSN if Initiator is GMSC INITIATOR CONSUMER OF { MTShortMsgRelayPackage-v3} ::= {map-ac shortMsgMT-Relay(25) version3(3)}
8482 The following application-context-name is assigned to the v2-equivalent application-context:
8483 8484
{map-ac shortMsgMT-Relay(25) version2(2)}
8485 The following application-context-name is assigned to the v1-equivalent application-context:
8486 8487
{map-ac shortMsgMO-Relay(21) version1(1)}
1110
8488 17.3.2.27
1111 Release 4 1112 1113
279
3GPP TS 29.002 V4.17.0 (2006-06)
MS purging
8489 This application context is used between HLR and VLR or between HLR and SGSN for MS purging procedures. For 8490 the SGSN - HLR interface only version 3 of this application context is applicable.
8491 8492 8493 8494 8495 8496 8497
msPurgingContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR -- Responder is HLR if Initiator is SGSN INITIATOR CONSUMER OF { purgingPackage-v3} ::= {map-ac msPurging(27) version3(3)}
8498 The following application-context-name is assigned to the v2-equivalent application-context:
8499
{map-ac msPurging(27) version2(2)}
8500
8501 17.3.2.28
Subscriber information enquiry
8502 This application context is used between HLR and VLR for subscriber information enquiry procedures.
8503 8504 8505 8506 8507 8508
subscriberInfoEnquiryContext-v3 APPLICATION-CONTEXT -- Responder is VLR if Initiator is HLR INITIATOR CONSUMER OF { SubscriberInformationEnquiryPackage-v3} ::= {map-ac subscriberInfoEnquiry(28) version3(3)}
8509 This application-context is v3 only.
8510 17.3.2.29
Any time information enquiry
8511 This application context is used between gsmSCF and HLR or GMLC for any time information enquiry procedures.
8512 8513 8514 8515 8516 8517
anyTimeInfoEnquiryContext-v3 APPLICATION-CONTEXT -- Responder is HLR or GMLC if Initiator is gsmSCF INITIATOR CONSUMER OF { AnyTimeInformationEnquiryPackage-v3} ::= {map-ac anyTimeInfoEnquiry(29) version3(3)}
8518 This application-context is v3 only.
8519 17.3.2.30
Group Call Control
8520 This application context is used between anchor MSC and relay MSC for group call and broadcast call procedures.
8521 8522 8523 8524 8525 8526
groupCallControlContext-v3 APPLICATION-CONTEXT -- Responder is relay MSC if Initiator is anchor MSC INITIATOR CONSUMER OF { GroupCallControlPackage-v3} ::= {map-ac groupCallControl(31) version3(3)}
8527 This application-context is v3 only.
8528 17.3.2.31
Provide SIWFS Number
8529 This application context is used for activation or modification of SIWF resources.
8530 8531 8532 8533 8534 8535 8536
sIWFSAllocationContext-v3 APPLICATION-CONTEXT
-- Responder is SIWF if Initiater is VMSC INITIATOR CONSUMER OF { ProvideSIWFSNumberPackage-v3, SIWFSSignallingModifyPackage-v3} ::= {map-ac sIWFSAllocation (12) version3(3)}
8537 This application-context is v3 only.
1114
8538 17.3.2.32
1115 Release 4 1116 1117
280
3GPP TS 29.002 V4.17.0 (2006-06)
Gprs Location Updating
8539 This application context is used between HLR and SGSN for gprs location updating procedures.
8540 8541 8542 8543 8544 8545 8546 8547 8548
gprsLocationUpdateContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is SGSN INITIATOR CONSUMER OF { GprsLocationUpdatingPackage-v3} RESPONDER CONSUMER OF { SubscriberDataMngtPackage-v3 TracingPackage-v3} ::= {map-ac gprsLocationUpdate(32) version3(3)}
8549 This application-context is v3 only.
8550 17.3.2.33
Gprs Location Information Retreival
8551 This application context is used between HLR and GGSN when retrieving gprs location information.
8552 8553 8554 8555 8556
gprsLocationInfoRetrievalContext-v4 APPLICATION-CONTEXT -- Responder is HLR if Initiator is GGSN INITIATOR CONSUMER OF { GprsInterrogationPackage-v4} ::= {map-ac gprsLocationInfoRetrieval(33) version4(4)}
8557 8558 The following application-context-name is assigned to the v3-equivalent application-context:
8559 8560 8561
{map-ac gprsLocationInfoRetrieval(33) version3(3)}
8562 17.3.2.34
Failure Reporting
8563 This application context is used between HLR and GGSN to inform that network requested PDP-context activation has 8564 failed.
8565 8566 8567 8568 8569 8570
failureReportContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is GGSN INITIATOR CONSUMER OF { FailureReportingPackage-v3} ::= {map-ac failureReport(34) version3(3)}
8571 This application-context is v3 only.
8572 17.3.2.35
GPRS Notifying
8573 This application context is used between HLR and GGSN for notifying that GPRS subscriber is present again.
8574 8575 8576 8577 8578 8579
gprsNotifyContext-v3 APPLICATION-CONTEXT -- Responder is GGSN if Initiator is HLR INITIATOR CONSUMER OF { GprsNotifyingPackage-v3} ::= {map-ac gprsNotify(35) version3(3)}
8580 This application-context is v3 only.
8581 17.3.2.36
Supplementary Service invocation notification
8582 This application context is used between the MSC and the gsmSCF and between the HLR and the gsmSCF for 8583 Supplementary Service invocation notification procedures.
8584 8585 8586 8587 8588 8589 8590
ss-InvocationNotificationContext-v3 APPLICATION-CONTEXT -- Responder is gsmSCF, Initiator is MSC -- Responder is gsmSCF, Initiator is HLR INITIATOR CONSUMER OF { SS-InvocationNotificationPackage-v3} ::= {map-ac ss-InvocationNotification(36) version3(3)}
8591 This application-context is v3 only.
1118
8592 17.3.2.37
1119 Release 4 1120 1121
281
3GPP TS 29.002 V4.17.0 (2006-06)
Reporting
8593 This application context is used between HLR and VLR for reporting procedures.
8594 8595 8596 8597 8598 8599 8600 8601 8602 8603 8604 8605
reportingContext-v3 APPLICATION-CONTEXT -- Responder is VLR if Initiator is HLR -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { SetReportingStatePackage-v3, StatusReportPackage-v3, RemoteUserFreePackage-v3} RESPONDER CONSUMER OF { SetReportingStatePackage-v3, StatusReportPackage-v3} ::= {map-ac reporting(7) version3(3)}
8606 This application-context is v3 only.
8607 17.3.2.38
Call Completion
8608 This application context is used between VLR and the HLR for subscriber control of call completion services.
8609 8610 8611 8612 8613 8614
callCompletionContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR INITIATOR CONSUMER OF { CallCompletionPackage-v3} ::= {map-ac callCompletion(8) version3(3)}
8615 This application-context is v3 only.
1122
8616 17.3.2.39
1123 Release 4 1124 1125
282
3GPP TS 29.002 V4.17.0 (2006-06)
Location Service Gateway
8617 This application context is used for location service gateway procedures.
8618 8619 8620 8621 8622
locationSvcGatewayContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is GMLC INITIATOR CONSUMER OF { locationSvcGatewayPackage-v3} ::= {map-ac locationSvcGateway(37) version3(3)}
8623 8624 17.3.2.40 Location Service Enquiry
8625 This application context is used for location service enquiry procedures.
8626 8627 8628 8629 8630 8631 8632 8633
locationSvcEnquiryContext-v3 APPLICATION-CONTEXT -- Responder is MSC or SGSN if Initiator is GMLC -- Responder is GMLC if Initiator is MSC -- Responder is GMLC if Initiator is SGSN INITIATOR CONSUMER OF { locationSvcEnquiryPackage-v3, locationSvcReportingPackage-v3} ::= {map-ac locationSvcEnquiry(38) version3 (3)}
8634
8635 17.3.2.41 8636 17.3.2.42 8637 17.3.2.43 8638 17.3.2.44
Void Void Void IST Alerting
8639 This application context is used between MSC (Visited MSC or Gateway MSC) and HLR for alerting services within 8640 IST procedures.
8641 8642 8643 8644 8645 8646 8647
istAlertingContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VMSC -- Responder is HLR if Initiator is GMSC INITIATOR CONSUMER OF { IST-AlertingPackage-v3} ::= {map-ac alerting(4) version3(3)}
8648 This application-context is v3 only.
8649 17.3.2.45
Service Termination
8650 This application context is used between HLR and MSC (Visited MSC or Gateway MSC) for service termination 8651 services within IST procedures.
8652 8653 8654 8655 8656 8657
serviceTerminationContext-v3 APPLICATION-CONTEXT -- Responder is VMSC or GMSC if Initiator is HLR INITIATOR CONSUMER OF { ServiceTerminationPackage-v3} ::= {map-ac serviceTermination(9) version3(3)}
8658 This application-context is v3 only.
1126
8659 17.3.2.46
1127 Release 4 1128 1129
283
3GPP TS 29.002 V4.17.0 (2006-06)
Mobility Management event notification
8660 This application context is used between VLR and gsmSCF for Mobility Management event notification procedures.
8661 8662 8663 8664 8665 8666
mm-EventReportingContext-v3 APPLICATION-CONTEXT -- Responder is gsmSCF, Initiator is VLR INITIATOR CONSUMER OF { MM-EventReportingPackage-v3} ::= {map-ac mm-EventReporting(42) version3(3)}
8667 This application-context is v3 only.
8668 17.3.2.47
Any time information handling
8669 This application context is used between gsmSCF and HLR for any time information handling procedures.
8670 8671 8672 8673 8674 8675
anyTimeInfohandlingContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is gsmSCF INITIATOR CONSUMER OF { AnyTimeInformationHandlingPackage-v3} ::= {map-ac anyTimeInfoHandling(43) version3(3)}
8676 This application-context is v3 only.
8677 17.3.2.48
Subscriber Data modification notification
This application context is used between HLR and gsmSCF for Subscriber Data modification notification procedures.
subscriberDataModificationNotificationContext-v3 APPLICATION-CONTEXT -- Responder is gsmSCF, Initiator is HLR INITIATOR CONSUMER OF { SubscriberDataModificationNotificationPackage-v3} ::= {map-ac subscriberDataModificationNotification(22) version3(3)}
This application-context is v3 only.
8678 17.3.2.49
Authentication Failure Report
8679 This application context is used between VLR and HLR or SGSN and HLR for reporting of authentication failures.
8680 8681 8682 8683 8684 8685 8686
authenticationFailureReportContext-v3 APPLICATION-CONTEXT -- Responder is HLR if Initiator is VLR -- Responder is HLR if Initiator is SGSN INITIATOR CONSUMER OF { AuthenticationFailureReportPackage-v3 } ::= {map-ac authenticationFailureReport(39) version3(3)}
8687 This application-context is v3 only.
8688
17.3.3 ASN.1 Module for application-context-names
The following ASN.1 module summarises the application-context-name assigned to MAP application-contexts.
MAP-ApplicationContexts { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ApplicationContexts (2) version7 (7)} DEFINITIONS ::= BEGIN -- EXPORTS everything IMPORTS gsm-NetworkId, ac-Id
8689 8690 8691 8692 8693 8694 8695 8696 8697 8698 8699 8700 8701 8702 8703 8704 8705
1130
1131 Release 4 1132 1133
8706 8707 8708 8709 8710 8711 8712 8713 8714 8715 8716 8717 8718 8719 8720 8721 8722 8723 8724 8725 8726 8727 8728 8729 8730 8731 8732 8733 8734 8735 8736 8737 8738 8739 8740 8741 8742 8743 8744 8745 8746 8747 8748 8749 8750 8751 8752 8753 8754 8755 8756 8757 8758 8759 8760 8761 8762 8763 8764 8765 8766 8767 8768 8769 8770 8771 8772 8773 8774 8775 8776 8777 8778 8779 8780
284
3GPP TS 29.002 V4.17.0 (2006-06)
FROM MobileDomainDefinitions { ccitt (0) identified-organization (4) etsi (0) mobileDomain (0) mobileDomainDefinitions (0) version1 (1)} ; -- application-context-names map-ac OBJECT IDENTIFIER ::= {gsm-NetworkId ac-Id}
networkLocUpContext-v3 OBJECT IDENTIFIER ::= {map-ac networkLocUp(1) version3(3)} locationCancellationContext-v3 OBJECT IDENTIFIER ::= {map-ac locationCancel(2) version3(3)} roamingNumberEnquiryContext-v3 OBJECT IDENTIFIER ::= {map-ac roamingNbEnquiry(3) version3(3)} authenticationFailureReportContext-v3 OBJECT IDENTIFIER ::= {map-ac authenticationFailureReport(39) version3(3)} locationInfoRetrievalContext-v3 OBJECT IDENTIFIER ::= {map-ac locInfoRetrieval(5) version3(3)} resetContext-v2 OBJECT IDENTIFIER ::= {map-ac reset(10) version2(2)} handoverControlContext-v3 OBJECT IDENTIFIER ::= {map-ac handoverControl(11) version3(3)} equipmentMngtContext-v2 OBJECT IDENTIFIER ::= {map-ac equipmentMngt(13) version2(2)} infoRetrievalContext-v3 OBJECT IDENTIFIER ::= {map-ac infoRetrieval(14) version3(3)} interVlrInfoRetrievalContext-v3 OBJECT IDENTIFIER ::= {map-ac interVlrInfoRetrieval(15) version3(3)} subscriberDataMngtContext-v3 OBJECT IDENTIFIER ::= {map-ac subscriberDataMngt(16) version3(3)} tracingContext-v3 OBJECT IDENTIFIER ::= {map-ac tracing(17) version3(3)} networkFunctionalSsContext-v2 OBJECT IDENTIFIER ::= {map-ac networkFunctionalSs(18) version2(2)} networkUnstructuredSsContext-v2 OBJECT IDENTIFIER ::= {map-ac networkUnstructuredSs(19) version2(2)} shortMsgGatewayContext-v3 OBJECT IDENTIFIER ::= {map-ac shortMsgGateway(20) version3(3)} shortMsgMO-RelayContext-v3 OBJECT IDENTIFIER ::= {map-ac shortMsgMO-Relay(21) version3(3)} shortMsgAlertContext-v2 OBJECT IDENTIFIER ::= {map-ac shortMsgAlert(23) version2(2)} mwdMngtContext-v3 OBJECT IDENTIFIER ::= {map-ac mwdMngt(24) version3(3)} shortMsgMT-RelayContext-v3 OBJECT IDENTIFIER ::= {map-ac shortMsgMT-Relay(25) version3(3)} imsiRetrievalContext-v2 OBJECT IDENTIFIER ::= {map-ac imsiRetrieval(26) version2(2)} msPurgingContext-v3 OBJECT IDENTIFIER ::= {map-ac msPurging(27) version3(3)}
subscriberInfoEnquiryContext-v3
OBJECT IDENTIFIER ::= {map-ac subscriberInfoEnquiry(28) version3(3)}
1134
1135 Release 4 1136 1137 8781 anyTimeInfoEnquiryContext-v3
8782 8783 8784 8785 8786 8787 8788 8789 8790 8791 8792 8793 8794 8795 8796 8797 8798 8799 8800 8801 8802 8803 8804 8805 8806 8807 8808 8809 8810 8811 8812 8813 8814 8815 8816 8817 8818 8819 8820 8821 8822 8823 8824 8825 8826 8827 8828 8829 8830 8831 8832 8833 8834 8835 8836 8837 8838 8839
285
3GPP TS 29.002 V4.17.0 (2006-06)
OBJECT IDENTIFIER ::= {map-ac anyTimeInfoEnquiry(29) version3(3)}
callControlTransferContext-v4 OBJECT IDENTIFIER ::= {map-ac callControlTransfer(6) version4(4)} ss-InvocationNotificationContext-v3 OBJECT IDENTIFIER ::= {map-ac ss-InvocationNotification(36) version3(3)}
sIWFSAllocationContext-v3 OBJECT IDENTIFIER ::= {map-ac sIWFSAllocation(12) version3(3)}
groupCallControlContext-v3 OBJECT IDENTIFIER ::= {map-ac groupCallControl(31) version3(3)} gprsLocationUpdateContext-v3 OBJECT IDENTIFIER ::= {map-ac gprsLocationUpdate(32) version3(3)} gprsLocationInfoRetrievalContext-v4 OBJECT IDENTIFIER ::= {map-ac gprsLocationInfoRetrieval(33) version4(4)} failureReportContext-v3 OBJECT IDENTIFIER ::= {map-ac failureReport(34) version3(3)} gprsNotifyContext-v3 OBJECT IDENTIFIER ::= {map-ac gprsNotify(35) version3(3)} reportingContext-v3 OBJECT IDENTIFIER ::= {map-ac reporting(7) version3(3)} callCompletionContext-v3 OBJECT IDENTIFIER ::= {map-ac callCompletion(8) version3(3)} istAlertingContext-v3 OBJECT IDENTIFIER ::= {map-ac istAlerting(4) version3(3)} serviceTerminationContext-v3 OBJECT IDENTIFIER ::= {map-ac immediateTermination(9) version3(3)} locationSvcGatewayContext-v3 OBJECT IDENTIFIER ::= {map-ac locationSvcGateway(37) version3(3)} locationSvcEnquiryContext-v3 OBJECT IDENTIFIER ::= {map-ac locationSvcEnquiry(38) version3(3)} mm-EventReportingContext-v3 OBJECT IDENTIFIER ::= {map-ac mm-EventReporting(42) version3(3)}
anyTimeInfoHandlingContext-v3
OBJECT IDENTIFIER ::= {map-ac anyTimeInfoHandling(43) version3(3)}
subscriberDataModificationNotificationContext-v3 OBJECT IDENTIFIER ::= {map-ac subscriberDataModificationNotification(22) version3(3)} -- The following Object Identifiers are reserved for application-- contexts existing in previous versions of the protocol
1138
1139 Release 4 1140 1141
8840 8841 8842 8843 8844 8845 8846 8847 8848 8849 8850 8851 8852 8853 8854 8855 8856 8857 8858 8859 8860 8861 8862 8863 8864 8865 8866 8867 8868 8869 8870 8871 8872 8873 8874
286
3GPP TS 29.002 V4.17.0 (2006-06)
-- AC Name & Version
--- networkLocUpContext-v1 -- networkLocUpContext-v2 -- locationCancellationContext-v1 -- locationCancellationContext-v2 -- roamingNumberEnquiryContext-v1 -- roamingNumberEnquiryContext-v2 -- locationInfoRetrievalContext-v1 -- locationInfoRetrievalContext-v2 -- resetContext-v1 -- handoverControlContext-v1 -- handoverControlContext-v2 -- equipmentMngtContext-v1 -- infoRetrievalContext-v1 -- infoRetrievalContext-v2 -- interVlrInfoRetrievalContext-v2 -- subscriberDataMngtContext-v1 -- subscriberDataMngtContext-v2 -- tracingContext-v1 -- tracingContext-v2 -- networkFunctionalSsContext-v1 -- shortMsgGatewayContext-v1 -- shortMsgGatewayContext-v2 -- shortMsgRelayContext-v1 -- shortMsgAlertContext-v1 -- mwdMngtContext-v1 -- mwdMngtContext-v2 -- shortMsgMT-RelayContext-v2 -- msPurgingContext-v2 -- callControlTransferContext-v3 -- gprsLocationInfoRetrievalContext-v3
Object Identifier
map-ac networkLocUp (1) version1 (1) map-ac networkLocUp (1) version2 (2) map-ac locationCancellation (2) version1 (1) map-ac locationCancellation (2) version2 (2) map-ac roamingNumberEnquiry (3) version1 (1) map-ac roamingNumberEnquiry (3) version2 (2) map-ac locationInfoRetrieval (5) version1 (1) map-ac locationInfoRetrieval (5) version2 (2) map-ac reset (10) version1 (1) map-ac handoverControl (11) version1 (1) map-ac handoverControl (11) version2 (2) map-ac equipmentMngt (13) version1 (1) map-ac infoRetrieval (14) version1 (1) map-ac infoRetrieval (14) version2 (2) map-ac interVlrInfoRetrieval (15) version2 (2) map-ac subscriberDataMngt (16) version1 (1) map-ac subscriberDataMngt (16) version2 (2) map-ac tracing (17) version1 (1) map-ac tracing (17) version2 (2) map-ac networkFunctionalSs (18) version1 (1) map-ac shortMsgGateway (20) version1 (1) map-ac shortMsgGateway (20) version2 (2) map-ac shortMsgRelay (21) version1 (1) map-ac shortMsgAlert (23) version1 (1) map-ac mwdMngt (24) version1 (1) map-ac mwdMngt (24) version2 (2) map-ac shortMsgMT-Relay (25) version2 (2) map-ac msPurging (27) version2 (2) map-ac callControlTransferContext (6) version3 (3) map-ac gprsLocationInfoRetrievalContext (33) version3 (3)
END
8875
8876 8877 8878 8879 8880 8881 8882 8883 8884 8885 8886 8887 8888 8889 8890 8891 8892 8893 8894 8895 8896 8897 8898 8899 8900 8901 8902 8903 8904 8905 8906 8907 8908 8909 8910 8911 8912 8913 8914
17.4 MAP Dialogue Information
MAP-DialogueInformation { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-DialogueInformation (3) version7 (7)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS map-DialogueAS, MAP-DialoguePDU ; IMPORTS gsm-NetworkId, as-Id FROM MobileDomainDefinitions { ccitt (0) identified-organization (4) etsi (0) mobileDomain (0) mobileDomainDefinitions (0) version1 (1)} AddressString FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network(1) modules (3) map-CommonDataTypes (18) version7 (7)} ExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version7 (7)} ;
1142
1143 Release 4 1144 1145
8915 8916 8917 8918 8919 8920 8921 8922 8923 8924 8925 8926 8927 8928 8929 8930 8931 8932 8933 8934 8935 8936 8937 8938 8939 8940 8941 8942 8943 8944 8945 8946 8947 8948 8949 8950 8951 8952 8953 8954 8955 8956 8957 8958 8959 8960 8961 8962 8963 8964 8965 8966 8967 8968 8969 8970 8971 8972 8973 8974 8975 8976 8977 8978 8979 8980 8981 8982 8983 8984 8985 8986 8987
287
3GPP TS 29.002 V4.17.0 (2006-06)
-- abstract syntax name for MAP-DialoguePDU map-DialogueAS OBJECT IDENTIFIER ::= {gsm-NetworkId as-Id map-DialoguePDU (1) version1 (1)} MAP-DialoguePDU ::= CHOICE { map-open map-accept map-close map-refuse map-userAbort map-providerAbort [0] [1] [2] [3] [4] [5] MAP-OpenInfo, MAP-AcceptInfo, MAP-CloseInfo, MAP-RefuseInfo, MAP-UserAbortInfo, MAP-ProviderAbortInfo} OPTIONAL, OPTIONAL, OPTIONAL
MAP-OpenInfo ::= SEQUENCE { destinationReference [0] AddressString originationReference [1] AddressString ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 } MAP-AcceptInfo ::= SEQUENCE { ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 } MAP-CloseInfo ::= SEQUENCE { ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 } MAP-RefuseInfo ::= SEQUENCE { reason Reason, ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 alternativeApplicationContext OBJECT IDENTIFIER -- alternativeApplicationContext must not be used in version 2 } Reason ::= ENUMERATED { noReasonGiven invalidDestinationReference invalidOriginatingReference (0), (1), (2) }
OPTIONAL
OPTIONAL
OPTIONAL, OPTIONAL
MAP-UserAbortInfo ::= SEQUENCE { map-UserAbortChoice MAP-UserAbortChoice, ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 } MAP-UserAbortChoice ::= CHOICE { userSpecificReason userResourceLimitation resourceUnavailable applicationProcedureCancellation [0] [1] [2] [3] NULL, NULL, ResourceUnavailableReason, ProcedureCancellationReason}
OPTIONAL
ResourceUnavailableReason ::= ENUMERATED { shortTermResourceLimitation (0), longTermResourceLimitation (1)} ProcedureCancellationReason ::= ENUMERATED { handoverCancellation (0), radioChannelRelease (1), networkPathRelease (2), callRelease (3), associatedProcedureFailure (4), tandemDialogueRelease (5), remoteOperationsFailure (6)}
1146
1147 Release 4 1148 1149
8988 8989 8990 8991 8992 8993 8994 8995 8996 8997 8998 8999 9000
288
3GPP TS 29.002 V4.17.0 (2006-06)
MAP-ProviderAbortInfo ::= SEQUENCE { map-ProviderAbortReason MAP-ProviderAbortReason, ..., extensionContainer ExtensionContainer -- extensionContainer must not be used in version 2 } MAP-ProviderAbortReason ::= ENUMERATED { abnormalDialogue (0), invalidPDU (1)} END
OPTIONAL
9001
9002 9003 9004 9005 9006 9007 9008 9009 9010 9011 9012 9013 9014 9015 9016 9017 9018 9019 9020 9021 9022 9023 9024 9025 9026 9027 9028 9029 9030 9031 9032 9033 9034 9035 9036 9037 9038 9039 9040 9041 9042 9043 9044 9045 9046 9047 9048 9049 9050 9051 9052 9053 9054 9055 9056 9057 9058 9059 9060 9061 9062
17.5 MAP operation and error codes
MAP-Protocol { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Protocol (4) version7 (7)} DEFINITIONS ::= BEGIN IMPORTS UpdateLocation, CancelLocation, PurgeMS, SendIdentification, UpdateGprsLocation, PrepareHandover, SendEndSignal, ProcessAccessSignalling, ForwardAccessSignalling, PrepareSubsequentHandover, SendAuthenticationInfo, AuthenticationFailureReport, CheckIMEI, InsertSubscriberData, DeleteSubscriberData, Reset, ForwardCheckSS-Indication, RestoreData, ProvideSubscriberInfo, AnyTimeInterrogation, AnyTimeSubscriptionInterrogation, AnyTimeModification, SendRoutingInfoForGprs, FailureReport, NoteMsPresentForGprs, NoteMM-Event, NoteSubscriberDataModified FROM MAP-MobileServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MobileServiceOperations (5) version7 (7)} ActivateTraceMode, DeactivateTraceMode, SendIMSI FROM MAP-OperationAndMaintenanceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-OperationAndMaintenanceOperations (6) version7 (7)} SendRoutingInfo, ProvideRoamingNumber, ResumeCallHandling, ProvideSIWFSNumber, SIWFSSignallingModify, SetReportingState, StatusReport, RemoteUserFree,
1150
1151 Release 4 1152 1153
9063 9064 9065 9066 9067 9068 9069 9070 9071 9072 9073 9074 9075 9076 9077 9078 9079 9080 9081 9082 9083 9084 9085 9086 9087 9088 9089 9090 9091 9092 9093 9094 9095 9096 9097 9098 9099 9100 9101 9102 9103 9104 9105 9106 9107 9108 9109 9110 9111 9112 9113 9114 9115 9116 9117 9118 9119 9120 9121 9122 9123 9124 9125 9126 9127 9128 9129 9130 9131 9132 9133 9134 9135 9136 9137 9138 9139 9140 9141
289
3GPP TS 29.002 V4.17.0 (2006-06)
IST-Alert, IST-Command FROM MAP-CallHandlingOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CallHandlingOperations (7) version7 (7)} RegisterSS, EraseSS, ActivateSS, DeactivateSS, InterrogateSS, ProcessUnstructuredSS-Request, UnstructuredSS-Request, UnstructuredSS-Notify, RegisterPassword, GetPassword, SS-InvocationNotification, RegisterCC-Entry, EraseCC-Entry FROM MAP-SupplementaryServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SupplementaryServiceOperations (8) version7 (7)} SendRoutingInfoForSM, MO-ForwardSM, MT-ForwardSM, ReportSM-DeliveryStatus, AlertServiceCentre, InformServiceCentre, ReadyForSM FROM MAP-ShortMessageServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ShortMessageServiceOperations (9) version7 (7)} PrepareGroupCall, ProcessGroupCallSignalling, ForwardGroupCallSignalling, SendGroupCallEndSignal FROM MAP-Group-Call-Operations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Group-Call-Operations (22) version7 (7)} ProvideSubscriberLocation, SendRoutingInfoForLCS, SubscriberLocationReport FROM MAP-LocationServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-LocationServiceOperations (24) version7 (7)} SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnknownSubscriber, NumberChanged, UnknownMSC, UnidentifiedSubscriber, UnknownEquipment, RoamingNotAllowed, IllegalSubscriber, IllegalEquipment, BearerServiceNotProvisioned, TeleserviceNotProvisioned, NoHandoverNumberAvailable, SubsequentHandoverFailure, TracingBufferFull, OR-NotAllowed, NoRoamingNumberAvailable, AbsentSubscriber, BusySubscriber, NoSubscriberReply, CallBarred, ForwardingViolation,
1154
1155 Release 4 1156 1157
9142 9143 9144 9145 9146 9147 9148 9149 9150 9151 9152 9153 9154 9155 9156 9157 9158 9159 9160 9161 9163 9164 9165 9166 9167 9168 9169 9170 9171 9172 9173 9174 9175 9176 9177 9178 9179 9180 9181 9182 9183 9184 9185 9186 9187 9188 9189 9190 9191 9192 9193 9194 9195 9196 9197 9198 9199 9200 9201 9202 9203 9204 9205 9206 9207 9208 9209 9210 9211 9212 9213 9214 9215 9216 9217 9218
9162
290
3GPP TS 29.002 V4.17.0 (2006-06)
ForwardingFailed, CUG-Reject, ATI-NotAllowed, IllegalSS-Operation, SS-ErrorStatus, SS-NotAvailable, SS-SubscriptionViolation, SS-Incompatibility, UnknownAlphabet, USSD-Busy, PW-RegistrationFailure, NegativePW-Check, NumberOfPW-AttemptsViolation, SubscriberBusyForMT-SMS, SM-DeliveryFailure, MessageWaitingListFull, AbsentSubscriberSM, ResourceLimitation, NoGroupCallNumberAvailable, ShortTermDenial, LongTermDenial, IncompatibleTerminal, UnauthorizedRequestingNetwork, UnauthorizedLCSClient, PositionMethodFailure, UnknownOrUnreachableLCSClient, ATSI-NotAllowed, ATM-NotAllowed, InformationNotAvailable, MM-EventNotSupported, TargetCellOutsideGroupCallArea
FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version7 (7)} ; -- location registration operation codes updateLocation UpdateLocation ::= localValue 2 cancelLocation CancelLocation ::= localValue 3 purgeMS PurgeMS ::= localValue 67 sendIdentification SendIdentification ::= localValue 55 -- handover operation codes prepareHandover PrepareHandover ::= localValue 68 sendEndSignal SendEndSignal ::= localValue 29 processAccessSignalling ProcessAccessSignalling ::= localValue 33 forwardAccessSignalling ForwardAccessSignalling ::= localValue 34 prepareSubsequentHandover PrepareSubsequentHandover ::= localValue 69 -- authentication operation codes sendAuthenticationInfo SendAuthenticationInfo ::= localValue 56 authenticationFailureReport AuthenticationFailureReport ::= localValue 15 -- IMEI MANAGEMENT operation codes checkIMEI CheckIMEI ::= localValue 43
-- subscriber management operation codes insertSubscriberData deleteSubscriberData InsertSubscriberData ::= localValue 7 DeleteSubscriberData ::= localValue 8
-- fault recovery operation codes
1158
1159 Release 4 1160 1161
9219 9220 9221 9222 9223 9224 9225 9226 9227 9228 9229 9230 9231 9232 9233 9234 9235 9236 9237 9238 9239 9240 9241 9242 9243 9244 9245 9246 9247 9248 9249 9250 9251 9252 9253 9254 9255 9256 9257 9258 9259 9260 9261 9262 9263 9264 9265 9266 9267 9268 9269 9270 9271 9272 9273 9274 9275 9276 9277 9278 9279 9280 9281 9282 9283 9284 9285 9286 9287 9288 9289 9290 9291 9292 9293 9294
291
3GPP TS 29.002 V4.17.0 (2006-06)
reset Reset ::= localValue 37 forwardCheckSS-Indication ForwardCheckSS-Indication ::= localValue 38 restoreData RestoreData ::= localValue 57 -- operation and maintenance operation codes activateTraceMode ActivateTraceMode ::= localValue 50 deactivateTraceMode DeactivateTraceMode ::= localValue 51 sendIMSI SendIMSI ::= localValue 58 -- call handling operation codes sendRoutingInfo SendRoutingInfo ::= localValue 22 provideRoamingNumber ProvideRoamingNumber ::= localValue 4 resumeCallHandling ResumeCallHandling ::= localValue 6 provideSIWFSNumber ProvideSIWFSNumber ::= localValue 31 sIWFSSignallingModify SIWFSSignallingModify ::= localValue 32 setReportingState SetReportingState ::= localValue 73 statusReport StatusReport ::= localValue 74 remoteUserFree RemoteUserFree ::= localValue 75 istAlert IST-Alert ::= localValue 87 istCommand IST-Command ::= localValue 88 -- supplementary service handling operation codes registerSS RegisterSS ::= localValue 10 eraseSS EraseSS ::= localValue 11 activateSS ActivateSS ::= localValue 12 deactivateSS DeactivateSS ::= localValue 13 interrogateSS InterrogateSS ::= localValue 14 processUnstructuredSS-Request ProcessUnstructuredSS-Request ::= localValue 59 unstructuredSS-Request UnstructuredSS-Request ::= localValue 60 unstructuredSS-Notify UnstructuredSS-Notify ::= localValue 61 registerPassword RegisterPassword ::= localValue 17 getPassword GetPassword ::= localValue 18 registerCC-Entry RegisterCC-Entry ::= localValue 76 eraseCC-Entry EraseCC-Entry ::= localValue 77 -- short message service operation codes sendRoutingInfoForSM SendRoutingInfoForSM ::= localValue 45 mo-forwardSM MO-ForwardSM ::= localValue 46 mt-forwardSM MT-ForwardSM ::= localValue 44 reportSM-DeliveryStatus ReportSM-DeliveryStatus ::= localValue 47 informServiceCentre InformServiceCentre ::= localValue 63 alertServiceCentre AlertServiceCentre ::= localValue 64 readyForSM ReadyForSM ::= localValue 66 -- provide subscriber info operation codes
provideSubscriberInfo
ProvideSubscriberInfo ::= localValue 70
-- any time interrogation operation codes
anyTimeInterrogation
AnyTimeInterrogation ::= localValue 71
-- any time information handling operation codes
anyTimeSubscriptionInterrogation AnyTimeSubscriptionInterrogation ::= localValue 62 anyTimeModification AnyTimeModification ::= localValue 65
-- subscriber data modification notification operation codes
noteSubscriberDataModified
NoteSubscriberDataModified ::= localValue 5
-- supplementary service invocation notification operation codes
ss-InvocationNotification
SS-InvocationNotification ::= localValue 72
1162
1163 Release 4 1164 1165
9295 9296 9297 9298 9299 9300 9301 9302 9303 9304 9305 9306 9307 9308 9309 9310 9311 9312 9313 9314 9315 9316 9317 9318 9319 9320 9321 9322 9323 9324 9325 9326 9328 9329 9330 9331 9332 9333 9334 9335 9336 9337 9338 9339 9340 9341 9342 9343 9344 9345 9346 9347 9348 9349 9350 9351 9352 9353 9354 9355 9356 9357 9358 9359 9360 9361 9362 9363 9364 9365 9366 9367 9368 9369 9370 9371
292
3GPP TS 29.002 V4.17.0 (2006-06)
--Group Call operation codes prepareGroupCall PrepareGroupCall ::= localValue 39 sendGroupCallEndSignal SendGroupCallEndSignal ::= localValue 40 processGroupCallSignalling ProcessGroupCallSignalling ::= localValue 41 forwardGroupCallSignalling ForwardGroupCallSignalling ::= localValue 42 -- gprs location updating operation codes
updateGprsLocation
UpdateGprsLocation ::= localValue 23
-- gprs location information retrieval operation codes
sendRoutingInfoForGprs
SendRoutingInfoForGprs ::= localValue 24
-- failure reporting operation codes
failureReport
FailureReport ::= localValue 25
-- GPRS notification operation codes
noteMsPresentForGprs
NoteMsPresentForGprs ::= localValue 26
-- Location service operation codes provideSubscriberLocation ProvideSubscriberLocation ::= localValue 83 sendRoutingInfoForLCS SendRoutingInfoForLCS ::= localValue 85 subscriberLocationReport SubscriberLocationReport ::= localValue 86 -- Mobility Management operation codes noteMM-Event NoteMM-Event ::= localValue 89
-- generic error codes systemFailure SystemFailure ::= localValue 34 dataMissing DataMissing ::= localValue 35 unexpectedDataValue UnexpectedDataValue ::= localValue 36 facilityNotSupported FacilityNotSupported ::= localValue 21 incompatibleTerminal IncompatibleTerminal ::= localValue 28 resourceLimitation ResourceLimitation ::= localValue 51 -- identification and numbering error codes unknownSubscriber UnknownSubscriber ::= localValue 1 numberChanged NumberChanged ::= localValue 44 unknownMSC UnknownMSC ::= localValue 3 unidentifiedSubscriber UnidentifiedSubscriber ::= localValue 5 unknownEquipment UnknownEquipment ::= localValue 7 -- subscription error codes roamingNotAllowed RoamingNotAllowed ::= localValue 8 illegalSubscriber IllegalSubscriber ::= localValue 9 illegalEquipment IllegalEquipment ::= localValue 12 bearerServiceNotProvisioned BearerServiceNotProvisioned ::= localValue 10 teleserviceNotProvisioned TeleserviceNotProvisioned ::= localValue 11 -- handover error codes noHandoverNumberAvailable NoHandoverNumberAvailable ::= localValue 25 subsequentHandoverFailure SubsequentHandoverFailure ::= localValue 26 targetCellOutsideGroupCallArea TargetCellOutsideGroupCallArea ::= localValue 42
1166
1167 Release 4 1168 1169
9372 9373 9374 9375 9376 9377 9378 9379 9380 9381 9382 9383 9384 9385 9386 9387 9388 9389 9390 9391 9392 9393 9394 9395 9396 9397 9398 9399 9400 9401 9402 9403 9404 9405 9406 9407 9408 9409 9410 9411 9412 9413 9414 9415 9416 9417 9418 9419 9420 9421 9422 9423 9424 9425 9426 9427 9428 9429 9430 9431 9432 9433 9434 9435 9436 9437 9438 9439 9440 9441 9442 9443 9444
293
3GPP TS 29.002 V4.17.0 (2006-06)
-- operation and maintenance error codes tracingBufferFull TracingBufferFull ::= localValue 40
-- call handling error codes noRoamingNumberAvailable NoRoamingNumberAvailable ::= localValue 39 absentSubscriber AbsentSubscriber ::= localValue 27 busySubscriber BusySubscriber ::= localValue 45 noSubscriberReply NoSubscriberReply ::= localValue 46 callBarred CallBarred ::= localValue 13 forwardingFailed ForwardingFailed ::= localValue 47 or-NotAllowed OR-NotAllowed ::= localValue 48 forwardingViolation ForwardingViolation ::= localValue 14 cug-Reject CUG-Reject ::= localValue 15 -- any time interrogation error codes ati-NotAllowed ATI-NotAllowed ::= localValue 49
-- any time information handling error codes atsi-NotAllowed ATSI-NotAllowed ::= localValue 60 atm-NotAllowed ATM-NotAllowed ::= localValue 61 informationNotAvailable InformationNotAvailable ::= localValue 62 -- Group Call error codes noGroupCallNumberAvailable
NoGroupCallNumberAvailable ::= localValue 50
-- supplementary service error codes illegalSS-Operation IllegalSS-Operation ::= localValue 16 ss-ErrorStatus SS-ErrorStatus ::= localValue 17 ss-NotAvailable SS-NotAvailable ::= localValue 18 ss-SubscriptionViolation SS-SubscriptionViolation ::= localValue 19 ss-Incompatibility SS-Incompatibility ::= localValue 20 unknownAlphabet UnknownAlphabet ::= localValue 71 ussd-Busy USSD-Busy ::= localValue 72 pw-RegistrationFailure PW-RegistrationFailure ::= localValue 37 negativePW-Check NegativePW-Check ::= localValue 38 numberOfPW-AttemptsViolation NumberOfPW-AttemptsViolation ::= localValue 43 shortTermDenial ShortTermDenial ::= localValue 29 longTermDenial LongTermDenial ::= localValue 30 -- short message service error codes subscriberBusyForMT-SMS SubscriberBusyForMT-SMS ::= localValue 31 sm-DeliveryFailure SM-DeliveryFailure ::= localValue 32 messageWaitingListFull MessageWaitingListFull ::= localValue 33 absentsubscriberSM AbsentSubscriberSM ::= localValue 6 -- location service error codes unauthorizedRequestingNetwork UnauthorizedRequestingNetwork::= localValue 52 unauthorizedLCSClient UnauthorizedLCSClient ::= localValue 53 positionMethodFailure PositionMethodFailure ::= localValue 54 unknownOrUnreachableLCSClient UnknownOrUnreachableLCSClient ::= localValue 58
-- Mobility Management error codes mm-EventNotSupported MM-EventNotSupported ::= localValue 59
-- The following operation codes are reserved for operations -- existing in previous versions of the protocol
1170
1171 Release 4 1172 1173
9445 9446 9447 9448 9449 9450 9451 9452 9453 9454 9455 9456 9457 9458 9459 9460 9461 9462 9463 9464 9465 9466 9467
294
AC used map-ac infoRetrieval (14) version1 (1) map-ac networkFunctionalSs (18) version1 (1) map-ac handoverControl (11) version1 (1) map-ac handoverControl (11) version1 (1) map-ac handoverControl (11) version1 (1) map-ac mwdMngt (24) version1 (1) map-ac shortMsgAlert (23) version1 (1) map-ac handoverControl (11) version1 (1) map-ac networkFunctionalSs (18) version1 (1)
3GPP TS 29.002 V4.17.0 (2006-06)
Oper. Code localValue 9 localValue 19 localValue 28 localValue 30 localValue 35 localValue 48 localValue 49 localValue 52 localValue 54
-- Operation Name --- sendParameters -- processUnstructuredSS-Data -- performHandover -- performSubsequentHandover -- noteInternalHandover -- noteSubscriberPresent -- alertServiceCentreWithoutResult -- traceSubscriberActivity -- beginSubscriberActivity
-- The following error codes are reserved for errors -- existing in previous versions of the protocol -- Error Name --- unknownBaseStation -- invalidTargetBaseStation -- noRadioResourceAvailable END AC used map-ac handoverControl (11) version1 (1) map-ac handoverControl (11) version1 (1) map-ac handoverControl (11) version1 (1) Error Code localValue 2 localValue 23 localValue 24
9468 9469
9470 9471 9472 9473 9474 9475 9476 9477 9478 9479 9480 9481 9482 9483 9484 9485 9486 9487 9488 9489 9490 9491 9492 9493 9494 9495 9496 9497 9498 9499 9500 9501 9502 9503 9504 9505 9506 9507 9508 9509 9510 9511 9512 9513 9514 9515 9516
17.6 MAP operation and error types
17.6.1 Mobile Service Operations
MAP-MobileServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MobileServiceOperations (5) version7 (7)} DEFINITIONS ::= BEGIN EXPORTS -- location registration operations UpdateLocation, CancelLocation, PurgeMS, SendIdentification, -- gprs location registration operations UpdateGprsLocation, -- subscriber information enquiry operations ProvideSubscriberInfo, -- any time information enquiry operations AnyTimeInterrogation, -- any time information handling operations AnyTimeSubscriptionInterrogation, AnyTimeModification, -- subscriber data modification notification operations NoteSubscriberDataModified, -- handover operations PrepareHandover, SendEndSignal, ProcessAccessSignalling, ForwardAccessSignalling, PrepareSubsequentHandover, -- authentication management operations SendAuthenticationInfo, AuthenticationFailureReport,
1174
1175 Release 4 1176 1177
9517 9518 9519 9520 9521 9522 9523 9524 9525 9526 9527 9528 9529 9530 9531 9532 9533 9534 9535 9536 9537 9538 9539 9540 9541 9542 9543 9544 9545 9546 9547 9548 9549 9550 9551 9552 9553 9554 9555 9556 9557 9558 9559 9560 9561 9562 9563 9564 9565 9566 9567 9568 9569 9570 9571 9572 9573 9574 9575 9576 9577 9578 9579 9580 9581 9582 9583 9584 9585 9586 9587 9588 9589 9590 9591 9592 9593 9594 9595
295
3GPP TS 29.002 V4.17.0 (2006-06)
-- IMEI management operations CheckIMEI, -- subscriber management operations InsertSubscriberData, DeleteSubscriberData, -- fault recovery operations Reset, ForwardCheckSS-Indication, RestoreData,
-- gprs location information retrieval operations SendRoutingInfoForGprs, -- failure reporting operations FailureReport, -- gprs notification operations NoteMsPresentForGprs, -- Mobility Management operations NoteMM-Event
; IMPORTS OPERATION FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SystemFailure, DataMissing, UnexpectedDataValue, UnknownSubscriber, UnknownMSC, UnidentifiedSubscriber, UnknownEquipment, RoamingNotAllowed, ATI-NotAllowed, NoHandoverNumberAvailable, SubsequentHandoverFailure, AbsentSubscriber, MM-EventNotSupported, ATSI-NotAllowed, ATM-NotAllowed, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-ErrorStatus, SS-NotAvailable, SS-Incompatibility, SS-SubscriptionViolation, InformationNotAvailable, TargetCellOutsideGroupCallArea FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version7 (7)} UpdateLocationArg, UpdateLocationRes, CancelLocationArg, CancelLocationRes, PurgeMS-Arg, PurgeMS-Res, SendIdentificationArg, SendIdentificationRes, UpdateGprsLocationArg, UpdateGprsLocationRes, PrepareHO-Arg, PrepareHO-Res, ForwardAccessSignalling-Arg, ProcessAccessSignalling-Arg,
1178
1179 Release 4 1180 1181
9596 9597 9598 9599 9600 9601 9602 9603 9604 9605 9606 9607 9608 9609 9610 9611 9612 9613 9614 9615 9616 9617 9618 9619 9620 9621 9622 9623 9624 9625 9626 9627 9628 9629 9630 9631 9632 9633 9634 9635 9636 9637 9638 9639 9640 9641 9642 9643 9644 9645 9646 9647 9648 9649 9650 9651 9652 9653 9654 9655 9656 9657 9658 9659 9660 9661 9662 9663 9664 9665 9666
296
3GPP TS 29.002 V4.17.0 (2006-06)
SendEndSignal-Arg, SendEndSignal-Res, PrepareSubsequentHO-Res, PrepareSubsequentHO-Arg, SendAuthenticationInfoArg, SendAuthenticationInfoRes, AuthenticationFailureReportArg, AuthenticationFailureReportRes, EquipmentStatus, InsertSubscriberDataArg, InsertSubscriberDataRes, DeleteSubscriberDataArg, DeleteSubscriberDataRes, ResetArg, RestoreDataArg, RestoreDataRes, ProvideSubscriberInfoArg, ProvideSubscriberInfoRes, AnyTimeSubscriptionInterrogationArg, AnyTimeSubscriptionInterrogationRes, AnyTimeModificationArg, AnyTimeModificationRes, NoteSubscriberDataModifiedArg, NoteSubscriberDataModifiedRes, AnyTimeInterrogationArg, AnyTimeInterrogationRes, SendRoutingInfoForGprsArg, SendRoutingInfoForGprsRes, FailureReportArg, FailureReportRes, NoteMsPresentForGprsArg, NoteMsPresentForGprsRes, NoteMM-EventArg, NoteMM-EventRes
FROM MAP-MS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MS-DataTypes (11) version7 (7)} IMEI FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version7 (7)} ; -- location registration operations UpdateLocation ::= OPERATION ARGUMENT updateLocationArg RESULT updateLocationRes ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, UnknownSubscriber, RoamingNotAllowed} CancelLocation ::= OPERATION ARGUMENT cancelLocationArg RESULT cancelLocationRes -- optional ERRORS { DataMissing, UnexpectedDataValue} --Timer m UpdateLocationArg UpdateLocationRes
--Timer m CancelLocationArg CancelLocationRes
1182
1183 Release 4 1184 1185
9667 9668 9669 9670 9671 9672 9673 9674 9675 9676 9677 9678 9679 9680 9681 9682 9683 9684 9685 9686 9687 9688 9689 9690 9691 9692 9693 9694 9695 9696 9697 9698 9699 9700 9701 9702 9703 9704 9705 9706 9707 9708 9709 9710 9711 9712 9713 9714 9715 9716 9717 9718 9719 9720 9721 9722 9723 9724 9725 9726 9727 9728 9729 9730 9731 9732 9733 9734 9735 9736 9737 9738 9739 9740 9741 9742 9743
297
3GPP TS 29.002 V4.17.0 (2006-06)
--Timer m
PurgeMS ::= OPERATION ARGUMENT purgeMS-Arg RESULT purgeMS-Res -- optional ERRORS{ DataMissing, UnexpectedDataValue, UnknownSubscriber} SendIdentification ::= OPERATION ARGUMENT sendIdentificationArg RESULT sendIdentificationRes ERRORS { DataMissing, UnidentifiedSubscriber} -- gprs location registration operations UpdateGprsLocation ::= OPERATION ARGUMENT updateGprsLocationArg RESULT updateGprsLocationRes ERRORS { SystemFailure, UnexpectedDataValue, UnknownSubscriber, RoamingNotAllowed}
PurgeMS-Arg PurgeMS-Res
--Timer s SendIdentificationArg SendIdentificationRes
--Timer m UpdateGprsLocationArg UpdateGprsLocationRes
-- subscriber information enquiry operations
ProvideSubscriberInfo ::= OPERATION
ARGUMENT provideSubscriberInfoArg RESULT provideSubscriberInfoRes ERRORS { DataMissing, UnexpectedDataValue} ProvideSubscriberInfoArg ProvideSubscriberInfoRes
--Timer m
-- any time information enquiry operations
AnyTimeInterrogation ::= OPERATION
ARGUMENT anyTimeInterrogationArg RESULT anyTimeInterrogationRes ERRORS { SystemFailure, ATI-NotAllowed, DataMissing, UnexpectedDataValue, UnknownSubscriber} AnyTimeInterrogationArg AnyTimeInterrogationRes
--Timer m
-- any time information handling operations
AnyTimeSubscriptionInterrogation ::= OPERATION
--Timer m ARGUMENT anyTimeSubscriptionInterrogationArg AnyTimeSubscriptionInterrogationArg RESULT anyTimeSubscriptionInterrogationRes AnyTimeSubscriptionInterrogationRes ERRORS { ATSI-NotAllowed, DataMissing, UnexpectedDataValue, UnknownSubscriber, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-NotAvailable, InformationNotAvailable}
1186
1187 Release 4 1188 1189
9744 9745 9746 9747 9748 9749 9750 9751 9752 9753 9754 9755 9756 9757 9758 9759 9760 9761 9762 9763 9764 9765 9766 9767 9768 9769 9770 9771 9772 9773 9774 9775 9776 9777 9778 9779 9780 9781 9782 9783 9784 9785 9786 9787 9788 9789 9790 9791 9792 9793 9794 9795 9796 9797 9798 9799 9800 9801 9802 9803 9804 9805 9806 9807 9808 9809 9810 9811 9812 9813 9814 9815 9816 9817 9818
298
3GPP TS 29.002 V4.17.0 (2006-06)
--Timer m
AnyTimeModification ::= OPERATION ARGUMENT anyTimeModificationArg RESULT anyTimeModificationRes ERRORS { ATM-NotAllowed, DataMissing, UnexpectedDataValue, UnknownSubscriber, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-SubscriptionViolation, SS-ErrorStatus, SS-Incompatibility, InformationNotAvailable}
AnyTimeModificationArg AnyTimeModificationRes
-- subscriber data modification notification operations NoteSubscriberDataModified ::= OPERATION ARGUMENT noteSubscriberDataModifiedArg NoteSubscriberDataModifiedArg RESULT noteSubscriberDataModifiedRes NoteSubscriberDataModifiedRes -- optional ERRORS { DataMissing, UnexpectedDataValue, UnknownSubscriber} -- handover operations PrepareHandover ::= OPERATION ARGUMENT prepareHO-Arg PrepareHO-Arg RESULT prepareHO-Res PrepareHO-Res ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, NoHandoverNumberAvailable, TargetCellOutsideGroupCallArea } SendEndSignal ::= OPERATION ARGUMENT sendEndSignal-Arg RESULT sendEndSignal-Res ProcessAccessSignalling ::= OPERATION ARGUMENT processAccessSignalling-Arg ForwardAccessSignalling ::= OPERATION ARGUMENT forwardAccessSignalling-Arg PrepareSubsequentHandover ::= OPERATION ARGUMENT prepareSubsequentHO-Arg RESULT prepareSubsequentHO-Res ERRORS { UnexpectedDataValue, DataMissing, UnknownMSC, SubsequentHandoverFailure} -- authentication management operations --Timer m --Timer m
--Timer l SendEndSignal-Arg SendEndSignal-Res --Timer s ProcessAccessSignalling-Arg --Timer s ForwardAccessSignalling-Arg --Timer m PrepareSubsequentHO-Arg PrepareSubsequentHO-Res
1190
1191 Release 4 1192 1193
9819 9820 9821 9822 9823 9824 9825 9826 9827 9828 9829 9830 9831 9832 9833 9834 9835 9836 9837 9838 9839 9840 9841 9842 9843 9844 9845 9846 9847 9848 9849 9850 9851 9852 9853 9854 9855 9856 9857 9858 9859 9860 9861 9862 9863 9864 9865 9866 9867 9868 9869 9870 9871 9872 9873 9874 9875 9876 9877 9878 9879 9880 9881 9882 9883 9884 9885 9886 9887 9888 9889 9890
299
3GPP TS 29.002 V4.17.0 (2006-06)
SendAuthenticationInfo ::= OPERATION --Timer m ARGUMENT sendAuthenticationInfoArg SendAuthenticationInfoArg -- optional -- within a dialogue sendAuthenticationInfoArg shall not be present in -- subsequent invoke components. If received in a subsequent invoke component -- it shall be discarded. RESULT sendAuthenticationInfoRes -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, UnknownSubscriber} SendAuthenticationInfoRes
AuthenticationFailureReport ::= OPERATION --Timer m ARGUMENT authenticationFailureReportArg AuthenticationFailureReportArg RESULT authenticationFailureReportRes AuthenticationFailureReportRes -- optional ERRORS { SystemFailure, UnexpectedDataValue, UnknownSubscriber} -- IMEI management operations CheckIMEI ::= OPERATION ARGUMENT imei RESULT equipmentStatus ERRORS { SystemFailure, DataMissing, UnknownEquipment} -- subscriber management operations InsertSubscriberData ::= OPERATION ARGUMENT insertSubscriberDataArg RESULT insertSubscriberDataRes -- optional ERRORS { DataMissing, UnexpectedDataValue, UnidentifiedSubscriber} DeleteSubscriberData ::= OPERATION ARGUMENT deleteSubscriberDataArg RESULT deleteSubscriberDataRes -- optional ERRORS { DataMissing, UnexpectedDataValue, UnidentifiedSubscriber} -- fault recovery operations Reset ::= OPERATION ARGUMENT resetArg ForwardCheckSS-Indication ::= OPERATION --Timer m ResetArg --Timer s --Timer m InsertSubscriberDataArg InsertSubscriberDataRes --Timer m IMEI EquipmentStatus
--Timer m DeleteSubscriberDataArg DeleteSubscriberDataRes
1194
1195 Release 4 1196 1197
9891 9892 9893 9894 9895 9896 9897 9898 9899 9900 9901 9902 9903 9904 9905 9906 9907 9908 9909 9910 9911 9912 9913 9914 9915 9916 9917 9918 9919 9920 9921 9922 9923 9924 9925 9926 9927 9928 9929 9930 9931 9932 9933 9934 9935 9936 9937 9938 9939 9940 9941 9942 9943 9944 9945 9946 9947 9948 9949 9950 9951 9952 9953 9954 9955 9956 9957
300
3GPP TS 29.002 V4.17.0 (2006-06)
--Timer m
RestoreData ::= OPERATION ARGUMENT restoreDataArg RESULT restoreDataRes ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, UnknownSubscriber}
RestoreDataArg RestoreDataRes
-- gprs location information retrieval operations SendRoutingInfoForGprs ::= OPERATION ARGUMENT sendRoutingInfoForGprsArg RESULT sendRoutingInfoForGprsRes ERRORS { AbsentSubscriber, SystemFailure, DataMissing, UnexpectedDataValue, UnknownSubscriber, CallBarred } -- failure reporting operations FailureReport ::= OPERATION ARGUMENT failureReportArg RESULT failureReportRes -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, UnknownSubscriber} -- gprs notification operations NoteMsPresentForGprs ::= OPERATION ARGUMENT noteMsPresentForGprsArg RESULT noteMsPresentForGprsRes -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, UnknownSubscriber} NoteMM-Event ::= OPERATION ARGUMENT noteMM-EventArg RESULT noteMM-EventRes ERRORS { DataMissing, UnexpectedDataValue, UnknownSubscriber, MM-EventNotSupported} END --Timer m NoteMsPresentForGprsArg NoteMsPresentForGprsRes --Timer m FailureReportArg FailureReportRes --Timer m SendRoutingInfoForGprsArg SendRoutingInfoForGprsRes
--Timer m NoteMM-EventArg NoteMM-EventRes
9958
9959 9960 9961 9962 9963 9964 9965 9966
17.6.2 Operation and Maintenance Operations
MAP-OperationAndMaintenanceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-OperationAndMaintenanceOperations (6) version7 (7)} DEFINITIONS ::=
1198
9967 9968 9969 9970 9971 9972 9973 9974 9975 9976 9977 9978 9979 9980 9981 9982 9983 9984 9985 9986 9987 9988 9989 9990 9991 9992 9993 9994 9995 9996 9997 9998 9999 10000 10001 10002 10003 10004 10005 10006 10007 10008 10009 10010 10011 10012 10013 10014 10015 10016 10017 10018 10019 10020 10021 10022 10023 10024 10025 10026 10027 10028 10029 10030 10031 10032 10033 10034 10035 10036 10037 10038 10039 10040 10041 10042 10043 10044
1199 Release 4 1200 1201
BEGIN EXPORTS ActivateTraceMode, DeactivateTraceMode, SendIMSI ;
301
3GPP TS 29.002 V4.17.0 (2006-06)
IMPORTS OPERATION FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnknownSubscriber, UnidentifiedSubscriber, TracingBufferFull FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version7 (7)} ActivateTraceModeArg, ActivateTraceModeRes, DeactivateTraceModeArg, DeactivateTraceModeRes FROM MAP-OM-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-OM-DataTypes (12) version7 (7)} ISDN-AddressString, IMSI FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version7 (7)} ; ActivateTraceMode ::= OPERATION ARGUMENT activateTraceModeArg RESULT activateTraceModeRes -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnidentifiedSubscriber, TracingBufferFull} DeactivateTraceMode ::= OPERATION ARGUMENT deactivateTraceModeArg RESULT deactivateTraceModeRes -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnidentifiedSubscriber} SendIMSI ::= OPERATION ARGUMENT msisdn RESULT imsi ERRORS { DataMissing, UnexpectedDataValue, UnknownSubscriber} --Timer m ActivateTraceModeArg ActivateTraceModeRes
--Timer m DeactivateTraceModeArg DeactivateTraceModeRes
--Timer m ISDN-AddressString IMSI
1202
10045
1203 Release 4 1204 1205
END
302
3GPP TS 29.002 V4.17.0 (2006-06)
10046
10047 10048 10049 10050 10051 10052 10053 10054 10055 10056 10057 10058 10059 10060 10061 10062 10063 10064 10065 10066 10067 10068 10069 10070 10071 10072 10073 10074 10075 10076 10077 10078 10079 10080 10081 10082 10083 10084 10085 10086 10087 10088 10089 10090 10091 10092 10095 10096 10097 10098 10099 10100 10101 10102 10103 10104 10105 10106 10107 10108 10109 10110 10111 10112 10113 10114 10115 10116 10117 10118 10119 10120 10121
10093 10094
17.6.3 Call Handling Operations
MAP-CallHandlingOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CallHandlingOperations (7) version7 (7)} DEFINITIONS ::= BEGIN EXPORTS SendRoutingInfo, ProvideRoamingNumber, ResumeCallHandling, ProvideSIWFSNumber, SIWFSSignallingModify, SetReportingState, StatusReport, RemoteUserFree, IST-Alert, IST-Command ; IMPORTS OPERATION FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, OR-NotAllowed, UnknownSubscriber, NumberChanged, BearerServiceNotProvisioned, TeleserviceNotProvisioned, NoRoamingNumberAvailable, AbsentSubscriber, BusySubscriber, NoSubscriberReply, CallBarred, ForwardingViolation, ForwardingFailed, CUG-Reject, ResourceLimitation, IncompatibleTerminal, UnidentifiedSubscriber FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version7 (7)} SendRoutingInfoArg, SendRoutingInfoRes, ProvideRoamingNumberArg, ProvideRoamingNumberRes, ResumeCallHandlingArg, ResumeCallHandlingRes, ProvideSIWFSNumberArg, ProvideSIWFSNumberRes, SIWFSSignallingModifyArg, SIWFSSignallingModifyRes, SetReportingStateArg, SetReportingStateRes, StatusReportArg, StatusReportRes, RemoteUserFreeArg, RemoteUserFreeRes, IST-AlertArg, IST-AlertRes, IST-CommandArg, IST-CommandRes FROM MAP-CH-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0)
1206
10122 10123 10124 10125 10126 10127 10128 10129 10130 10131 10132 10133 10134 10135 10136 10137 10138 10139 10140 10141 10142 10143 10144 10145 10146 10147 10148 10149 10150 10151 10152 10153 10154 10155 10156 10157 10158 10159 10160 10161 10162 10163 10164 10165 10166 10167 10168 10169 10170 10171 10172 10173 10174 10175 10176 10177 10178 10179 10180 10181 10182 10183 10184 10185 10186 10187 10188 10189 10190 10191 10192 10193 10194 10195 10196 10197 10198
1207 Release 4 1208 1209
;
303
3GPP TS 29.002 V4.17.0 (2006-06)
gsm-Network (1) modules (3) map-CH-DataTypes (13) version7 (7)}
SendRoutingInfo ::= OPERATION --Timer m -- The timer is set to the upper limit of the range if the GMSC supports pre-paging. ARGUMENT sendRoutingInfoArg SendRoutingInfoArg RESULT sendRoutingInfoRes SendRoutingInfoRes ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, OR-NotAllowed, UnknownSubscriber, NumberChanged, BearerServiceNotProvisioned, TeleserviceNotProvisioned, AbsentSubscriber, BusySubscriber, NoSubscriberReply, CallBarred, CUG-Reject, ForwardingViolation} ProvideRoamingNumber ::= OPERATION --Timer m -- The timer is set to the upper limit of the range if the HLR supports pre-paging. ARGUMENT provideRoamingNumberArg ProvideRoamingNumberArg RESULT provideRoamingNumberRes ProvideRoamingNumberRes ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, OR-NotAllowed, AbsentSubscriber, NoRoamingNumberAvailable} ResumeCallHandling ::= OPERATION ARGUMENT resumeCallHandlingArg RESULT resumeCallHandlingRes -- optional ERRORS { ForwardingFailed, OR-NotAllowed, UnexpectedDataValue, DataMissing } ProvideSIWFSNumber ::= OPERATION ARGUMENT provideSIWFSNumberArg RESULT provideSIWFSNumberRes ERRORS { ResourceLimitation, DataMissing, UnexpectedDataValue, SystemFailure} SIWFSSignallingModify ::= OPERATION ARGUMENT sIWFSSignallingModifyArg RESULT sIWFSSignallingModifyRes -- optional ERRORS { ResourceLimitation, DataMissing, UnexpectedDataValue, SystemFailure} --Timer m ResumeCallHandlingArg ResumeCallHandlingRes
--Timer m ProvideSIWFSNumberArg ProvideSIWFSNumberRes
--Timer m SIWFSSignallingModifyArg SIWFSSignallingModifyRes
1210
10199 10200 10201 10202 10203 10204 10205 10206 10207 10208 10209 10210 10211 10212 10213 10214 10215 10216 10217 10218 10219 10220 10221 10222 10223 10224 10225 10226 10227 10228 10229 10230 10231 10232 10233 10234 10235 10236 10237 10238 10239 10240 10241 10242 10243 10244 10245 10246 10247 10248 10249 10250 10251 10252 10253 10254 10255 10256 10257 10258 10259 10260 10261 10262 10263 10264
1211 Release 4 1212 1213
304
3GPP TS 29.002 V4.17.0 (2006-06)
--Timer m
SetReportingState ::= OPERATION ARGUMENT setReportingStateArg RESULT setReportingStateRes -- optional ERRORS { SystemFailure, UnidentifiedSubscriber, UnexpectedDataValue, DataMissing, ResourceLimitation, FacilityNotSupported} StatusReport ::= OPERATION ARGUMENT statusReportArg RESULT statusReportRes -- optional ERRORS { UnknownSubscriber, SystemFailure, UnexpectedDataValue, DataMissing} RemoteUserFree ::= OPERATION ARGUMENT remoteUserFreeArg RESULT remoteUserFreeRes ERRORS { UnexpectedDataValue, DataMissing, IncompatibleTerminal, AbsentSubscriber, SystemFailure, BusySubscriber} IST-Alert ::= OPERATION ARGUMENT istAlertArg RESULT istAlertRes -- optional ERRORS { UnexpectedDataValue, ResourceLimitation, UnknownSubscriber, SystemFailure, FacilityNotSupported} IST-Command ::= OPERATION ARGUMENT istCommandArg RESULT istCommandRes -- optional ERRORS { UnexpectedDataValue, ResourceLimitation, UnknownSubscriber, SystemFailure, FacilityNotSupported} END
SetReportingStateArg SetReportingStateRes
--Timer m StatusReportArg StatusReportRes
--Timer ml RemoteUserFreeArg RemoteUserFreeRes
--Timer m IST-AlertArg IST-AlertRes
--Timer m IST-CommandArg IST-CommandRes
10265
10266 10267 10268 10269 10270 10271 10272 10273 10274
17.6.4 Supplementary service operations
MAP-SupplementaryServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SupplementaryServiceOperations (8) version7 (7)} DEFINITIONS ::=
1214
10275 10276 10277 10278 10279 10280 10281 10282 10283 10284 10285 10286 10289 10290 10291 10292 10293 10294 10295 10296 10297 10298 10299 10300 10301 10302 10303 10304 10305 10306 10307 10308 10309 10310 10311 10312 10313 10314 10315 10316 10317 10318 10319 10320 10321 10322 10323 10324 10325 10326 10327 10328 10329 10330 10331 10332 10333 10334 10335 10336 10337 10338 10339 10340 10341 10342 10343 10344 10345 10346 10347 10348 10349 10350 10351
10287 10288
1215 Release 4 1216 1217
BEGIN EXPORTS RegisterSS, EraseSS, ActivateSS, DeactivateSS, InterrogateSS, ProcessUnstructuredSS-Request, UnstructuredSS-Request, UnstructuredSS-Notify, RegisterPassword, GetPassword, SS-InvocationNotification, RegisterCC-Entry, EraseCC-Entry ;
305
3GPP TS 29.002 V4.17.0 (2006-06)
IMPORTS OPERATION FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SystemFailure, DataMissing, UnexpectedDataValue, UnknownSubscriber, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-ErrorStatus, SS-NotAvailable, SS-SubscriptionViolation, SS-Incompatibility, PW-RegistrationFailure, NegativePW-Check, NumberOfPW-AttemptsViolation, UnknownAlphabet, USSD-Busy, AbsentSubscriber, IllegalSubscriber, IllegalEquipment, ShortTermDenial, LongTermDenial, FacilityNotSupported FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version7 (7)} RegisterSS-Arg, SS-Info, SS-ForBS-Code, InterrogateSS-Res, USSD-Arg, USSD-Res, Password, GuidanceInfo, SS-InvocationNotificationArg, SS-InvocationNotificationRes, RegisterCC-EntryArg, RegisterCC-EntryRes, EraseCC-EntryArg, EraseCC-EntryRes FROM MAP-SS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version7 (7)} SS-Code FROM MAP-SS-Code { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version7 (7)} ; -- supplementary service handling operations
1218
10352 10353 10354 10355 10356 10357 10358 10359 10360 10361 10362 10363 10364 10365 10366 10367 10368 10369 10370 10371 10372 10373 10374 10375 10376 10377 10378 10379 10380 10381 10382 10383 10384 10385 10386 10387 10388 10389 10390 10391 10392 10393 10394 10395 10396 10397 10398 10399 10400 10401 10402 10403 10404 10405 10406 10407 10408 10409 10410 10411 10412 10413 10414 10415 10416 10417 10418 10419 10420 10421 10422 10423 10424
1219 Release 4 1220 1221
306
3GPP TS 29.002 V4.17.0 (2006-06)
--Timer m
RegisterSS ::= OPERATION ARGUMENT registerSS-Arg RESULT ss-Info -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-ErrorStatus, SS-Incompatibility} EraseSS ::= OPERATION ARGUMENT ss-ForBS RESULT ss-Info -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-ErrorStatus } ActivateSS ::= OPERATION ARGUMENT ss-ForBS RESULT ss-Info -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-ErrorStatus, SS-SubscriptionViolation, SS-Incompatibility, NegativePW-Check, NumberOfPW-AttemptsViolation} DeactivateSS ::= OPERATION ARGUMENT ss-ForBS RESULT ss-Info -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-ErrorStatus, SS-SubscriptionViolation, NegativePW-Check, NumberOfPW-AttemptsViolation}
RegisterSS-Arg SS-Info
--Timer m SS-ForBS-Code SS-Info
--Timer m SS-ForBS-Code SS-Info
--Timer m SS-ForBS-Code SS-Info
1222
10425 10426 10427 10428 10429 10430 10431 10432 10433 10434 10435 10436 10437 10438 10439 10440 10441 10442 10443 10444 10445 10446 10447 10448 10449 10450 10451 10452 10453 10454 10455 10456 10457 10458 10459 10460 10461 10462 10463 10464 10465 10466 10467 10468 10469 10470 10471 10472 10473 10474 10475 10476 10477 10478 10479 10480 10481 10482 10483 10484 10485 10486 10487 10488 10489 10490 10491 10492 10493 10494 10495 10496 10497 10498
1223 Release 4 1224 1225
307
3GPP TS 29.002 V4.17.0 (2006-06)
--Timer m
InterrogateSS ::= OPERATION ARGUMENT ss-ForBS RESULT interrogateSS-Res ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, BearerServiceNotProvisioned, TeleserviceNotProvisioned, CallBarred, IllegalSS-Operation, SS-NotAvailable}
SS-ForBS-Code InterrogateSS-Res
ProcessUnstructuredSS-Request ::= OPERATION ARGUMENT ussd-Arg USSD-Arg RESULT ussd-Res USSD-Res ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, UnknownAlphabet, CallBarred} UnstructuredSS-Request ::= OPERATION ARGUMENT ussd-Arg RESULT ussd-Res -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, AbsentSubscriber, IllegalSubscriber, IllegalEquipment, UnknownAlphabet, USSD-Busy} UnstructuredSS-Notify ::= OPERATION ARGUMENT ussd-Arg RESULT ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, AbsentSubscriber, IllegalSubscriber, IllegalEquipment, UnknownAlphabet, USSD-Busy} RegisterPassword ::= OPERATION ARGUMENT ss-Code RESULT newPassword ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, CallBarred, SS-SubscriptionViolation, PW-RegistrationFailure, NegativePW-Check, NumberOfPW-AttemptsViolation} LINKED { GetPassword}
--Timer 10 minutes
--Timer ml USSD-Arg USSD-Res
--Timer ml USSD-Arg
--Timer ml SS-Code Password
1226
10499 10500 10501 10502 10503 10504
10505 10506 10507 10508 10509 10510 10511 10512 10513 10514
1227 Release 4 1228 1229
308
3GPP TS 29.002 V4.17.0 (2006-06)
--Timer m
GetPassword ::= OPERATION ARGUMENT guidanceInfo RESULT currentPassword SS-InvocationNotification ::= OPERATION ARGUMENT ss-InvocationNotificationArg RESULT ss-InvocationNotificationRes -- optional ERRORS { DataMissing, UnexpectedDataValue, UnknownSubscriber} RegisterCC-Entry ::= OPERATION ARGUMENT registerCC-EntryArg RESULT registerCC-EntryRes ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, CallBarred, IllegalSS-Operation, SS-ErrorStatus, SS-Incompatibility, ShortTermDenial, LongTermDenial, FacilityNotSupported} EraseCC-Entry ::= OPERATION ARGUMENT eraseCC-EntryArg RESULT eraseCC-EntryRes ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, CallBarred, IllegalSS-Operation, SS-ErrorStatus} END
GuidanceInfo Password --Timer m SS-InvocationNotificationArg SS-InvocationNotificationRes
10515 10516 10517 10518 10519 10520 10521 10522 10523 10524 10525 10526 10527 10528 10529 10530 10531 10532 10533 10534 10535 10536 10537 10538 10539 10540 10541 10542 10543 10544 10545 10546
--Timer m RegisterCC-EntryArg RegisterCC-EntryRes
--Timer m EraseCC-EntryArg EraseCC-EntryRes
10547
10548 10549 10550 10551 10552 10553 10554 10555 10556 10557 10558 10559 10560 10561 10562 10563 10564 10565 10566 10567 10568 10569 10570 10571 10572 10573 10574 10575 10576
17.6.5 Short message service operations
MAP-ShortMessageServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ShortMessageServiceOperations (9) version7 (7)} DEFINITIONS ::= BEGIN EXPORTS SendRoutingInfoForSM, MO-ForwardSM, MT-ForwardSM, ReportSM-DeliveryStatus, AlertServiceCentre, InformServiceCentre, ReadyForSM ; IMPORTS OPERATION FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SystemFailure, DataMissing, UnexpectedDataValue,
1230
10577 10578 10579 10580 10581 10582 10583 10584 10585 10586 10587 10588 10589 10590 10591 10592 10593 10594 10595 10596 10597 10598 10599 10600 10601 10602 10603 10604 10605 10606 10607 10608 10609 10610 10611 10612 10613 10614 10615 10616 10617 10618 10619 10620 10621 10622 10623 10624 10625 10626 10627 10628 10629 10630 10631 10632 10633 10634 10635 10636 10637 10638 10639
1231 Release 4 1232 1233
309
3GPP TS 29.002 V4.17.0 (2006-06)
FacilityNotSupported, UnknownSubscriber, UnidentifiedSubscriber, IllegalSubscriber, IllegalEquipment, TeleserviceNotProvisioned, CallBarred, SubscriberBusyForMT-SMS, SM-DeliveryFailure, MessageWaitingListFull, AbsentSubscriberSM FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version7 (7)} RoutingInfoForSM-Arg, RoutingInfoForSM-Res, MO-ForwardSM-Arg, MO-ForwardSM-Res, MT-ForwardSM-Arg, MT-ForwardSM-Res, ReportSM-DeliveryStatusArg, ReportSM-DeliveryStatusRes, AlertServiceCentreArg, InformServiceCentreArg, ReadyForSM-Arg, ReadyForSM-Res FROM MAP-SM-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SM-DataTypes (16) version7 (7)}
; SendRoutingInfoForSM ::= OPERATION ARGUMENT routingInfoForSM-Arg RESULT routingInfoForSM-Res ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnknownSubscriber, TeleserviceNotProvisioned, CallBarred, AbsentSubscriberSM} MO-ForwardSM ::= OPERATION ARGUMENT mo-forwardSM-Arg RESULT mo-forwardSM-Res -- optional ERRORS { SystemFailure, UnexpectedDataValue, FacilityNotSupported, SM-DeliveryFailure} --Timer m RoutingInfoForSM-Arg RoutingInfoForSM-Res
--Timer ml MO-ForwardSM-Arg MO-ForwardSM-Res
1234
10640 10641 10642 10643 10644 10645 10646 10647 10648 10649 10650 10651 10652 10653 10654 10655 10656 10657 10658 10659 10660 10661 10662 10663 10664 10665 10666 10667 10668 10669 10670 10671 10672 10673 10674 10675 10676 10677 10678 10679 10680 10681 10682 10683 10684 10685 10686 10687 10688 10689 10690 10691 10692 10693 10694 10695
1235 Release 4 1236 1237
310
3GPP TS 29.002 V4.17.0 (2006-06)
--Timer ml
MT-ForwardSM ::= OPERATION ARGUMENT mt-forwardSM-Arg RESULT mt-forwardSM-Res -- optional ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnidentifiedSubscriber, IllegalSubscriber, IllegalEquipment, SubscriberBusyForMT-SMS, SM-DeliveryFailure, AbsentSubscriberSM} ReportSM-DeliveryStatus ::= OPERATION ARGUMENT reportSM-DeliveryStatusArg RESULT reportSM-DeliveryStatusRes -- optional ERRORS { DataMissing, UnexpectedDataValue, UnknownSubscriber, MessageWaitingListFull} AlertServiceCentre ::= OPERATION ARGUMENT alertServiceCentreArg RESULT ERRORS { SystemFailure, DataMissing, UnexpectedDataValue} InformServiceCentre ::= OPERATION ARGUMENT informServiceCentreArg ReadyForSM ::= OPERATION ARGUMENT readyForSM-Arg RESULT readyForSM-Res -- optional ERRORS { DataMissing, UnexpectedDataValue, FacilityNotSupported, UnknownSubscriber} END
MT-ForwardSM-Arg MT-ForwardSM-Res
--Timer s ReportSM-DeliveryStatusArg ReportSM-DeliveryStatusRes
--Timer s AlertServiceCentreArg
--Timer s InformServiceCentreArg --Timer m ReadyForSM-Arg ReadyForSM-Res
10696
10697 10698 10699 10700 10701 10702 10703 10704 10705 10706 10707 10708 10709 10710 10711 10712 10713 10714 10715
17.6.6 Errors
MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version7 (7)} DEFINITIONS ::= BEGIN EXPORTS -- generic errors SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, IncompatibleTerminal, ResourceLimitation,
1238
10716 10717 10718 10719 10720 10721 10722 10723 10724 10725 10726 10727 10728 10729 10730 10731 10732 10733 10734 10735 10736 10737 10738 10739 10740 10741 10742 10743 10744 10745 10746 10747 10748 10749 10750 10751 10752 10753 10754 10755 10756 10757 10758 10759 10760 10761 10762 10763 10764 10765 10766 10767 10768 10769 10770 10771 10772 10773 10774 10775 10776 10777 10778 10779 10780 10781 10782 10783 10784 10785 10786 10787 10788 10789 10790 10791 10792 10793 10794
1239 Release 4 1240 1241
-- identification and numbering errors UnknownSubscriber, NumberChanged, UnknownMSC, UnidentifiedSubscriber, UnknownEquipment, -- subscription errors RoamingNotAllowed, IllegalSubscriber, IllegalEquipment, BearerServiceNotProvisioned, TeleserviceNotProvisioned, -- handover errors NoHandoverNumberAvailable, SubsequentHandoverFailure, TargetCellOutsideGroupCallArea, -- operation and maintenance errors TracingBufferFull, -- call handling errors OR-NotAllowed, NoRoamingNumberAvailable, BusySubscriber, NoSubscriberReply, AbsentSubscriber, CallBarred, ForwardingViolation, ForwardingFailed, CUG-Reject, -- any time interrogation errors ATI-NotAllowed, -- any time information handling errors ATSI-NotAllowed, ATM-NotAllowed, InformationNotAvailable, -- supplementary service errors IllegalSS-Operation, SS-ErrorStatus, SS-NotAvailable, SS-SubscriptionViolation, SS-Incompatibility, UnknownAlphabet, USSD-Busy, PW-RegistrationFailure, NegativePW-Check, NumberOfPW-AttemptsViolation, ShortTermDenial, LongTermDenial, -- short message service errors SubscriberBusyForMT-SMS, SM-DeliveryFailure, MessageWaitingListFull, AbsentSubscriberSM, -- Group Call errors NoGroupCallNumberAvailable, -- location service errors UnauthorizedRequestingNetwork, UnauthorizedLCSClient, PositionMethodFailure, UnknownOrUnreachableLCSClient, -- Mobility Management errors MM-EventNotSupported ; IMPORTS ERROR
311
3GPP TS 29.002 V4.17.0 (2006-06)
1242
10795 10796 10797 10798 10799 10800 10801 10802 10803 10804 10805 10806 10807 10808 10809 10810 10811 10812 10813 10814 10815 10816 10817 10818 10819 10820 10821 10822 10823 10824 10825 10826 10827 10828 10829 10830 10831 10832 10833 10834 10835 10836 10837 10838 10839 10840 10841 10842 10843 10844 10845 10846 10847 10848 10849 10850 10851 10852 10853 10854 10855 10856 10857 10858 10859 10860 10861 10862 10863 10864 10865 10866 10867 10868 10869 10870 10871
1243 Release 4 1244 1245
312
3GPP TS 29.002 V4.17.0 (2006-06)
FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SS-Status FROM MAP-SS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version7 (7)} SS-IncompatibilityCause, PW-RegistrationFailureCause, SM-DeliveryFailureCause, SystemFailureParam, DataMissingParam, UnexpectedDataParam, FacilityNotSupParam, UnknownSubscriberParam, NumberChangedParam, UnidentifiedSubParam, RoamingNotAllowedParam, IllegalSubscriberParam, IllegalEquipmentParam, BearerServNotProvParam, TeleservNotProvParam, TracingBufferFullParam, NoRoamingNbParam, OR-NotAllowedParam, AbsentSubscriberParam, BusySubscriberParam, NoSubscriberReplyParam, CallBarredParam, ForwardingViolationParam, ForwardingFailedParam, CUG-RejectParam, ATI-NotAllowedParam, SubBusyForMT-SMS-Param, MessageWaitListFullParam, AbsentSubscriberSM-Param, ResourceLimitationParam, NoGroupCallNbParam, IncompatibleTerminalParam, ShortTermDenialParam, LongTermDenialParam, UnauthorizedRequestingNetwork-Param, UnauthorizedLCSClient-Param, PositionMethodFailure-Param, UnknownOrUnreachableLCSClient-Param, MM-EventNotSupported-Param, ATSI-NotAllowedParam, ATM-NotAllowedParam, IllegalSS-OperationParam, SS-NotAvailableParam, SS-SubscriptionViolationParam, InformationNotAvailableParam, TargetCellOutsideGCA-Param
FROM MAP-ER-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ER-DataTypes (17) version7 (7)} ; -- generic errors SystemFailure ::= ERROR PARAMETER systemFailureParam -- optional
SystemFailureParam
DataMissing ::= ERROR PARAMETER dataMissingParam DataMissingParam -- optional -- dataMissingParam must not be used in version <3
1246
10872 10873 10874 10875 10876 10877 10878 10879 10880 10881 10882 10883 10884 10885 10886 10887 10888 10889 10890 10891 10892 10893 10894 10895 10896 10897 10898 10899 10900 10901 10902 10903 10904 10905 10906 10907 10908 10909 10910 10911 10912 10913 10914 10915 10916 10917 10918 10919 10920 10921 10922 10923 10924 10925 10926 10927 10928 10929 10930 10931 10932 10933 10934 10935 10936 10937 10938 10939 10940 10941 10942 10943 10944 10945 10946 10947 10948
1247 Release 4 1248 1249
313
3GPP TS 29.002 V4.17.0 (2006-06)
UnexpectedDataValue ::= ERROR PARAMETER unexpectedDataParam UnexpectedDataParam -- optional -- unexpectedDataParam must not be used in version <3 FacilityNotSupported ::= ERROR PARAMETER facilityNotSupParam FacilityNotSupParam -- optional -- facilityNotSupParam must not be used in version <3 IncompatibleTerminal ::= ERROR PARAMETER incompatibleTerminalParam -- optional ResourceLimitation ::= ERROR PARAMETER resourceLimitationParam -- optional -- identification and numbering errors UnknownSubscriber ::= ERROR PARAMETER unknownSubscriberParam UnknownSubscriberParam -- optional -- unknownSubscriberParam must not be used in version <3 NumberChanged ::= ERROR PARAMETER numberChangedParam -- optional UnknownMSC ::= ERROR UnidentifiedSubscriber ::= ERROR PARAMETER unidentifiedSubParam UnidentifiedSubParam -- optional -- unidentifiedSubParam must not be used in version <3 UnknownEquipment ::= ERROR -- subscription errors RoamingNotAllowed ::= ERROR PARAMETER roamingNotAllowedParam
IncompatibleTerminalParam
ResourceLimitationParam
NumberChangedParam
RoamingNotAllowedParam
IllegalSubscriber ::= ERROR PARAMETER illegalSubscriberParam IllegalSubscriberParam -- optional -- illegalSubscriberParam must not be used in version <3 IllegalEquipment ::= ERROR PARAMETER illegalEquipmentParam IllegalEquipmentParam -- optional -- illegalEquipmentParam must not be used in version <3 BearerServiceNotProvisioned ::= ERROR PARAMETER bearerServNotProvParam BearerServNotProvParam -- optional -- bearerServNotProvParam must not be used in version <3 TeleserviceNotProvisioned ::= ERROR PARAMETER teleservNotProvParam TeleservNotProvParam -- optional -- teleservNotProvParam must not be used in version <3
1250
10949 10950 10951 10952 10953 10954 10955 10956 10957 10958 10959 10960 10961 10962 10963 10964 10965 10966 10967 10968 10969 10970 10971 10972 10973 10974 10975 10976 10977 10978 10979 10980 10981 10982 10983 10984 10985 10986 10987 10988 10989 10990 10991 10992 10993 10994 10995 10996 10997 10998 10999 11000 11001 11002 11003 11004 11005 11006 11007 11008 11009 11010 11011 11012 11013 11014 11015 11016 11017 11018 11019 11020 11021 11022 11023 11024
1251 Release 4 1252 1253
314
3GPP TS 29.002 V4.17.0 (2006-06)
-- handover errors NoHandoverNumberAvailable ::= ERROR SubsequentHandoverFailure ::= ERROR TargetCellOutsideGroupCallArea ::= ERROR PARAMETER targetCellOutsideGCA-Param TargetCellOutsideGCA-Param -- optional -- operation and maintenance errors TracingBufferFull ::= ERROR PARAMETER tracingBufferFullParam -- optional -- call handling errors NoRoamingNumberAvailable ::= ERROR PARAMETER noRoamingNbParam -- optional
TracingBufferFullParam
NoRoamingNbParam
AbsentSubscriber ::= ERROR PARAMETER absentSubscriberParam AbsentSubscriberParam -- optional -- absentSubscriberParam must not be used in version <3 BusySubscriber ::= ERROR PARAMETER busySubscriberParam -- optional NoSubscriberReply ::= ERROR PARAMETER noSubscriberReplyParam -- optional CallBarred ::= ERROR PARAMETER callBarredParam -- optional ForwardingViolation ::= ERROR PARAMETER forwardingViolationParam -- optional ForwardingFailed ::= ERROR PARAMETER forwardingFailedParam -- optional CUG-Reject ::= ERROR PARAMETER cug-RejectParam -- optional OR-NotAllowed ::= ERROR PARAMETER or-NotAllowedParam -- optional -- any time interrogation errors ATI-NotAllowed ::= ERROR PARAMETER ati-NotAllowedParam -- optional
BusySubscriberParam
NoSubscriberReplyParam
CallBarredParam
ForwardingViolationParam
ForwardingFailedParam
CUG-RejectParam
OR-NotAllowedParam
ATI-NotAllowedParam
1254
11025 11026 11027 11028 11029 11030 11031 11032 11033 11034 11035 11036 11037 11038 11039 11040 11041 11042 11043 11044 11045 11046 11047 11048 11049 11050 11051 11052 11053 11054 11055 11056 11057 11058 11059 11060 11061 11062 11063 11064 11065 11066 11067 11068 11069 11070 11071 11072 11073 11074 11075 11076 11077 11078 11079 11080 11081 11082 11083 11084 11085 11086 11087 11088 11089 11090 11091 11092 11093 11094 11095 11096 11097 11098 11099 11100 11101
1255 Release 4 1256 1257
315
3GPP TS 29.002 V4.17.0 (2006-06)
-- any time information handling errors ATSI-NotAllowed ::= ERROR PARAMETER atsi-NotAllowedParam -- optional ATM-NotAllowed ::= ERROR PARAMETER atm-NotAllowedParam -- optional InformationNotAvailable ::= ERROR PARAMETER informationNotAvailableParam -- optional -- supplementary service errors
ATSI-NotAllowedParam
ATM-NotAllowedParam
InformationNotAvailableParam
IllegalSS-Operation ::= ERROR PARAMETER illegalSS-OperationParam IllegalSS-OperationParam -- optional -- illegalSS-OperationParam must not be used in version <3 SS-ErrorStatus ::= ERROR PARAMETER ss-Status -- optional
SS-Status
SS-NotAvailable ::= ERROR PARAMETER ss-NotAvailableParam SS-NotAvailableParam -- optional -- ss-NotAvailableParam must not be used in version <3 SS-SubscriptionViolation ::= ERROR PARAMETER ss-SubscriptionViolationParam SS-SubscriptionViolationParam -- optional -- ss-NotAvailableParam must not be used in version <3 SS-Incompatibility ::= ERROR PARAMETER ss-IncompatibilityCause -- optional UnknownAlphabet ::= ERROR USSD-Busy ::= ERROR PW-RegistrationFailure ::= ERROR PARAMETER pw-RegistrationFailureCause NegativePW-Check ::= ERROR NumberOfPW-AttemptsViolation ::= ERROR ShortTermDenial ::= ERROR PARAMETER shortTermDenialParam -- optional LongTermDenial ::= ERROR PARAMETER longTermDenialParam -- optional -- short message service errors SubscriberBusyForMT-SMS ::= ERROR PARAMETER subBusyForMT-SMS-Param -- optional
SS-IncompatibilityCause
PW-RegistrationFailureCause
ShortTermDenialParam
LongTermDenialParam
SubBusyForMT-SMS-Param
1258
11102 11103 11104 11105 11106 11107 11108 11109 11110 11111 11112 11113 11114 11115 11116 11117 11118 11119 11120 11121 11122 11123 11124 11125 11126 11127 11128 11129 11130 11131 11132 11133 11134 11135 11136 11137 11138 11139 11140 11141 11142 11143 11144 11145 11146 11147 11148 11149 11150 11151 11152
1259 Release 4 1260 1261
316
3GPP TS 29.002 V4.17.0 (2006-06)
SM-DeliveryFailure ::= ERROR PARAMETER sm-DeliveryFailureCause MessageWaitingListFull ::= ERROR PARAMETER messageWaitListFullParam -- optional AbsentSubscriberSM ::= ERROR PARAMETER absentSubscriberSM-Param -- optional -- Group Call errors NoGroupCallNumberAvailable ::= ERROR PARAMETER noGroupCallNbParam -- optional -- location service errors
SM-DeliveryFailureCause
MessageWaitListFullParam
AbsentSubscriberSM-Param
NoGroupCallNbParam
UnauthorizedRequestingNetwork ::= ERROR PARAMETER unauthorizedRequestingNetwork-Param UnauthorizedRequestingNetwork-Param -- optional UnauthorizedLCSClient ::= ERROR PARAMETER unauthorizedLCSClient-Param -- optional PositionMethodFailure ::= ERROR PARAMETER positionMethodFailure-Param -- optional
UnauthorizedLCSClient-Param
PositionMethodFailure-Param
UnknownOrUnreachableLCSClient ::= ERROR PARAMETER unknownOrUnreachableLCSClient-Param -- optional
UnknownOrUnreachableLCSClient-Param
MM-EventNotSupported ::= ERROR
PARAMETER mm-EventNotSupported-Param -- optional
MM-EventNotSupported-Param
END
11153
11154 11155 11156 11157 11158 11159 11160 11161 11162 11163 11164 11165 11166 11167 11168 11169 11170 11171 11172 11173 11174 11175 11176
17.6.7 Group Call operations
MAP-Group-Call-Operations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Group-Call-Operations (22) version7 (7)} DEFINITIONS ::= BEGIN EXPORTS PrepareGroupCall, SendGroupCallEndSignal, ForwardGroupCallSignalling, ProcessGroupCallSignalling ; IMPORTS OPERATION FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)}
1262
11177 11178 11179 11180 11181 11182 11183 11184 11185 11186 11187 11188 11189 11190 11191 11192 11193 11194 11195 11196 11197 11198 11199 11200 11201 11202 11203 11204 11205 11206 11207 11208 11209 11210 11211 11212 11213 11214 11215 11216 11217 11218 11219 11220 11221 11222 11223 11224
1263 Release 4 1264 1265
317
3GPP TS 29.002 V4.17.0 (2006-06)
SystemFailure, UnexpectedDataValue, NoGroupCallNumberAvailable FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version7 (7)} PrepareGroupCallArg, PrepareGroupCallRes, SendGroupCallEndSignalArg, SendGroupCallEndSignalRes, ForwardGroupCallSignallingArg, ProcessGroupCallSignallingArg FROM MAP-GR-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-GR-DataTypes (23) version7 (7)}
; PrepareGroupCall ::= OPERATION ARGUMENT prepareGroupCallArg RESULT prepareGroupCallRes ERRORS { SystemFailure, NoGroupCallNumberAvailable, UnexpectedDataValue} SendGroupCallEndSignal ::= OPERATION ARGUMENT sendGroupCallEndSignalArg RESULT sendGroupCallEndSignalRes --Timer m PrepareGroupCallArg PrepareGroupCallRes
--Timer l SendGroupCallEndSignalArg SendGroupCallEndSignalRes --Timer s
ProcessGroupCallSignalling ::= OPERATION ARGUMENT processGroupCallSignallingArg ProcessGroupCallSignallingArg ForwardGroupCallSignalling ::= OPERATION ARGUMENT forwardGroupCallSignallingArg ForwardGroupCallSignallingArg END
--Timer s
17.6.8 Location service operations
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
MAP-LocationServiceOperations { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-LocationServiceOperations (24) version7 (7)} DEFINITIONS ::= BEGIN EXPORTS ProvideSubscriberLocation, SendRoutingInfoForLCS, SubscriberLocationReport ;
1266
1267 Release 4 1268 1269
18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83
318
3GPP TS 29.002 V4.17.0 (2006-06)
IMPORTS OPERATION FROM TCAPMessages { ccitt recommendation q 773 modules (2) messages (1) version2 (2)} SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnknownSubscriber, AbsentSubscriber, UnauthorizedRequestingNetwork, UnauthorizedLCSClient, PositionMethodFailure, ResourceLimitation, UnknownOrUnreachableLCSClient, UnidentifiedSubscriber, IllegalEquipment, IllegalSubscriber FROM MAP-Errors { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Errors (10) version7 (7)} RoutingInfoForLCS-Arg, RoutingInfoForLCS-Res, ProvideSubscriberLocation-Arg, ProvideSubscriberLocation-Res, SubscriberLocationReport-Arg, SubscriberLocationReport-Res FROM MAP-LCS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-LCS-DataTypes (25) version7 (7)} ; SendRoutingInfoForLCS ::= OPERATION ARGUMENT routingInfoForLCS-Arg RoutingInfoForLCS-Arg RESULT routingInfoForLCS-Res RoutingInfoForLCS-Res ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnknownSubscriber, AbsentSubscriber, UnauthorizedRequestingNetwork } --Timer m
ProvideSubscriberLocation ::= OPERATION
ARGUMENT provideSubscriberLocation-Arg RESULT provideSubscriberLocation-Res ERRORS { SystemFailure, DataMissing, UnexpectedDataValue, FacilityNotSupported, UnidentifiedSubscriber, IllegalSubscriber, IllegalEquipment, AbsentSubscriber, UnauthorizedRequestingNetwork, UnauthorizedLCSClient, PositionMethodFailure } ProvideSubscriberLocation-Arg ProvideSubscriberLocation-Res
--Timer ml
1270
1271 Release 4 1272 1273
84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100
319
3GPP TS 29.002 V4.17.0 (2006-06)
--Timer m
SubscriberLocationReport ::= OPERATION ARGUMENT subscriberLocationReport-Arg RESULT subscriberLocationReport-Res ERRORS { SystemFailure, DataMissing, ResourceLimitation, UnexpectedDataValue, UnknownSubscriber, UnauthorizedRequestingNetwork, UnknownOrUnreachableLCSClient} END
SubscriberLocationReport-Arg SubscriberLocationReport-Res
17.6.9 void
101
102 103
104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151
17.7 MAP constants and data types
17.7.1 Mobile Service data types
MAP-MS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MS-DataTypes (11) version7 (7)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS -- location registration types UpdateLocationArg, UpdateLocationRes, CancelLocationArg, CancelLocationRes, PurgeMS-Arg, PurgeMS-Res, SendIdentificationArg, SendIdentificationRes, UpdateGprsLocationArg, UpdateGprsLocationRes, IST-SupportIndicator, SupportedLCS-CapabilitySets, -- gprs location registration types GSN-Address, -- handover types ForwardAccessSignalling-Arg, PrepareHO-Arg, PrepareHO-Res, PrepareSubsequentHO-Arg, PrepareSubsequentHO-Res, ProcessAccessSignalling-Arg, SendEndSignal-Arg, SendEndSignal-Res, -- authentication management types SendAuthenticationInfoArg, SendAuthenticationInfoRes, AuthenticationFailureReportArg, AuthenticationFailureReportRes,
1274
1275 Release 4 1276 1277
152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230
320
3GPP TS 29.002 V4.17.0 (2006-06)
-- security management types EquipmentStatus, Kc, -- subscriber management types InsertSubscriberDataArg, InsertSubscriberDataRes, LSAIdentity, DeleteSubscriberDataArg, DeleteSubscriberDataRes, Ext-QoS-Subscribed, SubscriberData, ODB-Data, SubscriberStatus, ZoneCodeList, maxNumOfZoneCodes, O-CSI, D-CSI, O-BcsmCamelTDPCriteriaList, T-BCSM-CAMEL-TDP-CriteriaList, SS-CSI, ServiceKey, DefaultCallHandling, CamelCapabilityHandling, BasicServiceCriteria, SupportedCamelPhases, maxNumOfCamelTDPData, CUG-Index, CUG-Info, CUG-Interlock, InterCUG-Restrictions, IntraCUG-Options, NotificationToMSUser, QoS-Subscribed, IST-AlertTimerValue, T-CSI, T-BcsmTriggerDetectionPoint, APN, -- fault recovery types ResetArg, RestoreDataArg, RestoreDataRes,
-- provide subscriber info types GeographicalInformation, -- subscriber information enquiry types ProvideSubscriberInfoArg, ProvideSubscriberInfoRes, SubscriberInfo, LocationInformation, SubscriberState, -- any time information enquiry types AnyTimeInterrogationArg, AnyTimeInterrogationRes, -- any time information handling types AnyTimeSubscriptionInterrogationArg, AnyTimeSubscriptionInterrogationRes, AnyTimeModificationArg, AnyTimeModificationRes, -- subscriber data modification notification types NoteSubscriberDataModifiedArg, NoteSubscriberDataModifiedRes, -- gprs location information retrieval types SendRoutingInfoForGprsArg, SendRoutingInfoForGprsRes, -- failure reporting types FailureReportArg, FailureReportRes, -- gprs notification types NoteMsPresentForGprsArg,
1278
1279 Release 4 1280 1281
231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309
321
3GPP TS 29.002 V4.17.0 (2006-06)
NoteMsPresentForGprsRes, -- Mobility Management types NoteMM-EventArg, NoteMM-EventRes
; IMPORTS maxNumOfSS, SS-SubscriptionOption, SS-List, SS-ForBS-Code, Password FROM MAP-SS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version7 (7)}
FROM MAP-SS-Code {
SS-Code
ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version7 (7)}
FROM MAP-BS-Code {
Ext-BearerServiceCode ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-BS-Code (20) version7 (7)}
FROM MAP-TS-Code {
Ext-TeleserviceCode ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-TS-Code (19) version7 (7)}
AddressString, ISDN-AddressString, ISDN-SubaddressString, FTN-AddressString, AccessNetworkSignalInfo, IMSI, TMSI, HLR-List, LMSI, Identity, GlobalCellId, CellGlobalIdOrServiceAreaIdOrLAI, Ext-BasicServiceCode, NAEA-PreferredCI, EMLPP-Info, MC-SS-Info, SubscriberIdentity, AgeOfLocationInformation, LCSClientExternalID, LCSClientInternalID, Ext-SS-Status, ASCI-CallReference, TBCD-STRING
FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version7 (7)} ExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version7 (7)} AbsentSubscriberDiagnosticSM FROM MAP-ER-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ER-DataTypes (17) version7 (7)} ;
1282
1283 Release 4 1284 1285
310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384
322
3GPP TS 29.002 V4.17.0 (2006-06)
-- location registration types UpdateLocationArg ::= SEQUENCE { imsi msc-Number vlr-Number lmsi extensionContainer ... , vlr-Capability informPreviousNetworkEntity IMSI, [1] ISDN-AddressString, ISDN-AddressString, [10] LMSI OPTIONAL, ExtensionContainer [6] VLR-Capability [11] NULL
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 [0] NULL, [1] AgeIndicator }
SuperChargerInfo ::= CHOICE { sendSubscriberData subscriberDataStored
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) } (SIZE (2..16)) Core network signalling capability set1 indicates LCS Release98 or Release99 version. Core network signalling capability set2 indicates LCS Release4 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. ISDN-AddressString, ExtensionContainer OPTIONAL,
UpdateLocationRes ::= SEQUENCE { hlr-Number extensionContainer ... } CancelLocationArg ::= [3] SEQUENCE { identity cancellationType extensionContainer ...}
Identity, CancellationType ExtensionContainer
OPTIONAL, OPTIONAL,
CancellationType ::= ENUMERATED { updateProcedure (0), subscriptionWithdraw (1), ...} -- The HLR shall not send values other than listed above CancelLocationRes ::= SEQUENCE { extensionContainer ...}
ExtensionContainer
OPTIONAL,
1286
1287 Release 4 1288 1289
385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 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
323
3GPP TS 29.002 V4.17.0 (2006-06)
PurgeMS-Arg ::= [3] SEQUENCE { imsi vlr-Number sgsn-Number extensionContainer ...} PurgeMS-Res ::= SEQUENCE { freezeTMSI freezeP-TMSI extensionContainer ...}
IMSI, [0] ISDN-AddressString [1] ISDN-AddressString ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL,
[0] NULL [1] NULL ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL,
SendIdentificationArg ::= SEQUENCE { tmsi TMSI, numberOfRequestedVectors NumberOfRequestedVectors -- 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 extensionContainer ExtensionContainer ...}
OPTIONAL,
OPTIONAL, OPTIONAL,
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)) RAND, SRES, Kc,
RAND, XRES, CK, IK, AUTN,
[0] GSM-SecurityContextData, [1] UMTS-SecurityContextData } Kc, Cksn,
CK, IK, KSI,
1290
1291 Release 4 1292 1293
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 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
324
3GPP TS 29.002 V4.17.0 (2006-06)
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)) 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 ... , IMSI, ISDN-AddressString, GSN-Address, ExtensionContainer [0] SGSN-Capability [1] NULL OPTIONAL,
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }
OPTIONAL, OPTIONAL, OPTIONAL } OPTIONAL, OPTIONAL, OPTIONAL , OPTIONAL, OPTIONAL, OPTIONAL }
sgsn-Capability
informPreviousNetworkEntity
SGSN-Capability ::= SEQUENCE{
solsaSupportIndicator NULL extensionContainer [1] ExtensionContainer ... , superChargerSupportedInServingNetworkEntity [2] SuperChargerInfo gprsEnhancementsSupportIndicator [3] NULL supportedCamelPhases [4] SupportedCamelPhases supportedLCS-CapabilitySets [5] SupportedLCS-CapabilitySets
1294
1295 Release 4 1296 1297
537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 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
325
3GPP TS 29.002 V4.17.0 (2006-06)
GSN-Address ::= OCTET STRING (SIZE (5..17)) -- Octets are coded according to TS 3GPP TS 23.003 [17] UpdateGprsLocationRes ::= SEQUENCE { hlr-Number extensionContainer ...} -- handover types ISDN-AddressString, ExtensionContainer
OPTIONAL,
ForwardAccessSignalling-Arg ::= [3] SEQUENCE {
an-APDU integrityProtectionInfo encryptionInfo keyStatus allowedGSM-Algorithms allowedUMTS-Algorithms radioResourceInformation extensionContainer ..., radioResourceList bssmap-ServiceHandover ranap-ServiceHandover bssmap-ServiceHandoverList
AccessNetworkSignalInfo, [0] IntegrityProtectionInformation OPTIONAL, [1] EncryptionInformation OPTIONAL, [2] KeyStatus OPTIONAL, [4] AllowedGSM-Algorithms OPTIONAL, [5] AllowedUMTS-Algorithms OPTIONAL, [6] RadioResourceInformation OPTIONAL, [3] ExtensionContainer OPTIONAL, [7] [9] [8] [10] RadioResourceList BSSMAP-ServiceHandover RANAP-ServiceHandover BSSMAP-ServiceHandoverList OPTIONAL, OPTIONAL, OPTIONAL, 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"
1298
1299 Release 4 1300 1301
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 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
326
3GPP TS 29.002 V4.17.0 (2006-06)
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 }
[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] RAB-Id BSSMAP-ServiceHandover RANAP-ServiceHandover BSSMAP-ServiceHandoverList ASCI-CallReference 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,
PrepareHO-Res ::= [3] SEQUENCE { handoverNumber relocationNumberList an-APDU multicallBearerInfo multipleBearerNotSupported selectedUMTS-Algorithms chosenRadioResourceInformation extensionContainer ...} SelectedUMTS-Algorithms ::= SEQUENCE { integrityProtectionAlgorithm encryptionAlgorithm extensionContainer ...}
[0] [1] [2]
ChosenIntegrityProtectionAlgorithm OPTIONAL, ChosenEncryptionAlgorithm OPTIONAL, ExtensionContainer OPTIONAL,
1302
1303 Release 4 1304 1305
676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741
327
3GPP TS 29.002 V4.17.0 (2006-06)
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] GlobalCellId targetMSC-Number [1] ISDN-AddressString, targetRNCId [2] RNCId an-APDU [3] AccessNetworkSignalInfo selectedRab-Id [4] RAB-Id extensionContainer [5] ExtensionContainer ...} PrepareSubsequentHO-Res ::= [3] SEQUENCE { an-APDU AccessNetworkSignalInfo, extensionContainer [0] ExtensionContainer ...}
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
OPTIONAL,
ProcessAccessSignalling-Arg ::= [3] SEQUENCE {
an-APDU selectedUMTS-Algorithms selectedGSM-Algorithm chosenRadioResourceInformation selectedRab-Id extensionContainer ...}
AccessNetworkSignalInfo, [1] SelectedUMTS-Algorithms OPTIONAL, [2] SelectedGSM-Algorithm OPTIONAL, [3] ChosenRadioResourceInformation OPTIONAL, [4] RAB-Id OPTIONAL, [0] ExtensionContainer OPTIONAL,
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 ...} extensionContainer ...}
AccessNetworkSignalInfo, [0] ExtensionContainer
OPTIONAL,
SendEndSignal-Res ::= SEQUENCE {
[0]
ExtensionContainer
OPTIONAL,
1306
1307 Release 4 1308 1309
742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 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
328
3GPP TS 29.002 V4.17.0 (2006-06)
RNCId ::= OCTET STRING (SIZE (7)) -- The internal structure is defined as follows: st -- octet 1 bits 4321 Mobile Country Code 1 digit nd -bits 8765 Mobile Country Code 2 digit rd -- octet 2 bits 4321 Mobile Country Code 3 digit rd -bits 8765 Mobile Network Code 3 digit -or filler (1111) for 2 digit MNCs st -- octet 3 bits 4321 Mobile Network Code 1 digit nd -bits 8765 Mobile Network Code 2 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 SendAuthenticationInfoArg ::= SEQUENCE { imsi [0] IMSI, numberOfRequestedVectors NumberOfRequestedVectors, segmentationProhibited NULL immediateResponsePreferred [1] NULL re-synchronisationInfo Re-synchronisationInfo extensionContainer [2] ExtensionContainer ..., requestingNodeType [3] RequestingNodeType NumberOfRequestedVectors ::= INTEGER (1..5) Re-synchronisationInfo ::= SEQUENCE { rand auts ...} RAND, AUTS,
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL}
SendAuthenticationInfoRes ::= [3] SEQUENCE { authenticationSetList AuthenticationSetList extensionContainer ExtensionContainer ...}
OPTIONAL, OPTIONAL,
1310
1311 Release 4 1312 1313
819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 882 883 884 885 886 887 888 889 890 891 892 893
881
329
3GPP TS 29.002 V4.17.0 (2006-06)
RequestingNodeType ::= ENUMERATED { vlr (0), sgsn (1), ...} -- exception handling: -- received values in the range 2-15 shall be treated as "vlr" -- received values greater than 15 shall be treated as "sgsn" -- security management types EquipmentStatus ::= ENUMERATED { whiteListed (0), blackListed (1), greyListed (2)} -- subscriber management types InsertSubscriberDataArg ::= SEQUENCE { imsi [0] IMSI COMPONENTS OF SubscriberData, extensionContainer [14] ExtensionContainer ... , naea-PreferredCI [15] NAEA-PreferredCI -- naea-PreferredCI is included at the discretion of the HLR operator. gprsSubscriptionData [16] GPRSSubscriptionData roamingRestrictedInSgsnDueToUnsupportedFeature [23] networkAccessMode lsaInformation lmu-Indicator lcsInformation istAlertTimer superChargerSupportedInHLR mc-SS-Info cs-AllocationRetentionPriority sgsn-CAMEL-SubscriptionInfo chargingCharacteristics [24] [25] [21] [22] [26] [27] [28] [29] [17] [18] 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
-- If the Network Access Mode parameter is sent, it shall be present only in -- the first sequence if seqmentation is used
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] lcs-PrivacyExceptionList molr-List ...} GMLC-List OPTIONAL, [1] LCS-PrivacyExceptionList [2] MOLR-List
OPTIONAL, OPTIONAL,
GMLC-List ::= SEQUENCE SIZE (1..maxNumOfGMLC) OF
ISDN-AddressString -- if segmentation is used, the complete GMLC-List shall be sent in one segment INTEGER ::= 5
maxNumOfGMLC
NetworkAccessMode ::= ENUMERATED {
bothMSCAndSGSN onlyMSC onlySGSN ...} -- if unknown values are received in -- they shall be discarded.
(0), (1), (2), NetworkAccessMode
GPRSDataList ::= SEQUENCE SIZE (1..maxNumOfPDP-Contexts) OF PDP-Context maxNumOfPDP-Contexts INTEGER ::= 50
1314
1315 Release 4 1316 1317
894 895 896 897 898 899 900 901 902 903 904 905 906 907 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
330
3GPP TS 29.002 V4.17.0 (2006-06)
PDP-Context ::= SEQUENCE { pdp-ContextId pdp-Type pdp-Address qos-Subscribed vplmnAddressAllowed apn extensionContainer ... , ext-QoS-Subscribed pdp-ChargingCharacteristics -- qos-Subscribed shall be discarded
ContextId, [16] PDP-Type, [17] PDP-Address [18] QoS-Subscribed, [19] NULL OPTIONAL, [20] APN, [21] ExtensionContainer
OPTIONAL,
OPTIONAL,
[0] Ext-QoS-Subscribed OPTIONAL, [1] ChargingCharacteristics OPTIONAL } if ext-QoS-Subscribed is received and supported
ContextId ::= INTEGER (1..maxNumOfPDP-Contexts) GPRSSubscriptionData ::= SEQUENCE { completeDataListIncluded
908
NULL
OPTIONAL,
-- If segmentation is used, completeDataListIncluded may only be present in the -- first segment. gprsDataList [1] GPRSDataList, extensionContainer [2] ExtensionContainer OPTIONAL, ... }
SGSN-CAMEL-SubscriptionInfo ::= SEQUENCE {
gprs-CSI sms-CSI extensionContainer ...} [0] [1] [2]
GPRS-CSI SMS-CSI ExtensionContainer
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-CamelTDPData GPRS-CamelTDPDataList shall not contain more than one instance of GPRS-CamelTDPData containing the same value for gprs-TriggerDetectionPoint. gprs-TriggerDetectionPoint serviceKey gsmSCF-Address defaultSessionHandling extensionContainer ... } [0] [1] [2] [3] [4] GPRS-TriggerDetectionPoint, ServiceKey, ISDN-AddressString, DefaultGPRS-Handling, ExtensionContainer
GPRS-CamelTDPDataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF
--
--
GPRS-CamelTDPData ::= SEQUENCE {
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"
1318
1319 Release 4 1320 1321 960 GPRS-TriggerDetectionPoint ::= ENUMERATED {
961 962 963 964 965 966 967 968 969 970
331
3GPP TS 29.002 V4.17.0 (2006-06)
-----
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.
971
972 973
APN ::= OCTET STRING (SIZE (2..63)) -- Octets are coded according to TS 3GPP TS 23.003 [17]
974
975 976
PDP-Type ::= OCTET STRING (SIZE (2)) -- Octets are coded according to TS 3GPP TS 29.060 [105]
977
978 979 980 981 982 983 984
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
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 1023 1024 1025 1026 1027 1028 1029 1030 1031
QoS-Subscribed ::= OCTET STRING (SIZE (3)) -- Octets are coded according to TS 3GPP TS 24.008 [35]. 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 Quality of Service Octets -- 6-13. ChargingCharacteristics ::= OCTET STRING (SIZE (2)) -- Octets are coded according to 3GPP TS 32.015. 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]
1322
1323 Release 4 1324 1325
1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109
332
3GPP TS 29.002 V4.17.0 (2006-06)
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 CCITT 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.
1326
1327 Release 4 1328 1329
1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1122 1123
1124
1125 1126 1127 1128 1129
333
3GPP TS 29.002 V4.17.0 (2006-06)
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.
1121
Ext-SS-InfoList ::= SEQUENCE SIZE (1..maxNumOfSS) OF
Ext-SS-Info [0] [1] [2] [3] [4]
Ext-SS-Info ::= CHOICE {
forwardingInfo callBarringInfo cug-Info ss-Data emlpp-Info
1130 1131
1132
1133 1134 1135 1136
Ext-ForwInfo, Ext-CallBarInfo, CUG-Info, Ext-SS-Data, EMLPP-Info}
1137
1138
Ext-ForwInfo ::= SEQUENCE { ss-Code forwardingFeatureList extensionContainer ...}
SS-Code, Ext-ForwFeatureList, [0] ExtensionContainer
OPTIONAL,
1140
1141
1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153
1139
Ext-ForwFeatureList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF
Ext-ForwFeature
Ext-ForwFeature ::= SEQUENCE {
1154
1155
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
1156
1157 1159 1160 1161 1163 1164 1165 1167 1168 1169 1171 1173 1174 1175 1176 1177 1179 1181 1182
1158
1162
1166
1170 1172
1178 1180 1183
1184
1185 1186 1187 1188 1189
-- bits 21: 00 (unused) -- OCTETS 2-5: reserved for future use. They shall be discarded if -- received and not understood.
Ext-NoRepCondTime ::= INTEGER (1..100)
1190
1191
1192 1193 1194 1195
-- 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 ss-Code callBarringFeatureList extensionContainer ...} SS-Code, Ext-CallBarFeatureList, ExtensionContainer
Ext-CallBarInfo ::= SEQUENCE {
OPTIONAL,
1196
1197
1199
1198
Ext-CallBarFeatureList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF
Ext-CallBarringFeature
1330
1331 Release 4 1332 1333 1200 Ext-CallBarringFeature ::= SEQUENCE {
1201 1202 1203 1204
334
3GPP TS 29.002 V4.17.0 (2006-06)
1205
1206
1207 1208 1209 1210
basicService ss-Status extensionContainer ...}
Ext-BasicServiceCode [4] Ext-SS-Status, ExtensionContainer
OPTIONAL, OPTIONAL,
CUG-Info ::= SEQUENCE {
1211 1213 1214
1215
1216 1217 1218 1219 1220 1221
cug-SubscriptionList cug-FeatureList extensionContainer ...}
CUG-SubscriptionList, CUG-FeatureList [0] ExtensionContainer
OPTIONAL, OPTIONAL,
1212
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,
1222 1224 1225 1227
1228
1229 1230 1231
1223
CUG-Index ::= INTEGER (0..32767)
-- The internal structure is defined in ETS 300 138.
1226
CUG-Interlock ::= OCTET STRING (SIZE (4)) IntraCUG-Options ::= ENUMERATED {
noCUG-Restrictions (0), cugIC-CallBarred (1), cugOG-CallBarred (2)} INTEGER ::= 10 CUG-Feature
1232 1234 1236 1237 1238 1239 1240 1242
1243
1244 1245 1246 1247 1248
1233 1235
maxNumOfCUG
CUG-FeatureList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF
Ext-BasicServiceGroupList ::= SEQUENCE SIZE (1..maxNumOfExt-BasicServiceGroups) OF Ext-BasicServiceCode
1241
maxNumOfExt-BasicServiceGroups CUG-Feature ::= SEQUENCE {
basicService preferentialCUG-Indicator interCUG-Restrictions extensionContainer ...}
INTEGER ::= 32 Ext-BasicServiceCode CUG-Index OPTIONAL, InterCUG-Restrictions, ExtensionContainer OPTIONAL, OPTIONAL,
1249 1251 1253 1254 1255
1256 1257 1258 1259 1260 1252
1250
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,
1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273
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
1334
1335 Release 4 1336 1337
1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 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
335
3GPP TS 29.002 V4.17.0 (2006-06)
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. -- 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, ... } 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. 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,
1338
1339 Release 4 1340 1341
1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 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
336
3GPP TS 29.002 V4.17.0 (2006-06)
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,
InsertSubscriberDataRes ::= SEQUENCE { teleserviceList bearerServiceList ss-List odb-GeneralData regionalSubscriptionResponse supportedCamelPhases extensionContainer ...}
RegionalSubscriptionResponse ::= ENUMERATED { networkNode-AreaRestricted (0), tooManyZoneCodes (1), zoneCodesConflict (2), regionalSubscNotSupported (3)} DeleteSubscriberDataArg ::= SEQUENCE { imsi [0] IMSI, basicServiceList [1] BasicServiceList -- The exception handling for reception of unsupported/not allocated -- basicServiceCodes is defined in section 6.8.2 ss-List [2] SS-List roamingRestrictionDueToUnsupportedFeature [4] NULL regionalSubscriptionIdentifier [5] ZoneCode vbsGroupIndication [7] NULL vgcsGroupIndication [8] NULL OPTIONAL, camelSubscriptionInfoWithdraw [9] NULL OPTIONAL, extensionContainer [6] ExtensionContainer OPTIONAL, ..., gprsSubscriptionDataWithdraw [10] GPRSSubscriptionDataWithdraw roamingRestrictedInSgsnDueToUnsuppportedFeature [11] NULL lsaInformationWithdraw [12] LSAInformationWithdraw gmlc-ListWithdraw [13] NULL istInformationWithdraw [14] NULL specificCSI-Withdraw [15] SpecificCSI-Withdraw chargingCharacteristicsWithdraw [16] NULL SpecificCSI-Withdraw ::= BIT STRING { o-csi (0), ss-csi (1), tif-csi (2), d-csi (3), vt-csi (4), sms-csi (5), m-csi (6), gprs-csi(7) , t-csi (8)} (SIZE(8..32)) -- exception handling: -- bits 9 to 31 shall be ignored if received. -- Bit 8 is 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 }
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }
LSAIdentityList ::= SEQUENCE SIZE (1..maxNumOfLSAs) OF LSAIdentity BasicServiceList ::= SEQUENCE SIZE (1..maxNumOfBasicServices) OF Ext-BasicServiceCode maxNumOfBasicServices INTEGER ::= 70
1342
1343 Release 4 1344 1345
1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 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
337
3GPP TS 29.002 V4.17.0 (2006-06)
DeleteSubscriberDataRes ::= SEQUENCE { regionalSubscriptionResponse extensionContainer ...} o-CSI extensionContainer ..., ss-CSI o-BcsmCamelTDP-CriteriaList tif-CSI m-CSI sms-CSI vt-CSI t-BCSM-CAMEL-TDP-CriteriaList d-CSI
[0] RegionalSubscriptionResponse ExtensionContainer
OPTIONAL, OPTIONAL,
VlrCamelSubscriptionInfo ::= SEQUENCE {
[0] O-CSI [1] ExtensionContainer [2] [4] [3] [5] [6] [7] [8] [9] SS-CSI O-BcsmCamelTDPCriteriaList NULL M-CSI SMS-CSI T-CSI T-BCSM-CAMEL-TDP-CriteriaList D-CSI
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL}
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, dp-AnalysedInfoCriteriaList and camelCapabilityHandling shall be present in the first segment ::= SEQUENCE SIZE (1..maxNumOfDP-AnalysedInfoCriteria) OF DP-AnalysedInfoCriterium
DP-AnalysedInfoCriteriaList
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. ::= SEQUENCE { ss-EventList gsmSCF-Address extensionContainer ...} ----------
SS-CamelData
SS-EventList, ISDN-AddressString, [0] ExtensionContainer
OPTIONAL,
SS-EventList
::= SEQUENCE SIZE (1..maxNumOfCamelSSEvents) OF SS-Code Actions for the following SS-Code values are defined in CAMEL Phase 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
1346
1347 Release 4 1348 1349 1504 O-CSI ::= SEQUENCE {
1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 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
338
3GPP TS 29.002 V4.17.0 (2006-06)
----
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-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. INTEGER ::= 10 O-BcsmTriggerDetectionPoint, ServiceKey, [0] ISDN-AddressString, [1] DefaultCallHandling, [2] ExtensionContainer
O-BcsmCamelTDPDataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF
maxNumOfCamelTDPData
O-BcsmCamelTDPData ::= SEQUENCE {
o-BcsmTriggerDetectionPoint serviceKey gsmSCF-Address defaultCallHandling extensionContainer ... }
OPTIONAL,
ServiceKey ::= INTEGER (0..2147483647) 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 T-BcsmTriggerDetectionPoint, [0] BasicServiceCriteria [1] T-CauseValueCriteria
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }
T-BCSM-CAMEL-TDP-Criteria ::= SEQUENCE {
t-BCSM-TriggerDetectionPoint basicServiceCriteria t-CauseValueCriteria ... }
OPTIONAL, OPTIONAL,
DestinationNumberCriteria
::= SEQUENCE { matchType [0] MatchType, destinationNumberList [1] DestinationNumberList OPTIONAL, destinationNumberLengthList [2] DestinationNumberLengthList OPTIONAL, -- one or both of destinationNumberList and destinationNumberLengthList -- shall be present ...} ::= SEQUENCE SIZE (1..maxNumOfCamelDestinationNumbers) OF ISDN-AddressString -- The receiving entity shall not check the format of a number in -- the dialled number list
DestinationNumberList
1350
1351 Release 4 1352 1353 1581 DestinationNumberLengthList
1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 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
339
3GPP TS 29.002 V4.17.0 (2006-06)
OF
::= SEQUENCE SIZE (1..maxNumOfCamelDestinationNumberLengths) INTEGER(1..maxNumOfISDN-AddressDigits)
BasicServiceCriteria
Ext-BasicServiceCode
::= SEQUENCE SIZE(1..maxNumOfCamelBasicServiceCriteria) OF INTEGER ::= 15 INTEGER ::= 10 INTEGER ::= 3
maxNumOfISDN-AddressDigits
maxNumOfCamelDestinationNumbers
maxNumOfCamelDestinationNumberLengths maxNumOfCamelBasicServiceCriteria
INTEGER ::= 5 (0), (1)} (0), (1)}
CallTypeCriteria
forwarded notForwarded inhibiting enabling CauseValue CauseValue
::= ENUMERATED {
MatchType
::= ENUMERATED {
O-CauseValueCriteria T-CauseValueCriteria
::= 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" ----value 1 = value 2 = value 3 = reception CAMEL phase 1, CAMEL phase 2, CAMEL Phase 3: of values greater than 3 shall be treated as CAMEL phase 3.
CamelCapabilityHandling ::= INTEGER(1..16)
SupportedCamelPhases ::= BIT STRING {
phase1 (0), phase2 (1) , phase3 (2) } (SIZE (1..16)) -- A node shall mark in the BIT STRING all CAMEL Phases it supports. -- 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 SMS-CSI is sent to VLR/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
1354
1355 Release 4 340 3GPP TS 29.002 V4.17.0 (2006-06) 1356 1357 1654 SMS-CAMEL-TDP-DataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF
1655 1656 1657 1658 1659 1660 1661 1662 1663 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 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
--
--
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-TriggerDetectionPoint serviceKey gsmSCF-Address defaultSMS-Handling extensionContainer ... } [0] [1] [2] [3] [4] SMS-TriggerDetectionPoint, ServiceKey, ISDN-AddressString, DefaultSMS-Handling, ExtensionContainer
SMS-CAMEL-TDP-Data ::= SEQUENCE {
OPTIONAL,
SMS-TriggerDetectionPoint ::= ENUMERATED {
-----
sms-CollectedInfo (1), ... } exception handling: For SMS-CAMEL-TDP-Data sequences containing this parameter with any other value than the ones listed the receiver shall ignore the whole SMS-CAMEL-TDP-Data sequence. 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" 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. MM-Code ::= SEQUENCE SIZE (1..maxNumOfMobilityTriggers) OF
DefaultSMS-Handling ::= ENUMERATED {
----
M-CSI ::= SEQUENCE {
---
MobilityTriggers
maxNumOfMobilityTriggers INTEGER ::= 10
MM-Code ::= OCTET STRING (SIZE (1)) -This type is used to indicate a Mobility Management event. -Actions for the following M-Code values are defined in CAMEL Phase 3: --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 --If any other MM-code is received in M-CSI, then that MM-code shall be -ignored.
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.
1358
1359 Release 4 341 3GPP TS 29.002 V4.17.0 (2006-06) 1360 1361 1725 T-BcsmCamelTDPDataList ::= SEQUENCE SIZE (1..maxNumOfCamelTDPData) OF
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 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
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,
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 ...} ggsn-Address extensionContainer ...}
[0] [1] [2] [3]
IMSI, ISDN-AddressString GSN-Address ExtensionContainer
, OPTIONAL, OPTIONAL,
FailureReportRes ::= SEQUENCE {
[0] GSN-Address [1] ExtensionContainer
OPTIONAL, OPTIONAL,
-- gprs notification types
NoteMsPresentForGprsArg ::= SEQUENCE {
imsi sgsn-Address ggsn-Address extensionContainer ...} extensionContainer ...}
[0] [1] [2] [3]
IMSI, GSN-Address, GSN-Address ExtensionContainer
OPTIONAL, OPTIONAL,
NoteMsPresentForGprsRes ::= SEQUENCE {
[0] ExtensionContainer
OPTIONAL,
-- fault recovery types
1362
1363 Release 4 1364 1365
1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 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 1870 1871 1872 1873 1874
342
3GPP TS 29.002 V4.17.0 (2006-06)
ResetArg ::= SEQUENCE { hlr-Number hlr-List ...} RestoreDataArg ::= SEQUENCE { imsi lmsi extensionContainer ... , vlr-Capability RestoreDataRes ::= SEQUENCE { hlr-Number msNotReachable extensionContainer ...}
ISDN-AddressString, HLR-List
OPTIONAL,
IMSI, LMSI ExtensionContainer [6] VLR-Capability ISDN-AddressString, NULL ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL }
OPTIONAL, OPTIONAL,
-- VBS/VGCS types VBSDataList ::= SEQUENCE SIZE (1..maxNumOfVBSGroupIds) OF VoiceBroadcastData VGCSDataList ::= SEQUENCE SIZE (1..maxNumOfVGCSGroupIds) OF VoiceGroupCallData maxNumOfVBSGroupIds maxNumOfVGCSGroupIds INTEGER ::= 50 INTEGER ::= 50 GroupId, ExtensionContainer
VoiceGroupCallData ::= SEQUENCE { groupId extensionContainer ...} VoiceBroadcastData ::= SEQUENCE { groupid broadcastInitEntitlement extensionContainer ...} GroupId -----
OPTIONAL,
GroupId, NULL ExtensionContainer
OPTIONAL, OPTIONAL,
::= TBCD-STRING (SIZE (3)) When Group-Id is less than six characters in length, the TBCD filler (1111) is used to fill unused half octets. Refers to the Group Identification as specified in 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 ...} subscriberInfo extensionContainer ...} OPTIONAL, [2] RequestedInfo, [3] ExtensionContainer
OPTIONAL,
ProvideSubscriberInfoRes ::= SEQUENCE {
SubscriberInfo, ExtensionContainer
OPTIONAL,
SubscriberInfo ::= SEQUENCE {
locationInformation subscriberState extensionContainer ...}
[0] LocationInformation [1] SubscriberState [2] ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL,
RequestedInfo ::= SEQUENCE {
locationInformation [0] NULL subscriberState [1] NULL extensionContainer [2] ExtensionContainer ..., currentLocation [3] NULL -- currentLocation shall not be present if locationInformation -- is not present in the RequestedInfo parameter
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }
1366
1367 Release 4 1368 1369 1875 LocationInformation ::= SEQUENCE {
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
343
3GPP TS 29.002 V4.17.0 (2006-06)
-----------------------
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. 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 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 -- the internal structure is defined in CCITT Rec Q.763 assumedIdle camelBusy [1] NULL, netDetNotReachable notProvidedFromVLR [0] NULL, NotReachableReason, [2] NULL}
GeographicalInformation ::= OCTET STRING (SIZE (8))
1 3 3 1
octet octets octets octet
GeodeticInformation ::= OCTET STRING (SIZE (10))
1 1 3 3 1 1
octet octet octets octets octet octet
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
LocationNumber ::= OCTET STRING (SIZE (2..10)) SubscriberState ::= CHOICE {
NotReachableReason ::= ENUMERATED {
msPurged (0), imsiDetached (1), restrictedArea (2), notRegistered (3)}
-- any time interrogation info types
AnyTimeInterrogationArg ::= SEQUENCE {
subscriberIdentity requestedInfo gsmSCF-Address extensionContainer ...} subscriberInfo extensionContainer ...}
[0] [1] [3] [2]
SubscriberIdentity, RequestedInfo, ISDN-AddressString, ExtensionContainer
OPTIONAL,
AnyTimeInterrogationRes ::= SEQUENCE {
SubscriberInfo, ExtensionContainer
OPTIONAL,
-- any time information handling types
1370
1371 Release 4 344 1372 1373 1936 AnyTimeSubscriptionInterrogationArg ::= SEQUENCE {
1937 1938 1939 1940 1941 1942 1943 1944 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 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013
1981
3GPP TS 29.002 V4.17.0 (2006-06)
subscriberIdentity requestedSubscriptionInfo gsmSCF-Address extensionContainer longFTN-Supported ...}
[0] [1] [2] [3] [4]
SubscriberIdentity, RequestedSubscriptionInfo, ISDN-AddressString, ExtensionContainer NULL
OPTIONAL, OPTIONAL,
AnyTimeSubscriptionInterrogationRes ::= SEQUENCE {
callForwardingData callBarringData odb-Info camel-SubscriptionInfo supportedVLR-CAMEL-Phases supportedSGSN-CAMEL-Phases extensionContainer ...} [1] [2] [3] [4] [5] [6] [7]
CallForwardingData CallBarringData ODB-Info CAMEL-SubscriptionInfo SupportedCamelPhases SupportedCamelPhases ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
RequestedSubscriptionInfo ::= SEQUENCE {
requestedSS-Info odb requestedCAMEL-SubscriptionInfo supportedVLR-CAMEL-Phases supportedSGSN-CAMEL-Phases extensionContainer ...} o-CSI t-CSI vt-CSI tif-CSI gprs-CSI sms-CSI ss-CSI m-CSI d-csi
[1] [2] [3] [4] [5] [6]
SS-ForBS-Code OPTIONAL, NULL OPTIONAL, RequestedCAMEL-SubscriptionInfo OPTIONAL, NULL OPTIONAL, NULL OPTIONAL, ExtensionContainer OPTIONAL,
RequestedCAMEL-SubscriptionInfo ::= ENUMERATED {
(0), (1), (2), (3), (4), (5), (6), (7), (8)}
CallForwardingData ::= SEQUENCE {
forwardingFeatureList notificationToCSE extensionContainer ...}
Ext-ForwFeatureList, NULL [0] ExtensionContainer
OPTIONAL, OPTIONAL,
CallBarringData ::= SEQUENCE {
callBarringFeatureList password wrongPasswordAttemptsCounter notificationToCSE extensionContainer ...}
Ext-CallBarFeatureList, Password WrongPasswordAttemptsCounter NULL ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
WrongPasswordAttemptsCounter ::= INTEGER (0..4)
ODB-Info ::= SEQUENCE {
odb-Data notificationToCSE extensionContainer ...}
ODB-Data, NULL ExtensionContainer
OPTIONAL, OPTIONAL,
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 sms-CSI ss-CSI m-CSI extensionContainer ..., specificCSIDeletedList
[0] [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13]
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
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }
[14] SpecificCSI-Withdraw
1374
1375 Release 4 1376 1377 2014 AnyTimeModificationArg ::= SEQUENCE {
2015 2016 2017 2018 2019 2020 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
345
3GPP TS 29.002 V4.17.0 (2006-06)
subscriberIdentity gsmSCF-Address modificationRequestFor-CF-Info modificationRequestFor-CB-Info modificationRequestFor-CSI extensionContainer longFTN-Supported ...} ss-InfoFor-CSE camel-SubscriptionInfo extensionContainer ...}
[0] [1] [2] [3] [4] [5] [6]
SubscriberIdentity, ISDN-AddressString, ModificationRequestFor-CF-Info OPTIONAL, ModificationRequestFor-CB-Info OPTIONAL, ModificationRequestFor-CSI OPTIONAL, ExtensionContainer OPTIONAL, NULL OPTIONAL,
AnyTimeModificationRes ::= SEQUENCE {
[0] [1] [2]
Ext-SS-InfoFor-CSE CAMEL-SubscriptionInfo ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL,
ModificationRequestFor-CF-Info ::= SEQUENCE {
ss-Code basicService ss-Status forwardedToNumber forwardedToSubaddress noReplyConditionTime modifyNotificationToCSE extensionContainer ...} [0] [1] [2] [3] [4] [5] [6] [7]
SS-Code, Ext-BasicServiceCode Ext-SS-Status AddressString ISDN-SubaddressString Ext-NoRepCondTime ModificationInstruction ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
ModificationRequestFor-CB-Info ::= SEQUENCE {
ss-Code basicService ss-Status password wrongPasswordAttemptsCounter modifyNotificationToCSE extensionContainer ...} [0] [1] [2] [3] [4] [5] [6]
SS-Code, Ext-BasicServiceCode Ext-SS-Status Password WrongPasswordAttemptsCounter ModificationInstruction ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
ModificationRequestFor-CSI ::= SEQUENCE {
requestedCamel-SubscriptionInfo modifyNotificationToCSE modifyCSI-State extensionContainer ...}
[0] [1] [2] [3]
RequestedCAMEL-SubscriptionInfo, ModificationInstruction OPTIONAL, ModificationInstruction OPTIONAL, ExtensionContainer OPTIONAL,
ModificationInstruction ::= ENUMERATED { deactivate (0), activate (1)} -- subscriber data modification notification types
NoteSubscriberDataModifiedArg ::= SEQUENCE {
imsi msisdn forwardingInfoFor-CSE callBarringInfoFor-CSE odb-Info camel-SubscriptionInfo allInformationSent extensionContainer ...} extensionContainer ...}
IMSI, ISDN-AddressString, [0] Ext-ForwardingInfoFor-CSE [1] Ext-CallBarringInfoFor-CSE [2] ODB-Info [3] CAMEL-SubscriptionInfo [4] NULL ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
NoteSubscriberDataModifiedRes ::= SEQUENCE {
ExtensionContainer
OPTIONAL,
-- mobility management event notificatioon info types
1378
1379 Release 4 1380 1381 2082 NoteMM-EventArg::= SEQUENCE {
2083 2084 2085 2086 2087 2088 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 2114 2115 2116 2117
346
3GPP TS 29.002 V4.17.0 (2006-06)
serviceKey eventMet imsi msisdn locationInformation supportedCAMELPhases extensionContainer ...} extensionContainer ...}
ServiceKey, [0] MM-Code, [1] IMSI, [2] ISDN-AddressString, [3] LocationInformation [5] SupportedCamelPhases [6] ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL,
NoteMM-EventRes ::= SEQUENCE {
ExtensionContainer
OPTIONAL,
Ext-SS-InfoFor-CSE ::= CHOICE { forwardingInfoFor-CSE callBarringInfoFor-CSE }
[0] Ext-ForwardingInfoFor-CSE, [1] Ext-CallBarringInfoFor-CSE
Ext-ForwardingInfoFor-CSE ::= SEQUENCE { ss-Code [0] forwardingFeatureList [1] notificationToCSE [2] extensionContainer [3] ...} Ext-CallBarringInfoFor-CSE ::= SEQUENCE { ss-Code [0] callBarringFeatureList [1] password [2] wrongPasswordAttemptsCounter [3] notificationToCSE [4] extensionContainer [5] ...} END
SS-Code, Ext-ForwFeatureList, NULL ExtensionContainer
OPTIONAL, OPTIONAL,
SS-Code, Ext-CallBarFeatureList, Password WrongPasswordAttemptsCounter NULL ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
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
17.7.2 Operation and maintenance data types
MAP-OM-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-OM-DataTypes (12) version7 (7)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS ActivateTraceModeArg, ActivateTraceModeRes, DeactivateTraceModeArg, DeactivateTraceModeRes ; IMPORTS AddressString, IMSI FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version7 (7)} ExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version7 (7)} ;
1382
1383 Release 4 1384 1385
2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182
347
3GPP TS 29.002 V4.17.0 (2006-06)
ActivateTraceModeArg ::= SEQUENCE { imsi traceReference traceType omc-Id extensionContainer ...}
[0] [1] [2] [3] [4]
IMSI TraceReference, TraceType, AddressString ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL,
TraceReference ::= OCTET STRING (SIZE (1..2)) TraceType ::= INTEGER (0..255) -- Trace types are fully defined in TS GSM 12.08. ActivateTraceModeRes ::= SEQUENCE { extensionContainer ...} DeactivateTraceModeArg ::= SEQUENCE { imsi traceReference extensionContainer ...} DeactivateTraceModeRes ::= SEQUENCE { extensionContainer ...} END [0] ExtensionContainer OPTIONAL,
[0] IMSI [1] TraceReference, [2] ExtensionContainer
OPTIONAL, OPTIONAL,
[0] ExtensionContainer
OPTIONAL,
2183
2184 2185 2186 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
17.7.3 Call handling data types
MAP-CH-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CH-DataTypes (13) version7 (7)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS SendRoutingInfoArg, SendRoutingInfoRes, ProvideRoamingNumberArg, ProvideRoamingNumberRes, ResumeCallHandlingArg, ResumeCallHandlingRes, NumberOfForwarding, SuppressionOfAnnouncement, CallReferenceNumber, ProvideSIWFSNumberArg, ProvideSIWFSNumberRes, SIWFSSignallingModifyArg, SIWFSSignallingModifyRes, SetReportingStateArg, SetReportingStateRes, StatusReportArg, StatusReportRes, RemoteUserFreeArg, RemoteUserFreeRes, IST-AlertArg, IST-AlertRes, IST-CommandArg, IST-CommandRes ; IMPORTS SubscriberInfo, SupportedCamelPhases, CUG-Interlock, O-CSI, D-CSI, O-BcsmCamelTDPCriteriaList,
1386
1387 Release 4 1388 1389
2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 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
348
3GPP TS 29.002 V4.17.0 (2006-06)
T-BCSM-CAMEL-TDP-CriteriaList, IST-SupportIndicator, IST-AlertTimerValue, T-CSI
FROM MAP-MS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MS-DataTypes (11) version7 (7)} ForwardingOptions, SS-List, CCBS-Feature FROM MAP-SS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version7 (7)} ISDN-AddressString, ISDN-SubaddressString, FTN-AddressString, ExternalSignalInfo, Ext-ExternalSignalInfo, IMSI, LMSI, Ext-BasicServiceCode, AlertingPattern, NAEA-PreferredCI FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version7 (7)} ExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version7 (7)} ; CUG-CheckInfo ::= SEQUENCE { cug-Interlock cug-OutgoingAccess extensionContainer ...} NumberOfForwarding ::= INTEGER (1..5) SendRoutingInfoArg ::= SEQUENCE { msisdn cug-CheckInfo numberOfForwarding interrogationType or-Interrogation or-Capability gmsc-Address callReferenceNumber forwardingReason basicServiceGroup networkSignalInfo camelInfo suppressionOfAnnouncement extensionContainer ..., alertingPattern ccbs-Call supportedCCBS-Phase additionalSignalInfo istSupportIndicator pre-pagingSupported callDiversionTreatmentIndicator longFTN-Supported [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]
CUG-Interlock, NULL ExtensionContainer
OPTIONAL, OPTIONAL,
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 }
SuppressionOfAnnouncement ::= NULL
1390
1391 Release 4 1392 1393 2304 InterrogationType ::= ENUMERATED {
2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 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
349
3GPP TS 29.002 V4.17.0 (2006-06)
basicCall (0), forwarding (1)}
OR-Phase ::= INTEGER (1..127) CallReferenceNumber ::= OCTET STRING (SIZE (1..8)) ForwardingReason ::= ENUMERATED {
notReachable (0), busy (1), noReply (2)}
SupportedCCBS-Phase ::= INTEGER (1..127) -- exception handling: -- Only value 1 is used. -- Values in the ranges 2-127 are reserved for future use. -- If received values 2-127 shall be mapped on to value 1.
CallDiversionTreatmentIndicator ::= OCTET STRING (SIZE(1)) -- callDiversionAllowed (xxxx xx01) -- callDiversionNotAllowed (xxxx xx10) -- network default is call diversion allowed
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 } OPTIONAL,
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL
NumberPortabilityStatus ::= ENUMERATED { notKnownToBePorted (0), ownNumberPortedOut (1), foreignNumberPortedToForeignNetwork (2), ...} -exception handling: -- reception of other values than the ones listed the receiver shall ignore the -- whole NumberPortabilityStatus 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}
1394
1395 Release 4 1396 1397
2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414 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
350
3GPP TS 29.002 V4.17.0 (2006-06)
ProvideRoamingNumberArg ::= SEQUENCE { imsi msc-Number msisdn lmsi gsm-BearerCapability networkSignalInfo suppressionOfAnnouncement gmsc-Address callReferenceNumber or-Interrogation extensionContainer ... , alertingPattern ccbs-Call supportedCamelPhasesInGMSC additionalSignalInfo orNotSupportedInGMSC pre-pagingSupported longFTN-Supported ProvideRoamingNumberRes ::= SEQUENCE { roamingNumber extensionContainer ...} ResumeCallHandlingArg ::= SEQUENCE { callReferenceNumber basicServiceGroup forwardingData imsi cug-CheckInfo o-CSI extensionContainer ccbs-Possible msisdn uu-Data allInformationSent ..., d-csi
[0] IMSI, [1] ISDN-AddressString, [2] ISDN-AddressString [4] LMSI [5] ExternalSignalInfo [6] ExternalSignalInfo [7] SuppressionOfAnnouncement [8] ISDN-AddressString [9] CallReferenceNumber [10] NULL [11] ExtensionContainer [12] [13] [15] [14] [16] [17] [18] AlertingPattern NULL SupportedCamelPhases Ext-ExternalSignalInfo NULL NULL NULL
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }
ISDN-AddressString, ExtensionContainer
OPTIONAL,
[0] CallReferenceNumber [1] Ext-BasicServiceCode [2] ForwardingData [3] IMSI [4] CUG-CheckInfo [5] O-CSI [7] ExtensionContainer [8] NULL [9] ISDN-AddressString [10] UU-Data [11] NULL [12] D-CSI [0] [1] [2] [3] UUIndicator UUI NULL ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL} OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
UU-Data ::= SEQUENCE {
uuIndicator uui uusCFInteraction extensionContainer ...}
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 ...} routingInfo camelRoutingInfo
SupportedCamelPhases, NULL ExtensionContainer
OPTIONAL, OPTIONAL,
ExtendedRoutingInfo ::= CHOICE {
RoutingInfo, [8] CamelRoutingInfo} ForwardingData [0] GmscCamelSubscriptionInfo, [1] ExtensionContainer OPTIONAL, OPTIONAL,
CamelRoutingInfo ::= SEQUENCE {
forwardingData gmscCamelSubscriptionInfo extensionContainer ...}
1398
1399 Release 4 1400 1401 2455 GmscCamelSubscriptionInfo ::= SEQUENCE {
2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 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 2511 2512 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527
351
3GPP TS 29.002 V4.17.0 (2006-06)
t-CSI o-CSI extensionContainer ..., o-BcsmCamelTDP-CriteriaList t-BCSM-CAMEL-TDP-CriteriaList d-csi
[0] T-CSI OPTIONAL, [1] O-CSI OPTIONAL, [2] ExtensionContainer
OPTIONAL,
[3] O-BcsmCamelTDPCriteriaList OPTIONAL, [4] T-BCSM-CAMEL-TDP-CriteriaList OPTIONAL, [5] D-CSI OPTIONAL} [0] [1] [2] [3] [4] [5] [6] [7] ExternalSignalInfo, ExternalSignalInfo, CallDirection, ISDN-AddressString, ExternalSignalInfo, ExternalSignalInfo ExternalSignalInfo ExtensionContainer
ProvideSIWFSNumberArg ::= SEQUENCE { gsm-BearerCapability isdn-BearerCapability call-Direction b-Subscriber-Address chosenChannel lowerLayerCompatibility highLayerCompatibility extensionContainer ...} CallDirection ::= OCTET STRING (SIZE (1)) -- OCTET 1 -- bit 1 (direction of call) -- 0 Mobile Originated Call (MOC) -- 1 Mobile Terminated Call (MTC) ProvideSIWFSNumberRes ::= SEQUENCE { sIWFSNumber extensionContainer ...} SIWFSSignallingModifyArg ::= SEQUENCE { channelType chosenChannel extensionContainer ...} SIWFSSignallingModifyRes ::= SEQUENCE { chosenChannel extensionContainer ...} 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 ...}
OPTIONAL, OPTIONAL, OPTIONAL,
[0] ISDN-AddressString, [1] ExtensionContainer
OPTIONAL,
[0] ExternalSignalInfo [1] ExternalSignalInfo [2] ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL,
[0] ExternalSignalInfo [1] ExtensionContainer
OPTIONAL, OPTIONAL,
[0] [1] [2] [3]
IMSI LMSI ReportingState ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
(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'
1402
1403 Release 4 1404 1405
2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 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
352
3GPP TS 29.002 V4.17.0 (2006-06)
StatusReportArg ::= SEQUENCE{ imsi eventReportData callReportdata extensionContainer ...} EventReportData ::= SEQUENCE{ ccbs-SubscriberStatus extensionContainer ...} CallReportData ::= SEQUENCE{ monitoringMode callOutcome extensionContainer ...}
[0] [1] [2] [3]
IMSI, EventReportData CallReportData ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL,
[0] [1]
CCBS-SubscriberStatus ExtensionContainer
OPTIONAL, OPTIONAL,
[0] [1] [2]
MonitoringMode CallOutcome ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL,
MonitoringMode ::= ENUMERATED { a-side (0), b-side (1), ...} -exception handling: -- reception of values 2-10 shall be mapped 'a-side' -- reception of values > 10 shall be mapped to 'b-side' CallOutcome ::= ENUMERATED { success (0), failure (1), busy (2), ...} -exception handling: -- reception of values 3-10 shall be mapped to 'success' -- reception of values 11-20 shall be mapped to 'failure' -- reception of values > 20 shall be mapped to 'busy' 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 ...} [0] [1] IMSI, ExtensionContainer
OPTIONAL,
1406
1407 Release 4 1408 1409
2604 2605 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630 2631
353
3GPP TS 29.002 V4.17.0 (2006-06)
IST-AlertRes ::= SEQUENCE{ istAlertTimer istInformationWithdraw callTerminationIndicator extensionContainer ...} IST-CommandArg ::= SEQUENCE{ imsi extensionContainer ...} IST-CommandRes ::= SEQUENCE{ extensionContainer ...}
[0] [1] [2] [3]
IST-AlertTimerValue NULL CallTerminationIndicator ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
[0] [1]
IMSI, ExtensionContainer
OPTIONAL,
ExtensionContainer
OPTIONAL,
CallTerminationIndicator ::= ENUMERATED { terminateCallActivityReferred (0), terminateAllCallActivities (1), ...} -- exception handling: -- reception of values 2-10 shall be mapped to ' terminateCallActivityReferred ' -- reception of values > 10 shall be mapped to ' terminateAllCallActivities ' -- In MSCs not supporting linkage of all call activities, any value received shall -- be interpreted as ' terminateCallActivityReferred ' END
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
17.7.4 Supplementary service data types
MAP-SS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version7 (7)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS RegisterSS-Arg, SS-Info, SS-Status, SS-SubscriptionOption, SS-ForBS-Code, InterrogateSS-Res, USSD-Arg, USSD-Res, USSD-DataCodingScheme, USSD-String, Password, GuidanceInfo, SS-List, SS-InfoList, OverrideCategory, CliRestrictionOption, NoReplyConditionTime, ForwardingOptions, maxNumOfSS, SS-Data, CCBS-Feature, RegisterCC-EntryArg, RegisterCC-EntryRes, EraseCC-EntryArg, EraseCC-EntryRes
SS-InvocationNotificationArg, SS-InvocationNotificationRes,
IMPORTS AddressString, ISDN-AddressString, ISDN-SubaddressString, FTN-AddressString,
1410
1411 Release 4 1412 1413
2680 2681 2682 2683 2684 2685 2686 2687 2688 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 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
354
3GPP TS 29.002 V4.17.0 (2006-06)
IMSI, BasicServiceCode, AlertingPattern, EMLPP-Priority, MaxMC-Bearers, MC-Bearers, ExternalSignalInfo
FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version7 (7)} ExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version7 (7)} SS-Code FROM MAP-SS-Code { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version7 (7)} ; 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 }
1414
1415 Release 4 1416 1417
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 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 2814 2815 2816 2817 2818 2819 2820 2821 2822 2823 2824 2825 2826 2827 2828 2829 2830 2831 2832
355
3GPP TS 29.002 V4.17.0 (2006-06)
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 }
1418
1419 Release 4 1420 1421
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 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
356
3GPP TS 29.002 V4.17.0 (2006-06)
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
1422
1423 Release 4 1424 1425 2901 SS-InvocationNotificationArg ::= SEQUENCE {
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 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
357
3GPP TS 29.002 V4.17.0 (2006-06)
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 }
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL
CCBS-RequestState ::= ENUMERATED { request (0), recall (1), active (2), completed (3), suspended (4), frozen (5), deleted (6) }
SS-InvocationNotificationRes ::= SEQUENCE {
extensionContainer ... }
ExtensionContainer
OPTIONAL,
SS-EventSpecification ::= SEQUENCE SIZE (1..maxEventSpecification) OF AddressString maxEventSpecification INTEGER ::= 2 [0] [1] SS-Code, CCBS-Data
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,
2971
2972 2973 2974 2975
17.7.5 Supplementary service codes
MAP-SS-Code { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version7 (7)}
1426
1427 Release 4 1428 1429
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 3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037 3038 3039 3040 3041 3042
358
3GPP TS 29.002 V4.17.0 (2006-06)
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
1430
1431 Release 4 1432 1433
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 3090 3091 3092 3093 3094 3095 3096 3097 3098 3099 3100 3101 3102 3103 3104 3105 3106
359
3GPP TS 29.002 V4.17.0 (2006-06)
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 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
1434
1435 Release 4 1436 1437
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
360
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 V4.17.0 (2006-06)
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 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
3153
3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 3181 3182
17.7.6 Short message data types
MAP-SM-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SM-DataTypes (16) version7 (7)} 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, Additional-Number ;
1438
1439 Release 4 1440 1441
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 3243 3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259
361
3GPP TS 29.002 V4.17.0 (2006-06)
IMPORTS AddressString, ISDN-AddressString, SignalInfo, IMSI, LMSI FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version7 (7)} AbsentSubscriberDiagnosticSM FROM MAP-ER-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ER-DataTypes (17) version7 (7)} ExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version7 (7)} ; 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.140. 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 }
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }
IMSI, [0] LocationInfoWithLMSI, [4] ExtensionContainer
OPTIONAL,
[1] ISDN-AddressString, LMSI ExtensionContainer [5] NULL the SGSN number is sent as the [6] Additional-Number msc-number or sgsn-number
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL
Additional-Number ::= CHOICE { msc-Number [0] ISDN-AddressString, sgsn-Number [1] ISDN-AddressString} -- additional-number can be either msc-number or sgsn-number -- if received networkNode-number is msc-number then the -- additional number is sgsn-number -- if received networkNode-number is sgsn-number then the -- additional number is msc-number
1442
1443 Release 4 1444 1445
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 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
362
3GPP TS 29.002 V4.17.0 (2006-06)
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)} ReportSM-DeliveryStatusRes ::= SEQUENCE { storedMSISDN ISDN-AddressString extensionContainer ExtensionContainer ...} AlertServiceCentreArg ::= SEQUENCE { msisdn serviceCentreAddress ...} OPTIONAL, OPTIONAL,
ISDN-AddressString, AddressString,
1446
1447 Release 4 1448 1449
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
363
3GPP TS 29.002 V4.17.0 (2006-06)
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)} END ExtensionContainer
OPTIONAL, OPTIONAL,
OPTIONAL,
3375
3376 3377 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
17.7.7 Error data types
MAP-ER-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ER-DataTypes (17) version7 (7)} 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,
1450
1451 Release 4 1452 1453
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 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
364
3GPP TS 29.002 V4.17.0 (2006-06)
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
; IMPORTS SS-Status FROM MAP-SS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version7 (7)} SignalInfo, BasicServiceCode, NetworkResource FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version7 (7)}
SS-Code FROM MAP-SS-Code { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version7 (7)} ExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version7 (7)} ; RoamingNotAllowedParam ::= SEQUENCE { roamingNotAllowedCause extensionContainer ...} 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)} RoamingNotAllowedCause, ExtensionContainer
OPTIONAL,
1454
1455 Release 4 1456 1457
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 3516 3517 3518 3519 3520 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
365
3GPP TS 29.002 V4.17.0 (2006-06)
ExtensibleCallBarredParam ::= SEQUENCE { callBarringCause CallBarringCause extensionContainer ExtensionContainer ... , unauthorisedMessageOriginator [1] NULL CUG-RejectParam ::= SEQUENCE { cug-RejectCause extensionContainer ...} 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)} 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 ETS 300 536 (3GPP TS 23.140) 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 ...} DataMissingParam ::= SEQUENCE { extensionContainer ...} ExtensionContainer OPTIONAL, OPTIONAL,
OPTIONAL,
1458
1459 Release 4 1460 1461
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 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
366
3GPP TS 29.002 V4.17.0 (2006-06)
UnexpectedDataParam ::= SEQUENCE { extensionContainer ...}
ExtensionContainer
OPTIONAL,
FacilityNotSupParam ::= SEQUENCE { extensionContainer ExtensionContainer ..., shapeOfLocationEstimateNotSupported [0] NULL OR-NotAllowedParam ::= SEQUENCE { extensionContainer ...} UnknownSubscriberParam ::= SEQUENCE { extensionContainer ..., unknownSubscriberDiagnostic ExtensionContainer
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 ...} 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
OPTIONAL,
ExtensionContainer
OPTIONAL,
ExtensionContainer
OPTIONAL,
ExtensionContainer [0] AbsentSubscriberReason
OPTIONAL, OPTIONAL}
1462
1463 Release 4 1464 1465
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 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 3700
367
3GPP TS 29.002 V4.17.0 (2006-06)
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,
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 ...} ExtensionContainer
OPTIONAL,
OPTIONAL,
OPTIONAL, OPTIONAL }
OPTIONAL,
ExtensionContainer
OPTIONAL,
1466
1467 Release 4 1468 1469
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 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
368
3GPP TS 29.002 V4.17.0 (2006-06)
NoGroupCallNbParam ::= SEQUENCE { extensionContainer ...}
ExtensionContainer
OPTIONAL,
IncompatibleTerminalParam ::= SEQUENCE { extensionContainer ExtensionContainer ...} ShortTermDenialParam ::= SEQUENCE { ...} LongTermDenialParam ::= SEQUENCE { ...} UnauthorizedRequestingNetwork-Param ::= SEQUENCE { extensionContainer 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), ... } -exception handling: -any unrecognized value shall be ignored PositionMethodFailure-Param ::= SEQUENCE { positionMethodFailure-Diagnostic [0] PositionMethodFailure-Diagnostic extensionContainer [1] ExtensionContainer ... } 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 ...}
OPTIONAL, OPTIONAL,
OPTIONAL, OPTIONAL,
OPTIONAL,
OPTIONAL,
OPTIONAL,
END
3769
3770 3771 3772 3773 3774 3775
17.7.8 Common data types
MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version7 (7)} DEFINITIONS
1470
1471 Release 4 1472 1473
3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 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
369
3GPP TS 29.002 V4.17.0 (2006-06)
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, NAEA-PreferredCI, NAEA-CIC, ASCI-CallReference, SubscriberIdentity, -- data types for CAMEL CellGlobalIdOrServiceAreaIdOrLAI, -- 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
IMPORTS TeleserviceCode, Ext-TeleserviceCode FROM MAP-TS-Code { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-TS-Code (19) version7 (7)} BearerServiceCode, Ext-BearerServiceCode FROM MAP-BS-Code { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-BS-Code (20) version7 (7)} SS-Code FROM MAP-SS-Code { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-Code (15) version7 (7)} ExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version7 (7)} ;
1474
1475 Release 4 1476 1477
3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 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
370
3GPP TS 29.002 V4.17.0 (2006-06)
-- 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 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 CCITT E.164) -0010 spare -0011 data numbering plan (CCITT Rec X.121) -0100 telex numbering plan (CCITT Rec F.69) -0101 spare -0110 land mobile numbering plan (CCITT 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
1478
1479 Release 4 1480 1481
3927 3928 3929 3930 3931 3932 3933 3934 3935 3936 3937 3938 3939 3940 3941 3942 3943 3944 3945 3946 3947 3948 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
371
3GPP TS 29.002 V4.17.0 (2006-06)
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 CCITT 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,
1482
1483 Release 4 1484 1485
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 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
372
3GPP TS 29.002 V4.17.0 (2006-06)
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) )
-------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
-- This type is used to represent Alerting Pattern
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}
1486
1487 Release 4 1488 1489
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 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
373
3GPP TS 29.002 V4.17.0 (2006-06)
IMSI-WithLMSI ::= SEQUENCE { imsi IMSI, lmsi LMSI, -- a special value 00000000 indicates that the LMSI is not in use ...} 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)}
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. [0] IMSI, [1] ISDN-AddressString
SubscriberIdentity ::= CHOICE {
imsi msisdn }
1490
1491 Release 4 1492 1493
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 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 4215
374
3GPP TS 29.002 V4.17.0 (2006-06)
LCSClientExternalID ::= SEQUENCE { externalAddress extensionContainer ... }
[0] 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 -- data types for CAMEL 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 [2] BearerServiceCode, [3] TeleserviceCode} [2] Ext-BearerServiceCode, [3] Ext-TeleserviceCode} EMLPP-Priority, EMLPP-Priority, ExtensionContainer
Ext-BasicServiceCode ::= CHOICE {
ext-BearerService ext-Teleservice
4214 4216 4217 4218 4219 4220
4221 4222 4223 4224 4225 4226 4227
EMLPP-Info ::= SEQUENCE { maximumentitledPriority defaultPriority 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 EMLPP-Priority EMLPP-Priority EMLPP-Priority EMLPP-Priority EMLPP-Priority EMLPP-Priority EMLPP-Priority ::= ::= ::= ::= ::= ::= ::= 6 5 0 1 2 3 4
4228 4229
1494
1495 Release 4 1496 1497
4230 4231 4232 4233 4234 4235 4236
375
3GPP TS 29.002 V4.17.0 (2006-06)
4237 4238 4239 4240 4241 4242 4243 4244
4245
MC-SS-Info ::= SEQUENCE { ss-Code ss-Status nbrSB nbrUser extensionContainer ...}
[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
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.
4246
4247 4248 4249 4250 4251 4252 4254 4256 4258 4260 4262 4263
4253 4255 4257 4259 4261 4264 4265 4266 4267 4268 4269 4270 4271 4272 4273 4274 4275 4276 4277 4278
-- 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
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
17.7.9 Teleservice Codes
MAP-TS-Code { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-TS-Code (19) version7 (7)} 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 teleservice, services are The internal
used to represent the code identifying a single a group of teleservices, or all teleservices. The defined in TS GSM 22.003 [4]. structure is defined as follows:
-- OCTET 1: -- bits 87654321: group (bits 8765) and specific service -- (bits 4321) -- OCTETS 2-5: reserved for future use. If received the
1498
1499 Release 4 1500 1501
4310 4311 4312 4313 4314 4315 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 4348 4349 4350 4351 4352 4353 4354 4355 4356 4357 4358 4359 4360 4361 4362 4363 4364 4365 4366 4367
376
3GPP TS 29.002 V4.17.0 (2006-06)
-- Ext-TeleserviceCode shall be -- treated according to the exception handling defined for the -- operation that uses this type. -- Ext-TeleserviceCode includes all values defined for TeleserviceCode.
allTeleservices allSpeechTransmissionServices telephony emergencyCalls allShortMessageServices shortMessageMT-PP shortMessageMO-PP allFacsimileTransmissionServices facsimileGroup3AndAlterSpeech automaticFacsimileGroup3 facsimileGroup4
TeleserviceCode ::= '00000000'B 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
4368
4369 4370 4371 4372 4373 4374 4375 4376 4377 4378
17.7.10 Bearer Service Codes
MAP-BS-Code { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-BS-Code (20) version7 (7)} DEFINITIONS ::= BEGIN
1502
1503 Release 4 1504 1505
4379 4380 4381 4382 4383 4384 4385 4386 4387 4388 4389 4390 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 4453 4454 4455
377
3GPP TS 29.002 V4.17.0 (2006-06)
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) 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) future use. If received the be exception handling defined for the type.
Ext-BearerServiceCode ::= OCTET STRING (SIZE (1..5))
-- OCTETS 2-5: reserved for -- Ext-TeleserviceCode shall -- treated according to the -- operation that uses this
-- 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 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
1506
1507 Release 4 1508 1509
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
378
3GPP TS 29.002 V4.17.0 (2006-06)
allSpeechFollowedByDataCDS
BearerServiceCode ::= '01001000'B
-- 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 END 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
4496
4497 4498 4499 4500 4501 4502 4503 4504 4505 4506 4507 4508 4509 4510 4511 4512 4513 4514 4515 4516 4517 4518 4519 4520 4521 4522 4523 4524 4525 4526 4527 4528
17.7.11 Extension data types
MAP-ExtensionDataTypes {
ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version7 (7)}
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
1510
1511 Release 4 1512 1513 4529 ExtensionContainer ::= SEQUENCE {
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
379
3GPP TS 29.002 V4.17.0 (2006-06)
privateExtensionList pcs-Extensions ...}
[0]PrivateExtensionList [1]PCS-Extensions
OPTIONAL, OPTIONAL,
SLR-ArgExtensionContainer ::= SEQUENCE {
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
MAP-EXTENSION.&extensionId ({ExtensionSet}), MAP-EXTENSION.&ExtensionType ({ExtensionSet}{@extId})
OPTIONAL}
maxNumOfPrivateExtensions ExtensionSet {...
}
INTEGER ::= 10
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
4567
4568 4569 4570 4571 4572 4573 4574 4575 4576 4577 4578 4579 4580 4581 4582 4583 4584 4585 4586 4587 4588 4589 4590 4591 4592 4593 4594 4595 4596 4597 4598 4599 4600 4601 4602 4603
17.7.12 Group Call data types
MAP-GR-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-GR-DataTypes (23) version7 (7)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS PrepareGroupCallArg, PrepareGroupCallRes, SendGroupCallEndSignalArg, SendGroupCallEndSignalRes, ForwardGroupCallSignallingArg, ProcessGroupCallSignallingArg ; IMPORTS ISDN-AddressString, IMSI, EMLPP-Priority, ASCI-CallReference FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version7 (7)} Ext-TeleserviceCode FROM MAP-TS-Code { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-TS-Code (19) version7 (7)} Kc
1514
1515 Release 4 1516 1517
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 4661 4662 4663 4664 4665 4666
4660
380
3GPP TS 29.002 V4.17.0 (2006-06)
FROM MAP-MS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MS-DataTypes (11) version7 (7)} ExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version7 (7)} ; PrepareGroupCallArg ::= SEQUENCE { teleservice asciCallReference codec-Info cipheringAlgorithm groupKeyNumber groupKey priority uplinkFree extensionContainer ...} PrepareGroupCallRes ::= SEQUENCE { groupCallNumber extensionContainer ...}
Ext-TeleserviceCode, ASCI-CallReference, CODEC-Info, CipheringAlgorithm, [0]GroupKeyNumber [1]Kc [2]EMLPP-Priority [3] NULL [4] ExtensionContainer
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
ISDN-AddressString, ExtensionContainer
OPTIONAL,
SendGroupCallEndSignalArg ::= SEQUENCE { imsi IMSI extensionContainer ExtensionContainer ...} SendGroupCallEndSignalRes ::= SEQUENCE { extensionContainer ExtensionContainer ...} ForwardGroupCallSignallingArg ::= SEQUENCE { imsi IMSI uplinkRequestAck [0] NULL uplinkReleaseIndication [1] NULL uplinkRejectCommand [2] NULL uplinkSeizedCommand [3] NULL uplinkReleaseCommand [4] NULL extensionContainer ExtensionContainer ..., stateAttributes [5] StateAttributes ProcessGroupCallSignallingArg ::= SEQUENCE { uplinkRequest [0] NULL uplinkReleaseIndication [1] NULL releaseGroupCall [2] NULL extensionContainer ExtensionContainer ...} GroupKeyNumber ::= INTEGER (0..15)
OPTIONAL, OPTIONAL,
OPTIONAL,
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, 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
1518
1519 Release 4 1520 1521
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
381
3GPP TS 29.002 V4.17.0 (2006-06)
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
StateAttributes ::= SEQUENCE { downlinkAttached uplinkAttached dualCommunication callOriginator
[5] [6] [7] [8]
NULL NULL NULL NULL
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }
-- Refers to 3GPP TS 44.068 for definitions of StateAttributes fields.
END
4696
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
17.7.13 Location service data types
MAP-LCS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-LCS-DataTypes (25) version7 (7)} DEFINITIONS IMPLICIT TAGS ::= BEGIN EXPORTS RoutingInfoForLCS-Arg, RoutingInfoForLCS-Res, ProvideSubscriberLocation-Arg, ProvideSubscriberLocation-Res, SubscriberLocationReport-Arg, SubscriberLocationReport-Res, LocationType, LCSClientName, LCS-QoS, Horizontal-Accuracy, ResponseTime, Ext-GeographicalInformation, SupportedGADShapes, Add-GeographicalInformation ; IMPORTS AddressString, ISDN-AddressString, IMEI, IMSI, LMSI, SubscriberIdentity, AgeOfLocationInformation, LCSClientExternalID, LCSClientInternalID FROM MAP-CommonDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-CommonDataTypes (18) version7 (7)}
1522
1523 Release 4 1524 1525
41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113
382
3GPP TS 29.002 V4.17.0 (2006-06)
ExtensionContainer, SLR-ArgExtensionContainer FROM MAP-ExtensionDataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-ExtensionDataTypes (21) version7 (7)} USSD-DataCodingScheme, USSD-String FROM MAP-SS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SS-DataTypes (14) version7 (7)} APN FROM MAP-MS-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-MS-DataTypes (11) version7 (7)} Additional-Number FROM MAP-SM-DataTypes { ccitt identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-SM-DataTypes (16) version7 (7)} ; RoutingInfoForLCS-Arg ::= SEQUENCE { mlcNumber targetMS extensionContainer ...} RoutingInfoForLCS-Res ::= SEQUENCE { targetMS lcsLocationInfo extensionContainer ...} LCSLocationInfo ::= SEQUENCE { networkNode-Number -- NetworkNode-number can be either lmsi extensionContainer ... , gprsNodeIndicator -- gprsNodeIndicator is set only if additional-Number } locationType mlc-Number lcs-ClientID privacyOverride imsi msisdn lmsi imei lcs-Priority lcs-QoS extensionContainer ... , supportedGADShapes lcs-ReferenceNumber
[0] ISDN-AddressString, [1] SubscriberIdentity, [2] ExtensionContainer
OPTIONAL,
[0] SubscriberIdentity, [1] LCSLocationInfo, [2] ExtensionContainer
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
ProvideSubscriberLocation-Arg ::= SEQUENCE {
LocationType, ISDN-AddressString, [0] LCS-ClientID [1] NULL [2] IMSI [3] ISDN-AddressString [4] LMSI [5] IMEI [6] LCS-Priority [7] LCS-QoS [8] ExtensionContainer [9] SupportedGADShapes [10] LCS-ReferenceNumber
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 }
1526
1527 Release 4 1528 1529
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
383
3GPP TS 29.002 V4.17.0 (2006-06)
LocationEstimateType ::= ENUMERATED { currentLocation (0), currentOrLastKnownLocation (1), initialLocation (2), ..., activateDeferredLocation (3), cancelDeferredLocation (4) } -exception handling: -a ProvideSubscriberLocation-Arg containing an unrecognized LocationEstimateType -shall be rejected by the receiver with a return error cause of unexpected data value DeferredLocationEventType ::= BIT STRING { msAvailable (0) } (SIZE (1..16)) -- 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 [0] [1] [2] [3] [4] LCSClientType, LCSClientExternalID AddressString LCSClientInternalID LCSClientName
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL }
[5] APN
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 ...} [0] USSD-DataCodingScheme, [2] NameString,
-- 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
LCS-Priority ::= OCTET STRING (SIZE (1)) -- 0 = highest priority -- 1 = normal priority -- all other values treated as 1 LCS-QoS ::= SEQUENCE { horizontal-accuracy verticalCoordinateRequest vertical-accuracy responseTime extensionContainer ...} [0] [1] [2] [3] [4] Horizontal-Accuracy NULL Vertical-Accuracy ResponseTime ExtensionContainer OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL,
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.
1530
1531 Release 4 1532 1533 191 ResponseTime ::= SEQUENCE {
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
384
3GPP TS 29.002 V4.17.0 (2006-06)
--
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))
ProvideSubscriberLocation-Res ::= SEQUENCE {
locationEstimate ageOfLocationEstimate extensionContainer ... , add-LocationEstimate deferredmt-lrResponseIndicator
Ext-GeographicalInformation, [0] AgeOfLocationInformation [1] ExtensionContainer [2] Add-GeographicalInformation [3] NULL
OPTIONAL, OPTIONAL, OPTIONAL, 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
1534
1535 Release 4 385 3GPP TS 29.002 V4.17.0 (2006-06) 1536 1537 235 Ext-GeographicalInformation ::= OCTET STRING (SIZE (1..maxExt-GeographicalInformation))
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
------------------------------------------------------
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
1538
1539 Release 4 386 3GPP TS 29.002 V4.17.0 (2006-06) 1540 1541 295 Add-GeographicalInformation ::= OCTET STRING (SIZE (1..maxAdd-GeographicalInformation))
296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368
the
-----------------
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 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
SubscriberLocationReport-Arg ::= SEQUENCE {
lcs-Event lcs-ClientID lcsLocationInfo msisdn imsi imei na-ESRD na-ESRK locationEstimate ageOfLocationEstimate slr-ArgExtensionContainer ... , add-LocationEstimate deferredmt-lrData lcs-ReferenceNumber ---------------
LCS-Event, LCS-ClientID, LCSLocationInfo, [0] ISDN-AddressString [1] IMSI [2] IMEI [3] ISDN-AddressString [4] ISDN-AddressString [5] Ext-GeographicalInformation [6] AgeOfLocationInformation [7] SLR-ArgExtensionContainer [8] Add-GeographicalInformation [9] Deferredmt-lrData [10] LCS-ReferenceNumber
OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, OPTIONAL, 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.
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) } -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
1542
1543 Release 4 1544 1545
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
387
3GPP TS 29.002 V4.17.0 (2006-06)
TerminationCause ::= ENUMERATED { normal (0), errorundefined (1), internalTimeout (2), congestion (3), mt-lrRestart (4), privacyViolation (5), ..., shapeOfLocationEstimateNotSupported (6) } -- 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) SubscriberLocationReport-Res ::= SEQUENCE { extensionContainer ExtensionContainer ..., na-ESRK [0] ISDN-AddressString OPTIONAL, OPTIONAL }
END
394
1546
1547
17.7.14
395
void
396 397
18
General on MAP user procedures
18.1 Introduction
398 Clauses 18 to 25 describe the use of MAP services for GSM signalling procedures. GSM signalling procedures may 399 involve one or several interfaces running one or several application protocols. The present document addresses only the 400 signalling procedures which require at least the use of one MAP service. 401 402 403 404 405
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.
406 407
408 409 410 411 412 413 414 415 416 417 418 419
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.
420 The mapping of service primitives on to protocol elements is described in clauses 14 to 17. 421 GSM signalling procedures are built from one or more sub-procedures (e.g. authentication, ciphering, ...). 422 Sub-procedures from which signalling procedures are built are represented using SDL MACRO descriptions. 423 In case of any discrepancy between the textual descriptions and the SDL descriptions, the latter take precedence.
424
18.2.2 Naming conventions
425 Events related to MAP are represented by MAP service primitives. The signal names used in the SDL diagrams are 426 derived from the service primitive names defined in clauses 7 to 12, with some lexical transformations for readability 427 and parsability purposes (blanks between words are replaced by underscores, the first letter of each word is capitalised). 428 Events received and sent on other interfaces are named by appending the message or signal name to a symbol 429 representing the interface type, with some lexical transformations for readability and parsability purposes (blanks 430 between words are replaced by underscores, the first letter of each word is capitalised). 431 The following symbols are used to represent the interface types: 432
"I":
For interfaces to the fixed network. "I" stands for ISUP interface.
1548
1549
433 434 435 436 437
"A": "OM": "SC": "HO_CA": "US":
For interfaces to BSS (i.e. A-interfaces); 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.
438 These naming conventions can be summarised by the following BNF description: 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
<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 | 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> ::= <Letter> | <Digit> ::= <Lower_Case_Letter> | <Upper_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
465 466 18.2.3.1
18.2.3 Convention on primitives parameters
Open service
1550
1551
467 When the originating and destination reference parameters shall be included in the MAP-OPEN request primitive, their 468 value are indicated as a comment to the signal which represents this primitive.
469 18.2.3.2
Close service
470 When a pre-arranged released is requested, a comment is attached to the signal which represents the MAP-CLOSE 471 request primitive. In the absence of comment, a normal release is assumed.
472
18.2.4 Version handling at dialogue establishment
473 Unless explicitly indicated in subsequent clauses, the following principles regarding version handling procedures at 474 dialogue establishment are applied by the MAP-user.
475 18.2.4.1
Behaviour at the initiating side
476 When a MAP user signalling procedure has to be executed, the MAP-user issues a MAP-OPEN request primitive with 477 an appropriate application-context-name. If several names are supported (i.e. several versions) a suitable one is selected 478 using the procedures described in clause 5. 479 480 481 482 483 484
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".
485 18.2.4.2
Behaviour at the responding side
486 On receipt of a MAP-OPEN indication primitive, the MAP-User analyses the application-context-name and executes 487 the procedure associated with the requested version context. For example,if it refers to a version one context, the 488 associated V1 procedure is executed; if it refers to a version two context, the associated V2 procedure is executed;etc.
489
18.2.5 Abort Handling
490 Unless explicitly indicated in subsequent clauses, the following principles are applied by the MAP-user regarding abort 491 handling procedures: 492 On receipt of a MAP-P-ABORT indication or MAP-U-ABORT Indication primitive from any MAP-provider 493 invocation, the MAP-User issues a MAP-U-ABORT Request primitive to each MAP-provider invocation associated 494 with the same user procedure. 495 If applicable a decision is made to decide if the affected user procedure has to be retried or not.
496
18.2.6 SDL conventions
497 The MAP SDLs make use of a number of SDL concepts and conventions, where not all of them may be widely known. 498 Therefore, this clause outlines the use of a few concepts and conventions to improve understanding of the MAP SDLs. 499 500 501 502
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.
503 All Processes are started at system initialisation and live forever, unless process creation/termination is indicated 504 explicitly (i.e. a process is created by some other process). 505 The direction of Input/Output Signals in the SDL graphs is used to indicate the entity to which/from which 506 communication is directed. If a process A communicates in parallel with processes B and C, all Inputs/Outputs to/from 507 B are directed to one side, whereas communication with C is directed to the other side. However, there has been no
1552
1553
508 formal convention used that communication to a certain entity (e.g. a HLR) will always be directed to a certain side 509 (e.g. right). 510 511 512 513
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.
514
515 516 517 518 519 520 521 522 523 524 525 526 527
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.
528 529
19
Mobility procedures
19.1 Location management Procedures
530 For non-GPRS subscribers, this clause comprises a number of processes to handle the mobile nature of the subscriber. 531 The processes will be addressed by SCCP Sub-System Number (MSC, VLR or HLR) and the Application Context. The 532 following processes are defined in this clause: 533 534 535 536 537 538 539 540 541 542 543 544 545 546
Process Update Location Area: Update_Location_Area_VLR, clause 19.1.1.3; Process Update Location: Initiator: Responder: Update_Location_Area_VLR, clause 19.1.1.3; Update_Location_HLR, clause 19.1.1.4;
Process Send Identification: Initiator: Responder: Send_Identification_VLR, clause 19.1.1.x; Send_Identification_PVLR, clause 19.1.1.5;
Process Cancel Location: Initiator: Responder: Process Purge MS: Initiator: Responder: Purge_MS_VLR, clause 19.1.4.2; Purge_MS_HLR, clause 19.1.4.3. Cancel_Location_HLR, clause 19.1.2.2; Cancel_Location_VLR, clause 19.1.2.3;
1554
1555
547 For GPRS subscribers, this clause comprises a number of other processes to handle the mobile nature of the subscriber. 548 The processes will be addressed by SCCP Sub-System Number (SGSN or HLR) and the Application Context. The 549 following processes are defined in this clause: 550 551 552 553 554 555 556 557 558 559 560 561 562 563
Process GPRS Update Location: Initiator: GPRS_Update_Location_Area_VLR, clause 19.1.1.3, or SGSN_Update_HLR, clause 19.1.1.8, Responder: Update_GPRS_Location_HLR, clause 19.1.1.4;
Process Cancel Location: Initiator: Responder: Process Purge MS: Initiator: Responder: Purge_MS_SGSN, clause 19.1.4.4; Purge_MS_HLR, clause 19.1.4.3. Cancel_GPRS_Location_HLR, clause 19.1.2.2; Cancel_Location_SGSN, clause 19.1.2.4;
The following existing process is also used for GPRS subscribers : Process Subscriber Present HLR: Initiator: Responder: Subscriber_Present_HLR, clause 19.1.1.7; Short_Message_Alert_IWMSC, clause 23.4.3;
564 Location Management Coordinator HLR 565 566 567 568
Sheet 1: After creation of the user process the service primitive received from the MAP service-provider is passed to the user process. Henceforth, the coordinator will relay all service primitives from MAP service-provider to the MAP service-user and vice versa, until a request or indication for dialogue termination is received. This last primitive will be relayed, too, before the Coordinator process returns to idle state.
1556
1557
Pro cess Location_M anagement_Coordinator_H LR
F ig ure 19 . 1 / 3 L o catio n m an a g em e nt co ordin a t ion p roce s s in t h e H L R
19.1_3(1)
NU L L
Rece ive_ O p e n_I nd
Fig ure 2 1.1 /1
'V r' 'O K '
'E rro r'
W A IT_ FO R_ S E RV IC E _ P RIM I TIV E
'P erf orm _ M A P _ V r_ Dia lo gu e'
MAP_ UP D A TE _ L O CA TI O N_ I nd
MAP_ RE S T O RE _ DA TA _I n d
M AP_ N O TI CE _ I nd
N UL L
NU LL
Up d a te_ Lo cat io n_ HLR
RE S T O RE _ DA TA _ H LR
M APC LOSE_ R eq
MAP_ UP D A TE _ L O CA TI O N _ Ind
MA P_ RE S T O RE _ DA TA _I nd
N UL L
RE LA Y _ I NFO
* from P rovid er
* fro m O FF S P R ING
M A P -U-A B O R T_ Req , M A P -CL OS E _ Re q f rom O FF S P RI NG
MA P -P -A B OR T_ I n d, MA P -U -A B O RT _ In d, M A P -C LO S E _ I n d
to O FF S P R ING
to P ro v id er
to P rovid er
to O F FS P RIN G
RE LA Y _ I NFO
R E L A Y _I NFO
NUL L
N UL L
569
570
Figure 19.1/3: Process Location_Management_Coordinator_HLR
1558
1559
571 572 19.1.1.1
573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596
19.1.1 Location updating
General
The location updating procedure is used to update the location information held in the network. For GPRS subscribers, this procedure describes also updating of the SGSN and, if Gs interface is installed, updating of the VLR in combination with an attach/routing area updating in the SGSN. This location information is used to route incoming calls, packet data, short messages and unstructured supplementary service data to the roaming subscriber. Additionally, this procedure is used to provide the VLR and/or the SGSN with the information that a subscriber already registered, but being detached, is reachable again (IMSI Attach and/or GPRS Attach, see 3GPP TS 23.012 [23] and 3GPP TS 23.060 [104]). The use of the IMSI Detach / Attach feature is optional for the network operator. To minimise the updates of the subscriber's HLR, the HLR holds only information about the VLR and MSC the subscriber is attached to and, for GPRS subscribers, the SGSN the subscriber is attached to. The VLR and the SGSN contain more detailed location information, i.e. the location area the subscriber is actually roaming in (for the VLR) and the routing area (RA) where the GPRS subscriber is located (for SGSN). Therefore, the VLR needs to be updated at each location area change (see figure 19.1.1/1 for this procedure) and the SGSN needs to be updated at each routing area change. The HLR needs updating only in the following cases: when the subscriber registers in a new VLR or SGSN, i.e. the VLR or SGSN has no data for that subscriber; when the subscriber registers in a new location area of the same VLR and new routing information is to be provided to the HLR (change of MSC area); if the indicator "Confirmed by HLR" or the indicator "Location Information Confirmed in HLR" is set to "Not Confirmed" because of HLR, VLR or SGSN restoration, and the VLR or SGSN receives an indication that the subscriber is present.
If a mobile subscriber registers in a visitor location register (VLR) not holding any information about this subscriber and is identified by a temporary mobile subscriber identity (TMSI) allocated by a previous visitor location register (PVLR), if the PVLR identity can be derived from LAI the new VLR must obtain the IMSI from PVLR to identify the HLR to be updated (see figure 19.1.1/2). If the IMSI cannot be retrieved from PVLR, it is requested from the MS (see figure 19.1.1/3).
597 The stage 2 specification for GPRS is in 3GPP TS 23.060 [104]. The interworking between the MAP signalling 598 procedures and the GPRS procedures in the SGSN is shown by the transfer of signals between these procedures (see 599 clause 19.1.1.8). 600 The message flow for successful GPRS Attach/ RA update procedure (with Gs interface not installed) is shown in 601 figure 19.1.1/4. 602 The message flow for successful GPRS Attach/ RA update procedure combined with a successful VLR location 603 updating (Gs interface installed) is shown in figure 19.1.1/5. 604 The following MAP services are invoked by the location update procedure: 605 606 607 608 609 610 611 612 613 614
MAP_UPDATE_LOCATION_AREA MAP_UPDATE_LOCATION MAP_UPDATE_GPRS_LOCATION MAP_CANCEL_LOCATION MAP_INSERT_SUBSCRIBER_DATA MAP_SEND_IDENTIFICATION MAP_PROVIDE_IMSI MAP_AUTHENTICATE MAP_SET_CIPHERING_MODE MAP_FORWARD_NEW_TMSI
(see clause 8.1);(**) (see clause 8.1);(**) (see clause 8.1) (*); (see clause 8.1); (see clause 8.8); (see clause 8.1) (**); (see clause 8.9) (**); (see clause 8.5) (**); (see clause 8.6) (**); (see clause 8.9) (**);
1560
1561
615 616 617 618 (*):
MAP_CHECK_IMEI MAP_ACTIVATE_TRACE_MODE
(see clause 8.7) (**); (see clause 9.2);
MAP_TRACE_SUBSCRIBER_ACTIVITY (see clause 9.2) (**). only used in SGSN and HLR for GPRS
619 (**): not used in SGSN
620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668
+----+ +----+ A +--------+ D +----+ MS - BS --+--MSC/VLR ---------+------------HLR +----+ +----+ +--------+ +----+ G +----+ D +-----+-----PVLR+----+-----+ +----+ A_LU_REQUEST --------------- -> MAP_SEND_IDENTIFICATION -------------> MAP_SEND_IDENTIFICATION <------------- ack MAP_UPDATE_LOCATION ----------------------> MAP_CANCEL_ LOCATION <------------ MAP_CANCEL_ LOCATION ack ------------> MAP_ACTIVATE_TRACE_MODE <-------------------------- MAP_ACTIVATE_TRACE_MODE ack --------------------------> MAP_INSERT_SUBSCRIBER_DATA <-------------------------- MAP_INSERT_SUBSCR._DATA ack --------------------------> MAP_UPDATE_LOCATION ack <-------------------------- A_LU_CONFIRM <-----------------
NOTE: Procedures shown in italics are optional.
672
673
669 670 671
Figure 19.1.1/2: Interface and services for location updating when changing the VLR area
1562
1563
674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721
+----+ +----+ A +--------+ D +----+ MS ---- BS ------MSC/VLR ------+------HLR +----+ +----+ +--------+ +----+ G +----+ D +---+--PVLR+--+----+ +----+ A_LU_REQUEST ----------------------> <---------------------- ----------------------> MAP_UPDATE_LOCATION ------------------> MAP_CANCEL_ LOCATION <----------- MAP CANCEL LOCATION ack -----------> MAP_ACTIVATE_TRACE_ <------------------ MODE MAP_ACTIVATE_TRACE_ ------------------> MODE ack MAP_INSERT_ <------------------ SUBSCRIBER_DATA MAP_INSERT_ ------------------> SUBSCRIBER_DATA ack MAP_UPDATE_LOCATION <------------------ A_LU_CONFIRM ack <----------------------
NOTE: Procedures shown in italics are optional.
725 726
723 724
Figure 19.1.1/3: Interface and services for location updating involving both a VLR and an HLR, when IMSI can not be retrieved from the previous VLR
1564
1565
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
+----+ +----+ Gb +-----+ Gr +----+ MS - BS --------------+--- SGSN----------+-----------HLR +----+ +----+ +-----+ +----+ +----+ D VLR +-----+----------+ Gs +----+ +-----+ Gr PSGSN+----+----+ +-----+ Gb_ATTACH/RA_UPDATE_REQUEST -----------------------------> (note_1) (Note_2) MAP_UPDATE_GPRS_LOCATION ----------------------------> MAP_CANCEL_ LOCATION <------------ MAP_CANCEL_ LOCATION ack ------------> MAP_ACTIVATE_TRACE_MODE <---------------------------- (note_3) MAP_ACTIVATE_TRACE_MODE ack ----------------------------> MAP_INSERT_SUBSCRIBER_DATA <---------------------------- MAP_INSERT_SUBSCR._DATA ack ----------------------------> MAP_UPDATE_GPRS LOCATION ack <---------------------------- (Note_4) Gb_ATTACH/RA_UPDATE_ <----------------------------- REQUEST ack PSGSN = Previous SGSN
NOTE 1: For details of the procedure on the radio path, see 3GPP TS 48.018. 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 section 25. NOTE 3: Optional services are printed in italics. NOTE 4: Refer to 3GPP TS 23.060 [104] for termination of the procedure and triggering of the signalling on the Gb interface.
781
782 783 784
785
Figure 19.1.1/4: Interface and services for GPRS location updating (Gs-interface not installed)
1566
1567
786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 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
+----+ +----+ Gb +-----+ Gr +----+ MS - BS --------------+---- SGSN---------+-----------HLR +----+ +----+ +-----+ +----+ +----+ D ++-VLR +-------+--------+ Gs +----+ +-----+ Gr PSGSN+----+----+ +-----+ Gb_ATTACH/RA_UPDATE_REQUEST -----------------------------> MAP_UPDATE_GPRS_LOCATION ----------------------------> MAP_CANCEL_ LOCATION <------------ MAP_CANCEL_ LOCATION ack ------------> MAP_ACTIVATE_TRACE_MODE <---------------------------- MAP_ACTIVATE_TRACE_MODE ack ----------------------------> MAP_INSERT_SUBSCRIBER_DATA <---------------------------- MAP_INSERT_SUBSCR._DATA ack ----------------------------> MAP_UPDATE_GPRS LOCATION ack <---------------------------- Gs_GPRS_LOCATION -------> UPDATING MAP_UPDATE_LOCATION -------------------> Note_1 MAP_INSERT <------------------- SUBSCRIBER_DATA MAP_INSERT -------------------> SUBSCRIBER_DATA ack MAP_UPDATE_LOCATION <------------------- Gs_GPRS_LOCATION ack <------- UPDATING Ack Gb_ATTACH/RA_UPDATE_ <----------------------------- REQUEST ack ----------------------------->Gs_GPRS_TMSI_REALLOCATION -------> COMPLETE
NOTE 1: The optional procedures in figure 19.1.1/14 apply here respectively. For details of the procedure on the Gs-interface, see 3GPP TS 29.018 [106]. NOTE 2: Location Cancellation procedure toward the old VLR and optional tracing activation toward the new VLR are not represented on this figure.
856
850 851 852 853 854 855
Figure 19.1.1/5: Interface and services for GPRS location updating (Gs-interface installed)
1568
1569
857 19.1.1.3
Detailed procedure in the VLR
858 Updating request via the Gs interface (optional for GPRS) 859 If Gs-interface is installed, the VLR may receive the Gs_GPRS_LOCATION_UPDATING_Request message from the 860 SGSN for triggering an IMSI Attach or Location Updating procedure (see 3GPP TS 23.060 [104] and 09.18). 861 Figure 19.1.1/16 shows the process for handling this Gs interface message. 862 The process specific macro 863 864
GPRS_Location_Update_Completion_VLR for optional initiation of TMSI reallocation as for acknowledgement of the Gs_GPRS_LOCATION_UPDATING_Request message (see figure 19.1.1/17),
865 and the optional process specific macro 866 867 868 869 870 871 872
VLR_Update_GPRS_HLR to update the HLR and download subscriber data from there (see figure 19.1.1/18), are invoked by this process. On receipt of the Gs_GPRS_LOCATION_UPDATING_Request message, the VLR checks whether the subscriber is unknown (i.e. no IMSI record). If so, the indicator "Location Information Confirmed in HLR" is set to "Not Confirmed" to initiate HLR updating later on. The indicator "Confirmed by Radio Contact" is set to "Confirmed" and the location information held in the register is updated. If no VLR/SGSN association exits it is created (storage of SGSN address received) otherwise it is updated.
873 If the HLR is to be updated, the VLR_Update_GPRS_HLR macro described below is performed, with one of the 874 following results (see sheet 2 of figure 19.1.1/18): 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891
OK, if HLR updating has been completed successfully. The response will contain the HLR number as parameter. Next, the GPRS_Location_Update_Completion VLR macro is invoked (checking amongst others the roaming restrictions and regional subscription data), and upon successful outcome of this macro the register is updated and the process terminates. Roaming Not Allowed, qualified by PLMN Roaming Not Allowed if the location information indicates a PLMN for which the subscriber has no subscription or if the subscribers HLR cannot be reached (e.g. SS7 links to the subscribers HPLMN do not yet exist). In this case, the appropriate error (see 3GPP TS 29.018 [106]) is sent to the SGSN in the Gs_GPRS_LOCATION_UPDATING Reject. The Subscriber Data are deleted in the VLR. if Roaming Not Allowed was qualified by the parameter Operator Determined Barring, the appropriate error (see 3GPP TS 29.018 [106]) is sent in the Gs_GPRS_LOCATION_UPDATING Reject to the SGSN. The subscriber data are deleted in the VLR. Unknown Subscriber, if the subscriber is not known in the HLR. In this case, the subscriber data are deleted in the VLR, and the appropriate error (see 3GPP TS 29.018 [106]) is sent in the Gs_GPRS_LOCATION_UPDATING Reject. Procedure error, if there occurs some other error during HLR updating (e.g. abort of the connection to HLR). In this case the appropriate error (see 3GPP TS 29.018 [106]) is sent in the Gs_GPRS_LOCATION_UPDATING Reject.
892 The macro GPRS Location Update Completion VLR 893 This macro completes the VLR updating process. First, the VLR checks whether there is a roaming restriction for the 894 subscriber (see figure 19.1.1/17): 895 896 897 898 899 900
if the target LA is not allowed for the subscriber due to national roaming restrictions, the appropriate error (see 3GPP TS 29.018 [106]) is sent in the Gs_GPRS_LOCATION_UPDATING Reject towards the SGSN. The subscriber data are not deleted from VLR, to avoid unnecessary HLR updating when roaming into other LAs of the same MSC/VLR. An indication that the subscriber is not allowed to roam is set in the VLR (LA Not Allowed Flag set to not allowed). As a consequence the subscriber is not reachable (checked for MTC, SMS and MT USSD) and cannot perform outgoing actions (checked in Access Management).
1570
1571
901 902 903 904 905 906 907 908 909 910 911 912 913
if the target LA is not allowed for the subscriber because of regional subscription data (Zone Code List) or Roaming Restriction Due To Unsupported Feature stored in the VLR, the appropriate error (see 3GPP TS 29.018 [106]) is returned to the SGSN in the Gs_GPRS_LOCATION_UPDATING Reject. Also in this case the subscriber data are not deleted from VLR, to avoid unnecessary HLR updating when roaming into other LAs of the same MSC. The LA Not Allowed Flag is set to not allowed in the VLR.
if, after check of possible roaming restrictions, the subscriber is allowed to roam in the target LA, the LA Not Allowed Flag is set to allowed (if necessary), the IMSI Detached Flag is set to attached and the process SUBSCRIBER_PRESENT_VLR is started; this may inform the HLR that the subscriber is present again to retry an SMS delivery (see clause 19.1.1.7). Thereafter, the VLR checks whether TMSI reallocation is required. if so, the VLR sends the TMSI within the Gs_GPRS_LOCATION_UPDATING Accept message and Gs_GPRS_TMSI_REALLOCATION_Complete is expected. if TMSI reallocation is not required, the VLR sends the Gs_GPRS_LOCATION_UPDATING Accept message to the SGSN.
914 The macro VLR Update GPRS HLR 915 This macro is invoked by the VLR process for location updating (see 3GPP TS 23.060 [104]). If the VLR does not 916 know the subscribers HLR (e.g. no IMSI translation exists as there are not yet any SS7 links to the subscribers 917 HPLMN), the error Roaming Not Allowed with cause PLMN Roaming Not Allowed is returned. 918 If the subscribers HLR can be reached, the VLR opens a dialogue towards the HLR (see figure 19.1.1/18) by sending a 919 MAP_OPEN request without any user specific parameters, together with a MAP_UPDATE_LOCATION request 920 containing the parameters 921 922 923 924 925 926
IMSI, identifying the subscriber; Location Info, containing the MSC number; VLR Number, the E.164 address of the VLR, to be used by the HLR when addressing the VLR henceforth (e.g. when requesting an MSRN); the LMSI as an VLR operator option; this is a subscriber identification local to the VLR, used for fast data base access.
927 In case the HLR rejects dialogue opening (see clause 25.1), the VLR will terminate the procedure indicating Procedure 928 error. If the HLR indicates version Vr protocol to be used, the VLR will revert to the version Vr procedure concerning 929 the dialogue with the HLR, with outcomes as for the current MAP version procedure. 930 If the HLR accepts the dialogue, the HLR will respond with: 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946
a MAP_INSERT_SUBSCRIBER_DATA indication, handled by the macro Insert_Subs_Data_VLR defined in clause 25.7; The HLR may repeat this service several times depending on the amount of data to be transferred to the VLR and to replace subscription data in case they are not supported by the VLR.
NOTE: -
a MAP_ACTIVATE_TRACE_MODE indication, handled by the macro Activate_Tracing_VLR defined in clause 25.9; a MAP_FORWARD_CHECK_SS_INDICATION_ind. This indication will not be relayed to the SGSN. the MAP_UPDATE_LOCATION confirmation: if this confirmation contains the HLR Number, this indicates that the HLR has passed all information and that updating has been successfully completed. The VLR is updated using the parameters provided in the service and needed by the VLR. If certain parameters are not needed in the VLR, e.g. because some service is not supported, the corresponding data may be discarded. The VLR sets the "Confirmed by HLR" and "Location information confirmed in HLR" indicators to "Confirmed" to indicate successful subscriber data updating; if the confirmation contains an User error cause (Unknown Subscriber, Roaming Not Allowed or some other), the process calling the macro continues accordingly. In the last case, the subscriber data are marked as
1572
1573
947 948 949 950 951 952
incomplete by setting the indicators "Confirmed by HLR" and "Location information confirmed in HLR" to "Not Confirmed". The same holds if there is a Provider error or a Data error in the confirmation; a MAP_P_ABORT, MAP_U_ABORT, or MAP_CLOSE indication. In these cases, the subscriber data are marked to be incomplete and the process continues as in the case of an error reported by the HLR; a MAP_NOTICE indication. Then, the dialogue towards the HLR is terminated, the subscriber data are marked to be incomplete and the process continues as in the case of an error reported by the HLR.
Process Update_HLR_VLR
VLR MAP protocol machine handling Location Management Signals to/from the left are to/from the VLR Location Management application. Signals to/from the right are to/from the HLR MAP protocol machine, handling Location Management. MAP_OPEN_Req MAP_UPDATE_LOCAT ION_Req MAP_DELIMITER_Req NULL
1(2)
Update Location
Receive Open Cnf.
OK WAIT_FOR_ ACK
Vr Perform_MAP_ Vr_Dialogue
Error Update Location Negative R esponse
NULL
MAP_UPDAT E_ LOCATION_cnf
MAP_INSERT _ SUBSCRIBER_ DATA_req
MAP_ACTIVE_ TRACE_MODE_ req
MAP_NOTICE_ Ind
MAP_U_ABORT_ind MAP_CLOSE_ind MAP_P_ABORT_ind
Insert Subscriber Data
Activate Trace mode
MAP_CLOSE_ req
Set negative response Wait_For_HLR_or_ Application_ Response Update Location negative response Insert Subscriber Data negative response
Inser t Subscriber Data ack
Activate Trace mode ack
Activate Trace mode negative response
MAP_INSERT _ SUBSCRIBER_ DATA_req
MAP_FORWARD_ CHECK_SS_ ind NULL
Set user error
Set user error
Insert Subscriber Data
Forward Check SS
MAP_INSERT_ SUBSCRIBER_DATA_ rsp
MAP_ACTIVE_ TRACE_MODE_ rsp
Wait_For_HLR_or_ Application_ Response
953
954
Figure 19.1.1/6 (sheet 1 of 2): Process Update_HLR_VLR
1574
1575
Process Update_HLR_VLR
VLR MAP protocol machine handling Location Management Signals to/from the left are to/from the VLR Location Management application.
2(2)
Signals to/from the right are to/from the HLR MAP protocol machine, handling Location Management. Wait_For_HLR_or_ Application_ Response
1 MAP_UPDAT E_ LOCATION_cnf MAP_NOTICE_ ind
MAP_U_ABORT_ind MAP_CLOSE_ind MAP_P_ABORT_ind
Check Confirmation
MAP_CLOSE_ req Provider Error, User Error, Data Error Set negative response Set negative response
OK Update Location ack
Update Location negative response
Update Location negative response
NULL
NULL
Result
Unknown Subscriber Set negative r esponse UnknownSubscriber
Roaming not allowed Set negative response Roaming not allowed
Procedure Error Set negative response Procedure Err or
Aborted
HLR No
Set negative response Abort
Update Location ack
Update Location negative response
NULL
NULL
955
956
Figure 19.1.1/6 (sheet 2 of 2): Process Update_HLR_VLR
1576
1577
Pro cess G PR S_U pdate_Location_ Are a_VLR
F ig u re 1 9.1 . 1/ 16 : L o c at io n u p d atin g in VL R s ig n als to /fro m th e lef t are to /fro m th e S G S N
19.1 .1_16.1(2)
(n o ) Id le
V L R /S G S N a s so c ia tio n e xis t s ? (y es )
c rea te th e G s _G P R S _ L O C A T IO N _ U P D A T IN G _ R eq ue s t a ss o c iat io n
u pd at e th e as s oc iat ion
S u bs c rib er k no w n in V L R
(n o )
(y es ) S et L o c In fo no t c o nf irme d in H L R
H LR u p d atin g re qu ired ?
(y es )
2 G P R S _L o c at io n _ U pd a te_ C o m p letio n_ V L R OK (no ) E rro r
S et ra dio c o nta c t flag to c o n firm ed
U p d ate L AI U pd a te R egist er
Id le
957
958
Figure 19.1.1/16 (sheet 1 of 2): Process GPRS_Update_Location_Area_VLR
1578
1579
Pro cess G PR S_U pdate_Location_ Are a_VLR
F ig u re 1 9.1 . 1/ 16 : L o c at io n u p d atin g in VL R
19.1 .1_16.2(2)
S ig n als to /f ro m th e lef t are to/ fro m th e S G S N
V L R _ U p d ate _ G P R S _H L R
F ig u re 1 9 .1 .1/1 8
OK
P ro c ed ure _ E rror
U n k n o wn _ S u bs c rib e r
R o a m in g_ N ot_ A llo w e d D elete S u b sc ribe r
G P R S _L o c at ion _ U p d ate _ C om p le tio n _V L R
D e lete S u b s c rib er F ig u re 1 9 .1 .1/1 7
OK
E rror
U pd a te reg is ter
S e t e rro r to a p pro p riate v alu e a c c o rding to 09 .1 8
Id le
G s _ G P R S _ LO C A T IO N _ U P D A T ING _R e jec t
Idle
959
960
Figure 19.1.1/16 (sheet 2 of 2): Process GPRS_Update_Location_Area_VLR
1580
1581
Macrodefin ition G PR S_Locatio n_U pdate_C ompletion_VLR
F ig u re 1 9. 1. 1 /17 : L o c ation u p d atin g in V L R fo r G P R S : c lo sing s eq u en c e
19.1 .1_17(1 )
S ig na ls to /f ro m th e left are to/ fro m th e S G S N
( 'ye s ') L A _n o t_ allow ed _ fla g := a llo w e d
R o am in g _ in_ targ et_ L A _ allow ed
('n o ')
L A _n o t_ allow ed _ fla g := n o t a llo w e d IM S I_ D et ac h ed _ F la g := atta c he d 'S e t_e rro r_ to _ A pp ro pria te_ v alu e _ ac c o rd in g_ to _ G S M _ 09 .1 8
S ub s c rib er_ P re se n t_ VL R
F ig u re 2 5 .1 0/1
T M S I_ rea llo c ation _ req uire d (y es )
(n o )
G s _ G P R S _ LO C A T IO N _ U P D A T IN G _ R ej ec t
OK
A llo c ate T M S I
G s_ G P R S _ L O C A T IO N _ U P D A T IN G _ A c c ep t
S et T im e r
OK
G s _ G P RS _ L O C A T IO N _ UP D A T IN G _A c c e p t inc lu ding T MS I
W A IT _F O R _ T M S I_ C n f
G s _ G P RS _ T M S I_ R E A L LO C A T IO N _C o mp lete
T im er E x p ir y
F re ez e old T M S I
OK
961
962
Figure 19.1.1/17: Macro GPRS_Location_Update_Completion_VLR
1582
1583
Macrodefin ition V LR_U pdate_G PR S_H LR
F ig u re 1 9.1 .1 / 18 : H L R up d at in g in V LR ' U n k n ow n _ H LR ' M A P _ O P E N_ R eq , M A P _U P D A T E _ LO C A T IO N _ R e q , M A P_ D E L IM IT E R _R eq R ec e ive _ O p en _ c n f
19.1 .1_18.1(2)
S ig na ls to /fro m th e rig ht are to /fr om th e H L R
( 'n o ')
( 'ye s' ) R o a m ing _ N o t_A llo w e d
OK W A IT _F O R _ D A TA
E rro r P ro c e du re_ E rr o r 1
Vr
Ins e rt _S ub s_ D ata _V L R
A c t iva te_ T ra c in g _V L R
M A P _ U P D A T E_ L O C A T IO N _ C nf
M A P _ U _ A B O R T _In d , M A P _ P _A B O R T _In d , M A P _ C lo se _In d Set not C o nf irme d b y HL R S et Lo c In fo n ot C o n firm ed in H LR
W A IT _F O R _ D A TA
W A IT _ F O R _ DA T A
C h ec k _ C o nf irm at io n
U se r E rro r P ro vid e r E r ro r, D ata E r ro r
OK S et C on firm e d b y HL R
S et L oc Info C o nfirm e d in H L R U p d ate re gis te r P ro c ed ure _ E rror
OK ELSE ' E rro r_ c as e' ' un k n o wn _ s u b sc ribe r' 'ro am ing _ n ot_ S et L o c Inf o n o t c n f in H L R a llo w e d ' Set not C o n firm ed by HLR Un kn o wn _ S u bs c rib e r R o a m in g_ N ot_ A llo w e d P ro c ed u re _ E rro r
963
964
Figure 19.1.1/18 (sheet 1 of 2): Macro VLR_Update_GPRS_HLR
1584
1585
Macrodefin ition V LR_U pdate_G PR S_H LR
F ig u re 1 9.1 .1 / 18 : H L R up d at in g in V LR
19.1 .1_18.2(2)
S ig na ls to /fro m th e rig ht are to /fr om th e H L R
P er fo rm M A P V r D ialo g ue
'R es u lt'
' HL R _ N o '
'un k n o w n _ su b s c rib er '
' ro a m in g_ n o t_ a llo w ed '
'P r oc e du r e_ err or'
' A bo rted '
P ro c ed u re E rro r
HL R _N o
U n k n ow n_ S u b s c rib er
R o am in g _n o t_ A llow ed
P roc edu re_ E rro r
W A IT _ F O R _ DA T A
M A P _N O T IC E _ Ind
M A P _ FO RW A RD _ C H E C K _ S S _ IN D IC A T IO N _In d
M A P _C L O S E _ Re q
W A IT _ F O R _ DATA
S et no t C o n firm e d b y H LR S et Lo c In fo n ot C o n firm ed _ in H LR
P ro c e du re_ E rro r
965
966
Figure 19.1.1/18 (sheet 2 of 2): Macro VLR_Update_GPRS_HLR
1586
1587
967 19.1.1.4
Detailed procedure in the HLR
968 Sheet 1: The procedure Super_Charged_Cancel_Location_HLR is specific to Super-Charger; it is specified in 969 TS 23.116 [110]. If the previous SGSN and the originating HLR support the Super-Charger functionality, processing 970 continues from the "Yes" exit of the test "Result=Pass?". 971 Sheet 2: The procedure Super_Charged_Location_Updating_HLR is specific to Super-Charger; it is specified in 972 TS 23.116 [110]. If subscription data needs to be sent to the SGSN, processing continues from the "No" exit of the test 973 "Result=Pass?". 974 When addressed by the SGSN, the following macros are used by the process Update_GPRS_Location_HLR: 975 976 977 978
Receive_Open_indication, defined in clause 25.1; Check_indication, defined in clause 25.2; Insert_Subs_Data_In_SGSN_Framed_HLR, described in clause 19.4; Control_Tracing_HLR_with_SGSN, described in clause 25.9;
979 and the processes Cancel_Location_HLR (see clause 19.1.2) and Subscriber_Present_HLR (see clause 19.1.1.7) are 980 invoked. 981 The location updating process in the HLR is activated by receipt of a MAP_UPDATE_GPRS_LOCATION indication 982 (see figure 19.1.1/19): 983 984 985 986 987 988 989 990 991 992
if there is a parameter problem in the indication, the error Unexpected Data Value is returned in the MAP_UPDATE_LOCATION response (see Check_indication macro defined in clause 25.2); if the subscriber is not known in the HLR, the error Unknown Subscriber (with diagnostic value set to Imsi Unknown) is returned in the response. In either case the process terminates; if Network Access Mode is set to non-GPRS only the error Unknown Subscriber (with diagnostic value set to Gprs Subscription Unknown) is returned in the response. The process terminates; tracing shall be set to deactive in the SGSN. if the SGSN number received in the MAP_UPDATE_GPRS_LOCATION indication differs from the one actually stored against the subscriber, the Cancel_Location_HLR process is started to cancel the subscriber data in the stored SGSN (see clause 19.1.2).
993 The next action will be to check whether the subscriber is allowed to roam into the PLMN indicated by the SGSN 994 Number given in the MAP_UPDATE_GPRS_LOCATION indication: 995 996 997 998 999 1000 1001
if the subscriber is not allowed to roam into the PLMN, the error Roaming not Allowed with cause PLMN Roaming Not Allowed or 'Operator determined Barring', depending on the case, is returned in the MAP_UPDATE_GPRS_LOCATION response, and the routing information stored (SGSN number) is deleted (deregistration); otherwise the HLR database will be updated with information received in the indication. The HLR sets the "MS purged for GPRS" flag to False and checks whether tracing is required for that subscriber. This is handled by the macro Control_Tracing_HLR-with_SGSN described in clause 25.9.
1002 Thereafter, the macro Insert_Subs_Data_In_SGSN_Framed_HLR described in clause 19.4 is invoked. The outcome of 1003 this macro may be: 1004 1005 1006 1007
aborted, in which case the process terminates; error, in which case the error System Failure is returned in the MAP_UPDATE_GPRS_LOCATION response and the process terminates; OK, indicating successful outcome of downloading the subscriber data to the SGSN.
1008 The SUBSCRIBER_PRESENT_HLR process is then started to alert the Short Message Service Centre, if required (see 1009 clause 19.1.7). 1010 Finally the HLR number is returned in the MAP_UPDATE_GPRS_LOCATION response.
1588
1589
1011 In all cases where the HLR sends a MAP_UPDATE_GPRS_LOCATION response to the SGSN, the dialogue towards 1012 the SGSN is terminated by a MAP_CLOSE request with parameter Release Method indicating Normal Release.
Process Update_Location_HLR
Process in the HLR MAP Protocol Machine for handling Location Update Signals to/from the left are to/from the VLR Signals to/from the right are to/from the HLR Application
1(4)
WAIT_FOR_SERVICE_ PRIMITIVE
MAP_UPDATE_ LOCATION_Ind
Update Location
WAIT_FOR_ APPLICATION_ RESPONSE
Update_ Location_Ack
Update_Location_ Negative_Response
Insert_Subscriber_ Data
Activate_Trace_ Mode
Set Result
Set Error
MAP_ACTIVATE_ TRACE_MODE_ Req.
MAP_UPDATE_ LOCATION_Rsp. MAP_CLOSE_Req.
MAP_UPDATE_ LOCATION_Rsp. MAP_CLOSE_Req.
WAIT_FOR_ ATM_Cnf
1013
1014
Figure 19.1.1/9 (sheet 1 of 4): Process Update_Location_HLR
1590
1591
Process Update_Location_HLR
Process in the HLR MAP Protocol Machine for handling Location Update WAIT_FOR_ ATM_Cnf
2(4)
Signals to/from the left are to/from the VLR Signals to/from the right are to/from the HLR Application
MAP_AT M_Cnf.
MAP_NOTICE_ Ind
MAP_U_ABORT _Ind MAP_P_ABORT _Ind MAP_CLOSE_Ind
MAP_CLOSE_ Req
Abort
Set Negative Response to System Failure
Update Location Negative R esponse
Check Confir mation
See 3G TS 29.002 Chapter 25.2.2
Pass
Provider Err or Data Error
User Error
ATM_ack.
Set Negative Response System Failure
Map User Error to Negative Response
WAIT_FOR_ SERVICE_PRIMITIVE
ATM Negative Response
WAIT_FOR_ APPLICATION_ RESPONSE
1015
1016
Figure 19.1.1/9 (sheet 2 of 4): Process Update_Location_HLR
1592
1593
Process Update_Location_HLR
Process in the HLR MAP Protocol Machine for handling Location Update
3(4)
Signals to/from the left are to/from the VLR Signals to/from the right are to/from the HLR Application
MAP_Insert_Subscriber_Data_Req MAP_Delimiter _Req
WAIT_F OR_ISD_Cnf_ OR_APPLICATION_ RESPONSE
MAP_Insert_Subscriber_ Data_Cnf
MAP_U_ABORT_Ind MAP_P_ABORT_Ind MAP_CLOSE_Ind
MAP_NOTICE_ Ind
Check Confirmation
See 3G TS 29.002 Chapter 25.2.2
Abort
Set Negative Result System Failure
ISD Negative R esponse
WAIT _FOR_ISD_Cnf_ OR_APPLICATION_ RESPONSE
OK
Pr ovider Err or Data Error
User Error
Inser t Subscr iber Data ack.
Set Negative Response System Failure
Map User Error to Negative Response
WAIT_FOR_ APPLICATION_ RESPONSE
ISD Negative Response
WAIT_FOR_ APPLICATION_ RESPONSE
1017
1018
Figure 19.1.1/9 (sheet 3 of 4): Process Update_Location_HLR
1594
1595
Process Update_Location_HLR
Process in the HLR MAP Protocol Machine for handling Location Update
4(4)
Signals to/from the left are to/from the VLR Signals to/from the right are to/from the HLR Application
WAIT _F OR_ISD_Cnf_ OR_APPLICATION_ RESPONSE
Update Location Ack
Update Location Negative R esponse
Insert Subscriber Data
Set Result
Set Error
MAP_UPDAT E_ LOCATION_Rsp
MAP_CLOSE_Req.
1019
1020
Figure 19.1.1/9 (sheet 4 of 4): Process Update_Location_HLR
1596
1597
Process Update_GPRS_ Location_ HLR
Fig ure 1 9.1 .1/ 19 : GP RS Lo cat ion U pd at in g in th e H LR
19.1.1_19.1(2)
Sig na ls to /fro m t he left a re to /f ro m the SG SN N U LL
W AIT _ F OR _ SER VI CE _ PR IM IT IVE R e ceive _ O pe n _In d MA P_U PD A T E_G PR S_ LO CA T IO N _I nd 'OK ' 'V r' W A IT _F O R _ S ER VIC E_ P RI MIT I VE 'Error'
F ig ure 25 .1/ 1
C he ck_ In dicat ion
S ee also th is sta te o n s hee t 2
N UL L
N UL L
OK No Su bscribe r kno wn Y es n on -G PR S only N et wo rk Acce ss Mo de GP RS -o nly or bo th Se t su bscribe r trac in g = de a ct iv e in SG SN Set D iag no stic= "GPR S S ub scrip tion U nkn ow n" S et Dia gn o st ic= "I MSI U n kno w n" Erro r
2 N ew SG S N Ye s No Su per_C harge d _ Ca nc el_L oc ation _ HL R See T S 23 .11 6 S et UE = U n know n S ub scrib er
M AP_ U PD AT E_ GPR S_ LO C AT ION _R sp M AP_ CL OSE _R e q Yes R esu lt:= Pa ss?
No Ca nc el_G PR S Lo catio n_ H LR F ig u re 1 9.1 .2/ 4 N UL L
Su bscribe r allo we d t o ro am into P LM N Ye s U pda te R out ing In fo
No
S et U E= R oam ing N o t Allo we d
1 Pa ge 2
D e lete R out in g I nf o
1021
1022
Figure 19.1.1/19 (sheet 1 of 2): Process Update_GPRS_Location_HLR
1598
1599
Process Update_GPRS_ Location_ HLR
Fig ure 1 9.1 .1/ 19 : GP RS Lo cat ion U pd at in g in th e H LR S ig n als to /fro m t he left a re t o/fro m t he H LR 1
19.1.1_19.2(2)
Re set F la g MS Purg ed Fo r G P RS
Co nt ro l_T racin g_ HL R_ w ith_ SGS N
F ig ure 25 .9/ 4
OK Erro r Sup er_C h arge d_ Lo ca tio n_ Up d ating _ HL R
S ee T S 23 .11 6
N U LL
Yes
Re sult: = P ass? No Inse rt _Su b sc rib er _D at a_ In_ SGS N _F ram ed _H L R OK Erro r 'Se t_e rro r_to _ _ Syste m_ _ F ailu re '
F ig ure 19 .4/ 1
Ab orte d
'Su bscrib er_ prese nt_ H LR '
F ig ure 19 .1 .1/ 13
N UL L
M AP _U PD AT E _GP RS _L OC AT ION _ R sp , M AP_ C LOS E_R e q
NU LL
W AIT _ F OR _ SER VI CE _ PR IM IT IVE
MAP _P _A BOR T _In d
M A P_N O T IC E_In d
M AP _C LO S E_ Re q
NU L L
1023
1024
Figure 19.1.1/19 (sheet 2 of 2): Process Update_GPRS_Location_HLR
1600
1601
1025 19.1.1.5 1026 19.1.1.5.1
1027 1028 1029 1030
Send Identification
General
This service is invoked by the VLR when it receives Update location from the MSC indicating that the subscriber was registered in a different VLR (henceforth called the Previous VLR, PVLR). If the identity of the PVLR is derivable for the VLR (usually if both are within the same network), the IMSI and authentication sets are requested from the PVLR (see clause 19.1.1.3), using the service described in clause 8.1.4.
1031 If the version negotiation between R99 VLR and pre-R99 PVLR leads to the MAP version 1 or 2, the VLR shall request 1032 authentication sets from the HLR.
1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047
+----+ G +----+ VLR -------+---------PVLR +----+ +----+ MAP_SEND_ ----------------------> IDENTIFICATION MAP_SEND_ <---------------------- IDENTIFICATION ack (see NOTE2)
NOTE1: NOTE2: The service shown in dotted lines indicates the trigger provided by other MAP signalling. Several MAP_SEND_IDENTIFICATION request/response may be used if message segmentation is required.
1053
1049 1050 1051 1052
Figure 19.1.1/10: Interface and services for Send Identification
1054 19.1.1.5.2
Detailed procedure in the VLR
1055 The VLR procedure is part of the location area updating process described in clause 19.1.1.X.
1056 19.1.1.5.3
Detailed procedure in the PVLR
1057 On receipt of a dialogue request for the Send Identification procedure, (see Receive_Open_Ind macro in clause 25.1), 1058 the PVLR will: 1059 1060 1061
terminate the procedure in case of parameter problems; revert to the MAP version Vr procedure in case the VLR indicated version Vr protocol; or continue as below, if the dialogue is accepted.
1062 If the PVLR process receives a MAP_NOTICE indication, it terminates the dialogue by sending a MAP_CLOSE 1063 request. 1064 If the PVLR process receives a MAP_SEND_IDENTIFICATION indication from the VLR (see figure 19.1.1/11), it 1065 checks whether the subscriber identity provided is known: 1066 1067 1068
if so, the IMSI and - if available - authentication parameters for the subscriber are returned in the MAP_SEND_IDENTIFICATION response; if not, the error Unidentified Subscriber is returned in the MAP_SEND_IDENTIFICATION response.
1069 If the VLR has indicated that segmentation is prohibited then the PVLR sends a MAP_SEND_IDENTIFICATION 1070 response to the VLR by means of the TC-RESULT-L service and terminates the dialogue towards the VLR by a 1071 MAP_CLOSE request with parameter Release Method indicating Normal Release. 1072 If the VLR has not indicated that segmentation is prohibited then the PVLR sends a MAP_SEND_IDENTIFICATION 1073 response to the VLR by means of the TC-RESULT-L service, followed either by a MAP_DELIMITER if more
1602
1603
1074 authentication sets are to be returned, or by a MAP_CLOSE request with parameter Release Method indicating Normal 1075 Release.
Process Send_Identification_VLR
Process in the new VLR for retrie val of IMSI and authentication sets from the previous VLR Idle Signals to/from the left are to from the requesting process in the new VLR; signals to/from the right are to from the previous VLR
1(2)
Request IMSI MAP_OPEN_Req, MAP_SEND_IDENTIFICATION_Req, MAP_DELIMITER_Req Section 25.1 Receive_ Open_Cnf Error
OK
Vr
Wait_For_ PVLR_Response
Perform MAP Vr Dialogue
Request IMSI negative response Idle
MAP_SEND_ IDENTIFICATION_Cnf
Check Confirmation OK Wait
Section 25.2
Provider Error, User Error, Data Error MAP_DELIMITER_ Ind 1
MAP_CLOSE_ Ind
Request IMSI Ack
MAP_SEND_IDENTIFICATION_Req, MAP_DELIMITER_Req yes
IMSI received
no Request IMSI negative response
Idle
Wait_For_ PVLR_Response
Request IMSI Ack
Idle
1076
1077
Figure 19.1.1/XX (sheet 1 of 2): Process Send_Identification_VLR
1604
1605
Process Send_Identification_VLR
Process in the new VLR for retrie val of IMSI and authentication sets from the previous VLR Wait_For_ PVLR_Response Signals to/from the left are to from the requesting process in the new VLR; signals to/from the right are to from the previous VLR
2(2)
Abort
MAP_U_ABORT_ind, MAP_P_ABORT_ind, MAP_CLOSE_ind
MAP_NOTICE_ ind
MAP_CLOSE_ req
IMSI received yes
no
Request IMSI Ack result
Request IMSI negative response
Idle
1078
1079
Figure 19.1.1/XX (sheet 2 of 2): Process Send_Identification_VLR
1606
1607
Process Send_Identification_PVLR
Figure 19.1/11: Proc ess in the Previous VLR to handle an identification request Signals to/from the left are to from the new VLR. Signals to/from the right are to/from the PVLR Location Management application
1(2)
NULL
Receive_Open_ Ind OK Vr Error
Wait_For_ Service_ Primitive
Perform MAP Vr Dialogue
NULL
NULL
MAP_ NOTICE_Ind
MAP_SEND_IDENTIFICATION_Ind
MAP_ CLOSE_Req
Send Identification Wait for Application respons e Send Identification negative response MAP_NOTICE_ ind MAP_U_ABORT_ind MAP_CLOSE_ind MAP_P_ABORT_ind
NULL
Send Identification Ack 1
Set user error
MAP_CLOSE_ req
MAP_SEND_IDENTIFICATION_rsp MAP_CLOSE_req
Set negative respons e
NULL
NULL
1080
1081
Figure 19.1.1/XX (sheet 1 of 2): Process Send_Identification_PVLR
1608
1609
Process Send_Identification_PVLR
Figure 19.1/11: Proc ess in the Previous VLR to handle an identification request Signals to/from the left are to/from the new VLR
2(2)
MAP_SEND_IDENTIF ICATION_rsp
no yes
more authenticatio n sets to send?
segmentation allowed no MAP_CLOSE_ req Wait for further requests MAP_SEND_ IDENTIFICATION_ ind MAP_NOTICE_ MAP_U_ABORT_ind MAP_CLOSE_ind ind MAP_P_ABORT_ind MAP_CLOSE_ req yes MAP_DELIMITER_req
NULL
NULL
1082
1083
Figure 19.1.1/XX (sheet 2 of 2): Process Send_Identification_PVLR
1610
1611
1084 19.1.1.6
1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100
Process Update Location VLR
This process is started by some other MAP user process in the case the HLR need to be updated due to previous network failure. It is invoked when the subscriber accesses the network, e.g. for mobile originated call set-up, response to paging or supplementary services handling. Here, location updating consists only of invoking the macro VLR_Update_HLR described above (see clause 19.1.1.3), which performs HLR updating and downloading of subscriber data. If updating is successful (OK), the HLR Number is received in the MAP_UPDATE_LOCATION confirm primitive; the register will be updated and the SCP will be informed about the Mobility Management event. The process then terminates. In the above case, the notification sent to the gsmSCF shall be Location Update to new VLR Service Area. If one of the errors Roaming not Allowed or Unknown Subscriber is received instead, all subscriber data are deleted from the VLR before the process terminates. In the case some other error occurs during HLR updating, the process simply terminates. Note, in all error cases the initiating restoration flags in VLR remain false, therefore a new HLR updating attempt will be started later on. NOTE 1: This process will be performed independent from the calling process, no coordination is required. NOTE 2: The procedure Notify_gsmSCF is specified in 3GPP TS 23.078.
1612
1613
Process Update_Location_VLR
19.1.1_12(1 )
NULL
VLR_ _update_ _HLR
Roaming_Not_Allowed
Unknown_Subscriber
Procedure_Error
Aborted
OK
'Set_HLR_ _cnf_ind_to_ _not_confirmed'
'Delete_MS'
'Delete_MS'
'Update_ _register'
Notify = update to new VLR service area
Notify gsmSCF
3G TS 23.078
Figure Location updating 19.1.1/12: initiated VLR process by VLR:
1101
1102
Figure 19.1.1/12: Process UL_VLR
1614
1615
1103 19.1.1.8
Detailed procedure in the SGSN
1104 Figure 19.1.1/20 shows the MAP process for updating of the SGSN. The following general macros are used: 1105 1106 1107 1108 1109
Receive_Open_Cnf Insert_Subscriber_Data_SGSN Activate_Tracing_SGSN
clause 25.1; clause 25.7; clause 25.9;
Sheet 2: The procedure Check_User_Error_In_Serving_Network_Entity is specific to Super-Charger; it is specified in 3GPP TS 23.116 [110].
1113 The location updating process 1114 1115 1116 1117
The MAP process receives an Update HLR request from the relevant process in the SGSN (see 3GPP TS 23.060 [104]) to perform HLR updating. If the SGSN does not know the subscribers HLR (e.g. no IMSI translation exists as there are not yet any SS7 links to the subscribers HPLMN), the Update HLR negative response with error Unknown HLR is returned to the requesting process.
1118 If the subscribers HLR can be reached, the SGSN opens a dialogue towards the HLR by sending a MAP_OPEN request 1119 without any user specific parameters, together with a MAP_UPDATE_GPRS_LOCATION request containing the 1120 parameters 1121 1122
IMSI, identifying the subscriber; SGSN Address and SGSN number.
1123 In case the HLR rejects dialogue opening (see clause 25.1) or indicates version Vr protocol to be used, the SGSN will 1124 terminate the process indicating Update HLR negative response to the requesting process. 1125 If the HLR accepts the dialogue, the HLR will respond with: 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142
a MAP_INSERT_SUBSCRIBER_DATA indication, handled by the macro Insert_Subs_Data_SGSN defined in clause 25.7; The HLR may repeat this service several times depending on the amount of data to be transferred to the SGSN and to replace subscription data in case they are not supported by the SGSN.
NOTE: -
a MAP_ACTIVATE_TRACE_MODE indication, handled by the macro Activate_Tracing_SGSN defined in clause 25.9; the MAP_UPDATE_GPRS_LOCATION confirmation: if this confirmation contains the HLR Number, this indicates that the HLR has passed all information and that updating has been successfully completed. The Update HLR response message is returned to the requesting process for completion of the SGSN updating (see 3GPP TS 23.060 [104]). if the confirmation contains an User error cause (Unknown Subscriber, Roaming Not Allowed or some other), the corresponding error is returned to the requesting process in the Update HLR negative response .
a MAP_P_ABORT, MAP_U_ABORT, or MAP_CLOSE indication. In these cases, the corresponding error is returned to the requesting process in the Update HLR negative response . a MAP_NOTICE indication. Then, the dialogue towards the HLR is terminated, and the HLR Update negative response with the appropriate error is returned to the requesting process.
1616
1617
Process SGSN_Update_HLR
Figure 19.1.1/20: HLR updating in SGSN
19.1.1_20.1(2)
Signals from/to the left are from/to requesting process in SGSN Signals to/from the right are to/from the HLR
Idle
Update HLR Request
from requesting process see 3GPP TS 23.060
('no')
'Unknown_ HLR'
(yes)
MAP_OPEN_Req, MAP_UPDATE_GPRS_LOCATION_Req, MAP_DELIMITER_Req Receive_ Open_cnf OK
Set Error
Unknown HLR
Error, Vr Set Error Procedure Error
Update HLR NegativeResponse
to requesting process see 3GPP TS 23.060
Idle
Update HLR NegativeResponse
to requesting process see 3GPP TS 23.060
WAIT_FOR _DATA
Idle
1143
1144
Figure 19.1.1/20 (sheet 1 of 2): Process SGSN_Update_HLR
1618
1619
Process SGSN_Update_ HLR
Fig ure 1 9.1 .1/ 20 : H L R u pd at in g in SGSN
19.1.1_20.2(2)
S igna l from /to t he le ft a re f ro m/ to req u est in g p roce ss in SGS N S ign als to /f ro m th e rig ht a re t o/fro m t he H LR
W AIT _ F OR _D AT A
In sert_ Sub s_ D ata _SG SN
F igu re 2 5.7 /6
Activa te_ Tra cing_ SG SN
Fig ure 25 .9/ 7
M AP_ U PD AT E_ GPR S_ L OC AT IO N _ _C n f
W AIT _ F OR _ D AT A
W AIT _ F OR _ DA TA
C he ck_ _C o nfirma tio n
U ser E rro r
Prov id e r E rro r, D ata E rror
OK
Se t R e sult Se e T S 2 3.1 16 Ch eck_ U ser_E rro r_ In_ Se rvin g_ N etw ork_ Entit y S et Erro r
Set Error
U pd at e H L R R esp o nse
to req ue sting pro cess see GS M 03. 60
U p da te H LR N e ga tiveR e spo nse
to re que stin g proce ss se e G SM 0 3.6 0
W AIT _ F OR D AT A
Idle
M AP_ N OT IC E_I nd
MAP _U _ ABO R T _I nd , MAP _P _AB OR T _In d, MAP _C L OSE _In d
A bo rt
f ro m re qu est ing proce ss se e T S GS M 03. 60
MA P_C L O SE_ R eq
M AP _U _A BOR T _ Req
t o HL R
Se t E rror
Pro ced ure Erro r
U pd ate H L R N eg ativ eR esp on se
to re q uest ing proc ess see GSM 0 3.6 0
Id le
1145
1146
Figure 19.1.1/20 (sheet 2 of 2): Process SGSN_Update_HLR
1620
1621
1147 1148 19.1.2.1
1149 1150 1151 1152 1153 1154
19.1.2 Location Cancellation
General
The purpose of this process is to delete a subscriber's record from a previous visitor location register after she has registered with a new visitor location register. Also this process is used to delete a subscriber's record from a old SGSN after she has registered with a SGSN. The procedure may also be used if the subscriber's record is to be deleted for other operator determined purposes, e.g. withdrawal of subscription, imposition of roaming restrictions or modifications to the subscription which result in roaming restrictions. Location cancellation can be used to enforce location updating including updating of subscriber data in the VLR or in the SGSN at the next subscriber access.
1155 In all cases, the process is performed independently of the invoking process (e.g. Location Updating). 1156 1157 1158 1159 1160 1161
1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176
The service as described in clause 8.1.3 is invoked when an HLR receives a MAP_UPDATE_LOCATION indication from a VLR other than that stored in its table for this subscriber. Also the MAP_CANCEL_LOCATION service is invoked when the HLR receives a MAP_UPDATE_GPRS_LOCATION indication from a SGSN other than stored in its table for this subscriber. Additionally the service may be invoked by operator intervention. The MAP_CANCEL_LOCATION service is in any case invoked towards the VLR or the SGSN whose identity is contained in the HLR table. +----+ D +----+ D +----+ VLR +-----------+------------HLR -------+---------PVLR +----+ +----+ +----+ MAP_UPDATE_LOCATION ----------------------------> MAP_CANCEL_ ---------------------> LOCATION MAP_CANCEL_LOCATION <--------------------- ack
NOTE: The service shown in dotted lines indicates the trigger provided by other MAP signalling.
1180
1178 1179
Figure 19.1.2/1: Interface and services for Location Cancellation
1181 19.1.2.2
1182 1183 1184 1185 1186 1187 1188 1189
Detailed procedure in the HLR
The location cancellation process is started by an external process as stated above. The HLR opens a dialogue with the VLR or with the SGSN whose identity is contained in the HLR table (MAP_OPEN request without any user specific parameters), sending the MAP_CANCEL_LOCATION request primitive (see figures 19.1.2/2 and 19.1.2/4), containing the parameters: IMSI, to identify the subscriber to be deleted from that VLR or SGSN; LMSI, which is included if available in the HLR. LMSI is not applicable between HLR and SGSN; Cancellation Type if the Cancel Location is sent to SGSN. Cancellation Type is not applicable between HLR and VLR. If the VLR receives this parameter and does not understand it, this parameter shall be ignored.
1190 19.1.2.3
Detailed procedure in the VLR
1622
1623
Process Cancel_Location_HLR
Process in the HLR MAP Protocol Machine for handling Location Cancellation
1(2)
Signals to/from the left are to/from the VLR Signals to/from the right are to/from the HLR Application
NULL
Cancel Location
MAP_OPEN_Req MAP_CANCEL_LOCAT ION_Req MAP_DELIMITER_Req
Receive Open Cnf. OK Vr
See 3G TS 29.002 Chapter 25.1.2
Error
WAIT_FOR_ ACK
Perform_MAP_ Vr_Dialogue
Set Negative Response to System Failure
NULL
Cancel Location Negative R esponse
NULL
1191
1192
Figure 19.1.2/2 (Sheet 1 of 2): Process Cancel_Location_HLR
1624
1625
Process Cancel_Location_HLR
Process in the HLR MAP Protocol Machine for handling Location Cancellation
2(2)
Signals to/from the left are to/from the VLR Signals to/from the right are to/from the HLR Application
WAIT_FOR_ ACK
MAP_CANCEL_ LOCATION_Cnf
MAP_P_ ABORT_Ind
MAP_ NOTICE_ Ind
Abort
MAP_CLOSE_ Req
Check_ Confirmation
See 3G TS 29.002 Chapter 25.2.2
NULL
Set Negative Response to System Failure
OK
Provider Error Data Error
Error Cancel Location Negative R esponse
Cancel Location Ack
Set Negative Response: System Failure
Map User Error to Negative Response
NULL
NULL
Cancel Location Negative R esponse
Cancel Location Negative R esponse
NULL
NULL
1193
1194
Figure 19.1.2/2 (Sheet 2 of 2): Process Cancel_Location_HLR
1626
1627
Process Cancel_Location_VLR
Process in the VLR for handling the Cancel location
1(1)
Signals to/from the left are to/from Location Management application Signals to/from the right are to/from the H LR MAP protocol machine.
NULL
Receive Open Ind.
OK
Vr
Error
WAIT_FOR_SERVICE_ PRIMITIVE
Perform_MAP_ Vr_Dialogue
NULL
NULL
MAP_NOTICE_ Ind
MAP_CANCEL_ LOCATION _Ind
MAP_CLOSE_ Req
Cancel Location
NULL
WAIT_FOR_ APPLICATION_ RESPONSE
Cancel location Ack
Cancel location Negative R esponse
Set result
Cancel Location Negative response
MAP_CANCEL_ LOCATION_Rsp MAP_CLOSE_Req
MAP_CANCEL_ LOCATION_Rsp MAP_CLOSE_Req
NULL
1195
1196
Figure 19.1.2/3: Process Cancel_Location_VLR
1197 19.1.2.4
-
Detailed procedure in the SGSN
1198 Opening of the dialogue is described in the macro Receive_Open_Ind in clause 25.1, with outcomes: 1199 1200
procedure termination; or dialogue acceptance, with processing as below.
1201 If the SGSN process receives a MAP_NOTICE indication, it terminates the dialogue by sending a MAP_CLOSE 1202 request.
1628
1629
1203 If the SGSN process receives a MAP_CANCEL_LOCATION indication from the HLR (see figure 19.1.2/4), the 1204 parameters are checked first (macro Check_Indication, see clause 25.2). In case of parameter problems the appropriate 1205 error is sent in the MAP_CANCEL_LOCATION response. 1206 Thereafter the SGSN checks whether the subscriber identity provided is known in the SGSN: 1207 1208 1209 1210
if so, the data of the subscriber are deleted from SGSN table and a MAP_CANCEL_LOCATION response is returned without any parameters; if not, location cancellation is regarded as being successful, too, and the MAP_CANCEL_LOCATION response is returned without any parameters.
1211 In either case, after sending the MAP_CANCEL_LOCATION response the SGSN process releases any P-TMSI which 1212 may be associated with the IMSI of the subscriber, terminates the dialogue (MAP_CLOSE with Release Method 1213 Normal Release) and returns to the idle state.
1630
1631
Pro cess Ca ncel_G PR S_Location _HLR
F ig u re 1 9. 1. 2 /4: Lo c a tio n C a n c ella tio n in t h e H LR f or G P R S
19.1.2_4(1 )
M A P _ O P E N _R e q, M A P _ C A N C E L_ L O C A T IO N _ R e q , M A P _ D E LIM IT E R _ R e q
R e c eiv e_ O pe n _c nf
OK W A IT _ F O R _ ACK
E rro r, V r
M AP _ C A N C E L _ LO C A T I O N _ Cn f
MAP_P_ A B ORT _ In d
M A P _ N O T IC E _ Ind
C h ec k _ C o n firm at io n
M A P _ CL O S E Re q
O .K .
P ro vid e r E rro r, U se r E r ror, D ata E r ro r R e pe at lo c a tio n c a n c ella tion ye s W a it fo r rep et itio n tim e r ex piry
no
1214
1215
Figure 19.1.2/4: Process Cancel_GPRS_Location_HLR
1632
1633
Pro cess Ca nc el_Locatio n_SG SN
F ig ure 1 9.1 .2 /5 : L o c at ion C an c e lla tio n in th e S G S N
19.1.2_5(1 )
N U LL
R e c eiv e_ O p en _In d
OK W ait_ F o r_ S e rvic e _ P rim itiv e
E rro r, V r N UL L
M A P _C A N C E L _ L O C A T IO N _ Ind
MAP_ N O T IC E _ In d
C h ec k _ In d ic a tio n
MAP_ C LOSE_ R eq Erro r no N U LL
OK S u bs c rib e r reg is tere d y es
D ele te s ub s c rib er from r egis ter
R e lea se P -T M S I
M A P _ C A N C E L _ LO C A T IO N _R sp M A P _ CL O S E _ Re q
N UL L
1216
1217
Figure 19.1.2/5: Process Cancel_Location_SGSN
1218
19.1.3 Void
1634
1635
1219 19.1.3.1 1220 19.1.3.2 1221 19.1.3.3 1222 1223 19.1.4.1
1224 1225 1226 1227 1228 1229
Void Void Void
19.1.4 Purge MS
General
When the VLR or the SGSN receives an indication on the O&M interface that the MS record is to be purged (either because of administrative action or because the MS has been inactive for an extended period), this procedure invokes the MAP_PURGE_MS service described in clause 8.1.6 to request the HLR to set the "MS purged for non-GPRS" or the MS purged for GPRS flag for the 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. The message flows are shown in figures 19.1.4/1and 19.1.4/5.
1230 It is optional for the network operator to delete MS records from the VLR or from the SGSN, but if the option is used 1231 the VLR or the SGSN shall notify the HLR when a record has been deleted. 1232 The O&M process in the VLR or in the SGSN must ensure that during the MS purging procedure any other attempt to 1233 access the MS record is blocked, to maintain consistency of data.
1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244
+-----+ D +-----+ VLR +--------|----------- HLR +-----+ +-----+ MAP_PURGE_MS -------------------------> MAP_PURGE_MS_ack <------------------------- Figure 19.1.4/1: MAP-D Interface and services for MAP_PURGE_MS +-----+ Gr +-----+ SGSN+--------|----------- HLR +-----+ +-----+ MAP_PURGE_MS -------------------------> MAP_PURGE_MS_ack <------------------------- Figure 19.1.4/5: Gr Interface and services for MAP_PURGE_MS
1246
1247
1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258
1260
1261 19.1.4.2 1262 19.1.4.3 1263 19.1.4.4
Void Void Detailed procedure in the SGSN
1264 Figure 19.1.4/4 shows the MAP process in the SGSN to notify the HLR that an MS record has been purged. The 1265 following general macro is used: 1266
Receive_Open_Cnf
clause 25.1;
1636
1637
1267 Sheet 1: The procedure Purge_MS_In_Serving_Network_Entity is specific to Super-Charger; it is specified in 3GPP 1268 TS 23.116 [110]. If the SGSN and the originating HLR support the Super-Charger functionality, processing continues 1269 from the "Yes" exit of the test "Result=Pass?". 1270 When the SGSN receives an indication from O&M that an MS record is to be purged, it invokes the MAP_PURGE_MS 1271 service. 1272 The SGSN opens the dialogue to the HLR with a MAP_OPEN request containing no user specific parameters. The 1273 MAP_PURGE_MS request contains the IMSI of the MS which is to be purged and the SGSN number. 1274 The SGSN then waits for the MAP_OPEN confirmation indicating one of: 1275 1276 1277
rejection of the dialogue (process terminates); reversion to Vr (process terminates); dialogue acceptance.
1278 If the HLR accepts the dialogue it returns a MAP_PURGE_MS confirmation, containing no parameter, indicating 1279 successful outcome of the procedure. 1280 1281 1282 1283
If a MAP_PURGE_MS confirmation containing a provider error, data error or user error, or a MAP_P_ABORT, MAP_NOTICE or premature MAP_CLOSE indication, has been received, the failure is reported to the O&M interface. Successful outcome of the procedure leads to deletion of the subscriber data and freezing of the P-TMSI if so requested by the HLR, and is reported to the O&M interface.
1638
1639
Process Purge_MS_VLR
Process in the VLR for handling purge MS
1(1)
Signals to/from the left are to/from Location Management application Signals to/from the right are to/from the H LR MAP protocol machine.
NULL
Purge MS
MAP_OPEN_Req MAP_PURGE_MS_Req MAP_DELIMITER_Req
Receive Open Cnf.
OK
Vr Perform_MAP_ Vr_Dialogue
Error Purge MS Negative R esponse
WAIT_FOR_ ACK
NULL
NULL
MAP_PURGE_MS_ cnf
MAP_P_ABORT _ ind
MAP_NOTICE_ ind
MAP_CLOSE_ req Check_ Confirmation
OK
Provider Error Data Error Set Negative Response System F ailur e
User Error
Map User Error to Negative Response
Set Negative Response System F ailure
Purge MS negative response Purge MS Ack
NULL
NULL
1284
1285
Figure 19.1.4/2: Process Purge_MS_VLR
1640
1641
Process Purge_MS_HLR
Process in the HLR MAP Protocol Machine for handling the Purging of an MS
1(2)
Signals to/from the left are to/from the VLR Signals to/from the right ar e to/from the HLR Application
NULL
Receive Open Ind. OK V2
See TS 29.002 Chapter 25.1.2
V1 Error
WAIT_FOR_SERVICE_ PRIMITIVE
Per form_MAP_ Vr_Dialogue
NULL
NULL
MAP_NOTICE_ Ind
MAP_PURGE_ MS_Ind
MAP_CLOSE_ Req
Purge MS
NULL
WAIT_FOR_ APPLICATION_ RESPONSE
1286
1287
Figure 19.1.4/3 (Sheet 1 of 2): Process Purge_MS_HLR
1642
1643
Process Purge_MS_HLR
Process in the HLR MAP Protocol Machine for handling the Purging of an MS Signals to/from the left are to/from the VLR Signals to/from the right are to/from the HLR Application
2(2)
WAIT_FOR_ APPLICATION_ RESPONSE
Purge MS Ack
Purge MS Negative R esponse
Set Result
Map Negative Response to User Error
MAP_PURGE_ MS_R sp MAP_CLOSE_Req
MAP_PURGE_ MS_R sp MAP_CLOSE_Req
NULL
1288
1289
Figure 19.1.4/3 (Sheet 2 of 2): Process Purge_MS_HLR
1644
1645
Proc ess Purge_MS_SGSN
F igure 1 9.1 .4 /4: Proce ss in the S G SN t o n otif y the H LR th at an M S r eco rd h as b e en pu rg ed
19.1.4_4(1)
Nu ll
O M_ PU R GE_ M S_ Re q
Purg e_M S_ In_ Serv in g_ Ne tw ork _ Entity
S ee T S 23 .11 6
Re sult: = P ass? Ye s No M AP _OP EN _R eq M AP_ PU R GE_ MS _R eq M AP_ DE LI MIT E R_ R eq
R e ceive_ O pen _ Cn f
OK
Vr, Erro r
W ait_ fo r_ R esp on se
MAP _PU R GE _ MS_ C nf
M AP_ N O TIC E _In d
M AP_ P_ AB O R T_In d
Ch ec k_ _C on fir mat ion
M AP _C L O SE Re q
OK U ser E rror, Prov id e r Erro r, D ata E rror
De let e Sub scribe r Da ta
Ye s P-TM SI to be fr oze n?
Se t Pu r gin g Fa ile d 1
Fre eze P-T MS I
No
Set Purg ing Suc ce ssfu l
OM_ PU R G E_ M S_R sp
N ull
1290
1291
Figure 19.1.4/4: Process Purge_MS_SGSN
1292
19.2 Handover procedure
1293 It should be noted that procedures related to the B-interface have not been updated for Release 99. The B-interface is 1294 not fully operational specified. It is strongly recommended not to implement the B-interface as an external interface.
1646
1647
1295
19.2.1 General
1296 The handover or relocation between different MSCs is called Inter-MSC handover. The interfaces involved for Inter1297 MSC handover are shown in figure 19.2/1. Following two Inter-MSC handover procedures apply: 1298 1299 1300 1301 1302 1303 1304 1305 1306
1307 1308 1309
1) Basic Inter-MSC handover: The call is handed over from the controlling MSC, called MSC-A to another MSC, called MSC-B (figure 19.2/1a). Figure 19.2/2 shows a successful handover between MSC-A and MSC-B including a request for handover number allocation by MSC-B to VLR-B. 2) Subsequent Inter-MSC handover: After the call has been handed over from MSC-A to MSC-B, a handover to either MSC-A (figure 19.2/1a) or to a third MSC (MSC-B') (figure 19.2/1b) is necessary in order to continue the connection. Figure 19.2/3 shows a successful subsequent handover. +------+ E +------+ B +------+ MSC-A +---+---MSC-B +---+---VLR-B +------+ +------+ +------+ a) Basic handover procedure MSC-A to MSC-B and subsequent handover procedure MSC-B to MSC-A. +------+ E +------+ B +------+ MSC-A+---+---MSC-B +---+---VLR-B +------+ +------+ +------+ E +------+ B +------+ +-------+---MSC-B'+---+---VLR-B' +------+ +------+ b) Subsequent handover procedure MSC-B to MSC-B'. Figure 19.2/1: Interface structure for handover
1310 1311
1312 1313 1314 1315 1316 1317
1318 1319 1320
1321 The MAP handover procedures achieve the functionality required to set up an MSC-MSC dialogue, to optionally 1322 allocate a handover number or one or several relocation numbers and to transport BSSAP or RANAP messages. 1323 1324 Minimum applicable MAP AC for intersystem inter-MSC GSM BSS to UTRAN handover shall be MAP handover AC 1325 version 3. 1326 Minimum applicable MAP AC for intersystem inter-MSC UTRAN to GSM BSS handover shall be MAP handover AC 1327 version 2. 1328 Note: If MAP AC version 2 is used, subsequent handover to UTRAN is not possible. 1329 Minimum applicable MAP AC for inter-MSC GSM BSS to GSM BSS handover should be MAP handover AC version 1330 2. 1331 NOTE: 1332 1333 1334 1335 1336
If MAP AC version 2 or lower is used, subsequent handover to UTRAN is not possible.
The transported BSSAP or RANAP messages are controlled and handled by the Handover Control Application in the MSCs. This information will be transparent to the MAP protocol. If the MSC receives via the MAP protocol BSSAP or RANAP messages, this information will be forwarded to the Handover Control Application (shown in the handover SDL diagrams with the internal HO_CA signalling, it is an internal process in the MSC) and vice versa if the Handover Control Application requires the sending of BSSAP or RANAP messages via the MAP protocol.
1337 For detailed interworking between the A-interface and MAP procedures or the Iu-interface and MAP procedures, see 1338 3GPP TS 23.009 and 3GPP TS 29.010.
1648
1649
1339
1342
1340 1341
NOTE:
This can be sent at any time after the connection between MSC-A and MSC-B is established.
Figure 19.2/2: Example of a successful basic handover procedure to MSC-B
1650
1651
1343
1346
1344 1345
NOTE:
This can be sent at any time after the connection between MSC-A and MSC-B is established.
Figure 19.2/3: Example of a handover towards a third MSC
1652
1653
1347
19.2.2 Handover procedure in MSC-A
1348 This clause describes the handover or relocation procedure in MSC-A, including the request for a basic handover or 1349 relocation to another MSC (MSC-B), subsequent handover or relocation to a third MSC (MSC-B') or back to the 1350 controlling MSC (MSC-A).
1351 19.2.2.1
Basic handover
1352 When MSC-A has decided that a call has to be handed over or relocated to MSC-B, the Handover Control Application 1353 in MSC-A requests the MAP application to initiate the MAP_PREPARE_HANDOVER request to MSC-B. 1354 MSC-A opens the dialogue to MSC-B with a MAP_OPEN request containing no user specific parameters and sends a 1355 MAP_PREPARE_HANDOVER request. This request shall contain all the information required by MSC-B to allocate 1356 the necessary radio resources. In addition, it may optionally contain:
1357 1358 1359 1360 1361
1362
an indication that a handover number allocation is not required; the targetCellId, for compatibility reasons in the case of handover or inter-system handover to GSM ; the targetRNCId, in case of SRNS relocation or inter-system handover from GSM to UMTS; the IMSI; UMTS encryption information and UMTS integrity protection information, which are necessary parameters for inter-system handover from GSM to UMTS; GSM radio resource information (channel type) shall be included at inter-MSC relocation to prepare for a possible subsequent intra-MSC handover from UMTS to GSM in MSC-B.
1363
1364
1365 The conditions when these parameters shall be included and the processing of them in MSC-B (3G_MSC-B) are 1366 described in detail in 3GPP TS 29.010 and 23.009. 1367 1368 1369 1370
If MSC-B accepts the dialogue, it returns a MAP_PREPARE_HANDOVER confirmation containing a handover number or one or several relocation numbers, unless the request has included the HO-NumberNotRequired parameter, and BSSAP or RANAP information which is forwarded to and handled by the Handover Control Application in MSC-A.
1371 Optionally MSC-A can receive, after a MAP_PREPARE_HANDOVER confirmation, a 1372 MAP_PROCESS_ACCESS_SIGNALLING indication containing BSSAP or RANAP information. 1373 When the connection has been established between the MS and MSC-B, MSC-A will be informed by a 1374 MAP_SEND_END_SIGNAL indication. 1375 When MSC-A wants to clear the connection with BSS-B, an indication from the Handover Control Application is 1376 received in the Map Application to send the MAP_SEND_END-SIGNAL response to MSC-B to close the MAP 1377 dialogue. 1378 MSC-A may abort the handover or relocation procedure at any time (e.g. if the call is cleared).
1379 19.2.2.2
Handling of access signalling
1380 If required, the Handover Control Application in MSC-A requests the MAP application to invoke the 1381 MAP_FORWARD_ACCESS_SIGNALLING request containing the information to be transferred to the A-interface or 1382 the Iu-interface of MSC-B (e.g. call control information). 1383 MAP_FORWARD_ACCESS_SIGNALLING is a non-confirmed service. 1384 1385 1386 1387 1388 1389
MSC-B will then forward the required information to the Handover Control Application. The MAP_FORWARD_ACCESS_SIGNALLING is composed in such a way that the information can be passed transparently to the A-interface or the Iu-interface for call control and mobility management information. Any response received in MSC-B from the A-interface or the Iu-interface that should be brought to MSC-A will require a new independent request from the Handover Control Application in MSC-B to MSC-A by invoking a MAP_PROCESS_ACCESS_SIGNALLING request.
1654
1655
1390 19.2.2.3
1391 1392 1393 1394
Other procedures in stable handover situation
During a call and after handover or relocation, a number of procedures between MSC-A and BSS-B or RNS-B controlled by or reported to MSC-A may be initiated in both directions by invoking a MAP_FORWARD_ACCESS_SIGNALLING request and reception of a MAP_PROCESS_ACCESS_SIGNALLING indication.
1395 19.2.2.4
1396 1397 1398 1399
Subsequent handover
When MSC-A receives a MAP_PREPARE_SUBSEQUENT_HANDOVER request, it will start the procedure of handing or relocating the call over to a third MSC (MSC-B'), or back to the controlling MSC (MSC-A). If the new handover or relocation procedure towards MSC-B' or MSC-A is successful, the handover control application in MSC-A will request the release of the dialogue towards MSC-B by sending the MAP_SEND_END_SIGNAL confirmation.
1400 19.2.2.5
SDL Diagrams
1401 The SDL diagrams on the following pages describe the user processes in MSC-A for the procedures described in this 1402 clause. 1403 The services used are defined in clause 8.4. 1404 1405 1406 1407
NOTE:
The message primitives HO_CA_MESSAGE used in the SDL-Diagrams are used to show the internal coordination between the MAP application and the Handover Control Application. For a detailed description of the co-ordination between the applications for the handover or relocation procedure, see 3GPP TS 23.009.
1408 Note that in case of reception of errors from the MSCs (see the Handover error handling macro), the MAP user reports 1409 them to the Handover Control Application and does not take any action except in cases explicitly mentioned in the SDL 1410 diagrams.
1656
1657
Process MSC_A_HO
Figure 19.2 2/1: HO in MSC-A
19.2.2_1.1(13)
NULL
HO_CA_MESSAGE_ind, see NOTE 1, [Handover request] 2 MAP_OPEN_req MAP_PREPARE_HANDOVER_req MAP_DELIMITER_req Receive_Open Cnf Ok See subclause 25.1
NULL
Vr
Error
Perform MAP Vr Dialogue Wait_for PH_result NULL
HO_CA_MESSAGE_req, see NOTE 1
MAP_PREPARE_HANDOVER_cnf
See subclause 19.2.4 Provider error User error Data error
Receive_error from HO_CA or MSC Null, Error
Check_ Confirmation Ok
See subclause 25.2
HO_CA_MESSAGE_req. see NOTE 1 Yes No 1
MAP_U_ABORT_req. see NOTE 1
multiple bearer not supported indicated?
Wait_for_ HO_completion on MSC-B
NULL
1411
1412
Figure 19.2.2/1 (sheet 1 of 13): Process MSC_A_HO
1658
1659
Process MSC_A_HO
Figure 19.2 2/1: HO in MSC-A
19.2.2_1.2(13)
Wait_for Resend
HO_CA_MESSAGE_ind. see NOTE 1. [Handover request]
Receive_error from HO_CA or MSC Null, Error
MAP_PREPARE_HANDOVER_req MAP_DELIMITER_req
NULL
1413
1414
Figure 19.2.2/1 (sheet 2 of 13): Process MSC_A_HO
1660
1661
Process MSC_A_HO
Figure 19.2 2/1: HO in MSC-A
19.2.2_1.3(13)
Wait_for_ HO_Completion on MSC-B HO_CA_MESSAGE_ ind, see NOTE 1, [Message transfer] MAP_FORWARD_ACCESS_ SIGNALLING_req MAP_DELIMITER_req Wait_for_ HO_Completion on MSC-B Receive_error from HO_CA or MSC Error See subclause 19.2.4 Null
Wait_for_ HO_Completion on MSC-B
NULL
MAP_SEND_END_ SIGNAL_ind
Check_ Indication Ok
See subclause 25.2 Error
MAP_PROCESS_ACCESS_ SIGNALLING_ind
Check_ Indication Ok
See subclause 25.2 Error Wait_for_ HO_Completion on MSC-B HO_CA_MESSAGE_ req, see NOTE 1, [Message transfer]
HO_CA_MESSAGE_ req, see NOTE 1, [Handover complete] MAP_U_ABORT_req
Wait_for_ HO_Completion on MSC-B Call on MSC-B NULL
1415
1416
Figure 19.2.2/1 (sheet 3 of 13): Process MSC_A_HO
1662
1663
Process MSC_A_HO
Figure 19.2 2/1: HO in MSC-A
19.2.2_1.4(13)
Call on MSC-B Receive_error from HO_CA or MSC Error See subclause 19.2.4 Null
Call on MSC-B
NULL
HO_CA_MESSAGE_ ind, see NOTE 1, [Message transfer] MAP_FORWARD_ACCESS_ SIGNALLING_req MAP_DELIMITER_req Error Check_ Indication Ok
MAP_PROCESS_ACCESS_ SIGNALLING_ind
See subclause 25.2
HO_CA_MESSAGE_ req, see NOTE 1, [Message transfer]
Call on MSC-B
Call on MSC-B
1417
1418
Figure 19.2.2/1 (sheet 4 of 13): Process MSC_A_HO
1664
1665
Process MSC_A_HO
Figure 19.2 2/1: HO in MSC-A
19.2.2_1.5(13)
Call on MSC-B HO_CA_MESSAGE_ ind, see NOTE 1, [HO Number required] MAP_PREPARE_ HANOVER_req MAP_DELIMITER_req HO_CA_MESSAGE_ ind, see NOTE 1, [Close connection] Wait_for_ HO_Number from MSC-B MAP_PREPARE_ SUBSEQUENT_HANDOVER_ind
MAP_SEND_END_SIGNAL_req MAP_CLOSE_req
Check_ Indication Ok
See subclause 25.2 Error
NULL
MSC known? Yes No Target MSC =MSC-A? Yes
No User Error := Unknown MSC
HO_CA_MESSAGE_ req, see NOTE 1, [Request for HO] Subcequent HO to a third MSC required Wait_for SUB_HO_ Indication
HO_CA_MESSAGE_ req, see NOTE 1, [Request for HO] Subcequent HO back to MSC-A MAP_PREPARE_ SUBSEQUENT_ HANOVER_rsp MAP_DELIMITER_req Call on MSC-B
Wait_for HO_Indication
1419
1420
Figure 19.2.2/1 (sheet 5 of 13): Process MSC_A_HO
1666
1667
Process MSC_A_HO
Figure 19.2 2/1: HO in MSC-A
19.2.2_1.6(13)
Wait_for_ HO_Number from MSC-B MAP_PREPARE_HANDOVER_cnf Receive_error from HO_CA or MSC Ok See subclause 19.2.4
Null
Check_ Confirmation Ok
See subclause 25.2
Provider error User error Data error
HO_NUMBER No present? Yes
HO_CA_MESSAGE_ req, see NOTE 1
Set HO-Number := present
Set HO-Number := not present
Call on MSC-B
NULL
HO_CA_MESSAGE_ req, see NOTE 1, [Routing information]
Call on MSC-B
1421
1422
Figure 19.2.2/1 (sheet 6 of 13): Process MSC_A_HO
1668
1669
Process MSC_A_HO
Figure 19.2 2/1: HO in MSC-A
19.2.2_1.7(13)
Wait_for_ HO_Indication
HO_CA_MESSAGE_ req, see NOTE 1, [HO preparation result] HO_CA_MESSAGE_ ind, see NOTE 1, [Message transfer] MAP_PREPARE_ SUBSEQUENT_ HANDOVER_rsp MAP_DELIMITER_req MAP_FORWARD_ ACCESS_ SIGNALLING_req MAP_DELIMITER_req Wait_for_ HO_Completion on MSC-A Wait_for_ HO_Indication HO_CA_MESSAGE_ req, see NOTE 1, [HO preparation result] Error
Receive_error from HO_CA or MSC Null
See subclause 19.2.4 Error
NULL
Call on MSC-B
MAP_PROCESS_ACCESS_ SIGNALLING_ind
Check_ Indication Ok
See subclause 25.2
MAP_SEND_END_ SIGNAL_rsp
HO_CA_MESSAGE_ req, see NOTE 1, [Message transfer]
Call on MSC-A
Wait_for_ HO_Indication
1423
1424
Figure 19.2.2/1 (sheet 7 of 13): Process MSC_A_HO
1670
1671
P ro c e s s M S C _ A _ H O
F ig u r e 1 9 .2 .2 /1: H O in M S C -A W ait_ for SUB_HO _ In d ic atio n
1 9 .2 .2 _ 1 .8 (1 3 )
H O _ C A _ M E S S A G E _ in d, s ee N O T E 1 [H O -R eq u es t]
H O _ C A _ M E S S A G E _in d , see N O TE 1 [H O pr ep eratio n r es u lt]
R ec eiv e_ err or from H O _C A or M S C N u ll, E rror
S ee s u bc la u s e 19
M AP_O PEN _req M AP_PRE PAR E_ H A N D O V E R _ r eq M A P _ D E L IM IT E R _ re q
M AP_PR E PAR E_S U BS EQ U E N T_ H A N D O V E R _ rs p M A P _ D E L IM IT E R _ r eq
NULL
T o M S C -B ' C all on M S C -B
T o M S C -B
F rom M S C -B
H O _ C A _ M E S S A G E _ ind , see N O TE 1, [M es s ag e tr an s fer]
M AP_PRO C ESS_ACCE SS_ S IG N A L L IN G _ in d
M A P _ F O R W A R D _A C C E S S _ S IG N A L L IN G _r e q M A P _ D E L IM IT E R _ re q E rror T o M S C -B
C h ec k _ in dic atio n
S ee s u b c la u s e 2 5.2
Ok
R ec eiv e _ O p e n _ Cnf Ok
S e e s u b c la us e 25 .1
H O _ C A _ M E S S A G E _ r eq , see N O TE 1, [M es s ag e tr a n s fer]
Vr
E rror
W ait for SUB_HO_ In dic atio n
P erform MAP Vr D ialog u e
H O _C A _ M E S S A G E _ req , s ee N O T E 1
W ait_ for S P H _r es u lt
W ait_ for SUB_HO _ In d ic atio n
N U LL
T h e s tate c h a n g es tow ar ds M S C -B ' on ly. N o c h an g es tow ar d s M S C -B
1425
1426
Figure 19.2.2/1 (sheet 8 of 13): Process MSC_A_HO
1672
1673
Process MSC_A_HO
Figure 19.2 2/1: HO in MSC-A
19.2.2_1.9(13)
Wait_for SPH_result
from MSC-B
HO_CA_MESSAGE_ind, see NOTE 1, [Message Transfer]
MAP_PROCESS_ACCESS_ SIGNALLING_ind
MAP_FORWARD_ACCESS_SIGNALLING_req, MAP_DELIMITER_req Error
Check_ Indication Ok
See subclause 25.2
To MSC-B
HO_CA_MESSAGE_req, see NOTE 1 [Message Transfer]
Wait_for SPH_result
Wait_for SPH_result
1427
1428
Figure 19.2.2/1 (sheet 9 of 13): Process MSC_A_HO
1674
1675
Process MSC_A_HO
Figure 19.2 2/1: HO in MSC-A
19.2.2_1.10(13)
Wait_for SPH_result Receive_error from HO_CA or MSC Null, Error
MAP_PREPARE_HANDOVER_cnf
See subclause 19.2.4
Check_ Confirmation Ok
See subclause 25.2
HO_CA_MESSAGE_req. see NOTE 1, [Message Transfer] Yes No multiple bearer not supported indicated?
Provider error User error Data error MAP_U_ ABORT_req
to MSC-B'
Wait_for_ Resend (SPH)
Wait_for_ HO_request for MSC-B'
HO_CA_MESSAGE_ind, see NOTE 1 [HO-Request]
Receive_error from HO_CA or MSC
Null, Error to MSC-B UserError:= SubsequentHandover Failure
MAP_PREPARE_HANDOVER_req MAP_DELIMITER_req
MAP_PREPARE_SUBSEQUENT_ HANDOVER_rsp MAP_DELIMITER_req HO_CA_MESSAGE_req, see NOTE 1, [Message Transfer]
Wait_for SPH_result
Call on MSC-B
1429
1430
Figure 19.2.2/1 (sheet 10 of 13): Process MSC_A_HO
1676
1677
Process MSC_A_HO
Figure 19.2 2/1: HO in MSC-A
19.2.2_1.11(13)
Wait_for HO_request for MSC-B'
HO_CA_MESSAGE_ind, see NOTE 1 [HO preparation result]
Receive_error from HO_CA on MSC Error
See subclause 19.2.4
Null
UserError := SubsequentHandover Failure To old MSC-B To old MSC-B
NULL
MAP_PREPARE_SUBSEQUENT_ HANDOVER_rsp MAP_DELIMITER_req
MAP_PREPARE_SUBSEQUENT_ HANDOVER_rsp MAP_DELIMITER_req
Wait_for_ HO_Completion on MSC-B'
Call on MSC-B
1431
1432
Figure 19.2.2/1 (sheet 11 of 13): Process MSC_A_HO
1678
1679
Process MSC_A_HO
Figure 19.2 2/1: HO in MSC-A
19.2.2_1.12(13)
Wait_for_ HO_Completion on MSC-B'
MAP_SEND_END_ SIGNAL_ind
MAP_PROCESS_ACCESS_ SIGNALLING_ind
from MSC-B'
Check_ Indication Ok
See subclause 25.2
Check_ Indication Error Ok
See subclause 25.2
Error
HO_CA_MESSAGE_req, see NOTE 1
MAP_U_ ABORT_req
HO_CA_MESSAGE_req, see NOTE 1 [Message transfer]
Wait_for_ Call_on MSC-B'
NULL
Wait_for_ HO_completion on MSC-B'
1433
1434
Figure 19.2.2/1 (sheet 12 of 13): Process MSC_A_HO
1680
1681
Process MSC_A_HO
Figure 19.2 2/1: HO in MSC-A
19.2.2_1.13(13)
Wait_for_ Call_on_ MSC-B'
HO_CA_MESSAGE_ ind, see NOTE 1 MAP_PROCESS_ ACCESS_ SIGNALLING_ind, MAP_DELIMITER_ind MAP_SEND_END_ SIGNAL_rsp, MAP_CLOSE_req to MSC-B
Receive_error from HO_CA or MSC Null, Error
See subclause 19.2.4
Call on MSC-B
HO_CA_MESSAGE_ind see NOTE 1
MSC-B is MSC-B'
Check_ Indication Ok
See subclase 25.2 Error MAP_FORWARD_ACCESS_ SIGNALLING_req MAP_DELIMITER_req To old MSC-B
HO_CA_MESSAGE_ req, see NOTE 1
Call on MSC-B
Wait_for_ Call_on_ MSC-B'
Wait_for_ Call_on_ MSC-B'
1435
1436
Figure 19.2.2/1 (sheet 13 of 13): Process MSC_A_HO
1437
19.2.3 Handover procedure in MSC-B
1438 This clause describes the handover or relocation procedure in MSC-B, including the request for a handover or 1439 relocation from another MSC (MSC-A), subsequent handover or relocation to a third MSC (MSC-B') or back to the 1440 controlling MSC (MSC-A).
1682
1683
1441 19.2.3.1
Basic handover
1442 Opening of the dialogue is described in the macro Receive_Open_Ind in clause 25.1. 1443 When MSC-B process receives a MAP_PREPARE_HANDOVER indication from MSC-A, MSC-B requests its 1444 associated VLR to provide a handover number, unless the parameter HO-NumberNotRequired is received in the 1445 indication. 1446 1447 1448 1449
When the connection between the MS and MSC-B is established on MSC-B, the Handover Control Application will request the MAP application to indicate this event to MSC-A by invoking the MAP_SEND_END_SIGNAL request. When a call is released, MSC-A will inform MSC-B by MAP_SEND_END_SIGNAL response and the MAP dialogue between MSC-A and MSC-B is closed.
1450 19.2.3.2
Allocation of handover number
1451 When a handover number is required, a MAP_ALLOCATE_HANDOVER_NUMBER request will be sent to the VLR. 1452 The handover number is received in the MAP_SEND_HANDOVER_REPORT request, and will be included in the 1453 MAP_PREPARE_HANDOVER response to MSC-A. 1454 When relocation numbers are required, one or several MAP_ALLOCATE_HANDOVER_NUMBER requests will be 1455 sent to the VLR. Each relocation number is received in a MAP_SEND_HANDOVER_REPORT request, and the 1456 collected relocation numbers will be included in the MAP_PREPARE_HANDOVER response to MSC-A. 1457 As soon as the call from MSC-A using the handover number arrives in MSC-B, MSC-B shall release the handover 1458 number in the VLR using the MAP_SEND_HANDOVER_REPORT response. 1459 As soon as a call from MSC-A using a relocation number arrives in MSC-B, MSC-B shall release the relocation number 1460 in the VLR using the MAP_SEND_HANDOVER_REPORT response.
1461 19.2.3.3
Handling of access signalling
1462 If required by the Handover Control Application, MSC-B invokes the MAP_PROCESS_ACCESS_SIGNALLING 1463 request containing the information received on the A-interface or the Iu-interface that should be transferred to MSC-A 1464 (e.g. call control information). 1465 MAP_PROCESS_ACCESS_SIGNALLING is a non-confirmed service and any response from MSC-A will require a 1466 MAP_FORWARD_ACCESS_SIGNALLING request.
1467 19.2.3.4
Other procedures in stable handover situation
1468 During a call and after handover or relocation, a number of procedures between MSC-A and BSS-B or RNS-B 1469 controlled by or reported to MSC-A may be initiated by involving access signalling transfer in both directions.
1470 19.2.3.5
Subsequent handover
1471 The procedure is used when the Handover Control Application in MSC-B has decided that a call is to be handed over or 1472 relocated to another MSC (either back to the controlling MSC (MSC-A) or to a third MSC (MSC-B')). 1473 After the MAP_PREPARE_SUBSEQUENT_HANDOVER response is received from MSC-A, MSC-B will await the 1474 disconnection of the call. Once the disconnect is complete, MSC-B will inform its VLR by invoking the 1475 MAP_SEND_HANDOVER_REPORT confirmation. VLR-B will then release the allocated handover number. 1476 The subsequent handover procedure is shown in figure 19.2/3.
1477 19.2.3.6
SDL Diagrams
1478 The SDL diagrams on the following pages describe the user process in MSC-B for the procedures described in this 1479 clause. 1480 The services used are defined in clause 8.4.
1684
1685
1481 1482 1483 1484 1485 1486
NOTE 1: The message primitives HO_CA_MESSAGE in the SDL-diagrams are used to show the internal coordination between the MAP application and the Handover Control Application. For a detailed description of the co-ordination between the applications for the handover procedure, see 3GPP TS 23.009. NOTE 2: The order in the SDL diagrams to allocate first the handover number and then the radio resources is not binding.
Process MSC_B_HO
NULL Figure 19.2.3/1: HO in MSC-B Receive_Open Ind Ok Wait_for_ service_ ind See section 25.1
1(11)
Vr
Error
MAP_PREPARE_HANDOVER_ind
MAP_ NOTICE_ ind
Perform MAP Vr dialogue
Check_ Indication Ok VGCS or VBS yes new cell in Group Call Area no
See section 25.2
MAP_ CLOSE_ req
Error no MAP_PREPARE_HANDOVER_rsp, MAP_CLOSE_req,
yes HO-Number allocatio n required yes multiple bearer requested No no
us er error = Target Cell Outside Group Call Area
HO_CA_MESSAGE_req, see NOTE 1 [Handover request] Ye s
Wait_for_ Channel
multiple bearer supported? Yes No MAP_PREPATRE_HANDOVER_rsp MAP_DELIMETER_req NULL 1 Wait_for_ service_ ind NULL
MAP_PREPARE_HANDOVER_rsp MAP_CLOSE_rsp
1487
1686
1687
1488
Figure 19.2.3/1 (sheet 1 of 11): Process MSC_B_HO
Proc ess MSC_B_HO
F ig ure 19.2. 3/1: HO in MS C-B
19.2 .3_1.2(11)
to VLR-B
M A P_O PE N_req M A P_A LLO C ATE _HA ND OV ER _NU MB ER _req M A P_D ELI MI TER _req
Receive_Open Cnf
See sect ion 25.2
OK
E rror, Vr
user er ror= NoHandover NumberAvailable
t o MS C -A
M AP _P RE P AR E_HA ND OV E R_rsp, MA P _C LO S E _req
W ait _for_ HO_Number
NULL
1489
1490
Figure 19.2.3/1 (sheet 2 of 11): Process MSC_B_HO
1688
1689
Proc ess MSC_B_HO
F ig ure 19.2. 3/1: HO in MS C-B
19.2 .3_1.3(11)
W ait _for_ HO_Number
M A P_S E ND_HA NDO VE R _R E PO RT _ind
MA P_A LLOC A TE _H AND O VE R_NUM BE R_c nf
Check _ Indicat ion
See sect ion 25.2
Ok
E rror
user error= S y st em Failure
user error = NoHandover NumberA vailable
HO _C A _M ES S A GE _req, see NO TE 1
MA P_P RE P AR E_HA ND OV ER _rs p MA P_CLO S E _req
W ait_for_ Channel
NULL
1491
1492
Figure 19.2.3/1 (sheet 3 of 11): Process MSC_B_HO
1690
1691
Proc ess MSC_B_HO
F ig ure 19.2. 3/1: HO in MS C-B
19.2 .3_1.4(11)
W ait_for_ Channel
HO_C A_ME S S A GE _ind, see NO T E 1, [Handov er request ack]
Receive_error from HO _CA or M S C
See se c tion 19.2. 4
Null, E rror
SC CP segment ation required no
yes NULL
M A P_DE LIM ITE R _req,
M A P_P RE PA RE _HA NDO VE R _rs p M A P_D ELI MI TER _req
W ait _for_ connec t ion
1493
1494
Figure 19.2.3/1 (sheet 4 of 11): Process MSC_B_HO
1692
1693
Proc ess MSC_B_HO
F ig ure 19.2. 3/1: HO in MS C-B
19.2 .3_1.5(11)
W ait _for_ connec t ion
HO_CA _ME S S AG E _ind, see NO TE 1, [HO -Number releas e requ est ]
see s ection 19.2.4
Rec eive_e rror from HO _CA or M SC Null, Error
HO_C A_ME S S A GE _ind, see NO TE 1
HO _CA _ME S SA G E _ind, s ee NO TE 1 (Mes sage Transfer)
NULL M A P_S E ND_E ND_S IG NA L_req M A P_D ELI MI TER _req S et = HO number us ed
MA P_PR OC ES S _AC CE S S _S I G NALLI NG_req M A P_DE LIM ITE R_req
MS on M SC -B
W ait_for_ c onnec tion
t o V LR- B
M AP _ SE ND _HA NDOV E R_RE P OR T_rs p M A P_ CLO SE _req
W ait _for_ c onnec tio n
1495
1496
Figure 19.2.3/1 (sheet 5 of 11): Process MSC_B_HO
1694
1695
Proc ess MSC_B_HO
F ig ure 19.2. 3/1: HO in MS C-B
19.2 .3_1.6(11)
MS on M SC -B
HO_C A_ME S S A GE _ind, see NO TE 1
M AP _F O RW A RD _AC CE S S_S I GNA LLING _ind MA P _D E LI MI TE R_ind
M A P_P RO CE S S_A CC ES S _S IG NA LLING _req M A P_D ELI MI TER _req
HO _C A _M E SS A G E _req, s ee NO TE 1
MS on M SC -B
1497
1498
Figure 19.2.3/1 (sheet 6 of 11): Process MSC_B_HO
1696
1697
Proc ess MSC_B_HO
F ig ure 19.2. 3/1: HO in MS C-B
19.2 .3_1.7(11)
MS on M S C -B
MA P_PR EP A RE _HA NDO VE R_ind,
S ee sec tion 19. 2. 4
R eceive_error f rom HO _C A or MS C
C heck_ I ndic at ion
See s ec t ion 25.2
Null Ok Error E rror
HO -NumberN ot Required param et er present
no
MS on M SC -B
NULL
yes yes
Handov er num ber al ready used
no
us er error= Unexpect ed Dat aValue
MA P_P RE P AR E_HA ND OV E R_rsp, MA P_D E LI MI TE R_req
MS o n MS C-B
1499
1500
Figure 19.2.3/1 (sheet 7 of 11): Process MSC_B_HO
1698
1699
Proc ess MSC_B_HO
F ig ure 19.2. 3/1: HO in MS C-B
19.2 .3_1.8(11)
to V LR -B
M A P_O PE N_req, M A P_A LLO C AT E_HA ND OV ER _NUMB E R_req, M A P_D ELI MI TE R_ req,
Receive_Open Cnf
See sect ion 25.2
OK
Error, Vr
user error= NoHandover NumberA vailable
MA P_P RE P AR E_HA ND OV E R_rsp, MA P_D E LI MI TE R_req
W ait _for_ HO_Number allocat ion
NULL
1501
1502
Figure 19.2.3/1 (sheet 8 of 11): Process MSC_B_HO
1700
1701
Proc ess MSC_B_HO
F ig ure 19.2. 3/1: HO in MS C-B
19.2 .3_1.9(11)
W ait _for_ H O_Number allocat ion
MA P_S EN D_HA NDO VE R _R E PO RT_ind
M AP _A LLOC A TE _ HAND O VE R_NUM BE R _c nf
C heck_ I ndic at ion
See s ect ion 25.2
Ok
E rror
us er error= S y st em Failure
user error = NoHandover Number Available
HO_CA _M ES S AG E _req See NO TE 1
M AP _P RE P AR E_HA ND OV ER _rs p M AP _D E LIMI TE R_req
W ait-forass ignm ent
MS on MS C-B
1503
1504
Figure 19.2.3/1 (sheet 9 of 11): Process MSC_B_HO
1702
1703
Proc ess MSC_B_HO
F ig ure 19.2. 3/1: HO in MS C-B
19.2 .3_1.10(11)
W ait_for_ a ss ignment
HO_CA _ME S S AG E _ind, see NO TE 1
Remov e_error from B A or M SC
see s ection 19.2.4
N ull, E rror
S C CP s egm ent atio n re quired
yes
no
M A P_DE LIM ITE R_ re q
MA P_PR E PA RE _HA NDO VE R_rs p MA P_D ELIM I TER _req
MS on M SC -B
MS on M SC -B
1505
1506
Figure 19.2.3/1 (sheet 10 of 11): Process MSC_B_HO
1704
1705
Proc ess MSC_B_HO
F ig ure 19.2. 3/1: HO in MS C-B
19.2 .3_1.11(11)
MS on M SC -B
M A P_S E ND_E ND_SI G NA L_cnf
HO _C A _MES SA G E_ ind, s ee NO TE 1 [ Hand over required]
Check Confirmation OK P rovider err or D a ta error W ait_f or_ S P H_result
MA P _PRE P AR E_S UB S E QUE NT_HA NDO V ER _req M AP _DE LIMI TE R_req
HO _C A _M ES S A GE _req, see NO T E 1, [C onnect ion c los ed]
M A P_U_AB O RT _req, see NO TE 1
NULL
M A P_P RE PA RE _S UB SE Q UE NT_ HA NDO VE R _cnf
Rec eiv e_error from HO _C A or M S C
S ee s ec t ion 19. 2.4
MA P_F OR W A RD_ AC CE S S_ SI G NA LLI NG _ind
Null, E rror HO_C A_ME S S A GE _ind, see NO T E 1, [HO -P repared] HO _C A_M E SS A GE _req see N OT E 1, [M essage received]
MS on M SC -B
NU LL
W ait_for_ S PH_result
1507
1508
Figure 19.2.3/1 (sheet 11 of 11): Process MSC_B_HO
1706
1707
1509
19.2.4 Handover error handling macro
1510 This macro is used for the handover procedures to receive errors from the MSCs and from the Handover Control 1511 Application at any state of a handover process. 1512 If a MAP_NOTICE indication is received, the Handover Control Application is informed and the actual situation is kept 1513 and the Handover Control Application decides how the handover or relocation process should continue. In all other 1514 cases the MSC is returned to a "NULL" state.
1708
1709
Macrodefin ition R ece ive_ error_from_H O _C A_o r_MSC
F ig ur e 19. 2.4/ 1: M acro R eceive_error_from_HO_C A _or_MS C
19.2 .4_1(1)
HO_C A_ME S S A GE _ind, see NO TE 1 [E rror_ind]
MA P_U_A B O RT_ind, M A P_P_A B OR T_ind
MA P _CLOS E _ ind
HO _CA _ME S SA G E _req, s ee NO TE 1 [ E rror_ind]
BA _M ES S A GE _req, see N OTE 1 [C onnect ion c los ed]
E rror indic ation C los e dia logue
K eep dialogue
MA P_NO TI CE _ind
MA P_NO TI CE prev iously rec eived
yes
HO _C A _ME S SA G E _req, s ee NO TE 1
no
MA P_U_ A BO RT_req
MA P_CLO S E_ req
M A P_ D E LI MI TE R_ re q
E rror
NULL
1515
1516
Figure 19.2.4/1: Macro Receive_error_from_HO_CA_or_MSC
1710
1711
1517 1518 19.2.5.1
19.2.5 Handover procedure in VLR
Allocation of handover number
1519 When receiving the MAP_ALLOCATE_HANDOVER_NUMBER indication, the VLR will determine whether a 1520 handover number is available. If no handover number is available, this will be indicated by a 1521 MAP_ALLOCATE_HANDOVER_NUMBER response with the appropriate error. 1522 The handover number allocated will otherwise be returned to MSC-B in the MAP_SEND_HANDOVER_REPORT 1523 request. 1524 The handover number will be reserved until a MAP_SEND_HANDOVER_REPORT confirmation is received from 1525 MSC-B.
1526 19.2.5.2
SDL Diagrams
1527 The SDL diagrams on the following pages describe the user processes in VLR for the procedures described in this 1528 clause. 1529 The services used are defined in clause 8.4.
1712
1713
Process VLR_B_HO
F ig ur e 19.2.5/ 1 N ULL
19.2.5_1.1(2)
R ec eive_O pen_ind
E rror, Vr
OK
M A P_ALLO CA TE _HA NDO VE R_NUM B ER _ind
NULL
C hec k_ I ndic ation E RRO R
OK Handov er Number a vailable no yes
U ser E rror= N o Handover N umbers A vaila ble
S elec t handov er nu mber
Mark Number as allocat ed
MA P _A LLO CA TE _HA ND OV E R_NUMB E R_rs p, MA P _CLOS E _req
MA P_S E ND_HA NDO V ER _RE PO RT _req, MA P_D E LI MI TE R_req
N ULL
W a it_f or_ remov al
1530
1531
Figure 19.2.5/1 (sheet 1 of 2): Process VLR_B_HO
1714
1715
Process VLR_B_HO
F ig ur e 19.2.5/ 1
19.2.5_1.2(2)
W ait_for_ rem oval
M A P_S E ND_HA NDO VE R _R E PO RT _c nf
LO CA L A B O RT
MA P_U_AB ORT _ind
Check _ Confirmation OK, P rovider E rror, D at a Error, Us er E rror Mark handover number as free
M AP _U_AB O RT_req
NULL
1532
1533
Figure 19.2.5/1 (sheet 2 of 2): Process VLR_B_HO
1716
1717
1534
19.3 Fault recovery procedures
1535 After a fault of a location register, the fault recovery procedures ensure that the subscriber data in the VLR or in the 1536 SGSN become consistent with the subscriber data that are stored in the HLR for the MS concerned and that the location 1537 information in HLR , VLR and SGSN reflect accurately the current location of the MS. 1538 The detailed specification of fault recovery procedures of location registers is given in 3GPP TS 23.007 [19].
1539
19.3.1 VLR fault recovery procedures
In case of a location registration request from the MS: Update_Location_Area_VLR Update_Location_HLR In case of a mobile terminated call: PRN_VLR RESTORE_DATA_VLR RESTORE_DATA_HLR ICS_VLR clause 21.2.4; clause 21.2.4; clause 19.3.3; clause 21.3.3. clause 19.1.1.3; clause 19.1.1.4.
1540 The following processes are involved with the restoration of one IMSI record in the VLR: 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553
After a restart, the VLR shall erase all IMSI records affected by the failure and shall cause all affected TMSIs and all affected LMSIs to become invalid. There will be no subscriber data or location information stored for an affected MS until after the VLR has received either a MAP_PROVIDE_ROAMING_NUMBER indication or a MAP_UPDATE_LOCATION_AREA indication for that MS. Restoration of subscriber data in the VLR is triggered individually for each IMSI record by receipt of either of these indications.
1554 Reception of either a MAP_UPDATE_LOCATION_AREA indication or a MAP_PROVIDE_ROAMING_NUMBER 1555 indication with an IMSI that is unknown in the VLR causes creation of a skeleton IMSI record that is marked as: 1556 1557 1558 1559
not confirmed by radio contact by the indicator "Confirmed by Radio Contact" (The function of this indicator is described in 3GPP TS 23.007 [19]); and not confirmed by HLR by the indicator "Confirmed by HLR" (The function of this indicator is described in 3GPP TS 23.007 [19]).
1560 A third indicator "Location Information Confirmed in HLR" is allocated to each IMSI record in the VLR (The function 1561 of this indicator is described in 3GPP TS 23.007 [19]). 1562 1563 1564 1565 1566
The indicator "Location Information Confirmed in HLR" shall be checked whenever authenticated radio contact with an MS has been established. The status "Not Confirmed" of this indicator shall force the VLR to invoke the MAP_UPDATE_LOCATION service but it shall never cause rejection of a mobile originated request. The status is changed from "Not Confirmed" to "Confirmed" only after successful completion of a MAP_UPDATE_LOCATION procedure for the MS concerned.
1567 If the VLR serves only one MSC, the indicator "Location Information Confirmed in HLR" is only relevant to the HLR 1568 restoration procedure and an initial value must be assigned when an IMSI record is created in the VLR: 1569 1570 1571
if the IMSI record was created due to a roaming number request, the initial value must be set to "Confirmed"; if reception of a MAP_UPDATE_LOCATION_AREA indication causes creation of the IMSI record, the initial value must be "Not Confirmed".
1572 If the VLR serves more than one MSC, the indicator "Location Information Confirmed in HLR" is used in the VLR 1573 restoration procedure as well as in the HLR restoration procedure. When an IMSI record is created in the VLR, the 1574 indicator must be set to "Not Confirmed".
1718
1719
1575 VLR restoration triggered by a location registration request 1576 Upon receipt of a MAP_UPDATE_LOCATION_AREA indication, the VLR retrieves authentication data from the 1577 HLR by using the MAP_SEND_AUTHENTICATION_INFO service if authentication is required and if no 1578 authentication data are available in the VLR for the IMSI concerned (see figure 19.1.1/6). 1579 1580 1581 1582
Receipt of a MAP_UPDATE_LOCATION_AREA indication for an MS whose IMSI is unknown in the VLR or whose data stored in the VLR are marked as "Not Confirmed" by the indicator "Confirmed by HLR" and/or by the indicator "Location Information Confirmed in HLR" forces the VLR to invoke the MAP_UPDATE_LOCATION service after successful authentication, if required. The location updating procedure is performed as described in clause 19.1.
1583 Any other mobile originated request from an MS whose IMSI is unknown in the VLR or whose subscriber data stored 1584 in the VLR are marked as "Not Confirmed" by the indicator "Confirmed by HLR" shall be rejected with error cause 1585 "Unidentified Subscriber". This causes the MS to trigger the location registration procedure. 1586 After successful completion of the MAP_UPDATE_LOCATION procedure, the indicators "Confirmed by HLR" and 1587 "Location Information Confirmed in HLR" are set to "Confirmed". 1588 The indicator "Confirmed by Radio Contact" is set to "Confirmed" when the radio contact with the MS is authenticated. 1589 VLR restoration triggered by a roaming number request 1590 Figure 19.3/1 illustrates the signalling sequence for restoration of an IMSI record in the VLR triggered by a mobile 1591 terminating call set-up. 1592 1593 1594 1595 1596 1597 1598 1599 1600
Upon receipt of a MAP_PROVIDE_ROAMING_NUMBER indication for an IMSI that is unknown in the VLR and for which authentication is required, the VLR retrieves authentication data from the HLR by using the MAP_SEND_AUTHENTICATION_INFO service after an MSRN has been sent to the HLR in the MAP_PROVIDE_ROAMING_NUMBER response. Receipt of a MAP_PROVIDE_ROAMING_NUMBER indication for an MS whose IMSI is unknown in the VLR or whose data record in the VLR is marked as "Not Confirmed" by the indicator "Confirmed by HLR" forces the VLR to request subscriber data from the HLR by sending a MAP_RESTORE_DATA request which triggers one or more INSERT_SUBSCRIBER_DATA operations from the HLR. The MAP_RESTORE_DATA request may also be used to send the LMSI to the HLR.
1601 The MAP_RESTORE_DATA process in the VLR is described in clause 21.2.4. 1602 The MAP_RESTORE_DATA process in the HLR is described in clause 19.3.3. 1603 After successful completion of the MAP_RESTORE_DATA procedure, the indicator "Confirmed by HLR" is set to 1604 "Confirmed". 1605 1606 1607 1608 1609 1610
If restoration of an IMSI record was triggered by a MAP_PROVIDE_ROAMING_NUMBER indication (i.e. by a mobile terminating call), the VLR has no valid Location Area Identity information for the MS concerned before successful establishment of the first authenticated radio contact. Upon receipt of a MAP_SEND_INFO_FOR_INCOMING_CALL indication from the MSC (see 5 in figure 19.3/1) for an MS whose subscriber data are marked as "Confirmed" by the indicator "Confirmed by HLR" but not confirmed by radio contact, the VLR shall invoke a "MAP_SEARCH_FOR_MS" instead of a "MAP_PAGE".
1611 A MAP_SEARCH_FOR_MS shall also be performed if the VLR receives a MAP_SEND_INFO_FOR_MT_SMS 1612 indication from the MSC for an MS whose IMSI record is marked as "Confirmed" by the indicator "Confirmed by 1613 HLR" but not confirmed by radio contact. 1614 The indicator "Confirmed by Radio Contact" is set to "Confirmed" when authenticated radio contact caused by a mobile 1615 originated or a mobile terminated activity is established.
1720
1721
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
+-----+ (B) +-----+ D +-----+ MSC +----------+---------- VLR +----------+---------- HLR +-----+ (no external +-----+ +-----+ interface) MAP_PROVIDE_ROAMING_NUMBER ) <---------------------------) PROVIDE_ROAMING_NUMBER_ack )1 --------------------------->) MAP_SEND_AUTHENTICATION_INFO) (note 1) --------------------------->) SEND_AUTHENTICATION_INFO_ack)2 <---------------------------) ) MAP_RESTORE_DATA +---------------------------> ( ( MAP_ACTIVATE_TRACE_MODE ( (note 2) <--------------------------- ( MAP_ACTIVATE_TRACE_MODE_ack ( ---------------------------> ( 4( MAP_INSERT_SUBSCRIBER_DATA ) ( 1) see clause 21.2.4 <---------------------------) ( 2) see clause 25.5 INSERT_SUBSCRIBER_DATA_ack )3 ( 3) see clauses 19.4 +--------------------------->) ( 25.7 ) ( 4) see clauses 19.3.3 MAP_RESTORE_DATA_ack ( 21.2.4 <--------------------------- ---+---------------------------+----------------------------+ ( MAP_SEND_INFO_FOR_INCOMING_CALL or ( +--------------------------> ( MAP_SEND_INFO_FOR_MT_SMS ( 5( MAP_SEARCH_FOR_MS ( <-------------------------- ( ( MAP_SEARCH_FOR_MS_ack ( +--------------------------> ( ( MAP_PROCESS_ACCESS_REQUEST ( +-------------------------->5) see clauses 21.3, 23.3
NOTE 1: If authentication required. NOTE 2: If subscriber tracing active in HLR.
1666
1663 1664 1665
Figure 19.3/1: Procedures related to restoration of VLR in case of mobile terminated call set-up
1667
19.3.2 HLR fault recovery procedures
HLR_RESTART REC_RESET_IN_VLR REC_RESET_IN_SGSN clause 19.3.2; clause 19.3.2; clause 19.3.2.
1668 The following processes are involved with the restart of the HLR: 1669 1670 1671
1672 In the case of a location registration request from the MS, the following processes are involved with the HLR 1673 restoration procedure: 1674 1675 1676 1677
Update_Location_Area_VLR Update_Location_HLR Update_GPRS_Location_HLR GPRS_Update_Location_Area_VLR
clause 19.1.1.3; clause 19.1.1.4; clause 19.1.1.4; clause 19.1.1.3;
1722
1723
1678
SGSN_Update_HLR
clause 19.1.1.8.
1679 In the case of a mobile originated service request, the 1680 1681
Macro Process_Access_Request_VLR Process Update_Location_HLR
clause 25.4.2; and the clause 19.1.1.4,
1682 are involved with the HLR restoration procedure. 1683 For the HLR, periodic back-up of data to non-volatile memory is mandatory. 1684 1685 1686 1687
Data that have been changed in the period of time after the last back-up storage and before the restart of the HLR cannot be recovered by reload from the non-volatile memory. Therefore, a restoration procedure is triggered individually for each IMSI record that has been affected by the HLR fault at the first authenticated radio contact that is established with the MS concerned.
1688 The HLR restoration procedure forces updating of MSC number, VLR number, SGSN number and, if provided by the 1689 VLR, LMSI in the HLR. Consistency of subscriber data that are stored in the VLR or in the SGSN for an MS that has 1690 been affected by a HLR fault with the subscriber data stored in the HLR for this MS will be achieved. 1691 1692 1693 1694
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 present the VLR shall not forward this notification.
1695 Figures 19.3/2 and 19.3/9 illustrates the signalling sequence for HLR restoration. 1696 After a restart, the home location register performs the following actions for the subscriber data records that have been 1697 affected by the HLR fault (see figure 19.3/3): 1698 1699 1700 1701 1702 1703 1704
reload all data from the non-volatile back-up; if the MAP_FORWARD_CHECK_SS_INDICATION service is implemented, mark each subscriber record "SS Check Required" by setting the "Check SS" indicator; set subscriber tracing deactive in the VLR for each of its Mss; reset the "MS Purged" flag for each of its MSs; send a MAP_RESET request to the VLRs where its MSs are located (see figure 19.3/4). send a MAP_RESET request to the SGSNs where its MSs are located (see figure 19.3/7).
1705 The MAP_RESET request contains the HLR number and optionally the HLR Identity List. 1706 1707 1708 1709
When receiving a MAP_RESET indication, the VLR or the SGSN will derive all involved MSs of that HLR either from the HLR Identity List (if present), or from the HLR number. The VLR or the SGSN will then mark these MSs with the indicator "Location Information Confirmed in HLR" set to "Not Confirmed" and will deactivate all subscriber tracings for these Mss (see figures 19.3/5 and 19.3/8).
1710 The status "Not Confirmed" of the indicator "Location Information Confirmed in HLR" forces the VLR to invoke the 1711 MAP_UPDATE_LOCATION service after establishment of authenticated radio contact with the MS concerned. 1712 Also the status "Not Confirmed" of the indicator "Location Information Confirmed in HLR" forces the SGSN to invoke 1713 the MAP_UPDATE_GPRS_LOCATION service after establishment of authenticated radio contact with the MS 1714 concerned. 1715 The MAP_UPDATE_LOCATION procedure is performed as described in clause 19.1. 1716 After receipt of the MAP_UPDATE_LOCATION or the MAP_UPDATE_GPRS_LOCATION acknowledgement 1717 containing the HLR number, the status of the indicator "Location Information Confirmed in HLR" is changed to 1718 "Confirmed".
1724
1725
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 1745 1746 1747 1748 1749 1750
If the MAP_UPDATE_LOCATION procedure is unsuccessful for any reason, the status of the indicator "Location Information Confirmed in HLR" remains unchanged except for the case that the IMSI record in the VLR is deleted because either of the errors "Unknown Subscriber" or "Roaming Not Allowed" has been received from the HLR in response to a MAP_UPDATE_LOCATION request. If the MAP_UPDATE_GPRS_LOCATION procedure is unsuccessful for any reason, the status of the indicator "Location Information Confirmed in HLR" remains unchanged except for the case that the IMSI record in the SGSN is deleted because either of the errors "Unknown Subscriber" or "Roaming Not Allowed" has been received from the HLR in response to a MAP_UPDATE_GPRS_LOCATION request. +-----+ D +-----+ (B) +-----+ HLR +----------+---------- VLR +----------+---------- MSC +-----+ +-----+ (no external +-----+ MAP_RESET interface) +--------------------------> MAP_UPDATE_LOCATION_AREA <-------------------------- MAP_PROCESS_ACCESS_REQUEST MAP_UPDATE_LOCATION <-------------------------- +--<------------------------- MAP_ACTIVATE_TRACE_MODE ) --------------------------> ) If subscriber tracing ACTIVATE_TRACE_MODE_ack ) is active in HLR. <-------------------------- ) MAP_INSERT_SUBSCR_DATA +--------------------------> INSERT_SUBSCR_DATA_ack <-------------------------- MAP_UPDATE_LOCATION_ack MAP_FORWARD_CHECK_SS_ +->+-------------------------->+--------------------------> and MAP_FORWARD_CHECK_SS_ INDICATION INDICATION (optional) (if received from HLR) Figure 19.3/2: Procedures related to restoration of HLR +-----+ Gr +-----+ HLR +----------+---------- SGSN+ +-----+ +-----+ MAP_RESET +--------------------------> MAP_UPDATE_GPRS LOCATION +--<------------------------- MAP_ACTIVATE_TRACE_MODE ) --------------------------> ) If subscriber tracing ACTIVATE_TRACE_MODE_ack ) is active in HLR. <-------------------------- ) MAP_INSERT_SUBSCR_DATA +--------------------------> INSERT_SUBSCR_DATA_ack <-------------------------- MAP_UPDATE_GPRS LOCATION_ack +->+-------------------------->+ Figure 19.3/9: Procedures related to restoration of HLR for GPRS
1751 1752
1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773
1775
1726
1727
Process HLR_R ESTA RT
F ig u re 1 9. 3/ 3 R es t ora tion o f t h e H L R A p plic a tion p ro ce s s in th e H L R fo r H LR R es t art
19.3_3(1)
1 N UL L C H EC K _ S S _s e rv ic e OM_ R ES T A R T _ In d ' n ot_ im plem ent e d' ' im p lem e nt ed ' F or ea c h MS th at is a ffe ct e d by th e H L R fa ult.
'C H E C K _ S S_ I ndic a to r := Ch ec k _R eq uire d'
'R eloa d _fr om _ ba c k u p'
S et S ub s c rib er tra c in g = d e ac t iv e in V L R
F o r e ac h M S th at is aff ec t ed by the H LR fau lt
Set S u bs c ribe r t rac in g = d ea c tive in S G S N
F or e ac h G P R S M S t ha t is a f fec te d by t he H LR f au lt
'R e s et _F la g M S _P U R G E D _ F O R _ NO N -G P R S '
F o r e ac h M S th at is F o r e ac h G P R S M S th a t is a f fec te d 'R es e t_ F la g aff ec t ed by the H LR fau lt b y t h e H L R f au lt . M S _P U R G ED _F O R _ G P R S '
' R e ad _ V LR _ a d dre s s _list '
'R ea d _S G S N _ a dd res s _ lis t'
S E N D _R E S E T _ T O _V L R
F ig u re 19 .3 /4
SE N D _ R ES E T _ T O _ SG S N
F ig ure 19 .3 / 7
' Y es '
A n ot he r_ V L R _ in _ the _ lis t no
'Y e s '
A no th er _ S G S N _ in _ the _ lis t no
1 NU L L
1776
1777
Figure 19.3/3: Process HLR_RESTART
1728
1729
Pro cess SEN D_R ESET_TO _VL R
F ig ure 19. 3/ 4 Rest orat ion o f t he HLR P roc ess for s ending t he R ES E T mes s age from HLR t o VLR
19.3_4(1)
MA P_O PE N_ Req
MA P_ RE SE T_R eq
MA PDE LIM ITE R _Req
'R eceive_ O pen_C nf'
F igure 25. 1/2
'O K'
Vr
'E rror'
MA P_CLO S E _Req
R el eas e method: 'P rearranged E nd'
'Perform_MA P_ V r_D ia logue'
1778
1779
Figure 19.3/4: Process SEND_RESET_TO_VLR
1730
1731
Pro cess RE C_ RE SET_IN _VLR
F ig ure 19. 3/ 5 Res toration of t he HLR - A pplic ation proc es s in t he VLR fo r rec ept ion of the R ES E T mess age from HLR
19.3_5(1)
NULL
R eceive_ O PE N_I nd
F igure 25. 1/1
'OK '
'Vr'
'E rror'
WAIT
'Perform_M A P_ Vr_Dialogue'
MA P_R ES E T _I nd
c ontains HLR_Number or HLR_Num ber and HLR _Id_Lis t
NULL
NULL
MAP _CLO S E _R eq
R el eas e method : 'P rearranged E nd'
'Identify _IM SI _Rec ords '
The IM SI s are der iv ed from t he HLR _Number or from t he HLR_I d_List .
'Location_Inf o_ C onf_in_HLR := Not_C onf irmed'
F or each identif ied IM S I rec ord.
Deact ivate Subs criber Tracing
F or each identif ied IMS I rec ord
NULL
1780
1781
Figure 19.3/5: Process REC_RESET_IN_VLR
1732
1733
Pro cess SEN D_R ESET_TO _SG SN
F ig u re 1 9.3 / 7: R es to ratio n o f th e HL R P ro c es s fo r s en d in g th e R E S E T me s sa g e fro m H LR to S G S N
19.3_7(1)
M A P _ O P E N_ R eq
M AP _ R E S E T _ R eq
MAPD E L IM IT E R _R eq
'R ec e ive _ O p en _ C n f'
F ig u re 2 5 .1/2
'O K ' M A P _ C L O S ER eleas e m eth o d : _R eq ' P rearr an g ed E n d '
Vr
'E rro r'
'P e rfo rm _M A P _ V r _ D ialog u e'
1782
1783
Figure 19.3/7: Process SEND_RESET_TO_SGSN
1734
1735
Process REC_RESET_IN_SGSN
F igure 19.3/8: R es toration of the H LR - Applic ation process in the SGSN f or reception of the RESET m essage f rom HLR
19.3_8(1)
NULL
Receive_ OPEN _Ind
F igure 25.1/1
'OK'
'Vr'
'Error'
W AIT 'Perform_M AP_ Vr_Dialogue' MAP_R ESET _Ind contains HLR_N um ber or H LR _Number and H LR_Id_List
NU LL
NULL
MAP_CLOSE _R eq
R elease method: 'Prearranged End'
'Identify_IMSI _Records '
The I MSIs are derived f rom the H LR_Number or f rom the HLR _Id_Lis t.
'Location_Info_ Conf_in_HLR := Not_C onfirmed'
F or each identified IMSI record.
Deactivate Subscriber Tracing
F or each identified I MSI rec or d
NULL
1784
1785
Figure 19.3/8: Process REC_RESET_IN_SGSN
1736
1737
1786
19.3.3 VLR restoration: the restore data procedure in the HLR
1787 The MAP_RESTORE_DATA procedure in the HLR (Process RESTORE_DATA_HLR) is described in this clause; the 1788 corresponding procedure in the VLR (RESTORE_DATA_VLR) is described in clause 21.2.4. 1789 The process RESTORE_DATA_HLR makes use of the following macros: 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810
Receive_Open_Ind Check_Indication Insert_Subs_Data_Framed_HLR
clause 25.1.1; clause 25.2.1; clause 19.4.
The MAP_RESTORE_DATA service is invoked by the VLR after provision of a roaming number in response to a MAP_PROVIDE_ROAMING_NUMBER indication for an unidentified MS (i.e. IMSI unknown in VLR), or for a known MS whose IMSI record is marked as "Not Confirmed" by the indicator "Confirmed by HLR" (see 4 in figure 19.3/1). The process RESTORE_DATA_VLR is shown in figure 21.2/6. The restore data process in the HLR is activated by receipt of a MAP_RESTORE_DATA indication from the VLR (see figure 19.3/6). If there is a parameter problem in the indication, either of the errors "Unexpected Data Value" or "Data Missing" is returned in the MAP_RESTORE_DATA response; if the subscriber is not known in the HLR, the error "Unknown Subscriber" is returned in the MAP_RESTORE_DATA response. In all of these cases the process in the HLR terminates. If the MAP_RESTORE_DATA indication is accepted and if the LMSI is received, the HLR updates the LMSI for the IMSI received in the MAP_RESTORE_DATA indication. For this IMSI the HLR sets "subscriber-tracing-not-activein-VLR" and checks whether tracing is required. This check is handled by the macro "Control_Tracing_HLR" that is described in clause 25.9. Thereafter, the macro "Insert_Subs_Data_Framed_HLR" that is described in clause 19.4 is invoked. The outcome of the macro Insert_Subs_Data_Framed_HLR is one of: abort, in which case the process terminates; error, in which case the HLR returns the error "System Failure" in the MAP_RESTORE_DATA response, and the process terminates; OK, indicating successful outcome of downloading the subscriber data to the VLR.
1811 After successful completion of the framed MAP_INSERT_SUBSCRIBER_DATA procedure, the HLR Number and, if 1812 applicable, the "MS Not Reachable Flag" which is used for SMS, are provided in the MAP_RESTORE_DATA 1813 response. 1814 Upon receipt of the MAP_RESTORE_DATA confirmation, the VLR behaves as described in clause 21.2.4, 1815 figure 21.2/6.
1738
1739
Pro cess RE STOR E_D ATA _HL R
F ig ur e 19.3/6 V LR Rest orat ion - A pplication P rocess in the H LR 1
19.3_6(1)
Ins ert _S ubs _D at a _Framed_HLR 'O K '
S ect ion 19 .4 .1
'E rror' 'S et _E rror := S ys tem_Failure'
'A borted'
W AI T_FO R_ S E RV IC E_ P RI MI TIV E
MA P_ RE S TOR E _ DA TA _ Rs p MA P_ RE S TOR E _ DA TA _I nd
'M A P_ CLO SE _ Req
C heck _ I ndicat ion
Figure 25. 2/1
'E rror' 'O K' 'I MS I _known' 'Y es ' 'No'
'MN RF _s et' 'No' 'Y es' 'Set _parameter_ MS _NO T_ R EA CHA BLE ' in th e MA P_ RE S TOR E _ DA TA _Rs p mess age
'Update_LMSI' (if received)
'Set _Error := Unknown_ S ubs c riber'
'Set _parameter_ HLR_NUMB ER '
in th e MA P_ RE S TOR E _ DA TA _Rs p mess age
'S et_s ubs criber_ t racing_not _ ac tive_in_VLR'
M AP _ RE S TO RE _ D AT A_Rs p Figure 25. 9/4 M AP _ CLO S E_ R eq 'Error'
Control_ Trac ing_HLR
'O K' M A P_ RE S TO RE _ D AT A_Rs p 1 M A P_ C LO SE _R eq
1816
1817
Figure 19.3/6: Process RESTORE_DATA_HLR
1740
1741
1818
19.4 Macro Insert_Subs_Data_Framed_HLR
1819 This macro is used by any procedure invoked in HLR which requires the transfer of subscriber data by means of the 1820 InsertSubscriberData operation (e.g. Update Location or Restore Data). 1821 The invocation of the operation is done in a dialogue already opened by the framing procedure. Therefore the latter is 1822 the one that handles the reception of the open indication and sends the dialogue close request. 1823 The macro calls the process "Send_Insert_Subs_Data" (see clause 25.7.4) as many times as it is needed for transferring 1824 all subscriber data. This process call is meant to describe two possible behaviours of HLR to handle service requests 1825 and confirmations: 1826 1827
either the HLR handles requests and confirmations in parallel; or the HLR sends the next request only after receiving the confirmation to the previous one.
1828 Another call is done to the macro "Wait_for_Insert_Subscriber_Data" (see clause 25.7.3). There the reception and 1829 handling of the service confirmations is described. 1830 If certain services required for a subscriber are not supported by the VLR or by the SGSN (e.g. Advice of Charge 1831 Charging Level), this may result in one of the following outcomes: 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842
The HLR stores and sends "Roaming Restriction Due To Unsupported Feature" in a subsequent MAP_INSERT_SUBSCRIBER_DATA service. If "Roaming Restriction Due To Unsupported Feature" is stored in the HLR, the "MSC Area Restricted Flag" shall be set to "restricted". This will prevent MT calls, MT SM and MT USSD from being forwarded to the MSC/VLR; The HLR stores and sends other induced subscriber data (e.g. a specific barring program) in a subsequent MAP_INSERT_SUBSCRIBER_DATA service. This will cause rejection of mobile originated service requests, except emergency calls. The HLR stores and sends "Roaming Restricted in the SGSN Due To Unsupported Feature" in a subsequent MAP_INSERT_SUBSCRIBER_DATA service. If "Roaming Restricted In SGSN Due To Unsupported Feature" is stored in the HLR, the "SGSN Area Restricted Flag" shall be set to "restricted". This will prevent MT SM from being forwarded to the SGSN and Network Requested PDP-Context Activation;
1843 When the VLR receives regional subscription data (Zone Code List) it may respond with "MSC Area Restricted" in the 1844 MAP_INSERT_SUBSCRIBER_DATA response. In this case the "MSC Area Restricted Flag" shall be set to 1845 "restricted" in the HLR. This will prevent MT calls, MT SM and MT USSD from being forwarded to the MSC/VLR. 1846 If the HLR neither stores "Roaming Restriction Due To Unsupported Feature" nor receives "MSC Area Restricted" in 1847 the MAP_INSERT_SUBSCRIBER_DATA response, the "MSC Area Restricted Flag" in the HLR shall be set to "not 1848 restricted". 1849 1850 1851 1852 1853 1854 1855 1856
If subscriber data for CAMEL Phase 2 or 3 services are sent to a VLR which does not support CAMEL Phase 2 or 3, the service behaviour may be unpredictable or incorrect. The HLR therefore needs to ensure that at the conclusion of a location updating dialogue 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. 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 higher. Thus, the ISD message containing the Forwarded-to number which is not in E.164 international format shall be sent to the VLR only after the HLR receives confirmation in the first ISD message result that CAMEL Phase 2 or higher is supported.
1857 A Forwarded-to number non-international E.164 format shall only be sent from an HLR to a VLR if the VLR supports 1858 CAMEL Phase 2, or a subsequent phase of CAMEL. 1859 1860 1861 1862
When the SGSN receives regional subscription data (Zone Code List) it may respond with "SGSN Area Restricted" in the MAP_INSERT_SUBSCRIBER_DATA response. In this case the "SGSN Area Restricted Flag" shall be set to "restricted" in the HLR. This will prevent MT SM from being forwarded to the SGSN and Network Requested PDPContext Activation.
1863 If the HLR neither stores "Roaming Restricted In SGSN Due To Unsupported Feature" nor receives "SGSN Area 1864 Restricted" in the MAP_INSERT_SUBSCRIBER_DATA response, the "SGSN Area Restricted Flag" in the HLR shall 1865 be set to "not restricted".
1742
1743
1866 The SDL diagrams are shown in figures 19.4/1 and 19.4/2.
Macrodefin ition Ins ert_Subs_D ata_Framed_H LR
F ig ure 19.4/ 1: Mac ro to transf er subsc riber data f rom HLR to VLR during an exis t ing dialogue
19.4_1(1)
MA P _I NS E RT_S UBS CR I BE R_D AT A_R eq MA P _DE LI MI TE R_R eq
Count: =1
yes
A ll dat a ins ert ed
no 1
Send_Insert _ Subs _data
Figure 25.7/4
W ait _for_ Insert_S ubs_ Da ta_Cnf
F igure 25. 7/3
Co unt := Count +1
OK Count := Count -1 Replace Servic e Error A bort
Error
Abort ed
yes
C ount >0 no
no
R oaming_rest ric t ion_due_t o_unsupport ed_featu re or MS C_area_restric ted received ? yes
MS C_area_ rest ric t ed_flag := not re s tric ted
MS C_a re a_ res tric ted_flag := rest ric t ed
Ok
1867
1868
Figure 19.4/1: Macro Insert_Subs_Data_Framed_HLR
1744
1745
Macrodefin iti on Insert_Subs_Data_In_SGSN _F rame d_H LR
F ig ure 1 9.4 /2 : Ma c ro to tra ns fe r s u b sc r ibe r d ata fro m H LR t o SG S N du r in g an e xis t in g d ia lo gu e
19.4_2(1)
M A P _ IN S E R T _ S U B S C R IB E R _ D A T A _ R eq M A P _ D E L IM IT E R _ R e q
C o u n t:= 1
ye s
A ll d a ta in s erted
no 1
S en d_ In s er t_ S ub s _ d ata
F ig u r e 2 5 .7 /4
W ait_ fo r_ In s er t_ G P R S _ Su b s_ D ata _ C n f
F ig ure 25 .7 /7
C o un t:= C o un t+ 1
OK
R eplac e S ervic e
E rro r
A b o rt
C o u nt := C o un t-1 1 E rro r A bo rte d
yes
C o un t >0 no
no
ye s S G S N _a rea_ res tric t ed _flag := n o t res tric ted SG S N _a re a_ re s tric ted _ fla g := res tric te d
R oa m in g _ re str ic ted _ in _ S G S N _ d u e_ to _u n s u pp o rted _ fea tu re o r S G S N _ are a_ res tric te d re c eiv ed ?
Ok
1869
1870
Figure 19.4/2: Macro Insert_Subs_Data_In_SGSN_Framed_HLR
1746
1747
1871 1872
19.5 Mobility Management Event notification procedure
19.5.1 General
1873 The Mobility Management Event Notification VLR process (MMEN_VLR) is used to notify a gsmSCF about the 1874 successful completion of a Mobility Management event. 1875 Figure 19.5/1. depicts the MAP signalling used for the event notification. 1876
VLR
(1) -------------------------------------------------> (2) <------------------------------------------------(3) <-------------------------------------------------
gsmSCF
1877
1882
1878 1879 1880 1881
(1) (2) (3)
Report Mobility Management Event (VLR to gsmSCF). Report Mobility Management Event Result (gsmSCF to VLR). Report Mobility Management Event Error (gsmSCF to VLR).
Figure 19.5/1: Interfaces and MAP Messages for Mobility Management Event notifications
1883
19.5.2 Process in the VLR
1884 The Mobility Management event notification procedure in the VLR is triggered when the following conditions are 1885 fulfilled: 1886 1887 1888
1. the VLR has successfully completed a Mobility Management event; 2. the subscriber has a subscription to Mobility Management event notifications; 3. the Mobility Management event is marked for reporting.
1889 The VLR notifies the gsmSCF of a mobility management event with the ReportMMEvent MAP message. This message 1890 is sent in a TCAP TC-BEGIN primitive. The VLR then awaits a positive result (RESULT) or a negative result 1891 (ERROR). This is received in a TCAP TC-END primitive. The Basic End procedure is used. 1892 When the VLR has received the RESULT or ERROR, the relationship between the VLR and the gsmSCF is terminated. 1893 The relationship, if existing, is also terminated when the VLR sends a TCAP P-ABORT primitive to the calling 1894 procedure or when the VLR receives a TCAP P-ABORT or a TCAP-U-ABORT primitive from the gsmSCF. 1895 The sending process shall indicate to the MMEN_VLR process, which Mobility Management event shall be reported to 1896 the gsmSCF. 1897 The MMEN_VLR process is illustrated in figure 19.5/2.
1748
1749
Process MM_Event_Notification Process in the VLR to send a Mobility Management event notification
MMEN_VLR1(1) Signals to/from the left are to/from the Location Management processes in the VLR; signals to/from the right are to/from the gsmSCF. Idle
Send MM Event Notification
MAP_OPEN_req, MAP_REPORT_MM_EVENT_req, MAP_DELIMITER_req
Receive_ Open_Cnf OK Wait_For_ SCF_Response
Section 25.1.2
Vr, Error Abort
MAP_CLOSE_ind, MAP_P_ABORT_ind, MAP_U_ABORT_ind
MAP_ NOTICE_ ind
Idle
MAP_ CLOSE_ req
MAP_REPORT_MM_EVENT_cnf
Set negative response: System failure Send MM Event Notification negative response
Check_ Confirmation
Section 25.2.2 Provider error,
MAP_P_ ABORT_req
User error, Data error
OK
Idle Send MM Event Notification positive response
Idle
Idle
1898
1899
Figure 19.5/2: Process MM_Event_Notification_VLR (sheet 1 of 1)
1750
1751
1900
19.5.3 Process in the gsmSCF
1901 When the gsmSCF receives the ReportMMEvent MAP Message (in a TCAP TC-BEGIN primitive), the 1902 MM_Event_Notification_gsmSCF (MMEN_SCF) process is started. 1903 If the gsmSCF has validated the information it has received in the ReportMMEvent MAP Message, then it informs the 1904 Service Logic in the SCP and awaits a response. 1905 If a positive response is received from the Service Logic, then a REPORT_MM_EVENT_RESULT is sent to the VLR. 1906 If a negative response is received from the Service Logic, then a REPORT_MM_EVENT_ERROR is sent to the VLR. 1907 Both RESULT and ERROR are sent in a TCAP TC-END primitive. The Basic End procedure is used. 1908 If the Service Logic returns a User Error, then a MAP U-ABORT primitive is sent to the VLR. 1909 The gsmSCF TCAP service may choose to abort the relationship with the VLR by sending a TCAP P-ABORT 1910 primitive to the VLR. 1911 When the gsmSCF receives a TCAP P-ABORT primitive from the VLR, it shall immediately terminate the mobility 1912 management process. 1913 This is illustrated in figure 19.5/3.
1752
1753
Process MM_Event_Notification_gsmSCF Process in the gsmSCF to receive a Mobility Management event notification Idle Receive_ Open_Ind Section 25.1.1
MMEN_SCF1(1)
Signals to/from the left are to/from the VLR; signals to/from the right are to/from the Service Logic in the gsmSCF
MAP_P_ ABORT_req OK Wait_For_ Service_ Indication Vr, Error Idle
MAP_P_ ABORT_ind
MAP_REPORT_ MM_EVENT_ind Report MM Event
MAP_ NOTICE_ind
Idle
MAP_ CLOSE_req
-
Wait_For_ Service_Logic_ Response
Idle
User Error
Report MM Event Ack
Report MM Event negative response
Set error
MAP_U_ ABORT_req
MAP_REPORT_ MM_EVENT_rsp
MAP_ CLOSE_req
Idle
1914
1915
Figure 19.5/3: Process MM_Event_Notification_gsmSCF (sheet 1 of 1)
1754
1755
1916 1917
20
Operation and maintenance procedures
20.1 General
1918 The Operation and Maintenance procedures are needed for operating and maintaining the GSM PLMN network. 1919 The following procedures exist for operation and maintenance purposes: 1920 1921 1922
i) Tracing procedures; ii) Subscriber Data Management procedures; iii) Subscriber Identity procedures.
1923 The following application contexts refer to complex MAP Users consisting of several processes: 1924 1925
subscriberDataManagementContext; tracingContext.
1926 These two application contexts need a co-ordinating process in the VLR or in the SGSN as described in the following 1927 clauses.
1928
20.1.1 Tracing Co-ordinator for the VLR
1929 The MAP_OPEN indication opens the dialogue for the stand-alone tracing procedure when the application context 1930 tracingContext is received. If that service is successful, the Co-ordinator can receive the first service primitive from the 1931 MAP_PM. Depending on the received primitive, the user process is created as follows: 1932 1933 1934
if the MAP_ACTIVATE_TRACE_MODE indication is received, the process ATM_VLR_Standalone is created; if the MAP_DEACTIVATE_TRACE_MODE indication is received, the process DTM_VLR_Standalone is created.
1935 After creation of the user process the Co-ordinator relays the messages between the MAP_PM and the invoked process 1936 until a request or an indication for dialogue termination is received. 1937 The Tracing Co-ordinator is shown in the figure 20.1/1.
1756
1757
Pro cess Co _T racing_ VLR
F ig ure 20. 1/ 1: Co-ordinating proces s for t he t rac ing proc edures in the V LR
20.1_1(1)
NU LL
Rec eive_ O pen_I nd
F ig. 25. 1/1
E rror
Vr P erform Vr Di alogue
OK WF_ S E RVI C E_ P RI MI TIV E
NULL
NULL
M A P_ A C TIVA TE _ TR A CE _MO DE _ ind
M A P_ D E AC TIV A TE_ TR AC E_M OD E _ ind
M AP _NOTI CE _ ind
MA P _P _A B O RT_ind MA P_U_AB ORT _ind MA P_C LOS E _ind
A TM _V LR_ S t andalo ne
F igure 20. 2/9
DTM _V LR_ S tand alon e
F igure 20. 2/ 10
MA P_CLO S E _ req
M A P_ AC TIV A TE_ TRA CE _MO DE _ ind
M A P_ D EA C TI VE _ TR AC E_M OD E _ ind
NULL
Relay_info
* F RO M P rovider
M A P_P _A B OR T_ind M AP _U_AB O RT _ind M A P_CLO S E _ind
* FRO M O F FS PRI NG
MA P_U_A B O RT _req MA P_CLO S E _req
- TO O F FS PRI NG
- TO O FF SP RI NG
- TO P rovider
- TO P rovider
Relay_I nf o
NULL
Relay_inf o
NULL
1938
1939
Figure 20.1/1: Process Co_Tracing_VLR
1758
1759
1940
1941 1942 1943 1944 1945 1946 1947 1948
20.1.2 Subscriber Data Management Co-ordinator for the VLR
The MAP_OPEN indication opens the dialogue for the stand-alone subscriber data management procedure when the application context subscriberDataManagementContex is received. If that service is successful, the Co-ordinator can receive the first service primitive from the MAP_PM. Depending on the received primitive, the user process is created as follows: if the MAP_INSERT_SUBSCRIBER_DATA indication is received, the process INS_SUBS_DATA_VLR is created; if the MAP_DELETE_SUBSCRIBER_DATA indication is received, the process Delete_Subscriber_Data_VLR is created.
1949 After creation of the user process the Co-ordinator relays the messages between the MAP_PM and the invoked process 1950 until a request or an indication for dialogue termination is received. 1951 The Subscriber_Data_Management Co-ordinator is shown in the figure 20.1/2.
1760
1761
Process C o_Data_Manageme nt_V LR
F ig ur e 20.1/2: Co data management
20.1_2(1)
NULL
R eceive_ O pen_ Ind
F igure 25. 1/1
E rror
Vr P erform Vr Di alogue
OK WF_ S E RVI C E_ P RI MI TIV E
NULL
NULL
M A P_ I NS E RT_ S UB S CRI B ER _ D A TA _ind
M A P_ DE LE TE _ S UB SC RI B ER _ D AT A_ind
M AP _NOTI CE _ ind
MA P _P _A B O RT_ind MA P_U_AB ORT _ind MA P_C LOS E _ind
INS _S UBS _ DA TA _VLR
F igure 20. 3/5
Delete_ S ubs c riber_ Dat a_V LR
Figure 20. 3/ 7
MA P_CLO S E _ req
M A P_IN S ER T_ SUB S C RIB E R __ DA TA _ind
MA P _DE LE TE _ S UB SC RI B ER _ D AT A_ind
NULL
Relay_info
* F RO M P rovider
M A P_P _A B OR T_ind M AP _U_AB O RT _ind M A P_CLO S E _ind
* FRO M O F FS PRI NG
MA P_U_A B O RT _req MA P_CLO S E _req
- TO O F FS PRI NG
- TO O FF SP RI NG
- TO P rovider
- TO P rovider
Relay_I nf o
NULL
Relay_inf o
NULL
1952
1953
Figure 20.1/2: Process Co_Data_Management_VLR
1762
1763
1954
20.1.3 Tracing Co-ordinator for the SGSN
1955 The MAP_OPEN indication opens the dialogue for the stand-alone tracing procedure when the application context 1956 tracingContext is received. If that service is successful, the Co-ordinator can receive the first service primitive from the 1957 MAP_PM. Depending on the received primitive, the user process is created as follows: 1958 1959 1960 1961
if the MAP_ACTIVATE_TRACE_MODE indication is received, the process ATM_SGSN_Standalone is created; if the MAP_DEACTIVATE_TRACE_MODE indication is received, the process DTM_SGSN_Standalone is created.
1962 After creation of the user process the Co-ordinator relays the messages between the MAP_PM and the invoked process 1963 until a request or an indication for dialogue termination is received. 1964 The Tracing Co-ordinator for the SGSN is shown in the figure 20.1/3.
1764
1765
Pro ces s Co _Tracing_ SG SN
F ig u re 2 0. 1/ 3 : C o -o rdin atin g p roc e s s f o r th e trac in g p roc ed u re s in th e S G S N
20.1_3(1)
N UL L
R e c eiv e_ O pe n _In d
F ig . 2 5 .1/1
E rro r
Vr P erfo rm V r D ialo g u e
OK WF_ S E R V IC E _ P R IM IT IV E M A P_ P _ A B O R T _ in d M A P_ U _ A B O R T _ in d M A P _C L O S E _ in d
N UL L
NU L L
MAP_ MAP_ M A P _ NO T IC E _ A C T IV A T E _ D E A C T IV A T E _ in d T R A CE _ M O D E _T R A CE _ M O D E _ in d in d
A T M _ S G S N_ S ta n da lo ne
F ig u re 2 0 .2/1 6
D T M_SGSN _ S ta n da lo ne
F igu re 2 0 .2 /1 7
M A P _C L O S E _ req
MAP_ A C T IV A T E _ T R A C E _ MO D E _ ind
M AP_ D E A C T IV E _ T R A CE _ M O D E _ in d
N UL L
R ela y_ in fo
* F RO M P rov id er
M A P _ P _ A B O R T _ in d M A P _ U _ A B O R T _ in d M A P _C L O S E _ in d
* FR O M O F F S P R IN G
M A P _U _ A B O R T _ re q M A P _ CL O S E _ re q
- TO O F F S P R ING
- TO O F F S PR IN G
- TO P r o vid er
- TO P rov id er
Relay _In fo
NU L L
R e la y_ in fo
N UL L
1965
1966
Figure 20.1/3: Process Co_Tracing_SGSN
1766
1767
1967
1968 1969 1970 1971 1972 1973 1974 1975
20.1.4 Subscriber Data Management Co-ordinator for the SGSN
The MAP_OPEN indication opens the dialogue for the stand-alone subscriber data management procedure when the application context subscriberDataManagementContext is received. If that service is successful, the Co-ordinator can receive the first service primitive from the MAP_PM. Depending on the received primitive, the user process is created as follows: if the MAP_INSERT_SUBSCRIBER_DATA indication is received, the process INS_SUBS_DATA_SGSN is created; if the MAP_DELETE_SUBSCRIBER_DATA indication is received, the process Delete_Subscriber_Data_SGSN is created.
1976 After creation of the user process the Co-ordinator relays the messages between the MAP_PM and the invoked process 1977 until a request or an indication for dialogue termination is received. 1978 The Subscriber_Data_Management Co-ordinator is shown in the figure 20.1/4.
1768
1769
Pr o ce s s C o_ Da ta _ M an a g e me nt_ S G S N
F ig u re 2 0. 1/ 4: C o - o rdina tin g pro c e ss fo r th e su b s c rib er d ata m a na ge m en t p ro c ed u re s in th e S G S N
2 0 .1 _ 4 (1 )
N U LL
R e c eiv e_ O pe n _In d OK
F ig ur e 2 5 .1 /1
V r , E rro r
W F_ S E R V IC E _ P R IM IT IV E
N UL L
M AP_ IN S E R T _ S U B S C R IB E R _ D A T A _ ind
M AP_ D E LE T E _ S U B S C R IB E R _ D A T A _ in d
M A P _ N O T IC E _ in d
M A P _P _ A B O R T _ind M A P _U _ A B O R T _ in d M A P _ C L O SE _ ind
F ig u re 2 0 .3 /1 1
IN S _ S U B S _ D A T A _S G S N
D e lete _ S u b sc r ibe r _ D at a_ S G S N
F ig ur e 2 0 .3 / 12
M A P _ CL O S E _ r eq
M A P _IN S E R T _ S U B S C R IB E R _ _ D A T A _ in d
M AP _D ELETE_ S U B S C R IB E R _ D A T A _ ind
N U LL
R elay_ in fo
* F RO M P r ov id er
M A P _ P _ A B O R T _ in d M A P _U _ A B O R T _ in d * F R O M O F F S P R IN G M A P _ C L O S E _ in d
M AP _ U_A B O RT _ r eq M AP_CLO SE _ r eq
- TO O F F S P R IN G
- TO O F F S P R IN G
- TO P r o vid e r
- TO P ro vid er
R e lay _ In fo
NU L L
R ela y_ in fo
N UL L
1979
1980
Figure 20.1/4: Process Co_Data_Management_SGSN
1770
1771
1981
20.2 Tracing procedures
i) Subscriber tracing management procedures; ii) Subscriber tracing procedures; iii) Event tracing procedures. The subscriber tracing management procedures are used for management of 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 for providing a trace request to the VLR are shown in figures 20.2/1 and 20.2/2. The procedures for providing a trace request to the SGSN are shown in figures 20.2/11 and 20.2/12. +-----+ +------+ +-------+ VLR HLR OMC +-----+ +------+ +-------+ 1. 2. +< - - - - - - - - - +<------------------ 3. +------------------> 4. + - - - - - - - - - >
1) 2) 3) 4) Subscriber Tracing Activation. MAP_ACTIVATE_TRACE_MODE. MAP_ACTIVATE_TRACE_MODE_ACK. Subscriber Tracing Activation Accepted.
1982 Three types of tracing procedures exist: 1983 1984 1985 1986 1987 1988 1989 1990
1991 1992 1993 1994 1995 1996 1997 1998 1999 2000
2007 2008
2009 2010 2011 2012 2013 2014 2015 2016 2017 2018
2002 2003 2004 2005 2006
Figure 20.2/1: Stand alone subscriber tracing activation procedure
+-----+ +------+ +-------+ SGSN HLR OMC +-----+ +------+ +-------+ 1. 2. +< - - - - - - - - - +<------------------ 3. +------------------> 4. + - - - - - - - - - >
1) 2) 3) 4) Subscriber Tracing Activation. MAP_ACTIVATE_TRACE_MODE. MAP_ACTIVATE_TRACE_MODE_ACK. Subscriber Tracing Activation Accepted.
2025 2026
2020 2021 2022 2023 2024
Figure 20.2/11: Stand alone subscriber tracing activation procedure for GPRS
1772
1773
2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039
+-----+ +------+ VLR HLR +-----+ +------+ 1. +------------------> 2. +<------------------ 3. +------------------> 4. +<------------------
1) 2) 3) 4) MAP_UPDATE_LOCATION or MAP_RESTORE_DATA. MAP_ACTIVATE_TRACE_MODE. MAP_ACTIVATE_TRACE_MODE_ACK. MAP_UPDATE_LOCATION_ACK or MAP_RESTORE_DATA_ACK.
2046 2047
2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060
2041 2042 2043 2044 2045
Figure 20.2/2: Subscriber tracing activation procedure at location updating or data restoration
+-----+ +------+ SGSN HLR +-----+ +------+ 1. +------------------> 2. +<------------------ 3. +------------------> 4. +<------------------
1) 2) 3) 4) MAP_UPDATE_GPRS_LOCATION. MAP_ACTIVATE_TRACE_MODE. MAP_ACTIVATE_TRACE_MODE_ACK. MAP_UPDATE_GPRS_LOCATION_ACK.
2067 2068 2069 2070 2071
2062 2063 2064 2065 2066
Figure 20.2/12: Subscriber tracing activation procedure at GPRS location updating The HLR sends the trace request (IMSI, trace reference, trace type and identity of the OMC) to the VLR or to the SGSN in a MAP_ACTIVATE_TRACE_MODE request. The receipt of this primitive is acknowledged. The acknowledge primitive will indicate that the trace request is accepted by the VLR or by the SGSN. If the request is not accepted, the reason will be reported to the HLR.
2072 The subscriber tracing deactivation procedure is used when the trace request of a subscriber is to be cancelled in the 2073 VLR or in the SGSN. The procedures is shown in figures 20.2/3 and 20.2/13.
2074 2075 2076 2077 2078 2079 2080 2081 2082 2083
+-----+ +------+ +-------+ VLR HLR OMC +-----+ +------+ +-------+ 1. 2. +< - - - - - - - - - +<------------------ 3. +------------------> 4. + - - - - - - - - - >
1) 2) 3) 4) Subscriber Tracing Deactivation. MAP_DEACTIVATE_TRACE_MODE. MAP_DEACTIVATE_TRACE_MODE_ACK. Subscriber Tracing Deactivation Accepted.
2084
2090
2085 2086 2087 2088 2089
Figure 20.2/3: Subscriber tracing deactivation procedure
1774
1775
2091 2092 2093 2094 2095 2096 2097 2098 2099 2100
+-----+ +------+ +-------+ SGSN HLR OMC +-----+ +------+ +-------+ 1. 2. +< - - - - - - - - - +<------------------ 3. +------------------> 4. + - - - - - - - - - >
1) 2) 3) 4) Subscriber Tracing Deactivation. MAP_DEACTIVATE_TRACE_MODE. MAP_DEACTIVATE_TRACE_MODE_ACK. Subscriber Tracing Deactivation Accepted.
2107
2101 2102 2103 2104 2105 2106
Figure 20.2/13: Subscriber tracing deactivation procedure for GPRS
2108 The HLR sends a MAP_DEACTIVATE_TRACE_MODE request to the VLR or to the SGSN. The VLR or the SGSN 2109 will acknowledge the deactivation. The acknowledge primitive will indicate that the trace request has been deleted by 2110 the VLR or by the SGSN. If the deactivation is not accepted, the reason will be reported to the HLR. 2111 The subscriber tracing procedures are used when the VLR detects any subscriber related activity for which the trace 2112 mode is activated, e.g. receives the MAP_PROCESS_ACCESS_REQUEST indication. The procedure is shown in 2113 figure 20.2/4.
2114 2115 2116 2117 2118 2119 2120 2121 2122 2123
+-----+ +------+ MSC VLR +-----+ +------+ 1. +------------------> 2. +<------------------ + - - - - - - - - - + - - - - - -
1) 2) 3)
+-------+ OMC +-------+ 3. - - >
2129
2124 2125 2126 2127 2128
MAP_PROCESS_ACCESS_REQUEST, MAP_UPDATE_LOCATION_AREA. MAP_TRACE_SUBSCRIBER_ACTIVITY. Subscriber tracing information.
Figure 20.2/4: Subscriber tracing procedure in the servicing MSC
2130 The VLR will generate the MAP_TRACE_SUBSCRIBER_ACTIVITY indication. The receiving MSC will send the 2131 trace record to the OMC. 2132 [Figure numbers 20.2/5 and 20.2/6 are spare.]
2133 2134 20.2.1.1
20.2.1 Procedures in the HLR
Subscriber tracing activation procedure
2135 When receiving the subscriber tracing mode activation command for a subscriber from the OMC, the HLR will activate 2136 tracing, if the subscriber is known and registered in the HLR and the subscriber is roaming in the home PLMN area. 2137 The MAP_ACTIVATE_TRACE_MODE request is sent to the VLR or to the SGSN where the subscriber is registered. 2138 If the MAP_ACTIVATE_TRACE_MODE confirmation is received indicating an error situation, the errors are mapped 2139 to the OMC interface. The activation request may also be repeated; the number of repeat attempts and the time in 2140 between are HLR operator options, depending on the error returned by the VLR or the SGSN. 2141 If the subscriber is known in the HLR, but is deregistered or roaming outside the home PLMN area, the subscriber 2142 tracing status is activated in the HLR, but the VLR or the SGSN is not updated. 2143 When receiving a request for location updating or data restoration while the subscriber trace mode is active, the macro 2144 Control_Tracing_HLR (see figure 25.9/4) shall be initiated by the location updating process in the HLR. 2145 The subscriber tracing activation process in the HLR with VLR is shown in figure 20.2/7.
1776
1777
2146 The subscriber tracing activation process in the HLR with SGSN is shown in figure 20.2/14.
Proc ess ATM_HLR _w ith_ VLR
F ig u re 2 0.2 /7 : T h e s ub s c rib e r t rac i ng a c tiv a tion pro c es s in th e H L R N UL L
20.2_7.1(2)
O M _S u bs c r ibe r_ _T ra c in g _ _A c ti v at io n_ _re q no
N UL L
S u b s cribe r K n ow n y es
y es T ra c in g a lre ad y ac tiv e ? 1 P ag e 1 no Set S u bs c rib e r T rac in g = A c tive in H L R S et Erro r T ra c in g alrea dy a c tiv e
S e t E rro r U nk no w n S u bs c rib e r
R ep e at a tte m p t no S e t s u bs c ribe r t rac in g = de ac tiv e in V LR
y es
D ere gis tere d S u bs c rib e r I nc rem e n t a tte m p t c o u nte r no S u b s cribe r in Ho me P L M N a rea y es
ye s
no
O M _ S ub s c r ib er_ _ T ra cing _ _ A ct iv a tion _ _ c nf
R ep ea t a tte m p t d ela y
M A P _ O P EN _re q M A P _A C T IV A T E _ _T R A C E _ M O D E _ re q M A P _ D E LI M I T E R S e t s u bs c ribe r t rac in g a c tiv at io n f a il ure
S et S u b s cri be r T rac ing = N ot A c tiv e in V LR
R e c eiv e_ O pe n_ C nf
O M _ S ub s c rib er_ _ T ra ci ng _ _ A ct iva tion _ _ c nf Vr P e rform _ M A P _ Vr_ D ia log u e OK
E rror
N UL L
N UL L
1 P ag e 1
N UL L
W F_ _A T M _ _R E SU L T
2147
2148
Figure 20.2/7 (sheet 1 of 2): Process ATM_HLR_with_VLR
1778
1779
Proc ess ATM_HLR _w ith_ VLR
F ig u re 2 0.2 /7 : T h e s ub s c rib e r t rac ing a c tiv a tion pro c es s in th e H L R
20.2_7.2(2)
W F_ _ A TM _ _ R ES U LT
MAP_ _ AC T IV A T E _ _T R A CE _ _ M O D E _c n f
M A P_ C LO S E _ in d , M A P _U _A B O R T _ in d, M A P _P _ A B O R T _ in d
M AP_ _ NO TICE
E rro r y es no S e t S u b s cribe r T ra c ing = A c tiv e in V LR O M _ S ub s c rib er_ _ T ra cing _ _ A ct iv a tion _ _ c nf S e t S u bs c rib e r T ra c in g = D e a c tiv e in V L R 1 Page 1
MA P _ C L O S E _ req
N ULL
2149
2150
Figure 20.2/7 (sheet 2 of 2): Process ATM_HLR_with_VLR
1780
1781
Process ATM_HLR_with_SGSN
NU LL F igure 20.2/14: T he subsc riber tracing activati on proc ess in the HLR w ith SGSN OM_GPRS_Subs criber _ _Tracing_ _Activation_ _req
20.2_14.1(2)
NU LL
GPRS Subsc riber Know n yes yes 1 Page 1 Trac ing already active ? no Set Subscriber Tracing = Ac tive in HLR yes no Set subscriber tracin g = deactive in SGSN Deregistered Subscriber Increm ent attem pt c ounter yes no Subsc riber in H om e PLMN area no Set Subsc riber Trac ing = Not Active in SGSN yes Set Error Tracing already active
no
Set Error Unknow n Subscriber
R epeat attem pt
OM _GPR S_ Subsc riber_ Tracing_ Activation_rsp
R epeat attem pt delay
Set subscriber tracin g activati on f ailure
M AP_OPEN_req M AP_ACTIVATE__TRAC E_M ODE_req M AP_D ELIMITER OM _GPRS_Subsc riber_ _Tr acing_ _Activation_ _rs p
R eceive_ Open_Cnf
Error
Vr Perform_ M AP_Vr_ D ialogue
OK NU LL
NU LL
1 Page 1
N ULL
W F_ _ATM _ _R ESU LT
2151
2152
Figure 20.2/14 (sheet 1 of 2): Process ATM_HLR_with_SGSN
1782
1783
Process ATM_HLR_with_SGSN
F igure 20.2/14: T he subsc riber tracing activation proc ess in the HLR w ith SGSN
20.2_14.2(2)
W F_ _ATM _ _R ESULT
MAP_ _AC TIVATE_ _T RACE_ _M OD E_cnf
M AP_CLOSE_ind, M AP_U_ABORT_ind, MAP_P_ABORT_ind
MAP_ _NOTICE
yes Error no Set Subsc riber Tracing = Active in SGSN Set Subscriber Tr acing = Deactive in SGSN 1 Page 1
MAP_C LOSE_ req
OM _GPR S_Subsc riber_ _Tracing_ _Activation_ _rs p
NU LL
2153
2154
Figure 20.2/14 (sheet 2 of 2): Process ATM_HLR_with_SGSN
1784
1785
2155 20.2.1.2
Subscriber tracing deactivation procedure
2156 When receiving the subscriber trace mode deactivation command for a subscriber from the OMC, the HLR will send the 2157 MAP_DEACTIVATE_TRACE_MODE request to the VLR or to the SGSN where the subscriber is registered, if the 2158 trace mode activation has been carried out. The subscriber tracing in HLR is set to a deactive state. 2159 If the operation is successful, the HLR will set the subscriber tracing in VLR or in SGSN to a deactive state. 2160 If the MAP_DEACTIVATE_TRACE_MODE confirmation is received indicating an error situation, the errors are 2161 mapped to the OMC interface. The deactivation request may be also repeated; the number of repeat attempts and the 2162 time in between are HLR operator options, depending on the error returned by the VLR or by the SGSN. 2163 The subscriber tracing deactivation procedure with VLR is shown in figure 20.2/8. 2164 The subscriber tracing deactivation procedure with SGSN is shown in figure 20.2/15.
1786
1787
Process DTM_HLR_w ith_VLR
F ig ure 2 0.2 /8 : T h e su b s cr ib er tra c in g d eac t iv a tio n p roc e s s in t he HL R N ULL
20.2_8.1(2)
O M _S u bs c ribe r_ _T ra c in g _ _ D ea c tiv at io n_ _re q no
N UL L
1 P ag e 1
S u b s cribe r K n ow n y es S u b s cribe r T r ac in g = A c tiv e in H L R y es S e t S u bs c ribe r T ra c in g = D ea c tive in H L R
R ep e at a tte m p t no S e t s u bs c ribe r t rac in g = de ac tiv e in V LR
y es
no
I nc rem e n t a tte m p t c o u nte r
S et erro r U nk n ow n S u bs c rib e r no
O M _ S ub s c r ib er_ _ T ra cing _ _ D e a ct iva tion _ _ c nf S e t s u bs c ribe r t rac in g d e ac tiv at io n f a ilure
R ep ea t a tte m p t d ela y
'S u bs cribe r T r ac in g = A c tiv e in VL R ' y es
M A P _ O P EN _re q M A P _ D E AC T IV A T E_ _ T R A C E _M O D E _re q M A P _ D E LI M I T E R O M _ S ub s c rib er_ _ T ra cing _ _ D ea c tiva tion _ _ c nf OK
R e c eiv e_ O pe n_ C nf
E rro r 1 P ag e 1
Vr Pe rfo rm _ MA P _ Vr _ D ialog u e
N UL L
N U LL
W F_ _D T M _ _R E S U L T
N UL L
2165
2166
Figure 20.2/8 (sheet 1 of 2): Process DTM_HLR_with_VLR
1788
1789
Process DTM_HLR_w ith_VLR
F ig ure 2 0.2 /8 : T h e su b s cr ib er tra c in g d eac t iv a tio n p roc e s s in t he HL R
20.2_8.2(2)
W F_ _ DT M _ _ R E S U LT
M A P_ _ D E AC T IV A T E_ _T R A C E _ _ MO D E _c n f
M A P _C LO S E _ in d , M A P _U _ AB O R T _ in d, M A P _P _ A B O R T _ in d
M AP_ _ NO T I C E
MA P _ CL O S E _ req ye s E rro r no S e t S u bs c ribe r T ra c in g = D ea c tiv e in V L R O M _ S ub sc ribe r_ _ T rac ing _ _ D e a ct iv a tion _ _ c nf 1 Page 1
NU L L
2167
2168
Figure 20.2/8 (sheet 2 of 2): Process DTM_HLR_with_VLR
1790
1791
Pro cess DTM _HLR _with_SGSN
F ig u re 2 0. 2/ 1 5: T he s u b sc rib e r trac ing d ea c tiv atio n p ro c es s in th e HL R w ith S G S N N UL L
20.2 _15.1(2 )
O M _ G P R S _S u b s c rib er _ T rac in g _ D ea c tiv at ion _ re q
N UL L
1 P ag e 1
G P RS S u b s c ribe r K n ow n y es yes S u b s c ribe r T r ac in g = A c t ive in H L R yes In c rem e nt a tte mp t c o u nt er S e t S u b sc ribe r T r ac in g = D eac tiv e in H L R no
no
R e pe at a tte m p t
no S e t s u b sc ribe r t rac in g = de ac t ive in S G S N O M _G P R S _ S u b s c rib er T rac in g _ D ea c tiv ation _ rsp Se t s u b sc ribe r trac in g dea c tivat io n failure
S et erro r U nk no w n S u b sc rib e r
R ep e at a tte mp t d elay
y es
'S u b s c rib er T r ac in g = A c t ive in S G S N '
no
M A P _ O P E N _re q M A P _ D E A C T IV A T E _ _ T R A C E _ MO D E _ req M A P _ D E LIM IT ER Re c eive_ O p en _ C n f Vr O M _ G P R S _ S ub s c rib er_ _ T ra c ing _ _ D ea c tiva tion _ _ rs p
E rro r 1 P ag e 1
OK
P erfo rm _ MA P _ V r_ Dialo g ue
N UL L
NU LL
W F_ _ DT M _ _ RE S U L T
N UL L
2169
2170
Figure 20.2/15 (sheet 1 of 2): Process DTM_HLR_with_SGSN
1792
1793
Pro cess DTM _HLR _with_SGSN
F ig u re 2 0. 2/ 1 5: T he s u b sc rib e r trac ing d ea c tiv atio n p ro c es s in th e HL R w ith S G S N
20.2 _15.2(2 )
W F_ _ D TM _ _ R E SUL T
M A P_ _ D E A C T IV A T E _ TRA C E _M O D E _ c n f
M A P _ C L O S E _ in d , M A P _ U _ A B O R T _ in d , M A P _ P _A B O R T _ ind
M AP _ _N O T IC E
M AP _ C LO S E _ re q yes E rro r no S e t S u b sc ribe r T r ac in g = D ea c tiv e in S G S N O M_ G P R S _ S u b sc ribe r T ra c in g _ D ea c tiva tion _ rs p 1 Page 1
NU L L
2171
2172
Figure 20.2/15 (sheet 2 of 2): Process DTM_HLR_with_SGSN
1794
1795
2173
20.2.2 Procedures in the VLR
i) Subscriber tracing activation procedure; ii) Subscriber tracing deactivation procedure; iii) Subscriber tracing procedure.
2174 The VLR is involved in the following tracing procedures: 2175 2176 2177
2178 20.2.2.1
Subscriber tracing activation procedure
2179 When receiving a MAP_ACTIVATE_TRACE_MODE indication, the VLR will check the parameters and data in the 2180 primitive. Data errors are reported as an unexpected data value error or as a data missing error depending on the nature 2181 of the error. 2182 If the subscriber is known, the tracing facility is supported and the tracing capacity is not exceeded, the successful 2183 report is sent in the MAP_ACTIVATE_TRACE_MODE response primitive. 2184 The MAP_ACTIVATE_TRACE_MODE indication primitive may be received during a location updating or data 2185 restoration procedure, so the location updating or restore data process shall use the macro Activate_Tracing_VLR (see 2186 figure 25.9/3). 2187 The subscriber tracing activation process in the VLR is shown in figure 20.2/9.
1796
1797
Process ATM_VLR_Standalone
FIGURE 20. 2/9 The subscriber tracing activation process f or standalone operation in t he VLR
20.2_9(1)
NULL
MA P_ACTIV ATE_ _TRA CE _ _MODE _ind
Check_ Indication
OK S ubscri ber known no
E rror
yes
S ET UE = UNIDE NTIFIED S UB SCRIBE R
Tracing supported
no
yes
SE T UE = FACILITY NOT SUPP ORTE D
Tracing buff er f ull no
yes
Set S ubscri ber Tracing = Act ive
SE T UE = TRACING BUFFER FULL
MAP _ACTIVA TE_TRA CE_MODE _rs p MAP _CLOS E
2188
2189
Figure 20.2/9: Process ATM_VLR_Standalone
1798
1799
2190 20.2.2.2
Subscriber tracing deactivation procedure
2191 When receiving a MAP_DEACTIVATE_TRACE_MODE indication, the VLR will check the parameters and data in 2192 the primitive. Data errors are reported as an unexpected data value error or as a data missing error depending on the 2193 nature of the error. 2194 If the subscriber is known and the tracing facility is supported, the successful report is sent in the 2195 MAP_DEACTIVATE_TRACE_MODE response primitive. 2196 The subscriber tracing deactivation procedure in the VLR is shown in figure 20.2/10.
1800
1801
Process DTM_VLR_Standalone
Figure 20.2/10: The s ubscriber t racing deac tivation proces s in the VLR
20.2_10(1)
NULL
MA P_ _DEA CTIVA TE _ _TRA CE_ _MODE_ind
Check_ Indicat ion
OK Subscriber known no
Error
yes
S ET UE = UNIDENTIFIE D S UBS CRIBE R
Tracing supported
no
yes
Set Subscriber Tracing = Dea ctive
S ET UE = FACILITY NOT SUP PORTE D
MAP _DE ACTIV ATE_TRACE_MODE_rsp MAP _CLOSE _req
2197
2198
Figure 20.2/10: Process DTM_VLR_Standalone
1802
1803
2199 20.2.2.3
Subscriber tracing procedure
2200 When the VLR receives a MAP_PROCESS_ACCESS_REQUEST or MAP_UPDATE_LOCATION_AREA indication 2201 related to any subscriber activity from the MSC, the subscriber tracing procedure may be carried out. The macro 2202 Trace_Subscriber_Activity_VLR is shown in figure 25.9/2. 2203
20.2.3 Procedures in the MSC
i) Subscriber tracing procedure.
2204 The MSC is involved in the following tracing procedure: 2205
2206 20.2.3.1
Subscriber tracing procedure
2207 When receiving the MAP_TRACE_SUBSCRIBER_ACTIVITY indication from the VLR, the MSC stores trace 2208 reference, trace type and the identity of the OMC in charge of the trace, and the MSC starts to collect the trace 2209 information. The MSC will send the trace record to the OMC. 2210 The macro Trace_Subscriber_Activity_MSC is shown in figure 25.9/1.
2211
20.2.4 Procedures in the SGSN
i) Subscriber tracing activation procedure; ii) Subscriber tracing deactivation procedure.
2212 The SGSN is involved in the following tracing procedures: 2213 2214
2215 20.2.4.1
Subscriber tracing activation procedure
2216 When receiving a MAP_ACTIVATE_TRACE_MODE indication, the SGSN will check the parameters and data in the 2217 primitive. Data errors are reported as an unexpected data value error or as a data missing error depending on the nature 2218 of the error. 2219 If the subscriber is known, the tracing facility is supported and the tracing capacity is not exceeded, the successful 2220 report is sent in the MAP_ACTIVATE_TRACE_MODE response primitive. 2221 The MAP_ACTIVATE_TRACE_MODE indication primitive may be received during a location updating or data 2222 restoration procedure, so the location updating or restore data process shall use the macro Activate_Tracing_SGSN (see 2223 figure 25.9/7). 2224 The subscriber tracing activation process in the SGSN is shown in figure 20.2/16.
2225 20.2.4.2
Subscriber tracing deactivation procedure in SGSN
2226 When receiving a MAP_DEACTIVATE_TRACE_MODE indication, the SGSN will check the parameters and data in 2227 the primitive. Data errors are reported as an unexpected data value error or as a data missing error depending on the 2228 nature of the error. 2229 If the subscriber is known and the tracing facility is supported, the successful report is sent in the 2230 MAP_DEACTIVATE_TRACE_MODE response primitive. 2231 The subscriber tracing deactivation procedure in the SGSN is shown in figure 20.2/17.
1804
1805
Process ATM_SGSN_Standalone
F IGU RE 20. 2/16: The s ubscriber tracing activation process f or standalone operation in the SGSN
20.2_16(1)
NU LL
MAP_ACTIVATE _TRACE _MOD E_ind
Check _ Indication
OK Subsc riber k nown no
Error
yes
SET U E = UNID EN TIFIED SU BSCR IBER no
Tracing s upported
yes
SET U E = FACILITY N OT SU PPORTED yes
Tracing buf fer f ull no Set Subscr iber Tracing = Active
SET U E = TR ACIN G BUFF ER FU LL
M AP_AC TIVATE_TRACE_MOD E_rsp M AP_CLOSE
2232
2233
Figure 20.2/16: Process ATM_SGSN_Standalone
1806
1807
Process DTM_SGSN_Standalone
F igure 20.2/17: T he subscriber tracing deactivation process in the SGSN
20.2_17(1)
NULL
MAP_ _DEACTIVAT E_ _TRACE_ _MOD E_ind
Check_ Indic ation
OK Subscriber known yes no
Error
SET U E = UNID EN TIFIED SU BSC RIBER no
Tracing supported yes Set Subscriber Tracing = Deactive
SET U E = FACILITY NOT SUPPOR TED
MAP_D EACTIVATE_TR AC E_M ODE_rs p MAP_C LOSE_req
2234
2235
Figure 20.2/17: Process DTM_SGSN_Standalone
1808
1809
2236
20.3 Subscriber data management procedures
i) Subscriber Deletion; ii) Subscriber Data Modification.
2237 Two types of subscriber data management procedures exist in the Mobile Application Part 2238 2239
2240 No requirements have been identified for the Subscriber creation and subscriber data interrogation procedures. 2241 The subscriber deletion and subscriber data modification procedures are initiated by the OMC (see figures 20.3/1 , 2242 20.3/2, 20.3/8 and 20.3/9).
2243 2244 2245 2246 2247 2248 2249 2250 2251
+-----+ +------+ +-------+ VLR HLR OMC +-----+ +------+ +-------+ 1. 2. +< - - - - - - - - - +<------------------ 3. +------------------> 4. + - - - - - - - - - >
1) 2) 3) 4) Delete Subscriber. MAP_CANCEL_LOCATION. MAP_CANCEL_LOCATION_ACK. Subscriber Deleted.
2258
2252 2253 2254 2255 2256 2257
Figure 20.3/1: Subscriber deletion procedure
2259 In the subscriber deletion procedure the subscriber data should be removed from the VLR and from the HLR. The HLR 2260 uses the MAP_CANCEL_LOCATION service.
2261 2262 2263 2264 2265 2266 2267 2268 2269
+-----+ +------+ +-------+ SGSN HLR OMC +-----+ +------+ +-------+ 1. 2. +< - - - - - - - - - +<------------------ 3. +------------------> 4. + - - - - - - - - - >
1) 2) 3) 4) Delete GPRS Subscriber. MAP_CANCEL_LOCATION. MAP_CANCEL_LOCATION_ACK. GPRS Subscriber Deleted.
2276
2270 2271 2272 2273 2274 2275
Figure 20.3/8: Subscriber deletion procedure for GPRS
2277 In the subscriber deletion procedure the subscriber data should be removed from the SGSN and from the HLR. The 2278 HLR uses the MAP_CANCEL_LOCATION service.
2279 2280 2281 2282 2283 2284 2285 2286 2287
+-----+ +------+ +-------+ VLR HLR OMC +-----+ +------+ +-------+ 1. 2. +< - - - - - - - - - +<------------------ 3. +------------------> 4. + - - - - - - - - - >
1) 2) 3) 4) Modify Subscriber Data. MAP_CANCEL_LOCATION, MAP_INSERT_SUBSCRIBER_DATA or MAP_DELETE_SUBSCRIBER_DATA. MAP_CANCEL_LOCATION_ACK, MAP_INSERT_SUBSCRIBER_DATA_ACK or MAP_DELETE_SUBSCRIBER_DATA_ACK. Subscriber Data Modified.
2288 2289 2290 2291 2292 2293 2294 2295
1810
1811
2296 2297
2298 2299 2300 2301 2302 2303 2304 2305 2306
Figure 20.3/2: Subscriber data modification procedure
+-----+ +------+ +-------+ SGSN HLR OMC +-----+ +------+ +-------+ 1. 2. +< - - - - - - - - - +<------------------ 3. +------------------> 4. + - - - - - - - - - >
1) 2) 3) 4) Modify Subscriber Data. MAP_CANCEL_LOCATION, MAP_INSERT_SUBSCRIBER_DATA or MAP_DELETE_SUBSCRIBER_DATA. MAP_CANCEL_LOCATION_ACK, MAP_INSERT_SUBSCRIBER_DATA_ACK or MAP_DELETE_SUBSCRIBER_DATA_ACK. Subscriber Data Modified.
2307
2315 2316 2317 2318 2319
2308 2309 2310 2311 2312 2313 2314
Figure 20.3/9: Subscriber data modification procedure for GPRS In the subscriber data modification procedure the subscriber data is modified in the HLR and when necessary also in the VLR or in the SGSN. The HLR initiates either the MAP_INSERT_SUBSCRIBER_DATA,MAP_DELETE_SUBSCRIBER_DATA or MAP_CANCEL_LOCATION service depending on the modified data.
2320 2321 20.3.1.1
20.3.1 Procedures in the HLR
Subscriber deletion procedure
2322 When the subscriber deletion request is received from the OMC, the HLR shall delete the subscriber data from the HLR 2323 and initiate the MAP_CANCEL_LOCATION request to the VLR or to the SGSN where the subscriber is registered. 2324 The subscriber deletion procedure in the HLR is shown in the figure 20.3/3.
1812
1813
Process D elete_Subsc riber_H LR
F ig u re 1 7.3 /3 : T he s u bs c rib e r de le tion p ro c e ss in th e H L R N ULL
20.3_3(1)
O M _D elete _ _S u bs c ribe r_ _re q
N UL L
S u b s cribe r K n ow n y es no S u b s cribe r R e gis te re d in a S G S N y es C a nc e l_ G P R S _ L o ca tion _ H LR
no
F ig ure 19 .1 .2/ 4
S et erro r U nk n ow n S u bs c rib e r
no
S u b s cribe r R e gist ere d in a V L R y es C a n c el_ Lo c a tio n _ HL R F ig ure 19 .1 .2/ 2
D e le te S u b s cribe r D a ta
OM_ _S u bs c ribe r_ _ D e le tion _ _ rs p
N ULL
2325
2326
Figure 20.3/3: Process Delete_Subscriber_HLR
1814
1815
2327 20.3.1.2
Subscriber data modification procedure
2328 The OMC can modify the subscriber data in several different ways. The modifications can be categorised in following 2329 groups: 2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342
a) no effect in the VLR; b) data shall be modified in both the HLR and the VLR; c) withdrawal of a basic service or a supplementary service requiring change to VLR data; d) modification affects on the roaming of the subscriber and the subscriber shall be removed from the VLR data base; e) authentication algorithm or authentication key of the subscriber is modified; f) no effect in the SGSN; g) data shall be modified in both the HLR and the SGSN; h) withdrawal of a GPRS subscription data or a basic service or both requiring change to SGSN data; i) modification affects on the roaming of the subscriber and the subscriber shall be removed from the SGSN data base; j) withdrawal of GPRS Subscription related to Network Access Mode; k) withdrawal of non-GPRS Subscription related to Network Access Mode;
2343 In case "b" and g the MAP_INSERT_SUBSCRIBER_DATA service is initiated in the HLR. 2344 In case "c" and h the MAP_DELETE_SUBSCRIBER_DATA service is initiated in the HLR. 2345 In cases "d", "e", i, j and k the MAP_CANCEL_LOCATION service is initiated in the HLR. 2346 If the result of a primitive received from the VLR or from the SGSN is unsuccessful, the HLR may initiate re-attempts; 2347 the number of repeat attempts and the time in between are HLR operator options, depending on the error returned by the 2348 VLR or by the SGSN. 2349 The subscriber data modification procedure in the HLR is shown in the figures 20.3/4, 20.3/5 and 25.7/2.
1816
1817
Process Modify_Data_HLR
Figure 20.3/4: The subscriber data modif ication process in the HLR N ULL
20.3_4.1(2)
OM_Modify_ Subsc riber_ Data_req no
1 page 1
Subsc riber Know n yes Modify Subsc riber D ata in HLR OM_Modify _Subscriber _Data_rs p Subsc riber R egistered in a VLR yes Type of modific ation
no
Repeat operation yes W ait for repetition timer expiring
Set Error Unknow n Subscr iber OM_Modify_ Subscriber_ Data_rs p no Null
2 Page 2
2 Page 2
d,e,k
2 Page 2
Insert_Subs_ Data_Stand_ Alone_HLR
F igure 25.7/2
Delete_ Subscriber_ Data_HLR
F igure 20.3/5
Cancel_ Location_ HLR
Figure 19.1.2/2
Error 2 Page 2 1 Page 1
Ok 2 Page 2 2 Page 2
2350
2351
Figure 20.3/4 (sheet 1 of 2): Process Modify_Data_HLR
1818
1819
Process Modify_Data_HLR
F igure 20.3/4: T he subscr iber data m odific ation process in the H LR
20.3_4.2(2)
2 Page 2
3 page 2
no
Repeat oper ation yes
Subscriber R egistered in a SGSN yes
no
Null
W ait for repetition timer expiring Null Type of m odific ation
e,i,j
Null
Insert_GPRS_ Subs_ Figure 25.7/5 Da ta_Stand_ Alone_HL R
D elete_GPRS_ Subs cri ber _ D ata_H LR
F igure 20.3/10
Cancel_GPRS_ Location_HLR
Figure 19 .1.2/4
Err or N ull 3 Page 2
Ok Null Null
2352
2353
Figure 20.3/4 (sheet 2 of 2): Process Modify_Data_HLR
1820
1821
Macrodefiniti on De lete_GPRS_Subscriber_D ata_H LR
F ig u re 2 0.3 /1 0 : T he d elete G P R S s u bs c rib er d a ta m a c ro in the H LR
20.3 _10(1)
M A P _ O P E N _ req M A P _ D E L E T E _S U B S C R IB E R _ D A T A _ re q M A P _ D E L IM IT E R
R ec e ive _ O pe n_ C n f
OK
V r, E rro r
W a it_ F o r_ _ C o nf irm
M A P _D E L E T E _ _ S U B S C R IB E R _ _D A T A _ c n f
M A P _ N O T IC E _ in d
M A P _ U _ A B O R T _ in d , M A P _ P _A B O R T _in d, M A P _ C L O S E_ in d
M A P _ C LO S E _ re q
ye s E rro r no
no
M S C _A re a_ R e s tric te d_ re c eiv ed o r "R o am in g _ R es tric ted _ In_ S S G N _ D u e _ T o _U n su p p orte d _F ea ture " ye s
S G S N _A re a_ _ R es t ric ted _ F la g = n o t_ re st ric ted
SG S N _ A rea _ _R es tr ic t ed _F lag = res tric te d
OK
E rro r
2354
2355
Figure 20.3/10: Macro Delete_GPRS_Subscriber_Data_HLR
1822
1823
Macrodefinition Delete_Subscriber_Data_HLR
Figure 17.3/5: The delete subs criber data macro in the HLR
20.3_5(1)
MAP _O PE N_req MAP _DELETE_SUBS CRIB ER_DA TA _req MAP _DELIMITE R
Receive_ Open_Cnf
Vr
OK
E rror
Perform_ MA P_Vr_ Dialogue
W ait _For_ _Confirm
M AP_DE LETE _ _S UB SCRIB ER_ _DATA_cnf
MA P_N OTICE_ ind
MAP _U_ABORT_ind, MAP _P _A BORT_ind, MAP _CLOSE_ind
MA P_C LOSE _ req
yes E rror no
no
MSC_Area_Restric ted_rec eived or "Roaming_Restrict ed_Due_To_Unsupported_Feat ure" yes
MSC_A rea_ _Rest rict ed_Flag = not_restrict ed
MS C_A rea_ _Restricted_ Flag = restricted
E rror OK
2356
2357
Figure 20.3/5: Macro Delete_Subscriber_Data_HLR
1824
1825
2358 2359 20.3.2.1
20.3.2 Procedures in the VLR
Subscriber deletion procedure
2360 The subscriber deletion procedure in the VLR is described in the clause 19.1.
2361 20.3.2.2
Subscriber data modification procedure
2362 When receiving either the MAP_INSERT_SUBSCRIBER_DATA indication or the 2363 MAP_DELETE_SUBSCRIBER_DATA indication, the VLR checks the parameters and data in the primitive. Data 2364 errors are reported as an unexpected data value error or a data missing error depending on the nature of the error. 2365 After receiving the first MAP_INSERT_SUBSCRIBER_DATA indication, the VLR will check the IMSI that is 2366 included in the primitive. If the IMSI is unknown, the error "Unidentified subscriber" is returned. 2367 If the VLR does not support received basic or supplementary services or the network feature Operator Determined 2368 Barring, or there is a problem with Regional Subscription Data then it reports it to the HLR. 2369 If the entire MSC area is restricted due to regional subscription, this is reported to the HLR. 2370 If the updating of the subscriber data is not possible, the VLR will initiate the MAP_U_ABORT request primitive. If 2371 the updating is successful, the MAP_CLOSE indication is received from the HLR. 2372 The subscriber data modification procedure in the VLR is shown in the figures 20.3/6, 20.3/7 and 25.7/1.
1826
1827
Process INS_SUBS_DATA_VLR
Figure 20.3/ 6: The in sert subscriber data process in the V LR
20.3_6(1)
NULL
MAP _INS ERT_ S UBS CRIB ER_ DATA_Ind
P aram eters OK yes IMS I known yes no S ervices supported yes Set parameter Unsupported Se rvice Update Subscriber Data
no
no
S et UE = Unidentified S ubscri ber
Set UE = Unexpected Dat a V alue
no
MS C_A rea_Restricted_Due_ _To_Regional_Subs cription yes S et MSC _Area_ _Rest ricted
MA P_INS ERT_S UB SCRIBER_DATA_Rsp MA P_DELIMITER_Req
W F_ P RI MITIV E _OR_CLOS E
MAP _CLO SE _ ind
MA P_ _NO TICE
MA P_U_A BORT_ind, MA P_P_AB ORT_ind
Insert_ Subs _Data_ VLR
'S tore data in V LR' Figure 25. 7/1
MAP_CLOS E_ req
S et Not Confirmed by HLR
W F_ PRIMI TIVE _ OR_CLOS E
2373
2374
Figure 20.3/6: Process INS_SUBS_DATA_VLR
1828
1829
Process Delete_Subscriber_Data_VLR
Figure 20.3/7: The delet e subs criber data process in t he VLR
20.3_7(1)
NULL
MA P_DE LE TE _ _SUBS CRIB ER_ _DATA_ind
Check_ Indicat ion
E rror OK Subscriber known No yes S et Not Confirmed by HLR
Delete data E rror OK S et Not Confirmed by HLR yes No Set MSC_A rea_ _Restricted
'SE T UE = UNIDE NTIFIED SUB SCRIBE R'
MSC_Area_Restric ted_Due_ _To_Regional_Subsc ript ion
MA P_U_ AB ORT_req
MAP _DE LE TE_S UB SCRIBE R_DA TA _rsp, MAP _CLOSE _req
2375
2376
Figure 20.3/7: Process Delete_Subscriber_Data_VLR
1830
1831
2377 2378 20.3.3.1
20.3.3 Procedures in the SGSN
Subscriber deletion procedure
2379 The subscriber deletion procedure in the SGSN is described in the clause 19.1.
2380 20.3.3.2
Subscriber data modification procedure
2381 When receiving either the MAP_INSERT_SUBSCRIBER_DATA indication or the 2382 MAP_DELETE_SUBSCRIBER_DATA indication, the SGSN checks the parameters and data in the primitive. Data 2383 errors are reported as an unexpected data value error or a data missing error depending on the nature of the error. 2384 After receiving the first MAP_INSERT_SUBSCRIBER_DATA indication, the SGSN will check the IMSI that is 2385 included in the primitive. If the IMSI is unknown, the error "Unidentified subscriber" is returned. 2386 If the SGSN does not support received basic services or the network feature Operator Determined Barring, or there is a 2387 problem with Regional Subscription Data then it reports it to the HLR. 2388 If the entire SGSN area is restricted due to regional subscription, this is reported to the HLR. 2389 If the updating of the subscriber data is not possible, the SGSN will initiate the MAP_U_ABORT request primitive. If 2390 the updating is successful, the MAP_CLOSE indication is received from the HLR. 2391 The subscriber data modification procedure in the SGSN is shown in the figures 20.3/11, 20.3/12 and 25.7/5.
1832
1833
Process INS_SUBS_DATA_SGSN
F igu re 20.3/11: T he insert subscriber data process in the SGSN N ULL
20.3_11(1)
MAP_IN SER T_ SUBSCRIBER_ D ATA_Ind no
Parameters OK yes IMSI k nown yes Services s upported yes U pdate Subscriber D ata no
no
no Set parameter Unsupported Service
Set UE= Unidentified Subscriber
Set UE= Unexpec ted Data Value
SGSN_Area_Res tricted_Due_ _To_Regional_Subs cription yes Set SG SN _Area_ _Restric ted
MAP_IN SER T_SU BSCR IBER_D ATA_Rs p MAP_DELIM ITER_Req
W F_ PRIMITIVE _OR_C LOSE
MAP_ _NOTICE MAP_C LOSE_ ind Figure 25.7/1
MAP_U_ABOR T_ind, MAP_P_ABORT_ind
Insert_ Subs _Data_ SGSN
MAP_CLOSE_ req
'Store data in SGSN'
Set Not C onfirmed by HLR
W F_ PR IM ITIVE_ OR _CLOSE
2392
2393
Figure 20.3/11: Process INS_SUBS_DATA_SGSN
1834
1835
Process Delete_Subscriber_Data_SGSN
F igu re 20.3/12: T he delete subscriber data process in t he SGSN
20.3_12(1)
NULL
MAP_DELETE _SU BSC RIBER _DATA_ind
Check_ Indic ation
OK Subscriber known yes Delete data OK SGSN_Area_Restricted_Due_ _To_R egional_Subs cription yes Set SGSN_Area_ _Restric ted 'SET UE = UNID EN TIFIED SUBSC RIBER ' no
Error Set Not C onfirm ed by HLR
Error Set Not C onfirm ed by HLR no
MAP_U _ ABOR T_req
MAP_D ELETE_SUBSCR IBER_DATA_rsp, MAP_C LOSE_req
2394
2395
Figure 20.3/12: Process Delete_Subscriber_Data_SGSN
1836
1837
2396
20.4 Subscriber Identity procedure
2397 In the subscriber identity procedure the IMSI of the subscriber is retrieved from the HLR. The procedure is shown in 2398 figure 20.4/1.
2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409
+-----+ +------+ +------+ OMC VLR HLR +-----+ +------+ +------+ 1. + - - - - > 2. +---------------------> 3. 4. +<--------------------- +< - - - -
1) 2) 3) 4) Identity request. MAP_SEND_IMSI. MAP_SEND_IMSI_ACK. Identity confirm.
2410 2411 2412 2413 2414
2415
Figure 20.4/1: The subscriber identity procedure
2416
20.4.1 Subscriber identity procedure in the HLR
procedure termination; or dialogue acceptance, with proceeding as below.
2417 Opening of the dialogue is described in the macro Receive_Open_Ind in clause 25.1, with outcomes: 2418 2419
2420 When receiving the MAP_SEND_IMSI indication, the HLR will check the parameters and data in the primitive. Data 2421 errors are reported as an unexpected data value error or a data missing error depending on the nature of the error. 2422 If the subscriber is known in the HLR, the IMSI is fetched from the database and sent to the VLR. If the MSISDN 2423 cannot be identified, unknown subscriber indication is passed to the VLR. 2424 The subscriber identity procedure in the HLR is shown in figure 20.4/2.
1838
1839
Process Send_IMSI_HLR
Figure 20.4/2: The send IMS I process in the HLR
20.4_2(1)
Null
Receive_ Open_Ind
Vr
E rror
W ait_For_ S ervice_ P rimit ive
Perf orm Vr Dialogue
MA P_ NOTICE_ ind
MAP _S END_ IMSI_Ind
NULL
NULL
M AP_CLOS E_ req
Check_ Indicat ion
Figure 25.2/1
OK S ubscri ber K nown yes no
E rror
NULL
Fetch S ubscri ber Data
Set UE = Unk nown Subscriber
MAP _S END_IMS I_rsp MAP _CLOS E_req
NULL
2425
2426
Figure 20.4/2: Process Send_IMSI_HLR
1840
1841
2427
20.4.2 Subscriber identity procedure in the VLR
2428 When the IMSI request is received from the OMC, the VLR will send the MAP_SEND_IMSI request to the HLR. The 2429 contents of the response are sent to the OMC. 2430 The subscriber identity procedure in the VLR is shown in figure 20.4/3.
1842
1843
Process Send_IMSI_VLR
Figure 20.4/ 3: The send IMSI process in the V LR NULL
20.4_3(1)
OM_Subsc riber_ _Identit y_ _req
NULL
MAP _OPE N_req MAP _S END_IMS I_req MAP _DE LIMITE R_req
Receive_ Open_Cnf
E rror
Vr
OK W F_ _IDENTITY_ _RES ULT
V r=V1 Yes No
S et error
P erform V r D ialogue
MA P_S END_ _IMSI_c nf
MAP _NOTICE
MAP _CLOS E_ind, MAP _U_A BORT_ind, MAP _P_AB ORT_ind
NULL
Check _ Confirmat ion
MAP _U_ _AB ORT_req
OK
E rror
Set error
OM_S ubscriber_ _ident ity_ _cnf
OM_Subscriber_ _identity_ _cnf
NULL
NULL
2431
2432
Figure 20.4/3: Process Send_IMSI_VLR
1844
1845
2433 2434
21
Call handling procedures
21.1 General
2435 The MAP call handling procedures are used: 2436 2437 2438 2439 2440 2441 2442 2443
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 allocate resources in an SIWFS; 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.
2444 The procedures to handle a mobile originating call and a mobile terminating call after the call has arrived at the 2445 destination MSC do not require any signalling over a MAP interface. These procedures are specified in 3GPP TS 2446 23.018 [97]. 2447 2448 2449 2450 2451
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.
2452 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 2453 TS 23.079 [99]. The interworking between the MAP signalling procedures and the call handling procedures for each 2454 entity (VMSC and GMSC) is shown by the transfer of signals between these procedures. 2455 The stage 2 specifications for inter MSC group calls / broadcast calls are in 3GPP TS 43.068 [100] and 3GPP TS 2456 43.069 [101]. The interworking between the MAP signalling procedures and the group call /broadcast call procedures 2457 for each entity (Anchor MSC and Relay MSC) is shown by the transfer of signals between these procedures. 2458 The stage 2 specification for the allocation of resources in an SIWFS is in GSM 03.54. The interworking between the 2459 MAP signalling procedures and the call handling procedures for each entity (VMSC and SIWFS) is shown by the 2460 transfer of signals between these procedures. 2461 The interworking between the call handling procedures and signalling protocols other than MAP are shown in 3GPP TS 2462 23.018, 3GPP TS 23.078 and 3GPP TS 23.079 [99]. 2463 The stage 2 specification for the handling of reporting of MS status for call completion services and notification of 2464 remote user free for CCBS is in 3GPP TS 23.093 [107].
2465 2466
21.2 Retrieval of routing information
21.2.1 General
2467 The message flows for successful retrieval of routeing information for a mobile terminating call are shown in 2468 figure 21.2/1 (mobile terminating call which has not been optimally routed) and 21.2/2 (mobile-to-mobile call which 2469 has been optimally routed).
1846
1847
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
Network Gateway +---+ +---+ +---+ +---+ +----------MSC+--------------HLR+----------------VLR +---+ +---+ +---+ +---+ I_IAM (note 2)MAP_SEND_ROUTING_ +------------->INFORMATION +---+ +-----------------> MSC+-------- (note 1) MAP_PROVIDE_SUBSCRI- +---+ BER INFORMATION +-------------------> MAP_PROVIDE_SUBSCRI- BER INFORMATION ack MAP_SEND_ROUTING_<------------------- INFORMATION ack (note 3) <----------------- MAP_SEND_ROUTING_ INFORMATION +-----------------> MAP_PROVIDE_ROAMING_ NUMBER +-------------------> MAP_PROVIDE_ROAMING_ NUMBER ack MAP_SEND_ROUTING_<------------------- INFORMATION ack <----------------- MAP_RESTORE_DATA I-IAM <---------
xxx = Optional Procedure NOTE 1: This service may also be used by an ISDN exchange for obtaining routing information from the HLR. NOTE 2: 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 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].
2512
2499 2500 2501 2502 2503 2504 2505 2506 2507 2508 2509 2510 2511
Figure 21.2/1: Message flow for retrieval of routeing information (non-optimally routed call)
1848
1849
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
Visited Gateway +---+ +---+ +---+ +---+ MSC+----------MSC+--------------HLR+----------------VLR +---+ +---+ +---+ +---+ I_IAM (note) MAP_SEND_ROUTING_ +-------------> INFORMATION MAP_PROVIDE_ +-----------------> SUBSCRIBER_INFO +-------------------> MAP_PROVIDE_ SUBSCRIBER_INFO ack <------------------- _ OR _ MAP_PROVIDE_ROAMING_ NUMBER +-------------------> +---+ MSC+-------- MAP_PROVIDE_ROAMING_ +---+ NUMBER ack MAP_SEND_ROUTING_<------------------- INFORMATION ack <----------------- MAP_RESTORE_DATA I-IAM <---------
xxx = Optional Procedure NOTE 1: For Optimal Routeing phase 1, only one of the information flows for Provide Subscriber Info and Provide Roaming Number is used. For later phases of Optimal Routeing, the HLR may return a MAP_SEND_ROUTEING_INFORMATION ack after the Provide Subscriber Info information flow, and the GMSC may send a second MAP_SEND_ ROUTEING_INFORMATION, which will trigger the Provide Roaming Number information flow. NOTE 2: 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 CCITT 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.
2554
2540 2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553
Figure 21.2/2: Message flow for retrieval of routeing information (optimally routed call)
2555 The following MAP services are used to retrieve routing information: 2556 2557 2558 2559
MAP_SEND_ROUTING_INFORMATION MAP_PROVIDE_ROAMING_NUMBER MAP_PROVIDE_SUBSCRIBER_INFO MAP_RESTORE_DATA
see clause 10.1; see clause 10.2; see clause 8.11.2; see clause 8.10.3.
2560
21.2.2 Process in the GMSC
2561 The MAP process in the GMSC to retrieve routeing information for a mobile terminating call is shown in figure 21.2/3. 2562 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 2563 2564
Receive_Open_Cnf Check_Confirmation
see clause 25.1.2; see clause 25.2.2.
2565 Successful Outcome 2566 2567 2568 2569 2570
When the MAP process receives a Send Routeing Info request from the call handling process in the GMSC, it requests a dialogue with the HLR whose identity is contained in the Send Routeing Info request by sending a MAP_OPEN service request, requests routeing information using a MAP_SEND_ROUTING_INFORMATION service request and invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the HLR.
1850
1851
2571 2572 2573 2574 2575
If the MAP process receives a MAP_SEND_ROUTING_INFORMATION service confirm from the HLR, the MAP process invokes the macro Check_Confirmation to check the content of the confirm. If the MAP_SEND_ROUTING_INFORMATION confirm from the HLR cannot be carried in a single TC-Result component, it is carried in one or more TC-Result-NL components (each sent in a TC-CONTINUE), followed by a TC-Result-L component in a TC-END message.
2576 If the macro Check_Confirmation takes the OK exit, the MAP process sends a Send Routeing Info ack containing the 2577 routeing information received from the HLR to the call handling process in the GMSC and returns to the idle state. 2578 Earlier version MAP dialogue with the HLR 2579 If the macro Receive_Open_Cnf takes the Vr exit, the MAP process checks whether this is an OR interrogation 2580 (indicated by the inclusion of the OR interrogation parameter in the MAP_SEND_ROUTING_INFORMATION service 2581 request). 2582 If this is not an OR interrogation, the GMSC performs the earlier version MAP dialogue as specified in [51] and the 2583 process returns to the idle state. 2584 If this is an OR interrogation, the MAP process sends a Send Routeing Info negative response indicating OR not 2585 allowed to the call handling process in the GMSC and returns to the idle state. 2586 Dialogue opening failure 2587 If the macro Receive_Open_Cnf indicates that the dialogue with the HLR could not be opened, the MAP process sends 2588 an Abort to the call handling process in the GMSC and returns to the idle state. 2589 Error in MAP_SEND_ROUTING_INFORMATION confirm 2590 If the MAP_SEND_ROUTING_INFORMATION service confirm contains a user error or a provider error, or the 2591 macro Check_Confirmation indicates that there is a data error, the MAP process sends a Send Routeing Info negative 2592 response to the call handling process in the GMSC and returns to the idle state. 2593 Call release 2594 If the call handling process in the GMSC indicates that the call has been aborted (i.e. prematurely released by the 2595 calling subscriber), the MAP process returns to the idle state. Any response from the HLR will be discarded. 2596 Abort of HLR dialogue 2597 2598 2599 2600
After the dialogue with the HLR has been established, the MAP service provider may abort the dialogue by issuing a MAP_P_ABORT indication, or the HLR may send a MAP_U_ABORT indication or a MAP_CLOSE indication. In any of these cases, the MAP process sends a Send Routeing Info negative response to the call handling process in the GMSC and returns to the idle state.
2601 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 2602 dialogue with the HLR, sends a Send Routeing Info negative response indicating system failure to the call handling 2603 process in the GMSC and returns to the idle state.
1852
1853
Process SRI_GMSC
Figu re 2 1.2/3: P rocess in the GMSC f or re trieval of route ing info rmatio n
21.2_3.1(2)
S ignals to/from the lef t are to/ from the GMS C call han dling process; signa ls to/ from t he right are to/ from the HLR
Idle
S end Routein g In fo
MAP _OP EN_req , MAP _SE ND_ROUTING_INFORMA TION_ req, MAP _DE LIMITE R_req
Rece ive_ Op en_Cnf
Sectio n 25. 1
OK W ait_For_ HLR_ Response
Vr OR int erro gation? Yes No Abort
E rror
MAP _SE ND_ ROUTING_INFORMA TION_c nf
S et negative response: OR not allowed
Idle
Check_ Con firmation
Section 25 .2 Provider Erro r, User E rror, Dat a E rror Send Routeing Info negative response
S end Rout eing In fo negative response
Perf orm MAP V r Dialog ue
Refer to the relevant version of GSM 09. 02
OK S end Routeing Info ack
Idle
Idle
Idle
Id le
2604
2605
Figure 21.2/3 (sheet 1 of 2): Process SRI_GMSC
1854
1855
Process SRI_GMSC
Figu re 2 1.2/3: P rocess in the GMSC f or re trieval of route ing info rmatio n W ait _For_HLR_ Response
21.2_3.2(2)
S igna ls to /from the left are to/ from t he GMS C ca ll hand ling process; signals to/ from t he right are to/ from t he HLR
Abort
MAP _U_ABO RT_ind, MAP _P _A BORT_ind, MAP _CLOSE _in d
MA P_ NOTICE_ind
Idle
MAP _CL OSE_ind
Set negative resp on se: S ystem Failure
S en d Rout eing Info ne gative re spon se
Idle
2606
2607
Figure 21.2/3 (sheet 2 of 2): Process SRI_GMSC
1856
1857
2608
21.2.3 Procedures in the HLR
2609 The MAP process in the HLR to retrieve routeing information for a mobile terminating call is shown in figure 21.2/4. 2610 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 2611 2612 2613
Receive_Open_Ind Receive_Open_Cnf Check_Confirmation
see clause 25.1.1; see clause 25.1.2; see clause 25.2.2.
2614 Successful outcome 2615 When the MAP process receives a MAP_OPEN indication with the application context locInfoRetrieval, it checks it by 2616 invoking the macro Receive_Open_Ind. 2617 If the macro takes the OK exit, the MAP process waits for a service indication. 2618 If a MAP_SEND_ROUTING_INFORMATION service indication is received, the MAP process sends a Send Routeing 2619 Info request to the call handling process in the HLR, and waits for a response. The Send Routeing Info request contains 2620 the parameters received in the MAP_SEND_ROUTING_INFORMATION service indication. 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630
If the call handling process in the HLR returns a Send Routeing Info ack, the MAP process constructs a MAP_SEND_ROUTING_INFORMATION service response containing the routeing information contained in the Send Routeing Info ack, constructs a MAP_CLOSE service request, sends them to the GMSC and returns to the idle state. If the MAP_SEND_ROUTING_INFORMATION response cannot be carried in a single TC-Result component, it is carried in one or more TC-Result-NL components (each sent in a TC-CONTINUE), followed by a TC-Result-L component in a TC-END message. If the call handling process in the HLR returns a Provide Subscriber Info request, the MAP process requests a dialogue with the VLR whose identity is contained in the Provide Subscriber Info request by sending a MAP_OPEN service request, requests the subscriber status using a MAP_PROVIDE_SUBSCRIBER_INFO service request, and invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request.
2631 If the macro takes the OK exit, the MAP process waits for the response from the VLR. 2632 If the MAP process receives a MAP_PROVIDE_SUBSCRIBER_INFO service confirm, it invokes the macro 2633 Check_Confirmation to check the content of the confirm. 2634 2635 2636 2637 2638 2639 2640 2641 2642 2643 2644 2645 2646 2647
If the Check_Confirmation macro takes the OK exit, the MAP process sends a Provide Subscriber Info ack containing the information received in the MAP_PROVIDE_SUBSCRIBER_INFO service confirm to the call handling process in the HLR, and waits for a response. The handling of the response from the call handling process in the HLR is described above. If the MAP_PROVIDE_SUBSCRIBER_INFO service confirm contains a provider error or a data error, the MAP process sends a Provide Subscriber Info negative response indicating the type of error to the call handling process in the HLR, and waits for a response. The handling of the response from the call handling process in the HLR is described above. NOTE: The 'User Error' exit from the macro Check_Confirmation is shown for formal completeness; the MAP_PROVIDE_SUBSCRIBER_INFO_cnf primitive cannot contain a user error.
If the call handling process in the HLR returns a Provide Roaming Number request, the MAP process requests a dialogue with the VLR whose identity is contained in the Provide Roaming Number request by sending a MAP_OPEN service request, requests a roaming number using a MAP_PROVIDE_ROAMING_NUMBER service request, and invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request.
2648 If the macro takes the OK exit, the MAP process waits for the response from the VLR. 2649 If the MAP process receives a MAP_PROVIDE_ROAMING_NUMBER service confirm, it invokes the macro 2650 Check_Confirmation to check the content of the confirm.
1858
1859
2651 2652 2653 2654 2655 2656 2657 2658
If the Check_Confirmation macro takes the OK exit, the MAP process sends a Provide Roaming Number ack containing the MSRN received in the MAP_PROVIDE_ROAMING_NUMBER service confirm to the call handling process in the HLR, and waits for a response. The handling of the response from the call handling process in the HLR is described above. If the MAP_PROVIDE_ROAMING_NUMBER service confirm contains a user error or a provider error, or the macro Check_Confirmation indicates that there is a data error, the MAP process sends a Provide Roaming Number negative response indicating the type of error to the call handling process in the HLR, and waits for a response. The handling of the response from the call handling process in the HLR is described above.
2659 Negative response from HLR call handling process 2660 2661 2662 2663
If the call handling process in the HLR returns a negative response, either before or after a dialogue with the VLR to obtain a roaming number, the MAP process constructs a MAP_SEND_ROUTING_INFORMATION service response containing the appropriate error, constructs a MAP_CLOSE service request, sends them to the GMSC and returns to the idle state.
2664 Earlier version MAP Provide Roaming Number dialogue with the VLR 2665 If the macro Receive_Open_Cnf takes the Vr exit after the MAP process has requested opening of a Provide Roaming 2666 Number dialogue with the VLR, the MAP process checks whether this is an OR interrogation (indicated by the 2667 inclusion of the OR interrogation parameter in the MAP_PROVIDE_ROAMING_NUMBER service request). 2668 If this is not an OR interrogation, the HLR performs the earlier version MAP dialogue as specified in [51], relays the 2669 result of the dialogue to the HLR call handling process, and waits for a response. The handling of the response from the 2670 call handling process in the HLR is described above. 2671 If this is an OR interrogation, the MAP process sends a Provide Roaming Number negative response indicating OR not 2672 allowed to the call handling process in the HLR and waits for a response. The handling of the response from the call 2673 handling process in the HLR is described above. 2674 Failure of Provide Subscriber Info dialogue with the VLR 2675 2676 2677 2678
If the Receive_Open_Cnf macro takes the Vr exit or the Error exit after the MAP process has requested opening of a Provide Subscriber Info dialogue with the VLR, the MAP process sends a Provide Subscriber Info negative response indicating system failure to the call handling process in the HLR, and waits for a response. The handling of the response from the call handling process in the HLR is described above.
2679 Failure of Provide Roaming Number dialogue with the VLR 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 2690 2691
If the Receive_Open_Cnf macro takes the Error exit after the MAP process has requested opening of a Provide Roaming Number dialogue with the VLR, the MAP process sends a Provide Roaming Number negative response indicating system failure to the call handling process in the HLR, and waits for a response. The handling of the response from the call handling process in the HLR is described above. If the MAP process receives a MAP_U_ABORT, a MAP_P_ABORT or a premature MAP_CLOSE from the MAP provider, it sends a Provide Roaming Number negative response indicating system failure to the call handling process in the HLR, and waits for a response. The handling of the response from the call handling process in the HLR is described above. If the MAP process receives a MAP_NOTICE from the MAP provider, it returns a MAP_CLOSE request to the MAP provider, sends a Provide Roaming Number negative response indicating system failure to the call handling process in the HLR, and waits for a response. The handling of the response from the call handling process in the HLR is described above.
2692 Earlier version MAP dialogue with the GMSC 2693 If the macro Receive_Open_Ind takes the Vr exit, the HLR performs the earlier version MAP dialogue as specified in 2694 [51] and the process returns to the idle state. 2695 Failure of dialogue opening with the GMSC 2696 If the macro Receive_Open_Ind takes the Error exit, the MAP process returns to the idle state.
1860
1861
2697 If the MAP provider sends a MAP_P_ABORT while the MAP process is waiting for a service indication, the MAP 2698 process returns to the idle state. 2699 If the MAP provider sends a MAP_NOTICE while the MAP process is waiting for a service indication, the MAP 2700 process sends a MAP_CLOSE request to terminate the dialogue and returns to the idle state.
1862
1863
Process SRI_HLR
Figure 2 1.2/4: P roce ss in the HLR to respon d to a reque st for rout eing in format ion
21.2_4.1(3)
S ignals to/from the lef t are to/ from the GMSC; signals to/ from t he right are to/ from the VL R unles s specified oth erwise
Idle
Receive_ Open_ Ind
S ection 25 .1
Vr Perform MA P V r Dia logue Re fer to t he relevant version of GSM 09.02
OK W ait_For_ S ervice _ In dication
E rror
Idle
Idle
MA P_P_ ABORT_ind
MAP _S END_ROUTING_ INFORMATION_ ind
MA P_ NO TICE_in d
Id le
S en d Route ing Info
To HLR ca ll handlin g process
MA P_ CLOSE _req
W ait_ For_ Call_Ha ndli ng_ Response
Idle
Send Routeing In fo ack
From HLR call h andlin g pro ces s
S end Routeing Info negative res ponse
From HLR c all h andling proc ess
S et res ult
Se t e rror
MAP _SEND_ ROUTING_ INFORMATION_rsp
Idle
2701
2702
Figure 21.2/4 (sheet 1 of 3): Process SRI_HLR
1864
1865
Process SRI_HLR
Figure 2 1.2/4: P roce ss in the HLR to respon d to a reque st for rout eing in format ion Wait_For_ Call_Ha ndling_ Res ponse
21.2_4.2(3)
S igna ls to /from the left are to/ from t he GMSC; signal s to/ from t he rig ht are to/ from t he VLR un les s spe cified otherwise
P rovide S ubscriber Info
From HLR call han dling proces s
MAP _OP EN_req , MA P_PROVIDE_S UB SCRIBE R_ INFO_ req, MAP _DE LIMITE R_req
Rec eive_ Op en_Cnf
S ect ion 25.1
OK
Vr, E rror P rovide S ubscribe r I nfo neg ative re sponse To HLR call handling p roc ess
Wait_For_ PS I_Response
W ait_For_ Call_ Handli ng_ Resp onse
MA P_PROVIDE _S UB SCRIBER _INFO_cnf
MAP _U_ABORT_ind, MAP _P _A BORT_ind, MAP _CLOSE_ind
MA P_ NOTICE _ ind
Check_ Con firm ation
Sec tion 25 .2 User E rror, Provider Error, Data E rror To HLR call handlin g pro ce ss P rovide S ubscribe r Info n eg at ive respons e To HL R call han dling proces s Provide S ub scribe r Info negative respon se
MA P_ CLOS E_ ind
OK Provide Subsc riber Info ack
To HL R call handling proce ss
Wait_For_ Call_Ha ndling_ Res ponse
2703
2704
Figure 21.2/4 (sheet 2 of 3): Process SRI_HLR
1866
1867
Process SRI_HLR
Figure 2 1.2/4: P roce ss in the HLR to respon d to a reque st for rout eing in format ion
W ait_For_ Call_Han dling _ Res ponse
21.2_4.3(3)
S ignals to/from the lef t are to/ from the GMSC; signals to/ from t he right are to/ from the VL R unles s specified oth erwise From HLR call h andlin g pro ces s
Provide Roaming Numbe r
MA P_OP EN_re q, MA P_PROV IDE_ROAMING_NUMBE R_req, MA P_DE LIMITE R_req
Rec eive _ Op en _Cnf
S ection 25.1
E rror Provide Roa ming Number ne ga tive res ponse To HLR ca ll handling process
OK
Vr OR int errogation ? No Yes
Wait _For_ Ca ll_Han dling_ Re sp onse
Perform MA P V r Dialogue
Ref er to the relevant version of GS M 09.02
Se t negat ive response: OR not allowed
MA P V r Dialogue Result
To HLR ca ll handling process
Pro vide Roaming Number n egative res ponse
To HLR c all handling process
W ait_For_ P RN_Response
W ait_ For_ Call_Ha ndli ng_ Response
W ait _For_ Call_Ha ndling_ Respons e
MAP_PROVIDE _ROAMING_NUMBE R_cn f
MAP _U_ ABO RT_in d, MAP _P _A BORT_ind, MAP _CL OSE _ind
MA P_ NOTICE _ ind
Check_ Con firmation
Section 25 .2 User E rror, Provide r Error, Dat a E rror To HLR ca ll handling process Provide Roamin g Numbe r negat ive respons e To HLR ca ll h andlin g pro ces s P rovide Roaming Num ber negative response
MA P_ CLOS E_ ind
OK Provide Roa ming Number ack
To HLR call h andling proc ess
W ait_For_ Call_Han dling _ Res ponse
2705
2706
Figure 21.2/4 (sheet 3 of 3): Process SRI_HLR
1868
1869
2707
21.2.4 Process in the VLR to provide a roaming number
2708 The MAP process in the VLR to provide a roaming number for a mobile terminating call is shown in figure 21.2/5. The 2709 MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: 2710
Receive_Open_Ind
see clause 25.1.1;
2711 Successful outcome 2712 When the MAP process receives a MAP_OPEN indication with the application context roamingNbEnquiry, it checks it 2713 by invoking the macro Receive_Open_Ind. 2714 If the macro takes the OK exit, the MAP process waits for a service indication. 2715 If a MAP_PROVIDE_ROAMING_NUMBER service indication is received, the MAP process sends a Provide 2716 Roaming Number request to the call handling process in the VLR, and waits for a response. The Provide Roaming 2717 Number request contains the parameters received in the MAP_ PROVIDE_ROAMING_NUMBER service indication. 2718 If the call handling process in the VLR returns a Provide Roaming Number ack, the MAP process constructs a 2719 MAP_PROVIDE_ROAMING_NUMBER service response containing the roaming number contained in the Send 2720 Routeing Info ack, constructs a MAP_CLOSE service request, sends them to the HLR and returns to the idle state. 2721 Earlier version MAP dialogue with the HLR 2722 If the macro Receive_Open_Ind takes the Vr exit, the VLR performs the earlier version MAP dialogue as specified in 2723 [51] and the process returns to the idle state. 2724 Failure of dialogue opening with the HLR 2725 If the macro Receive_Open_Ind takes the Error exit, the MAP process returns to the idle state. 2726 If the MAP provider sends a MAP_P_ABORT while the MAP process is waiting for a service indication, the MAP 2727 process returns to the idle state. 2728 If the MAP provider sends a MAP_NOTICE while the MAP process is waiting for a service indication, the MAP 2729 process sends a MAP_CLOSE request to terminate the dialogue and returns to the idle state. 2730 Negative response from VLR call handling process 2731 If the call handling process in the HLR returns a negative response, the MAP process constructs a 2732 MAP_PROVIDE_ROAMING_NUMBER service response containing the appropriate error, constructs a MAP_CLOSE 2733 service request, sends them to the HLR and returns to the idle state.
1870
1871
Process PRN_VLR
Figu re 2 1.2/5: P rocess in the V LR t o handle a re quest for a roamin g nu mber
21.2_5(1)
S ignals to/from the lef t are to/ from the HLR; signals to/ from t he right are to/ from the VL R call han dling process
Idle
Rece ive_ Open_Ind
Sectio n 25. 1
Vr Pe rform MA P V r Dia logue Refe r to t he ap propriate ve rsion of GSM 09.02
OK W ait_For_ S ervice_ In dication
E rror
Idle
Idle
MA P_P_ ABORT_ind
MAP _P ROVIDE_RO AMING_NUMB ER_ind
MA P_ NO TICE_in d
Idle
Rrovide Roaming Number
To VLR c all h andling pro cess
MA P_ CLOSE _req
W ait_For_ Roaming_ Numbe r
Idle
Provid e Roamin g Numb er ack
Provide Roaming Number nega tive response
S et res ult
Set error
MAP _P ROVIDE_RO AMING_NUMB ER_rsp
Idle
2734
2735
Figure 21.2/5: Process PRN_VLR
1872
1873
2736
21.2.5 Process in the VLR to restore subscriber data
2737 The MAP process in the HLR to restore subscriber data is shown in figure 21.2/6. The MAP process invokes macros 2738 not defined in this clause; the definitions of these macros can be found as follows: 2739 2740 2741 2742
Receive_Open_Cnf Check_Confirmation Insert_Subs_Data_VLR Activate_Tracing_VLR
see clause 25.1.2; see clause 25.2.2; see clause 25.7.1; see clause 25.9.3.
2743 Successful outcome 2744 2745 2746 2747 2748
When the MAP process receives a Restore Data request from the data restoration process in the VLR, it requests a dialogue with the HLR whose identity is contained in the Restore Data request by sending a MAP_OPEN service request, requests data restoration using a MAP_RESTORE_DATA service request and invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the HLR.
2749 The VLR may receive a MAP_INSERT_SUBSCRIBER_DATA service indication from the HLR; this is handled by 2750 the macro Insert_Subs_Data_VLR as described in clause 25.7.1, and the MAP process waits for a further response from 2751 the HLR. 2752 The VLR may receive a MAP_ACTIVATE_TRACE_MODE service indication from the HLR; this is handled by the 2753 macro Activate_Tracing_VLR as described in clause 25.9.3, and the MAP process waits for a further response from the 2754 HLR. 2755 If the MAP process receives a MAP_RESTORE_DATA service confirm, it invokes the macro Check_Confirmation to 2756 check the content of the confirm. 2757 If the Check_Confirmation macro takes the OK exit, the MAP process sends a Restore Data ack containing the 2758 information received from the HLR to the data restoration process in the VLR and returns to the idle state. 2759 Error in MAP_RESTORE_DATA confirm 2760 If the MAP_RESTORE_DATA service confirm contains a user error or a provider error, or the macro 2761 Check_Confirmation indicates that there is a data error, the MAP process sends a Restore Data negative response 2762 indicating the type of error to the call handling process in the HLR, and returns to the idle state. 2763 Earlier version MAP dialogue with the HLR 2764 If the macro Receive_Open_Cnf takes the Vr exit, the VLR performs the earlier MAP version dialogue as specified in 2765 [51] and the process terminates. 2766 Dialogue opening failure 2767 If the macro Receive_Open_Cnf indicates that the dialogue with the HLR could not be opened, the MAP process sends 2768 a negative response indicating system failure to the data restoration process in the GMSC and returns to the idle state.
1874
1875
Process Restore_Data_VLR
Figu re 2 1.2/6: P rocess in the V LR t o t rigger restoration of subscribe r da ta
21.2_6(1)
S ignals to/from the lef t are to/ from the VL R data restoration p roces s; signa ls to/ from t he right are to/ from the HLR
Idle
Restore Data
MAP _OP EN_req, MA P_RE STO RE_DA TA _req MAP _DE LIMITE R_req
Receive_ Open_Cnf
S ection 25 .1
OK W ait _For_ HLR_Resp onse Refer to t he appropriate version of GSM 09.02
Vr Pe rform MAP Vr Dia logue
E rror Restore Dat a negative resp ons e
Ins ert _S ubs_ Data_VLR
Section 25 .7
Activate_ Tracing_ VLR
S ection 25.9
MAP _ RES TO RE _ DATA_cnf
Idle
Idle
Wait_For_ HLR_Res ponse
Check_ Confirmat io n
Section 25. 2
OK
Provid er E rror, User Error, Data Error Rest ore Data ne ga tive response
Restore Data ack
Idle
2769
2770
Figure 21.2/6: Process Restore_Data_VLR
1876
1877
2771
21.2.6 Process in the VLR to provide subscriber information
2772 The MAP process in the VLR to provide subscriber information for a mobile terminating call subject to CAMEL 2773 invocation is shown in figure 21.2/6. The MAP process invokes a macro not defined in this clause; the definition of this 2774 macro can be found as follows: 2775
Receive_Open_Ind
see clause 25.1.1;
2776 Successful outcome 2777 When the MAP process receives a MAP_OPEN indication with the application context subscriberInfoEnquiry, it 2778 checks it by invoking the macro Receive_Open_Ind. 2779 If the macro takes the OK exit, the MAP process waits for a service indication. 2780 2781 2782 2783 2784 2785 2786 2787
If a MAP_PROVIDE_SUBSCRIBER_INFO service indication is received, the MAP process sends a Provide Subscriber Info request to the subscriber information request process in the VLR, and waits for a response. The Provide Subscriber Info request contains the parameters received in the MAP_PROVIDE_SUBSCRIBER_INFO service indication. If the subscriber information request process in the VLR returns a Provide Subscriber Info ack, the MAP process constructs a MAP_PROVIDE_SUBSCRIBER_INFO service response containing the information contained in the Provide Subscriber Info ack, constructs a MAP_CLOSE service request, sends them to the HLR and returns to the idle state.
2788 Failure of dialogue opening with the HLR 2789 If the macro Receive_Open_Ind takes the Vr exit or the Error exit, the MAP process returns to the idle state. 2790 If the MAP provider sends a MAP_P_ABORT while the MAP process is waiting for a service indication, the MAP 2791 process returns to the idle state. 2792 If the MAP provider sends a MAP_NOTICE while the MAP process is waiting for a service indication, the MAP 2793 process sends a MAP_CLOSE request to terminate the dialogue and returns to the idle state.
1878
1879
Process PSI_VLR
Figure 2 1.2/ 7: P roce ss in the V LR to handle a reque st for subsc riber inf ormatio n
21.2_7(1)
S igna ls to /from the left are to/ from t he HLR; signal s to/ from t he rig ht are to/ from t he VLR su bscriber info rmation reques t proc ess
Idle
Receive_ Open_Ind
Se ction 25. 1
OK W ait_For_ S ervice _ In dication
V r, Error
Idle
MA P_ P_ ABORT_ind
MAP _P ROVIDE_SUBS CRIB ER_INFO_ind
MA P_ NO TICE_in d
Id le
Rrovide S ubscriber In fo
MA P_ CLOSE _ req
W ait_ For_ Subs criber_ Inf o
Idle
P ro vide S ubscriber In fo ack
Set result
MAP _P ROVIDE_SUBS CRIB ER_ INFO_rsp
Idle
2794
2795
Figure 21.2/7: Process PSI_VLR
1880
1881
2796
21.2.7 Process in the HLR for Any Time Interrogation
2797 The message flows for successful retrieval of subscriber information related to an any time interrogation from the 2798 CAMEL server are shown in figure 21.2/8.
2799 2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 2814 2815
gsmSCF +---+ +---+ +---+ SCF+--------------HLR+----------------VLR +---+ +---+ +---+ MAP_ANY TIME INTERROGATION +-----------------> MAP_PROVIDE_SUBSCRI- BER INFORMATION +-------------------> MAP_PROVIDE_SUBSCRI- BER INFORMATION ack MAP_ANY TIME _<------------------- INTERROGATION ack <----------------- Figure 21.2/8: Message flow for any time interrogation
2816
2817 The following MAP services are used to retrieve routing information: 2818 2819
MAP_ANY_TIME_INTERROGATION see clause 8.11.1; MAP_PROVIDE_SUBSCRIBER_INFO see clause 8.11.2.
2820 21.2.7.1
Process in the gsmSCF
2821 Out of the scope of the MAP specification.
2822 21.2.7.2
Process in the HLR
2823 The MAP process in the HLR to provide subscriber information in response to an interrogation from the CAMEL server 2824 is shown in figure 21.2/8. The MAP process invokes macros not defined in this clause; the definitions of these macros 2825 can be found as follows: 2826 2827 2828
Receive_Open_Ind Receive_Open_Cnf Check_Confirmation
see clause 25.1.1; see clause 25.1.2; see clause 25.2.2.
2829 Successful outcome 2830 When the MAP process receives a MAP_OPEN indication with the application context anyTimeInterrogationEnquiry, 2831 it checks it by invoking the macro Receive_Open_Ind. 2832 If the macro takes the OK exit, the MAP process waits for a service indication. 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842 2843 2844
If a MAP_ANY_TIME_INTERROGATION service indication is received, the MAP process sends an Any Time Interrogation request to the call handling process in the HLR (described in 3GPP TS 23.078), and waits for a response. The Any Time Interrogation request contains the parameters received in the MAP_ ANY_TIME_INTERROGATION service indication. If the call handling process in the HLR returns an Any Time Interrogation response, the MAP process constructs a MAP_ANY_TIME_INTERROGATION service response containing the subscriber information contained in the Any Time Interrogation response, constructs a MAP_CLOSE service request, sends them to the CAMEL server and returns to the idle state. If the call handling process in the HLR returns a Provide Subscriber Info request, the MAP process requests a dialogue with the VLR whose identity is contained in the Provide Subscriber Info request by sending a MAP_OPEN service request, requests the subscriber status using a MAP_PROVIDE_SUBSCRIBER_INFO service request, and invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request.
1882
1883
2845 If the macro takes the OK exit, the MAP process waits for the response from the VLR. 2846 If the MAP process receives a MAP_PROVIDE_SUBSCRIBER_INFO service confirm, it invokes the macro 2847 Check_Confirmation to check the content of the confirm. 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857
If the Check_Confirmation macro takes the OK exit, the MAP process sends a Provide Subscriber Info ack containing the information received in the MAP_PROVIDE_SUBSCRIBER_INFO service confirm to the call handling process in the HLR, and waits for a response. The handling of the response from the call handling process in the HLR is described above. If the MAP_PROVIDE_SUBSCRIBER_INFO service confirm contains a provider error or a data error, the MAP process sends a Provide Subscriber Info negative response indicating the type of error to the call handling process in the HLR, and waits for a response. The handling of the response from the call handling process in the HLR is described above. NOTE: The 'User Error' exit from the macro Check_Confirmation is shown for formal completeness; the MAP_PROVIDE_SUBSCRIBER_INFO_cnf primitive cannot contain a user error.
2858 Negative response from HLR call handling process 2859 2860 2861 2862
If the call handling process in the HLR returns a negative response, either before or after a dialogue with the VLR to obtain subscriber information, the MAP process constructs a MAP_ANY_TIME_INTERROGATION service response containing the appropriate error, constructs a MAP_CLOSE service request, sends them to the CAMEL server and returns to the idle state.
2863 Failure of Provide Subscriber Info dialogue with the VLR 2864 2865 2866 2867
If the Receive_Open_Cnf macro takes the Vr exit or the Error exit after the MAP process has requested opening of a Provide Subscriber Info dialogue with the VLR, the MAP process sends a Provide Subscriber Info negative response indicating system failure to the call handling process in the HLR, and waits for a response. The handling of the response from the call handling process in the HLR is described above.
2868 Failure of dialogue opening with the CAMEL server 2869 If the macro Receive_Open_Ind takes the Vr or Error exit, the MAP process returns to the idle state. 2870 If the MAP provider sends a MAP_P_ABORT while the MAP process is waiting for a service indication, the MAP 2871 process returns to the idle state. 2872 If the MAP provider sends a MAP_NOTICE while the MAP process is waiting for a service indication, the MAP 2873 process sends a MAP_CLOSE request to terminate the dialogue and returns to the idle state.
1884
1885
Process ATI_HLR
Figu re 2 1.2/9: P roce ss in the HLR t o respond to a request for any time interro gation
21.2_9.1(2)
S ignals to/from the lef t are to/ from the gsmS CF; signals to/ from t he right are to/ from the VL R unles s specified oth erwise
Idle
Receive_ Open_ Ind
S ection 25 .1
OK W ait_For_ S ervice _ In dication
V r Error
Idle
MA P_P_ ABORT_ind
MAP _A NY_TIME _INTERROG ATION_ ind
MA P_ NO TICE_in d
Id le
A ny Time Interrogation Request
To HL R call handling (see GS M 03.78)
MA P_ CLOSE _req
W ait_ For_ Call_Ha ndli ng_ Response
Idle
Any Time In terrog ation Response
From HLR call h andlin g pro ces s
A ny Time Interrog ation negative response
From HLR c all h andling proc ess
S et res ult
Se t e rror
MAP _A NY_TIME _INTERROG ATION_ rsp
Idle
2874
2875
Figure 21.2/9 (sheet 1 of 2): Process ATI_HLR (New)
1886
1887
Process ATI_HLR
Figu re 2 1.2/9: P roce ss in the HLR t o respond to a request for any time interro gation Wait_For_ Call_Ha ndling_ Res ponse
21.2_9.2(2)
S igna ls to /from the left are to/ from t he gsmS CF; signal s to/ from t he rig ht are to/ from t he VLR un les s spe cified otherwise
P rovide S ubscriber Info
From HLR call han dling proces s
MAP _OP EN_req , MA P_PROVIDE_S UB SCRIBE R_ INFO_ req, MAP _DE LIMITE R_req
Rec eive_ Op en_Cnf
S ect ion 25.1
OK
Vr, E rror P rovide S ubscribe r I nfo neg ative re sponse To HLR call handling p roc ess
Wait_For_ PS I_Response
W ait_For_ Call_ Handli ng_ Resp onse
MA P_PROVIDE _S UB SCRIBER _INFO_cnf
MAP _U_ABORT_ind, MAP _P _A BORT_ind, MAP _CLOSE_ind
MA P_ NOTICE _ ind
Check_ Con firm ation
Sec tion 25 .2 User E rror, Provider Error, Data E rror To HLR call handlin g pro ce ss P rovide S ubscribe r Info n eg at ive respons e To HL R call han dling proces s Provide S ub scribe r Info negative respon se
MA P_ CLOS E_ ind
OK Provide Subsc riber Info ack
To HL R call handling proce ss
Wait_For_ Call_Ha ndling_ Res ponse
2876
2877
Figure 21.2/9 (sheet 2 of 2): Process ATI_HLR (New)
1888
1889
2878
21.2.8 Process in the GMLC for Any Time Interrogation
2879 The message flows for successful retrieval of subscriber information related to an any time interrogation from the 2880 CAMEL server are shown in figure 21.2.8/1. 2881
GsmSCF
(1) -------------------------------------------------> (2) <------------------------------------------------(3) <-------------------------------------------------
GMLC
2889
2882 2883 2884 2885 2886 2887 2888
(1) (2) (3)
Any Time Interrogation (gsmSCF to GMLC). Any Time Interrogation Result (GMLC to gsmSCF). Any Time Interrogation Error (GMLC to gsmSCF)The following MAP services are used to retrieve routing information: - MAP_ANY_TIME_INTERROGATION see clause 8.11.1;
Figure 21.2.8/1
2890 In addition, the GMLC may use Location Services specific MAP Services.
2891 21.2.8.1
Process in the gsmSCF
2892 The process in the gsmSCF to request location information from the GMLC is shown in figure 21.2.8/2. 2893 The process is started with internal signal Request_Subscriber_Info_GMLC. This signal is sent by the Service Logic in 2894 the gsmSCF. 2895 The process responds with Request_Subscriber_Info_GMLC positive response or Request_Subscriber_Info_GMLC 2896 negative response.
2897 21.2.8.2
Process in the GMLC
2898 The MAP process in the GMLC to provide location information in response to a request from the gsmSCF is shown in 2899 figure 21.2.8/3. 2900 Successful outcome 2901 When the GMLC has successfully received the MAP Any_Time_Interrogation MAP Message, it will send an internal 2902 signal to the Location Service process in the GMLC to obtain the subscribers Location Information. The result received 2903 from that process is sent back to the gsmSCF, in the Any_Time_Interrogation Result MAP Message. 2904 Unsuccessful outcome 2905 In the case of a Provider Error received, the process will terminate. 2906 When a User error is received from the Location Services process in the GMLC, then a User Abort is sent to the 2907 gsmSCF. 2908 If a negative response is received from the Location Services process in the GMLC, then this response is forwarded to 2909 the gsmSCF.
1890
1891
Process Request_Subscriber_Info_GMLC Process in the gsmSCF to request Location Information From the GMLC
ATI_SCP_GMLC1(1) Signals to/from the left are to/from the Service Logic in the SCP. Signals to/from the right are to/from right are to/from the GMLC. Idle
Request_Subscriber_Info_GMLC
MAP_OPEN_req, MAP_ANY_TIME_INTERROGATION_req, MAP_DELIMITER_req
Receive_ Open_Cnf OK Wait_For_ GMLC_response
Section 25.1.2
Vr, Error Abort
MAP_CLOSE_ind, MAP_P_ABORT_ind, MAP_U_ABORT_ind
MAP_ NOTICE_ ind
Idle
MAP_ CLOSE_ req
MAP_ANY_TIME_INTERROGATION_cnf
Set negative response: System failure Request Subscriber Info GMLC negative response
Check_ Confirmation
Section 25.2.2 Provider error,
MAP_P_ ABORT_req
User error, Data error
OK
Idle Request Subscriber Info GMLC positive response
Idle
Idle
2910
2911
Figure 21.2.8/2: Process Request_Subscriber_Info_GMLC
1892
1893
Process ATI_GMLC
Figure 21.2/9.2: Process in the GMLC to respond to a request for any time interrogation
21.2/9.2
Signals to/from the left are to/from the gsmSCF; signals to/from the right are to/from the GMLC Location services
Idle
Receive_ Open_Ind
Section 25.1
OK Wait_For_ Service_ Indication
Vr Error
Idle
MAP_P_ ABORT_ind
MAP_ANY_TIME_INTERROGATION_ind
MAP_ NOTICE_ind
Idle
Any Time Interrogation Request
To GMLC location services (see 3G TS 23.078)
MAP_ CLOSE_req
Wait_For_ GMLC_ Response
Idle
User Error
Any Time Interrogation Response
From GMLC location services
Any Time Interrogation negative response
From GMLC location services
Set result
Set error
MAP_U_ ABORT_req
MAP_ANY_TIME_INTERROGATION_rsp
Idle
2912
2913
Figure 21.2.8/3: Process ATI_GMLC
1894
1895
2914 2915
21.3 Transfer of call handling
21.3.1 General
Gateway Visited Forwarded-to +---+ +---+ +---+ +---+ MSC+--------------HLR+----------------MSC+--------------L E +---+ +---+ +---+ +---+ MAP_RESUME_CALL_ HANDLING <-----------------+-------------------- MAP_SEND_ROUTING_ INFORMATION +-----------------> MAP_SEND_ROUTING_ INFORMATION ack <----------------- MAP_RESUME_CALL_ HANDLING ack +------------------+-------------------> I_REL (note) +------------------+-------------------> I_IAM (note) +------------------+--------------------+----------------->
NOTE: xxx = Optional Procedure 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 CCITT 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.
2916 The message flow for successful transfer of call handling to forward a call is shown in figure 21.3/1.
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
2952 2953 2954 2955 2956
2943 2944 2945 2946 2947 2948 2949 2950 2951
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.
2957
21.3.2 Process in the VMSC
2958 The MAP process in the VMSC to retrieve routeing information for a mobile terminating call is shown in figure 21.3/2. 2959 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 2960 2961
Receive_Open_Cnf Check_Confirmation
see clause 25.1.2; see clause 25.2.2.
2962 Successful Outcome 2963 2964 2965 2966 2967 2968
When the MAP process receives a Resume Call Handling request from the call handling process in the VMSC, it requests a dialogue with the GMSC whose identity is contained in the Resume Call Handling request by sending a MAP_OPEN service request, requests routeing information using a MAP_RESUME_CALL_HANDLING service request and invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the GMSC. VMSC shall not send any duplicate data to the GMSC.
1896
1897
2969 If the VMSC notices after receiving a Resume Call Handling request that the segmentation is needed the VMSC does 2970 not set the All Information Sent indicator. Otherwise the indicator is set and the process returns to the Wait For 2971 GMSC Response state. 2972 If the MAP process receives a MAP_RESUME_CALL_HANDLING service confirm from the GMSC, the MAP 2973 process invokes the macro Check_Confirmation to check the content of the confirm. 2974 2975 2976 2977 2978 2979
If the macro Check_Confirmation takes the OK exit, the MAP process checks if the All Information Sent indicator is set. If it is set the MAP process sends a Resume Call Handling ack to the call handling process in the VMSC and returns to the idle state. If the All Information Sent indicator is not set the MAP process checks if further segmentation is needed. If segmentation is needed the VMSC does not set the indicator and sends MAP_RESUME_CALL_HANDLING service request to the GMSC. Otherwise the indicator is set and the MAP_RESUME_CALL_HANDLING service request is sent to the GMSC.
2980 Dialogue opening failure 2981 If the macro Receive_Open_Cnf indicates that the dialogue with the GMSC could not be opened or that the dialogue 2982 can be opened only at an earlier version, the MAP process sends an Resume Call Handling negative response indicating 2983 system failure to the call handling process in the VMSC and returns to the idle state. 2984 Error in MAP_RESUME_CALL_HANDLING confirm 2985 If the MAP_RESUME_CALL_HANDLING service confirm contains a user error or a provider error, the MAP process 2986 sends a Resume Call Handling negative response to the call handling process in the VMSC and returns to the idle state. 2987 2988
NOTE:
the 'Data Error' exit from the macro Check_Confirmation is shown for formal completeness; the result is empty, so the MAP_PROVIDE_SUBSCRIBER_INFO_cnf primitive cannot contain a data error.
2989 Abort of GMSC dialogue 2990 2991 2992 2993
After the dialogue with the GMSC has been established, the MAP service provider may abort the dialogue by issuing a MAP_P_ABORT indication, or the GMSC may send a MAP_CLOSE indication. In either of these cases, the MAP process sends a Resume Call Handling negative response to the call handling process in the GMSC and returns to the idle state.
2994 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 2995 dialogue with the GMSC, sends a Resume Call Handling negative response indicating system failure to the call 2996 handling process in the VMSC and returns to the idle state.
1898
1899
Process R CH _ VM S C
F ig ur e 2 1 .3/ 2: P r oc e s s in the V M S C to re q ue st th e G M S C t o re s um e c all h and ling
21.3_ 2(1 )
S ig na ls to/ fr om the le ft ar e to /fr om th e G M S C; s ign als t o/ fro m the r igh t ar e to /fr om th e c all h and l ing pr o ce s s in th e V M S C Id le
Y es S e gm en tat io n ne ed ed No Y es
R es u m e C all H an d li n g
S eg m e nt ation n ee de d Se t " A ll In fo r m a tion S en t" i n dic a to r No
S et " A ll In for m a tio n S ent " ind ic ato r
M A P _R E S UM E_ CA LL _ HA N DL IN G _r e q, M A P _D E L IM I T E R _r eq
M A P _ O P E N _ re q, M A P _ RE S U M E _C A L L_ HA N DL IN G _r e q, M A P _ DE LIM IT E R _ re q
R e c eiv e_ O pen _ Cn f
S e c tio n 25. 1
OK V r , E r ro r W a it_ Fo r _ G M SC _ R e s po ns e Re s um e C a ll H and ling neg at iv e r es po ns e
M A P _R E SU M E _C AL L_ H A N D LI NG _c n f
M AP_ N O T I CE _in d
M A P _P _A BO R T _in d, M A P _C L O SE _ ind
I dl e
Ch ec k_ C onf ir m at io n
S ec tion 25 .2
M AP_ C LO S E _ re q
OK "A ll In for m a tio n S en t" i n dic a tor Se t Ye s Re s um e Ca ll H and li ng ac k
P r o v ide r E r ro r, U s er E rr or , D at a E rr or
No
R es u m e C all H an d li n g ne g ativ e r es p on s e
R e s um e C a ll H and l ing n eg at iv e r es p o ns e Id le
I dle
2997
2998
Figure 21.3/2: Process RCH_VMSC
1900
1901
2999
21.3.3 Process in the GMSC
3000 The MAP process in the GMSC to handle a request for the GMSC to resume call handling is shown in figure 21.3/3. 3001 The MAP process invokes a macro not defined in this clause; the definition of this macro can be found as follows: 3002
Receive_Open_Ind
see clause 25.1.1;
3003 Successful outcome 3004 When the MAP process receives a MAP_OPEN indication with the application context callControlTransfer, it checks it 3005 by invoking the macro Receive_Open_Ind. 3006 If the macro takes the OK exit, the MAP process waits for a service indication. 3007 3008 3009 3010 3011 3012 3013
If a MAP_RESUME_CALL_HANDLING service indication is received, the MAP process checks if the All Information Sent indicator is set and if so it sends a Resume Call Handling request including all the stored data to the call handling process in the GMSC, and waits for a response. The Resume Call Handling request contains the parameters received in the MAP_RESUME_CALL_HANDLING service indication. If the All Information Sent indicator is not set, the received data is stored and the MAP process constructs an empty MAP_RESUME_CALL_HANDLING service response, sends it to the VMSC and returns to the Wait For Service Indication state.
3014 If the call handling process in the GMSC returns a Resume Call Handling ack, the MAP process constructs a 3015 MAP_RESUME_CALL_HANDLING service response, constructs a MAP_CLOSE service request, sends them to the 3016 VMSC and returns to the idle state. 3017 Failure of dialogue opening with the VMSC 3018 If the macro Receive_Open_Ind takes the Vr exit or the Error exit, the MAP process returns to the idle state. 3019 If the MAP provider sends a MAP_P_ABORT while the MAP process is waiting for a service indication, the MAP 3020 process returns to the idle state. 3021 If the MAP provider sends a MAP_NOTICE while the MAP process is waiting for a service indication, the MAP 3022 process sends a MAP_CLOSE request to terminate the dialogue and returns to the idle state.
1902
1903
Process RCH_GMSC
F ig ur e 21 .3/ 3: Pr oc e s s in the G M SC t o h an dle a r e qu es t to re su me call h an dlin g
21.3_3(1)
Sign a ls to/ fr om the le ft ar e to /fr om the G M S C ca ll h an dlin g p r oc e ss ; sign als t o/f ro m the r ig h t ar e t o/f ro m the VM SC Id le
R e ceiv e _ O pe n_ Ind V r, Er ro r OK W a it_ F or _ S er v ic e_ I nd ica tio n
I dle
MA P_P _ AB O RT _ ind
M AP_ RE S U M E_C AL L_ HA N DL IN G _ in d
MA P _ N O T IC E_ ind
No "All I nfo r mat io n S e nt " ind ic ato r set I dle Yes MA P _ CL O SE _req
S t or e re ceive d dat a
A s sem ble r e ce ive d d ata
I dle M AP_ R ESU M E_ CA LL_ H AN D LI NG _r s p M AP_ D EL IME TE R_ r eq R e su me C a ll H a nd lin g
W ait_ F or _ Serv ice_ Ind icatio n
W a it_ F or _ C a ll_H a ndlin g_ R e spo ns e
Re s um e C a ll H and ling a ck
R es u me C all H an dlin g n eg at ive r es p o ns e
S et re s ult
Se t e rr o r
M AP_ RE S U M E_C AL L _H A N DL IN G _ rsp , M AP_ CL O SE _r eq
Id le
3023
3024
Figure 21.3/3: Process RCH_GMSC
1904
1905
3025 3026
21.4 Inter MSC Group Call Procedures
21.4.1 General
Network Anchor Relay +---+ +---+ E +---+ +----------MSC+-----------/--------------MSC +---+ +---+ +---+ I_IAM(note 1) +-------------> MAP_PREPARE_GROUP CALL +-----------------------------> MAP_PREPARE_GROUP CALL_ACK <----------------------------- I_IAM(note 1) +-----------------------------> MAP_SEND_GROUP CALL_END_SIGNAL <----------------------------- I_ACM (note 1) I_ACM(note 1)<----------------------------- <------------- MAP_FORWARD_GROUP CALL_SIGNALLING (note 2) +-----------------------------> MAP_PROCESS_GROUP CALL_SIGNALLING (note 2) <----------------------------- MAP_SEND_GROUP CALL_END_SIGNAL_ACK +-----------------------------> I_REL I_REL <------------><---------------------------->
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.
3027 The message flows for successful inter MSC group call / broadcast call set-up is shown in figure 21.4/1.
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
3065
3056 3057 3058 3059 3060 3061 3062 3063 3064
Figure 21.4/1: Message flow for inter MSC group call / broadcast call
3066
21.4.2 Process in the Anchor MSC
3067 The MAP process in the Anchor MSC to retrieve and transfer information from / to the Relay MSC for VBS and VGCS 3068 calls is shown in figure 21.4/2. The MAP process invokes macros not defined in this clause; the definitions of these 3069 macros can be found as follows: 3070 3071 3072
Receive_Open_Cnf Check_Indication Check_Confirmation
see clause 25.1.2; see clause 25.2.1; see clause 25.2.2.
3073 Successful Outcome 3074 3075 3076 3077 3078
When the MAP process receives a Prepare Group Call request from the ASCI handling process in the anchor MSC, it requests a dialogue with the relay MSC whose identity is contained in the Prepare Group Call request by sending a MAP_OPEN service request, requests an Group Call number by using a MAP_PREPARE_GROUP_CALL service request and invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the relay MSC.
3079 If the MAP process receives a MAP_PREPARE_GROUP_CALL service confirm from the relay MSC, the MAP 3080 process invokes the macro Check_Confirmation to check the content of the confirm.
1906
1907
3081 If the macro Check_Confirmation takes the OK exit, the MAP process sends a Prepare Group Call ack containing the 3082 Group Call number received from the relay MSC to the ASCI handling process in the anchor MSC and waits for 3083 completion of call set-up in the relay MSC. 3084 On receipt of a MAP_SEND_GROUP_CALL_END_SIGNAL service indication from the relay MSC the MAP process 3085 invokes the macro Check_Indication to check the content of the indication. 3086 If the macro Check_Indication takes the OK exit, the MAP process sends a Send Group Call End Signal to the ASCI 3087 handling process in the anchor MSC and waits for uplink management signals. In this state the following events are 3088 processed: 3089 3090 3091
Reception of a Send Group Call End Signal ack from the ASCI handling process in the anchor MSC; Reception of a Forward Group Call Signalling request from the ASCI handling process in the anchor MSC; Reception of a MAP_PROCESS_GROUP_CALL_SIGNALLING service indication from the relay MSC.
3092 On reception of a Send Group Call End Signal ack from the ASCI handling process in the anchor MSC, the MAP 3093 process constructs a MAP_SEND_GROUP_CALL_END_SIGNAL service response, constructs a MAP_CLOSE 3094 service request, sends them to the relay MSC and returns to the idle state. 3095 On reception of a Forward Group Call Signalling request from the ASCI handling process in the anchor MSC, the MAP 3096 process constructs a MAP_FORWARD_GROUP_CALL_SIGNALLING service request, sends it to the relay MSC and 3097 returns to the uplink management state. 3098 On reception of a MAP_PROCESS_GROUP_CALL_SIGNALLING service indication from the relay MSC, the MAP 3099 process invokes the macro Check_Indication to check the content of the indication. 3100 If the macro Check_Indication takes the OK exit, the MAP process sends a Process Group Call Signalling to the ASCI 3101 handling process in the anchor MSC and returns to the uplink management state. 3102 Dialogue opening failure 3103 If the macro Receive_Open_Cnf indicates that the dialogue with the relay MSC could not be opened, the MAP process 3104 sends an Abort to the ASCI handling process and returns to the idle state. 3105 Error in MAP_PREPARE_GROUP_CALL confirm 3106 3107 3108 3109
If the MAP_PREPARE_GROUP_CALL service confirm contains a user error or a provider error, or the macro Check_Confirmation indicates that there is a data error, the MAP process sends a Prepare Group Call negative response to the ASCI handling process in the anchor MSC, sends a MAP_U_ABORT request to the relay MSC and returns to the idle state.
3110 Abort of MAP dialogue 3111 3112 3113 3114
After the dialogue with the relay MSC has been established, the MAP service provider may abort the dialogue by issuing a MAP_P_ABORT indication, or the relay MSC may send a MAP_U_ABORT indication or a MAP_CLOSE indication. In any of these cases, the MAP process sends an Abort to the ASCI handling process in the anchor MSC and returns to the idle state.
3115 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 3116 dialogue with the relay MSC, sends an Abort to the ASCI handling process in the anchor MSC and returns to the idle 3117 state.
1908
1909
Process ASCI_Anchor_MSC
Fig ure 2 1 .4/2 : Proce ss in th e A nch or M SC fo r AS CI c all h and ling Sig na ls t o/from the le ft a re to /fro m th e A -M SC A SCI p ro ces s; sig nals to /from t he rig ht are to/ from t he R -M SC
21.4_2.1(4)
Id le
Pre p are Grou p Ca ll
M A P_OP EN _ re q, M A P_ PR EP AR E_ GR OUP_ CA LL _req , M A P_DE LIM ITE R_ re q
R ec eive _ Op en _C nf
S ect ion 25 .1
OK
els e
W ait for Grou p Ca ll Nu m be r
A bo rt
Idle
3118
3119
Figure 21.4/2 (sheet 1 of 4): Process ASCI_Anchor_MSC
1910
1911
Process ASCI_Anchor_MSC
Figure 2 1.4/2: Process in the A nchor MSC for AS CI c all hand ling Sig nals t o/from the le ft are to/fro m the A -MSC A SCI proces s; sig nals to/from t he right are to/ from t he R-MSC
21.4_2.2(4)
W ait for Group Call Number
MAP _PREP ARE _GROUP_ CA LL_c nf
MAP _ NOTICE_ ind
MAP _U_ABORT_ind MAP _P _AB ORT_ ind MAP _CLOSE_ind
Check Con firmation
Section 25 .2
MAP _CLOSE _ req
OK
else A bort
Prep are Gro up Call ACK
Prepare Gro up Call negative rsp
Idle
W a it for Completio n
MA P_U_ AB ORT_ req
Idle
3120
3121
Figure 21.4/2 (sheet 2 of 4): Process ASCI_Anchor_MSC
1912
1913
Process ASCI_Anchor_MSC
Figure 2 1.4/2: Process in the A nchor MSC for AS CI c all hand ling Sig nals t o/from the left are to/from th e A -MS C A SCI proces s; signals to/from t he right are to/from t he R-MSC
21.4_2.3(4)
W a it for Completio n
MAP_SE ND_ GROU P_CALL_ END_SIGNAL_ ind
Ch ec k In dic ation
Se ction 25.2
OK
else
Se nd Group Call End Signal
Ab ort
Uplink Manag ement
MA P_U_ AB ORT_req
Idle
3122
3123
Figure 21.4/2 (sheet 3 of 4): Process ASCI_Anchor_MSC
1914
1915
Process ASCI_Anchor_MSC
Figure 2 1.4/2: Process in the A nchor MSC for AS CI c all hand ling Sig nals t o/from the le ft are to/fro m the A -MSC A SCI proces s; sig nals to/from t he right are to/ from t he R-MSC
21.4_2.4(4)
Uplink Manag ement
Se nd Group Call End Signa l ACK
Forward Grou p Call S ign alling
MAP_SE ND_GRO UP_CA LL_ END_S IGNA L_rs p, MA P_CLOSE _req
MAP _FORW ARD_ GROUP_CA LL_ SIGNA LLI NG _req, MAP _DEL IMITE R_ req
Idle
Uplink Manag ement
Uplink Manag ement
MAP _PROCE SS _GROUP_CA LL _S IGNA LL ING _ind
Ch ec k In dic ation
Section 25 .2
OK P roc ess Gro up Call S igna lling MA P_ U_ AB ORT_req
else
Uplink Manag ement
Abort
Idle
3124
3125
Figure 21.4/2 (sheet 4 of 4): Process ASCI_Anchor_MSC
1916
1917
3126
21.4.3 Process in the Relay MSC
3127 The MAP process in the Relay MSC to receive and transfer information from / to the Anchor MSC for VBS and VGCS 3128 calls is shown in figure 21.4/3. The MAP process invokes macros not defined in this clause; the definitions of these 3129 macros can be found as follows: 3130 3131
Receive_Open_Ind Check_Indication
see clause 25.1.2; see clause 25.2.1.
3132 Successful Outcome 3133 When the MAP process receives a MAP_OPEN indication with the application context groupCallControl, it checks it 3134 by invoking the macro Receive_Open_Ind. 3135 If the macro takes the OK exit, the MAP process waits for a service indication. 3136 If a MAP_PREPARE_GROUP_CALL service indication is received, the MAP process invokes the macro 3137 Check_Indication. 3138 If the macro takes the OK exit, the MAP process sends a Prepare Group Call request to the ASCI handling process in 3139 the relay MSC and waits for a response. The Prepare Group Call request contains the parameters received in the 3140 MAP_PREPARE_GROUP_CALL service indication. 3141 3142 3143 3144 3145 3146 3147 3148 3149 3150 3151
If the ASCI handling process in the relay MSC returns a Prepare Group Call ack, the MAP process constructs a MAP_PREPARE_GROUP_CALL service response containing the information contained in the Prepare Group Call ack, constructs a MAP_DELIMITER service request, sends them to the anchor MSC and waits for the GROUP CALL END SIGNAL. If the ASCI handling process in the relay MSC sends a Send Group Call End Signal request to the MAP process, the MAP process constructs a MAP_SEND_GROUP_CALL_END_SIGNAL service request containing the information contained in the SEND GROUP CALL End Signal request, constructs a MAP_DELIMITER service request, sends them to the anchor MSC and waits for uplink management signals. In this state the following events are processed: Reception of a MAP_SEND_GROUP_CALL_END_SIGNAL service confirmation from the anchor MSC; Reception of a MAP_FORWARD_GROUP_CALL_SIGNALLING service indication from the anchor MSC; Reception of a Process Group Call Signalling request from the ASCI handling process in the relay MSC.
3152 On reception of a MAP_SEND_GROUP_CALL_END_SIGNAL service confirmation from the anchor MSC, the MAP 3153 process returns to the idle state. 3154 3155 3156 3157 3158 3159 3160 3161
On reception of a MAP_FORWARD_GROUP_CALL_SIGNALLING service indication from the anchor MSC, the MAP process invokes the macro Check Indication. If the macro takes the OK exit, the MAP process sends a Forward Group Call Signalling request to the ASCI handling process in the relay MSC and waits for further uplink management signals. On reception of a Process Group Call Signalling request from the ASCI handling process in the relay MSC, the MAP process constructs a MAP_PROCESS_GROUP_CALL_SIGNALLING service request containing the information received in the Process Group Call Signalling request, constructs a MAP_DELIMITER service request, sends them to the anchor MSC and waits for further uplink management signals.
3162 Failure of dialogue opening with the anchor MSC 3163 If the macro Receive_Open_Ind takes the Error exit, the MAP process returns to the idle state. 3164 If the MAP provider sends a MAP_P_ABORT while the MAP process is waiting for a service indication, the MAP 3165 process returns to the idle state. 3166 If the MAP provider sends a MAP_NOTICE while the MAP process is waiting for a service indication, the MAP 3167 process sends a MAP_CLOSE request to terminate the dialogue and returns to the idle state. 3168 Error in MAP_PREPARE_GROUP_CALL indication
1918
1919
3169 If the macro Check Indication takes the Error exit, the MAP process sends a MAP_U_ABORT request to the anchor 3170 MSC and returns to the idle state. 3171 Negative response received from the ASCI handling process 3172 If the ASCI handling process in the relay MSC returns a negative response to the Prepare Group Call request, the MAP 3173 process constructs a MAP_PREPARE_GROUP_CALL service response containing the appropriate error, constructs a 3174 MAP_CLOSE service request, sends them to the anchor MSC and returns to the idle state. 3175 Error in MAP_FORWARD_GROUP CALL_SIGNALLING indication 3176 If the macro Check Indication takes the Error exit, the MAP process sends a MAP_U_ABORT request to the anchor 3177 MSC, sends an Abort to the ASCI handling process in the relay MSC ind returns to the idle state. 3178 Abort of MAP dialogue 3179 3180 3181 3182
After the dialogue with the anchor MSC has been established, the MAP service provider may abort the dialogue by issuing a MAP_P_ABORT indication, or the anchor MSC may send a MAP_U_ABORT indication or a MAP_CLOSE indication. In any of these cases, the MAP process sends an Abort to the ASCI handling process in the relay MSC and returns to the idle state.
3183 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 3184 dialogue with the anchor MSC, sends an Abort to the ASCI handling process in the anchor MSC and returns to the idle 3185 state.
1920
1921
Process ASCI_Relay_MSC
F igure 21.4/3: Proc ess in the R elay M SC for ASCI call handling
21.4_3.1(3)
Sign als to/fr om the left ar e to/fr om the A-M SC; Sign als to/fr om the righ t ar e to/fr om the R- MSC ASCI proc ess
Idle
Receive Open _Ind
Section 25.1
OK
Vr , Error
W ait for Servic e Indication
Idle
MAP_P_ ABOR T_ind
MAP_PREPARE_ GR OUP_CALL_in d
M AP_ NOTIC E_ in d
Idle
C heck Indication
M AP_ C LOSE_req
OK
else Idle
Prepar e Group Call
M AP_U _ ABORT_req
W ait for G roup C all N umber
Idle
3186
3187
Figure 21.4/3 (sheet 1 of 3): Process ASCI_Relay_MSC
1922
1923
Process ASCI_Relay_MSC
F igure 21.4/3: Proc ess in the Relay M SC for ASCI c all handling
21.4_3.2(3)
Signals to/from the lef t are to/from the A-MSC; Signals to/from the right are to/from the R -M SC ASCI proc ess
W ait for Group Call Number
Prepare Group C all ACK
Prepare Group Call negative rsp
Set result
Set error
MAP_PR EPARE_GR OUP_CALL_rsp, MAP_DELIMITER_req
M AP_PR EPARE_GROU P_C ALL_rsp, M AP_CLOSE_req
W ait for End Signal
Idle
MAP_ NOTIC E_ind
MAP_U _ABORT_ind MAP_P_ABORT_ind MAP_C LOSE_ind
MAP_ CLOSE_req
Abort
Idle
3188
3189
Figure 21.4/3 (sheet 2 of 3): Process ASCI_Relay_MSC
1924
1925
Process ASCI_Relay_MSC
F igure 21.4/3: Proc ess in the Relay M SC for ASCI c all handling
21.4_3.3(3)
Signals to/fr om the left are to/from the A-MSC; Signals to/fr om the right are to/from the R-MSC ASCI proc ess
W ait for End Signal
Send Group Call End Signal
MAP_SEN D_G ROU P_CALL_EN D_SIGNAL_req, MAP_DELIMITER_req
Uplink Managem ent
MAP_SEND _ GROUP_CALL_ END_SIGN AL _cnf No VGCS Yes OK Send Group Call End Signal AC K Forward Group Call Signalling
MAP_FOR W ARD_ GROU P_C ALL_ SIGN ALLING_ind
Process Group C all Signalling
Check Indic ation else Uplink M anagement
M AP_PROC ESS_GR OUP_CALL_ SIGNALLING_req, M AP_DELIMIT ER_req
Abort
Uplink Management
MAP_U _ ABORT_req
Idle
Idle
3190
3191
Figure 21.4/3 (sheet 3 of 3): Process ASCI_Relay_MSC
1926
1927
3192 3193 3194
21.5 Allocation and modifications of resources in an SIWFS
21.5.1 General
3195 The message flow for successful allocation and modification of resources in an SIWFS is shown in figure 21.5/1 3196 (mobile originating call non-loop method), 21.5/2 (mobile originating call loop method) and 21.5/3 (mobile terminating 3197 call loop method).
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 3243 3244 3245 3246 3247 3248 3249 3250
3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261
xxx = Optional Procedure NOTE 1: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the MSCs. The Release message can be initiated either by the calling or called subscriber. For further details on the TUP and ISUP procedures refer to the following CCITT 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: The number on the ISUP messages have been added to link the messages to respective signalling sequence. NOTE 3: The modification of SIWF resources could be initiated any time during the call either by the VMSC or the SIWFS.
Visited +---+ +-----+ +----+ MSC+---------------------SIWFS+---------------------ISDN +---+ +-----+ +----+ MAP_PROVIDE_SIWFS_ NUMBER +-------------------------> MAP_PROVIDE_SIWFS_ NUMBER_ack <------------------------- 1 I_IAM (note) +-------------------------> I_IAM2 (note) +--------------------------> I_ACM2 (note) <-------------------------- I_ACM1 (note) <------------------------- 2 I_ANM (note) <-------------------------- I_ANM1 (note) <------------------------- MAP_SIWFS_SIGNALLING_ MODIFY +-------------------------> MAP_SIWFS_SIGNALLING_ MODIFY_ack <------------------------- MAP_SIWFS_SIGNALLING_ MODIFY <------------------------- MAP_SIWFS_SIGNALLING_ MODIFY_ack -------------------------> I_REL1 (note) +-------------------------> 1 2 I_RLC (note) I_REL (note) <-------------------------+--------------------------> I_RLC2 (note) <-------------------------- MAP_CLOSE_ +------------------------->
1928
1929
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 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
Figure 21.5/1: Message flow for mobile originating call non-loop method Visited +---+ +-----+ +----+ MSC+---------------------SIWFS+---------------------ISDN +---+ +-----+ +----+ MAP_PROVIDE_SIWFS_ NUMBER +-------------------------> MAP_PROVIDE_SIWFS_ NUMBER_ack <------------------------- 1 I_IAM (note) +-------------------------> 2 I_IAM (note) <------------------------- 3 I_IAM (note) +--------------------------+--------------------------> I_ACM3 (note) <-------------------------+--------------------------- I_ACM2 (note) +-------------------------> 1 I_ACM (note) <------------------------- 3 I_ANM (note) <-------------------------+--------------------------- I_ANM2 (note) +-------------------------> 1 I_ANM (note) <------------------------- MAP_SIWFS_SIGNALLING_ MODIFY +-------------------------> MAP_SIWFS_SIGNALLING_ MODIFY_ack <------------------------- MAP_SIWFS_SIGNALLING_ MODIFY <------------------------- MAP_SIWFS_SIGNALLING_ MODIFY_ack -------------------------> 1 I_REL (note) +-------------------------> 1 I_RLC (note) <------------------------- 2 I_REL (note) <------------------------- 2 I_RLC (note) +-------------------------> 3 I_REL (note) +--------------------------+--------------------------> I_RLC3 (note) <-------------------------+--------------------------- MAP_CLOSE +------------------------->
3338 3339 3340 3341 3342 3343 3344
xxx = Optional Procedure NOTE 1: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the MSCs. The Release message can be initiated either by calling or called subscriber. For further details on the TUP and ISUP procedures refer to the following CCITT 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.
1930
1931 3345 3346 3347 3348
NOTE 2: The number on the ISUP messages have been added to link the messages to respective signalling sequence. NOTE 3: The modification of SIWF resources could be initiated any time during the call either by the VMSC or the SIWFS.
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 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
Figure 21.5/2: Message flow for mobile originating call loop method Visited +---+ +-----+ +----+ MSC+---------------------SIWFS+---------------------ISDN +---+ +-----+ +----+ I_IAM1 (note) <-------------------------+--------------------------- MAP_PROVIDE_SIWFS_ NUMBER +-------------------------> MAP_PROVIDE_SIWFS_ NUMBER_ack <------------------------- 2 I_IAM (note) +-------------------------> 3 I_IAM (note) <------------------------- 3 I_ACM (note) +-------------------------> 2 I_ACM (note) <------------------------- 1 I_ACM (note) --------------------------+--------------------------> I_ANM3 (note) +-------------------------> 2 I_ANM (note) <------------------------- 1 I_ANM (note) --------------------------+--------------------------> MAP_SIWFS_SIGNALLING_ MODIFY +-------------------------> MAP_SIWFS_SIGNALLING_ MODIFY_ack <------------------------- MAP_SIWFS_SIGNALLING_ MODIFY <------------------------- MAP_SIWFS_SIGNALLING_ MODIFY_ack -------------------------> 1 I_REL (note) <-------------------------+--------------------------- I_RLC1 (note) +--------------------------+--------------------------> I_REL2 (note) +-------------------------> 2 I_RLC (note) <------------------------- 3 I_REL (note) <------------------------- 3 I_RLC (note) +-------------------------> MAP_CLOSE +------------------------->
xxx = Optional Procedure
3427
1932
1933 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438
NOTE 1: TUP or ISUP may be used in signalling between MSCs, depending on the network type between the MSCs. The Release message can be initiated either by calling or called subscriber. For further details on the TUP and ISUP procedures refer to the following CCITT 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: The number on the ISUP messages have been added to link the messages to respective signalling sequence. NOTE 3: The modification of SIWF resources could be initiated any time during the call either by the VMSC or the SIWFS.
3439
Figure 21.5/3: Message flow for mobile terminating call loop method
3440 The following MAP services are used to allocate resources in an SIWFS: 3441
MAP_PROVIDE_SIWFS_NUMBER
see clause 10.8.
3442 The following MAP services are used to modify resources in an SIWFS: 3443
MAP_SIWFS_SIGNALLING_MODIFY
see clause 10.9.
3444
21.5.2 Process in the VMSC
3445 The MAP process in the VMSC to allocate and modify resources in an SIWFS for a mobile call is shown in 3446 figure 21.5/4. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found 3447 as follows: 3448 3449
Receive_Open_Cnf Check_Confirmation
see clause 25.1.2; see clause 25.2.2.
3450 21.5.2.1
Allocation of SIWFS resources
3451 Successful Outcome 3452 3453 3454 3455 3456
When the MAP process receives a Provide SIWFS Number request from the call handling process in the VMSC, it requests a dialogue with the SIWF whose identity is contained in the Provide SIWFS Number request by sending a MAP_OPEN service request, requests resources in the SIWFS using a MAP_PROVIDE_SIWFS_NUMBER service request and invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the SIWFS.
3457 If the MAP process receives a MAP_PROVIDE_SIWFS_NUMBER service confirm from the SIWFS, the MAP 3458 process invokes the macro Check_Confirmation to check the content of the confirm. 3459 If the macro Check_Confirmation takes the OK exit, the MAP process sends a Provide SIWFS Number ack containing 3460 the SIWFS Number received from the SIWFS to the call handling process in the VMSC and go to 3461 Wait_For_Modification state. 3462 Earlier version MAP dialogue with the SIWFS 3463 If the macro Receive_Open_Cnf takes the Vr exit, the MAP process sends an Abort to the call handling process in the 3464 VMSC and returns to the idle state. 3465 Dialogue opening failure 3466 If the macro Receive_Open_Cnf indicates that the dialogue with the SIWFS could not be opened, the MAP process 3467 sends an Abort to the call handling process in the VMSC and returns to the idle state. 3468 Error in MAP_PROVIDE_SIWFS_NUMBER confirm 3469 If the MAP_PROVIDE_SIWFS_NUMBER service confirm contains a user error or a provider error, or the macro 3470 Check_Confirmation indicates that there is a data error, the MAP process sends a Provide SIWFS number negative 3471 response to the call handling process in the VMSC and returns to the idle state. 3472 Call release
1934
1935
3473 If the call handling process in the VMSC indicates that the call has been aborted, the MAP process returns to the idle 3474 state. Any response from the SIWFS will be discarded. 3475 If the call handling process in the VMSC indicates that the traffic channel has been released (i.e. call released by a user) 3476 a MAP_CLOSE_req is sent and the process is returned to the idle state. 3477 Abort of SIWFS dialogue 3478 3479 3480 3481
During the time an answer is expected from the SIWFS, the MAP service provider may abort the dialogue by issuing a MAP_P_ABORT indication, or the SIWFS may send a MAP_U_ABORT indication or a MAP_CLOSE indication. In any of these cases, the MAP process sends a Provide SIWFS number negative response to the call handling process in the VMSC and returns to the idle state.
3482 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 3483 dialogue with the SIWFS, sends a Provide SIWFS number negative response indicating system failure to the call 3484 handling process in the VMSC and returns to the idle state. 3485 After the dialogue with the SIWFS has been established, the MAP service provider may abort the dialogue by issuing a 3486 MAP_P_ABORT indication, or the SIWFS may send a MAP_U_ABORT indication or a MAP_CLOSE indication. In 3487 any of these cases, the MAP process returns to the idle state. 3488 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 3489 dialogue with the SIWFS, and returns to the idle state.
3490 21.5.2.2
Modification of SIWFS resources initiated by the user
3491 Successful Outcome 3492 When the MAP process receives an SIWFS Signalling Modify request from the call handling process in the VMSC, it 3493 requests a dialogue with the SIWFS whose identity is contained in the SIWFS Signalling Modify request by sending a 3494 MAP_SIWFS_SIGNALLING_MODIFY service request and waits for a response from the SIWFS. 3495 If the MAP process receives a MAP_SIWFS_SIGNALLING_MODIFY service confirm from the SIWFS, the MAP 3496 process invokes the macro Check_Confirmation to check the content of the confirm. 3497 If the macro Check_Confirmation takes the OK exit, the MAP process sends an SIWFS Signalling Modify ack 3498 containing the response received from the SIWFS to the call handling process in the VMSC and go to 3499 Wait_For_Modification state. 3500 Error in MAP_SIWFS_SIGNALLING_MODIFY confirm 3501 If the MAP_SIWFS_SIGNALLING_MODIFY service confirm contains a user error or a provider error, or the macro 3502 Check_Confirmation indicates that there is a data error, the MAP process sends an SIWFS Signalling Modify negative 3503 response to the call handling process in the VMSC and go to Wait_For_Modification state. 3504 Abort of SIWFS dialogue 3505 3506 3507 3508
During the time an answer is expected from the SIWFS, the MAP service provider may abort the dialogue by issuing a MAP_P_ABORT indication, or the SIWFS may send a MAP_U_ABORT indication or a MAP_CLOSE indication. In any of these cases, the MAP process sends an SIWFS Signalling Modify negative response to the call handling process in the VMSC and returns to the idle state.
3509 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 3510 dialogue with the SIWFS, sends an SIWFS Signalling Modify negative response indicating system failure to the call 3511 handling process in the VMSC and returns to the idle state.
3512 21.5.2.3
Modification of SIWFS resources initiated by the SIWFS
3513 Successful outcome 3514 3515 3516 3517
If a MAP_SIWFS_SIGNALLING_MODIFY service indication is received, the MAP process sends an SIWFS signalling modify Info request to the call handling process in the VMSC, and waits for a response. The SIWFS signalling modify request contains the parameters received in the MAP_SIWFS_SIGNALLING_MODIFY service indication.
1936
1937
3518 If the call handling process in the VMSC returns an SIWFS signalling modify ack, the MAP process constructs a 3519 MAP_SIWFS_SIGNALLING_MODIFY service response contained in the Provide SIWFS Number ack, send it to the 3520 SIWFS and go to Wait_For_Modification state. 3521 Negative response from VMSC call handling process 3522 If the call handling process in the VMSC returns a negative response the MAP process constructs a 3523 MAP_SIWFS_SIGNALLING_MODIFY service response containing the appropriate error, send it to the SIWFS and go 3524 to Wait_For_Modification state.
1938
1939
Process SRA_VMSC
F igure 21.5/4: Proc ess in the VMSC for adm inistration of SIW F S r esourc es Idle
21.5_4.1(6)
Signals to/from th e left are to/f rom the VMSC call handling process; signals to/fr om the right are to/from the SIW FS
Send_Pr ovide_ SIW F S_N um ber
M AP_ OPEN_req, M AP_ PROVIDE_SIW FS_ NUM BER _r eq, M AP_ DELIMITER _req
R eceive_ Open_Cnf OK W ait_F or _SIW F S_ Re spons e
Section 2 5.1
Er ror, Vr Abor t
MAP_PR OVID E_ SIW FS_NU MBER_cnf
Idle
Check _ Confirm at io n Ok
Section 25 .2
Pr ovider Error, User Err or, Data Error
Send_Pr ovide_ SIW FS_Num be r_ ack
Send_Pro vide_ SIW FS_Num ber negative r esponse
W ait_For_ M odificatio n
Idle
3525
3526
Figure 21.5/4 (sheet 1 of 6): Process SRA (SIWFS_RESOURCE_ADMINISTRATION)_VMSC
1940
1941
Process SRA_VMSC
F igur e 21.5/4: Proc ess in th e V MS C for a dm inistra tion of SIW F S resourc es W ait_For_SIW FS_ R esponse
21.5_4.2(6)
Signals to/from th e left are to/f rom the V MSC call handling proce ss; sign als to/fr om the right are to/from the S IW FS
Abor t
Call Released
M A P_U_A BORT_ind M AP _P_A BO RT_ind M A P_CL OSE_in d
M AP _ NOTIC E_ind
Idle
MA P_ CLO SE _r eq
M AP _ CLOS E_req
Id le
S et negative respon se: S ystem Fa ilu re
Send_Pro vide _ SIW FS_Nu m ber negative r esponse
Idle
3527
3528
Figure 21.5/4 (sheet 2 of 6): Process SRA_VMSC
1942
1943
Process SRA_VMSC
Fig ure 2 1 .5/ 4: P ro ce ss in th e V MS C fo r a dm i nistrat io n o f SIW FS re so urces W a it_ For_ M od ificat ion
21.5_4.3(6)
S ig na ls to /from th e lef t are to/ from th e V M SC ca ll ha ndlin g proce ss; sign a ls to/ from t he rig ht are to/ from th e SIW FS
Ab ort
Ca ll Re leas ed
M AP _ U_ ABO RT_in d, M AP _P _A BORT_ind , M AP _ CL OSE _in d
MA P_ NOTICE_ ind
Id le
MA P_ CL OSE _req
MA P_ CLOSE _ re q
Id le
Idle
3529
3530
Figure 21.5/4 (sheet 3 of 6): Process SRA_VMSC
1944
1945
Process SRA_VMSC
F igure 21.5/4: Proc ess in the VMSC for adm inistration of SIW F S r esourc es W ait_For_ M odific ation
21.5_4.4(6)
Signals to/fr om the left are to/f rom th e VM SC call h andling process; sign als to/f rom the right are to/from th e SIW F S
Send_SIW FS_ Signalling_ M odify
M AP_SIW FS_SIG NALLING_M ODIFY_r eq, M AP_ DELIMITER _req
W ait_Fo r_SIW FS_ M odification_R esponse
M AP_ SIW FS_SIGN ALLING_M ODIFY_cfn
C heck_ C onfir m ation
Section 2 5.1
OK
Provider Err or, User Error, Data Er ror
Send_SIW FS_ Signalling_ M odify ack
Sen d_SIW FS_ Signalling_M odify negative response
W ait_For_ M odification
W ait_F or_ M odification
3531
3532
Figure 21.5/4 (sheet 4 of 6): Process SRA_VMSC
1946
1947
Process SRA_VMSC
F igur e 21.5/4: Proc ess in th e V MS C for a dm inistra tion of SIW F S resourc es W ait_For_SIW FS_ M odification_Response
21.5_4.5(6)
Signals to/from th e left are to/f rom the V MSC call handling proce ss; sign als to/fr om the right are to/from the S IW FS
Abor t
Ca ll Re leased
M AP _U _AB OR T_ind, M AP_ P _ABOR T_ind, M AP _C LOSE _ ind
M A P_ NOTIC E_in d
Idle
MA P_ CL OSE _req
M A P_ C LOS E_ req
Idle
Set negati ve response: System Failure
S en d_S IW FS _ S ignalling_M odify negative re spons e
Id le
3533
3534
Figure 21.5/4 (sheet 5 of 6): Process SRA_VMSC
1948
1949
Process SRA_VMSC
F igure 21.5/4: Proc ess in the VMSC for adm inistration of SIW F S r esourc es
21.5_4.6(6)
Signals to/from th e left are to/f rom the VMSC call handling process; signals to/fr om the right are to/from the SIW FS W ait_For_ M odific ation
M AP_SIW FS_SIG NALLING_M ODIF Y_ind
Send_SIW FS_ Signalling_ M odify
W ait_For _ C all_Han dling_ R esponse
Send_SIW FS_ Signalling_ M odify ack
Sen d_SIW FS_ Signalling_M odify negative response
Set result
Set error
M AP_ SIW FS_SIGN ALLING_M ODIFY_rs p M AP_ DELIMITER _req
W ait_For_ M odific ation
3535
3536
Figure 21.5/4 (sheet 6 of 6): Process SRA_VMSC
1950
1951
3537
21.5.3 Process in the SIWFS
3538 The MAP process in the SIWFS to allocate and modify SIWFS resources for a mobile call is shown in figure 21.5/5. 3539 The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows: 3540 3541
Receive_Open_Ind Check_Confirmation
see clause 25.1.1. see clause 25.2.2.
3542 21.5.3.1
Procedures for allocation of SIWFS resources
3543 Successful outcome 3544 When the MAP process receives a MAP_OPEN indication with the application context locInfoRetrieval, it checks it by 3545 invoking the macro Receive_Open_Ind. 3546 If the macro takes the OK exit, the MAP process waits for a service indication. 3547 If a MAP_PROVIDE_SIWFS_NUMBER service indication is received, the MAP process sends a Provide SIWFS 3548 number Info request to the call handling process in the SIWFS, and waits for a response. The Provide SIWFS number 3549 request contains the parameters received in the MAP_PROVIDE_SIWFS_NUMBER service indication. 3550 3551 3552 3553
If the call handling process in the SIWFS returns a Provide SIWFS number ack, the MAP process constructs a MAP_PROVIDE_SIWFS_NUMBER service response containing the routing information contained in the Provide SIWFS Number ack, constructs a MAP_DELIMITER service request, sends them to the VMSC and go to Wait_For_Modification state.
3554 Earlier version MAP dialogue with the VMSC 3555 If the macro Receive_Open_Ind takes the Vr exit, the MAP process returns to the idle state. 3556 Dialogue opening failure 3557 If the macro Receive_Open_Ind takes the Error exit, the MAP process returns to the idle state. 3558 If the MAP provider sends a MAP_P_ABORT while the MAP process is waiting for a service indication, the MAP 3559 process returns to the idle state. 3560 If the MAP provider sends a MAP_NOTICE while the MAP process is waiting for a service indication, the MAP 3561 process sends a MAP_CLOSE request to terminate the dialogue and returns to the idle state. 3562 Negative response from SIWFS call handling process 3563 If the call handling process in the SIWFS returns a negative response the MAP process constructs a 3564 MAP_PROVIDE_SIWFS_NUMBER service response containing the appropriate error, constructs a MAP_CLOSE 3565 service request, sends them to the VMSC and returns to the idle state. 3566 Call release 3567 If the call handling process in the SIWFS indicates that the call has been aborted, the MAP process returns to the idle 3568 state. Any response from the VMSC will be discarded. 3569 If the call handling process in the SIWFS indicates that the traffic channel has been released (i.e. call released by a user) 3570 a MAP_CLOSE_req is sent and the process is returned to the idle state. 3571 Abort of VMSC dialogue 3572 After the dialogue with the VMSC has been established, the MAP service provider may abort the dialogue by issuing a 3573 MAP_P_ABORT indication, or the VMSC may send a MAP_U_ABORT indication or a MAP_CLOSE indication. In 3574 any of these cases, the MAP process returns to the idle state. 3575 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 3576 dialogue with the VMSC, and returns to the idle state.
1952
1953
3577 21.5.3.2
Process for modification of SIWFS resources initiated by the user
3578 Successful outcome 3579 3580 3581 3582
If a MAP_SIWFS_SIGNALLING_MODIFY service indication is received, the MAP process sends an SIWFS signalling modify Info request to the call handling process in the SIWFS, and waits for a response. The SIWFS signalling modify request contains the parameters received in the MAP_SIWFS_SIGNALLING_MODIFY service indication.
3583 If the call handling process in the SIWFS returns an SIWFS signalling modify ack, the MAP process constructs a 3584 MAP_SIWFS_SIGNALLING_MODIFY service response contained in the Provide SIWFS Number ack, send it to the 3585 VMSC and go to Wait_For_Modification state. 3586 Negative response from SIWFS call handling process 3587 If the call handling process in the SIWFS returns a negative response the MAP process constructs a 3588 MAP_SIWFS_SIGNALLING_MODIFY service response containing the appropriate error, send it to the VMSC and go 3589 to Wait_For_Modification state.
3590 21.5.3.3
Process for modification of SIWFS resources initiated by the SIWFS
3591 Successful Outcome 3592 3593 3594 3595
When the MAP process receives an SIWFS Signalling Modify request from the call handling process in the SIWF, it requests a dialogue with the VMSC whose identity is contained in the VMSC Signalling Modify request by sending a MAP_DELIMITER service request, requests resources in the VMSC using a MAP_SIWFS_SIGNALLING_MODIFY service request, the MAP process waits for a response from the VMSC.
3596 If the MAP process receives a MAP_SIWFS_SIGNALLING_MODIFY service confirm from the VMSC, the MAP 3597 process invokes the macro Check_Confirmation to check the content of the confirm. 3598 If the macro Check_Confirmation takes the OK exit, the MAP process sends an SIWFS Signalling Modify ack 3599 containing the response received from the VMSC to the call handling process in the SIWF and go to 3600 Wait_For_Modification state. 3601 Error in MAP_SIWFS_SIGNALLING_MODIFY confirm 3602 If the MAP_SIWFS_SIGNALLING_MODIFY service confirm contains a user error or a provider error, or the macro 3603 Check_Confirmation indicates that there is a data error, the MAP process sends an SIWFS Signalling Modify negative 3604 response to the call handling process in the SIWFS and go to Wait_For_Modification state. 3605 Abort of SIWFS dialogue 3606 3607 3608 3609
During the time an answer is expected from the VMSC, the MAP service provider may abort the dialogue by issuing a MAP_P_ABORT indication, or the VMSC may send a MAP_U_ABORT indication or a MAP_CLOSE indication. In any of these cases, the MAP process sends an SIWFS Signalling Modify negative response to the call handling process in the SIWFS and returns to the idle state.
3610 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 3611 dialogue with the VMSC, sends an SIWFS Signalling Modify negative response indicating system failure to the call 3612 handling process in the SIWFS and returns to the idle state.
1954
1955
Process SR A_S IW F S
F ig u re 2 1. 5/5 : P ro c es s in the S IW F S fo r a dm inis tration of S IW F S r es o urc e s
21.5_5.1( 5)
S ig na ls to /fr o m t he le f t ar e to /f rom th e SI W F S c all h an dlin g pro c es s ; s ign al s to /fro m the ri gh t ar e to /fr o m the V M S C
Id le
R e c eive _ O pe n_ in d
S e c tio n 25 .1
OK
E rr o r , Vr
W ait_ F or_ S e rv ic e _ ind ic ati on
Id le
M A P _P _ A B O R T _in d
M A P _P R O V ID E _ S IW F S _N U M B E R _ req
M AP _ N O T IC E _ in d
Id le
S en d _ P ro vi de _ S IW F S _ N u m be r
M AP_ C LO S E _r e q
I dle W a it _F o r_ C a ll _ H a nd ling _ R e s po n s e
S en d _P ro vid e_ S IW F S _N um b er _ ack
S en d_ P ro vi de _ S IW F S _N um be r ne g ativ e re s po n s e
S e t re su lt
S et er ro r
M A P _P R O V ID E _ S IW F S _N U M B E R _ rs p M A P _ D E L IM IT E R _re q
M A P _P R O V ID E _ S IW F S _N U M B E R _ rs p M A P _C LO S E _ re q
W ait_ F or_ M o di fic at io n
Id le
3613
3614
Figure 21.5/5 (sheet 1 of 5): Process SRA_SIWFS
1956
1957
Process SR A_SIW FS
F ig u re 2 1.5 /5 : P r oc es s in the S IW F S fo r ad m in is tra tion of S IW F S re s o urc e s
21.5_5.2(5)
S ig na ls to/ fro m th e le f t are to /f ro m th e SI W F S c all h and lin g pro c es s ; s ign als to /fro m the righ t are to /fr o m the V M S C
W a it _F o r_ M od if ic a tion
A bo rt
C all re le a se d
M A P _U _ AB O R T _ in d, M A P _P _ AB O R T _ in d , M A P _C L O SE _ in d
M AP_ N O T IC E _ in d
Idle
MA P _ C L O S E _re q
M AP_ C L O S E _re q
I dle
Id le
3615
3616
Figure 21.5/5 (sheet 2 of 5): Process SRA_SIWFS
1958
1959
Process SR A_SIW FS
F ig u re 2 1.5 /5 : P r oc es s in the S IW F S fo r ad m in is tra tion of S IW F S re s o urc e s
21.5_5.3(5)
S ig na ls to/ fro m th e le f t are to /f ro m th e SI W F S c all h and lin g pro c es s ; s ign als to /fro m the righ t are to /fr o m the V M S C
W a ir_F o r_ M od if ic a tion
M A P _S IW F S _ S IG N AL LI N G _ M O D IF Y_ in d
S en d_ S IW F S _ S ig na lling _ M od if y
W a it_ F or_ C a ll_H an dling _ M o dific at io n_ R e s po n s e
S en d _S IW F S _ S igna lling _ M od if y_ a ck
S end _ S IW F S _ S ig na lling _M o dify ne ga tiv e r epo n s e
S e t re su lt
S et error
M A P _S IW F S _S IG N A L LIN G _ M O D IF Y_ rs p M A P _D EL IM IT ER _re q
W a it _F o r_ M od if ic a tion
3617
3618
Figure 21.5/5 (sheet 3 of 5): Process SRA_SIWFS
1960
1961
Process SR A_SIW FS
F ig u re 2 1.5 /5 : P r oc es s in the S IW F S fo r ad m in is tra tion W a it _F o r_ of S IW F S re s o urc e s M od if ic a tion
21.5_5.4(5)
S ig na ls to/ fro m th e le f t are to /f ro m th e SI W F S c all h and lin g pro c es s ; s ign als to /fro m the righ t are to /fr o m the V M S C
S en d_ S IW F S _ S ig na lling _ M od if y
M A P _S IW F S _ S IG N AL LI N G _ M O D IF Y_ in d M A P _D EL IM IT ER _re q
W ait_ F or _ V MS C _ R e s po ns e
M A P _S IW F S _S I G N A L LIN G _ M O D IF Y_ c nf
C h ec k _ C o nfir m at io n
S e c tio n 25 .2
OK
P ro v id er E rror , U s er E rror , D a ta E rro r
S en d_ S IW F S _ S ig na lling _ M od if y_ a ck
S e nd _ SI W F S _ S ign a llin g _M od if y n eg a tiv e res p o ns e
W a it _F o r_ M od if ic a tion
W a it_ F o r_ Mo d ific a tio n
3619
3620
Figure 21.5/5 (sheet 4 of 5): Process SRA_SIWFS
1962
1963
Process SR A_SIW FS
F ig u re 2 1.5 /5 : P r oc es s in the S IW F S fo r ad m in is tra tion of S IW F S re s o urc e s
21.5_5.5(5)
S ig na ls to/ fro m th e le f t are to /f ro m th e SI W F S c all h and lin g pro c es s ; s ign als to /fro m the righ t are to /fr o m the V M S C
W a it_ F or_ V M S C _ R es p on s e
A bo rt
C all re le a se d
M A P _U _ AB O R T _ in d, M A P _P _ AB O R T _ in d , M A P _C L O SE _ in d
M AP_ N O T IC E _ in d
Idle
MA P _ C L O S E _r e q
M AP_ C L O S E _re q
I dle
S e t n eg a tiv e re s po n se : S y s te m F ailu re
S en d_ S IW F S _ S ig na lling _M o d ify ne g ativ e re s po n s e
Id le
3621
3622
Figure 21.5/5 (sheet 5 of 5): Process SRA_SIWFS
1964
1965
3623 3624
21.6 Setting of Reporting State
21.6.1 General
3625 The message flow for setting the reporting state in a stand-alone dialogue is shown in figure 21.6.1/1. 3626
VLR MAP_SET_REPORTING_STATE <--------------------------------------------------------------MAP_SET_REPORTING_STATE ack --------------------------------------------------------------->
HLR
3628
3627
Figure 21.6/1: Message Flow for Setting the Reporting State
3629 In Set Reporting State, the HLR can request a start or a stop of monitoring in the VLR.
3630
21.6.2 Process in the HLR for Set Reporting State stand-alone
3631 The MAP process in the HLR to set the reporting state in the VLR in a separate stand-alone dialogue is shown in 3632 figure 21.6/2. The MAP process invokes macros not defined in this clause; the definitions of these macros can be found 3633 as follows: 3634 3635
Receive_Open_Cnf Check_Confirmation
see clause 25.1.2; see clause 25.2.2.
3636 Successful Outcome 3637 3638 3639 3640 3641
When the MAP process receives a Start Reporting or Stop Reporting request from the CCBS application process in the HLR, it requests a dialogue with the VLR whose identity is contained in the request by sending a MAP_OPEN service request and sending the necessary information using a MAP_SET_REPORTING_STATE service request. The HLR then invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the VLR.
3642 If the MAP process receives a MAP_SET_REPORTING_STATE service confirm from the VLR, the MAP process 3643 invokes the macro Check_Confirmation to check the content of the confirm. 3644 If the macro Check_Confirmation takes the OK exit and the request was for Start Reporting, the MAP process sends a 3645 positive acknowledgement containing the information received from the VLR to the CCBS application process in the 3646 HLR and returns to the idle state. In the case of Stop Reporting the CCBS application process returns to the idle state. 3647 Failure of dialogue opening with the VLR 3648 If the macro Receive_Open_Cnf takes the Vr exit or the Error exit, the MAP process sends (in the case of Start 3649 Reporting) a negative response to the CCBS application process in the HLR and returns to the idle state. In the case of 3650 Stop Reporting the process returns to the idle state. 3651 Error in MAP_SET_REPORTING_STATE confirm 3652 3653 3654 3655
If the MAP_SET_REPORTING_STATE service confirm contains a user error or a provider error, or the macro Check_Confirmation indicates that there is a data error, the MAP process sends a negative response (in the case of Start Reporting) to the CCBS application process in the HLR and returns to the idle state. In the case of Stop Reporting the CCBS application process returns to the idle state.
3656 Abort of VLR dialogue
1966
1967
3657 After the dialogue with the VLR has been established, the MAP service provider may abort the dialogue by issuing a 3658 MAP_P_ABORT or a MAP_U_ABORT indication. If the request was for the Start Reporting, the MAP process sends a 3659 Start Reporting negative response to the CCBS application process in the HLR and returns to the idle state. 3660 3661 3662 3663
If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the dialogue with the VLR, sends a negative response (in the case of the Start Reporting) indicating system failure to the CCBS application process in the HLR and returns to the idle state. In the case of Stop Reporting the CCBS application process returns to the idle state.
1968
1969
Process Set_Reporting_State_HLR
F igu re 2 1.2/2: P r ocess in the HLR to set the re po rtin g state in the V LR in a sep arate dialogue Idle S ig n als to/from the l eft are to/from the V LR; signals to/f rom th e right ar e to/f rom the CC BS app lication process in the HL R S top R eporting
21.2_2(1)
Start Rep or ting
S et r eq uired r ep or ting state: S ta rt
S et requir ed reporting state: S top
MAP _ OPEN _r eq , M AP _ SET_REP ORTIN G_S TATE _req , MAP _ DE LIM ITER_ req
R eceive_ Open_ Cnf
See sectio n 2 5.1
OK W ait_ For_ V L R_Response No
V r, Erro r Requ ired r epor ting st ate=S tar t? Y es
M AP _SE T_ R EPO R TIN G _ S TATE _cnf
M AP_ CLOSE_ind, M AP_ P_ ABORT_ ind, M AP_ U_AB OR T_ind
MA P _N OTICE_ in d
S tart R eportin g Negati ve re sp on se
Ch eck _ Co nf irm atio n
See section 25.2
MA P _CLOSE _ re q Idle No
D ata err or , P rovider e rr or, User e rror OK No Req uired r eporting state=S tart? Y es S tart R eporting A ck R equired repo rting state=S tar t? Yes S tar t Repor tin g N eg ative r espon se
Idl e
3664
3665
Figure 21.6/2: Process Set_Reporting_State_HLR
1970
1971
3666
21.6.3 Reporting co-ordinator process in the VLR
3667 The MAP co-ordinating process in the VLR to handle a dialogue opened with the reporting application context is shown 3668 in figure 21.6/3. The MAP process invokes a macro not defined in this clause; the definition of this macro can be found 3669 as follows: 3670 3671 3672 3673 3674 3675
Receive_Open_Ind
see clause 25.1.1.
Any reporting process in the VLR starts by the VLR receiving a MAP-OPEN service indication. If that service is successful, the VLR can handle reporting indications from the HLR. Table 21.6/1 shows the co-ordinating process' reaction on receipt of specific reporting indications from the HLR. After the relevant process is invoked, the received service indication is sent to that process. Table 21.6/1: Relationship between received service indication and invoked process in the VLR
Service indication received MAP_REMOTE_USER_FREE_ind MAP_SET_REPORTING_STATE_ind Process invoked REMOTE_USER_FREE_VLR SET_REPORTING_STATE_VLR
3676 3677 After creation of the user process the co-ordinator relays the messages between the MAP protocol machine and the 3678 invoked process until a request or an indication for dialogue termination is received.
1972
1973
Process Reporting_Coord_VLR
F igure 21.6/3: Coord inating process in the VLR to handle a dialogue opened w ith the AC Repor tingC ontext Idle
21.6_3(1)
Signals to/fr om the left are to/f rom the HLR via th e M AP provider; signals to/f rom the r ight are to/f rom the child pr ocess
R ece ive_ Open_Ind
Section 2 5.1
W ait_For_ Service_Indication
Id le
M AP_R EM OTE_ U SER_F REE_ind
M AP_SET_ R EPORTIN G_ STATE_ind
MAP_N OTICE_ in d
M AP_ C LO SE_ind, M AP_ P_ABOR T_ind, M AP_ U _ABORT_ind
Remote_User_ Free_VLR
Set_R eporting_ State_VLR
M AP_C LOSE_ r eq
M AP_REM O TE_ USER_FR EE_ind
MAP_SET_ REPOR TING_ STATE_ind
Idle
Relay_ In form ation
M AP_C LOSE_ind, M AP_P_ABOR T_ind, M AP_U _ABORT_ind
MAP_C LOSE_in d, MAP_U_ABORT _ind
Idle
Relay_ in formation
Idle
Relay_ inform ation
3679
3680
Figure 21.6/3: Process Reporting_Coord_VLR
1974
1975
3681
21.6.4 Process in the VLR to set the reporting state
3682 The MAP process in the VLR to set the reporting state is shown in figure 21.6/4. 3683 The co-ordinator opens the process. The macro Receive_Set_Reporting_State_VLR handles the receipt of the request 3684 from the HLR, and the possible response from the CCBS application process in the VLR. When the macro exits, a MAP 3685 CLOSE is sent to the HLR and the process terminates. 3686 The macro Set_Reporting_State_VLR is defined in figure 21.6/5. 3687 When the VLR receives a MAP_SET_REPORTING_STATE service indication, it checks whether the required 3688 monitoring state is stopped. 3689 If the required monitoring state is stopped, the MAP process sends a Stop Reporting message to the CCBS application 3690 in the VLR, sends a MAP_SET_REPORTING_STATE response to the HLR and exits from the macro. 3691 If the required monitoring state is started, the MAP process sends a Start Reporting message to the CCBS application in 3692 the VLR and waits for a response. 3693 If the CCBS application sends a Start Reporting ack, the MAP process sends a MAP_SET_REPORTING_STATE 3694 response to the HLR and exits from the macro. 3695 If the CCBS application sends a Start Reporting negative response, the MAP process translates the negative response 3696 into a MAP user error, sends a MAP_SET_REPORTING_STATE response to the HLR and exits from the macro.
1976
1977
Pro ce s s S et_ Re p or tin g _ S ta te_ VL R
F ig u re 2 1.6 / 4: P r o c es s in th e V L R to h an d le a req u es t fro m th e H L R to s et th e rep ortin g s ta te f or a s ub s c rib er
2 1 .6 _ 4 (1 )
S ig na ls to /fr o m th e rig ht ar e to /from th e H L R
Id le
R ec e ive _ S et_ R ep o rtin g_ S ta te_ VLR
M A P _ C LO S E _ r eq
3697
3698
Figure 21.6/4: Process Set_Reporting_State_VLR
1978
1979
M a cro d e fin itio n Re ce ive _ S et_R e p or tin g_ S ta te _ VL R
F ig u re 2 1.6 / 5: M ac r o in the V L R to h an dle a S et R e po r ting S ta te in s tru c t ion f ro m t he H L R
2 1 .6 _ 5 (1 )
S ig n als to /fro m th e lef t are to / fr om th e C C B S ap p lic at io n pr o c es s in th e V LR ; s ign a ls to /fr o m th e righ t are to /fr om th e H LR
M AP _ S E T _ R E P O R T IN G _ S T A T E _ in d
Yes
R eq uire m o nito ring s tate = S ta rt?
No
S t art R e po r tin g
S to p R ep or t ing
W A it _F or_ A p p lic a t io n_ R es po n s e
S ta rt R ep o rt in g Ack
S ta rt R epo r ting N e ga tiv e res po n s e
S e t U s er E r ro r
M AP _ S E T _ R E P O R T IN G _ S T A T E _ rsp
3699
3700
Figure 21.6/5: Macro Receive_Set_Reporting_State_VLR
1980
1981
3701 3702
21.7 Status Reporting
21.7.1 General
3703 The message flows for reporting the status of a subscriber are shown in figures 21.7/1 and 21.7/2. 3704
VLR MAP_STATUS_REPORT ---------------------------------------------------------------> MAP_STATUS_REPORT ack <---------------------------------------------------------------
HLR
3705 3706 3707
Figure 21.7/1: Status reporting, when monitoring continues in the VLR
VLR MAP_STATUS_REPORT ---------------------------------------------------------------> MAP_STATUS_REPORT ack <--------------------------------------------------------------MAP_SET_REPORTING_STATE <--------------------------------------------------------------MAP_SET_REPORTING_STATE ack --------------------------------------------------------------->
HLR
3708 3709
Figure 21.7/2: Status reporting, when monitoring stops
3710 When the HLR sends a MAP_SET_REPORTING_STATE, it requests the stop of monitoring in the VLR.
3711
21.7.2 Process in the VLR for Status Reporting
3712 The MAP process in the VLR to send a status report to the HLR is shown in figure 21.7/3. The MAP process invokes 3713 macros not defined in this clause; the definitions of these macros can be found as follows:
1982
1983
3714 3715
Receive_Open_Cnf Check_Confirmation
see clause 25.1.2; see clause 25.2.2.
3716 Successful Outcome 3717 3718 3719 3720 3721
When the MAP process receives a Event Report or CCBS Call Report from the CCBS application process in the VLR, it requests a dialogue with the HLR whose identity is contained in the request by sending a MAP_OPEN service request, and requests status report using a MAP_STATUS_REPORT service request. The VLR then invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the HLR.
3722 If the MAP process receives a MAP_STATUS_REPORT service confirm from the HLR, the MAP process invokes the 3723 macro Check_Confirmation to check the content of the confirm. 3724 If the macro Check_Confirmation takes the OK exit, the MAP process sends an Event Report ack or a CCBS Call 3725 Report ack containing the information received from the HLR to the CCBS application process in the VLR and waits 3726 for a possible instruction from the HLR to set the reporting state. 3727 If the HLR requests the VLR to set a reporting state (in the macro Receive_Set_Reporting_State_VLR), the VLR closes 3728 the dialogue with the HLR by sending a MAP CLOSE to the HLR. 3729 If the HLR requires monitoring in the VLR to continue, it closes the dialogue by sending a MAP_CLOSE, and the MAP 3730 process in the VLR sends Continue Monitoring message to the CCBS application process in the VLR and returns to the 3731 idle state. 3732 Failure of dialogue opening with the HLR 3733 If the macro Receive_Open_Cnf takes the Vr exit or the Error exit, the MAP process sends a Event Report negative 3734 response or CCBS Call Report negative response to the CCBS application process in the VLR and returns to the idle 3735 state. 3736 Error in MAP_STATUS_REPORT confirm 3737 If the MAP_STATUS_REPORT service confirm contains a user error or a provider error, or the macro 3738 Check_Confirmation indicates that there is a data error, the MAP process sends an Event Report negative response or 3739 CCBS Call Report negative response to the CCBS application process in the VLR and returns to the idle state. 3740 Abort of HLR dialogue in State Wait_For_HLR_Response 3741 After the dialogue with the HLR has been established, the MAP service provider may abort the dialogue by issuing a 3742 MAP_P_ABORT or a MAP_U_ABORT indication. In this case, the MAP process sends a Event Report or CCBS Call 3743 Report negative response to the CCBS application process in the VLR and returns to the idle state. 3744 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 3745 dialogue with the HLR. The VLR sends an Event Report negative response or CCBS Call Report negative response 3746 indicating system failure to the CCBS application process in the VLR and returns to the idle state. 3747 Abort of HLR dialogue in State Wait_For_Set_Reporting 3748 After the dialogue with the HLR has been established, the MAP service provider may abort the dialogue by issuing a 3749 MAP_P_ABORT or a MAP_U_ABORT indication. In this case, the VLR returns to the idle state. 3750 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 3751 dialogue with the HLR and returns to the idle state.
1984
1985
Process Send_Status_Report_VLR
F igu re 2 1.7/3: P r ocess in the VL R to se nd a statu s r epo r t to the HLR
21.7_3.1(2)
Sign als to/from th e l eft ar e to/f rom the CC BS app lication process in th e VLR; signals to/f rom th e right ar e to/fro m the HL R
Idl e
E ve nt R eport
C CB S C all Report
Build MAP m essage
B uild M AP me ssage
Inc lude call r eport data
MA P_ O PEN _req, M AP_ S TAT US_REPO R T_r eq, MA P_ DELIMITE R_req R eceive_ Open_ Cnf
S ee sectio n 25.1
OK W ait_ For_ H LR _R esp on se
Vr, Error
MAP _STA TUS _ REP ORT_ cnf
M A P_C LOS E _ind, M A P_P_ AB OR T_ind, M A P_U _A BO RT_ ind
M AP_ NOTICE _ ind
Check _ Conf irm atio n
See section 25.2
M AP_ CLOS E_ req
OK Yes
Data er ror, P rovider er ror, U ser error Yes No CC BS call report da ta pres ent No
CC BS cal l re po rt da ta pr ese nt
CC BS C all Repor t ack
Event Rep ort ack
CCBS Call Rep ort Neg ative respo ns e
E ven t Re port Ne gative r esp on se
W ait_ For_ S et _Re po r ting _ S tate
Idle
3752
3753
Figure 21.7/3 (sheet 1 of 2): Process Send_Status_Report_VLR
1986
1987
Process Send_Status_Report_VLR
F igu re 21.7/3: Pr ocess in the VLR to send a status r epor t to the HLR W ait_F or_ Set_Reporting_ State
21.7_3.2(2)
Signals to/from the right are to/ from the HLR
Receive_Set_ Repor tin g_ State_ VLR
M AP_N OTICE_ ind
M AP_CLOSE_ind, M AP_P_ABORT_ind, M AP_U_ABOR T_ind
M AP_CLOSE_ req
M AP_C LOSE_ r eq
Idle
Idle
Idle
3754
3755
Figure 21.7/3 (sheet 2 of 2): Process Send_Status_Report_VLR
1988
1989
3756
21.7.3 Process in the HLR for Status Reporting
3757 The MAP process in the HLR to handle a status report is shown in figure 21.7/4. The MAP process invokes macros not 3758 defined in this clause; the definitions of these macros can be found as follows: 3759 3760
Receive_Open_Ind Check_Confirmation
see clause 25.1.1; see clause 25.2.2.
3761 Successful outcome 3762 When the MAP process receives a MAP_OPEN indication with the application context reporting, it checks it by 3763 invoking the macro Receive_Open_Ind. 3764 If the macro takes the OK exit, the MAP process waits for a service indication. 3765 The MAP process invokes the macro Receive_Status_Report_HLR to handle a MAP_STATUS_REPORT service 3766 indication; this macro is defined in figure 21.7/5. The MAP process then waits for a response from the CCBS 3767 application in the HLR. 3768 If the MAP process receives a Stop Reporting message from the CCBS process, it sets the required monitoring state to 3769 stop, and may send a MAP_DELIMITER service request to the VLR. The HLR then invokes the macro 3770 Set_Reporting_State_HLR. After exiting the macro, the MAP process returns to the idle state. 3771 If the MAP process receives a Continue Reporting from the CCBS process, it sends a MAP CLOSE Request to VLR 3772 and returns to the idle state. 3773 Failure of dialogue opening with the VLR 3774 If the macro Receive_Open_Ind takes the Vr exit or the Error exit, the MAP process returns to the idle state. 3775 Abort of VLR dialogue in State Wait_For_Service_Indication 3776 After the dialogue with the HLR has been established, the MAP service provider may abort the dialogue by issuing a 3777 MAP_P_ABORT indication. In this case, the MAP process returns to the idle state. 3778 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 3779 dialogue with the VLR and returns to the idle state. 3780 Macro Receive_Status_Report_HLR 3781 The macro Receive_Status_Report_HLR is shown in figure 21.7/5. 3782 When a MAP_STATUS_REPORT service indication is received, the HLR checks whether call report data are present. 3783 If call report data are present, the MAP process sends a CCBS Call Report message to the CCBS application process in 3784 the HLR and waits for a response; otherwise it sends an Event Report message to the CCBS application process in the 3785 HLR and waits for a response. 3786 If the MAP process receives a CCBS Call Report ack or Event Report ack from the CCBS application process in the 3787 HLR, it sends a MAP_STATUS_REPORT service confirm to the VLR and exits from the macro. 3788 If the MAP process receives a CCBS Call Report negative response or Event Report negative response from the CCBS 3789 application process in the HLR, it sets the User Error according to the negative response, sends a 3790 MAP_STATUS_REPORT service confirm to the VLR and exits from the macro. 3791 Macro Set_Reporting_State_HLR 3792 The macro Set_Reporting_State_HLR is shown in figure 21.7/6. 3793 The MAP process in the HLR sends a MAP_SET_REPORTING_STATE service request to the VLR and waits for a 3794 response. 3795 If the MAP process receives a MAP_SET_REPORTING_STATE service confirm from the VLR, it invokes the macro 3796 Check_Confirmation to check the content of the confirm.
1990
1991
3797 If the macro Check_Confirmation takes the OK exit, the macro Set_Reporting_State_HLR takes the OK exit. 3798 If the macro Check_Confirmation takes the Data error, Provider error or User error exit, the macro 3799 Set_Reporting_State_HLR takes the Error exit. 3800 While the MAP process is waiting for a response from the VLR, the MAP provider may terminate the dialogue by 3801 sending a MAP_CLOSE, MAP_P_ABORT or MAP_U_ABORT. In this case the macro takes the Aborted exit. 3802 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 3803 dialogue with the VLR and the macro takes the Aborted exit.
1992
1993
Process Status_Report_HLR
Process in the HLR to handle a status r eport 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 process in the HLR
Idle
Receive_ Open_Ind
Section 25.1
OK Wait_For_ Service_ Indication Idle
Vr, Error
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 monitoring state= Stop
Idle
MAP_DELIMITER _req
Sending of MAP_DELIMITER_req is implementation option
Set_Reporting_ State_HLR
Idle
3804
3805
Figure 21.7/4: Process Status Report_HLR
1994
1995
Macrodefinition Receive_Status_Report_HLR
F igure 21.7/5: Mac ro in the HLR to receive a status report from the VLR
21.7_5(1)
Signals to'from the left are to/from the VLR; signals to/from the right are to/f rom the CC BS application proc ess in the HLR
MAP_STATUS_ REPORT_ind
Yes
CC BS call report pres ent?
No
C CBS Call R eport
Event Report
W ait_F or_ Application_ Respons e
CC BS C all Report Ack
CCBS Call Report Negative respons e
Event R eport Ack
Event Report Negative respons e
Set U ser Error
Set U ser Error
MAP_STATUS_ REPORT_rs p
3806
3807
Figure 21.7/5: Macro Receive_Status_Report_HLR
1996
1997
Ma cr o de finitio n Se t_ Re p o r tin g _Sta te _H L R
F ig u re 2 1.7 /6 : M ac r o in th e H L R to in s tru c t th e V L R to se t th e re p o rting s ta te fo r a su b s c ribe r
2 1 .7 _ 6 (1 )
S ig na ls to /fr o m th e left ar e t o / fro m the V L R
M A P _ S E T _ R E P O R T IN G _ S T A T E _ req , M A P _ D E L IM IT E R _r e q
W a it_ F o r _ V L R _ R es p o n se
M A P _ S E T_ R E P O R T IN G _ S TA TE _ cn f
M A P _ C L O S E _ in d , M A P _N O T IC E _ M A P _ P _A B O R T _ in d , ind M A P _ U _ A B O R T _in d
C h ec k _ C o n fir m a tio n
S ec tio n 2 5 .2
M A P _C L O S E _ r eq
OK OK
U s e r erro r, P r ov id er e rro r, D at a e rr o r E r ro r A b orte d
3808
3809
Figure 21.7/6: Macro Set_Reporting_State_HLR
1998
1999
3810 3811
21.8 Remote User Free
21.8.1 General
3812 The message flows for handling remote user free are shown in figures 21.8/1 and 21.8/2. 3813
VLR MAP_REMOTE_USER_FREE <--------------------------------------------------------------MAP_REMOTE_USER_FREE ack --------------------------------------------------------------->
HLR
3814 3815 3816
Figure 21.8/1: Remote User Free: recall not accepted
VLR MAP_REMOTE_USER_FREE <--------------------------------------------------------------MAP_REMOTE_USER_FREE ack ---------------------------------------------------------------> MAP_STATUS_REPORT ---------------------------------------------------------------> MAP_STATUS_REPORT ack <---------------------------------------------------------------
HLR
3817 3818
Figure 21.8/2: Remote User Free: recall accepted
3819
21.8.2 Process in the HLR for Remote User Free
3820 The MAP process in the HLR to handle Remote User Free is shown in figure 21.8/3. The MAP process invokes macros 3821 not defined in this clause; the definitions of these macros can be found as follows: 3822
Receive_Open_Cnf
see clause 25.1.2;
2000
2001
3823
Check_Confirmation
see clause 25.2.2.
3824 Successful Outcome 3825 3826 3827 3828 3829
When the MAP process receives a CCBS RUF request from the CCBS application process in the HLR, it requests a dialogue with the VLR whose identity is contained in the request by sending a MAP_OPEN service request and sending the necessary information using a MAP_REMOTE_USER_FREE service request. The HLR then invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the VLR.
3830 If the MAP process receives a MAP_REMOTE_USER_FREE service confirm from the VLR, the MAP process 3831 invokes the macro Check_Confirmation to check the content of the confirm. 3832 3833 3834 3835 3836 3837 3838
If the macro Check_Confirmation takes the OK exit, the MAP process sends a CCBS RUF ack containing the information received from the VLR to the CCBS application process in the HLR and waits for a MAP_STATUS_REPORT service indication from the VLR. If in this state a MAP_CLOSE service indication is received, the MAP process returns to the idle state. If in this state a MAP_STATUS_REPORT service indication is received, further processing is described by the macro Receive_Status_Report_HLR (described in clause 21.7.3). When the macro exits, the MAP process constructs a MAP_CLOSE service request, sends it to the VLR and returns to the idle state.
3839 Failure of dialogue opening with the VLR 3840 If the macro Receive_Open_Cnf takes the Vr exit or the Error exit, the MAP process sends a negative response to the 3841 CCBS application process in the HLR and returns to the idle state. 3842 Error in MAP_REMOTE_USER_FREE confirm 3843 If the MAP_REMOTE_USER_FREE service confirm contains a user error or a provider error, or the macro 3844 Check_Confirmation indicates that there is a data error, the MAP process sends a CCBS RUF negative response to the 3845 CCBS application process in the HLR and returns to the idle state. 3846 Abort of VLR dialogue 3847 3848 3849 3850 3851 3852 3853 3854
When the MAP process is waiting for a VLR response to the MAP_REMOTE_USER_FREE, the MAP service provider may abort the dialogue by issuing a MAP_CLOSE, a MAP_P_ABORT or a MAP_U_ABORT indication. In this case, the MAP process sends a CCBS RUF negative response to the CCBS application process in the HLR and returns to the idle state. If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication when the MAP process is waiting for a VLR response to the MAP_REMOTE_USER_FREE, the MAP process closes the dialogue with the VLR, sends a CCBS RUF negative response indicating system failure to the CCBS application process in the HLR and returns to the idle state.
3855 When the MAP process is waiting for a possible MAP_STATUS_REPORT from the VLR, the MAP service provider 3856 may abort the dialogue by issuing a MAP_P_ABORT or a MAP_U_ABORT indication. In this case, the MAP process 3857 returns to the idle state. 3858 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication when the MAP process is 3859 waiting for a possible MAP_STATUS_REPORT from the VLR, the MAP process closes the dialogue with the VLR 3860 and returns to the idle state. 3861 If the CCBS application in the HLR decides to abort the dialogue, it sends an Abort message to the MAP process, 3862 which closes the dialogue with the VLR and returns to the idle state.
2002
2003
Process Remote_User_Free_HLR
F igure 21.8/3: Pr ocess in the HLR to handle a R em ote U ser Fr ee notific ation to the VLR Idle
21.8_3(1)
Signals to/from the left are to/from the VL R; signals to/f rom the r ight ar e to/f rom the CC BS application proc ess in the HLR
C CBS R UF
MAP_O PEN _req, M AP_REM OTE_U SER_ F REE_r eq, MAP_DELIMITER_req R eceive_ Open_Cnf OK
Section 25.1 Vr, Error
W ait_F or_ VLR _Respons e
CCBS RU F Negative respons e
M AP_R EM OTE_ U SER _F REE_ cnf
M AP_CLO SE_ind, M AP_P_ABORT_ind, M AP_U_ABOR T_ind
M AP_N OTICE_ ind
Idle
Check _ Conf ir matio n
Section 21.2 Pro vider error, Us er er ror, Da ta error C CBS RUF N egative response
M AP_CLOSE_ req
OK CC BS R UF Ack
W ait_F or_ Status_Report
Idle
M AP_C LOSE_ind, M AP_P_ABOR T_ind, M AP_U _ABORT_ind
M AP_NOTICE_ ind
R eceive_ Status_ R eport _HLR
Abor t
M AP_CLO SE_ req
Idle
Idle
3863
3864
Figure 21.8/3: Process Remote_User_Free_HLR
2004
2005
3865
21.8.3 Process in the VLR for Remote User Free
3866 The MAP process in the VLR to handle Remote User Free is shown in figure 21.8/4. The MAP process invokes a 3867 macro not defined in this clause; the definitions of this macro can be found as follows: 3868
Check_Confirmation
see clause 25.2.2.
3869 Successful outcome (Recall accepted) 3870 When the MAP process receives a MAP_REMOTE_USER_FREE service indication, the VLR sends a CCBS RUF 3871 request to the CCBS application process in the VLR, and waits for a response. The request contains the parameters 3872 received in the MAP_REMOTE_USER_FREE service indication. 3873 3874 3875 3876 3877 3878 3879 3880
If the CCBS application process in the VLR returns a positive response indicating "recall accepted, the MAP process constructs a MAP_REMOTE_USER_FREE service response and a MAP_DELIMITER service request, sends them to the VLR and waits for a CCBS Call Report message from the CCBS application process in the VLR. When the MAP process receives the CCBS Call Report from the CCBS application process in the VLR, it constructs a MAP_STATUS_REPORT service request and a MAP_DELIMITER service request, sends them to the HLR and waits for a response. If the MAP process receives a MAP_STATUS_REPORT service confirm, the VLR calls the macro Check_Confirmation. If this macro takes the OK exit, the MAP process sends a CCBS Call Report ack to the CCBS application process in the VLR and the MAP process terminates.
3881 Successful outcome (Recall not accepted) 3882 If the CCBS application process in the VLR returns a positive response indicating "recall not accepted, the MAP 3883 process constructs a MAP_REMOTE_USER_FREE service response and a MAP_CLOSE service request, sends them 3884 to the HLR and terminates. 3885 Negative response from VLR CCBS application process 3886 If the CCBS application process in the VLR returns a negative response, the MAP process constructs a 3887 MAP_REMOTE_USER_FREE service response containing the appropriate error and a MAP_CLOSE service request, 3888 sends them to the HLR and terminates. 3889 Failure of dialogue with the HLR 3890 When waiting for a response or a call result from the CCBS application process in the VLR, the MAP process may 3891 receive a MAP_CLOSE service indication, a MAP_U_ABORT service indication or a MAP_P_ABORT service 3892 indication from the co-ordinating process, in which case the MAP process terminates. 3893 When waiting for a call result from the CCBS application process in the VLR, the MAP process may receive a 3894 MAP_NOTICE indication from the co-ordinating process, in which case the MAP process constructs a MAP_CLOSE 3895 service request, sends it to the co-ordinating process and terminates. 3896 When waiting for a response from the HLR, the MAP process may receive a MAP_CLOSE indication, a 3897 MAP_U_ABORT indication or a MAP_P_ABORT indication from the co-ordinating process, in which case the MAP 3898 process sends a CCBS Call Report negative response to the CCBS application process in the VLR and terminates. 3899 3900 3901 3902
When waiting for a response from the HLR, the MAP process may receive a MAP_NOTICE indication from the co-ordinating process, in which case the MAP process constructs a MAP_CLOSE service request, sends it to the co-ordinating process, sends a CCBS Call Report negative response to the CCBS application process in the VLR and terminates.
3903 Error in MAP_STATUS_REPORT confirm 3904 If the MAP_STATUS_REPORT service confirm contains a user error or a provider error, the MAP process sends a 3905 CCBS Call Report negative response to the CCBS application process in the VLR and terminates.
2006
2007
Process Remote_User_Free_VLR
Figure 21.8/4: Process in the VLR to handle a R emote User Free notific ation
21.8_4.1(2)
Signals to/from the left are to/from the CC BS application process in the VLR; signals to/f rom the right are to/from the HLR via the cordinating process
Idle
MAP_R EMOTE_ U SER_FREE_ind
CC BS RU F
Wait_F or_ Application_ Respons e
C CBS R UF Ack (Rec all accepted)
C CBS R UF Ack (R ecall uns ucc essf ul)
CCBS RUF Negative respons e
MAP_C LOSE_ind, MAP_P_ABOR T_ind, MAP_U_ABORT_ in d
Set U ser Error
MAP_REMOTE_USER_FR EE_rsp, MAP_D ELIMITER _req
MAP_REMOTE_U SER_FR EE_rsp, MAP_CLOSE_req
W ait_For_ C all_Report
3906
3907
Figure 21.8/4 (sheet 1 of 2): Process Remote_User_Free_VLR
2008
2009
Process Remote_User_Free_VLR
Figur e 21.8/4: P rocess in the VLR to h andle a R em ote User Free notific ation W a it_F or_ Call_Report
21.8_4.2(2)
C CB S C all Re port
M AP _ N OTICE_ ind
M A P_CLOS E_ind, M A P_P_AB ORT_ind, M A P_U_A BORT_ind
S ignals to/from the left are to/from the CC BS application process in th e VLR; signals to /f rom th e right are to/from the HLR via the co rdin ating process
M AP_ST ATU S_ R EP ORT_ req, MA P_DEL IM ITE R_re q
M A P_ C LOS E _ r eq
W a it_F or _ HLR_Respons e
MA P_STA TU S_ REP ORT_ cn f
M AP _ N OTICE_ ind
M A P_CLOS E_ind, M A P_P_AB ORT_ind, M A P_U_A BORT_ind
Check _ Conf irm atio n
Sectio n 2 5.2
M A P_ C LOS E _ r eq
OK CC BS Call Report A ck
Provider error , Us er err or, Data err or
CC BS Call Rep or t Negati ve respo ns e
3908
3909
Figure 21.8/4 (sheet 2 of 2): Process Remote_User_Free_VLR
2010
2011
3910 3911
21.9 IST Alert
21.9.1 General
3912 The Immediate Service Termination Alert procedure is used to keep track of the call activities performed by IST 3913 subscribers and, eventually, to terminate the alerted call activities, or all the call activities related to the alerted 3914 subscriber. 3915 The message flow for alerting and terminating the call(s) is shown in figure 21.9/1, where the MSC may be a Visited 3916 MSC or a Gateway MSC.
3917 3918 3919 3920 3921 3922 3923 3924 3925 3926 3927 3928
+-----+ C +-----+ MSC +------------+------------ HLR +-----+ +-----+ IST_ALERT ------------------------------> IST_ALERT ack <------------------------------ Figure 21.9/1: IST Alert
3929
3930 21.9.2
Procedure in the MSC
3931 The MAP process in the MSC (Visited MSC or Gateway MSC) is shown in figure 21.9/2. The MAP process invokes 3932 macros not defined in this clause; the definitions of these macros can be found as follows: 3933 3934
Receive_Open_Cnf Check_Confirmation
see clause 25.1.2; see clause 25.2.2.
3935 Successful Outcome 3936 3937 3938 3939 3940
When the MAP process receives an IST Alert request from a call handling process in the Visited MSC or Gateway MSC, it requests a dialogue with the HLR that the subscriber belongs to, by sending a MAP_OPEN service request, a MAP_IST_ALERT service request, and a MAP_DELIMITER service request. The MSC then invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the HLR.
3941 If the MAP process receives a MAP_IST_ALERT service confirm from the HLR, the MAP process invokes the macro 3942 Check_Confirmation to check the content of the confirm. 3943 If the macro Check_Confirmation takes the OK exit, the MAP process sends a IST Alert ack containing the information 3944 received from the HLR to the call handling process in the MSC and returns to the idle state. 3945 Failure of dialogue opening with the HLR 3946 If the macro Receive_Open_Cnf takes the Vr exit or the Error exit, the MAP process sends a negative response to the 3947 call handling process in the MSC, and returns to the idle state. 3948 Error in MAP_IST_ALERT confirm 3949 If the MAP_IST_ALERT service confirm contains a user error or a provider error, or the macro Check_Confirmation 3950 indicates that there is a data error, the MAP process sends a negative response to the call handling process in the MSC, 3951 and returns to the idle state. 3952 Abort of HLR dialogue 3953 When the MAP process is waiting for an HLR response to the MAP_ IST_ALERT, the MAP service provider may 3954 abort the dialogue by issuing a MAP_CLOSE, a MAP_P_ABORT or a MAP_U_ABORT indication. In this case, the 3955 MAP process sends a negative response to the call handling process in the MSC, and returns to the idle state.
2012
2013
3956 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication when the MAP process is 3957 waiting for an HLR response to the MAP_ IST_ALERT, the MAP process closes the dialogue with the HLR, sends a 3958 negative response to the call handling process in the MSC, and returns to the idle state.
P rocess IS T_A lert_M C S 21.9_3(1)
S igna to mth left ls /fro e a to re /from th H ; e LR sign to/fro the rig als m ht a to re /from th call ha e ndlin g P roce in the M C ss S
Figu 21 : P re .9/3 rocess in the M C S to h le an IS and T A to the H lert LR Id le
IS A R T LE T
M P O E _ q, A _ P N re M P T_ LE T_re A _IS A R q, M P DE ITE _req A _ LIM R
R iv ece e_ O _C pen nf O K
S ectio 2 n 5.1
V E r r, rro IS A E T T L R Ng e e ativ respon se
W it_F a or_ H _R LR espon se
Id le M P T_ A _IS A R cnf LE T_ M P LO E d, A _C S _in M P _A O T_ind, A _P B R M P _A O T_ A _U B R ind MP O A _N TICE _ ind
C ck_ he C firm n on atio O K IS A R T LE T A ck
S ection 25 .2
M P LO E A _C S _ req
P id error, rov er U r error, se D ta erro a r
IS A R T LE T N gativ e e resp onse
Id le
Idle
3959
3960
Figure 21.9/2: Process IST_Alert_MSC
2014
2015
3961 21.9.3
Procedure in the HLR
3962 The MAP process in the HLR is shown in figure 21.9/3. The MAP process invokes a macro not defined in this clause; 3963 the definition of this macro can be found as follows: 3964
Receive_Open_Ind
see clause 25.1.1;
3965 Successful outcome 3966 When the MAP process in the HLR receives a request to open a dialogue, it invokes the macro Receive_Open_Ind to 3967 check if the dialogue can be opened. 3968 If the dialogue can be opened, and the service indication received is a MAP_IST_ALERT, the HLR then sends the IST 3969 alert indication to the call handling process in the HLR, and waits for a response. 3970 If the call handling process in the HLR returns a positive response, the MAP process constructs a MAP_ IST_ALERT 3971 service response and a MAP_CLOSE service request, sends them to the MSC, and returns to the idle state. 3972 Negative response from HLR call handling process 3973 If the call handling process in the HLR returns a negative response, the MAP process constructs a MAP_IST_ALERT 3974 service response containing the appropriate error and a MAP_CLOSE service request, sends them to the MSC and 3975 returns to the idle state. 3976 Failure of dialogue opening in the HLR 3977 If the macro Reeive_Open_Ind takes the Vr exit or the Error exit, the MAP process returns to the idle state. 3978 Abort of MSC dialogue 3979 If the MAP process receives a MAP_P_ABORT indication before receiving a service indication, the MAP process 3980 returns to the idle state. 3981 When the MAP process receives a MAP_NOTICE indication before receiving a service indication, the MAP process 3982 closes the dialogue with the MSC, and returns to the idle state. 3983 When the MAP process is waiting for the application response to the IST Alert, the MAP service provider may abort 3984 the dialogue by issuing a MAP_CLOSE, a MAP_P_ABORT or a MAP_U_ABORT indication. In this case, the MAP 3985 process returns to the idle state.
2016
2017
Process IST_Alert_HLR
Figure 21.9/4: Process in the HLR to handle an IST Alert notification
21.9_4.1(2)
Idle
Signals to/from the left are to/from the call handling process in the HLR; signals to/from the right are to/from the MSC
Receive_ Open_Ind
Section 25.1
OK Wait_For_ Service_ Indication Idle
Vr, Error
MAP_P_ ABORT_ind
MAP_IST_ ALERT_ind
MAP_ NOTICE_ind
Idle
IST ALERT
MAP_ CLOSE_req
Wait_For_ Application_ Response
Idle
IST ALERT Ack
IST ALERT Negative response Set User Error
MAP_CLOSE_ind, MAP_P_ABORT_ind, MAP_U_ABORT_ind
MAP_IST_ALERT_rsp, MAP_CLOSE_req
Idle
Idle
3986
3987
Figure 21.9/3: Process IST_Alert_HLR
2018
2019 Release 4
624
3GPP TS 29.002 V4.17.0 (2006-06)
3988 3989
21.10 IST Command
21.10.1 General
3990 The Immediate Service Termination Command procedure is used to terminate the call activities related to a subscriber. 3991 The message flow for the IST Command service is shown in figure 21.10/1, where the MSC may be a Visited MSC or a 3992 Gateway MSC.
3993 3994 3995 3996 3997 3998 3999 4000 4001 4002 4003
+-----+ C +-----+ HLR +------------+------------ MSC +-----+ +-----+ IST_COMMAND ------------------------------> IST_COMMAND ack <------------------------------ Figure 21.10/1: IST Command
4005
4006
21.10.2 Procedure in the HLR
4007 The MAP process in the HLR is shown in figure 21.10/2. The MAP process invokes macros not defined in this clause; 4008 the definitions of these macros can be found as follows: 4009 4010
Receive_Open_Cnf Check_Confirmation
see clause 25.1.2; see clause 25.2.2.
4011 Successful Outcome 4012 4013 4014 4015 4016
When the MAP process receives an IST Command request, it requests a dialogue with the MSC (Gateway MSC or Visited MSC), by sending a MAP_OPEN service request, a MAP_IST_COMMAND service request, and a MAP_DELIMITER service request. The HLR then invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the MSC.
4017 If the MAP process receives a MAP_IST_COMMAND service confirm from the MSC, the MAP process invokes the 4018 macro Check_Confirmation to check the content of the confirm. 4019 If the macro Check_Confirmation takes the OK exit, the MAP process sends a IST Command ack containing the 4020 information received from the MSC to the call handling process in the HLR and returns to the idle state. 4021 Failure of dialogue opening with the HLR 4022 If the macro Receive_Open_Cnf takes the Vr exit or the Error exit, the MAP process sends a negative response to the 4023 call handling process in the HLR, and returns to the idle state. 4024 Error in MAP_IST_COMMAND confirm 4025 If the MAP_IST_COMMAND service confirm contains a user error or a provider error, or the macro 4026 Check_Confirmation indicates that there is a data error, the MAP process sends a negative response to the call handling 4027 process in the HLR, and returns to the idle state. 4028 Abort of MSC dialogue 4029 When the MAP process is waiting for an MSC response to the MAP_ IST_COMMAND, the MAP service provider 4030 may abort the dialogue by issuing a MAP_CLOSE, a MAP_P_ABORT or a MAP_U_ABORT indication. In this case, 4031 the MAP process sends a negative response to the call handling process in the HLR, and returns to the idle state.
2020
3GPP
2021 Release 4
625
3GPP TS 29.002 V4.17.0 (2006-06)
4032 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication when the MAP process is 4033 waiting for an MSC response to the MAP_ IST_COMMAND, the MAP process closes the dialogue with the MSC, 4034 sends a negative response to the call handling process in the HLR, and returns to the idle state.
Process IST_C m om and_H LR 21.10_2(1)
S ignals to/from the left are to/from the M ; SC signals to/from the right are to/from the call handling P rocess in the H LR
Figure 21.9/2: P rocess in the H LR to handle an IST C m om and to the M C S Idle
IST C M A O M ND
M _OP N_req, AP E M _IS AP T_C M A D O M N _req, M _DE ITE _req AP LIM R
R eceiv e_ O pen_C nf O K
S ection 25.1
V Error r, IST C M A O M ND Negative response
W ait_For_ M C S _Response
Idle M P T_ A _IS C M AN O M D_cnf M P_CLO _ind, A SE M P_P_AB R A O T_ind, M P_U_AB R A O T_ind M _N TICE_ AP O ind
C heck_ C onfirm ation OK IS C m T om and Ack
S ection 25.2
M _CLO _ AP SE req
Prov ider error, User error, Data error
IS C M A T O M ND Negativ e response
Idle
Idle
4035
4036
Figure 21.10/2: Process IST_Command_HLR
2022
3GPP
2023 Release 4
626
3GPP TS 29.002 V4.17.0 (2006-06)
4037
21.10.3 Procedure in the MSC
4038 The MAP process in the MSC is shown in figure 21.10/3. The MAP process invokes a macro not defined in this clause; 4039 the definition of this macro can be found as follows: 4040
Receive_Open_Ind
see clause 25.1.1.
4041 Successful outcome 4042 When the MAP process in the MSC receives a request to open a dialogue, it invokes the macro Receive_Open_Ind to 4043 check if the dialogue can be opened. 4044 If the dialogue can be opened, and the service indication received is a MAP_IST_COMMAND, the MSC then sends the 4045 IST command indication to the call handling process in the MSC, and waits for a response. 4046 If the call handling process in the MSC returns a positive response, the MAP process constructs a 4047 MAP_IST_COMMAND service response and a MAP_CLOSE service request, sends them to the HLR, and returns to 4048 the idle state. 4049 Negative response from MSC call handling process 4050 If the call handling process in the MSC returns a negative response, the MAP process constructs a 4051 MAP_IST_COMMAND service response containing the appropriate error and a MAP_CLOSE service request, sends 4052 them to the HLR and returns to the idle state. 4053 Failure of dialogue opening in the MSC 4054 If the macro Receive_Open_Ind takes the Vr exit or the Error exit, the MAP process returns to the idle state. 4055 Abort of HLR dialogue 4056 If the MAP process receives a MAP_P_ABORT indication before receiving a service indication, the MAP process 4057 returns to the idle state. 4058 When the MAP process receives a MAP_NOTICE indication before receiving a service indication, the MAP process 4059 closes the dialogue with the HLR, and returns to the idle state. 4060 When the MAP process is waiting for the application response to the IST Command, the MAP service provider may 4061 abort the dialogue by issuing a MAP_CLOSE, a MAP_P_ABORT or a MAP_U_ABORT indication. In this case, the 4062 MAP process returns to the idle state.
2024
3GPP
2025 Release 4
627
3GPP TS 29.002 V4.17.0 (2006-06)
Process IST_Command_MSC
Figure 21.10/3: Process in the MSC to handle an IST Command notification
21.10_3.1(2)
Idle
Signals to/from the left are to/from the call handling process in the MSC; signals to/from the right are to/from the HLR
Receive_ Open_Ind
Section 25.1
OK Wait_For_ Service_ Indication Idle
Vr, Error
MAP_P_ ABORT_ind
MAP_IST_ COMMAND_ind
MAP_ NOTICE_ind
Idle
IST COMMAND
MAP_ CLOSE_req
Wait_For_ Application_ Response
Idle
IST COMMAND Ack
IST COMMAND Negative response Set User Error
MAP_CLOSE_ind, MAP_P_ABORT_ind, MAP_U_ABORT_ind
MAP_IST_ALERT_rsp, MAP_CLOSE_req
Idle
Idle
4063
4064
Figure 21.10/3: Process IST_Command_MSC
2026
3GPP
2027 Release 4
628
3GPP TS 29.002 V4.17.0 (2006-06)
4065
22
-
Supplementary services procedures
accessUnstructuredSsContext; accessFunctionalSsContext.
4066 The following application contexts exist for handling of supplementary services: 4067 4068
4069 The accessUnstructuredSsContext refers to a simple MAP user, for which the corresponding MAP process can be 4070 identified by the MAP-Provider directly. 4071 4072 4073 4074
However, the accessFunctionalSsContext refers to a complex MAP-User consisting of several processes. For this user, a process co-ordinator is defined for each network entity, in order to identify the correct process to invoke. These processes open and validate the dialogue, then invoke the necessary operation-specific process. These processes are described below.
4075 4076 4077
22.1 Functional supplementary service processes
22.1.1 Functional supplementary service process co-ordinator for MSC
4078 Upon receipt of a CM-Service request with CM-service type = SS, the MSC initiates the process access request 4079 procedure towards the VLR as described in clause 25 of the present document. 4080 4081 4082 4083 4084
Once a CM connection is established, the MSC can handle supplementary service indications from the MS. Table 22.1/1 shows the co-ordinating process' reaction on receipt of specific SS service indications on the air interface. After the relevant process is invoked, the received air interface service indication is sent to that process. The creation of service requests on the basis of air interface messages is described in 3GPP TS 29.011 [59]. Table 22.1/1: Relationship between received service indication and invoked process in the MSC
Service indication received A_REGISTER_SS_ind A_ERASE_SS_ind A_ACTIVATE_SS_ind A_DEACTIVATE_SS_ind A_INTERROGATE_SS_ind A_REGISTER_PASSWORD Process invoked REGISTER_SS_MSC ERASE_SS_MSC ACTIVATE_SS_MSC DEACTIVATE_SS_MSC INTERROGATE_SS_MSC REGISTER_PASSWORD_MSC
4085 4086 Figure 22.1/1 shows the co-ordinating process in the MSC.
2028
3GPP
2029 Release 4
629
3GPP TS 29.002 V4.17.0 (2006-06)
Process SS_Coordinator_MSC
Figure 22.1/1: S up plementary S ervice Coordination process in t he MS C, t o identify which fun ctional supplementary service pro cess s hall be invoked.
22.1_1(1)
NULL
NULL
A_CM_ SE RV _RE Q
G SM 04.08, 04.10
P rocess_ A ccess_ Request _MSC OK
S ec tion 25.4 Error
W ait _f or_ servic e_ind
NULL
From int erworking funct ion, see GSM 09.1 1
A_ REGISTER_ SS_ind
A_ ERAS E_ SS_ind
A_ A CTIV ATE _ S S_ind
A_ DE ACTIV ATE_ S S_ind
A _INTE RROGA TE_ SS _ind
A_ REGISTER_ P ASS W ORD_ ind
Register_ SS _MS C
E rase_ S S_MS C
Ac tivate_ SS _MS C
Deact ivat e_ S S_MS C
Interrogate_ SS _MSC
Register_ P assw ord_ MS C
A_ REGIS TER_ SS _ind
A_ ERAS E_ SS_ind
A_ A CTIV ATE _ S S_ind
A_ DE ACTIV ATE_ S S_ind
A_ INTE RROGA TE _ SS _ind
A_ REGIS TER_ P ASS W ORD_ ind
Relay_Inf o
To P roc ess
* FROM A_Interf ace
A_RE L FROM A_Interface
A _* FROM O FFS PRING
A _RE L FROM OFFS PRING
Receive_ errors_MS C
- TO OFFS PRING
A_RE L TO OFFSPRING
- TO A _Interface
A _DISC TO A -interface
Null
Relay_Inf o
NULL
Relay_Info
NULL
4087
4088
Figure 22.1/1: Process SS_Coordinator_MSC
2030
3GPP
2031 Release 4
630
3GPP TS 29.002 V4.17.0 (2006-06)
4089 4090
22.1.2 Functional supplementary service process co-ordinator for VLR
4091 Any functional SS process in the VLR starts by the VLR receiving the MAP_PROCESS_ACCESS_REQUEST 4092 indication. The VLR then acts as described in clause 25 of the present document. 4093 4094 4095 4096 4097
If the Process Access Request was successful, the VLR can handle supplementary service indications from the MSC. Table 22.1/2 shows the co-ordinating process' reaction on receipt of specific SS service indications from the MSC. After the relevant process is invoked, the received service indication is sent to that process, and the co-ordinating process terminates. Table 22.1/2: Relationship between received service indication and invoked process in the VLR
Service indication received MAP_REGISTER_SS_ind MAP_ERASE_SS_ind MAP_ACTIVATE_SS_ind MAP_DEACTIVATE_SS_ind MAP_INTERROGATE_SS_ind MAP_REGISTER_PASSWORD Process invoked REGISTER_SS_VLR ERASE_SS_VLR ACTIVATE_SS_VLR DEACTIVATE_SS_VLR INTERROGATE_SS_VLR REGISTER_PASSWORD_VLR
4098 4099 Figure 22.1/2 shows the co-ordinating process in the VLR.
2032
3GPP
2033 Release 4
631
3GPP TS 29.002 V4.17.0 (2006-06)
Process SS_Coordinator_VLR
Figure 22.1/2: S up plementary S ervice Coordination process in t he VLR, to open and process the acce ss request from t he MS C, and then identif y which funct ional s upplementary servic e process shall be invoked.
22.1_2.1(2)
NULL
NULL
Receive_ Open_ ind OK
S ec tion 25.1
Error W ait _f or_ PA R
V1 P erform_ MAP _V 1_ Dialogue
Receive_ error_ from _MS C Err E rror
P roc ess _ Acc ess _ Request_VLR OK
Section 25.4
NULL
NULL
W ait_for_ service_ind
MA P_ REGISTER_ SS_ind
MA P_ E RA SE _ SS _ind
MA P_ ACTIV ATE_ SS_ind
MA P_ DE ACTIV ATE_ SS_ ind
M AP _INTERROG ATE _ S S_ind
MAP _ REGIS TE R_ P ASS W O RD_ ind
Receive_ e rrors_ f rom _MSC Err
Register_ SS _V LR
E ras e_ SS _VLR
Act ivat e_ SS _V LR
Deac tivate_ SS _VLR
Int errogat e_ SS _VLR
Register_ P as sword_ VLR
NULL
MA P_ REGIS TER_ SS _ind
MA P_ E RA SE _ SS _ind
MA P_ ACTIV ATE_ SS_ind
MA P_ DE ACTIV ATE_ SS_ind
MAP _ INTE RRO GATE_ S S_ind
MAP _ REGIS TE R_ P ASS W O RD_ ind
Relay_Inf o
4100
4101
Figure 22.1/2 (sheet 1 of 2): Process SS_Coordinator_VLR
2034
3GPP
2035 Release 4
632
3GPP TS 29.002 V4.17.0 (2006-06)
Process SS_Coordinator_VLR
Figure 22.1/2: S upplementary S ervice Coordination process in t he VLR, to open and process the access request from t he MS C, and then identif y which functional s upplementary servic e process shall be invoked.
22.1_2.2(2)
Relay_Inf o
* FROM PROV IDE R
MA P_U_AB ORT_ind MA P_P _ ABORT_ind MA P_CLOSE _ind
* FROM OFFS PRING
MAP _U_A BORT_ind MAP _CLO SE_ind
- TO OFFS PRING
- TO OFFSP RING
- TO P ROVIDER
- TO PROV IDE R
Relay_Inf o
NULL
Relay_Info
NULL
4102
4103
Figure 22.1/2 (sheet 2 of 2): Process SS_Coordinator_VLR
4104 4105
4106 4107 4108 4109 4110
22.1.3 Functional supplementary service process co-ordinator for HLR
Any functional SS process in the HLR starts by the HLR receiving a MAP-OPEN service indication. If that service is successful, the HLR can handle supplementary service indications from the VLR. Table 22.1/3 shows the co-ordinating process' reaction on receipt of specific SS service indications from the VLR. After the relevant process is invoked, the received service indication is sent to that process, and the co-ordinating process terminates. Table 22.1/3: Relationship between received service indication and invoked process in the HLR
Service indication received MAP_REGISTER_SS_ind MAP_ERASE_SS_ind MAP_ACTIVATE_SS_ind MAP_DEACTIVATE_SS_ind MAP_INTERROGATE_SS_ind MAP_REGISTER_PASSWORD Process invoked REGISTER_SS_HLR ERASE_SS_HLR ACTIVATE_SS_HLR DEACTIVATE_SS_HLR INTERROGATE_SS_HLR REGISTER_PASSWORD_HLR
4111 4112 Figure 22.1/3 shows the co-ordinating process in the HLR.
2036
3GPP
2037 Release 4
633
3GPP TS 29.002 V4.17.0 (2006-06)
Process SS_Coordinator_HLR
Figure 22.1/ 3: S upplementary S ervice Coordination process in the HLR, t o identify which func tional supplement ary s ervice process shall be invoked.
22.1_3.1(2)
NULL
NULL
Receive_ Open_ ind
S ec tion 25.1
Error W ait _f or_ servic e_ind
V1 P erform_ MAP _V 1_ Dialogue
NULL
MA P_ REGISTER_ SS_ind
MA P_ ERAS E_ SS_ind
MA P_ A CTIV ATE _ S S_ind
MAP _ DE ACTIV ATE_ S S_ind
MAP _INTERROGA TE_ SS _ind
MA P_ REGISTER_ P ASS W ORD_ ind
Register_ S S_HLR
Erase_ SS _HLR
Activate_ SS _HLR
Deact ivat e_ S S_HLR
Interrogate_ SS _HLR
Register_ P assw ord_ HLR
MA P_ REGIS TER_ SS _ind
MA P_ ERAS E_ SS_ind
MA P_ A CTIV ATE _ S S_ind
MAP _ DE ACTIV ATE_ S S_ind
MAP _ INTE RROGA TE _ SS _ind
MA P_ REGIS TER_ P ASS W ORD_ ind
Relay_Inf o
MA P_ NOTICE _ ind
MA P_U_A BORT_ind, MA P_P_AB ORT_ind, MA P_CLOS E_ind
MA P_ CLOS E_ req
NULL
4113
4114
Figure 22.1/3 (sheet 1 of 2): Process SS_Coordinator_HLR
2038
3GPP
2039 Release 4
634
3GPP TS 29.002 V4.17.0 (2006-06)
Process SS_Coordinator_HLR
Figure 22.1/ 3: S upplementary S ervice Coordination process in the HLR, t o identify which func tional supplement ary s ervice process shall be invoked.
22.1_3.2(2)
Relay_Inf o
* FROM PROV IDE R
MA P_U_AB ORT_ind MA P_P _ ABORT_ind MA P_CLOSE _ind
* FROM OFFSP RING
MAP _U_A BORT_ind MAP _CLO SE_ind
- TO OFFS PRING
- TO OFFSP RING
- TO P ROVIDER
- TO PROV IDE R
Relay_Inf o
NULL
Rel ay_Info
NULL
4115
4116
Figure 22.1/3 (sheet 2 of 2): Process SS_Coordinator_HLR
4117 4118
22.1.4 Call completion supplementary service process co-ordinator for HLR
4119 The MAP co-ordinating process in the HLR to handle a dialogue opened with the callCompletion application context is 4120 shown in figure 22.1/4. The MAP process invokes a macro not defined in this clause; the definition of this macro can be 4121 found as follows: 4122 4123 4124 4125 4126 4127
Receive_Open_Ind
see clause 25.1.1.
Any call completion SS process in the HLR starts by the HLR receiving a MAP-OPEN service indication. If that service is successful, the HLR can handle call completion supplementary service indications from the VLR. Table 22.1/4 shows the co-ordinating process' reaction on receipt of specific call completion SS service indications from the VLR. After the relevant process is invoked, the received service indication is sent to that process. Table 22.1/4: Relationship between received service indication and invoked process in the HLR
Service indication received MAP_REGISTER_CC_ENTRY_ind MAP_ERASE_CC_ENTRY_ind Process invoked REGISTER_CC_ENTRY_HLR ERASE_CC_ENTRY_HLR
4128 4129 After creation of the user process the Co-ordinator relays the messages between the MAP_PM and the invoked process 4130 until a request or an indication for dialogue termination is received. 4131 The Call_Completion Co-ordinator is shown in figure 22.1/4.
2040
3GPP
2041 Release 4
635
3GPP TS 29.002 V4.17.0 (2006-06)
Process CC_Coord_HLR
F igur e 2 2.1/4: Coord inating proces s in the HLR to h an dl e a d ialog ue opened with the A C CallCom pleti on Con text
22.1_4(1)
Sign als to/fr om the left ar e to/f rom the V L R via the M AP provider ; signa ls to/f rom th e r ight ar e to/f rom the child pr oce ss Id le
R eceive_ O pe n_Ind
Section 25.1
OK W ait_F or_ Service_ Indication
Vr , E rror
Idle
M AP _R EG IS TER_ C C_ ENTRY _in d
M AP _ER ASE _ CC _E NT RY _ind
MA P _N OTICE_ ind
M A P_C LO SE _ind, M A P_P_ AB OR T_ ind, M A P_U _A BO RT_ in d
Registe r_CC _ E ntry_H L R
Erase_ CC _ En try_HL R
MA P _CLOSE _ req
M AP_REGIS TER _ CC _ENTR Y_ in d
MA P_E R AS E_ CC_ENTR Y_ind
Id le
Relay_ Info rm ation
M A P_C LO SE _ ind, M A P_P_AB OR T_ind , M A P_U _A BO RT_ind
M A P_ CLO SE _ind, M A P_ U_A BO RT_ind
Idle
R elay_ In for m atio n
Idle
Relay_ In f or mation
4132
4133
Figure 22.1/4: Process_CC_Coord_HLR
2042
3GPP
2043 Release 4
636
3GPP TS 29.002 V4.17.0 (2006-06)
4134 4135
22.2 Registration procedure
22.2.1 General
4136 The registration procedure is used to register data related to a supplementary service in the HLR. The registration 4137 procedure is a fully transparent communication between the MS and the HLR, except that some services may be 4138 invoked as a result of the procedure, as described in the clauses below. 4139 The registration procedure is shown in figure 22.2.1/1. 4140 The following services may be used: 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
MAP_PROCESS_ACCESS_REQUEST
(defined in clauses 8 and 25);
MAP_TRACE_SUBSCRIBER_ACTIVITY (defined in 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 MAP_REGISTER_SS (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 12 and 25); (defined in clauses 8 and 25); (defined in clause 11).
+----+ +----+ B +----+ D +----+ MS ------------MSC ------+-------VLR ----+------HLR +----+ +----+ +----+ +----+ A_CM_SERV_REQ ----------------> MAP_PROCESS_ACC_REQ (note 1) ------------------->... (note 2) A_REGISTER_SS MAP_REGISTER_SS ---------------->------------------->MAP_REGISTER_SS ----------------> MAP_REGISTER_SS ack MAP_REGIS_SS ack A_REGISTER_SS ack<-------------------<---------------- <---------------- MAP_INS_SUBS_DATA <---------------- (note 3)
NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 04.10, 04.8x and 04.9x. 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 on the Process Access Request procedure, please refer to clause 25 in the present document. NOTE 3: Services printed in italics are optional.
4176
4169 4170 4171 4172 4173 4174 4175
Figure 22.2.1/1: Interfaces and services for supplementary service registration
4177
22.2.2 Procedures in the MSC
4178 Supplementary service registration 4179 The A_REGISTER_SS service indication received by the MAP user in the MSC contains the SS-Code and any 4180 parameters that are related to the supplementary service. 4181 The MAP user transfers the received information to the VLR in the MAP_REGISTER_SS request without checking the 4182 contents of the service indication. Rules for the mapping are described in 3GPP TS 29.011 [59].
2044
3GPP
2045 Release 4
637
3GPP TS 29.002 V4.17.0 (2006-06)
4183 The MSC then awaits the receipt of the MAP_REGISTER_SS confirm from the VLR. The outcome of the procedure is 4184 reported to the MS in the A_REGISTER_SS response message as described in GSM 04.8x, 04.9x and 09.11. Finally the 4185 SS-connection is released. 4186 For call independent SS operations, each message shall only contain a single component. Messages which contain more 4187 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). 4188 Error handling 4189 4190 4191 4192 4193
If at any time during the supplementary service part of this procedure a MAP_P_ABORT, MAP_U_ABORT, MAP_NOTICE or unexpected MAP_CLOSE indication is received from the VLR concerning the process, a CM_RELEASE_COMPLETE indication is sent to the MS (as specified in 3GPP TS 29.011 [59]). Upon receipt of a MAP_NOTICE indication from the VLR, the MSC must close the VLR dialogue by sending a MAP_CLOSE request. The process is then terminated.
4194 If an A_CM_RELEASE indication is received from the MS, all open transactions shall be released using the 4195 MAP_U_ABORT request indicating application procedure cancellation, and the process is terminated. 4196 The registration procedure in the MSC is shown in figure 22.2.2/1.
2046
3GPP
2047 Release 4
638
3GPP TS 29.002 V4.17.0 (2006-06)
Process SS_REGISTER_MSC
Figure 22.2. 2/1 :Mobile intiated reg is tration of s upplementary servic e in the MS C
22.2.2_1(1)
NULL
A_ RE GISTER_ SS_ind
GSM 04.8X
Receive_ errors_ MS C
Sectio n 22. 11 NULL
MA P_REGIS TER_SS _req MA P_DE LIMITE R_req
W ait_f or_ SS_cnf
MA P_ RE GISTER_ SS_cnf
Receive_ errors_ MS C
Sectio n 22. 11
MAP _P ERROR
yes MA P_U_ AB ORT_req
no A_ RE GISTER_ SS _rs p
GS M 04.8X
A_CM_ REL_COMP
4197
4198
Figure 22.2.2/1: Procedure SS_Register_MSC
2048
3GPP
2049 Release 4
639
3GPP TS 29.002 V4.17.0 (2006-06)
4199
22.2.3 Procedures in the VLR
4200 Supplementary service registration 4201 When receiving the MAP_REGISTER_SS indication, the MAP user in the VLR transfers the information to the HLR in 4202 the MAP_REGISTER_SS request without checking the contents of the service indication. 4203 The VLR then awaits the receipt of the MAP_REGISTER_SS confirm from the HLR. The MAP user in the VLR shall 4204 transfer the information contained in this primitive to the MSC in the MAP_REGISTER_SS response without checking 4205 its contents. 4206 For call independent SS operations, each message shall only contain a single component. Messages which contain more 4207 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). 4208 Error handling 4209 4210 4211 4212 4213
If at any time during this procedure a MAP_P_ABORT, MAP_U_ABORT, MAP_NOTICE or unexpected MAP_CLOSE indication is received from the MSC concerning the process, a MAP_U_ABORT request indicating application procedure cancellation is sent to the HLR (if a connection exists). If a MAP_NOTICE indication was received from the MSC, that dialogue must be closed by sending a MAP_CLOSE request towards the MSC. The process is terminated.
4214 If a MAP_P_ABORT, MAP_U_ABORT or MAP_CLOSE indication is received from the HLR, a MAP_U_ABORT 4215 request shall be sent to the MSC terminating the process. If a MAP_NOTICE indication was received from the HLR, 4216 that dialogue must be closed by sending a MAP_CLOSE request towards the HLR. The process terminates. 4217 The registration procedure in the VLR is shown in figure 22.2.3/1.
2050
3GPP
2051 Release 4
640
3GPP TS 29.002 V4.17.0 (2006-06)
Process SS_REGISTER_VLR
Figure 22.2.3/1: Mob ile initated regist ration of supplementart y services in the V LR
22.2.3_1.1(2)
NULL
MA P_ REGISTER_ SS_ind
From MS C
Receive_ error_ from_ MS C Err
Figure 22.11.2/2
MAP_OP EN_ req
To HLR, including - Des tination ref erenc e = subscriber's IMSI - Originat ing referenc e = VLR number
MA P_ REGIS TER_ SS _req
To HLR
MA P_ DELIMITER_ req
To HLR
Receive_ Open_ Conf irm
Section 25.1
OK W ait_for_ ss_cnf
V1 Perform_ MA P_V1_ Dialogue
Error
MAP _U_ A BORT_req
To MS C
4218
4219
Figure 22.2.3/1 (sheet 1 of 2): Procedure SS_Register_VLR
2052
3GPP
2053 Release 4
641
3GPP TS 29.002 V4.17.0 (2006-06)
Process SS_REGISTER_VLR
Figure 22.2.3/1: Mobile initated regist ration of supplementart y services in the V LR
22.2.3_1.2(2)
W ait_for_ ss_cnf
MA P_ REGIS TER_ SS _cnf
From HLR
Receive_ error_ from_HLR
Figure 22. 11.2/ 3
Receive_ error_ from_MS C err
Figure 22.11.2/2
MAP _P _ ERROR
yes
no 1 MA P_U_ A BORT_ req To HLR
MA P_ REGISTER_ SS _rsp
To MSC
MA P_ CLOS E_ req
To MSC
4220
4221
Figure 22.2.3/1 (sheet 2 of 2): Procedure SS_Register_VLR
4222
22.2.4 Procedures in the HLR
4223 The procedure in the HLR is initiated when it receives a MAP_REGISTER_SS indication. 4224 The HLR acts as follows: 4225 4226
if the operator has barred the subscriber from access to supplementary services, the Call Barred error should be returned to the VLR. The parameter "operatorBarring" shall be included with the error.
4227 The supplementary service request shall then be processed according to 3GPP TS 23.011 [22] and the 03.8x and 03.9x4228 series of technical specifications. This handling may lead to either a successful result, a partially successful result, or an 4229 error being returned. 4230 For call independent SS operations, each message shall only contain a single component. Messages which contain more 4231 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]): 4232 4233 4234 4235 4236
if the VLR is to be updated after the supplementary service registration, the MAP_INSERT_SUBS_DATA_HLR process shall be initiated; if at any time during this procedure a MAP_P_ABORT, MAP_U_ABORT or MAP_CLOSE indication concerning the process is received from the VLR, the process is terminated. If a MAP_NOTICE indication is received, a MAP_CLOSE request is sent towards the VLR.
4237 The registration procedure in the HLR is shown in figure 22.2.4/1.
2054
3GPP
2055 Release 4
642
3GPP TS 29.002 V4.17.0 (2006-06)
Process SS_REGISTER_HLR
Figure 22.2. 4/1: Registration of supplementary services proc edure in HLR
22.2.4_1.1(2)
NULL
NULL
MA P_ REGIS TE R_ SS _ind
yes
Operator det ermined barring of S S Management no
SS _Request
To proces s SS_REQUE ST_W ITH_B S_G ROUP specifie d in GSM 03. 11
Wa it_for_ handling
S S_ackn
SS _P artial_ Ac ceptence
SS _E rror
Set error CA LL BA RRE D
S et s uccessful result
S et error
MA P_ RE GISTER_ SS _rs p
To VLR
4238
4239
Figure 22.2.4/1 (sheet 1 of 2): Procedure SS_Register_HLR
2056
3GPP
2057 Release 4
643
3GPP TS 29.002 V4.17.0 (2006-06)
Process SS_REGISTER_HLR
Figure 22.2. 4/1: Registration of supplementary services proc edure in HLR
22.2.4_1.2(2)
MAP _ CLO SE_ req
no
Insert _ subscriber_ data yes
Ins_S ubs_Dat a_ S tan d_Alone_HLR
Section 25. 7
MA P_ N OTICE_ ind
MAP _P _A BORT_ind MAP _U_ABORT_ind MAP _CLOSE_ind
MA P_ C LOSE _ req
4240
4241
Figure 22.2.4/1 (sheet 2 of 2): Procedure SS_Register_HLR
2058
3GPP
2059 Release 4
644
3GPP TS 29.002 V4.17.0 (2006-06)
4242 4243
22.3 Erasure procedure
22.3.1 General
4244 The erasure procedure is used to erase data related to a supplementary service in the HLR. The erasure procedure is a 4245 fully transparent communication between the MS and the HLR, except that some services may be invoked as a result of 4246 the procedure, as described in the clauses below. 4247 The erasure procedure is shown in figure 22.3.1/1. 4248 The following services may be used: 4249 4250 4251 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
MAP_PROCESS_ACCESS_REQUEST
(defined in clauses 8 and 25);
MAP_TRACE_SUBSCRIBER_ACTIVITY (defined in 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 MAP_ERASE_SS (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 12 and 25); (defined in clauses 8 and 25); (defined in clause 11).
+----+ +----+ B +----+ D +----+ MS ------------MSC ------+-------VLR ----+-------HLR +----+ +----+ +----+ +----+ A_CM_SERV_REQ ----------------> MAP_PROCESS_ACC_REQ (note 1) ------------------->... (note 2) A_ERASE_SS MAP_ERASE_SS ---------------->-------------------> MAP_ERASE_SS ----------------> MAP_ERASE_SS ack MAP_ERASE_SS ack A_ERASE_SS ack <-------------------<---------------- <---------------- MAP_INS_SUBS_DATA <---------------- (note 3)
NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 04.10, 04.8x and 04.9x. 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 on the Process Access Request procedure, please refer to clause 25 in the present document. NOTE 3: Services printed in italics are optional.
4284
4277 4278 4279 4280 4281 4282 4283
Figure 22.3.1/1: Interfaces and services for supplementary service erasure
4285
22.3.2 Procedures in the MSC
4286 The MSC procedures for erasure are identical to those specified for registration in clause 22.2.2. The text and diagrams 4287 in clause 22.2.2 apply with all references to registration changed to erasure.
2060
3GPP
2061 Release 4
645
3GPP TS 29.002 V4.17.0 (2006-06)
4288
22.3.3 Procedures in the VLR
4289 The VLR procedures for erasure are identical to those specified for registration in clause 22.2.3. The text and diagrams 4290 in clause 22.2.3 apply with all references to registration changed to erasure.
4291
22.3.4 Procedures in the HLR
4292 The HLR procedure for erasure is identical to those specified for registration in clause 22.2.4. The text and diagrams in 4293 clause 22.2.4 apply with all references to registration changed to erasure.
4294 4295
22.4 Activation procedure
22.4.1 General
4296 The activation procedure is used to activate a supplementary service in the HLR. The activation procedure is a fully 4297 transparent communication between the MS and the HLR, except that some services may be invoked as a result of the 4298 procedure, as described in the clauses below. 4299 The activation procedure is shown in figure 22.4.1/1. 4300 The following services may be used: 4301 4302 4303 4304 4305 4306 4307 4308 4309 4310 4311
MAP_PROCESS_ACCESS_REQUEST
(defined in clauses 8 and 25);
MAP_TRACE_SUBSCRIBER_ACTIVITY (defined in 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 MAP_ACTIVATE_SS (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 12 and 25); (defined in clause 11); (defined in clauses 8 and 25); (defined in clause 11).
2062
3GPP
2063 Release 4
4312 4313 4314 4315 4316 4317 4318 4319 4320 4321 4322 4323 4324 4325 4326 4327 4328 4329 4330 4331 4332 4333 4334
646
3GPP TS 29.002 V4.17.0 (2006-06)
+----+ +----+ +----+ B +----+ D +----+ MS -EIR -----MSC ------+-------VLR ----+------HLR +----+ +----+ +----+ +----+ +----+ A_CM_SERV_REQ ---------------->MAP_PROCESS_ACC_REQ (note 1) ------------------->... (note 2) A_ACTIVATE_SS MAP_ACTIVATE_SS MAP_ACTIVATE_SS ---------------->------------------->----------------> A_GET_PW MAP_GET_PW MAP_GET_PW <--------------- <-------------------<---------------- A_GET_PW ack MAP_GET_PW ack MAP_GET_PW ack ---------------->------------------->----------------> A_ACTIVATE_SS ack MAP_ACTIVATE_SS ackMAP_ACTIV_SS ack <----------------<-------------------<---------------- MAP_INS_SUBS_DATA ...<---------------- (note 3)
NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 04.10, 04.8x and 04.9x. 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 on the Process Access Request procedure, please refer to clause 25 of this document. NOTE 3: Services printed in italics are optional.
4342
4335 4336 4337 4338 4339 4340 4341
Figure 22.4.1/1: Interfaces and services for supplementary service activation
4343
22.4.2 Procedures in the MSC
4344 The A_ACTIVATE_SS service indication received by the MAP user in the MSC contains the SS-Code and any 4345 parameters related to the supplementary service. 4346 The MSC transfers the received information to the VLR in the MAP_ACTIVATE_SS request without checking the 4347 contents of the service indication. Rules for the mapping are described in 3GPP TS 29.011 [59]. 4348 4349 4350 4351 4352
The MAP user may subsequently receive the MAP_GET_PASSWORD indication from the VLR. Upon receipt of this indication, the MSC sends the A_GET_PASSWORD message towards the MS and then awaits the response from the MS. When an A_GET_PASSWORD confirm message is received from the MS, the MSC initiates the MAP_GET_PASSWORD response towards the VLR without checking further the contents of the indication. Also see 3GPP TS 29.011 [59].
4353 The MSC will receive a MAP_ACTIVATE_SS confirm from the VLR. The outcome of the procedure is reported to the 4354 MS in the A_ACTIVATE_SS response message, see GSM 04.8x, 04.9x and 09.11. Finally the SS connection is 4355 released. 4356 For call independent SS operations, each message shall only contain a single component. Messages which contain more 4357 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). 4358 The handling of MAP_P_ABORT, MAP_U_ABORT, MAP_NOTICE and unexpected MAP_CLOSE or 4359 A_CM_RELEASE in this procedure is identical to the handling in the Registration procedure in the MSC, see 4360 clause 22.2.2 of the present document. 4361 The activation procedure in the MSC is shown in figure 22.4.2/1.
2064
3GPP
2065 Release 4
647
3GPP TS 29.002 V4.17.0 (2006-06)
Pro ces s AC TIVATE_S S_M SC
F ig ure 22 .4. 2/ 1: Mobile int ia ted activat ion of s upplement ary s ervice in th e M S C
22.4 .2_1(1)
NU LL
NU LL
A_ A CTI V A TE _ S S _ind
G S M 04 .8x and 04.9 x-series
Receive_ errors_ MS C
S ec t ion 22. 11
M A P _A C TIV A T E _S S _req M A P _DE LI MI TE R _req
W ait _for_ S S _c nf
MA P _ A CT IV A TE _ S S _c nf
R ec eiv e_ errors_ MS C
S ect ion 2 2.11
G E T_ P A S S W O RD_ MS C
S ec t ion 22. 11
OK MA P _ P E RRO R y es no W ait_for_ S S _c nf
N ull
MA P _U_ A B O R T_req
A_ A CTI V A TE _ S S _rsp
G S M 04. 8x and 04. 9x-series
A _CM_ RE L_ CO MP
4362
4363
Figure 22.4.2/1: Procedure Activate_SS_MSC
2066
3GPP
2067 Release 4
648
3GPP TS 29.002 V4.17.0 (2006-06)
4364
22.4.3 Procedures in the VLR
4365 Supplementary service activation 4366 When receiving the MAP_ACTIVATE_SS indication, the MAP user in the VLR transfers the information to the HLR 4367 in the MAP_ACTIVATE_SS request without checking the contents of the service indication. 4368 The VLR may then receive the MAP_GET_PASSWORD indication. This information is transferred to the MSC in the 4369 MAP_GET_PASSWORD request. If a MAP_GET_PASSWORD confirm primitive is received from the MSC, the 4370 VLR initiates the MAP_GET_PASSWORD response towards the HLR. 4371 The VLR will receive the MAP_ACTIVATE_SS confirm from the HLR. The MAP user in the VLR shall transfer the 4372 information contained in this primitive to the MSC in the MAP_ACTIVATE_SS response without checking its 4373 contents. 4374 For call independent SS operations, each message shall only contain a single component. Messages which contain more 4375 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). 4376 Error handling 4377 The handling of MAP_P_ABORT, MAP_U_ABORT, MAP_NOTICE and unexpected MAP_CLOSE in this procedure 4378 is identical to the handling in the Registration procedure in the VLR, see clause 22.2.3 of the present document. 4379 The activation procedure in the VLR is shown in figure 22.4.3/1.
2068
3GPP
2069 Release 4
649
3GPP TS 29.002 V4.17.0 (2006-06)
Pro ces s AC TIVATE_S S_VLR
F ig ure 22. 4. 3/ 1: A ct ivation of s upplem en tary service proc edure in t he V LR
22.4.3_1.1(2)
NU LL
MA P _ A CT IV A TE _ S S _ind
From MS C
Receive_ error_ fr om _M S C E rr
Figure 22.1 1.2 /2
MA P _ O P E N_ req
To H LR, inc luding - Des tinat ion reference = s ubs criber's I MS I - O rigin atin g reference = V LR numb er
MA P _ A CT IV A TE _ S S _req
To H LR
MA P _ DE LI MI TE R_ req
To H LR
R ec e ive_ O pen_ C onfirm
S ect ion 25. 1 1 V1 P erform _ M A P _V 1_ Dialog ue E rror
OK W ait _for_ ss _cnf
M A P _U_ A B O RT_req
To MS C
4380
4381
Figure 22.4.3/1 (sheet 1 of 2): Procedure Activate_SS_VLR
2070
3GPP
2071 Release 4
650
3GPP TS 29.002 V4.17.0 (2006-06)
Pro ces s AC TIVATE_S S_VLR
F ig ure 22. 4. 3/ 1: A ct ivation of s upplem en tary service proc edure in t he V LR
22.4.3_1.2(2)
W ait _for_ ss _cnf
MA P _ A CT IV ATE _ S S _c nf
From H LR
R ec eive_ error_ f rom _H LR
F ig ure 22 .11. 2/3
Receive_ error_ fr om _M S C err
Figure 22.1 1.2 /2
MA P _P _ E RRO R no
yes
M A P _U_ A B O R T_ req
To H LR
MA P _ A CT IV A TE _ S S _rsp
To MS C
MA P _ CL OS E _ req
To MS C G E T_ P A S S W O RD_ V LR
Figure 22.1 1.1 /2
OK
N ULL
W a it_f or_ ss _c nf
4382
4383
Figure 22.4.3/1 (sheet 2 of 2): Procedure SS_Activate_VLR
2072
3GPP
2073 Release 4
651
3GPP TS 29.002 V4.17.0 (2006-06)
4384
22.4.4 Procedures in the HLR
4385 The procedure in the HLR is initiated when it receives a MAP_ACTIVATE_SS indication. 4386 The HLR acts as follows: 4387 4388
if the operator has barred the subscriber from access to supplementary services, the Call Barred error should be returned to the VLR. The parameter "operatorBarring" shall be included with the error.
4389 The supplementary service request shall then be processed according to 3GPP TS 23.011 [22] and the 03.8x and 03.9x4390 series of technical specifications. This handling may lead to either a successful result, a partially successful result, or an 4391 error being returned. 4392 During the handling of activation, the get password procedure may be initiated (as specified in 3GPP TS 23.011 [22]). 4393 This will involve the sending of a MAP_GET_PASSWORD request to the VLR. 4394 For call independent SS operations, each message shall only contain a single component. Messages which contain more 4395 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]): 4396 4397 4398 4399
if the VLR is to be updated after the supplementary service activation, the MAP_INSERT_SUBS_DATA_HLR process is initiated; handling of receipt of MAP_P_ABORT, MAP_U_ABORT or MAP_CLOSE indications from the VLR is identical to their handling in the registration procedure, see clause 22.2.4 above.
4400 The activation procedure in the HLR is shown in figure 22.4.4/1.
2074
3GPP
2075 Release 4
652
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess ACTIVATE_S S_H LR
F ig ure 22 .4. 4/ 1: A ct iva tion of supplem entary services proc edu re in H LR .
22.4.4_1.1(2)
NULL
NU LL
M AP_ A CTI V A TE _ S S _ind
y es
O p erat or determ ined b arring of S S M an agem ent no S S _Requ es t T o process S S _R E Q U E S T_W IT H_B S _G RO UP sp ecified in TS G S M 03. 11
S et error CA LL B A RR ED
W ait _for_ hand lin g
S S _ac kn
SS_ P art ial_ A ccep ten ce
SS_ E rror
S S _G et _ P ass word
S et suc ces sfu l res ult
S et er ror
MA P _ GE T _P A S S W O R D_req M A P _DE LI MI NA TO R_req
MA P _ A CT IV ATE _ S S _rsp
To V LR
W ait_f or_ ps swd
M A P _G E T_ P A S S W O RD_ c nf
S S _G et _ P as sword_ Ac k
W ait_f or_ han dling
4401
4402
Figure 22.4.4/1 (sheet 1 of 2): Procedure Activate_SS_HLR
2076
3GPP
2077 Release 4
653
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess ACTIVATE_SS_H LR
F igure 22 .4. 4/ 1: A ct ivation of sup plem entary services proc e du re in H LR .
22.4.4_1.2(2)
MA P _ CLO S E _ req
MA P _ N OT ICE _ ind
MA P _ P _A B O RT_ ind MA P _ U_A B O R T_ind M A P _CLO S E _ ind
no
I nsert _ s ubs criber_ d ata yes
MA P _ C LO S E _ req
In s_S u bs _Dat a_ S tand _A lone_ HLR
S ec t ion 25. 7
4403
4404
Figure 22.4.4/1 (sheet 2 of 2): Procedure Activate_SS_HLR
4405 4406
22.5 Deactivation procedure
22.5.1 General
4407 The deactivation procedure is used to deactivate a supplementary service in the HLR. The deactivation procedure is a 4408 fully transparent communication between the MS and the HLR, except that some services may be invoked as a result of 4409 the procedure, as described in the clauses below. 4410 The deactivation procedure is shown in figure 22.5.1/1. 4411 The following services may be used: 4412 4413 4414 4415 4416 4417 4418
MAP_PROCESS_ACCESS_REQUEST
(defined in clauses 8 and 25);
MAP_TRACE_SUBSCRIBER_ACTIVITY (defined in clauses 9 and 25); MAP_PROVIDE_IMSI MAP_FORWARD_NEW_TMSI MAP_AUTHENTICATE MAP_SET_CIPHERING_MODE MAP_CHECK_IMEI (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25);
2078
3GPP
2079 Release 4
654
3GPP TS 29.002 V4.17.0 (2006-06)
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
MAP_READY_FOR_SM MAP_GET_PASSWORD MAP_INSERT_SUBSCRIBER_DATA MAP_DEACTIVATE_SS
(defined in clauses 12 and 25); (defined in clause 11); (defined in clauses 8 and 25); (defined in clause 11).
+----+ +----+ B +----+ D +----+ MS ------------MSC ------+-------VLR ----+------HLR +----+ +----+ +----+ +----+ A_CM_SERV_REQ ---------------->MAP_PROCESS_ACC_REQ (note 1) ------------------->... (note 2) A_DEACTIVATE_SS MAP_DEACTIVATE_SS MAP_DEACTIVATE_SS ---------------->------------------->----------------> A_GET_PW MAP_GET_PW MAP_GET_PW <--------------- <-------------------<---------------- A_GET_PW ack MAP_GET_PW ack MAP_GET_PW ack ---------------->------------------->----------------> A_DEACTIV_SS ack MAP_DEACTIV_SS ack MAP_DEACT_SS ack <----------------<-------------------<---------------- MAP_INS_SUBS_DATA ...<---------------- (note 3)
NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 04.10, 04.8x and 04.9x. 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 on the Process Access Request procedure, please refer to clause 25 in the present document. NOTE 3: Services printed in italics are optional.
4453
4446 4447 4448 4449 4450 4451 4452
Figure 22.5.1/1: Interfaces and services for supplementary service deactivation
4454
22.5.2 Procedures in the MSC
4455 The MSC procedures for deactivation are identical to those specified for activation in clause 22.4.2. The text and 4456 diagrams in clause 22.4.2 apply with all references to activation changed to deactivation.
4457
22.5.3 Procedures in the VLR
4458 The VLR procedures for deactivation are identical to those specified for activation in clause 22.4.3. The text and 4459 diagrams in clause 22.4.3 apply with all references to activation changed to deactivation.
4460
22.5.4 Procedures in the HLR
4461 The HLR procedures for deactivation are identical to those specified for activation in clause 22.4.4. The text and 4462 diagrams in clause 22.4.4 apply with all references to activation changed to deactivation.
4463 4464
22.6 Interrogation procedure
22.6.1 General
4465 The interrogation procedure is used to retrieve information related to a supplementary service from the VLR or the 4466 HLR. It is the VLR which decides whether an interrogation request should be forwarded to the HLR or not. Some non4467 supplementary service related services may be invoked as a result of the procedure, as described in the clauses below. 4468 The interrogation procedure is shown in figure 22.6.1/1.
2080
3GPP
2081 Release 4
655
3GPP TS 29.002 V4.17.0 (2006-06)
4469 The following services may be used: 4470 4471 4472 4473 4474 4475 4476 4477 4478
4479 4480 4481 4482 4483 4484 4485 4486 4487 4488 4489 4490 4491 4492
MAP_PROCESS_ACCESS_REQUEST
(defined in clauses 8 and 25);
MAP_TRACE_SUBSCRIBER_ACTIVITY (defined in 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_INTERROGATE_SS (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 12 and 25); (defined in clause 11).
+----+ +----+ B +----+ D +----+ MS ------------MSC ------+-------VLR ----+-------HLR +----+ +----+ +----+ +----+ A_CM_SERV_REQ ---------------->MAP_PROCESS_ACC_REQ (note 1) ------------------->... (note 2) A_INTERROGATE_SS MAP_INTERROGATE_SS MAP_INTERROGATE_SS ---------------->------------------->-----------------> A_INTERR_SS ack MAP_INTERR_SS ack MAP_INTER_SS ack <----------------<-------------------<----------------- (note 3)
NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 04.10, 04.8x and 04.9x. 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 on the Process Access Request procedure, please refer to clause 25 in the present document. NOTE 3: Services printed in italics are optional.
4500
4493 4494 4495 4496 4497 4498 4499
Figure 22.6.1/1: Interfaces and services for supplementary service interrogation
4501
22.6.2 Procedures in the MSC
4502 The MSC procedures for interrogation are identical to those specified for registration in clause 22.2.2. The text and 4503 diagrams in clause 22.2.2 apply with all references to registration changed to interrogation.
4504
22.6.3 Procedures in the VLR
4505 Supplementary service interrogation 4506 When receiving the MAP_INTERROGATE_SS indication, the MAP user acts as follows: 4507 4508
if the operator has barred the subscriber from access to supplementary services, the error Call Barred is returned to the MSC. The parameter "operatorBarring" shall be included with the error.
4509 The interrogation is either answered by the VLR or by the HLR, depending on the service interrogated. 4510
a) Interrogation to be handled by the VLR
4511 The supplementary service request shall then be processed according to 3GPP TS 23.011 [22] and the 03.8x and 03.9x4512 series of technical specifications. This handling may lead to either a successful result, a partially successful result, or an 4513 error being returned. 4514 For call independent SS operations, each message shall only contain a single component. Messages which contain more 4515 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]).
2082
3GPP
2083 Release 4
656
3GPP TS 29.002 V4.17.0 (2006-06)
4516
b) Interrogation to be handled by HLR
4517 If the interrogation is to be handled by the HLR, on receiving the MAP_INTERROGATE_SS indication, the MAP user 4518 in the VLR transfers the information to the HLR in the MAP_INTERROGATE_SS request without further checking the 4519 contents of the service indication. 4520 The VLR will receive the MAP_INTERROGATE_SS confirm from the HLR. The MAP user in the VLR shall transfer 4521 the information contained in this primitive to the MSC in the MAP_INTERROGATE_SS response without checking its 4522 contents. 4523 For call independent SS operations, each message shall only contain a single component. Messages which contain more 4524 than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]). 4525 Error handling 4526 Handling of MAP_P_ABORT, MAP_U_ABORT, MAP_NOTICE and unexpected MAP_CLOSE in this procedure is 4527 identical to the handling in the Registration procedure in the VLR, clause 22.2.3. The Interrogation procedure is 4528 described in figure 22.6.3/1. 4529
2084
3GPP
2085 Release 4
657
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess INTER R OG ATE _SS_VL R
F ig ure 22. 6. 3/ 1: Int errorrogation of supplem entary service procedure in V LR
22.6.3_1.1(3)
NU LL
NU LL MA P _I NTE R RO G A TE _ S S _ind
Receive_ error_ from_ MS C F rom MS C E rr
Figure 22.1 1.2 /2
O pe rator d etermined barring of S S Managem ent yes no SS known no yes S et error CA LL B A RR E D in terrog at io n hand led b y V LR no yes
S S _Request
To proc ess S S _R E Q UE S T_ W ITH _B S _G RO UP spec ified in TS G S M 03. 11
W ait for reques t to be h and led
S S _ackn
S S _P art ial_ A cc eptenc e
S S _E rror
S et suc ces sfu l res ult
S et erro r
MA P _I NTE R RO G A TE _ S S _rsp
4530
4531
Figure 22.6.3/1 (sheet 1 of 3): Procedure Interrogate_SS_VLR
2086
3GPP
2087 Release 4
658
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess INTER R OG ATE _SS_VL R
F ig ure 22. 6. 3/ 1: Int errorrogation of supplem entary service procedure in V LR
22.6.3_1.2(3)
MA P _ O P E N_ req
To H LR, inc luding - Des tinat ion reference = s ubs criber's I MS I - O rigin atin g reference = V LR numb er
MA P _ IN TE RR O G A TE _ S S _req
To H LR
MA P _ DE LI MI TE R_ req
To H LR
R ec e ive_ O pen_ C onfirm
S ect ion 25. 1 2
OK W ait _for_ ss _cnf
V1 P erf orm _ MA P _V 1_ Dialog ue
E rror
M A P _U_ A B O RT_req
To MS C
4532
4533
Figure 22.6.3/1 (sheet 2 of 3): Procedure Interrogate_SS_VLR
2088
3GPP
2089 Release 4
659
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess INTER R OG ATE _SS_VL R
F ig ure 22. 6. 3/ 1: Int errorrogation of supplem entary service procedure in V LR
22.6.3_1.3(3)
W ait _for_ ss _cnf
MA P _ IN TE RR O G A TE _ S S _c nf
From H LR
R ec eive_ error_ f rom _H LR
F ig ure 22. 11. 2/3
Receive_ error_ fr om _M S C err
Figure 22.1 1.2 /2
MA P _P _ E RRO R no
yes
M A P _U_ A B O R T_ req
To H LR
MA P _ INT E RR O G A TE _ To MS C S S _rsp
MA P _ CL OS E _ req
To MS C
4534
4535
Figure 22.6.3/1 (sheet 3 of 3): Procedure Interrogate_SS_VLR
2090
3GPP
2091 Release 4
660
3GPP TS 29.002 V4.17.0 (2006-06)
4536
22.6.4 Procedures in the HLR
if the operator has barred the subscriber from access to supplementary services, the error Call Barred is returned to the MSC. The parameter "operatorBarring" shall be included with the error; if the supplementary service is not supported in the HLR, the error Unexpected Data Value is returned to the VLR.
4537 When receiving the MAP_INTERROGATE_SS indication, the MAP user acts as follows: 4538 4539 4540 4541
4542 The interrogation is either answered by the VLR or by the HLR, depending on the service interrogated. 4543 4544 4545 4546 4547 4548 4549
a) 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. b) Interrogation to be handled by HLR The supplementary service request shall be processed according to 3GPP TS 23.011 [22] and the 03.8x and 03.9x-series of technical specifications. This handling may lead to either a successful result or an error being returned.
4550 For call independent SS operations, each message shall only contain a single component. 4551 Error handling 4552 Handling of MAP_P_ABORT, MAP_U_ABORT, MAP_NOTICE and unexpected MAP_CLOSE in this procedure is 4553 identical to the handling in the Registration procedure in the VLR, clause 22.2.3. The Interrogation procedure is 4554 described in figure 22.6.4/1.
2092
3GPP
2093 Release 4
661
3GPP TS 29.002 V4.17.0 (2006-06)
Pr o ce s s INT E RR O G AT E _ S S_ H L R
F ig u re 2 2 .6 . 4 / 1 : In te rro g at io n of s u p p le m en t a ry s e rvice s p ro ce d u re in H L R
2 2 .6 .4 _ 1 (1 )
N UL L
NU LL
M AP_ I N TE RR O G A TE _ S S -in d
ye s
O p e ra to r d e te rm in ed b a rrin g o f S S M an a g em e n t no
S e t e rro r CA L L B A RR E D no
SS s u p p o rte d in H L R ye s
S et e rro r Un e xp ec te d Da t a V a lu e ye s
I n t erro g a t io n s ho u ld h a ve b ee n a n sw ere d by the V LR no
S et e rro r S S N ot A va ila b le
S S _ R e q u es t
T o p ro ce ss S S _ R E Q UE S T_ W IT H _ B S _ G R O UP s p e cifie d in TS G S M 0 3 . 1 1
W a it _ fo r_ h a n d lin g
S S _ a ck n
S S _ E rro r
S et s u c ce s sfu l re s u lt
S et e rro r
MAP _ IN TE R R O G A TE _ S S _ rsp
MAP _ CL OS E _ req
4555
4556
Figure 22.6.4/1: Procedure Interrogate_SS_HLR
2094
3GPP
2095 Release 4
662
3GPP TS 29.002 V4.17.0 (2006-06)
4557 4558
22.7 Invocation procedure
22.7.1 General
4559 The invocation procedure is used to check subscription data in the VLR for certain supplementary services which are 4560 invoked after the call set-up phase is finished. For invocation of supplementary services which are invoked during the 4561 call set-up phase, please refer to the Call Handling procedure descriptions. 4562 The invocation procedure is shown in figure 22.7.1/1. Note that some optional services may be invoked in connection 4563 with this procedure, as described in the clause below. 4564 The following services are used: 4565 4566 4567 4568 4569 4570 4571 4572 4573
4574 4575 4576 4577 4578 4579 4580 4581 4582 4583 4584 4585 4586
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_INVOKE_SS
(defined in clauses 8 and 25); (defined in clauses 9 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 12 and 25); (defined in clause 11).
+----+ +----+ B +----+ MS -------------MSC ------+-------VLR +----+ +----+ +----+ A_CM_SERV_REQ ----------------->MAP_PROCESS_ACC_REQ (note 1) ------------------->.. (note 2) A_INVOKE_SS -----------------> MAP_INVOKE_SS (note 3) -------------------> A_INVOKE_SS MAP_INVOKE_SS <-----------------<-------------------
NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 04.10, 04.8x and 04.9x. 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 on the Process Access Request procedure, please refer to clause 25 in the present document. NOTE 3: A_INVOKESS is a generic message to illustrate any supplementary service invocation request message on the air interface, e.g. BuildMPTY, see 3GPP TS 24.080 [38].
4595
4587 4588 4589 4590 4591 4592 4593 4594
Figure 22.7.1/1: Interfaces and services for supplementary service invocation
4596
22.7.2 Procedures in the MSC
4597 Process access request 4598 Before the Call Hold or Multi-Party supplementary services can be invoked, a CC connection must be established 4599 between the MS and the MSC as described in 3GPP TS 24.008 [35] and the Call Handling procedure descriptions 4600 within the present document. 4601 4602 4603 4604
When an A_INVOKE_SS request message arrives at the MSC during a call (as described in 3GPP TS 24.010 [36], 04.8x and 04.9x-series of technical specifications), then if control of subscription to the invoked supplementary service is required, the MSC initiates the process access request procedure towards the VLR as described in clause 25 of the present document.
2096
3GPP
2097 Release 4
663
3GPP TS 29.002 V4.17.0 (2006-06)
4605 Supplementary service invocation 4606 4607 4608 4609 4610 4611 4612 4613 4614
If the Process Access Request procedure towards the VLR is successful, the MSC shall forward a MAP_INVOKE_SS service request towards the VLR. This request shall contain the SS-Code of the supplementary service to be invoked, and possibly the Basic service code. Mapping from the A_INVOKE_SS to this service request is described in 3GPP TS 29.011 [59]. The MSC will receive a MAP_INVOKE_SS confirm from the VLR. If the outcome of the service is successful (i.e. the service confirm is empty), the MSC will invoke the requested supplementary service as described in GSM 02.8x-series, 03.8x and 03.9x-series of technical specifications. If the outcome of the service is unsuccessful, the MSC shall send an appropriate A_INVOKE_SS response towards the MS. The structure of this message is described in 3GPP TS 29.011 [59] and 04.8x and 04.9x-series of technical specifications.
4615 Error handling 4616 4617 4618 4619
If at any time during this procedure a MAP_P_ABORT, MAP_U_ABORT, MAP_NOTICE or MAP_CLOSE indication concerning the process is received from the VLR, the process is terminated. If a MAP_NOTICE indication was received from the VLR, the VLR dialogue must also be aborted by sending a MAP_U_ABORT request indicating Procedure error towards the VLR. Possible signalling to the MS is described in 3GPP TS 24.010 [36].
4620 If an A_CM_RELEASE indication is received from the MS, all open transactions are released using the 4621 MAP_U_ABORT request indicating application procedure cancellation; the process terminates. 4622 The invocation procedure in the MSC is shown in figure 22.7.2/1.
2098
3GPP
2099 Release 4
664
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess INV OKE_S S_M SC
F ig ure 22 .7. 2/ 1: Mobile initiated in vocat ion of su pp lem ent ary s ervic e procedu re in the M S C
22.7.2_1.1(2)
N ULL
CC connect ion exist s
A_ I NV O K E _ S S _ ind
Not e 1
S ubs cription ch ec k req uired yes
no
P roc ess _ A cc ess _ Reques t_M S C
S ec tion 25 .4
Inv ok e su pplem e nt ary servic e
GS M 02 .8X 03 .8X 04 .8X
null ac k MA P_ I NVO K E _S S _ req A _I NV O K E _ S S _rsp
NU LL
Note 1
MA P_ DE L IMI TE R _ req
NU LL
W ai t_f or S S _c nf
Not e 1: F ict itio us sig nal t o indic at e receipt /s ending of S S invoc at ion in vo ke c omponen t on t he a ir int erface (eg. B uildMP T Y) . Des cribed in G S M 04. 8X and 09 .11.
4623
4624
Figure 22.7.2/1 (sheet 1 of 2): Procedure Invoke_SS_MSC
2100
3GPP
2101 Release 4
665
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess INV OKE_S S_M SC
F ig ure 22 .7. 2/ 1: Mobile initiated in vocat ion of su pp lem ent ary s ervic e procedu re in the M S C
22.7.2_1.2(2)
W ait _for S S _ cnf
MAP_ IN V O K E _ S S _c nf
Receive_ error s_ MS C
S ect ion 2 2.11
MA P _ CL OS E _ req
err M A P _P _ E RRO R yes no Invok e su pp lem ent ary service GS M 02 .8X 03 .8X 04 .8X M A P _U_ A B O RT_req
sys tem fa ilure S et error S YS TE M FA I LU RE
N ULL
A _I N V OK E _ S S _r sp
Not e 1
A _I NV O K E _ S S _rsp
N ot e 1
N ULL
N ULL
CC c onnection exist s
NU LL
Not e 1: F ict itio us s ignal t o indic at e rec eip t/ s ending of S S invocat ion invok e c omponent on th e air int erf ac e, (eg. B uild MP TY ). Des cribed in G S M 0 4.8 X and 09. 11.
4625
4626
Figure 22.7.2/1 (sheet 2 of 2): Procedure Invoke_SS_MSC
2102
3GPP
2103 Release 4
666
3GPP TS 29.002 V4.17.0 (2006-06)
4627
22.7.3 Procedures in the VLR
4628 Process Access Request 4629 When receiving the MAP_PROCESS_ACCESS_REQUEST indication, the VLR acts as described in clause 25 of the 4630 present document. 4631 Supplementary service invocation 4632 When receiving the MAP_INVOKE_SS indication, the MAP user acts as follows: 4633 4634 4635 4636 4637 4638 4639 4640 4641 4642 4643 4644
if the operator has barred the subscriber from access to supplementary services, the error "Call Barred" is returned to the MSC. The parameter "operatorBarring" shall be included with the error; if any irrelevant information elements (according to the service description) or invalid information element values are present in the service request, then the unexpected data value error is returned to the MSC in the MAP_INVOKE_SS response; if the VLR does not support the invoked supplementary service then the VLR shall respond with the SS Not Available error; if the requested supplementary service cannot be invoked by subscriber actions, then the VLR shall respond with the Illegal SS Operation error; if the subscriber is not provided with (i.e. subscribed to) the requested supplementary service, then the SS error status error (possibly including the SS-Status as parameter) is returned to the MSC in the MAP_INVOKE_SS response.
4645 If all checks are passed the VLR returns an empty MAP_INVOKE_SS response to the MSC, thus indicating that the 4646 invocation request was accepted. 4647 4648 4649 4650
If at any time during this procedure a MAP_P_ABORT, MAP_U_ABORT, MAP_NOTICE or unexpected MAP_CLOSE indication concerning the process is received from the MSC, the process terminates. If a MAP_NOTICE indication was received from the MSC, that dialogue must be aborted by sending a MAP_U_ABORT request indicating Procedure error towards the MSC. The process terminates.
4651 The invocation procedure in the VLR is shown in figure 22.7.3/1.
2104
3GPP
2105 Release 4
667
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess INV OKE_S S_VLR
F ig ure 22. 7. 3/ 1: Inv oc ation of s upplem ent ary service p roc edure in V LR 1
22.7 .3_1(1)
O perator d etermined barring of S S Management no C hec k_ In dicat ion NU LL
yes
S ec t ion 25.2
S et error C A LL B A R RE D
E rror OK P LMN supports SS S ect ion 25 .1 yes no
Receive_ O pen_ Ind
S et error S S NO T A V A I LA B LE
V1 S et error ILLE G A L S S OP E R A TI O N
O.K.
null S S c an be inv ok ed yes no
W ait
NUL L
S et error ILL E G A L S S O P E RA T IO N
MA P _ I NV O K E _ S S _rsp
P roc ess _ A cc ess _ Request _V LR null ac k
R ec eiv e_ error_ from _MS C null
SS sub s cribed
no
yes MA P _ CL OS E _ req W ait_ for_ S S _R eq NUL L
S et error S S E RRO R S TA TU S
NU LL
MA P _ IN V O K E _ S S _in d
R ec eiv e_ e rrors_ from _MS C null
S ect ion 22.11
MA P _ I NV O K E _ S S _rsp
S ect ion 25 .4
NUL L
MA P _ C LO S E _ req
N ULL
4652
4653
Figure 22.7.3/1: Procedure Invoke_SS_VLR
2106
3GPP
2107 Release 4
668
3GPP TS 29.002 V4.17.0 (2006-06)
4654 4655
22.8 Password registration procedure
22.8.1 General
4656 The password registration procedure is used to register a password in the HLR. The password registration procedure is a 4657 fully transparent communication between the MS and the HLR, except that some services may be invoked as a result of 4658 the procedure, as described below. 4659 The password registration procedure is shown in figure 22.8.1/1. 4660 The following services may be used: 4661 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
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_GET_PASSWORD
(defined in clauses 8 and 25); (defined in clauses 9 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 12 and 25); (defined in clause 11).
+----+ +----+ B +----+ D +----+ MS ------------MSC ------+-------VLR ----+-----HLR +----+ +----+ +----+ +----+ A_CM_SERV_REQ MAP_PROC_ACC_REQ ---------------->------------------->... (note 1) (note 2) A_REGISTER_PW MAP_REGISTER_PW MAP_REGISTER_PW ---------------->------------------->---------------> A_GET_PW MAP_GET_PW MAP_GET_PW <--------------- <-------------------<--------------- A_GET_PW ack MAP_GET_PW ack MAP_GET_PW ack ---------------->------------------->---------------> A_GET_PW MAP_GET_PW MAP_GET_PW <--------------- <-------------------<--------------- A_GET_PW ack MAP_GET_PW ack MAP_GET_PW ack ---------------->------------------->---------------> A_GET_PW MAP_GET_PW MAP_GET_PW <--------------- <-------------------<--------------- A_GET_PW ack MAP_GET_PW ack MAP_GET_PW ack ---------------->------------------->---------------> A_REGISTER_PW ackMAP_REGISTER_PW ack MAP_REG_PW ack <----------------<-------------------<---------------
NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 04.10, 04.8x and 04.9x. Services shown in dotted lines are triggers/ triggered signalling on the radio path. NOTE 2: For details on the Process Access Request procedure, please refer to clause 25 in the present document. NOTE 3: Use of each of the three MAP_GET_PASSWORD operations is described in clause 22.8.4.
4704
4698 4699 4700 4701 4702 4703
Figure 22.8.1/1: Interfaces and services for supplementary service password registration
2108
3GPP
2109 Release 4
669
3GPP TS 29.002 V4.17.0 (2006-06)
4705
22.8.2 Procedures in the MSC
4706 The password registration procedure in the MSC is identical to that for activation specified in clause 22.4.2. All the text 4707 and diagrams in clause 22.4.2 apply with all references to activation changed to password registration.
4708
22.8.3 Procedures in the VLR
4709 The password registration procedure in the VLR is identical to that for activation specified in clause 22.4.3. All the text 4710 and diagrams in clause 22.4.3 apply with all references to activation changed to password registration.
4711
22.8.4 Procedures in the HLR
4712 The procedure in the HLR is initiated when it receives a MAP_REGISTER_PASSWORD indication. 4713 The HLR acts as follows: 4714 4715 4716 4717 4718
if the operator has barred the subscriber for access to supplementary services, the Call Barred error is returned to the VLR. The parameter "operatorBarring" shall be included with the error; if any irrelevant information elements (according to the service description) or invalid information element values are present, then the unexpected data value error is returned to the VLR in the response. This error should thus be returned if the SS-Code provided by the mobile subscriber is not allocated.
4719 The HLR shall then process the MAP_REGISTER_PASSWORD indication as specified in 3GPP TS 23.011 [22]. 4720 During the handling of password registration, the password procedure will be initiated (as specified in 3GPP TS 23.011 4721 [22]) This will involve the sending of MAP_GET_PASSWORD requests to the VLR. 4722 4723
Handling of receipt of MAP_P_ABORT, MAP_U_ABORT or MAP_CLOSE indications from the VLR is identical to their handling in the registration procedure, see clause 22.2.4 above.
4724 The password registration procedure in the HLR is shown in figure 22.8.4/1.
2110
3GPP
2111 Release 4
670
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess RE G ISTER _PASSW O RD _H LR
F ig ure 22. 8. 4/ 1: Regis tration of s u pplement ary s erv ice pass word procedure in H LR
22.8.4_1.1(2)
N ULL
M A P _RE G IS T E R_P A S S W O R D ind
O perator det ermined barrin g of S S M anagement no Chec k_ In dic at ion
yes
S et error CA LL B A RR E D Fig ure 25. 2/1
ok SS_ R egist er_ P as sword To process P W 1 as sp ecified in TS G S M 03. 11
error
W ait_ for_P W MA P _R E G IS TE R_P A S S W O RD _rsp
MA P _ CLO S E _ req
MA P _ NO TI CE _ ind
M A P _P _A B O R T_ind M A P _U _A B O RT_ind M A P _C LO S E _ind
MA P _ CL OS E _ req
4725
4726
Figure 22.8.4/1 (sheet 1 of 2): Procedure Register_PW_HLR
2112
3GPP
2113 Release 4
671
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess RE G ISTER _PASSW O RD _H LR
F ig ure 22. 8. 4/ 1: Regis tration of s u pplement ary s erv ice pass word procedure in H LR
22.8.4_1.2(2)
W ait _f or_ PW
S S _G et_ P ass word
S S _G et_ New_ P as sword
S S _G et_N ew_ P as s word_ A gain
S S _U ser_ E rrors
SS_ P as sword_ C hang ed
A ll t hese in dicat ions are from process P W 1, P W 2, P W 3 or P W 4
MA P _ G E T_ P A S S W O R D_ req
To V LR
set error
MA P _ DE LI MI TE R_ req
MA P _ RE G IS T E R_ P A S S W O RD_ rsp
To V LR
W ait _f or_ p as sword
MA P _ C LO S E _ req
MA P _ G E T_ P A S S W O R D_ cnf
S S _G et_ P ass word_ A ck
T o proces s P W 1, P W 2, P W3 or P W 4 s pecif ied in TS G S M 0 3.11
W ait_ for_ PW
4727
4728
Figure 22.8.4/1 (sheet 2 of 2): Procedure Register_PW_HLR
2114
3GPP
2115 Release 4
672
3GPP TS 29.002 V4.17.0 (2006-06)
4729 4730
22.9 Mobile Initiated USSD procedure
22.9.1 General
4731 The procedure supports supplementary service signalling procedures which can allow PLMN specific services to be 4732 introduced. 4733 The message flow for the procedure can be found in 3GPP TS 23.090 [34]. 4734 The following services may be used: 4735 4736 4737 4738 4739 4740 4741 4742 4743 4744
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
(defined in clauses 8 and 25); (defined in clauses 9 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 12 and 25); (defined in clause 11); (defined in clause 11).
4745 The following service is certainly used: 4746
MAP_PROCESS_UNSTRUCTURED_SS_REQUEST (defined in clause 11).
4747
22.9.2 Procedures in the MSC
4748 Before the Process Unstructured SS Request service can be invoked, a call independent CM connection must be created 4749 between the MS and the MSC. 4750 Once a CM-connection is established, the MSC may handle the A_PROCESS_UNSTRUCTURED_SS_REQUEST 4751 from the MS. This message contains information input by the user, the message may be fed to an application contained 4752 locally in the MSC or to the VLR. The rules for determining this are specified in 3GPP TS 23.090 [34]. 4753
1) Message Destined for VLR
4754 If the message is destined for the VLR then the MSC shall transfer the message to the VLR using the mapping specified 4755 in detail in 3GPP TS 29.011 [59]. 4756 The MSC may subsequently receive one or more MAP_UNSTRUCTURED_SS_REQUEST or 4757 MAP_UNSTRUCTURED_SS_NOTIFY indications from the VLR. These shall be sent transparently to the MS. When 4758 a confirmation is received from the MS this shall be returned to the VLR. 4759 When the MSC receives a MAP_PROCESS_UNSTRUCTURED_SS_REQUEST confirmation from the VLR then it 4760 shall pass this to the MS and initiate release of the CM connection. 4761
2) Message Destined for Local Application
4762 If the message is destined for the local USSD application then the MSC shall transfer the message to the application. 4763 The MSC may subsequently receive one or more requests from the application which correspond to the 4764 MAP_UNSTRUCTURED_SS_REQUEST or MAP_UNSTRUCTURED_SS_NOTIFY indications. These shall be sent 4765 transparently to the MS. When a confirmation is received from the MS this shall be returned to the application.
2116
3GPP
2117 Release 4
673
3GPP TS 29.002 V4.17.0 (2006-06)
4766 When the MSC receives the result of the original operation from the application then it shall pass this to the MS and 4767 initiate release of the CM connection. 4768 Error Handling 4769 Both the MS and the VLR or USSD Application may initiate release of the CM-connection at any time. This is handled 4770 as shown in the diagrams. 4771 The procedure in the MSC is shown in figure 22.9.2/1.
2118
3GPP
2119 Release 4
674
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess MS _IN IT_USSD_MSC
F ig ure22.9 .2/ 1: H and ling of mob ile initiat ed U S S D at MS C
22.9.2_1.1(2)
W ait _for_ servic e_ ind
A rrows t o left are to M S , arrows t o right are t o V LR unless ot herw is e s tat ed.
NU LL
A _P R O CE S S _ UN S T'D_S S _ RE Q UES T_ind
A _CM _ S E RV _R E Q
G S M 04. 08 , 04. 10
Handle at M S C? (S ee G S M 03. 90) y es no
P roc ess_ A cc ess_ Re quest _MS C
S ect ion 25 .4
OK M A P _P R O CE S S _ UN S T'D_ S S _RE Q UE S T_req M A P _D E LIM IT E R_req W ait_for_ servic e_ ind
E rror
NU LL
W ait _for_ pus sd_c nf
Receive_ E rrors _MS C
M A P _P R O CE S S _ UN S T'D _S S _ RE Q U E S T_c nf
M A P _UN S T'D_ S S _NO TI FY _ ind
MA P _ UNS T'D_ S S _RE Q UE S T_ ind
NU LL
MA P _P E RRO R
no
A _ UN S T'D _ S S _NO TI FY _ req
A _U NS T'D_ S S _RE Q UE S T_ req
Y es S ect ion 22. 11 W ait _for_ us sd n _c nf W ait_for_ uss dr_c nf
MA P _ U_ A B O R T_req
A _P RO C E S S _ UNS T 'D _S S _ RE Q U E S T_rsp
A _ UN S T'D _ S S _NO TI FY _ c nf
R ec eive_ E rrors_M S C
A _U NS T'D_ S S _RE Q UE S T_ cn f
Receive_ E rr ors _MS C
A _CM_ RE L_C O MP
M A P _UN S T'D_ S S _NO TI FY _ rs p
N ULL
MA P _ UNS T'D_ S S _RE Q UE S T_ rsp
NU LL
NU LL
M AP_ DE L IM IT E R_ req
S ec tion 22. 11
MA P _ DE LI MI TE R_ req
S ect ion 22. 11
W ait _for_ pu ss d _c nf
W ait_for_ pus sd_ cnf
4772
4773
Figure 22.9.2/1 (sheet 1 of 2): Procedure MI_USSD_MSC
2120
3GPP
2121 Release 4
675
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess MS _IN IT_USSD_MSC
F ig ure22.9 .2/ 1: H and ling of mob ile initiat ed U S S D at MS C A rrows to lef t are to MS , arrows to rig ht are to US S D applic ation unles s ot herwis e st ated.
22.9.2_1.2(2)
US _ P RO CE S S _ UN S T'D_S S _ RE Q U E S T_req
MA P _ CL O S E _req
To V LR
W ait _for_ US S D _A pp l
US _P R O CE S S _ UNS T'D _S S _ RE Q U E S T_c nf
U S _U NS T'D_ S S _NO TI FY _ ind
US _ UN S T'D_ S S _RE Q UE S T_ ind
A _P RO C E S S _ UNS T 'D _S S _ RE Q U E S T_rsp
A _ UN S T'D _ S S _NO TI FY _ req
A _U NS T'D_ S S _RE Q UE S T_ req
NULL
W ait _for_ us sd n_c nf _2
W ait _for_ uss d r_ c nf_2
A _ UN S T'D _ S S _NO TI FY _ c nf
A _U NS T'D_ S S _RE Q UE S T_ cnf
U S _U NS T'D_ S S _NO TI FY _ rs p
US _ UN S T'D_ S S _RE Q UE S T_ rsp
W ait _for_ U S S D_ A ppl
W ait _for_ US S D_A pp l
US _ Release
A _CM _ S E RV _ RE L
US _ R eleas e
A _C M_ S E R V _RE L
US _ Release
A _CM_ S E RV _ RE L
A _CM_ RE L_ CO MP
US _ Releas e
A _C M_ R E L_C OM P
US _ R elease
A _CM _ RE L_ CO MP
US _ Re leas e
NU LL
N ULL
NU LL
4774
4775
Figure 22.9.2/1 (sheet 2 of 2): Procedure MI_USSD_MSC
2122
3GPP
2123 Release 4
676
3GPP TS 29.002 V4.17.0 (2006-06)
4776
22.9.3 Procedures in the VLR
4777 The initiation of the process is shown in clause 22.1.2. 4778 Once a MAP dialogue is established, the VLR may handle the MAP_PROCESS_UNSTRUCTURED_SS_REQUEST 4779 from the MSC. This message contains information input by the user, the message may be fed to an application 4780 contained locally in the VLR or to the HLR. The rules for determining this are specified in 3GPP TS 23.090 [34]. 4781 Message Destined for HLR 4782 If the message is destined for the HLR then the VLR shall transfer the message transparently to the HLR. 4783 The VLR may subsequently receive one or more MAP_UNSTRUCTURED_SS_REQUEST or 4784 MAP_UNSTRUCTURED_SS_NOTIFY indications from the HLR. These shall be sent transparently to the MSC. 4785 When a confirmation is received from the MSC this shall be returned to the HLR. 4786 When the VLR receives a MAP_PROCESS_UNSTRUCTURED_SS_REQUEST confirmation from the HLR then it 4787 shall pass this to the MS and close the MAP provider service. 4788 Message Destined for Local Application 4789 If the message is destined for the local USSD application then the VLR shall transfer the message to the application. 4790 The VLR may subsequently receive one or more requests from the application which correspond to the 4791 MAP_UNSTRUCTURED_SS_REQUEST or MAP_UNSTRUCTURED_SS_NOTIFY indications. These shall be sent 4792 transparently to the MSC. When a confirmation is received from the MSC this shall be returned to the application. 4793 When the VLR receives the result of the original operation from the application then it shall pass this to the MSC and 4794 initiate release of the CM connection. 4795 Error Handling 4796 Both the MSC and the HLR or USSD Application may initiate release of the MAP service at any time. This is handled 4797 as shown in the diagrams. 4798 The procedure in the VLR is shown in figures 22.9.3/1 and 22.9.3/2.
2124
3GPP
2125 Release 4
677
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess MS _IN IT_USSD_VLR
N UL L F ig ure 22 .9. 3/ 1: Handling fo r m obile init iated US S D at V LR Rec eiv e_ O p en_ ind OK W ait _f or_ PAR
22.9.3_1.1(3)
S ec tion 25.1
E rror, v1 N ULL NU LL
R ec eive_ error_ from _MS C E rr
Fifure 22 .11. 2/ 2
P roc es s_ A c c es s_ R equest _V LR
S ec tion 25.4
E rror OK W ait _f or_ s erv ice_ind
NU LL
MA P _P RO C E S S _ U NS T 'D _S S _ From M S C R E Q UE S T_ind
y es
O perator Det erm ined B arring of S S M an agem ent no
S et UE = C all B arred y es M A P _P R O CE S S _ UN S T'D _S S _ RE Q U E S T_rsp 1 NU LL
H andle at V LR? (S ee G S M 03 .90) no
MA P _ O P E N_req MA P _ P RO CE S S _UN S T'D _S S _ RE Q UE S T _req MA P _ DE LI MI TE R_req
To HLR , inc lud ing - Dest in ation ref eren ce = sub sc rib er's I MS I - O rigin ation ref erenc e = V LR num ber
Rec eiv e_ O p en_ c nf
S ection 25
OK W ait _f or_ p uss d_ c nf
E rror S et U E = S ys tem Failure
V1 MA P _ U_ A B O R T_req
MA P _ P RO C E S S _ U NS T'D_S S _ R E Q UE S T _rsp
NU LL
4799
4800
Figure 22.9.3/1 (sheet 1 of 3): Procedure MI_USSD_VLR
2126
3GPP
2127 Release 4
678
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess MS _IN IT_USSD_VLR
F ig ure 22 .9. 3/ 1: Handling fo r m obile init iated US S D at V LR A rrows to lef t are to MS C , arrows to rig ht are to HLR unles s ot herwis e st ated.
22.9.3_1.2(3)
W ait _for_ pus sd_c nf
R ec eive_ E rror_at_ V LR
MA P _ P R O CE S S _ UN S T'D _S S _ RE Q U E S T_c nf
M A P _UN S T'D_ S S _NO TI FY _ ind
MA P _ UNS T'D_ S S _RE Q UE S T_ ind
NU LL
MA P _P E RRO R
no
MA P _UN S T'D_ S S _NO TI FY _ req
MA P _ UNS T'D_ S S _RE Q UE S T_ req
yes Figure 22.9. 3/ 2
MA P _ DE L IM IT E R_ req
MA P _ DE LI MI TE R_ req
MA P _ U_ A B O R T_req
M A P _P R OC E S S _ U NS T 'D _S S _ R E Q U E S T_rsp
W ait _f or_ us sd n_cnf
W ait _for_ uss dr_c nf
M A P _ U_ A B O RT _req
M AP_ C LO S E _ r eq
MA P _UN S T'D_ S S _NO TI FY _ c nf
Receive_ E rror_at _ V LR
MA P _ UNS T'D_ S S _RE Q UE S T_ cnf
R ec eive_ E rror_at_ V LR
NU LL
M A P _UN S T'D_ S S _NO TI FY _ rs p
N ULL
MA P _ UNS T'D_ S S _RE Q UE S T_ rsp
NU LL
M AP_ DE L IM IT E R_ req
Figu re 22. 9.3 /2
MA P _ DE LI MI TE R_ req
Figure 2 2.9. 3/2
W ait _f or_ pu ss d_cnf
W ait _for_ pus sd_ cnf
4801
4802
Figure 22.9.3/1 (sheet 2 of 3): Procedure MI_USSD_VLR
2128
3GPP
2129 Release 4
679
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess MS _IN IT_USSD_VLR
F ig ure 22 .9. 3/ 1: Handling fo r m obile init iated US S D at V LR A rrows to lef t are to MS C , arrows to rig ht are to US S D applic ation unles s ot herwis e st at ed.
22.9.3_1.3(3)
US _ P RO CE S S _ UN S T'D_S S _ RE Q U E S T_req
W ait _for_ US S D _A pp l
US _P RO CE S S _ UN S T'D _S S _ RE Q U E S T_c nf
U S _U NS T'D_ S S _NO TI FY _ ind
US _UN S T'D_ S S _R E Q UE S T_ ind
MA P _P R O CE S S _ UNS T'D _S S _ RE Q U E S T_rsp
M A P _UN S T'D_S S _ N O TIF Y _req MA P _DE LI MI TE R _req
MA P _U NS T 'D _S S _ RE Q U E S T_req MA P _D E LI MIT E R_req
MA P _ CLO S E _ req
W ait _for_ us sd n_c nf_2
W ait_fo r_ uss dr_c nf_2
NU LL
M A P _UN S T'D_ S S _NO TI FY _ c nf
MA P _ UNS T'D_ S S _RE Q UE S T_ c nf
U S _U NS T'D_ S S _NO TI FY _ rs p
US _UN S T'D_ S S _R E Q UE S T_ rsp
W ait _for_ U S S D_ A ppl
W ait_fo r_ US S D_A pp l
US _ Release
R ec eive_ error_ from _MS C err
U S_ R eleas e
Receive_ error_ from _ MS C err
US _ Release
R ec eive_ error_ from _MS C err
MA P _U_ A B O R T_req
US _ Releas e
M A P _U_ A B O RT_req
US _ R eleas e
M A P _U_ A B O R T_re q
US _ Release
NU LL
N ULL
NU LL
Figure 22.1 1. 2/ 2
4803
4804
Figure 22.9.3/1 (sheet 3 of 3): Procedure_MI_USSD_VLR
2130
3GPP
2131 Release 4
680
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefin ition Re ce ive_Error_at_VLR
F ig ure 22 .9. 3/ 2: Handling of errors at V LR for U S S D
22.9 .3_2(1)
MA P _ CL OS E _ ind
From H LR
R ec eive_ error_from_ H LR
S ect ion 2 2.11
Receive_ error_f rom _ MS C err
S ec t ion 22. 11
MA P _ U_ A B O R T_ req
To MS C
MA P _U_ A B O R T_ req
To H LR
4805
4806
Figure 22.9.3/2: Macro Receive_Error_at_VLR
2132
3GPP
2133 Release 4
681
3GPP TS 29.002 V4.17.0 (2006-06)
4807
22.9.4 Procedures in the HLR
4808 The Mobile initiated USSD Procedure in the HLR starts by the HLR receiving a MAP-OPEN service indication from 4809 the VLR. 4810 4811 4812 4813 4814
Once a MAP dialogue is established, the HLR may handle the MAP_PROCESS_UNSTRUCTURED_SS_REQUEST from the VLR. This message contains information input by the user. If the alphabet used for the message is understood then the message shall either be fed to an application contained locally in the HLR or to the gsmSCF or to a secondary HLR where the USSD application is located. If the alphabet is not understood then the error "UnknownAlphabet" shall be returned.
4815 Message Destined for Local Application 4816 If the message is destined for the local USSD application then the HLR shall transfer the message to the local 4817 application. 4818 The HLR may subsequently receive one or more requests from the application which correspond to the 4819 MAP_UNSTRUCTURED_SS_REQUEST or MAP_UNSTRUCTURED_SS_NOTIFY indications. These shall be sent 4820 transparently to the VLR. When a confirmation is received from the VLR this shall be returned to the application. 4821 When the HLR receives the result of the original operation from the application then it shall pass this to the VLR and 4822 initiate release of the CM connection. 4823 Message Destined for gsmSCF or secondary HLR 4824 If the message is destined for the gsmSCF or secondary HLR then the primary HLR shall transfer the message 4825 transparently to the next node. 4826 The primary HLR may subsequently receive one or more MAP_UNSTRUCTURED_SS_REQUEST or 4827 MAP_UNSTRUCTURED_SS_NOTIFY indications from the gsmSCF. These shall be sent transparently to the VLR. 4828 When a confirmation is received from the VLR this shall be returned to the gsmSCF. 4829 When the primary HLR receives a MAP_PROCESS_UNSTRUCTURED_SS_REQUEST confirmation from the 4830 gsmSCF then it shall pass this to the VLR and closes the MAP provider service. 4831 Error Handling 4832 The VLR, the USSD Application and the gsmSCF or secondary HLR may initiate release of the MAP service at any 4833 time. This is handled as shown in the diagrams. 4834 The procedure in the primary HLR is shown in figure 22.9.4/1.
2134
3GPP
2135 Release 4
682
3GPP TS 29.002 V4.17.0 (2006-06)
Process MS_INIT_USSD_HLR
Handling of mobile initiated U SSD at H LR Signals to/from the left are to/from the VLR; Signals to/from the right are to/from the USSD application NULL
1(4)
MAP_ NOTICE_ ind MAP_ CLOSE_req
MAP_P_ABORT_ind MAP_U_ABORT _ind MAP_CLOSE_ind
Receive_ Open_ind OK
Section 25.1
Error
Vr
SS_ Release
Wait_for_ serv ice_ind
NULL
Perform MAP Vr Dialogue
NULL
NULL
MAP_PR OCESS_ UNST'D_SS_ REQUEST_ind
yes no alphabet supported no Operator Determ ined Barring of SS Management Handle at HLR ? US_PROCESS_ UNST'D_SS_ REQUEST_req yes Set UE = Unknown Alphabet Set UE = Call Barred
yes
no 1 page 3
MAP_PR OCESS_ UNST'D_SS_REQUEST_rsp, MAP_CLOSE_req W ait_for_ USSD _Appl. NULL
4835
4836
Figure 22.9.4/1 (sheet 1 of 4): Procedure MI_USSD_HLR
2136
3GPP
2137 Release 4
683
3GPP TS 29.002 V4.17.0 (2006-06)
Process MS_INIT_USSD_HLR
Fig u re 2 2 .9. 4 /1 : H an dling o f m ob ile in tia te d U S S D a t HL R .
22.9.4_1 .2(4)
A rro ws to lef t a re to V L R, a rro ws to rig ht a re to US S D a pp lica tio n u n le ss ot h erw ise sta te d.
W a it_ fo r_ U SS D _A p pl
US _P R O C E S S_ US _ UN ST 'D _ UN ST 'D _S S _ SS _ NO TIF Y _ RE Q U E S T_cn f in d MA P _ PR O C E S S _ UN ST 'D _S S _ RE Q U E S T_r sp M AP _ CL O S E _ re q U S_ Re le a se W a it_ fo r_ ussd n_ cnf
U S_ U NS T'D _ S S _ RE Q U E S T_ in d MA P _ UN ST 'D _S S _ NO T IFY _ re q MA P _ DE L IM ITE R _ re q W a it_ f or_ u s sdr_ cnf M A P _U NS T ' D_ S S _ RE Q UE S T_ req M A P _D E L IMI TE R_ re q
NU L L
M A P _ UN ST 'D _ S _ U S S _ NO TIF Y _ R e le ase c nf US _ UN ST 'D _ SS _ NO TIF Y _ rs p W a it_ fo r_ US S D_ A pp l M A P _U _ A B O R T_ req
M A P _U NS T' D_ S _ U S S _ RE Q U E S T_ le a se Re cn f U S_ U NS T'D _ S S _ RE Q U E S T_ rsp W a it_ f or_ U S SD _ A pp l MA P _ U _ A B O RT _re q
MA P _ U_ A BO RT_ re q
N UL L
N UL L
N UL L
4837
4838
Figure 22.9.4/1 (sheet 2 of 4): Procedure MI_USSD_HLR
2138
3GPP
2139 Release 4
684
3GPP TS 29.002 V4.17.0 (2006-06)
P ro c es s M S _INIT _U SS D_ HL R
Han d lin g of mob ile in itiate d US SD a t H LR Si gn al s to /fro m th e le ft ar e to/from th e V LR; Si gn al s to /fro m th e r igh t ar e to/from th e n ext n o de
3(4 )
MA P _O P EN _re q MA P _P RO CE S S_ UNS T'D_ S S _RE Q UE ST_ re q MA P _DE L IM ITER _re q Re ceive _ Op e n_ cnf OK Se ction 25
To n ext no de , in clu di ng -De sti na ti on refe re nce = IMS I o r MS IS DN -O rig ina tion re fere nc e = H LR n umb er
E rro r
V1
Se t U E = System Fa il ur e
MA P_ P ROC ES S _UN ST'D_ SS _ REQ UE S T_r sp MA P_ CL OS E _re q
MA P_ U_ AB O RT_ req
W ait_ for_ pu ssd -cn f Re ceive _ er ror _fro m_ VL R Re ceive _ er ror _fro m_ ne xt_ no d e MA P_ P ROC ES S_ UNS T'D_ SS _ REQ UE S T_c nf
NUL L
Se cti on 22 .11
MA P_ UNS T'D_ MA P_ UNS T'D_ SS _ NO TIFY _ SS _ REQ UE S T_ ind ind MA P_ UNS T'D_ SS _ REQ UE S T_ re q
MA P_ U_ AB O RT_ req Se t U E = System Fa il ur e MA P_ P ROC ES S_ UNS T'D_ SS _ REQ UE S T_r sp MA P_ CLO S E _ re q NUL L MA P_ DEL IMITE R_ re q NUL L MA P_ P ROC ES S _ UNS T'D_ SS _ REQ UE S T_r sp MA P_ UNS T'D_ SS _ NO TIFY _ re q MA P_ DEL IMITE R_ re q W ait _fo r_ ussd n _cn f
NUL L
MA P_ DEL IMITE R_ re q
W ai t_ for _ u ssdr_ cn f
4839
4840
Figure 22.9.4/1 (sheet 3 of 4): Procedure MI_USSD_HLR
2140
3GPP
2141 Release 4
685
3GPP TS 29.002 V4.17.0 (2006-06)
Proc ess MS_INIT_USSD_HLR
Fig ure 2 2.9 .4/ 1: Ha n dling of mo b ile in tiate d US SD at H LR .
22.9.4_1.4(4)
W ait _fo r_ us sd n _cnf
MA P_U N S T'D _ SS_ N OTIF Y _ cnf
Re ce iv e _ erro r_fro m_ VLR
S ectio n 22. 11
R ec eive_ e rro r_ from _ n ext_ no de
Se ctio n 2 2.1 1
MA P_U N S T' D _ SS_ N OTIFY _ rs p
Set U E = Syste m Fa ilur e
S et UE = S yst em Fa ilu re
MA P_ D ELI MITE R_ req
MAP _U N ST'D_ SS_ N OT IFY_ rsp
M AP_ PR OC ES S_ U N ST'D_ SS _ R EQ U ES T_rsp
W ait _fo r_ pu ssd _cnf
Sh eet 3
MAP _ CL OSE_ re q
M AP_ C LO S E_ req
NU LL
N U LL
W ait _fo r_ us sd r_cn f
MA P_U N S T'D _ SS_ R EQU ES T_ cnf
Re ce iv e _ erro r_fro m_ VLR
S ectio n 22. 11
R ec eive_ e rro r_ from _ n ext_ no de
Se ctio n 2 2.1 1
MA P_U N S T' D _ SS_ R EQU ES T_ rs p
Set U E = Syste m Fa ilur e
S et UE = S yst em Fa ilu re
MA P_ D ELI MITE R_ req
MAP _U N ST'D_ SS_ RE Q U EST_ rsp
M AP_ PR OC ES S_ U N ST'D_ SS _ R EQ U ES T_rsp
W ait _fo r_ pu ssd _cnf
Sh eet 3
MAP _ CL OSE_ re q
M AP_ C LO S E_ req
NU LL
N U LL
4841
4842
Figure 22.9.4/1 (sheet 4 of 4): Procedure MI_USSD_HLR
4843
22.9.5 Procedures in the gsmSCF/secondary HLR
4844 The Mobile initiated USSD Procedure in the gsmSCF/secondary HLR starts by the gsmSCF/secondary HLR receiving a 4845 MAP-OPEN service indication from the HLR. 4846 Once a MAP dialogue is established, the gsmSCF/secondary HLR may handle the 4847 MAP_PROCESS_UNSTRUCTURED_SS_REQUEST from the HLR.
2142
3GPP
2143 Release 4
686
3GPP TS 29.002 V4.17.0 (2006-06)
4848 The gsmSCF/secondary HLR shall transfer the message to the local application. 4849 The gsmSCF/secondary HLR may subsequently receive one or more requests from the application which correspond to 4850 the MAP_UNSTRUCTURED_SS_REQUEST or MAP_UNSTRUCTURED_SS_NOTIFY indications. These shall be 4851 sent transparently to the HLR. When a confirmation is received from the HLR this shall be returned to the application. 4852 When the gsmSCF/secondary HLR receives the result of the original operation from the application then it shall pass 4853 this to the HLR and initiate release of the CM connection. 4854 Error Handling 4855 Both the HLR and the USSD Application may initiate release of the MAP service at any time. This is handled as shown 4856 in the diagrams. 4857 The procedure in the gsmSCF and secondary HLR is shown in figure 22.9.5/1.
2144
3GPP
2145 Release 4
687
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess M S_INIT _U SSD_ gsmSC F_ secon da ry_H LR
Han d lin g of Mo bil e Initia ted USS D at the gsmS CF o r secon da ry H LR Si gn als to /fro m th e le ft a re to /fr om the HL R; Si gn als to /fro m th e righ t a re to /fr om the US SD ap plica tio n NUL L
1(1 )
MA P_ NOTIC E _ind MA P_CL OS E _req
MAP- P-AB ORT_ ind MAP_ U_ AB ORT_ ind MAP_ CL OSE _in d
Re cei ve_ O pen_ ind OK W ait_ for_ serv ice_ ind
Sectio n 25 .1 Erro r NUL L Vr P erform M AP V r di alogu e
SS _R el ease
MA P_ PROC ES S_ UNS T'D_SS _ REQ UE ST_i nd US_PROCESS_ UNST'D_ SS_ REQUES T_req W ai t for USS D Ap pl. US_ P RO CE SS_ UNS T'D_SS _ REQ UE ST_c nf MAP_ PROC ESS_ UNST'D_ SS_ REQUES T_r sp MAP_ CL OSE _ re q
NULL
NUL L
US_ Rel ease
US_UN ST'D_ SS_ NOTIFY_ ind
US_UN ST'D_ SS _REQUE S T_i nd
MA P_U_ ABO RT_ req
MA P_ UNST'D_ SS_ NOTIFY _r eq
MA P_UNS T'D_ SS_ REQUE ST_i nd
NUL L
MA P_ DEL IMITER_req
MA P_ DEL IMITER_r eq
NUL L
W ai t_ for_ us sd n_ cn f MAP_ UNST'D _S S_NOTIFY _cn f US_ UN ST'D _SS _NO TIFY _r sp W ai t_ for _ USS D_A p pl.
W ait_for_ ussd r_c nf
MAP_ UNS T'D _S S _NOTIFY _cn f US_ UN ST'D _S S_NOTIFY_ rsp W ai t_ for_ USS D_App l.
US_ Rel ea se MA P_ U_ ABO RT _req NUL L
US_ Rel ease
MA P_U_ ABO RT_ req
NULL
4858
4859
Figure 22.9.5/1 Process MS_INIT_USSD_gsmSCF_secondary_HLR
2146
3GPP
2147 Release 4
688
3GPP TS 29.002 V4.17.0 (2006-06)
4860 4861
22.10 Network initiated USSD procedure
22.10.1 General
4862 The procedure supports supplementary service signalling procedures which can allow PLMN specific services to be 4863 introduced. 4864 The message flow for the procedure can be found in 3GPP TS 23.090 [34]. 4865 The following services may be used: 4866 4867 4868 4869 4870 4871 4872
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
(defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 8 and 25); (defined in clauses 12 and 25).
4873 At least one of the following services will certainly be used, and both may be used: 4874 4875
MAP_UNSTRUCTURED_SS_REQUEST MAP_UNSTRUCTURED_SS_NOTIFY
(defined in clause 11); (defined in clause 11).
4876
22.10.2 Procedure in the MSC
4877 The procedure may be invoked either by the VLR or by a USSD application local to the MSC. They may start by using 4878 either the MAP_UNSTRUCTURED_SS_REQUEST or MAP_UNSTRUCTURED_SS_NOTIFY service. If the request 4879 is initiated by a local USSD application then the MSC will open a dialogue with the VLR. 4880 In both cases the MSC will initiate a CM connection to the MS (using the page or search macros defined in 4881 clause 25.3). Once the connection is successfully established the message received from the VLR or USSD application 4882 will be sent to the MS using the mapping specified in 3GPP TS 29.011 [59]. 4883 Following transfer of the message the MSC will wait for a confirmation from the MS. This will be sent to the VLR or 4884 USSD application as appropriate. 4885 Following this, the MSC may receive further uses of the MAP_UNSTRUCTURED_SS_REQUEST or 4886 MAP_UNSTRUCTURED_SS_NOTIFY services, or may receive an indication to release the connection to the MS. 4887 In the event of an error, the connection to the MS shall be released, and the MAP process with the VLR shall be aborted 4888 as shown in the diagram. 4889 The procedure in the MSC is shown in figure 22.10.2/1.
2148
3GPP
2149 Release 4
689
3GPP TS 29.002 V4.17.0 (2006-06)
Process N W _IN IT_U SSD_M SC
F ig ure 22 .10 .2/ 1: H and ling of network init iat ed US S D in MS C
22.1 0.2_1.1(4)
NU LL
Receive_ O pen_ ind
Fro m V LR S ect ion 25 .1
N ULL
OK W ait _for_ P aging
E rror, V 1
NU LL
Fro m V LR
M AP_ N O TI CE _ ind
F rom V LR
MA P _ U_A B O R T_ind MA P _ P _A B O RT_ ind MA P _CL O S E _ ind
To V LR
M AP_ C LO S E _ r eq
N ULL
P age_ MS C
S ect ion 2 5.3
S earc h_For_ MS _MS C
S ec tion 25 .3
N u ll
E rror
OK
NU LL
MAP_ CLO S E _ req
To V LR
P roces s_ A c ces s_ Requ es t_ MS C
S ec tion 25. 4
NU LL
OK
E rror
W ait _f or_ us sd _ ind
N ULL
4890
4891
Figure 22.10.2/1 (sheet 1 of 4): Procedure NI_USSD_MSC
2150
3GPP
2151 Release 4
690
3GPP TS 29.002 V4.17.0 (2006-06)
Process N W _IN IT_U SSD_M SC
F ig ure 22 .10 .2/ 1: H and ling of network init iat ed US S D in MS C
22.1 0.2_1.2(4)
W ait _for_ US S D _ind
A rrows t o left are t o M S , arrows t o right are t o V LR u nless ot herwis e s tat ed.
Receive_ E rrors _MS C
M A P _UN S T'D_ S S _NO TI FY _ ind
MA P _ UNS T'D_ S S _RE Q UE S T_ ind
NU LL
A _ UN S T'D _ S S _NO TI FY _ req
A _U NS T'D_ S S _RE Q UE S T_ req
S ect ion 22. 11
W ait _f or_ us sd n_cnf
W ait _for_ uss dr_c nf
A _ UN S T'D _ S S _NO TI FY _ c nf
R ec eive_ E rrors _M S C
A _U NS T'D_ S S _RE Q UE S T_ cnf
Receive_ E rrors _MS C
M A P _UN S T'D_ S S _NO TI FY _ rs p
N ULL
MA P _ UNS T'D_ S S _RE Q UE S T_ rsp
NU LL
M AP_ DE L IM IT E R_ req
S ec tion 22. 11
MA P _ DE LI MI TE R_ req
S e ct ion 22. 11
W ait _f or_ U S S D_ ind
W ait _for_ US S D_in d
4892
4893
Figure 22.10.2/1 (sheet 2 of 4): Procedure NI_USSD_MSC
2152
3GPP
2153 Release 4
691
3GPP TS 29.002 V4.17.0 (2006-06)
Process N W _IN IT_U SSD_M SC
F ig ure 22 .10 .2/ 1: H and ling of network init iat ed US S D in MS C
22.1 0.2_1.3(4)
N ULL
Receive_ O pen_c nf
Fro m V LR S ec t ion 25
U S _O pen_ T rans ac t ion
S ignal from local U S S D applic at ion t hat it wis hes to op en a t ransac tion
OK W ait _for_ P aging_2
E rror, v 1
MA P _ O P E N_req MA P _ DE LI M I TE R_req
NU LL
To V LR
Fro m V LR
M AP_ N O TI CE _ ind
F rom V LR
MA P _ U_A B O R T_ind MA P _ P _A B O RT_ ind MA P _CL O S E _ ind
To V LR
M AP_ C LO S E _ r eq
P age_ MS C
S ect ion 25 .3
S earc h_For_ MS _MS C
S ec tion 25.3
N u ll
E rror
OK
MAP_ CLO S E _ req
To V LR
P roces s_ A c ces s_ Requ es t_ MS C
S ec tion 25.4
US _ Release
To local US S D ap plic ation
OK MA P _ C LO S E _ req
E rror US _ Release To local US S D ap plic ation
To V LR
NU LL W ait _f or_ U S S D_ A ppl NU LL
4894
4895
Figure 22.10.2/1 (sheet 3 of 4): Procedure NI_USSD_MSC
2154
3GPP
2155 Release 4
692
3GPP TS 29.002 V4.17.0 (2006-06)
Process N W _IN IT_U SSD_M SC
F ig ure 22 .10 .2/ 1: H and ling of network init iat ed US S D in MS C
22.1 0.2_1.4(4)
W ait _for_ US S D _A pp l
A rrows t o left are t o MS , arrows to right are to U S S D ap plic ation u nles s otherwis e st ated.
U S _U NS T'D_ S S _NO TI FY _ ind
US _ UN S T'D _ S S _RE Q UE S T_ ind
A _ UN S T'D _ S S _NO TI FY _ req
A _U NS T'D_ S S _ RE Q UE S T_ req
W ait _f or_ us sd n_cnf _2
W ait _for_ uss dr_c nf_2
A _ UN S T'D _ S S _NO TI FY _ c nf
A _U NS T'D_ S S _ RE Q UE S T_ cnf
U S _U NS T'D_ S S _NO TI FY _ rs p
US _ UN S T'D _ S S _RE Q UE S T_ rsp
W ait _f or_ U S S D_ A ppl
W ait _for_ US S D _ A pp l
US _ Release
A _CM_ S E RV _ RE L
US _ R eleas e
A _C M_ S E R V _RE L
US _ Release
A _ CM_ S E RV _ RE L
A _ CM_ RE L_ CO MP
US _ Releas e
A _C M_ R E L_CO M P
US _ R elea se
A _CM_ RE L _ CO MP
US _ Releas e
NU LL
N UL L
NU LL
4896
4897
Figure 22.10.2/1 (sheet 4 of 4): Procedure NI_USSD_MSC
2156
3GPP
2157 Release 4
693
3GPP TS 29.002 V4.17.0 (2006-06)
4898
22.10.3 Procedure in the VLR
4899 The procedure may be invoked either by the HLR or by a USSD application local to the VLR. They may start by using 4900 either the MAP_UNSTRUCTURED_SS_REQUEST or MAP_UNSTRUCTURED_SS_NOTIFY service. 4901 4902 4903 4904
In both cases the VLR will first initiate a MAP dialogue with the MSC. When the indication for the unstructured SS request or notify is received then the macro Start_USSD_VLR will be used to page the MS and open a CM connection. Once the CM connection is successfully established the indication received from the HLR or USSD application will be sent to the MSC.
4905 Following transfer of the message the VLR will wait for a confirmation from the MSC. This will be sent to the HLR or 4906 USSD application as appropriate. 4907 Following this, the VLR may receive further uses of the MAP_UNSTRUCTURED_SS_REQUEST or 4908 MAP_UNSTRUCTURED_SS_NOTIFY services, or may receive a MAP_CLOSE_ind. 4909 In the event of an error, the MAP process with the MSC shall be released, and if necessary the MAP process with the 4910 HLR shall be aborted as shown in the diagram. 4911 The procedure in the VLR is shown in figure 22.10.3/1. 4912 MSC Initiated USSD 4913 If a USSD application in the MSC wishes to use the network initiated USSD procedure, and a connection to the MS 4914 does not exist then it shall open a dialogue to the VLR. This dialogue will automatically lead to the VLR performing 4915 page and search using the macro Start_USSD_VLR. 4916 Macro Start_USSD_VLR 4917 This macro is used to initiate a CM connection with the MS for transfer of network initiated unstructured SS data. 4918 It first checks for correct data in the VLR. If a problem is found then "Err" is returned. 4919 A page or search procedure (as appropriate) will then be used to contact the MS. Following successful page or search 4920 the macro Process_Access_Request_VLR specified in clause 25.4 will be used to handle the CM connection 4921 establishment. 4922 The macro is shown in figure 22.10.3/2.
2158
3GPP
2159 Release 4
694
3GPP TS 29.002 V4.17.0 (2006-06)
Process N W _IN IT_U SSD_VLR
F ig ure 2 2.10 .3/ 1: H and ling of network init iat ed US S D at V LR A rrows to lef t are to MS C , A rrows to rig ht are to H LR unles s ot herwis e st ated.
22.1 0.3_1.1(4)
MA P _ O P E N_req MA P _ D E LIM I TO R_req
NU LL
R ec eive_ O pen_ C onfirm
S ect ion 25.1 E rror, V 1
M A P _U_ A B O RT_req
Receive_ O pen_ ind
From H LR S ect ion 25 .1
OK N ULL W ait _for_ US S D _ind 1
OK
E rror, V 1
NU LL
From H LR
M AP_ N O TI CE _ ind
F rom HLR
MA P _U _A B O R T_ind MA P _P _A B O RT_ind MA P _C LO S E _ ind
To H LR
M AP_ C LO S E _ req
MA P _U NS T'D_ S S _N O TI FY _ ind
MA P _UN S T'D_ S S _R E Q UE S T_ ind
N ULL
S tart_ US S D_ V LR
S t art _US S D_ V LR
OK MA P _U NS T'D_ S S _N O TIF Y_ req
Loc al E rr
E rr M AP_ C LO S E _ re q
OK MA P _UN S T'D_ S S _R E Q UE S T_ req
Loc al E rr
E rr MA P _ CL OS E _ req
MA P _ DE LI MI TE R_ req
S e t E rror
MA P _ DE L IMI TE R_ req
S et E rror
W ait _for_ uss dn_c nf
MA P _ U NS T'D_ S S _N O TIF Y_ rsp
W ait_f or_ us sd r_ cnf
MA P _ UN S T'D _ S S _R E Q UE S T_ rsp
S heet 2
NU LL
S h ee t 2
N ULL
4923
4924
Figure 22.10.3/1 (sheet 1 of 4): Procedure NI_USSD_VLR
2160
3GPP
2161 Release 4
695
3GPP TS 29.002 V4.17.0 (2006-06)
Process N W _IN IT_U SSD_VLR
F ig ure 2 2.10 .3/ 1: H and ling of network init iat ed US S D at V LR A rrows to lef t are to MS C , arrows t o rig ht are to HLR unles s ot herwise st at ed.
22.1 0.3_1.2(4)
W ait _for_ us sd _or_ close
MA P _ CL OS E _ ind
MA P _UN S T'D_ S S _NO TI FY _ ind
MA P _ UNS T'D_ S S _RE Q UE S T_ ind
MA P _ CL OS E _ req
MA P _UN S T'D_ S S _NO TI FY _ req
MA P _U NS T'D_ S S _ RE Q UE S T_ req
NU LL
MA P _ DE L IM IT E R_ req
MA P _ DE L IMI TE R_ req
W ait _f or_ us sd n_cnf
W ait _for_ uss dr_c nf
MA P _UN S T'D_ S S _NO TI FY _ c nf
Receive_ E rror_at _ V LR
MA P _U NS T'D_ S S _ RE Q UE S T_ cnf
R ec eive_ E rror_at_ V LR
MA P _UN S T'D_ S S _NO TI FY _ rsp
N ULL
MA P _ UNS T'D_ S S _RE Q UE S T_ rsp
NU LL
MA P _ DE L IM IT E R_ req
S ec tion 2 2.9 .3
MA P _ DE LI MI TE R_ req
S ection 22. 9.3
W ait _for_ uss d_or_c los e
W ait _for_ us s d_or_ close
Receive_ error_ from_ HLR
Figure 22.11 .2/3
Rec eiv e_ error_ from_ MS C e rr M A P _U_ A B O RT_req
F iguur 22.11. 2/ 2
NU LL
4925
4926
Figure 22.10.3/1 (sheet 2 of 4): Procedure NI_USSD_VLR
2162
3GPP
2163 Release 4
696
3GPP TS 29.002 V4.17.0 (2006-06)
Process N W _IN IT_U SSD_VLR
F ig ure 2 2.10 .3/ 1: H and ling of network init iat ed US S D at V LR A rrows to lef t are to MS C , arrows to rig ht are to US S D applic ation unles s ot herwis e st at ed.
22.1 0.3_1.3(4)
NU LL
US _O pen_ Transac tion
S ignal f rom loc al US S D ap pli cation that it wis hes to op en a t ransac tion
Receive_ O pen_ ind
From M S C S ect ion 25 .1
MA P _ O P E N_req MA P _ D E LIM IT E R_req
OK S tart _US S D_ V LR
E rror, V 1
R ec eive_ O pen_ C onfirm
O K , E rr S ect ion 25. 1 US _ R eleas e E rror, V 1 Loc al E rr MA P _ CL O S E _ req
OK
W ait
N ULL NU LL
US _ UN S T'D _ S S _N O TI FY _ ind
U S _U NS T'D_ S S _R E Q UE S T_ ind
S tart_ US S D_ V LR
S t art _US S D_ V LR
OK MA P _U NS T'D_ S S _N O TIF Y_ req
Loc al E rr
E rr M AP_ C LO S E _ re q
OK MA P _UN S T'D_ S S _R E Q UE S T_ req
Loc al E rr
E rr MA P _ CL OS E _ req
MA P _ DE LI MI TE R_ req
S e t E rror
MA P _ DE L IMI TE R_ req
S et E rror
W ait _for_ uss dn_c nf_ 2
US _U NS T'D_ S S _N O TIF Y_ rsp
W ait_f or_ us sd r_ cnf_2
US _UN S T'D_ S S _R E Q UE S T_ rsp
S heet 4
NU LL
S h ee t 4
N ULL
4927
4928
Figure 22.10.3/1 (sheet 3 of 4): Procedure NI_USSD_VLR
2164
3GPP
2165 Release 4
697
3GPP TS 29.002 V4.17.0 (2006-06)
Process N W _IN IT_U SSD_VLR
F ig ure 2 2.10 .3/ 1: H and ling of network init iat ed US S D at V LR A rrows to lef t are to MS C , arrows to rig ht are to US S D applic ation unles s ot herwis e st at ed.
22.1 0.3_1.4(4)
W ait _for_ US S D _A pp l
U S _U NS T'D_ S S _NO TI FY _ ind
US _UN S T'D_ S S _R E Q UE S T_ ind
M A P _UN S T'D_S S _ N O TIF Y _req MA P _DE LI MI TE R _req
MA P _U NS T 'D _S S _ RE Q U E S T_req MA P _D E LI MIT E R_req
W ait _for_ us sd n_c nf_2
W ait_fo r_ uss dr_c nf_2
M A P _UN S T'D_ S S _NO TI FY _ c nf
MA P _ UNS T'D_ S S _RE Q UE S T_ c nf
U S _U NS T'D_ S S _NO TI FY _ rs p
US _UN S T'D_ S S _R E Q UE S T_ rsp
W ait _for_ U S S D_ A ppl
W ait_fo r_ US S D_A pp l
US _ Release
R ec eive_ E rrors_ from _MS C err
U S_ R eleas e
Receive_ E rrors_ from _ MS C err
US _ Release
R ec eive_ E rrors_ from _MS C err
MA P _ CL OS E _ req
US _ Releas e
M A P _U_ A B O RT_req
US _ R eleas e
M A P _U_ A B O R T_re q
US _ Release
NU LL
N ULL
NU LL
4929
4930
Figure 22.10.3/1 (sheet 4 of 4): Procedure NI_USSD_VLR
2166
3GPP
2167 Release 4
698
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition Start_USSD_VLR
Figure 22.10.3/2: Macro to establish a connection to the MS for a network initiated USSD operation.
22.10.3_2.1(2)
Confirmed by HLR? Yes
No Set UE= System Failure
IMSI Detached? No
Yes
Roaming in LA allowed? Yes
No Set UE= Absent Subscriber
Err
4931
4932
Figure 22.10.3/2 (sheet 1 of 2): Macro Start_USSD_VLR
2168
3GPP
2169 Release 4
699
3GPP TS 29.002 V4.17.0 (2006-06)
Ma crodefinition Start_USSD _VLR
F ig ure 22 .10 .3/ 2: Mac ro to est abli sh a c onn ec tion t o th e MS for a network init iat ed U S S D operat ion.
22.1 0.3_2.2(2)
L A I K nown ye s
no
MA P _P A G E _req MA P _D E LIM ITE R_req
S E A R CH_ V LR
S ee s ect ion 21 .3
To MS C OK A bort W ait _for_ par Local E rr E rror A bs ent S ubs criber no P roc es s_ A cc ess _ Reques t_ V LR OK S ect ion 25.4 E rror M A P _P A G E _ c nf S et UE = S ys tem Failu re S et UE = A bsent S ubs criber yes
F rom MS C
OK
E rr
4933
4934
Figure 22.10.3/2 (sheet 2 of 2): Macro Start_USSD_VLR
2170
3GPP
2171 Release 4
700
3GPP TS 29.002 V4.17.0 (2006-06)
4935
22.10.4 Procedure in the HLR
4936 The procedure may be invoked either by a gsmSCF, a secondary HLR or by a USSD application local to the primary 4937 HLR. It may start by using either the MAP_UNSTRUCTURED_SS_REQUEST or 4938 MAP_UNSTRUCTURED_SS_NOTIFY service. 4939 In both cases the primary HLR will first check whether the MS is reachable . 4940 If the MS is reachable, the primary HLR will initiate a MAP dialogue with the VLR and send the message received 4941 from the gsmSCF or secondary HLR or USSD application to the VLR. 4942 Following transfer of the message the primary HLR will wait for a confirmation from the VLR. This will be sent to the 4943 gsmSCF or secondary HLR or USSD application as appropriate. 4944 Following this, the primary HLR may receive further uses of the MAP_UNSTRUCTURED_SS_REQUEST or 4945 MAP_UNSTRUCTURED_SS_NOTIFY services, or may receive a MAP_CLOSE_ind. 4946 In the event of an error, the MAP process with the VLR shall be released and if necessary the MAP process with the 4947 gsmSCF or secondary HLR shall be aborted, as shown in the diagram. 4948 Message Originated by gsmSCF or secondary HLR 4949 If the message is originated by the gsmSCF or a secondary HLR then the primary HLR shall transfer the message 4950 transparently to the VLR. 4951 4952 4953 4954
The primary HLR may subsequently receive one or more MAP_UNSTRUCTURED_SS_REQUEST_ind or MAP_UNSTRUCTURED_SS_NOTIFY_ind indications from the gsmSCF or secondary HLR. These shall be sent transparently to the VLR. When a confirmation is received from the VLR this shall be returned to the next node as appropriate.
4955 When the primary HLR receives a MAP_CLOSE_ind from the gsmSCF or secondary HLR then it shall pass this to the 4956 VLR and close the MAP dialogue. 4957 The procedure in the primary HLR is shown in figure 22.10.4/1 and 22.10.4/2.
2172
3GPP
2173 Release 4
701
3GPP TS 29.002 V4.17.0 (2006-06)
Process NW _INIT_USSD_ HLR
Fig ure 22 .1 0.4 /1 H and ling o f ne tw ork in itiat ed U SSD a t H L R A rrow s to le ft are to V LR , A rrow s to righ t a re to t he ne xt n od e u nle s s o the rwise stat ed .
22.10.4_1.1(5)
N UL L
R ec e iv e_ Ope n _ ind OK
F rom gsm SC F Se e G SM 0 3.7 8 or F ro m Se cond a ry HL R Erro r, v 1
NU L L
W ait _fo r_ U SSD _in d
F rom gsm SC F o r Se con da ry H LR
MAP _ NO T IC E_ in d
Fro m g smS CF or S eco nd ary H L R
M AP_ U _A BOR T_in d MA P_ P_ ABOR T_in d MA P_ CL O SE _in d
T o gsm SC F o r Se con da ry H LR
MAP _ CL OSE_ re q
N UL L MA P_U N S T'D _ SS_ N OTIF Y _ ind MAP _U N ST' D_ SS_ RE Q U EST_ in d
1 pa ge 2
2 pa ge 2
4958
4959
Figure 22.10.4/1 (sheet 1 of 5): Procedure NI_USSD_HLR
2174
3GPP
2175 Release 4
702
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess N W _IN IT _U SSD _H LR
Han d lin g of Ne two rk in itiate d USS D at the HLR sign als to/fr om the le ft ar e to/from th e VLR; sign als to/fr om the right ar e to/from th e next n ode 2
2(5 )
Sta rt_ US SD_ HLR OK
Err
A bo rt
Start_US S D_ HLR OK
Err
A bo rt
MA P_UNST'D_ MAP_ U_ SS_ NOTIFY _ AB ORT_ req rsp MA P_ CLOSE _req NUL L
MA P_UNS T'D_ MAP_U_ SS_ REQ UE ST AB O RT_ req _r sp MA P_ CLO SE _re q NUL L
NUL L
NULL
MA P_O PEN_req, MA P_UNST'D_ SS _NOTIFY_req, MA P_DE LIMITE R_r eq
MA P_O PEN_ req, MA P_UNS T'D_ SS _RE QUEST_ re q , MA P_DELIMITER_req
Rec eive_ Open_ cnf
Se ction 25.1
Re ceive _ Op e n_ cnf OK
Sectio n 25 .1
E rro r, Vr
OK
E rror, Vr MA P_U_ ABO RT_ req MA P_U_ ABO RT_ req
NUL L
NULL
W ait_ for_ us sd n_ cn f
Sh eet 3
W ait_ for_ ussd r_cn f
She et 3
4960
4961
Figure 22.10.4/1 (sheet 2 of 5): Procedure NI_USSD_HLR
2176
3GPP
2177 Release 4
703
3GPP TS 29.002 V4.17.0 (2006-06)
Process NW _INIT_USSD_ HLR
Fig ure 22 .1 0.4 /1 H and ling o f ne tw ork in itiat ed U SSD a t H L R A rrow s to le ft are to V LR , A rrow s to righ t a re t o th e ne x t no d e u nle s s o the rwise stat ed .
22.10.4_1.3(5)
W ait _fo r_ us sd _ or_clo se
MA P_ C LOSE _ ind
Re ce ive _ er ror_ from _n ext_ no de
Re ce iv e _ erro r_ fro m_ VL R
M AP_ U N ST'D _ S S_ N OTIFY_ in d
M AP_ UN ST 'D _ SS _R EQ UE ST _ in d
MA P_ C LOSE _ re q
MAP _U _ ABO RT _ re q
MAP _U _ ABO RT_ re q
M AP_ U N ST'D _ S S_N OTIF Y_ re q
M AP_ UN S T 'D _ SS _R EQ UE ST_ r eq
M AP_ D EL IM ITER _ re q
M AP_ D EL IMI T ER _ r eq
Sect io n 22. 11
N UL L
W a it_ for_ u ssdn _ cn f
W a it_f or_ u ssdr_c n f
Sec tion 22 .11
Re ce ive _ error _f ro m_ ne xt_n od e
Re ce iv e _ erro r_fro m_ VLR
M AP_ U N ST'D _ S S_N OTIF Y_ cn f
M AP_ UN S T 'D _ SS _R EQ UE ST_ c nf
R ece iv e_ e rr or_ from _ VL R
R ec e ive _ error _f ro m_ ne xt_ nod e
MAP _U _ ABO RT _ re q
Set U E = Syste m Fa ilur e
M AP_ U N ST'D _ S S_ N OTIFY_ rs p
M AP_ UN ST 'D _ SS _R EQ UE ST _ rsp
Se t U E = Syst em Failu re
MA P_U _ ABO R T_ re q
NU L L
MAP _U N ST'D_ SS_ N OT IFY_ rsp
M AP_ D EL IM ITER _ re q
M AP_ D EL IMI T ER _ req
MA P_ UN S T'D _ SS _R EQ UE ST_ rs p
N UL L
MAP _ CL OSE_ re q
W a it_ for_ u s sd_ o r_ c lose
W a it_f or_ u ssd_ or _ close
MA P_ C LOS E_ req
NU LL
N UL L
4962
4963
Figure 22.10.4/1 (sheet 3 of 5): Procedure NI_USSD_HLR
2178
3GPP
2179 Release 4
704
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess N W _IN IT _U SSD _H LR
Han d lin g of Ne two rk in itiate d USS D at the HLR
4(5 )
sign als to/fr om the le ft ar e to/from th e VLR; sign als to/fr om the right ar e to/from th e USSD a pplic atio n
NUL L
US_ UN ST'D_ SS _N O TIFY_ ind MS re ach able Yes
US_ UN ST'D_ SS_ REQ UE ST_ ind MS re ach ab le Yes
No Set er ror = MS no t reac ha ble US_ UN ST'D_ SS_ NOTIFY _ rsp NUL L
No S et er ror = MS no t re ac hable US_UN ST'D_ SS _REQUE S T_ rsp NUL L
MA P_O PEN_req MA P_UNST'D_ SS_ NO TIFY_ req MA P_DE LIMITE R_r eq
MAP_O PEN_ req MAP_UNST'D_ SS_ REQ UEST_req MAP_DE LIMITE R_req
Re cei ve_ Ope n_ cn f OK
Se ction 25
Re cei ve_ O p en_cn f OK
Se ction 25
E rror, Vr
Erro r, Vr
W ait_ for_ us sdn _cn f2
W ait_ for_ ussdr_ cnf2
Sh e et 5
US_ Rele ase
She et 5
US_Re le ase
NUL L
NUL L
4964
4965
Figure 22.10.4/1 (sheet 4 of 5): Procedure NI_USSD_HLR
2180
3GPP
2181 Release 4
705
3GPP TS 29.002 V4.17.0 (2006-06)
Process NW _INIT _USSD_HLR
Handling of Network initiated USSD at the HLR W ait_for USSD _Appl US_ Release MAP_ CLOSE_ req NULL W ait_for_ us sdn_cnf2 MAP_UNST'D_ SS_NOTIFY_ cnf US_UN ST'D_ SS_NOTIFY_ ind MAP_UNST'D_SS_ NOTIFY_req, MAP_DELIMITER_req US_UN ST'D_ SS_REQUEST_ ind signals to/from the left are to/from the VLR; signals to/from the right are to/from the USSD applic ation
5(5)
Rec eive_ error_from_ VLR
US_ Release
MAP_U_ ABORT_req US_UN ST'D_ SS_NOTIFY_ rsp W ait_for USSD _Appl
Abort
NULL
NULL
MAP_UNST'D_SS_ REQUEST_req, MAP_DELIMITER_req W ait_for_ ussdr_cnf2 Receive_ error_from_ VLR MAP_UNST'D_ SS_REQUEST_ cnf
US_ Release
MAP_U_ ABORT_req US_UN ST'D_ SS_REQUEST_ rsp W ait_for USSD _Appl
Abort
NULL
NULL
4966
4967
Figure 22.10.4/1 (sheet 5 of 5): Procedure NI_USSD_HLR
2182
3GPP
2183 Release 4
706
3GPP TS 29.002 V4.17.0 (2006-06)
Ma crodefinition Start_USSD_HLR
Fig u re 2 2 .10 . 4/ 2: M ac ro t o ch e ck M S is rea c h ab le a t th e H L R f o r a n etw o rk in itiat ed U S SD o pe ra tio n
22.10.4_2.1(1)
Su bs cribe r kno wn ? y es
no
Lo cat io n kno wn ? y es
no A bo rt
MS P urg ed ? no
yes
MS C A re a Rest rict ed ? no
yes
Ro a m in g Re s tricte d du e to U n su pp o rte d Fe atu re ? no
yes
Set U E = A b se n t S u bs cribe r
OK
E rr
4968
4969
Figure 22.10.4/2: Macro Start_USSD_HLR
4970
22.10.5 Procedure in the gsmSCF and secondary HLR
4971 The procedure is invoked by an USSD application local to the gsmSCF/secondary HLR. It may start by using either the 4972 MAP_UNSTRUCTURED_SS_REQUEST or MAP_UNSTRUCTURED_SS_NOTIFY service. 4973 In both cases the gsmSCF will initiate a MAP dialogue with the HLR and send the message received from the USSD 4974 application to the HLR.
2184
3GPP
2185 Release 4
707
3GPP TS 29.002 V4.17.0 (2006-06)
4975 Following transfer of the message the gsmSCF will wait for a confirmation from the HLR. This will be relayed to the 4976 USSD application.. 4977 Following this, the gsmSCF/secondary HLR may receive further UNSTRUCTURED_SS_REQUEST or 4978 UNSTRUCTURED_SS_NOTIFY requests, or may receive a Release from the USSD application. 4979 In the event of an error, the MAP dialogue with the HLR shall be released as shown in the diagram. 4980 The procedure in the gsmSCF and secondary HLR is shown in figure 22.10.5/1. 4981
2186
3GPP
2187 Release 4
708
3GPP TS 29.002 V4.17.0 (2006-06)
Process NW _INIT _USSD_gsm SCF_secondary_HLR
Handling of network initiated USSD at the gsmSCF and secondary H LR signals to/from the left are to/from the HLR; signals to/from the right are to/from the USSD applic ation NULL
1(2)
UNST'D_SS_ NOTIFY_req
UNST'D_SS_ REQUEST_req
MAP_OPEN_req MAP_UNST'D_SS_NOTIFY_req MAP_DELIMITER_req
MAP_OPEN_req MAP_UNST'D_SS_REQUEST_req MAP_DELIMITER_req
Receive_ Open_Confirm OK
Section 25.1
Receive_ Open_Confirm OK
Section 25.1
Error, Vr
Error, Vr
Abort
Abort
W ait_for_ us sd n_cnf
NULL
W ait_for_ ussd r_c nf
NULL
4982
4983
Figure 22.10.5/1 (sheet 1 of 2): Procedure NI_USSD_gsmSCF_secondary_HLR
2188
3GPP
2189 Release 4
709
3GPP TS 29.002 V4.17.0 (2006-06)
Process NW _INIT _USSD_gsm SCF_secondary_HLR
Handling of network initiated USSD at the gsmSCF and secondary H LR W ait_for_ us sd n_cnf MAP_UNST'D_ SS_NOTIFY_ cnf UNST'D_SS_ NOTIFY_rsp W ait_for_ USSD or Release Release UNST'D_SS _NOTIFY_req UNST'D_SS _REQUEST_req W ait_for_ ussd r_cnf MAP_UNST'D_ SS_REQUEST_ cnf UNST'D_SS_ REQUEST_r sp signals to/from the left are to/from the HLR; signals to/from the right are to/from the USSD applic ation
2(2)
MAP_ CLOSE_req
M AP_UN ST'D_SS_REQUEST _req M AP_DELIM ITER _req MAP_UNST'D_SS_NOTIFY_req MAP_DELIMITER_req W ait_for_ us sd n_cnf W ait_for_ ussd r_c nf
NULL
MAP_ NOTIC E _ind MAP_ CLOSE_req
MAP_P_ABOR T_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind
Abort
NULL
4984
4985
Figure 22.10.5/1 (sheet 2 of 2): Procedure NI_USSD_gsmSCF_secondary_HLR
2190
3GPP
2191 Release 4
710
3GPP TS 29.002 V4.17.0 (2006-06)
4986
22.11 Common macros for clause 22
4987 The following macros are used for the description of more than one of the supplementary service processes described in 4988 clause 22.
4989
22.11.1 SS Password handling macros
4990 Macro Get_Password_MSC 4991 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 4992 the MS back to the VLR. The macro is described in figure 22.11.1/1. 4993 Macro Get_Password_VLR 4994 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 4995 the MSC back to the HLR. The macro is described in figure 22.11.1/2.
2192
3GPP
2193 Release 4
711
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefin ition G ET_PASSW O RD _MSC
F ig ure 22 .11. 1/ 1: Mac ro which relay s a G et P as s word request f rom t he V LR to th e MS and relays th e G etP as sword res ponse from th e MS to t he V L R ,
22.1 1.1_1(1 )
MA P _G E T_ P A S S W O R D_ ind
A _G E T_ P A S S W O R D_ req
W ait _for_ pas sw ord
A _G E T_ P A S S W O R D_ cnf
R ec eive_ errors_ MS C
F igure 22 .11. 2/1
null MA P _G E T_ P A S S W O R D_ rsp
MA P _ DE LI MI TE R_ req
OK
NU LL
4996
4997
Figure 22.11.1/1: Macro Get_PW_MSC
2194
3GPP
2195 Release 4
712
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefin ition G ET_PASSW O RD _VL R
F ig ure 22 .11. 1/ 2: Mac ro which relay a G etP ass word reques t from t he H LR to t he V LR an d relays th e G etP as sword response from th e V LR t o t he H LR ,
22.1 1.1_2(1 )
MA P _G E T_ P A S S W O R D_ ind
From H LR
MA P _G E T_ P A S S W O R D_ req
To MS C
MA P _ DE LI MI TE R_ req
W ait _for_ p as sw ord
MA P _G E T_ P A S S W O R D_ cnf
From MS C
R ec eive_ error_ f rom _H LR
Fig ure 22. 11. 2/3
Receive_ error_ from _M S C err
Figure 22.1 1. 2/ 2
MA P _G E T_ P A S S W O R D_ rsp
To H LR
NU LL
MA P _ DE LI MI TE R_ req
To H LR
OK
4998
4999
Figure 22.11.1/2: Macro Get_PW_VLR
2196
3GPP
2197 Release 4
713
3GPP TS 29.002 V4.17.0 (2006-06)
5000
22.11.2 SS Error handling macros
This macro is used by the MSC to receive signals which should lead to failure if received in any state of a supplementary service process. If the air interface connection is released by the MS, the communication towards the VLR is aborted, and the MSC should return to a stable "NULL" state. If a MAP_NOTICE indication is received from the VLR, or the VLR aborts or unexpectedly closes the connection, then the air interface connection shall be released. The macro is described in figure 22.11.2/1.
5001 Macro Receive_errors_MSC 5002 5003 5004 5005 5006
5007 Macro Receive_error_from_MSC 5008 5009 5010 5011
This macro is used by the VLR to receive signals from the MSC which should lead to failure if received in any state of a supplementary service process. If a MAP_NOTICE indication is received from the MSC, that connection is closed before the only outcome of the macro, "err" is reported back to the calling process. The macro is described in figure 22.11.2/2.
5012 Macro Receive_error_from_HLR 5013 This macro is used by the VLR to receive signals from the HLR which should lead to failure if received in any state of a 5014 supplementary service process. If a MAP_NOTICE indication is received from the HLR, that connection is closed. The 5015 macro is described in figure 22.11.2/3. 5016 Macro Receive_error_from_VLR 5017 5018 5019 5020
This macro is used by the HLR to receive signals from the VLR that should lead to failure if received in any state of a supplementary service process. If a MAP_NOTICE indication is received from the VLR, that connection is closed before the only outcome of the macro, "err" is reported back to the calling process. The macro is described in figure 22.11.2/4.
5021 Macro Receive_error_from_next_node 5022 This macro is used by the primary HLR to receive signals from the gsmSCF or secondary HLR that should lead to 5023 failure if received in any state of a supplementary service process. If a MAP_NOTICE indication is received from the 5024 next node, that connection is closed. The macro is described in figure 22.11.2/5.
2198
3GPP
2199 Release 4
714
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefin ition R ece ive_ errors_MSC
F ig ure 2 2.11 .2/ 1: Mac ro which han dles pos sible error s itu at ions while t he M S C is wait ing for a confirm ation of a sup plem entary s ervic e reques t to t he V LR
22.1 1.2_1(1 )
A _CM_ S E RV _ RE L
M AP_ N O TI CE _ ind
MA P _ C LO S E _ ind
MA P _U _A B O R T_ind , MA P _P _A B O RT_ind
MA P _U_ A B O R T_ req
A pplicat ion p ro cedure cancellat ion
M AP_ C LO S E _ r eq
A _CM_ RE L_ CO MP
5025
5026
Figure 22.11.2/1: Macro Receive_Errors_MSC
2200
3GPP
2201 Release 4
715
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefin ition Re ce ive_ error_from_M SC
F ig ure 22. 11. 2/2 : Macro to r ec eiv e errors from the MS C during su p plem ent ar y s erv ices procedures in th e V LR
22.1 1.2_2(1 )
MA P _ NO TI CE _ ind
F rom MS C
MA P _ U_A B O R T_ind MA P _ P _A B O R T_ ind M A P _CLO S E _ ind from MS C
MA P _ CLO S E _ req
To MS C
err
5027
5028
Figure 22.11.2/2: Macro Receive_Error_from_MSC
2202
3GPP
2203 Release 4
716
3GPP TS 29.002 V4.17.0 (2006-06)
Ma crodefinition Re ceive_error_from_H LR
F ig ure 22. 11. 2/3 : Macro to r ec eiv e errors fr om the H LR while the V LR is waiting fo r a confirm at ion of a supp lement ary s ervice requ es t se nt t o t he H LR
22.1 1.2_3(1 )
M A P _U _A B O RT_ ind M A P _P _A B O R T_ind from HLR
MA P _ N OT ICE _ ind
From H LR
MA P _ C LO S E _ req
To H LR
M A P _U_ A B O R T_ req
To M S C
5029
5030
Figure 22.11.2/3: Macro Receive_Errors_HLR
2204
3GPP
2205 Release 4
717
3GPP TS 29.002 V4.17.0 (2006-06)
Ma crodefinition Receive_error_from_VLR
Fig ure 2 2 .11 .2 / 4: M acro to re ceive er rors f rom th e V LR d urin g sup plem e n tar y se rvice s p ro ced ure s in th e HL R
22.11.2_ 4(1)
M A P_ NO TICE _ in d
Fro m V L R
M A P _ U_ AB O RT_ in d M A P _ P_ A B O RT _in d M A P _C LO SE _ ind f rom V LR
5031
5032
Figure 22.11.2/4: Macro Receive_error_from_VLR
2206
3GPP
2207 Release 4
718
3GPP TS 29.002 V4.17.0 (2006-06)
Macro definition Receive_error_from_next_node
Fig ure 2 2.1 1.2 /5 : M ac ro to re c eive e rr o rs from t he n ext nod e wh ile the HL R is w a it ing for a con firma tion of a sup ple me nta ry service r e qu est s en t t o th e ne xt no d e
22.11.2_5(1)
M AP_U _ AB O RT_ ind MAP _P _A BO R T _in d fr om ne xt n od e
M AP_ N O T I CE _ in d
F rom n ex t nod e
5033
5034
Figure 22.11.2/5: Macro Receive_error_from_next_node
2208
3GPP
2209 Release 4
719
3GPP TS 29.002 V4.17.0 (2006-06)
5035 5036 5037
22.12 Supplementary Service Invocation Notification procedure
22.12.1 General
5038 The Supplementary Service Invocation Notification procedure is used to notify a gsmSCF about the invocation of a 5039 GSM Supplementary Service. 5040 The password registration procedure is shown in figure 22.12.1/1. 5041 The following services may be used: 5042
MSC (1) ------------------------------------------------->
gsmSCF
(2) <-------------------------------------------------
5043
5048
5044 5045 5046 5047
(1) (2)
MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION (MSC to gsmSCF). MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION-ACK (gsmSCF to MSC). MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION (defined in clauses 8 and 25).
Figure 22.12.1/1: Interfaces and services for supplementary service invocation notification
5049
5050 5051 5052 5053 5054 5055 5056 5057
22.12.2 Procedures in the MSC
The supplementary service invocation notification procedure in the MSC is triggered when the requested supplementary service is invoked at the MSC. The MSC notifies the gsmSCF of a supplementary service invocation via the MAPSUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION service. This is sent in a TCAP TC-BEGIN primitive. The MSC then awaits a positive or negative acknowledgement from the gsmSCF to the MAPSUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION. This is received in a TCAP TC-END primitive, and upon receipt the relationship between the MSC and the gsmSCF is terminated. Similarly, the relationship is terminated at the MSC by the sending of or receipt of a TCAP P-ABORT primitive. This is illustrated in figure 22.12.2/1.
2210
3GPP
2211 Release 4
720
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess SS_Invocation_No tify_ MSC
P ro ce ss in t h e M S C to n o tify th e g s m S C F tha t th e u s er has in vo k ed a s u p p lem e nta ry se rv ice (C D , E C T o r M P TY ) Idle
SSIN_M1(1)
S ig na ls to /f ro m t he le ft are to /fro m th e S S ha n dler in the M S C ; sig n als to /f ro m t he rig h t are to /fro m th e gs m S C F
N o tify S S in voca tio n
M A P _ O P E N _ re q , M A P _ S S _ INV O CA T IO N _N O T IFY_ req , M A P _ DE LIM ITE R _ req
R ec e ive _ O pe n_ C n f
S ec t io n 2 4 .1
OK W a it_ Fo r_ S C F_ R esp on se
V r, E rro r A b ort
M A P _ CL O S E _ in d , MA P _ P _ A B O R T_ in d , MA P _ U _ A B O R T_ in d
MAP_ N O T IC E _ in d
Id le
MAP_ C L OSE_ re q
M A P _ S S _ INV O CA T IO N _N O T IFY_ cn f
S et n eg ative res p o nse : S ys te m fa ilu re N o tif y S S inv o catio n n e ga tive re sp o n se
C h ec k_ C o nf irm atio n
S ec t io n 2 4 .2
P ro vid e r error , U s er erro r, D ata e rro r
OK N o tify S S in voca tio n a ck No tify S S invo c at io n n ega tive res po n s e
Id le
Idle
Id le
5058
5059
Figure 22.12.2/1: Process SS_Invocation_Notify_MSC (sheet 1 of 1)
2212
3GPP
2213 Release 4
721
3GPP TS 29.002 V4.17.0 (2006-06)
5060
5061 5062 5063 5064 5065 5066 5067 5068 5069 5070
22.12.3 Procedures in the gsmSCF
Upon receiving notification of the supplementary service invocation via the MAP-SUPPLEMENTARY-SERVICEINVOCATION-NOTIFICATION service, the gsmSCF analyses the received information. If the gsmSCF understands the information sent via the MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION service then it returns a positive acknowledgement to the MAP-SUPPLEMENTARY-SERVICE-INVOCATION-NOTIFICATION, indicating the success of the service. This is returned in a TCAP TC-END primitive, using the basic end procedure. Otherwise, a negative acknowledgement to the MAP-SUPPLEMENTARY-SERVICE-INVOCATIONNOTIFICATION is returned. This is also returned in a TCAP TC-END primitive, again using the basic end procedure. The gsmSCF TCAP service may also choose to abort the relationship to the MSC by sending a TCAP P-ABORT primitive. It will immediately terminate processing of a MAP-SUPPLEMENTARY-SERVICE-INVOCATIONNOTIFICATION should a TCAP P-ABORT primitive be received from the MSC. This is illustrated in figure 22.12.3/1.
2214
3GPP
2215 Release 4
722
3GPP TS 29.002 V4.17.0 (2006-06)
Process SS_Invocation_Notify_gsmSCF
Process in the gsmSCF to receive a notification that an SS (CD, ECT or MPT) has been invoked
SSINSCF1(1)
Signals to/from the left are to/from the VMSC; signals to/from the right are to/from the service logic in the gsmSCF
Idle
Receive_ Open_Ind
Section 24.1
OK Wait_For_ Service_ Indication
Vr, Error
Idle
MAP_P_ ABORT_ind
MAP_SS_ INVOCATION_ NOTIFY_ind
MAP_ NOTICE_ind
Notify SS invocation Idle MAP_ CLOSE_req
Wait_For_ Service_Logic_ Response Idle
Notify SS invocation ack
Notify SS invocation negativeresponse
Set error
MAP_SS_ INVOCATION_ NOTIFY_rsp
MAP_ CLOSE_req
Idle
5071
5072
Figure 22.12.3/1: Process SS_Invocation_Notify_gsmSCF (sheet 1 of 1)
2216
3GPP
2217 Release 4
723
3GPP TS 29.002 V4.17.0 (2006-06)
5073 5074
22.13 Activation of a CCBS request
22.13.1 General
5075 The message flow to activate a CCBS request is shown in figure 22.13.1/1. 5076
VLR MAP_REGISTER_CC_ENTRY ---------------------------------------------------------------> MAP_REGISTER_CC_ENTRY ack <---------------------------------------------------------------
HLR
5078
5077
Figure 22.13.1/1: Message flow to activate a CCBS request
5079
22.13.2 Procedure in the VLR
5080 The MAP process in the VLR to activate a CCBS request is shown in figure 22.13.2/1. The MAP process invokes 5081 macros not defined in this clause; the definitions of these macros can be found as follows: 5082 5083
Receive_Open_Cnf Check_Confirmation
see clause 25.1.2; see clause 25.2.2.
5084 Successful Outcome 5085 5086 5087 5088 5089
When the MAP process receives a CCBS Request message from the CCBS application process in the VLR, it requests a dialogue with the HLR whose identity is contained in the request by sending a MAP_OPEN service request and the necessary information in a MAP_REGISTER_CC_ENTRY service request. The VLR then invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the HLR.
5090 If the MAP process receives a MAP_REGISTER_CC_ENTRY service confirm from the HLR, the MAP process 5091 invokes the macro Check_Confirmation to check the content of the confirm. 5092 If the macro Check_Confirmation takes the OK exit, the MAP process sends a CCBS Request Ack message containing 5093 the information received from the HLR to the CCBS application process in the VLR and returns to the idle state. 5094 Failure of dialogue opening with the HLR 5095 If the macro Receive_Open_Cnf takes the Vr exit or the Error exit, the MAP process sends a CCBS Request Negative 5096 response message to the CCBS application process in the VLR and returns to the idle state. 5097 Error in MAP_REGISTER_CC_ENTRY confirm 5098 If the MAP_REGISTER_CC_ENTRY service confirm contains a user error or a provider error, or the macro 5099 Check_Confirmation indicates that there is a data error, the MAP process sends a CCBS Request Negative response 5100 message to the CCBS application process in the VLR and returns to the idle state. 5101 Abort of HLR dialogue 5102 After the dialogue with the HLR has been established, the MAP service provider may abort the dialogue by issuing a 5103 MAP_P_ABORT indication. In this case, the MAP process sends a CCBS Request negative response to the CCBS 5104 application process in the VLR and returns to the idle state.
2218
3GPP
2219 Release 4
724
3GPP TS 29.002 V4.17.0 (2006-06)
5105 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 5106 dialogue with the HLR, sends a CCBS Request negative response indicating system failure to the CCBS application 5107 process in the VLR and returns to the idle state.
Process Register_CC_Entry_VLR
Figu re 2 2.1 3.2/1 : Proc ess in the VLR to reg ister a CC en try in the HLR
22.13.2_1(1)
Sign als to/from the left ar e to/f rom the CC BS application process in the VLR; sig nals to/fr om the rig ht ar e to/ from th e HLR
Idle
CC BS R equest
MAP_ OPEN _req, M AP_ REG ISTER _CC _ENTRY_ req, MAP_ DEL IM ITER_req
R eceive_ Open_Cnf
See section 25 .1
OK W ait_Fo r_ HLR _R esp onse
Vr, Error CC BS R eque st Negative r esp onse
MAP_REGIST ER _ CC_ ENT RY_ cn f
M AP_P_ ABORT_ ind
M AP_NOTIC E_ ind
Idle
See se ction 25 .2
Che ck_ Conf irm ation
M AP_CLOSE_ re q
OK CCBS Req uest Ack
D ata erro r, Pr ovid er error, U ser erro r CC BS Request Negative re spons e
Idle
5108
5109
Figure 22.13.2/1: Process Register_CC_Entry_VLR
2220
3GPP
2221 Release 4
725
3GPP TS 29.002 V4.17.0 (2006-06)
5110
22.13.3 Procedure in the HLR
5111 Successful outcome 5112 When the MAP process receives a MAP_REGISTER_CC_ENTRY_indication from the co-ordinating process, it sends 5113 a CCBS Request message to the CCBS application process in the HLR, and waits for a response. The request contains 5114 the parameters received in the MAP_REGISTER_CC_ENTRY service indication. 5115 If the CCBS application process in the HLR returns a positive response, the MAP process constructs a 5116 MAP_REGISTER_CC_ENTRY service response, constructs a MAP_CLOSE service request, sends them to the co5117 ordinating process and terminates. 5118 Negative response from HLR CCBS application process 5119 If the CCBS application process in the HLR returns a negative response, the MAP process constructs a 5120 MAP_REGISTER_CC_ENTRY service response containing the appropriate error, constructs a MAP_CLOSE service 5121 request, sends them to the co-ordinating process and terminates.
2222
3GPP
2223 Release 4
726
3GPP TS 29.002 V4.17.0 (2006-06)
Process Register_CC_Entry_HLR
F igure 22.13.3/1: Process in the H LR to handle a reques t to register a CC entry
22.13.3_1(1)
Signals to/fr om the left are to/f rom the VLR via the coordinating pr ocess; signals to/f rom the r ight are to/f rom the CC BS application process in t he HLR Idle
MAP_REGISTER _ CC _ENTR Y_ind
C CBS R equest
W ait_F or_ Application_ Respons e
CCBS Request Negative respons e
C CBS R equest Ack
Set U ser Er ror
M AP_ REGISTER _CC_ENTRY_rsp, M AP_ CLOSE_req
5122
5123
Figure 22.13.3/1: Process Register_CC_Entry_HLR
2224
3GPP
2225 Release 4
727
3GPP TS 29.002 V4.17.0 (2006-06)
5124 5125
22.14 Deactivation of a CCBS request
22.14.1 General
5126 The message flow to deactivate a CCBS request is shown in figure 22.14.1/1. 5127
VLR MAP_ERASE_CC_ENTRY ---------------------------------------------------------------> MAP_ERASE_CC_ENTRY ack <---------------------------------------------------------------
HLR
5129
5128
Figure 22.14.1/1: Message flow to deactivate a CCBS request
5130
22.14.2 Procedure in the VLR
5131 The MAP process in the VLR to deactivate a CCBS request is shown in figure 22.14.2/1. The MAP process invokes 5132 macros not defined in this clause; the definitions of these macros can be found as follows: 5133 5134
Receive_Open_Cnf Check_Confirmation
see clause 25.1.2; see clause 25.2.2.
5135 Successful Outcome 5136 5137 5138 5139 5140
When the MAP process receives a Deactivate CCBS message from the CCBS application process in the VLR, it requests a dialogue with the HLR whose identity is contained in the request by sending a MAP_OPEN service request and the necessary information in a MAP_ERASE_CC_ENTRY service request. The VLR then invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the HLR.
5141 If the MAP process receives a MAP_ERASE_CC_ENTRY service confirm from the HLR, the MAP process invokes 5142 the macro Check_Confirmation to check the content of the confirm. 5143 If the macro Check_Confirmation takes the OK exit, the MAP process sends a Deactivate CCBS Ack message 5144 containing the information received from the HLR to the CCBS application process in the VLR and returns to the idle 5145 state. 5146 Failure of dialogue opening with the HLR 5147 If the macro Receive_Open_Cnf takes the Vr exit or the Error exit, the MAP process sends a Deactivate CCBS 5148 Negative response message to the CCBS application process in the VLR and returns to the idle state. 5149 Error in MAP_ERASE_CC_ENTRY confirm 5150 If the MAP_ERASE_CC_ENTRY service confirm contains a user error or a provider error, or the macro 5151 Check_Confirmation indicates that there is a data error, the MAP process sends a Deactivate CCBS Negative response 5152 message to the CCBS application process in the VLR and returns to the idle state. 5153 Abort of HLR dialogue 5154 After the dialogue with the HLR has been established, the MAP service provider may abort the dialogue by issuing a 5155 MAP_P_ABORT indication. In this case, the MAP process sends a Deactivate CCBS negative response to the CCBS 5156 application process in the VLR and returns to the idle state.
2226
3GPP
2227 Release 4
728
3GPP TS 29.002 V4.17.0 (2006-06)
5157 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 5158 dialogue with the HLR, sends a Deactivate CCBS negative response indicating system failure to the CCBS application 5159 process in the VLR and returns to the idle state.
Process Erase_CC_Entry_VLR
Figu r e 2 2.14.2/1 : P roc ess in the V LR to e ras e a CC entr y in th e HLR
22.14.2_1(1)
Signal s to /fro m the left ar e to/f rom the CC BS ap pli cation proc ess in the V L R; signals to/from the right ar e to/f rom the HLR Idl e
Deactivate CC BS
MA P _O P EN _r eq , MA P _E RA SE _CC _E NT RY _r eq , MA P _DE L IMITE R_ req
R ece ive_ O p en _Cnf
S ee section 25.1
OK W ait_ For_ H LR _R espon se
V r, E rr or De activate CC B S Ne ga tive r esponse
MA P _E R AS E _ CC_ E N TRY _ cnf
M AP _P _ A B O RT_ in d
M AP _ NO TIC E_ ind
Id le
Se e section 25 .2
Check_ Con f ir m ation
M A P_CL OS E _ req
OK
D ata err o r, P rovid er err or, U ser er ro r Deactivate CC BS Negati ve respo ns e
De acti vate CC BS A ck
Idl e
5160
5161
Figure 22.14.2/1: Process Erase_CC_Entry_VLR
2228
3GPP
2229 Release 4
729
3GPP TS 29.002 V4.17.0 (2006-06)
5162
22.14.3 Procedure in the HLR
5163 Successful outcome 5164 When the MAP process receives a MAP_ERASE_CC_ENTRY_indication from the co-ordinating process, it sends a 5165 Deactivate CCBS message to the CCBS application process in the HLR, and waits for a response. The message contains 5166 the parameters received in the MAP_ERASE_CC_ENTRY service indication. 5167 If the CCBS application process in the HLR returns a positive response, the MAP process constructs a 5168 MAP_ERASE_CC_ENTRY service response, constructs a MAP_CLOSE service request, sends them to the co5169 ordinating process and terminates. 5170 Negative response from HLR CCBS application process 5171 If the CCBS application process in the HLR returns a negative response, the MAP process constructs a 5172 MAP_ERASE_CC_ENTRY service response containing the appropriate error, constructs a MAP_CLOSE service 5173 request, sends them to the co-ordinating process and terminates.
2230
3GPP
2231 Release 4
730
3GPP TS 29.002 V4.17.0 (2006-06)
Process Erase_CC_Entry_HLR
F igure 22.14.3/1: Process in the H LR to hand le a request to er ase a C C entry
22.14.3_1(1)
Signals to/fr om the left are to/f rom the VLR via the coor din ating pr ocess; sig nals to/f rom the right are to/f rom the CC BS appli cation pr ocess in the HLR Idle
MAP_ER ASE_ CC _ENTR Y_ind
D eactivate C CBS
W ait_F or_ Application_ Respons e
Deactivate CCBS Negative respons e
D eac tivate CC BS Ack
Se t U ser Error
M AP_ERASE_C C_EN TRY_rsp, M AP_CLOSE_r eq
5174
5175
Figure 22.14.3/1: Process Erase_CC_Entry_HLR
2232
3GPP
2233 Release 4
731
3GPP TS 29.002 V4.17.0 (2006-06)
5176 5177
23
Short message service procedures
23.1 General
5178 The short message service procedures are used to control both mobile originated and mobile terminated short message 5179 transfer. 5180 Four procedures exist for short message services: 5181 5182 5183 5184
mobile originated short message service transfer; mobile terminated short message service transfer; short message alert procedure; short message waiting data set procedure.
5185 The following application context refers to a complex MAP user consisting of several processes: 5186
shortMessageGatewayContext.
5187 This application context needs a co-ordinating process in the HLR. Additionally a Co-ordinator has to be defined for the 5188 mobile originated situation in the MSC, because the A_CM_SERV_REQ message does not distinguish between mobile 5189 originated short message transfer and the short message alert procedures. 5190
NOTE:
A_CM_SERV_REQ message is not used for SMS over GPRS.
5191 5192
23.1.1 Mobile originated short message service Co-ordinator for the MSC
5193 The A_CM_SERV_REQ message (3GPP TS 24.008 [35]) is received from the A-interface containing the CM service 5194 type. This parameter indicates mobile originated short message service. The service 5195 MAP_PROCESS_ACCESS_REQUEST is started. 5196 If the MAP_PROCESS_ACCESS_REQUEST service ends successfully, the MS initiates mobile originated short 5197 message transfer or alerting indication. Depending on the situation, the appropriate process is initiated as follows: 5198 5199 5200
if the A_RP_MO_DATA indication is received, the process MOSM_MSC is initiated (see clause 23.2.1); if the A_RP_SM_MEMORY_AVAILABLE indication is received, the process SC_Alert_MSC is initiated (see clause 23.4.1).
5201 After creation of the user process the Co-ordinator relays the messages between the A-interface and the invoked process 5202 until a request or an indication for dialogue termination is received. 5203 The SMS process Co-ordinator is shown in the figure 23.1/1.
2234
3GPP
2235 Release 4
732
3GPP TS 29.002 V4.17.0 (2006-06)
Process C o_SMS_MSC
F ig ure 23. 1/ 1: The S MS co-ordina ting process in t he MS C.
23.1_1(1)
NUL L
A _C M_ S E RV _ R EQ
P roces s_ A c ces s_ R e q_ MS C E rror OK
F igure 2 5.4/ 1
NU LL
W F_ S E RV I CE _ P RIM I TI V E
A _RE L
A _RP _M O _ DA TA
A _R P _S M _ M E MO R Y_ A V A ILA B L E
MA P _ NO T ICE _ ind
MA P _U _A B O RT_ ind MA P _P _A B O RT_ind MA P _C LO S E _ind
MA P _U_ A B O R T_ind
MO S M_ MS C
F igure 2 3.2 /2
S M _A lert_ M SC
F igure 23. 4/ 4
MA P _ CL OS E _ req
NU LL
A _R P _MO _ DA T A
A _R P _S M_ ME MO RY _ A V A I LA B L E
NU LL
R e lay_inf o
* FR O M P rov ider
A _RE L FR O M M S
* FRO M IW F
* F RO M O F FS P RIN G (MA P )
A _DI S C FR O M O F FS P R IN G
* FR O M O FF S P R ING
- TO O F FS P R IN G
- TO O FF S P RI NG
- TO O FF S P RIN G
- TO P rovider
- TO IW F
- TO IW F
Relay_I nfo
NU LL
Relay_info
N ULL
Relay_I nfo
5204
5205
Figure 23.1/1: Process Co_SMS_MSC
2236
3GPP
2237 Release 4
733
3GPP TS 29.002 V4.17.0 (2006-06)
5206
5207 5208 5209 5210 5211 5212 5213 5214
23.1.2 Short message Gateway Co-ordinator for the HLR
The MAP_OPEN indication opens a dialogue for the short message procedure between the gateway MSC and the HLR when the application context shortMessageGatewayContext is received. If that service is successful, the Co-ordinator can receive the first service primitive from the MAP_PM. Depending on the received primitive, the user process is created as follows: if the MAP_SEND_ROUTING_INFO_FOR_SM indication is received, the process Mobile_Terminated_SM_HLR is created; if the MAP_REPORT_SM_DELIVERY_STATUS indication is received, the process Report_SM_delivery_stat_HLR is created.
5215 After creation of the user process the Co-ordinator relays the messages between the MAP_PM and the invoked process 5216 until a request or an indication for dialogue termination is received. 5217 The SM Gateway Co-ordinator is shown in the figure 23.1/2. 5218 If the Receive_Open_Ind macro takes the Vr exit then HLR shall perform the MAP Vr dialogue. But based on the 5219 subscriber data, handling at the MAP user application level may be performed as described in release 97 : 5220 5221 5222 5223 5224 5225 5226 5227 5228 5229 5230 5231 5232 5233
If the subscriber is not a GPRS subscriber then the behaviour of the HLR shall be the same as described in the corresponding MAP Vr release. If the subscriber is a GPRS subscriber and a non-GPRS subscriber with the option transfer of SM via the MSC when GPRS is not supported in the GMSC then the behaviour of the HLR shall be the same as described in the corresponding MAP Vr release. If the subscriber is a GPRS subscriber and a non-GPRS subscriber with the option transfer of SM via the SGSN when GPRS is not supported in the GMSC or if the subscriber is a GPRS subscriber only then the behaviour of the HLR shall be the same as for the case transfer over GPRS described in MAP release 97, with the following precision: because GMSC does not support MAP release 97, the previous MAP protocol release is used. When the HLR sends the MAP_SEND_ROUTING_INFO_FOR_SM_Resp, the SGSN number is mapped to the MAP parameter MSC number . When the HLR sends the MAP_INFORM_SERVICE_CENTRE_resp, the MNRG status shall be mapped to the MAP parameter mnrf-set . When the HLR receives the MAP_REPORT_SM_DELIVERY_STATUS_Ind, it shall interpret the delivery outcome as a GPRS delivery outcome.
2238
3GPP
2239 Release 4
734
3GPP TS 29.002 V4.17.0 (2006-06)
Pro ces s Co _ S MS _ G a tew ay_ HL R
F ig u re 2 3 .1 /2 : T h e S M S g a te w a y c o o rd i n a ti n g p r o c e s s in th e H L R .
2 3 .1 _ 2 (1 )
NU LL
R e c e iv e _ O p e n _ In d
F ig u r e 2 5 . 1 /1
E rro r
OK
Vr P erf orm Vr d ia lo g u e
N UL L
WF_ S E R V IC E _ P R IM IT I V E
N ULL
MAP _ S E ND _ R O U T I N G _ IN F O _ F O R _ S M _ in d
M A P _R E P O R T _ S M _ D E L IV E R Y _ S T A T U S _ in d
M AP_ N O T IC E _ in d M AP _ U _A B O R T _in d M A P _ P _ A B O R T _ in d M A P _ C L O S E _ in d
M o b il e _ te r m in a t e d _ SM_ HL R
F igur e 2 3 .3 / 6
R e p o rt _ S M _ D e li v e r y _ H L R
F ig u r e 2 3. 5/ 2
M AP_ C LO S E _ re q
MA P _S E ND _ R O U T I N G _ IN F O _ F O R _ S M _ in d
M A P _R E P O R T _ S M _ D E L IV E R Y _ S T A T U S _ in d
N ULL
R e l a y _ in fo
* FRO M P rov ide r
M A P _ P _ A B O R T _ in d * F R O M M A P _ U _ A B O R T _ in d O F F S P R IN G M A P _ C L O S E _in d - TO O F F S P R IN G - TO P r o v id e r - TO P r o vi d e r
M A P _U _A B O R T _re q M A P _ C L O S E _ re q
- TO O F F S P R IN G
R e la y _ In fo
NU LL
R e la y _ i n fo
N ULL
5234
5235
Figure 23.1/2: Process Co_SMS_Gateway_HLR
2240
3GPP
2241 Release 4
735
3GPP TS 29.002 V4.17.0 (2006-06)
5236 5237
23.1.3 Mobile originated short message service Co-ordinator for the SGSN
5238 The MS initiates mobile originated short message transfer or alerting indication. Depending on the situation, the 5239 appropriate process is initiated as follows: 5240 5241 5242
if the A_RP_MO_DATA indication is received, the process MOSM_SGSN is initiated (see clause 23.2.4); if the A_RP_SM_MEMORY_AVAILABLE indication is received, the process SC_Alert_SGSN is initiated (see clause 23.4.5).
5243 After creation of the user process the Co-ordinator relays the messages between the SGSN and the MS, and the invoked 5244 process until a request or an indication for dialogue termination is received. 5245 The SMS process Co-ordinator is shown in the figure 23.1/3.
2242
3GPP
2243 Release 4
736
3GPP TS 29.002 V4.17.0 (2006-06)
Process C o_SMS_SG SN
F ig ure 2 3.1 /3 : T h e SM S co -ord in a tin g pro c es s in the S G S N
23.1_3(1)
N U LL
A _R E L
A _R P_ M O _ DA TA
A _ R P_ S M _ M E M O R Y_ A V A IL A B LE
MA P _ U _ A B O R T _ ind
M O S M_ SGSN
F ig ure 2 3. 2/ 5
S M _A lert_ SGSN
F igu re 23 .4 /9
N UL L
A _R P_ M O _ DA TA
A _ RP _ S M _ M E M O RY _ A V A IL A B LE
R e lay _ in fo
* FRO M P rov ide r
A _R E L FRO M M S
* F ROM IW F
* FR O M O F F S P R IN G (M A P ) - TO P ro vid er
A _D IS C FR O M O F F S P R IN G - TO IW F
* F RO M O F F S P R IN G
- TO O F F S P R IN G
- TO O FFS P RING
- TO O F F S P R IN G
- TO IW F
R e la y_ In fo
NU L L
R e la y_ inf o
N UL L
R e la y_ In fo
5246
5247
Figure 23.1/3: Process Co_SMS_SGSN
2244
3GPP
2245 Release 4
737
3GPP TS 29.002 V4.17.0 (2006-06)
5248 5249
23.2 The mobile originated short message transfer procedure
5250 The mobile originated short message service procedure is used to forward short message from a mobile subscriber to a 5251 Service Centre. The mobile originated short message service procedure is shown in figure 23.2/1.
5252 5253 5254 5255 5256 5257 5258 5259 5260 5261 5262 5263 5264 5265 5266 5267 5268
+-----+ +-----------+ +------+ +-------------+ +----+ MS Servicing VLR Interworking SC MSC or SGSN MSC +-----+ +-----------+ +------+ +-------------+ +----+ 1. + - - - - -> 2. +------------> 3. +<------------ 4. -------------+-------------> 5. + - - - - -> 6. 7. +<- - - - - 8. +<------------+-------------- +< - - - - -
1) 2) 3) 4) 5) 6) 7) 8) (*) Short Message (3GPP TS 24.011 [37]). MAP_SEND_INFO_FOR_MO_SMS (*). MAP_SEND_INFO_FOR_MO_SMS_ACK (*). MAP_MO_FORWARD_SHORT_MESSAGE. Short message (3GPP TS 23.140). Short message Acknowledgement (3GPP TS 23.140). MAP_MO_FORWARD_SHORT_MESSAGE_ACK. Short Message Acknowledgement (3GPP TS 24.011 [37]). Messages 2) and 3) are not used by SGSN.
5280
5269 5270 5271 5272 5273 5274 5275 5276 5277 5278 5279
Figure 23.2/1: Mobile originated short message transfer
5281 In addition the following MAP services are used: 5282 5283 5284 5285 5286 5287 5288 5289 5290
MAP_PROCESS_ACCESS_REQUEST MAP_AUTHENTICATE MAP_SET_CIPHERING_MODE MAP_PROVIDE_IMSI MAP_CHECK_IMEI MAP_FORWARD_NEW_TMSI MAP_TRACE_SUBSCRIBER_ACTIVITY MAP_READY_FOR_SM (*) Those messages are not used by SGSN.
(see clause 8.3); (*) (see clause 8.5); (*) (see clause 8.6); (*) (see clause 8.9); (*) (see clause 8.7); (see clause 8.9); (*) (see clause 9.1); (*) (see clause 12.4).
5291
23.2.1 Procedure in the servicing MSC
5292 Any CAMEL-specific handling defined in this subclause is omitted if the MSC does not support CAMEL control of 5293 MO SMS or if the subscriber does not have a subscription for CAMEL control of MO SMS. 5294 When the MSC receives the short message from the A-interface, it sends a MAP_SEND_INFO_FOR_MO_SMS 5295 request to the VLR and waits for a response. While the MSC is waiting for a response from the VLR: 5296 5297 5298
if the VLR aborts, or prematurely closes, the dialogue, the MSC reports to the gsmSCF that the short message submission has failed and sends an A_RP_ERROR with error cause "Network out of order" to the MS, and the process terminates;
2246
3GPP
2247 Release 4
738
3GPP TS 29.002 V4.17.0 (2006-06)
5299 5300 5301 5302 5303 5304 5305 5306 5307 5308 5309 5310 5311 5312 5313 5314 5315 5316 5317 5318 5319
if it receives a MAP_CONTINUE_CAMEL_SMS_HANDLING indication, it checks the indication. if the indication is badly formed, the MSC sends an A_RP_ERROR with error cause "Network out of order" to the MS and aborts the dialogue with the VLR, and the process terminates; if the indication is OK, the MSC calls the procedure CAMEL_O_SMS_INIT and tests the result. if the result was "SMS_Aborted", the MSC aborts the dialogue with the VLR, and the process terminates; if the result was "Release_SMS", the MSC returns an A_RP_ERROR with an error cause as instructed by the gsmSCF to the MS and aborts the dialogue with the VLR, and the process terminates; if the result was "Redirect SMS", the MSC modifies the data for the submitted short message as instructed by the gsmSCF, sends to the VLR a MAP_SEND_INFO_FOR_MO_SMS request and waits for a response; if the result was "Continue", the MSC sends to the VLR a MAP_SEND_INFO_FOR_MO_SMS request and waits for a response. The handling for this request is shown in the procedure CAMEL_MO_SMS_VLR (see 3GPP TS 23.078 [98]).
if it receives a MAP_SEND_INFO_FOR_MO_SMS confirmation from VLR, it checks the confirmation. if the confirmation includes an error, the MSC reports to the gsmSCF that the short message submission has failed and sends an A_RP_ERROR with the appropriate error cause to the MS, and the process terminates; if the confirmation indicates a successful result, the MSC checks whether the MSC is also the SMS-IWMSC. if the MSC is separate from the SMS-IWMSC, MSC handling continues as described below under the heading "Serving MSC is separate from SMS-IWMSC". if the MSC is also the SMS-IWMSC, the MSC handling continues as described below under the heading "Serving MSC is SMS-IWMSC";
5320 Serving MSC is separate from SMS-IWMSC 5321 The MSC checks whether the MAP_OPEN request and the MAP_MO_FORWARD_SHORT_MESSAGE request can 5322 be sent in a single message signal unit through the lower layers of the protocol. 5323 5324 5325 5326 5327 5328 5329 5330 5331 5332 5333 5334 5335 5336 5337 5338 5339 5340 5341
if the two requests can be grouped in a single TC message, the MSC requests a dialogue with the SMS-IWMSC, including the MAP_MO_FORWARD_SHORT_MESSAGE request; if the dialogue opening is successful, the MSC waits for the response from the SMS-IWMSC; if the macro Receive_Open_Cnf takes the "Error" exit, the MSC reports to the gsmSCF that the short message submission has failed and returns an A_RP_ERROR with cause "Network out of order" to the MS, and the process terminates; if the macro Receive_Open_Cnf takes the "Vr" exit, the MSC handles the dialogue according to the specification for the earlier version of the protocol and checks the result. if the submission was successful, the MSC reports to the gsmSCF that the short message submission was successful and returns an A_RP_ACK to the MS, and the process terminates; if the submission failed, the MSC reports to the gsmSCF that the short message submission has failed and returns an A_RP_ERROR with the appropriate error cause to the MS, and the process terminates.
if the two requests cannot be grouped in a single TC message, the MSC requests a dialogue with the SMSIWMSC, omitting the MAP_MO_FORWARD_SHORT_MESSAGE request; if the dialogue opening is successful, the MSC sends a MAP_MO_FORWARD_SHORT_MESSAGE request to the SMS-IWMSC, and waits for the response from the SMS-IWMSC; if the macro Receive_Open_Cnf takes the "Error" exit, the MSC reports to the gsmSCF that the short message submission has failed and returns an A_RP_ERROR with cause "Network out of order" to the MS, and the process terminates;
2248
3GPP
2249 Release 4
739
3GPP TS 29.002 V4.17.0 (2006-06)
5342 5343 5344 5345 5346 5347 5348 5349 5350 5351 5352 5353 5354 5355 5356 5357 5358
if the macro Receive_Open_Cnf takes the "Vr" exit, the MSC handles the dialogue according to the specification for the earlier version of the protocol, and checks the result. if the submission was successful, the MSC reports to the gsmSCF that the short message submission was successful and returns an A_RP_ACK to the MS, and the process terminates; if the submission failed, the MSC reports to the gsmSCF that the short message submission has failed and returns an A_RP_ERROR with the appropriate error cause to the MS, and the process terminates.
if the MSC receives a MAP_MO_FORWARD_SHORT_MESSAGE confirmation from the SMS-IWMSC, it checks the content of the confirmation; if the confirmation indicates that the submission of the short message was successful, the MSC reports to the gsmSCF that the short message submission was successful and returns an A_RP_ACK to the MS, and the process terminates; if the confirmation indicates that the submission of the short message failed, the MSC reports to the gsmSCF that the short message submission has failed and returns an A_RP_ERROR with the appropriate error cause to the MS, and the process terminates;
if the dialogue with the SMS-IWMSC fails, the MSC reports to the gsmSCF that the short message submission has failed and returns an A_RP_ERROR with cause "Network out of order" to the MS, and the process terminates.
5359 Serving MSC is SMS-IWMSC 5360 The MSC sends an SC_RP_MO_DATA request to the Short Message Service Centre (SMSC), and waits for the 5361 response. 5362 5363 5364 5365 5366 5367 5368
if the MSC receives an error response from the SMSC, it reports to the gsmSCF that the short message submission has failed and returns an A_RP_ERROR with the appropriate error cause to the MS, and the process terminates; if the SMSC aborts the dialogue, the MSC reports to the gsmSCF that the short message submission has failed and returns an A_RP_ERROR with cause "Network out of order" to the MS, and the process terminates; if the MSC receives a positive response from the SMSC, it reports to the gsmSCF that the short message submission was successful and returns an A_RP_ACK to the MS, and the process terminates.
5369 The mobile originated short message service process in the MSC is shown in figure 23.2/2.
2250
3GPP
2251 Release 4
740
3GPP TS 29.002 V4.17.0 (2006-06)
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
5370
5371
Figure 23.2/2 (sheet 1 of 4): Process MO_SM_MSC
2252
3GPP
2253 Release 4
741
3GPP TS 29.002 V4.17.0 (2006-06)
process MO_SM_MSC
Process in the MSC to handle MO shor t 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 See 3GPP TS 23.078
Error
Result?
SMS_Abor ted
Release_SMS 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_r eq MAP_DELIMITER_req
MAP_U_ ABORT_ req
Wait_For_ VLR_Response
5372
5373
Figure 23.2/2 (sheet 2 of 4): Process MO_SM_MSC
2254
3GPP
2255 Release 4
742
3GPP TS 29.002 V4.17.0 (2006-06)
process MO_SM_MSC
Process in the M to handle MO SC 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
Message segm entation needed?
MAP_OPEN_req MAP_MO_FORWARD_SHORT_M ESSAGE_req MAP_DELIMITER_req
MAP_OPEN_req MAP_DELIMITER_req
Receive_ Open_Cnf
Receive_ Open_Cnf OK
OK
Vr Perform MAP Vr dialogue
Error
Error See 3GPP TS 23.078
Vr Perform MAP Vr dialogue
CAMEL_O_ SM S_ FAILURE
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_M ESSAGE_cnf
No Check_ Confirmation OK Provider Error, User Error, Data Error CAMEL_O_ SM S_ FAILURE Submission successful?
Yes
CAMEL_O_ SM S_ SUBMITTED
See 3GPP TS 23.078
See 3GPP TS 23.078
CAMEL_O_ SM S_ SUBMITTED
See 3GPP TS 23.078
Set RP_ERROR
A_RP_ ACK_req
A_RP_ ERROR_req
A_RP_ ACK_req
5374
5375
Figure 23.2/2 (sheet 3 of 4): Process MO_SM_MSC
2256
3GPP
2257 Release 4
743
3GPP TS 29.002 V4.17.0 (2006-06)
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
5376
5377
Figure 23.2/2 (sheet 4 of 4): Process MO_SM_MSC
2258
3GPP
2259 Release 4
744
3GPP TS 29.002 V4.17.0 (2006-06)
5378
23.2.2 Procedure in the VLR
5379 Any CAMEL-specific handling defined in this subclause is omitted if the VLR does not support CAMEL control of 5380 MO SMS. 5381 The process is triggered by a dialogue opening request followed by a MAP_PROCESS_ACCESS_REQUEST including 5382 a CM service type Short Message Service. 5383 If the macro Process_Access_Request_VLR takes the "OK" exit, the VLR waits for a 5384 MAP_SEND_INFO_FOR_MO_SMS indication from the MSC. 5385 5386 5387 5388 5389 5390 5391 5392 5393 5394 5395 5396 5397 5398 5399 5400 5401 5402 5403 5404 5405 5406 5407
If the MSC aborts the dialogue, the process returns to the Null state; if the indication is badly formed, the VLR returns a MAP_SEND_INFO_FOR_MO_SMS response containing the appropriate user error; if the indication is OK, the VLR checks whether the submission of the short message is allowed if MO SMS is not provisioned, VLR returns a MAP_SEND_INFO_FOR_MO_SMS response containing the user error "Teleservice not provisioned"; if the submission of the short message is prevented by Operator Determined Barring of all outgoing calls, the VLR returns a MAP_SEND_INFO_FOR_MO_SMS response containing the user error "Call barred" with barring cause "Operator barring"; if the submission of the short message is prevented by supplementary service barring of all outgoing calls, the VLR returns a MAP_SEND_INFO_FOR_MO_SMS response containing the user error "Call barred" with barring cause "Barring service active"; the VLR calls the procedure CAMEL_MO_SMS_VLR and checks the result. if the result is "Fail", the process returns to the Null state; if the result is "Pass", the VLR continues to check the subscription information.
if the submission of the short message is prevented by Operator Determined Barring (other than barring of all outgoing calls), the VLR returns a MAP_SEND_INFO_FOR_MO_SMS response containing the user error "Call barred" with barring cause "Operator barring"; if the submission of the short message is prevented by supplementary service barring (other than barring of all outgoing calls), the VLR returns a MAP_SEND_INFO_FOR_MO_SMS response containing the user error "Call barred" with barring cause "Barring service active"; if the submission of the short message is allowed, the VLR returns a MAP_SEND_INFO_FOR_MO_SMS response containing the MSISDN of the requesting subscriber..
5408 When the VLR has returned the MAP_SEND_INFO_FOR_MO_SMS response, the process returns to the Null state. 5409 The mobile originated short message transfer process in the VLR is shown in figure 23.2/3.
2260
3GPP
2261 Release 4
745
3GPP TS 29.002 V4.17.0 (2006-06)
process MO_SM_VLR
Process in the VLR to handle a request for information 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, Err or
OK Wait_For_ Service_ Primitive
Process_ Access_ Request_VLR
Error
OK Wait_For_ Info_Request
Null
5410
5411
Figure 23.2/3(sheet 1 of 2): Process MO_SM_VLR
2262
3GPP
2263 Release 4
746
3GPP TS 29.002 V4.17.0 (2006-06)
process MO_SM_VLR
Process in the VLR to handle a request for information 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 SMS provisioned?
Error
Set User Error : Teleser vice not provisioned
Yes Operator barring? No BAOC
Yes SS barring? No BAOC
Set User Error: Call barred (Oper ator 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 (Oper ator 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_r sp MAP_CLOSE_r eq
Null
5412
5413
Figure 23.2/3(sheet 2 of 2): Process MO_SM_VLR
2264
3GPP
2265 Release 4
747
3GPP TS 29.002 V4.17.0 (2006-06)
5414
23.2.3 Procedure in the interworking MSC
When receiving a MAP_OPEN indication primitive that is not associated with any MAP service indication primitive and if the dialogue is accepted, the MAP service-user in the interworking MSC issues a MAP_DELIMITER request primitive in order to trigger the local MAP service-provider to confirm the dialogue. Then a MAP_MO_FORWARD_SHORT_MESSAGE indication shall be received.
5415 This procedure applies only when the IWMSC is not the servicing MSC or SGSN. 5416 5417 5418 5419
5420 When a MAP_MO_FORWARD_SHORT_MESSAGE indication is correctly received, the Interworking MSC invokes 5421 forwarding of the short message to the Service Centre. If invalid data content is detected, an unexpected data value error 5422 or a data missing error is returned to the servicing MSC or SGSN. 5423 The outcome of the procedure with the Service Centre is awaited before a 5424 MAP_MO_FORWARD_SHORT_MESSAGE response is given back to the servicing MSC or SGSN: 5425 5426 5427 5428 5429 5430 5431
if a short message is accepted by the Service Centre, an acknowledgement is sent back to the servicing MSC or SGSN; if the Service Centre is not identified, the SM Delivery Failure error is returned to the servicing MSC or SGSN; if the Service Centre returns an error indication, the SM Delivery Failure error is returned to the servicing MSC with the error cause and any diagnostic information received from the Service Centre; if the short message cannot be forwarded to the Service Centre or the procedure towards the Service Centre fails for some reason, a system failure error is sent to the servicing MSC or SGSN.
5432 The mobile originated short message service transfer in the IWMSC is shown in figure 23.2/4.
2266
3GPP
2267 Release 4
748
3GPP TS 29.002 V4.17.0 (2006-06)
Process MOSM _IW MSC
F ig ure 2 3.2 / 4: T he m o bile o rigina te d s ho rt m es s a ge s e rv ic e p roc e s s in th e IW M S C . W F_ S E R V IC E _ P R I M IT I VE
23.2_4(1)
M A P _U _A B O R T _ in d, M A P_ P _ A BO R T _ in d , M AP _ C LO S E _ in d NU L L MAP_ N O T IC E _ in d
MAP_ D EL IM IT E R _ In d M A P _ F O R W AR D _ _S H O R T _ MAP_ _M E SS A G E _ in d D EL IM IT E R _ Re q
R e c eive _ O pe n _ Ind
OK
E rro r
V1
MAP_ CL O S E _ req
C h ec k _ In di c a tio n
W F_ S ER V IC E _ P R I M I T IV E
OK W F_ S ER V IC E _ P R I M I T IV E P e rf or m _ M A P _V 1 _ D ia log ue Y es 'S C k no w n' No S C _R P _M O _ _ D AT A _ _ re q ' S ET P A R A = U N K N O W N _S C ' 'S E T U E = S M D E LIV E R Y F A ILU R E '
E rr or
NU L L
W A IT _F O R _ C O N F IR M _ F RO M _ S C
M A P_ U _ A B O R T _ in d, M A P_ P _A B O R T _ in d, M AP _ C L O S E _ in d
M AP_ N O T IC E _ in d
S C_R P _ _ A C K _ in d
S C_ RP _ _E R R O R _ _ in d
M AP_ CL O S E _ req
'S E T P A R A = [S C E R R O R V A LU E ]'
'S E T U E = S M D E LIV E R Y F A ILU R E'
SC _A B O R T _ _r e q
MA P _ FO R W A RD _ S H O R T _ M E SS A G E _ rs p M A P _ C L O S E _re q
N UL L
5433
5434
Figure 23.2/4: Process MOSM_IWMSC
2268
3GPP
2269 Release 4
749
3GPP TS 29.002 V4.17.0 (2006-06)
5435
23.2.4 Procedure in the SGSN
5436 Any CAMEL-specific handling defined in this subclause is omitted if the SGSN does not support CAMEL control of 5437 MO SMS, or if the subscriber is not a CAMEL subscriber. 5438 The process is triggered by a short message received from the MS over the Gb interface. 5439 If the MO SMS service is not provisioned, the SGSN returns a Gb_RP_ERROR with error cause "Requested facility not 5440 subscribed", and the process returns to the Null state. 5441 If the MO SMS service is provisioned, the SGSN checks whether Operator Determined Barring of all outgoing calls is 5442 in force. 5443 5444 5445 5446 5447
if Operator Determined Barring would prevent the submission of the short message, the SGSN returns a Gb_RP_ERROR with error cause "Operator determined barring" to the MS, and the process returns to the Null state; if Operator Determined Barring would not prevent the submission of the short message, the SGSN handling continues.
5448 The SGSN calls the procedure CAMEL_O_SMS_INIT and tests the result. 5449 5450 5451 5452 5453 5454
if the result was "SMS_Aborted", the process returns to the Null state; if the result was "Release_SMS", the SGSN returns a Gb_RP_ERROR with an error cause as instructed by the gsmSCF to the MS, and the process returns to the Null state; if the result was "Redirect_SMS", the SGSN modifies the data for the submitted short message as instructed by the gsmSCF, and the MSC handling continues; if the result was "Continue", the SGSN handling continues.
5455 The SGSN checks whether Operator Determined Barring of outgoing calls (other than barring of all outgoing calls) 5456 would prevent the submission of the short message. 5457 5458 5459 5460 5461
if Operator Determined Barring would prevent the submission of the short message, the SGSN reports to the gsmSCF that the short message submission has failed and returns a Gb_RP_ERROR with error cause "Operator determined barring" to the MS, and the process returns to the Null state; if Operator Determined Barring would not prevent the submission of the short message, the SGSN handling continues.
5462 The SGSN checks whether the MAP_OPEN request and the MAP_MO_FORWARD_SHORT_MESSAGE request can 5463 be sent in a single message signal unit through the lower layers of the protocol. 5464 5465 5466 5467 5468 5469 5470 5471 5472 5473 5474 5475 5476 5477 5478
if the two requests can be grouped in a single TC message, the SGSN requests a dialogue with the SMSIWMSC, including the MAP_MO_FORWARD_SHORT_MESSAGE request; if the dialogue opening is successful, the SGSN waits for the response from the SMS-IWMSC; if the macro Receive_Open_Cnf takes the "Error" exit, the SGSN reports to the gsmSCF that the short message submission has failed and returns a Gb_RP_ERROR with cause "Network out of order" to the MS, and the process returns to the Null state. if the macro Receive_Open_Cnf takes the "Vr" exit, the SGSN handles the dialogue according to the specification for the earlier version of the protocol and checks the result. if the submission was successful, the SGSN reports to the gsmSCF that the short message submission was successful and returns a Gb_RP_ACK to the MS, and the process returns to the Null state; if the submission failed, the SGSN reports to the gsmSCF that the short message submission has failed and returns a Gb_RP_ERROR with the appropriate error cause to the MS, and the process returns to the Null state.
if the two requests cannot be grouped in a single TC message, the SGSN requests a dialogue with the SMSIWMSC, omitting the MAP_MO_FORWARD_SHORT_MESSAGE request;
2270
3GPP
2271 Release 4
750
3GPP TS 29.002 V4.17.0 (2006-06)
5479 5480 5481 5482 5483 5484 5485 5486 5487 5488 5489 5490 5491 5492 5493 5494 5495 5496 5497 5498 5499 5500 5501
if the dialogue opening is successful, the SGSN sends a MAP_MO_FORWARD_SHORT_MESSAGE request to the SMS-IWMSC, and waits for the response from the SMS-IWMSC; if the macro Receive_Open_Cnf takes the "Error" exit, the SGSN reports to the gsmSCF that the short message submission has failed and returns a Gb_RP_ERROR with cause "Network out of order" to the MS, and the process returns to the Null state. if the macro Receive_Open_Cnf takes the "Vr" exit, the SGSN handles the dialogue according to the specification for the earlier version of the protocol and checks the result. if the submission was successful, the SGSN reports to the gsmSCF that the short message submission was successful and returns a Gb_RP_ACK to the MS, and the process returns to the Null state; if the submission failed, the SGSN reports to the gsmSCF that the short message submission has failed and returns a Gb_RP_ERROR with the appropriate error cause to the MS, and the process returns to the Null state.
if the SGSN receives a MAP_MO_FORWARD_SHORT_MESSAGE confirmation from the SMS-IWMSC, it checks the content of the confirmation; if the confirmation indicates that the submission of the short message was successful, the SGSN reports to the gsmSCF that the short message submission was successful and returns a Gb_RP_ACK to the MS, and the process returns to the Null state; if the confirmation indicates that the submission of the short message failed, the SGSN reports to the gsmSCF that the short message submission has failed and returns a Gb_RP_ERROR with the appropriate error cause to the MS, and the process returns to the Null state;
if the dialogue with the SMS-IWMSC fails, the SGSN reports to the gsmSCF that the short message submission has failed and returns an A_RP_ERROR with cause "Network out of order" to the MS, and the process returns to the Null state.
5502 The mobile originated short message service process in the SGSN is shown in figure 23.2/5.
2272
3GPP
2273 Release 4
751
3GPP TS 29.002 V4.17.0 (2006-06)
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 MO SM S provi sioned? Yes Yes Operator barring? No Set RP_ERROR: Operator determ ined barring BAOC
CAMEL_O_ SM S_INIT
See 3GPP TS 23.078
Gb_RP_ ERROR_ req
Result?
SM S_Aborted
Release_SM S
Redirect_SMS Modify data according to gsmSCF instructions Yes
Continue
Operator barring? No
BOIC or BOIC-exHC etc
See 3GPP TS 23.078
CAMEL_O_ SM S_FAILURE
Set RP_ERROR according to gsmSCF instructions
Set RP_ERROR: Operator determ ined barring
Set RP_ERROR: Requested facili ty not subscribed
Gb_RP_ ERROR_ req
Gb_RP_ ERROR_ req
Gb_RP_ ERROR_ req
Null
Null
Null
Null
5503
5504
Figure 23.2/5 (sheet 1 of 3): Process MO_SM_SGSN
2274
3GPP
2275 Release 4
752
3GPP TS 29.002 V4.17.0 (2006-06)
process MO_SM_SGSN
Process in the SGSN to handle submission of a short message 1
MO_SM_SGSN2(3)
Signals to/from the left are to/from the UE; signals to/from the right are to/from the HLR Yes
No
Message segm entation needed?
MAP_OPEN_req MAP_MO_FORWARD_SHORT_M ESSAGE_req MAP_DELIMITER_req
MAP_OPEN_req MAP_DELIMITER_req
Receive_ Open_Cnf
Receive_ Open_Cnf
OK
Vr Perform MAP_Vr dialogue
Error
Error See 3GPP TS 23.078
Vr Perform MAP_Vr dialogue
OK
CAMEL_O_ SM S_ FAILURE
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_M ESSAGE_cnf
No Check_ Confirmation Provider Error, User Error, Data Error CAMEL_O_ SM S_ FAILURE Submission successful?
Yes
OK CAMEL_O_ SM S_ SUBMITTED
See 3GPP TS 23.078
See 3GPP TS 23.078
CAMEL_O_ SM S_ SUBMITTED
See 3GPP TS 23.078
Set RP_ERROR
Gb_RP_ ACK_req
Gb_RP_ ERROR_req
Gb_RP_ ACK_req
Null
Null
Null
5505
5506
Figure 23.2/5 (sheet 2 of 3): Process MO_SM_SGSN
2276
3GPP
2277 Release 4
753
3GPP TS 29.002 V4.17.0 (2006-06)
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
5507
5508
Figure 23.2/5 (sheet 3 of 3): Process MO_SM_SGSN
2278
3GPP
2279 Release 4
754
3GPP TS 29.002 V4.17.0 (2006-06)
5509 5510
23.3 The mobile terminated short message transfer procedure
5511 The mobile terminated short message transfer procedure is used for forwarding a short message or several short 5512 messages from a Service Centre to a mobile subscriber. The mobile terminated short message procedure for a single 5513 short message transfer is shown in figure 23.3/1.
5514 5515 5516 5517 5518 5519 5520 5521 5522 5523 5524 5525 5526 5527 5528 5529 5530 5531 5532 5533 5534 5535 5536 5537 5538 5539
+-----+ +---------++------+ +------+ +---------+ +----+ MS Servicing VLR HLR Gateway SC MSCorSGSN MSC +-----+ +---------++------+ +------+ +---------+ +----+ 1. 2. +< - - - - +<---------- 3. +----------> 4. +<--------+--------+----------- 5. +--------> 6. 7. +<-------- +< - - - - 8. + - - - -> 9. +--------> 10. 11. +<-------- +< - - - - 12. + - - - -> 13. +---------+--------+----------> 14. + - - - - >
1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) 13) 14) (*) Short Message (3GPP TS 23.140). MAP_SEND_ROUTING_INFO_FOR_SM. MAP_SEND_ROUTING_INFO_FOR_SM_ACK. MAP_MT_FORWARD_SHORT_MESSAGE. 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.140). Messages 5), 6), 9), and 10) are not used by SGSN.
5558
5540 5541 5542 5543 5544 5545 5546 5547 5548 5549 5550 5551 5552 5553 5554 5555 5556 5557
Figure 23.3/1: Mobile terminated short message service procedures
2280
3GPP
2281 Release 4
755
3GPP TS 29.002 V4.17.0 (2006-06)
5559 The mobile terminated short message procedure for multiple short message transfer is shown in figure 23.3/2.
5560 5561 5562 5563 5564 5565 5566 5567 5568 5569 5570 5571 5572 5573 5574 5575 5576 5577 5578 5579 5580 5581 5582 5583 5584
+-----+ +---------++------+ +------+ +---------+ +----+ MS Servicing VLR HLR Gateway SC MSCorSGSN MSC +-----+ +---------++------+ +------+ +---------+ +----+ < - - - - 1. +<----------2. 3.+----------> <--------+--------+-----------4. 5.--------> <--------6. < - - - -7. 8. - - - -> 9.--------> <--------10. < - - - -11. 12 - - - -> 13.---------+--------+----------> 14.+ - - - - > +< - - - - 15. <--------+--------+-----------16. < - - - -17. 18 - - - -> 19.---------+--------+----------> 20.+ - - - - >
1) 2) 3) 4) 5) 6) 7) 8) 9) Short Message (3GPP TS 23.140). MAP_SEND_ROUTING_INFO_FOR_SM. MAP_SEND_ROUTING_INFO_FOR_SM_ACK. MAP_MT_FORWARD_SHORT_MESSAGE (note 1). 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 (*). 10) MAP_SEND_INFO_FOR_MT_SMS_ACK (*). 11) Short Message (3GPP TS 24.011 [37]). 12) Short Message Acknowledgement (3GPP TS 24.011 [37]). 13) MAP_MT_FORWARD_SHORT_MESSAGE_ACK. 14) Short Message Acknowledgement (3GPP TS 23.140). 15) Short Message (3GPP TS 23.140). 16) MAP_MT_FORWARD_SHORT_MESSAGE (note 2). 17) Short Message (3GPP TS 24.011 [37]). 18) Short Message Acknowledgement (3GPP TS 24.011 [37]). 19) MAP_MT_FORWARD_SHORT_MESSAGE_ACK. 20) Short Message Acknowledgement (3GPP TS 23.140). (*) Messages 5), 6), 9), and 10) are not used by SGSN. NOTE 1: The More Messages To Send flag is TRUE. NOTE 2: The More Messages To Send flag is FALSE.
5611
5585 5586 5587 5588 5589 5590 5591 5592 5593 5594 5595 5596 5597 5598 5599 5600 5601 5602 5603 5604 5605 5606 5607 5608 5609 5610
Figure 23.3/2: Mobile terminated short message procedure for multiple short message transfer
5612 In the multiple short message transfer the service MAP_MT_FORWARD_SHORT_MESSAGE can be used several 5613 times. However, the short message transfer is always acknowledged to the Service Centre before the next short message 5614 is sent. 5615 In addition the following MAP services are used: 5616 5617 5618 5619 5620
MAP_PROCESS_ACCESS_REQUEST MAP_PAGE MAP_SEARCH_FOR_MS MAP_AUTHENTICATE MAP_SET_CIPHERING_MODE
(see clause 8.3); (*) (see clause 8.2); (*) (see clause 8.2); (*) (see clause 8.5); (*) (see clause 8.6); (*)
2282
3GPP
2283 Release 4
756
3GPP TS 29.002 V4.17.0 (2006-06)
5621 5622 5623 5624 5625 5626 5627
MAP_CHECK_IMEI MAP_FORWARD_NEW_TMSI MAP_REPORT_SM_DELIVERY_STATUS MAP_INFORM_SERVICE_CENTRE MAP_TRACE_SUBSCRIBER_ACTIVITY MAP_READY_FOR_SM (*) Those messages are not used by SGSN.
(see clause 8.7); (see clause 8.9); (*) (see clause 12.3); see clause 12.6); (see clause 9.1); (*) (see clause 12.4).
5628
23.3.1 Procedure in the Servicing MSC
5629 When initiating the dialogue with the servicing MSC, the SMS Gateway MSC must provide the IMSI of the subscriber 5630 to whom the short message is directed. 5631 The IMSI can be included either in the Destination Reference of the MAP_OPEN indication received from the SMS 5632 Gateway MSC or in the sm-RP-DA information field of the MAP_MT_FORWARD_SHORT_MESSAGE indication. 5633 When receiving a MAP_OPEN indication primitive that is not associated with any MAP service indication primitive 5634 and if the dialogue is accepted, the MAP service-user in the servicing MSC issues a MAP_DELIMITER request 5635 primitive in order to trigger the local MAP service-provider to confirm the dialogue. 5636 When receiving the first MAP_MT_FORWARD_SHORT_MESSAGE indication from the gateway MSC, the servicing 5637 MSC sends the MAP_SEND_INFO_FOR_MT_SMS request primitive to the VLR, if the MAP service primitive is 5638 accepted and if short message service is supported in the servicing MSC. 5639 The MAP_MT_FORWARD_SHORT_MESSAGE indication primitive is checked by the macro "Check_Indication". If 5640 the received MAP service primitive contains errors, the service is aborted and an unexpected data value error or data 5641 missing error is returned to the GMSC. 5642 If the MSC does not support the short message service, the service is aborted in the servicing MSC and the error 5643 "Facility Not Supported" is returned to the GMSC. 5644 The subscriber identity information that may be included in the MAP_OPEN indication primitive and in the MAP 5645 service indication primitive is checked by the macro "Check_Subscr_Identity_For_MT_SMS" as follows. 5646 5647 5648 5649 5650 5651 5652 5653 5654 5655 5656 5657 5658
If a Destination Reference has been received in the MAP_OPEN indication, an LMSI must be present in the sm-RP-DA information field of the MAP_MT_FORWARD_SHORT_MESSAGE indication. The LMSI shall be included in the sm-RP-DA information field of the MAP_SEND_INFO_FOR_MT_SMS request sent to the VLR; the associated MAP_OPEN request must contain a Destination Reference that carries an IMSI. Otherwise, if the IMSI is included in the sm-RP-DA information field of the MAP_MT_FORWARD_SHORT_MESSAGE indication, it is mapped into the sm-RP-DA information field of the MAP_SEND_INFO_FOR_MT_SMS request that is sent to the VLR. In this case, the IMSI is not accompanied by an LMSI and neither the MAP_OPEN indication received from the gateway MSC nor the MAP_OPEN request sent to the VLR shall include a Destination Reference. If a Destination Reference has been received in the servicing MSC and the sm-RP-DA information field of the MAP_MT_FORWARD_SHORT_MESSAGE indication does not include an LMSI or if no Destination Reference has been received and the sm-RP-DA information field does not cover an IMSI the service is aborted in the servicing MSC and the error "Unexpected Data Value" is returned to the SMS GMSC.
5659 The following responses to the MAP_SEND_INFO_FOR_MT_SMS request may be received from the VLR:
5660
unidentified subscriber or system failure error. The error code is forwarded to the GMSC; absent subscriber error. The absent subscriber_SM error is forwarded to the GMSC with the absent subscriber diagnostic indication set to 'IMSI Detached'; unknown subscriber error. The system failure indication is provided to the GMSC;
2284
3GPP
2285 Release 4
757
3GPP TS 29.002 V4.17.0 (2006-06)
5661 5662 5663 5664 5665
data missing or unexpected data value error. The system failure indication is provided to the GMSC; a provider error or an abort indication. The system failure indication is provided to the GMSC; subscriber busy for MT SMS. The error code is forwarded to the GMSC; paging procedure invocation (see clause 25.3) reporting the successful outcome of the procedure; search procedure invocation (see clause 25.3) reporting the successful outcome of the procedure.
5666 The result of the paging or the search procedure is processed as follows: 5667 5668 5669 5670 5671
if the procedure is completed successfully, the MSC will send the MAP_PROCESS_ACCESS_REQUEST request to the VLR (see clause 25.4); if the procedure is completed successfully, but the MS has no mobile terminated short message transfer capability, the procedure is terminated and SM delivery failure indication with cause "equipment not SM equipped" is provided to the GMSC; if the procedure ends unsuccessfully, the termination of the procedure is awaited from the VLR. The absent subscriber_SM error is forwarded to the GMSC with the absent subscriber diagnostic indication set to 'No Paging Response', but the other error causes are reported as a system failure indication.
5672 If the short message transfer is aborted for any reason, the dialogue with the VLR is aborted. If the procedure with the 5673 VLR is aborted by the VLR or by the provider, a system failure indication is provided to the GMSC. 5674 The unsuccessful outcome of the MAP_PROCESS_ACCESS_REQUEST service is reported by using the system 5675 failure error to the GMSC. 5676 When the service MAP_PROCESS_ACCESS_REQUEST is carried out, the MSC will receive the 5677 MAP_SEND_INFO_FOR_MT_SMS confirmation indicating: 5678 5679 5680
the unsuccessful outcome of the procedure. The error indication received from the VLR is forwarded to the GMSC; the successful outcome of the procedure. The MSC initiates forwarding of the short message to the MS.
5681 If the primitive itself is badly formatted or data is missing, the system failure error is sent to the GMSC. 5682 If forwarding of the short message is initiated, the MSC awaits the result before one of the following responses is sent 5683 back to the GMSC: 5684 5685 5686 5687 5688
an acknowledgement if the short message has been successfully delivered to the mobile subscriber; an SM delivery failure error containing a parameter indicating either of the following: there is a MS protocol error or the MS memory capacity is exceeded; detailed diagnostic information (see clause 7.6.1.4) may also be carried; a system failure error if the delivery procedure is aborted.
5689 If the More Messages To Send flag was FALSE or the service MAP_MT_FORWARD_SHORT_MESSAGE ends 5690 unsuccessfully, the transaction to the gateway MSC is terminated. Otherwise, the servicing MSC waits for the next 5691 short message from the Service Centre. 5692 When receiving the next MAP_MT_FORWARD_SHORT_MESSAGE indication from the gateway MSC the servicing 5693 MSC will act as follows: 5694 5695 5696 5697 5698
if the received primitive contains errors, the unexpected data value error or data missing error is provided to the gateway MSC; if the More Messages To Send flag is FALSE, the servicing MSC will start the short message transfer procedure to the mobile subscriber. The successful or unsuccessful outcome of this procedure is reported to the gateway MSC and the transaction is terminated.
2286
3GPP
2287 Release 4
758
3GPP TS 29.002 V4.17.0 (2006-06)
5699 5700 5701 5702
if the More Messages To Send flag is TRUE, the servicing MSC will start the short message transfer to the mobile subscriber. If the outcome of this procedure is unsuccessful, the reason is reported to the gateway MSC and the procedure is terminated. If the procedure is successful, it is acknowledged to the gateway MSC and more short messages can be received.
5703 The tracing procedure may be activated. It is described in detail in the clause 20. 5704 The mobile terminated short message transfer procedure in the servicing MSC is shown in figures 23.3/3 and 23.3/4. 5705 The page and search procedures are shown in figure 25.3/1 and 25.3/2.
2288
3GPP
2289 Release 4
759
3GPP TS 29.002 V4.17.0 (2006-06)
P rocess MTSM _V MS C
F igu re 23. 3/ 3: T he m ob ile te rm ina te d s hor t m es s a ge s erv ic e p roc e s s in t he M S C N U LL
2 3.3_3.1(3)
R e c ei v e_ O pe n_ In d 'O K ' D e s t_R e f_ rec e ive d 'Y es ' 'S tore _ D e s tina tion _ R e fe ren c e' 'N o'
F ig ure 2 5. 1/ 1
'E rr or'
'V 1' 'P erf orm _ M AP _ V 1_ D ia lo gu e
W A IT _F O R _ S E R V IC E _ P R IM IT IV E
N UL L
N UL L
MAP_ D E LIM I T E R _ In d
M A P _M T _ FO R W A RD _ S HO RT _ MESSAGE
M A P _ U _ A BO R T _ In d , M A P _ P _A B O R T _In d , M A P _ C L O S E_ In d
MAP_ N O T IC E _ In d
MAP_ D E LIM I T E R _ Re q
C h ec k _ I nd ic a tion 'O K '
F ig ure 2 5. 2/ 1
MA P_ C LO SE _R e q ' Erro r'
W A I T _F O R _ S E R V IC E _ P R I M IT IV E 'O K '
M T _S M _ T ra ns fe r _M S C 'A b or t'
F ig ure 2 3. 3/ 4 N UL L ' Erro r'
NU L L M or e_m s g _ to _s e n t 'Ye s ' M A P _F O R W A R D _ S H O R T _ M E SS A G E _ R s p M A P _D E L IM IT E R _ R e q W A IT _F O R _M O R E _ ME S S A G E S M A P _F O R W AR D _ S H O R T _ M ES S A G E _ R s p M A P _C LO S E _ R e q 'N o'
N UL L
5706
5707
Figure 23.3/3 (sheet 1 of 3): Procedure MTSM_VMSC
2290
3GPP
2291 Release 4
760
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess MTSM_VMSC
F ig u re 2 3.3 /3 : T h e m ob il e term in at ed s h ort m e s s ag e s e rv ic e p roc e s s in th e M S C
23.3_3.2(3)
W A IT _ F O R _ MOR E_ M E S S AG ES
M A P _F O R W A R D _ S HO R T_ M E S S A G E _ in d
C he c k _ In dic at io n
E rro r
OK A _R P _ _M T _ D A T A_ re q
W A IT _ F O R _ SH O RT _ MESSAGE_ C O N F IR M
A _R P _ ER R O R _ in d
A_R P_ A C K _ in d
' SE T U S E R E R RO R'
No
'M ore m es s a ges to s en d' Ye s
M A P _F O R W A R D _ S H O R T _M ES S A G E _ rs p M A P _C LO S E _ re q
M A P _ FO R W A RD _ S H O R T _M E S S A G E_ rs p M A P _D E LIM I T E R _ req
NU L L
W A I T _F O R _ M ORE_ M ES S A G E S
5708
5709
Figure 23.3/3 (sheet 2 of 3): Procedure MTSM_VMSC
2292
3GPP
2293 Release 4
761
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess MTSM_VMSC
F ig u re 2 3.3 /3 : T h e m ob ile term in at ed s h ort m e s s ag e s e rv ic e p roc e s s in th e M S C
23.3_3.3(3)
W A IT _ F O R _ M O R E _ M E SS A G E S , W A IT _ F O R _S H O R T _M E SS A G E _ C O N F IR M
M AP _ U _ A B O R T _ in d M A P_ P _A B O R T _ in d
A _ M M_ R E LE A S E
M A P_ N O T IC E _ in d
A _ AB O R T _ req
M A P _U _ A B O R T_ re q
MAP_ C LO S E _ re q
A _ AB O R T _ re q
N U LL
5710
5711
Figure 23.3/3 (sheet 3 of 3): Procedure MTSM_VMSC
2294
3GPP
2295 Release 4
762
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition MT_SM_Transfer_MSC
Figure 23.3/4: The mobile t erminated s hort m essage t ransfer m acro in the MS C
23.3_4.1(3)
MT SM s upported?
No
Yes
Check_Subscr_ Identity_for_ MT_S MS Error
S ET UE = FA CILITY NOT S UP PORTED'
OK
MAP _O PE N_req MAP _S END_INFO_FOR_MT_S MS _req MAP _DELIMITE R_ req
Receive_ Open_ Cnf
Figure 25.1/2
V1
OK
E rror 'S ET UE= SYSTEM FA ILURE'
Perf orm_ MA P_V1_ Dialogue
W F_PA GE
Abort P age_MS C Figure 25.3/1 S earch_for_ MS_MS C Figure 25.3/2 MA P_SE ND_ INFO_FOR_ MT_SMS_cnf
Null Error 'User_error := System_Failure' W AIT_FOR_ A NS W E R_ FROM_V LR W AI T_FOR_ ANSW ER_ FROM_VLR Yes P roc ess_ Acc ess_ Reques t_ MS C Figure 25.4/1 'User_error := System_Failure' OK OK Error Null 'S ET USER E RRO R'
ERROR
No 'S ET UE = SM DELIVE RY FAILURE'
'MT SM CA PAB ILITY?'
MA P_U_ AB ORT_ req(VLR)
Error 'S ET UE= S ys tem Failure'
OK W AI T_FOR_ ANSW ER_ FROM_VLR ERROR
A_ABO RT_ req
5712
5713
Figure 23.3/4 (sheet 1 of 3): Macro MT_SM_Transfer_MSC
2296
3GPP
2297 Release 4
763
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition MT_SM_Transfer_MSC
Figure 23.3/4: The mobile t erminated s hort m essage t ransfer m acro in the MS C W A IT_FO R_ ANS WER_ FROM_VLR
23.3_4.2(3)
MA P_S END_ _INFO_FOR_ _MT_SMS_ _cnf
Trace_ Subc riber_ Act ivit y_MS C
Fig. 25.9/1
W A IT_FO R_ ANS WER_ FROM_VLR
Check _ Conf irmat ion
OK
Provider Error, Data Error
User Error
A -RP-MT-DATAreq
'SE T UE = S YSTEM FAILURE '
'S ET USE R ERRO R'
for Absent Subsc riber Us er error inc ludes diagnostic indi cation
W A IT_FOR_ S HORT_ ME SSA GE_ CONFIRM
Error
A-RP ACK-ind
A -RPE RRORind
OK
'S ET US ER E RROR'
Error
5714
5715
Figure 23.3/4 (sheet 2 of 3): Macro MT_SM_Transfer_MSC
2298
3GPP
2299 Release 4
764
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition MT_SM_Transfer_MSC
Figure 23.3/4: The mobile t erminated s hort m essage t ransfer m acro in the MS C
23.3_4.3(3)
W F_PA GE, W AIT_FOR_ANS WER_FROM_VLR, W AIT_FOR_SHORT_MES SA GE_CO NFIRM
A _MM_ RELEASE_ ind
M AP _NOTICE_ Ind from VLR
MA P_N OTICE_ ind from G MS C
MAP _U_A BORT_ind from GMSC, MAP _P_A BORT_ind from GMS C, MAP _CLOS E_ind from GMS C
MA P_U_ A BORT_ Req to VLR
MA P_ CLOS E_Req to VLR
MA P_ C LOSE _Req to GMS C
MAP_U_A BORT_ind f rom VLR, MA P_P_AB ORT_ind from V LR, MAP_CLOS E_ind from VLR
A_ AB ORT_ Req
MA P_U_ A BO RT_ Req to VLR
A_A BORT_ req
A _A BORT_ Req
A bort
'S ET UE = S ystem Failure'
E rror
5716
5717
Figure 23.3/4 (sheet 3 of 3): Macro MT_SM_Transfer_MSC
2300
3GPP
2301 Release 4
765
3GPP TS 29.002 V4.17.0 (2006-06)
5718
23.3.2 Procedures in the VLR
the parameters and data in the primitive are checked by the macro "Check_Indication". A data failure is reported as an unexpected data value error or a data missing error depending on the nature of the failure; for mobile terminated short message the mobile subscriber is identified either by the IMSI only or by the IMSI accompanied by the LMSI. The subscriber identity information that may be included in the MAP_OPEN indication primitive and in the MAP service indication primitive is checked by the macro "Check_Subscr_Identity_For_MT_SMS". In the first case, the IMSI is included in the sm-RP-DA information field and the Destination Reference must not be present in the MAP_OPEN primitive. In the latter case the IMSI must be obtained from the Destination Reference of the MAP_OPEN indication primitive and an LMSI must be present in the sm-RP-DA information field of the MAP_SEND_INFO_FOR_MT_SMS indication. If the mobile subscriber is unknown, the unidentified subscriber error is returned; if the "Confirmed by HLR" indicator is set to "Not Confirmed", the unidentified subscriber error is returned; if the IMSI Detached Flag is set to detached or the LA Not Allowed Flag is set to not allowed in the VLR, an absent subscriber error with the diagnostic indication set to 'IMSI Detached' is returned and the MS not reachable flag (MNRF) is set; if the MAP_SEND_INFO_FOR_MT_SMS indication has passed all the tests, the VLR will initiate the paging procedure. If the location area identification is known and the "Confirmed by Radio Contact" indicator is set to "Confirmed", the MAP_PAGE service is used. Otherwise the MAP_SEARCH_FOR_MOBILE_SUBSCRIBER service is started.
5719 When receiving the MAP_SEND_INFO_FOR_MT_SMS indication, the VLR will act as follows: 5720 5721 5722 5723 5724 5725 5726 5727 5728 5729 5730
5731 5732 5733 5734
5735 The following responses to the paging procedure may be received from the MSC: 5736 5737 5738
the MAP_SEARCH_FOR_MOBILE_SUBSCRIBER confirmation indicating a successful outcome, if the search procedure is used. After that the VLR awaits the MAP_PROCESS_ACCESS_REQUEST indication from the MSC; the MAP_PAGE confirmation or MAP_SEARCH_FOR_MOBILE_SUBSCRIBER confirmation indicating unsuccessful outcome. If an absent subscriber error is received, the MS not reachable flag (MNRF) is set in the VLR. The errors are forwarded to the MSC in the MAP_SEND_INFO_FOR_MT_SMS response, the absent subscriber error is forwarded with the diagnostic indication set to 'No Paging Response for non GPRS'. If the unexpected data value, or unknown location area error is received, the system failure indication is given to the MSC; if subscriber busy for MT SMS is received, this cause is given to the MSC. the MAP_PROCESS_ACCESS_REQUEST indication telling that the outcome of the service MAP_PAGE is successful.
5739 5740
5741 If the paging procedure or process access request procedure or any other procedure invoked fails, the appropriate error 5742 is reported to the MSC. 5743 If the process access request procedure is successful, the VLR will send the MAP_SEND_INFO_FOR_MT_SMS 5744 response to the MSC and the transaction is terminated in the VLR. 5745 The mobile terminated short message transfer procedure in the VLR is shown in figure 23.3/5.
2302
3GPP
2303 Release 4
766
3GPP TS 29.002 V4.17.0 (2006-06)
Process MT_SM_VLR
Figure 23.3/5: The mobile t erminated s hort message service process in t he VLR
23.3_5.1(3)
NULL
NULL
Rec eive_ Open_Ind
OK Dest_Ref_ rec eived yes S tore_ Des tination_ Ref erence V1 no E rror
Perform MA P v1 Dialogue
W AIT_FOR_ S ERV ICE_ PRIMITIV E
NUL L
NULL
MA P_S END_ INFO_FOR_ MT_S MS_Ind
MA PNO TICE _In d
Check_ Indicat ion
Figure 25.2/1
MA PCLOS E _Req
OK Chec k_S ubsc r_ Identity_For_ MT_S MS OK Figure 23.3/8
E rror
NULL
Subscriber known yes
Error no
Confirmed by HLR
no
yes
Us er_error := Unidenti fied_ Subscriber'
MA P_SE ND_INFO_ FOR_S MS _Rsp MAP _CLO SE_Req
1 Page 2
NUL L
5746
5747
Figure 23.3/5 (sheet 1 of 3): Process MT_SM_VLR
2304
3GPP
2305 Release 4
767
3GPP TS 29.002 V4.17.0 (2006-06)
Process MT_SM_VLR
Figure 23.3/5: The mobile t erminated s hort message service process in t he VLR
23.3_5.2(3)
2 Page 1
IMSI_Detac hed_Flag = detached ?
yes
no
LA_Not_Allowed_Flag = not allowed ? no
yes
Confirmed by radio contact yes
no
SE T UE = AB SE NT SUBS CRIB ER with diagnostic 'IMS I- De tached'
yes
LAI known
SE T MOB ILE S TA TION NOT REA CHA BLE FLAG
no
MA P_PA GE_Req MA P_DELIMITER_Req
MA P_SE ND_INFO_FOR_SMS _Rsp MAP _CLO SE_Req
NULL
MA P_SE ARCH_FO R_MOBILE _S UBS CRIB ER_Req MAP _DE LIMITE R_Req
W A IT_FOR_ A CCES S_ REQUE ST
5748
5749
Figure 23.3/5 (sheet 2 of 3): Process MT_SM_VLR
2306
3GPP
2307 Release 4
768
3GPP TS 29.002 V4.17.0 (2006-06)
Process MT_SM_VLR
Figure 23.3/5: The mobile t erminated s hort message service process in t he VLR W A IT_FO R_ A CCES S_ REQUES T
23.3_5.3(3)
Process_ Access_ Requ est_VLR E rror OK SE T SUBS CRIB ER DA TA
Figure 25.4/2
MAP _ P AGE _Cnf
MAP _S EA RCH_FOR_ MOB ILE _S UB SCRIBE R_Cnf
Check_ Confirm ation
NULL
Us er Error
OK
P rovid er Error, Data Error
no
A bsent subscriber? yes
S ET USE R ERROR
S ET UE= A BS ENT S UBS CRIB ER with diagnost ic 'No paging Resp onse'
UP DA TE LA I
NULL
S ET M OBILE S TA TION NOT REA CHA BLE FLAG
W AI T_FOR_ ACCES S_ RE QUE ST
MAP _S END_INFO_FOR_MT_S MS _Rsp MAP _CLO SE_Req
W AIT_FOR_ A CCE SS _ REQUE ST
NULL
MA P_ NOTICE_ Ind
MAP _U_AB ORT_Ind, MAP _P _ABORT_Ind
MA P_ CLOS E_ Req
NULL
5750
5751
Figure 23.3/5 (sheet 3 to 3): Process MT_SM_VLR
2308
3GPP
2309 Release 4
769
3GPP TS 29.002 V4.17.0 (2006-06)
5752
23.3.3 Procedures in the HLR
5753 The MAP_SEND_ROUTING_INFO_FOR_SM indication is received from the GMSC. The following error cases are 5754 reported to the GMSC in the MAP_SEND_ROUTING_INFO_FOR_SM response as an unsuccessful outcome of the 5755 procedure: 5756 5757 5758 5759 5760 5761 5762 5763 5764 5765 5766 5767 5768 5769 5770 5771 5772 5773 5774 5775 5776 5777 5778 5779 5780 5781 5782
if the necessary parameters and data are not present in the primitive or they are badly formatted, the data missing or unexpected data value error is returned; if the mobile subscriber is unknown, i.e. it cannot be identified from the MSISDN given, an unknown subscriber error is returned; if the short message transfer would contravene operator determined barring, the call barred error with cause operator barring is returned; if the short message transfer would contravene the SM filtering by the HPLMN function criteria, the call barred error with cause unauthorised Message Originator is returned (the definition of the filtering function is out of the scope of GSM specification. Filtering may be based on SM-RP-SMEA information element if received from the GMSC); if the mobile subscription identified by the given MSISDN number does not include the short message service, the teleservice not provisioned error is returned; if the GMSC does not support the GPRS functionality, the behaviour of the HLR depends on the following conditions: if the subscriber is not a GPRS subscriber then the behaviour of the HLR shall be the same as for a subscriber only registered as non GPRS and for SMS delivery; if the subscriber is a GPRS subscriber and a non-GPRS subscriber with the option transfer of SM via the MSC when GPRS is not supported in the GMSC then the behaviour of the HLR shall be the same as for a subscriber only registered as non GPRS and for SMS delivery; if the subscriber is a GPRS subscriber and a non-GPRS subscriber with the option transfer of SM via the SGSN when GPRS is not supported in the GMSC or if the subscriber is a GPRS subscriber only then the behaviour of the HLR shall be the same as for the case transfer over GPRS described in MAP release 97, with the following precision: because GMSC does not support MAP release 97, the previous MAP protocol release is used. When the HLR sends the MAP_SEND_ROUTING_INFO_FOR_SM_Resp, the SGSN number is mapped to the MAP parameter MSC number . When the HLR sends the MAP_INFORM_SERVICE_CENTRE_resp, the MNRG status shall be mapped to the MAP parameter mnrf-set .
5783 The HLR may send the MSC, SGSN or both numbers as routing information to SMS-GMSC based on the following:
A) The subscriber may only be registered as non GPRS and for SMS delivery:
5784 5785 5786 5787 5788 5789 5790 5791 5792
if the short message transfer would contravene the supplementary service barring, the call barred error with cause barring service active is returned; if the location registration of the mobile subscriber shows that the VLR in the visited PLMN does not support the MT short message service, the facility not supported error is returned;
if no MSC identity is stored for the mobile subscriber or the "MSC Area Restricted Flag" is set or the "MS purged for non GPRS" flag is set, i.e. the MS is not reachable, the MSISDN-Alert and the SC address are included in the MWD (if possible), the flag MNRF is set and the "Absent Subscriber_SM" error is returned with the appropriate absent subscriber diagnostic indication, i.e. 'Deregistered in HLR for non GPRS ', 'Roaming Restricted' or 'MS-Purged for non GPRS '.
2310
3GPP
2311 Release 4
770
3GPP TS 29.002 V4.17.0 (2006-06)
5793 5794 5795 5796 5797 5798 5799 5800 5801 5802 5803 5804 5805 5806 5807 5808 5809 5810 5811 5812 5813 5814 5815 5816 5817 5818 5819 5820 5821 5822 5823 5824 5825 5826 5827 5828 5829 5830 5831 5832 5833 5834 5835 5836 5837 5838 5839 5840 5841
The priority parameter (SM_RP_PRI) is processed as follows: if the priority is low (SM_RP_PRI = False) and the mobile station not reachable flag (MNRF) is set, an absent subscriber_SM error is returned. If a reason for the subscriber's absence for non GPRS is stored in the mobile not reachable reason (MNRR) in the subscriber data, then this is returned with the absent subscriber_SM error. The SC-address given in the request will be included in the MWD if possible. The service MAP_INFORM_SERVICE_CENTRE including the parameter MW Status is invoked to indicate whether or not the SC address has been included in the MWD list. if the priority is low (SM_RP_PRI = False), and the MNRF is clear, the routing information with MSC number is retrieved as described below; if the priority is high (SM_RP_PRI = True) and the MNRF is set, the HLR will send the acknowledge primitive containing the routing information with MSC number to the gateway MSC. In addition the service MAP_INFORM_SERVICE_CENTRE including the parameter MW Status is invoked to indicate whether or not the SC address is already included in the MWD list.
B) The subscriber may only be registered as GPRS and for SMS delivery: if the location registration of the mobile subscriber shows that the SGSN in the visited PLMN does not support the MT short message service, the facility not supported error is returned; if no SGSN identity is stored for the mobile subscriber or the "SGSN Area Restricted Flag" is set or the "MS purged for GPRS" flag is set, i.e. the MS is not reachable, the MSISDN-Alert and the SC address are included in the MWD (if possible), the flag MNRG is set and the "Absent Subscriber_SM" error is returned with the appropriate absent subscriber diagnostic indication, i.e. 'Deregistered in HLR for GPRS', 'Roaming Restricted' or 'MS-Purged for GPRS '.
The priority parameter (SM_RP_PRI) is processed as follows: if the priority is low (SM_RP_PRI = False) and the mobile station not reachable for GPRS (MNRG) flag is set, an absent subscriber_SM error is returned. If a reason for the subscriber's absence for GPRS is stored in the mobile not reachable reason (MNRR) in the subscriber data, then this is returned with the absent subscriber_SM error. The SC-address given in the request will be included in the MWD if possible. The service MAP_INFORM_SERVICE_CENTRE including the parameter MW Status is invoked to indicate whether or not the SC address has been included in the MWD list. if the priority is low (SM_RP_PRI = False), and the MNRG is clear, the routing information with SGSN number is retrieved as described below; if the priority is high (SM_RP_PRI = True) and the MNRG is set, the HLR will send the acknowledge primitive containing the routing information with SGSN number to the gateway MSC. In addition the service MAP_INFORM_SERVICE_CENTRE including the parameter MW Status is invoked to indicate whether or not the SC address is already included in the MWD list.
C) The subscriber may be registered as non GPRS and GPRS and for SMS Delivery: if the short message transfer would contravene the supplementary service barring, the behaviour is the same as for a subscriber only registered for GPRS and SMS delivery. if the location registration of the mobile subscriber shows that the VLR in the visited PLMN does not support the MT short message service, the behaviour is the same as for a subscriber only registered for GPRS and SMS delivery; if the location registration of the mobile subscriber shows that the SGSN in the visited PLMN does not support the MT short message service, the behaviour is the same as for a subscriber only registered for non GPRS and SMS delivery; if no MSC and SGSN identities are stored for the mobile subscriber or the "MSC and SGSN Area Restricted Flags" are set or the "MS purged for non GPRS and GPRS" flags are set or a combination of these errors for non GPRS and GPRS are used, i.e. the MS is not reachable, the MSISDN-Alert and the SC address are included in the MWD (if possible), the flags MNRF and MNRG are set and the "Absent Subscriber_SM" error is returned with the appropriate absent subscriber diagnostic indication, i.e. 'Deregistered in HLR for non GPRS or GPRS', 'Roaming Restricted', 'MS-Purged for non GPRS or GPRS' or both.
2312
3GPP
2313 Release 4
771
3GPP TS 29.002 V4.17.0 (2006-06)
5842 5843 5844 5845 5846 5847 5848 5849 5850 5851 5852 5853 5854 5855 5856 5857 5858
The priority parameter (SM_RP_PRI) is processed as follows: if the priority is low (SM_RP_PRI = False), the MNRF and MNRG are set, an absent subscriber_SM error is returned. If reasons for the subscriber's absence for non GPRS and GPRS are stored in MNRR in the subscriber data, then this is returned with the absent subscriber_SM error. The SC-address given in the request will be included in the MWD if possible. The service MAP_INFORM_SERVICE_CENTRE including the parameter MW Status is invoked to indicate whether or not the SC address has been included in the MWD list. if the priority is low (SM_RP_PRI = False), and the MNRF is clear and MNRG is set, the routing information with MSC number is retrieved as described below; if the priority is low (SM_RP_PRI = False), and the MNRF is set and MNRG is clear, the routing information with SGSN number is retrieved as described below; if the priority is low (SM_RP_PRI = False), and the MNRF and MNRG are clear, the routing information with MSC and SGSN numbers is retrieved as described below; if the priority is high (SM_RP_PRI = True) and the MNRF, the MNRG or both are set, the HLR will send the acknowledge primitive containing the routeing information with both MSC and SGSN numbers to the gateway MSC. In addition the service MAP_INFORM_SERVICE_CENTRE including the parameter MW Status is invoked to indicate whether or not the SC address is already included in the MWD list.
5859 If the MSISDN-Alert number of the mobile subscriber stored in the MWD is not the same as that received in the 5860 MAP_SEND_ROUTING_INFO_FOR_SM indication, the HLR will include in the 5861 MAP_INFORM_SERVICE_CENTRE request to the GMSC the MSISDN-Alert number stored. 5862 The MAP_INFORM_SERVICE_CENTRE request is sent also when the MCEF, MNRF, MNRG or both are set but the 5863 routing information is still sent to the GMSC. The status of the flags is indicated in the parameter MW Status. 5864 The routing information is included in a MAP_SEND_ROUTING_INFO_FOR_SM response as follows: 5865 5866 5867
the IMSI will be returned to the GMSC together with the MSC, SGSN or both numbers and may be optionally accompanied by the LMSI. an indication specifying which number belongs the MSC and the SGSN will be returned to the GSMC.
5868 LMSI shall not be used in case only the SGSN number is sent by HLR. 5869 The mobile terminated short message transfer procedure in the HLR is shown in figure 23.3/6.
2314
3GPP
2315 Release 4
772
3GPP TS 29.002 V4.17.0 (2006-06)
Pro c ess M obile _term ina te d_S M _ HL R
F ig u re 2 3 .3 /6 : T h e m o bi le t e r m i n a te d s h o r t m e ss a g e s e rv ic e p ro c e s s i n the H L R in c a s e the MA P _ S E N D _ s u b s c r ib e r is re g i s te r ed a s n o n- G PR S R O U T IN G _ a nd /or G P R S IN F O _ F O R _ SM _ in d
23 .3_ 6 .1 (5)
N UL L
C he c k _ I nd ic a tio n
OK 'S ub s c rib e r kno w n ' Y es 'MT S M p ro v is io n e d ' Y es 'O p e r a tor b a rr in g ' Ye s 'S E T U E = T E LE SE R V IC E N O T P R O V IS IO N E D ' No 'S E T U E = UN K NO W N S U B S C R IB E R ' No
E rro r
No S M F IL T E R IN G B Y H PL M N F UN CTIO N ? Y es 'S E T U E = C ALL B A RR E D' 'S E T C B C AU S E = O PERATO R BA R R I N G '
No
No
G M S C s u p p o r ts G P R S fu n c tio n a l ity ? 'S E T U E = C AL L B A R R E D ' M AP -S E N D -R O U T IN G IN F O -F O R - S M -r s p M A P - C L O SE -r e q
Y es ' W h ic h s u b s c r ip t io n ?' GPR S 4 P ag e 3
n o n -G P R S
no n - G P R S an d G P RS 5 P ag e 4
1 P ag e 2
'S E T C B - C A U S E = U N A U T H O R IS E D M E S SA G E O R I G IN AT O R
5870
5871
Figure 23.3/6 (sheet 1 of 5): Process Mobile_terminated_SM_HLR
2316
3GPP
2317 Release 4
773
3GPP TS 29.002 V4.17.0 (2006-06)
Process Mobile_term inated_S M _HLR
F ig ure 2 3.3 /6 :
1 T h e m o bile t erm in ate d s ho rt m es s a ge P a g e 1 s erv ic e p roc es s in the H LR in c a s e t he s u bs c rib e r is re gis ter ed as no n-G PR S a nd /or G P R S 'MT S M S B a rre d ' Ye s No No 'MT S M s u pp o rte d by M S C ' 'S et C B -C au s e = B arrin g S erv ic e Ye s 'S E T U E = A c tiv e ' F AC IL IT Y N O T SU P PO R T E D ' 'S u bs cri be r Y es re ac h a ble' No
23.3_ 6.2(5)
7 P ag e 4
'S et U E = C a ll B arre d'
'M N R F se t' No 'R et rie v e r o ut in g d at a'
Ye s
'S e t M NR F'
M S IS D N = M S IS D N -Aler t M A P _ S EN D _ R O U T IN G _ IN F O _ F O R _S M _rs p MCEF set Y es 'S et M W S ta tus ' No No Ye s 'S e t M S IS D N A l ert'
's m - R P -P R I (P rio r ity)' F a ls e = Lo w T ru e= 'S E T U E = H ig h AB S E N T S U B S C R IB E R ' 'R e triev e ro u tin g da ta' 'S e t M W S ta tu s ' In c lu de a pp rop ria te d ia gn os tic i nd ic a tion
M A P _ C LO SE _ req
No 'M S IS D N = M SI S D N - A ler t' Y es M A P IN F O R M S E R VI C E _ C E N T R E _ re q M A P _C LO S E _ r eq M A P _S E N D _R O U T IN G _ IN F O _F O R _ S M _ rs p
'S e t M S I SD N Alert'
M A P _I N F O R M _ SE R V IC E_ C E N T R E _ re q , M A P _C L O S E _re q
3 P ag e 5
M A P_ S EN D _R O U T IN G _ _ IN F O _F O R _S M _ rs p M AP _ C L O S E _re q 2 P ag e 5
M A P _S E N D _R O U T IN G _ IN F O _F O R _ S M _ rs p
5872
5873
Figure 23.3/6 (sheet 2 of 5): Process Mobile_terminated_SM_HLR
2318
3GPP
2319 Release 4
774
3GPP TS 29.002 V4.17.0 (2006-06)
Process Mobile_term inated_S M _HLR
F ig ure 2 3.3 /6 : T h e m o bile t erm in ate d s ho rt m es s a ge 4 s erv ic e p roc es s in the H LR in c a s e t he P a g e 1 s u bs c rib e r is re gis ter ed as no n-G PR S a nd /or G P R S 'MT S M s u pp o rte d by S G S N ' Ye s 6 P ag e 4
23.3_ 6.3(5)
No
'S E T U E = F A C IL IT Y N O T SU P P O R T E D ' 'M NR G s e t' No 'R et rie v e r o ut in g d at a' Ye s
Y es
'S u bs cri be r re ac h a ble'
No
'S e t M N RG ' F a ls e = 's m - R P -P R I Lo w (P rio r ity)' T rue = H igh
M S IS D N = M S IS D N -Ale rt No M A P _ S EN D _ R O U T IN G _ IN F O _ Y es F O R _S M _rs p 'S e t M S IS D N A l ert' MCEF set Y es 'S et M W S ta tus ' No M A P _ C LO SE _ req
'S E T U E = AB S E N T S U B S C R IB E R ' In c lu de a pp rop ria te d ia gn os tic i nd ic a tion
'R e triev e ro u tin g da ta'
No 'M S IS D N = M SI S D N - A ler t' Y es
M A P IN F O R M S E R VI C E _ C E N T R E _ re q M A P _C LO S E _ r eq
'S e t M S I SD N Alert' 'S e t M W S ta tu s ' M A P _S E N D _R O U T IN G _ IN F O _F O R _ S M _ rs p
M A P _I N F O R M _ SE R V IC E_ C E N T R E _ re q , M A P _C L O S E _re q
3 P ag e 5
M A P_ S EN D _R O U T IN G _ _ IN F O _F O R _S M _ rs p M AP _ C L O S E _re q 2 P ag e 5
M A P _S E N D _R O U T IN G _ IN F O _F O R _ S M _ rs p
5874
5875
Figure 23.3/6 (sheet 3 of 5): Process Mobile_terminated_SM_HLR
2320
3GPP
2321 Release 4
775
3GPP TS 29.002 V4.17.0 (2006-06)
Process Mobile_terminated_S M_HLR
F ig ure 2 3.3 /6 :
5 T h e m o bile t erm in ate d s ho rt m esP a g e 1 s s erv i c e p roc es s in the H LR in c a s e the s u bs c rib e r is re gi s ter ed as no n-G PR S a nd /or G P R S No No
23.3_6.4(5)
No 'M T SM S B arre d' Y es
'M T S M s u pp ort ed in V L R ' Ye s Ye s 'M T S M s u pp orte d in S G S N ' Yes 'S u bs c rib er rea c ha b le ' No 'S e t M N R F an d M N R G ' 's m -R P -P R I (P rio ri ty)' T rue = H igh 4 P ag e 3
'M T S M s up po rte d i n S G S N ' Ye s 6 P ag e 3
7 P ag e 2
No
No
'M N R F a n d M N R G s e t'
Y es
No
'M N R F se t'
Y es
T ru e = 'S M _ R P _P R I H ig h (Pr io ri ty )'
'MN RG s e t' No 'S E T U E = F A C IL IT Y N O T SU P P O R T E D ' 'S et M S C a nd SG SN a dd res s e s ' Ye s
F a ls e = L ow 'S e t S G S N a dd re s s '
F als e = Low
T ru e = H ig h 'S M _ R P _P R I (Pr io rity )' F a ls e = Lo w 'S e t M S C a dd res s '
'S e t M S C a n d S G S N a d dre ss es '
'R et rie v e ro ut in g d at a' M A P _S E N D _ R O U T IN G _ IN F O _ F O R _S M _rs p M CE F se t No
'S e t M S C an d S G S N ad dre s s es '
'S E T U E = A BS E N T S U B S C R IB E R ' In c lu de a pp rop ria te d ia gn os tic ind ic ation
M S IS D N = M S IS D N -Ale rt No Y es M A P _ C LO SE 'S e t M S IS D N A lert' _ req
Y es 'S et M W S ta tus '
No 'M S IS D N = M SI SD N -A lert' Y es
M A P IN F O R M S E R V IC E _ C E N T R E _ re q M A P _C LO S E _ req 'S e t M W S ta tu s '
'R e triev e ro u tin g da ta'
M A P _S E N D _R O U T IN G _ IN F O _F O R _ S M _ rs p
3 P ag e 5
'S e t M S IS D N Alert' M A P _S E N D _R O U T IN G _ IN F O _F O R _ S M _ rs p
M A P_ S EN D _R O U T IN G _ _ IN F O _F O R _S M _ rs p M AP _ C L O S E _re q
M A P _I N F O R M _ S E R VI C E _ C E N T R E_ req , M A P _C LO S E _ req 2 P ag e 5
5876
5877
Figure 23.3/6 (sheet 4 of 5): Process Mobile_terminated_SM_HLR
2322
3GPP
2323 Release 4
776
3GPP TS 29.002 V4.17.0 (2006-06)
Proc ess Mobile_terminated_SM_HLR
F ig ure 2 3.3 /6 : T h e mo bile t ermin ate d s ho rt m es s a g e s erv ic e p r oc es s in the H LR in c a s e the s ub s c rib er is reg is te re d as n on - G P R S a nd /or G P R S
23.3_6.5(5)
3 P a ge s 2, 3, 4
2 P ag es 2 ,3 ,4
'S C ad dre s s in M W D lis t' No 'U p da te M W D lis t'
Y es
Ye s
'S C a dd r es s in M W D lis t' No
Y es
'M W D upd a te fa ilu re '
No
' MW D S t atu s = S c A d dre s s N o tInc lu de d
'M W D S ta tu s = S c A dd res s In c lude d '
M W D S t atu s = Sc A d res s N o tIn c lu de d '
'S e t M C E F /M N R G a nd /o r M N R F _S ta tu s '
'M S IS D N = MS IS D N Aler t' No 'S e t M S IS D N A le rt'
Y es
M A P_ IN F O R M _ S E R V IC E _C E N T R E _r e q M AP _ C L O S E _re q
5878
5879
Figure 23.3/6 (sheet 5 of 5): Process Mobile_terminated_SM_HLR
2324
3GPP
2325 Release 4
777
3GPP TS 29.002 V4.17.0 (2006-06)
Procedure S elect_Transfer_Nodes
F ig u re 2 3. 3/ 1 1: P roc ed u re in th e H LR to s elec t th e n o de (M S C or/ and S G S N ) to w h ic h the S M S -G M S C h as to s en d S h o rt M es sa g e
23.3_11 (1)
no
G P RS s u pp o rted by HL R yes
no
GPR S s ub sc ribe r? yes
G P RS s u pp o rted by G MSC no n on -G P R S S ub s c rib er? yes MSC O p t ion SGSN
ye s
no
no
no n -G P R S su bs c rib e r? y es
R es u lt= M S C
R es u lt= S G S N
R es u lt =b o th
5880
5881
Figure 23.3/11: Procedure Select_Transfer_Nodes
2326
3GPP
2327 Release 4
778
3GPP TS 29.002 V4.17.0 (2006-06)
5882
5883 5884 5885 5886
23.3.4 Procedures in the gateway MSC
The short message handling function of the GMSC will request routing information when a mobile terminated short message is received from a Service Centre. The GMSC sends the MAP_SEND_ROUTING_INFO_FOR_SM request to the HLR containing the subscriber data of the mobile subscriber and the indication that the SMS-GMSC supports the GPRS functionality.
5887 As an outcome of the procedure the MAP_SEND_ROUTING_INFO_FOR_SM confirmation is received indicating: 5888 5889 5890 5891 5892
an unsuccessful event indication containing an error; The mapping between the MAP error causes and the RP_ERROR causes is explained in 3GPP TS 23.140.
a successful event indication containing following parameters: an IMSI optionally accompanied by an LMSI; and routing addresses (servicing MSC, SGSN or both numbers).
5893 The LMSI shall not be used in case the short message is routed towards the SGSN. 5894 5895 5896 5897 5898
The GMSC may also receive a MAP_INFORM_SERVICE_CENTRE indication after the MAP_SEND_ROUTING_INFO_FOR_SM confirmation. The parameter MW Status in the message indicates whether or not the Service Centre address is stored in the Message Waiting Data. It also indicates the status of the MCEF , MNRF and MNRG flags in the HLR. The message also indicates the value of the MNRR if this is stored in the HLR and one or both of the MNRF and MNRG flags is set in the HLR.
5899 If the MSISDN-Alert stored in the MWD data is not the same as the one sent to the HLR, the MSISDN-Alert is 5900 received in the MAP_INFORM_SERVICE_CENTRE indication. This MSISDN number shall be transferred in a 5901 delivery failure report to the SC. 5902 In the abnormal end or in the provider error case the system failure error is provided to the SC. 5903 The forward short message procedure is initiated when the GMSC has obtained the routing information needed to 5904 forward a mobile terminated short message to the servicing MSC or SGSN. 5905 If both numbers MSC and SGSN are received from HLR as routing information, the SMS-GMSC may choose which 5906 path (SGSN or MSC) first the SMS is to be transferred. 5907 5908 5909 5910 5911 5912 5913 5914
If an LMSI has been provided in the MAP_SEND_ROUTING_INFO_FOR_SM confirmation, it can be included in the sm-RP-DA information field of the first MAP_MT_FORWARD_SHORT_MESSAGE request sent to the servicing MSC. In this case, the IMSI must be included in the Destination Reference of the MAP_OPEN request. If the LMSI is not sent by the SMS Gateway MSC, the sm-RP-DA information field in the first MAP_MT_FORWARD_SHORT_MESSAGE request sent to the servicing MSC or SGSN shall contain the IMSI and the Destination Reference in the MAP_OPEN request shall not be present. The Service Centre address is sent in the parameter SM_RP_OA. The More Messages To Send flag is set to TRUE or FALSE depending on the information received from the Service Centre.
5915 If the GMSC is the servicing MSC then the MAP service is not initiated. The procedure in the Servicing MSC is 5916 described in clause 23.3.1 and in the figure 23.3/4. 5917 5918 5919 5920
If the grouping of MAP_OPEN request and MAP_MT_FORWARD_SHORT_MESSAGE request together would need segmenting, these primitives must not be grouped together. The MAP_OPEN request primitive is sent first without any associated MAP service request primitive and the dialogue confirmation must be received before the MAP_MT_FORWARD_SHORT_MESSAGE request is sent.
5921 As a response to the procedure, the GMSC will receive the MAP_MT_FORWARD_SHORT_MESSAGE confirmation 5922 indicating: 5923 5924
a successful forwarding of the short message. This indication is passed to the SC; unsuccessful forwarding of the short message:
2328
3GPP
2329 Release 4
779
3GPP TS 29.002 V4.17.0 (2006-06)
5925 5926 5927 5928 5929 5930 5931 5932 5933 5934 5935 5936 5937 5938 5939 5940 5941 5942 5943
In case only one number (MSC or SGSN) was received from HLR as routing information, the mapping of the MAP error causes and the RP_ERROR causes is explained in 3GPP TS 23.140. The appropriate error indication is sent to the SC. In case both numbers (MSC and SGSN) were received from HLR as routing information, the transfer of SMS is re-attempted towards the second path only when one of the following errors is received from the unsuccessful transfer over the first path: Facility Not Supported Unidentified Subscriber Absent Subscriber with indication: GPRS or IMSI Detach Unexpected Data Value System failure Data Missing Subscriber Busy for MT SMS: GPRS Connection Suspended SM Delivery Failure with indication: equipment Not SM Equipped otherwise, the mapping of the MAP error causes and the RP_ERROR causes is performed (see 3GPP TS 23.140) and the appropriate error indication is sent to the SC. If second forwarding of short message is unsuccessful, the mapping of the MAP error causes and the RP_ERROR causes is explained in 3GPP TS 23.140. The appropriate error indications are sent to the SC. If second forwarding of short message is successful, the successful indication is passed to the SC.
5944 A provider error is indicated as a system failure error to the SC.
The GMSC invokes the procedure MAP_REPORT_SM_DELIVERY_STATUS, if:
-
an absent subscriber_SM, an unidentified subscriber or SM delivery failure with error cause MS memory capacity exceeded indication is received from the servicing MSC, SGSN or both, and the SC address is not yet included in the MWD set, or the reason received from the serving node (MSC or SGSN) 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 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.
If absent subscriber diagnostic information (see 3GPP TS 23.140) is included with the absent subscriber_SM error indication then this information is relayed to the HLR using the procedure MAP_REPORT_SM_DELIVERY_STATUS. In case the SMS was attempted to be delivered towards the MSC and the SGSN, and both delivery failed with causes described above, the two unsuccessful SMS delivery outcomes for GPRS and non GPRS are sent to the HLR. In case the SMS was attempted to be delivered towards the MSC and the SGSN, and the first delivery failed with causes described above and the second delivery succeeded, the unsuccessful and successful SMS delivery outcomes for GPRS and non GPRS are sent to HLR. The gateway MSC may also invoke the procedure when the first SMS delivery was successful towards MSC, if the MNRF, MCEF flags or both were set in the HLR. The gateway MSC may also invoke the procedure when the first SMS delivery was successful towards SGSN, if the MNRG, MCEF flags or both were set in the HLR.
2330
3GPP
2331 Release 4
780
3GPP TS 29.002 V4.17.0 (2006-06)
This procedure is described in detail in clause 23.5.
5945 Unexpected data value, system failure errors are indicated as a system failure to the SC. Other errors are indicated using 5946 appropriate cause values and diagnostic information between the GMSC and the SC as described in 3GPP TS 23.140 5947 and 3GPP TS 24.011 [37]. 5948 The unidentified subscriber error is indicated to the SC as absent subscriber with diagnostic information set to 5949 'Unidentified subscriber' as described in 3GPP TS 23.140. 5950 Note that the indication, on which number belongs the SGSN and MSC, received from the HLR at routing information 5951 result (see clause 23.3.3) will enable the GMSC to map the causes received from the SGSN, MSC or both into the 5952 appropriate causes for non GPRS, GPRS or both, and send them to the SC and HLR. 5953 If there are more short messages to send in the Service Centre and the previous short message transfer succeeded, then 5954 the gateway MSC awaits the next short message. 5955 When receiving the next short message from the SC, the gateway MSC sets the More Messages To Send flag according 5956 to the information received and starts the service MAP_MT_FORWARD_SHORT_MESSAGE again. 5957 If the gateway MSC is the servicing MSC, then the short message transfer to mobile subscriber is started as described in 5958 the clause 23.3.1. 5959 The mobile terminated short message transfer procedure in the gateway MSC is shown in figure 23.3/7.
2332
3GPP
2333 Release 4
781
3GPP TS 29.002 V4.17.0 (2006-06)
Process MT_SM_GMSC
Figure 23 .3/7: The mobile terminate d s hort messa ge service p rocess in the GMS C NULL
23.3_7.1(6)
S C_RP_MT _DATA _in d
NULL
MAP _O PE N_ req MAP _S END_ROUTING_INFO_ FO R_SM_ req MAP _DEL IMITE R_re q
Receive_ OP EN_Cn f
'V1 '
'OK '
'E rror'
WA IT_FOR_ RES UL T 'P erform_ MA P_V1_ Dialog ue'
1 P age 2
SC_A BORT _in d
MAP _S END_ROUTING _ INFO_FOR_S M_cnf
MA P_ NOTICE _ In d
MAP _U_A BORT_ind MAP _P_AB ORT_ind MAP _CLOS E_ind
MA P_U_ AB ORT_req
MA P_ CLOS E _ Re q
NULL
Che ck_ conf irmat ion
OK 'LMS I _ in cluded _in _locat io n_info' 'Yes' 'No'
User Error
P ro vid er Error, Da ta Error
'Set_De stinatio n _Refe rence = IMS I'
'Set_Destinatio n_ Re ference_Not _I nclude d'
'Set_ RP_CAUSE '
'S et_ RP_CA USE = System_Failure'
'S et _ SM_ RP _DA = L MS I'
'Set_ SM_RP _DA = IMS I'
SC_RP _ ERROR_rsp
WA IT_FOR_ INFO RM_S C
NULL
5960
5961
Figure 23.3/7 (sheet 1 of 6): Procedure MT_SM_GMSC
2334
3GPP
2335 Release 4
782
3GPP TS 29.002 V4.17.0 (2006-06)
Process MT_SM_GMSC
Figure 23.3/7: The mobile terminated s hort message service process in the GMS C W A IT_FO R_ INFO RM_S C
23.3_7.2(6)
1 P age 1
MA P_ CLOS E_ Ind
MA P_INFORM_ S ERV ICE _ CE NTRE_ Ind
MAP _ NOTICE _ Ind
SC_ ABORT_Ind
Check_ Indicat ion Error OK No Error from HLR? Yes
MAP _ CLOS E_ Req
MA P_U_ AB ORT_Req
NULL
S et RP_MS I & RP_MS ISDN Rout ing Info received ? Yes S C_RP_ E RROR_Req VMSC= GMSC? No
No
Yes
3 P age 3 No
mes sag e segmenting needed?
Yes NULL
M AP_OPE N_Req MA P_FORW ARD_S HORT_ MES SA GE_Re q M AP _DELIMITER_Req
MAP _OP EN_Req MAP _DELIMITER_Req
Receive_ Open_ Cnf Error OK W AIT_FOR_ MT_S MS_ CONFIRM V1 Perfo rm MAP V1 dialogue SE T RP_E RROR =SY STEM FAILUR E Error
Receive_ Open_ Cnf
V1 P erform MA P V 1 dialogue
OK MA P_FORW ARD_S HORT_ ME SSA GE_Req MAP _DELIMITER_Req
NULL
S C_RP_ E RROR_Req
NULL
W AI T_FOR_ MT_SMS_ CONFIRM
NULL
5962
5963
Figure 23.3/7 (sheet 2 to 6): Procedure MT_SM_GMSC
2336
3GPP
2337 Release 4
783
3GPP TS 29.002 V4.17.0 (2006-06)
Process MT_SM_GMSC
Figure 23.3/7: The mobile terminated short message service process in the GMSC WAIT_FOR_ MT _SMS_ CONFIRM
23.3_7.3(6)
Check_ Confirmation
Fig 25.2/2
MAP_FORWARD_SHORT_ MESSAGE_Cnf
OK
User Error 2 Page 4
Provider Error, Data Error
No 3 Page 2 Unidentified Subscriber? Yes
MT_SM_ Transfer_ MSC
Fig 23.3/3
SET UE= ABSENT SUBSCRIBER Error
No Absent subscriber? Yes
Abort OK Yes NULL MWD already set? More messages to send? No Yes No MC EF or MN RF set in HLR? Yes OK Error Report_SM Delivery_ Stat_GMSC OK Error SC_RP_ ACK_Req SC_RP_ ACK_Req SC_RP_ ERROR_Req Report_SM Delivery_ Stat_GMSC No No Failure cause from VMSC= Indication from HLR? Yes MS memory capacity exceeded? No
Yes
Set RP_ERROR
WAIT_FOR_ MORE_ MESSAGES
NULL
5964
5965
Figure 23.3/7 (sheet 3 of 6): Procedure MT_SM_GMSC
2338
3GPP
2339 Release 4
784
3GPP TS 29.002 V4.17.0 (2006-06)
Process MT_SM_GMSC
Figure 23.3/7: The mobile terminated s hort message service process in the GMS C W A IT_FO R_ MORE_ MESS AGE S
23.3_7.4(6)
S C_RP _MT_ DATA_Ind
GM SC= V MS C? Yes
No
A _RP_MT_ DA TA_Req
MA P_FORW ARD_S HORT_ ME SSA GE_Req MAP _DELIMITER_Req
W A IT_FO R_A_ SM_CONFIRM
W AI T_FOR_ MT_SMS_ CONFIRM
A_RP_ ACK_Ind
A _RP_ E RROR_Ind
SC_RP _ ACK_Rsp
S ET US ER ERROR
More m essages t o s end? Yes
No
2 P age 3
W AIT_FOR_ MORE_ M ES SA GE S
NULL
5966
5967
Figure 23.3/7 (sheet 4 of 6): Procedure_MT_SM_GMSC
2340
3GPP
2341 Release 4
785
3GPP TS 29.002 V4.17.0 (2006-06)
Process MT_SM_GMSC
Figure 23.3/7: The mobile terminated s hort message service process in the GMS C W A IT_FOR_MT_SMS_CONFIRM, W A IT_FO R_A_SM_CONFIRM
23.3_7.5(6)
SC_ ABORT_Ind
MAP _U_AB ORT_Ind, MAP _P _ABORT_Ind, A _ABORT_Ind
MA P_ NOTICE_ Ind
MA P_ CLOS E_ Req
Yes
GMS C= V MSC? No
SE T RP _E RROR =SYS TE M FAILURE
A_AB ORT_ Req
MA P_U_ ABORT_Ind
S C_RP_ E RROR_Req
NULL
5968
5969
Figure 23.3/7 (sheet 5 to 6): Procedure MT_SM_GMSC
2342
3GPP
2343 Release 4
786
3GPP TS 29.002 V4.17.0 (2006-06)
Process MT_SM_GMSC
Fig ure 2 3 .3/7 : The m o bile term in ate d s hort m essa ge se rvice p roce ss in th e GMS C
23.3_7.6(6)
W A UT_ FOR_ M ORE _M ES SA GES
SC_ ABORT_ Ind
M AP _ U_ ABO RT_In d M AP _P _A BORT_ Ind A _A BORT_ Ind
M AP _NOTICE _in d
GMS C = VM S C ? Ye s No M AP _CLO SE_ Req
A _AB ORT_ Re q
MA P_ U _A BORT_ Ind
S C _A BORT_ Re q
NU LL
5970
5971
Figure 23.3/7 (sheet 6 of 6): Procedure MT_SM_GMSC
2344
3GPP
2345 Release 4
787
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition Check_Subscr_Identity_For_MT_SMS
Figure 23.3/8: Check of t he subscriber identit y for a mobile t erminated short m ess age in the servicing MSC and in the V LR
23.3_8(1)
Des t_Ref present
'No'
'Yes'
sm_RP _DA = LMSI
'No'
'No'
sm_RP _DA = IMSI
'Yes'
'Yes'
'Destination_ Ref erence := IMSI'
'Set_Dest ination_ Re ference_not_ included'
'sm_RP_DA := LMS I'
'User_error := Unexpect ed_Data _V alue'
'sm_RP _DA := IMS I'
OK
Error
OK
5972
5973
Figure 23.3/8: Macro Check_Subscr_Identity_For_MT_SMS
2346
3GPP
2347 Release 4
788
3GPP TS 29.002 V4.17.0 (2006-06)
5974
23.3.5 Procedure in the Servicing SGSN
5975 When initiating the dialogue with the servicing SGSN, the SMS Gateway MSC must provide the IMSI of the subscriber 5976 to whom the short message is directed. 5977 The IMSI is included in the sm-RP-DA information field of the MAP_MT_FORWARD_SHORT_MESSAGE 5978 indication. 5979 When receiving a MAP_OPEN indication primitive that is not associated with any MAP service indication primitive 5980 and if the dialogue is accepted, the MAP service-user in the servicing SGSN issues a MAP_DELIMITER request 5981 primitive in order to trigger the local MAP service-provider to confirm the dialogue. 5982 When receiving the first MAP_MT_FORWARD_SHORT_MESSAGE indication from the gateway MSC, the servicing 5983 SGSN performs some subscriber data checks, if the MAP service primitive is accepted and if short message service is 5984 supported in the servicing SGSN. 5985 The MAP_MT_FORWARD_SHORT_MESSAGE indication primitive is checked by the macro "Check_Indication". If 5986 the received MAP service primitive contains errors, the service is aborted and an unexpected data value error or data 5987 missing error is returned to the GMSC. 5988 If the SGSN does not support the short message service, the service is aborted in the servicing SGSN and the error 5989 "Facility Not Supported" is returned to the GMSC. 5990 If the connection is GPRS suspended, the SGSN sends to the GMSC an error specifying that the GPRS connection is 5991 suspended. 5992 The subscriber identity information that are included in the MAP service indication primitive is checked by the macro 5993 "Check_Subscr_Identity_For_MT_SMS" as follows: 5994 If the IMSI is included in the sm-RP-DA information field of the MAP_MT_FORWARD_SHORT_MESSAGE 5995 indication, the MAP_OPEN indication received from the gateway MSC shall not include a Destination Reference. 5996 If no Destination Reference has been received and the sm-RP-DA information field does not cover an IMSI the service 5997 is aborted in the servicing SGSN and the error "Unexpected Data Value" is returned to the GMSC. 5998 The following outcomes from the subscriber data checks can occur in SGSN: 5999 6000 6001 6002 6003 6004 6005 6006 6007
if the mobile subscriber is unknown, the unidentified subscriber error is forwarded to the GMSC; if the Confirmed by HLR indicator is set to Not Confirmed, the unidentified subscriber error is forwarded to the GMSC. if the GPRS Detached Flag is set to detached or the LA Not Allowed Flag is set to not allowed in the SGSN, an absent subscriber error with the diagnostic indication set to 'GPRS Detached' is forwarded to the GMSC and the MS not reachable for GPRS (MNRG) flag is set; If the location area identification is known and the "Confirmed by Radio Contact" indicator is set to "Confirmed", the paging procedure is invoked (see clause 25.3).Otherwise the search procedure is invoked (see clause 25.3).
6008 The result of the paging or the search procedure is processed as follows: 6009 6010 6011 6012 6013 6014 6015 6016 6017
if the procedure is completed successfully, the SGSN may trigger the Authentication, Ciphering and IMEI check procedures (see clauses 25.4 and 25.5). Then, if the procedure are completed successfully, the SGSN will send the short message to the MS; if the procedure is completed successfully, but the MS has no mobile terminated short message transfer capability, the SM delivery failure indication with cause "equipment not SM equipped" is provided to the GMSC; if the procedure is ended unsuccessfully because of subscriber already busy for SMS, another paging, emergency call, location updating, inter SGSN routing area update or a call set-up, the subscriber busy for MT SMS is provided to the GMSC.
2348
3GPP
2349 Release 4
789
3GPP TS 29.002 V4.17.0 (2006-06)
6018 6019 6020
if the procedure is ended unsuccessfully, the absent subscriber_SM error is forwarded to the GMSC with the absent subscriber diagnostic indication set to 'No Paging Response for GPRS', but if the location area is unknown, the system failure indication is provided to the GMSC.
6021 If forwarding of the short message is initiated, the SGSN awaits the result before one of the following responses is sent 6022 back to the GMSC: 6023 6024 6025 6026 6027
an acknowledgement if the short message has been successfully delivered to the mobile subscriber; an SM delivery failure error containing a parameter indicating either of the following: there is a MS protocol error or the MS memory capacity is exceeded; detailed diagnostic information (see clause 7.6.1.4) may also be carried; a system failure error if the delivery procedure is aborted.
6028 If the More Messages To Send flag was FALSE or the service MAP_MT_FORWARD_SHORT_MESSAGE ends 6029 unsuccessfully, the transaction to the gateway MSC is terminated. Otherwise, the servicing SGSN waits for the next 6030 short message from the Service Centre. 6031 When receiving the next MAP_MT_FORWARD_SHORT_MESSAGE indication from the gateway MSC the servicing 6032 MSC will act as follows: 6033 6034 6035 6036 6037 6038 6039 6040 6041
if the received primitive contains errors, the unexpected data value error or data missing error is provided to the gateway MSC; if the More Messages To Send flag is FALSE, the servicing SGSN will start the short message transfer procedure to the mobile subscriber. The successful or unsuccessful outcome of this procedure is reported to the gateway MSC and the transaction is terminated. if the More Messages To Send flag is TRUE, the servicing SGSN will start the short message transfer to the mobile subscriber. If the outcome of this procedure is unsuccessful, the reason is reported to the gateway MSC and the procedure is terminated. If the procedure is successful, it is acknowledged to the gateway MSC and more short messages can be received.
6042 The mobile terminated short message transfer procedure in the servicing SGSN is shown in figures 23.3/9 and 23.3/10. 6043 The page and search procedures are shown in figure 25.3/1 and 25.3/2.
2350
3GPP
2351 Release 4
790
3GPP TS 29.002 V4.17.0 (2006-06)
Process M T_S M_Transfer_SG SN
F ig ure 2 3.3 /9 : T h e mo b ile t erm in ate d s h ort m e s sa g e s e rv ic e pr oc e s s in th e S G S N N ULL
23.3_9.1(3)
R ec e ive _ O p e n_ In d 'O K ' D e s t_R e f_ r ec e iv e d 'Y es ' 'S tore _ D e s tina tion _ R e fe re n c e' 'N o' 'E rror' 'V r '
F igu re 25 .1 /1
'P e rform _ M A P _V r_ D ia logu e
R e fe r to th e re lev a nt v ers io n o f G S M 09 .0 2
W A IT _F O R _ S E R V IC E _ P R IM IT I VE
N UL L
N UL L
MAP_ D E LIM IT E R _ In d
M AP _ F S M _ In d
M A P _U _A B O R T _I nd , M A P _P _ A BO R T _ In d , M A P _C L O S E_ In d
MAP_ N O T IC E _ In d
MAP_ D E LIM IT E R _ Re q
C he c k _ I ndic a tio n 'O K '
F ig ure 2 5. 2/ 1 ' Erro r' F ig ure 2 3 .3/1 0
MAP_ C LO SE _ Re q
W A I T _F O R _ S E R V IC E _ P R I MIT IV E
MT _S M _S G S N
N UL L 'A b ort' 'N o ' NU LL 'E rr o r'
'O K ' M ore _m s g _ to _s e nt ' Ye s ' M A P _M T _ F O R W A R D _S H O R T _ M E S S A G E _R s p M A P _D E L IM IT E R _R e q
M A P _M T _ F O R W A R D _ S H O R T _ M E S S AG E _ R s p M A P _C LO S E _ R e q
W A IT _ F O R _M OR E_ M E S S AG ES
N UL L
6044
6045
Figure 23.3/9 (sheet 1 of 3): Procedure MT_SM_Transfer_SGSN
2352
3GPP
2353 Release 4
791
3GPP TS 29.002 V4.17.0 (2006-06)
Process M T_S M_Transfer_SG SN
F ig ure 2 3.3 /9 : T h e m o b ile t erm in ate d s h ort m e s sa g e s e rv ic e pr oc e s s in th e S G S N
23.3_9.2(3)
W A IT _ F O R _ MOR E_ M E S S AG ES
M A P_ M T _ FO R W A RD _ S HO R T_ M E S S A G E _ in d
C he c k _ In dic at io n E rro r OK
A _R P _ _M T _ D A T A_ re q
W A IT _ F O R _ SH O RT _ MESSAGE_ C O N F IR M A _ RP _ E R ROR _ i nd
A _R P _ A C K _ in d
' SE T U S E R E R RO R'
No
'M ore m es s a ges to s en d' Ye s
M A P _ M T _F O R W A R D _ SH O R T _M E S S A G E_ rs p M A P _C L O S E _re q
M A P_ M T _ F O R W A R D _ SH O R T _ M E S S A G E _rs p M A P _ D E L IM IT E R _r e q
NU L L
W A I T _F O R _ M ORE_ M ES S A G E S
6046
6047
Figure 23.3/9 (sheet 2 of 3): Procedure MT_SM_Transfer_SGSN
2354
3GPP
2355 Release 4
792
3GPP TS 29.002 V4.17.0 (2006-06)
Process M T_S M_Transfer_SG SN
F ig ure 2 3.3 /9 : T h e mo b ile t erm in ate d s h ort m e s sa g e s e rv ic e pr oc e s s in th e S G S N
23.3_9.3(3)
W A IT _ F O R _ M O R E _ M E SS A G E S , W A IT _ F O R _S H O R T _M E SS A G E _ C O N F IR M
M AP _ U _ A B O R T _ in d M A P_ P _A B O R T _ in d
A _ L LC _ R E LE A S E
M A P_ N O T IC E _ in d
A _ AB O R T _ req
M A P _U _ A B O R T_ re q
MAP_ C LO S E _ re q
A _ AB O R T _ re q
N U LL
6048
6049
Figure 23.3/9 (sheet 3 of 3): Procedure MT_SM_Transfer_SGSN
2356
3GPP
2357 Release 4
793
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefin ition MT_SM_S GS N
F ig u re 2 3 .3/ 10 : T h e m o b ile t erm in ate d s h ort m e ss a g e tran s fe r m ac ro in th e S G S N Ye s M T SM s u pp o rte d b y S G S N? No
23.3_10.1(3)
C h ec k_ S ub s c r_ Id en tity_ fo r_ M T _ SM S E rro r OK S u bs c rib e r k n ow n? Y es C o nf i rm e d by H LR ? Y es G P R S_ D e ta c he d_ F l a g = d eta c he d ? No L A_ N ot_ A ll o w e d_ F la g = n ot allo w e d ? No C o nf i rm e d b y ra dio c on ta c t? Y es LAI k no w n ? Y es P a ge _ M S C F ig u re 2 5. 3/ 1 No Ye s Ye s No No
SE T U E = F AC IL IT Y N O T SU P PO R T E D '
U s er_ error : = U ni de n tif ie d _ S u bs c ri be r
S E T U E = A B S EN T S U B SC R I BE R w ith d ia g no s tic ' G P R S D e tac h ed '
S E T M NR G
No
M A P_ M T _ F O R W A R D _ SM _ R s p M A P_ C LO S E _ re q
S e a rc h_f or_ M S_M SC
F igu re 25 .3 /2
N UL L
OK N ul l 'U s er_ erro r : = S y s te m _ F a ilure ' 1 P ag e 2 E RRO R No 'M T S M C A P A B ILI T Y? ' Y es 2 Page 2 E rro r OK U P DA TE LAI
E rro r 1 P a ge 2
N ull
'U s er_ erro r := S y s te m _ F a il ure '
'S E T U E = SM D E LI VE R Y F A ILU R E '
A _ AB O R T _ req
E R RO R
6050
6051
Figure 23.3/10 (sheet 1 of 3): Macro MT_SM_SGSN
2358
3GPP
2359 Release 4
794
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition MT_SM_SG SN
F ig u re 2 3.3 /1 0 : T h e mo bile t erm in ate d s ho rt m es s a ge tr an s fe r ma c ro in th e SG S N
23.3_10.2(3)
1 P ag e 1
2 P ag e 1
No
A b s en t s u b sc ribe r?
A -R P -M T -D A T A re q
Y es SE T US E R E RR O R 'S E T U E = AB S E N T S U B S C R IB E R w ith diag no s tic N o p ag in g' W A I T _F O R _ S HO R T_ M E SS A G E _ C O NFIRM
'SE T M N R G F LA G '
A-R P AC K -in d
A -RP E R RO R ind
M A P _M T _ F O R W A R D_ S M_ R s p M A P _C LO S E _ R e q
'S E T U S E R E RR O R'
OK NU LL
E rro r
6052
6053
Figure 23.3/10 (sheet 2 of 3): Macro MT_SM_SGSN
2360
3GPP
2361 Release 4
795
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition MT_SM_SG SN
F ig u re 2 3.3 /1 0 : T h e mo bile t erm in ate d s ho rt m es s a ge tr an s fe r ma c ro in th e SG S N
23.3_10.3(3)
W A IT _ F O R _S H O R T _M E S SA G E _ C O N F I R M
A _ L LC _ R E LE A S E _ ind
M A P _N O T IC E _ in d fro m G M SC
M A P _U _A B O R T _in d f rom G M S C , M A P_ P _ A BO R T _ in d fro m G M S C , M A P _C LO SE _ in d from G M S C
MA P _ C L O S E _R eq to G M S C
' SE T U E = S y s te m F a ilu r e '
A _ AB O R T _ Re q
E rro r
A b ort
6054
6055
Figure 23.3/10 (sheet 3 of 3): Macro MT_SM_SGSN
2362
3GPP
2363 Release 4
796
3GPP TS 29.002 V4.17.0 (2006-06)
6056
23.4 The Short Message Alert procedure
6057 The Short Message Alert procedure is used for alerting the Service Centre when the mobile subscriber is active after a 6058 short message transfer has failed because the mobile subscriber is not reachable or when the MS has indicated that it has 6059 memory capacity to accept a short message. 6060 The Short Message Alert procedure for the case when the mobile subscriber was not reachable is shown in 6061 figure 23.4/1.
6062 6063 6064 6065 6066 6067 6068 6069 6070 6071 6072 6073 6074 6075 6076 6077 6078 6079
+----+ MS +----+ -
1) 2) 3)
+---------+ +-----+ +-----+ +-----------+ Servicing VLR HLR Inter MSCorSGSN working MSC +---------+ +-----+ +-----+ +-----------+ 1. - -> 2. ---------> 3. -------> <-------4. 5.----------> + - - - 5.----------> + - - - 5.----------> + - - - <----------7. <----------7. <----------7.
+----+ SC +----+ 6. -> 6. -> 6. ->
6095
6080 6081 6082 6083 6084 6085 6086 6087 6088 6089 6090 6091 6092 6093 6094
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.140). 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. (*) In case of GPRS, messages 3) and 4) are sent/received by SGSN. (**) Those messages are not used by SGSN.
Figure 23.4/1: Short message alert procedure (Mobile is present)
6096 The Short Message Alert procedure for the case where the MS indicates that it has memory capacity to accept one or 6097 more short messages is shown in figure 23.4/2.
2364
3GPP
2365 Release 4
6098 6099 6100 6101 6102 6103 6104 6105 6106 6107 6108 6109 6110 6111 6112 6113 6114 6115 6116 6117
797
3GPP TS 29.002 V4.17.0 (2006-06)
+----+ MS +----+ - 6. <-
1) 2) 3) 4) 5) 6) 7) 8) 9) NOTE: (*) (**)
+---------+ +-----+ +-----+ +-----------+ Servicing VLR HLR Inter MSCorSGSN working MSC +---------+ +-----+ +-----+ +-----------+ 1. - -> 2. ---------> 3. -------> 5. <-------4. <--------- - - 7.----------> + - - - 7.----------> + - - - 7.----------> + - - - <----------9. <----------9. <----------9.
+----+ SC +----+ 8. -> 8. -> 8. ->
6132
6118 6119 6120 6121 6122 6123 6124 6125 6126 6127 6128 6129 6130 6131
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.140). MAP_ALERT_SERVICE_CENTRE_ACK. To all Service Centres in the Message Waiting List. Message 2) and 5) are not used by SGSN. In the case of GPRS messages 3) and 4) are sent/received by SGSN.
Figure 23.4/2: Short message alert procedure (MS memory capacity available)
6133 In addition the following MAP services are used in the MS memory available case: 6134 6135 6136 6137 6138 6139 6140 6141
MAP_PROCESS_ACCESS_REQUEST MAP_AUTHENTICATE MAP_SET_CIPHERING_MODE MAP_PROVIDE_IMSI MAP_CHECK_IMEI MAP_FORWARD_NEW_TMSI MAP_TRACE_SUBSCRIBER_ACTIVITY (*) Those messages are not used by SGSN.
(see clause 8.3); (*) (see clause 8.5); (*) (see clause 8.6); (*) (see clause 8.9); (*) (see clause 8.7); (see clause 8.9); (*) (see clause 9.1). (*)
6142 The Short Message Alert procedure when the MS indicates successful transfer after polling is shown in figure 23.4/3.
2366
3GPP
2367 Release 4
6143 6144 6145 6146 6147 6148 6149 6150 6151 6152 6153 6154 6155 6156 6157 6158
798
3GPP TS 29.002 V4.17.0 (2006-06)
+---------+ +-----+ +-----------+ +----+ Gateway HLR Inter SC MSC working MSC +---------+ +-----+ +-----------+ +----+ 1.---------> <---------2. 3.----------> 4. - - - - -> 3.----------> 4. + - - - - -> 3.----------> 4. + - - - - -> <----------5. <----------5. <----------5.
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.140). MAP_ALERT_SERVICE_CENTRE_ACK. To all Service Centres in the Message Waiting List.
6167
6159 6160 6161 6162 6163 6164 6165 6166
Figure 23.4/3: Short message alert procedure (Successful transfer after polling)
6168
23.4.1 Procedures in the Servicing MSC
6169 The activation of the MAP_PROCESS_ACCESS_REQUEST service is described in the clause 23.6.2. 6170 After receiving the SM memory capacity available indication, the servicing MSC sends the MAP_READY_FOR_SM 6171 request to the VLR indicating memory available. The outcome of that procedure is one of the following: 6172 6173 6174 6175 6176 6177
successful acknowledgement. The MSC sends the corresponding message to the MS; negative acknowledgement, where the error causes are treated as follows: unexpected data value, data missing and system failure errors are reported as network out of order error to the MS; facility not supported is reported as requested facility not implemented error to the MS;
procedure failure, which is reported as network out of order error to the MS if a connection to the MS still exists.
6178 The short message alert procedure in the MSC for the MS memory capacity available case is shown in figure 23.4/4.
2368
3GPP
2369 Release 4
799
3GPP TS 29.002 V4.17.0 (2006-06)
Process SM_Alert_MSC
Figure 23.4/4: The short message alert process in t he servicing MS C for MS memory capacity available. NULL
23.4_4(1)
A_RP_SM_ME MORY_AV AILAB LE
NULL
MAP _REA DY_FOR_SM_req, MAP _DELIMITE R_ req
WA IT_FOR_ RES ULT
MAP _REA DY_ FOR_S M_cnf
A _MM _ RE LE AS E_ ind
MAP _ NOTICE_ ind
MAP _ CLOS E_ind
MA P_U_A BORT_ind, MA P_P_AB ORT_ind
Check _ confirmation
MA P_U_ A BO RT_ req
MAP _ CLOSE _ req
OK
P rovider E rror, User Error, Data Error
'SE T RP_ ERROR = NE TWOR K OUT OF ORDE R'
A _RP_ A CK _ req
'S ET RP E RROR'
A _RP_ ERROR_ req
A_RP_ ERROR_ req
6179
6180
Figure 23.4/4: Procedure SM_Alert_MSC
2370
3GPP
2371 Release 4
800
3GPP TS 29.002 V4.17.0 (2006-06)
6181 6182 23.4.2.1
6183 6184 6185 6186 6187
23.4.2 Procedures in the VLR
The Mobile Subscriber is present
When receiving the MAP_PROCESS_ACCESS_REQUEST indication, MAP_UPDATE_LOCATION_AREA indication while the MS not reachable flag (MNRF) is set, the VLR will send the MAP_READY_FOR_SM request towards the HLR. The Alert Reason is set to indicate that the mobile subscriber is present for non GPRS. If the authentication procedure is initiated and it fails, the VLR will not initiate the service. The process in VLR is described in detail in the clause 25.10.
6188 23.4.2.2
The Mobile Equipment has memory available
6189 The MAP_PROCESS_ACCESS_REQUEST indication starts the MAP_PROCESS_ACCESS_REQUEST service in 6190 the VLR. The application context in the MAP_OPEN indication refers to the short message alerting procedure. 6191 6192 6193 6194
If the service MAP_PROCESS_ACCESS_REQUEST is successful, the VLR waits for the next message from the MSC. When receiving the MAP_READY_FOR_SM indication from the MSC, the VLR will check the contents. Data errors are reported to the MSC as an unexpected data value or data missing error, depending on the error. If the primitive passes the data check, the VLR forwards it to the HLR and awaits an acknowledgement.
6195 When receiving the MAP_READY_FOR_SM confirmation from the HLR and the Alert Reason is MS memory 6196 available, the VLR will act as follows: 6197 6198 6199 6200 6201 6202
the MAP_READY_FOR_SM response is sent to the MSC as follows: an acknowledgement in the positive case; system failure error, if unexpected data value, data missing, or unknown subscriber errors are received, otherwise the error cause received from the HLR; a facility not supported error, if the HLR supports MAP Vr only; procedure failure is reported as a system failure error.
6203 The short message alert procedure in the VLR is shown in figures 23.4/5.
2372
3GPP
2373 Release 4
801
3GPP TS 29.002 V4.17.0 (2006-06)
Process SM_Alert_VLR
Figure 23.4/5: The short messages alert proc ess in the VLR f or MS memory capac it y available
23.4_5(1)
NULL
Receive_ Open_Ind
OK W F_ S ERV ICE _ P RI MITIV E W F_ INVOK E
Error, V1
P rocess_ A ccess_ Req_VLR
MAP _READ Y_ FOR_S M_ind
OK
E rror NULL
C heck _ Indic ation Error OK MA P-OPE N-req MAP_REA DY _FOR_S M_ req MA P_DELIM ITER_req W F_INVO KE, W F_RE SULT
Receive_ O pen_Cnf Error OK W F_ RE SULT 'Set UE = system failure' 'Set UE = f acility not s upported' V1
MAP _ NOTICE _ ind
MAP _U_A BORT_ind, MA P_p_AB ORT_ind, MAP _CLO SE_ind
MAP _ CLOS E_ req
MAP _REA DY_ FOR_S M_cnf MA P_U_ AB ORT_ind Check_ Confirm ation OK P rovider E rror, User Error, Data Error NULL
MAP _REA DY _FOR_S M_rs p MAP _CLOS E_req
'S ET USE R E RRO R' NULL
6204
6205
Figure 23.4/5: Procedure SM_Alert_VLR
2374
3GPP
2375 Release 4
802
3GPP TS 29.002 V4.17.0 (2006-06)
6206
6207 6208 6209 6210 6211 6212 6213 6214 6215 6216
23.4.3 Procedures in the HLR
When receiving the MAP_READY_FOR_SM indication, the HLR will check the contents. Data errors are reported to the VLR as an unexpected data value or a data missing error depending on the error. If the HLR does not support the MNRF or MNRG, MCEF, and MWD a facility not supported error is reported to the VLR or SGSN. If the IMSI is unknown an unknown subscriber error is reported to the VLR or SGSN. Otherwise an acknowledgement is returned to the VLR or SGSN. If neither the MS not reachable flag (MNRF) or the MS not reachable for GPRS (MNRG) flag, nor the memory capacity exceeded flag (MCEF) are set, and MAP_READY_FOR_SM is received from the VLR or SGSN, the HLR sets a timer and waits for it to expire. This ensures that in the race situation the MAP_REPORT_SM_DELIVERY_STATUS service (as described in the clause 23.6) for the same subscriber can be carried out when delayed in the GMSC. If the Alert Reason indicates the mobile present for non GPRS situation, or when the update location procedure has been successfully completed or Supplementary Service Control request is received, the MS not reachable flag (MNRF) is cleared and the service centre alert procedure is initiated. If the memory capacity exceeded flag is set, the MS not reachable flag is cleared and stored reason for absence for non GPRS are cleared but the alert procedure is not started. If the Alert Reason indicates the mobile present for GPRS situation, or when the Update GPRS location procedure has been successfully completed, the MS not reachable for GPRS (MNRG) flag is cleared and the service centre alert procedure is initiated. If the memory capacity exceeded flag is set, the MS detach for GPRS flag is cleared and stored reason for absence for GPRS are cleared but the alert procedure is not started. If the Alert Reason indicates the memory available for non GPRS situation, the HLR initiates the alert procedure. The MS not reachable and memory capacity available flags are cleared. If the Alert Reason indicates the memory available for GPRS situation, the HLR initiates the alert procedure. The MS detach for GPRS and memory capacity available flags are cleared. If the MAP_REPORT_SM_DELIVERY_STATUS indication is received and it indicates the successful transfer of the mobile terminated short message for non GPRS, the HLR initiates the alert procedure described in the clause 25.10 and clears MCEF and MNRF flags and stored reason for absence for non GPRS are cleared. If the MAP_REPORT_SM_DELIVERY_STATUS indication is received and it indicates the successful transfer of the mobile terminated short message for GPRS, the HLR initiates the alert procedure described in the clause 25.10 and clears MCEF and MNRG flags and stored reason for absence for GPRS are cleared.
6217 The short message alert procedure in the HLR is shown in figures 23.4/6 and 25.10/2.
2376
3GPP
2377 Release 4
803
3GPP TS 29.002 V4.17.0 (2006-06)
Process SM_Alert_HLR
F ig ure 2 3.4 /6 : T he s ho rt m e ss a g e a lert p roc e s s in t he H L R W FS E RV ICE P R IM IT I VE
23.4_6.1(2)
NU L L
M A P _R E AD Y _ F O R _ SM _ in d
MAP_ N O T IC E _ind
M A P _P _ A B O R T _ind
M A P _R EP O R T _ S M _ D E LI V ER Y _ S T A T U S _ in d
R e c eiv e _ O p en _In d
C he c k _ In dic a tio n
E rro r
Vr
OK
E rr or
OK
MAP_ C LO S E _ re q
R e po rt_ SM _ D eliv e ry_ S ta t_H L R
Re fe r to th e relev a nt v ers ion o f G S M 09 .0 2 Pe rfo rm _ M A P_ V r_ D ia lo gu e
M N R F or M N R G , M C E F, M W D s u pp o rte d y es ye s S u b s cribe r k n ow n no S E T UE = U NK N OW N S U B S C R IB E R
no N UL L E rro r OK
S to p R A C E tim e r
N UL L
SET UE = F A C IL IT Y N O T SU P P O R T E D
1 P ag e 2
M A P _R E AD Y _F O R _ S M _r sp , M A P _C LO SE
S ta rt R A C E tim e r
M C E F o r M NR G o r M N R F s et
no A LE R T _ PE N D IN G
Y es 1 P ag e 2 RA C E T I M ER T I M E-O U T R ec e iv e _ O p en _ Ind
N ULL
Pe rfo rm _ M AP _ V 1_ D ia lo gu e
V1
E rro r
OK
N ULL
A LE R T _ PE N D IN G
W F_ S E R V IC E _ P R IM IT IV E
6218
6219
Figure 23.4/6 (sheet 1 of 2): Process SM_Alert_HLR
2378
3GPP
2379 Release 4
804
3GPP TS 29.002 V4.17.0 (2006-06)
Process SM_Alert_HLR
F ig ure 2 3.4 /6 : T he s ho rt m e ss a g e a lert p roc e s s in t he H L R
23.4_6.2(2)
1 Page 1
R ea s o n M e m ory a v a ilab le f or G PR S S u bs c ribe r p res e nt fo r G P RS S ub s c rib er pre s en t f or no n- G P R S M e mo ry a v a ilab le f or n on -G P R S
C lea r M C E F an d M NR G
C le ar M NR G
C le ar M N RF
Clea r M CE F an d M NR F
M CE F se t No A le rt_ S erv ice _ C ent re_ H L R A le rt _ S erv ice _ C e nt re _ H L R
Y es
Y es
M CE F s et
No
A lert_ S e rv ic e _ C en tre_ H LR
A le rt_ S erv ice _ C ent re_ H L R
N UL L
6220
6221
Figure 23.4/6 (sheet 2 of 2): Process SM_Alert_HLR
2380
3GPP
2381 Release 4
805
3GPP TS 29.002 V4.17.0 (2006-06)
6222
23.4.4 Procedures in the Interworking MSC
6223 When a MAP_ALERT_SERVICE_CENTRE indication is correctly received by the IWMSC, the IWMSC will forward 6224 the alerting to the given Service Centre if possible. 6225 Data errors are reported to the HLR as an unexpected data value or a data missing error depending on the error. 6226 The short message alert procedure is shown in figure 23.4/7.
2382
3GPP
2383 Release 4
806
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess Alert_SC_IW MSC
F ig u re 2 3.4 /7 : T h e s ho rt m e ss a g e a le rt m e ss a g e in th e IW M S C
23.4_7(1)
N UL L
R ec e ive _ O p e n_ In d
V1 P e rfor m _ M A P _ V1 _ D ia log u e
E rror
OK W F_ S E R VI C E _ P R IM IT IV E
NU L L
M AP _ A LE R T _ _S E R V IC E _ _C E N T R E _ in d
MAP_ N O T IC E _ ind
C hec k _ In dic at io n
MAP_ C LO S E _ re q E rro r N UL L
OK S C _R P _ A L E RT _ _ S C _ req
M AP _ A LE R T _ S E R V IC E _C E N T R E _rs p M AP _ C LO S E _ re q
N UL L
6227
6228
Figure 23.4/7: Process Alert_SC_IWMSC
2384
3GPP
2385 Release 4
807
3GPP TS 29.002 V4.17.0 (2006-06)
6229 6230 23.4.5.1
23.4.5 Procedures in the Servicing SGSN
The Mobile Subscriber is present
6231 When receiving Page response, Attach request or Routing area update request messages (3GPP TS 24.008 [35]), while 6232 the MS not reachable for GPRS (MNRG) flag is set, the SGSN will send the MAP_READY_FOR_SM request towards 6233 the HLR. The Alert Reason is set to indicate that the mobile subscriber is present for GPRS. 6234 When receiving the answer, the SGSN will act as follows: 6235 6236
MNRG is cleared if the procedure is successful MNRG is not cleared if the procedure is not successful
6237 The process in SGSN is described in detail in the clause 25.10/3.
6238 23.4.5.2
The Mobile Equipment has memory available
6239 After receiving the SM memory capacity available indication, the servicing SGSN sends the MAP_READY_FOR_SM 6240 request to the HLR indicating memory available for GPRS. The outcome of that procedure is one of the following: 6241 6242 6243 6244 6245 6246
successful acknowledgement. The SGSN sends the corresponding message to the MS; negative acknowledgement, where the error causes are treated as follows: unexpected data value, data missing and system failure errors are reported as network out of order error to the MS; facility not supported is reported as requested facility not implemented error to the MS;
procedure failure, which is reported as network out of order error to the MS if a connection to the MS still exists.
6247 The short message alert procedure in the SGSN for the MS memory capacity available case is shown in figure 23.4/8.
2386
3GPP
2387 Release 4
808
3GPP TS 29.002 V4.17.0 (2006-06)
Process Subscriber_Present_S GSN
N ULL F ig ure 2 3.4 /8 : T h e sh o rt me s s a ge a le rt p roc e s s in th e S G S N fo r m o b ile p res en t s itua tion
23.4_8(1)
-P ag e R e s po n s e -A tta c h R e qu e s t o r R ou ting A rea U pd a te R e qu es t (S e e T S 04 .0 8) no M NR G s et Ye s 'S E T R E A S O N = M O BI LE S U B SC R I B ER P R E S E N T F OR GPR S' N UL L
M A P_ O P E N _re q M A P_ R E A D Y _F O R _S M _ re q M A P_ D EL IM IT ER _re q R e c eive _ O p e n_ C n f OK W FR E SP O N S E
F igu re 25 .1 /2
E rro r
Vr
Pe rfo rm _ M A P_ V r_ D ia lo gu e
M A P _R E AD Y _F O R _ S M _ rs p
M AP _ U _ A B O R T _ ind M A P _P _A B O R T _ in d M A P_ C L O S E _ in d
ye s E rro r no
C le ar M N R G
6248
6249
Figure 23.4/8: Process Subscriber_Present_SGSN
2388
3GPP
2389 Release 4
809
3GPP TS 29.002 V4.17.0 (2006-06)
6250
23.5 The SM delivery status report procedure
6251 The SM delivery status report procedure is used to set the Service Centre address into the message waiting list in the 6252 HLR because the subscriber is absent or unidentified or the memory capacity is exceeded. The procedure sets 6253 6254 6255
the memory capacity exceeded flag in the HLR if the MS memory does not have room for more messages and/or the MS not reachable flag for non GPRS in the case of unidentified or absent subscriber and/or the MS not reachable for GPRS flag in the case of unidentified or absent subscriber for GPRS
6256 Additionally the procedure is used to report the HLR about the successful transfer for GPRS or non GPRS after the 6257 Service Centre has polled the subscriber. This procedure is described also in the clause 23.4. 6258 The SM delivery status report procedure is shown in figure 23.5/1.
6259 6260 6261 6262 6263 6264 6265 6266 6267 6268 6269 6270
+---------+ +-----+ +-----+ +---------+ Visited VLR HLR Gateway MSCorSGSN MSC +---------+ +-----+ +-----+ +---------+ 1. -----------+----------+-------> 2. <------- 3. -------> - - -
1) 2) 3) 4)
+----+ SC +----+ 4. ->
6278
6271 6272 6273 6274 6275 6276 6277
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.140).
Figure 23.5/1: Short message delivery status report procedure
6279
23.5.1 Procedures in the HLR
6280 When the HLR receives a MAP_REPORT_SM_DELIVERY_STATUS indication, it acts as described in the 6281 clause 23.6, macro Report_SM_Delivery_Stat_HLR. 6282 The short message delivery status report process in the HLR is shown in figure 23.5/2.
2390
3GPP
2391 Release 4
810
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess SM _Delivery_S tatus_R eport_HL R
F ig u re 2 3.5 /2 : T h e re po rt S M deliv ery p ro c es s in th e H L R
23.5_2(1)
N U LL
M A P _R E P O R T S M _D E L IV E R Y S T A T U S _ in d
R ep o rt_ S M _ D elive ry_ S t at_ H L R
F ig. 2 3.6 /1
6283
6284
Figure 23.5/2: Process SM_Delivery_Status_Report_HLR
2392
3GPP
2393 Release 4
811
3GPP TS 29.002 V4.17.0 (2006-06)
6285
23.5.2 Procedures in the gateway MSC
The GMSC invokes the short message delivery status report procedure if an absent subscriber_SM indication, unidentified subscriber indication, SM delivery failure error indicating MS memory capacity exceeded or both are received from the servicing MSC, SGSN or both during a mobile terminated short message transfer, and the HLR has not indicated that the SC address is included in the MWD. The unidentified subscriber indication is however processed as the absent subscriber_SM indication. In case of successful SMS delivery on the second path, the successful SMS Delivery outcome is sent in combination with the unsuccessful SMS Delivery outcome to the HLR. The service is invoked also when the HLR has indicated that either of the flags MCEF, MNRF or both are set and the first SM delivery was successful from the servicing MSC or, in case of subsequent SM, the last SM delivery was successful from the servicing MSC. The service is invoked also when the HLR has indicated that either of the flags MCEF, MNRF or both are set and the SM delivery was successful from the servicing SGSN or, in case of subsequent SM, the last SM delivery was successful from the servicing SGSN. The reason for unsuccessful, successful for GPRS, non GPRS or both deliveries of the short message are included in the SM Delivery Outcome in the MAP_REPORT_SM_DELIVERY_STATUS request. In the case of an unsuccessful delivery due to the subscriber being absent the absent subscriber diagnostic indication (if available) is also included in the MAP_REPORT_SM_DELIVERY_STATUS request. If the reason for unsuccessful delivery is absent subscriber with diagnostic Paging failure for GPRS or non GPRS, the two SM Delivery Outcomes absent subscriber with both diagnostics Paging failure for GPRS and non GPRS is included in the MAP_REPORT_SM_DELIVERY_STATUS request.
6286 The GMSC sends the MAP_REPORT_SM_DELIVERY_STATUS request to the HLR. As a response the GMSC will 6287 receive the MAP_REPORT_SM_DELIVERY_STATUS confirmation reporting: 6288 6289 6290 6291 6292
successful outcome of the procedure. The acknowledge primitive may contain the MSISDN-Alert number which is stored in the MWD List in the HLR; unsuccessful outcome of the procedure. The system failure indication is forwarded to the SC. In that case, if the SM Delivery Outcome was successful SMS delivery for GPRS or non GPRS (combined or not with another unsuccessful reason), a successful report is forwarded to the SC.
6293 A provider error is indicated as a system failure to the SC. 6294 Note that the indication, on which number belongs the SGSN and MSC, received from the HLR at routing information 6295 result (see clause 23.3.3) will enable the GMSC to map the causes received from the SGSN, MSC or both into the 6296 appropriate causes for GPRS, non GPRS or both, and send them to the SC and HLR. 6297 The procedure towards the Service Centre may also be aborted. If so the operation towards the HLR is also aborted. 6298 The short message delivery status report procedure in the GMSC is shown in figure 23.5/3.
2394
3GPP
2395 Release 4
812
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition Report_SM_Delivery_Stat_GMSC
Figure 23.5/3: The report S M delivery status mac ro in t he GMSC
23.5_3(1)
MAP _OPE N_req MAP _RE PORT_SM_ DELIVE RY _S TATUS_req MAP _DE LIMITE R
Rec eive_ Open_Cnf
OK
ERROR
V1
W A IT_FOR_ CONFIRM
'Reason' A bsent Subsc riber
O ther reason MA P_RE PORT_ S M_DE LIVE RY_ S TATUS _cnf
Perform_ MA P_V1_ Dialogue
Check _ Conf irmat ion
OK
OK
Provider Error, User Error, Data Error
'Set UE = S ystem Failure'
OK
ERROR
W A IT_FO R_ CONFIRM
MAP _ NOTICE_ ind
MAP _U_A BORt_ind, MAP _P_AB ORT_ind, MAP _CLOS E_ind
MAP _ CLO SE _ req
NULL
6299
6300
Figure 23.5/3: Macro Report_SM_Delivery_Stat_GMSC
2396
3GPP
2397 Release 4
813
3GPP TS 29.002 V4.17.0 (2006-06)
6301 6302
23.6 Common procedures for the short message clause
23.6.1 The macro Report_SM_Delivery_Stat_HLR
6303 This macro is used when the HLR receives a MAP_REPORT_SM_DELIVERY_STATUS indication from the GMSC. 6304 The HLR responses to the indication as follows: 6305 6306 6307 6308 6309 6310 6311 6312 6313 6314 6315 6316 6317 6318 6319 6320 6321 6322 6323 6324 6325
if the flag GPRS Support Indicator is absent then if the subscriber is a GPRS subscriber and a non-GPRS subscriber with the option transfer of SM via the SGSN when GPRS is not supported in the GMSC or if the subscriber is a GPRS subscriber only, the HLR shall interpret the delivery outcome as a GPRS delivery outcome. if invalid data content is detected, an unexpected data value error or a data missing error is returned to the GMSC; if the MSISDN number provided is not recognised by the HLR, an unknown subscriber error is returned to the GMSC; if the MAP_REPORT_SM_DELIVERY_STATUS indication reports a successful SM delivery, the Service Centres in the Message Waiting list are alerted as described in the clause 25.10; if the SM Delivery Outcome reports unsuccessful delivery and the inclusion of the SC address in the MWD is not possible, a message waiting list full error is returned to the GMSC; if the SM Delivery Outcome reports unsuccessful delivery and the message waiting list is not full, the given Service Centre address is inserted and an acknowledgement is sent to the GMSC. If the MSISDN-Alert stored in the subscriber data is not the same as that received in the MAP_REPORT_SM_DELIVERY_STATUS indication, the MSISDN-Alert is sent in a response primitive to the GMSC; The SC address is only stored in the MWD if the unsuccessful SM Delivery Outcome is not received in combination with another successful SM Delivery Outcome
if the SM Delivery Outcome is MS memory capacity exceeded for non GPRS, the HLR sets the memory capacity exceeded flag in the subscriber data and resets the MNRF; if the SM Delivery Outcome is MS memory capacity exceeded for GPRS the HLR sets the memory capacity exceeded flag in the subscriber data and resets the MNRG; if the SM Delivery Outcome is absent subscriber for non GPRS, the HLR sets the mobile station not reachable flag in the subscriber data. If a reason for absence is provided by the GMSC then this is stored in the mobile station not reachable reason (MNRR) in the subscriber data. if the SM Delivery Outcome is absent subscriber for GPRS, the HLR sets the mobile station not reachable for GPRS flag in the subscriber data. If a reason for absence is provided by the GMSC then this is stored in the mobile station not reachable reason (MNRR) in the subscriber data.
6326 Note that a combination of all the SM Delivery Outcome specified above may be provided to the HLR from the SMS6327 GMSC. 6328 The short message delivery status report macro in the HLR is shown in figure 23.6/1.
2398
3GPP
2399 Release 4
814
3GPP TS 29.002 V4.17.0 (2006-06)
Macro definitio n Report_SM_Delivery_Stat_HLR
Fig u re 23 .6 /1 : The re p ort S M de liv e ry s tat us m ac ro in th e HL R
23.6_1(1)
C h ec k _ I n dica t io n OK ' Su b s cr ib er k now n ' Y es D e livery O ut c om e ' SE T UE = U NK N OW N S U B SC RI B E R' U n s uc ce ssf ul t ran sfe r No
E rr or
'C le ar M CE F a nd M N RF'
S u cce ss fu l Tr an sfer
M A P_ RE P O R T_ S M _ DE L IV E RY _ S TA TUS _ rsp M AP _ CL O S E _ req A lert _ S erv ic e_ C en tre _H L R 'S et M S IS DN Ale rt'
' Up da t e M e s s ag e W aiting D a ta' Ye s 'S to rin g s ucc e ss f ul'
No
No ' SE T UE = M E S S A G E W A ITI NG LI ST FU LL '
MS IS D N = MS I S DN A lert ? Yes
A b se n t S u bs cribe r
De liv e ry O u tc om e
M S m e m o ry c ap a c ity ex ce ed e d ' S et M C E F' M A P -RE P O R T_S M DE L IV E R Y_ S TA TU S _rs p M A P_ C LO S E_ re q
'S et M NR F'
Re aso n fo r ab s e nce av a ila b le ? Yes St o re re a so n in s ub scrib e r D ata in M N RR C hec k _A bse n t_ Su b s cr ib e rS M _ In _H L R
No E rro r
S ee TS ab .cd e
M A P _ RE P O R T_S M _ D E LI V ER Y _S TA T US _r sp M A P _ CLO S E_ re q
OK
6329
6330
Figure 23.6/1: Macro Report_SM_Delivery_Stat_HLR
2400
3GPP
2401 Release 4
815
3GPP TS 29.002 V4.17.0 (2006-06)
6331 6332
24
GPRS process description
24.1 General
6333 The MAP GPRS procedures are used for the Network Requested PDP-Context Activation procedures. 6334 The stage 2 specification for General Packet Radio Service (GPRS) is in 3GPP TS 23.060 [104] [100].
6335
24.1.1 Process in the HLR for Send Routing Information for GPRS
6336 The MAP process in the HLR to provide routing information for a network-requested PDP context activation is shown 6337 in figure 24.1/1. The MAP process invokes macros not defined in this clause; the definition of these macros can be 6338 found as follows: 6339 6340
Receive_Open_Ind Check_Indication
see clause 25.1.1; see clause 25.2.1.
6341 Successful outcome 6342 When the MAP process receives a MAP_OPEN indication with the application context gprsLocationInfoRetrieval, it 6343 checks it by invoking the macro Receive_Open_Ind. 6344 If the macro takes the OK exit, the MAP process waits for a service indication. 6345 If a MAP_SEND_ROUTING_INFO_FOR_GPRS service indication is received, the HLR sends a Send Routing Info 6346 For Gprs request to the GPRS application process in the HLR, and waits for a response. The Send Routing Info For 6347 Gprs request contains the parameter received in the MAP_SEND_ROUTING_INFO_FOR_GPRS service indication. 6348 If the GPRS application process in the HLR returns a positive response containing the routing information, the MAP 6349 process constructs a MAP_SEND_ROUTING_INFO_FOR_GPRS service response containing the routing info, 6350 constructs a MAP_CLOSE service request, sends them to the GGSN and returns to the idle state. 6351 Negative response from HLR GPRS application process 6352 If the GPRS application process in the HLR returns a negative response, the MAP process constructs a 6353 MAP_SEND_ROUTING_INFO_FOR_GPRS service response containing the appropriate error, constructs a 6354 MAP_CLOSE service request, sends them to the GGSN and returns to the idle state. 6355 Failure of dialogue opening with the GGSN 6356 If the macro Receive_Open_Ind takes the Vr exit or the Error exit, the MAP process returns to the idle state. 6357 If the MAP provider sends a MAP_P_ABORT while the MAP process is waiting for a service indication, the MAP 6358 process returns to the idle state. 6359 If the MAP provider sends a MAP_NOTICE while the MAP process is waiting for a service indication, the MAP 6360 process sends a MAP_CLOSE request to terminate the dialogue and returns to the idle state.
2402
3GPP
2403 Release 4
816
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess Sen d_R outing_Info_For_ Gprs_H LR
F ig u re 2 4. 1/ 1 : T h e S en d R o u tin g In fo F o r G p rs p ro c e s s in th e H L R
24.1_1(1)
S ig n als t o/f rom th e rig ht are to/ fro m th e G P R S ap p lic atio n p roc es s
Idle
R e c eiv e_ O pe n _In d
S e c tio n 25 .1
OK W a it_ F o r_ S ervic e_ Ind ic atio n Id le
V r, E rro r
M A P_ P _ A B O R T _ in d
M A P _ S E N D _ R O U T IN G _IN F O _ F O R _ G P R S _ in d
M A P_ N O T IC E _ ind
S e n d R o ut in g In fo F o r G p rs Id le W a it fo r R o ut ing In fo
M A P_ C L O S E _ r eq
Id le S en d R o u tin g In fo F or G p rs ne ga tiv e res po n se S en d R ou t in g In fo F o r G p rs Ack
S et U E
S et R ou tin g In fo
M A P _ S E N D _ R O U T ING _IN F O _ F O R _G P R S _rs p , M A P _ C L O S E _ req
Idle
6361
6362
Figure 24.1/1: Process Send Routing Info For Gprs_HLR
2404
3GPP
2405 Release 4
817
3GPP TS 29.002 V4.17.0 (2006-06)
6363
24.1.2 Process in the GGSN for Send Routing Information for GPRS
When the MAP process receives a Send Routing Info For Gprs request from the GPRS application process in the GGSN, it requests a dialogue with the HLR whose identity is contained in the Send Routing Info For Gprs request by sending a MAP_OPEN service request, requests routeing information using a MAP_SEND_ROUTING_INFO_FOR_GPRS service request and invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the HLR.
6364 Successful Outcome 6365 6366 6367 6368 6369 6370
6371 If the MAP process receives a MAP_SEND_ROUTING_INFO_FOR_GPRS service confirm from the HLR, the MAP 6372 process invokes the macro Check_Confirmation to check the content of the confirm. 6373 If the macro Check_Confirmation takes the OK exit, the MAP process sends a Send Routing Info For Gprs ack 6374 containing the routing information received from the HLR to the GPRS application process in the GGSN and returns to 6375 the idle state. 6376 Failure of dialogue opening with the HLR 6377 If the macro Receive_Open_Cnf takes the Vr exit or the Error exit, the MAP process sends a negative response to the 6378 GPRS application process in the GGSN and returns to the idle state. 6379 Error in MAP_SEND_ROUTING_INFO_FOR_GPRS confirm 6380 If the MAP_SEND_ROUTING_INFO_FOR_GPRS service confirm contains a user error or a provider error, or the 6381 macro Check_Confirmation indicates that there is a data error, the MAP process sends a Send Routing Info For Gprs 6382 negative response to the GPRS application process in the GGSN and returns to the idle state. 6383 Abort of HLR dialogue 6384 After the dialogue with the HLR has been established, the MAP service provider may abort the dialogue by issuing a 6385 MAP_P_ABORT or a MAP_U_ABORT indication. In this case, the MAP process sends a Send Routing Info For Gprs 6386 negative response to the GPRS application process in the GGSN and returns to the idle state. 6387 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 6388 dialogue with the HLR, sends a Send Routing Info For Gprs negative response indicating system failure to the GPRS 6389 application process in the GGSN and returns to the idle state.
2406
3GPP
2407 Release 4
818
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess Send_Routing_Info_For_ Gprs_ GG SN
F ig u re 2 4.1 /2 : S en d R o u tin g In fo F o r G prs p roc es s in th e G G S N
24.1_2(1)
S ig na ls to /f ro m th e rig ht are to /fro m th e G P R S ap p lic atio n p roc es s
Idle
S e n d R o ut in g In fo F o r G p rs
M A P _ O P E N _ Re q , M A P _ S E N D _ R O U T IN G _IN F O _ F O R _ G P R S _ R eq , M A P _ D E L IM IT E R _ R e q R e c eiv e_ O pe n _c n f
OK W A IT _ F O R _ ACK
V r, E rro r S en d R ou tin g In fo F o r G p rs N ega tive R e s po n se
M A P _ S E N D _ R O U T IN G _ IN F O _ F O R _ G P R S _ C nf
M A P _P _ A B O R T _ Ind , M A P _U _ A B O R T _ in d
MA P _ N O T IC E _ In d
Id le
C h ec k _ C o n firm a tio n
M A P _ CL O S E Re q
OK
P ro vid e r E rro r, U s e r E rror, D ata E r ror S e n d R o ut in g I nfo F or G p rs N e ga tiv e R es p o ns e
S en d R ou ting In fo F o r G p rs Ack
Idle
6390
6391
Figure 24.1/2: Process Send_Routing_Info_For_Gprs_GGSN
2408
3GPP
2409 Release 4
819
3GPP TS 29.002 V4.17.0 (2006-06)
6392
24.2.1 Process in the HLR for Failure Report
6393 The MAP process in the HLR to set the MNRG (Mobile station Not Reachable for GPRS) flag for the subscriber is 6394 shown in figure 24.2/1. The MAP process invokes macros not defined in this clause; the definition of these macros can 6395 be found as follows: 6396 6397
Receive_Open_Ind Check Indication
see clause 25.1.1; see clause 25.2.1.
6398 Successful outcome 6399 When the MAP process receives a MAP_OPEN indication with the application context failureReport, it checks it by 6400 invoking the macro Receive_Open_Ind. 6401 If the macro takes the OK exit, the MAP process waits for a service indication. 6402 If a MAP_FAILURE_REPORT service indication is received, the HLR sends a Failure Report request to the GPRS 6403 application process in the HLR, and waits for a response. The Failure Report request contains the parameter received in 6404 the MAP_FAILURE_REPORT service indication. 6405 If a positive response is received, the MAP process constructs a MAP_FAILURE_REPORT service response, 6406 constructs a MAP_CLOSE service request, sends them to the GGSN and returns to the idle state. 6407 Negative response from HLR GPRS application process 6408 If the GPRS application process in the HLR returns a negative response, the MAP process constructs a 6409 MAP_FAILURE_REPORT service response containing the appropriate error, constructs a MAP_CLOSE service 6410 request, sends them to the GGSN and returns to the idle state. 6411 Failure of dialogue opening with the GGSN 6412 If the macro Receive_Open_Ind takes the Vr exit or the Error exit, the MAP process returns to the idle state. 6413 If the MAP provider sends a MAP_P_ABORT while the MAP process is waiting for a service indication, the MAP 6414 process returns to the idle state. 6415 If the MAP provider sends a MAP_NOTICE while the MAP process is waiting for a service indication, the MAP 6416 process sends a MAP_CLOSE request to terminate the dialogue and returns to the idle state.
2410
3GPP
2411 Release 4
820
3GPP TS 29.002 V4.17.0 (2006-06)
Pro ces s Failure_R epo rt_H LR
F ig ure 2 4.2 /1 : T h e F ailure R epo rt p ro c es s in th e H L R
24.2_1(1)
S ig n als t o/ fr om th e rig ht are to/ fro m th e G P R S ap p lic atio n p r o c es s
Idle
R ec eiv e_ O pe n_ In d OK
S ec tio n 25 .1 V r, E rror
W a it_ F o r_ S ervic e_ Ind ic atio n
Id le
M AP _ P _ A B O R T _ in d
M A P _ F A IL UR E _ R E P O R T _ in d
M A P_ N O T IC E _ ind
F a ilu re R e p ort Id le W a it for re s po n se Id le M A P_ C L O S E _ r eq
F ailu re R ep ort ne ga tiv e res po n se
F a ilu re R e po rt Ack
S et U E
M A P _ F A IL UR E _ R E P O R T _r sp , M A P _ C L O S E _ req
Idle
6417
6418
Figure 24.2/1: Process Failure_Report_HLR
2412
3GPP
2413 Release 4
821
3GPP TS 29.002 V4.17.0 (2006-06)
6419
24.2.2 Process in the GGSN for Failure Report
When the MAP process receives a Failure Report request from the GPRS application process in the GGSN, it requests a dialogue with the HLR whose identity is contained in the Failure Report request by sending a MAP_OPEN service request, sending failure information using a MAP_FAILURE_REPORT service request and invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the HLR.
6420 Successful Outcome 6421 6422 6423 6424 6425
6426 If the MAP process receives a MAP_FAILURE_REPORT service confirm from the HLR, the MAP process invokes the 6427 macro Check_Confirmation to check the content of the confirm. 6428 If the macro Check_Confirmation takes the OK exit, the MAP process sends a Failure Report ack containing the 6429 information received from the HLR to the GPRS application process in the GGSN and returns to the idle state. 6430 Failure of dialogue opening with the HLR 6431 If the macro Receive_Open_Cnf takes the Vr exit or the Error exit, the MAP process sends a negative response to the 6432 GPRS application process in the GGSN and returns to the idle state. 6433 Error in MAP_FAILURE_REPORT confirm 6434 If the MAP_FAILURE_REPORT service confirm contains a user error or a provider error, or the macro 6435 Check_Confirmation indicates that there is a data error, the MAP process sends a Failure Report negative response to 6436 the GPRS application process in the GGSN and returns to the idle state. 6437 Abort of HLR dialogue 6438 After the dialogue with the HLR has been established, the MAP service provider may abort the dialogue by issuing a 6439 MAP_P_ABORT or a MAP_U_ABORT indication. In this case, the MAP process sends a Failure Report negative 6440 response to the GPRS application process in the GGSN and returns to the idle state. 6441 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 6442 dialogue with the HLR, sends a Failure Report negative response indicating system failure to the GPRS application 6443 process in the GGSN and returns to the idle state.
2414
3GPP
2415 Release 4
822
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess Failure_R epo rt_G G SN
F ig u re 2 4.2 / 2: F a ilu re R e po rt p roc es s in th e G G S N S ig na ls to /f ro m t he rig h t are to /fro m th e G P RS ap p lic atio n p ro c es s Idle
24.2_2(1)
F ailure R e p ort
M A P _ O P E N _ Re q , M A P _ F A IL U R E _ R E P O R T _R e q, M A P _ D E L IM IT E R _ R e q R e c eiv e_ O pe n _c n f OK W A IT _ F O R _ ACK V r, E rro r
F ailu r e R ep or t n ega tive re s po n se
M A P _ F A IL U R E _ R E P O R T_ C n f
M A P _P _ A B O R T _ Ind , M A P _U _ A B O R T _ in d
M A P _ N O T IC E _ In d
Id le
C h ec k _ C o n firm at io n
P ro vid e r E rro r, U s e r E rror, D ata E r ror
M A P _CL O S E Re q
OK F ailu re R ep or t Ack F ailure R e p ort n e gat ive res p o ns e
Idle
6444
6445
Figure 24.2/2: Process Failure_Report_GGSN
2416
3GPP
2417 Release 4
823
3GPP TS 29.002 V4.17.0 (2006-06)
6446
24.3.1 Process in the GGSN for Note Ms Present For Gprs
6447 The MAP process in the GGSN to inform that the subscriber is present for GPRS again is shown in figure 24.3/1. The 6448 MAP process invokes macros not defined in this clause; the definition of these macros can be found as follows: 6449 6450
Receive_Open_Ind Check_Indication
see clause 25.1.1; see clause 25.2.1.
6451 Successful outcome 6452 When the MAP process receives a MAP_OPEN indication with the application context gprsNotify, it checks it by 6453 invoking the macro Receive_Open_Ind. 6454 If the macro takes the OK exit, the MAP process waits for a service indication. 6455 If a MAP_NOTE_MS_PRESENT_FOR_GPRS service indication is received, the GGSN sends a Note Ms Present For 6456 Gprs request to the GPRS application process in the GGSN, and waits for a response. The Note Ms Present For Gprs 6457 request contains the parameter received in the MAP_NOTE_MS_PRESENT_FOR_GPRS service indication. 6458 If the GPRS application process in the GGSN returns a positive response, the MAP process constructs a 6459 MAP_NOTE_MS_PRESENT_FOR_GPRS service response, constructs a MAP_CLOSE service request, sends them to 6460 the HLR and returns to the idle state. 6461 Negative response from GGSN GPRS application process 6462 If the GPRS application process in the GGSN returns a negative response, the MAP process constructs a 6463 MAP_NOTE_MS_PRESENT_FOR_GPRS service response containing the appropriate error, constructs a 6464 MAP_CLOSE service request, sends them to the HLR and returns to the idle state. 6465 Failure of dialogue opening with the HLR 6466 If the macro Receive_Open_Ind takes the Vr exit or the Error exit, the MAP process returns to the idle state. 6467 If the MAP provider sends a MAP_P_ABORT while the MAP process is waiting for a service indication, the MAP 6468 process returns to the idle state. 6469 If the MAP provider sends a MAP_NOTICE while the MAP process is waiting for a service indication, the MAP 6470 process sends a MAP_CLOSE request to terminate the dialogue and returns to the idle state.
2418
3GPP
2419 Release 4
824
3GPP TS 29.002 V4.17.0 (2006-06)
Process N ote_Ms_Present_For_G prs_G GSN
F ig u re 2 4. 3/ 1 : T h e N o t e M s P res en t F o r G prs p ro c es s in th e H L R
24.3_1(1)
S ig na ls to /f ro m th e rig ht are to/ fro m th e G P R S ap p lic atio n p r o c es s
Idle
R e c eiv e_ O pe n _In d
S e c tio n 25 .1
OK W a it_ F o r_ S erv ic e_ Ind ic at io n Id le
V r, E rro r
M A P _P _ A B O R T _ in d
M A P _ NO TE _ M S _ P RE S E N T_ F O R _ G P R S _ in d
M A P_ N O T IC E _ ind
N o te M s P res en t F or G p rs Id le W ait fo r re s po n se
M A P_ C L O S E _ r eq
Id le N o te M s P res en t F o r G p rs ne ga tiv e re s po n s e
N o te Ms P re se n t F o r G p rs A c k
S et U E
M A P _ N O T E _ M S _ P R E S E N T _ F O R _ G P R S _ rs p, M A P _ C L O S E _ req
Idle
6471
6472
Figure 24.3/1: Process Note_Ms_Present_For_Gprs_GGSN
2420
3GPP
2421 Release 4
825
3GPP TS 29.002 V4.17.0 (2006-06)
6473
24.3.2 Process in the HLR for Note Ms Present For Gprs
When the MAP process receives a Note Ms Present For Gprs request from the GPRS application process in the HLR, it requests a dialogue with the GGSN whose identity is contained in the Note Ms Present For Gprs request by sending a MAP_OPEN service request, sending necessary information using a MAP_NOTE_MS_PRESENT_FOR_GPRS service request and invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the GGSN.
6474 Successful Outcome 6475 6476 6477 6478 6479
6480 If the MAP process receives a MAP_NOTE_MS_PRESENT_FOR_GPRS service confirm from the GGSN, the MAP 6481 process invokes the macro Check_Confirmation to check the content of the confirm. 6482 If the macro Check_Confirmation takes the OK exit, the MAP process sends a Note Ms Present For Gprs ack 6483 containing the information received from the GGSN to the GPRS application process in the HLR and returns to the idle 6484 state. 6485 Failure of dialogue opening with the GGSN 6486 If the macro Receive_Open_Cnf takes the Vr exit or the Error exit, the MAP process sends a negative response to the 6487 GPRS application process in the HLR and returns to the idle state. 6488 Error in MAP_NOTE_MS_PRESENT_FOR_GPRS confirm 6489 If the MAP_NOTE_MS_PRESENT_FOR_GPRS service confirm contains a user error or a provider error, or the macro 6490 Check_Confirmation indicates that there is a data error, the MAP process sends a Note Ms Present For Gprs negative 6491 response to the GPRS application process in the HLR and returns to the idle state. 6492 Abort of GGSN dialogue 6493 After the dialogue with the GGSN has been established, the MAP service provider may abort the dialogue by issuing a 6494 MAP_P_ABORT or a MAP_U_ABORT indication. In this case, the MAP process sends a Note Ms Present For Gprs 6495 negative response to the GPRS application process in the HLR and returns to the idle state. 6496 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 6497 dialogue with the GGSN, sends a Failure Report negative response indicating system failure to the GPRS application 6498 process in the HLR and returns to the idle state.
2422
3GPP
2423 Release 4
826
3GPP TS 29.002 V4.17.0 (2006-06)
Process N ote_MS_Present_For_Gprs_H LR
F ig u re 2 4.3 /2 : N o te M s P res en t F or G pr s p ro c e s s in th e H L R
24.3_2(1)
S ign a ls to /fro m th e rig ht are to /fro m th e G P R S ap p lic atio n p roc e s s
Idle
N o te M s P re s en t F or G prs
M A P _ O P E N _ Re q , M A P _ NO TE _ M S _ P RE S E N T_ FO R_ G P R S _ Re q , M A P _ D E L IM IT E R _ R e q R e c eiv e_ O pe n _c n f
V r, E rro r
OK W A IT _ F O R _ ACK N o te M s P res en t F o r G p rs n eg ative res p on s e
M A P _ NO TE _ M S _ P R E S E N T _F O R _ G P R S _ Cn f
M A P _P _ A B O R T _ Ind , M A P _U _ A B O R T _ in d
M A P _ N O T IC E _ In d
Id le
C h ec k _ C o n firm at io n
P ro vid er E rror, U s er E rro r, D a ta E rro r
M A P _ CL O S E Re q
OK
No te M s P res en t F o r G p rs A c k
N o te M s P res en t F or G p rs n e ga tiv e re s po n se
Idle
6499
6500
Figure 24.3/2: Process Note_Ms_Present_For_Gprs_HLR
2424
3GPP
2425 Release 4
827
3GPP TS 29.002 V4.17.0 (2006-06)
6501 6502 6503
24A
CSE control of subscriber data
24A.1Any Time Subscription Interrogation procedure
24A.1.1 General
6504 The message flows for successful retrieval of subscription information related to an any time interrogation from the 6505 CAMEL server are shown in figure 24A.1/1.
6506 6507 6508 6509 6510 6511 6512 6513 6514 6515 6516 6517
gsmSCF +---+ +---+ SCF+----------------------HLR+ +---+ +---+ MAP_ANY TIME SUBSCRIPTION INTERROGATION +------------------------> MAP_ANY TIME SUBSCRIPTION INTERROGATION ack_ <------------------------ Figure 24A.1/1: Message flow for any time subscription interrogation
6518
6519 The following MAP services are used to retrieve requested information: 6520
MAP_ANY_TIME_SUBSCRIPTION_INTERROGATIONsee clause 8.11.x.
6521
24A.1.2 Process in the gsmSCF
6522 Out of the scope of the MAP specification.
6523
24A.1.3 Process in the HLR
6524 The MAP process in the HLR to provide subscription information in response to an interrogation from the CAMEL 6525 server is shown in figure 24A.1/2. The MAP process invokes macros not defined in this clause; the definitions of these 6526 macros can be found as follows: 6527
Receive_Open_Ind
see clause 25.1.1;
6528 Successful outcome 6529 When the MAP process receives a MAP_OPEN indication with the application context anyTimeInformationHandlng, it 6530 checks it by invoking the macro Receive_Open_Ind. 6531 If the macro takes the OK exit, the MAP process waits for a service indication. 6532 6533 6534 6535 6536 6537 6538 6539 6540 6541 6542
If a MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION service indication is received, the MAP process sends an Any Time Subscription Interrogation request to the call handling process in the HLR (described in 3GPP TS 23.078), and waits for a response. The Any Time Subscription Interrogation request contains the parameters received in the MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION service indication. If the call handling process in the HLR returns an Any Time Subscription Interrogation response, the MAP process constructs a MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION service response containing the subscription information contained in the Any Time Subscription Interrogation response, constructs a MAP_CLOSE service request, sends them to the CAMEL server and returns to the idle state. If the MAP_ANY_TIME_ SUBSCRIPTION_INTERROGATION service response cannot be carried in a single TC-Result component, it is carried in one or more TC-Result-NL components (each sent in a TC-CONTINUE), followed by a TC-Result-L component in a TC-END message.
6543 Negative response from HLR call handling process
2426
3GPP
2427 Release 4
828
3GPP TS 29.002 V4.17.0 (2006-06)
6544 If the call handling process in the HLR returns a negative response to obtain subscription information, the MAP process 6545 constructs a MAP_ANY_TIME_SUBSCRIPTION_INTERROGATION service response containing the appropriate 6546 error, constructs a MAP_CLOSE service request, sends them to the CAMEL server and returns to the idle state. 6547 Failure of dialogue opening with the CAMEL server 6548 If the macro Receive_Open_Ind takes the Vr or Error exit, the MAP process returns to the idle state. 6549 If the MAP provider sends a MAP_P_ABORT while the MAP process is waiting for a service indication, the MAP 6550 process returns to the idle state. 6551 If the MAP provider sends a MAP_NOTICE while the MAP process is waiting for a service indication, the MAP 6552 process sends a MAP_CLOSE request to terminate the dialogue and returns to the idle state.
2428
3GPP
2429 Release 4
829
3GPP TS 29.002 V4.17.0 (2006-06)
Process ATSI_HLR
Figure 24A.1/2: Process in the HLR to respond to the request any time subscription interrogation idle
24A.1_2.1(1)
Signals to/from the left are to /from the gsmSCF
idel
Receive_ Open_ind ok Wait_For_ Service_ indication
Section 25.1
Vr Error idle
MAP_P_ ABORT_ind
MAP_ANY_TIME_SUBSCRIPTION_ INTERROGATION_ind Any Time Subscription Interrogation Request Wait_For Call_Handling Response
MAP_NOTICE_ind
idle
To HLR call handling (See 3G TS 23.078)
MAP_CLOSE_req
idle
Any Time Subscription Interrogation Response Set result
From HLR call handling process
Any Time Subscription Interrogation Response Set error
From HLR call handling process
MAP_ANY_TIME_SUBSCRIPTION_ INTERROGATION_rsp
MAP_CLOSE_req
idle
6553
6554
Figure 24A.1/2: Process ATSI_HLR
2430
3GPP
2431 Release 4
830
3GPP TS 29.002 V4.17.0 (2006-06)
6555 6556
24A.2Any Time Modification procedure
24A.2.1 General
6557 The message flows for successful modification of subscriber information related to an any time modification from the 6558 CAMEL server are shown in figure 24A.2/1
6559 6560 6561 6562 6563 6564 6565 6566 6567 6568 6569 6570
gsmSCF +---+ +---+ SCF+--------------HLR +---+ +---+ MAP ANY TIME MODIFICATION +-----------------> MAP ANY TIME _ MODIFICATION ack <----------------- Figure 24A.2/1: Message flow for any time modification
6571
6572 The following MAP services are used to modify subscription information: 6573 MAP_ANY_TIME_MODIFICATIONsee clause 8.11.x.
6574
24A.2.2 Process in the gsmSCF
6575 Out of the scope of the MAP specification.
6576
24A.2.3 Process in the HLR
6577 The MAP process in the HLR to modify subscriber information in response to a modification request from the CAMEL 6578 server is shown in figure 24A.2/2. The MAP process invokes macros not defined in this clause; the definitions of these 6579 macros can be found as follows: 6580 Receive_Open_Ind 6581 Insert_Subs_Data_Stand_Alone_HLR 6582 Successful outcome 6583 When the MAP process receives a MAP_OPEN indication with the application context anyTimeInfromationHandling, 6584 it checks it by invoking the macro Receive_Open_Ind. 6585 If the macro takes the OK exit, the MAP process waits for a service indication. 6586 6587 6588 6589 6590 6591 6592 6593 6594 6595 6596
see clause 25.1.1; see clause 25.7.2;
If a MAP_ANY_TIME_MODIFICATION service indication is received, the MAP process sends an Any Time modification request to the call handling process in the HLR (described in 3GPP TS 23.078), and waits for a response. The Any Time modification request contains the parameters received in the MAP_ ANY_TIME_ MODIFICATION service indication. If the call handling process in the HLR returns an Any Time modification response, the MAP process constructs a MAP_ANY_TIME_ MODIFICATION service response containing the modified subscription information contained in the Any Time modification response, constructs a MAP_CLOSE service request, sends them to the CAMEL server. If the MAP_ANY_TIME_MODIFICATION service response cannot be carried in a single TC-Result component, it is carried in one or more TC-Result-NL components (each sent in a TC-CONTINUE), followed by a TC-Result-L component in a TC-END message. IF the VLR/SGSN is to be updated after the modification, the MAP_INSERT_SUBS_DATA_HLR process shall be initiated and then returns to the idle state.
6597 Negative response from HLR call handling process 6598 If the call handling process in the HLR returns a negative response to modify subscription information, the MAP 6599 process constructs a MAP_ANY_TIME_ MODIFICATION service response containing the appropriate error, 6600 constructs a MAP_CLOSE service request, sends them to the CAMEL server and returns to the idle state.
2432
3GPP
2433 Release 4
831
3GPP TS 29.002 V4.17.0 (2006-06)
6601 Failure of dialogue opening with the CAMEL server 6602 If the macro Receive_Open_Ind takes the Vr or Error exit, the MAP process returns to the idle state. 6603 If the MAP provider sends a MAP_P_ABORT while the MAP process is waiting for a service indication, the MAP 6604 process returns to the idle state. 6605 If the MAP provider sends a MAP_NOTICE while the MAP process is waiting for a service indication, the MAP 6606 process sends a MAP_CLOSE request to terminate the dialogue and returns to the idle state.
2434
3GPP
2435 Release 4
832
3GPP TS 29.002 V4.17.0 (2006-06)
Process ATM_HLR
Figure 24A.2/2: Process in the HLR to respond to the request any time modification idle
24A.2_2.1(1)
Signals to/from the left are to /from the gsmSCF; signals to/from the right are to/from the HLR call handling unless specified otherwise Section 25.1 Vr Error idle
Receive_ Open_ind ok Wait_For_ Service_ indication
idel
MAP_P_ ABORT_ind
MAP_ANY_TIME_MODIFICATION_ind
MAP_NOTICE_ind
idle
Any Time Modification Request Wait_For Call_Handling Response Any Time Modification Response Set result From HLR call handling process
To HLR call handling process
MAP_CLOSE_req
idle
Any Time From HLR call Modification handling process negative response Set error
MAP_ANY_TIME_MODIFICATION_rsp
MAP_CLOSE_req
Insert subscriber data ? yes Ins_Subs_data Stand_Alone_HLR Section 25.7
no
idle
6607
6608
Figure 24A.2/2: Process ATM_HLR
2436
3GPP
2437 Release 4
833
3GPP TS 29.002 V4.17.0 (2006-06)
6609 6610
24A.3Subscriber Data Modification Notification procedure
24A.3.1 General
6611 The Subscriber Data Modification Notification procedure is used to notify a gsmSCF about the modification of 6612 subscriber data. 6613 The stage 2 specification for Subscriber Data Modification Notification is in 3GPP TS 23.078. The interworking 6614 between the MAP signalling procedures and the Subscriber Data Modification Notification procedures for each entity 6615 (HLR, gsmSCF) is shown by the transfer of signals between these procedures. 6616 The following services are used: 6617
HLR (1) ------------------------------------------------->
gsmSCF
(2) <-------------------------------------------------
6622
6618 6619 6620 6621
(1) (2)
MAP-NOTE_SUBSCRIBER_DATA_MODIFIED (HLR to gsmSCF). MAP-NOTE_SUBSCRIBER_DATA_MODIFIED-ACK (gsmSCF to HLR).
Figure 24A.3/1: Interfaces and services for subscriber data modification notification
6623
24A.3.2 Processes in the MAP Entities
6624 The text in this clause is a supplement to the definition in the SDL diagrams; it does not duplicate the information in the 6625 SDL diagrams.
6626 24A.3.2.1
Process in the HLR
6627 The MAP process in the HLR to send modified data to the gsmSCF is shown in figure 24A.3/2. The MAP process 6628 invokes macros not defined in this clause; the definitions of these macros can be found as follows: 6629 6630
Receive_Open_Cnf Check_Confirmation
see clause 25.1.2; see clause 25.2.2.
6631 Successful Outcome 6632 6633 6634 6635 6636 6637
When the MAP process receives a Notify Subscriber Data Change request from the process in the HLR, it requests a dialogue with the gsmSCF whose identity is contained in the Note Subscriber Data Modified request by sending a MAP_OPEN service request, notifies modified subscriber data to the gsmSCF using a MAP_NOTE_SUBSCRIBER_DATA_MODIFIED service request and invokes the macro Receive_Open_Cnf to wait for the response to the dialogue opening request. If the dialogue opening is successful, the MAP process waits for a response from the gsmSCF.
6638 If the HLR notices after receiving a Notify Subscriber Data Change request that the segmentation is needed the HLR 6639 does not set the All Information Sent indicator. Otherwise the indicator is set and the process returns to the Wait for 6640 SCF response state.
2438
3GPP
2439 Release 4
834
3GPP TS 29.002 V4.17.0 (2006-06)
6641 If the MAP process receives a MAP_NOTE_SUBSCRIBER_DATA_MODIFIED service confirm from the gsmSCF, 6642 the MAP process invokes the macro Check_Confirmation to check the content of the confirm. 6643 6644 6645 6646 6647 6648
If the macro Check_Confirmation takes the OK exit, the MAP process checks if the All Information Sent indicator is set. If it is set the MAP process sends a Notify Subscriber Data Modified ack to the process in the HLR and returns to the idle state. If the All Information Sent indicator is not set the MAP process checks if the further segmentation is needed. If segmentation is needed the HLR does not set the indicator and sends MAP_NOTE_SUBSCRIBER_DATA_MODIFIED service request to the gsmSCF. Otherwise the indicator is set and the MAP_NOTE_SUBSCRIBER_DATA_MODIFIED service request is sent to the gsmSCF.
6649 Dialogue opening failure 6650 If the macro Receive_Open_Cnf indicates that the dialogue with the gsmSCF could not be opened or that the dialogue 6651 can be opened only at an earlier version, the MAP process sends a Notify Subscriber Data Modified negative response 6652 indicating system failure to the process in the HLR and returns to the idle state. 6653 Error in MAP_NOTE_SUBSCRIBER_DATA_MODIFIED confirm 6654 If the MAP_NOTE_SUBSCRIBER_DATA_MODIFIED service confirm contains a user error or a provider error, the 6655 MAP process sends a Notify Subscriber Data Change negative response to the process in the HLR and returns to the 6656 idle state. 6657 Abort of gsmSCF dialogue 6658 After the dialogue with the gsmSCF has been established, the MAP service provider may abort the dialogue by issuing 6659 a MAP_P_ABORT indication, or the gsmSCF may send a MAP_CLOSE indication. In either of these cases, the MAP 6660 process sends a Notify Subscriber Data Change negative response to the process in the HLR and returns to the idle state. 6661 If the MAP provider indicates a protocol problem by sending a MAP_NOTICE indication, the MAP process closes the 6662 dialogue with the gsmSCF, sends a Notify Subscriber Data Change negative response indicating system failure to the 6663 process in the HLR and returns to the idle state.
2440
3GPP
2441 Release 4
835
3GPP TS 29.002 V4.17.0 (2006-06)
Process NSDC_HLR
Process in the HLR to notify the gsmSCF that subscriber data have been changed. idle
Signals to/from the left are to/from the Procedure CAMEL_NSDC_HLR (See 3G TS 23.078) Signals to/from the right are to/from the gsmSCF
1(1)
Notify Subscriber Data Change
Yes
Segmentation needed No Set 'All Information Sent' indicator
Yes
Segmentation needed No Set 'All Information Sent' indicator
MAP_NOTE_SUBSCRIBER_ DATA_MODIFIED_req MAP_DELIMITER_req
MAP_OPEN_req MAP_NOTE_SUBSCRIBER_ DATA_MODIFIED_req MAP_DELIMITER_req Receive_ Open_Cnf Ok Wait for SCF response MAP_U_ABORT_ind MAP_P_ABORT_ind MAP_CLOSE_ind
Figure 25.1/2 Vr, Error
MAP_NOTE_SUBSCRIBER_ DATA_MODIFIED_cnf
MAP_NOTICE_ind
Check_ confirmation OK 'All Information Sent' indicator is set Yes
Figure 25.2/2 Provider error User error Data error No
MAP_ CLOSE_req
Notify Subscriber Data Change reponse idle 1
Notify Subscriber Data Change negative reponse idle
6664
6665
Figure 24A.3/2 Process Subscriber_Data_Modification_Notification_HLR (sheet 1 of 1)
2442
3GPP
2443 Release 4
836
3GPP TS 29.002 V4.17.0 (2006-06)
6666 24A.3.2.2
Process in the gsmSCF
6667 The MAP process in the gsmSCF to handle a notification to the gsmSCF of change of subscriber data resume is shown 6668 in figure 24A.3/3. The MAP process invokes a macro not defined in this clause; the definition of this macro can be 6669 found as follows: 6670
Receive_Open_Ind
see clause 25.1.1;
6671 Successful outcome 6672 When the MAP process receives a MAP_OPEN indication with the application context noteSubscriberDataModified, it 6673 checks it by invoking the macro Receive_Open_Ind. 6674 If the macro takes the OK exit, the MAP process waits for a service indication. 6675 6676 6677 6678 6679 6680 6681
If a MAP_NOTE_SUBSCRIBER_DATA_MODIFIED service indication is received, the MAP process checks if the All Information Sent indicator is set and if so it sends a Subscriber Data Changed request including all the stored data to the process in the gsmSCF, and waits for a response. The Subscriber Data Changed request contains the parameters received in the MAP_NOTE_SUBSCRIBER_DATA_MODIFIED service indication. If the All Information Sent indicator is not set, the received data is stored and the MAP process constructs an empty MAP_NOTE_SUBSCRIBER_DATA_MODIFIED service response, sends it to the HLR and returns to the Wait for response state.
6682 If the process in the gsmSCF returns a negative response, the MAP process constructs a 6683 MAP_NOTE_SUBSCRIBER_DATA_MODIFIED service response, constructs a MAP_CLOSE service request, sends 6684 them to the HLR and returns to the idle state. 6685 Failure of dialogue opening with the HLR 6686 If the macro Receive_Open_Ind takes the Vr exit or the Error exit, the MAP process returns to the idle state. 6687 If the MAP provider sends a MAP_P_ABORT while the MAP process is waiting for a service indication, the MAP 6688 process returns to the idle state. 6689 If the MAP provider sends a MAP_NOTICE while the MAP process is waiting for a service indication, the MAP 6690 process sends a MAP_CLOSE request to terminate the dialogue and returns to the idle.
2444
3GPP
2445 Release 4
837
3GPP TS 29.002 V4.17.0 (2006-06)
Process NSDC_gsmSCF
Process in the gsmSCF to receive notification of change of subscriber data.. idle
Signals to/from the left are to/from the process in the gsmSCF Signals to/from the right are to/from the HLR
1(1)
Receive_ Open_Ind Ok Wait for service indication
Figure 25.1/1 Vr, Error idle
MAP_P_ABORT_ind
MAP_NOTE_SUBSCRIBER_ DATA_MODIFIED_ind 'All Information Sent' indicator is set Yes Assemble reseived data Store reseived data
MAP_NOTICE_ind
idle
No
MAP_ CLOSE_req
idle
Subscriber Data Changed Wait_For_ Service_ Indication negative response
MAP_NOTE_SUBSCRIBER_ DATA_MODIFIED_rsp MAP_DELIMITER_req
Wait for response
positive response
set user error MAP_NOTE_SUBSCRIBER_ DATA_MODIFIED_rsp MAP_CLOSE_req idle
6691
6692
Figure 24A.3/3: Process Subscriber_Data_Modification_Notification_gsmSCF (sheet 1 of 1)
6693 6694
24B
Location Service process description
24B.1Routeing information retrieval procedure for LCS
2446
3GPP
2447 Release 4
838
3GPP TS 29.002 V4.17.0 (2006-06)
6695
24B.1.1 General
6696 The message flows for successful retrieval of routeing information related to location services are shown in figure 6697 24B.1/1.
6698 6699 6700 6701 6702 6703 6704 6705 6706 6707 6708 6709 6711
+-----+ +-----+ GMLC +-------------------- HLR +-----+ +-----+ MAP SEND ROUTEING INFO -------------------------> FOR LCS MAP SEND ROUTEING INFO <------------------------- FOR LCS ACK Figure 24B.1/1: Message flow for retrieval of routeing information for LCS
6712
6713 The following MAP services are used to retrieve routeing information: 6714
MAP_SEND_ROUTING_INFO_FOR_LCS see clause 13A.1.
2448
3GPP
2449 Release 4
839
3GPP TS 29.002 V4.17.0 (2006-06)
6715
24B.1.2 Process in the GMLC
Process SRI_FOR_LCS_GMLC
Pr oce s s in t he G M L C f or ret rie va l o f ro u te in g in for ma t io n
SRI_LCS_GMLC(1)
S ign als to / from th e le ft a re to /fro m t he a pp lic at io n p roce ss in the G ML C; sign als t o/ from th e right a re to /fr om th e H L R Id le
S en d Ro u tin g In fo fo r L CS
MA P _ O P E N_ req M A P _S EN D _R O UT ING _I NFO _FO R _ LC S_ re q M AP _ DE L IM ITE R_ re q R ece ive _ O pe n _C nf OK W ait_ Fo r_ Re spo ns e
S ect io n 25 .1 .2
V r, E rro r I dle
MA P _ SE N D _ RO UTI NG _ INF O _ FO R _L CS _ c nf
MA P _ N O TIC E _in d
M A P _C LO S E_ in d, M A P _U _A B O RT _in d, M A P _P _A B O R T_ in d
Ch eck _ Co nfirm a tion
S ec t io n 2 5 .2 P ro v id er E rro r, Use r E rro r, Da ta E rror
MA P _ C L O S E _ in d
OK
S en d Ro ut in g In fo fo r L CS ack
S e n d Rou t in g I nf o for LC S n e ga tive re spo n se
S et n eg at iv e re sp on se: S yst em Failure S en d Ro u tin g In fo fo r L CS ne g ative res p o nse
Id le
Idle
Id le
6716
6717 6718
Figure 24B.1/2: Process SRI_FOR_LCS_GMLC
2450
3GPP
2451 Release 4
840
3GPP TS 29.002 V4.17.0 (2006-06)
6719 24B.1.3 Process in the HLR
Process SRI_FOR_LCS_HLR
Pro ce ss in t he H LR to re s po nd to a req ue st f o r th e rou te in g in fo rm a tio n
SRI_L CS_HLR(1)
S ign als t o/ from th e le ft ar e to / from th e G M LC ; s ig nals t o/ from t he rig h t a re t o /fro m th e ap p licat io n in th e H L R a p plicat ion p ro ce ss Id le
R ece ive _ O p en _I nd OK W ait_ F o r_ R ep ort
S ect io n 25 .1 .1
V r, E rror M AP _ P _ A B O RT _re q MA P _P _ A BO RT_ in d I dle
M AP _ SE N D _ RO UTI NG _ INF O _F O R_ LC S _ind
MA P _ N O TIC E _ind
S en d Ro u tin g In fo fo r L CS
To HL R ap plica tion p ro ce ss
MA P _ CL O S E _in d
W ait_ Fo r_ S RI _fo r_L C S _ resp on se S en d Ro u tin g In fo fo r LC S ack S end R ou ting Inf o for LC S n eg at ive re s po n se
Idle
Se t resu lt
Se t erro r
MA P _ SE N D _ RO UTI NG _ IN F O _ FO R _L CS _ rsp M AP _ CL O S E _re q
Id le
6720
6721 6722
Figure 24B.1/3: Process SRI_FOR_LCS_HLR
2452
3GPP
2453 Release 4
841
3GPP TS 29.002 V4.17.0 (2006-06)
6723 6724
24B.2Provide Subscriber Location procedure
24B.2.1 General
6725 The message flows for successful retrieval of the location information of a target MS related to location services are 6726 shown in figure 24B.1/1.
6727 6728 6729 6730 6731 6732 6733 6734 6735 6736 6737 6738 6739
+-----+ +-----+ GMLC +--------------------MSC/ + SGSN +-----+ +-----+ MAP PROVIDE SUBSCRIBER -------------------------> LOCATION MAP PROVIDE SUBSCRIBER <------------------------- LOCATION ACK Figure 24B.2/1: Message flow for request of the location information
6741
6742 The following MAP services are used to retrieve location information: 6743
MAP_PROVIDE_SUBSCRIBER_LOCATION see clause 13A.2.
2454
3GPP
2455 Release 4
842
3GPP TS 29.002 V4.17.0 (2006-06)
6744
24B.2.2 Process in the GMLC
Process PSL_GMLC
Pro ces s in th e G M LC t o re q ue st the loca tion o f a t arg e t M S
PSL_GMLC(1)
S ign als to / from th e le ft a re to /fro m t he a pp lic at io n p roce ss in the G ML C; sign als t o/ from th e right a re to /fr om th e M S C /SG S N Id le
P rov id e S ub scr ib er Lo c a tio n
MA P _ O P E N_ req MA P _ P R O V ID E _S U BS C RI BE R _L O C A TIO N _re q M AP _ DE L IM ITE R_ re q
R ece ive _ O pe n _C nf
S ect io n 25 .1 .2
OK W ait_ Fo r_ Re spo ns e I dle
V r, E r ro r
M AP _ PR O V I DE _ S UB S CR IB E R_ LO CA TIO N _ cnf
MA P _ N O TIC E _in d
M A P _C L O S E_ in d , M A P _U _A B O R T _ in d, M A P _P _A B O R T _ in d
Ch eck _ Co nfirm a tion
S ec t io n 2 5 .2 P ro v id er E rro r, Use r E rro r, Da ta E rror MA P _ C L O S E _ in d
OK
P rovid e S ub scr ib er L oca tio n ack
P r ovid e S u bs cribe r L o cat io n ne ga tive re spo ns e Idle
S et n eg at iv e re sp on se: S yst em Failure P rov id e S ub scr ib er L oc a tion ne g at iv e resp on se Id le
Id le
6745
6746 6747
Figure 24B.2/2: Process PSL_GMLC
2456
3GPP
2457 Release 4
843
3GPP TS 29.002 V4.17.0 (2006-06)
6748
24B.2.3 Process in the MSC
Process PSL _MSC
Pro ces s in th e M SC t o respo n se the loca tion o f a t arg e t M S
PSL_MSC(1)
S ign als t o/ from th e le ft ar e to / from th e G M LC ; s ig nals t o/ from t he rig h t a re t o /fro m th e ap p licat io n in th e M S C ap p licat io n pro cess Id le
R ece ive _ O p en _I nd OK W ait_ F o r_ R ep ort
S ect io n 25 .1 .1
V r, E rror M AP _ P _ A B O RT _re q MA P _P _ A BO RT_ in d I dle
M AP _ PR O V I DE S UB S CR IB E R_ LO C A TIO N _ in d
MA P _ N O TIC E _ind
P rovid e S ub scr ib er Lo c a tio n W ait_ Fo r_ PS L _ re spo n se
To M S C a p plicat io n p ro c e ss
MA P _ CL O S E _re q
Pr ovid e S ub scr ib er L oc a tio n resp on se Se t resu lt
P rovid e S u bscriber Lo c at io n ne ga tive re s po n se
Se t erro r
Id le
M AP _ PR O V I DE _S U B S CR IB E R_ LO C AT IO N_r sp M AP _ CL O S E _re q
Id le
6749
6750
Figure 24B.2/3: Process PSL_MSC
6751
24B.2.4 Process in the SGSN
2458
3GPP
2459 Release 4
844
3GPP TS 29.002 V4.17.0 (2006-06)
Process PSL _SGSN
Pr oce s s in t he S G S N to re spo nse the loca tion o f a t arg e t M S
PSL_SGSN(1)
S ign als t o/ from th e le ft ar e to / from th e G M LC ; s ig nals t o/ from t he rig h t a re t o /fro m th e ap p licat io n in th e S G S N a pp licat io n pro ce ss Id le
R ece ive _ O p en _I nd OK W ait_ F o r_ R ep ort
S ect io n 25 .1 .1
V r, E rror M AP _ P _ A B O RT _re q MA P _P _ A BO RT_ in d I dle
M AP _ PR O V I DE _ S UB S CR IB E R_ LO C A TIO N _ in d
MA P _ N O TIC E _ind
P rovid e S ub scr ib er Lo c a tio n W ait_ Fo r_ PS L _ re spo n se
To S G S N a p plica tion p roce ss
MA P _ CL O S E _re q
P rovid e S ub scr ib er Lo c a tio n resp on se Se t resu lt
P rovid e S u bscriber Lo c at io n ne ga tive re s po n se
Se t erro r
Id le
M AP _ PR O V I DE _S U B S CR IB E R_ LO C AT IO N_r sp M AP _ CL O S E _re q
Id le
6752
6753
Figure 24B.2/4: Process PSL_SGSN
2460
3GPP
2461 Release 4
845
3GPP TS 29.002 V4.17.0 (2006-06)
6754 6755
24B.3Subscriber Location Report procedure
24B.3.1 General
6756 The message flows for successful report of the location information of a target MS related to location services are 6757 shown in figure 24B.3/1.
6758 6759 6760 6761 6762 6763 6764 6765 6766 6767 6768 6769 6770
+-----+ +-----+ GMLC +--------------------MSC/ + SGSN +-----+ +-----+ MAP SUBSCRIBER <------------------------- LOCATION REPORT MAP SUBSCRIBER -------------------------> LOCATION REPORT ACK Figure 24B.3/1: Message flow for report of the location information
6772
6773 The following MAP services are used to report location information: 6774
MAP_SUBSCRIBER_LOCATION_REPORT see clause 13A.3.
2462
3GPP
2463 Release 4
846
3GPP TS 29.002 V4.17.0 (2006-06)
6775
24B.3.2 Process in the GMLC
Process SLR_GMLC
Pro ces s in th e G M LC to re spo n se the loca tion o f a t arg e t M S
SL R_GMLC(1)
S ign als t o/ from th e le ft ar e t o/ fro m th e M SC o r S G S N ; s ig nals t o/ from t he rig h t a re t o /fro m th e ap p licat io n in th e G ML C ap p licatio n pro cess Id le
R ece ive _ O p en _I nd OK W ait_ F o r_ R ep ort
S ect io n 25 .1 .1
V r, E rror M AP _ P _ A B O RT _re q MA P _P _ A BO RT_ in d I dle
M AP _ SU B S CR IB E R_ LO C A TIO N_ RE P O RT _ind
MA P _ N O TIC E _ind
S ub scr ib er Lo c a tio n R epo rt W ait_ Fo r_ S LR _re spo nse
To G M LC a pp licat io n p ro ce ss
MA P _ CL O S E _re q
S ub scr ib er L oc a tio n R epo rt resp on se Se t resu lt
S ub sc rib er L o cat io n Rep o rt n eg at ive re s po n se
Se t erro r
Id le
M AP _ SU B S CR IB E R_ LO C A TIO N_ RE P O R T_rsp M AP _ CL O S E _re q
Id le
6776
6777 6778
Figure 24B.3/2 Process SLR_GMLC
2464
3GPP
2465 Release 4
847
3GPP TS 29.002 V4.17.0 (2006-06)
6779
24B.3.3 Process in the MSC
Process SLR_MSC
Pro ce ss in t he M SC t o req ue st the loca tion o f a t arg e t M S
SLR_MSC(1)
S ign als to / from th e le ft a re to /fro m t he a pp lic at io n p roce ss in the M S C; sign als t o/ from th e right a re to /fr om th e G ML C Id le
S ub scr ib er Lo c a tio n R epo rt
MA P _ O P E N_ req M A P_ S U B S CR IB E R_ LO CA TI O N_ RE P O R T_ re q M AP _ DE L IM ITE R_ re q
R ece ive _ O pe n _C nf
S ect io n 25 .1 .2
OK W ait_ Fo r_ Re spo ns e I dle
V r, E r ro r
M AP _ SU B S CR IB E R_ L O CA TIO N_ RE P O R T_cn f
MA P _ N O TIC E _in d
M A P _C L O S E_ in d , M A P _U _A B O R T _ in d, M A P _P _A B O R T _ in d
Ch eck _ Co nfirm a tion
S ec t io n 2 5 .2 MA P _ C L O S E _ in d P ro v id er E rro r, Use r E rro r, Da ta E rror S u bs cribe r L oca tion R ep o rt n e ga tive re spo n se S et n eg at iv e re sp on se: S yst em Failure S ub scr ib er Lo c at io n Re po rt ne g ative res p o nse
OK
S ub scr ib er Lo ca tio n R epo rt ack
Id le
Idle
Id le
6780
6781
Figure 24B.3/3 Process SLR_MSC
2466
3GPP
2467 Release 4
848
3GPP TS 29.002 V4.17.0 (2006-06)
6782
24B.3.4 Process in the SGSN
Process SLR_SGSN
Pro ces s in th e S G S N to re que s t the loca tion o f a t arg e t M S
SLR_SGSN(1)
S ign als to / from th e le ft a re to /fro m t he a pp lic at io n p roce ss in th e S G S N; sign als t o/ from th e right a re to /fr om th e G ML C Id le
S ub scr ib er Lo c a tio n R epo rt
MA P _ O P E N_ req M A P_ S U B S CR IB E R_ LO CA TI O N_ RE P O R T_ re q M AP _ DE L IM ITE R_ re q
R ece ive _ O pe n _C nf
S ect io n 25 .1 .2
OK W ait_ Fo r_ Re spo ns e I dle
V r, E r ro r
M AP _ SU B S CR IB E R_ L O CA TIO N_ RE P O R T_cn f
MA P _ N O TIC E _in d
M A P _C L O S E_ in d , M A P _U _A B O R T _ in d, M A P _P _A B O R T _ in d
C heck Co nfirm a tion
S ec t io n 2 5 .2 MA P _ C L O S E _ in d P ro v id er E rro r, Use r E rro r, Da ta E rror S u bs cribe r L o ca t io n R ep o rt n eg at ive re spo ns e Idle S et n eg at iv e re sp on se: S yst em Failure S ub scr ib er Lo c a tio n Re po rt ne ga tive resp on se Id le
OK
S ub scr ib er Lo ca tio n R epo rt ack
Id le
6783
6784
Figure 24B.3/4 Process SLR_SGSN
2468
3GPP
2469 Release 4
849
3GPP TS 29.002 V4.17.0 (2006-06)
6785 6786 6787
25
General macro description
25.1 MAP open macros
25.1.1 Macro Receive_Open_Ind
6788 This macro is used by a MAP service-user procedure when a peer entity requests opening of a dialogue. 6789 If the application context received in the MAP-OPEN indication primitive indicates a context name of the MAP version 6790 one context set, the macro takes the Vr exit.. 6791 If an application-context different from version 1 is received, the presence of MAP_OPEN information is checked. If no 6792 MAP_OPEN information has been received, the MAP_OPEN response with: 6793 6794
Result set to Dialogue Accepted; and Application Context Name set to the received value,
6795 is returned. 6796 If the received version (Vr) is the one described in this version of MAP, the macro takes the OK exit, otherwise it takes 6797 the Vr exit.. 6798 If MAP_OPEN information is received, the macro "CHECK_REFERENCE" is called in order to check whether the 6799 received values for Destination Reference and Originating Reference correspond with the requirements of the received 6800 application-context-name. If the outcome of this check is an error, the MAP_OPEN responds with: 6801 6802 6803
Result set to Dialogue Refused; Refuse Reason set to Invalid Destination Reference or Invalid Originating Reference; Application Context Name set to the highest version supported,
6804 is returned and the macro takes the error exit. 6805 If the data values received for Destination Reference and Originating Reference are accepted for the associated 6806 application-context-name it is checked whether the Destination Reference is known if this check is required by the 6807 process that calls the macro. 6808 If the Destination Reference (e.g. a subscribers IMSI) is unknown, the MAP_OPEN response with 6809 6810 6811
Result set to Dialogue Refused; Refuse Reason set to Invalid Destination Reference; Application Context Name set to the highest version supported,
6812 is returned and the macro takes the error exit. 6813 Else, if the Destination Reference is accepted or if no check is required, the MAP_OPEN response with 6814 6815
Result set to Dialogue Accepted; and Application Context Name set to the received value,
6816 is returned and 6817 If the received version (Vr) is the one described in this version of MAP, the macro takes the OK exit, otherwise it takes 6818 the Vr exit.
6819
25.1.2 Macro Receive_Open_Cnf
6820 This macro is used by a user procedure after it requested opening of a dialogue towards a peer entity.
2470
3GPP
2471 Release 4
850
3GPP TS 29.002 V4.17.0 (2006-06)
6821 On receipt of a MAP_OPEN Confirmation with a "Result" parameter indicating "Dialogue Accepted", the macro takes 6822 the OK exit. 6823 If the "Result" parameter indicates "Dialogue Refused", the "Refuse-reason" parameter is examined. If the "Refuse6824 reason" parameter indicates "Potential Version Incompatibility", the macro terminates in a way that causes restart of the 6825 dialogue by using the version 1 protocol. 6826 If the "Refuse-reason" parameter indicates "Application Context Not Supported" and if the received Application 6827 Context Name indicates "Version Vr" (Vr < Vn), the macro terminates in a way that causes restart of the dialogue by 6828 using the version Vr protocol. Otherwise, the macro takes the Error exit. 6829 If the "Refuse-reason" parameter indicates neither "Potential Version Incompatibility" nor "Application Context Not 6830 Supported", the macro takes the Error exit. 6831 If a MAP_U_ABORT, a MAP_P_ABORT or a MAP_NOTICE Indication is received, the macro takes the Error exit.
2472
3GPP
2473 Release 4
851
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition Receive_Open_Ind
Figure 25.1/1: Macro Receive_Open_Ind
25.1_1(1)
MAPOPEN _Ind
'AC= MAP_v1' no MAPOPEN_INFO present yes 'Reference := Destination_ Reference'
yes
no Vr
CHECK_ REFERENCE Error 'Refuse-reason := Invalid_destination _reference' OK 'Reference := Originating_ Reference'
Figure 25.1/3
1 CHECK_ REFERENCE Error 'Refuse-reason := Invalid_originating _reference' OK Dest_Ref _check yes no 1 no Figure 25.1/3
Dest_Ref _known yes
'Result := Dialogue_ refused'
'Refuse-reason := Invalid_destination _reference'
'AC_name := Received_AC _name'
'AC_name := Highest_version _supported'
'Result := Dialogue_ Accepted' Received version (Vr) = the one described in this version of MAP ? no
MAPOPEN _Rsp
MAPOPEN _Rsp
yes Error 2 OK Vr
6832
6833
Figure 25.1/1: Macro Receive_Open_Ind
2474
3GPP
2475 Release 4
852
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition Receive_Open_Cnf
Figure 25.1/ 2: Macro to receive a MA P_OPE N _Cnf
25.1_2(1)
W A IT_FOR_ OP EN_Cnf
MA P_ NOTICE_ Ind
M AP _U_A BORT_Ind, M AP _P_AB ORT_Ind
MA P_O PE N_ Cnf
MAP_CLOS E_ Req
Dialogue_Refus ed Res ult
Dialogue_ A ccepted ELSE Re fus e_ Reason A C_Not_Supported Potential_ Version_ Incompatibility
Vr = V1
Vr = received AC version
Vr < Vn Error E rror O.K . Error yes no
Vr
Vr
E rror
6834
6835
Figure 25.1/2: Macro Receive_Open_Cnf
2476
3GPP
2477 Release 4
853
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition CHECK_REFERENCE
Figure 25.1/ 3: Check of Dest ination Reference and Originating Reference received in a MA P-OPE N indication primit ive
25.1_3(1)
Ref erence_ present
no
yes
P resence_ required_for _AC
no
yes
P resence_ allowed_f or _A C yes
no
correct_ data_type
no
yes
OK
Error
OK
6836
6837
Figure 25.1/3: Macro CHECK_REFERENCE
2478
3GPP
2479 Release 4
854
3GPP TS 29.002 V4.17.0 (2006-06)
6838 6839 6840
25.2 Macros to check the content of indication and confirmation primitives
25.2.1 Macro Check_Indication
6841 If a parameter required by the application is missing from the indication, the macro takes the error exit, with a user error 6842 of "Data Missing". 6843 If a parameter not expected by the application is present in the indication, or an expected parameter has a value not in 6844 the set of values permitted by the application, the macro takes the error exit, with a user error of "Unexpected Data 6845 Value". 6846 Otherwise the macro takes the "OK" exit. 6847 The macro is shown in figure 25.2/1.
6848
25.2.2 Macro Check_Confirmation
6849 If the confirmation contains a provider error the macro issues a MAP CLOSE request and takes the provider error exit. 6850 Otherwise, if the confirmation contains a user error the macro takes the user error exit. 6851 Otherwise, if a parameter required by the application is missing from the confirmation, or a parameter not expected by 6852 the application is present in the confirmation, or an expected parameter has a value not in the set of values permitted by 6853 the application, the macro takes the data error exit. 6854 Otherwise the macro takes the "OK" exit. 6855 The macro is shown in figure 25.2/2.
2480
3GPP
2481 Release 4
855
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition Check_Indication
Figure 25.2/1: Mac ro to check the parameters of an in dic ation primitive
25.2_1(1)
Data Missing No
Yes
Unexpect ed Data No
Yes
Unexpect ed V alue No
Yes
S et User E rror Data Missing
OK
Set Use r E rror Unexpected Data Value
Error
6856
6857
Figure 25.2/1: Macro Check_Indication
2482
3GPP
2483 Release 4
856
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition Check_Confirmation
Figure 25.2/2: Macro to chec k the parameters of a c onf irmation primitive
25.2_2(1)
Provider error no
yes
MAP_CLOS E_ Req yes
Us er error
no
Provider error
Data mis sing
yes
no
User error
Unexpected dat a
yes
no
Unexpected value
yes
no
OK
Dat a error
6858
6859
Figure 25.2/2: Macro Check_Confirmation
2484
3GPP
2485 Release 4
857
3GPP TS 29.002 V4.17.0 (2006-06)
6860 6861
25.3 The page and search macros
25.3.1 Macro PAGE_MSC
6862 This macro (see figure 25.3/1) is called if a mobile terminating call set-up, an unstructured SS notification, a network6863 initiated unstructured SS request or a mobile terminating short message is to be delivered to the MS and the current 6864 location area identity of the MS is known in the VLR. 6865 When the MSC receives a MAP_PAGE indication, parameter checks are performed first (macro Check_Indication, see 6866 clause 25.2). If parameter errors are detected, the MSC returns a MAP_PAGE response containing the appropriate error 6867 cause and the macro terminates with unsuccessful outcome. 6868 Thereafter, several checks on the indication content are performed. The macro terminates by returning the MAP_PAGE 6869 response with error: 6870 6871 6872
Unknown Location Area if the LAI is not known in the MSC; System Failure if the call has been released by the calling subscriber or the SMS or SS transaction for this subscriber has been released by the originating entity in the meantime.
6873 Next, the MSC checks if an MM-connection over the radio link already exists for the given IMSI. If so, 6874 6875 6876 6877 6878 6879 6880 6881 6882 6883 6884 6885 6886 6887 6888 6889 6890 6891 6892 6893 6894 6895 6896 6897 6898 6899 6900 6901 6902 6903
in the case of mobile terminating call set-up the MSC determines whether the busy condition can be established (see 3GPP TS 22.001 [2] for a definition of busy states). If the MSC determines that the MS is busy, it returns a MAP_PAGE response with error Busy Subscriber, qualified by either More Calls Allowed or No More Calls Allowed. The macro then terminates with unsuccessful outcome. if the service requested is short message service or an unstructured SS notification or network-initiated unstructured SS request, or if the service is mobile terminating call set-up, but the existing connection is for signalling purposes only (i.e. a service different from call set-up), the access connection status is set according to the characteristics of the existing connection (i.e. RR-connection established, ciphering mode on/off, MMconnection existing and authenticated or not), and the macro terminates with successful outcome.
If no MM-connection for the given IMSI exists, paging is initiated at the radio interface within all cells of the location area indicated by the VLR. If the VLR provided the TMSI, the MSC uses it to identify the MS at the radio interface; otherwise the MSC uses the IMSI. The IMSI will also be used to determine the page group (see 3GPP TS 24.008 [35]). There are several possible outcomes of paging: the MS responds to paging, causing the access connection status to be set accordingly (i.e. no RR-connection, in which case other values are not significant), and the macro terminates with successful outcome; 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 before the macro terminates with unsuccessful outcome. This will give priority to the mobile originating request. Alternatively, as an implementation option, the MSC may treat this as a response to paging, which will give priority to the mobile terminating request. there is no response from the MS. The MSC sends a MAP_PAGE response primitive with user error Absent Subscriber before the macro terminates with unsuccessful outcome; the call handling connection or MAP transaction on which the call, SMS or unstructured SS transaction is waiting for delivery, is released before a response is received from the MS (indicated in the SDL by the input signal I-REL). The MAP transaction with the VLR will be released in this case by a MAP_U_ABORT request, and the unsuccessful macro termination will indicate transaction termination. the MAP transaction with the VLR may be released by receiving a MAP_U_ABORT or MAP_P_ABORT indication. The call handling connection or MAP transaction on which the call, SMS or unstructured SS transaction is waiting for delivery, is released (indicated in the SDL by the output signal I-REL), and the unsuccessful macro termination will indicate transaction termination.
2486
3GPP
2487 Release 4
858
3GPP TS 29.002 V4.17.0 (2006-06)
6904
25.3.2 Macro Search_For_MS_MSC
6905 This macro (see figure 25.3/2) is called if a mobile terminating call set-up, an unstructured SS notification, a network6906 initiated unstructured SS request or a mobile terminating short message is to be delivered to the MS and the current 6907 location area identity of the MS is not known in VLR. 6908 When the MSC receives a MAP_SEARCH_FOR_MS Indication, parameter checks are performed first (macro 6909 Check_indication, see clause 25.2). If parameter errors are detected, the MSC returns a MAP_SEARCH_FOR_MS 6910 response containing the appropriate error cause and the macro terminates with unsuccessful outcome. 6911 Thereafter, the MSC checks whether the call or the SMS or SS transaction still exists in the MSC. If the call or the SMS 6912 or SS transaction has been released, the MSC returns a MAP_SEARCH_FOR_MS response with error System Failure 6913 and the macro terminates with unsuccessful outcome. 6914 Next, the MSC checks if an MM-connection over the radio link already exists for the given IMSI. If so, 6915 6916 6917 6918 6919 6920 6921 6922 6923 6924 6925
in the case of mobile terminating call set-up the MSC determines whether the busy condition can be established (see 3GPP TS 22.001 [2] for a definition of busy states). If the MSC determines that the MS is busy, it returns a MAP_SEARCH_FOR_MS response with error Busy Subscriber, qualified by either More Calls Allowed or No More Calls Allowed. The macro then terminates with unsuccessful outcome. if the service requested is short message service or an unstructured SS notification or network-initiated unstructured SS request, or if the service is mobile terminating call set-up, but the existing connection is for signalling purposes only (i.e. a service different from call set-up), a MAP_SEARCH_FOR_MS response containing the IMSI and current location area identification of the called MS is returned to the VLR. The access connection status is set according to the characteristics of the existing connection (i.e. RR-connection established, ciphering mode on/off, MM-connection existing and authenticated or not), and the macro terminates with successful outcome.
6926 If no MM-connection for the given IMSI exists, paging is initiated at the radio interface within all cells of all location 6927 areas of the VLR, using the IMSI to identify the subscriber and the page group (see 3GPP TS 24.008 [35]). There are 6928 several possible outcomes of paging: 6929 6930 6931 6932 6933 6934 6935 6936 6937 6938 6939 6940 6941 6942 6943 6944 6945 6946 6947
the MS responds to paging, causing a MAP_SEARCH_FOR_MS response containing the IMSI and current location area identification of the called MS to be returned to the VLR. The access connection status will be set accordingly (i.e. no RR-connection, in which case other values are not significant), and the macro terminates with successful outcome. 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 primitive with user error "Busy Subscriber" before the macro terminates with unsuccessful outcome. This will give priority to the mobile originating request. Alternatively, as an implementation option, the MSC may treat this as a response to paging, which will give priority to the mobile terminating request. there is no response from the MS. The MSC sends a MAP_SEARCH_FOR_MS response primitive with user error "Absent Subscriber" before the macro terminates with unsuccessful outcome. the call handling connection or MAP transaction on which the call, SMS or unstructured SS transaction is waiting for delivery, is released before a response is received from the MS (indicated in the SDL by the input signal I-REL). The MAP transaction with the VLR will be released in this case by a MAP_U_ABORT request, and the unsuccessful macro termination will indicate transaction termination. the MAP transaction with the VLR may be released by receiving a MAP_U_ABORT or MAP_P_ABORT indication. The call handling connection or MAP transaction on which the call, SMS or unstructured SS transaction is waiting for delivery, is released (indicated in the SDL by the output signal I-REL), and the unsuccessful macro termination will indicate transaction termination.
2488
3GPP
2489 Release 4
859
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition Page_MSC
Figure 25.3/1: Mac ro Page_MSC
25.3_1(1)
MA P_PA GE_ Ind
Check_ Indication Error OK LA I known yes Call_ still_ exists yes no no
Set UE= Unknown LA I
S et UE = S ystem Fail ure yes
MS con nect ion exist s no
yes S MS or SS no MA P_ PA GE_Rs p MAP _DELIMITER_Req yes NDUB no Error
A_P age_ Request
W AI T_FOR_ PAGE _RE SP ONS E
S et a ccess connection status
Set UE = Busy Subscriber
OK
A_P age_ Response
A _No_P age_ Response
A_CM_SE RV_ Req uest
I_REL
MA P_U_A BORT_Ind, MA P_P_AB ORT_Ind
S et acc ess con nect ion status
S et UE= A bsent S ubscri ber
Set UE = Busy Subscriber
MA P_U_ A BORT_ _Req
I_REL
OK
Null
6948
6949
Figure 25.3/1: Macro Page_MSC
2490
3GPP
2491 Release 4
860
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition Search_For_MS_MSC
Figure 25.3/ 2: Macro S earc h_For_MS _MS C
25.3_2(1)
MA P_SE ARCH_ FOR_MS_Ind
Check_ Indication Error OK Call still exists yes no
Set UE= S yst em Failure yes
MS con nect ion exist s no
MA P_SE ARCH_ FOR_MS_Rsp yes S MS or S S MA P_ DELIMITER_ Req
A_P age_ Request
no
W AIT_FOR_ S EA RCH_ RES PONS E
no NDUB E rror
yes
A_P age_ Response
Set UE = Busy Subscriber
MA P_SE ARCH_ FOR_MS_Rsp
MA P_ DELIMITER_ Req
A _No_P age_ Response
A_CM_SE RV_ Req uest
I_REL
MA P_P_AB ORT_Ind, MA P_U_A BORT_Ind
Set access con nection status and LAI
S et UE= A bsent S ubscri ber
Set UE = Busy Subscriber
MA P_U_ A BORT_ Req
I_REL
OK
Null
Null
6950
6951
Figure 25.3/2: Macro Search_for_MS_MSC
2492
3GPP
2493 Release 4
861
3GPP TS 29.002 V4.17.0 (2006-06)
6952
25.4 Macros for handling an Access Request
6953 These macros are invoked when a MS accesses the network, e.g. to set up an outgoing call or when responding to 6954 paging. The macro handles identification and authentication of the mobile subscriber as well as invocation of security 6955 related features (see 3GPP TS 42.009 [6]).
6956
25.4.1 Macro Process_Access_Request_MSC
6957 This macro is invoked by any procedure receiving an access request from the MS, e.g. the page response at mobile 6958 terminating call set-up or the request for outgoing call set-up. 6959 If no dialogue with the VLR exists (e.g. within the procedure for outgoing call set-up), the MSC will open a dialogue 6960 towards the VLR by sending a MAP_OPEN request without any user specific parameters. 6961 In any case, the parameters received from the MS are mapped to a MAP_PROCESS_ACCESS_REQUEST request 6962 primitive, containing: 6963 6964 6965 6966 6967 6968
the received subscriber identification (IMSI, TMSI) or - in case of emergency call set-up - an IMEI; 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.
6969 If opening of the dialogue was required, the MSC will wait for the dialogue confirmation (see macro 6970 Receive_Open_Confirmation, clause 25.1), leading either to: 6971 6972 6973 6974 6975
immediate unsuccessful exit from the macro, in case no dialogue is possible; reversion to MAP version one dialogue if indicated by the VLR. The macro terminates with unsuccessful outcome, as the complete dialogue will be covered by the version one procedure, so that no further action from the calling process is required; continuation as given below, if the dialogue is accepted by the VLR.
6976 The MSC waits then for the MAP_PROCESS_ACCESS_REQUEST confirmation. In between, several other 6977 indications may be received from the VLR: 6978 6979 6980 6981 6982 6983 6984 6985 6986 6987 6988 6989 6990 6991 6992 6993
the MSC may receive a MAP_PROVIDE_IMSI indication, handled by the macro Obtain_IMSI_MSC defined in clause 25.8. In case of positive outcome, the procedure continues waiting for the MAP_PROCESS_ACCESS_REQUEST confirmation, else the macro terminates with unsuccessful outcome; the MSC may receive a MAP_AUTHENTICATE indication, handled by the macro Authenticate_MSC defined in clause 25.5. In case of positive outcome, the procedure continues waiting for the MAP_PROCESS_ACCESS_REQUEST confirmation, else the macro terminates with unsuccessful outcome; the MSC may receive a MAP_TRACE_SUBSCRIBER_ACTIVITY indication, handled by the macro Trace_Subscriber_Activity_MSC defined in clause 25.9; the MSC may receive a MAP_SET_CIPHERING_MODE indication, which will be stored for initiating ciphering later on; the MSC may receive a MAP_CHECK_IMEI indication, handled by the macro Check_IMEI_MSC defined in clause 25.6. In case of positive outcome, the procedure continues waiting for the MAP_PROCESS_ACCESS_REQUEST confirmation, else the macro terminates with unsuccessful outcome; the MSC may receive a MAP_Obtain_IMEI indication, handled by the macro Obtain_IMEI_MSC defined in clause 25.6. In case of positive outcome, the procedure continues waiting for the MAP_PROCESS_ACCESS_REQUEST confirmation, else the macro terminates with unsuccessful outcome;
2494
3GPP
2495 Release 4
862
3GPP TS 29.002 V4.17.0 (2006-06)
6994 6995 6996 6997 6998 6999 7000 7001 7002 7003 7004 7005 7006 7007 7008 7009 7010
the MSC may receive a MAP_U_ABORT or MAP_P_ABORT indication, or a premature MAP_CLOSE indication from the VLR. In all these cases, the macro terminates with unsuccessful outcome, after sending the appropriate reject towards the MS (see 3GPP TS 29.010 [58]); the MSC may receive a MAP_NOTICE indication from the VLR. In this case, the dialogue towards the VLR is terminated by a MAP_CLOSE primitive, the appropriate reject is sent towards the MS (see 3GPP TS 29.010 [58]), and the macro terminates with unsuccessful outcome; the MSC may receive an indication for release of the radio path, in which case the dialogue towards the VLR will be terminated by a MAP_U_ABORT primitive, containing the diagnostic information Radio Channel Release.
When the MAP_PROCESS_ACCESS_REQUEST confirmation is received, the parameters of this primitive are checked first. In case of unsuccessful outcome of the service, the MAP User Error received is mapped onto the appropriate radio interface message (see 3GPP TS 29.010 [58]), before the macro terminates with unsuccessful outcome. In case of positive outcome of the service, ciphering is initiated on the radio path, if this had been requested by the VLR (see above). Otherwise, if the access request was not triggered by a page response from the MS, the access request is accepted explicitly by sending a CM_Service_Accept message to the MS. If the access request was triggered by a page response from the MS then no CM Service Accept message is sent.
7011 After ciphering has been initiated, the MSC will wait for the MAP_FORWARD_NEW_TMSI indication from the VLR. 7012 While waiting, the MSC may receive: 7013 7014 7015 7016 7017 7018 7019 7020 7021 7022 7023 7024 7025 7026 7027 7028 7029
a MAP_U_ABORT or MAP_P_ABORT indication, or a premature MAP_CLOSE indication from the VLR. In these cases, the macro terminates with unsuccessful outcome, after sending a release request towards the MS (see 3GPP TS 29.010 [58]); a MAP_NOTICE indication from the VLR. In this case, the dialogue towards the VLR is terminated by a MAP_CLOSE primitive, the appropriate reject is sent towards the MS (see 3GPP TS 29.010 [58]), and the macro terminates with unsuccessful outcome; an indication for release of the radio path, in which case the dialogue towards the VLR will be terminated by a MAP_U_ABORT primitive, containing the diagnostic information Radio Channel Release; a MAP_DELIMITER request from the VLR. This will be taken as a successful outcome of the macro (i.e. the VLR did not require TMSI reallocation), and it terminates successfully; an A_SETUP request from the MS. This will be saved for handling by the procedure which invoked the macro Process_Access_Request_MSC after the macro has terminated.
When the MAP_FORWARD_NEW_TMSI indication is received in the MSC, the TMSI Reallocation Command is sent to the MS, and the MSC waits for an acknowledgement from the MS. In case a positive acknowledgement is received, the MSC sends an empty MAP_FORWARD_NEW_TMSI response primitive to the VLR and terminates successfully. Else, the dialogue is terminated locally (MAP_CLOSE_Req with Release method Prearranged End) without any further action.
7030 If the MSC receives an A_SETUP request while it is waiting for the TMSI acknowledgement from the MS, the 7031 A_SETUP is saved for handling by the procedure which invoked the macro Process_Access_Request_MSC after the 7032 macro has terminated. 7033 If the dialogue is aborted by the VLR while waiting for the TMSI acknowledgement from the MS, the MSC regards the 7034 access request to be failed and terminates with unsuccessful outcome, after sending a release request towards the MS 7035 (see 3GPP TS 29.010 [58]).
2496
3GPP
2497 Release 4
863
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition Process_Access_Request_MSC
Figure 25.4/1: Macro for processing the acc ess request in MSC
25.4_1.1(3)
yes
V LR_ Dialogue_ exist s
no
MAP_OP EN_Req, MAP_P ROCE SS_A CCES S_RE QUES T_Req, MAP _DELIMITER_Re q MAP _P ROCE SS_A CCES S_ _REQ UE ST_Req, MAP _DELIMITER_Req
Rec eive_Open_ Cnf
V1 OK Error Perform_MA P_ V1_Procedure
W AI T_FOR_ PROCES S_ACCES S_ RE SULT
Error Error
MA P_PROCES S_ ACCES S_ RE QUEST_Cnf
Obtain_IMSI_ MS C
uthent icate_ _MS C
Trace_ S ubscriber_ A ctivity_MSC
Chec k_ Conf irmation
OK
Error
OK
E rror
OK
Error
Error
W AIT_FOR_ P ROCE SS _A CCE SS _ RE SULT
W A IT_FOR_ P ROCE SS_ A CCES S_ RES ULT
W AI T_FOR_ PROCE SS_ACCES S_ RE SULT
Ciphering_ Required
no
P rovider error, User error, Dat a error
yes
yes
CM Service type = Page Response no
Map_Error_to_ Rejec t_Cause
A_CIP HER_ MODE_ COMMA ND
A _CM_ S ERV_A CC
A_CM_ SE RV _RE J
W AIT
E rror
7036
7037
Figure 25.4/1 (sheet 1 of 3): Macro Process_Access_Request_MSC
2498
3GPP
2499 Release 4
864
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition Process_Access_Request_MSC
Figure 25.4/1: Macro for processing the acc ess request in MSC
25.4_1.2(3)
W AI T_FOR_ P ROCE SS_A CCESS_ RES ULT
MAP _U_AB ORT_Ind, MAP _P _ABORT_Ind, MAP _CLOSE _Ind
MAP _SE T_ CIPHERING_ MODE _Ind
A _DISC_Ind
MAP _NOTICE _ Ind
MAP_CLOS E_ Req Set_Ciphering_ Required A _CM_ S ERV _REJ MAP _U_AB ORT_ Req A_CM_ S ERV_REJ
W AI T_FOR_ P ROCE SS_A CCESS_ RES ULT
Error
Error
Error
Check_IM EI_ MSC
Obtain_IMEI_ MS C
OK
Error
OK
Error
W AI T_FOR_ PROCES S_ACCES S_ RE SULT
Error
W A IT_FO R_ P ROCE SS_A CCES S_ RES ULT
E rror
7038
7039
Figure 25.4/1 (sheet 2 of 3): Macro Process_Access_Request_MSC
2500
3GPP
2501 Release 4
865
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition Process_Access_Request_MSC
Figure 25.4/1: Macro for processing the acc ess request in MSC
25.4_1.3(3)
W A IT
MAP _FORW A RD_ NEW _ TMS I_Ind
MA P_ DELIMITER_ Ind
MA P_ N OTICE_ Ind
A _DISC_Ind
MAP _U_A BORT_Ind, MAP _P _AB ORT_Ind, MAP _CLO SE_Ind
A_TMSI_ REA LLOC_ CMD OK
A _CM_ S ERV_ R EJ
MAP _U_ A BORT_ Req
A_CM_ SE RV_ REJ
MA P_C LOSE _ Req W AIT_FOR_ TMSI_ack
Error
Error
A _S ETUP
Error
A_TMSI_ REA LLOC_ COMP LETE
A _SE TUP
A _TMSI_ RE ALLOC_ FA ILURE
MAP _U_A BORT_Ind, MAP _P _AB ORT_Ind, MAP _CLO SE_Ind
M AP_FORW ARD_NEW _TMSI_Rsp, M AP _DELIMITER_Req
OK
A _DISC_Req
OK
Error
7040
7041
Figure 25.4/1 (sheet 3 of 3): Macro Process_Access_Request_MSC
2502
3GPP
2503 Release 4
866
3GPP TS 29.002 V4.17.0 (2006-06)
7042
25.4.2 Macro Process_Access_Request_VLR
7043 When the VLR receives a MAP_PROCESS_ACCESS_REQUEST indication, the VLR will check this indication first 7044 (macro Check_Indication, see clause 25.2). In case of negative outcome, the macro will proceed with the error handling 7045 described below. 7046 If the indication data are correct, it is checked first whether the subscriber identification (IMSI or TMSI) is known if 7047 included: 7048 7049 7050 7051 7052 7053
if the identification is not known, the IMSI may be requested from the MS, described in the macro Identification_Procedure (see below) with outcome: OK, if a IMSI known in the VLR has been received; Error, if the VLR did not recognise the subscriber's identity. The macro will proceed with the error handling described below; Aborted, if the transaction to the MSC is released. The macro will terminate immediately with unsuccessful.
7054 In case the identity received is an IMEI, the error System Failure is set and the macro proceeds with the error handling 7055 described below. 7056
NOTE:
Emergency Call with IMEI may be accepted within the error handling phase.
7057 For a known subscriber the authentication check is performed next (see macro Authenticate_VLR, clause 25.5), if 7058 required. If a negative result is received, the VLR proceeds on receipt of user error: 7059 7060 7061 7062 7063 7064 7065 7066 7067 7068 7069 7070 7071 7072 7073 7074 7075 7076 7077 7078 7079 7080
illegal subscriber depending on the identity used for authentication; In case IMSI is already used or no new authentication attempt with IMSI shall not be performed (operator option), the error Illegal Subscriber is set and the macro proceeds with the error handling described below. If a new authentication attempt with IMSI shall be performed, the IMSI is requested from the MS (macro Obtain_IMSI_VLR, see clause 25.8): the authentication will be performed again if a IMSI known in the VLR is received; the error Unidentified Subscriber is set and the macro proceeds with the error handling described below, if the IMSI received is unknown in VLR; if the IMSI request procedure fails for any other reason, the error System Failure is set and the macro proceeds with the error handling described below; if the dialogue has been aborted during the IMSI request, the macro terminates immediately with unsuccessful outcome;
unknown subscriber by setting the error Unidentified Subscriber and proceeding with the error handling described below. This can occur only in case of data inconsistency between HLR and VLR;
NOTE: -
procedure error by setting the error System Failure and proceeding with the error handling described below; null (i.e. the dialogue towards the MSC is terminated) by terminating immediately with unsuccessful outcome.
The MS access is accepted if no authentication is required or after successful authentication. Then, the indicator "Confirmed by Radio Contact" is set to "Confirmed". If the indicator "Location Information Confirmed in HLR" is set to "Not Confirmed", HLR updating will be started as an independent process (Update_Location_VLR, see clause 19.1.1.6).
7081 If the indicator "Confirmed by HLR" is set to "Not Confirmed", the error Unidentified Subscriber is set and the macro 7082 proceeds with the error handling described below.
2504
3GPP
2505 Release 4
867
3GPP TS 29.002 V4.17.0 (2006-06)
7083 If roaming is not allowed in the location area indicated in the Current Location Area Id parameter, the error Roaming 7084 Not Allowed qualified by the roaming restriction reason is set and the macro proceeds with the error handling described 7085 below. 7086 In case roaming is allowed, the IMSI is set to attached and the process for notifying the HLR that the subscriber is 7087 present is started if required (Subscriber Present VLR, see clause 25.10). 7088 At next, tracing is invoked if required by the operator (macro Trace_Subscriber_Activity_VLR, see clause 25.9). 7089 Thereafter, 7090 7091 7092 7093 7094 7095 7096 7097 7098 7099 7100 7101
if ciphering is not required, IMEI checking is invoked if required by the operator (see macro Check_IMEI_VLR defined in clause 25.6). The error Illegal Equipment is set in case of unsuccessful outcome of the IMEI check, the subscriber is marked as detached and the macro proceeds with the error handling described below. The macro terminates immediately with unsuccessful outcome if the MSC dialogue has been released during the IMEI check. Else, the macro terminates successfully by returning the MAP_PROCESS_ACCESS_REQUEST response containing the IMSI to indicate acceptance of the MS access. if ciphering is required, the MAP_SET_CIPHERING_MODE request containing: the cipher mode indicating the cipher algorithm required; and the cipher key to be used;
is sent to the MSC.
7102 As a further operator option, IMEI checking may be performed next. 7103 7104 7105 7106 7107 7108 7109 7110 7111 7112 7113 7114
The error Illegal Equipment is set in case of unsuccessful outcome of the IMEI check, the subscriber is marked as detached and the macro proceeds with the error handling described below. The macro terminates immediately with unsuccessful outcome if the MSC dialogue has been released during the IMEI check. Else, the macro terminates successfully by returning the MAP_PROCESS_ACCESS_REQUEST response containing the IMSI to indicate acceptance of the MS access. IF no TMSI reallocation is required (again an operator option), the macro terminates thereafter. Else, TMSI reallocation is performed by sending a MAP_FORWARD_NEW_TMSI request, containing the new TMSI as parameter. The old TMSI will be frozen until an acknowledgement from the MS has been received. Before the macro terminates, the VLR will wait for the MAP_FORWARD_NEW_TMSI response, containing no parameters if reallocation has been confirmed by the MS, or a Provider Error, otherwise, in which case the old TMSI is kept frozen to avoid double allocation. In this case, both the old as the new TMSI are subsequently regarded valid when used by the MS.
7115 Error handling 7116 In case some error is detected during handling the access request, a respective error has been set. Before returning this 7117 error cause to the MSC in a MAP_PROCESS_ACCESS_REQUEST response, it need to be checked whether this 7118 access is for emergency call set-up, as this will require extra treatment. 7119 If the CM Service type given in the MAP_PROCESS_ACCESS_REQUEST indication is emergency call set-up, it is 7120 checked whether EC set-up in the particular error situation is permitted (operator option). If so, it is checked whether 7121 the IMEI is required, and if so the IMEI is requested from the MS (macro Obtain_IMEI_VLR, see clause 25.6). 7122 7123 7124 7125 7126
The macro will terminate immediately with unsuccessful outcome if the MSC transaction has been aborted during the IMEI retrieval. In case of an error reported back from IMEI retrieval, MAP_PROCESS_ACCESS_REQUEST response containing the error cause set previously is returned to the MSC, the dialogue is closed (MAP_CLOSE request indicating normal release) and the macro terminates with unsuccessful outcome.
2506
3GPP
2507 Release 4
868
3GPP TS 29.002 V4.17.0 (2006-06)
7127 When a subscriber identity required by the operator (IMSI or IMEI) is available, the user error set previously is deleted, 7128 the respective identity is returned in the MAP_PROCESS_ACCESS_REQUEST response to indicate acceptance of 7129 emergency call, and the macro terminates with successful outcome. 7130 In all other cases, the MAP_PROCESS_ACCESS_REQUEST response containing the error cause set previously is 7131 returned to the MSC, the dialogue is closed (MAP_CLOSE request indicating normal release) and the macro terminates 7132 with unsuccessful outcome.
7133
25.4.3 Macro Identification Procedure
7134 This macro is invoked by the macro Process_Access_Request_VLR in case the subscribers identity is not known in the 7135 VLR. 7136 If the identity received from the MS is an IMSI, the error Unidentified Subscriber will be set and reported back to the 7137 calling macro (to be sent in the MAP_PROCESS_ACCESS_REQUEST response). The same error is used in case a 7138 TMSI was received from the MS, but the operator does not allow open identification of the MS. 7139 If open identification of the MS is allowed, the macro Obtain_IMSI_VLR is invoked, requesting the subscribers IMSI 7140 from the MS (see clause 25.8), with outcome 7141 7142 7143 7144 7145
OK, in which case it is checked whether for the IMSI received there exists a subscriber record in the VLR. If so, the macro terminates successfully, else the error Unidentified Subscriber will be set and reported back to the calling macro. Error, in which case the error System Failure will be set and reported back to the calling macro. Aborted, i.e. the MSC transaction is released, in which the macro terminates accordingly.
2508
3GPP
2509 Release 4
869
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefiniti on P rocess_Acc ess _R equest_VLR
F ig ure 25 .4/ 2: M a cro f or proces sing on acc ess request in V LR
25.4 _2.1(3)
M A P _P R O CE S S _A C CE S S _ _RE Q UE S T _I nd
Ch ec k_ _In dic at ion
OK no ID _kn own 2 yes ID _P roc 1
E rror
OK y es ID= IM E I no 'S et _error_ _S ys tem_ _Failure' A uth_ _required yes 3 1 A ut henti cate_ _ V LR no 1 E rror E rror A bort ed
OK yes
Illegal_ _S ub sc rib er I MS I _used
Unk nown_ _S ubs criber 'S et_error_ _U nide ntified_ _S ubsc riber'
P r oc edure_ _E rror 'S et _error_ _S ys tem_ _Failure'
N ull
3 no
E rror
1 N ew_ _att emp t_wit h_ _I MS I no yes
O bt ain_I M S I_ _V LR E rror
'S et _error_ _Illegal_ _S ubsc riber'
OK
A bort ed 'S et _error_ _ S yst em_ _ Failure'
E rror I MS I _kn own no
yes
'S et_error_ _Un ident ified_ _S ub scriber'
7146
7147
Figure 25.4/2 (sheet 1 of 3): Macro Process_Access_Request_VLR
2510
3GPP
2511 Release 4
870
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefiniti on P rocess_Acc ess _R equest_VLR
F ig ure 25 .4/ 2: M a cro f or proces sing on acc ess request in V LR 3
25.4 _2.2(3)
'S et _c onfirm ed_ _ by_radio_ _ contac t'
'S et_I M S I_ _at tach ed '
Loc _info_ _c nf_in_ _ HLR yes
no
UL_V LR
A lert_ S C _required no
yes
S ubsc riber_ _P res ent _V L R
'S et _P ara_ _t o_I MS I '
C nf_ _ by_H LR yes R oam in g_ _ in_LA _ _allowed yes
no
MA P _P R O C E S S _A CC E S S _ _RE Q U E S T_R sp, MA P _D E LI MI TE R_R eq
no OK 'S et _error_ _Roami ng_Not_ _A llo wed ' yes 'S et_error_ _U nidentified_ _S ubsc ribe r'
Tracin g_ _R equired no
Trac e_ _S ubs criber_ _A c tivit y_V LR
C ipherin g_ _R equired yes
no
M A P _S E T _CI P HE R ING _MO D E _Req, M A P _D E LI MITE R _R eq E rror IM E I_ _Chec k_R eq no yes 'S et_I MS I_ _det ached' E rror
I ME I_ _Ch eck_ Req y es Check _I ME I_ _V LR
no
C hec k _IM E I_ _V LR
OK OK A b ort ed 'S et _error_ _Ill egal_ _ E quip ment ' A b ort ed
E rror
E rror
7148
7149
Figure 25.4/2 (sheet 2 of 3): Macro Process_Access_Request_VLR
2512
3GPP
2513 Release 4
871
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefiniti on P rocess_Acc ess _R equest_VLR
F ig ure 25 .4/ 2: M a cro f or proces sing on acc ess request in V LR 4
25.4 _2.3(3)
'S et _P ara_ _t o_ IMS I'
MA P _P RO C E S S _A CC E S S _ _RE Q U E S T_R sp
TM S I_ _Realloc_ _R eq 1 yes MA P _FO RW A RD _N E W _ TMS I _Req, MA P _D E LI MI TE R_R eq CM_ _S ervice_Typ e_ _E C yes no 'Unfreeze_ _old_ TMS I '
no
MA P _ _DE L IMI TE R_ _R eq
OK
EC_ _s etup_ _allowed yes
no W A I T_ FO R_ _TM S I_A C K
no
IM E I_ _required yes
MA P _FO R W A RD_ _NE W _TMS I _Cnf
P ara=E rror O b tain_I ME I_ _ V LR yes E rr or OK A bort ed
no
'U nfreez e_ _old_T MS I '
OK 'Reset _Us er_ _E rro r' M A P _P RO C E S S _A C CE S S _ _RE Q UE S T_ Rs p, M A P _CLO S E _ Req
E rror
'S et _P ara_ _ to_I ME I '
E rror MA P _P R O CE S S _A CCE S S _ _R E Q U E S T_Rs p, MA P _D E LI MI TE R_R eq
OK
7150
7151
Figure 25.4/2 (sheet 3 of 3): Macro Process_Access_Request_VLR
2514
3GPP
2515 Release 4
872
3GPP TS 29.002 V4.17.0 (2006-06)
Macro definition ID _Proc_V LR
F ig u re 2 5. 4/ 3
25.4_3(1)
y es ID= IMS I no Id en tific at io n_ _ allo w e d no
y es
O b ta in _IM S I _ _V L R E rro r OK A bo rte d
no I M S I _k now n y es A b o rt e d
OK
' S et _e rror_ _ Un ide nt if ie d _ _ S u bs c ribe r'
'S e t_ erro r_ _U n id en tified _ _ Su b s cr ib er'
E rror
E rr or
7152
7153
Figure 25.4/3: Macro ID_Proc_VLR
2516
3GPP
2517 Release 4
873
3GPP TS 29.002 V4.17.0 (2006-06)
7154
25.5 Authentication macros and processes
25.5.1 Macro Authenticate_MSC
This macro is used by the MSC to relay a request for authentication transparently from the VLR to the MS, wait for a response from the MS and to relay the response from the MS back to the VLR. If, while the MSC is waiting for the authentication response, the air interface connection is released or a MAP_U_ABORT, MAP_P_ABORT or MAP_CLOSE indication is received from the VLR, then necessary connections are released and the "Error" exit is used. The macro is described in figure 25.5/1.
7155 The following macros are used in the GSM network in order to enable authentication of a mobile subscriber.
7156
7157 7158 7159 7160 7161
7162
25.5.2 Macro Authenticate_VLR
if there are not enough authentication vectors in the VLR to perform the authentication, then the macro "Obtain_Authent_Para_VLR" described below is invoked. If this macro fails, then the corresponding error (Unknown Subscriber or Procedure Error) is returned to the calling process; if there are enough authentication vectors in the VLR, or the Obtain_Authent_Para_VLR macro was successful, then a MAP_AUTHENTICATE request is sent to the MSC. This request contains the RAND, CKSN or KSI, and possibly AUTN parameters as indicated in the service description; the VLR then waits for a response from the MSC; if a MAP_U_ABORT, MAP_P_ABORT or MAP_CLOSE indication is received from the MSC in this wait state, the VLR checks whether authentication sets are available. If no sets are available the process Obtain_Authent_Sets_VLR is invoked to fetch authentication sets from the HLR. The "Null" exit is then used; if a MAP_NOTICE indication is received from the MSC in this wait state, the VLR closes the dialogue with the MSC, then checks whether authentication sets are available. If no sets are available the process Obtain_Authent_Sets_VLR is invoked to fetch authentication sets from the HLR. The "Null" exit is then used; if a MAP_AUTHENTICATE confirmation is received by the VLR, it checks whether the received Signed Result (SRES) is identical to the stored one (see 3GPP TS 43.020 [24]), or whether the received RES is identical to the stored XRES. If this is not the case, the "Illegal Subscriber" exit is used. If the SRES values or RES and XRES are identical, then the "OK" exit is used; before exit, the VLR may fetch a new set of triplets from the HLR. This is done by initiating a separate Obtain_Authent_Sets_VLR process described below.
7163 This macro is used by the VLR to control the authentication of a subscriber. The macro proceeds as follows: 7164 7165 7166 7167 7168 7169 7170 7171 7172 7173 7174 7175 7176 7177 7178 7179 7180 7181 7182
7183 The macro is described in figure 25.5/2.
7184
25.5.3 Process Obtain_Authentication_Sets_VLR
7185 This process is initiated by the VLR to fetch authentication vectors from a subscriber's HLR in a stand-alone, 7186 independent manner. The Obtain_Authent_Para_VLR macro described below is simply called; the process is described 7187 in figure 25.5/3.
7188
25.5.4 Macro Obtain_Authent_Para_VLR
a connection is opened, and a MAP_SEND_AUTHENTICATION_INFO request sent to the HLR; if the HLR indicates that a MAP version 1 or 2 dialogue is to be used, the VLR performs the equivalent MAP version 1 or 2 dialogue. which can return a positive result containing authentication sets, an empty positive result, or an error; if the dialogue opening fails, the "Procedure Error" exit is used. Otherwise, the VLR waits for the response from the HLR;
7189 This macro is used by the VLR to request authentication vectors from the HLR. The macro proceeds as follows: 7190 7191 7192 7193 7194 7195
2518
3GPP
2519 Release 4
874
3GPP TS 29.002 V4.17.0 (2006-06)
7196 7197
if a MAP_SEND_AUTHENTICATION_INFO confirmation is received from the HLR, the VLR checks the received data.
7198 One of the following positive responses may be received from a MAP version 1 or MAP version 2 dialogue with the 7199 HLR: 7200 7201
Authentication triplets, in which case the outcome is successful; Empty response, in which case the VLR may re-use old triplets, if allowed by the PLMN operator.
7202 If the VLR cannot re-use old triplets (or no such triplets are available) then the "Procedure Error" exit is used. 7203 If the outcome was successful or re-use of old parameters in the VLR is allowed, then the "OK" exit is used. 7204 If an "Unknown Subscriber" error is returned by the MAP version 1 or 2 dialogue, then the "Unknown Subscriber" exit 7205 is used. 7206 7207 7208 7209 7210 7211 7212 7213
In a MAP version 3 dialogue a (possibly empty) set of authentication vectors may be received, transferred by means of the TC-RESULT-L service, from the HLR followed by a MAP_CLOSE_Indication or by a MAP_DELIMITER_Indication. If a MAP_DELIMITER_Indication is received, the VLR may request additional authentication vectors from the HLR by sending a new MAP_SEND_AUTHENTIFICATION_INFO_Request with no parameter part. If a MAP_CLOSE_Indication is received, and authentication vectors have been received during the dialogue, then the "OK" exit is used. If no authentication vectors have been received during the dialogue, the VLR checks whether old GSM Triplets are available and can be re-used. If so, the "OK" exit is used, otherwise the "Procedure Error" exit is used. Note that re-use of old UMTS Quintuplets is not allowed.
7214 If in a MAP version 3 dialogue an "Unknown Subscriber" error is received, then the "Unknown Subscriber" exit is used. 7215 If other errors are received, the VLR checks whether old GSM Triplets are available and can be re-used. If so, the "OK" 7216 exit is used, otherwise the "Procedure Error" exit is used. Note that re-use of old UMTS Quintuplets is not allowed. 7217 7218 7219 7220 7221 7222 7223 7224 7225 7226
if a MAP-U-ABORT, MAP_P_ABORT, MAP_NOTICE or unexpected MAP_CLOSE service indication is received from the MSC, then open connections are terminated, and the macro takes the "Null" exit; if a MAP-U-ABORT, MAP_P_ABORT or unexpected MAP_CLOSE service indication is received from the HLR, then the VLR checks whether old authentication parameters (GSM triplets) can be re-used. If old parameters cannot be re-used the macro takes the "Procedure Error" exit; otherwise it takes the "OK" exit; note that re-use of old UMTS Quintuplets is not allowed; if a MAP_NOTICE service indication is received from the HLR, then the dialogue with the HLR is closed. The VLR then checks whether old authentication parameters (GSM triplets) can be re-used. If old parameters cannot be re-used the macro takes the "Procedure Error" exit; otherwise it takes the "OK" exit; note that re-use of old UMTS Quintuplets is not allowed.
7227 The macro is described in figure 25.5/4.
7228
25.5.5 Process Obtain_Auth_Sets_HLR
reversion to version one or two procedure; procedure termination; or dialogue acceptance, with proceeding as below.
7229 Opening of the dialogue is described in the macro Receive_Open_Ind in clause 25.1, with outcomes: 7230 7231 7232
7233 This process is used by the HLR to obtain authentication vectors from the AuC, upon request from the VLR or from the 7234 SGSN. The process acts as follows: 7235
a MAP_SEND_AUTHENTICATION_INFO indication is received by the HLR; -the HLR checks the service indication for errors. If any, they are reported to the VLR or to the SGSN in the MAP_SEND_AUTHENTICATION_INFO response. If no errors are detected, authentication vectors are fetched from the AuC. Further details are found in 3GPP TS 43.020 [24];
7236
7237 7238
2520
3GPP
2521 Release 4
875
3GPP TS 29.002 V4.17.0 (2006-06)
7239
7240 7241
-If Network Access Mode is set to non-GPRS only and if the Requesting Node Type is present and indicates SGSN, the HLR may return error Unknown Subscriber (with diagnostic value set to Gprs Subscription Unknown) in the response and terminate the process; -If Network Access Mode is set to GPRS only and if the Requesting Node Type is present and indicates VLR, the HLR may return error Unknown Subscriber in the response and terminate the process; -if errors are detected they are reported to the VLR or to the SGSN in the MAP_SEND_AUTHENTICATION_INFO response. Otherwise the authentication vectors are returned by means of the TC-RESULT-L service. if segmentation of the response message is required and allowed, a MAP_SEND_AUTHENTICATION_INFO_response transferred by means of the TC-RESULT-L service, containing at least one authentication vector, followed by a MAP_DELIMITER_request is returned to the VLR or SGSN, the remaining authentication vectors are stored and the HLR waits for a new service indication from the VLR or SGSN.
7242
7243
7244
7245 7246 7247 7248 7249 7250 7251
7252 The process is described in figure 25.5/5.
2522
3GPP
2523 Release 4
876
3GPP TS 29.002 V4.17.0 (2006-06)
Ma crodefinition A uthenticate_MSC
F ig ure 25 .5/ 1: A u the nt ication m ac ro in t he MS C , relaying aut hen ticat ion in dic ation from th e V LR t o t he M S , an d relay in g t he confirm ation f rom the MS C t o t he V LR
25.5_1(1)
W ait_f or_ _ A uth_f rom _ _M S
A _A UT HE NTIC A TE _c nf
A _C M_ RE L
MA P _U _A B O R T_ ind MA P _P _A B O RT_ind MA P _C LO S E _ind
MA P _ _A UT HEN TI C A TE _ _ind
No E rror ?
M A P _U_ A B O RT_req
Y es
C heck _ I ndicat ion E rror OK A _ A U THE N TIC A TE _req
S et error
E rro r
MA P _A U THE N TI C A TE _rsp
W ait _for_ A ut h_ from_ MS
MA P _ DE LI MI TE R_ req
OK
7253
7254
Figure 25.5/1: Macro Authenticate_MSC
2524
3GPP
2525 Release 4
877
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition Authenticate_VLR
Figure 25.5/2: Authentication macro in the VLR, controlling the authentication procedure towards the MSC/MS and obtaining authentication vectors from the HLR as applicable. yes Authentication vectors av ailable Obtain_Authent_ Para_VLR
215_2(1)
no
OK MAP_ To MSC AUTHENTICATE_Req MAP_ DELIMITER_ To MSC Req Wait for response
Null Null
Unknown_subscriber Unknown_ Subscriber
Procedure_error Procedure_ error
MAP__ From MSC AUTHENTICATE_Cnf Check_ Confirmation Section 25.2
MAP_U_ABORT_Ind, MAP_P_ABORT_Ind, MAP_CLOSE_Ind from MSC
MAP_ NOTICE_ Ind MAP_ CLOSE_ Req
From MSC
OK
Provider error, User Error, Data error no yes Authentication vectors av ailable no
Received SRES =expected SRES yes
Authentication no vectors av ailable Obtain_Authent_ yes Sets_VLR
Figure 25.5/3
Obtain_Authent_ Sets_VLR
Figure 25.5/3
OK
Illegal_subscriber
Null
7255
7256
Figure 25.5/2: Macro Authenticate_VLR
2526
3GPP
2527 Release 4
878
3GPP TS 29.002 V4.17.0 (2006-06)
Process O btain_A uthent_Sets_VLR
F ig ure 25 .5/ 3: P rocess to obt ain aut hent ication se ts from t he H LR to t he V LR
25.5_3(1)
O bt ain_ A u th ent_ P ara_V LR
Fig ure 25. 5/4
OK
Un known _ S ubs criber
P rocedure_ E rror
N ull
7257
7258
Figure 25.5/3: Process Obtain_Authentication_Sets_VLR
2528
3GPP
2529 Release 4
879
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition OBTAIN_AUTHENT_PARA_VLR
Figure 25.5/4: Macro to obtain authentication parameters from the HLR to the VLR
1(3)
MAP_OPEN_Req MAP_SEND_AUTHENTICATION_INFO_Req MAP_DELIMITER_Req
Receive_ Open_Cnf ok
Section 25.1
V2 Perform_ MAP_V2_ Dialogue
V1 Perform_ MAP_V1_ Dialogue
Error
WAIT_FOR_ AUTHENTICATION_ INFO
MAP_SEND_AUTHENTICATION_ INFO_Cnf
Procedure_ Error Positive result no yes
Empty result yes
no
Error = Unknown Subscriber 1 yes
no Re-use old Triplets no
yes
Unknown_ Subscriber
Procedure_ Error
OK
7259
7260
Figure 25.5/4 (sheet 1 of 3): Macro Obtain_Authent_Para_VLR
2530
3GPP
2531 Release 4
880
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition OBTAIN_AUTHENT_PARA_VLR
Figure 25.5/4: Macro to obtain authentication parameters from the HLR to the VLR
2(3)
Check_ Confirmation OK
Figure 25.2/2
Provider Error, Data Error no 2
User Error Unknown Subscriber yes
re-use old Triplets no
yes OK
Wait
Procedure_ Error
Unknown_ Subscriber
MAP_ CLOSE_ind
MAP_ DELIMITER_Ind
no yes 2 OK
Authentication vectors received
more vectors required yes
no
MAP_SEND_AUTHENTICATION_ INFO_req, MAP_DELIMITER_req
MAP_CLOSE_ req
OK WAIT_FOR_ AUTHENTICATION_ INFO
7261
7262
Figure 25.5/4 (sheet 2 of 3): Macro Obtain_Authent_Para_VLR
2532
3GPP
2533 Release 4
881
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition OBTAIN_AUTHENT_PARA_VLR
Figure 25.5/4: Macro to obtain authentication parameters from the HLR to the VLR
3(3)
WAIT_FOR_ AUTHENTICATION_ INFO
MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind from MSC
MAP_ NOTICE_ind
From HLR
MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind from HLR
MAP_ CLOSE_req
To HLR
MAP_U_ ABORT_req
to HLR
Re-use old Triplets yes
no
Null
OK
Procedure_Error
MAP_ NOTICE_ind
from MSC
MAP_ CLOSE_req
To MSC
MAP_U_ ABORT_req
To HLR
Null
7263
7264
Figure 25.5/4 (sheet 3 of 3): Macro Obtain_Authent_Para_VLR
2534
3GPP
2535 Release 4
882
3GPP TS 29.002 V4.17.0 (2006-06)
Process Obtain_Auth_Sets_HLR
Figure 25.5/5: Process in the HLR to obtain authentication sets from the AuC and relay them to the VLR
1(2)
Null
Receive_ Open_Ind Error Vr OK Wait_For Service_ Primitive MAP_NOTICE_ Ind
Figure 25.1/1
MAP_SEND_AUTHENTICATION_INFO_Ind
Check_ Indication OK Perform MAP Vr Dialogue
Figure 25.2/1
Error MAP_SEND_ AUTHENTICATION_INFO_ Rsp, MAP_CLOSE_Req
MAP_CLOSE_ Req
Null
Null
Null
Null
7265
7266
Figure 25.5/5 (sheet 1 of 2): Process Obtain_Auth_Sets_HLR
2536
3GPP
2537 Release 4
883
3GPP TS 29.002 V4.17.0 (2006-06)
process Obtain_Auth_Sets_HLR
Figure 25.5/5: Process in the HLR to obtain authentication sets from the AuC and relay them to the VLR 1
2(2)
Early check of Requesting Node Type implemented? no yes
no Requesting Node Type Present? yes no Requesting Node = SGSN and Network Access Mode = 'non-gprs only' yes Set Diagnostic to 'gprsSubscriptionUnknown' Requesting Node = VLR and Network Access Mode = 'g prs only' yes no
Set User Error to 'Unknown Subscriber'
Check available vecotrs Segmentation allowed and supported and needed yes
Figure 25.5/5a
MAP_SEND_AUTHENTICATION_INFO_Rsp MAP_CLOSE_Req
no
Null
MAP_SEND_AUTHENTICATION_INFO_Rsp MAP_CLOSE_Req to be stored for later use; see TS 33.102 (UMTS) or GSM 03.20 (GSM)
obtain vectors from AuC
Null
MAP_SEND_AUTHENTICATION_INFO_Rsp MAP_DELIMITER_Req Wait_For Serv ice_ Primitive
7267
7268
Figure 25.5/5 (sheet 2 of 2): Process Obtain_Auth_Sets_HLR
2538
3GPP
2539 Release 4
884
3GPP TS 29.002 V4.17.0 (2006-06)
pro cedu re Check _Availab l _Vect ors e
Fi g u 2 5 /5 a re .5
1(1 )
Ch e ck Av a l a b e i l Ve cto rs No Mo re ve c t rs re u e ste d o q th n sto re d a Ye s No ve c t r s t re d o o No Ye s
Im me d i a Re sp o n e te s P re rre d i n d c a r fe i to s u p o rte d p Ye s
No Re q u s t v e cto rs e fro m Au C No
Imm e d te R e p o s e ia s n Pre fe re r d Ye s
HL R ma y op n ll tio a y p e rm th i s rfo ta k s
Re q u s t v e cto rs e fro m Au C
7269
7270
Figure 25.5/6: Procedure Check_Available_Vectors
7271
25.5.6 Process Obtain_Authent_Para_SGSN
7272 For authentication procedure description see 3GPP TS 23.060 [104] and 3GPP TS 24.008 [35]. 7273 This Process is used by the SGSN to request authentication vectors from the HLR. 7274 If the SGSN does not know the subscriber's HLR address (e.g. no IMSI translation exists), the Authentication Parameter 7275 negative response with error Unknown HLR is returned to the requesting process.
2540
3GPP
2541 Release 4
885
3GPP TS 29.002 V4.17.0 (2006-06)
7276 Otherwise, the Process proceeds as follows: 7277 7278 7279 7280 7281 7282 7283 7284
a connection is opened, and a MAP_SEND_AUTHENTICATION_INFO request sent to the HLR; if the HLR indicates that a MAP version 1 or 2dialogue is to be used, the SGSN performs the equivalent MAP version 1 or 2dialogue. which can return a positive result containing authentication sets, an empty positive result, or an error; if the dialogue opening fails, the Authentication Parameters negative response with appropriate error is sent to the requesting process. Otherwise, the SGSN waits for the response from the HLR; if a MAP_SEND_AUTHENTICATION_INFO confirmation is received from the HLR, the SGSN checks the received data.
7285 One of the following positive responses may be received from a MAP version 1 or MAP version 2 dialogue with the 7286 HLR: 7287 7288
Authentication triplets, in which case the outcome is successful; Empty response, in which case the SGSN may re-use old triplets, if allowed by the PLMN operator.
7289 If the SGSN cannot re-use old triplets (or no such triplets are available) then the Authentication Parameters negative 7290 response with appropriate error is sent to the requesting process. 7291 If the outcome was successful or re-use of old parameters in the SGSN is allowed, then the Authentication Parameters 7292 response is sent to the requesting process 7293 If an "Unknown Subscriber" error is included in the MAP_SEND_AUTHENTICATION_INFO confirm or is returned 7294 by the MAP version 1 dialogue, then the appropriate error is sent to the requesting process in the Authentication 7295 Parameters negative response 7296 7297 7298 7299 7300 7301 7302 7303 7304 7305 7306 7307 7308 7309 7310 7311 7312 7313 7314
In a MAP version 3 dialogue a (possibly empty) set of authentication vectors may be received , transferred by means of the TC-RESULT-L service,from the HLR followed by a MAP_CLOSE_Indication or by a MAP_DELIMITER_Indication. If a MAP_DELIMITER_Indication is received, the SGSN may request additional authentication vectors from the HLR by sending a new MAP_SEND_AUTHENTIFICATION_INFO_Request. If a MAP_CLOSE_Indication is received, and authentication vectors have been received during the dialogue, then the "OK" exit is used. If no authentication vectors have been received during the dialogue, the SGSN checks whether old GSM Triplets are available and can be re-used. If so, the "OK" exit is used, otherwise the "Procedure Error" exit is used. Note that re-use of old UMTS Quintuplets is not allowed. If in a MAP version 3 dialogue an "Unknown Subscriber" error is received, then the "Unknown Subscriber" exit is used. If other errors are received, the SGSN checks whether old GSM Triplets are available and can be re-used. If so, the "OK" exit is used, otherwise the "Procedure Error" exit is used. Note that re-use of old UMTS Quintuplets is not allowed. if a MAP-U-ABORT, MAP_P_ABORT or unexpected MAP_CLOSE service indication is received from the HLR, then the SGSN checks whether old authentication parameters can be re-used. If old parameters cannot be re-used the Authentication Parameters negative response with appropriate error is sent to the requesting process. if a MAP_NOTICE service indication is received from the HLR, then the dialogue with the HLR is closed. The SGSN then checks whether old authentication parameters can be re-used. If old parameters cannot be re-used the process terminates and the Authentication Parameters negative response with appropriate error is sent to the requesting process; Otherwise the Authentication Parameters response is sent to requesting process.
7315 The process is described in figure 25.5/6.
2542
3GPP
2543 Release 4
886
3GPP TS 29.002 V4.17.0 (2006-06)
Process Obtain_Authent_Para_SGSN
Figure 25.5/6: Process to obtain authentication parameters from the HLR to the SGSN
1(3)
Idle
Authentication Parameter Reques t
from requesting proc ess see G SM 03.60
('no') 'Unknown_ HLR'
(yes)
1 1 1
Set Error
Unknown HLR
Authentication Parameter Negative Response
to requesting process see G SM 03.60
Idle
7316
7317
Figure 25.5/6 (sheet 1 of 3): Process Obtain_Authen_Para_SGSN
2544
3GPP
2545 Release 4
887
3GPP TS 29.002 V4.17.0 (2006-06)
Process Obtain_Authent_Para_SGSN
Figure 25.5/6: Process to obtain authentication parameters from the HLR to the SGSN
2(3)
MAP_OPEN_Req, MAP_SEND_AUTHENTICATION_INFO_Req, MAP_DELIMITER_Req
Receive_ Open_ Cnf OK
Section 25.1
V2
V1
Error
WAIT_FOR AUTHENTICATION_ INFO MAP_SEND_AUTHENTICATION_ INFO_Cnf Check_ confirmation OK
Perform MAP V2 Dialogue
Perform MAP V1 Dialogue
Figure 25.2/2 no else
Positive result
yes
WAIT
Unknow n Subscriber yes
no yes
Empty result
no
no 3
Re-use old Triplets
yes 2
7318
7319
Figure 25.5/6 (sheet 2 of 3): Process Obtain_Authen_Para_SGSN
2546
3GPP
2547 Release 4
888
3GPP TS 29.002 V4.17.0 (2006-06)
Process Obtain_Authent_Para_SGSN
Figure 25.5/6: Process to obtain authentication parameters from the HLR to the SGSN
3(3)
Wait
MAP_ CLOSE_ind
MAP_ DELIMITER_Ind
Authentic ation vectors receiv ed no yes
more vectors required yes
no
MAP_SEND_AUTHENTICATION_ INFO_req, MAP_DELIMITER_req
MAP_CLOSE_ req
WAIT_FOR_ AUTHENTICATION_ INFO
Authentic atin parameters negative response
To requesting process see GSM 03.60
Authentic ation parameters Response
To requesting process see GSM 03.60
Idle
Wait_FOR_ AUTHENTICATION_ INFO MAP_ NOTICE_ ind MAP_P_ABORT_ind, MAP_U_ABORT_ind, MAP_CLOSE_ind f rom HLR 3 MAP_CLOSE_ Req From HLR
7320
7321
Figure 25.5/6 (sheet 3 of 3): Process Obtain_Authen_Para_SGSN
2548
3GPP
2549 Release 4
889
3GPP TS 29.002 V4.17.0 (2006-06)
7322 7323 25.5.7.1
25.5.7 Process Authentication_Failure_Report
General
7324 The Authentication Failure Report procedure is used to notify a HLR about the occurrence of an authentication failure 7325 in the SGSN or VLR. 7326 The procedure is shown in figure 25.5/7.
VLR
HLR
MAP_AUTHENTICATION FAILURE_REPORT
MAP_AUTHENTICATION FAILURE_REPORT_ACK
7327
7328
Figure 25.5/7: Message Flows to Authentication Failure Report
SGSN
HLR
MAP_AUTHENTICATION FAILURE_REPORT
MAP_AUTHENTICATION FAILURE_REPORT_ACK
7329
7330
Figure 25.6/7: Message Flows to Authentication Failure Report
7331 25.5.7.2
Process in the VLR
2550
3GPP
2551 Release 4
890
3GPP TS 29.002 V4.17.0 (2006-06)
Process Note_Authentication_Failure_VLR
Process in the VLR to notify the HLR that an Authentication Failure has occured Signals to/from the left are to/from the process in the VLR; signals to/from the right are to from the HLR
1(1)
Idle
Authentication Failure Report MAP_OPEN_req MAP_AUTHENTICATION_FAILURE_REPORT_req MAP_DELIMITER_req Receive_Open_ Cnf OK vr, Error
Wait_for_Response
Idle
MAP_AUTHENTICATION_ FAILURE_REPORT_cnf
MAP_ NOTICE_Ind MAP_ CLOSE_Ind
MAP_CLOSE_Ind, MAP_U_ABORT_Ind, MAP_P_ABORT_Ind
Idle
7332
7333
Figure 25.6/8: Process Note_Authentication_Failure_VLR
2552
3GPP
2553 Release 4
891
3GPP TS 29.002 V4.17.0 (2006-06)
7334 25.5.7.3
Process in the SGSN
1(1)
Signals to/from the left are to/from the process in the SGSN; signals to/from the right are to from the HLR
Process Note_Authentication_Failure_SGSN
Process in the SGSN to notify the HLR that an Authentication Failure has occured
Idle
Authentication Failure Report MAP_OPEN_req MAP_AUTHENTICATION_FAILURE_REPORT_req MAP_DELIMITER_req Receive_Open_ Cnf OK vr, Error
Wait_for_Response
Idle
MAP_AUTHENTICATION_ FAILURE_REPORT_cnf
MAP_ NOTICE_Ind MAP_ CLOSE_Ind
MAP_CLOSE_Ind, MAP_U_ABORT_Ind, MAP_P_ABORT_Ind
Idle
7335
7336
Figure 25.6/9: Process Note_Authentication_Failure_SGSN
2554
3GPP
2555 Release 4
892
3GPP TS 29.002 V4.17.0 (2006-06)
7337 25.5.7.4
Process in the HLR
1(1)
Signals to/from the left are to/from the VLR or SGSN; signals to/from the Failure Report application in the HLR
Process Note_Authentication_Failure_HLR
Process in the HLR to handle an authentication failure report from the VLR or SGSN
Idle
Receive_Open_ Ind OK
Section 25.1.1 vr, Error MAP_P_ ABORT_rec
Wait_for_Report
Idle
MAP_AUTHENTICATION_ FAILURE_REPORT_req unknown subscriber? ? unexpected data value?
MAP_ NOTICE_Ind MAP_ CLOSE_req
MAP_P_ ABORT_Ind
yes
yes Idle
Authentication Failure Report set user error
MAP_AUTHENTICATION_ FAILURE_REPORT_rsp MAP_CLOSE_req Idle
7338
7339
Figure 25.6/10: Process Note_Authentication_Failure_HLR
2556
3GPP
2557 Release 4
893
3GPP TS 29.002 V4.17.0 (2006-06)
7340
25.6 IMEI Handling Macros
7341 The following macros are used in the GSM network in order to enable handling and checking of the mobile equipment 7342 identity.
7343
25.6.1 Macro Check_IMEI_MSC
7344 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 7345 back to the VLR. The macro proceeds as follows: 7346 7347 7348 7349 7350 7351 7352 7353 7354 7355 7356 7357 7358 7359 7360 7361 7362 7363 7364 7365 7366 7367 7368
a MAP_CHECK_IMEI service indication containing only the Invoke Id is received from the VLR; if the IMEI is not available in the MSC, it is requested from the MS using the IDENTITY REQUEST message; if the MS releases the radio resources, a MAP_U_ABORT request indicating "Application procedure Cancellation" is sent to the VLR, and the "Error" exit of the macro is used; when the IMEI is known, a connection is set up towards the EIR, and a MAP_CHECK_IMEI service request is sent including the IMEI; if the opening of the dialogue fails, a System Failure is reported to the VLR. Otherwise, the MSC waits for a response from the EIR; when the MAP_CHECK_IMEI service confirm is received, it is checked for errors. Any errors discovered in the MSC lead to the System Failure error to be reported to the VLR in the MAP_CHECK_IMEI response. Any errors reported from the EIR are sent directly to the VLR in the MAP_CHECK_IMEI service response. If no errors are detected by or reported to the MSC, the IMEI is added to the MAP_CHECK_IMEI service response returned to the VLR. The "OK" exit is used in all cases; if a MAP_P_ABORT, MAP_U_ABORT, MAP_CLOSE or MAP_NOTICE service indication is received from the EIR, the MSC closes the transaction with the EIR (if necessary), reports a System Failure error back to the VLR in the MAP_CHECK_IMEI response, and uses the macro's "OK" exit; if a MAP_P_ABORT, MAP_U_ABORT, MAP_CLOSE or MAP_NOTICE indication is received from the VLR, the MSC closes the transaction with the VLR (if necessary) and aborts the connections towards the EIR and the MS; the macro takes the "Error" exit.
If the dialogue with the EIR drops back to version 1, the result or error returned by the EIR is checked. The use of the "Check_Confirmation" macro in the SDL diagram indicates that the checks carried out on the result returned by the EIR in a MAP v1 dialogue are functionally equivalent to those carried out on the parameters of the MAP_CHECK_IMEI confirm received from the EIR in a MAP v2 dialogue.
7369 The macro is described in figure 25.6/1.
7370
25.6.2 Macro Check_IMEI_VLR
a MAP_CHECK_IMEI service request is sent to the MSC, including only the Invoke Id; the VLR then waits for the response from the MSC; if a MAP_CHECK_IMEI service confirm including either: the IMEI and the Equipment Status; or an error;
7371 This macro is used by the VLR to control the check of a mobile equipment's IMEI. The macro proceeds as follows: 7372 7373 7374 7375 7376 7377 7378 7379 7380 7381
is received, the VLR checks whether the response requires that an alarm be generated on the Operation and Maintenance interface. The criteria for such alarms are PLMN operator dependent; the VLR then checks whether the response from the MSC means that service is granted to the MS. The criteria for granting service depending on the equipment status or errors received in the MAP_CHECK_IMEI service response are also PLMN operator dependent;
2558
3GPP
2559 Release 4
894
3GPP TS 29.002 V4.17.0 (2006-06)
7382 7383
if a MAP_P_ABORT, MAP_U_ABORT, MAP_CLOSE or MAP_NOTICE indication is received from the MSC, then the MSC connection is closed (if necessary) and the macro takes the "Aborted" exit.
7384 The macro is described in figure 25.6/2.
7385
25.6.3 Process Check_IMEI_EIR
7386 This process is used by the EIR to obtain the status of a piece of mobile equipment, upon request from the MSC or from 7387 the SGSN. The process acts as follows: 7388 7389 7390 7391 7392 7393 7394 7395 7396 7397
a MAP_OPEN service indication is received (macro Receive_Open_Ind, clause 25.1.1). If the dialogue opening fails, the process terminates; otherwise, a MAP_CHECK_IMEI indication is received by the EIR, containing the IMEI to be checked; the EIR checks the service indication for errors. If there are any, they are reported to the MSC or to the SGSN in the MAP_CHECK_IMEI response. If no errors are detected, the EIR data base function is interrogated for the status of the given equipment. Further details are found in 3GPP TS 22.016 [7]; the status of the equipment (white-listed, grey-listed, black-listed or unknown) is returned to the MSC or to the SGSN in the MAP_CHECK_IMEI service response; if a MAP_U_ABORT, MAP_P_ABORT, MAP_NOTICE or MAP_CLOSE indication is received from the MSC or from the SGSN at any time during this process, the process in the EIR terminates.
7398 The process is described in figure 25.6/3.
7399
25.6.4 Macro Obtain_IMEI_MSC
7400 This macro is used by the MSC to respond to a request from the VLR to provide the IMEI. The macro proceeds as 7401 follows: 7402 7403 7404 7405 7406 7407 7408 7409
a MAP_OBTAIN_IMEI service indication containing only the Invoke Id is received from the VLR; if the IMEI is not available in the MSC, it is requested from the MS using the IDENTITY REQUEST message; when the IMEI is known, it is returned to the VLR in the MAP_OBTAIN_IMEI service response. The macro terminates at the "OK" exit; if the IMEI cannot be obtained by the MSC, the System Failure error is reported back to the VLR in the MAP_OBTAIN_IMEI service response. The macro terminates at the "OK" exit; if a MAP_P_ABORT, MAP_U_ABORT or MAP_CLOSE indication is received from the VLR, the macro terminates at the "Error" exit.
7410 The macro is described in figure 25.6/4.
7411
25.6.5 Macro Obtain_IMEI_VLR
7412 This macro is used by the VLR to obtain the IMEI from the MSC, e.g. to enable handling of emergency calls in case of 7413 authentication failure (in which case the IMEI may be used by some operators as an alternative to the IMSI). It proceeds 7414 as follows: 7415 7416 7417 7418 7419 7420 7421
the MAP_OBTAIN_IMEI service request is sent to the MSC, including only the Invoke Id; the VLR then waits for the response from the MSC; if the IMEI is received in the MAP_OBTAIN_IMEI service response, the macro terminates at the "OK" exit; if the System Failure error is reported in the MAP_OBTAIN_IMEI service response, the "Error" exit is used; if the MSC terminates the dialogue using a MAP_P_ABORT, MAP_U_ABORT, MAP_CLOSE or MAP_NOTICE service indication, the necessary connections are released, and the "Aborted" exit is used for termination of the macro.
2560
3GPP
2561 Release 4
895
3GPP TS 29.002 V4.17.0 (2006-06)
7422 The macro is shown in figure 25.6/5.
Macrodefinition Check_IMEI_MSC
Figure 25.6/1: Check IME I mac ro in the MSC, relaying the IMEI check indication from the V LR t o the MS C and relaying the confi rmation from t he EIR to t he VLR
25.6_1.1(2)
W ait_for_ identity
Wait_for_ IMEI_ Result
Conti nues on page 2
MA P_ CHE CK_ IMEI_ind
From VLR
A_ IDE NTITY_ RES PONS E
A_CM_REL
MA P_ CHE CK_ IMEI_c nf
From EIR
IMEI available
yes
MAP _U_ AB ORT_req
no
A_IDE NTITY_ RE QUES T
MA P_OPE N_ req
To E IR
Error
Check_ Confirmation
Section 25 .2
User Error OK P rovid er Error, Data Error Set UE= Syst em Failure
W ait_f or_ ident ity
MA P_CHE CK_ IME I_req
To E IR
Add IME I to service response for V LR
MA P_ DELIMITER_ req
To E IR
MA P_ CHE CK_ IMEI_rsp
To VLR
Rec eive_ Open_ Cnf
S ect ion 25.1
MA P_ DELIMITER_ req
To VLR
V1
OK
Error
Perf orm_ MA P_V1_ Dialogue
Wait _f or_ IME I_ Result
Set error SY STE M FAILURE
OK
7423
7424
Figure 25.6/1 (sheet 1 of 2): Process Check_IMEI_MSC
2562
3GPP
2563 Release 4
896
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition Check_IMEI_MSC
Figure 25.6/1: Check IME I mac ro in the MSC, relaying the IMEI check indication from the V LR t o the MS C and relaying the confi rmation from t he EIR to t he VLR
25.6_1.2(2)
W ait _for_ IME I_ Result
Continued f rom page 1
A_CM_ REL
MA P_ NOTICE_ ind
MAP _P _ABORT_Ind MAP _U_AB ORT_Ind MAP _CLOSE _Ind from VLR
MAP _P_AB ORT_Ind, MAP _U_A BORT_Ind, MAP _CLOS E_Ind from E IR
MA P_ CLOS E_ ind
From/ to VLR
MA P_U_ A BO RT_req
To E IR
MAP _ NOTICE _ Ind
From EIR
MA P_U_ A BORT_ req
To EIR
A _DIS C
MAP _ CLOS E_ Req
To E IR
MA P_U_ A BORT_ req
To VLR
A _CL_CMD
S et UE = S ystem Fail ure
Error
Error
7425
7426
Figure 25.6/1 (sheet 2 of 2): Process Check_IMEI_MSC
2564
3GPP
2565 Release 4
897
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition Check_IMEI_VLR
Figure 25.6/2: Check IME I mac ro in the V LR, cont aining the request towards the MS C/EIR
25.6_2(1)
MA P_ CHE CK _ IME I_req
To MS C
MA P_ DELIMITER_ req
To MS C
W ait _f or_ IME I_ result
MA P_ CHE CK _ IME I_cnf
From MS C
MAP _ NOTICE _ ind
MAP _U_A BORT_ind MAP _P_AB ORT_ind MAP _CLOS E_ind from MSC
MAP _ CLOS E_ req
no
O& M noti fi cation requi red yes
Aborted
OM_ALARM
To OMC
S ervice grant ed
no
yes
OK
Error
7427
7428
Figure 25.6/2: Process Check_IMEI_VLR
2566
3GPP
2567 Release 4
898
3GPP TS 29.002 V4.17.0 (2006-06)
Process Check_IMEI_EIR
Figure 25.6/3: The proces s in t he EIR to check an IMEI
25.6_3(1)
NULL
Receive_ Open_ind
Section 25. 1
OK E rror W ait
V1 Perform_ MA P_V1_ Dialogue
MA P_ CHE CK_ IME I_in d
MAP _P _A BORT_ind MAP _U_ABOR T_ind MAP _CLOSE_ind
MA P_ NOTICE_ ind
NULL
C heck _ Indic ation
Sec tion 25.2
NULL
MA P_ CLOS E_ req
OK Error Unk nown S tatus W hit e-li st ed, grey-list ed, blac k-listed S et E quipment S tatus Set error UNK NOW N EQUIPMENT NULL
MA P_ CHE CK _ IME I_rsp
MA P_ CLOS E_ req
NULL
7429
7430
Figure 25.6/3: Process Check_IMEI_EIR
2568
3GPP
2569 Release 4
899
3GPP TS 29.002 V4.17.0 (2006-06)
Ma crodefinition Obtain_ IME I_M SC
F ig ure 25. 6/ 4: O bt ain I ME I m acro in t he M S C, receivin g t he O bt ain_IM E I indic a tion fr om the V LR t o the MS C and ret urning th e confirm at io n to the V LR ,
25.6_4(1)
MA P _ O B TA I N_ I ME I_ ind
Fro m V LR
W ait _for_ ident ity
A_ I DE NTITY_ R ESPON SE I ME I av ailable no A_ I DE NTI TY _ RE Q U E S T yes
A _ CM_ RE L
MA P _U _A B O RT _ind, MA P _P _A B O RT_in d, MA P _C LO S E _ind
S et respons e
S et error S Y S TE M F A ILU RE
E rror
W ait _for_ identit y
M AP_ O B T A IN_ IM E I_rs p
To V LR
M AP_ D E LI MIT E R_ r eq
To V LR
OK
7431
7432
Figure 25.6/4: Process Obtain_IMEI_MSC
2570
3GPP
2571 Release 4
900
3GPP TS 29.002 V4.17.0 (2006-06)
Ma crodefinition Obtain_ IME I_VLR
F ig ure 25 .6/ 5: O bt ain I ME I m acro in t he V LR, con trolling the requ es t t owards t he M S C
25.6_5(1)
MA P _ OB TA IN_ IM E I_req
To MS C
MA P _ DE LI MI TE R_ req
To MS C
W ait_ for_ IM E I
MA P _ OB TA IN_ IM E I_ cnf
F rom MS C
MA P _ N OT ICE _ ind
MA P _U _A B O R T_ind, MA P _P _A B O RT_in d, MA P _C LO S E _ind from MS C
yes E rror ?
MA P _ C LO S E _ req
no
OK
E rror
A bort ed
7433
7434
Figure 25.6/5: Process Obtain_IMEI_VLR
2572
3GPP
2573 Release 4
901
3GPP TS 29.002 V4.17.0 (2006-06)
7435
25.6.6 Process Check_IMEI_SGSN
if the MS does not complete successfully the procedure, the "Error" exit of the macro is used; when the IMEI is known, a connection is set up towards the EIR, and a MAP_CHECK_IMEI service request is sent including the IMEI; if the opening of the dialogue fails, a System Failure is set. Otherwise, the SGSN waits for a response from the EIR; if a MAP_CHECK_IMEI service confirm including either: the IMEI and the Equipment Status; or an error;
7436 This process is used by the SGSN to control the check of a mobile equipment's IMEI. The process proceeds as follows: 7437 7438 7439 7440 7441 7442 7443 7444 7445 7446 7447 7448 7449 7450 7451 7452 7453
is received, the SGSN checks whether the response requires that an alarm be generated on the Operation and Maintenance interface. The criteria for such alarms are PLMN operator dependent; the SGSN then checks whether the response from the EIR means that service is granted to the MS. The criteria for granting service depending on the equipment status or errors received in the MAP_CHECK_IMEI service response are also PLMN operator dependent;
If the dialogue with the EIR drops back to version 1, the result or error returned by the EIR is checked. The use of the "Check_Confirmation" macro in the SDL diagram indicates that the checks carried out on the result returned by the EIR in a MAP v1 dialogue are functionally equivalent to those carried out on the parameters of the MAP_CHECK_IMEI confirm received from the EIR in a MAP v2 dialogue.
7454 The process is described in figure 25.6/6.
2574
3GPP
2575 Release 4
902
3GPP TS 29.002 V4.17.0 (2006-06)
Pro c es s Ch e ck_ IM E I_SG S N
F ig u re 2 5.6 /6 : C he c k IM E I p r oc e s s in t he S G S N
2 5 .6 _ 6 .1 ( 2)
I dle
W a it _f or _ IM E I_ R e s u lt
C o nt in ue s on pa g e 2
IM E I c h ec k in g req u es t
F r om r e qu es t in g pro ce s s . S ee G S M 03 .6 0 ye s
MAP_ CH E CK _ IM E I_ c nf
Fro m E IR
IME I a v a ila ble
No M AP _ O P E N _ re q C he c k _ C o n firm a tio n
T o E IR
S ec t io n 2 5. 2
2 P ag e 2
M AP _ C H E C K _ IM E I_r e q
U s e r er ro r T o E IR no
OK
P r ov ide r E r ro r , D ata E r ro r
M AP _ D E L IM IT E R _ re q
O&M no tific at io n re q uired yes
Se t U E = Sy s te m F a ilur e
T o E IR 2 P a ge 2
2 P ag e 2 O M _A L A R M
R ec e ive _ O pe n_ C nf
S e c tion 2 1. 1
To O M C
V1
OK
E rro r S er vic e gra nte d Y es 1 P ag e 2 2 P ag e 2 No
P e rfo rm _ M A P _ V1 _ D ia log u e
W a it_ fo r _ IM E I _ R e su lt
S et e rro r S YS T E M F A IL U R E
2 Page 2
7455
7456
Figure 25.6/6 (sheet 1 of 2): Process Check_IMEI_SGSN
2576
3GPP
2577 Release 4
903
3GPP TS 29.002 V4.17.0 (2006-06)
Pro c es s Ch e ck_ IM E I_SG S N
F ig u re 2 5.6 /6 : C he c k IM E I p r oc e s s in t he S G S N W ait_ fo r _ I M E I_ R es u l t C on tinu ed fro m pag e 1
2 5 .6 _ 6 .2 ( 2)
M A P_ P _ AB O R T _ Ind , M A P _ U _ A BO R T _ In d , M A P _C LO S E _ In d fro m E I R
MAP_ N O T IC E _ In d
Fro m E I R
MAP_ C LO SE _ R eq
1 P ag e 2
2 Page 2
Set U E = S y s te m F ailu r e
IM E I c he c k in g R es po ns e
T o re q ue s tin g p ro c es s . S ee G S M 03 .6 0
IM E I c h ec k in g N e ga tiv e R e s po n s e
T o req u es tin g p r oc e s s . S ee G S M 0 3 .60
I dle
2 P ag e 2
7457
7458
Figure 25.6/6 (sheet 2 of 2): Process Check_IMEI_SGSN
2578
3GPP
2579 Release 4
904
3GPP TS 29.002 V4.17.0 (2006-06)
7459 7460
25.7 Insert Subscriber Data Macros
25.7.1 Macro Insert_Subs_Data_VLR
7461 This macro describes the reception of the InsertSubscriberData service indication. This macro is used by any procedure 7462 that triggers the reception of subscriber data (e.g. Update Location or Restore Data). 7463 If the VLR does not support any basic or supplementary service or the network feature Operator Determined Barring, or 7464 there is a problem with Regional Subscription Data then it reports it to the HLR. 7465 If the entire MSC area is restricted due to regional subscription this is reported to the HLR. 7466 The SDL diagram is shown in figure 25.7/1.
2580
3GPP
2581 Release 4
905
3GPP TS 29.002 V4.17.0 (2006-06)
Ma crodefinition Insert_Subs_Data_VLR
F ig ure 2 5.7 /1 : M a cro to rec e iv e and s to re s ub s c rib er dat a in th e VL R
25.7_1(1)
M A P _I ns e rt _ S u b sc ribe r_ D at a_ in d
P a ram et ers OK Ye s A ll re ce iv ed fe a ture s & s erv ice s s u pp o rte d ? Ye s
No
no
U p d at e s u bs c ribe r d ata f or s u pp ort ed fe a ture
U pd at e S u b s cribe r D a ta
S et pa ram et ers fo r un s u ppo rte d fe atu re s
Se t U E = U n ex p ec te d D ata V a lu e
M S C are a re s tric t ed du e to r egio na l s ub s c ript io n ? Ye s
No
S et M S C A re a R es tric te d
M A P _In s e rt_S u bs c rib e r_ D at a_ R s p M A P _D elim iter_ re q
7467
7468
Figure 25.7/1: Macro Insert_Subs_Data_VLR
2582
3GPP
2583 Release 4
906
3GPP TS 29.002 V4.17.0 (2006-06)
7469
25.7.2 Process Insert_Subs_Data_Stand_Alone_HLR
7470 This process is used by HLR to transfer subscriber data to VLR or to SGSN in a stand alone mode, i.e. in its own 7471 dialogue. This is done whenever a change of subscriber data is performed either by the operator or by the subscriber and 7472 this change has to be reported to VLR or to SGSN. 7473 The process, after opening the dialogue with VLR or with SGSN, sends as many requests of the InsertSubscriberData 7474 service as necessary to transfer the subscriber data. The call to the process "Send_Insert_Subs_Data" (see clause 25.7.4) 7475 is meant to describe two possible behaviours of the HLR when more than one service request has to be sent: 7476 7477
either the HLR handles the requests and the confirmations in parallel; or the HLR sends every request after receiving the confirmation to the previous one.
7478 The macros "Wait_for_Insert_Subs_Data_Cnf" and Wait_for_Insert_GPRS_Subs_Data_Cnf (see clauses 25.7.3 and 7479 25.7.6) are also called in order to handle every single confirmation. 7480 If the result of a primitive received from the VLR or from the SGSN is unsuccessful, the HLR may initiate re-attempts; 7481 the number of repeat attempts and the time in between are HLR operator options, depending on the error returned by the 7482 VLR or by the SGSN. 7483 If certain services required for a subscriber are not supported by the VLR or by the SGSN (e.g. Advice of Charge 7484 Charging Level), this may result in one of the following outcomes: 7485 7486 7487 7488 7489 7490 7491 7492 7493 7494 7495
the HLR stores and sends "Roaming Restriction Due To Unsupported Feature" in a subsequent MAP_INSERT_SUBSCRIBER_DATA service. If "Roaming Restriction Due To Unsupported Feature" is stored in the HLR, the "MSC Area Restricted Flag" shall be set to "restricted". This will prevent MT calls, MT SM and MT USSD from being forwarded to the MSC/VLR. the HLR stores and sends other induced subscriber data (e.g. a specific barring program) in a subsequent MAP_INSERT_SUBSCRIBER_DATA service. This will cause rejection of mobile originated service requests, except emergency calls. the HLR stores and sends "Roaming Restricted In SGSN Due To Unsupported Feature" in a subsequent MAP_INSERT_SUBSCRIBER_DATA service. If "Roaming Restricted In SGSN Due To Unsupported Feature" is stored in the HLR, the "SGSN Area Restricted Flag" shall be set to "restricted". This will prevent MT SM from being forwarded to the SGSN and Network Requested PDP-Context activation.
7496 When the VLR receives regional subscription data (Zone Code List) it may respond with "MSC Area Restricted" in the 7497 MAP_INSERT_SUBSCRIBER_DATA response. In this case the "MSC Area Restricted Flag" shall be set to 7498 "restricted" in the HLR. This will prevent MT calls, MT SM and MT USSD from being forwarded to the MSC/VLR. 7499 7500 7501 7502 7503 7504 7505 7506 7507 7508 7509 7510
When the SGSN receives regional subscription data (Zone Code List) it may respond with "SGSN Area Restricted" in the MAP_INSERT_SUBSCRIBER_DATA response. In this case the "SGSN Area Restricted Flag" shall be set to "restricted" in the HLR. This will prevent MT SM from being forwarded to the SGSN and Network Requested PDPContext activation. If subscriber data for CAMEL Phase 2 or 3 services are sent to a VLR which does not support CAMEL Phase 2 or 3, the service behaviour may be unpredictable or incorrect. The HLR therefore needs to ensure that at the conclusion of a stand alone Insert Subscriber data procedure that 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. 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 3. 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 3 is supported.
7511 A Forwarded-to number in non-international E.164 format shall only be sent from an HLR to a VLR if the VLR 7512 supports CAMEL Phase 2, or a subsequent version of CAMEL.
2584
3GPP
2585 Release 4
907
3GPP TS 29.002 V4.17.0 (2006-06)
7513 7514 7515 7516 7517 7518 7519 7520 7521 7522
If the HLR does not store "Roaming Restriction Due To Unsupported Feature" as a consequence of the stand alone Insert Subscriber Data procedure and the HLR does not receive "MSC Area Restricted" in the MAP_INSERT_SUBSCRIBER_DATA response and "Roaming Restriction Due To Unsupported Feature" has not been stored in the HLR in the course of a previous subscriber data retrieval procedure, the "MSC Area Restricted Flag" in the HLR shall be set to "not restricted". If the HLR does not store "Roaming Restricted In SGSN Due To Unsupported Feature" as a consequence of the stand alone Insert Subscriber Data procedure and the HLR does not receive "SGSN Area Restricted" in the MAP_INSERT_SUBSCRIBER_DATA response and "Roaming Restricted In SGSN Due To Unsupported Feature" has not been stored in the HLR in the course of a previous subscriber data retrieval procedure, the "SGSN Area Restricted Flag" in the HLR shall be set to "not restricted".
7523 The SDL diagram of process between HLR and VLR is shown in figure 25.7/2; 7524 The SDL diagram of process between HLR and SGSN is shown in figure 25.7/5.
2586
3GPP
2587 Release 4
908
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess Insert_Subs_Data_Stand_Alone_HLR
F ig ure 2 5.7 /2 : In d epe n d ent pr oc es s to op en a ne w dia lo gu e a n d t ra n s fe r s u b sc ribe r d at a f ro m H L R to VL R 5 P ag e 2
25.7_2.1(2)
M A P_ O P E N _re q M AP _ IN S E R T _ SU B S C R IB E R _ D A T A _ re q M A P _ D EL IM IT E R _re q
R ec e ive _ O p e n_C n f
F igu re 25 .1 /2
Vr P e rfor m MAP Vr d ia log u e
OK W a it_ F o r_ Ins e rt_ Su bs _ Da ta _C nf R ep la c e _ s e rvic e F ig ure 25 .7 /3
E rro r
E rro r MA P _ U _ A B O R T _re q
A b ort
Se t_ re p la c em e nt_ s erv ic e(s ) no A ll d at a in s e rted y es C o un t:= 0 3 Pa g e 2 All d at a in s e rte d no ye s 1 pa g e 1 , 2
4 P ag e 2
S en d _In s ert _ S ub s _D at a
F igu re 25 .7 /4
2 P ag e 2
C ou n t:= C ou nt+ 1
1 Page 1
7525
7526
Figure 25.7/2 (sheet 1 of 2): Process Insert_Subs_Data_Stand_Alone_HLR
2588
3GPP
2589 Release 4
909
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess Insert_S ubs_Data_Stand_Alone_H LR
F ig ure 25 .7/ 2: I ndependent proces s to op en a n ew dialogue an d trans fer s ubs criber d at a from H LR t o V L R
25.7 _2.2(2)
2 P ag e 1, 2
W ait_F or_ I nsert _S ub s Dat a_ Cnf
Fig ure 25. 7/3
R ep lac e_S erv ice Count := Cou nt -1
OK C ount := C ount -1
E rror
A b ort
M A P _U_ A B OR T_req
S et_ rep lacem ent _ servic e(s)
Count >0 no
y es
1 P age 1
3 page 1
2 P age 2
no
R oam ing_rest rict ion_ due_t o_ unsupp ort ed _feat ure_or_ MS C _area_ res trict ed_received yes
M S C_area_ res trict ed_fla g : = res tric ted
4 P age 1
M A P _CL O S E _ req
R ep eat u pdat ing of V LR yes W ait_for_ repetit ion_ t im er_expiry
no
5 P age 1
7527
7528
Figure 25.7/2 (sheet 2 of 2): Process Insert_Subs_Data_Stand_Alone_HLR
2590
3GPP
2591 Release 4
910
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess Ins ert_G P RS_ Subs_Da ta_Stand_Alone_H LR
F ig u re 2 5.7 / 5: Ind ep e nd en t pro c e ss to o p en a n ew d ialog u e a nd t ran s fer G P R S s u bs c riber d a ta fro m H L R to S G S N 5
25.7 _5.1(2)
M A P _ O P E N_ r eq M A P _ IN S E R T _ S U B S C R IB E R _ D A T A _ req M A P _ D E L IM IT E R _re q
R ec e iv e_ O p en_ C n f
F ig u re 2 5 .1 /2
OK W a it_ F o r_ In s ert_ G P R S _S ub s _ D ata _ C n f Ok F ig ure 25 .7 /7
V r,E rro r
E rro r M A P _ U_ A B O R T _ req
A b or t
Se t_ re p lac e m en t_ se rv ic e (s) 4 no A ll da ta in s erte d ye s C o un t: =0 3 Pa g e 2 A ll d a ta in s erted no yes 1 p a ge 1
S en d _In s ert_ S u bs _ D ata
F ig u re 2 5 .7 /4
2 P ag e 2
C o u nt: = C o un t+ 1
1 P a ge 1
7529
7530
Figure 25.7/5 (sheet 1 of 2): Process Insert_GPRS_Subs_Data_Stand_Alone_HLR
2592
3GPP
2593 Release 4
911
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess Ins ert_G P RS_ Subs_Da ta_Stand_Alone_H LR
F ig u re 2 5.7 / 5: Ind ep e nd en t pro c e ss to o p en a n ew d ialog u e a nd t ran s fer G P R S s u bs c riber d a ta fro m H L R to S G S N
25.7 _5.2(2)
2 P a ge 1
W a it_ F o r_ In s er t_ G P R S _S u b s D ata _ C n f
F ig u re 2 5 .7 /7
R ep la c e_ S ervic e C ou n t:= C o u n t-1
OK C o u nt := C o un t-1
E rro r M A P _ U_ A B O R T _ req
A b or t
S et_ rep la c em en t_ s ervic e(s )
C o un t >0 no 3 pa g e 1
ye s
4 2 P a ge 2
1 P ag e 1 no
R o am in g _re st ric ted _ In _S G S N_ d u e_t o _u n s up p ort ed _f eat u re _o r _ S G S N _ a re a_ res tric t ed _re c eiv ed ye s SG S N _a re a_ re s tric ted _ fla g := res tric te d
M A P _ C LO S E _ re q
Re pe at up d atin g o f SGSN ye s W a it_ fo r_ rep e tition _ t im er_ exp iry
no
7531
7532
Figure 25.7/5 (sheet 2 of 2): Process Insert_GPRS_Subs_Data_Stand_Alone_HLR
2594
3GPP
2595 Release 4
912
3GPP TS 29.002 V4.17.0 (2006-06)
7533
25.7.3 Macro Wait_for_Insert_Subs_Data_Cnf
7534 This macro is used by any process or macro that describes the handling of the reception of the Insert_Subscriber_Data 7535 service in HLR that is coming from VLR (e.g. Update Location or Restore Data). 7536 If the VLR reports the non-support of some basic or supplementary service or the network feature Operator Determined 7537 Barring then three actions are possible: 7538 7539 7540
to ignore the information received; to replace the not supported service; or to perform any other internal action.
7541 The SDL diagram is shown in figure 25.7/3.
2596
3GPP
2597 Release 4
913
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefin ition W ait_For_Insert_S ub s_Data_ Cnf
F ig ure 25 .7/ 3: Mac ro t o recieve confirmat ion or errorind ication for M A P _I NS E R T_S UB S CRI B E R _DA TA
25.7_3(1)
W ait_ For_ I S D_ Cnf
MA P _I N S E RT_ S UB S C RI B E R_ DA TA _ cnf
MA P _ U_A B OR T_ind, MA P _ P _A B O R T_ind, M A P _CLO S E _ ind
MA P _ NO TI CE _ind
Chec k_ Confirm at ion
Figure 2 5. 2/ 2
MA P _ CL O S E _ req
OK
Us er error, Data er ror
P rovid er error
E rror
A bort
S ervic e u nsu pp ort ed in V LR? No
Yes
Yes
Ig nore it ? No
Replac e service in V LR ? No
Yes
HLR in ternal act ion
R eplace S ervice
OK
7542
7543
Figure 25.7/3: Macro Wait_for_Insert_Subs_Data_Cnf
2598
3GPP
2599 Release 4
914
3GPP TS 29.002 V4.17.0 (2006-06)
7544
25.7.4 Process Send_Insert_Subs_Data
7545 This process is used by any process or macro where the Insert_Subscriber_Data request is sent to VLR or to SGSN. 7546 The SDL diagram is shown in figure 25.7/4.
Pro ces s Sen d_Insert_Subs_D ata
F igure 25 .7/ 4: I ndependent proces s to s end a com ponen t of s ubsc riber dat a from H LR to V LR
25.7_4(1)
MA P _IN S E RT_ S UB S C RI B E R_D A TA _req MA P _ DE LI MI TE R_req
7547
7548
Figure 25.7/4: Process Send_Insert_Subs_Data
7549
25.7.5 Macro Insert_Subs_Data_SGSN
7550 This macro describes the reception of the InsertSubscriberData service indication. This macro is used by any procedure 7551 that triggers the reception of subscriber data (e.g. Update GPRS Location ). 7552 If the SGSN does not support any basic or the network feature Operator Determined Barring, or there is a problem with 7553 Regional Subscription Data then it reports it to the HLR. 7554 If the entire SGSN area is restricted due to regional subscription this is reported to the HLR. 7555 The SDL diagram is shown in figure 25.7/6.
2600
3GPP
2601 Release 4
915
3GPP TS 29.002 V4.17.0 (2006-06)
Ma crodefinition Insert_Subs_Data_SGSN
F ig ure 2 5.7 /6 : M a cro to rec e iv e a n d s t ore s ub s c r ib er d at a in th e S G S N
25.7_6(1)
MA P _I ns e rt_ Su b sc ribe r_ D at a_ in d
P a ra m et ers OK Y es A ll re ce iv ed fe a ture s & s erv ic es s u pp o r ted ? Y es no
No
U pd at e su b s cribe r d at a f or s u p por t ed fe a ture
U pd a te S u b s cribe r D a ta
S et p ara m e ters fo r un s u pp orte d fe a ture s
S et U E = U n e xp ec te d D at a V a lu e
SG S N a rea r es tric te d du e to re gion al s u bs c riptio n ? Y es Set SGSN A re a R es tric te d
No
M A P _In s e rt_S u bs c ribe r_D at a_ R s p M A P _D elimite r_ req
7556
7557
Figure 25.7/6: Macro Insert_Subs_Data_SGSN
2602
3GPP
2603 Release 4
916
3GPP TS 29.002 V4.17.0 (2006-06)
7558
25.7.6 Macro Wait_for_Insert_GPRS_Subs_Data_Cnf
7559 This macro is used by any process or macro that describes the handling of the reception of the Insert_Subscriber_Data 7560 service in HLR that is coming from SGSN (e.g. Update GPRS Location). 7561 If the SGSN reports the non-support of some basic or the network feature Operator Determined Barring then three 7562 actions are possible: 7563 7564 7565
to ignore the information received; to replace the not supported service; or to perform any other internal action.
7566 The SDL diagram is shown in figure 25.7/7.
2604
3GPP
2605 Release 4
917
3GPP TS 29.002 V4.17.0 (2006-06)
Macro definition W ait_For_Insert_GPRS_Subs_Data_Cnf
F ig ure 25 .7 /7: M a cro to rec ie ve c o nf irm at io n or e rro r in dic at io n f or M A P _ IN SE R T _S U B SC R I B ER _ D A T A f r om S G S N
25.7_7(1)
W a it _F o r_ IS D _ C nf
M A P _ IN S E R T _ S U B SC R I BE R _ D A T A _c n f
M A P _ U _ AB O R T _ in d , M A P _ P_ A BO R T _ind , M A P _ C L O SE _ in d
M AP_ N O T IC E _in d
C hec k _ C on firm a tio n OK
F ig u re 2 5. 2/ 2
M AP_ C LO S E_ re q
U s e r e rro r, D a ta err o r E rro r
P ro v id er error
A bo rt
S erv ic e un s u pp orte d in S G S N ? No Ye s
Y es
Ig n ore it?
No
R e plac e s erv ic e in S G S N ? No H LR in tern al a c tio n
Y es
Re p la c e S e rvic e
OK
7567
7568
Figure 25.7/7: Macro Wait_for_Insert_GPRS_Subs_Data_Cnf
2606
3GPP
2607 Release 4
918
3GPP TS 29.002 V4.17.0 (2006-06)
7569 7570
25.8 Request IMSI Macros
25.8.1 Macro Obtain_IMSI_MSC
7571 This macro describes the handling of the request received from the VLR to provide the IMSI of a subscriber (e.g. at 7572 Location Updating). 7573 The SDL diagram is shown in figure 25.8/1.
Ma crodefinition Obtain_ IMSI_M SC
F igure 25.8 /1: Macr o to relay an I M S I req ues t from t he V L R to t he MS an d ret urn t he resp on se to t he V L R
25.8_1(1)
MA P _ P R O V IDE _ I MS I_ind
from V LR
A _I MS I _R eq
W ait _F or_ IMS I
A _IM S I_ cnf
A _RE LE A S E
MA P _P _A B O RT_in d, MA P _U _A B O R T_ind, MA P _C LO S E _ind
S et UE = A bsent S u bsc riber
E rror
MA P _P R O V I DE _ IM S I _rs p
OK
7574
7575
Figure 25.8/1: Macro Obtain_IMSI_MSC
7576
25.8.2 Macro Obtain_IMSI_VLR
7577 This macro describes the way VLR requests the MSC the IMSI of a subscriber (e.g. at Location Updating). 7578 The SDL diagram is shown in figure 25.8/2.
2608
3GPP
2609 Release 4
919
3GPP TS 29.002 V4.17.0 (2006-06)
Ma crodefinition Obtain_ IMS I_VLR
F ig ure 25. 8/ 2: Macr o to obtain the IM S I from t he M S v ia the M S C
25.8_2(1)
MA P _ P RO V I DE _ IMS I _req MA P _ DE LI M I TE R_req
W ait_ For_ I MS I
MA P _P R O V I DE _ IM S I_ cnf
M AP_ NO TIC E _ind
MA P _U _A B O R T_ind , MA P _P _A B O RT _in d, MA P _C LO S E _ ind
M AP_ C LO S E _ req
Chec k_ Confirm at ion
Figure 2 5. 2/ 2
A borted
OK
U ser error, D at a error
P rov id er error
OK
E rror
A bort ed
7579
7580
Figure 25.8/2: Macro Obtain_IMSI_VLR
2610
3GPP
2611 Release 4
920
3GPP TS 29.002 V4.17.0 (2006-06)
7581 7582
25.9 Tracing macros
25.9.1 Macro Trace_Subscriber_Activity_MSC
7583 The Trace_Subscriber_Activity_MSC is invoked in the MSC, when the MSC receives the 7584 MAP_TRACE_SUBSCRIBER_ACTIVITY indication from the VLR. The data of the primitive is checked and the 7585 tracing in the MSC is started if the content includes no errors. No response is returned to the VLR. 7586 The Trace_Subscriber_Activity_MSC macro is described in the figure 25.9/1.
Macrodefin ition Trace_S ubscriber_ Activity_MSC
F igure 25.9 /1: The S ubsc riber t rac ing mac ro in t he MS C
25.9_1(1)
MA P _TRA CE _ S U B S CR IB E R_ A CT IV I TY _ind
Ch ec k_ In dic ation
OK 'S t art act ivit y t racing'
E rror
7587
7588
Figure 25.9/1: Macro Trace_Subscriber_Activity_MSC
7589
25.9.2 Macro Trace_Subscriber_Activity_VLR
7590 The macro Trace_Subscriber_Activity_VLR is invoked, if the subscriber activity is detected by the VLR and the tracing 7591 is active. The VLR sends MAP_TRACE_SUBSCRIBER_ACTIVITY request to the MSC. No answer is awaited from 7592 the MSC. 7593 The Trace_Subscriber_Activity_VLR macro is shown in the figure 25.9/2.
2612
3GPP
2613 Release 4
921
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefin ition Trace_S ubscriber_ Activity_VL R
F igure 25 .9/ 2: The subs c riber tracin g m a cro in t he V L R
25.9_2(1)
no
'S ubs criber Trac ing = A c tive' yes
MA P _TRA C E _S U B S CR IB E R _A CTI V I TY _req
7594
7595
Figure 25.9/2: Macro Trace_Subscriber_Activity_VLR
7596
25.9.3 Macro Activate_Tracing_VLR
7597 The Activate_Tracing_VLR macro is invoked, when the MAP_ACTIVATE_TRACE_MODE indication is received 7598 from the HLR. The primitive is processed in the VLR as follows: 7599 7600 7601 7602 7603
if the data contains errors, a data missing or unexpected data value indication is returned to the HLR; if the tracing is not supported, a facility not supported indication is returned to the HLR; if the tracing buffer does not have any space left for the data, a tracing buffer full indication is returned to the HLR; if no errors are detected, the tracing is set active and a positive acknowledgement is returned to the HLR.
7604 The Activate_Tracing_VLR macro is described in the figure 25.9/3.
2614
3GPP
2615 Release 4
922
3GPP TS 29.002 V4.17.0 (2006-06)
Ma crodefinition Activate_Tracin g_VLR
F ig ure 25. 9/ 3: The activat e t rac e mo de m acro in t he V LR
25.9_3(1)
M AP_ _A CTI V A TE _ _ TRA C E _ _M O DE _ind
Che c k_ In dic ation E rror
OK 'S ubs criber kn own ' yes no
'Tracing s upport ed' yes
no
'S E T UE = UN ID E NTI FI E D S UB S CRI B E R '
'T rac ing buff er fu ll' no 'S et S ub sc rib er Trac ing = A c t iv e'
yes
'S E T U E = FA CI LI TY N O T S UP P O RT E D'
'S E T UE = TR A CIN G B UF FE R F ULL'
M A P _A CT IV A TE _ TRA CE _MO D E _rsp, MA P _ DE LI MI TE R_req
7605
7606
Figure 25.9/3: Macro Activate_Tracing_VLR
2616
3GPP
2617 Release 4
923
3GPP TS 29.002 V4.17.0 (2006-06)
7607
25.9.4 Macro Control_Tracing_HLR
7608 The Control_Tracing_HLR macro may be invoked in the HLR, if subscriber related activity is detected. If the tracing is 7609 active in the HLR and not active in the VLR or in the SGSN, the MAP_ACTIVATE_TRACE_MODE request is sent to 7610 the VLR or to the SGSN. 7611 The MAP_ACTIVATE_TRACE_MODE confirmation from the VLR or from the SGSN is processed as follows: 7612 7613
if the primitive contains a successful acknowledgement, the tracing in VLR or in the SGSN is set active; if the primitive contains errors, the tracing in VLR or in SGSN is set to deactive.
7614 The Control_Tracing_HLR macro between HLR and VLR is shown in the figure 25.9/4. 7615 The Control_Tracing_HLR_with_SGSN macro between HLR and SGSN is shown in the figure 25.9/5.
2618
3GPP
2619 Release 4
924
3GPP TS 29.002 V4.17.0 (2006-06)
Ma crodefinition Co ntrol_Tracing_H LR
F ig ure 25. 9/ 4: The subs c riber tracing act ivation m ac ro in the HLR
25.9_4(1)
no
S ubs criber trac ing = ac tive in HLR yes
y es
S ubs criber trac ing = active in V LR no
no
S ub sc rib er in HP L M N area yes
OK
MA P _ A CTI V A TE _T RA CE _M O DE _ Req M A P _DE L IM I TE R_ Req
W A I T_FO R _ A TM_ RE S U L T
MA P _ A C TIV A TE _TR A CE _M O DE _C nf
MA P _NO TI CE _ I nd
MA P _U _A B O R T_In d, MA P _P _A B O RT _I nd, MA P _C LO S E _I nd
M A P _CL OS E _ R eq Chec k_ Confirm at ion
Figure 2 5.2/ 2
E rror
OK
Us er error, Dat a error S et S ub sc rib er Trac ing = I nact ive in V LR
P rov id er error
S et S ubs criber Trac ing = A ct ive in V LR
S et S ubs c riber Tracing = I nac t iv e in V LR
OK
E rro r
7616
7617
Figure 25.9/4: Macro Control_Tracing_HLR
2620
3GPP
2621 Release 4
925
3GPP TS 29.002 V4.17.0 (2006-06)
Ma crodefinition Control_Tracing_HLR_w ith_S GS N
F ig u re 2 5.9 /5 : T h e s ub s c rib er tr ac in g a c tiv a tio n m ac ro in th e H L R
25.9_5(1)
no
S u bs c ribe r t ra c ing = a c tive in H L R ye s
y es
S u bs c rib e r trac in g = ac ti v e in S G S N no
no
S u bs c ribe r in H P LM N a re a ye s
OK
M AP _ A C T IV A T E_ T R A C E _ M O D E _ R e q M A P _D E LIM IT E R _ R e q
W A IT _ F O R _ A TM _ R ES U L T
M A P _N O T IC E _ M A P _ A C T I VA T E _ T R AC E _ M O D E _C nf In d
M A P _ U _ A BO R T _ In d, M A P_ P _A B O R T _I nd , M A P _C LO S E _ Ind
M A P _C LO S E _ R eq C hec k _ C onf irm a tio n F ig u re 2 1. 2/2
OK
U se r e rro r, D a ta erro r S e t S u bs c rib e r T ra c in g = In ac tiv e in S G S N
P ro v id e r erro r
E rro r
S e t S ub s c rib er T rac ing = A c tiv e i n S G S N
S e t S ub s c rib er T rac i ng = In ac ti v e in S G S N
OK
E rro r
7618
7619
Figure 25.9/5: Macro Control_Tracing_HLR_with_SGSN
2622
3GPP
2623 Release 4
926
3GPP TS 29.002 V4.17.0 (2006-06)
7620
25.9.5 Macro Trace_Subscriber_Activity_SGSN
7621 The macro Trace_Subscriber_Activity_SGSN is invoked, if the subscriber activity is detected by the SGSN and the 7622 tracing is active. 7623 The Trace_Subscriber_Activity_SGSN macro is shown in the figure 25.9/6.
Macrodefinition Trace_Subscriber_Activity_ SGSN
F ig ure 25 .9 /6: T h e su b s crib er tra c in g ma c ro in th e SG SN
25.9_6(1)
no
'S u b s cribe r T rac ing = Ac tiv e ' y es
S ta rt ac tiv ity tra c ing
7624
7625
Figure 25.9/6: Macro Trace_Subscriber_Activity_SGSN
7626
25.9.6 Macro Activate_Tracing_SGSN
7627 The Activate_Tracing_SGSN macro is invoked, when the MAP_ACTIVATE_TRACE_MODE indication is received 7628 from the HLR. The primitive is processed in the SGSN as follows: 7629 7630 7631 7632 7633
if the data contains errors, a data missing or unexpected data value indication is returned to the HLR; if the tracing is not supported, a facility not supported indication is returned to the HLR; if the tracing buffer does not have any space left for the data, a tracing buffer full indication is returned to the HLR; if no errors are detected, the tracing is set active and a positive acknowledgement is returned to the HLR.
7634 The Activate_Tracing_SGSN macro is described in the figure 25.9/7.
2624
3GPP
2625 Release 4
927
3GPP TS 29.002 V4.17.0 (2006-06)
Macrodefinition Ac tivate_Tracing_ SGSN
F ig u re 2 5.9 /7 : T h e ac t iv at e trac e m o d e m a c ro in th e S G S N .
25.9_7(1)
M AP _ _A C T IV A T E _ _T R A C E _ _M O D E _ in d
C he c k _ I nd ic a tio n
E rro r
OK 'S ub s c ribe r k no w n ' y es 'T ra c in g su p po rte d' y es 'T ra c in g bu ffe r fu ll' no 'S et S ub s c rib er T rac ing = A c tiv e ' ye s no no
'S E T U E = U N ID E N T IF I E D S U B S C R IB E R '
'S E T U E = F A C IL IT Y N O T SU P P O R T E D '
' S ET U E = T R A C IN G B U FFE R F U L L'
M A P _ A C T I VA T E _ T R AC E _M O D E _rs p , M A P _D E LIM I T E R _ re q
7635
7636
Figure 25.9/7: Macro Activate_Tracing_SGSN
2626
3GPP
2627 Release 4
928
3GPP TS 29.002 V4.17.0 (2006-06)
7637 7638
25.10 Short Message Alert procedures
25.10.1 Subscriber_Present_VLR process
7639 The Subscriber_Present_VLR process is invoked by the VLR, when the mobile subscriber becomes active and the 7640 MNRF flag is set. The general description of the short message alert procedures is in the clause 23.4. 7641 The VLR sends the MAP_READY_FOR_SM request to the HLR and waits for the HLR to answer. When receiving the 7642 answer, the VLR will act as follows: 7643 7644
the MNRF flag is cleared if the procedure is successful; the MNRF flag is not cleared if the procedure is not successful.
7645 The Subscriber_Present_VLR process is shown in the figure 25.10/1.
2628
3GPP
2629 Release 4
929
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess Sub scriber_Present_VLR
F ig ure 25. 10/ 1: The short m ess ag e alert proc ess in th e V LR for mobile pres ent sit uation
25.1 0_1(1)
no
MN RF set yes
MA P _O P E N _req MA P _RE A DY _FO R _S M_req MA P _DE LI MI TE R _req
R ec eiv e_ O pen_C nf
F ig ure 25. 1/2
E rr or
V1
OK
W FRE S P O NS E
P erf orm _ MA P _V 1_ Dialog ue
MA P _RE A DY _FO R _S M_rs p
MA P _U _A B O R T_ ind MA P _P _A B O RT_ind MA P _C LO S E _ind
E rror
yes
no
Clear MN RF
7646
7647
Figure 25.10/1: Process Subscriber_Present_VLR
2630
3GPP
2631 Release 4
930
3GPP TS 29.002 V4.17.0 (2006-06)
7648
25.10.2 Macro Alert_Service_Centre_HLR
7649 The Alert_Service_Centre_HLR macro is initiated when the HLR notices that the Service Centre(s) shall be alerted. 7650 The macro starts process Alert_Service_Centre_HLR for every SC address in the MWD list. 7651 7652 7653 7654
In the process Alert_Service_Centre_HLR the HLR sends MAP_ALERT_SERVICE_CENTRE request to the appropriate IWMSC. The MWD entry is deleted when the positive acknowledgement is received from the IWMSC. The unsuccessful alert may be repeated. The MWD entry should be purged in the unsuccessful case, at least when a suitable time period has expired.
7655 The Alert_Service_Centre_HLR macro is shown in the figure 25.10/2 and the Alert_Service_Centre_HLR process is 7656 shown in the figure 25.10/3.
Macrodefin ition Ale rt_Service_C entre _H LR
F igure 25.10/2 : The short m ess age alert m acro in t he H LR
25.1 0_2(1)
A ll MW D ent ries not iced ? yes
no
A lert _S ervic e_ Cent re_ HLR
7657
7658
Figure 25.10/2: Macro Alert_Service_Centre_HLR
2632
3GPP
2633 Release 4
931
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess Ale rt_Serv ice_C entre_H LR
F ig ure 25 .10/ 3: The short m ess ag e alert process in t he H LR
22.1 0_3(1)
MA P _ O P E N _req M A P _A LE R T_S E R V IC E _CE N TRE _req MA P _ DE LI MI TE R _req
Rec eiv e_ O pen_C nf
Fig ure 25. 1/2
E rror
OK W FA LE R TRE S P O NS E
V1 P erform_ MA P _V 1_ D ialogue
NU LL
MA P _A LE RT_ S E RV I CE _ CE N TRE _ cnf
M AP_ N O TI CE _ ind
MA P _ U_A B O R T_ind MA P _ P _A B O RT_ ind MA P _CLO S E _ ind
E rror ?
yes
M AP_ C LO S E _ re q
no
Rem ove S C address ? yes
no
Rem ov e S C addres s
Rep eat ?
yes
no W a it for repeat tim er expiring
7659
7660
Figure 25.10/3: Process Alert_Service_Centre_HLR
2634
3GPP
2635 Release 4
932
3GPP TS 29.002 V4.17.0 (2006-06)
7661
25.10.3 The Mobile Subscriber is present
7662 When receiving Page response, Attach request or Routing area update request messages (3GPP TS 24.008 [35]), while 7663 the MS not reachable for GPRS (MNRG) flag is set, the SGSN will send the MAP_READY_FOR_SM request towards 7664 the HLR. The Alert Reason is set to indicate that the mobile subscriber is present for GPRS. 7665 When receiving the answer, the SGSN will act as follows: 7666 7667
MNRG is cleared if the procedure is successful MNRG is not cleared if the procedure is not successful
7668 The Subscriber_Present_SGSN process is shown in the figure 25.10/4.
2636
3GPP
2637 Release 4
933
3GPP TS 29.002 V4.17.0 (2006-06)
Pro cess Sub scriber_Present_SG SN
F ig u re 2 5.1 0 /4 : T he s ho rt m e s s age a lert p ro c es s in t he S G S N fo r m o bile p res e nt s itu at ion
25.1 0_4(1)
no
M N RG se t ye s M A P _ O P E N _ re q M A P _R E A D Y _ F O R _ S M_ re q M A P _ D E L IM IT E R _ req
R e c eive_ O p en _ C n f
F ig ure 2 5.1 /2
E rro r, V r
OK W FR ESPON SE
M A P _ R E A D Y _F O R _ S M_ rs p
M A P _U _ A B O R T _ in d M A P _P _ A B O RT _in d M A P _C L O S E _ in d
yes E rro r no
C le ar M N R G
7669
7670
Figure 25.10/4: Process Subscriber_Present_SGSN
2638
3GPP
2639 Release 4
934
3GPP TS 29.002 V4.17.0 (2006-06)
7671 7672
Annex A (informative): Cross-reference for abstract syntaxes of MAP
7673 Annex A is not part of the standard, it is included for information purposes only. 7674 For every ASN.1 item such as identifier, type-reference or value-reference the cross-reference allows to locate all 7675 occurrences by means of module-name and line numbers. For that purpose line numbers are printed at the left margin in 7676 front of each ASN.1 source line starting with 1 for every module. 7677 The items are sorted alphabetically in the cross-reference in a case-insensitive manner. Occurrences of an item are its 7678 definition and all its usages such as in exports, imports or within a type or value assignment. 7679 For every item additional information is provided such as kind of item (identifier, value reference, type reference), and 7680 tag, associated type and value if applicable. 7681 The cross-reference for a root module includes all modules referred to directly or indirectly via imports. The cross7682 references for the root modules MAP-Protocol/TCAPMessages and MAP-DialoguePDU are included.
7683 7684 7685 7686 7687 7688 7689 7690 7691 7692 7693 7694 7695 7696 7697 7698 7699 7700 7701 7702 7703 7704 7705 7706 7707 7708 7709 7710 7711 7712 7713 7714 7715 7716 7717 7718 7719 7720 7721 7722 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732 7733 7734 7735 7736
TAG R6.0
Cross Reference Listing for MAP-Protocol
2006-06-08 12:10:15 PAGE 1
&extensionId............................identifier of Fieldspec DEFINED in MAP-ExtensionDataTypes : 25 USED in MAP-ExtensionDataTypes : 47 &ExtensionType..........................identifier of Fieldspec DEFINED in MAP-ExtensionDataTypes : 24 USED in MAP-ExtensionDataTypes : 49 abort...................................identifier of [APPLICATION 7] IMPLICIT Abort DEFINED in TCAPMessages : 56 Abort...................................type reference SEQUENCE DEFINED in TCAPMessages : 74 USED in TCAPMessages : 56 absentSubscriber........................value reference AbsentSubscriber, CHOICE VALUE DEFINED in MAP-Protocol : 378 AbsentSubscriber........................type reference ERROR DEFINED in MAP-Errors : 280 USED in MAP-Protocol : 136 378 USED in MAP-MobileServiceOpera : 93 441 USED in MAP-CallHandlingOperat : 40 96 115 188 USED in MAP-SupplementaryServi : 50 197 211 USED in MAP-LocationServiceOpe : 28 63 79 USED in MAP-Errors : 48 absentSubscriber........................identifier of Named Number, 1 DEFINED in MAP-SM-DataTypes : 169 absentSubscriberDiagnosticSM............identifier of [0] AbsentSubscriberDiagnosticSM DEFINED in MAP-SM-DataTypes : 148 absentSubscriberDiagnosticSM............identifier of AbsentSubscriberDiagnosticSM DEFINED in MAP-SM-DataTypes : 188 absentSubscriberDiagnosticSM............identifier of AbsentSubscriberDiagnosticSM DEFINED in MAP-ER-DataTypes : 158 AbsentSubscriberDiagnosticSM............type reference INTEGER DEFINED in MAP-ER-DataTypes : 168 USED in MAP-MS-DataTypes : 199 1659 USED in MAP-SM-DataTypes : 41 148 161 188 189 USED in MAP-ER-DataTypes : 43 158 163 absentSubscriberParam...................identifier of AbsentSubscriberParam DEFINED in MAP-Errors : 282 AbsentSubscriberParam...................type reference SEQUENCE
2640
3GPP
2641 Release 4
7737 7738 7739 7740 7741 7742 7743 7744 7745 7746 7747 7748 7749 7750 7751 7752 7753 7754 7755 7756 7757 7758 7759 7760 7761 7762 7763 7764 7765 7766 7767
935
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-ER-DataTypes : 246 USED in MAP-Errors : 125 282 USED in MAP-ER-DataTypes : 34 absentSubscriberReason..................identifier of [0] AbsentSubscriberReason DEFINED in MAP-ER-DataTypes : 249 AbsentSubscriberReason..................type reference ENUMERATED DEFINED in MAP-ER-DataTypes : 251 USED in MAP-ER-DataTypes : 249 absentsubscriberSM......................value reference AbsentSubscriberSM, CHOICE VALUE DEFINED in MAP-Protocol : 424 AbsentSubscriberSM......................type reference ERROR DEFINED in MAP-Errors : 415 USED in MAP-Protocol : 157 424 USED in MAP-ShortMessageServic : 40 79 109 USED in MAP-Errors : 80 absentSubscriberSM-Param................identifier of AbsentSubscriberSM-Param DEFINED in MAP-Errors : 417 AbsentSubscriberSM-Param................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 157 USED in MAP-Errors : 135 417 USED in MAP-ER-DataTypes : 42 accepted................................identifier of Named Number, 0 DEFINED in MAP-CH-DataTypes : 401
2642
3GPP
2643 Release 4
7768 7769 7770 7771 7772 7773 7774 7775 7776 7777 7778 7779 7780 7781 7782 7783 7784 7785 7786 7787 7788 7789 7790 7791 7792 7793 7794 7795 7796 7797 7798 7799 7800 7801 7802 7803 7804 7805 7806 7807 7808 7809 7810 7811 7812 7813 7814 7815 7816 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7827 7828 7829 7830 7831 7832 7833 7834 7835 7836 7837 7838 7839 7840 7841 7842 7843 7844
936
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 2
accessNetworkProtocolId.................identifier of AccessNetworkProtocolId DEFINED in MAP-CommonDataTypes : 242 AccessNetworkProtocolId.................type reference ENUMERATED DEFINED in MAP-CommonDataTypes : 258 USED in MAP-CommonDataTypes : 242 AccessNetworkSignalInfo.................type reference SEQUENCE DEFINED in MAP-CommonDataTypes : 241 USED in MAP-MS-DataTypes : 168 445 504 558 605 611 616 630 USED in MAP-CommonDataTypes : 23 accessOutsideLSAsAllowed................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 896 accessOutsideLSAsRestricted.............identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 897 accessType..............................identifier of AccessType DEFINED in MAP-MS-DataTypes : 385 AccessType..............................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 390 USED in MAP-MS-DataTypes : 385 activate................................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 1965 activateDeferredLocation................identifier of Named Number, 3 DEFINED in MAP-LCS-DataTypes : 119 activateSS..............................value reference ActivateSS, CHOICE VALUE DEFINED in MAP-Protocol : 249 ActivateSS..............................type reference OPERATION DEFINED in MAP-SupplementaryServi : 121 USED in MAP-Protocol : 71 249 USED in MAP-SupplementaryServi : 15 activateTraceMode.......................value reference ActivateTraceMode, CHOICE VALUE DEFINED in MAP-Protocol : 226 ActivateTraceMode.......................type reference OPERATION DEFINED in MAP-OperationAndMainte : 50 USED in MAP-Protocol : 46 226 USED in MAP-OperationAndMainte : 13 activateTraceModeArg....................identifier of ActivateTraceModeArg DEFINED in MAP-OperationAndMainte : 52 ActivateTraceModeArg....................type reference SEQUENCE DEFINED in MAP-OM-DataTypes : 36 USED in MAP-OperationAndMainte : 34 52 USED in MAP-OM-DataTypes : 14 activateTraceModeRes....................identifier of ActivateTraceModeRes DEFINED in MAP-OperationAndMainte : 54 ActivateTraceModeRes....................type reference SEQUENCE DEFINED in MAP-OM-DataTypes : 50 USED in MAP-OperationAndMainte : 35 54 USED in MAP-OM-DataTypes : 15 active..................................identifier of Named Number, 2 DEFINED in MAP-SS-DataTypes : 288 additionalAbsentSubscriberDiagnosticSM..identifier of [5] AbsentSubscriberDiagnosticSM DEFINED in MAP-SM-DataTypes : 161 additionalAbsentSubscriberDiagnosticSM..identifier of [0] AbsentSubscriberDiagnosticSM DEFINED in MAP-SM-DataTypes : 189 additionalAbsentSubscriberDiagnosticSM..identifier of [0] AbsentSubscriberDiagnosticSM DEFINED in MAP-ER-DataTypes : 163
2644
3GPP
2645 Release 4
7845 7846 7847 7848 7849 7850 7851
937
3GPP TS 29.002 V4.17.0 (2006-06)
additionalSignalInfo....................identifier of [17] Ext-ExternalSignalInfo DEFINED in MAP-CH-DataTypes : 113 additionalSignalInfo....................identifier of [14] Ext-ExternalSignalInfo DEFINED in MAP-CH-DataTypes : 214 additionalSM-DeliveryOutcome............identifier of [4] SM-DeliveryOutcome
2646
3GPP
2647 Release 4
7852 7853 7854 7855 7856 7857 7858 7859 7860 7861 7862 7863 7864 7865 7866 7867 7868 7869 7870 7871 7872 7873 7874 7875 7876 7877 7878 7879 7880 7881 7882 7883 7884 7885 7886 7887 7888 7889 7890 7891 7892 7893 7894 7895 7896 7897 7898 7899 7900 7901 7902 7903 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7915 7916 7917 7918 7919 7920 7921 7922 7923 7924 7925 7926 7927 7928
938
Cross Reference Listing for MAP-Protocol : 158
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 3
DEFINED in MAP-SM-DataTypes
additional-Number.......................identifier of [6] Additional-Number DEFINED in MAP-SM-DataTypes : 94 Additional-Number.......................type reference CHOICE DEFINED in MAP-SM-DataTypes : 98 USED in MAP-SM-DataTypes : 28 94 USED in MAP-LCS-DataTypes : 58 85 additional-Number.......................identifier of [3] Additional-Number DEFINED in MAP-LCS-DataTypes : 85 AddressString...........................type reference OCTET STRING DEFINED in MAP-CommonDataTypes : 100 USED in MAP-MS-DataTypes : 164 1939 USED in MAP-CommonDataTypes : 16 144 150 379 USED in MAP-OM-DataTypes : 21 40 USED in MAP-SS-DataTypes : 44 75 301 USED in MAP-SM-DataTypes : 32 56 136 141 146 180 USED in MAP-LCS-DataTypes : 28 135 Add-GeographicalInformation.............type reference OCTET STRING DEFINED in MAP-LCS-DataTypes : 294 USED in MAP-LCS-DataTypes : 24 220 328 add-LocationEstimate....................identifier of [2] Add-GeographicalInformation DEFINED in MAP-LCS-DataTypes : 220 add-LocationEstimate....................identifier of [8] Add-GeographicalInformation DEFINED in MAP-LCS-DataTypes : 328 AgeIndicator............................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 235 USED in MAP-MS-DataTypes : 233 749 ageOfLocationEstimate...................identifier of [0] AgeOfLocationInformation DEFINED in MAP-LCS-DataTypes : 217 ageOfLocationEstimate...................identifier of [6] AgeOfLocationInformation DEFINED in MAP-LCS-DataTypes : 325 ageOfLocationInformation................identifier of AgeOfLocationInformation DEFINED in MAP-MS-DataTypes : 1770 AgeOfLocationInformation................type reference INTEGER DEFINED in MAP-CommonDataTypes : 497 USED in MAP-MS-DataTypes : 181 1770 USED in MAP-CommonDataTypes : 58 USED in MAP-LCS-DataTypes : 34 217 325 alertingCategory-1......................value reference AlertingPattern, '00000100'B DEFINED in MAP-CommonDataTypes : 286 alertingCategory-2......................value reference AlertingPattern, '00000101'B DEFINED in MAP-CommonDataTypes : 287 alertingCategory-3......................value reference AlertingPattern, '00000110'B DEFINED in MAP-CommonDataTypes : 288 alertingCategory-4......................value reference AlertingPattern, '00000111'B DEFINED in MAP-CommonDataTypes : 289 alertingCategory-5......................value reference AlertingPattern, '00001000'B DEFINED in MAP-CommonDataTypes : 290 alertingLevel-0.........................value reference AlertingPattern, '00000000'B DEFINED in MAP-CommonDataTypes : 280 alertingLevel-1.........................value reference AlertingPattern, '00000001'B DEFINED in MAP-CommonDataTypes : 281 alertingLevel-2.........................value reference AlertingPattern, '00000010'B DEFINED in MAP-CommonDataTypes : 282
2648
3GPP
2649 Release 4
7929 7930 7931 7932 7933 7934 7935
939
3GPP TS 29.002 V4.17.0 (2006-06)
AlertingPattern.........................type reference OCTET STRING DEFINED in MAP-CommonDataTypes : 267 USED in MAP-CommonDataTypes : 26 280 281 282 286 287 288 289 290 USED in MAP-CH-DataTypes : 71 110 211 391 USED in MAP-SS-DataTypes : 50 225 alertingPattern.........................identifier of [14] AlertingPattern
2650
3GPP
2651 Release 4
7936 7937 7938 7939 7940 7941 7942 7943 7944 7945 7946 7947 7948 7949 7950 7951 7952 7953 7954 7955 7956 7957 7958 7959 7960 7961 7962 7963 7964 7965 7966 7967 7968 7969 7970 7971 7972 7973 7974 7975 7976 7977 7978 7979 7980 7981 7982 7983 7984 7985 7986 7987 7988 7989 7990 7991 7992 7993 7994 7995 7996 7997 7998 7999 8000 8001 8002 8003 8004 8005 8006 8007 8008 8009 8010 8011 8012
940
Cross Reference Listing for MAP-Protocol : 110
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 4
DEFINED in MAP-CH-DataTypes
alertingPattern.........................identifier of [12] AlertingPattern DEFINED in MAP-CH-DataTypes : 211 alertingPattern.........................identifier of [5] AlertingPattern DEFINED in MAP-CH-DataTypes : 391 alertingPattern.........................identifier of AlertingPattern DEFINED in MAP-SS-DataTypes : 225 alertReason.............................identifier of AlertReason DEFINED in MAP-SM-DataTypes : 205 AlertReason.............................type reference ENUMERATED DEFINED in MAP-SM-DataTypes : 217 USED in MAP-SM-DataTypes : 27 205 alertReasonIndicator....................identifier of NULL DEFINED in MAP-SM-DataTypes : 206 alertServiceCentre......................value reference AlertServiceCentre, CHOICE VALUE DEFINED in MAP-Protocol : 269 AlertServiceCentre......................type reference OPERATION DEFINED in MAP-ShortMessageServic : 123 USED in MAP-Protocol : 91 269 USED in MAP-ShortMessageServic : 17 alertServiceCentreArg...................identifier of AlertServiceCentreArg DEFINED in MAP-ShortMessageServic : 125 AlertServiceCentreArg...................type reference SEQUENCE DEFINED in MAP-SM-DataTypes : 178 USED in MAP-ShortMessageServic : 53 125 USED in MAP-SM-DataTypes : 22 allAdditionalInfoTransferSS.............value reference SS-Code, '10000000'B DEFINED in MAP-SS-Code : 107 allAlternateSpeech-DataCDA..............value reference BearerServiceCode, '00110000'B DEFINED in MAP-BS-Code : 82 allAlternateSpeech-DataCDS..............value reference BearerServiceCode, '00111000'B DEFINED in MAP-BS-Code : 84 allAsynchronousServices.................value reference BearerServiceCode, '01100000'B DEFINED in MAP-BS-Code : 95 allBarringSS............................value reference SS-Code, '10010000'B DEFINED in MAP-SS-Code : 117 allBearerServices.......................value reference BearerServiceCode, '00000000'B DEFINED in MAP-BS-Code : 49 allCallCompletionSS.....................value reference SS-Code, '01000000'B DEFINED in MAP-SS-Code : 72 allCallOfferingSS.......................value reference SS-Code, '00110000'B DEFINED in MAP-SS-Code : 63 allCallPrioritySS.......................value reference SS-Code, '10100000'B DEFINED in MAP-SS-Code : 153 allChargingSS...........................value reference SS-Code, '01110000'B DEFINED in MAP-SS-Code : 99 allCommunityOfInterest-SS...............value reference SS-Code, '01100000'B DEFINED in MAP-SS-Code : 93 allCondForwardingSS.....................value reference SS-Code, '00101000'B DEFINED in MAP-SS-Code : 52 allDataCDA-Services.....................value reference BearerServiceCode, '00010000'B DEFINED in MAP-BS-Code : 51
2652
3GPP
2653 Release 4
8013 8014 8015 8016 8017 8018 8019
941
3GPP TS 29.002 V4.17.0 (2006-06)
allDataCDS-Services.....................value reference BearerServiceCode, '00011000'B DEFINED in MAP-BS-Code : 60 allDataCircuitAsynchronous..............value reference BearerServiceCode, '01010000'B DEFINED in MAP-BS-Code : 92
2654
3GPP
2655 Release 4
8020 8021 8022 8023 8024 8025 8026 8027 8028 8029 8030 8031 8032 8033 8034 8035 8036 8037 8038 8039 8040 8041 8042 8043 8044 8045 8046 8047 8048 8049 8050 8051 8052 8053 8054 8055 8056 8057 8058 8059 8060 8061 8062 8063 8064 8065 8066 8067 8068 8069 8070 8071 8072 8073 8074 8075 8076 8077 8078 8079 8080 8081 8082 8083 8084 8085 8086 8087 8088 8089 8090 8091 8092 8093 8094 8095 8096
942
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 5
allDataCircuitSynchronous...............value reference BearerServiceCode, '01011000'B DEFINED in MAP-BS-Code : 98 allDataPDS-Services.....................value reference BearerServiceCode, '00101000'B DEFINED in MAP-BS-Code : 76 allDataTeleservices.....................value reference TeleserviceCode, '01110000'B DEFINED in MAP-TS-Code : 55 allECT-Barred...........................identifier of Named Number, 9 DEFINED in MAP-MS-DataTypes : 980 allFacsimileTransmissionServices........value reference TeleserviceCode, '01100000'B DEFINED in MAP-TS-Code : 48 allForwardingSS.........................value reference SS-Code, '00100000'B DEFINED in MAP-SS-Code : 48 allGPRSData.............................identifier of NULL DEFINED in MAP-MS-DataTypes : 1307 allIC-CallsBarred.......................identifier of Named Number, 19 DEFINED in MAP-MS-DataTypes : 990 allInformationSent......................identifier of [4] NULL DEFINED in MAP-MS-DataTypes : 1976 allInformationSent......................identifier of [11] NULL DEFINED in MAP-CH-DataTypes : 235 allLCSPrivacyException..................value reference SS-Code, '10110000'B DEFINED in MAP-SS-Code : 159 allLineIdentificationSS.................value reference SS-Code, '00010000'B DEFINED in MAP-SS-Code : 25 allLSAData..............................identifier of NULL DEFINED in MAP-MS-DataTypes : 1314 allMOLR-SS..............................value reference SS-Code, '11000000'B DEFINED in MAP-SS-Code : 171 allMultiPartySS.........................value reference SS-Code, '01010000'B DEFINED in MAP-SS-Code : 87 allNameIdentificationSS.................value reference SS-Code, '00011000'B DEFINED in MAP-SS-Code : 40 allOG-CallsBarred.......................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 971 allowedGSM-Algorithms...................identifier of [4] AllowedGSM-Algorithms DEFINED in MAP-MS-DataTypes : 449 AllowedGSM-Algorithms...................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 459 USED in MAP-MS-DataTypes : 449 510 allowedGSM-Algorithms...................identifier of [9] AllowedGSM-Algorithms DEFINED in MAP-MS-DataTypes : 510 allowedUMTS-Algorithms..................identifier of [5] AllowedUMTS-Algorithms DEFINED in MAP-MS-DataTypes : 450 AllowedUMTS-Algorithms..................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 464 USED in MAP-MS-DataTypes : 450 511 allowedUMTS-Algorithms..................identifier of [10] AllowedUMTS-Algorithms DEFINED in MAP-MS-DataTypes : 511 allPacketOrientedServicesBarred.........identifier of Named Number, 15 DEFINED in MAP-MS-DataTypes : 986 allPadAccessCA-Services.................value reference BearerServiceCode, '00100000'B
2656
3GPP
2657 Release 4
8097 8098 8099 8100 8101 8102 8103
943
: 67
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-BS-Code
allPLMN-specificBS......................value reference BearerServiceCode, '11010000'B DEFINED in MAP-BS-Code : 110 allPLMN-specificSS......................value reference SS-Code, '11110000'B DEFINED in MAP-SS-Code : 136
2658
3GPP
2659 Release 4
8104 8105 8106 8107 8108 8109 8110 8111 8112 8113 8114 8115 8116 8117 8118 8119 8120 8121 8122 8123 8124 8125 8126 8127 8128 8129 8130 8131 8132 8133 8134 8135 8136 8137 8138 8139 8140 8141 8142 8143 8144 8145 8146 8147 8148 8149 8150 8151 8152 8153 8154 8155 8156 8157 8158 8159 8160 8161 8162 8163 8164 8165 8166 8167 8168 8169 8170 8171 8172 8173 8174 8175 8176 8177 8178 8179 8180
944
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 6
allPLMN-specificTS......................value reference TeleserviceCode, '11010000'B DEFINED in MAP-TS-Code : 71 allShortMessageServices.................value reference TeleserviceCode, '00100000'B DEFINED in MAP-TS-Code : 44 allSpeechFollowedByDataCDA..............value reference BearerServiceCode, '01000000'B DEFINED in MAP-BS-Code : 86 allSpeechFollowedByDataCDS..............value reference BearerServiceCode, '01001000'B DEFINED in MAP-BS-Code : 88 allSpeechTransmissionServices...........value reference TeleserviceCode, '00010000'B DEFINED in MAP-TS-Code : 40 allSS...................................value reference SS-Code, '00000000'B DEFINED in MAP-SS-Code : 21 allSynchronousServices..................value reference BearerServiceCode, '01101000'B DEFINED in MAP-BS-Code : 101 allTeleservices.........................value reference TeleserviceCode, '00000000'B DEFINED in MAP-TS-Code : 38 allTeleservices-ExeptSMS................value reference TeleserviceCode, '10000000'B DEFINED in MAP-TS-Code : 58 allVoiceGroupCallServices...............value reference TeleserviceCode, '10010000'B DEFINED in MAP-TS-Code : 67 anonymousLocation.......................identifier of Named Number, 3 DEFINED in MAP-CommonDataTypes : 387 anyTimeInterrogation....................value reference AnyTimeInterrogation, CHOICE VALUE DEFINED in MAP-Protocol : 278 AnyTimeInterrogation....................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 244 USED in MAP-Protocol : 31 278 USED in MAP-MobileServiceOpera : 27 anyTimeInterrogationArg.................identifier of AnyTimeInterrogationArg DEFINED in MAP-MobileServiceOpera : 246 AnyTimeInterrogationArg.................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1826 USED in MAP-MobileServiceOpera : 151 246 USED in MAP-MS-DataTypes : 105 anyTimeInterrogationRes.................identifier of AnyTimeInterrogationRes DEFINED in MAP-MobileServiceOpera : 248 AnyTimeInterrogationRes.................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1833 USED in MAP-MobileServiceOpera : 152 248 USED in MAP-MS-DataTypes : 106 anyTimeModification.....................value reference AnyTimeModification, CHOICE VALUE DEFINED in MAP-Protocol : 283 AnyTimeModification.....................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 275 USED in MAP-Protocol : 33 283 USED in MAP-MobileServiceOpera : 31 anyTimeModificationArg..................identifier of AnyTimeModificationArg DEFINED in MAP-MobileServiceOpera : 277 AnyTimeModificationArg..................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1919 USED in MAP-MobileServiceOpera : 147 277 USED in MAP-MS-DataTypes : 111 anyTimeModificationRes..................identifier of AnyTimeModificationRes
2660
3GPP
2661 Release 4
8181 8182 8183 8184 8185 8186 8187
945
279
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-MobileServiceOpera :
AnyTimeModificationRes..................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1929 USED in MAP-MobileServiceOpera : 148 279 USED in MAP-MS-DataTypes : 112
2662
3GPP
2663 Release 4
8188 8189 8190 8191 8192 8193 8194 8195 8196 8197 8198 8199 8200 8201 8202 8203 8204 8205 8206 8207 8208 8209 8210 8211 8212 8213 8214 8215 8216 8217 8218 8219 8220 8221 8222 8223 8224 8225 8226 8227 8228 8229 8230 8231 8232 8233 8234 8235 8236 8237 8238 8239 8240 8241 8242 8243 8244 8245 8246 8247 8248 8249 8250 8251 8252 8253 8254 8255 8256 8257 8258 8259 8260 8261 8262 8263 8264
946
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 7
anyTimeSubscriptionInterrogation.value reference AnyTimeSubscriptionInterrogation, CHOICE VALUE DEFINED in MAP-Protocol : 282 AnyTimeSubscriptionInterrogation........type reference OPERATION DEFINED in MAP-MobileServiceOpera : 258 USED in MAP-Protocol : 32 282 USED in MAP-MobileServiceOpera : 30 anyTimeSubscriptionInterrogationArg.....identifier of AnyTimeSubscriptionInterrogationArg DEFINED in MAP-MobileServiceOpera : 260 AnyTimeSubscriptionInterrogationArg.....type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1841 USED in MAP-MobileServiceOpera : 145 260 USED in MAP-MS-DataTypes : 109 anyTimeSubscriptionInterrogationRes.....identifier of AnyTimeSubscriptionInterrogationRes DEFINED in MAP-MobileServiceOpera : 262 AnyTimeSubscriptionInterrogationRes.....type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1849 USED in MAP-MobileServiceOpera : 146 262 USED in MAP-MS-DataTypes : 110 an-APDU.................................identifier of AccessNetworkSignalInfo DEFINED in MAP-MS-DataTypes : 445 an-APDU.................................identifier of [2] AccessNetworkSignalInfo DEFINED in MAP-MS-DataTypes : 504 an-APDU.................................identifier of [2] AccessNetworkSignalInfo DEFINED in MAP-MS-DataTypes : 558 an-APDU.................................identifier of [3] AccessNetworkSignalInfo DEFINED in MAP-MS-DataTypes : 605 an-APDU.................................identifier of AccessNetworkSignalInfo DEFINED in MAP-MS-DataTypes : 611 an-APDU.................................identifier of AccessNetworkSignalInfo DEFINED in MAP-MS-DataTypes : 616 an-APDU.................................identifier of AccessNetworkSignalInfo DEFINED in MAP-MS-DataTypes : 630 aocc....................................value reference SS-Code, '01110010'B DEFINED in MAP-SS-Code : 104 aoci....................................value reference SS-Code, '01110001'B DEFINED in MAP-SS-Code : 102 apn.....................................identifier of [20] APN DEFINED in MAP-MS-DataTypes : 796 APN.....................................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 868 USED in MAP-MS-DataTypes : 86 796 USED in MAP-LCS-DataTypes : 53 139 asciCallReference.......................identifier of [20] ASCI-CallReference DEFINED in MAP-MS-DataTypes : 519 asciCallReference.......................identifier of ASCI-CallReference DEFINED in MAP-GR-DataTypes : 51 ASCI-CallReference......................type reference TBCD-STRING DEFINED in MAP-CommonDataTypes : 310 USED in MAP-MS-DataTypes : 185 519 USED in MAP-CommonDataTypes : 41 USED in MAP-GR-DataTypes : 26 51 assumedIdle.............................identifier of [0] NULL DEFINED in MAP-MS-DataTypes : 1813 ati-NotAllowed..........................value reference ATI-NotAllowed, CHOICE VALUE
2664
3GPP
2665 Release 4
8265 8266 8267 8268 8269 8270 8271
947
: 390
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-Protocol
ATI-NotAllowed..........................type reference ERROR DEFINED in MAP-Errors : 324 USED in MAP-Protocol : 143 390 USED in MAP-MobileServiceOpera : 90 251 USED in MAP-Errors : 55
2666
3GPP
2667 Release 4
8272 8273 8274 8275 8276 8277 8278 8279 8280 8281 8282 8283 8284 8285 8286 8287 8288 8289 8290 8291 8292 8293 8294 8295 8296 8297 8298 8299 8300 8301 8302 8303 8304 8305 8306 8307 8308 8309 8310 8311 8312 8313 8314 8315 8316 8317 8318 8319 8320 8321 8322 8323 8324 8325 8326 8327 8328 8329 8330 8331 8332 8333 8334 8335 8336 8337 8338 8339 8340 8341 8342 8343 8344 8345 8346 8347 8348
948
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 8
ati-NotAllowedParam.....................identifier of ATI-NotAllowedParam DEFINED in MAP-Errors : 326 ATI-NotAllowedParam.....................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 283 USED in MAP-Errors : 132 326 USED in MAP-ER-DataTypes : 39 atm-NotAllowed..........................value reference ATM-NotAllowed, CHOICE VALUE DEFINED in MAP-Protocol : 394 ATM-NotAllowed..........................type reference ERROR DEFINED in MAP-Errors : 335 USED in MAP-Protocol : 168 394 USED in MAP-MobileServiceOpera : 96 281 USED in MAP-Errors : 59 atm-NotAllowedParam.....................identifier of ATM-NotAllowedParam DEFINED in MAP-Errors : 337 ATM-NotAllowedParam.....................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 291 USED in MAP-Errors : 147 337 USED in MAP-ER-DataTypes : 55 atsi-NotAllowed.........................value reference ATSI-NotAllowed, CHOICE VALUE DEFINED in MAP-Protocol : 393 ATSI-NotAllowed.........................type reference ERROR DEFINED in MAP-Errors : 330 USED in MAP-Protocol : 167 393 USED in MAP-MobileServiceOpera : 95 264 USED in MAP-Errors : 58 atsi-NotAllowedParam....................identifier of ATSI-NotAllowedParam DEFINED in MAP-Errors : 332 ATSI-NotAllowedParam....................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 287 USED in MAP-Errors : 146 332 USED in MAP-ER-DataTypes : 54 attach..................................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 857 attachChangeOfPosition..................identifier of Named Number, 2 DEFINED in MAP-MS-DataTypes : 858 authenticationFailureReport...........value reference AuthenticationFailureReport, CHOICE VALUE DEFINED in MAP-Protocol : 202 AuthenticationFailureReport.............type reference OPERATION DEFINED in MAP-MobileServiceOpera : 367 USED in MAP-Protocol : 23 202 USED in MAP-MobileServiceOpera : 46 authenticationFailureReportArg..........identifier of AuthenticationFailureReportArg DEFINED in MAP-MobileServiceOpera : 369 AuthenticationFailureReportArg..........type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 379 USED in MAP-MobileServiceOpera : 133 369 USED in MAP-MS-DataTypes : 46 authenticationFailureReportRes..........identifier of AuthenticationFailureReportRes DEFINED in MAP-MobileServiceOpera : 371 AuthenticationFailureReportRes..........type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 406 USED in MAP-MobileServiceOpera : 134 371 USED in MAP-MS-DataTypes : 47 AuthenticationQuintuplet................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 334
2668
3GPP
2669 Release 4
8349 8350 8351 8352 8353 8354 8355
949
: 326
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-MS-DataTypes
authenticationSetList...................identifier of AuthenticationSetList DEFINED in MAP-MS-DataTypes : 311 AuthenticationSetList...................type reference CHOICE DEFINED in MAP-MS-DataTypes : 318
2670
3GPP
2671 Release 4
8356 8357 8358 8359 8360 8361 8362 8363 8364 8365 8366 8367 8368 8369 8370 8371 8372 8373 8374 8375 8376 8377 8378 8379 8380 8381 8382 8383 8384 8385 8386 8387 8388 8389 8390 8391 8392 8393 8394 8395 8396 8397 8398 8399 8400 8401 8402 8403 8404 8405 8406 8407 8408 8409 8410 8411 8412 8413 8414 8415 8416 8417 8418 8419 8420 8421 8422 8423 8424 8425 8426 8427 8428 8429 8430 8431 8432
950
Cross Reference Listing for MAP-Protocol : 311 712
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 9
USED in MAP-MS-DataTypes
authenticationSetList...................identifier of AuthenticationSetList DEFINED in MAP-MS-DataTypes : 712 AuthenticationTriplet...................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 328 USED in MAP-MS-DataTypes : 323 autn....................................identifier of AUTN DEFINED in MAP-MS-DataTypes : 339 AUTN....................................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 369 USED in MAP-MS-DataTypes : 339 automaticFacsimileGroup3................value reference TeleserviceCode, '01100010'B DEFINED in MAP-TS-Code : 50 autonomousSelfLocation..................value reference SS-Code, '11000010'B DEFINED in MAP-SS-Code : 175 AUTS....................................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 371 USED in MAP-MS-DataTypes : 708 auts....................................identifier of AUTS DEFINED in MAP-MS-DataTypes : 708 a-side..................................identifier of Named Number, 0 DEFINED in MAP-CH-DataTypes : 364 badlyFormattedTransactionPortion........identifier of Named Number, 2 DEFINED in TCAPMessages : 105 badlyStructuredComponent................identifier of Named Number, 2 DEFINED in TCAPMessages : 181 baic....................................value reference SS-Code, '10011010'B DEFINED in MAP-SS-Code : 130 baoc....................................value reference SS-Code, '10010010'B DEFINED in MAP-SS-Code : 121 barringOfIncomingCalls..................value reference SS-Code, '10011001'B DEFINED in MAP-SS-Code : 128 barringOfOutgoingCalls..................value reference SS-Code, '10010001'B DEFINED in MAP-SS-Code : 119 barringServiceActive....................identifier of Named Number, 0 DEFINED in MAP-ER-DataTypes : 110 basicCall...............................identifier of Named Number, 0 DEFINED in MAP-CH-DataTypes : 122 basicISTSupported.......................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 240 basicSelfLocation.......................value reference SS-Code, '11000001'B DEFINED in MAP-SS-Code : 173 basicService............................identifier of Ext-BasicServiceCode DEFINED in MAP-MS-DataTypes : 1038 basicService............................identifier of Ext-BasicServiceCode DEFINED in MAP-MS-DataTypes : 1097 basicService............................identifier of Ext-BasicServiceCode DEFINED in MAP-MS-DataTypes : 1140 basicService............................identifier of [1] Ext-BasicServiceCode DEFINED in MAP-MS-DataTypes : 1937 basicService............................identifier of [1] Ext-BasicServiceCode
2672
3GPP
2673 Release 4
8433 8434 8435 8436 8437 8438 8439
951
: 1948
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-MS-DataTypes
basicService............................identifier of [5] Ext-BasicServiceCode DEFINED in MAP-CH-DataTypes : 155 basicService............................identifier of BasicServiceCode DEFINED in MAP-SS-DataTypes : 74
2674
3GPP
2675 Release 4
8440 8441 8442 8443 8444 8445 8446 8447 8448 8449 8450 8451 8452 8453 8454 8455 8456 8457 8458 8459 8460 8461 8462 8463 8464 8465 8466 8467 8468 8469 8470 8471 8472 8473 8474 8475 8476 8477 8478 8479 8480 8481 8482 8483 8484 8485 8486 8487 8488 8489 8490 8491 8492 8493 8494 8495 8496 8497 8498 8499 8500 8501 8502 8503 8504 8505 8506 8507 8508 8509 8510 8511 8512 8513 8514 8515 8516
952
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 10
basicService............................identifier of BasicServiceCode DEFINED in MAP-SS-DataTypes : 100 basicService............................identifier of BasicServiceCode DEFINED in MAP-SS-DataTypes : 157 basicService............................identifier of BasicServiceCode DEFINED in MAP-SS-DataTypes : 186 basicService............................identifier of BasicServiceCode DEFINED in MAP-ER-DataTypes : 132 BasicServiceCode........................type reference CHOICE DEFINED in MAP-CommonDataTypes : 429 USED in MAP-CommonDataTypes : 48 USED in MAP-SS-DataTypes : 49 74 100 157 186 210 265 USED in MAP-ER-DataTypes : 74 132 basicServiceCriteria....................identifier of [1] BasicServiceCriteria DEFINED in MAP-MS-DataTypes : 1452 basicServiceCriteria....................identifier of [0] BasicServiceCriteria DEFINED in MAP-MS-DataTypes : 1460 BasicServiceCriteria....................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1480 USED in MAP-MS-DataTypes : 73 1452 1460 basicServiceGroup.......................identifier of [9] Ext-BasicServiceCode DEFINED in MAP-CH-DataTypes : 104 basicServiceGroup.......................identifier of [1] Ext-BasicServiceCode DEFINED in MAP-CH-DataTypes : 226 basicServiceGroup.......................identifier of [3] BasicServiceCode DEFINED in MAP-SS-DataTypes : 210 basicServiceGroupList...................identifier of Ext-BasicServiceGroupList DEFINED in MAP-MS-DataTypes : 1115 basicServiceGroupList...................identifier of Ext-BasicServiceGroupList DEFINED in MAP-MS-DataTypes : 1162 basicServiceGroupList...................identifier of BasicServiceGroupList DEFINED in MAP-SS-DataTypes : 165 basicServiceGroupList...................identifier of [2] BasicServiceGroupList DEFINED in MAP-SS-DataTypes : 217 BasicServiceGroupList...................type reference SEQUENCE OF DEFINED in MAP-SS-DataTypes : 264 USED in MAP-SS-DataTypes : 165 217 basicServiceList........................identifier of [1] BasicServiceList DEFINED in MAP-MS-DataTypes : 1273 BasicServiceList........................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1320 USED in MAP-MS-DataTypes : 1273 bearerService...........................identifier of [2] BearerServiceCode DEFINED in MAP-CommonDataTypes : 430 BearerServiceCode.......................type reference OCTET STRING DEFINED in MAP-BS-Code : 11 USED in MAP-CommonDataTypes : 70 430 USED in MAP-BS-Code : 49 51 52 53 54 55 56 57 60 61 62 63 64 65 67 68 69 70 71 72 73 74 76 77 78 79 80 82 84 86 88 92 95 98 101 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 bearerServiceList.......................identifier of [4] BearerServiceList
58
2676
3GPP
2677 Release 4
8517 8518 8519 8520 8521 8522 8523
953
: 932
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-MS-DataTypes
BearerServiceList.......................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 954 USED in MAP-MS-DataTypes : 932 1257 bearerServiceList.......................identifier of [2] BearerServiceList
2678
3GPP
2679 Release 4
8524 8525 8526 8527 8528 8529 8530 8531 8532 8533 8534 8535 8536 8537 8538 8539 8540 8541 8542 8543 8544 8545 8546 8547 8548 8549 8550 8551 8552 8553 8554 8555 8556 8557 8558 8559 8560 8561 8562 8563 8564 8565 8566 8567 8568 8569 8570 8571 8572 8573 8574 8575 8576 8577 8578 8579 8580 8581 8582 8583 8584 8585 8586 8587 8588 8589 8590 8591 8592 8593 8594 8595 8596 8597 8598 8599 8600
954
Cross Reference Listing for MAP-Protocol : 1257
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 11
DEFINED in MAP-MS-DataTypes
bearerServiceNotProvisioned...........value reference BearerServiceNotProvisioned, CHOICE VALUE DEFINED in MAP-Protocol : 353 BearerServiceNotProvisioned.............type reference ERROR DEFINED in MAP-Errors : 240 USED in MAP-Protocol : 129 353 USED in MAP-MobileServiceOpera : 97 268 285 USED in MAP-CallHandlingOperat : 37 94 USED in MAP-SupplementaryServi : 37 97 114 131 151 169 USED in MAP-Errors : 32 bearerServNotProvParam..................identifier of BearerServNotProvParam DEFINED in MAP-Errors : 242 BearerServNotProvParam..................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 230 USED in MAP-Errors : 120 242 USED in MAP-ER-DataTypes : 30 begin...................................identifier of [APPLICATION 2] IMPLICIT Begin DEFINED in TCAPMessages : 53 Begin...................................type reference SEQUENCE DEFINED in TCAPMessages : 61 USED in TCAPMessages : 53 bicRoam.................................value reference SS-Code, '10011011'B DEFINED in MAP-SS-Code : 132 blackListed.............................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 728 boic....................................value reference SS-Code, '10010011'B DEFINED in MAP-SS-Code : 123 boicExHC................................value reference SS-Code, '10010100'B DEFINED in MAP-SS-Code : 125 bothMSCAndSGSN..........................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 778 broadcastInitEntitlement................identifier of NULL DEFINED in MAP-MS-DataTypes : 1730 broadcastService........................identifier of Named Number, 0 DEFINED in MAP-CommonDataTypes : 384 bssmap-ServiceHandover..................identifier of [9] BSSMAP-ServiceHandover DEFINED in MAP-MS-DataTypes : 455 bssmap-ServiceHandover..................identifier of [13] BSSMAP-ServiceHandover DEFINED in MAP-MS-DataTypes : 516 bssmap-ServiceHandover..................identifier of BSSMAP-ServiceHandover DEFINED in MAP-MS-DataTypes : 526 BSSMAP-ServiceHandover..................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 533 USED in MAP-MS-DataTypes : 455 516 526 BSSMAP-ServiceHandoverInfo..............type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 525 USED in MAP-MS-DataTypes : 523 bssmap-ServiceHandoverList..............identifier of [10] BSSMAP-ServiceHandoverList DEFINED in MAP-MS-DataTypes : 457 bssmap-ServiceHandoverList..............identifier of [15] BSSMAP-ServiceHandoverList DEFINED in MAP-MS-DataTypes : 518 BSSMAP-ServiceHandoverList..............type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 522 USED in MAP-MS-DataTypes : 457 518
2680
3GPP
2681 Release 4
8601 8602 8603 8604 8605 8606 8607
955
3GPP TS 29.002 V4.17.0 (2006-06)
busy....................................identifier of Named Number, 1 DEFINED in MAP-CH-DataTypes : 131 busy....................................identifier of Named Number, 2 DEFINED in MAP-CH-DataTypes : 374
2682
3GPP
2683 Release 4
8608 8609 8610 8611 8612 8613 8614 8615 8616 8617 8618 8619 8620 8621 8622 8623 8624 8625 8626 8627 8628 8629 8630 8631 8632 8633 8634 8635 8636 8637 8638 8639 8640 8641 8642 8643 8644 8645 8646 8647 8648 8649 8650 8651 8652 8653 8654 8655 8656 8657 8658 8659 8660 8661 8662 8663 8664 8665 8666 8667 8668 8669 8670 8671 8672 8673 8674 8675 8676 8677 8678 8679 8680 8681 8682 8683 8684
956
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 12
busySubscriber..........................value reference BusySubscriber, CHOICE VALUE DEFINED in MAP-Protocol : 379 BusySubscriber..........................type reference ERROR DEFINED in MAP-Errors : 287 USED in MAP-Protocol : 137 379 USED in MAP-CallHandlingOperat : 41 97 190 USED in MAP-Errors : 46 busySubscriberParam.....................identifier of BusySubscriberParam DEFINED in MAP-Errors : 289 BusySubscriberParam.....................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 265 USED in MAP-Errors : 126 289 USED in MAP-ER-DataTypes : 35 b-side..................................identifier of Named Number, 1 DEFINED in MAP-CH-DataTypes : 365 b-subscriberNumber......................identifier of [1] ISDN-AddressString DEFINED in MAP-SS-DataTypes : 208 b-subscriberNumber......................identifier of [5] ISDN-AddressString DEFINED in MAP-SS-DataTypes : 281 b-subscriberSubaddress..................identifier of [2] ISDN-SubaddressString DEFINED in MAP-SS-DataTypes : 209 b-Subscriber-Address....................identifier of [3] ISDN-AddressString DEFINED in MAP-CH-DataTypes : 285 call....................................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 391 callBarred..............................value reference CallBarred, CHOICE VALUE DEFINED in MAP-Protocol : 381 CallBarred..............................type reference ERROR DEFINED in MAP-Errors : 297 USED in MAP-Protocol : 139 381 USED in MAP-MobileServiceOpera : 99 270 287 446 USED in MAP-CallHandlingOperat : 43 99 USED in MAP-SupplementaryServi : 39 99 116 133 153 171 185 226 260 277 USED in MAP-ShortMessageServic : 36 78 USED in MAP-Errors : 49 callBarredParam.........................identifier of CallBarredParam DEFINED in MAP-Errors : 299 CallBarredParam.........................type reference CHOICE DEFINED in MAP-ER-DataTypes : 102 USED in MAP-Errors : 128 299 USED in MAP-ER-DataTypes : 15 callBarringCause........................identifier of CallBarringCause DEFINED in MAP-ER-DataTypes : 103 CallBarringCause........................type reference ENUMERATED DEFINED in MAP-ER-DataTypes : 109 USED in MAP-ER-DataTypes : 103 114 callBarringCause........................identifier of CallBarringCause DEFINED in MAP-ER-DataTypes : 114 callBarringData.........................identifier of [2] CallBarringData DEFINED in MAP-MS-DataTypes : 1851 CallBarringData.........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1885 USED in MAP-MS-DataTypes : 1851 CallBarringFeature......................type reference SEQUENCE DEFINED in MAP-SS-DataTypes : 156
2684
3GPP
2685 Release 4
8685 8686 8687 8688 8689 8690 8691
957
: 154
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-SS-DataTypes
callBarringFeatureList..................identifier of Ext-CallBarFeatureList DEFINED in MAP-MS-DataTypes : 1089 callBarringFeatureList..................identifier of Ext-CallBarFeatureList DEFINED in MAP-MS-DataTypes : 1886
2686
3GPP
2687 Release 4
8692 8693 8694 8695 8696 8697 8698 8699 8700 8701 8702 8703 8704 8705 8706 8707 8708 8709 8710 8711 8712 8713 8714 8715 8716 8717 8718 8719 8720 8721 8722 8723 8724 8725 8726 8727 8728 8729 8730 8731 8732 8733 8734 8735 8736 8737 8738 8739 8740 8741 8742 8743 8744 8745 8746 8747 8748 8749 8750 8751 8752 8753 8754 8755 8756 8757 8758 8759 8760 8761 8762 8763 8764 8765 8766 8767 8768
958
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 13
callBarringFeatureList..................identifier of [1] Ext-CallBarFeatureList DEFINED in MAP-MS-DataTypes : 2015 callBarringFeatureList..................identifier of CallBarringFeatureList DEFINED in MAP-SS-DataTypes : 150 CallBarringFeatureList..................type reference SEQUENCE OF DEFINED in MAP-SS-DataTypes : 153 USED in MAP-SS-DataTypes : 150 callBarringInfo.........................identifier of [1] Ext-CallBarInfo DEFINED in MAP-MS-DataTypes : 1022 callBarringInfo.........................identifier of [1] CallBarringInfo DEFINED in MAP-SS-DataTypes : 87 CallBarringInfo.........................type reference SEQUENCE DEFINED in MAP-SS-DataTypes : 148 USED in MAP-SS-DataTypes : 87 callBarringInfoFor-CSE..................identifier of [1] Ext-CallBarringInfoFor-CSE DEFINED in MAP-MS-DataTypes : 1973 callBarringInfoFor-CSE..................identifier of [1] Ext-CallBarringInfoFor-CSE DEFINED in MAP-MS-DataTypes : 2003 CallDirection...........................type reference OCTET STRING DEFINED in MAP-CH-DataTypes : 292 USED in MAP-CH-DataTypes : 284 callDiversionTreatmentIndicator.........identifier of [20] CallDiversionTreatmentIndicator DEFINED in MAP-CH-DataTypes : 116 CallDiversionTreatmentIndicator.........type reference OCTET STRING DEFINED in MAP-CH-DataTypes : 140 USED in MAP-CH-DataTypes : 116 calledPartySS-InteractionViolation......identifier of Named Number, 7 DEFINED in MAP-ER-DataTypes : 128 callForwardingData......................identifier of [1] CallForwardingData DEFINED in MAP-MS-DataTypes : 1850 CallForwardingData......................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1879 USED in MAP-MS-DataTypes : 1850 callInfo................................identifier of [1] ExternalSignalInfo DEFINED in MAP-CH-DataTypes : 387 callInfo................................identifier of [3] ExternalSignalInfo DEFINED in MAP-SS-DataTypes : 314 callOriginator..........................identifier of [8] NULL DEFINED in MAP-GR-DataTypes : 122 callOutcome.............................identifier of [1] CallOutcome DEFINED in MAP-CH-DataTypes : 359 CallOutcome.............................type reference ENUMERATED DEFINED in MAP-CH-DataTypes : 371 USED in MAP-CH-DataTypes : 359 callReferenceNumber.....................identifier of [7] CallReferenceNumber DEFINED in MAP-CH-DataTypes : 102 CallReferenceNumber.....................type reference OCTET STRING DEFINED in MAP-CH-DataTypes : 127 USED in MAP-CH-DataTypes : 22 102 207 225 callReferenceNumber.....................identifier of [9] CallReferenceNumber DEFINED in MAP-CH-DataTypes : 207 callReferenceNumber.....................identifier of [0] CallReferenceNumber
2688
3GPP
2689 Release 4
8769 8770 8771 8772 8773 8774 8775
959
: 225
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-CH-DataTypes
callReportdata..........................identifier of [2] CallReportData DEFINED in MAP-CH-DataTypes : 348 CallReportData..........................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 357
2690
3GPP
2691 Release 4
8776 8777 8778 8779 8780 8781 8782 8783 8784 8785 8786 8787 8788 8789 8790 8791 8792 8793 8794 8795 8796 8797 8798 8799 8800 8801 8802 8803 8804 8805 8806 8807 8808 8809 8810 8811 8812 8813 8814 8815 8816 8817 8818 8819 8820 8821 8822 8823 8824 8825 8826 8827 8828 8829 8830 8831 8832 8833 8834 8835 8836 8837 8838 8839 8840 8841 8842 8843 8844 8845 8846 8847 8848 8849 8850 8851 8852
960
Cross Reference Listing for MAP-Protocol : 348
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 14
USED in MAP-CH-DataTypes
callSessionRelated......................value reference SS-Code, '10110010'B DEFINED in MAP-SS-Code : 163 callSessionUnrelated....................value reference SS-Code, '10110011'B DEFINED in MAP-SS-Code : 166 callTerminationIndicator................identifier of [2] CallTerminationIndicator DEFINED in MAP-CH-DataTypes : 424 CallTerminationIndicator................type reference ENUMERATED DEFINED in MAP-CH-DataTypes : 437 USED in MAP-CH-DataTypes : 424 callToClientNotSetup....................identifier of Named Number, 2 DEFINED in MAP-ER-DataTypes : 352 callTypeCriteria........................identifier of [2] CallTypeCriteria DEFINED in MAP-MS-DataTypes : 1453 CallTypeCriteria........................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 1491 USED in MAP-MS-DataTypes : 1453 call-Direction..........................identifier of [2] CallDirection DEFINED in MAP-CH-DataTypes : 284 camelBusy...............................identifier of [1] NULL DEFINED in MAP-MS-DataTypes : 1814 camelCapabilityHandling.................identifier of [1] CamelCapabilityHandling DEFINED in MAP-MS-DataTypes : 822 camelCapabilityHandling.................identifier of [1] CamelCapabilityHandling DEFINED in MAP-MS-DataTypes : 1345 camelCapabilityHandling.................identifier of [0] CamelCapabilityHandling DEFINED in MAP-MS-DataTypes : 1404 CamelCapabilityHandling.................type reference INTEGER DEFINED in MAP-MS-DataTypes : 1522 USED in MAP-MS-DataTypes : 72 822 1345 1404 1537 1612 camelCapabilityHandling.................identifier of [1] CamelCapabilityHandling DEFINED in MAP-MS-DataTypes : 1537 camelCapabilityHandling.................identifier of [0] CamelCapabilityHandling DEFINED in MAP-MS-DataTypes : 1612 camelInfo...............................identifier of [11] CamelInfo DEFINED in MAP-CH-DataTypes : 106 CamelInfo...............................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 256 USED in MAP-CH-DataTypes : 106 camelRoutingInfo........................identifier of [8] CamelRoutingInfo DEFINED in MAP-CH-DataTypes : 264 CamelRoutingInfo........................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 266 USED in MAP-CH-DataTypes : 264 camelSubscriptionInfoWithdraw...........identifier of [9] NULL DEFINED in MAP-MS-DataTypes : 1281 camel-invoked...........................identifier of Named Number, 1 DEFINED in MAP-SS-DataTypes : 320 camel-SubscriptionInfo..................identifier of [4] CAMEL-SubscriptionInfo DEFINED in MAP-MS-DataTypes : 1853 CAMEL-SubscriptionInfo..................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1901
2692
3GPP
2693 Release 4
8853 8854 8855 8856 8857 8858 8859
961
: 1853 1931 1975
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-MS-DataTypes
camel-SubscriptionInfo..................identifier of [1] CAMEL-SubscriptionInfo DEFINED in MAP-MS-DataTypes : 1931 camel-SubscriptionInfo..................identifier of [3] CAMEL-SubscriptionInfo DEFINED in MAP-MS-DataTypes : 1975
2694
3GPP
2695 Release 4
8860 8861 8862 8863 8864 8865 8866 8867 8868 8869 8870 8871 8872 8873 8874 8875 8876 8877 8878 8879 8880 8881 8882 8883 8884 8885 8886 8887 8888 8889 8890 8891 8892 8893 8894 8895 8896 8897 8898 8899 8900 8901 8902 8903 8904 8905 8906 8907 8908 8909 8910 8911 8912 8913 8914 8915 8916 8917 8918 8919 8920 8921 8922 8923 8924 8925 8926 8927 8928 8929 8930 8931 8932 8933 8934 8935 8936
962
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 15
cancelDeferredLocation..................identifier of Named Number, 4 DEFINED in MAP-LCS-DataTypes : 120 cancellationType........................identifier of CancellationType DEFINED in MAP-MS-DataTypes : 266 CancellationType........................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 271 USED in MAP-MS-DataTypes : 266 cancelLocation..........................value reference CancelLocation, CHOICE VALUE DEFINED in MAP-Protocol : 184 CancelLocation..........................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 188 USED in MAP-Protocol : 13 184 USED in MAP-MobileServiceOpera : 16 cancelLocationArg.......................identifier of CancelLocationArg DEFINED in MAP-MobileServiceOpera : 190 CancelLocationArg.......................type reference [3] SEQUENCE DEFINED in MAP-MS-DataTypes : 264 USED in MAP-MobileServiceOpera : 115 190 USED in MAP-MS-DataTypes : 18 cancelLocationRes.......................identifier of CancelLocationRes DEFINED in MAP-MobileServiceOpera : 192 CancelLocationRes.......................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 278 USED in MAP-MobileServiceOpera : 116 192 USED in MAP-MS-DataTypes : 19 category................................identifier of [2] Category DEFINED in MAP-MS-DataTypes : 930 Category................................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 947 USED in MAP-MS-DataTypes : 930 CauseValue..............................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 1509 USED in MAP-MS-DataTypes : 1500 1503 ccbsIdle................................identifier of Named Number, 1 DEFINED in MAP-CH-DataTypes : 337 ccbsNotIdle.............................identifier of Named Number, 0 DEFINED in MAP-CH-DataTypes : 336 ccbsNotReachable........................identifier of Named Number, 2 DEFINED in MAP-CH-DataTypes : 338 ccbs-A..................................value reference SS-Code, '01000011'B DEFINED in MAP-SS-Code : 79 ccbs-B..................................value reference SS-Code, '01000100'B DEFINED in MAP-SS-Code : 81 ccbs-Busy...............................identifier of [1] NULL DEFINED in MAP-ER-DataTypes : 269 ccbs-Call...............................identifier of [15] NULL DEFINED in MAP-CH-DataTypes : 111 ccbs-Call...............................identifier of [13] NULL DEFINED in MAP-CH-DataTypes : 212 ccbs-Data...............................identifier of [1] CCBS-Data DEFINED in MAP-SS-DataTypes : 307 CCBS-Data...............................type reference SEQUENCE DEFINED in MAP-SS-DataTypes : 310
2696
3GPP
2697 Release 4
8937 8938 8939 8940 8941 8942 8943
963
: 307
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-SS-DataTypes
ccbs-Feature............................identifier of [2] CCBS-Feature DEFINED in MAP-CH-DataTypes : 388 CCBS-Feature............................type reference SEQUENCE DEFINED in MAP-SS-DataTypes : 206
2698
3GPP
2699 Release 4
8944 8945 8946 8947 8948 8949 8950 8951 8952 8953 8954 8955 8956 8957 8958 8959 8960 8961 8962 8963 8964 8965 8966 8967 8968 8969 8970 8971 8972 8973 8974 8975 8976 8977 8978 8979 8980 8981 8982 8983 8984 8985 8986 8987 8988 8989 8990 8991 8992 8993 8994 8995 8996 8997 8998 8999 9000 9001 9002 9003 9004 9005 9006 9007 9008 9009 9010 9011 9012 9013 9014 9015 9016 9017 9018 9019 9020
964
Cross Reference Listing for MAP-Protocol : : 58 388 36 202 311 325
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 16
USED in MAP-CH-DataTypes USED in MAP-SS-DataTypes
ccbs-Feature............................identifier of [0] CCBS-Feature DEFINED in MAP-SS-DataTypes : 311 ccbs-Feature............................identifier of [0] CCBS-Feature DEFINED in MAP-SS-DataTypes : 325 ccbs-FeatureList........................identifier of [2] CCBS-FeatureList DEFINED in MAP-SS-DataTypes : 196 CCBS-FeatureList........................type reference SEQUENCE OF DEFINED in MAP-SS-DataTypes : 201 USED in MAP-SS-DataTypes : 196 ccbs-Index..............................identifier of [0] CCBS-Index DEFINED in MAP-SS-DataTypes : 207 CCBS-Index..............................type reference INTEGER DEFINED in MAP-SS-DataTypes : 213 USED in MAP-SS-DataTypes : 207 330 ccbs-Index..............................identifier of [1] CCBS-Index DEFINED in MAP-SS-DataTypes : 330 ccbs-Indicators.........................identifier of [11] CCBS-Indicators DEFINED in MAP-CH-DataTypes : 162 CCBS-Indicators.........................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 177 USED in MAP-CH-DataTypes : 162 ccbs-Monitoring.........................identifier of [2] ReportingState DEFINED in MAP-CH-DataTypes : 318 ccbs-Possible...........................identifier of [0] NULL DEFINED in MAP-CH-DataTypes : 178 ccbs-Possible...........................identifier of [8] NULL DEFINED in MAP-CH-DataTypes : 232 ccbs-Possible...........................identifier of [0] NULL DEFINED in MAP-ER-DataTypes : 268 ccbs-RequestState.......................identifier of [6] CCBS-RequestState DEFINED in MAP-SS-DataTypes : 282 CCBS-RequestState.......................type reference ENUMERATED DEFINED in MAP-SS-DataTypes : 285 USED in MAP-SS-DataTypes : 282 ccbs-SubscriberStatus...................identifier of [0] CCBS-SubscriberStatus DEFINED in MAP-CH-DataTypes : 331 CCBS-SubscriberStatus...................type reference ENUMERATED DEFINED in MAP-CH-DataTypes : 335 USED in MAP-CH-DataTypes : 331 353 ccbs-SubscriberStatus...................identifier of [0] CCBS-SubscriberStatus DEFINED in MAP-CH-DataTypes : 353 cd......................................value reference SS-Code, '00100100'B DEFINED in MAP-SS-Code : 60 cellGlobalIdOrServiceAreaIdFixedLength..identifier of [0] CellGlobalIdOrServiceAreaIdFixedLength DEFINED in MAP-CommonDataTypes : 395 CellGlobalIdOrServiceAreaIdFixedLength..type reference OCTET STRING DEFINED in MAP-CommonDataTypes : 398 USED in MAP-CommonDataTypes : 395 cellGlobalIdOrServiceAreaIdOrLAI........identifier of [3] CellGlobalIdOrServiceAreaIdOrLAI DEFINED in MAP-MS-DataTypes : 1774
2700
3GPP
2701 Release 4
9021 9022 9023 9024 9025 9026 9027
965
3GPP TS 29.002 V4.17.0 (2006-06)
CellGlobalIdOrServiceAreaIdOrLAI........type reference CHOICE DEFINED in MAP-CommonDataTypes : 394 USED in MAP-MS-DataTypes : 175 1774 USED in MAP-CommonDataTypes : 45 cfb.....................................value reference SS-Code, '00101001'B DEFINED in MAP-SS-Code : 54
2702
3GPP
2703 Release 4
9028 9029 9030 9031 9032 9033 9034 9035 9036 9037 9038 9039 9040 9041 9042 9043 9044 9045 9046 9047 9048 9049 9050 9051 9052 9053 9054 9055 9056 9057 9058 9059 9060 9061 9062 9063 9064 9065 9066 9067 9068 9069 9070 9071 9072 9073 9074 9075 9076 9077 9078 9079 9080 9081 9082 9083 9084 9085 9086 9087 9088 9089 9090 9091 9092 9093 9094 9095 9096 9097 9098 9099 9100 9101 9102 9103 9104
966
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 17
cfnrc...................................value reference SS-Code, '00101011'B DEFINED in MAP-SS-Code : 58 cfnry...................................value reference SS-Code, '00101010'B DEFINED in MAP-SS-Code : 56 cfu.....................................value reference SS-Code, '00100001'B DEFINED in MAP-SS-Code : 50 channelType.............................identifier of [0] ExternalSignalInfo DEFINED in MAP-CH-DataTypes : 305 chargeableECT-Barred....................identifier of Named Number, 10 DEFINED in MAP-MS-DataTypes : 981 chargingCharacteristics.................identifier of [18] ChargingCharacteristics DEFINED in MAP-MS-DataTypes : 753 ChargingCharacteristics.................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 892 USED in MAP-MS-DataTypes : 753 800 chargingCharacteristicsWithdraw.........identifier of [16] NULL DEFINED in MAP-MS-DataTypes : 1290 checkIMEI...............................value reference CheckIMEI, CHOICE VALUE DEFINED in MAP-Protocol : 207 CheckIMEI...............................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 380 USED in MAP-Protocol : 24 207 USED in MAP-MobileServiceOpera : 49 chosenChannel...........................identifier of [4] ExternalSignalInfo DEFINED in MAP-CH-DataTypes : 286 chosenChannel...........................identifier of [1] ExternalSignalInfo DEFINED in MAP-CH-DataTypes : 306 chosenChannel...........................identifier of [0] ExternalSignalInfo DEFINED in MAP-CH-DataTypes : 311 chosenChannelInfo.......................identifier of [0] ChosenChannelInfo DEFINED in MAP-MS-DataTypes : 587 ChosenChannelInfo.......................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 592 USED in MAP-MS-DataTypes : 587 ChosenEncryptionAlgorithm...............type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 579 USED in MAP-MS-DataTypes : 568 ChosenIntegrityProtectionAlgorithm......type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 572 USED in MAP-MS-DataTypes : 567 chosenRadioResourceInformation..........identifier of [6] ChosenRadioResourceInformation DEFINED in MAP-MS-DataTypes : 562 ChosenRadioResourceInformation..........type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 586 USED in MAP-MS-DataTypes : 562 619 chosenRadioResourceInformation..........identifier of [3] ChosenRadioResourceInformation DEFINED in MAP-MS-DataTypes : 619 chosenSpeechVersion.....................identifier of [1] ChosenSpeechVersion DEFINED in MAP-MS-DataTypes : 588 ChosenSpeechVersion.....................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 596 USED in MAP-MS-DataTypes : 588
2704
3GPP
2705 Release 4
9105 9106 9107 9108 9109 9110 9111
967
3GPP TS 29.002 V4.17.0 (2006-06)
cipheringAlgorithm......................identifier of CipheringAlgorithm DEFINED in MAP-GR-DataTypes : 53 CipheringAlgorithm......................type reference OCTET STRING DEFINED in MAP-GR-DataTypes : 100 USED in MAP-GR-DataTypes : 53
2706
3GPP
2707 Release 4
9112 9113 9114 9115 9116 9117 9118 9119 9120 9121 9122 9123 9124 9125 9126 9127 9128 9129 9130 9131 9132 9133 9134 9135 9136 9137 9138 9139 9140 9141 9142 9143 9144 9145 9146 9147 9148 9149 9150 9151 9152 9153 9154 9155 9156 9157 9158 9159 9160 9161 9162 9163 9164 9165 9166 9167 9168 9169 9170 9171 9172 9173 9174 9175 9176 9177 9178 9179 9180 9181 9182 9183 9184 9185 9186 9187 9188
968
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 18
ck......................................identifier of CK DEFINED in MAP-MS-DataTypes : 337 ck......................................identifier of CK DEFINED in MAP-MS-DataTypes : 352 CK......................................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 365 USED in MAP-MS-DataTypes : 337 352 cksn....................................identifier of Cksn DEFINED in MAP-MS-DataTypes : 348 Cksn....................................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 373 USED in MAP-MS-DataTypes : 348 clientIdentity..........................identifier of LCSClientExternalID DEFINED in MAP-MS-DataTypes : 1210 clientNotInMSPrivacyExceptionList.......identifier of Named Number, 1 DEFINED in MAP-ER-DataTypes : 351 clip....................................value reference SS-Code, '00010001'B DEFINED in MAP-SS-Code : 28 clir....................................value reference SS-Code, '00010010'B DEFINED in MAP-SS-Code : 30 cliRestrictionOption....................identifier of [2] CliRestrictionOption DEFINED in MAP-SS-DataTypes : 172 CliRestrictionOption....................type reference ENUMERATED DEFINED in MAP-SS-DataTypes : 175 USED in MAP-SS-DataTypes : 29 172 192 cliRestrictionOption....................identifier of CliRestrictionOption DEFINED in MAP-SS-DataTypes : 192 clir-invoked............................identifier of Named Number, 0 DEFINED in MAP-SS-DataTypes : 319 cnap....................................value reference SS-Code, '00011001'B DEFINED in MAP-SS-Code : 42 codec-Info..............................identifier of CODEC-Info DEFINED in MAP-GR-DataTypes : 52 CODEC-Info..............................type reference OCTET STRING DEFINED in MAP-GR-DataTypes : 95 USED in MAP-GR-DataTypes : 52 collectedInfo...........................identifier of Named Number, 2 DEFINED in MAP-MS-DataTypes : 1432 colp....................................value reference SS-Code, '00010011'B DEFINED in MAP-SS-Code : 32 colr....................................value reference SS-Code, '00010100'B DEFINED in MAP-SS-Code : 34 completed...............................identifier of Named Number, 3 DEFINED in MAP-SS-DataTypes : 289 completeDataListIncluded................identifier of NULL DEFINED in MAP-MS-DataTypes : 806 completeDataListIncluded................identifier of NULL DEFINED in MAP-MS-DataTypes : 912 Component...............................type reference CHOICE DEFINED in TCAPMessages : 124 USED in TCAPMessages : 47 115 ComponentPortion........................type reference [APPLICATION 12] IMPLICIT SEQUENCE OF
2708
3GPP
2709 Release 4
9189 9190 9191 9192 9193 9194 9195
969
: : 115 59 63
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in TCAPMessages USED in TCAPMessages
67
72
components..............................identifier of ComponentPortion DEFINED in TCAPMessages : 59 components..............................identifier of ComponentPortion
2710
3GPP
2711 Release 4
9196 9197 9198 9199 9200 9201 9202 9203 9204 9205 9206 9207 9208 9209 9210 9211 9212 9213 9214 9215 9216 9217 9218 9219 9220 9221 9222 9223 9224 9225 9226 9227 9228 9229 9230 9231 9232 9233 9234 9235 9236 9237 9238 9239 9240 9241 9242 9243 9244 9245 9246 9247 9248 9249 9250 9251 9252 9253 9254 9255 9256 9257 9258 9259 9260 9261 9262 9263 9264 9265 9266 9267 9268 9269 9270 9271 9272
970
Cross Reference Listing for MAP-Protocol : 63
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 19
DEFINED in TCAPMessages
components..............................identifier of ComponentPortion DEFINED in TCAPMessages : 67 components..............................identifier of ComponentPortion DEFINED in TCAPMessages : 72 congestion..............................identifier of Named Number, 3 DEFINED in MAP-LCS-DataTypes : 370 congestion..............................identifier of Named Number, 0 DEFINED in MAP-ER-DataTypes : 365 ContextId...............................type reference INTEGER DEFINED in MAP-MS-DataTypes : 803 USED in MAP-MS-DataTypes : 791 1311 contextIdList...........................identifier of ContextIdList DEFINED in MAP-MS-DataTypes : 1308 ContextIdList...........................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1310 USED in MAP-MS-DataTypes : 1308 Continue................................type reference SEQUENCE DEFINED in TCAPMessages : 69 USED in TCAPMessages : 55 continueCall............................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 1515 continueTransaction.....................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 849 continueTransaction.....................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 1572 continue-ME.............................identifier of [APPLICATION 5] IMPLICIT Continue DEFINED in TCAPMessages : 55 controllingMSC..........................identifier of Named Number, 4 DEFINED in MAP-CommonDataTypes : 356 csiActive...............................identifier of [2] NULL DEFINED in MAP-MS-DataTypes : 1406 csi-Active..............................identifier of [4] NULL DEFINED in MAP-MS-DataTypes : 825 csi-Active..............................identifier of [4] NULL DEFINED in MAP-MS-DataTypes : 1348 csi-Active..............................identifier of [1] NULL DEFINED in MAP-MS-DataTypes : 1376 csi-Active..............................identifier of [4] NULL DEFINED in MAP-MS-DataTypes : 1540 csi-Active..............................identifier of [3] NULL DEFINED in MAP-MS-DataTypes : 1585 csi-Active..............................identifier of [2] NULL DEFINED in MAP-MS-DataTypes : 1614 cs-AllocationRetentionPriority..........identifier of [29] CS-AllocationRetentionPriority DEFINED in MAP-MS-DataTypes : 751 CS-AllocationRetentionPriority..........type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 758 USED in MAP-MS-DataTypes : 751 cug.....................................value reference SS-Code, '01100001'B DEFINED in MAP-SS-Code : 96
2712
3GPP
2713 Release 4
9273 9274 9275 9276 9277 9278 9279
971
3GPP TS 29.002 V4.17.0 (2006-06)
cugIC-CallBarred........................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 1126 cugOG-CallBarred........................identifier of Named Number, 2 DEFINED in MAP-MS-DataTypes : 1127 cugSubscriptionFlag.....................identifier of [6] NULL
2714
3GPP
2715 Release 4
9280 9281 9282 9283 9284 9285 9286 9287 9288 9289 9290 9291 9292 9293 9294 9295 9296 9297 9298 9299 9300 9301 9302 9303 9304 9305 9306 9307 9308 9309 9310 9311 9312 9313 9314 9315 9316 9317 9318 9319 9320 9321 9322 9323 9324 9325 9326 9327 9328 9329 9330 9331 9332 9333 9334 9335 9336 9337 9338 9339 9340 9341 9342 9343 9344 9345 9346 9347 9348 9349 9350 9351 9352 9353 9354 9355 9356
972
Cross Reference Listing for MAP-Protocol : 152
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 20
DEFINED in MAP-CH-DataTypes
CUG-CheckInfo...........................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 86 USED in MAP-CH-DataTypes : 96 151 229 cug-CheckInfo...........................identifier of [1] CUG-CheckInfo DEFINED in MAP-CH-DataTypes : 96 cug-CheckInfo...........................identifier of [3] CUG-CheckInfo DEFINED in MAP-CH-DataTypes : 151 cug-CheckInfo...........................identifier of [4] CUG-CheckInfo DEFINED in MAP-CH-DataTypes : 229 CUG-Feature.............................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1139 USED in MAP-MS-DataTypes : 1132 cug-FeatureList.........................identifier of CUG-FeatureList DEFINED in MAP-MS-DataTypes : 1104 CUG-FeatureList.........................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1131 USED in MAP-MS-DataTypes : 1104 cug-Index...............................identifier of CUG-Index DEFINED in MAP-MS-DataTypes : 1112 CUG-Index...............................type reference INTEGER DEFINED in MAP-MS-DataTypes : 1119 USED in MAP-MS-DataTypes : 76 1112 1141 cug-Info................................identifier of [2] CUG-Info DEFINED in MAP-MS-DataTypes : 1023 CUG-Info................................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1102 USED in MAP-MS-DataTypes : 77 1023 cug-Interlock...........................identifier of CUG-Interlock DEFINED in MAP-MS-DataTypes : 1113 CUG-Interlock...........................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 1122 USED in MAP-MS-DataTypes : 78 1113 USED in MAP-CH-DataTypes : 42 87 cug-Interlock...........................identifier of CUG-Interlock DEFINED in MAP-CH-DataTypes : 87 cug-OutgoingAccess......................identifier of NULL DEFINED in MAP-CH-DataTypes : 88 cug-Reject..............................value reference CUG-Reject, CHOICE VALUE DEFINED in MAP-Protocol : 385 CUG-Reject..............................type reference ERROR DEFINED in MAP-Errors : 312 USED in MAP-Protocol : 142 385 USED in MAP-CallHandlingOperat : 46 100 USED in MAP-Errors : 52 cug-RejectCause.........................identifier of CUG-RejectCause DEFINED in MAP-ER-DataTypes : 120 CUG-RejectCause.........................type reference ENUMERATED DEFINED in MAP-ER-DataTypes : 124 USED in MAP-ER-DataTypes : 120 cug-RejectParam.........................identifier of CUG-RejectParam DEFINED in MAP-Errors : 314 CUG-RejectParam.........................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 119
2716
3GPP
2717 Release 4
9357 9358 9359 9360 9361 9362 9363
973
131 314 : 16
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-Errors : USED in MAP-ER-DataTypes
CUG-Subscription........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1111 USED in MAP-MS-DataTypes : 1109
2718
3GPP
2719 Release 4
9364 9365 9366 9367 9368 9369 9370 9371 9372 9373 9374 9375 9376 9377 9378 9379 9380 9381 9382 9383 9384 9385 9386 9387 9388 9389 9390 9391 9392 9393 9394 9395 9396 9397 9398 9399 9400 9401 9402 9403 9404 9405 9406 9407 9408 9409 9410 9411 9412 9413 9414 9415 9416 9417 9418 9419 9420 9421 9422 9423 9424 9425 9426 9427 9428 9429 9430 9431 9432 9433 9434 9435 9436 9437 9438 9439 9440
974
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 21
cug-SubscriptionList....................identifier of CUG-SubscriptionList DEFINED in MAP-MS-DataTypes : 1103 CUG-SubscriptionList....................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1108 USED in MAP-MS-DataTypes : 1103 currentLocation.........................identifier of [3] NULL DEFINED in MAP-MS-DataTypes : 1765 currentLocation.........................identifier of Named Number, 0 DEFINED in MAP-LCS-DataTypes : 115 currentLocationRetrieved................identifier of [8] NULL DEFINED in MAP-MS-DataTypes : 1780 currentOrLastKnownLocation..............identifier of Named Number, 1 DEFINED in MAP-LCS-DataTypes : 116 currentPassword.........................identifier of Password DEFINED in MAP-SupplementaryServi : 238 currentSecurityContext..................identifier of [2] CurrentSecurityContext DEFINED in MAP-MS-DataTypes : 312 CurrentSecurityContext..................type reference CHOICE DEFINED in MAP-MS-DataTypes : 342 USED in MAP-MS-DataTypes : 312 cw......................................value reference SS-Code, '01000001'B DEFINED in MAP-SS-Code : 75 dataCDA-1200bps.........................value reference BearerServiceCode, '00010010'B DEFINED in MAP-BS-Code : 53 dataCDA-1200-75bps......................value reference BearerServiceCode, '00010011'B DEFINED in MAP-BS-Code : 54 dataCDA-2400bps.........................value reference BearerServiceCode, '00010100'B DEFINED in MAP-BS-Code : 55 dataCDA-300bps..........................value reference BearerServiceCode, '00010001'B DEFINED in MAP-BS-Code : 52 dataCDA-4800bps.........................value reference BearerServiceCode, '00010101'B DEFINED in MAP-BS-Code : 56 dataCDA-9600bps.........................value reference BearerServiceCode, '00010110'B DEFINED in MAP-BS-Code : 57 dataCDS-1200bps.........................value reference BearerServiceCode, '00011010'B DEFINED in MAP-BS-Code : 61 dataCDS-2400bps.........................value reference BearerServiceCode, '00011100'B DEFINED in MAP-BS-Code : 62 dataCDS-4800bps.........................value reference BearerServiceCode, '00011101'B DEFINED in MAP-BS-Code : 63 dataCDS-9600bps.........................value reference BearerServiceCode, '00011110'B DEFINED in MAP-BS-Code : 64 dataCodingScheme........................identifier of [0] USSD-DataCodingScheme DEFINED in MAP-LCS-DataTypes : 153 dataMissing.............................value reference DataMissing, CHOICE VALUE DEFINED in MAP-Protocol : 332 DataMissing.............................type reference ERROR DEFINED in MAP-Errors : 170 USED in MAP-Protocol : 118 332 USED in MAP-MobileServiceOpera : 83 183 195 205 215 239 252 265 282 303 317 344 363 387 399 410 429 443 458 472 483 USED in MAP-OperationAndMainte : 24 58 72 83
2720
3GPP
2721 Release 4
9441 9442 9443 9444 9445 9446 9447
975
31 34 275 28 24 88 111 128 137 149 163 177 186 95 112 129 149 167 182 195 209 73 101 118 129 143 59 73 91
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-CallHandlingOperat : USED in MAP-SupplementaryServi : 224 247 258 USED in MAP-ShortMessageServic : USED in MAP-LocationServiceOpe : USED in MAP-Errors : 15
2722
3GPP
2723 Release 4
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 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
976
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 22
dataMissingParam........................identifier of DataMissingParam DEFINED in MAP-Errors : 172 DataMissingParam........................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 183 USED in MAP-Errors : 111 172 USED in MAP-ER-DataTypes : 21 dataPDS-2400bps.........................value reference BearerServiceCode, '00101100'B DEFINED in MAP-BS-Code : 77 dataPDS-4800bps.........................value reference BearerServiceCode, '00101101'B DEFINED in MAP-BS-Code : 78 dataPDS-9600bps.........................value reference BearerServiceCode, '00101110'B DEFINED in MAP-BS-Code : 79 deactivate..............................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 1964 deactivateSS............................value reference DeactivateSS, CHOICE VALUE DEFINED in MAP-Protocol : 250 DeactivateSS............................type reference OPERATION DEFINED in MAP-SupplementaryServi : 141 USED in MAP-Protocol : 72 250 USED in MAP-SupplementaryServi : 16 deactivateTraceMode.....................value reference DeactivateTraceMode, CHOICE VALUE DEFINED in MAP-Protocol : 227 DeactivateTraceMode.....................type reference OPERATION DEFINED in MAP-OperationAndMainte : 64 USED in MAP-Protocol : 47 227 USED in MAP-OperationAndMainte : 14 deactivateTraceModeArg..................identifier of DeactivateTraceModeArg DEFINED in MAP-OperationAndMainte : 66 DeactivateTraceModeArg..................type reference SEQUENCE DEFINED in MAP-OM-DataTypes : 54 USED in MAP-OperationAndMainte : 36 66 USED in MAP-OM-DataTypes : 16 deactivateTraceModeRes..................identifier of DeactivateTraceModeRes DEFINED in MAP-OperationAndMainte : 68 DeactivateTraceModeRes..................type reference SEQUENCE DEFINED in MAP-OM-DataTypes : 60 USED in MAP-OperationAndMainte : 37 68 USED in MAP-OM-DataTypes : 17 defaultCallHandling.....................identifier of DefaultCallHandling DEFINED in MAP-MS-DataTypes : 1367 defaultCallHandling.....................identifier of [1] DefaultCallHandling DEFINED in MAP-MS-DataTypes : 1424 DefaultCallHandling.....................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 1514 USED in MAP-MS-DataTypes : 71 1367 1424 1632 defaultCallHandling.....................identifier of [1] DefaultCallHandling DEFINED in MAP-MS-DataTypes : 1632 DefaultGPRS-Handling....................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 848 USED in MAP-MS-DataTypes : 843 defaultPriority.........................identifier of EMLPP-Priority DEFINED in MAP-CommonDataTypes : 439 defaultPriority.........................identifier of [7] EMLPP-Priority DEFINED in MAP-SS-DataTypes : 79
2724
3GPP
2725 Release 4
9525 9526 9527 9528 9529 9530 9531
977
3GPP TS 29.002 V4.17.0 (2006-06)
defaultPriority.........................identifier of EMLPP-Priority DEFINED in MAP-SS-DataTypes : 167 defaultPriority.........................identifier of [1] EMLPP-Priority DEFINED in MAP-SS-DataTypes : 195 defaultSessionHandling..................identifier of [3] DefaultGPRS-Handling
2726
3GPP
2727 Release 4
9532 9533 9534 9535 9536 9537 9538 9539 9540 9541 9542 9543 9544 9545 9546 9547 9548 9549 9550 9551 9552 9553 9554 9555 9556 9557 9558 9559 9560 9561 9562 9563 9564 9565 9566 9567 9568 9569 9570 9571 9572 9573 9574 9575 9576 9577 9578 9579 9580 9581 9582 9583 9584 9585 9586 9587 9588 9589 9590 9591 9592 9593 9594 9595 9596 9597 9598 9599 9600 9601 9602 9603 9604 9605 9606 9607 9608
978
Cross Reference Listing for MAP-Protocol : 843
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 23
DEFINED in MAP-MS-DataTypes
defaultSMS-Handling.....................identifier of [3] DefaultSMS-Handling DEFINED in MAP-MS-DataTypes : 1558 DefaultSMS-Handling.....................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 1571 USED in MAP-MS-DataTypes : 1558 deferredLocationEventType...............identifier of [1] DeferredLocationEventType DEFINED in MAP-LCS-DataTypes : 112 DeferredLocationEventType...............type reference BIT STRING DEFINED in MAP-LCS-DataTypes : 125 USED in MAP-LCS-DataTypes : 112 349 deferredLocationEventType...............identifier of DeferredLocationEventType DEFINED in MAP-LCS-DataTypes : 349 deferredmt-lrData.......................identifier of [9] Deferredmt-lrData DEFINED in MAP-LCS-DataTypes : 329 Deferredmt-lrData.......................type reference SEQUENCE DEFINED in MAP-LCS-DataTypes : 348 USED in MAP-LCS-DataTypes : 329 deferredmt-lrResponse...................identifier of Named Number, 3 DEFINED in MAP-LCS-DataTypes : 361 deferredmt-lrResponseIndicator..........identifier of [3] NULL DEFINED in MAP-LCS-DataTypes : 221 delaytolerant...........................identifier of Named Number, 1 DEFINED in MAP-LCS-DataTypes : 197 deleted.................................identifier of Named Number, 6 DEFINED in MAP-SS-DataTypes : 292 deleteSubscriberData....................value reference DeleteSubscriberData, CHOICE VALUE DEFINED in MAP-Protocol : 213 DeleteSubscriberData....................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 403 USED in MAP-Protocol : 26 213 USED in MAP-MobileServiceOpera : 53 deleteSubscriberDataArg.................identifier of DeleteSubscriberDataArg DEFINED in MAP-MobileServiceOpera : 405 DeleteSubscriberDataArg.................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1271 USED in MAP-MobileServiceOpera : 138 405 USED in MAP-MS-DataTypes : 57 deleteSubscriberDataRes.................identifier of DeleteSubscriberDataRes DEFINED in MAP-MobileServiceOpera : 407 DeleteSubscriberDataRes.................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1325 USED in MAP-MobileServiceOpera : 139 407 USED in MAP-MS-DataTypes : 58 deliveryOutcomeIndicator................identifier of [3] NULL DEFINED in MAP-SM-DataTypes : 155 derivable...............................identifier of InvokeIdType DEFINED in TCAPMessages : 167 destinationNumberCriteria...............identifier of [0] DestinationNumberCriteria DEFINED in MAP-MS-DataTypes : 1451 DestinationNumberCriteria...............type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1464 USED in MAP-MS-DataTypes : 1451
2728
3GPP
2729 Release 4
9609 9610 9611 9612 9613 9614 9615
979
3GPP TS 29.002 V4.17.0 (2006-06)
destinationNumberLengthList.............identifier of [2] DestinationNumberLengthList DEFINED in MAP-MS-DataTypes : 1467 DestinationNumberLengthList.............type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1477 USED in MAP-MS-DataTypes : 1467
2730
3GPP
2731 Release 4
9616 9617 9618 9619 9620 9621 9622 9623 9624 9625 9626 9627 9628 9629 9630 9631 9632 9633 9634 9635 9636 9637 9638 9639 9640 9641 9642 9643 9644 9645 9646 9647 9648 9649 9650 9651 9652 9653 9654 9655 9656 9657 9658 9659 9660 9661 9662 9663 9664 9665 9666 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
980
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 24
destinationNumberList...................identifier of [1] DestinationNumberList DEFINED in MAP-MS-DataTypes : 1466 DestinationNumberList...................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1472 USED in MAP-MS-DataTypes : 1466 DestTransactionID.......................type reference [APPLICATION 9] IMPLICIT TransactionID DEFINED in TCAPMessages : 98 USED in TCAPMessages : 65 70 74 diagnosticInfo..........................identifier of SignalInfo DEFINED in MAP-ER-DataTypes : 153 dialledNumber...........................identifier of ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1364 dialoguePortion.........................identifier of DialoguePortion DEFINED in TCAPMessages : 58 dialoguePortion.........................identifier of DialoguePortion DEFINED in TCAPMessages : 62 dialoguePortion.........................identifier of DialoguePortion DEFINED in TCAPMessages : 66 dialoguePortion.........................identifier of DialoguePortion DEFINED in TCAPMessages : 71 dialoguePortion.........................identifier of DialoguePortion DEFINED in TCAPMessages : 77 DialoguePortion.........................type reference [APPLICATION 11] EXTERNAL DEFINED in TCAPMessages : 82 USED in TCAPMessages : 58 62 66 71 77 disallowedByLocalRegulatoryRequirements.identifier of Named Number, 4 DEFINED in MAP-ER-DataTypes : 354 doublyChargeableECT-Barred..............identifier of Named Number, 13 DEFINED in MAP-MS-DataTypes : 984 downlinkAttached........................identifier of [5] NULL DEFINED in MAP-GR-DataTypes : 119 dp-AnalysedInfoCriteriaList.............identifier of [0] DP-AnalysedInfoCriteriaList DEFINED in MAP-MS-DataTypes : 1344 DP-AnalysedInfoCriteriaList.............type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1358 USED in MAP-MS-DataTypes : 1344 DP-AnalysedInfoCriterium................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1363 USED in MAP-MS-DataTypes : 1359 dtid....................................identifier of DestTransactionID DEFINED in TCAPMessages : 65 dtid....................................identifier of DestTransactionID DEFINED in TCAPMessages : 70 dtid....................................identifier of DestTransactionID DEFINED in TCAPMessages : 74 dualCommunication.......................identifier of [7] NULL DEFINED in MAP-GR-DataTypes : 121 duplicateInvokeID.......................identifier of Named Number, 0 DEFINED in TCAPMessages : 183 d-csi...................................identifier of Named Number, 3 DEFINED in MAP-MS-DataTypes : 1296 d-CSI...................................identifier of [9] D-CSI
2732
3GPP
2733 Release 4
9693 9694 9695 9696 9697 9698 9699
981
: 1341
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-MS-DataTypes
D-CSI...................................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1343 USED in MAP-MS-DataTypes : 66 1341 1904 USED in MAP-CH-DataTypes : 44 237 279
2734
3GPP
2735 Release 4
9700 9701 9702 9703 9704 9705 9706 9707 9708 9709 9710 9711 9712 9713 9714 9715 9716 9717 9718 9719 9720 9721 9722 9723 9724 9725 9726 9727 9728 9729 9730 9731 9732 9733 9734 9735 9736 9737 9738 9739 9740 9741 9742 9743 9744 9745 9746 9747 9748 9749 9750 9751 9752 9753 9754 9755 9756 9757 9758 9759 9760 9761 9762 9763 9764 9765 9766 9767 9768 9769 9770 9771 9772 9773 9774 9775 9776
982
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 25
d-csi...................................identifier of Named Number, 8 DEFINED in MAP-MS-DataTypes : 1877 d-CSI...................................identifier of [2] D-CSI DEFINED in MAP-MS-DataTypes : 1904 d-csi...................................identifier of [12] D-CSI DEFINED in MAP-CH-DataTypes : 237 d-csi...................................identifier of [5] D-CSI DEFINED in MAP-CH-DataTypes : 279 ect.....................................value reference SS-Code, '00110001'B DEFINED in MAP-SS-Code : 66 eir.....................................identifier of Named Number, 6 DEFINED in MAP-CommonDataTypes : 358 ellipsoidArc............................identifier of Named Number, 6 DEFINED in MAP-LCS-DataTypes : 209 ellipsoidPoint..........................identifier of Named Number, 0 DEFINED in MAP-LCS-DataTypes : 203 ellipsoidPointWithAltitude..............identifier of Named Number, 4 DEFINED in MAP-LCS-DataTypes : 207 ellipsoidPointWithAltitudeAndUncertaintyidentifier of Named Number, 5 DEFINED in MAP-LCS-DataTypes : 208 ellipsoidPointWithUncertaintyCircle.....identifier of Named Number, 1 DEFINED in MAP-LCS-DataTypes : 204 ellipsoidPointWithUncertaintyEllipse....identifier of Named Number, 2 DEFINED in MAP-LCS-DataTypes : 205 emergencyCall...........................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 392 emergencyCallOrigination................identifier of Named Number, 0 DEFINED in MAP-LCS-DataTypes : 357 emergencyCallRelease....................identifier of Named Number, 1 DEFINED in MAP-LCS-DataTypes : 358 emergencyCalls..........................value reference TeleserviceCode, '00010010'B DEFINED in MAP-TS-Code : 42 emergencyServices.......................identifier of Named Number, 0 DEFINED in MAP-LCS-DataTypes : 142 emlpp...................................value reference SS-Code, '10100001'B DEFINED in MAP-SS-Code : 156 emlpp-Info..............................identifier of [4] EMLPP-Info DEFINED in MAP-MS-DataTypes : 1025 EMLPP-Info..............................type reference SEQUENCE DEFINED in MAP-CommonDataTypes : 437 USED in MAP-MS-DataTypes : 178 1025 USED in MAP-CommonDataTypes : 50 EMLPP-Priority..........................type reference INTEGER DEFINED in MAP-CommonDataTypes : 443 USED in MAP-CommonDataTypes : 51 438 439 449 450 451 452 453 454 455 USED in MAP-SS-DataTypes : 51 79 167 194 195 USED in MAP-GR-DataTypes : 25 56 enabling................................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 1497 encryptionAlgorithm.....................identifier of [1] ChosenEncryptionAlgorithm DEFINED in MAP-MS-DataTypes : 568
2736
3GPP
2737 Release 4
9777 9778 9779 9780 9781 9782 9783
983
3GPP TS 29.002 V4.17.0 (2006-06)
encryptionAlgorithms....................identifier of [1] PermittedEncryptionAlgorithms DEFINED in MAP-MS-DataTypes : 466 encryptionInfo..........................identifier of [1] EncryptionInformation DEFINED in MAP-MS-DataTypes : 447 encryptionInfo..........................identifier of [6] EncryptionInformation
2738
3GPP
2739 Release 4
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 9851 9852 9853 9854 9855 9856 9857 9858 9859 9860
984
Cross Reference Listing for MAP-Protocol : 508
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 26
DEFINED in MAP-MS-DataTypes
EncryptionInformation...................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 682 USED in MAP-MS-DataTypes : 447 508 End.....................................type reference SEQUENCE DEFINED in TCAPMessages : 65 USED in TCAPMessages : 54 end-ME..................................identifier of [APPLICATION 4] IMPLICIT End DEFINED in TCAPMessages : 54 enterNewPW..............................identifier of Named Number, 1 DEFINED in MAP-SS-DataTypes : 250 enterNewPW-Again........................identifier of Named Number, 2 DEFINED in MAP-SS-DataTypes : 251 enterPW.................................identifier of Named Number, 0 DEFINED in MAP-SS-DataTypes : 249 equipmentNotSM-Equipped.................identifier of Named Number, 2 DEFINED in MAP-ER-DataTypes : 145 equipmentProtocolError..................identifier of Named Number, 1 DEFINED in MAP-ER-DataTypes : 144 equipmentStatus.........................identifier of EquipmentStatus DEFINED in MAP-MobileServiceOpera : 384 EquipmentStatus.........................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 726 USED in MAP-MobileServiceOpera : 135 384 USED in MAP-MS-DataTypes : 50 eraseCC-Entry...........................value reference EraseCC-Entry, CHOICE VALUE DEFINED in MAP-Protocol : 259 EraseCC-Entry...........................type reference OPERATION DEFINED in MAP-SupplementaryServi : 268 USED in MAP-Protocol : 81 259 USED in MAP-SupplementaryServi : 25 eraseCC-EntryArg........................identifier of EraseCC-EntryArg DEFINED in MAP-SupplementaryServi : 270 EraseCC-EntryArg........................type reference SEQUENCE DEFINED in MAP-SS-DataTypes : 328 USED in MAP-SupplementaryServi : 72 270 USED in MAP-SS-DataTypes : 39 eraseCC-EntryRes........................identifier of EraseCC-EntryRes DEFINED in MAP-SupplementaryServi : 272 EraseCC-EntryRes........................type reference SEQUENCE DEFINED in MAP-SS-DataTypes : 333 USED in MAP-SupplementaryServi : 73 272 USED in MAP-SS-DataTypes : 40 eraseSS.................................value reference EraseSS, CHOICE VALUE DEFINED in MAP-Protocol : 248 EraseSS.................................type reference OPERATION DEFINED in MAP-SupplementaryServi : 104 USED in MAP-Protocol : 70 248 USED in MAP-SupplementaryServi : 14 errorCode...............................identifier of ERROR DEFINED in TCAPMessages : 158 USED in TCAPMessages : 159 errorundefined..........................identifier of Named Number, 1 DEFINED in MAP-LCS-DataTypes : 368
2740
3GPP
2741 Release 4
9861 9862 9863 9864 9865 9866 9867
985
3GPP TS 29.002 V4.17.0 (2006-06)
ets-300102-1............................identifier of Named Number, 4 DEFINED in MAP-CommonDataTypes : 222 ets-300356..............................identifier of Named Number, 1 DEFINED in MAP-CommonDataTypes : 233 eventMet................................identifier of [0] MM-Code
2742
3GPP
2743 Release 4
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 9911 9912 9913 9914 9915 9916 9917 9918 9919 9920 9921 9922 9923 9924 9925 9926 9927 9928 9929 9930 9931 9932 9933 9934 9935 9936 9937 9938 9939 9940 9941 9942 9943 9944
986
Cross Reference Listing for MAP-Protocol : 1989
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 27
DEFINED in MAP-MS-DataTypes
eventReportData.........................identifier of [1] EventReportData DEFINED in MAP-CH-DataTypes : 347 EventReportData.........................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 352 USED in MAP-CH-DataTypes : 347 extendedRoutingInfo.....................identifier of ExtendedRoutingInfo DEFINED in MAP-CH-DataTypes : 150 ExtendedRoutingInfo.....................type reference CHOICE DEFINED in MAP-CH-DataTypes : 262 USED in MAP-CH-DataTypes : 150 extensibleCallBarredParam...............identifier of ExtensibleCallBarredParam DEFINED in MAP-ER-DataTypes : 105 ExtensibleCallBarredParam...............type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 113 USED in MAP-ER-DataTypes : 105 extensibleSystemFailureParam............identifier of ExtensibleSystemFailureParam DEFINED in MAP-ER-DataTypes : 174 ExtensibleSystemFailureParam............type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 178 USED in MAP-ER-DataTypes : 174 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 216 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 223 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 261 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 267 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 279 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 286 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 292 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 303 extensionContainer......................identifier of [3] ExtensionContainer DEFINED in MAP-MS-DataTypes : 313 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 382 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 407 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 420 extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-MS-DataTypes : 427 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 439 extensionContainer......................identifier of [3] ExtensionContainer DEFINED in MAP-MS-DataTypes : 452
2744
3GPP
2745 Release 4
9945 9946 9947 9948 9949 9950 9951
987
3GPP TS 29.002 V4.17.0 (2006-06)
extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-MS-DataTypes : 467 extensionContainer......................identifier of [8] ExtensionContainer DEFINED in MAP-MS-DataTypes : 513 extensionContainer......................identifier of [4] ExtensionContainer
2746
3GPP
2747 Release 4
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 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
988
Cross Reference Listing for MAP-Protocol : 563
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 28
DEFINED in MAP-MS-DataTypes
extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-MS-DataTypes : 569 extensionContainer......................identifier of [5] ExtensionContainer DEFINED in MAP-MS-DataTypes : 607 extensionContainer......................identifier of [0] ExtensionContainer DEFINED in MAP-MS-DataTypes : 612 extensionContainer......................identifier of [0] ExtensionContainer DEFINED in MAP-MS-DataTypes : 621 extensionContainer......................identifier of [0] ExtensionContainer DEFINED in MAP-MS-DataTypes : 631 extensionContainer......................identifier of [0] ExtensionContainer DEFINED in MAP-MS-DataTypes : 635 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-MS-DataTypes : 700 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 713 extensionContainer......................identifier of [14] ExtensionContainer DEFINED in MAP-MS-DataTypes : 737 extensionContainer......................identifier of [21] ExtensionContainer DEFINED in MAP-MS-DataTypes : 797 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-MS-DataTypes : 811 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-MS-DataTypes : 817 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-MS-DataTypes : 823 extensionContainer......................identifier of [4] ExtensionContainer DEFINED in MAP-MS-DataTypes : 844 extensionContainer......................identifier of [3] ExtensionContainer DEFINED in MAP-MS-DataTypes : 908 extensionContainer......................identifier of [3] ExtensionContainer DEFINED in MAP-MS-DataTypes : 918 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 967 extensionContainer......................identifier of [0] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1031 extensionContainer......................identifier of [9] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1047 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1090 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1099 extensionContainer......................identifier of [0] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1105 extensionContainer......................identifier of [0] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1116 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1143 extensionContainer......................identifier of [5] ExtensionContainer
2748
3GPP
2749 Release 4
10029 10030 10031 10032 10033 10034 10035
989
: 1163
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-MS-DataTypes
extensionContainer......................identifier of [3] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1186 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1215
2750
3GPP
2751 Release 4
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 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
990
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 29
extensionContainer......................identifier of [0] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1244 extensionContainer......................identifier of [7] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1262 extensionContainer......................identifier of [6] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1282 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1327 extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1332 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1346 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1368 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1373 extensionContainer......................identifier of [0] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1384 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1402 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1425 extensionContainer......................identifier of [4] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1456 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1538 extensionContainer......................identifier of [4] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1559 extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1583 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1610 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1633 extensionContainer......................identifier of [3] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1653 extensionContainer......................identifier of [3] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1660 extensionContainer......................identifier of [3] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1669 extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1674 extensionContainer......................identifier of [3] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1683 extensionContainer......................identifier of [0] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1687 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1701 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1708
2752
3GPP
2753 Release 4
10113 10114 10115 10116 10117 10118 10119
991
3GPP TS 29.002 V4.17.0 (2006-06)
extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1725 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1731
2754
3GPP
2755 Release 4
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 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
992
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 30
extensionContainer......................identifier of [3] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1746 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1751 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1757 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1763 extensionContainer......................identifier of [4] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1775 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1830 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1835 extensionContainer......................identifier of [3] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1845 extensionContainer......................identifier of [7] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1856 extensionContainer......................identifier of [6] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1865 extensionContainer......................identifier of [0] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1882 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1890 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1898 extensionContainer......................identifier of [13] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1915 extensionContainer......................identifier of [5] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1925 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1932 extensionContainer......................identifier of [7] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1943 extensionContainer......................identifier of [6] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1953 extensionContainer......................identifier of [3] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1960 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1977 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1981 extensionContainer......................identifier of [6] ExtensionContainer DEFINED in MAP-MS-DataTypes : 1994 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-MS-DataTypes : 1998 extensionContainer......................identifier of [3] ExtensionContainer DEFINED in MAP-MS-DataTypes : 2010 extensionContainer......................identifier of [5] ExtensionContainer DEFINED in MAP-MS-DataTypes : 2019
2756
3GPP
2757 Release 4
10197 10198 10199 10200 10201 10202 10203
993
3GPP TS 29.002 V4.17.0 (2006-06)
extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-CommonDataTypes : 203 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-CommonDataTypes : 229 extensionContainer......................identifier of ExtensionContainer
2758
3GPP
2759 Release 4
10204 10205 10206 10207 10208 10209 10210 10211 10212 10213 10214 10215 10216 10217 10218 10219 10220 10221 10222 10223 10224 10225 10226 10227 10228 10229 10230 10231 10232 10233 10234 10235 10236 10237 10238 10239 10240 10241 10242 10243 10244 10245 10246 10247 10248 10249 10250 10251 10252 10253 10254 10255 10256 10257 10258 10259 10260 10261 10262 10263 10264 10265 10266 10267 10268 10269 10270 10271 10272 10273 10274 10275 10276 10277 10278 10279 10280
994
Cross Reference Listing for MAP-Protocol : 246
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 31
DEFINED in MAP-CommonDataTypes
extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-CommonDataTypes : 363 extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-CommonDataTypes : 380 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-CommonDataTypes : 440 extensionContainer......................identifier of [4] ExtensionContainer DEFINED in MAP-CommonDataTypes : 463 extensionContainer......................identifier of [4] ExtensionContainer DEFINED in MAP-OM-DataTypes : 41 extensionContainer......................identifier of [0] ExtensionContainer DEFINED in MAP-OM-DataTypes : 51 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-OM-DataTypes : 57 extensionContainer......................identifier of [0] ExtensionContainer DEFINED in MAP-OM-DataTypes : 61 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-CH-DataTypes : 89 extensionContainer......................identifier of [13] ExtensionContainer DEFINED in MAP-CH-DataTypes : 108 extensionContainer......................identifier of [0] ExtensionContainer DEFINED in MAP-CH-DataTypes : 158 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-CH-DataTypes : 180 extensionContainer......................identifier of [7] ExtensionContainer DEFINED in MAP-CH-DataTypes : 194 extensionContainer......................identifier of [11] ExtensionContainer DEFINED in MAP-CH-DataTypes : 209 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-CH-DataTypes : 221 extensionContainer......................identifier of [7] ExtensionContainer DEFINED in MAP-CH-DataTypes : 231 extensionContainer......................identifier of [3] ExtensionContainer DEFINED in MAP-CH-DataTypes : 243 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-CH-DataTypes : 253 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-CH-DataTypes : 259 extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-CH-DataTypes : 269 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-CH-DataTypes : 275 extensionContainer......................identifier of [7] ExtensionContainer DEFINED in MAP-CH-DataTypes : 289 extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-CH-DataTypes : 301 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-CH-DataTypes : 307 extensionContainer......................identifier of [1] ExtensionContainer
2760
3GPP
2761 Release 4
10281 10282 10283 10284 10285 10286 10287
995
: 312
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-CH-DataTypes
extensionContainer......................identifier of [3] ExtensionContainer DEFINED in MAP-CH-DataTypes : 319 extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-CH-DataTypes : 332
2762
3GPP
2763 Release 4
10288 10289 10290 10291 10292 10293 10294 10295 10296 10297 10298 10299 10300 10301 10302 10303 10304 10305 10306 10307 10308 10309 10310 10311 10312 10313 10314 10315 10316 10317 10318 10319 10320 10321 10322 10323 10324 10325 10326 10327 10328 10329 10330 10331 10332 10333 10334 10335 10336 10337 10338 10339 10340 10341 10342 10343 10344 10345 10346 10347 10348 10349 10350 10351 10352 10353 10354 10355 10356 10357 10358 10359 10360 10361 10362 10363 10364
996
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 32
extensionContainer......................identifier of [3] ExtensionContainer DEFINED in MAP-CH-DataTypes : 349 extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-CH-DataTypes : 354 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-CH-DataTypes : 360 extensionContainer......................identifier of [0] ExtensionContainer DEFINED in MAP-CH-DataTypes : 382 extensionContainer......................identifier of [6] ExtensionContainer DEFINED in MAP-CH-DataTypes : 392 extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-CH-DataTypes : 397 extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-CH-DataTypes : 418 extensionContainer......................identifier of [3] ExtensionContainer DEFINED in MAP-CH-DataTypes : 425 extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-CH-DataTypes : 430 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-CH-DataTypes : 434 extensionContainer......................identifier of [4] ExtensionContainer DEFINED in MAP-SS-DataTypes : 279 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-SS-DataTypes : 296 extensionContainer......................identifier of [6] ExtensionContainer DEFINED in MAP-SM-DataTypes : 57 extensionContainer......................identifier of [4] ExtensionContainer DEFINED in MAP-SM-DataTypes : 83 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-SM-DataTypes : 89 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-SM-DataTypes : 111 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-SM-DataTypes : 117 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-SM-DataTypes : 125 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-SM-DataTypes : 130 extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-SM-DataTypes : 150 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-SM-DataTypes : 174 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-SM-DataTypes : 186 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-SM-DataTypes : 209 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-SM-DataTypes : 213 extensionContainer......................identifier of [4] ExtensionContainer DEFINED in MAP-GR-DataTypes : 58
2764
3GPP
2765 Release 4
10365 10366 10367 10368 10369 10370 10371
997
3GPP TS 29.002 V4.17.0 (2006-06)
extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-GR-DataTypes : 63 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-GR-DataTypes : 68
2766
3GPP
2767 Release 4
10372 10373 10374 10375 10376 10377 10378 10379 10380 10381 10382 10383 10384 10385 10386 10387 10388 10389 10390 10391 10392 10393 10394 10395 10396 10397 10398 10399 10400 10401 10402 10403 10404 10405 10406 10407 10408 10409 10410 10411 10412 10413 10414 10415 10416 10417 10418 10419 10420 10421 10422 10423 10424 10425 10426 10427 10428 10429 10430 10431 10432 10433 10434 10435 10436 10437 10438 10439 10440 10441 10442 10443 10444 10445 10446 10447 10448
998
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 33
extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-GR-DataTypes : 72 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-GR-DataTypes : 82 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-GR-DataTypes : 90 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-LCS-DataTypes : 68 extensionContainer......................identifier of [2] ExtensionContainer DEFINED in MAP-LCS-DataTypes : 74 extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-LCS-DataTypes : 81 extensionContainer......................identifier of [8] ExtensionContainer DEFINED in MAP-LCS-DataTypes : 99 extensionContainer......................identifier of [4] ExtensionContainer DEFINED in MAP-LCS-DataTypes : 175 extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-LCS-DataTypes : 218 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-LCS-DataTypes : 384 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 95 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 115 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 121 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 154 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 161 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 180 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 184 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 188 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 192 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 197 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 201 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 215 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 219 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 223 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 227
2768
3GPP
2769 Release 4
10449 10450 10451 10452 10453 10454 10455
999
3GPP TS 29.002 V4.17.0 (2006-06)
extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 231 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 235 extensionContainer......................identifier of ExtensionContainer
2770
3GPP
2771 Release 4
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 10512 10513 10514 10515 10516 10517 10518 10519 10520 10521 10522 10523 10524 10525 10526 10527 10528 10529 10530 10531 10532
1000
Cross Reference Listing for MAP-Protocol : 239
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 34
DEFINED in MAP-ER-DataTypes
extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 243 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 247 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 266 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 272 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 276 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 280 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 284 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 288 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 292 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 296 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 300 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 304 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 308 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 312 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 319 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 323 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 327 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 331 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 341 extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-ER-DataTypes : 346 extensionContainer......................identifier of [1] ExtensionContainer DEFINED in MAP-ER-DataTypes : 361 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 379 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 383 extensionContainer......................identifier of ExtensionContainer DEFINED in MAP-ER-DataTypes : 388 ExtensionContainer......................type reference SEQUENCE
2772
3GPP
2773 Release 4
10533 10534 10535 10536 10537 10538 10539
1001
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-ExtensionDataTypes : 33 USED in MAP-MS-DataTypes : 194 216 223 261 267 279 286 292 303 313 382 407 420 427 439 452 467 513 563 569 607 612 621 631 635 700 713 737 797 811 817 823 844 908 918 967 1031 1047 1090 1099 1105 1116 1143 1163 1186 1215 1244 1262 1282 1327 1332 1346 1368 1373
2774
3GPP
2775 Release 4
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 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
1002
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 35
1384 1402 1425 1456 1538 1559 1583 1610 1633 1653 1660 1669 1674 1683 1687 1701 1708 1725 1731 1746 1751 1757 1763 1775 1830 1835 1845 1856 1865 1882 1890 1898 1915 1925 1932 1943 1953 1960 1977 1981 1994 1998 2010 2019 USED in MAP-CommonDataTypes : 81 203 229 246 363 380 440 463 USED in MAP-OM-DataTypes : 27 41 51 57 61 USED in MAP-CH-DataTypes : 79 89 108 158 180 194 209 221 231 243 253 259 269 275 289 301 307 312 319 332 349 354 360 382 392 397 418 425 430 434 USED in MAP-SS-DataTypes : 60 279 296 USED in MAP-SM-DataTypes : 46 57 83 89 111 117 125 130 150 174 186 209 213 USED in MAP-GR-DataTypes : 42 58 63 68 72 82 90 USED in MAP-LCS-DataTypes : 41 68 74 81 99 175 218 384 USED in MAP-ER-DataTypes : 87 95 115 121 154 161 180 184 188 192 197 201 215 219 223 227 231 235 239 243 247 266 272 276 280 284 288 292 296 300 304 308 312 319 323 327 331 341 346 361 379 383 388 USED in MAP-ExtensionDataTypes : 16 ExtensionSet.............information object set reference MAP-EXTENSION, Information Object Set DEFINED in MAP-ExtensionDataTypes : 54 USED in MAP-ExtensionDataTypes : 48 50 externalAddress.........................identifier of [0] AddressString DEFINED in MAP-CommonDataTypes : 379 ExternalClient..........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1209 USED in MAP-MS-DataTypes : 1195 1205 externalClientList......................identifier of [1] ExternalClientList DEFINED in MAP-MS-DataTypes : 1179 ExternalClientList......................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1194 USED in MAP-MS-DataTypes : 1179 ExternalSignalInfo......................type reference SEQUENCE DEFINED in MAP-CommonDataTypes : 198 USED in MAP-CommonDataTypes : 21 USED in MAP-CH-DataTypes : 66 105 203 204 282 283 286 287 288 305 306 311 387 USED in MAP-SS-DataTypes : 54 314 315 extId...................................identifier of InformationObjectClassFieldType DEFINED in MAP-ExtensionDataTypes : 47 extType.................................identifier of InformationObjectClassFieldType DEFINED in MAP-ExtensionDataTypes : 49 Ext-BasicServiceCode....................type reference CHOICE DEFINED in MAP-CommonDataTypes : 433 USED in MAP-MS-DataTypes : 176 1038 1097 1135 1140 1321 1481 1937 1948 USED in MAP-CommonDataTypes : 49 USED in MAP-CH-DataTypes : 70 104 155 226 Ext-BasicServiceGroupList...............type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1134 USED in MAP-MS-DataTypes : 1115 1162 ext-BearerService.......................identifier of [2] Ext-BearerServiceCode DEFINED in MAP-CommonDataTypes : 434 Ext-BearerServiceCode...................type reference OCTET STRING DEFINED in MAP-BS-Code : 25 USED in MAP-MS-DataTypes : 153 955 USED in MAP-CommonDataTypes : 71 434 Ext-CallBarFeatureList..................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1093 USED in MAP-MS-DataTypes : 1089 1886 2015
2776
3GPP
2777 Release 4
10617 10618 10619 10620 10621 10622 10623
1003
3GPP TS 29.002 V4.17.0 (2006-06)
Ext-CallBarInfo.........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1087 USED in MAP-MS-DataTypes : 1022 Ext-CallBarringFeature..................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1096
2778
3GPP
2779 Release 4
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 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
1004
Cross Reference Listing for MAP-Protocol : 1094
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 36
USED in MAP-MS-DataTypes
Ext-CallBarringInfoFor-CSE..............type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 2013 USED in MAP-MS-DataTypes : 1973 2003 ext-externalClientList..................identifier of [4] Ext-ExternalClientList DEFINED in MAP-MS-DataTypes : 1188 Ext-ExternalClientList..................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1204 USED in MAP-MS-DataTypes : 1188 Ext-ExternalSignalInfo..................type reference SEQUENCE DEFINED in MAP-CommonDataTypes : 224 USED in MAP-CommonDataTypes : 22 USED in MAP-CH-DataTypes : 67 113 214 Ext-ForwardingInfoFor-CSE...............type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 2006 USED in MAP-MS-DataTypes : 1972 2002 Ext-ForwFeature.........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1037 USED in MAP-MS-DataTypes : 1035 Ext-ForwFeatureList.....................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1034 USED in MAP-MS-DataTypes : 1030 1880 2008 Ext-ForwInfo............................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1028 USED in MAP-MS-DataTypes : 1021 Ext-ForwOptions.........................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 1051 USED in MAP-MS-DataTypes : 1045 Ext-GeographicalInformation.............type reference OCTET STRING DEFINED in MAP-LCS-DataTypes : 234 USED in MAP-LCS-DataTypes : 22 216 324 Ext-NoRepCondTime.......................type reference INTEGER DEFINED in MAP-MS-DataTypes : 1080 USED in MAP-MS-DataTypes : 1046 1941 ext-ProtocolId..........................identifier of Ext-ProtocolId DEFINED in MAP-CommonDataTypes : 225 Ext-ProtocolId..........................type reference ENUMERATED DEFINED in MAP-CommonDataTypes : 232 USED in MAP-CommonDataTypes : 225 ext-QoS-Subscribed......................identifier of [0] Ext-QoS-Subscribed DEFINED in MAP-MS-DataTypes : 799 Ext-QoS-Subscribed......................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 885 USED in MAP-MS-DataTypes : 59 799 Ext-SS-Data.............................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1158 USED in MAP-MS-DataTypes : 1024 Ext-SS-Info.............................type reference CHOICE DEFINED in MAP-MS-DataTypes : 1020 USED in MAP-MS-DataTypes : 1018 Ext-SS-InfoFor-CSE......................type reference CHOICE DEFINED in MAP-MS-DataTypes : 2001 USED in MAP-MS-DataTypes : 1930 Ext-SS-InfoList.........................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1017 USED in MAP-MS-DataTypes : 938
2780
3GPP
2781 Release 4
10701 10702 10703 10704 10705 10706 10707
1005
3GPP TS 29.002 V4.17.0 (2006-06)
Ext-SS-Status...........................type reference OCTET STRING DEFINED in MAP-CommonDataTypes : 473 USED in MAP-MS-DataTypes : 184 1039 1098 1160 1173 1243 1938 1949 USED in MAP-CommonDataTypes : 55 460 ext-Teleservice.........................identifier of [3] Ext-TeleserviceCode
2782
3GPP
2783 Release 4
10708 10709 10710 10711 10712 10713 10714 10715 10716 10717 10718 10719 10720 10721 10722 10723 10724 10725 10726 10727 10728 10729 10730 10731 10732 10733 10734 10735 10736 10737 10738 10739 10740 10741 10742 10743 10744 10745 10746 10747 10748 10749 10750 10751 10752 10753 10754 10755 10756 10757 10758 10759 10760 10761 10762 10763 10764 10765 10766 10767 10768 10769 10770 10771 10772 10773 10774 10775 10776 10777 10778 10779 10780 10781 10782 10783 10784
1006
Cross Reference Listing for MAP-Protocol : 435
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 37
DEFINED in MAP-CommonDataTypes
Ext-TeleserviceCode.....................type reference OCTET STRING DEFINED in MAP-TS-Code : 20 USED in MAP-MS-DataTypes : 158 960 USED in MAP-CommonDataTypes : 65 435 USED in MAP-GR-DataTypes : 31 50 facilityNotSupParam.....................identifier of FacilityNotSupParam DEFINED in MAP-Errors : 184 FacilityNotSupParam.....................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 191 USED in MAP-Errors : 113 184 USED in MAP-ER-DataTypes : 23 facilityNotSupported....................value reference FacilityNotSupported, CHOICE VALUE DEFINED in MAP-Protocol : 334 FacilityNotSupported....................type reference ERROR DEFINED in MAP-Errors : 182 USED in MAP-Protocol : 120 334 USED in MAP-OperationAndMainte : 26 60 74 USED in MAP-CallHandlingOperat : 33 90 113 165 203 216 USED in MAP-SupplementaryServi : 55 266 USED in MAP-ShortMessageServic : 30 75 90 103 145 USED in MAP-LocationServiceOpe : 26 61 75 USED in MAP-Errors : 17 facsimileGroup3AndAlterSpeech...........value reference TeleserviceCode, '01100001'B DEFINED in MAP-TS-Code : 49 facsimileGroup4.........................value reference TeleserviceCode, '01100011'B DEFINED in MAP-TS-Code : 51 failure.................................identifier of Named Number, 1 DEFINED in MAP-CH-DataTypes : 373 failureCause............................identifier of FailureCause DEFINED in MAP-MS-DataTypes : 381 FailureCause............................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 410 USED in MAP-MS-DataTypes : 381 failureReport...........................value reference FailureReport, CHOICE VALUE DEFINED in MAP-Protocol : 312 FailureReport...........................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 450 USED in MAP-Protocol : 35 312 USED in MAP-MobileServiceOpera : 64 failureReportArg........................identifier of FailureReportArg DEFINED in MAP-MobileServiceOpera : 452 FailureReportArg........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1665 USED in MAP-MobileServiceOpera : 155 452 USED in MAP-MS-DataTypes : 123 failureReportRes........................identifier of FailureReportRes DEFINED in MAP-MobileServiceOpera : 454 FailureReportRes........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1672 USED in MAP-MobileServiceOpera : 156 454 USED in MAP-MS-DataTypes : 124 foreignNumberPortedToForeignNetwork.....identifier of Named Number, 2 DEFINED in MAP-CH-DataTypes : 171 forwardAccessSignalling.................value reference ForwardAccessSignalling, CHOICE VALUE DEFINED in MAP-Protocol : 194
2784
3GPP
2785 Release 4
10785 10786 10787 10788 10789 10790 10791
1007
3GPP TS 29.002 V4.17.0 (2006-06)
ForwardAccessSignalling.................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 333 USED in MAP-Protocol : 20 194 USED in MAP-MobileServiceOpera : 41 forwardAccessSignalling-Arg.............identifier of ForwardAccessSignalling-Arg DEFINED in MAP-MobileServiceOpera : 335
2786
3GPP
2787 Release 4
10792 10793 10794 10795 10796 10797 10798 10799 10800 10801 10802 10803 10804 10805 10806 10807 10808 10809 10810 10811 10812 10813 10814 10815 10816 10817 10818 10819 10820 10821 10822 10823 10824 10825 10826 10827 10828 10829 10830 10831 10832 10833 10834 10835 10836 10837 10838 10839 10840 10841 10842 10843 10844 10845 10846 10847 10848 10849 10850 10851 10852 10853 10854 10855 10856 10857 10858 10859 10860 10861 10862 10863 10864 10865 10866 10867 10868
1008
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 38
ForwardAccessSignalling-Arg.............type reference [3] SEQUENCE DEFINED in MAP-MS-DataTypes : 444 USED in MAP-MobileServiceOpera : 125 335 USED in MAP-MS-DataTypes : 33 forwardCheckSS-Indication...............value reference ForwardCheckSS-Indication, CHOICE VALUE DEFINED in MAP-Protocol : 219 ForwardCheckSS-Indication...............type reference OPERATION DEFINED in MAP-MobileServiceOpera : 420 USED in MAP-Protocol : 28 219 USED in MAP-MobileServiceOpera : 57 forwarded...............................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 1492 forwardedToNumber.......................identifier of [5] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1040 forwardedToNumber.......................identifier of [3] AddressString DEFINED in MAP-MS-DataTypes : 1939 forwardedToNumber.......................identifier of [5] ISDN-AddressString DEFINED in MAP-CH-DataTypes : 188 forwardedToNumber.......................identifier of [4] AddressString DEFINED in MAP-SS-DataTypes : 75 forwardedToNumber.......................identifier of [5] ISDN-AddressString DEFINED in MAP-SS-DataTypes : 102 forwardedToSubaddress...................identifier of [8] ISDN-SubaddressString DEFINED in MAP-MS-DataTypes : 1044 forwardedToSubaddress...................identifier of [4] ISDN-SubaddressString DEFINED in MAP-MS-DataTypes : 1940 forwardedToSubaddress...................identifier of [4] ISDN-SubaddressString DEFINED in MAP-CH-DataTypes : 192 forwardedToSubaddress...................identifier of [6] ISDN-SubaddressString DEFINED in MAP-SS-DataTypes : 76 forwardedToSubaddress...................identifier of [8] ISDN-SubaddressString DEFINED in MAP-SS-DataTypes : 103 forwardGroupCallSignalling..............value reference ForwardGroupCallSignalling, CHOICE VALUE DEFINED in MAP-Protocol : 299 ForwardGroupCallSignalling..............type reference OPERATION DEFINED in MAP-Group-Call-Operati : 67 USED in MAP-Protocol : 101 299 USED in MAP-Group-Call-Operati : 15 forwardGroupCallSignallingArg...........identifier of ForwardGroupCallSignallingArg DEFINED in MAP-Group-Call-Operati : 69 ForwardGroupCallSignallingArg...........type reference SEQUENCE DEFINED in MAP-GR-DataTypes : 75 USED in MAP-Group-Call-Operati : 35 69 USED in MAP-GR-DataTypes : 18 forwarding..............................identifier of Named Number, 1 DEFINED in MAP-CH-DataTypes : 123 forwardingData..........................identifier of ForwardingData DEFINED in MAP-CH-DataTypes : 185 ForwardingData..........................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 187 USED in MAP-CH-DataTypes : 185 227 267 forwardingData..........................identifier of [2] ForwardingData DEFINED in MAP-CH-DataTypes : 227
2788
3GPP
2789 Release 4
10869 10870 10871 10872 10873 10874 10875
1009
3GPP TS 29.002 V4.17.0 (2006-06)
forwardingData..........................identifier of ForwardingData DEFINED in MAP-CH-DataTypes : 267 forwardingFailed........................value reference ForwardingFailed, CHOICE VALUE DEFINED in MAP-Protocol : 382
2790
3GPP
2791 Release 4
10876 10877 10878 10879 10880 10881 10882 10883 10884 10885 10886 10887 10888 10889 10890 10891 10892 10893 10894 10895 10896 10897 10898 10899 10900 10901 10902 10903 10904 10905 10906 10907 10908 10909 10910 10911 10912 10913 10914 10915 10916 10917 10918 10919 10920 10921 10922 10923 10924 10925 10926 10927 10928 10929 10930 10931 10932 10933 10934 10935 10936 10937 10938 10939 10940 10941 10942 10943 10944 10945 10946 10947 10948 10949 10950 10951 10952
1010
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 39
ForwardingFailed........................type reference ERROR DEFINED in MAP-Errors : 307 USED in MAP-Protocol : 141 382 USED in MAP-CallHandlingOperat : 45 125 USED in MAP-Errors : 51 forwardingFailedParam...................identifier of ForwardingFailedParam DEFINED in MAP-Errors : 309 ForwardingFailedParam...................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 279 USED in MAP-Errors : 130 309 USED in MAP-ER-DataTypes : 38 ForwardingFeature.......................type reference SEQUENCE DEFINED in MAP-SS-DataTypes : 99 USED in MAP-SS-DataTypes : 97 forwardingFeatureList...................identifier of Ext-ForwFeatureList DEFINED in MAP-MS-DataTypes : 1030 forwardingFeatureList...................identifier of Ext-ForwFeatureList DEFINED in MAP-MS-DataTypes : 1880 forwardingFeatureList...................identifier of [1] Ext-ForwFeatureList DEFINED in MAP-MS-DataTypes : 2008 forwardingFeatureList...................identifier of ForwardingFeatureList DEFINED in MAP-SS-DataTypes : 92 ForwardingFeatureList...................type reference SEQUENCE OF DEFINED in MAP-SS-DataTypes : 95 USED in MAP-SS-DataTypes : 92 218 forwardingFeatureList...................identifier of [3] ForwardingFeatureList DEFINED in MAP-SS-DataTypes : 218 forwardingInfo..........................identifier of [0] Ext-ForwInfo DEFINED in MAP-MS-DataTypes : 1021 forwardingInfo..........................identifier of [0] ForwardingInfo DEFINED in MAP-SS-DataTypes : 86 ForwardingInfo..........................type reference SEQUENCE DEFINED in MAP-SS-DataTypes : 90 USED in MAP-SS-DataTypes : 86 forwardingInfoFor-CSE...................identifier of [0] Ext-ForwardingInfoFor-CSE DEFINED in MAP-MS-DataTypes : 1972 forwardingInfoFor-CSE...................identifier of [0] Ext-ForwardingInfoFor-CSE DEFINED in MAP-MS-DataTypes : 2002 forwardingInterrogationRequired.........identifier of [4] NULL DEFINED in MAP-CH-DataTypes : 156 forwardingOptions.......................identifier of [6] Ext-ForwOptions DEFINED in MAP-MS-DataTypes : 1045 forwardingOptions.......................identifier of [6] ForwardingOptions DEFINED in MAP-CH-DataTypes : 193 forwardingOptions.......................identifier of [6] ForwardingOptions DEFINED in MAP-SS-DataTypes : 104 ForwardingOptions.......................type reference OCTET STRING DEFINED in MAP-SS-DataTypes : 124 USED in MAP-CH-DataTypes : 56 193 USED in MAP-SS-DataTypes : 31 104 forwardingReason........................identifier of [8] ForwardingReason DEFINED in MAP-CH-DataTypes : 103 ForwardingReason........................type reference ENUMERATED DEFINED in MAP-CH-DataTypes : 129
2792
3GPP
2793 Release 4
10953 10954 10955 10956 10957 10958 10959
1011
: 103
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-CH-DataTypes
forwardingViolation.....................value reference ForwardingViolation, CHOICE VALUE DEFINED in MAP-Protocol : 384 ForwardingViolation.....................type reference ERROR DEFINED in MAP-Errors : 302
2794
3GPP
2795 Release 4
10960 10961 10962 10963 10964 10965 10966 10967 10968 10969 10970 10971 10972 10973 10974 10975 10976 10977 10978 10979 10980 10981 10982 10983 10984 10985 10986 10987 10988 10989 10990 10991 10992 10993 10994 10995 10996 10997 10998 10999 11000 11001 11002 11003 11004 11005 11006 11007 11008 11009 11010 11011 11012 11013 11014 11015 11016 11017 11018 11019 11020 11021 11022 11023 11024 11025 11026 11027 11028 11029 11030 11031 11032 11033 11034 11035 11036
1012
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 40
USED in MAP-Protocol : 140 384 USED in MAP-CallHandlingOperat : 44 101 USED in MAP-Errors : 50 forwardingViolationParam................identifier of ForwardingViolationParam DEFINED in MAP-Errors : 304 ForwardingViolationParam................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 275 USED in MAP-Errors : 129 304 USED in MAP-ER-DataTypes : 37 freezeP-TMSI............................identifier of [1] NULL DEFINED in MAP-MS-DataTypes : 291 freezeTMSI..............................identifier of [0] NULL DEFINED in MAP-MS-DataTypes : 290 frozen..................................identifier of Named Number, 5 DEFINED in MAP-SS-DataTypes : 291 FTN-AddressString.......................type reference AddressString DEFINED in MAP-CommonDataTypes : 149 USED in MAP-MS-DataTypes : 167 1049 USED in MAP-CommonDataTypes : 19 USED in MAP-CH-DataTypes : 65 196 USED in MAP-SS-DataTypes : 47 107 generalProblem..........................identifier of [0] IMPLICIT GeneralProblem DEFINED in TCAPMessages : 170 GeneralProblem..........................type reference INTEGER DEFINED in TCAPMessages : 179 USED in TCAPMessages : 170 general-dataCDA.........................value reference BearerServiceCode, '00010111'B DEFINED in MAP-BS-Code : 58 general-dataCDS.........................value reference BearerServiceCode, '00011111'B DEFINED in MAP-BS-Code : 65 general-dataPDS.........................value reference BearerServiceCode, '00101111'B DEFINED in MAP-BS-Code : 80 general-padAccessCA.....................value reference BearerServiceCode, '00100111'B DEFINED in MAP-BS-Code : 74 GenericServiceInfo......................type reference SEQUENCE DEFINED in MAP-SS-DataTypes : 190 USED in MAP-SS-DataTypes : 219 genericServiceInfo......................identifier of [4] GenericServiceInfo DEFINED in MAP-SS-DataTypes : 219 geodeticInformation.....................identifier of [7] GeodeticInformation DEFINED in MAP-MS-DataTypes : 1779 GeodeticInformation.....................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 1797 USED in MAP-MS-DataTypes : 1779 geographicalInformation.................identifier of [0] GeographicalInformation DEFINED in MAP-MS-DataTypes : 1771 GeographicalInformation.................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 1787 USED in MAP-MS-DataTypes : 94 1771 getPassword.............................value reference GetPassword, CHOICE VALUE DEFINED in MAP-Protocol : 257 GetPassword.............................type reference OPERATION DEFINED in MAP-SupplementaryServi : 234 USED in MAP-Protocol : 78 257 USED in MAP-SupplementaryServi : 22 232
2796
3GPP
2797 Release 4
11037 11038 11039 11040 11041 11042 11043
1013
3GPP TS 29.002 V4.17.0 (2006-06)
ggsn-Address............................identifier of [1] GSN-Address DEFINED in MAP-MS-DataTypes : 1651 ggsn-Address............................identifier of [1] GSN-Address DEFINED in MAP-MS-DataTypes : 1658
2798
3GPP
2799 Release 4
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 11105 11106 11107 11108 11109 11110 11111 11112 11113 11114 11115 11116 11117 11118 11119 11120
1014
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 41
ggsn-Address............................identifier of [2] GSN-Address DEFINED in MAP-MS-DataTypes : 1668 ggsn-Address............................identifier of [0] GSN-Address DEFINED in MAP-MS-DataTypes : 1673 ggsn-Address............................identifier of [2] GSN-Address DEFINED in MAP-MS-DataTypes : 1682 ggsn-Number.............................identifier of [2] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1652 ggsn-Number.............................identifier of [1] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1667 GlobalCellId............................type reference OCTET STRING DEFINED in MAP-CommonDataTypes : 338 USED in MAP-MS-DataTypes : 174 501 602 USED in MAP-CommonDataTypes : 37 gmlc-List...............................identifier of [0] GMLC-List DEFINED in MAP-MS-DataTypes : 765 GMLC-List...............................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 770 USED in MAP-MS-DataTypes : 765 gmlc-List...............................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 1219 gmlc-ListWithdraw.......................identifier of [13] NULL DEFINED in MAP-MS-DataTypes : 1287 gmlc-Restriction........................identifier of [0] GMLC-Restriction DEFINED in MAP-MS-DataTypes : 1211 GMLC-Restriction........................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 1218 USED in MAP-MS-DataTypes : 1211 gmscCamelSubscriptionInfo...............identifier of [0] GmscCamelSubscriptionInfo DEFINED in MAP-CH-DataTypes : 268 GmscCamelSubscriptionInfo...............type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 272 USED in MAP-CH-DataTypes : 268 gmsc-Address............................identifier of [6] ISDN-AddressString DEFINED in MAP-CH-DataTypes : 101 gmsc-Address............................identifier of [8] ISDN-AddressString DEFINED in MAP-CH-DataTypes : 206 gprsAttach..............................identifier of Named Number, 5 DEFINED in MAP-MS-DataTypes : 396 gprsConnectionSuspended.................identifier of NULL DEFINED in MAP-ER-DataTypes : 314 GPRSDataList............................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 785 USED in MAP-MS-DataTypes : 810 gprsDataList............................identifier of [1] GPRSDataList DEFINED in MAP-MS-DataTypes : 810 gprsDetach..............................identifier of Named Number, 10 DEFINED in MAP-MS-DataTypes : 402 gprsEnhancementsSupportIndicator........identifier of [3] NULL DEFINED in MAP-MS-DataTypes : 430 gprsNodeIndicator.......................identifier of [5] NULL DEFINED in MAP-SM-DataTypes : 91
2800
3GPP
2801 Release 4
11121 11122 11123 11124 11125 11126 11127
1015
3GPP TS 29.002 V4.17.0 (2006-06)
gprsNodeIndicator.......................identifier of [2] NULL DEFINED in MAP-LCS-DataTypes : 83 gprsSubscriptionData....................identifier of [16] GPRSSubscriptionData DEFINED in MAP-MS-DataTypes : 741 GPRSSubscriptionData....................type reference SEQUENCE
2802
3GPP
2803 Release 4
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 11178 11179 11180 11181 11182 11183 11184 11185 11186 11187 11188 11189 11190 11191 11192 11193 11194 11195 11196 11197 11198 11199 11200 11201 11202 11203 11204
1016
Cross Reference Listing for MAP-Protocol : : 805 741
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 42
DEFINED in MAP-MS-DataTypes USED in MAP-MS-DataTypes
gprsSubscriptionDataWithdraw............identifier of [10] GPRSSubscriptionDataWithdraw DEFINED in MAP-MS-DataTypes : 1284 GPRSSubscriptionDataWithdraw............type reference CHOICE DEFINED in MAP-MS-DataTypes : 1306 USED in MAP-MS-DataTypes : 1284 gprsSubscriptionUnknown.................identifier of Named Number, 1 DEFINED in MAP-ER-DataTypes : 207 gprsSupportIndicator....................identifier of [7] NULL DEFINED in MAP-SM-DataTypes : 59 gprsSupportIndicator....................identifier of [2] NULL DEFINED in MAP-SM-DataTypes : 152 GPRS-CamelTDPData.......................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 839 USED in MAP-MS-DataTypes : 835 gprs-CamelTDPDataList...................identifier of [0] GPRS-CamelTDPDataList DEFINED in MAP-MS-DataTypes : 821 GPRS-CamelTDPDataList...................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 834 USED in MAP-MS-DataTypes : 821 gprs-CSI................................identifier of [0] GPRS-CSI DEFINED in MAP-MS-DataTypes : 815 GPRS-CSI................................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 820 USED in MAP-MS-DataTypes : 815 1911 gprs-csi................................identifier of Named Number, 7 DEFINED in MAP-MS-DataTypes : 1300 gprs-CSI................................identifier of Named Number, 4 DEFINED in MAP-MS-DataTypes : 1873 gprs-CSI................................identifier of [9] GPRS-CSI DEFINED in MAP-MS-DataTypes : 1911 gprs-TriggerDetectionPoint..............identifier of [0] GPRS-TriggerDetectionPoint DEFINED in MAP-MS-DataTypes : 840 GPRS-TriggerDetectionPoint..............type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 856 USED in MAP-MS-DataTypes : 840 greyListed..............................identifier of Named Number, 2 DEFINED in MAP-MS-DataTypes : 729 groupCallNumber.........................identifier of ISDN-AddressString DEFINED in MAP-GR-DataTypes : 62 groupId.................................identifier of GroupId DEFINED in MAP-MS-DataTypes : 1724 groupid.................................identifier of GroupId DEFINED in MAP-MS-DataTypes : 1729 GroupId.................................type reference TBCD-STRING DEFINED in MAP-MS-DataTypes : 1734 USED in MAP-MS-DataTypes : 1724 1729 groupKey................................identifier of [1] Kc DEFINED in MAP-GR-DataTypes : 55 groupKeyNumber..........................identifier of [0] GroupKeyNumber DEFINED in MAP-GR-DataTypes : 54
2804
3GPP
2805 Release 4
11205 11206 11207 11208 11209 11210 11211
1017
3GPP TS 29.002 V4.17.0 (2006-06)
GroupKeyNumber..........................type reference INTEGER DEFINED in MAP-GR-DataTypes : 93 USED in MAP-GR-DataTypes : 54 gsmSCF-Address..........................identifier of [2] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 842
2806
3GPP
2807 Release 4
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 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
1018
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 43
gsmSCF-Address..........................identifier of ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1366 gsmSCF-Address..........................identifier of ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1383 gsmSCF-Address..........................identifier of [0] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1423 gsmSCF-Address..........................identifier of [2] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1557 gsmSCF-Address..........................identifier of [0] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1582 gsmSCF-Address..........................identifier of [0] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1631 gsmSCF-Address..........................identifier of [3] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1829 gsmSCF-Address..........................identifier of [2] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1844 gsmSCF-Address..........................identifier of [1] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1921 gsm-0408................................identifier of Named Number, 1 DEFINED in MAP-CommonDataTypes : 218 gsm-0806................................identifier of Named Number, 2 DEFINED in MAP-CommonDataTypes : 219 gsm-BearerCapability....................identifier of [5] ExternalSignalInfo DEFINED in MAP-CH-DataTypes : 203 gsm-BearerCapability....................identifier of [0] ExternalSignalInfo DEFINED in MAP-CH-DataTypes : 282 gsm-BSSMAP..............................identifier of Named Number, 3 DEFINED in MAP-CommonDataTypes : 220 gsm-SecurityContextData.................identifier of [0] GSM-SecurityContextData DEFINED in MAP-MS-DataTypes : 343 GSM-SecurityContextData.................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 346 USED in MAP-MS-DataTypes : 343 GSN-Address.............................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 434 USED in MAP-MS-DataTypes : 30 419 1651 1657 1658 1668 1673 1681 1682 guidanceInfo............................identifier of GuidanceInfo DEFINED in MAP-SupplementaryServi : 236 GuidanceInfo............................type reference ENUMERATED DEFINED in MAP-SS-DataTypes : 248 USED in MAP-SupplementaryServi : 67 236 USED in MAP-SS-DataTypes : 25 handoverNumber..........................identifier of [0] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 556 handoverNumber..........................identifier of ISDN-AddressString DEFINED in MAP-MS-DataTypes : 657 highLayerCompatibility..................identifier of [6] ExternalSignalInfo DEFINED in MAP-CH-DataTypes : 288 hlr.....................................identifier of Named Number, 1 DEFINED in MAP-CommonDataTypes : 353 HLR-Id..................................type reference IMSI DEFINED in MAP-CommonDataTypes : 327
2808
3GPP
2809 Release 4
11289 11290 11291 11292 11293 11294 11295
1019
: 332
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-CommonDataTypes
hlr-List................................identifier of HLR-List DEFINED in MAP-MS-DataTypes : 1695 HLR-List................................type reference SEQUENCE OF DEFINED in MAP-CommonDataTypes : 331
2810
3GPP
2811 Release 4
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 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
1020
Cross Reference Listing for MAP-Protocol 171 1695 : 35
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 44
USED in MAP-MS-DataTypes : USED in MAP-CommonDataTypes
hlr-Number..............................identifier of ISDN-AddressString DEFINED in MAP-MS-DataTypes : 259 hlr-Number..............................identifier of ISDN-AddressString DEFINED in MAP-MS-DataTypes : 438 hlr-Number..............................identifier of ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1694 hlr-Number..............................identifier of ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1706 hold....................................value reference SS-Code, '01000010'B DEFINED in MAP-SS-Code : 77 home-Country............................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 1220 horizontal-accuracy.....................identifier of [0] Horizontal-Accuracy DEFINED in MAP-LCS-DataTypes : 172 Horizontal-Accuracy.....................type reference OCTET STRING DEFINED in MAP-LCS-DataTypes : 178 USED in MAP-LCS-DataTypes : 20 172 ho-NumberNotRequired....................identifier of NULL DEFINED in MAP-MS-DataTypes : 502 identity................................identifier of Identity DEFINED in MAP-MS-DataTypes : 265 Identity................................type reference CHOICE DEFINED in MAP-CommonDataTypes : 300 USED in MAP-MS-DataTypes : 173 265 USED in MAP-CommonDataTypes : 32 ik......................................identifier of IK DEFINED in MAP-MS-DataTypes : ik......................................identifier of IK DEFINED in MAP-MS-DataTypes : 338 353
IK......................................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 367 USED in MAP-MS-DataTypes : 338 353 illegalEquipment........................value reference IllegalEquipment, CHOICE VALUE DEFINED in MAP-Protocol : 352 IllegalEquipment........................type reference ERROR DEFINED in MAP-Errors : 234 USED in MAP-Protocol : 128 352 USED in MAP-SupplementaryServi : 52 199 213 USED in MAP-ShortMessageServic : 34 106 USED in MAP-LocationServiceOpe : 35 78 USED in MAP-Errors : 31 illegalEquipmentParam...................identifier of IllegalEquipmentParam DEFINED in MAP-Errors : 236 IllegalEquipmentParam...................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 226 USED in MAP-Errors : 119 236 USED in MAP-ER-DataTypes : 29 illegalSS-Operation.....................value reference IllegalSS-Operation, CHOICE VALUE DEFINED in MAP-Protocol : 404 IllegalSS-Operation.....................type reference ERROR DEFINED in MAP-Errors : 348 USED in MAP-Protocol : 144 404 USED in MAP-MobileServiceOpera : 100 271 288
2812
3GPP
2813 Release 4
11373 11374 11375 11376 11377 11378 11379
1021
40 100 117 134 154 172 261 278
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-SupplementaryServi : USED in MAP-Errors : 63
illegalSS-OperationParam................identifier of IllegalSS-OperationParam DEFINED in MAP-Errors : 350 IllegalSS-OperationParam................type reference SEQUENCE
2814
3GPP
2815 Release 4
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 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
1022
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 45
DEFINED in MAP-ER-DataTypes : 295 USED in MAP-Errors : 148 350 USED in MAP-ER-DataTypes : 56 illegalSubscriber.......................value reference IllegalSubscriber, CHOICE VALUE DEFINED in MAP-Protocol : 351 IllegalSubscriber.......................type reference ERROR DEFINED in MAP-Errors : 228 USED in MAP-Protocol : 127 351 USED in MAP-SupplementaryServi : 51 198 212 USED in MAP-ShortMessageServic : 33 105 USED in MAP-LocationServiceOpe : 36 77 USED in MAP-Errors : 30 illegalSubscriberParam..................identifier of IllegalSubscriberParam DEFINED in MAP-Errors : 230 IllegalSubscriberParam..................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 222 USED in MAP-Errors : 118 230 USED in MAP-ER-DataTypes : 28 imei....................................identifier of IMEI DEFINED in MAP-MobileServiceOpera : 382 IMEI....................................type reference TBCD-STRING DEFINED in MAP-CommonDataTypes : 320 USED in MAP-MobileServiceOpera : 167 382 USED in MAP-CommonDataTypes : 34 USED in MAP-LCS-DataTypes : 30 96 321 imei....................................identifier of [5] IMEI DEFINED in MAP-LCS-DataTypes : 96 imei....................................identifier of [2] IMEI DEFINED in MAP-LCS-DataTypes : 321 immediateResponsePreferred..............identifier of [1] NULL DEFINED in MAP-MS-DataTypes : 698 imsi....................................identifier of IMSI DEFINED in MAP-OperationAndMainte : 81
imsi....................................identifier of IMSI DEFINED in MAP-MS-DataTypes : 211 imsi....................................identifier of IMSI DEFINED in MAP-MS-DataTypes : 283 imsi....................................identifier of IMSI DEFINED in MAP-MS-DataTypes : 307 imsi....................................identifier of IMSI DEFINED in MAP-MS-DataTypes : 380 imsi....................................identifier of IMSI DEFINED in MAP-MS-DataTypes : 417 imsi....................................identifier of [4] IMSI DEFINED in MAP-MS-DataTypes : 506 imsi....................................identifier of [0] IMSI DEFINED in MAP-MS-DataTypes : 695 imsi....................................identifier of [0] IMSI DEFINED in MAP-MS-DataTypes : 735 imsi....................................identifier of [0] IMSI DEFINED in MAP-MS-DataTypes : 1272 imsi....................................identifier of [0] IMSI DEFINED in MAP-MS-DataTypes : 1650 imsi....................................identifier of [0] IMSI
2816
3GPP
2817 Release 4
11457 11458 11459 11460 11461 11462 11463
1023
: 1666
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-MS-DataTypes
imsi....................................identifier of [0] IMSI DEFINED in MAP-MS-DataTypes : 1680 imsi....................................identifier of IMSI DEFINED in MAP-MS-DataTypes : 1699
2818
3GPP
2819 Release 4
11464 11465 11466 11467 11468 11469 11470 11471 11472 11473 11474 11475 11476 11477 11478 11479 11480 11481 11482 11483 11484 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
1024
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 46
imsi....................................identifier of [0] IMSI DEFINED in MAP-MS-DataTypes : 1743 imsi....................................identifier of IMSI DEFINED in MAP-MS-DataTypes : 1970 imsi....................................identifier of [1] IMSI DEFINED in MAP-MS-DataTypes : 1990 IMSI....................................type reference TBCD-STRING DEFINED in MAP-CommonDataTypes : 297 USED in MAP-OperationAndMainte : 43 81 USED in MAP-MS-DataTypes : 169 211 283 307 380 417 506 695 735 1272 1650 1666 1680 1699 1743 1970 1990 USED in MAP-CommonDataTypes : 30 301 305 317 327 374 USED in MAP-OM-DataTypes : 22 37 55 USED in MAP-CH-DataTypes : 68 146 199 228 316 346 386 417 429 USED in MAP-SS-DataTypes : 48 270 USED in MAP-SM-DataTypes : 35 81 113 134 204 USED in MAP-GR-DataTypes : 24 67 76 USED in MAP-LCS-DataTypes : 31 93 320 imsi....................................identifier of IMSI DEFINED in MAP-CommonDataTypes : imsi....................................identifier of IMSI DEFINED in MAP-CommonDataTypes : 301 305
imsi....................................identifier of [0] IMSI DEFINED in MAP-CommonDataTypes : 317 imsi....................................identifier of [0] IMSI DEFINED in MAP-CommonDataTypes : 374 imsi....................................identifier of [0] IMSI DEFINED in MAP-OM-DataTypes : 37 imsi....................................identifier of [0] IMSI DEFINED in MAP-OM-DataTypes : 55 imsi....................................identifier of [9] IMSI DEFINED in MAP-CH-DataTypes : 146 imsi....................................identifier of [0] IMSI DEFINED in MAP-CH-DataTypes : 199 imsi....................................identifier of [3] IMSI DEFINED in MAP-CH-DataTypes : 228 imsi....................................identifier of [0] IMSI DEFINED in MAP-CH-DataTypes : 316 imsi....................................identifier of [0] IMSI DEFINED in MAP-CH-DataTypes : 346 imsi....................................identifier of [0] IMSI DEFINED in MAP-CH-DataTypes : 386 imsi....................................identifier of [0] IMSI DEFINED in MAP-CH-DataTypes : 417 imsi....................................identifier of [0] IMSI DEFINED in MAP-CH-DataTypes : 429 imsi....................................identifier of [0] IMSI DEFINED in MAP-SS-DataTypes : 270 imsi....................................identifier of IMSI DEFINED in MAP-SM-DataTypes : 81 imsi....................................identifier of IMSI DEFINED in MAP-SM-DataTypes : 113 imsi....................................identifier of [0] IMSI
2820
3GPP
2821 Release 4
11541 11542 11543 11544 11545 11546 11547
1025
: 134
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-SM-DataTypes
imsi....................................identifier of [0] IMSI DEFINED in MAP-SM-DataTypes : 204 imsi....................................identifier of IMSI DEFINED in MAP-GR-DataTypes : 67
2822
3GPP
2823 Release 4
11548 11549 11550 11551 11552 11553 11554 11555 11556 11557 11558 11559 11560 11561 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
1026
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 47
imsi....................................identifier of IMSI DEFINED in MAP-GR-DataTypes : 76 imsi....................................identifier of [2] IMSI DEFINED in MAP-LCS-DataTypes : 93 imsi....................................identifier of [1] IMSI DEFINED in MAP-LCS-DataTypes : 320 imsiDetach..............................identifier of Named Number, 0 DEFINED in MAP-ER-DataTypes : 252 imsiDetached............................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 1820 imsiUnknown.............................identifier of Named Number, 0 DEFINED in MAP-ER-DataTypes : 206 imsi-WithLMSI...........................identifier of IMSI-WithLMSI DEFINED in MAP-CommonDataTypes : 302 IMSI-WithLMSI...........................type reference SEQUENCE DEFINED in MAP-CommonDataTypes : 304 USED in MAP-CommonDataTypes : 302 incomingCallsBarredWithinCUG............identifier of Named Number, 0 DEFINED in MAP-ER-DataTypes : 125 incompatibleTerminal....................value reference IncompatibleTerminal, CHOICE VALUE DEFINED in MAP-Protocol : 335 IncompatibleTerminal....................type reference ERROR DEFINED in MAP-Errors : 188 USED in MAP-Protocol : 162 335 USED in MAP-CallHandlingOperat : 48 187 USED in MAP-Errors : 18 incompatibleTerminalParam...............identifier of IncompatibleTerminalParam DEFINED in MAP-Errors : 190 IncompatibleTerminalParam...............type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 330 USED in MAP-Errors : 138 190 USED in MAP-ER-DataTypes : 46 inconsistentMeasurementData.............identifier of Named Number, 3 DEFINED in MAP-ER-DataTypes : 368 incorrectTransactionPortion.............identifier of Named Number, 3 DEFINED in TCAPMessages : 106 informationNotAvailable.................value reference InformationNotAvailable, CHOICE VALUE DEFINED in MAP-Protocol : 395 InformationNotAvailable.................type reference ERROR DEFINED in MAP-Errors : 340 USED in MAP-Protocol : 169 395 USED in MAP-MobileServiceOpera : 105 273 292 USED in MAP-Errors : 60 informationNotAvailableParam............identifier of InformationNotAvailableParam DEFINED in MAP-Errors : 342 InformationNotAvailableParam............type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 307 USED in MAP-Errors : 151 342 USED in MAP-ER-DataTypes : 59 informPreviousNetworkEntity.............identifier of [11] NULL DEFINED in MAP-MS-DataTypes : 219 informPreviousNetworkEntity.............identifier of [1] NULL DEFINED in MAP-MS-DataTypes : 423
2824
3GPP
2825 Release 4
11625 11626 11627 11628 11629 11630 11631
1027
3GPP TS 29.002 V4.17.0 (2006-06)
informServiceCentre.....................value reference InformServiceCentre, CHOICE VALUE DEFINED in MAP-Protocol : 268 InformServiceCentre.....................type reference OPERATION DEFINED in MAP-ShortMessageServic : 132 USED in MAP-Protocol : 92 268 USED in MAP-ShortMessageServic : 18
2826
3GPP
2827 Release 4
11632 11633 11634 11635 11636 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 11697 11698 11699 11700 11701 11702 11703 11704 11705 11706 11707 11708
1028
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 48
informServiceCentreArg..................identifier of InformServiceCentreArg DEFINED in MAP-ShortMessageServic : 134 InformServiceCentreArg..................type reference SEQUENCE DEFINED in MAP-SM-DataTypes : 183 USED in MAP-ShortMessageServic : 54 134 USED in MAP-SM-DataTypes : 23 inhibiting..............................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 1496 initialLocation.........................identifier of Named Number, 2 DEFINED in MAP-LCS-DataTypes : 117 initiatingRelease.......................identifier of Named Number, 4 DEFINED in TCAPMessages : 187 insertSubscriberData....................value reference InsertSubscriberData, CHOICE VALUE DEFINED in MAP-Protocol : 212 InsertSubscriberData....................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 392 USED in MAP-Protocol : 25 212 USED in MAP-MobileServiceOpera : 52 insertSubscriberDataArg.................identifier of InsertSubscriberDataArg DEFINED in MAP-MobileServiceOpera : 394 InsertSubscriberDataArg.................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 734 USED in MAP-MobileServiceOpera : 136 394 USED in MAP-MS-DataTypes : 54 insertSubscriberDataRes.................identifier of InsertSubscriberDataRes DEFINED in MAP-MobileServiceOpera : 396 InsertSubscriberDataRes.................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1255 USED in MAP-MobileServiceOpera : 137 396 USED in MAP-MS-DataTypes : 55 insufficientMeasurementData.............identifier of Named Number, 2 DEFINED in MAP-ER-DataTypes : 367 insufficientResources...................identifier of Named Number, 1 DEFINED in MAP-ER-DataTypes : 366 integrityProtectionAlgorithm............identifier of [0] ChosenIntegrityProtectionAlgorithm DEFINED in MAP-MS-DataTypes : 567 integrityProtectionAlgorithms...........identifier of [0] PermittedIntegrityProtectionAlgorithms DEFINED in MAP-MS-DataTypes : 465 integrityProtectionInfo.................identifier of [0] IntegrityProtectionInformation DEFINED in MAP-MS-DataTypes : 446 integrityProtectionInfo.................identifier of [5] IntegrityProtectionInformation DEFINED in MAP-MS-DataTypes : 507 IntegrityProtectionInformation..........type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 672 USED in MAP-MS-DataTypes : 446 507 interCUG-Restrictions...................identifier of InterCUG-Restrictions DEFINED in MAP-MS-DataTypes : 1142 InterCUG-Restrictions...................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 1146 USED in MAP-MS-DataTypes : 79 1142 internalTimeout.........................identifier of Named Number, 2 DEFINED in MAP-LCS-DataTypes : 369 internationalECT-Barred.................identifier of Named Number, 11
2828
3GPP
2829 Release 4
11709 11710 11711 11712 11713 11714 11715
1029
: 982
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-MS-DataTypes
internationalOGCallsBarred..............identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 972 internationalOGCallsNotToHPLMN-CountryBaidentifier of Named Number, 2 DEFINED in MAP-MS-DataTypes : 973
2830
3GPP
2831 Release 4
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 11790 11791 11792
1030
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 49
interrogateSS...........................value reference InterrogateSS, CHOICE VALUE DEFINED in MAP-Protocol : 251 InterrogateSS...........................type reference OPERATION DEFINED in MAP-SupplementaryServi : 160 USED in MAP-Protocol : 73 251 USED in MAP-SupplementaryServi : 17 interrogateSS-Res.......................identifier of InterrogateSS-Res DEFINED in MAP-SupplementaryServi : 164 InterrogateSS-Res.......................type reference CHOICE DEFINED in MAP-SS-DataTypes : 215 USED in MAP-SupplementaryServi : 63 164 USED in MAP-SS-DataTypes : 19 interrogationType.......................identifier of [3] InterrogationType DEFINED in MAP-CH-DataTypes : 98 InterrogationType.......................type reference ENUMERATED DEFINED in MAP-CH-DataTypes : 121 USED in MAP-CH-DataTypes : 98 interzonalECT-Barred....................identifier of Named Number, 12 DEFINED in MAP-MS-DataTypes : 983 interzonalOGCallsAndInternationalOGCallsidentifier of Named Number, 8 DEFINED in MAP-MS-DataTypes : 976 interzonalOGCallsBarred.................identifier of Named Number, 6 DEFINED in MAP-MS-DataTypes : 974 interzonalOGCallsNotToHPLMN-CountryBarreidentifier of Named Number, 7 DEFINED in MAP-MS-DataTypes : 975 intraCUG-Options........................identifier of IntraCUG-Options DEFINED in MAP-MS-DataTypes : 1114 IntraCUG-Options........................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 1124 USED in MAP-MS-DataTypes : 80 1114 invalidFormat...........................identifier of Named Number, 1 DEFINED in MAP-ER-DataTypes : 138 invalidSME-Address......................identifier of Named Number, 5 DEFINED in MAP-ER-DataTypes : 148 invoke..................................identifier of [1] IMPLICIT Invoke DEFINED in TCAPMessages : 125 Invoke..................................type reference SEQUENCE DEFINED in TCAPMessages : 133 USED in TCAPMessages : 125 invokeID................................identifier of InvokeIdType DEFINED in TCAPMessages : 134 invokeID................................identifier of InvokeIdType DEFINED in TCAPMessages : 145 invokeID................................identifier of InvokeIdType DEFINED in TCAPMessages : 157 invokeID................................identifier of CHOICE DEFINED in TCAPMessages : 166 InvokeIdType............................type reference INTEGER DEFINED in TCAPMessages : 175 USED in TCAPMessages : 47 134 135 145 157 167 invokeProblem...........................identifier of [1] IMPLICIT InvokeProblem DEFINED in TCAPMessages : 171
2832
3GPP
2833 Release 4
11793 11794 11795 11796 11797 11798 11799
1031
3GPP TS 29.002 V4.17.0 (2006-06)
InvokeProblem...........................type reference INTEGER DEFINED in TCAPMessages : 183 USED in TCAPMessages : 171 ISDN-AddressString......................type reference AddressString DEFINED in MAP-CommonDataTypes : 143 USED in MAP-OperationAndMainte : 42 79
2834
3GPP
2835 Release 4
11800 11801 11802 11803 11804 11805 11806 11807 11808 11809 11810 11811 11812 11813 11814 11815 11816 11817 11818 11819 11820 11821 11822 11823 11824 11825 11826 11827 11828 11829 11830 11831 11832 11833 11834 11835 11836 11837 11838 11839 11840 11841 11842 11843 11844 11845 11846 11847 11848 11849 11850 11851 11852 11853 11854 11855 11856 11857 11858 11859 11860 11861 11862 11863 11864 11865 11866 11867 11868 11869 11870 11871 11872 11873 11874 11875 11876
1032
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 50
USED in MAP-MS-DataTypes : 165 213 214 259 284 285 387 388 418 438 556 603 657 771 842 929 1040 1364 1366 1383 1423 1473 1557 1582 1631 1652 1667 1694 1706 1772 1778 1829 1844 1921 1971 1991 USED in MAP-CommonDataTypes : 17 375 USED in MAP-CH-DataTypes : 63 95 101 157 163 184 188 200 201 206 220 233 285 300 389 USED in MAP-SS-DataTypes : 45 102 208 226 271 281 312 USED in MAP-SM-DataTypes : 33 54 87 99 100 140 145 173 179 184 USED in MAP-GR-DataTypes : 23 62 USED in MAP-LCS-DataTypes : 29 66 78 90 94 319 322 323 386 isdn-BearerCapability...................identifier of [1] ExternalSignalInfo DEFINED in MAP-CH-DataTypes : 283 ISDN-SubaddressString...................type reference OCTET STRING DEFINED in MAP-CommonDataTypes : 158 USED in MAP-MS-DataTypes : 166 1044 1940 USED in MAP-CommonDataTypes : 20 USED in MAP-CH-DataTypes : 64 192 USED in MAP-SS-DataTypes : 46 76 103 209 istAlert................................value reference IST-Alert, CHOICE VALUE DEFINED in MAP-Protocol : 241 istAlertArg.............................identifier of IST-AlertArg DEFINED in MAP-CallHandlingOperat : 194 istAlertRes.............................identifier of IST-AlertRes DEFINED in MAP-CallHandlingOperat : 196 istAlertTimer...........................identifier of [26] IST-AlertTimerValue DEFINED in MAP-MS-DataTypes : 748 istAlertTimer...........................identifier of [14] IST-AlertTimerValue DEFINED in MAP-CH-DataTypes : 165 istAlertTimer...........................identifier of [0] IST-AlertTimerValue DEFINED in MAP-CH-DataTypes : 422 istCommand..............................value reference IST-Command, CHOICE VALUE DEFINED in MAP-Protocol : 242 istCommandArg...........................identifier of IST-CommandArg DEFINED in MAP-CallHandlingOperat : 207 istCommandRes...........................identifier of IST-CommandRes DEFINED in MAP-CallHandlingOperat : 209 istCommandSupported.....................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 241 istInformationWithdraw..................identifier of [14] NULL DEFINED in MAP-MS-DataTypes : 1288 istInformationWithdraw..................identifier of [1] NULL DEFINED in MAP-CH-DataTypes : 423 istSupportIndicator.....................identifier of [1] IST-SupportIndicator DEFINED in MAP-MS-DataTypes : 226 istSupportIndicator.....................identifier of [18] IST-SupportIndicator DEFINED in MAP-CH-DataTypes : 114 IST-Alert...............................type reference OPERATION DEFINED in MAP-CallHandlingOperat : 192 USED in MAP-Protocol : 62 241 USED in MAP-CallHandlingOperat : 21 IST-AlertArg............................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 416 USED in MAP-CallHandlingOperat : 70 194 USED in MAP-CH-DataTypes : 33
2836
3GPP
2837 Release 4
11877 11878 11879 11880 11881 11882 11883
1033
3GPP TS 29.002 V4.17.0 (2006-06)
IST-AlertRes............................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 421 USED in MAP-CallHandlingOperat : 71 196 USED in MAP-CH-DataTypes : 34 IST-AlertTimerValue.....................type reference INTEGER DEFINED in MAP-MS-DataTypes : 762
2838
3GPP
2839 Release 4
11884 11885 11886 11887 11888 11889 11890 11891 11892 11893 11894 11895 11896 11897 11898 11899 11900 11901 11902 11903 11904 11905 11906 11907 11908 11909 11910 11911 11912 11913 11914 11915 11916 11917 11918 11919 11920 11921 11922 11923 11924 11925 11926 11927 11928 11929 11930 11931 11932 11933 11934 11935 11936 11937 11938 11939 11940 11941 11942 11943 11944 11945 11946 11947 11948 11949 11950 11951 11952 11953 11954 11955 11956 11957 11958 11959 11960
1034
Cross Reference Listing for MAP-Protocol : : 83 748 48 165 422
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 51
USED in MAP-MS-DataTypes USED in MAP-CH-DataTypes
IST-Command.............................type reference OPERATION DEFINED in MAP-CallHandlingOperat : 205 USED in MAP-Protocol : 63 242 USED in MAP-CallHandlingOperat : 22 IST-CommandArg..........................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 428 USED in MAP-CallHandlingOperat : 72 207 USED in MAP-CH-DataTypes : 35 IST-CommandRes..........................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 433 USED in MAP-CallHandlingOperat : 73 209 USED in MAP-CH-DataTypes : 36 IST-SupportIndicator....................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 239 USED in MAP-MS-DataTypes : 26 226 USED in MAP-CH-DataTypes : 47 114 kc......................................identifier of Kc DEFINED in MAP-MS-DataTypes : kc......................................identifier of Kc DEFINED in MAP-MS-DataTypes : 331 347
Kc......................................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 361 USED in MAP-MS-DataTypes : 51 331 347 USED in MAP-GR-DataTypes : 36 55 keepCCBS-CallIndicator..................identifier of [1] NULL DEFINED in MAP-CH-DataTypes : 179 keyStatus...............................identifier of [2] KeyStatus DEFINED in MAP-MS-DataTypes : 448 KeyStatus...............................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 492 USED in MAP-MS-DataTypes : 448 ksi.....................................identifier of KSI DEFINED in MAP-MS-DataTypes : 354 KSI.....................................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 376 USED in MAP-MS-DataTypes : 354 laiFixedLength..........................identifier of [1] LAIFixedLength DEFINED in MAP-CommonDataTypes : 396 LAIFixedLength..........................type reference OCTET STRING DEFINED in MAP-CommonDataTypes : 414 USED in MAP-CommonDataTypes : 396 lawfulInterceptServices.................identifier of Named Number, 3 DEFINED in MAP-LCS-DataTypes : 145 lcsAPN..................................identifier of [5] APN DEFINED in MAP-LCS-DataTypes : 139 lcsCapabilitySet1.......................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 247 lcsCapabilitySet2.......................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 248 lcsClientDialedByMS.....................identifier of [2] AddressString DEFINED in MAP-LCS-DataTypes : 135 LCSClientExternalID.....................type reference SEQUENCE DEFINED in MAP-CommonDataTypes : 378
2840
3GPP
2841 Release 4
11961 11962 11963 11964 11965 11966 11967
1035
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-MS-DataTypes : 182 1210 USED in MAP-CommonDataTypes : 59 USED in MAP-LCS-DataTypes : 35 134 lcsClientExternalID.....................identifier of [1] LCSClientExternalID DEFINED in MAP-LCS-DataTypes : 134
2842
3GPP
2843 Release 4
11968 11969 11970 11971 11972 11973 11974 11975 11976 11977 11978 11979 11980 11981 11982 11983 11984 11985 11986 11987 11988 11989 11990 11991 11992 11993 11994 11995 11996 11997 11998 11999 12000 12001 12002 12003 12004 12005 12006 12007 12008 12009 12010 12011 12012 12013 12014 12015 12016 12017 12018 12019 12020 12021 12022 12023 12024 12025 12026 12027 12028 12029 12030 12031 12032 12033 12034 12035 12036 12037 12038 12039 12040 12041 12042 12043 12044
1036
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 52
LCSClientInternalID.....................type reference ENUMERATED DEFINED in MAP-CommonDataTypes : 383 USED in MAP-MS-DataTypes : 183 1200 USED in MAP-CommonDataTypes : 60 USED in MAP-LCS-DataTypes : 36 136 lcsClientInternalID.....................identifier of [3] LCSClientInternalID DEFINED in MAP-LCS-DataTypes : 136 lcsClientName...........................identifier of [4] LCSClientName DEFINED in MAP-LCS-DataTypes : 137 LCSClientName...........................type reference SEQUENCE DEFINED in MAP-LCS-DataTypes : 152 USED in MAP-LCS-DataTypes : 18 137 lcsClientType...........................identifier of [0] LCSClientType DEFINED in MAP-LCS-DataTypes : 133 LCSClientType...........................type reference ENUMERATED DEFINED in MAP-LCS-DataTypes : 141 USED in MAP-LCS-DataTypes : 133 lcsInformation..........................identifier of [22] LCSInformation DEFINED in MAP-MS-DataTypes : 747 LCSInformation..........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 764 USED in MAP-MS-DataTypes : 747 lcsLocationInfo.........................identifier of [1] LCSLocationInfo DEFINED in MAP-LCS-DataTypes : 73 LCSLocationInfo.........................type reference SEQUENCE DEFINED in MAP-LCS-DataTypes : 77 USED in MAP-LCS-DataTypes : 73 318 351 lcsLocationInfo.........................identifier of LCSLocationInfo DEFINED in MAP-LCS-DataTypes : 318 lcsLocationInfo.........................identifier of [1] LCSLocationInfo DEFINED in MAP-LCS-DataTypes : 351 lcs-ClientID............................identifier of [0] LCS-ClientID DEFINED in MAP-LCS-DataTypes : 91 LCS-ClientID............................type reference SEQUENCE DEFINED in MAP-LCS-DataTypes : 132 USED in MAP-LCS-DataTypes : 91 317 lcs-ClientID............................identifier of LCS-ClientID DEFINED in MAP-LCS-DataTypes : 317 lcs-Event...............................identifier of LCS-Event DEFINED in MAP-LCS-DataTypes : 316 LCS-Event...............................type reference ENUMERATED DEFINED in MAP-LCS-DataTypes : 356 USED in MAP-LCS-DataTypes : 316 lcs-Priority............................identifier of [6] LCS-Priority DEFINED in MAP-LCS-DataTypes : 97 LCS-Priority............................type reference OCTET STRING DEFINED in MAP-LCS-DataTypes : 166 USED in MAP-LCS-DataTypes : 97 LCS-PrivacyClass........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1171 USED in MAP-MS-DataTypes : 1167 lcs-PrivacyExceptionList................identifier of [1] LCS-PrivacyExceptionList DEFINED in MAP-MS-DataTypes : 766 LCS-PrivacyExceptionList................type reference SEQUENCE OF
2844
3GPP
2845 Release 4
12045 12046 12047 12048 12049 12050 12051
1037
: 1166 766
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-MS-DataTypes USED in MAP-MS-DataTypes
lcs-QoS.................................identifier of [7] LCS-QoS DEFINED in MAP-LCS-DataTypes : 98 LCS-QoS.................................type reference SEQUENCE
2846
3GPP
2847 Release 4
12052 12053 12054 12055 12056 12057 12058 12059 12060 12061 12062 12063 12064 12065 12066 12067 12068 12069 12070 12071 12072 12073 12074 12075 12076 12077 12078 12079 12080 12081 12082 12083 12084 12085 12086 12087 12088 12089 12090 12091 12092 12093 12094 12095 12096 12097 12098 12099 12100 12101 12102 12103 12104 12105 12106 12107 12108 12109 12110 12111 12112 12113 12114 12115 12116 12117 12118 12119 12120 12121 12122 12123 12124 12125 12126 12127 12128
1038
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 53
DEFINED in MAP-LCS-DataTypes : 171 USED in MAP-LCS-DataTypes : 19 98 lcs-ReferenceNumber.....................identifier of [10] LCS-ReferenceNumber DEFINED in MAP-LCS-DataTypes : 102 LCS-ReferenceNumber.....................type reference OCTET STRING DEFINED in MAP-LCS-DataTypes : 213 USED in MAP-LCS-DataTypes : 102 330 lcs-ReferenceNumber.....................identifier of [10] LCS-ReferenceNumber DEFINED in MAP-LCS-DataTypes : 330 linkedID................................identifier of [0] IMPLICIT InvokeIdType DEFINED in TCAPMessages : 135 linkedResponseUnexpected................identifier of Named Number, 6 DEFINED in TCAPMessages : 189 lmsi....................................identifier of [10] LMSI DEFINED in MAP-MS-DataTypes : 215 lmsi....................................identifier of LMSI DEFINED in MAP-MS-DataTypes : 1700 lmsi....................................identifier of [1] LMSI DEFINED in MAP-MS-DataTypes : 1744 lmsi....................................identifier of LMSI DEFINED in MAP-CommonDataTypes : 306
LMSI....................................type reference OCTET STRING DEFINED in MAP-CommonDataTypes : 336 USED in MAP-MS-DataTypes : 172 215 1700 1744 USED in MAP-CommonDataTypes : 36 306 USED in MAP-CH-DataTypes : 69 202 317 USED in MAP-SM-DataTypes : 36 88 135 USED in MAP-LCS-DataTypes : 32 80 95 lmsi....................................identifier of [4] LMSI DEFINED in MAP-CH-DataTypes : 202 lmsi....................................identifier of [1] LMSI DEFINED in MAP-CH-DataTypes : 317 lmsi....................................identifier of LMSI DEFINED in MAP-SM-DataTypes : 88 lmsi....................................identifier of [1] LMSI DEFINED in MAP-SM-DataTypes : 135 lmsi....................................identifier of [0] LMSI DEFINED in MAP-LCS-DataTypes : 80 lmsi....................................identifier of [4] LMSI DEFINED in MAP-LCS-DataTypes : 95 lmu-Indicator...........................identifier of [21] NULL DEFINED in MAP-MS-DataTypes : 746 locationEstimate........................identifier of Ext-GeographicalInformation DEFINED in MAP-LCS-DataTypes : 216 locationEstimate........................identifier of [5] Ext-GeographicalInformation DEFINED in MAP-LCS-DataTypes : 324 locationEstimateType....................identifier of [0] LocationEstimateType DEFINED in MAP-LCS-DataTypes : 110 LocationEstimateType....................type reference ENUMERATED DEFINED in MAP-LCS-DataTypes : 114 USED in MAP-LCS-DataTypes : 110 locationInformation.....................identifier of [0] LocationInformation DEFINED in MAP-MS-DataTypes : 1755
2848
3GPP
2849 Release 4
12129 12130 12131 12132 12133 12134 12135
1039
3GPP TS 29.002 V4.17.0 (2006-06)
locationInformation.....................identifier of [0] NULL DEFINED in MAP-MS-DataTypes : 1761 LocationInformation.....................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1769 USED in MAP-MS-DataTypes : 101 1755 1992
2850
3GPP
2851 Release 4
12136 12137 12138 12139 12140 12141 12142 12143 12144 12145 12146 12147 12148 12149 12150 12151 12152 12153 12154 12155 12156 12157 12158 12159 12160 12161 12162 12163 12164 12165 12166 12167 12168 12169 12170 12171 12172 12173 12174 12175 12176 12177 12178 12179 12180 12181 12182 12183 12184 12185 12186 12187 12188 12189 12190 12191 12192 12193 12194 12195 12196 12197 12198 12199 12200 12201 12202 12203 12204 12205 12206 12207 12208 12209 12210 12211 12212
1040
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 54
locationInformation.....................identifier of [3] LocationInformation DEFINED in MAP-MS-DataTypes : 1992 locationInfoWithLMSI....................identifier of [0] LocationInfoWithLMSI DEFINED in MAP-SM-DataTypes : 82 LocationInfoWithLMSI....................type reference SEQUENCE DEFINED in MAP-SM-DataTypes : 86 USED in MAP-SM-DataTypes : 82 locationNotAllowed......................identifier of Named Number, 3 DEFINED in MAP-MS-DataTypes : 1231 locationNumber..........................identifier of [2] LocationNumber DEFINED in MAP-MS-DataTypes : 1773 LocationNumber..........................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 1809 USED in MAP-MS-DataTypes : 1773 locationProcedureNotCompleted...........identifier of Named Number, 4 DEFINED in MAP-ER-DataTypes : 369 locationProcedureNotSupportedByTargetMS.identifier of Named Number, 5 DEFINED in MAP-ER-DataTypes : 370 locationType............................identifier of LocationType DEFINED in MAP-LCS-DataTypes : 89 LocationType............................type reference SEQUENCE DEFINED in MAP-LCS-DataTypes : 109 USED in MAP-LCS-DataTypes : 17 89 locationUpdating........................identifier of Named Number, 2 DEFINED in MAP-MS-DataTypes : 393 longForwardedToNumber...................identifier of [10] FTN-AddressString DEFINED in MAP-MS-DataTypes : 1049 longForwardedToNumber...................identifier of [8] FTN-AddressString DEFINED in MAP-CH-DataTypes : 196 longForwardedToNumber...................identifier of [9] FTN-AddressString DEFINED in MAP-SS-DataTypes : 107 longFTN-Supported.......................identifier of [4] NULL DEFINED in MAP-MS-DataTypes : 228 longFTN-Supported.......................identifier of [4] NULL DEFINED in MAP-MS-DataTypes : 1846 longFTN-Supported.......................identifier of [6] NULL DEFINED in MAP-MS-DataTypes : 1926 longFTN-Supported.......................identifier of [21] NULL DEFINED in MAP-CH-DataTypes : 117 longFTN-Supported.......................identifier of [18] NULL DEFINED in MAP-CH-DataTypes : 217 longFTN-Supported.......................identifier of [9] NULL DEFINED in MAP-SS-DataTypes : 81 longFTN-Supported.......................identifier of [4] NULL DEFINED in MAP-SS-DataTypes : 188 LongSignalInfo..........................type reference OCTET STRING DEFINED in MAP-CommonDataTypes : 249 USED in MAP-CommonDataTypes : 243 longTermDenial..........................value reference LongTermDenial, CHOICE VALUE DEFINED in MAP-Protocol : 416 LongTermDenial..........................type reference ERROR
2852
3GPP
2853 Release 4
12213 12214 12215 12216 12217 12218 12219
1041
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-Errors : 393 USED in MAP-Protocol : 161 416 USED in MAP-SupplementaryServi : 54 265 USED in MAP-Errors : 74 longTermDenialParam.....................identifier of LongTermDenialParam DEFINED in MAP-Errors : 395
2854
3GPP
2855 Release 4
12220 12221 12222 12223 12224 12225 12226 12227 12228 12229 12230 12231 12232 12233 12234 12235 12236 12237 12238 12239 12240 12241 12242 12243 12244 12245 12246 12247 12248 12249 12250 12251 12252 12253 12254 12255 12256 12257 12258 12259 12260 12261 12262 12263 12264 12265 12266 12267 12268 12269 12270 12271 12272 12273 12274 12275 12276 12277 12278 12279 12280 12281 12282 12283 12284 12285 12286 12287 12288 12289 12290 12291 12292 12293 12294 12295 12296
1042
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 55
LongTermDenialParam.....................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 337 USED in MAP-Errors : 140 395 USED in MAP-ER-DataTypes : 48 lowdelay................................identifier of Named Number, 0 DEFINED in MAP-LCS-DataTypes : 196 lowerLayerCompatibility.................identifier of [5] ExternalSignalInfo DEFINED in MAP-CH-DataTypes : 287 lsaActiveModeIndicator..................identifier of [2] NULL DEFINED in MAP-MS-DataTypes : 907 lsaAttributes...........................identifier of [1] LSAAttributes DEFINED in MAP-MS-DataTypes : 906 LSAAttributes...........................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 924 USED in MAP-MS-DataTypes : 906 LSAData.................................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 904 USED in MAP-MS-DataTypes : 900 LSADataList.............................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 899 USED in MAP-MS-DataTypes : 917 lsaDataList.............................identifier of [2] LSADataList DEFINED in MAP-MS-DataTypes : 917 lsaIdentity.............................identifier of [0] LSAIdentity DEFINED in MAP-MS-DataTypes : 905 LSAIdentity.............................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 921 USED in MAP-MS-DataTypes : 56 905 1318 1777 lsaIdentityList.........................identifier of LSAIdentityList DEFINED in MAP-MS-DataTypes : 1315 LSAIdentityList.........................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1317 USED in MAP-MS-DataTypes : 1315 lsaInformation..........................identifier of [25] LSAInformation DEFINED in MAP-MS-DataTypes : 745 LSAInformation..........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 911 USED in MAP-MS-DataTypes : 745 lsaInformationWithdraw..................identifier of [12] LSAInformationWithdraw DEFINED in MAP-MS-DataTypes : 1286 LSAInformationWithdraw..................type reference CHOICE DEFINED in MAP-MS-DataTypes : 1313 USED in MAP-MS-DataTypes : 1286 LSAOnlyAccessIndicator..................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 895 USED in MAP-MS-DataTypes : 916 lsaOnlyAccessIndicator..................identifier of [1] LSAOnlyAccessIndicator DEFINED in MAP-MS-DataTypes : 916 mah.....................................value reference SS-Code, '00110010'B DEFINED in MAP-SS-Code : 68 MAP-BS-Code.............................module reference DEFINED in MAP-BS-Code : 1 USED in MAP-MS-DataTypes : 154 USED in MAP-CommonDataTypes : 72
2856
3GPP
2857 Release 4
12297 12298 12299 12300 12301 12302 12303
1043
3GPP TS 29.002 V4.17.0 (2006-06)
MAP-CallHandlingOperations..............module reference DEFINED in MAP-CallHandlingOperat : 1 USED in MAP-Protocol : 64 MAP-CH-DataTypes........................module reference DEFINED in MAP-CH-DataTypes : 1
2858
3GPP
2859 Release 4
12304 12305 12306 12307 12308 12309 12310 12311 12312 12313 12314 12315 12316 12317 12318 12319 12320 12321 12322 12323 12324 12325 12326 12327 12328 12329 12330 12331 12332 12333 12334 12335 12336 12337 12338 12339 12340 12341 12342 12343 12344 12345 12346 12347 12348 12349 12350 12351 12352 12353 12354 12355 12356 12357 12358 12359 12360 12361 12362 12363 12364 12365 12366 12367 12368 12369 12370 12371 12372 12373 12374 12375 12376 12377 12378 12379 12380
1044
Cross Reference Listing for MAP-Protocol 74
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 56
USED in MAP-CallHandlingOperat :
MAP-CommonDataTypes.....................module reference DEFINED in MAP-CommonDataTypes : 1 USED in MAP-MobileServiceOpera : 168 USED in MAP-OperationAndMainte : 44 USED in MAP-MS-DataTypes : 190 USED in MAP-OM-DataTypes : 23 USED in MAP-CH-DataTypes : 75 USED in MAP-SS-DataTypes : 56 USED in MAP-SM-DataTypes : 37 USED in MAP-GR-DataTypes : 27 USED in MAP-LCS-DataTypes : 37 USED in MAP-ER-DataTypes : 76 MAP-Errors..............................module reference DEFINED in MAP-Errors : 1 USED in MAP-Protocol : 175 USED in MAP-MobileServiceOpera : 109 USED in MAP-OperationAndMainte : 30 USED in MAP-CallHandlingOperat : 51 USED in MAP-SupplementaryServi : 56 USED in MAP-ShortMessageServic : 41 USED in MAP-Group-Call-Operati : 27 USED in MAP-LocationServiceOpe : 37 MAP-ER-DataTypes........................module reference DEFINED in MAP-ER-DataTypes : 1 USED in MAP-Errors : 157 USED in MAP-MS-DataTypes : 200 USED in MAP-SM-DataTypes : 42 MAP-EXTENSION...........................information object class reference CLASS DEFINED in MAP-ExtensionDataTypes : 23 USED in MAP-ExtensionDataTypes : 47 49 54 MAP-ExtensionDataTypes..................module reference DEFINED in MAP-ExtensionDataTypes : 1 USED in MAP-MS-DataTypes : 195 USED in MAP-CommonDataTypes : 82 USED in MAP-OM-DataTypes : 28 USED in MAP-CH-DataTypes : 80 USED in MAP-SS-DataTypes : 61 USED in MAP-SM-DataTypes : 47 USED in MAP-GR-DataTypes : 43 USED in MAP-LCS-DataTypes : 43 USED in MAP-ER-DataTypes : 88 MAP-Group-Call-Operations...............module reference DEFINED in MAP-Group-Call-Operati : 1 USED in MAP-Protocol : 103 MAP-GR-DataTypes........................module reference DEFINED in MAP-GR-DataTypes : 1 USED in MAP-Group-Call-Operati : 37 MAP-LCS-DataTypes.......................module reference DEFINED in MAP-LCS-DataTypes : 1 USED in MAP-LocationServiceOpe : 47 MAP-LocationServiceOperations...........module reference DEFINED in MAP-LocationServiceOpe : 1 USED in MAP-Protocol : 111 MAP-MobileServiceOperations.............module reference DEFINED in MAP-MobileServiceOpera : 1 USED in MAP-Protocol : 41 MAP-MS-DataTypes........................module reference DEFINED in MAP-MS-DataTypes : 1 USED in MAP-MobileServiceOpera : 163 USED in MAP-CH-DataTypes : 52 USED in MAP-GR-DataTypes : 37 USED in MAP-LCS-DataTypes : 54
2860
3GPP
2861 Release 4
12381 12382 12383 12384 12385 12386 12387
1045
3GPP TS 29.002 V4.17.0 (2006-06)
MAP-OM-DataTypes........................module reference DEFINED in MAP-OM-DataTypes : 1 USED in MAP-OperationAndMainte : 38 MAP-OperationAndMaintenanceOperations...module reference DEFINED in MAP-OperationAndMainte : 1 USED in MAP-Protocol : 49
2862
3GPP
2863 Release 4
12388 12389 12390 12391 12392 12393 12394 12395 12396 12397 12398 12399 12400 12401 12402 12403 12404 12405 12406 12407 12408 12409 12410 12411 12412 12413 12414 12415 12416 12417 12418 12419 12420 12421 12422 12423 12424 12425 12426 12427 12428 12429 12430 12431 12432 12433 12434 12435 12436 12437 12438 12439 12440 12441 12442 12443 12444 12445 12446 12447 12448 12449 12450 12451 12452 12453 12454 12455 12456 12457 12458 12459 12460 12461 12462 12463 12464
1046
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 57
MAP-Protocol............................module reference DEFINED in MAP-Protocol : 1 MAP-ShortMessageServiceOperations.......module reference DEFINED in MAP-ShortMessageServic : 1 USED in MAP-Protocol : 94 MAP-SM-DataTypes........................module reference DEFINED in MAP-SM-DataTypes : 1 USED in MAP-ShortMessageServic : 57 USED in MAP-LCS-DataTypes : 59 MAP-SS-Code.............................module reference DEFINED in MAP-SS-Code : 1 USED in MAP-SupplementaryServi : 79 USED in MAP-MS-DataTypes : 149 USED in MAP-CommonDataTypes : 77 USED in MAP-SS-DataTypes : 66 USED in MAP-ER-DataTypes : 83 MAP-SS-DataTypes........................module reference DEFINED in MAP-SS-DataTypes : 1 USED in MAP-SupplementaryServi : 74 USED in MAP-Errors : 103 USED in MAP-MS-DataTypes : 144 USED in MAP-CH-DataTypes : 59 USED in MAP-LCS-DataTypes : 49 USED in MAP-ER-DataTypes : 69 MAP-SupplementaryServiceOperations......module reference DEFINED in MAP-SupplementaryServi : 1 USED in MAP-Protocol : 82 MAP-TS-Code.............................module reference DEFINED in MAP-TS-Code : 1 USED in MAP-MS-DataTypes : 159 USED in MAP-CommonDataTypes : 66 USED in MAP-GR-DataTypes : 32 matchType...............................identifier of [0] MatchType DEFINED in MAP-MS-DataTypes : 1465 MatchType...............................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 1495 USED in MAP-MS-DataTypes : 1465 maxAddressLength........................value reference INTEGER, 20 DEFINED in MAP-CommonDataTypes : 141 USED in MAP-CommonDataTypes : 100 maxAdd-GeographicalInformation..........value reference INTEGER, 91 DEFINED in MAP-LCS-DataTypes : 312 USED in MAP-LCS-DataTypes : 294 maxEventSpecification...................value reference INTEGER, 2 DEFINED in MAP-SS-DataTypes : 303 USED in MAP-SS-DataTypes : 300 maxExt-GeographicalInformation..........value reference INTEGER, 20 DEFINED in MAP-LCS-DataTypes : 290 USED in MAP-LCS-DataTypes : 234 maxFTN-AddressLength....................value reference INTEGER, 15 DEFINED in MAP-CommonDataTypes : 156 USED in MAP-CommonDataTypes : 150 maximumentitledPriority.................identifier of EMLPP-Priority DEFINED in MAP-CommonDataTypes : 438 maximumEntitledPriority.................identifier of [0] EMLPP-Priority DEFINED in MAP-SS-DataTypes : 194 maxISDN-AddressLength...................value reference INTEGER, 9 DEFINED in MAP-CommonDataTypes : 147
2864
3GPP
2865 Release 4
12465 12466 12467 12468 12469 12470 12471
1047
: 18 144
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-CommonDataTypes
maxISDN-SubaddressLength................value reference INTEGER, 21 DEFINED in MAP-CommonDataTypes : 196 USED in MAP-CommonDataTypes : 159 maxLongSignalInfoLength.................value reference INTEGER, 2560
2866
3GPP
2867 Release 4
12472 12473 12474 12475 12476 12477 12478 12479 12480 12481 12482 12483 12484 12485 12486 12487 12488 12489 12490 12491 12492 12493 12494 12495 12496 12497 12498 12499 12500 12501 12502 12503 12504 12505 12506 12507 12508 12509 12510 12511 12512 12513 12514 12515 12516 12517 12518 12519 12520 12521 12522 12523 12524 12525 12526 12527 12528 12529 12530 12531 12532 12533 12534 12535 12536 12537 12538 12539 12540 12541 12542 12543 12544 12545 12546 12547 12548
1048
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 58
DEFINED in MAP-CommonDataTypes : 251 USED in MAP-CommonDataTypes : 249 MaxMC-Bearers...........................type reference INTEGER DEFINED in MAP-CommonDataTypes : 466 USED in MAP-CommonDataTypes : 53 461 USED in MAP-SS-DataTypes : 52 197 maxNameStringLength.....................value reference INTEGER, 63 DEFINED in MAP-LCS-DataTypes : 164 USED in MAP-LCS-DataTypes : 162 maxNrOfRABs.............................value reference INTEGER, 255 DEFINED in MAP-MS-DataTypes : 664 USED in MAP-MS-DataTypes : 662 maxNumOfBasicServiceGroups..............value reference INTEGER, 13 DEFINED in MAP-SS-DataTypes : 267 USED in MAP-SS-DataTypes : 96 153 264 maxNumOfBasicServices...................value reference INTEGER, 70 DEFINED in MAP-MS-DataTypes : 1323 USED in MAP-MS-DataTypes : 1320 maxNumOfBearerServices..................value reference INTEGER, 50 DEFINED in MAP-MS-DataTypes : 957 USED in MAP-MS-DataTypes : 954 maxNumOfCamelBasicServiceCriteria.......value reference INTEGER, 5 DEFINED in MAP-MS-DataTypes : 1489 USED in MAP-MS-DataTypes : 1480 maxNumOfCamelDestinationNumberLengths...value reference INTEGER, 3 DEFINED in MAP-MS-DataTypes : 1487 USED in MAP-MS-DataTypes : 1477 maxNumOfCamelDestinationNumbers.........value reference INTEGER, 10 DEFINED in MAP-MS-DataTypes : 1485 USED in MAP-MS-DataTypes : 1472 maxNumOfCamelSSEvents...................value reference INTEGER, 10 DEFINED in MAP-MS-DataTypes : 1398 USED in MAP-MS-DataTypes : 1387 maxNumOfCamelTDPData....................value reference INTEGER, 10 DEFINED in MAP-MS-DataTypes : 1418 USED in MAP-MS-DataTypes : 75 834 1411 1443 1446 1549 1620 maxNumOfCAMEL-O-CauseValueCriteria......value reference INTEGER, 5 DEFINED in MAP-MS-DataTypes : 1505 USED in MAP-MS-DataTypes : 1499 maxNumOfCAMEL-T-CauseValueCriteria......value reference INTEGER, 5 DEFINED in MAP-MS-DataTypes : 1507 USED in MAP-MS-DataTypes : 1502 maxNumOfCCBS-Requests...................value reference INTEGER, 5 DEFINED in MAP-SS-DataTypes : 204 USED in MAP-SS-DataTypes : 201 213 maxNumOfCUG.............................value reference INTEGER, 10 DEFINED in MAP-MS-DataTypes : 1129 USED in MAP-MS-DataTypes : 1108 maxNumOfDP-AnalysedInfoCriteria.........value reference INTEGER, 10 DEFINED in MAP-MS-DataTypes : 1361 USED in MAP-MS-DataTypes : 1358 maxNumOfEncryptionInfo..................value reference INTEGER, 100 DEFINED in MAP-MS-DataTypes : 690 USED in MAP-MS-DataTypes : 682 maxNumOfExternalClient..................value reference INTEGER, 5 DEFINED in MAP-MS-DataTypes : 1197 USED in MAP-MS-DataTypes : 1194
2868
3GPP
2869 Release 4
12549 12550 12551 12552 12553 12554 12555
1049
3GPP TS 29.002 V4.17.0 (2006-06)
maxNumOfExt-BasicServiceGroups..........value reference INTEGER, 32 DEFINED in MAP-MS-DataTypes : 1137 USED in MAP-MS-DataTypes : 1034 1093 1131 1134 maxNumOfExt-ExternalClient..............value reference INTEGER, 35 DEFINED in MAP-MS-DataTypes : 1207
2870
3GPP
2871 Release 4
12556 12557 12558 12559 12560 12561 12562 12563 12564 12565 12566 12567 12568 12569 12570 12571 12572 12573 12574 12575 12576 12577 12578 12579 12580 12581 12582 12583 12584 12585 12586 12587 12588 12589 12590 12591 12592 12593 12594 12595 12596 12597 12598 12599 12600 12601 12602 12603 12604 12605 12606 12607 12608 12609 12610 12611 12612 12613 12614 12615 12616 12617 12618 12619 12620 12621 12622 12623 12624 12625 12626 12627 12628 12629 12630 12631 12632
1050
Cross Reference Listing for MAP-Protocol : 1204
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 59
USED in MAP-MS-DataTypes
maxNumOfGMLC............................value reference INTEGER, 5 DEFINED in MAP-MS-DataTypes : 774 USED in MAP-MS-DataTypes : 770 maxNumOfHLR-Id..........................value reference INTEGER, 50 DEFINED in MAP-CommonDataTypes : 334 USED in MAP-CommonDataTypes : 331 maxNumOfIntegrityInfo...................value reference INTEGER, 100 DEFINED in MAP-MS-DataTypes : 680 USED in MAP-MS-DataTypes : 672 maxNumOfISDN-AddressDigits..............value reference INTEGER, 15 DEFINED in MAP-MS-DataTypes : 1483 USED in MAP-MS-DataTypes : 1478 maxNumOfLSAs............................value reference INTEGER, 20 DEFINED in MAP-MS-DataTypes : 902 USED in MAP-MS-DataTypes : 899 1317 maxNumOfMC-Bearers......................value reference INTEGER, 7 DEFINED in MAP-CommonDataTypes : 470 USED in MAP-CommonDataTypes : 466 468 maxNumOfMobilityTriggers................value reference INTEGER, 10 DEFINED in MAP-MS-DataTypes : 1593 USED in MAP-MS-DataTypes : 1590 maxNumOfMOLR-Class......................value reference INTEGER, 3 DEFINED in MAP-MS-DataTypes : 1239 USED in MAP-MS-DataTypes : 1236 maxNumOfPDP-Contexts....................value reference INTEGER, 50 DEFINED in MAP-MS-DataTypes : 788 USED in MAP-MS-DataTypes : 785 803 1310 maxNumOfPLMNClient......................value reference INTEGER, 5 DEFINED in MAP-MS-DataTypes : 1202 USED in MAP-MS-DataTypes : 1199 maxNumOfPrivacyClass....................value reference INTEGER, 4 DEFINED in MAP-MS-DataTypes : 1169 USED in MAP-MS-DataTypes : 1166 maxNumOfPrivateExtensions...............value reference INTEGER, 10 DEFINED in MAP-ExtensionDataTypes : 52 USED in MAP-ExtensionDataTypes : 43 maxNumOfRadioResources..................value reference INTEGER, 7 DEFINED in MAP-MS-DataTypes : 553 USED in MAP-MS-DataTypes : 544 maxNumOfRelocationNumber................value reference INTEGER, 7 DEFINED in MAP-MS-DataTypes : 666 USED in MAP-MS-DataTypes : 651 654 maxNumOfServiceHandovers................value reference INTEGER, 7 DEFINED in MAP-MS-DataTypes : 531 USED in MAP-MS-DataTypes : 522 maxNumOfSS..............................value reference INTEGER, 30 DEFINED in MAP-SS-DataTypes : 259 USED in MAP-MS-DataTypes : 139 1017 USED in MAP-SS-DataTypes : 32 256 261 maxNumOfTeleservices....................value reference INTEGER, 20 DEFINED in MAP-MS-DataTypes : 962 USED in MAP-MS-DataTypes : 959 maxNumOfVBSGroupIds.....................value reference INTEGER, 50 DEFINED in MAP-MS-DataTypes : 1719 USED in MAP-MS-DataTypes : 1713
2872
3GPP
2873 Release 4
12633 12634 12635 12636 12637 12638 12639
1051
3GPP TS 29.002 V4.17.0 (2006-06)
maxNumOfVGCSGroupIds....................value reference INTEGER, 50 DEFINED in MAP-MS-DataTypes : 1721 USED in MAP-MS-DataTypes : 1716 maxNumOfZoneCodes.......................value reference INTEGER, 10 DEFINED in MAP-MS-DataTypes : 1253 USED in MAP-MS-DataTypes : 64 1247
2874
3GPP
2875 Release 4
12640 12641 12642 12643 12644 12645 12646 12647 12648 12649 12650 12651 12652 12653 12654 12655 12656 12657 12658 12659 12660 12661 12662 12663 12664 12665 12666 12667 12668 12669 12670 12671 12672 12673 12674 12675 12676 12677 12678 12679 12680 12681 12682 12683 12684 12685 12686 12687 12688 12689 12690 12691 12692 12693 12694 12695 12696 12697 12698 12699 12700 12701 12702 12703 12704 12705 12706 12707 12708 12709 12710 12711 12712 12713 12714 12715 12716
1052
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 60
maxPermittedEncryptionAlgorithmsLength..value reference INTEGER, 9 DEFINED in MAP-MS-DataTypes : 490 USED in MAP-MS-DataTypes : 482 maxPermittedIntegrityProtectionAlgorithmvalue reference INTEGER, 9 DEFINED in MAP-MS-DataTypes : 479 USED in MAP-MS-DataTypes : 471 maxSignalInfoLength.....................value reference INTEGER, 200 DEFINED in MAP-CommonDataTypes : 209 USED in MAP-CommonDataTypes : 25 207 maxUSSD-StringLength....................value reference INTEGER, 160 DEFINED in MAP-SS-DataTypes : 242 USED in MAP-SS-DataTypes : 238 mc......................................value reference SS-Code, '01000101'B DEFINED in MAP-SS-Code : 84 mcef-Set................................identifier of Named Number, 2 DEFINED in MAP-SM-DataTypes : 198 mci.....................................value reference SS-Code, '00010101'B DEFINED in MAP-SS-Code : 36 MC-Bearers..............................type reference INTEGER DEFINED in MAP-CommonDataTypes : 468 USED in MAP-CommonDataTypes : 54 462 USED in MAP-SS-DataTypes : 53 80 168 198 199 mc-SS-Info..............................identifier of [28] MC-SS-Info DEFINED in MAP-MS-DataTypes : 750 MC-SS-Info..............................type reference SEQUENCE DEFINED in MAP-CommonDataTypes : 458 USED in MAP-MS-DataTypes : 179 750 USED in MAP-CommonDataTypes : 52 memoryAvailable.........................identifier of Named Number, 1 DEFINED in MAP-SM-DataTypes : 219 memoryCapacityExceeded..................identifier of Named Number, 0 DEFINED in MAP-SM-DataTypes : 168 memoryCapacityExceeded..................identifier of Named Number, 0 DEFINED in MAP-ER-DataTypes : 143 MessageType.............................type reference CHOICE DEFINED in TCAPMessages : 51 USED in TCAPMessages : 47 messageWaitingListFull..................value reference MessageWaitingListFull, CHOICE VALUE DEFINED in MAP-Protocol : 423 MessageWaitingListFull..................type reference ERROR DEFINED in MAP-Errors : 410 USED in MAP-Protocol : 156 423 USED in MAP-ShortMessageServic : 39 121 USED in MAP-Errors : 79 messageWaitListFullParam................identifier of MessageWaitListFullParam DEFINED in MAP-Errors : 412 MessageWaitListFullParam................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 318 USED in MAP-Errors : 134 412 USED in MAP-ER-DataTypes : 41 mistypedComponent.......................identifier of Named Number, 1 DEFINED in TCAPMessages : 180 mistypedParameter.......................identifier of Named Number, 2 DEFINED in TCAPMessages : 185
2876
3GPP
2877 Release 4
12717 12718 12719 12720 12721 12722 12723
1053
3GPP TS 29.002 V4.17.0 (2006-06)
mistypedParameter.......................identifier of Named Number, 2 DEFINED in TCAPMessages : 194 mistypedParameter.......................identifier of Named Number, 4 DEFINED in TCAPMessages : 200 mlcNumber...............................identifier of [0] ISDN-AddressString
2878
3GPP
2879 Release 4
12724 12725 12726 12727 12728 12729 12730 12731 12732 12733 12734 12735 12736 12737 12738 12739 12740 12741 12742 12743 12744 12745 12746 12747 12748 12749 12750 12751 12752 12753 12754 12755 12756 12757 12758 12759 12760 12761 12762 12763 12764 12765 12766 12767 12768 12769 12770 12771 12772 12773 12774 12775 12776 12777 12778 12779 12780 12781 12782 12783 12784 12785 12786 12787 12788 12789 12790 12791 12792 12793 12794 12795 12796 12797 12798 12799 12800
1054
Cross Reference Listing for MAP-Protocol : 66
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 61
DEFINED in MAP-LCS-DataTypes
mlc-Number..............................identifier of ISDN-AddressString DEFINED in MAP-LCS-DataTypes : 90 MM-Code.................................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 1595 USED in MAP-MS-DataTypes : 1591 1989 mm-EventNotSupported....................value reference MM-EventNotSupported, CHOICE VALUE DEFINED in MAP-Protocol : 435 MM-EventNotSupported....................type reference ERROR DEFINED in MAP-Errors : 449 USED in MAP-Protocol : 170 435 USED in MAP-MobileServiceOpera : 94 486 USED in MAP-Errors : 92 mm-EventNotSupported-Param..............identifier of MM-EventNotSupported-Param DEFINED in MAP-Errors : 451 MM-EventNotSupported-Param..............type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 382 USED in MAP-Errors : 145 451 USED in MAP-ER-DataTypes : 53 mnrf-Set................................identifier of Named Number, 1 DEFINED in MAP-SM-DataTypes : 197 mnrg-Set................................identifier of Named Number, 3 DEFINED in MAP-SM-DataTypes : 199 mobileNotReachableReason................identifier of [2] AbsentSubscriberDiagnosticSM DEFINED in MAP-MS-DataTypes : 1659 mobilityTriggers........................identifier of MobilityTriggers DEFINED in MAP-MS-DataTypes : 1580 MobilityTriggers........................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1590 USED in MAP-MS-DataTypes : 1580 ModificationInstruction.................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 1963 USED in MAP-MS-DataTypes : 1942 1952 1958 1959 modificationRequestFor-CB-Info..........identifier of [3] ModificationRequestFor-CB-Info DEFINED in MAP-MS-DataTypes : 1923 ModificationRequestFor-CB-Info..........type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1946 USED in MAP-MS-DataTypes : 1923 modificationRequestFor-CF-Info..........identifier of [2] ModificationRequestFor-CF-Info DEFINED in MAP-MS-DataTypes : 1922 ModificationRequestFor-CF-Info..........type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1935 USED in MAP-MS-DataTypes : 1922 modificationRequestFor-CSI..............identifier of [4] ModificationRequestFor-CSI DEFINED in MAP-MS-DataTypes : 1924 ModificationRequestFor-CSI..............type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1956 USED in MAP-MS-DataTypes : 1924 modifyCSI-State.........................identifier of [2] ModificationInstruction DEFINED in MAP-MS-DataTypes : 1959 modifyNotificationToCSE.................identifier of [6] ModificationInstruction DEFINED in MAP-MS-DataTypes : 1942 modifyNotificationToCSE.................identifier of [5] ModificationInstruction DEFINED in MAP-MS-DataTypes : 1952
2880
3GPP
2881 Release 4
12801 12802 12803 12804 12805 12806 12807
1055
3GPP TS 29.002 V4.17.0 (2006-06)
modifyNotificationToCSE.................identifier of [1] ModificationInstruction DEFINED in MAP-MS-DataTypes : 1958 MOLR-Class..............................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1241 USED in MAP-MS-DataTypes : 1237
2882
3GPP
2883 Release 4
12808 12809 12810 12811 12812 12813 12814 12815 12816 12817 12818 12819 12820 12821 12822 12823 12824 12825 12826 12827 12828 12829 12830 12831 12832 12833 12834 12835 12836 12837 12838 12839 12840 12841 12842 12843 12844 12845 12846 12847 12848 12849 12850 12851 12852 12853 12854 12855 12856 12857 12858 12859 12860 12861 12862 12863 12864 12865 12866 12867 12868 12869 12870 12871 12872 12873 12874 12875 12876 12877 12878 12879 12880 12881 12882 12883 12884
1056
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 62
molr-List...............................identifier of [2] MOLR-List DEFINED in MAP-MS-DataTypes : 767 MOLR-List...............................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1236 USED in MAP-MS-DataTypes : 767 monitoringMode..........................identifier of [0] MonitoringMode DEFINED in MAP-CH-DataTypes : 358 MonitoringMode..........................type reference ENUMERATED DEFINED in MAP-CH-DataTypes : 363 USED in MAP-CH-DataTypes : 358 moreMessagesToSend......................identifier of NULL DEFINED in MAP-SM-DataTypes : 124 mo-forwardSM............................value reference MO-ForwardSM, CHOICE VALUE DEFINED in MAP-Protocol : 265 MO-ForwardSM............................type reference OPERATION DEFINED in MAP-ShortMessageServic : 81 USED in MAP-Protocol : 88 265 USED in MAP-ShortMessageServic : 14 mo-forwardSM-Arg........................identifier of MO-ForwardSM-Arg DEFINED in MAP-ShortMessageServic : 83 MO-ForwardSM-Arg........................type reference SEQUENCE DEFINED in MAP-SM-DataTypes : 107 USED in MAP-ShortMessageServic : 47 83 USED in MAP-SM-DataTypes : 16 mo-forwardSM-Res........................identifier of MO-ForwardSM-Res DEFINED in MAP-ShortMessageServic : 85 MO-ForwardSM-Res........................type reference SEQUENCE DEFINED in MAP-SM-DataTypes : 115 USED in MAP-ShortMessageServic : 48 85 USED in MAP-SM-DataTypes : 17 mo-lr...................................identifier of Named Number, 2 DEFINED in MAP-LCS-DataTypes : 359 msAvailable.............................identifier of Named Number, 0 DEFINED in MAP-LCS-DataTypes : 126 msc-Number..............................identifier of [1] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 213 msc-Number..............................identifier of [6] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1778 msc-Number..............................identifier of [1] ISDN-AddressString DEFINED in MAP-CH-DataTypes : 200 msc-Number..............................identifier of [0] ISDN-AddressString DEFINED in MAP-SM-DataTypes : 99 msisdn..................................identifier of ISDN-AddressString DEFINED in MAP-OperationAndMainte : 79 msisdn..................................identifier of [1] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 929 msisdn..................................identifier of ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1971 msisdn..................................identifier of [2] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1991 msisdn..................................identifier of [1] ISDN-AddressString DEFINED in MAP-CommonDataTypes : 375
2884
3GPP
2885 Release 4
12885 12886 12887 12888 12889 12890 12891
1057
3GPP TS 29.002 V4.17.0 (2006-06)
msisdn..................................identifier of [0] ISDN-AddressString DEFINED in MAP-CH-DataTypes : 95 msisdn..................................identifier of [12] ISDN-AddressString DEFINED in MAP-CH-DataTypes : 163 msisdn..................................identifier of [2] ISDN-AddressString
2886
3GPP
2887 Release 4
12892 12893 12894 12895 12896 12897 12898 12899 12900 12901 12902 12903 12904 12905 12906 12907 12908 12909 12910 12911 12912 12913 12914 12915 12916 12917 12918 12919 12920 12921 12922 12923 12924 12925 12926 12927 12928 12929 12930 12931 12932 12933 12934 12935 12936 12937 12938 12939 12940 12941 12942 12943 12944 12945 12946 12947 12948 12949 12950 12951 12952 12953 12954 12955 12956 12957 12958 12959 12960 12961 12962 12963 12964 12965 12966 12967 12968
1058
Cross Reference Listing for MAP-Protocol : 201
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 63
DEFINED in MAP-CH-DataTypes
msisdn..................................identifier of [9] ISDN-AddressString DEFINED in MAP-CH-DataTypes : 233 msisdn..................................identifier of [0] ISDN-AddressString DEFINED in MAP-SS-DataTypes : 226 msisdn..................................identifier of [1] ISDN-AddressString DEFINED in MAP-SS-DataTypes : 271 msisdn..................................identifier of [0] ISDN-AddressString DEFINED in MAP-SM-DataTypes : 54 msisdn..................................identifier of [2] ISDN-AddressString DEFINED in MAP-SM-DataTypes : 140 msisdn..................................identifier of ISDN-AddressString DEFINED in MAP-SM-DataTypes : 145 msisdn..................................identifier of ISDN-AddressString DEFINED in MAP-SM-DataTypes : 179 msisdn..................................identifier of [3] ISDN-AddressString DEFINED in MAP-LCS-DataTypes : 94 msisdn..................................identifier of [0] ISDN-AddressString DEFINED in MAP-LCS-DataTypes : 319 msNotReachable..........................identifier of NULL DEFINED in MAP-MS-DataTypes : 1707 msPurged................................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 1819 ms-Present..............................identifier of Named Number, 0 DEFINED in MAP-SM-DataTypes : 218 mt-forwardSM............................value reference MT-ForwardSM, CHOICE VALUE DEFINED in MAP-Protocol : 266 MT-ForwardSM............................type reference OPERATION DEFINED in MAP-ShortMessageServic : 93 USED in MAP-Protocol : 89 266 USED in MAP-ShortMessageServic : 15 mt-forwardSM-Arg........................identifier of MT-ForwardSM-Arg DEFINED in MAP-ShortMessageServic : 95 MT-ForwardSM-Arg........................type reference SEQUENCE DEFINED in MAP-SM-DataTypes : 120 USED in MAP-ShortMessageServic : 49 95 USED in MAP-SM-DataTypes : 18 mt-forwardSM-Res........................identifier of MT-ForwardSM-Res DEFINED in MAP-ShortMessageServic : 97 MT-ForwardSM-Res........................type reference SEQUENCE DEFINED in MAP-SM-DataTypes : 128 USED in MAP-ShortMessageServic : 50 97 USED in MAP-SM-DataTypes : 19 mt-lrRestart............................identifier of Named Number, 4 DEFINED in MAP-LCS-DataTypes : 371 multicallBearerInfo.....................identifier of [3] MulticallBearerInfo DEFINED in MAP-MS-DataTypes : 559 MulticallBearerInfo.....................type reference INTEGER DEFINED in MAP-MS-DataTypes : 654 USED in MAP-MS-DataTypes : 559 multipleBearerNotSupported..............identifier of NULL DEFINED in MAP-MS-DataTypes : 560
2888
3GPP
2889 Release 4
12969 12970 12971 12972 12973 12974 12975
1059
3GPP TS 29.002 V4.17.0 (2006-06)
multipleBearerRequested.................identifier of [3] NULL DEFINED in MAP-MS-DataTypes : 505 multipleECT-Barred......................identifier of Named Number, 14 DEFINED in MAP-MS-DataTypes : 985 multiPTY................................value reference SS-Code, '01010001'B
2890
3GPP
2891 Release 4
12976 12977 12978 12979 12980 12981 12982 12983 12984 12985 12986 12987 12988 12989 12990 12991 12992 12993 12994 12995 12996 12997 12998 12999 13000 13001 13002 13003 13004 13005 13006 13007 13008 13009 13010 13011 13012 13013 13014 13015 13016 13017 13018 13019 13020 13021 13022 13023 13024 13025 13026 13027 13028 13029 13030 13031 13032 13033 13034 13035 13036 13037 13038 13039 13040 13041 13042 13043 13044 13045 13046 13047 13048 13049 13050 13051 13052
1060
Cross Reference Listing for MAP-Protocol : 90
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 64
DEFINED in MAP-SS-Code
mw-Status...............................identifier of MW-Status DEFINED in MAP-SM-DataTypes : 185 MW-Status...............................type reference BIT STRING DEFINED in MAP-SM-DataTypes : 195 USED in MAP-SM-DataTypes : 185 m-csi...................................identifier of Named Number, 6 DEFINED in MAP-MS-DataTypes : 1299 m-CSI...................................identifier of [5] M-CSI DEFINED in MAP-MS-DataTypes : 1337 M-CSI...................................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1579 USED in MAP-MS-DataTypes : 1337 1914 m-CSI...................................identifier of Named Number, 7 DEFINED in MAP-MS-DataTypes : 1876 m-CSI...................................identifier of [12] M-CSI DEFINED in MAP-MS-DataTypes : 1914 NAEA-CIC................................type reference OCTET STRING DEFINED in MAP-CommonDataTypes : 366 USED in MAP-CommonDataTypes : 40 362 naea-PreferredCI........................identifier of [15] NAEA-PreferredCI DEFINED in MAP-MS-DataTypes : 739 NAEA-PreferredCI........................type reference SEQUENCE DEFINED in MAP-CommonDataTypes : 361 USED in MAP-MS-DataTypes : 177 739 USED in MAP-CommonDataTypes : 39 USED in MAP-CH-DataTypes : 72 160 naea-PreferredCI........................identifier of [10] NAEA-PreferredCI DEFINED in MAP-CH-DataTypes : 160 naea-PreferredCIC.......................identifier of [0] NAEA-CIC DEFINED in MAP-CommonDataTypes : 362 nameString..............................identifier of [2] NameString DEFINED in MAP-LCS-DataTypes : 154 NameString..............................type reference USSD-String DEFINED in MAP-LCS-DataTypes : 162 USED in MAP-LCS-DataTypes : 154 na-ESRD.................................identifier of [3] ISDN-AddressString DEFINED in MAP-LCS-DataTypes : 322 na-ESRK.................................identifier of [4] ISDN-AddressString DEFINED in MAP-LCS-DataTypes : 323 na-ESRK.................................identifier of [0] ISDN-AddressString DEFINED in MAP-LCS-DataTypes : 386 na-ESRK-Request.........................identifier of [0] NULL DEFINED in MAP-ExtensionDataTypes : 67 nbrSB...................................identifier of [2] MaxMC-Bearers DEFINED in MAP-CommonDataTypes : 461 nbrSB...................................identifier of [3] MaxMC-Bearers DEFINED in MAP-SS-DataTypes : 197 nbrSN...................................identifier of [5] MC-Bearers DEFINED in MAP-SS-DataTypes : 199 nbrUser.................................identifier of [3] MC-Bearers DEFINED in MAP-CommonDataTypes : 462
2892
3GPP
2893 Release 4
13053 13054 13055 13056 13057 13058 13059
1061
3GPP TS 29.002 V4.17.0 (2006-06)
nbrUser.................................identifier of [8] MC-Bearers DEFINED in MAP-SS-DataTypes : 80 nbrUser.................................identifier of [5] MC-Bearers DEFINED in MAP-SS-DataTypes : 168 nbrUser.................................identifier of [4] MC-Bearers
2894
3GPP
2895 Release 4
13060 13061 13062 13063 13064 13065 13066 13067 13068 13069 13070 13071 13072 13073 13074 13075 13076 13077 13078 13079 13080 13081 13082 13083 13084 13085 13086 13087 13088 13089 13090 13091 13092 13093 13094 13095 13096 13097 13098 13099 13100 13101 13102 13103 13104 13105 13106 13107 13108 13109 13110 13111 13112 13113 13114 13115 13116 13117 13118 13119 13120 13121 13122 13123 13124 13125 13126 13127 13128 13129 13130 13131 13132 13133 13134 13135 13136
1062
Cross Reference Listing for MAP-Protocol : 198
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 65
DEFINED in MAP-SS-DataTypes
negativePW-Check........................value reference NegativePW-Check, CHOICE VALUE DEFINED in MAP-Protocol : 412 NegativePW-Check........................type reference ERROR DEFINED in MAP-Errors : 384 USED in MAP-Protocol : 152 412 USED in MAP-SupplementaryServi : 46 138 157 229 USED in MAP-Errors : 71 netDetNotReachable......................identifier of NotReachableReason DEFINED in MAP-MS-DataTypes : 1815 networkAccessMode.......................identifier of [24] NetworkAccessMode DEFINED in MAP-MS-DataTypes : 744 NetworkAccessMode.......................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 777 USED in MAP-MS-DataTypes : 744 networkNode-AreaRestricted..............identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 1266 networkNode-Number......................identifier of [1] ISDN-AddressString DEFINED in MAP-SM-DataTypes : 87 networkNode-Number......................identifier of ISDN-AddressString DEFINED in MAP-LCS-DataTypes : 78 NetworkResource.........................type reference ENUMERATED DEFINED in MAP-CommonDataTypes : 351 USED in MAP-CommonDataTypes : 38 USED in MAP-ER-DataTypes : 75 172 179 networkResource.........................identifier of NetworkResource DEFINED in MAP-ER-DataTypes : 172 networkResource.........................identifier of NetworkResource DEFINED in MAP-ER-DataTypes : 179 networkSignalInfo.......................identifier of [10] ExternalSignalInfo DEFINED in MAP-CH-DataTypes : 105 networkSignalInfo.......................identifier of [6] ExternalSignalInfo DEFINED in MAP-CH-DataTypes : 204 networkSignalInfo.......................identifier of [4] ExternalSignalInfo DEFINED in MAP-SS-DataTypes : 315 new.....................................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 494 newPassword.............................identifier of Password DEFINED in MAP-SupplementaryServi : 221 newPasswordsMismatch....................identifier of Named Number, 2 DEFINED in MAP-ER-DataTypes : 139 noAdditionalInformation.................identifier of Named Number, 0 DEFINED in MAP-ER-DataTypes : 350 noCUG-Restrictions......................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 1125 noGroupCallNbParam......................identifier of NoGroupCallNbParam DEFINED in MAP-Errors : 424 NoGroupCallNbParam......................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 326 USED in MAP-Errors : 137 424 USED in MAP-ER-DataTypes : 45 noGroupCallNumberAvailable..............value reference NoGroupCallNumberAvailable, CHOICE VALUE DEFINED in MAP-Protocol : 399
2896
3GPP
2897 Release 4
13137 13138 13139 13140 13141 13142 13143
1063
3GPP TS 29.002 V4.17.0 (2006-06)
NoGroupCallNumberAvailable..............type reference ERROR DEFINED in MAP-Errors : 422 USED in MAP-Protocol : 159 399 USED in MAP-Group-Call-Operati : 26 53 USED in MAP-Errors : 83
2898
3GPP
2899 Release 4
13144 13145 13146 13147 13148 13149 13150 13151 13152 13153 13154 13155 13156 13157 13158 13159 13160 13161 13162 13163 13164 13165 13166 13167 13168 13169 13170 13171 13172 13173 13174 13175 13176 13177 13178 13179 13180 13181 13182 13183 13184 13185 13186 13187 13188 13189 13190 13191 13192 13193 13194 13195 13196 13197 13198 13199 13200 13201 13202 13203 13204 13205 13206 13207 13208 13209 13210 13211 13212 13213 13214 13215 13216 13217 13218 13219 13220
1064
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 66
noHandoverNumberAvailable...............value reference NoHandoverNumberAvailable, CHOICE VALUE DEFINED in MAP-Protocol : 361 NoHandoverNumberAvailable...............type reference ERROR DEFINED in MAP-Errors : 255 USED in MAP-Protocol : 131 361 USED in MAP-MobileServiceOpera : 91 319 USED in MAP-Errors : 36 noPageResponse..........................identifier of Named Number, 2 DEFINED in MAP-ER-DataTypes : 254 noReply.................................identifier of Named Number, 2 DEFINED in MAP-CH-DataTypes : 132 noReplyConditionTime....................identifier of [7] Ext-NoRepCondTime DEFINED in MAP-MS-DataTypes : 1046 noReplyConditionTime....................identifier of [5] Ext-NoRepCondTime DEFINED in MAP-MS-DataTypes : 1941 noReplyConditionTime....................identifier of [5] NoReplyConditionTime DEFINED in MAP-SS-DataTypes : 77 NoReplyConditionTime....................type reference INTEGER DEFINED in MAP-SS-DataTypes : 83 USED in MAP-SS-DataTypes : 30 77 105 noReplyConditionTime....................identifier of [7] NoReplyConditionTime DEFINED in MAP-SS-DataTypes : 105 noResponseFromBusyMS....................identifier of Named Number, 3 DEFINED in MAP-CH-DataTypes : 404 noResponseFromFreeMS....................identifier of Named Number, 2 DEFINED in MAP-CH-DataTypes : 403 normal..................................identifier of Named Number, 0 DEFINED in MAP-LCS-DataTypes : 367 noRoamingNbParam........................identifier of NoRoamingNbParam DEFINED in MAP-Errors : 277 NoRoamingNbParam........................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 242 USED in MAP-Errors : 123 277 USED in MAP-ER-DataTypes : 33 noRoamingNumberAvailable................value reference NoRoamingNumberAvailable, CHOICE VALUE DEFINED in MAP-Protocol : 377 NoRoamingNumberAvailable................type reference ERROR DEFINED in MAP-Errors : 275 USED in MAP-Protocol : 135 377 USED in MAP-CallHandlingOperat : 39 116 USED in MAP-Errors : 45 noSM-RP-DA..............................identifier of [5] NULL DEFINED in MAP-SM-DataTypes : 137 noSM-RP-OA..............................identifier of [5] NULL DEFINED in MAP-SM-DataTypes : 142 noSubscriberReply.......................value reference NoSubscriberReply, CHOICE VALUE DEFINED in MAP-Protocol : 380 NoSubscriberReply.......................type reference ERROR DEFINED in MAP-Errors : 292 USED in MAP-Protocol : 138 380 USED in MAP-CallHandlingOperat : 42 98 USED in MAP-Errors : 47 noSubscriberReplyParam..................identifier of NoSubscriberReplyParam DEFINED in MAP-Errors : 294
2900
3GPP
2901 Release 4
13221 13222 13223 13224 13225 13226 13227
1065
3GPP TS 29.002 V4.17.0 (2006-06)
NoSubscriberReplyParam..................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 271 USED in MAP-Errors : 127 294 USED in MAP-ER-DataTypes : 36 NoteMM-Event............................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 477
2902
3GPP
2903 Release 4
13228 13229 13230 13231 13232 13233 13234 13235 13236 13237 13238 13239 13240 13241 13242 13243 13244 13245 13246 13247 13248 13249 13250 13251 13252 13253 13254 13255 13256 13257 13258 13259 13260 13261 13262 13263 13264 13265 13266 13267 13268 13269 13270 13271 13272 13273 13274 13275 13276 13277 13278 13279 13280 13281 13282 13283 13284 13285 13286 13287 13288 13289 13290 13291 13292 13293 13294 13295 13296 13297 13298 13299 13300 13301 13302 13303 13304
1066
Cross Reference Listing for MAP-Protocol 70
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 67
USED in MAP-Protocol : 37 USED in MAP-MobileServiceOpera :
noteMM-EventArg.........................identifier of NoteMM-EventArg DEFINED in MAP-MobileServiceOpera : 479 NoteMM-EventArg.........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1987 USED in MAP-MobileServiceOpera : 159 479 USED in MAP-MS-DataTypes : 131 noteMM-EventRes.........................identifier of NoteMM-EventRes DEFINED in MAP-MobileServiceOpera : 481 NoteMM-EventRes.........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1997 USED in MAP-MobileServiceOpera : 160 481 USED in MAP-MS-DataTypes : 132 noteMsPresentForGprs....................value reference NoteMsPresentForGprs, CHOICE VALUE DEFINED in MAP-Protocol : 316 NoteMsPresentForGprs....................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 464 USED in MAP-Protocol : 36 316 USED in MAP-MobileServiceOpera : 67 noteMsPresentForGprsArg.................identifier of NoteMsPresentForGprsArg DEFINED in MAP-MobileServiceOpera : 466 NoteMsPresentForGprsArg.................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1679 USED in MAP-MobileServiceOpera : 157 466 USED in MAP-MS-DataTypes : 127 noteMsPresentForGprsRes.................identifier of NoteMsPresentForGprsRes DEFINED in MAP-MobileServiceOpera : 468 NoteMsPresentForGprsRes.................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1686 USED in MAP-MobileServiceOpera : 158 468 USED in MAP-MS-DataTypes : 128 noteSubscriberDataModified..............value reference NoteSubscriberDataModified, CHOICE VALUE DEFINED in MAP-Protocol : 287 NoteSubscriberDataModified..............type reference OPERATION DEFINED in MAP-MobileServiceOpera : 296 USED in MAP-Protocol : 38 287 USED in MAP-MobileServiceOpera : 34 noteSubscriberDataModifiedArg...........identifier of NoteSubscriberDataModifiedArg DEFINED in MAP-MobileServiceOpera : 298 NoteSubscriberDataModifiedArg...........type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1969 USED in MAP-MobileServiceOpera : 149 298 USED in MAP-MS-DataTypes : 115 noteSubscriberDataModifiedRes...........identifier of NoteSubscriberDataModifiedRes DEFINED in MAP-MobileServiceOpera : 300 NoteSubscriberDataModifiedRes...........type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1980 USED in MAP-MobileServiceOpera : 150 300 USED in MAP-MS-DataTypes : 116 notForwarded............................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 1493 notificationToCSE.......................identifier of [3] NULL DEFINED in MAP-MS-DataTypes : 824 notificationToCSE.......................identifier of [3] NULL DEFINED in MAP-MS-DataTypes : 1347
2904
3GPP
2905 Release 4
13305 13306 13307 13308 13309 13310 13311
1067
3GPP TS 29.002 V4.17.0 (2006-06)
notificationToCSE.......................identifier of [0] NULL DEFINED in MAP-MS-DataTypes : 1375 notificationToCSE.......................identifier of [1] NULL DEFINED in MAP-MS-DataTypes : 1405
2906
3GPP
2907 Release 4
13312 13313 13314 13315 13316 13317 13318 13319 13320 13321 13322 13323 13324 13325 13326 13327 13328 13329 13330 13331 13332 13333 13334 13335 13336 13337 13338 13339 13340 13341 13342 13343 13344 13345 13346 13347 13348 13349 13350 13351 13352 13353 13354 13355 13356 13357 13358 13359 13360 13361 13362 13363 13364 13365 13366 13367 13368 13369 13370 13371 13372 13373 13374 13375 13376 13377 13378 13379 13380 13381 13382 13383 13384 13385 13386 13387 13388
1068
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 68
notificationToCSE.......................identifier of [3] NULL DEFINED in MAP-MS-DataTypes : 1539 notificationToCSE.......................identifier of [2] NULL DEFINED in MAP-MS-DataTypes : 1584 notificationToCSE.......................identifier of [1] NULL DEFINED in MAP-MS-DataTypes : 1613 notificationToCSE.......................identifier of NULL DEFINED in MAP-MS-DataTypes : 1881 notificationToCSE.......................identifier of NULL DEFINED in MAP-MS-DataTypes : 1889 notificationToCSE.......................identifier of NULL DEFINED in MAP-MS-DataTypes : 1897 notificationToCSE.......................identifier of [2] NULL DEFINED in MAP-MS-DataTypes : 2009 notificationToCSE.......................identifier of [4] NULL DEFINED in MAP-MS-DataTypes : 2018 notificationToMSUser....................identifier of [0] NotificationToMSUser DEFINED in MAP-MS-DataTypes : 1174 notificationToMSUser....................identifier of [1] NotificationToMSUser DEFINED in MAP-MS-DataTypes : 1212 NotificationToMSUser....................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 1226 USED in MAP-MS-DataTypes : 81 1174 1212 notifyAndVerify-LocationAllowedIfNoRespoidentifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 1228 notifyAndVerify-LocationNotAllowedIfNoReidentifier of Named Number, 2 DEFINED in MAP-MS-DataTypes : 1229 notifyLocationAllowed...................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 1227 notKnownToBePorted......................identifier of Named Number, 0 DEFINED in MAP-CH-DataTypes : 169 notProvidedFromVLR......................identifier of [2] NULL DEFINED in MAP-MS-DataTypes : 1816 notReachable............................identifier of Named Number, 0 DEFINED in MAP-CH-DataTypes : 130 NotReachableReason......................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 1818 USED in MAP-MS-DataTypes : 1815 notRegistered...........................identifier of Named Number, 3 DEFINED in MAP-MS-DataTypes : 1822 not-derivable...........................identifier of NULL DEFINED in TCAPMessages : 168 npdbMismatch............................identifier of Named Number, 2 DEFINED in MAP-ER-DataTypes : 209 numberChanged...........................value reference NumberChanged, CHOICE VALUE DEFINED in MAP-Protocol : 342 NumberChanged...........................type reference ERROR DEFINED in MAP-Errors : 206 USED in MAP-Protocol : 122 342 USED in MAP-CallHandlingOperat : 36 93 USED in MAP-Errors : 23 numberChangedParam......................identifier of NumberChangedParam
2908
3GPP
2909 Release 4
13389 13390 13391 13392 13393 13394 13395
1069
: 208
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-Errors
NumberChangedParam......................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 214 USED in MAP-Errors : 115 208 USED in MAP-ER-DataTypes : 26
2910
3GPP
2911 Release 4
13396 13397 13398 13399 13400 13401 13402 13403 13404 13405 13406 13407 13408 13409 13410 13411 13412 13413 13414 13415 13416 13417 13418 13419 13420 13421 13422 13423 13424 13425 13426 13427 13428 13429 13430 13431 13432 13433 13434 13435 13436 13437 13438 13439 13440 13441 13442 13443 13444 13445 13446 13447 13448 13449 13450 13451 13452 13453 13454 13455 13456 13457 13458 13459 13460 13461 13462 13463 13464 13465 13466 13467 13468 13469 13470 13471 13472
1070
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 69
NumberOfForwarding......................type reference INTEGER DEFINED in MAP-CH-DataTypes : 92 USED in MAP-CH-DataTypes : 20 97 numberOfForwarding......................identifier of [2] NumberOfForwarding DEFINED in MAP-CH-DataTypes : 97 numberOfPW-AttemptsViolation.........value reference NumberOfPW-AttemptsViolation, CHOICE VALUE DEFINED in MAP-Protocol : 413 NumberOfPW-AttemptsViolation............type reference ERROR DEFINED in MAP-Errors : 386 USED in MAP-Protocol : 153 413 USED in MAP-SupplementaryServi : 47 139 158 230 USED in MAP-Errors : 72 numberOfRequestedVectors................identifier of NumberOfRequestedVectors DEFINED in MAP-MS-DataTypes : 297 numberOfRequestedVectors................identifier of NumberOfRequestedVectors DEFINED in MAP-MS-DataTypes : 696 NumberOfRequestedVectors................type reference INTEGER DEFINED in MAP-MS-DataTypes : 704 USED in MAP-MS-DataTypes : 297 696 numberPortabilityStatus.................identifier of [13] NumberPortabilityStatus DEFINED in MAP-CH-DataTypes : 164 NumberPortabilityStatus.................type reference ENUMERATED DEFINED in MAP-CH-DataTypes : 168 USED in MAP-CH-DataTypes : 164 odb.....................................identifier of [2] NULL DEFINED in MAP-MS-DataTypes : 1861 odb-Data................................identifier of [8] ODB-Data DEFINED in MAP-MS-DataTypes : 939 ODB-Data................................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 964 USED in MAP-MS-DataTypes : 61 939 1896 odb-Data................................identifier of ODB-Data DEFINED in MAP-MS-DataTypes : 1896 odb-GeneralData.........................identifier of ODB-GeneralData DEFINED in MAP-MS-DataTypes : 965 ODB-GeneralData.........................type reference BIT STRING DEFINED in MAP-MS-DataTypes : 970 USED in MAP-MS-DataTypes : 965 1259 odb-GeneralData.........................identifier of [4] ODB-GeneralData DEFINED in MAP-MS-DataTypes : 1259 odb-HPLMN-Data..........................identifier of ODB-HPLMN-Data DEFINED in MAP-MS-DataTypes : 966 ODB-HPLMN-Data..........................type reference BIT STRING DEFINED in MAP-MS-DataTypes : 1006 USED in MAP-MS-DataTypes : 966 odb-Info................................identifier of [3] ODB-Info DEFINED in MAP-MS-DataTypes : 1852 ODB-Info................................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1895 USED in MAP-MS-DataTypes : 1852 1974 odb-Info................................identifier of [2] ODB-Info DEFINED in MAP-MS-DataTypes : 1974 old.....................................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 493
2912
3GPP
2913 Release 4
13473 13474 13475 13476 13477 13478 13479
1071
3GPP TS 29.002 V4.17.0 (2006-06)
omc-Id..................................identifier of [3] AddressString DEFINED in MAP-OM-DataTypes : 40 onlyMSC.................................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 779
2914
3GPP
2915 Release 4
13480 13481 13482 13483 13484 13485 13486 13487 13488 13489 13490 13491 13492 13493 13494 13495 13496 13497 13498 13499 13500 13501 13502 13503 13504 13505 13506 13507 13508 13509 13510 13511 13512 13513 13514 13515 13516 13517 13518 13519 13520 13521 13522 13523 13524 13525 13526 13527 13528 13529 13530 13531 13532 13533 13534 13535 13536 13537 13538 13539 13540 13541 13542 13543 13544 13545 13546 13547 13548 13549 13550 13551 13552 13553 13554 13555 13556
1072
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 70
onlySGSN................................identifier of Named Number, 2 DEFINED in MAP-MS-DataTypes : 780 operationCode...........................identifier of OPERATION DEFINED in TCAPMessages : 136 USED in TCAPMessages : 137 operationCode...........................identifier of OPERATION DEFINED in TCAPMessages : 147 USED in TCAPMessages : 148 operatorBarring.........................identifier of Named Number, 1 DEFINED in MAP-ER-DataTypes : 111 operatorDeterminedBarring...............identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 952 operatorDeterminedBarring...............identifier of Named Number, 3 DEFINED in MAP-ER-DataTypes : 100 OrigTransactionID.......................type reference [APPLICATION 8] IMPLICIT TransactionID DEFINED in TCAPMessages : 97 USED in TCAPMessages : 61 69 orNotSupportedInGMSC....................identifier of [16] NULL DEFINED in MAP-CH-DataTypes : 215 or-Capability...........................identifier of [5] OR-Phase DEFINED in MAP-CH-DataTypes : 100 or-Interrogation........................identifier of [4] NULL DEFINED in MAP-CH-DataTypes : 99 or-Interrogation........................identifier of [10] NULL DEFINED in MAP-CH-DataTypes : 208 or-NotAllowed...........................value reference OR-NotAllowed, CHOICE VALUE DEFINED in MAP-Protocol : 383 OR-NotAllowed...........................type reference ERROR DEFINED in MAP-Errors : 317 USED in MAP-Protocol : 134 383 USED in MAP-CallHandlingOperat : 34 91 114 126 USED in MAP-Errors : 44 or-NotAllowedParam......................identifier of OR-NotAllowedParam DEFINED in MAP-Errors : 319 OR-NotAllowedParam......................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 196 USED in MAP-Errors : 124 319 USED in MAP-ER-DataTypes : 24 OR-Phase................................type reference INTEGER DEFINED in MAP-CH-DataTypes : 125 USED in MAP-CH-DataTypes : 100 otid....................................identifier of OrigTransactionID DEFINED in TCAPMessages : 61 otid....................................identifier of OrigTransactionID DEFINED in TCAPMessages : 69 overrideCategory........................identifier of [1] OverrideCategory DEFINED in MAP-SS-DataTypes : 173 OverrideCategory........................type reference ENUMERATED DEFINED in MAP-SS-DataTypes : 180 USED in MAP-SS-DataTypes : 28 173 overrideDisabled........................identifier of Named Number, 1 DEFINED in MAP-SS-DataTypes : 182 overrideEnabled.........................identifier of Named Number, 0 DEFINED in MAP-SS-DataTypes : 181
2916
3GPP
2917 Release 4
13557 13558 13559 13560 13561 13562 13563
1073
3GPP TS 29.002 V4.17.0 (2006-06)
ownNumberPortedOut......................identifier of Named Number, 1 DEFINED in MAP-CH-DataTypes : 170 o-andM-HPLMN............................identifier of Named Number, 1 DEFINED in MAP-CommonDataTypes : 385
2918
3GPP
2919 Release 4
13564 13565 13566 13567 13568 13569 13570 13571 13572 13573 13574 13575 13576 13577 13578 13579 13580 13581 13582 13583 13584 13585 13586 13587 13588 13589 13590 13591 13592 13593 13594 13595 13596 13597 13598 13599 13600 13601 13602 13603 13604 13605 13606 13607 13608 13609 13610 13611 13612 13613 13614 13615 13616 13617 13618 13619 13620 13621 13622 13623 13624 13625 13626 13627 13628 13629 13630 13631 13632 13633 13634 13635 13636 13637 13638 13639 13640
1074
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 71
o-andM-VPLMN............................identifier of Named Number, 2 DEFINED in MAP-CommonDataTypes : 386 O-BcsmCamelTDPCriteriaList..............type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1443 USED in MAP-MS-DataTypes : 67 1335 1903 USED in MAP-CH-DataTypes : 45 277 O-BcsmCamelTDPData......................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1420 USED in MAP-MS-DataTypes : 1412 o-BcsmCamelTDPDataList..................identifier of O-BcsmCamelTDPDataList DEFINED in MAP-MS-DataTypes : 1401 O-BcsmCamelTDPDataList..................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1411 USED in MAP-MS-DataTypes : 1401 O-BcsmCamelTDP-Criteria.................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1449 USED in MAP-MS-DataTypes : 1444 o-BcsmCamelTDP-CriteriaList.............identifier of [4] O-BcsmCamelTDPCriteriaList DEFINED in MAP-MS-DataTypes : 1335 o-BcsmCamelTDP-CriteriaList.............identifier of [1] O-BcsmCamelTDPCriteriaList DEFINED in MAP-MS-DataTypes : 1903 o-BcsmCamelTDP-CriteriaList.............identifier of [3] O-BcsmCamelTDPCriteriaList DEFINED in MAP-CH-DataTypes : 277 o-BcsmTriggerDetectionPoint.............identifier of O-BcsmTriggerDetectionPoint DEFINED in MAP-MS-DataTypes : 1421 O-BcsmTriggerDetectionPoint.............type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 1431 USED in MAP-MS-DataTypes : 1421 1450 o-BcsmTriggerDetectionPoint.............identifier of O-BcsmTriggerDetectionPoint DEFINED in MAP-MS-DataTypes : 1450 o-CauseValueCriteria....................identifier of [3] O-CauseValueCriteria DEFINED in MAP-MS-DataTypes : 1455 O-CauseValueCriteria....................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1499 USED in MAP-MS-DataTypes : 1455 o-csi...................................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 1293 o-CSI...................................identifier of [0] O-CSI DEFINED in MAP-MS-DataTypes : 1331 O-CSI...................................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1400 USED in MAP-MS-DataTypes : 65 1331 1902 USED in MAP-CH-DataTypes : 43 230 274 o-CSI...................................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 1869 o-CSI...................................identifier of [0] O-CSI DEFINED in MAP-MS-DataTypes : 1902 o-CSI...................................identifier of [5] O-CSI DEFINED in MAP-CH-DataTypes : 230 o-CSI...................................identifier of [1] O-CSI DEFINED in MAP-CH-DataTypes : 274 padAccessCA-1200bps.....................value reference BearerServiceCode, '00100010'B DEFINED in MAP-BS-Code : 69
2920
3GPP
2921 Release 4
13641 13642 13643 13644 13645 13646 13647
1075
3GPP TS 29.002 V4.17.0 (2006-06)
padAccessCA-1200-75bps..................value reference BearerServiceCode, '00100011'B DEFINED in MAP-BS-Code : 70 padAccessCA-2400bps.....................value reference BearerServiceCode, '00100100'B DEFINED in MAP-BS-Code : 71 padAccessCA-300bps......................value reference BearerServiceCode, '00100001'B
2922
3GPP
2923 Release 4
13648 13649 13650 13651 13652 13653 13654 13655 13656 13657 13658 13659 13660 13661 13662 13663 13664 13665 13666 13667 13668 13669 13670 13671 13672 13673 13674 13675 13676 13677 13678 13679 13680 13681 13682 13683 13684 13685 13686 13687 13688 13689 13690 13691 13692 13693 13694 13695 13696 13697 13698 13699 13700 13701 13702 13703 13704 13705 13706 13707 13708 13709 13710 13711 13712 13713 13714 13715 13716 13717 13718 13719 13720 13721 13722 13723 13724
1076
Cross Reference Listing for MAP-Protocol : 68
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 72
DEFINED in MAP-BS-Code
padAccessCA-4800bps.....................value reference BearerServiceCode, '00100101'B DEFINED in MAP-BS-Code : 72 padAccessCA-9600bps.....................value reference BearerServiceCode, '00100110'B DEFINED in MAP-BS-Code : 73 parameter...............................identifier of ANY DEFINED BY operationCode DEFINED in TCAPMessages : 137 parameter...............................identifier of ANY DEFINED BY operationCode DEFINED in TCAPMessages : 148 parameter...............................identifier of ANY DEFINED BY errorCode DEFINED in TCAPMessages : 159 password................................identifier of Password DEFINED in MAP-MS-DataTypes : 1887 password................................identifier of [3] Password DEFINED in MAP-MS-DataTypes : 1950 password................................identifier of [2] Password DEFINED in MAP-MS-DataTypes : 2016 Password................................type reference NumericString DEFINED in MAP-SS-DataTypes : 244 USED in MAP-SupplementaryServi : 66 221 238 USED in MAP-MS-DataTypes : 143 1887 1950 2016 USED in MAP-SS-DataTypes : 24 pcs-Extensions..........................identifier of [1] PCS-Extensions DEFINED in MAP-ExtensionDataTypes : 35 PCS-Extensions..........................type reference SEQUENCE DEFINED in MAP-ExtensionDataTypes : 62 USED in MAP-ExtensionDataTypes : 35 pdpContextActivation....................identifier of Named Number, 8 DEFINED in MAP-MS-DataTypes : 399 pdpContextDeactivation..................identifier of Named Number, 9 DEFINED in MAP-MS-DataTypes : 400 pdp-Address.............................identifier of [17] PDP-Address DEFINED in MAP-MS-DataTypes : 793 PDP-Address.............................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 874 USED in MAP-MS-DataTypes : 793 pdp-ChargingCharacteristics.............identifier of [1] ChargingCharacteristics DEFINED in MAP-MS-DataTypes : 800 PDP-Context.............................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 790 USED in MAP-MS-DataTypes : 786 pdp-ContextChangeOfPosition.............identifier of Named Number, 14 DEFINED in MAP-MS-DataTypes : 861 pdp-ContextEstablishment................identifier of Named Number, 11 DEFINED in MAP-MS-DataTypes : 859 pdp-ContextEstablishmentAcknowledgement.identifier of Named Number, 12 DEFINED in MAP-MS-DataTypes : 860 pdp-ContextId...........................identifier of ContextId DEFINED in MAP-MS-DataTypes : 791 pdp-Type................................identifier of [16] PDP-Type DEFINED in MAP-MS-DataTypes : 792 PDP-Type................................type reference OCTET STRING
2924
3GPP
2925 Release 4
13725 13726 13727 13728 13729 13730 13731
1077
: : 871 792
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-MS-DataTypes USED in MAP-MS-DataTypes
permanent...............................identifier of Named Number, 0 DEFINED in MAP-SS-DataTypes : 176 PermittedEncryptionAlgorithms...........type reference OCTET STRING
2926
3GPP
2927 Release 4
13732 13733 13734 13735 13736 13737 13738 13739 13740 13741 13742 13743 13744 13745 13746 13747 13748 13749 13750 13751 13752 13753 13754 13755 13756 13757 13758 13759 13760 13761 13762 13763 13764 13765 13766 13767 13768 13769 13770 13771 13772 13773 13774 13775 13776 13777 13778 13779 13780 13781 13782 13783 13784 13785 13786 13787 13788 13789 13790 13791 13792 13793 13794 13795 13796 13797 13798 13799 13800 13801 13802 13803 13804 13805 13806 13807 13808
1078
Cross Reference Listing for MAP-Protocol : : 481 466
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 73
DEFINED in MAP-MS-DataTypes USED in MAP-MS-DataTypes
PermittedIntegrityProtectionAlgorithms..type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 470 USED in MAP-MS-DataTypes : 465 phase1..................................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 1529 phase2..................................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 1530 phase3..................................identifier of Named Number, 2 DEFINED in MAP-MS-DataTypes : 1531 plmn....................................identifier of Named Number, 0 DEFINED in MAP-CommonDataTypes : 352 plmnClientList..........................identifier of [2] PLMNClientList DEFINED in MAP-MS-DataTypes : 1184 PLMNClientList..........................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1199 USED in MAP-MS-DataTypes : 1184 plmnoperator............................value reference SS-Code, '10110100'B DEFINED in MAP-SS-Code : 168 plmnOperatorServices....................identifier of Named Number, 2 DEFINED in MAP-LCS-DataTypes : 144 plmnRoamingNotAllowed...................identifier of Named Number, 0 DEFINED in MAP-ER-DataTypes : 99 plmn-SpecificBarringType1...............identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 1007 plmn-SpecificBarringType2...............identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 1008 plmn-SpecificBarringType3...............identifier of Named Number, 2 DEFINED in MAP-MS-DataTypes : 1009 plmn-SpecificBarringType4...............identifier of Named Number, 3 DEFINED in MAP-MS-DataTypes : 1010 plmn-specificBS-1.......................value reference BearerServiceCode, '11010001'B DEFINED in MAP-BS-Code : 111 plmn-specificBS-2.......................value reference BearerServiceCode, '11010010'B DEFINED in MAP-BS-Code : 112 plmn-specificBS-3.......................value reference BearerServiceCode, '11010011'B DEFINED in MAP-BS-Code : 113 plmn-specificBS-4.......................value reference BearerServiceCode, '11010100'B DEFINED in MAP-BS-Code : 114 plmn-specificBS-5.......................value reference BearerServiceCode, '11010101'B DEFINED in MAP-BS-Code : 115 plmn-specificBS-6.......................value reference BearerServiceCode, '11010110'B DEFINED in MAP-BS-Code : 116 plmn-specificBS-7.......................value reference BearerServiceCode, '11010111'B DEFINED in MAP-BS-Code : 117 plmn-specificBS-8.......................value reference BearerServiceCode, '11011000'B DEFINED in MAP-BS-Code : 118 plmn-specificBS-9.......................value reference BearerServiceCode, '11011001'B DEFINED in MAP-BS-Code : 119 plmn-specificBS-A.......................value reference BearerServiceCode, '11011010'B
2928
3GPP
2929 Release 4
13809 13810 13811 13812 13813 13814 13815
1079
: 120
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-BS-Code
plmn-specificBS-B.......................value reference BearerServiceCode, '11011011'B DEFINED in MAP-BS-Code : 121 plmn-specificBS-C.......................value reference BearerServiceCode, '11011100'B DEFINED in MAP-BS-Code : 122
2930
3GPP
2931 Release 4
13816 13817 13818 13819 13820 13821 13822 13823 13824 13825 13826 13827 13828 13829 13830 13831 13832 13833 13834 13835 13836 13837 13838 13839 13840 13841 13842 13843 13844 13845 13846 13847 13848 13849 13850 13851 13852 13853 13854 13855 13856 13857 13858 13859 13860 13861 13862 13863 13864 13865 13866 13867 13868 13869 13870 13871 13872 13873 13874 13875 13876 13877 13878 13879 13880 13881 13882 13883 13884 13885 13886 13887 13888 13889 13890 13891 13892
1080
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 74
plmn-specificBS-D.......................value reference BearerServiceCode, '11011101'B DEFINED in MAP-BS-Code : 123 plmn-specificBS-E.......................value reference BearerServiceCode, '11011110'B DEFINED in MAP-BS-Code : 124 plmn-specificBS-F.......................value reference BearerServiceCode, '11011111'B DEFINED in MAP-BS-Code : 125 plmn-specificSS-1.......................value reference SS-Code, '11110001'B DEFINED in MAP-SS-Code : 137 plmn-specificSS-2.......................value reference SS-Code, '11110010'B DEFINED in MAP-SS-Code : 138 plmn-specificSS-3.......................value reference SS-Code, '11110011'B DEFINED in MAP-SS-Code : 139 plmn-specificSS-4.......................value reference SS-Code, '11110100'B DEFINED in MAP-SS-Code : 140 plmn-specificSS-5.......................value reference SS-Code, '11110101'B DEFINED in MAP-SS-Code : 141 plmn-specificSS-6.......................value reference SS-Code, '11110110'B DEFINED in MAP-SS-Code : 142 plmn-specificSS-7.......................value reference SS-Code, '11110111'B DEFINED in MAP-SS-Code : 143 plmn-specificSS-8.......................value reference SS-Code, '11111000'B DEFINED in MAP-SS-Code : 144 plmn-specificSS-9.......................value reference SS-Code, '11111001'B DEFINED in MAP-SS-Code : 145 plmn-specificSS-A.......................value reference SS-Code, '11111010'B DEFINED in MAP-SS-Code : 146 plmn-specificSS-B.......................value reference SS-Code, '11111011'B DEFINED in MAP-SS-Code : 147 plmn-specificSS-C.......................value reference SS-Code, '11111100'B DEFINED in MAP-SS-Code : 148 plmn-specificSS-D.......................value reference SS-Code, '11111101'B DEFINED in MAP-SS-Code : 149 plmn-specificSS-E.......................value reference SS-Code, '11111110'B DEFINED in MAP-SS-Code : 150 plmn-specificSS-F.......................value reference SS-Code, '11111111'B DEFINED in MAP-SS-Code : 151 plmn-specificTS-1.......................value reference TeleserviceCode, '11010001'B DEFINED in MAP-TS-Code : 72 plmn-specificTS-2.......................value reference TeleserviceCode, '11010010'B DEFINED in MAP-TS-Code : 73 plmn-specificTS-3.......................value reference TeleserviceCode, '11010011'B DEFINED in MAP-TS-Code : 74 plmn-specificTS-4.......................value reference TeleserviceCode, '11010100'B DEFINED in MAP-TS-Code : 75 plmn-specificTS-5.......................value reference TeleserviceCode, '11010101'B DEFINED in MAP-TS-Code : 76 plmn-specificTS-6.......................value reference TeleserviceCode, '11010110'B DEFINED in MAP-TS-Code : 77 plmn-specificTS-7.......................value reference TeleserviceCode, '11010111'B DEFINED in MAP-TS-Code : 78
2932
3GPP
2933 Release 4
13893 13894 13895 13896 13897 13898 13899
1081
3GPP TS 29.002 V4.17.0 (2006-06)
plmn-specificTS-8.......................value reference TeleserviceCode, '11011000'B DEFINED in MAP-TS-Code : 79 plmn-specificTS-9.......................value reference TeleserviceCode, '11011001'B DEFINED in MAP-TS-Code : 80
2934
3GPP
2935 Release 4
13900 13901 13902 13903 13904 13905 13906 13907 13908 13909 13910 13911 13912 13913 13914 13915 13916 13917 13918 13919 13920 13921 13922 13923 13924 13925 13926 13927 13928 13929 13930 13931 13932 13933 13934 13935 13936 13937 13938 13939 13940 13941 13942 13943 13944 13945 13946 13947 13948 13949 13950 13951 13952 13953 13954 13955 13956 13957 13958 13959 13960 13961 13962 13963 13964 13965 13966 13967 13968 13969 13970 13971 13972 13973 13974 13975 13976
1082
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 75
plmn-specificTS-A.......................value reference TeleserviceCode, '11011010'B DEFINED in MAP-TS-Code : 81 plmn-specificTS-B.......................value reference TeleserviceCode, '11011011'B DEFINED in MAP-TS-Code : 82 plmn-specificTS-C.......................value reference TeleserviceCode, '11011100'B DEFINED in MAP-TS-Code : 83 plmn-specificTS-D.......................value reference TeleserviceCode, '11011101'B DEFINED in MAP-TS-Code : 84 plmn-specificTS-E.......................value reference TeleserviceCode, '11011110'B DEFINED in MAP-TS-Code : 85 plmn-specificTS-F.......................value reference TeleserviceCode, '11011111'B DEFINED in MAP-TS-Code : 86 polygon.................................identifier of Named Number, 3 DEFINED in MAP-LCS-DataTypes : 206 positionMethodFailure...................value reference PositionMethodFailure, CHOICE VALUE DEFINED in MAP-Protocol : 430 PositionMethodFailure...................type reference ERROR DEFINED in MAP-Errors : 439 USED in MAP-Protocol : 165 430 USED in MAP-LocationServiceOpe : 31 82 USED in MAP-Errors : 88 positionMethodFailure-Diagnostic........identifier of [0] PositionMethodFailure-Diagnostic DEFINED in MAP-ER-DataTypes : 360 PositionMethodFailure-Diagnostic........type reference ENUMERATED DEFINED in MAP-ER-DataTypes : 364 USED in MAP-ER-DataTypes : 360 positionMethodFailure-Param.............identifier of PositionMethodFailure-Param DEFINED in MAP-Errors : 441 PositionMethodFailure-Param.............type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 359 USED in MAP-Errors : 143 441 USED in MAP-ER-DataTypes : 51 positionMethodNotAvailableInLocationAreaidentifier of Named Number, 8 DEFINED in MAP-ER-DataTypes : 373 positionMethodNotAvailableInNetwork.....identifier of Named Number, 7 DEFINED in MAP-ER-DataTypes : 372 preferentialCUG-Indicator...............identifier of CUG-Index DEFINED in MAP-MS-DataTypes : 1141 premiumRateEntertainementOGCallsBarred..identifier of Named Number, 4 DEFINED in MAP-MS-DataTypes : 978 premiumRateInformationOGCallsBarred.....identifier of Named Number, 3 DEFINED in MAP-MS-DataTypes : 977 prepareGroupCall........................value reference PrepareGroupCall, CHOICE VALUE DEFINED in MAP-Protocol : 296 PrepareGroupCall........................type reference OPERATION DEFINED in MAP-Group-Call-Operati : 46 USED in MAP-Protocol : 99 296 USED in MAP-Group-Call-Operati : 13 prepareGroupCallArg.....................identifier of PrepareGroupCallArg DEFINED in MAP-Group-Call-Operati : 48 PrepareGroupCallArg.....................type reference SEQUENCE DEFINED in MAP-GR-DataTypes : 49 USED in MAP-Group-Call-Operati : 31 48 USED in MAP-GR-DataTypes : 14
2936
3GPP
2937 Release 4
13977 13978 13979 13980 13981 13982 13983
1083
3GPP TS 29.002 V4.17.0 (2006-06)
prepareGroupCallRes.....................identifier of PrepareGroupCallRes DEFINED in MAP-Group-Call-Operati : 50 PrepareGroupCallRes.....................type reference SEQUENCE DEFINED in MAP-GR-DataTypes : 61 USED in MAP-Group-Call-Operati : 32 50
2938
3GPP
2939 Release 4
13984 13985 13986 13987 13988 13989 13990 13991 13992 13993 13994 13995 13996 13997 13998 13999 14000 14001 14002 14003 14004 14005 14006 14007 14008 14009 14010 14011 14012 14013 14014 14015 14016 14017 14018 14019 14020 14021 14022 14023 14024 14025 14026 14027 14028 14029 14030 14031 14032 14033 14034 14035 14036 14037 14038 14039 14040 14041 14042 14043 14044 14045 14046 14047 14048 14049 14050 14051 14052 14053 14054 14055 14056 14057 14058 14059 14060
1084
Cross Reference Listing for MAP-Protocol : 15
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 76
USED in MAP-GR-DataTypes
prepareHandover.........................value reference PrepareHandover, CHOICE VALUE DEFINED in MAP-Protocol : 191 PrepareHandover.........................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 310 USED in MAP-Protocol : 17 191 USED in MAP-MobileServiceOpera : 38 prepareHO-Arg...........................identifier of PrepareHO-Arg DEFINED in MAP-MobileServiceOpera : 312 PrepareHO-Arg...........................type reference [3] SEQUENCE DEFINED in MAP-MS-DataTypes : 500 USED in MAP-MobileServiceOpera : 123 312 USED in MAP-MS-DataTypes : 34 prepareHO-Res...........................identifier of PrepareHO-Res DEFINED in MAP-MobileServiceOpera : 314 PrepareHO-Res...........................type reference [3] SEQUENCE DEFINED in MAP-MS-DataTypes : 555 USED in MAP-MobileServiceOpera : 124 314 USED in MAP-MS-DataTypes : 35 prepareSubsequentHandover...............value reference PrepareSubsequentHandover, CHOICE VALUE DEFINED in MAP-Protocol : 195 PrepareSubsequentHandover...............type reference OPERATION DEFINED in MAP-MobileServiceOpera : 337 USED in MAP-Protocol : 21 195 USED in MAP-MobileServiceOpera : 42 prepareSubsequentHO-Arg.................identifier of PrepareSubsequentHO-Arg DEFINED in MAP-MobileServiceOpera : 339 PrepareSubsequentHO-Arg.................type reference [3] SEQUENCE DEFINED in MAP-MS-DataTypes : 601 USED in MAP-MobileServiceOpera : 130 339 USED in MAP-MS-DataTypes : 36 prepareSubsequentHO-Res.................identifier of PrepareSubsequentHO-Res DEFINED in MAP-MobileServiceOpera : 341 PrepareSubsequentHO-Res.................type reference [3] SEQUENCE DEFINED in MAP-MS-DataTypes : 610 USED in MAP-MobileServiceOpera : 129 341 USED in MAP-MS-DataTypes : 37 pre-pagingSupported.....................identifier of [19] NULL DEFINED in MAP-CH-DataTypes : 115 pre-pagingSupported.....................identifier of [17] NULL DEFINED in MAP-CH-DataTypes : 216 priority................................identifier of [2] EMLPP-Priority DEFINED in MAP-GR-DataTypes : 56 priorityLevel0..........................value reference EMLPP-Priority, 0 DEFINED in MAP-CommonDataTypes : 451 priorityLevel1..........................value reference EMLPP-Priority, 1 DEFINED in MAP-CommonDataTypes : 452 priorityLevel2..........................value reference EMLPP-Priority, 2 DEFINED in MAP-CommonDataTypes : 453 priorityLevel3..........................value reference EMLPP-Priority, 3 DEFINED in MAP-CommonDataTypes : 454 priorityLevel4..........................value reference EMLPP-Priority, 4 DEFINED in MAP-CommonDataTypes : 455 priorityLevelA..........................value reference EMLPP-Priority, 6
2940
3GPP
2941 Release 4
14061 14062 14063 14064 14065 14066 14067
1085
: 449
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-CommonDataTypes
priorityLevelB..........................value reference EMLPP-Priority, 5 DEFINED in MAP-CommonDataTypes : 450 privacyOverride.........................identifier of [1] NULL DEFINED in MAP-LCS-DataTypes : 92
2942
3GPP
2943 Release 4
14068 14069 14070 14071 14072 14073 14074 14075 14076 14077 14078 14079 14080 14081 14082 14083 14084 14085 14086 14087 14088 14089 14090 14091 14092 14093 14094 14095 14096 14097 14098 14099 14100 14101 14102 14103 14104 14105 14106 14107 14108 14109 14110 14111 14112 14113 14114 14115 14116 14117 14118 14119 14120 14121 14122 14123 14124 14125 14126 14127 14128 14129 14130 14131 14132 14133 14134 14135 14136 14137 14138 14139 14140 14141 14142 14143 14144
1086
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 77
privacyOverrideNotApplicable............identifier of Named Number, 3 DEFINED in MAP-ER-DataTypes : 353 privacyViolation........................identifier of Named Number, 5 DEFINED in MAP-LCS-DataTypes : 372 PrivateExtension........................type reference SEQUENCE DEFINED in MAP-ExtensionDataTypes : 46 USED in MAP-ExtensionDataTypes : 15 44 privateExtensionList....................identifier of [0] PrivateExtensionList DEFINED in MAP-ExtensionDataTypes : 34 privateExtensionList....................identifier of [0] PrivateExtensionList DEFINED in MAP-ExtensionDataTypes : 39 PrivateExtensionList....................type reference SEQUENCE OF DEFINED in MAP-ExtensionDataTypes : 43 USED in MAP-ExtensionDataTypes : 34 39 problem.................................identifier of CHOICE DEFINED in TCAPMessages : 169 processAccessSignalling.................value reference ProcessAccessSignalling, CHOICE VALUE DEFINED in MAP-Protocol : 193 ProcessAccessSignalling.................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 329 USED in MAP-Protocol : 19 193 USED in MAP-MobileServiceOpera : 40 processAccessSignalling-Arg.............identifier of ProcessAccessSignalling-Arg DEFINED in MAP-MobileServiceOpera : 331 ProcessAccessSignalling-Arg.............type reference [3] SEQUENCE DEFINED in MAP-MS-DataTypes : 615 USED in MAP-MobileServiceOpera : 126 331 USED in MAP-MS-DataTypes : 38 processGroupCallSignalling..............value reference ProcessGroupCallSignalling, CHOICE VALUE DEFINED in MAP-Protocol : 298 ProcessGroupCallSignalling..............type reference OPERATION DEFINED in MAP-Group-Call-Operati : 63 USED in MAP-Protocol : 100 298 USED in MAP-Group-Call-Operati : 16 processGroupCallSignallingArg...........identifier of ProcessGroupCallSignallingArg DEFINED in MAP-Group-Call-Operati : 65 ProcessGroupCallSignallingArg...........type reference SEQUENCE DEFINED in MAP-GR-DataTypes : 86 USED in MAP-Group-Call-Operati : 36 65 USED in MAP-GR-DataTypes : 19 processUnstructuredSS-Request.......value reference ProcessUnstructuredSS-Request, CHOICE VALUE DEFINED in MAP-Protocol : 252 ProcessUnstructuredSS-Request...........type reference OPERATION DEFINED in MAP-SupplementaryServi : 175 USED in MAP-Protocol : 74 252 USED in MAP-SupplementaryServi : 18 protocolId..............................identifier of ProtocolId DEFINED in MAP-CommonDataTypes : 199 ProtocolId..............................type reference ENUMERATED DEFINED in MAP-CommonDataTypes : 217 USED in MAP-CommonDataTypes : 199 provideRoamingNumber....................value reference ProvideRoamingNumber, CHOICE VALUE DEFINED in MAP-Protocol : 234 ProvideRoamingNumber....................type reference OPERATION
2944
3GPP
2945 Release 4
14145 14146 14147 14148 14149 14150 14151
1087
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-CallHandlingOperat : 103 USED in MAP-Protocol : 55 234 USED in MAP-CallHandlingOperat : 14 provideRoamingNumberArg.................identifier of ProvideRoamingNumberArg DEFINED in MAP-CallHandlingOperat : 106
2946
3GPP
2947 Release 4
14152 14153 14154 14155 14156 14157 14158 14159 14160 14161 14162 14163 14164 14165 14166 14167 14168 14169 14170 14171 14172 14173 14174 14175 14176 14177 14178 14179 14180 14181 14182 14183 14184 14185 14186 14187 14188 14189 14190 14191 14192 14193 14194 14195 14196 14197 14198 14199 14200 14201 14202 14203 14204 14205 14206 14207 14208 14209 14210 14211 14212 14213 14214 14215 14216 14217 14218 14219 14220 14221 14222 14223 14224 14225 14226 14227 14228
1088
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 78
ProvideRoamingNumberArg.................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 198 USED in MAP-CallHandlingOperat : 56 106 USED in MAP-CH-DataTypes : 16 provideRoamingNumberRes.................identifier of ProvideRoamingNumberRes DEFINED in MAP-CallHandlingOperat : 108 ProvideRoamingNumberRes.................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 219 USED in MAP-CallHandlingOperat : 57 108 USED in MAP-CH-DataTypes : 17 provideSIWFSNumber......................value reference ProvideSIWFSNumber, CHOICE VALUE DEFINED in MAP-Protocol : 236 ProvideSIWFSNumber......................type reference OPERATION DEFINED in MAP-CallHandlingOperat : 130 USED in MAP-Protocol : 57 236 USED in MAP-CallHandlingOperat : 16 provideSIWFSNumberArg...................identifier of ProvideSIWFSNumberArg DEFINED in MAP-CallHandlingOperat : 132 ProvideSIWFSNumberArg...................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 281 USED in MAP-CallHandlingOperat : 60 132 USED in MAP-CH-DataTypes : 23 provideSIWFSNumberRes...................identifier of ProvideSIWFSNumberRes DEFINED in MAP-CallHandlingOperat : 134 ProvideSIWFSNumberRes...................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 299 USED in MAP-CallHandlingOperat : 61 134 USED in MAP-CH-DataTypes : 24 provideSubscriberInfo...................value reference ProvideSubscriberInfo, CHOICE VALUE DEFINED in MAP-Protocol : 274 ProvideSubscriberInfo...................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 233 USED in MAP-Protocol : 30 274 USED in MAP-MobileServiceOpera : 24 provideSubscriberInfoArg................identifier of ProvideSubscriberInfoArg DEFINED in MAP-MobileServiceOpera : 235 ProvideSubscriberInfoArg................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1742 USED in MAP-MobileServiceOpera : 143 235 USED in MAP-MS-DataTypes : 98 provideSubscriberInfoRes................identifier of ProvideSubscriberInfoRes DEFINED in MAP-MobileServiceOpera : 237 ProvideSubscriberInfoRes................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1749 USED in MAP-MobileServiceOpera : 144 237 USED in MAP-MS-DataTypes : 99 provideSubscriberLocation...............value reference ProvideSubscriberLocation, CHOICE VALUE DEFINED in MAP-Protocol : 320 ProvideSubscriberLocation...............type reference OPERATION DEFINED in MAP-LocationServiceOpe : 66 USED in MAP-Protocol : 108 320 USED in MAP-LocationServiceOpe : 13 provideSubscriberLocation-Arg...........identifier of ProvideSubscriberLocation-Arg DEFINED in MAP-LocationServiceOpe : 68 ProvideSubscriberLocation-Arg...........type reference SEQUENCE DEFINED in MAP-LCS-DataTypes : 88 USED in MAP-LocationServiceOpe : 43 68
2948
3GPP
2949 Release 4
14229 14230 14231 14232 14233 14234 14235
1089
: 13
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-LCS-DataTypes
provideSubscriberLocation-Res...........identifier of ProvideSubscriberLocation-Res DEFINED in MAP-LocationServiceOpe : 70 ProvideSubscriberLocation-Res...........type reference SEQUENCE DEFINED in MAP-LCS-DataTypes : 215
2950
3GPP
2951 Release 4
14236 14237 14238 14239 14240 14241 14242 14243 14244 14245 14246 14247 14248 14249 14250 14251 14252 14253 14254 14255 14256 14257 14258 14259 14260 14261 14262 14263 14264 14265 14266 14267 14268 14269 14270 14271 14272 14273 14274 14275 14276 14277 14278 14279 14280 14281 14282 14283 14284 14285 14286 14287 14288 14289 14290 14291 14292 14293 14294 14295 14296 14297 14298 14299 14300 14301 14302 14303 14304 14305 14306 14307 14308 14309 14310 14311 14312
1090
Cross Reference Listing for MAP-Protocol 70
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 79
USED in MAP-LocationServiceOpe : 44 USED in MAP-LCS-DataTypes : 14
provisionedSS...........................identifier of [7] Ext-SS-InfoList DEFINED in MAP-MS-DataTypes : 938 purgedMS................................identifier of Named Number, 3 DEFINED in MAP-ER-DataTypes : 256 purgeMS.................................value reference PurgeMS, CHOICE VALUE DEFINED in MAP-Protocol : 185 PurgeMS.................................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 198 USED in MAP-Protocol : 14 185 USED in MAP-MobileServiceOpera : 17 purgeMS-Arg.............................identifier of PurgeMS-Arg DEFINED in MAP-MobileServiceOpera : 200 PurgeMS-Arg.............................type reference [3] SEQUENCE DEFINED in MAP-MS-DataTypes : 282 USED in MAP-MobileServiceOpera : 117 200 USED in MAP-MS-DataTypes : 20 purgeMS-Res.............................identifier of PurgeMS-Res DEFINED in MAP-MobileServiceOpera : 202 PurgeMS-Res.............................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 289 USED in MAP-MobileServiceOpera : 118 202 USED in MAP-MS-DataTypes : 21 pvlr....................................identifier of Named Number, 3 DEFINED in MAP-CommonDataTypes : 355 pw-RegistrationFailure..................value reference PW-RegistrationFailure, CHOICE VALUE DEFINED in MAP-Protocol : 411 PW-RegistrationFailure..................type reference ERROR DEFINED in MAP-Errors : 380 USED in MAP-Protocol : 151 411 USED in MAP-SupplementaryServi : 45 228 USED in MAP-Errors : 70 pw-RegistrationFailureCause.............identifier of PW-RegistrationFailureCause DEFINED in MAP-Errors : 382 PW-RegistrationFailureCause.............type reference ENUMERATED DEFINED in MAP-ER-DataTypes : 136 USED in MAP-Errors : 108 382 USED in MAP-ER-DataTypes : 18 p-abortCause............................identifier of P-AbortCause DEFINED in TCAPMessages : 76 P-AbortCause............................type reference [APPLICATION 10] IMPLICIT INTEGER DEFINED in TCAPMessages : 102 USED in TCAPMessages : 76 qoSNotAttainable........................identifier of Named Number, 6 DEFINED in MAP-ER-DataTypes : 371 qos-Subscribed..........................identifier of [18] QoS-Subscribed DEFINED in MAP-MS-DataTypes : 794 QoS-Subscribed..........................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 882 USED in MAP-MS-DataTypes : 82 794 quintupletList..........................identifier of [1] QuintupletList DEFINED in MAP-MS-DataTypes : 320 QuintupletList..........................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 325
2952
3GPP
2953 Release 4
14313 14314 14315 14316 14317 14318 14319
1091
: 320
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-MS-DataTypes
rab-Id..................................identifier of [12] RAB-Id DEFINED in MAP-MS-DataTypes : 515 rab-Id..................................identifier of RAB-Id DEFINED in MAP-MS-DataTypes : 527
2954
3GPP
2955 Release 4
14320 14321 14322 14323 14324 14325 14326 14327 14328 14329 14330 14331 14332 14333 14334 14335 14336 14337 14338 14339 14340 14341 14342 14343 14344 14345 14346 14347 14348 14349 14350 14351 14352 14353 14354 14355 14356 14357 14358 14359 14360 14361 14362 14363 14364 14365 14366 14367 14368 14369 14370 14371 14372 14373 14374 14375 14376 14377 14378 14379 14380 14381 14382 14383 14384 14385 14386 14387 14388 14389 14390 14391 14392 14393 14394 14395 14396
1092
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 80
rab-Id..................................identifier of RAB-Id DEFINED in MAP-MS-DataTypes : 549 rab-Id..................................identifier of RAB-Id DEFINED in MAP-MS-DataTypes : 658 RAB-Id..................................type reference INTEGER DEFINED in MAP-MS-DataTypes : 662 USED in MAP-MS-DataTypes : 515 527 549 606 620 658 RadioResource...........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 547 USED in MAP-MS-DataTypes : 545 radioResourceInformation................identifier of [6] RadioResourceInformation DEFINED in MAP-MS-DataTypes : 451 radioResourceInformation................identifier of [7] RadioResourceInformation DEFINED in MAP-MS-DataTypes : 509 radioResourceInformation................identifier of RadioResourceInformation DEFINED in MAP-MS-DataTypes : 548 RadioResourceInformation................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 668 USED in MAP-MS-DataTypes : 451 509 548 radioResourceList.......................identifier of [7] RadioResourceList DEFINED in MAP-MS-DataTypes : 454 radioResourceList.......................identifier of [11] RadioResourceList DEFINED in MAP-MS-DataTypes : 512 RadioResourceList.......................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 544 USED in MAP-MS-DataTypes : 454 512 ranap-ServiceHandover...................identifier of [8] RANAP-ServiceHandover DEFINED in MAP-MS-DataTypes : 456 ranap-ServiceHandover...................identifier of [14] RANAP-ServiceHandover DEFINED in MAP-MS-DataTypes : 517 RANAP-ServiceHandover...................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 537 USED in MAP-MS-DataTypes : 456 517 rand....................................identifier of RAND DEFINED in MAP-MS-DataTypes : 329 rand....................................identifier of RAND DEFINED in MAP-MS-DataTypes : 335 RAND....................................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 357 USED in MAP-MS-DataTypes : 329 335 386 707 rand....................................identifier of RAND DEFINED in MAP-MS-DataTypes : 386 rand....................................identifier of RAND DEFINED in MAP-MS-DataTypes : 707 readyForSM..............................value reference ReadyForSM, CHOICE VALUE DEFINED in MAP-Protocol : 270 ReadyForSM..............................type reference OPERATION DEFINED in MAP-ShortMessageServic : 136 USED in MAP-Protocol : 93 270 USED in MAP-ShortMessageServic : 19 readyForSM-Arg..........................identifier of ReadyForSM-Arg DEFINED in MAP-ShortMessageServic : 138
2956
3GPP
2957 Release 4
14397 14398 14399 14400 14401 14402 14403
1093
3GPP TS 29.002 V4.17.0 (2006-06)
ReadyForSM-Arg..........................type reference SEQUENCE DEFINED in MAP-SM-DataTypes : 203 USED in MAP-ShortMessageServic : 55 138 USED in MAP-SM-DataTypes : 24 readyForSM-Res..........................identifier of ReadyForSM-Res DEFINED in MAP-ShortMessageServic : 140
2958
3GPP
2959 Release 4
14404 14405 14406 14407 14408 14409 14410 14411 14412 14413 14414 14415 14416 14417 14418 14419 14420 14421 14422 14423 14424 14425 14426 14427 14428 14429 14430 14431 14432 14433 14434 14435 14436 14437 14438 14439 14440 14441 14442 14443 14444 14445 14446 14447 14448 14449 14450 14451 14452 14453 14454 14455 14456 14457 14458 14459 14460 14461 14462 14463 14464 14465 14466 14467 14468 14469 14470 14471 14472 14473 14474 14475 14476 14477 14478 14479 14480
1094
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 81
ReadyForSM-Res..........................type reference SEQUENCE DEFINED in MAP-SM-DataTypes : 212 USED in MAP-ShortMessageServic : 56 140 USED in MAP-SM-DataTypes : 25 reason..................................identifier of CHOICE DEFINED in TCAPMessages : 75 recall..................................identifier of Named Number, 1 DEFINED in MAP-SS-DataTypes : 287 regionalSubscNotSupported...............identifier of Named Number, 3 DEFINED in MAP-MS-DataTypes : 1269 regionalSubscriptionData................identifier of [10] ZoneCodeList DEFINED in MAP-MS-DataTypes : 941 regionalSubscriptionIdentifier..........identifier of [5] ZoneCode DEFINED in MAP-MS-DataTypes : 1278 regionalSubscriptionResponse............identifier of [5] RegionalSubscriptionResponse DEFINED in MAP-MS-DataTypes : 1260 RegionalSubscriptionResponse............type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 1265 USED in MAP-MS-DataTypes : 1260 1326 regionalSubscriptionResponse............identifier of [0] RegionalSubscriptionResponse DEFINED in MAP-MS-DataTypes : 1326 registerCC-Entry........................value reference RegisterCC-Entry, CHOICE VALUE DEFINED in MAP-Protocol : 258 RegisterCC-Entry........................type reference OPERATION DEFINED in MAP-SupplementaryServi : 251 USED in MAP-Protocol : 80 258 USED in MAP-SupplementaryServi : 24 registerCC-EntryArg.....................identifier of RegisterCC-EntryArg DEFINED in MAP-SupplementaryServi : 253 RegisterCC-EntryArg.....................type reference SEQUENCE DEFINED in MAP-SS-DataTypes : 305 USED in MAP-SupplementaryServi : 70 253 USED in MAP-SS-DataTypes : 37 registerCC-EntryRes.....................identifier of RegisterCC-EntryRes DEFINED in MAP-SupplementaryServi : 255 RegisterCC-EntryRes.....................type reference SEQUENCE DEFINED in MAP-SS-DataTypes : 324 USED in MAP-SupplementaryServi : 71 255 USED in MAP-SS-DataTypes : 38 registerPassword........................value reference RegisterPassword, CHOICE VALUE DEFINED in MAP-Protocol : 256 RegisterPassword........................type reference OPERATION DEFINED in MAP-SupplementaryServi : 217 USED in MAP-Protocol : 77 256 USED in MAP-SupplementaryServi : 21 registerSS..............................value reference RegisterSS, CHOICE VALUE DEFINED in MAP-Protocol : 247 RegisterSS..............................type reference OPERATION DEFINED in MAP-SupplementaryServi : 87 USED in MAP-Protocol : 69 247 USED in MAP-SupplementaryServi : 13 registerSS-Arg..........................identifier of RegisterSS-Arg DEFINED in MAP-SupplementaryServi : 89 RegisterSS-Arg..........................type reference SEQUENCE
2960
3GPP
2961 Release 4
14481 14482 14483 14484 14485 14486 14487
1095
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-SS-DataTypes : 72 USED in MAP-SupplementaryServi : 60 USED in MAP-SS-DataTypes : 14
89
registrationAllCF-Barred................identifier of Named Number, 24 DEFINED in MAP-MS-DataTypes : 995
2962
3GPP
2963 Release 4
14488 14489 14490 14491 14492 14493 14494 14495 14496 14497 14498 14499 14500 14501 14502 14503 14504 14505 14506 14507 14508 14509 14510 14511 14512 14513 14514 14515 14516 14517 14518 14519 14520 14521 14522 14523 14524 14525 14526 14527 14528 14529 14530 14531 14532 14533 14534 14535 14536 14537 14538 14539 14540 14541 14542 14543 14544 14545 14546 14547 14548 14549 14550 14551 14552 14553 14554 14555 14556 14557 14558 14559 14560 14561 14562 14563 14564
1096
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 82
registrationCFNotToHPLMN-Barred.........identifier of Named Number, 25 DEFINED in MAP-MS-DataTypes : 996 registrationInternationalCF-Barred......identifier of Named Number, 28 DEFINED in MAP-MS-DataTypes : 999 registrationInterzonalCFNotToHPLMN-Barreidentifier of Named Number, 27 DEFINED in MAP-MS-DataTypes : 998 registrationInterzonalCF-Barred.........identifier of Named Number, 26 DEFINED in MAP-MS-DataTypes : 997 reject..................................identifier of [4] IMPLICIT Reject DEFINED in TCAPMessages : 128 Reject..................................type reference SEQUENCE DEFINED in TCAPMessages : 165 USED in TCAPMessages : 128 rejected................................identifier of Named Number, 1 DEFINED in MAP-CH-DataTypes : 402 releaseCall.............................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 1516 releaseGroupCall........................identifier of [2] NULL DEFINED in MAP-GR-DataTypes : 89 releaseTransaction......................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 850 releaseTransaction......................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 1573 RelocationNumber........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 656 USED in MAP-MS-DataTypes : 652 relocationNumberList....................identifier of [1] RelocationNumberList DEFINED in MAP-MS-DataTypes : 557 RelocationNumberList....................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 651 USED in MAP-MS-DataTypes : 557 remoteUserFree..........................value reference RemoteUserFree, CHOICE VALUE DEFINED in MAP-Protocol : 240 RemoteUserFree..........................type reference OPERATION DEFINED in MAP-CallHandlingOperat : 179 USED in MAP-Protocol : 61 240 USED in MAP-CallHandlingOperat : 20 remoteUserFreeArg.......................identifier of RemoteUserFreeArg DEFINED in MAP-CallHandlingOperat : 181 RemoteUserFreeArg.......................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 385 USED in MAP-CallHandlingOperat : 68 181 USED in MAP-CH-DataTypes : 31 remoteUserFreeRes.......................identifier of RemoteUserFreeRes DEFINED in MAP-CallHandlingOperat : 183 RemoteUserFreeRes.......................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 395 USED in MAP-CallHandlingOperat : 69 183 USED in MAP-CH-DataTypes : 32 replaceB-Number.........................identifier of [4] NULL DEFINED in MAP-CH-DataTypes : 390 ReportingState..........................type reference ENUMERATED DEFINED in MAP-CH-DataTypes : 322 USED in MAP-CH-DataTypes : 318
2964
3GPP
2965 Release 4
14565 14566 14567 14568 14569 14570 14571
1097
3GPP TS 29.002 V4.17.0 (2006-06)
reportSM-DeliveryStatus.................value reference ReportSM-DeliveryStatus, CHOICE VALUE DEFINED in MAP-Protocol : 267 ReportSM-DeliveryStatus.................type reference OPERATION DEFINED in MAP-ShortMessageServic : 111 USED in MAP-Protocol : 90 267
2966
3GPP
2967 Release 4
14572 14573 14574 14575 14576 14577 14578 14579 14580 14581 14582 14583 14584 14585 14586 14587 14588 14589 14590 14591 14592 14593 14594 14595 14596 14597 14598 14599 14600 14601 14602 14603 14604 14605 14606 14607 14608 14609 14610 14611 14612 14613 14614 14615 14616 14617 14618 14619 14620 14621 14622 14623 14624 14625 14626 14627 14628 14629 14630 14631 14632 14633 14634 14635 14636 14637 14638 14639 14640 14641 14642 14643 14644 14645 14646 14647 14648
1098
Cross Reference Listing for MAP-Protocol 16
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 83
USED in MAP-ShortMessageServic :
reportSM-DeliveryStatusArg..............identifier of ReportSM-DeliveryStatusArg DEFINED in MAP-ShortMessageServic : 113 ReportSM-DeliveryStatusArg..............type reference SEQUENCE DEFINED in MAP-SM-DataTypes : 144 USED in MAP-ShortMessageServic : 51 113 USED in MAP-SM-DataTypes : 20 reportSM-DeliveryStatusRes..............identifier of ReportSM-DeliveryStatusRes DEFINED in MAP-ShortMessageServic : 115 ReportSM-DeliveryStatusRes..............type reference SEQUENCE DEFINED in MAP-SM-DataTypes : 172 USED in MAP-ShortMessageServic : 52 115 USED in MAP-SM-DataTypes : 21 request.................................identifier of Named Number, 0 DEFINED in MAP-SS-DataTypes : 286 requestedBasicServiceViolatesCUG-Constraidentifier of Named Number, 5 DEFINED in MAP-ER-DataTypes : 127 requestedCAMEL-SubscriptionInfo.........identifier of [3] RequestedCAMEL-SubscriptionInfo DEFINED in MAP-MS-DataTypes : 1862 RequestedCAMEL-SubscriptionInfo.........type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 1868 USED in MAP-MS-DataTypes : 1862 1957 requestedCamel-SubscriptionInfo.........identifier of [0] RequestedCAMEL-SubscriptionInfo DEFINED in MAP-MS-DataTypes : 1957 requestedInfo...........................identifier of [2] RequestedInfo DEFINED in MAP-MS-DataTypes : 1745 RequestedInfo...........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1760 USED in MAP-MS-DataTypes : 1745 1828 requestedInfo...........................identifier of [1] RequestedInfo DEFINED in MAP-MS-DataTypes : 1828 requestedSS-Info........................identifier of [1] SS-ForBS-Code DEFINED in MAP-MS-DataTypes : 1860 requestedSubscriptionInfo...............identifier of [1] RequestedSubscriptionInfo DEFINED in MAP-MS-DataTypes : 1843 RequestedSubscriptionInfo...............type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1859 USED in MAP-MS-DataTypes : 1843 requestingNodeType......................identifier of [3] RequestingNodeType DEFINED in MAP-MS-DataTypes : 702 RequestingNodeType......................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 716 USED in MAP-MS-DataTypes : 702 reset...................................value reference Reset, CHOICE VALUE DEFINED in MAP-Protocol : 218 Reset...................................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 416 USED in MAP-Protocol : 27 218 USED in MAP-MobileServiceOpera : 56 resetArg................................identifier of ResetArg DEFINED in MAP-MobileServiceOpera : 418 ResetArg................................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1693 USED in MAP-MobileServiceOpera : 140 418
2968
3GPP
2969 Release 4
14649 14650 14651 14652 14653 14654 14655
1099
: 89
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-MS-DataTypes
resourceLimitation......................value reference ResourceLimitation, CHOICE VALUE DEFINED in MAP-Protocol : 336 ResourceLimitation......................type reference ERROR DEFINED in MAP-Errors : 193
2970
3GPP
2971 Release 4
14656 14657 14658 14659 14660 14661 14662 14663 14664 14665 14666 14667 14668 14669 14670 14671 14672 14673 14674 14675 14676 14677 14678 14679 14680 14681 14682 14683 14684 14685 14686 14687 14688 14689 14690 14691 14692 14693 14694 14695 14696 14697 14698 14699 14700 14701 14702 14703 14704 14705 14706 14707 14708 14709 14710 14711 14712 14713 14714 14715 14716 14717 14718 14719 14720 14721 14722 14723 14724 14725 14726 14727 14728 14729 14730 14731 14732
1100
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 84
USED in MAP-Protocol : 158 336 USED in MAP-CallHandlingOperat : 47 136 148 164 200 213 USED in MAP-LocationServiceOpe : 32 92 USED in MAP-Errors : 19 resourceLimitation......................identifier of Named Number, 4 DEFINED in TCAPMessages : 107 resourceLimitation......................identifier of Named Number, 3 DEFINED in TCAPMessages : 186 resourceLimitationParam.................identifier of ResourceLimitationParam DEFINED in MAP-Errors : 195 ResourceLimitationParam.................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 322 USED in MAP-Errors : 136 195 USED in MAP-ER-DataTypes : 44 responseTime............................identifier of [3] ResponseTime DEFINED in MAP-LCS-DataTypes : 174 ResponseTime............................type reference SEQUENCE DEFINED in MAP-LCS-DataTypes : 190 USED in MAP-LCS-DataTypes : 21 174 responseTimeCategory....................identifier of ResponseTimeCategory DEFINED in MAP-LCS-DataTypes : 191 ResponseTimeCategory....................type reference ENUMERATED DEFINED in MAP-LCS-DataTypes : 195 USED in MAP-LCS-DataTypes : 191 restoreData.............................value reference RestoreData, CHOICE VALUE DEFINED in MAP-Protocol : 221 RestoreData.............................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 422 USED in MAP-Protocol : 29 221 USED in MAP-MobileServiceOpera : 58 restoreDataArg..........................identifier of RestoreDataArg DEFINED in MAP-MobileServiceOpera : 424 RestoreDataArg..........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1698 USED in MAP-MobileServiceOpera : 141 424 USED in MAP-MS-DataTypes : 90 restoreDataRes..........................identifier of RestoreDataRes DEFINED in MAP-MobileServiceOpera : 426 RestoreDataRes..........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1705 USED in MAP-MobileServiceOpera : 142 426 USED in MAP-MS-DataTypes : 91 restrictedArea..........................identifier of Named Number, 2 DEFINED in MAP-MS-DataTypes : 1821 restrictedArea..........................identifier of Named Number, 1 DEFINED in MAP-ER-DataTypes : 253 result-RR...............................identifier of SEQUENCE DEFINED in TCAPMessages : 146 resumeCallHandling......................value reference ResumeCallHandling, CHOICE VALUE DEFINED in MAP-Protocol : 235 ResumeCallHandling......................type reference OPERATION DEFINED in MAP-CallHandlingOperat : 118 USED in MAP-Protocol : 56 235 USED in MAP-CallHandlingOperat : 15 resumeCallHandlingArg...................identifier of ResumeCallHandlingArg
2972
3GPP
2973 Release 4
14733 14734 14735 14736 14737 14738 14739
1101
120
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-CallHandlingOperat :
ResumeCallHandlingArg...................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 224 USED in MAP-CallHandlingOperat : 58 120 USED in MAP-CH-DataTypes : 18
2974
3GPP
2975 Release 4
14740 14741 14742 14743 14744 14745 14746 14747 14748 14749 14750 14751 14752 14753 14754 14755 14756 14757 14758 14759 14760 14761 14762 14763 14764 14765 14766 14767 14768 14769 14770 14771 14772 14773 14774 14775 14776 14777 14778 14779 14780 14781 14782 14783 14784 14785 14786 14787 14788 14789 14790 14791 14792 14793 14794 14795 14796 14797 14798 14799 14800 14801 14802 14803 14804 14805 14806 14807 14808 14809 14810 14811 14812 14813 14814 14815 14816
1102
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 85
resumeCallHandlingRes...................identifier of ResumeCallHandlingRes DEFINED in MAP-CallHandlingOperat : 122 ResumeCallHandlingRes...................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 252 USED in MAP-CallHandlingOperat : 59 122 USED in MAP-CH-DataTypes : 19 returnError.............................identifier of [3] IMPLICIT ReturnError DEFINED in TCAPMessages : 127 ReturnError.............................type reference SEQUENCE DEFINED in TCAPMessages : 156 USED in TCAPMessages : 127 returnErrorProblem......................identifier of [3] IMPLICIT ReturnErrorProblem DEFINED in TCAPMessages : 173 ReturnErrorProblem......................type reference INTEGER DEFINED in TCAPMessages : 196 USED in TCAPMessages : 173 returnErrorUnexpected...................identifier of Named Number, 1 DEFINED in TCAPMessages : 197 ReturnResult............................type reference SEQUENCE DEFINED in TCAPMessages : 144 USED in TCAPMessages : 126 129 returnResultLast........................identifier of [2] IMPLICIT ReturnResult DEFINED in TCAPMessages : 126 returnResultNotLast.....................identifier of [7] IMPLICIT ReturnResult DEFINED in TCAPMessages : 129 returnResultProblem.....................identifier of [2] IMPLICIT ReturnResultProblem DEFINED in TCAPMessages : 172 ReturnResultProblem.....................type reference INTEGER DEFINED in TCAPMessages : 192 USED in TCAPMessages : 172 returnResultUnexpected..................identifier of Named Number, 1 DEFINED in TCAPMessages : 193 re-attempt..............................identifier of BOOLEAN DEFINED in MAP-MS-DataTypes : 384 re-synchronisationInfo..................identifier of Re-synchronisationInfo DEFINED in MAP-MS-DataTypes : 699 Re-synchronisationInfo..................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 706 USED in MAP-MS-DataTypes : 699 RNCId...................................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 638 USED in MAP-MS-DataTypes : 503 604 roamerAccessToHPLMN-AP-Barred...........identifier of Named Number, 16 DEFINED in MAP-MS-DataTypes : 987 roamerAccessToVPLMN-AP-Barred...........identifier of Named Number, 17 DEFINED in MAP-MS-DataTypes : 988 roamingNotAllowed.......................value reference RoamingNotAllowed, CHOICE VALUE DEFINED in MAP-Protocol : 350 RoamingNotAllowed.......................type reference ERROR DEFINED in MAP-Errors : 224 USED in MAP-Protocol : 126 350 USED in MAP-MobileServiceOpera : 89 186 229 USED in MAP-Errors : 29 roamingNotAllowedCause..................identifier of RoamingNotAllowedCause
2976
3GPP
2977 Release 4
14817 14818 14819 14820 14821 14822 14823
1103
: 94
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-ER-DataTypes
RoamingNotAllowedCause..................type reference ENUMERATED DEFINED in MAP-ER-DataTypes : 98 USED in MAP-ER-DataTypes : 94 roamingNotAllowedParam..................identifier of RoamingNotAllowedParam
2978
3GPP
2979 Release 4
14824 14825 14826 14827 14828 14829 14830 14831 14832 14833 14834 14835 14836 14837 14838 14839 14840 14841 14842 14843 14844 14845 14846 14847 14848 14849 14850 14851 14852 14853 14854 14855 14856 14857 14858 14859 14860 14861 14862 14863 14864 14865 14866 14867 14868 14869 14870 14871 14872 14873 14874 14875 14876 14877 14878 14879 14880 14881 14882 14883 14884 14885 14886 14887 14888 14889 14890 14891 14892 14893 14894 14895 14896 14897 14898 14899 14900
1104
Cross Reference Listing for MAP-Protocol : 226
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 86
DEFINED in MAP-Errors
RoamingNotAllowedParam..................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 93 USED in MAP-Errors : 117 226 USED in MAP-ER-DataTypes : 14 roamingNumber...........................identifier of ISDN-AddressString DEFINED in MAP-CH-DataTypes : 184 roamingNumber...........................identifier of ISDN-AddressString DEFINED in MAP-CH-DataTypes : 220 roamingOutsidePLMNICountryIC-CallsBarredidentifier of Named Number, 21 DEFINED in MAP-MS-DataTypes : 992 roamingOutsidePLMNIC-CallsBarred........identifier of Named Number, 20 DEFINED in MAP-MS-DataTypes : 991 roamingOutsidePLMNOG-CallsBarred........identifier of Named Number, 18 DEFINED in MAP-MS-DataTypes : 989 roamingOutsidePLMN-Barred...............identifier of Named Number, 22 DEFINED in MAP-MS-DataTypes : 993 roamingOutsidePLMN-CountryBarred........identifier of Named Number, 23 DEFINED in MAP-MS-DataTypes : 994 roamingRestrictedInSgsnDueToUnsupportedFidentifier of [23] NULL DEFINED in MAP-MS-DataTypes : 742 roamingRestrictedInSgsnDueToUnsuppportedidentifier of [11] NULL DEFINED in MAP-MS-DataTypes : 1285 roamingRestrictionDueToUnsupportedFeaturidentifier of [9] NULL DEFINED in MAP-MS-DataTypes : 940 roamingRestrictionDueToUnsupportedFeaturidentifier of [4] NULL DEFINED in MAP-MS-DataTypes : 1277 routeSelectFailure......................identifier of Named Number, 4 DEFINED in MAP-MS-DataTypes : 1434 routingAreaUpdating.....................identifier of Named Number, 6 DEFINED in MAP-MS-DataTypes : 397 RoutingInfo.............................type reference CHOICE DEFINED in MAP-CH-DataTypes : 183 USED in MAP-CH-DataTypes : 263 routingInfo.............................identifier of RoutingInfo DEFINED in MAP-CH-DataTypes : 263 routingInfoForLCS-Arg...................identifier of RoutingInfoForLCS-Arg DEFINED in MAP-LocationServiceOpe : 54 RoutingInfoForLCS-Arg...................type reference SEQUENCE DEFINED in MAP-LCS-DataTypes : 65 USED in MAP-LocationServiceOpe : 41 54 USED in MAP-LCS-DataTypes : 11 routingInfoForLCS-Res...................identifier of RoutingInfoForLCS-Res DEFINED in MAP-LocationServiceOpe : 56 RoutingInfoForLCS-Res...................type reference SEQUENCE DEFINED in MAP-LCS-DataTypes : 71 USED in MAP-LocationServiceOpe : 42 56 USED in MAP-LCS-DataTypes : 12 routingInfoForSM-Arg....................identifier of RoutingInfoForSM-Arg DEFINED in MAP-ShortMessageServic : 68 RoutingInfoForSM-Arg....................type reference SEQUENCE DEFINED in MAP-SM-DataTypes : 53 USED in MAP-ShortMessageServic : 45 68
2980
3GPP
2981 Release 4
14901 14902 14903 14904 14905 14906 14907
1105
: 14
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-SM-DataTypes
routingInfoForSM-Res....................identifier of RoutingInfoForSM-Res DEFINED in MAP-ShortMessageServic : 70 RoutingInfoForSM-Res....................type reference SEQUENCE DEFINED in MAP-SM-DataTypes : 80
2982
3GPP
2983 Release 4
14908 14909 14910 14911 14912 14913 14914 14915 14916 14917 14918 14919 14920 14921 14922 14923 14924 14925 14926 14927 14928 14929 14930 14931 14932 14933 14934 14935 14936 14937 14938 14939 14940 14941 14942 14943 14944 14945 14946 14947 14948 14949 14950 14951 14952 14953 14954 14955 14956 14957 14958 14959 14960 14961 14962 14963 14964 14965 14966 14967 14968 14969 14970 14971 14972 14973 14974 14975 14976 14977 14978 14979 14980 14981 14982 14983 14984
1106
Cross Reference Listing for MAP-Protocol 70
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 87
USED in MAP-ShortMessageServic : 46 USED in MAP-SM-DataTypes : 15
rss.....................................identifier of Named Number, 7 DEFINED in MAP-CommonDataTypes : 359 ruf-Outcome.............................identifier of [0] RUF-Outcome DEFINED in MAP-CH-DataTypes : 396 RUF-Outcome.............................type reference ENUMERATED DEFINED in MAP-CH-DataTypes : 400 USED in MAP-CH-DataTypes : 396 sai-Present.............................identifier of [9] NULL DEFINED in MAP-MS-DataTypes : 1781 sc-AddressNotIncluded...................identifier of Named Number, 0 DEFINED in MAP-SM-DataTypes : 196 sc-Congestion...........................identifier of Named Number, 4 DEFINED in MAP-ER-DataTypes : 147 segmentationProhibited..................identifier of NULL DEFINED in MAP-MS-DataTypes : 302 segmentationProhibited..................identifier of NULL DEFINED in MAP-MS-DataTypes : 697 selectedGSM-Algorithm...................identifier of [2] SelectedGSM-Algorithm DEFINED in MAP-MS-DataTypes : 618 SelectedGSM-Algorithm...................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 624 USED in MAP-MS-DataTypes : 618 selectedLSA-Id..........................identifier of [5] LSAIdentity DEFINED in MAP-MS-DataTypes : 1777 selectedRab-Id..........................identifier of [4] RAB-Id DEFINED in MAP-MS-DataTypes : 606 selectedRab-Id..........................identifier of [4] RAB-Id DEFINED in MAP-MS-DataTypes : 620 selectedUMTS-Algorithms.................identifier of [5] SelectedUMTS-Algorithms DEFINED in MAP-MS-DataTypes : 561 SelectedUMTS-Algorithms.................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 566 USED in MAP-MS-DataTypes : 561 617 selectedUMTS-Algorithms.................identifier of [1] SelectedUMTS-Algorithms DEFINED in MAP-MS-DataTypes : 617 sendAuthenticationInfo..................value reference SendAuthenticationInfo, CHOICE VALUE DEFINED in MAP-Protocol : 201 SendAuthenticationInfo..................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 350 USED in MAP-Protocol : 22 201 USED in MAP-MobileServiceOpera : 45 sendAuthenticationInfoArg...............identifier of SendAuthenticationInfoArg DEFINED in MAP-MobileServiceOpera : 352 SendAuthenticationInfoArg...............type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 694 USED in MAP-MobileServiceOpera : 131 352 USED in MAP-MS-DataTypes : 44 sendAuthenticationInfoRes...............identifier of SendAuthenticationInfoRes DEFINED in MAP-MobileServiceOpera : 359 SendAuthenticationInfoRes...............type reference [3] SEQUENCE DEFINED in MAP-MS-DataTypes : 711
2984
3GPP
2985 Release 4
14985 14986 14987 14988 14989 14990 14991
1107
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-MobileServiceOpera : 132 359 USED in MAP-MS-DataTypes : 45 sendEndSignal...........................value reference SendEndSignal, CHOICE VALUE DEFINED in MAP-Protocol : 192 SendEndSignal...........................type reference OPERATION
2986
3GPP
2987 Release 4
14992 14993 14994 14995 14996 14997 14998 14999 15000 15001 15002 15003 15004 15005 15006 15007 15008 15009 15010 15011 15012 15013 15014 15015 15016 15017 15018 15019 15020 15021 15022 15023 15024 15025 15026 15027 15028 15029 15030 15031 15032 15033 15034 15035 15036 15037 15038 15039 15040 15041 15042 15043 15044 15045 15046 15047 15048 15049 15050 15051 15052 15053 15054 15055 15056 15057 15058 15059 15060 15061 15062 15063 15064 15065 15066 15067 15068
1108
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 88
DEFINED in MAP-MobileServiceOpera : 322 USED in MAP-Protocol : 18 192 USED in MAP-MobileServiceOpera : 39 sendEndSignal-Arg.......................identifier of SendEndSignal-Arg DEFINED in MAP-MobileServiceOpera : 324 SendEndSignal-Arg.......................type reference [3] SEQUENCE DEFINED in MAP-MS-DataTypes : 629 USED in MAP-MobileServiceOpera : 127 324 USED in MAP-MS-DataTypes : 39 sendEndSignal-Res.......................identifier of SendEndSignal-Res DEFINED in MAP-MobileServiceOpera : 326 SendEndSignal-Res.......................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 634 USED in MAP-MobileServiceOpera : 128 326 USED in MAP-MS-DataTypes : 40 sendGroupCallEndSignal..................value reference SendGroupCallEndSignal, CHOICE VALUE DEFINED in MAP-Protocol : 297 SendGroupCallEndSignal..................type reference OPERATION DEFINED in MAP-Group-Call-Operati : 56 USED in MAP-Protocol : 102 297 USED in MAP-Group-Call-Operati : 14 sendGroupCallEndSignalArg...............identifier of SendGroupCallEndSignalArg DEFINED in MAP-Group-Call-Operati : 58 SendGroupCallEndSignalArg...............type reference SEQUENCE DEFINED in MAP-GR-DataTypes : 66 USED in MAP-Group-Call-Operati : 33 58 USED in MAP-GR-DataTypes : 16 sendGroupCallEndSignalRes...............identifier of SendGroupCallEndSignalRes DEFINED in MAP-Group-Call-Operati : 60 SendGroupCallEndSignalRes...............type reference SEQUENCE DEFINED in MAP-GR-DataTypes : 71 USED in MAP-Group-Call-Operati : 34 60 USED in MAP-GR-DataTypes : 17 sendIdentification......................value reference SendIdentification, CHOICE VALUE DEFINED in MAP-Protocol : 186 SendIdentification......................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 209 USED in MAP-Protocol : 15 186 USED in MAP-MobileServiceOpera : 18 sendIdentificationArg...................identifier of SendIdentificationArg DEFINED in MAP-MobileServiceOpera : 211 SendIdentificationArg...................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 295 USED in MAP-MobileServiceOpera : 119 211 USED in MAP-MS-DataTypes : 22 sendIdentificationRes...................identifier of SendIdentificationRes DEFINED in MAP-MobileServiceOpera : 213 SendIdentificationRes...................type reference [3] SEQUENCE DEFINED in MAP-MS-DataTypes : 306 USED in MAP-MobileServiceOpera : 120 213 USED in MAP-MS-DataTypes : 23 sendIMSI................................value reference SendIMSI, CHOICE VALUE DEFINED in MAP-Protocol : 228 SendIMSI................................type reference OPERATION DEFINED in MAP-OperationAndMainte : 77 USED in MAP-Protocol : 48 228 USED in MAP-OperationAndMainte : 15
2988
3GPP
2989 Release 4
15069 15070 15071 15072 15073 15074 15075
1109
3GPP TS 29.002 V4.17.0 (2006-06)
sendRoutingInfo.........................value reference SendRoutingInfo, CHOICE VALUE DEFINED in MAP-Protocol : 233 SendRoutingInfo.........................type reference OPERATION DEFINED in MAP-CallHandlingOperat : 80 USED in MAP-Protocol : 54 233
2990
3GPP
2991 Release 4
15076 15077 15078 15079 15080 15081 15082 15083 15084 15085 15086 15087 15088 15089 15090 15091 15092 15093 15094 15095 15096 15097 15098 15099 15100 15101 15102 15103 15104 15105 15106 15107 15108 15109 15110 15111 15112 15113 15114 15115 15116 15117 15118 15119 15120 15121 15122 15123 15124 15125 15126 15127 15128 15129 15130 15131 15132 15133 15134 15135 15136 15137 15138 15139 15140 15141 15142 15143 15144 15145 15146 15147 15148 15149 15150 15151 15152
1110
Cross Reference Listing for MAP-Protocol 13
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 89
USED in MAP-CallHandlingOperat :
sendRoutingInfoArg......................identifier of SendRoutingInfoArg DEFINED in MAP-CallHandlingOperat : 83 SendRoutingInfoArg......................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 94 USED in MAP-CallHandlingOperat : 54 83 USED in MAP-CH-DataTypes : 14 sendRoutingInfoForGprs..................value reference SendRoutingInfoForGprs, CHOICE VALUE DEFINED in MAP-Protocol : 308 SendRoutingInfoForGprs..................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 435 USED in MAP-Protocol : 34 308 USED in MAP-MobileServiceOpera : 61 sendRoutingInfoForGprsArg...............identifier of SendRoutingInfoForGprsArg DEFINED in MAP-MobileServiceOpera : 437 SendRoutingInfoForGprsArg...............type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1649 USED in MAP-MobileServiceOpera : 153 437 USED in MAP-MS-DataTypes : 119 sendRoutingInfoForGprsRes...............identifier of SendRoutingInfoForGprsRes DEFINED in MAP-MobileServiceOpera : 439 SendRoutingInfoForGprsRes...............type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1656 USED in MAP-MobileServiceOpera : 154 439 USED in MAP-MS-DataTypes : 120 sendRoutingInfoForLCS...................value reference SendRoutingInfoForLCS, CHOICE VALUE DEFINED in MAP-Protocol : 321 SendRoutingInfoForLCS...................type reference OPERATION DEFINED in MAP-LocationServiceOpe : 52 USED in MAP-Protocol : 109 321 USED in MAP-LocationServiceOpe : 14 sendRoutingInfoForSM....................value reference SendRoutingInfoForSM, CHOICE VALUE DEFINED in MAP-Protocol : 264 SendRoutingInfoForSM....................type reference OPERATION DEFINED in MAP-ShortMessageServic : 66 USED in MAP-Protocol : 87 264 USED in MAP-ShortMessageServic : 13 sendRoutingInfoRes......................identifier of SendRoutingInfoRes DEFINED in MAP-CallHandlingOperat : 85 SendRoutingInfoRes......................type reference [3] SEQUENCE DEFINED in MAP-CH-DataTypes : 145 USED in MAP-CallHandlingOperat : 55 85 USED in MAP-CH-DataTypes : 15 sendSubscriberData......................identifier of [0] NULL DEFINED in MAP-MS-DataTypes : 232 serviceCentreAddress....................identifier of [2] AddressString DEFINED in MAP-SM-DataTypes : 56 serviceCentreAddress....................identifier of AddressString DEFINED in MAP-SM-DataTypes : 146 serviceCentreAddress....................identifier of AddressString DEFINED in MAP-SM-DataTypes : 180 serviceCentreAddressDA..................identifier of [4] AddressString DEFINED in MAP-SM-DataTypes : 136 serviceCentreAddressOA..................identifier of [4] AddressString DEFINED in MAP-SM-DataTypes : 141
2992
3GPP
2993 Release 4
15153 15154 15155 15156 15157 15158 15159
1111
3GPP TS 29.002 V4.17.0 (2006-06)
serviceGranted..........................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 951 serviceIndicator........................identifier of [2] ServiceIndicator DEFINED in MAP-SS-DataTypes : 313
2994
3GPP
2995 Release 4
15160 15161 15162 15163 15164 15165 15166 15167 15168 15169 15170 15171 15172 15173 15174 15175 15176 15177 15178 15179 15180 15181 15182 15183 15184 15185 15186 15187 15188 15189 15190 15191 15192 15193 15194 15195 15196 15197 15198 15199 15200 15201 15202 15203 15204 15205 15206 15207 15208 15209 15210 15211 15212 15213 15214 15215 15216 15217 15218 15219 15220 15221 15222 15223 15224 15225 15226 15227 15228 15229 15230 15231 15232 15233 15234 15235 15236
1112
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 90
ServiceIndicator........................type reference BIT STRING DEFINED in MAP-SS-DataTypes : 318 USED in MAP-SS-DataTypes : 313 serviceKey..............................identifier of [1] ServiceKey DEFINED in MAP-MS-DataTypes : 841 serviceKey..............................identifier of ServiceKey DEFINED in MAP-MS-DataTypes : 1365 serviceKey..............................identifier of ServiceKey DEFINED in MAP-MS-DataTypes : 1422 ServiceKey..............................type reference INTEGER DEFINED in MAP-MS-DataTypes : 1429 USED in MAP-MS-DataTypes : 70 841 1365 1422 1556 1581 1630 1988 serviceKey..............................identifier of [1] ServiceKey DEFINED in MAP-MS-DataTypes : 1556 serviceKey..............................identifier of ServiceKey DEFINED in MAP-MS-DataTypes : 1581 serviceKey..............................identifier of ServiceKey DEFINED in MAP-MS-DataTypes : 1630 serviceKey..............................identifier of ServiceKey DEFINED in MAP-MS-DataTypes : 1988 serviceRequest..........................identifier of Named Number, 7 DEFINED in MAP-MS-DataTypes : 398 setReportingState.......................value reference SetReportingState, CHOICE VALUE DEFINED in MAP-Protocol : 238 SetReportingState.......................type reference OPERATION DEFINED in MAP-CallHandlingOperat : 153 USED in MAP-Protocol : 59 238 USED in MAP-CallHandlingOperat : 18 setReportingStateArg....................identifier of SetReportingStateArg DEFINED in MAP-CallHandlingOperat : 155 SetReportingStateArg....................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 315 USED in MAP-CallHandlingOperat : 64 155 USED in MAP-CH-DataTypes : 27 setReportingStateRes....................identifier of SetReportingStateRes DEFINED in MAP-CallHandlingOperat : 157 SetReportingStateRes....................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 330 USED in MAP-CallHandlingOperat : 65 157 USED in MAP-CH-DataTypes : 28 sgsn....................................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 718 sgsn-Address............................identifier of GSN-Address DEFINED in MAP-MS-DataTypes : 419 sgsn-Address............................identifier of [0] GSN-Address DEFINED in MAP-MS-DataTypes : 1657 sgsn-Address............................identifier of [1] GSN-Address DEFINED in MAP-MS-DataTypes : 1681 sgsn-CAMEL-SubscriptionInfo.............identifier of [17] SGSN-CAMEL-SubscriptionInfo DEFINED in MAP-MS-DataTypes : 752 SGSN-CAMEL-SubscriptionInfo.............type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 814 USED in MAP-MS-DataTypes : 752
2996
3GPP
2997 Release 4
15237 15238 15239 15240 15241 15242 15243
1113
3GPP TS 29.002 V4.17.0 (2006-06)
sgsn-Capability.........................identifier of [0] SGSN-Capability DEFINED in MAP-MS-DataTypes : 422 SGSN-Capability.........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 425 USED in MAP-MS-DataTypes : 422
2998
3GPP
2999 Release 4
15244 15245 15246 15247 15248 15249 15250 15251 15252 15253 15254 15255 15256 15257 15258 15259 15260 15261 15262 15263 15264 15265 15266 15267 15268 15269 15270 15271 15272 15273 15274 15275 15276 15277 15278 15279 15280 15281 15282 15283 15284 15285 15286 15287 15288 15289 15290 15291 15292 15293 15294 15295 15296 15297 15298 15299 15300 15301 15302 15303 15304 15305 15306 15307 15308 15309 15310 15311 15312 15313 15314 15315 15316 15317 15318 15319 15320
1114
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 91
sgsn-Number.............................identifier of [1] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 285 sgsn-Number.............................identifier of [1] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 388 sgsn-Number.............................identifier of ISDN-AddressString DEFINED in MAP-MS-DataTypes : 418 sgsn-Number.............................identifier of [1] ISDN-AddressString DEFINED in MAP-SM-DataTypes : 100 shapeOfLocationEstimateNotSupported.....identifier of Named Number, 6 DEFINED in MAP-LCS-DataTypes : 374 shapeOfLocationEstimateNotSupported.....identifier of [0] NULL DEFINED in MAP-ER-DataTypes : 194 shortMessage............................identifier of Named Number, 4 DEFINED in MAP-MS-DataTypes : 395 shortMessageMO-PP.......................value reference TeleserviceCode, '00100010'B DEFINED in MAP-TS-Code : 46 shortMessageMT-PP.......................value reference TeleserviceCode, '00100001'B DEFINED in MAP-TS-Code : 45 shortTermDenial.........................value reference ShortTermDenial, CHOICE VALUE DEFINED in MAP-Protocol : 415 ShortTermDenial.........................type reference ERROR DEFINED in MAP-Errors : 388 USED in MAP-Protocol : 160 415 USED in MAP-SupplementaryServi : 53 264 USED in MAP-Errors : 73 shortTermDenialParam....................identifier of ShortTermDenialParam DEFINED in MAP-Errors : 390 ShortTermDenialParam....................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 334 USED in MAP-Errors : 139 390 USED in MAP-ER-DataTypes : 47 signalInfo..............................identifier of SignalInfo DEFINED in MAP-CommonDataTypes : 200 SignalInfo..............................type reference OCTET STRING DEFINED in MAP-CommonDataTypes : 207 USED in MAP-CommonDataTypes : 24 200 226 USED in MAP-SM-DataTypes : 34 110 116 123 129 USED in MAP-ER-DataTypes : 73 153 signalInfo..............................identifier of SignalInfo DEFINED in MAP-CommonDataTypes : 226 signalInfo..............................identifier of LongSignalInfo DEFINED in MAP-CommonDataTypes : 243 sIWFSNumber.............................identifier of [0] ISDN-AddressString DEFINED in MAP-CH-DataTypes : 300 sIWFSSignallingModify...................value reference SIWFSSignallingModify, CHOICE VALUE DEFINED in MAP-Protocol : 237 SIWFSSignallingModify...................type reference OPERATION DEFINED in MAP-CallHandlingOperat : 141 USED in MAP-Protocol : 58 237 USED in MAP-CallHandlingOperat : 17 sIWFSSignallingModifyArg................identifier of SIWFSSignallingModifyArg DEFINED in MAP-CallHandlingOperat : 143 SIWFSSignallingModifyArg................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 304
3000
3GPP
3001 Release 4
15321 15322 15323 15324 15325 15326 15327
1115
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-CallHandlingOperat : 62 143 USED in MAP-CH-DataTypes : 25 sIWFSSignallingModifyRes................identifier of SIWFSSignallingModifyRes DEFINED in MAP-CallHandlingOperat : 145 SIWFSSignallingModifyRes................type reference SEQUENCE
3002
3GPP
3003 Release 4
15328 15329 15330 15331 15332 15333 15334 15335 15336 15337 15338 15339 15340 15341 15342 15343 15344 15345 15346 15347 15348 15349 15350 15351 15352 15353 15354 15355 15356 15357 15358 15359 15360 15361 15362 15363 15364 15365 15366 15367 15368 15369 15370 15371 15372 15373 15374 15375 15376 15377 15378 15379 15380 15381 15382 15383 15384 15385 15386 15387 15388 15389 15390 15391 15392 15393 15394 15395 15396 15397 15398 15399 15400 15401 15402 15403 15404
1116
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 92
DEFINED in MAP-CH-DataTypes : 310 USED in MAP-CallHandlingOperat : 63 145 USED in MAP-CH-DataTypes : 26 slr-ArgExtensionContainer...............identifier of [7] SLR-ArgExtensionContainer DEFINED in MAP-LCS-DataTypes : 326 SLR-ArgExtensionContainer...............type reference SEQUENCE DEFINED in MAP-ExtensionDataTypes : 38 USED in MAP-LCS-DataTypes : 42 326 USED in MAP-ExtensionDataTypes : 17 slr-Arg-PCS-Extensions..................identifier of [1] SLR-Arg-PCS-Extensions DEFINED in MAP-ExtensionDataTypes : 40 SLR-Arg-PCS-Extensions..................type reference SEQUENCE DEFINED in MAP-ExtensionDataTypes : 65 USED in MAP-ExtensionDataTypes : 40 SMS-CAMEL-TDP-Data......................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1554 USED in MAP-MS-DataTypes : 1550 sms-CAMEL-TDP-DataList..................identifier of [0] SMS-CAMEL-TDP-DataList DEFINED in MAP-MS-DataTypes : 1536 SMS-CAMEL-TDP-DataList..................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1549 USED in MAP-MS-DataTypes : 1536 sms-CollectedInfo.......................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 1564 sms-CSI.................................identifier of [1] SMS-CSI DEFINED in MAP-MS-DataTypes : 816 sms-csi.................................identifier of Named Number, 5 DEFINED in MAP-MS-DataTypes : 1298 sms-CSI.................................identifier of [6] SMS-CSI DEFINED in MAP-MS-DataTypes : 1338 SMS-CSI.................................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1535 USED in MAP-MS-DataTypes : 816 1338 1912 sms-CSI.................................identifier of Named Number, 5 DEFINED in MAP-MS-DataTypes : 1874 sms-CSI.................................identifier of [10] SMS-CSI DEFINED in MAP-MS-DataTypes : 1912 sms-TriggerDetectionPoint...............identifier of [0] SMS-TriggerDetectionPoint DEFINED in MAP-MS-DataTypes : 1555 SMS-TriggerDetectionPoint...............type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 1563 USED in MAP-MS-DataTypes : 1555 sm-DeliveryFailure......................value reference SM-DeliveryFailure, CHOICE VALUE DEFINED in MAP-Protocol : 422 SM-DeliveryFailure......................type reference ERROR DEFINED in MAP-Errors : 406 USED in MAP-Protocol : 155 422 USED in MAP-ShortMessageServic : 38 91 108 USED in MAP-Errors : 78 sm-DeliveryFailureCause.................identifier of SM-DeliveryFailureCause DEFINED in MAP-Errors : 408 SM-DeliveryFailureCause.................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 151 USED in MAP-Errors : 109 408 USED in MAP-ER-DataTypes : 19
3004
3GPP
3005 Release 4
15405 15406 15407 15408 15409 15410 15411
1117
3GPP TS 29.002 V4.17.0 (2006-06)
sm-DeliveryOutcome......................identifier of SM-DeliveryOutcome DEFINED in MAP-SM-DataTypes : 147 SM-DeliveryOutcome......................type reference ENUMERATED DEFINED in MAP-SM-DataTypes : 167 USED in MAP-SM-DataTypes : 26 147 158
3006
3GPP
3007 Release 4
15412 15413 15414 15415 15416 15417 15418 15419 15420 15421 15422 15423 15424 15425 15426 15427 15428 15429 15430 15431 15432 15433 15434 15435 15436 15437 15438 15439 15440 15441 15442 15443 15444 15445 15446 15447 15448 15449 15450 15451 15452 15453 15454 15455 15456 15457 15458 15459 15460 15461 15462 15463 15464 15465 15466 15467 15468 15469 15470 15471 15472 15473 15474 15475 15476 15477 15478 15479 15480 15481 15482 15483 15484 15485 15486 15487 15488
1118
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 93
SM-EnumeratedDeliveryFailureCause.......type reference ENUMERATED DEFINED in MAP-ER-DataTypes : 142 USED in MAP-ER-DataTypes : 152 sm-EnumeratedDeliveryFailureCause.......identifier of SM-EnumeratedDeliveryFailureCause DEFINED in MAP-ER-DataTypes : 152 sm-RP-DA................................identifier of SM-RP-DA DEFINED in MAP-SM-DataTypes : 108 sm-RP-DA................................identifier of SM-RP-DA DEFINED in MAP-SM-DataTypes : 121 SM-RP-DA................................type reference CHOICE DEFINED in MAP-SM-DataTypes : 133 USED in MAP-SM-DataTypes : 108 121 sm-RP-MTI...............................identifier of [8] SM-RP-MTI DEFINED in MAP-SM-DataTypes : 62 SM-RP-MTI...............................type reference INTEGER DEFINED in MAP-SM-DataTypes : 65 USED in MAP-SM-DataTypes : 62 sm-RP-OA................................identifier of SM-RP-OA DEFINED in MAP-SM-DataTypes : 109 sm-RP-OA................................identifier of SM-RP-OA DEFINED in MAP-SM-DataTypes : 122 SM-RP-OA................................type reference CHOICE DEFINED in MAP-SM-DataTypes : 139 USED in MAP-SM-DataTypes : 109 122 sm-RP-PRI...............................identifier of [1] BOOLEAN DEFINED in MAP-SM-DataTypes : 55 sm-RP-SMEA..............................identifier of [9] SM-RP-SMEA DEFINED in MAP-SM-DataTypes : 63 SM-RP-SMEA..............................type reference OCTET STRING DEFINED in MAP-SM-DataTypes : 72 USED in MAP-SM-DataTypes : 63 sm-RP-UI................................identifier of SignalInfo DEFINED in MAP-SM-DataTypes : 110 sm-RP-UI................................identifier of SignalInfo DEFINED in MAP-SM-DataTypes : 116 sm-RP-UI................................identifier of SignalInfo DEFINED in MAP-SM-DataTypes : 123 sm-RP-UI................................identifier of SignalInfo DEFINED in MAP-SM-DataTypes : 129 solsaSupportIndicator...................identifier of [2] NULL DEFINED in MAP-MS-DataTypes : 225 solsaSupportIndicator...................identifier of NULL DEFINED in MAP-MS-DataTypes : 426 specificCSIDeletedList..................identifier of [14] SpecificCSI-Withdraw DEFINED in MAP-MS-DataTypes : 1917 specificCSI-Withdraw....................identifier of [15] SpecificCSI-Withdraw DEFINED in MAP-MS-DataTypes : 1289 SpecificCSI-Withdraw....................type reference BIT STRING DEFINED in MAP-MS-DataTypes : 1292 USED in MAP-MS-DataTypes : 1289 1917 sres....................................identifier of SRES DEFINED in MAP-MS-DataTypes : 330
3008
3GPP
3009 Release 4
15489 15490 15491 15492 15493 15494 15495
1119
3GPP TS 29.002 V4.17.0 (2006-06)
SRES....................................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 359 USED in MAP-MS-DataTypes : 330 ss-AccessBarred.........................identifier of Named Number, 5 DEFINED in MAP-MS-DataTypes : 979
3010
3GPP
3011 Release 4
15496 15497 15498 15499 15500 15501 15502 15503 15504 15505 15506 15507 15508 15509 15510 15511 15512 15513 15514 15515 15516 15517 15518 15519 15520 15521 15522 15523 15524 15525 15526 15527 15528 15529 15530 15531 15532 15533 15534 15535 15536 15537 15538 15539 15540 15541 15542 15543 15544 15545 15546 15547 15548 15549 15550 15551 15552 15553 15554 15555 15556 15557 15558 15559 15560 15561 15562 15563 15564 15565 15566 15567 15568 15569 15570 15571 15572
1120
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 94
ss-CamelData............................identifier of SS-CamelData DEFINED in MAP-MS-DataTypes : 1372 SS-CamelData............................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1381 USED in MAP-MS-DataTypes : 1372 ss-Code.................................identifier of SS-Code DEFINED in MAP-SupplementaryServi : 219 ss-Code.................................identifier of SS-Code DEFINED in MAP-MS-DataTypes : 1029 ss-Code.................................identifier of SS-Code DEFINED in MAP-MS-DataTypes : 1088 ss-Code.................................identifier of SS-Code DEFINED in MAP-MS-DataTypes : 1159 ss-Code.................................identifier of SS-Code DEFINED in MAP-MS-DataTypes : 1172 ss-Code.................................identifier of SS-Code DEFINED in MAP-MS-DataTypes : 1242 ss-Code.................................identifier of [0] SS-Code DEFINED in MAP-MS-DataTypes : 1936 ss-Code.................................identifier of [0] SS-Code DEFINED in MAP-MS-DataTypes : 1947 ss-Code.................................identifier of [0] SS-Code DEFINED in MAP-MS-DataTypes : 2007 ss-Code.................................identifier of [0] SS-Code DEFINED in MAP-MS-DataTypes : 2014 ss-Code.................................identifier of [0] SS-Code DEFINED in MAP-CommonDataTypes : 459 ss-Code.................................identifier of SS-Code DEFINED in MAP-SS-DataTypes : 73 ss-Code.................................identifier of SS-Code DEFINED in MAP-SS-DataTypes : 91 ss-Code.................................identifier of SS-Code DEFINED in MAP-SS-DataTypes : 149 ss-Code.................................identifier of SS-Code DEFINED in MAP-SS-DataTypes : 162 ss-Code.................................identifier of SS-Code DEFINED in MAP-SS-DataTypes : 185 ss-Code.................................identifier of [0] SS-Code DEFINED in MAP-SS-DataTypes : 306 ss-Code.................................identifier of [0] SS-Code DEFINED in MAP-SS-DataTypes : 329 ss-Code.................................identifier of [0] SS-Code DEFINED in MAP-SS-DataTypes : 334 SS-Code.................................type reference OCTET STRING DEFINED in MAP-SS-Code : 11 USED in MAP-SupplementaryServi : 78 219 USED in MAP-MS-DataTypes : 148 1029 1088 1159 1172 1242 1387 1936 1947 2007 2014 USED in MAP-CommonDataTypes : 76 459 USED in MAP-SS-DataTypes : 65 73 91 149 162 185 257 272 306 329 334 USED in MAP-SS-Code : 21 25 28 30 32 34 36 40 42 48 50 52 54 56 58 60 63 66
3012
3GPP
3013 Release 4
15573 15574 15575 15576 15577 15578 15579
1121
75 77 79 81 84 87 90 99 102 104 107 110 112 114 121 123 125 128 130 132 136 139 140 141 142 143 144 145 148 149 150 151 153 156 159 166 168 171 173 175 178 : 82 131
3GPP TS 29.002 V4.17.0 (2006-06)
68 72 93 96 117 119 137 138 146 147 161 163 USED in MAP-ER-DataTypes
3014
3GPP
3015 Release 4
15580 15581 15582 15583 15584 15585 15586 15587 15588 15589 15590 15591 15592 15593 15594 15595 15596 15597 15598 15599 15600 15601 15602 15603 15604 15605 15606 15607 15608 15609 15610 15611 15612 15613 15614 15615 15616 15617 15618 15619 15620 15621 15622 15623 15624 15625 15626 15627 15628 15629 15630 15631 15632 15633 15634 15635 15636 15637 15638 15639 15640 15641 15642 15643 15644 15645 15646 15647 15648 15649 15650 15651 15652 15653 15654 15655 15656
1122
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 95
ss-Code.................................identifier of [1] SS-Code DEFINED in MAP-ER-DataTypes : 131 ss-csi..................................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 1294 ss-CSI..................................identifier of [2] SS-CSI DEFINED in MAP-MS-DataTypes : 1334 SS-CSI..................................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1371 USED in MAP-MS-DataTypes : 69 1334 1913 ss-CSI..................................identifier of Named Number, 6 DEFINED in MAP-MS-DataTypes : 1875 ss-CSI..................................identifier of [11] SS-CSI DEFINED in MAP-MS-DataTypes : 1913 ss-Data.................................identifier of [3] Ext-SS-Data DEFINED in MAP-MS-DataTypes : 1024 ss-Data.................................identifier of [3] SS-Data DEFINED in MAP-SS-DataTypes : 88 SS-Data.................................type reference SEQUENCE DEFINED in MAP-SS-DataTypes : 161 USED in MAP-SS-DataTypes : 33 88 ss-ErrorStatus..........................value reference SS-ErrorStatus, CHOICE VALUE DEFINED in MAP-Protocol : 405 SS-ErrorStatus..........................type reference ERROR DEFINED in MAP-Errors : 354 USED in MAP-Protocol : 145 405 USED in MAP-MobileServiceOpera : 101 290 USED in MAP-SupplementaryServi : 41 101 118 135 155 262 279 USED in MAP-Errors : 64 ss-Event................................identifier of [2] SS-Code DEFINED in MAP-SS-DataTypes : 272 ss-EventList............................identifier of SS-EventList DEFINED in MAP-MS-DataTypes : 1382 SS-EventList............................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1387 USED in MAP-MS-DataTypes : 1382 ss-EventSpecification...................identifier of [3] SS-EventSpecification DEFINED in MAP-SS-DataTypes : 278 SS-EventSpecification...................type reference SEQUENCE OF DEFINED in MAP-SS-DataTypes : 300 USED in MAP-SS-DataTypes : 278 ss-ForBS................................identifier of SS-ForBS-Code DEFINED in MAP-SupplementaryServi : 106 ss-ForBS................................identifier of SS-ForBS-Code DEFINED in MAP-SupplementaryServi : 123 ss-ForBS................................identifier of SS-ForBS-Code DEFINED in MAP-SupplementaryServi : 143 ss-ForBS................................identifier of SS-ForBS-Code DEFINED in MAP-SupplementaryServi : 162 SS-ForBS-Code...........................type reference SEQUENCE DEFINED in MAP-SS-DataTypes : 184 USED in MAP-SupplementaryServi : 62 106 123 143 162 USED in MAP-MS-DataTypes : 142 1860 USED in MAP-SS-DataTypes : 18
3016
3GPP
3017 Release 4
15657 15658 15659 15660 15661 15662 15663
1123
3GPP TS 29.002 V4.17.0 (2006-06)
ss-Incompatibility......................value reference SS-Incompatibility, CHOICE VALUE DEFINED in MAP-Protocol : 408 SS-Incompatibility......................type reference ERROR DEFINED in MAP-Errors : 371 USED in MAP-Protocol : 148 408 USED in MAP-MobileServiceOpera : 103 291
3018
3GPP
3019 Release 4
15664 15665 15666 15667 15668 15669 15670 15671 15672 15673 15674 15675 15676 15677 15678 15679 15680 15681 15682 15683 15684 15685 15686 15687 15688 15689 15690 15691 15692 15693 15694 15695 15696 15697 15698 15699 15700 15701 15702 15703 15704 15705 15706 15707 15708 15709 15710 15711 15712 15713 15714 15715 15716 15717 15718 15719 15720 15721 15722 15723 15724 15725 15726 15727 15728 15729 15730 15731 15732 15733 15734 15735 15736 15737 15738 15739 15740
1124
Cross Reference Listing for MAP-Protocol 44 102 137 263
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 96
USED in MAP-SupplementaryServi : USED in MAP-Errors : 67
ss-IncompatibilityCause.................identifier of SS-IncompatibilityCause DEFINED in MAP-Errors : 373 SS-IncompatibilityCause.................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 130 USED in MAP-Errors : 107 373 USED in MAP-ER-DataTypes : 17 ss-Info.................................identifier of SS-Info DEFINED in MAP-SupplementaryServi : 91 ss-Info.................................identifier of SS-Info DEFINED in MAP-SupplementaryServi : 108 ss-Info.................................identifier of SS-Info DEFINED in MAP-SupplementaryServi : 125 ss-Info.................................identifier of SS-Info DEFINED in MAP-SupplementaryServi : 145 SS-Info.................................type reference CHOICE DEFINED in MAP-SS-DataTypes : 85 USED in MAP-SupplementaryServi : 61 91 108 125 145 USED in MAP-SS-DataTypes : 15 262 ss-InfoFor-CSE..........................identifier of [0] Ext-SS-InfoFor-CSE DEFINED in MAP-MS-DataTypes : 1930 SS-InfoList.............................type reference SEQUENCE OF DEFINED in MAP-SS-DataTypes : 261 USED in MAP-SS-DataTypes : 27 ss-InvocationNotification...............value reference SS-InvocationNotification, CHOICE VALUE DEFINED in MAP-Protocol : 291 SS-InvocationNotification...............type reference OPERATION DEFINED in MAP-SupplementaryServi : 240 USED in MAP-Protocol : 79 291 USED in MAP-SupplementaryServi : 23 ss-InvocationNotificationArg............identifier of SS-InvocationNotificationArg DEFINED in MAP-SupplementaryServi : 242 SS-InvocationNotificationArg............type reference SEQUENCE DEFINED in MAP-SS-DataTypes : 269 USED in MAP-SupplementaryServi : 68 242 USED in MAP-SS-DataTypes : 34 ss-InvocationNotificationRes............identifier of SS-InvocationNotificationRes DEFINED in MAP-SupplementaryServi : 244 SS-InvocationNotificationRes............type reference SEQUENCE DEFINED in MAP-SS-DataTypes : 295 USED in MAP-SupplementaryServi : 69 244 USED in MAP-SS-DataTypes : 35 ss-List.................................identifier of [3] SS-List DEFINED in MAP-MS-DataTypes : 1258 ss-List.................................identifier of [2] SS-List DEFINED in MAP-MS-DataTypes : 1276 ss-List.................................identifier of [1] SS-List DEFINED in MAP-CH-DataTypes : 154 SS-List.................................type reference SEQUENCE OF DEFINED in MAP-SS-DataTypes : 256 USED in MAP-MS-DataTypes : 141 1258 1276 USED in MAP-CH-DataTypes : 57 154 USED in MAP-SS-DataTypes : 26 ss-NotAvailable.........................value reference SS-NotAvailable, CHOICE VALUE
3020
3GPP
3021 Release 4
15741 15742 15743 15744 15745 15746 15747
1125
: 406
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-Protocol
SS-NotAvailable.........................type reference ERROR DEFINED in MAP-Errors : 359 USED in MAP-Protocol : 146 406 USED in MAP-MobileServiceOpera : 102 272 USED in MAP-SupplementaryServi : 42 173
3022
3GPP
3023 Release 4
15748 15749 15750 15751 15752 15753 15754 15755 15756 15757 15758 15759 15760 15761 15762 15763 15764 15765 15766 15767 15768 15769 15770 15771 15772 15773 15774 15775 15776 15777 15778 15779 15780 15781 15782 15783 15784 15785 15786 15787 15788 15789 15790 15791 15792 15793 15794 15795 15796 15797 15798 15799 15800 15801 15802 15803 15804 15805 15806 15807 15808 15809 15810 15811 15812 15813 15814 15815 15816 15817 15818 15819 15820 15821 15822 15823 15824
1126
Cross Reference Listing for MAP-Protocol : 65
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 97
USED in MAP-Errors
ss-NotAvailableParam....................identifier of SS-NotAvailableParam DEFINED in MAP-Errors : 361 SS-NotAvailableParam....................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 299 USED in MAP-Errors : 149 361 USED in MAP-ER-DataTypes : 57 ss-Status...............................identifier of SS-Status DEFINED in MAP-Errors : 356 ss-Status...............................identifier of [4] Ext-SS-Status DEFINED in MAP-MS-DataTypes : 1039 ss-Status...............................identifier of [4] Ext-SS-Status DEFINED in MAP-MS-DataTypes : 1098 ss-Status...............................identifier of [4] Ext-SS-Status DEFINED in MAP-MS-DataTypes : 1160 ss-Status...............................identifier of Ext-SS-Status DEFINED in MAP-MS-DataTypes : 1173 ss-Status...............................identifier of Ext-SS-Status DEFINED in MAP-MS-DataTypes : 1243 ss-Status...............................identifier of [2] Ext-SS-Status DEFINED in MAP-MS-DataTypes : 1938 ss-Status...............................identifier of [2] Ext-SS-Status DEFINED in MAP-MS-DataTypes : 1949 ss-Status...............................identifier of [1] Ext-SS-Status DEFINED in MAP-CommonDataTypes : 460 ss-Status...............................identifier of [4] SS-Status DEFINED in MAP-SS-DataTypes : 101 SS-Status...............................type reference OCTET STRING DEFINED in MAP-SS-DataTypes : 109 USED in MAP-Errors : 102 356 USED in MAP-SS-DataTypes : 16 101 158 163 191 216 335 USED in MAP-ER-DataTypes : 68 133 ss-Status...............................identifier of [4] SS-Status DEFINED in MAP-SS-DataTypes : 158 ss-Status...............................identifier of [4] SS-Status DEFINED in MAP-SS-DataTypes : 163 ss-Status...............................identifier of SS-Status DEFINED in MAP-SS-DataTypes : 191 ss-Status...............................identifier of [0] SS-Status DEFINED in MAP-SS-DataTypes : 216 ss-Status...............................identifier of [1] SS-Status DEFINED in MAP-SS-DataTypes : 335 ss-Status...............................identifier of [4] SS-Status DEFINED in MAP-ER-DataTypes : 133 ss-SubscriptionOption...................identifier of SS-SubscriptionOption DEFINED in MAP-MS-DataTypes : 1161 ss-SubscriptionOption...................identifier of SS-SubscriptionOption DEFINED in MAP-SS-DataTypes : 164 SS-SubscriptionOption...................type reference CHOICE DEFINED in MAP-SS-DataTypes : 171 USED in MAP-MS-DataTypes : 140 1161 USED in MAP-SS-DataTypes : 17 164
3024
3GPP
3025 Release 4
15825 15826 15827 15828 15829 15830 15831
1127
3GPP TS 29.002 V4.17.0 (2006-06)
ss-SubscriptionViolation................value reference SS-SubscriptionViolation, CHOICE VALUE DEFINED in MAP-Protocol : 407 SS-SubscriptionViolation................type reference ERROR DEFINED in MAP-Errors : 365 USED in MAP-Protocol : 147 407 USED in MAP-MobileServiceOpera : 104 289
3026
3GPP
3027 Release 4
15832 15833 15834 15835 15836 15837 15838 15839 15840 15841 15842 15843 15844 15845 15846 15847 15848 15849 15850 15851 15852 15853 15854 15855 15856 15857 15858 15859 15860 15861 15862 15863 15864 15865 15866 15867 15868 15869 15870 15871 15872 15873 15874 15875 15876 15877 15878 15879 15880 15881 15882 15883 15884 15885 15886 15887 15888 15889 15890 15891 15892 15893 15894 15895 15896 15897 15898 15899 15900 15901 15902 15903 15904 15905 15906 15907 15908
1128
Cross Reference Listing for MAP-Protocol 43 136 156 227
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 98
USED in MAP-SupplementaryServi : USED in MAP-Errors : 66
ss-SubscriptionViolationParam...........identifier of SS-SubscriptionViolationParam DEFINED in MAP-Errors : 367 SS-SubscriptionViolationParam...........type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 303 USED in MAP-Errors : 150 367 USED in MAP-ER-DataTypes : 58 startMonitoring.........................identifier of Named Number, 1 DEFINED in MAP-CH-DataTypes : 324 stateAttributes.........................identifier of [5] StateAttributes DEFINED in MAP-GR-DataTypes : 84 StateAttributes.........................type reference SEQUENCE DEFINED in MAP-GR-DataTypes : 118 USED in MAP-GR-DataTypes : 84 statusReport............................value reference StatusReport, CHOICE VALUE DEFINED in MAP-Protocol : 239 StatusReport............................type reference OPERATION DEFINED in MAP-CallHandlingOperat : 167 USED in MAP-Protocol : 60 239 USED in MAP-CallHandlingOperat : 19 statusReportArg.........................identifier of StatusReportArg DEFINED in MAP-CallHandlingOperat : 169 StatusReportArg.........................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 345 USED in MAP-CallHandlingOperat : 66 169 USED in MAP-CH-DataTypes : 29 statusReportRes.........................identifier of StatusReportRes DEFINED in MAP-CallHandlingOperat : 171 StatusReportRes.........................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 381 USED in MAP-CallHandlingOperat : 67 171 USED in MAP-CH-DataTypes : 30 stopMonitoring..........................identifier of Named Number, 0 DEFINED in MAP-CH-DataTypes : 323 storedMSISDN............................identifier of ISDN-AddressString DEFINED in MAP-SM-DataTypes : 173 storedMSISDN............................identifier of ISDN-AddressString DEFINED in MAP-SM-DataTypes : 184 subBusyForMT-SMS-Param..................identifier of SubBusyForMT-SMS-Param DEFINED in MAP-Errors : 403 SubBusyForMT-SMS-Param..................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 311 USED in MAP-Errors : 133 403 USED in MAP-ER-DataTypes : 40 subscriberBusyForMT-SMS.................value reference SubscriberBusyForMT-SMS, CHOICE VALUE DEFINED in MAP-Protocol : 421 SubscriberBusyForMT-SMS.................type reference ERROR DEFINED in MAP-Errors : 401 USED in MAP-Protocol : 154 421 USED in MAP-ShortMessageServic : 37 107 USED in MAP-Errors : 77 SubscriberData..........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 928 USED in MAP-MS-DataTypes : 60 736
3028
3GPP
3029 Release 4
15909 15910 15911 15912 15913 15914 15915
1129
3GPP TS 29.002 V4.17.0 (2006-06)
subscriberDataStored....................identifier of [1] AgeIndicator DEFINED in MAP-MS-DataTypes : 233 SubscriberId............................type reference CHOICE DEFINED in MAP-CommonDataTypes : 316 USED in MAP-CommonDataTypes : 33
3030
3GPP
3031 Release 4
15916 15917 15918 15919 15920 15921 15922 15923 15924 15925 15926 15927 15928 15929 15930 15931 15932 15933 15934 15935 15936 15937 15938 15939 15940 15941 15942 15943 15944 15945 15946 15947 15948 15949 15950 15951 15952 15953 15954 15955 15956 15957 15958 15959 15960 15961 15962 15963 15964 15965 15966 15967 15968 15969 15970 15971 15972 15973 15974 15975 15976 15977 15978 15979 15980 15981 15982 15983 15984 15985 15986 15987 15988 15989 15990 15991 15992
1130
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 99
subscriberIdentity......................identifier of [0] SubscriberIdentity DEFINED in MAP-MS-DataTypes : 1827 subscriberIdentity......................identifier of [0] SubscriberIdentity DEFINED in MAP-MS-DataTypes : 1842 subscriberIdentity......................identifier of [0] SubscriberIdentity DEFINED in MAP-MS-DataTypes : 1920 SubscriberIdentity......................type reference CHOICE DEFINED in MAP-CommonDataTypes : 373 USED in MAP-MS-DataTypes : 180 1827 1842 1920 USED in MAP-CommonDataTypes : 42 USED in MAP-LCS-DataTypes : 33 67 72 subscriberInfo..........................identifier of SubscriberInfo DEFINED in MAP-MS-DataTypes : 1750 SubscriberInfo..........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1754 USED in MAP-MS-DataTypes : 100 1750 1834 USED in MAP-CH-DataTypes : 40 153 subscriberInfo..........................identifier of SubscriberInfo DEFINED in MAP-MS-DataTypes : 1834 subscriberInfo..........................identifier of [7] SubscriberInfo DEFINED in MAP-CH-DataTypes : 153 subscriberLocationReport................value reference SubscriberLocationReport, CHOICE VALUE DEFINED in MAP-Protocol : 322 SubscriberLocationReport................type reference OPERATION DEFINED in MAP-LocationServiceOpe : 84 USED in MAP-Protocol : 110 322 USED in MAP-LocationServiceOpe : 15 subscriberLocationReport-Arg............identifier of SubscriberLocationReport-Arg DEFINED in MAP-LocationServiceOpe : 86 SubscriberLocationReport-Arg............type reference SEQUENCE DEFINED in MAP-LCS-DataTypes : 315 USED in MAP-LocationServiceOpe : 45 86 USED in MAP-LCS-DataTypes : 15 subscriberLocationReport-Res............identifier of SubscriberLocationReport-Res DEFINED in MAP-LocationServiceOpe : 88 SubscriberLocationReport-Res............type reference SEQUENCE DEFINED in MAP-LCS-DataTypes : 383 USED in MAP-LocationServiceOpe : 46 88 USED in MAP-LCS-DataTypes : 16 subscriberNotMemberOfCUG................identifier of Named Number, 1 DEFINED in MAP-ER-DataTypes : 126 subscriberNotSC-Subscriber..............identifier of Named Number, 6 DEFINED in MAP-ER-DataTypes : 149 subscriberState.........................identifier of [1] SubscriberState DEFINED in MAP-MS-DataTypes : 1756 subscriberState.........................identifier of [1] NULL DEFINED in MAP-MS-DataTypes : 1762 SubscriberState.........................type reference CHOICE DEFINED in MAP-MS-DataTypes : 1812 USED in MAP-MS-DataTypes : 102 1756 subscriberStatus........................identifier of [3] SubscriberStatus DEFINED in MAP-MS-DataTypes : 931 SubscriberStatus........................type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 950 USED in MAP-MS-DataTypes : 62 931
3032
3GPP
3033 Release 4
15993 15994 15995 15996 15997 15998 15999
1131
3GPP TS 29.002 V4.17.0 (2006-06)
subscriptionWithdraw....................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 273 subsequentHandoverFailure...............value reference SubsequentHandoverFailure, CHOICE VALUE DEFINED in MAP-Protocol : 363
3034
3GPP
3035 Release 4
16000 16001 16002 16003 16004 16005 16006 16007 16008 16009 16010 16011 16012 16013 16014 16015 16016 16017 16018 16019 16020 16021 16022 16023 16024 16025 16026 16027 16028 16029 16030 16031 16032 16033 16034 16035 16036 16037 16038 16039 16040 16041 16042 16043 16044 16045 16046 16047 16048 16049 16050 16051 16052 16053 16054 16055 16056 16057 16058 16059 16060 16061 16062 16063 16064 16065 16066 16067 16068 16069 16070 16071 16072 16073 16074 16075 16076
1132
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 100
SubsequentHandoverFailure...............type reference ERROR DEFINED in MAP-Errors : 257 USED in MAP-Protocol : 132 363 USED in MAP-MobileServiceOpera : 92 346 USED in MAP-Errors : 37 success.................................identifier of Named Number, 0 DEFINED in MAP-CH-DataTypes : 372 successfulTransfer......................identifier of Named Number, 2 DEFINED in MAP-SM-DataTypes : 170 SuperChargerInfo........................type reference CHOICE DEFINED in MAP-MS-DataTypes : 231 USED in MAP-MS-DataTypes : 227 429 superChargerSupportedInHLR..............identifier of [27] AgeIndicator DEFINED in MAP-MS-DataTypes : 749 superChargerSupportedInServingNetworkEntidentifier of [3] SuperChargerInfo DEFINED in MAP-MS-DataTypes : 227 superChargerSupportedInServingNetworkEntidentifier of [2] SuperChargerInfo DEFINED in MAP-MS-DataTypes : 429 supplementaryService....................identifier of Named Number, 3 DEFINED in MAP-MS-DataTypes : 394 supportedCamelPhases....................identifier of [0] SupportedCamelPhases DEFINED in MAP-MS-DataTypes : 222 supportedCamelPhases....................identifier of [4] SupportedCamelPhases DEFINED in MAP-MS-DataTypes : 431 supportedCamelPhases....................identifier of [6] SupportedCamelPhases DEFINED in MAP-MS-DataTypes : 1261 SupportedCamelPhases....................type reference BIT STRING DEFINED in MAP-MS-DataTypes : 1528 USED in MAP-MS-DataTypes : 74 222 431 1261 1854 1855 1993 USED in MAP-CH-DataTypes : 41 213 257 supportedCAMELPhases....................identifier of [5] SupportedCamelPhases DEFINED in MAP-MS-DataTypes : 1993 supportedCamelPhases....................identifier of SupportedCamelPhases DEFINED in MAP-CH-DataTypes : 257 supportedCamelPhasesInGMSC..............identifier of [15] SupportedCamelPhases DEFINED in MAP-CH-DataTypes : 213 supportedCCBS-Phase.....................identifier of [16] SupportedCCBS-Phase DEFINED in MAP-CH-DataTypes : 112 SupportedCCBS-Phase.....................type reference INTEGER DEFINED in MAP-CH-DataTypes : 134 USED in MAP-CH-DataTypes : 112 supportedGADShapes......................identifier of [9] SupportedGADShapes DEFINED in MAP-LCS-DataTypes : 101 SupportedGADShapes......................type reference BIT STRING DEFINED in MAP-LCS-DataTypes : 202 USED in MAP-LCS-DataTypes : 23 101 supportedLCS-CapabilitySets.............identifier of [5] SupportedLCS-CapabilitySets DEFINED in MAP-MS-DataTypes : 229 SupportedLCS-CapabilitySets.............type reference BIT STRING DEFINED in MAP-MS-DataTypes : 246 USED in MAP-MS-DataTypes : 27 229 432 supportedLCS-CapabilitySets.............identifier of [5] SupportedLCS-CapabilitySets DEFINED in MAP-MS-DataTypes : 432
3036
3GPP
3037 Release 4
16077 16078 16079 16080 16081 16082 16083
1133
3GPP TS 29.002 V4.17.0 (2006-06)
supportedSGSN-CAMEL-Phases..............identifier of [6] SupportedCamelPhases DEFINED in MAP-MS-DataTypes : 1855 supportedSGSN-CAMEL-Phases..............identifier of [5] NULL DEFINED in MAP-MS-DataTypes : 1864 supportedVLR-CAMEL-Phases...............identifier of [5] SupportedCamelPhases
3038
3GPP
3039 Release 4
16084 16085 16086 16087 16088 16089 16090 16091 16092 16093 16094 16095 16096 16097 16098 16099 16100 16101 16102 16103 16104 16105 16106 16107 16108 16109 16110 16111 16112 16113 16114 16115 16116 16117 16118 16119 16120 16121 16122 16123 16124 16125 16126 16127 16128 16129 16130 16131 16132 16133 16134 16135 16136 16137 16138 16139 16140 16141 16142 16143 16144 16145 16146 16147 16148 16149 16150 16151 16152 16153 16154 16155 16156 16157 16158 16159 16160
1134
Cross Reference Listing for MAP-Protocol : 1854
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 101
DEFINED in MAP-MS-DataTypes
supportedVLR-CAMEL-Phases...............identifier of [4] NULL DEFINED in MAP-MS-DataTypes : 1863 suppressionOfAnnouncement...............identifier of [12] SuppressionOfAnnouncement DEFINED in MAP-CH-DataTypes : 107 SuppressionOfAnnouncement...............type reference NULL DEFINED in MAP-CH-DataTypes : 119 USED in MAP-CH-DataTypes : 21 107 205 suppressionOfAnnouncement...............identifier of [7] SuppressionOfAnnouncement DEFINED in MAP-CH-DataTypes : 205 suppress-T-CSI..........................identifier of NULL DEFINED in MAP-CH-DataTypes : 258 suspended...............................identifier of Named Number, 4 DEFINED in MAP-SS-DataTypes : 290 systemFailure...........................value reference SystemFailure, CHOICE VALUE DEFINED in MAP-Protocol : 331 SystemFailure...........................type reference ERROR DEFINED in MAP-Errors : 165 USED in MAP-Protocol : 117 331 USED in MAP-MobileServiceOpera : 82 182 226 250 316 362 374 386 428 442 457 471 USED in MAP-OperationAndMainte : 23 57 71 USED in MAP-CallHandlingOperat : 30 87 110 139 151 160 175 189 202 215 USED in MAP-SupplementaryServi : 33 94 111 128 148 166 181 194 208 223 257 274 USED in MAP-ShortMessageServic : 27 72 88 100 128 USED in MAP-Group-Call-Operati : 24 52 USED in MAP-LocationServiceOpe : 23 58 72 90 USED in MAP-Errors : 14 systemFailureParam......................identifier of SystemFailureParam DEFINED in MAP-Errors : 167 SystemFailureParam......................type reference CHOICE DEFINED in MAP-ER-DataTypes : 171 USED in MAP-Errors : 110 167 USED in MAP-ER-DataTypes : 20 targetCellId............................identifier of [0] GlobalCellId DEFINED in MAP-MS-DataTypes : 501 targetCellId............................identifier of [0] GlobalCellId DEFINED in MAP-MS-DataTypes : 602 targetCellOutsideGCA-Param..............identifier of TargetCellOutsideGCA-Param DEFINED in MAP-Errors : 261 TargetCellOutsideGCA-Param..............type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 387 USED in MAP-Errors : 152 261 USED in MAP-ER-DataTypes : 60 targetCellOutsideGroupCallArea.....value reference TargetCellOutsideGroupCallArea, CHOICE VALUE DEFINED in MAP-Protocol : 365 TargetCellOutsideGroupCallArea..........type reference ERROR DEFINED in MAP-Errors : 259 USED in MAP-Protocol : 171 365 USED in MAP-MobileServiceOpera : 106 320 USED in MAP-Errors : 38 targetMS................................identifier of [1] SubscriberIdentity DEFINED in MAP-LCS-DataTypes : 67 targetMS................................identifier of [0] SubscriberIdentity DEFINED in MAP-LCS-DataTypes : 72
3040
3GPP
3041 Release 4
16161 16162 16163 16164 16165 16166 16167
1135
3GPP TS 29.002 V4.17.0 (2006-06)
targetMSC-Number........................identifier of [1] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 603 targetMSsubscribedService...............identifier of Named Number, 4 DEFINED in MAP-CommonDataTypes : 388
3042
3GPP
3043 Release 4
16168 16169 16170 16171 16172 16173 16174 16175 16176 16177 16178 16179 16180 16181 16182 16183 16184 16185 16186 16187 16188 16189 16190 16191 16192 16193 16194 16195 16196 16197 16198 16199 16200 16201 16202 16203 16204 16205 16206 16207 16208 16209 16210 16211 16212 16213 16214 16215 16216 16217 16218 16219 16220 16221 16222 16223 16224 16225 16226 16227 16228 16229 16230 16231 16232 16233 16234 16235 16236 16237 16238 16239 16240 16241 16242 16243 16244
1136
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 102
targetRNCId.............................identifier of [1] RNCId DEFINED in MAP-MS-DataTypes : 503 targetRNCId.............................identifier of [2] RNCId DEFINED in MAP-MS-DataTypes : 604 TBCD-STRING.............................type reference OCTET STRING DEFINED in MAP-CommonDataTypes : 90 USED in MAP-MS-DataTypes : 186 1734 USED in MAP-CommonDataTypes : 27 297 310 320 tBusy...................................identifier of Named Number, 13 DEFINED in MAP-MS-DataTypes : 1639 TCAPMessages............................module reference DEFINED in TCAPMessages : 1 USED in MAP-MobileServiceOpera : 79 USED in MAP-OperationAndMainte : 20 USED in MAP-CallHandlingOperat : 27 USED in MAP-SupplementaryServi : 30 USED in MAP-ShortMessageServic : 24 USED in MAP-Group-Call-Operati : 21 USED in MAP-LocationServiceOpe : 20 USED in MAP-Errors : 99 telephony...............................value reference TeleserviceCode, '00010001'B DEFINED in MAP-TS-Code : 41 teleservice.............................identifier of [3] TeleserviceCode DEFINED in MAP-CommonDataTypes : 431 teleservice.............................identifier of Ext-TeleserviceCode DEFINED in MAP-GR-DataTypes : 50 TeleserviceCode.........................type reference OCTET STRING DEFINED in MAP-TS-Code : 11 USED in MAP-CommonDataTypes : 64 431 USED in MAP-TS-Code : 38 40 41 42 44 45 46 50 51 55 58 67 68 69 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 teleserviceList.........................identifier of [6] TeleserviceList DEFINED in MAP-MS-DataTypes : 935 TeleserviceList.........................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 959 USED in MAP-MS-DataTypes : 935 1256 teleserviceList.........................identifier of [1] TeleserviceList DEFINED in MAP-MS-DataTypes : 1256 teleserviceNotProvisioned...............value reference TeleserviceNotProvisioned, CHOICE VALUE DEFINED in MAP-Protocol : 355 TeleserviceNotProvisioned...............type reference ERROR DEFINED in MAP-Errors : 246 USED in MAP-Protocol : 130 355 USED in MAP-MobileServiceOpera : 98 269 286 USED in MAP-CallHandlingOperat : 38 95 USED in MAP-SupplementaryServi : 38 98 115 132 152 170 USED in MAP-ShortMessageServic : 35 77 USED in MAP-Errors : 33 teleservNotProvParam....................identifier of TeleservNotProvParam DEFINED in MAP-Errors : 248 TeleservNotProvParam....................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 234 USED in MAP-Errors : 121 248 USED in MAP-ER-DataTypes : 31 temporaryDefaultAllowed.................identifier of Named Number, 2 DEFINED in MAP-SS-DataTypes : 178
48
49
3044
3GPP
3045 Release 4
16245 16246 16247 16248 16249 16250 16251
1137
3GPP TS 29.002 V4.17.0 (2006-06)
temporaryDefaultRestricted..............identifier of Named Number, 1 DEFINED in MAP-SS-DataTypes : 177 termAttemptAuthorized...................identifier of Named Number, 12 DEFINED in MAP-MS-DataTypes : 1637 terminateAllCallActivities..............identifier of Named Number, 1
3046
3GPP
3047 Release 4
16252 16253 16254 16255 16256 16257 16258 16259 16260 16261 16262 16263 16264 16265 16266 16267 16268 16269 16270 16271 16272 16273 16274 16275 16276 16277 16278 16279 16280 16281 16282 16283 16284 16285 16286 16287 16288 16289 16290 16291 16292 16293 16294 16295 16296 16297 16298 16299 16300 16301 16302 16303 16304 16305 16306 16307 16308 16309 16310 16311 16312 16313 16314 16315 16316 16317 16318 16319 16320 16321 16322 16323 16324 16325 16326 16327 16328
1138
Cross Reference Listing for MAP-Protocol : 439
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 103
DEFINED in MAP-CH-DataTypes
terminateCallActivityReferred...........identifier of Named Number, 0 DEFINED in MAP-CH-DataTypes : 438 terminationCause........................identifier of [0] TerminationCause DEFINED in MAP-LCS-DataTypes : 350 TerminationCause........................type reference ENUMERATED DEFINED in MAP-LCS-DataTypes : 366 USED in MAP-LCS-DataTypes : 350 tif-csi.................................identifier of Named Number, 2 DEFINED in MAP-MS-DataTypes : 1295 tif-CSI.................................identifier of [3] NULL DEFINED in MAP-MS-DataTypes : 1336 tif-CSI.................................identifier of Named Number, 3 DEFINED in MAP-MS-DataTypes : 1872 tif-CSI.................................identifier of [7] NULL DEFINED in MAP-MS-DataTypes : 1909 tif-CSI-NotificationToCSE...............identifier of [8] NULL DEFINED in MAP-MS-DataTypes : 1910 tmsi....................................identifier of TMSI DEFINED in MAP-MS-DataTypes : 296 TMSI....................................type reference OCTET STRING DEFINED in MAP-CommonDataTypes : 314 USED in MAP-MS-DataTypes : 170 296 USED in MAP-CommonDataTypes : 31 318 tmsi....................................identifier of [1] TMSI DEFINED in MAP-CommonDataTypes : 318 tNoAnswer...............................identifier of Named Number, 14 DEFINED in MAP-MS-DataTypes : 1640 tooManyZoneCodes........................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 1267 traceReference..........................identifier of [1] TraceReference DEFINED in MAP-OM-DataTypes : 38 TraceReference..........................type reference OCTET STRING DEFINED in MAP-OM-DataTypes : 44 USED in MAP-OM-DataTypes : 38 56 traceReference..........................identifier of [1] TraceReference DEFINED in MAP-OM-DataTypes : 56 traceType...............................identifier of [2] TraceType DEFINED in MAP-OM-DataTypes : 39 TraceType...............................type reference INTEGER DEFINED in MAP-OM-DataTypes : 46 USED in MAP-OM-DataTypes : 39 tracingBufferFull.......................value reference TracingBufferFull, CHOICE VALUE DEFINED in MAP-Protocol : 372 TracingBufferFull.......................type reference ERROR DEFINED in MAP-Errors : 267 USED in MAP-Protocol : 133 372 USED in MAP-OperationAndMainte : 29 62 USED in MAP-Errors : 41 tracingBufferFullParam..................identifier of TracingBufferFullParam DEFINED in MAP-Errors : 269 TracingBufferFullParam..................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 238
3048
3GPP
3049 Release 4
16329 16330 16331 16332 16333 16334 16335
1139
122 269 : 32
3GPP TS 29.002 V4.17.0 (2006-06)
USED in MAP-Errors : USED in MAP-ER-DataTypes
TransactionID...........................type reference OCTET STRING DEFINED in TCAPMessages : 100 USED in TCAPMessages : 47 97 98
3050
3GPP
3051 Release 4
16336 16337 16338 16339 16340 16341 16342 16343 16344 16345 16346 16347 16348 16349 16350 16351 16352 16353 16354 16355 16356 16357 16358 16359 16360 16361 16362 16363 16364 16365 16366 16367 16368 16369 16370 16371 16372 16373 16374 16375 16376 16377 16378 16379 16380 16381 16382 16383 16384 16385 16386 16387 16388 16389 16390 16391 16392 16393 16394 16395 16396 16397 16398 16399 16400 16401 16402 16403 16404 16405 16406 16407 16408 16409 16410 16411 16412
1140
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 104
transferToThirdParty....................value reference SS-Code, '11000011'B DEFINED in MAP-SS-Code : 178 translatedB-Number......................identifier of [3] ISDN-AddressString DEFINED in MAP-CH-DataTypes : 389 translatedB-Number......................identifier of [1] ISDN-AddressString DEFINED in MAP-SS-DataTypes : 312 tripletList.............................identifier of [0] TripletList DEFINED in MAP-MS-DataTypes : 319 TripletList.............................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 322 USED in MAP-MS-DataTypes : 319 ts3G-25413..............................identifier of Named Number, 2 DEFINED in MAP-CommonDataTypes : 260 ts3G-48006..............................identifier of Named Number, 1 DEFINED in MAP-CommonDataTypes : 259 T-BcsmCamelTDPData......................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1628 USED in MAP-MS-DataTypes : 1621 t-BcsmCamelTDPDataList..................identifier of T-BcsmCamelTDPDataList DEFINED in MAP-MS-DataTypes : 1609 T-BcsmCamelTDPDataList..................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1620 USED in MAP-MS-DataTypes : 1609 t-BcsmTriggerDetectionPoint.............identifier of T-BcsmTriggerDetectionPoint DEFINED in MAP-MS-DataTypes : 1629 T-BcsmTriggerDetectionPoint.............type reference ENUMERATED DEFINED in MAP-MS-DataTypes : 1636 USED in MAP-MS-DataTypes : 85 1459 1629 T-BCSM-CAMEL-TDP-Criteria...............type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1458 USED in MAP-MS-DataTypes : 1447 t-BCSM-CAMEL-TDP-CriteriaList...........identifier of [8] T-BCSM-CAMEL-TDP-CriteriaList DEFINED in MAP-MS-DataTypes : 1340 T-BCSM-CAMEL-TDP-CriteriaList...........type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1446 USED in MAP-MS-DataTypes : 68 1340 1906 1908 USED in MAP-CH-DataTypes : 46 278 t-BCSM-CAMEL-TDP-CriteriaList...........identifier of [4] T-BCSM-CAMEL-TDP-CriteriaList DEFINED in MAP-MS-DataTypes : 1906 t-BCSM-CAMEL-TDP-CriteriaList...........identifier of [4] T-BCSM-CAMEL-TDP-CriteriaList DEFINED in MAP-CH-DataTypes : 278 t-BCSM-TriggerDetectionPoint............identifier of T-BcsmTriggerDetectionPoint DEFINED in MAP-MS-DataTypes : 1459 t-CauseValueCriteria....................identifier of [1] T-CauseValueCriteria DEFINED in MAP-MS-DataTypes : 1461 T-CauseValueCriteria....................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1502 USED in MAP-MS-DataTypes : 1461 t-csi...................................identifier of Named Number, 8 DEFINED in MAP-MS-DataTypes : 1301 T-CSI...................................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1608 USED in MAP-MS-DataTypes : 84 1339 1905 1907 USED in MAP-CH-DataTypes : 49 273
3052
3GPP
3053 Release 4
16413 16414 16415 16416 16417 16418 16419
1141
3GPP TS 29.002 V4.17.0 (2006-06)
t-CSI...................................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 1870 t-CSI...................................identifier of [3] T-CSI DEFINED in MAP-MS-DataTypes : 1905
3054
3GPP
3055 Release 4
16420 16421 16422 16423 16424 16425 16426 16427 16428 16429 16430 16431 16432 16433 16434 16435 16436 16437 16438 16439 16440 16441 16442 16443 16444 16445 16446 16447 16448 16449 16450 16451 16452 16453 16454 16455 16456 16457 16458 16459 16460 16461 16462 16463 16464 16465 16466 16467 16468 16469 16470 16471 16472 16473 16474 16475 16476 16477 16478 16479 16480 16481 16482 16483 16484 16485 16486 16487 16488 16489 16490 16491 16492 16493 16494 16495 16496
1142
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 105
t-CSI...................................identifier of [0] T-CSI DEFINED in MAP-CH-DataTypes : 273 udubFromBusyMS..........................identifier of Named Number, 5 DEFINED in MAP-CH-DataTypes : 406 udubFromFreeMS..........................identifier of Named Number, 4 DEFINED in MAP-CH-DataTypes : 405 umts-SecurityContextData................identifier of [1] UMTS-SecurityContextData DEFINED in MAP-MS-DataTypes : 344 UMTS-SecurityContextData................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 351 USED in MAP-MS-DataTypes : 344 unauthorisedMessageOriginator...........identifier of [1] NULL DEFINED in MAP-ER-DataTypes : 117 unauthorizedLCSClient...................value reference UnauthorizedLCSClient, CHOICE VALUE DEFINED in MAP-Protocol : 429 UnauthorizedLCSClient...................type reference ERROR DEFINED in MAP-Errors : 434 USED in MAP-Protocol : 164 429 USED in MAP-LocationServiceOpe : 30 81 USED in MAP-Errors : 87 unauthorizedLCSClient-Diagnostic........identifier of [0] UnauthorizedLCSClient-Diagnostic DEFINED in MAP-ER-DataTypes : 345 UnauthorizedLCSClient-Diagnostic........type reference ENUMERATED DEFINED in MAP-ER-DataTypes : 349 USED in MAP-ER-DataTypes : 345 unauthorizedLCSClient-Param.............identifier of UnauthorizedLCSClient-Param DEFINED in MAP-Errors : 436 UnauthorizedLCSClient-Param.............type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 344 USED in MAP-Errors : 142 436 USED in MAP-ER-DataTypes : 50 unauthorizedRequestingNetwork.......value reference UnauthorizedRequestingNetwork, CHOICE VALUE DEFINED in MAP-Protocol : 428 UnauthorizedRequestingNetwork...........type reference ERROR DEFINED in MAP-Errors : 429 USED in MAP-Protocol : 163 428 USED in MAP-LocationServiceOpe : 29 64 80 95 USED in MAP-Errors : 86 unauthorizedRequestingNetwork-Param.....identifier of UnauthorizedRequestingNetwork-Param DEFINED in MAP-Errors : 431 UnauthorizedRequestingNetwork-Param.....type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 340 USED in MAP-Errors : 141 431 USED in MAP-ER-DataTypes : 49 undetermined............................identifier of Named Number, 0 DEFINED in MAP-ER-DataTypes : 137 unexpectedDataParam.....................identifier of UnexpectedDataParam DEFINED in MAP-Errors : 178 UnexpectedDataParam.....................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 187 USED in MAP-Errors : 112 178 USED in MAP-ER-DataTypes : 22 unexpectedDataValue.....................value reference UnexpectedDataValue, CHOICE VALUE DEFINED in MAP-Protocol : 333 UnexpectedDataValue.....................type reference ERROR
3056
3GPP
3057 Release 4
16497 16498 16499 16500 16501 16502 16503
1143
3GPP TS 29.002 V4.17.0 (2006-06)
DEFINED in MAP-Errors : 176 USED in MAP-Protocol : 119 USED in MAP-MobileServiceOpera : 304 318 343 459 473 484 USED in MAP-OperationAndMainte : USED in MAP-CallHandlingOperat :
333 84 184 196 206 227 240 253 266 283 364 375 400 411 430 444 25 59 73 84 32 89 112 127 138 150 162 176 185
3058
3GPP
3059 Release 4
16504 16505 16506 16507 16508 16509 16510 16511 16512 16513 16514 16515 16516 16517 16518 16519 16520 16521 16522 16523 16524 16525 16526 16527 16528 16529 16530 16531 16532 16533 16534 16535 16536 16537 16538 16539 16540 16541 16542 16543 16544 16545 16546 16547 16548 16549 16550 16551 16552 16553 16554 16555 16556 16557 16558 16559 16560 16561 16562 16563 16564 16565 16566 16567 16568 16569 16570 16571 16572 16573 16574 16575 16576 16577 16578 16579 16580
1144
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 106
199 212 USED in MAP-SupplementaryServi : 225 248 259 USED in MAP-ShortMessageServic : USED in MAP-Group-Call-Operati : USED in MAP-LocationServiceOpe : USED in MAP-Errors : 16
35 96 113 130 150 168 183 196 210 276 29 74 89 102 119 130 144 25 54 25 60 74 93
unexpectedError.........................identifier of Named Number, 3 DEFINED in TCAPMessages : 199 unexpectedLinkedOperation...............identifier of Named Number, 7 DEFINED in TCAPMessages : 190 unidentifiedSubParam....................identifier of UnidentifiedSubParam DEFINED in MAP-Errors : 215 UnidentifiedSubParam....................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 218 USED in MAP-Errors : 116 215 USED in MAP-ER-DataTypes : 27 unidentifiedSubscriber..................value reference UnidentifiedSubscriber, CHOICE VALUE DEFINED in MAP-Protocol : 344 UnidentifiedSubscriber..................type reference ERROR DEFINED in MAP-Errors : 213 USED in MAP-Protocol : 124 344 USED in MAP-MobileServiceOpera : 87 216 401 412 USED in MAP-OperationAndMainte : 28 61 75 USED in MAP-CallHandlingOperat : 49 161 USED in MAP-ShortMessageServic : 32 104 USED in MAP-LocationServiceOpe : 34 76 USED in MAP-Errors : 25 unidirectional..........................identifier of [APPLICATION 1] IMPLICIT Unidirectional DEFINED in TCAPMessages : 52 Unidirectional..........................type reference SEQUENCE DEFINED in TCAPMessages : 58 USED in TCAPMessages : 52 universal...............................value reference SS-Code, '10110001'B DEFINED in MAP-SS-Code : 161 unknownAlphabet.........................value reference UnknownAlphabet, CHOICE VALUE DEFINED in MAP-Protocol : 409 UnknownAlphabet.........................type reference ERROR DEFINED in MAP-Errors : 376 USED in MAP-Protocol : 149 409 USED in MAP-SupplementaryServi : 48 184 200 214 USED in MAP-Errors : 68 unknownEquipment........................value reference UnknownEquipment, CHOICE VALUE DEFINED in MAP-Protocol : 345 UnknownEquipment........................type reference ERROR DEFINED in MAP-Errors : 219 USED in MAP-Protocol : 125 345 USED in MAP-MobileServiceOpera : 88 388 USED in MAP-Errors : 26 unknownMSC..............................value reference UnknownMSC, CHOICE VALUE DEFINED in MAP-Protocol : 343 UnknownMSC..............................type reference ERROR DEFINED in MAP-Errors : 211 USED in MAP-Protocol : 123 343 USED in MAP-MobileServiceOpera : 86 345 USED in MAP-Errors : 24 unknownOrUnreachableLCSClient.......value reference UnknownOrUnreachableLCSClient, CHOICE VALUE DEFINED in MAP-Protocol : 431
3060
3GPP
3061 Release 4
16581 16582 16583 16584 16585 16586 16587
1145
3GPP TS 29.002 V4.17.0 (2006-06)
UnknownOrUnreachableLCSClient...........type reference ERROR DEFINED in MAP-Errors : 444 USED in MAP-Protocol : 166 431 USED in MAP-LocationServiceOpe : 33 96 USED in MAP-Errors : 89 unknownOrUnreachableLCSClient-Param.....identifier of UnknownOrUnreachableLCSClient-Param
3062
3GPP
3063 Release 4
16588 16589 16590 16591 16592 16593 16594 16595 16596 16597 16598 16599 16600 16601 16602 16603 16604 16605 16606 16607 16608 16609 16610 16611 16612 16613 16614 16615 16616 16617 16618 16619 16620 16621 16622 16623 16624 16625 16626 16627 16628 16629 16630 16631 16632 16633 16634 16635 16636 16637 16638 16639 16640 16641 16642 16643 16644 16645 16646 16647 16648 16649 16650 16651 16652 16653 16654 16655 16656 16657 16658 16659 16660 16661 16662 16663 16664
1146
Cross Reference Listing for MAP-Protocol : 446
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 107
DEFINED in MAP-Errors
UnknownOrUnreachableLCSClient-Param.....type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 378 USED in MAP-Errors : 144 446 USED in MAP-ER-DataTypes : 52 unknownServiceCentre....................identifier of Named Number, 3 DEFINED in MAP-ER-DataTypes : 146 unknownSubscriber.......................value reference UnknownSubscriber, CHOICE VALUE DEFINED in MAP-Protocol : 341 UnknownSubscriber.......................type reference ERROR DEFINED in MAP-Errors : 200 USED in MAP-Protocol : 121 341 USED in MAP-MobileServiceOpera : 85 185 207 228 254 267 284 305 365 376 431 445 460 474 485 USED in MAP-OperationAndMainte : 27 85 USED in MAP-CallHandlingOperat : 35 92 174 201 214 USED in MAP-SupplementaryServi : 36 249 USED in MAP-ShortMessageServic : 31 76 120 146 USED in MAP-LocationServiceOpe : 27 62 94 USED in MAP-Errors : 22 unknownSubscriberDiagnostic.............identifier of UnknownSubscriberDiagnostic DEFINED in MAP-ER-DataTypes : 203 UnknownSubscriberDiagnostic.............type reference ENUMERATED DEFINED in MAP-ER-DataTypes : 205 USED in MAP-ER-DataTypes : 203 unknownSubscriberParam..................identifier of UnknownSubscriberParam DEFINED in MAP-Errors : 202 UnknownSubscriberParam..................type reference SEQUENCE DEFINED in MAP-ER-DataTypes : 200 USED in MAP-Errors : 114 202 USED in MAP-ER-DataTypes : 25 unrecognizedComponent...................identifier of Named Number, 0 DEFINED in TCAPMessages : 179 unrecognizedError.......................identifier of Named Number, 2 DEFINED in TCAPMessages : 198 unrecognizedInvokeID....................identifier of Named Number, 0 DEFINED in TCAPMessages : 192 unrecognizedInvokeID....................identifier of Named Number, 0 DEFINED in TCAPMessages : 196 unrecognizedLinkedID....................identifier of Named Number, 5 DEFINED in TCAPMessages : 188 unrecognizedMessageType.................identifier of Named Number, 0 DEFINED in TCAPMessages : 103 unrecognizedOperation...................identifier of Named Number, 1 DEFINED in TCAPMessages : 184 unrecognizedTransactionID...............identifier of Named Number, 1 DEFINED in TCAPMessages : 104 unstructuredSS-Notify...................value reference UnstructuredSS-Notify, CHOICE VALUE DEFINED in MAP-Protocol : 255 UnstructuredSS-Notify...................type reference OPERATION DEFINED in MAP-SupplementaryServi : 203 USED in MAP-Protocol : 76 255 USED in MAP-SupplementaryServi : 20 unstructuredSS-Request..................value reference UnstructuredSS-Request, CHOICE VALUE DEFINED in MAP-Protocol : 254
3064
3GPP
3065 Release 4
16665 16666 16667 16668 16669 16670 16671
1147
3GPP TS 29.002 V4.17.0 (2006-06)
UnstructuredSS-Request..................type reference OPERATION DEFINED in MAP-SupplementaryServi : 187 USED in MAP-Protocol : 75 254 USED in MAP-SupplementaryServi : 19 updateGprsLocation......................value reference UpdateGprsLocation, CHOICE VALUE DEFINED in MAP-Protocol : 304
3066
3GPP
3067 Release 4
16672 16673 16674 16675 16676 16677 16678 16679 16680 16681 16682 16683 16684 16685 16686 16687 16688 16689 16690 16691 16692 16693 16694 16695 16696 16697 16698 16699 16700 16701 16702 16703 16704 16705 16706 16707 16708 16709 16710 16711 16712 16713 16714 16715 16716 16717 16718 16719 16720 16721 16722 16723 16724 16725 16726 16727 16728 16729 16730 16731 16732 16733 16734 16735 16736 16737 16738 16739 16740 16741 16742 16743 16744 16745 16746 16747 16748
1148
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 108
UpdateGprsLocation......................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 220 USED in MAP-Protocol : 16 304 USED in MAP-MobileServiceOpera : 21 updateGprsLocationArg...................identifier of UpdateGprsLocationArg DEFINED in MAP-MobileServiceOpera : 222 UpdateGprsLocationArg...................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 416 USED in MAP-MobileServiceOpera : 121 222 USED in MAP-MS-DataTypes : 24 updateGprsLocationRes...................identifier of UpdateGprsLocationRes DEFINED in MAP-MobileServiceOpera : 224 UpdateGprsLocationRes...................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 437 USED in MAP-MobileServiceOpera : 122 224 USED in MAP-MS-DataTypes : 25 updateLocation..........................value reference UpdateLocation, CHOICE VALUE DEFINED in MAP-Protocol : 183 UpdateLocation..........................type reference OPERATION DEFINED in MAP-MobileServiceOpera : 176 USED in MAP-Protocol : 12 183 USED in MAP-MobileServiceOpera : 15 updateLocationArg.......................identifier of UpdateLocationArg DEFINED in MAP-MobileServiceOpera : 178 UpdateLocationArg.......................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 210 USED in MAP-MobileServiceOpera : 113 178 USED in MAP-MS-DataTypes : 16 updateLocationRes.......................identifier of UpdateLocationRes DEFINED in MAP-MobileServiceOpera : 180 UpdateLocationRes.......................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 258 USED in MAP-MobileServiceOpera : 114 180 USED in MAP-MS-DataTypes : 17 updateProcedure.........................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 272 uplinkAttached..........................identifier of [6] NULL DEFINED in MAP-GR-DataTypes : 120 uplinkFree..............................identifier of [3] NULL DEFINED in MAP-GR-DataTypes : 57 uplinkRejectCommand.....................identifier of [2] NULL DEFINED in MAP-GR-DataTypes : 79 uplinkReleaseCommand....................identifier of [4] NULL DEFINED in MAP-GR-DataTypes : 81 uplinkReleaseIndication.................identifier of [1] NULL DEFINED in MAP-GR-DataTypes : 78 uplinkReleaseIndication.................identifier of [1] NULL DEFINED in MAP-GR-DataTypes : 88 uplinkRequest...........................identifier of [0] NULL DEFINED in MAP-GR-DataTypes : 87 uplinkRequestAck........................identifier of [0] NULL DEFINED in MAP-GR-DataTypes : 77 uplinkSeizedCommand.....................identifier of [3] NULL DEFINED in MAP-GR-DataTypes : 80
3068
3GPP
3069 Release 4
16749 16750 16751 16752 16753 16754 16755
1149
3GPP TS 29.002 V4.17.0 (2006-06)
ussd-Arg................................identifier of USSD-Arg DEFINED in MAP-SupplementaryServi : 177 ussd-Arg................................identifier of USSD-Arg DEFINED in MAP-SupplementaryServi : 189
3070
3GPP
3071 Release 4
16756 16757 16758 16759 16760 16761 16762 16763 16764 16765 16766 16767 16768 16769 16770 16771 16772 16773 16774 16775 16776 16777 16778 16779 16780 16781 16782 16783 16784 16785 16786 16787 16788 16789 16790 16791 16792 16793 16794 16795 16796 16797 16798 16799 16800 16801 16802 16803 16804 16805 16806 16807 16808 16809 16810 16811 16812 16813 16814 16815 16816 16817 16818 16819 16820 16821 16822 16823 16824 16825 16826 16827 16828 16829 16830 16831 16832
1150
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 109
ussd-Arg................................identifier of USSD-Arg DEFINED in MAP-SupplementaryServi : 205 USSD-Arg................................type reference SEQUENCE DEFINED in MAP-SS-DataTypes : 221 USED in MAP-SupplementaryServi : 64 177 189 205 USED in MAP-SS-DataTypes : 20 ussd-Busy...............................value reference USSD-Busy, CHOICE VALUE DEFINED in MAP-Protocol : 410 USSD-Busy...............................type reference ERROR DEFINED in MAP-Errors : 378 USED in MAP-Protocol : 150 410 USED in MAP-SupplementaryServi : 49 201 215 USED in MAP-Errors : 69 ussd-DataCodingScheme...................identifier of USSD-DataCodingScheme DEFINED in MAP-SS-DataTypes : 222 ussd-DataCodingScheme...................identifier of USSD-DataCodingScheme DEFINED in MAP-SS-DataTypes : 229 USSD-DataCodingScheme...................type reference OCTET STRING DEFINED in MAP-SS-DataTypes : 233 USED in MAP-SS-DataTypes : 22 222 229 USED in MAP-LCS-DataTypes : 47 153 ussd-Res................................identifier of USSD-Res DEFINED in MAP-SupplementaryServi : 179 ussd-Res................................identifier of USSD-Res DEFINED in MAP-SupplementaryServi : 191 USSD-Res................................type reference SEQUENCE DEFINED in MAP-SS-DataTypes : 228 USED in MAP-SupplementaryServi : 65 179 191 USED in MAP-SS-DataTypes : 21 ussd-String.............................identifier of USSD-String DEFINED in MAP-SS-DataTypes : 223 ussd-String.............................identifier of USSD-String DEFINED in MAP-SS-DataTypes : 230 USSD-String.............................type reference OCTET STRING DEFINED in MAP-SS-DataTypes : 238 USED in MAP-SS-DataTypes : 23 223 230 USED in MAP-LCS-DataTypes : 48 162 uui.....................................identifier of [1] UUI DEFINED in MAP-CH-DataTypes : 241 UUI.....................................type reference OCTET STRING DEFINED in MAP-CH-DataTypes : 249 USED in MAP-CH-DataTypes : 241 uuIndicator.............................identifier of [0] UUIndicator DEFINED in MAP-CH-DataTypes : 240 UUIndicator.............................type reference OCTET STRING DEFINED in MAP-CH-DataTypes : 246 USED in MAP-CH-DataTypes : 240 uus1....................................value reference SS-Code, '10000001'B DEFINED in MAP-SS-Code : 110 uus2....................................value reference SS-Code, '10000010'B DEFINED in MAP-SS-Code : 112 uus3....................................value reference SS-Code, '10000011'B DEFINED in MAP-SS-Code : 114 uusCFInteraction........................identifier of [2] NULL DEFINED in MAP-CH-DataTypes : 242
3072
3GPP
3073 Release 4
16833 16834 16835 16836 16837 16838 16839
1151
3GPP TS 29.002 V4.17.0 (2006-06)
uu-Data.................................identifier of [10] UU-Data DEFINED in MAP-CH-DataTypes : 234 UU-Data.................................type reference SEQUENCE DEFINED in MAP-CH-DataTypes : 239 USED in MAP-CH-DataTypes : 234
3074
3GPP
3075 Release 4
16840 16841 16842 16843 16844 16845 16846 16847 16848 16849 16850 16851 16852 16853 16854 16855 16856 16857 16858 16859 16860 16861 16862 16863 16864 16865 16866 16867 16868 16869 16870 16871 16872 16873 16874 16875 16876 16877 16878 16879 16880 16881 16882 16883 16884 16885 16886 16887 16888 16889 16890 16891 16892 16893 16894 16895 16896 16897 16898 16899 16900 16901 16902 16903 16904 16905 16906 16907 16908 16909 16910 16911 16912 16913 16914 16915 16916
1152
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 110
valueAddedServices......................identifier of Named Number, 1 DEFINED in MAP-LCS-DataTypes : 143 VBSDataList.............................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1713 USED in MAP-MS-DataTypes : 942 vbsGroupIndication......................identifier of [7] NULL DEFINED in MAP-MS-DataTypes : 1279 vbsSubscriptionData.....................identifier of [11] VBSDataList DEFINED in MAP-MS-DataTypes : 942 verticalCoordinateRequest...............identifier of [1] NULL DEFINED in MAP-LCS-DataTypes : 173 vertical-accuracy.......................identifier of [2] Vertical-Accuracy DEFINED in MAP-LCS-DataTypes : 174 Vertical-Accuracy.......................type reference OCTET STRING DEFINED in MAP-LCS-DataTypes : 184 USED in MAP-LCS-DataTypes : 174 VGCSDataList............................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1716 USED in MAP-MS-DataTypes : 943 vgcsGroupIndication.....................identifier of [8] NULL DEFINED in MAP-MS-DataTypes : 1280 vgcsSubscriptionData....................identifier of [12] VGCSDataList DEFINED in MAP-MS-DataTypes : 943 vlr.....................................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 717 vlr.....................................identifier of Named Number, 2 DEFINED in MAP-CommonDataTypes : 354 vlrCamelSubscriptionInfo................identifier of [13] VlrCamelSubscriptionInfo DEFINED in MAP-MS-DataTypes : 944 VlrCamelSubscriptionInfo................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1330 USED in MAP-MS-DataTypes : 944 vlr-Capability..........................identifier of [6] VLR-Capability DEFINED in MAP-MS-DataTypes : 218 VLR-Capability..........................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 221 USED in MAP-MS-DataTypes : 218 1703 vlr-Capability..........................identifier of [6] VLR-Capability DEFINED in MAP-MS-DataTypes : 1703 vlr-Number..............................identifier of ISDN-AddressString DEFINED in MAP-MS-DataTypes : 214 vlr-Number..............................identifier of [0] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 284 vlr-Number..............................identifier of [0] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 387 vlr-number..............................identifier of [1] ISDN-AddressString DEFINED in MAP-MS-DataTypes : 1772 vmsc....................................identifier of Named Number, 5 DEFINED in MAP-CommonDataTypes : 357 vmsc-Address............................identifier of [2] ISDN-AddressString DEFINED in MAP-CH-DataTypes : 157
3076
3GPP
3077 Release 4
16917 16918 16919 16920 16921 16922 16923
1153
3GPP TS 29.002 V4.17.0 (2006-06)
voiceBroadcastCall......................value reference TeleserviceCode, '10010010'B DEFINED in MAP-TS-Code : 69 VoiceBroadcastData......................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1728 USED in MAP-MS-DataTypes : 1714
3078
3GPP
3079 Release 4
16924 16925 16926 16927 16928 16929 16930 16931 16932 16933 16934 16935 16936 16937 16938 16939 16940 16941 16942 16943 16944 16945 16946 16947 16948 16949 16950 16951 16952 16953 16954 16955 16956 16957 16958 16959 16960 16961 16962 16963 16964 16965 16966 16967 16968 16969 16970 16971 16972 16973 16974 16975 16976 16977 16978 16979 16980 16981 16982 16983 16984 16985 16986 16987 16988 16989 16990
1154
Cross Reference Listing for MAP-Protocol
3GPP TS 29.002 V4.17.0 (2006-06)
TAG R6.0
2006-06-08 12:10:15 PAGE 111
voiceGroupCall..........................value reference TeleserviceCode, '10010001'B DEFINED in MAP-TS-Code : 68 VoiceGroupCallData......................type reference SEQUENCE DEFINED in MAP-MS-DataTypes : 1723 USED in MAP-MS-DataTypes : 1717 vplmnAddressAllowed.....................identifier of [19] NULL DEFINED in MAP-MS-DataTypes : 795 vt-BCSM-CAMEL-TDP-CriteriaList..........identifier of [6] T-BCSM-CAMEL-TDP-CriteriaList DEFINED in MAP-MS-DataTypes : 1908 vt-csi..................................identifier of Named Number, 4 DEFINED in MAP-MS-DataTypes : 1297 vt-CSI..................................identifier of [7] T-CSI DEFINED in MAP-MS-DataTypes : 1339 vt-CSI..................................identifier of Named Number, 2 DEFINED in MAP-MS-DataTypes : 1871 vt-CSI..................................identifier of [5] T-CSI DEFINED in MAP-MS-DataTypes : 1907 whiteListed.............................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 727 wrongNetworkSignature...................identifier of Named Number, 1 DEFINED in MAP-MS-DataTypes : 412 wrongPasswordAttemptsCounter............identifier of WrongPasswordAttemptsCounter DEFINED in MAP-MS-DataTypes : 1888 WrongPasswordAttemptsCounter............type reference INTEGER DEFINED in MAP-MS-DataTypes : 1893 USED in MAP-MS-DataTypes : 1888 1951 2017 wrongPasswordAttemptsCounter............identifier of [4] WrongPasswordAttemptsCounter DEFINED in MAP-MS-DataTypes : 1951 wrongPasswordAttemptsCounter............identifier of [3] WrongPasswordAttemptsCounter DEFINED in MAP-MS-DataTypes : 2017 wrongUserResponse.......................identifier of Named Number, 0 DEFINED in MAP-MS-DataTypes : 411 xres....................................identifier of XRES DEFINED in MAP-MS-DataTypes : 336 XRES....................................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 363 USED in MAP-MS-DataTypes : 336 ZoneCode................................type reference OCTET STRING DEFINED in MAP-MS-DataTypes : 1250 USED in MAP-MS-DataTypes : 1248 1278 ZoneCodeList............................type reference SEQUENCE OF DEFINED in MAP-MS-DataTypes : 1247 USED in MAP-MS-DataTypes : 63 941 zoneCodesConflict.......................identifier of Named Number, 2 DEFINED in MAP-MS-DataTypes : 1268
3080
3GPP
3081 Release 4
1155
3GPP TS 29.002 V4.17.0 (2006-06)
16991 16992 16993
Annex B (informative): Fully expanded ASN.1 sources for abstract syntaxes of MAP
16994 Annex B is not part of the standard, it is included for information purposes only. 16995 For every (Value)Assignment in the root ASN.1 module all the used defined types and defined values, which are 16996 defined within the ASN.1 module or imported from ASN.1 modules, are replaced by the constructs this type or value is 16997 composed of. 16998 The fully expanded ASN.1 root module is itself a correct and equivalent representation of the MAP-Protocol. 16999 It allows to see at all the parameters, including all nested ones for a specific operationcode or errorcode at once. 17000 Note that for those operations which use a result without parameters the keyword RESULT is not shown. Empty results 17001 are only defined in the ASN.1 description in clause 17.
17002 17003
17004 17005 17006 17007 17008 17009 17010 17011 17012 17013 17014 17015 17016 17017 17018 17019 17020 17021 17022 17023 17024 17025 17026 17027 17028 17029 17030 17031 17032 17033 17034 17035 17036 17037 17038 17039 17040 17041 17042 17043 17044 17045 17046 17047 17048 17049
B.1
Fully Expanded ASN.1 Source of MAPProtocol/TCAPMessages
-Expanded ASN1 Module 'MAP-Protocol' --SIEMENS ASN.1 Compiler R6.0 (Production_6.0) -Date: 2006-06-08 Time: 12:10:15 MAP-Protocol{ 0 identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) map-Protocol (4) version7 (7) } DEFINITIONS ::= BEGIN updateLocation OPERATION ARGUMENT updateLocationArg SEQUENCE { imsi OCTET STRING ( SIZE( 3 .. 8 ) ), msc-Number [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), vlr-Number OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), lmsi [10] IMPLICIT OCTET STRING ( SIZE( 4 ) ) OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , vlr-Capability [6] IMPLICIT SEQUENCE { supportedCamelPhases [0] IMPLICIT BIT STRING { phase1 (0 ), phase2 (1 ), phase3 (2 )} ( SIZE( 1 .. 16 ) ) OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { ,
3082
3GPP
3083 Release 4
17050 17051 17052 17053 17054 17055 17056 17057 17058 17059 17060 17061 17062 17063 17064 17065 17066 17067 17068 17069 17070 17071 17072 17073 17074 17075 17076 17077 17078 17079 17080 17081 17082 17083 17084 17085 17086 17087 17088 17089 17090 17091 17092 17093 17094 17095 17096 17097 17098 17099 17100 17101 17102 17103 17104 17105 17106 17107 17108 17109 17110 17111 17112 17113 17114 17115 17116 17117 17118 17119 17120 17121 17122 17123 17124 17125 17126
1156
3GPP TS 29.002 V4.17.0 (2006-06)
...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , solsaSupportIndicator [2] IMPLICIT NULL OPTIONAL, istSupportIndicator [1] IMPLICIT ENUMERATED { basicISTSupported ( 0 ), istCommandSupported ( 1 ), ... } OPTIONAL, superChargerSupportedInServingNetworkEntity [3] CHOICE { sendSubscriberData [0] IMPLICIT NULL, subscriberDataStored [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 6 ) )} OPTIONAL, longFTN-Supported [4] IMPLICIT NULL OPTIONAL, supportedLCS-CapabilitySets [5] IMPLICIT BIT STRING { lcsCapabilitySet1 (0 ), lcsCapabilitySet2 (1 )} ( SIZE( 2 .. 16 ) ) OPTIONAL} OPTIONAL, informPreviousNetworkEntity [11] IMPLICIT NULL OPTIONAL} RESULT updateLocationRes SEQUENCE { hlr-Number OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- unknownSubscriber -- localValue : 1, -- roamingNotAllowed -- localValue : 8} ::= localValue : 2 cancelLocation OPERATION ARGUMENT cancelLocationArg [3] IMPLICIT SEQUENCE { identity CHOICE { imsi OCTET STRING ( SIZE( 3 .. 8 ) ), imsi-WithLMSI SEQUENCE { imsi OCTET STRING ( SIZE( 3 .. 8 ) ), lmsi OCTET STRING ( SIZE( 4 ) ), ... }}, cancellationType ENUMERATED { updateProcedure ( 0 ), subscriptionWithdraw ( 1 ), ... } OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT cancelLocationRes SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( {
3084
3GPP
3085 Release 4
17127 17128 17129 17130 17131 17132 17133 17134 17135 17136 17137 17138 17139 17140 17141 17142 17143 17144 17145 17146 17147 17148 17149 17150 17151 17152 17153 17154 17155 17156 17157 17158 17159 17160 17161 17162 17163 17164 17165 17166 17167 17168 17169 17170 17171 17172 17173 17174 17175 17176 17177 17178 17179 17180 17181 17182 17183 17184 17185 17186 17187 17188 17189 17190 17191 17192 17193 17194 17195 17196 17197 17198 17199 17200 17201 17202 17203
1157
3GPP TS 29.002 V4.17.0 (2006-06)
, ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36} ::= localValue : 3 purgeMS OPERATION ARGUMENT purgeMS-Arg [3] IMPLICIT SEQUENCE { imsi OCTET STRING ( SIZE( 3 .. 8 ) ), vlr-Number [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, sgsn-Number [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT purgeMS-Res SEQUENCE { freezeTMSI [0] IMPLICIT NULL OPTIONAL, freezeP-TMSI [1] IMPLICIT NULL OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- unknownSubscriber -- localValue : 1} ::= localValue : 67 sendIdentification OPERATION ARGUMENT sendIdentificationArg SEQUENCE { tmsi OCTET STRING ( SIZE( 1 .. 4 ) ), numberOfRequestedVectors INTEGER ( 1 .. 5 ) OPTIONAL, segmentationProhibited NULL OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT sendIdentificationRes [3] IMPLICIT SEQUENCE { imsi OCTET STRING ( SIZE( 3 .. 8 ) ) OPTIONAL, authenticationSetList CHOICE { tripletList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF
3086
3GPP
3087 Release 4
17204 17205 17206 17207 17208 17209 17210 17211 17212 17213 17214 17215 17216 17217 17218 17219 17220 17221 17222 17223 17224 17225 17226 17227 17228 17229 17230 17231 17232 17233 17234 17235 17236 17237 17238 17239 17240 17241 17242 17243 17244 17245 17246 17247 17248 17249 17250 17251 17252 17253 17254 17255 17256 17257 17258 17259 17260 17261 17262 17263 17264 17265 17266 17267 17268 17269 17270 17271 17272 17273 17274 17275 17276 17277 17278 17279 17280
1158
3GPP TS 29.002 V4.17.0 (2006-06)
SEQUENCE { rand OCTET STRING ( SIZE( 16 ) ), sres OCTET STRING ( SIZE( 4 ) ), kc OCTET STRING ( SIZE( 8 ) ), ... }, quintupletList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF SEQUENCE { rand OCTET STRING ( SIZE( 16 ) ), xres OCTET STRING ( SIZE( 4 .. 16 ) ), ck OCTET STRING ( SIZE( 16 ) ), ik OCTET STRING ( SIZE( 16 ) ), autn OCTET STRING ( SIZE( 16 ) ), ... }} OPTIONAL, currentSecurityContext [2] CHOICE { gsm-SecurityContextData [0] IMPLICIT SEQUENCE { kc OCTET STRING ( SIZE( 8 ) ), cksn OCTET STRING ( SIZE( 1 ) ), ... }, umts-SecurityContextData [1] IMPLICIT SEQUENCE { ck OCTET STRING ( SIZE( 16 ) ), ik OCTET STRING ( SIZE( 16 ) ), ksi OCTET STRING ( SIZE( 1 ) ), ... }} OPTIONAL, extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- dataMissing -- localValue : 35, -- unidentifiedSubscriber -- localValue : 5} ::= localValue : 55 prepareHandover OPERATION ARGUMENT prepareHO-Arg [3] IMPLICIT SEQUENCE { targetCellId [0] IMPLICIT OCTET STRING ( SIZE( 5 .. 7 ) ) OPTIONAL, ho-NumberNotRequired NULL OPTIONAL, targetRNCId [1] IMPLICIT OCTET STRING ( SIZE( 7 ) ) OPTIONAL, an-APDU [2] IMPLICIT SEQUENCE { accessNetworkProtocolId ENUMERATED { ts3G-48006 ( 1 ), ts3G-25413 ( 2 ), ... }, signalInfo OCTET STRING ( SIZE( 1 .. 2560 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, multipleBearerRequested [3] IMPLICIT NULL OPTIONAL, imsi [4] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ) OPTIONAL, integrityProtectionInfo [5] IMPLICIT OCTET STRING ( SIZE( 18 .. 100 ) ) OPTIONAL, encryptionInfo [6] IMPLICIT OCTET STRING ( SIZE( 18 .. 100 ) ) OPTIONAL, radioResourceInformation [7] IMPLICIT OCTET STRING ( SIZE( 3 .. 13 ) ) OPTIONAL, allowedGSM-Algorithms [9] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, allowedUMTS-Algorithms [10] IMPLICIT SEQUENCE { integrityProtectionAlgorithms [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 9 ) ) OPTIONAL, encryptionAlgorithms [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 9 ) ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF
3088
3GPP
3089 Release 4
17281 17282 17283 17284 17285 17286 17287 17288 17289 17290 17291 17292 17293 17294 17295 17296 17297 17298 17299 17300 17301 17302 17303 17304 17305 17306 17307 17308 17309 17310 17311 17312 17313 17314 17315 17316 17317 17318 17319 17320 17321 17322 17323 17324 17325 17326 17327 17328 17329 17330 17331 17332 17333 17334 17335 17336 17337 17338 17339 17340 17341 17342 17343 17344 17345 17346 17347 17348 17349 17350 17351 17352 17353 17354 17355 17356 17357
1159
3GPP TS 29.002 V4.17.0 (2006-06)
SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, radioResourceList [11] IMPLICIT SEQUENCE ( SIZE( 1 .. 7 ) ) OF SEQUENCE { radioResourceInformation OCTET STRING ( SIZE( 3 .. 13 ) ), rab-Id INTEGER ( 1 .. 255 ), ... } OPTIONAL, extensionContainer [8] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , rab-Id [12] IMPLICIT INTEGER ( 1 .. 255 ) OPTIONAL, bssmap-ServiceHandover [13] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ranap-ServiceHandover [14] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, bssmap-ServiceHandoverList [15] IMPLICIT SEQUENCE ( SIZE( 1 .. 7 ) ) OF SEQUENCE { bssmap-ServiceHandover OCTET STRING ( SIZE( 1 ) ), rab-Id INTEGER ( 1 .. 255 ), ... } OPTIONAL, asciCallReference [20] IMPLICIT OCTET STRING ( SIZE( 1 .. 8 ) ) OPTIONAL} RESULT prepareHO-Res [3] IMPLICIT SEQUENCE { handoverNumber [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, relocationNumberList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 7 ) ) OF SEQUENCE { handoverNumber OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), rab-Id INTEGER ( 1 .. 255 ), ... } OPTIONAL, an-APDU [2] IMPLICIT SEQUENCE { accessNetworkProtocolId ENUMERATED { ts3G-48006 ( 1 ), ts3G-25413 ( 2 ), ... }, signalInfo OCTET STRING ( SIZE( 1 .. 2560 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, multicallBearerInfo [3] IMPLICIT INTEGER ( 1 .. 7 ) OPTIONAL, multipleBearerNotSupported NULL OPTIONAL, selectedUMTS-Algorithms [5] IMPLICIT SEQUENCE { integrityProtectionAlgorithm [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, encryptionAlgorithm [1] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( {
3090
3GPP
3091 Release 4
17358 17359 17360 17361 17362 17363 17364 17365 17366 17367 17368 17369 17370 17371 17372 17373 17374 17375 17376 17377 17378 17379 17380 17381 17382 17383 17384 17385 17386 17387 17388 17389 17390 17391 17392 17393 17394 17395 17396 17397 17398 17399 17400 17401 17402 17403 17404 17405 17406 17407 17408 17409 17410 17411 17412 17413 17414 17415 17416 17417 17418 17419 17420 17421 17422 17423 17424 17425 17426 17427 17428 17429 17430 17431 17432 17433 17434
1160
3GPP TS 29.002 V4.17.0 (2006-06)
, ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, chosenRadioResourceInformation [6] IMPLICIT SEQUENCE { chosenChannelInfo [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, chosenSpeechVersion [1] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ... } OPTIONAL, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- noHandoverNumberAvailable -- localValue : 25, -- targetCellOutsideGroupCallArea -- localValue : 42} ::= localValue : 68 sendEndSignal OPERATION ARGUMENT sendEndSignal-Arg [3] IMPLICIT SEQUENCE { an-APDU SEQUENCE { accessNetworkProtocolId ENUMERATED { ts3G-48006 ( 1 ), ts3G-25413 ( 2 ), ... }, signalInfo OCTET STRING ( SIZE( 1 .. 2560 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer [0] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT sendEndSignal-Res SEQUENCE { extensionContainer [0] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL,
3092
3GPP
3093 Release 4
17435 17436 17437 17438 17439 17440 17441 17442 17443 17444 17445 17446 17447 17448 17449 17450 17451 17452 17453 17454 17455 17456 17457 17458 17459 17460 17461 17462 17463 17464 17465 17466 17467 17468 17469 17470 17471 17472 17473 17474 17475 17476 17477 17478 17479 17480 17481 17482 17483 17484 17485 17486 17487 17488 17489 17490 17491 17492 17493 17494 17495 17496 17497 17498 17499 17500 17501 17502 17503 17504 17505 17506 17507 17508 17509 17510 17511
1161
[1] IMPLICIT SEQUENCE {
3GPP TS 29.002 V4.17.0 (2006-06)
pcs-Extensions ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 29
processAccessSignalling OPERATION ARGUMENT processAccessSignalling-Arg [3] IMPLICIT SEQUENCE { an-APDU SEQUENCE { accessNetworkProtocolId ENUMERATED { ts3G-48006 ( 1 ), ts3G-25413 ( 2 ), ... }, signalInfo OCTET STRING ( SIZE( 1 .. 2560 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, selectedUMTS-Algorithms [1] IMPLICIT SEQUENCE { integrityProtectionAlgorithm [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, encryptionAlgorithm [1] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, selectedGSM-Algorithm [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, chosenRadioResourceInformation [3] IMPLICIT SEQUENCE { chosenChannelInfo [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, chosenSpeechVersion [1] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ... } OPTIONAL, selectedRab-Id [4] IMPLICIT INTEGER ( 1 .. 255 ) OPTIONAL, extensionContainer [0] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 33 forwardAccessSignalling OPERATION ARGUMENT forwardAccessSignalling-Arg [3] IMPLICIT SEQUENCE { an-APDU SEQUENCE { accessNetworkProtocolId ENUMERATED { ts3G-48006 ( 1 ), ts3G-25413 ( 2 ), ... }, signalInfo OCTET STRING ( SIZE( 1 .. 2560 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE {
3094
3GPP
3095 Release 4
17512 17513 17514 17515 17516 17517 17518 17519 17520 17521 17522 17523 17524 17525 17526 17527 17528 17529 17530 17531 17532 17533 17534 17535 17536 17537 17538 17539 17540 17541 17542 17543 17544 17545 17546 17547 17548 17549 17550 17551 17552 17553 17554 17555 17556 17557 17558 17559 17560 17561 17562 17563 17564 17565 17566 17567 17568 17569 17570 17571 17572 17573 17574 17575 17576 17577 17578 17579 17580 17581 17582 17583 17584 17585 17586 17587 17588
1162
3GPP TS 29.002 V4.17.0 (2006-06)
extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, integrityProtectionInfo [0] IMPLICIT OCTET STRING ( SIZE( 18 .. 100 ) ) OPTIONAL, encryptionInfo [1] IMPLICIT OCTET STRING ( SIZE( 18 .. 100 ) ) OPTIONAL, keyStatus [2] IMPLICIT ENUMERATED { old ( 0 ), new ( 1 ), ... } OPTIONAL, allowedGSM-Algorithms [4] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, allowedUMTS-Algorithms [5] IMPLICIT SEQUENCE { integrityProtectionAlgorithms [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 9 ) ) OPTIONAL, encryptionAlgorithms [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 9 ) ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, radioResourceInformation [6] IMPLICIT OCTET STRING ( SIZE( 3 .. 13 ) ) OPTIONAL, extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , radioResourceList [7] IMPLICIT SEQUENCE ( SIZE( 1 .. 7 ) ) OF SEQUENCE { radioResourceInformation OCTET STRING ( SIZE( 3 .. 13 ) ), rab-Id INTEGER ( 1 .. 255 ), ... } OPTIONAL, bssmap-ServiceHandover [9] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ranap-ServiceHandover [8] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, bssmap-ServiceHandoverList [10] IMPLICIT SEQUENCE ( SIZE( 1 .. 7 ) ) OF SEQUENCE { bssmap-ServiceHandover OCTET STRING ( SIZE( 1 ) ), rab-Id INTEGER ( 1 .. 255 ), ... } OPTIONAL} ::= localValue : 34 prepareSubsequentHandover OPERATION ARGUMENT prepareSubsequentHO-Arg [3] IMPLICIT SEQUENCE { targetCellId [0] IMPLICIT OCTET STRING ( SIZE( 5 .. 7 ) ) OPTIONAL, targetMSC-Number [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), targetRNCId [2] IMPLICIT OCTET STRING ( SIZE( 7 ) ) OPTIONAL, an-APDU [3] IMPLICIT SEQUENCE { accessNetworkProtocolId ENUMERATED { ts3G-48006 ( 1 ), ts3G-25413 ( 2 ), ... }, signalInfo OCTET STRING ( SIZE( 1 .. 2560 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( {
3096
3GPP
3097 Release 4
17589 17590 17591 17592 17593 17594 17595 17596 17597 17598 17599 17600 17601 17602 17603 17604 17605 17606 17607 17608 17609 17610 17611 17612 17613 17614 17615 17616 17617 17618 17619 17620 17621 17622 17623 17624 17625 17626 17627 17628 17629 17630 17631 17632 17633 17634 17635 17636 17637 17638 17639 17640 17641 17642 17643 17644 17645 17646 17647 17648 17649 17650 17651 17652 17653 17654 17655 17656 17657 17658 17659 17660 17661 17662 17663 17664 17665
1163
3GPP TS 29.002 V4.17.0 (2006-06)
, ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, selectedRab-Id [4] IMPLICIT INTEGER ( 1 .. 255 ) OPTIONAL, extensionContainer [5] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT prepareSubsequentHO-Res [3] IMPLICIT SEQUENCE { an-APDU SEQUENCE { accessNetworkProtocolId ENUMERATED { ts3G-48006 ( 1 ), ts3G-25413 ( 2 ), ... }, signalInfo OCTET STRING ( SIZE( 1 .. 2560 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer [0] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- unexpectedDataValue -- localValue : 36, -- dataMissing -- localValue : 35, -- unknownMSC -- localValue : 3, -- subsequentHandoverFailure -- localValue : 26} ::= localValue : 69 sendAuthenticationInfo OPERATION ARGUMENT sendAuthenticationInfoArg SEQUENCE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), numberOfRequestedVectors INTEGER ( 1 .. 5 ), segmentationProhibited NULL OPTIONAL, immediateResponsePreferred [1] IMPLICIT NULL OPTIONAL, re-synchronisationInfo SEQUENCE { rand OCTET STRING ( SIZE( 16 ) ), auts OCTET STRING ( SIZE( 14 ) ), ... } OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF
3098
3GPP
3099 Release 4
17666 17667 17668 17669 17670 17671 17672 17673 17674 17675 17676 17677 17678 17679 17680 17681 17682 17683 17684 17685 17686 17687 17688 17689 17690 17691 17692 17693 17694 17695 17696 17697 17698 17699 17700 17701 17702 17703 17704 17705 17706 17707 17708 17709 17710 17711 17712 17713 17714 17715 17716 17717 17718 17719 17720 17721 17722 17723 17724 17725 17726 17727 17728 17729 17730 17731 17732 17733 17734 17735 17736 17737 17738 17739 17740 17741 17742
1164
3GPP TS 29.002 V4.17.0 (2006-06)
SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , requestingNodeType [3] IMPLICIT ENUMERATED { vlr ( 0 ), sgsn ( 1 ), ... } OPTIONAL} RESULT sendAuthenticationInfoRes [3] IMPLICIT SEQUENCE { authenticationSetList CHOICE { tripletList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF SEQUENCE { rand OCTET STRING ( SIZE( 16 ) ), sres OCTET STRING ( SIZE( 4 ) ), kc OCTET STRING ( SIZE( 8 ) ), ... }, quintupletList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF SEQUENCE { rand OCTET STRING ( SIZE( 16 ) ), xres OCTET STRING ( SIZE( 4 .. 16 ) ), ck OCTET STRING ( SIZE( 16 ) ), ik OCTET STRING ( SIZE( 16 ) ), autn OCTET STRING ( SIZE( 16 ) ), ... }} OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- unknownSubscriber -- localValue : 1} ::= localValue : 56 authenticationFailureReport OPERATION ARGUMENT authenticationFailureReportArg SEQUENCE { imsi OCTET STRING ( SIZE( 3 .. 8 ) ), failureCause ENUMERATED { wrongUserResponse ( 0 ), wrongNetworkSignature ( 1 ) }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , re-attempt BOOLEAN OPTIONAL, accessType ENUMERATED { call ( 0 ), emergencyCall ( 1 ), locationUpdating ( 2 ),
3100
3GPP
3101 Release 4
17743 17744 17745 17746 17747 17748 17749 17750 17751 17752 17753 17754 17755 17756 17757 17758 17759 17760 17761 17762 17763 17764 17765 17766 17767 17768 17769 17770 17771 17772 17773 17774 17775 17776 17777 17778 17779 17780 17781 17782 17783 17784 17785 17786 17787 17788 17789 17790 17791 17792 17793 17794 17795 17796 17797 17798 17799 17800 17801 17802 17803 17804 17805 17806 17807 17808 17809 17810 17811 17812 17813 17814 17815 17816 17817 17818 17819
1165
3GPP TS 29.002 V4.17.0 (2006-06)
supplementaryService ( 3 ), shortMessage ( 4 ), gprsAttach ( 5 ), routingAreaUpdating ( 6 ), serviceRequest ( 7 ), pdpContextActivation ( 8 ), pdpContextDeactivation ( 9 ), ... , gprsDetach ( 10 ) } OPTIONAL, rand OCTET STRING ( SIZE( 16 ) ) OPTIONAL, vlr-Number [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, sgsn-Number [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL} RESULT authenticationFailureReportRes SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- unexpectedDataValue -- localValue : 36, -- unknownSubscriber -- localValue : 1} ::= localValue : 15 checkIMEI OPERATION ARGUMENT imei OCTET STRING ( SIZE( 8 ) ) RESULT equipmentStatus ENUMERATED { whiteListed ( 0 ), blackListed ( 1 ), greyListed ( 2 ) } ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unknownEquipment -- localValue : 7} ::= localValue : 43 insertSubscriberData OPERATION ARGUMENT insertSubscriberDataArg SEQUENCE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ) OPTIONAL, msisdn [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, category [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, subscriberStatus [3] IMPLICIT ENUMERATED { serviceGranted ( 0 ), operatorDeterminedBarring ( 1 ) } OPTIONAL, bearerServiceList [4] IMPLICIT SEQUENCE ( SIZE( 1 .. 50 ) ) OF OCTET STRING ( SIZE( 1 .. 5 ) ) OPTIONAL, teleserviceList [6] IMPLICIT SEQUENCE ( SIZE( 1 .. 20 ) ) OF OCTET STRING ( SIZE( 1 .. 5 ) ) OPTIONAL, provisionedSS [7] IMPLICIT SEQUENCE ( SIZE( 1 .. 30 ) ) OF CHOICE { forwardingInfo [0] IMPLICIT SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ), forwardingFeatureList SEQUENCE ( SIZE( 1 .. 32 ) ) OF SEQUENCE { basicService CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), forwardedToNumber [5] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, forwardedToSubaddress [8] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, forwardingOptions [6] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ) OPTIONAL, noReplyConditionTime [7] IMPLICIT INTEGER ( 1 .. 100 ) OPTIONAL, extensionContainer [9] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE {
3102
3GPP
3103 Release 4
17820 17821 17822 17823 17824 17825 17826 17827 17828 17829 17830 17831 17832 17833 17834 17835 17836 17837 17838 17839 17840 17841 17842 17843 17844 17845 17846 17847 17848 17849 17850 17851 17852 17853 17854 17855 17856 17857 17858 17859 17860 17861 17862 17863 17864 17865 17866 17867 17868 17869 17870 17871 17872 17873 17874 17875 17876 17877 17878 17879 17880 17881 17882 17883 17884 17885 17886 17887 17888 17889 17890 17891 17892 17893 17894 17895 17896
1166
3GPP TS 29.002 V4.17.0 (2006-06)
extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , longForwardedToNumber [10] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 15 ) ) OPTIONAL}, extensionContainer [0] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, callBarringInfo [1] IMPLICIT SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ), callBarringFeatureList SEQUENCE ( SIZE( 1 .. 32 ) ) OF SEQUENCE { basicService CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, cug-Info [2] IMPLICIT SEQUENCE { cug-SubscriptionList SEQUENCE ( SIZE( 0 .. 10 ) ) OF SEQUENCE { cug-Index INTEGER ( 0 .. 32767 ), cug-Interlock OCTET STRING ( SIZE( 4 ) ), intraCUG-Options ENUMERATED { noCUG-Restrictions ( 0 ), cugIC-CallBarred ( 1 ), cugOG-CallBarred ( 2 ) }, basicServiceGroupList SEQUENCE ( SIZE( 1 .. 32 ) ) OF CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, extensionContainer [0] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) ,
3104
3GPP
3105 Release 4
17897 17898 17899 17900 17901 17902 17903 17904 17905 17906 17907 17908 17909 17910 17911 17912 17913 17914 17915 17916 17917 17918 17919 17920 17921 17922 17923 17924 17925 17926 17927 17928 17929 17930 17931 17932 17933 17934 17935 17936 17937 17938 17939 17940 17941 17942 17943 17944 17945 17946 17947 17948 17949 17950 17951 17952 17953 17954 17955 17956 17957 17958 17959 17960 17961 17962 17963 17964 17965 17966 17967 17968 17969 17970 17971 17972 17973
1167
3GPP TS 29.002 V4.17.0 (2006-06)
extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, cug-FeatureList SEQUENCE ( SIZE( 1 .. 32 ) ) OF SEQUENCE { basicService CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, preferentialCUG-Indicator INTEGER ( 0 .. 32767 ) OPTIONAL, interCUG-Restrictions OCTET STRING ( SIZE( 1 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, extensionContainer [0] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, ss-Data [3] IMPLICIT SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ), ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ss-SubscriptionOption CHOICE { cliRestrictionOption [2] IMPLICIT ENUMERATED { permanent ( 0 ), temporaryDefaultRestricted ( 1 ), temporaryDefaultAllowed ( 2 ) }, overrideCategory [1] IMPLICIT ENUMERATED { overrideEnabled ( 0 ), overrideDisabled ( 1 ) }} OPTIONAL, basicServiceGroupList SEQUENCE ( SIZE( 1 .. 32 ) ) OF CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, extensionContainer [5] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, emlpp-Info [4] IMPLICIT SEQUENCE { maximumentitledPriority INTEGER ( 0 .. 15 ), defaultPriority INTEGER ( 0 .. 15 ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) ,
3106
3GPP
3107 Release 4
17974 17975 17976 17977 17978 17979 17980 17981 17982 17983 17984 17985 17986 17987 17988 17989 17990 17991 17992 17993 17994 17995 17996 17997 17998 17999 18000 18001 18002 18003 18004 18005 18006 18007 18008 18009 18010 18011 18012 18013 18014 18015 18016 18017 18018 18019 18020 18021 18022 18023 18024 18025 18026 18027 18028 18029 18030 18031 18032 18033 18034 18035 18036 18037 18038 18039 18040 18041 18042 18043 18044 18045 18046 18047 18048 18049 18050
1168
3GPP TS 29.002 V4.17.0 (2006-06)
extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }} OPTIONAL, odb-Data [8] IMPLICIT SEQUENCE { 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 ) ), odb-HPLMN-Data BIT STRING { plmn-SpecificBarringType1 (0 ), plmn-SpecificBarringType2 (1 ), plmn-SpecificBarringType3 (2 ), plmn-SpecificBarringType4 (3 )} ( SIZE( 4 .. 32 ) ) OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, roamingRestrictionDueToUnsupportedFeature [9] IMPLICIT NULL OPTIONAL, regionalSubscriptionData [10] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF OCTET STRING ( SIZE( 2 ) ) OPTIONAL, vbsSubscriptionData [11] IMPLICIT SEQUENCE ( SIZE( 1 .. 50 ) ) OF SEQUENCE { groupid OCTET STRING ( SIZE( 3 ) ), broadcastInitEntitlement NULL OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, vgcsSubscriptionData [12] IMPLICIT SEQUENCE ( SIZE( 1 .. 50 ) ) OF
3108
3GPP
3109 Release 4
18051 18052 18053 18054 18055 18056 18057 18058 18059 18060 18061 18062 18063 18064 18065 18066 18067 18068 18069 18070 18071 18072 18073 18074 18075 18076 18077 18078 18079 18080 18081 18082 18083 18084 18085 18086 18087 18088 18089 18090 18091 18092 18093 18094 18095 18096 18097 18098 18099 18100 18101 18102 18103 18104 18105 18106 18107 18108 18109 18110 18111 18112 18113 18114 18115 18116 18117 18118 18119 18120 18121 18122 18123 18124 18125 18126 18127
1169
3GPP TS 29.002 V4.17.0 (2006-06)
SEQUENCE { groupId OCTET STRING ( SIZE( 3 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, vlrCamelSubscriptionInfo [13] IMPLICIT SEQUENCE { o-CSI [0] IMPLICIT SEQUENCE { o-BcsmCamelTDPDataList SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { o-BcsmTriggerDetectionPoint ENUMERATED { collectedInfo ( 2 ), ... , routeSelectFailure ( 4 ) }, serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling [1] IMPLICIT ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , camelCapabilityHandling [0] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, notificationToCSE [1] IMPLICIT NULL OPTIONAL, csiActive [2] IMPLICIT NULL OPTIONAL} OPTIONAL, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , ss-CSI [2] IMPLICIT SEQUENCE { ss-CamelData SEQUENCE { ss-EventList SEQUENCE ( SIZE( 1 .. 10 ) ) OF OCTET STRING ( SIZE( 1 ) ), gsmSCF-Address OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), extensionContainer [0] IMPLICIT SEQUENCE {
3110
3GPP
3111 Release 4
18128 18129 18130 18131 18132 18133 18134 18135 18136 18137 18138 18139 18140 18141 18142 18143 18144 18145 18146 18147 18148 18149 18150 18151 18152 18153 18154 18155 18156 18157 18158 18159 18160 18161 18162 18163 18164 18165 18166 18167 18168 18169 18170 18171 18172 18173 18174 18175 18176 18177 18178 18179 18180 18181 18182 18183 18184 18185 18186 18187 18188 18189 18190 18191 18192 18193 18194 18195 18196 18197 18198 18199 18200 18201 18202 18203 18204
1170
3GPP TS 29.002 V4.17.0 (2006-06)
privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , notificationToCSE [0] IMPLICIT NULL OPTIONAL, csi-Active [1] IMPLICIT NULL OPTIONAL} OPTIONAL, o-BcsmCamelTDP-CriteriaList [4] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { o-BcsmTriggerDetectionPoint ENUMERATED { collectedInfo ( 2 ), ... , routeSelectFailure ( 4 ) }, destinationNumberCriteria [0] IMPLICIT SEQUENCE { matchType [0] IMPLICIT ENUMERATED { inhibiting ( 0 ), enabling ( 1 ) }, destinationNumberList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, destinationNumberLengthList [2] IMPLICIT SEQUENCE ( SIZE( 1 .. 3 ) ) OF INTEGER ( 1 .. 15 ) OPTIONAL, ... } OPTIONAL, basicServiceCriteria [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, callTypeCriteria [2] IMPLICIT ENUMERATED { forwarded ( 0 ), notForwarded ( 1 ) } OPTIONAL, ... , o-CauseValueCriteria [3] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF OCTET STRING ( SIZE( 1 ) ) OPTIONAL, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL} OPTIONAL, tif-CSI [3] IMPLICIT NULL OPTIONAL, m-CSI [5] IMPLICIT SEQUENCE { mobilityTriggers SEQUENCE ( SIZE( 1 .. 10 ) ) OF OCTET STRING ( SIZE( 1 ) ), serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( {
3112
3GPP
3113 Release 4
18205 18206 18207 18208 18209 18210 18211 18212 18213 18214 18215 18216 18217 18218 18219 18220 18221 18222 18223 18224 18225 18226 18227 18228 18229 18230 18231 18232 18233 18234 18235 18236 18237 18238 18239 18240 18241 18242 18243 18244 18245 18246 18247 18248 18249 18250 18251 18252 18253 18254 18255 18256 18257 18258 18259 18260 18261 18262 18263 18264 18265 18266 18267 18268 18269 18270 18271 18272 18273 18274 18275 18276 18277 18278 18279 18280 18281
1171
3GPP TS 29.002 V4.17.0 (2006-06)
, ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [2] IMPLICIT NULL OPTIONAL, csi-Active [3] IMPLICIT NULL OPTIONAL, ... } OPTIONAL, sms-CSI [6] IMPLICIT SEQUENCE { sms-CAMEL-TDP-DataList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { sms-TriggerDetectionPoint [0] IMPLICIT ENUMERATED { sms-CollectedInfo ( 1 ), ... }, serviceKey [1] IMPLICIT INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultSMS-Handling [3] IMPLICIT ENUMERATED { continueTransaction ( 0 ), releaseTransaction ( 1 ), ... }, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camelCapabilityHandling [1] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [3] IMPLICIT NULL OPTIONAL, csi-Active [4] IMPLICIT NULL OPTIONAL, ... } OPTIONAL, vt-CSI [7] IMPLICIT SEQUENCE { t-BcsmCamelTDPDataList SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { t-BcsmTriggerDetectionPoint ENUMERATED { termAttemptAuthorized ( 12 ), ... , tBusy ( 13 ), tNoAnswer ( 14 ) }, serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling [1] IMPLICIT ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE {
3114
3GPP
3115 Release 4
18282 18283 18284 18285 18286 18287 18288 18289 18290 18291 18292 18293 18294 18295 18296 18297 18298 18299 18300 18301 18302 18303 18304 18305 18306 18307 18308 18309 18310 18311 18312 18313 18314 18315 18316 18317 18318 18319 18320 18321 18322 18323 18324 18325 18326 18327 18328 18329 18330 18331 18332 18333 18334 18335 18336 18337 18338 18339 18340 18341 18342 18343 18344 18345 18346 18347 18348 18349 18350 18351 18352 18353 18354 18355 18356 18357 18358
1172
3GPP TS 29.002 V4.17.0 (2006-06)
privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , camelCapabilityHandling [0] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, notificationToCSE [1] IMPLICIT NULL OPTIONAL, csi-Active [2] IMPLICIT NULL OPTIONAL} OPTIONAL, t-BCSM-CAMEL-TDP-CriteriaList [8] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { t-BCSM-TriggerDetectionPoint ENUMERATED { termAttemptAuthorized ( 12 ), ... , tBusy ( 13 ), tNoAnswer ( 14 ) }, basicServiceCriteria [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, t-CauseValueCriteria [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ... } OPTIONAL, d-CSI [9] IMPLICIT SEQUENCE { dp-AnalysedInfoCriteriaList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { dialledNumber OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camelCapabilityHandling [1] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [3] IMPLICIT NULL OPTIONAL, csi-Active [4] IMPLICIT NULL OPTIONAL, ... } OPTIONAL} OPTIONAL, extensionContainer [14] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL,
3116
3GPP
3117 Release 4
18359 18360 18361 18362 18363 18364 18365 18366 18367 18368 18369 18370 18371 18372 18373 18374 18375 18376 18377 18378 18379 18380 18381 18382 18383 18384 18385 18386 18387 18388 18389 18390 18391 18392 18393 18394 18395 18396 18397 18398 18399 18400 18401 18402 18403 18404 18405 18406 18407 18408 18409 18410 18411 18412 18413 18414 18415 18416 18417 18418 18419 18420 18421 18422 18423 18424 18425 18426 18427 18428 18429 18430 18431 18432 18433 18434 18435
1173
3GPP TS 29.002 V4.17.0 (2006-06)
pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , naea-PreferredCI [15] IMPLICIT SEQUENCE { naea-PreferredCIC [0] IMPLICIT OCTET STRING ( SIZE( 3 ) ), extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, gprsSubscriptionData [16] IMPLICIT SEQUENCE { completeDataListIncluded NULL OPTIONAL, gprsDataList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 50 ) ) OF SEQUENCE { pdp-ContextId INTEGER ( 1 .. 50 ), pdp-Type [16] IMPLICIT OCTET STRING ( SIZE( 2 ) ), pdp-Address [17] IMPLICIT OCTET STRING ( SIZE( 1 .. 16 ) ) OPTIONAL, qos-Subscribed [18] IMPLICIT OCTET STRING ( SIZE( 3 ) ), vplmnAddressAllowed [19] IMPLICIT NULL OPTIONAL, apn [20] IMPLICIT OCTET STRING ( SIZE( 2 .. 63 ) ), extensionContainer [21] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , ext-QoS-Subscribed [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 9 ) ) OPTIONAL, pdp-ChargingCharacteristics [1] IMPLICIT OCTET STRING ( SIZE( 2 ) ) OPTIONAL}, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, roamingRestrictedInSgsnDueToUnsupportedFeature [23] IMPLICIT NULL OPTIONAL, networkAccessMode [24] IMPLICIT ENUMERATED { bothMSCAndSGSN ( 0 ), onlyMSC ( 1 ), onlySGSN ( 2 ), ... } OPTIONAL, lsaInformation [25] IMPLICIT SEQUENCE { completeDataListIncluded NULL OPTIONAL, lsaOnlyAccessIndicator [1] IMPLICIT ENUMERATED { accessOutsideLSAsAllowed ( 0 ), accessOutsideLSAsRestricted ( 1 ) } OPTIONAL, lsaDataList [2] IMPLICIT SEQUENCE ( SIZE( 1 .. 20 ) ) OF SEQUENCE { lsaIdentity [0] IMPLICIT OCTET STRING ( SIZE( 3 ) ), lsaAttributes [1] IMPLICIT OCTET STRING ( SIZE( 1 ) ), lsaActiveModeIndicator [2] IMPLICIT NULL OPTIONAL, extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( {
3118
3GPP
3119 Release 4
18436 18437 18438 18439 18440 18441 18442 18443 18444 18445 18446 18447 18448 18449 18450 18451 18452 18453 18454 18455 18456 18457 18458 18459 18460 18461 18462 18463 18464 18465 18466 18467 18468 18469 18470 18471 18472 18473 18474 18475 18476 18477 18478 18479 18480 18481 18482 18483 18484 18485 18486 18487 18488 18489 18490 18491 18492 18493 18494 18495 18496 18497 18498 18499 18500 18501 18502 18503 18504 18505 18506 18507 18508 18509 18510 18511 18512
1174
3GPP TS 29.002 V4.17.0 (2006-06)
, ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, lmu-Indicator [21] IMPLICIT NULL OPTIONAL, lcsInformation [22] IMPLICIT SEQUENCE { gmlc-List [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, lcs-PrivacyExceptionList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 4 ) ) OF SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ), ss-Status OCTET STRING ( SIZE( 1 .. 5 ) ), notificationToMSUser [0] IMPLICIT ENUMERATED { notifyLocationAllowed ( 0 ), notifyAndVerify-LocationAllowedIfNoResponse ( 1 ), notifyAndVerify-LocationNotAllowedIfNoResponse ( 2 ), ... , locationNotAllowed ( 3 ) } OPTIONAL, externalClientList [1] IMPLICIT SEQUENCE ( SIZE( 0 .. 5 ) ) OF SEQUENCE { clientIdentity SEQUENCE { externalAddress [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) OPTIONAL, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, gmlc-Restriction [0] IMPLICIT ENUMERATED { gmlc-List ( 0 ), home-Country ( 1 ), ... } OPTIONAL, notificationToMSUser [1] IMPLICIT ENUMERATED { notifyLocationAllowed ( 0 ), notifyAndVerify-LocationAllowedIfNoResponse ( 1 ), notifyAndVerify-LocationNotAllowedIfNoResponse ( 2 ), ... , locationNotAllowed ( 3 ) } OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, plmnClientList [2] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF
3120
3GPP
3121 Release 4
18513 18514 18515 18516 18517 18518 18519 18520 18521 18522 18523 18524 18525 18526 18527 18528 18529 18530 18531 18532 18533 18534 18535 18536 18537 18538 18539 18540 18541 18542 18543 18544 18545 18546 18547 18548 18549 18550 18551 18552 18553 18554 18555 18556 18557 18558 18559 18560 18561 18562 18563 18564 18565 18566 18567 18568 18569 18570 18571 18572 18573 18574 18575 18576 18577 18578 18579 18580 18581 18582 18583 18584 18585 18586 18587 18588 18589
1175
3GPP TS 29.002 V4.17.0 (2006-06)
ENUMERATED { broadcastService ( 0 ), o-andM-HPLMN ( 1 ), o-andM-VPLMN ( 2 ), anonymousLocation ( 3 ), targetMSsubscribedService ( 4 ), ... } OPTIONAL, extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , ext-externalClientList [4] IMPLICIT SEQUENCE ( SIZE( 1 .. 35 ) ) OF SEQUENCE { clientIdentity SEQUENCE { externalAddress [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) OPTIONAL, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, gmlc-Restriction [0] IMPLICIT ENUMERATED { gmlc-List ( 0 ), home-Country ( 1 ), ... } OPTIONAL, notificationToMSUser [1] IMPLICIT ENUMERATED { notifyLocationAllowed ( 0 ), notifyAndVerify-LocationAllowedIfNoResponse ( 1 ), notifyAndVerify-LocationNotAllowedIfNoResponse ( 2 ), ... , locationNotAllowed ( 3 ) } OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL} OPTIONAL, molr-List [2] IMPLICIT SEQUENCE ( SIZE( 1 .. 3 ) ) OF SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ), ss-Status OCTET STRING ( SIZE( 1 .. 5 ) ), extensionContainer [0] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL,
3122
3GPP
3123 Release 4
18590 18591 18592 18593 18594 18595 18596 18597 18598 18599 18600 18601 18602 18603 18604 18605 18606 18607 18608 18609 18610 18611 18612 18613 18614 18615 18616 18617 18618 18619 18620 18621 18622 18623 18624 18625 18626 18627 18628 18629 18630 18631 18632 18633 18634 18635 18636 18637 18638 18639 18640 18641 18642 18643 18644 18645 18646 18647 18648 18649 18650 18651 18652 18653 18654 18655 18656 18657 18658 18659 18660 18661 18662 18663 18664 18665 18666
1176
3GPP TS 29.002 V4.17.0 (2006-06)
... } OPTIONAL, istAlertTimer [26] IMPLICIT INTEGER ( 15 .. 255 ) OPTIONAL, superChargerSupportedInHLR [27] IMPLICIT OCTET STRING ( SIZE( 1 .. 6 ) ) OPTIONAL, mc-SS-Info [28] IMPLICIT SEQUENCE { ss-Code [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ), ss-Status [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), nbrSB [2] IMPLICIT INTEGER ( 2 .. 7 ), nbrUser [3] IMPLICIT INTEGER ( 1 .. 7 ), extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, cs-AllocationRetentionPriority [29] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, sgsn-CAMEL-SubscriptionInfo [17] IMPLICIT SEQUENCE { gprs-CSI [0] IMPLICIT SEQUENCE { gprs-CamelTDPDataList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { gprs-TriggerDetectionPoint [0] IMPLICIT ENUMERATED { attach ( 1 ), attachChangeOfPosition ( 2 ), pdp-ContextEstablishment ( 11 ), pdp-ContextEstablishmentAcknowledgement ( 12 ), pdp-ContextChangeOfPosition ( 14 ), ... }, serviceKey [1] IMPLICIT INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultSessionHandling [3] IMPLICIT ENUMERATED { continueTransaction ( 0 ), releaseTransaction ( 1 ), ... }, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camelCapabilityHandling [1] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [3] IMPLICIT NULL OPTIONAL, csi-Active [4] IMPLICIT NULL OPTIONAL, ... } OPTIONAL, sms-CSI [1] IMPLICIT SEQUENCE { sms-CAMEL-TDP-DataList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { sms-TriggerDetectionPoint [0] IMPLICIT ENUMERATED { sms-CollectedInfo ( 1 ), ... }, serviceKey [1] IMPLICIT INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultSMS-Handling [3] IMPLICIT ENUMERATED {
3124
3GPP
3125 Release 4
18667 18668 18669 18670 18671 18672 18673 18674 18675 18676 18677 18678 18679 18680 18681 18682 18683 18684 18685 18686 18687 18688 18689 18690 18691 18692 18693 18694 18695 18696 18697 18698 18699 18700 18701 18702 18703 18704 18705 18706 18707 18708 18709 18710 18711 18712 18713 18714 18715 18716 18717 18718 18719 18720 18721 18722 18723 18724 18725 18726 18727 18728 18729 18730 18731 18732 18733 18734 18735 18736 18737 18738 18739 18740 18741 18742 18743
1177
3GPP TS 29.002 V4.17.0 (2006-06)
continueTransaction ( 0 ), releaseTransaction ( 1 ), ... }, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camelCapabilityHandling [1] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [3] IMPLICIT NULL OPTIONAL, csi-Active [4] IMPLICIT NULL OPTIONAL, ... } OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, chargingCharacteristics [18] IMPLICIT OCTET STRING ( SIZE( 2 ) ) OPTIONAL} RESULT insertSubscriberDataRes SEQUENCE { teleserviceList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 20 ) ) OF OCTET STRING ( SIZE( 1 .. 5 ) ) OPTIONAL, bearerServiceList [2] IMPLICIT SEQUENCE ( SIZE( 1 .. 50 ) ) OF OCTET STRING ( SIZE( 1 .. 5 ) ) OPTIONAL, ss-List [3] IMPLICIT SEQUENCE ( SIZE( 1 .. 30 ) ) OF OCTET STRING ( SIZE( 1 ) ) OPTIONAL, odb-GeneralData [4] IMPLICIT 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 ),
3126
3GPP
3127 Release 4
18744 18745 18746 18747 18748 18749 18750 18751 18752 18753 18754 18755 18756 18757 18758 18759 18760 18761 18762 18763 18764 18765 18766 18767 18768 18769 18770 18771 18772 18773 18774 18775 18776 18777 18778 18779 18780 18781 18782 18783 18784 18785 18786 18787 18788 18789 18790 18791 18792 18793 18794 18795 18796 18797 18798 18799 18800 18801 18802 18803 18804 18805 18806 18807 18808 18809 18810 18811 18812 18813 18814 18815 18816 18817 18818 18819 18820
1178
3GPP TS 29.002 V4.17.0 (2006-06)
roamingOutsidePLMN-Barred (22 ), roamingOutsidePLMN-CountryBarred (23 ), registrationAllCF-Barred (24 ), registrationCFNotToHPLMN-Barred (25 ), registrationInterzonalCF-Barred (26 ), registrationInterzonalCFNotToHPLMN-Barred (27 ), registrationInternationalCF-Barred (28 )} ( SIZE( 15 .. 32 ) ) OPTIONAL, regionalSubscriptionResponse [5] IMPLICIT ENUMERATED { networkNode-AreaRestricted ( 0 ), tooManyZoneCodes ( 1 ), zoneCodesConflict ( 2 ), regionalSubscNotSupported ( 3 ) } OPTIONAL, supportedCamelPhases [6] IMPLICIT BIT STRING { phase1 (0 ), phase2 (1 ), phase3 (2 )} ( SIZE( 1 .. 16 ) ) OPTIONAL, extensionContainer [7] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- unidentifiedSubscriber -- localValue : 5} ::= localValue : 7 deleteSubscriberData OPERATION ARGUMENT deleteSubscriberDataArg SEQUENCE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), basicServiceList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 70 ) ) OF CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, ss-List [2] IMPLICIT SEQUENCE ( SIZE( 1 .. 30 ) ) OF OCTET STRING ( SIZE( 1 ) ) OPTIONAL, roamingRestrictionDueToUnsupportedFeature [4] IMPLICIT NULL OPTIONAL, regionalSubscriptionIdentifier [5] IMPLICIT OCTET STRING ( SIZE( 2 ) ) OPTIONAL, vbsGroupIndication [7] IMPLICIT NULL OPTIONAL, vgcsGroupIndication [8] IMPLICIT NULL OPTIONAL, camelSubscriptionInfoWithdraw [9] IMPLICIT NULL OPTIONAL, extensionContainer [6] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , gprsSubscriptionDataWithdraw [10] CHOICE { allGPRSData NULL, contextIdList SEQUENCE ( SIZE( 1 .. 50 ) ) OF INTEGER ( 1 .. 50 )} OPTIONAL, roamingRestrictedInSgsnDueToUnsuppportedFeature [11] IMPLICIT NULL OPTIONAL, lsaInformationWithdraw [12] CHOICE { allLSAData NULL, lsaIdentityList SEQUENCE ( SIZE( 1 .. 20 ) ) OF OCTET STRING ( SIZE( 3 ) )} OPTIONAL, gmlc-ListWithdraw [13] IMPLICIT NULL OPTIONAL, istInformationWithdraw [14] IMPLICIT NULL OPTIONAL, specificCSI-Withdraw [15] IMPLICIT BIT STRING { o-csi (0 ), ss-csi (1 ),
3128
3GPP
3129 Release 4
18821 18822 18823 18824 18825 18826 18827 18828 18829 18830 18831 18832 18833 18834 18835 18836 18837 18838 18839 18840 18841 18842 18843 18844 18845 18846 18847 18848 18849 18850 18851 18852 18853 18854 18855 18856 18857 18858 18859 18860 18861 18862 18863 18864 18865 18866 18867 18868 18869 18870 18871 18872 18873 18874 18875 18876 18877 18878 18879 18880 18881 18882 18883 18884 18885 18886 18887 18888 18889 18890 18891 18892 18893 18894 18895 18896 18897
1179
3GPP TS 29.002 V4.17.0 (2006-06)
tif-csi (2 ), d-csi (3 ), vt-csi (4 ), sms-csi (5 ), m-csi (6 ), gprs-csi (7 ), t-csi (8 )} ( SIZE( 8 .. 32 ) ) OPTIONAL, chargingCharacteristicsWithdraw [16] IMPLICIT NULL OPTIONAL} RESULT deleteSubscriberDataRes SEQUENCE { regionalSubscriptionResponse [0] IMPLICIT ENUMERATED { networkNode-AreaRestricted ( 0 ), tooManyZoneCodes ( 1 ), zoneCodesConflict ( 2 ), regionalSubscNotSupported ( 3 ) } OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- unidentifiedSubscriber -- localValue : 5} ::= localValue : 8 reset OPERATION ARGUMENT resetArg SEQUENCE { hlr-Number OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), hlr-List SEQUENCE ( SIZE( 1 .. 50 ) ) OF OCTET STRING ( SIZE( 3 .. 8 ) ) OPTIONAL, ... } ::= localValue : 37 forwardCheckSS-Indication OPERATION ::= localValue : 38 restoreData OPERATION ARGUMENT restoreDataArg SEQUENCE { imsi OCTET STRING ( SIZE( 3 .. 8 ) ), lmsi OCTET STRING ( SIZE( 4 ) ) OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , vlr-Capability [6] IMPLICIT SEQUENCE { supportedCamelPhases [0] IMPLICIT BIT STRING { phase1 (0 ), phase2 (1 ), phase3 (2 )} ( SIZE( 1 .. 16 ) ) OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { ,
3130
3GPP
3131 Release 4
18898 18899 18900 18901 18902 18903 18904 18905 18906 18907 18908 18909 18910 18911 18912 18913 18914 18915 18916 18917 18918 18919 18920 18921 18922 18923 18924 18925 18926 18927 18928 18929 18930 18931 18932 18933 18934 18935 18936 18937 18938 18939 18940 18941 18942 18943 18944 18945 18946 18947 18948 18949 18950 18951 18952 18953 18954 18955 18956 18957 18958 18959 18960 18961 18962 18963 18964 18965 18966 18967 18968 18969 18970 18971 18972 18973 18974
1180
3GPP TS 29.002 V4.17.0 (2006-06)
...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , solsaSupportIndicator [2] IMPLICIT NULL OPTIONAL, istSupportIndicator [1] IMPLICIT ENUMERATED { basicISTSupported ( 0 ), istCommandSupported ( 1 ), ... } OPTIONAL, superChargerSupportedInServingNetworkEntity [3] CHOICE { sendSubscriberData [0] IMPLICIT NULL, subscriberDataStored [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 6 ) )} OPTIONAL, longFTN-Supported [4] IMPLICIT NULL OPTIONAL, supportedLCS-CapabilitySets [5] IMPLICIT BIT STRING { lcsCapabilitySet1 (0 ), lcsCapabilitySet2 (1 )} ( SIZE( 2 .. 16 ) ) OPTIONAL} OPTIONAL} RESULT restoreDataRes SEQUENCE { hlr-Number OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), msNotReachable NULL OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- unknownSubscriber -- localValue : 1} ::= localValue : 57 activateTraceMode OPERATION ARGUMENT activateTraceModeArg SEQUENCE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ) OPTIONAL, traceReference [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 2 ) ), traceType [2] IMPLICIT INTEGER ( 0 .. 255 ), omc-Id [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) OPTIONAL, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT activateTraceModeRes SEQUENCE { extensionContainer [0] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS {
3132
3GPP
3133 Release 4
18975 18976 18977 18978 18979 18980 18981 18982 18983 18984 18985 18986 18987 18988 18989 18990 18991 18992 18993 18994 18995 18996 18997 18998 18999 19000 19001 19002 19003 19004 19005 19006 19007 19008 19009 19010 19011 19012 19013 19014 19015 19016 19017 19018 19019 19020 19021 19022 19023 19024 19025 19026 19027 19028 19029 19030 19031 19032 19033 19034 19035 19036 19037 19038 19039 19040 19041 19042 19043 19044 19045 19046 19047 19048 19049 19050 19051
1181
3GPP TS 29.002 V4.17.0 (2006-06)
-- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- facilityNotSupported -- localValue : 21, -- unidentifiedSubscriber -- localValue : 5, -- tracingBufferFull -- localValue : 40} ::= localValue : 50 deactivateTraceMode OPERATION ARGUMENT deactivateTraceModeArg SEQUENCE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ) OPTIONAL, traceReference [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 2 ) ), extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT deactivateTraceModeRes SEQUENCE { extensionContainer [0] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- facilityNotSupported -- localValue : 21, -- unidentifiedSubscriber -- localValue : 5} ::= localValue : 51 sendIMSI OPERATION ARGUMENT msisdn OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) RESULT imsi OCTET STRING ( SIZE( 3 .. 8 ) ) ERRORS { -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- unknownSubscriber -- localValue : 1} ::= localValue : 58 sendRoutingInfo OPERATION ARGUMENT sendRoutingInfoArg SEQUENCE { msisdn [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), cug-CheckInfo [1] IMPLICIT SEQUENCE { cug-Interlock OCTET STRING ( SIZE( 4 ) ), cug-OutgoingAccess NULL OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE {
3134
3GPP
3135 Release 4
19052 19053 19054 19055 19056 19057 19058 19059 19060 19061 19062 19063 19064 19065 19066 19067 19068 19069 19070 19071 19072 19073 19074 19075 19076 19077 19078 19079 19080 19081 19082 19083 19084 19085 19086 19087 19088 19089 19090 19091 19092 19093 19094 19095 19096 19097 19098 19099 19100 19101 19102 19103 19104 19105 19106 19107 19108 19109 19110 19111 19112 19113 19114 19115 19116 19117 19118 19119 19120 19121 19122 19123 19124 19125 19126 19127 19128
1182
3GPP TS 29.002 V4.17.0 (2006-06)
... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, numberOfForwarding [2] IMPLICIT INTEGER ( 1 .. 5 ) OPTIONAL, interrogationType [3] IMPLICIT ENUMERATED { basicCall ( 0 ), forwarding ( 1 ) }, or-Interrogation [4] IMPLICIT NULL OPTIONAL, or-Capability [5] IMPLICIT INTEGER ( 1 .. 127 ) OPTIONAL, gmsc-Address [6] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), callReferenceNumber [7] IMPLICIT OCTET STRING ( SIZE( 1 .. 8 ) ) OPTIONAL, forwardingReason [8] IMPLICIT ENUMERATED { notReachable ( 0 ), busy ( 1 ), noReply ( 2 ) } OPTIONAL, basicServiceGroup [9] CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, networkSignalInfo [10] IMPLICIT SEQUENCE { protocolId ENUMERATED { gsm-0408 ( 1 ), gsm-0806 ( 2 ), gsm-BSSMAP ( 3 ), ets-300102-1 ( 4 ) }, signalInfo OCTET STRING ( SIZE( 1 .. 200 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camelInfo [11] IMPLICIT SEQUENCE { supportedCamelPhases BIT STRING { phase1 (0 ), phase2 (1 ), phase3 (2 )} ( SIZE( 1 .. 16 ) ), suppress-T-CSI NULL OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, suppressionOfAnnouncement [12] IMPLICIT NULL OPTIONAL, extensionContainer [13] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , alertingPattern [14] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ccbs-Call [15] IMPLICIT NULL OPTIONAL, supportedCCBS-Phase [16] IMPLICIT INTEGER ( 1 .. 127 ) OPTIONAL, additionalSignalInfo [17] IMPLICIT SEQUENCE { ext-ProtocolId ENUMERATED { ets-300356 ( 1 ),
3136
3GPP
3137 Release 4
19129 19130 19131 19132 19133 19134 19135 19136 19137 19138 19139 19140 19141 19142 19143 19144 19145 19146 19147 19148 19149 19150 19151 19152 19153 19154 19155 19156 19157 19158 19159 19160 19161 19162 19163 19164 19165 19166 19167 19168 19169 19170 19171 19172 19173 19174 19175 19176 19177 19178 19179 19180 19181 19182 19183 19184 19185 19186 19187 19188 19189 19190 19191 19192 19193 19194 19195 19196 19197 19198 19199 19200 19201 19202 19203 19204 19205
1183
3GPP TS 29.002 V4.17.0 (2006-06)
... }, signalInfo OCTET STRING ( SIZE( 1 .. 200 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, istSupportIndicator [18] IMPLICIT ENUMERATED { basicISTSupported ( 0 ), istCommandSupported ( 1 ), ... } OPTIONAL, pre-pagingSupported [19] IMPLICIT NULL OPTIONAL, callDiversionTreatmentIndicator [20] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, longFTN-Supported [21] IMPLICIT NULL OPTIONAL} RESULT sendRoutingInfoRes [3] IMPLICIT SEQUENCE { imsi [9] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ) OPTIONAL, extendedRoutingInfo CHOICE { routingInfo CHOICE { roamingNumber OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), forwardingData SEQUENCE { forwardedToNumber [5] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, forwardedToSubaddress [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, forwardingOptions [6] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, extensionContainer [7] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , longForwardedToNumber [8] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 15 ) ) OPTIONAL}}, camelRoutingInfo [8] IMPLICIT SEQUENCE { forwardingData SEQUENCE { forwardedToNumber [5] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, forwardedToSubaddress [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, forwardingOptions [6] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, extensionContainer [7] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , longForwardedToNumber [8] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 15 ) ) OPTIONAL} OPTIONAL, gmscCamelSubscriptionInfo [0] IMPLICIT SEQUENCE { t-CSI [0] IMPLICIT SEQUENCE { t-BcsmCamelTDPDataList SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { t-BcsmTriggerDetectionPoint ENUMERATED { termAttemptAuthorized ( 12 ), ... , tBusy ( 13 ), tNoAnswer ( 14 ) }, serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling [1] IMPLICIT ENUMERATED {
3138
3GPP
3139 Release 4
19206 19207 19208 19209 19210 19211 19212 19213 19214 19215 19216 19217 19218 19219 19220 19221 19222 19223 19224 19225 19226 19227 19228 19229 19230 19231 19232 19233 19234 19235 19236 19237 19238 19239 19240 19241 19242 19243 19244 19245 19246 19247 19248 19249 19250 19251 19252 19253 19254 19255 19256 19257 19258 19259 19260 19261 19262 19263 19264 19265 19266 19267 19268 19269 19270 19271 19272 19273 19274 19275 19276 19277 19278 19279 19280 19281 19282
1184
3GPP TS 29.002 V4.17.0 (2006-06)
continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , camelCapabilityHandling [0] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, notificationToCSE [1] IMPLICIT NULL OPTIONAL, csi-Active [2] IMPLICIT NULL OPTIONAL} OPTIONAL, o-CSI [1] IMPLICIT SEQUENCE { o-BcsmCamelTDPDataList SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { o-BcsmTriggerDetectionPoint ENUMERATED { collectedInfo ( 2 ), ... , routeSelectFailure ( 4 ) }, serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling [1] IMPLICIT ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , camelCapabilityHandling [0] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, notificationToCSE [1] IMPLICIT NULL OPTIONAL, csiActive [2] IMPLICIT NULL OPTIONAL} OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE {
3140
3GPP
3141 Release 4
19283 19284 19285 19286 19287 19288 19289 19290 19291 19292 19293 19294 19295 19296 19297 19298 19299 19300 19301 19302 19303 19304 19305 19306 19307 19308 19309 19310 19311 19312 19313 19314 19315 19316 19317 19318 19319 19320 19321 19322 19323 19324 19325 19326 19327 19328 19329 19330 19331 19332 19333 19334 19335 19336 19337 19338 19339 19340 19341 19342 19343 19344 19345 19346 19347 19348 19349 19350 19351 19352 19353 19354 19355 19356 19357 19358 19359
1185
3GPP TS 29.002 V4.17.0 (2006-06)
extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , o-BcsmCamelTDP-CriteriaList [3] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { o-BcsmTriggerDetectionPoint ENUMERATED { collectedInfo ( 2 ), ... , routeSelectFailure ( 4 ) }, destinationNumberCriteria [0] IMPLICIT SEQUENCE { matchType [0] IMPLICIT ENUMERATED { inhibiting ( 0 ), enabling ( 1 ) }, destinationNumberList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, destinationNumberLengthList [2] IMPLICIT SEQUENCE ( SIZE( 1 .. 3 ) ) OF INTEGER ( 1 .. 15 ) OPTIONAL, ... } OPTIONAL, basicServiceCriteria [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, callTypeCriteria [2] IMPLICIT ENUMERATED { forwarded ( 0 ), notForwarded ( 1 ) } OPTIONAL, ... , o-CauseValueCriteria [3] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF OCTET STRING ( SIZE( 1 ) ) OPTIONAL, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL} OPTIONAL, t-BCSM-CAMEL-TDP-CriteriaList [4] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { t-BCSM-TriggerDetectionPoint ENUMERATED { termAttemptAuthorized ( 12 ), ... , tBusy ( 13 ), tNoAnswer ( 14 ) }, basicServiceCriteria [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, t-CauseValueCriteria [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ... } OPTIONAL, d-csi [5] IMPLICIT SEQUENCE { dp-AnalysedInfoCriteriaList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { dialledNumber OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) ,
3142
3GPP
3143 Release 4
19360 19361 19362 19363 19364 19365 19366 19367 19368 19369 19370 19371 19372 19373 19374 19375 19376 19377 19378 19379 19380 19381 19382 19383 19384 19385 19386 19387 19388 19389 19390 19391 19392 19393 19394 19395 19396 19397 19398 19399 19400 19401 19402 19403 19404 19405 19406 19407 19408 19409 19410 19411 19412 19413 19414 19415 19416 19417 19418 19419 19420 19421 19422 19423 19424 19425 19426 19427 19428 19429 19430 19431 19432 19433 19434 19435 19436
1186
3GPP TS 29.002 V4.17.0 (2006-06)
extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camelCapabilityHandling [1] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [3] IMPLICIT NULL OPTIONAL, csi-Active [4] IMPLICIT NULL OPTIONAL, ... } OPTIONAL}, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }} OPTIONAL, cug-CheckInfo [3] IMPLICIT SEQUENCE { cug-Interlock OCTET STRING ( SIZE( 4 ) ), cug-OutgoingAccess NULL OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, cugSubscriptionFlag [6] IMPLICIT NULL OPTIONAL, subscriberInfo [7] IMPLICIT SEQUENCE { locationInformation [0] IMPLICIT SEQUENCE { ageOfLocationInformation INTEGER ( 0 .. 32767 ) OPTIONAL, geographicalInformation [0] IMPLICIT OCTET STRING ( SIZE( 8 ) ) OPTIONAL, vlr-number [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, locationNumber [2] IMPLICIT OCTET STRING ( SIZE( 2 .. 10 ) ) OPTIONAL, cellGlobalIdOrServiceAreaIdOrLAI [3] CHOICE { cellGlobalIdOrServiceAreaIdFixedLength [0] IMPLICIT OCTET STRING ( SIZE( 7 ) ), laiFixedLength [1] IMPLICIT OCTET STRING ( SIZE( 5 ) )} OPTIONAL, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , selectedLSA-Id [5] IMPLICIT OCTET STRING ( SIZE( 3 ) ) OPTIONAL, msc-Number [6] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL,
3144
3GPP
3145 Release 4
19437 19438 19439 19440 19441 19442 19443 19444 19445 19446 19447 19448 19449 19450 19451 19452 19453 19454 19455 19456 19457 19458 19459 19460 19461 19462 19463 19464 19465 19466 19467 19468 19469 19470 19471 19472 19473 19474 19475 19476 19477 19478 19479 19480 19481 19482 19483 19484 19485 19486 19487 19488 19489 19490 19491 19492 19493 19494 19495 19496 19497 19498 19499 19500 19501 19502 19503 19504 19505 19506 19507 19508 19509 19510 19511 19512 19513
1187
3GPP TS 29.002 V4.17.0 (2006-06)
geodeticInformation [7] IMPLICIT OCTET STRING ( SIZE( 10 ) ) OPTIONAL, currentLocationRetrieved [8] IMPLICIT NULL OPTIONAL, sai-Present [9] IMPLICIT NULL OPTIONAL} OPTIONAL, subscriberState [1] CHOICE { assumedIdle [0] IMPLICIT NULL, camelBusy [1] IMPLICIT NULL, netDetNotReachable ENUMERATED { msPurged ( 0 ), imsiDetached ( 1 ), restrictedArea ( 2 ), notRegistered ( 3 ) }, notProvidedFromVLR [2] IMPLICIT NULL} OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, ss-List [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 30 ) ) OF OCTET STRING ( SIZE( 1 ) ) OPTIONAL, basicService [5] CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, forwardingInterrogationRequired [4] IMPLICIT NULL OPTIONAL, vmsc-Address [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, extensionContainer [0] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , naea-PreferredCI [10] IMPLICIT SEQUENCE { naea-PreferredCIC [0] IMPLICIT OCTET STRING ( SIZE( 3 ) ), extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, ccbs-Indicators [11] IMPLICIT SEQUENCE { ccbs-Possible [0] IMPLICIT NULL OPTIONAL, keepCCBS-CallIndicator [1] IMPLICIT NULL OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, msisdn [12] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL,
3146
3GPP
3147 Release 4
19514 19515 19516 19517 19518 19519 19520 19521 19522 19523 19524 19525 19526 19527 19528 19529 19530 19531 19532 19533 19534 19535 19536 19537 19538 19539 19540 19541 19542 19543 19544 19545 19546 19547 19548 19549 19550 19551 19552 19553 19554 19555 19556 19557 19558 19559 19560 19561 19562 19563 19564 19565 19566 19567 19568 19569 19570 19571 19572 19573 19574 19575 19576 19577 19578 19579 19580 19581 19582 19583 19584 19585 19586 19587 19588 19589 19590
1188
3GPP TS 29.002 V4.17.0 (2006-06)
numberPortabilityStatus [13] IMPLICIT ENUMERATED { notKnownToBePorted ( 0 ), ownNumberPortedOut ( 1 ), foreignNumberPortedToForeignNetwork ( 2 ), ... } OPTIONAL, istAlertTimer [14] IMPLICIT INTEGER ( 15 .. 255 ) OPTIONAL} ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- facilityNotSupported -- localValue : 21, -- or-NotAllowed -- localValue : 48, -- unknownSubscriber -- localValue : 1, -- numberChanged -- localValue : 44, -- bearerServiceNotProvisioned -- localValue : 10, -- teleserviceNotProvisioned -- localValue : 11, -- absentSubscriber -- localValue : 27, -- busySubscriber -- localValue : 45, -- noSubscriberReply -- localValue : 46, -- callBarred -- localValue : 13, -- cug-Reject -- localValue : 15, -- forwardingViolation -- localValue : 14} ::= localValue : 22 provideRoamingNumber OPERATION ARGUMENT provideRoamingNumberArg SEQUENCE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), msc-Number [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), msisdn [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, lmsi [4] IMPLICIT OCTET STRING ( SIZE( 4 ) ) OPTIONAL, gsm-BearerCapability [5] IMPLICIT SEQUENCE { protocolId ENUMERATED { gsm-0408 ( 1 ), gsm-0806 ( 2 ), gsm-BSSMAP ( 3 ), ets-300102-1 ( 4 ) }, signalInfo OCTET STRING ( SIZE( 1 .. 200 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, networkSignalInfo [6] IMPLICIT SEQUENCE { protocolId ENUMERATED { gsm-0408 ( 1 ), gsm-0806 ( 2 ), gsm-BSSMAP ( 3 ), ets-300102-1 ( 4 ) }, signalInfo OCTET STRING ( SIZE( 1 .. 200 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, suppressionOfAnnouncement [7] IMPLICIT NULL OPTIONAL, gmsc-Address [8] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, callReferenceNumber [9] IMPLICIT OCTET STRING ( SIZE( 1 .. 8 ) ) OPTIONAL, or-Interrogation [10] IMPLICIT NULL OPTIONAL, extensionContainer [11] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF
3148
3GPP
3149 Release 4
19591 19592 19593 19594 19595 19596 19597 19598 19599 19600 19601 19602 19603 19604 19605 19606 19607 19608 19609 19610 19611 19612 19613 19614 19615 19616 19617 19618 19619 19620 19621 19622 19623 19624 19625 19626 19627 19628 19629 19630 19631 19632 19633 19634 19635 19636 19637 19638 19639 19640 19641 19642 19643 19644 19645 19646 19647 19648 19649 19650 19651 19652 19653 19654 19655 19656 19657 19658 19659 19660 19661 19662 19663 19664 19665 19666 19667
1189
3GPP TS 29.002 V4.17.0 (2006-06)
SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , alertingPattern [12] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ccbs-Call [13] IMPLICIT NULL OPTIONAL, supportedCamelPhasesInGMSC [15] IMPLICIT BIT STRING { phase1 (0 ), phase2 (1 ), phase3 (2 )} ( SIZE( 1 .. 16 ) ) OPTIONAL, additionalSignalInfo [14] IMPLICIT SEQUENCE { ext-ProtocolId ENUMERATED { ets-300356 ( 1 ), ... }, signalInfo OCTET STRING ( SIZE( 1 .. 200 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, orNotSupportedInGMSC [16] IMPLICIT NULL OPTIONAL, pre-pagingSupported [17] IMPLICIT NULL OPTIONAL, longFTN-Supported [18] IMPLICIT NULL OPTIONAL} RESULT provideRoamingNumberRes SEQUENCE { roamingNumber OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- facilityNotSupported -- localValue : 21, -- or-NotAllowed -- localValue : 48, -- absentSubscriber -- localValue : 27, -- noRoamingNumberAvailable -- localValue : 39} ::= localValue : 4 resumeCallHandling OPERATION ARGUMENT resumeCallHandlingArg SEQUENCE { callReferenceNumber [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 8 ) ) OPTIONAL, basicServiceGroup [1] CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, forwardingData [2] IMPLICIT SEQUENCE { forwardedToNumber [5] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, forwardedToSubaddress [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, forwardingOptions [6] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, extensionContainer [7] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF
3150
3GPP
3151 Release 4
19668 19669 19670 19671 19672 19673 19674 19675 19676 19677 19678 19679 19680 19681 19682 19683 19684 19685 19686 19687 19688 19689 19690 19691 19692 19693 19694 19695 19696 19697 19698 19699 19700 19701 19702 19703 19704 19705 19706 19707 19708 19709 19710 19711 19712 19713 19714 19715 19716 19717 19718 19719 19720 19721 19722 19723 19724 19725 19726 19727 19728 19729 19730 19731 19732 19733 19734 19735 19736 19737 19738 19739 19740 19741 19742 19743 19744
1190
3GPP TS 29.002 V4.17.0 (2006-06)
SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , longForwardedToNumber [8] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 15 ) ) OPTIONAL} OPTIONAL, imsi [3] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ) OPTIONAL, cug-CheckInfo [4] IMPLICIT SEQUENCE { cug-Interlock OCTET STRING ( SIZE( 4 ) ), cug-OutgoingAccess NULL OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, o-CSI [5] IMPLICIT SEQUENCE { o-BcsmCamelTDPDataList SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { o-BcsmTriggerDetectionPoint ENUMERATED { collectedInfo ( 2 ), ... , routeSelectFailure ( 4 ) }, serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling [1] IMPLICIT ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , camelCapabilityHandling [0] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, notificationToCSE [1] IMPLICIT NULL OPTIONAL, csiActive [2] IMPLICIT NULL OPTIONAL} OPTIONAL, extensionContainer [7] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) ,
3152
3GPP
3153 Release 4
19745 19746 19747 19748 19749 19750 19751 19752 19753 19754 19755 19756 19757 19758 19759 19760 19761 19762 19763 19764 19765 19766 19767 19768 19769 19770 19771 19772 19773 19774 19775 19776 19777 19778 19779 19780 19781 19782 19783 19784 19785 19786 19787 19788 19789 19790 19791 19792 19793 19794 19795 19796 19797 19798 19799 19800 19801 19802 19803 19804 19805 19806 19807 19808 19809 19810 19811 19812 19813 19814 19815 19816 19817 19818 19819 19820 19821
1191
3GPP TS 29.002 V4.17.0 (2006-06)
extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ccbs-Possible [8] IMPLICIT NULL OPTIONAL, msisdn [9] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, uu-Data [10] IMPLICIT SEQUENCE { uuIndicator [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, uui [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 131 ) ) OPTIONAL, uusCFInteraction [2] IMPLICIT NULL OPTIONAL, extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, allInformationSent [11] IMPLICIT NULL OPTIONAL, ... , d-csi [12] IMPLICIT SEQUENCE { dp-AnalysedInfoCriteriaList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { dialledNumber OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camelCapabilityHandling [1] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [3] IMPLICIT NULL OPTIONAL, csi-Active [4] IMPLICIT NULL OPTIONAL, ... } OPTIONAL} RESULT resumeCallHandlingRes SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL,
3154
3GPP
3155 Release 4
19822 19823 19824 19825 19826 19827 19828 19829 19830 19831 19832 19833 19834 19835 19836 19837 19838 19839 19840 19841 19842 19843 19844 19845 19846 19847 19848 19849 19850 19851 19852 19853 19854 19855 19856 19857 19858 19859 19860 19861 19862 19863 19864 19865 19866 19867 19868 19869 19870 19871 19872 19873 19874 19875 19876 19877 19878 19879 19880 19881 19882 19883 19884 19885 19886 19887 19888 19889 19890 19891 19892 19893 19894 19895 19896 19897 19898
1192
3GPP TS 29.002 V4.17.0 (2006-06)
pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- forwardingFailed -- localValue : 47, -- or-NotAllowed -- localValue : 48, -- unexpectedDataValue -- localValue : 36, -- dataMissing -- localValue : 35} ::= localValue : 6 provideSIWFSNumber OPERATION ARGUMENT provideSIWFSNumberArg SEQUENCE { gsm-BearerCapability [0] IMPLICIT SEQUENCE { protocolId ENUMERATED { gsm-0408 ( 1 ), gsm-0806 ( 2 ), gsm-BSSMAP ( 3 ), ets-300102-1 ( 4 ) }, signalInfo OCTET STRING ( SIZE( 1 .. 200 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, isdn-BearerCapability [1] IMPLICIT SEQUENCE { protocolId ENUMERATED { gsm-0408 ( 1 ), gsm-0806 ( 2 ), gsm-BSSMAP ( 3 ), ets-300102-1 ( 4 ) }, signalInfo OCTET STRING ( SIZE( 1 .. 200 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, call-Direction [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), b-Subscriber-Address [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), chosenChannel [4] IMPLICIT SEQUENCE { protocolId ENUMERATED { gsm-0408 ( 1 ), gsm-0806 ( 2 ), gsm-BSSMAP ( 3 ), ets-300102-1 ( 4 ) }, signalInfo OCTET STRING ( SIZE( 1 .. 200 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, lowerLayerCompatibility [5] IMPLICIT SEQUENCE {
3156
3GPP
3157 Release 4
19899 19900 19901 19902 19903 19904 19905 19906 19907 19908 19909 19910 19911 19912 19913 19914 19915 19916 19917 19918 19919 19920 19921 19922 19923 19924 19925 19926 19927 19928 19929 19930 19931 19932 19933 19934 19935 19936 19937 19938 19939 19940 19941 19942 19943 19944 19945 19946 19947 19948 19949 19950 19951 19952 19953 19954 19955 19956 19957 19958 19959 19960 19961 19962 19963 19964 19965 19966 19967 19968 19969 19970 19971 19972 19973 19974 19975
1193
3GPP TS 29.002 V4.17.0 (2006-06)
protocolId ENUMERATED { gsm-0408 ( 1 ), gsm-0806 ( 2 ), gsm-BSSMAP ( 3 ), ets-300102-1 ( 4 ) }, signalInfo OCTET STRING ( SIZE( 1 .. 200 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, highLayerCompatibility [6] IMPLICIT SEQUENCE { protocolId ENUMERATED { gsm-0408 ( 1 ), gsm-0806 ( 2 ), gsm-BSSMAP ( 3 ), ets-300102-1 ( 4 ) }, signalInfo OCTET STRING ( SIZE( 1 .. 200 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, extensionContainer [7] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT provideSIWFSNumberRes SEQUENCE { sIWFSNumber [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- resourceLimitation -- localValue : 51, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- systemFailure -- localValue : 34} ::= localValue : 31 sIWFSSignallingModify OPERATION ARGUMENT
3158
3GPP
3159 Release 4
19976 19977 19978 19979 19980 19981 19982 19983 19984 19985 19986 19987 19988 19989 19990 19991 19992 19993 19994 19995 19996 19997 19998 19999 20000 20001 20002 20003 20004 20005 20006 20007 20008 20009 20010 20011 20012 20013 20014 20015 20016 20017 20018 20019 20020 20021 20022 20023 20024 20025 20026 20027 20028 20029 20030 20031 20032 20033 20034 20035 20036 20037 20038 20039 20040 20041 20042 20043 20044 20045 20046 20047 20048 20049 20050 20051 20052
1194
3GPP TS 29.002 V4.17.0 (2006-06)
sIWFSSignallingModifyArg SEQUENCE { channelType [0] IMPLICIT SEQUENCE { protocolId ENUMERATED { gsm-0408 ( 1 ), gsm-0806 ( 2 ), gsm-BSSMAP ( 3 ), ets-300102-1 ( 4 ) }, signalInfo OCTET STRING ( SIZE( 1 .. 200 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, chosenChannel [1] IMPLICIT SEQUENCE { protocolId ENUMERATED { gsm-0408 ( 1 ), gsm-0806 ( 2 ), gsm-BSSMAP ( 3 ), ets-300102-1 ( 4 ) }, signalInfo OCTET STRING ( SIZE( 1 .. 200 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT sIWFSSignallingModifyRes SEQUENCE { chosenChannel [0] IMPLICIT SEQUENCE { protocolId ENUMERATED { gsm-0408 ( 1 ), gsm-0806 ( 2 ), gsm-BSSMAP ( 3 ), ets-300102-1 ( 4 ) }, signalInfo OCTET STRING ( SIZE( 1 .. 200 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, extensionContainer [1] IMPLICIT SEQUENCE {
3160
3GPP
3161 Release 4
20053 20054 20055 20056 20057 20058 20059 20060 20061 20062 20063 20064 20065 20066 20067 20068 20069 20070 20071 20072 20073 20074 20075 20076 20077 20078 20079 20080 20081 20082 20083 20084 20085 20086 20087 20088 20089 20090 20091 20092 20093 20094 20095 20096 20097 20098 20099 20100 20101 20102 20103 20104 20105 20106 20107 20108 20109 20110 20111 20112 20113 20114 20115 20116 20117 20118 20119 20120 20121 20122 20123 20124 20125 20126 20127 20128 20129
1195
3GPP TS 29.002 V4.17.0 (2006-06)
privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- resourceLimitation -- localValue : 51, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- systemFailure -- localValue : 34} ::= localValue : 32 setReportingState OPERATION ARGUMENT setReportingStateArg SEQUENCE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ) OPTIONAL, lmsi [1] IMPLICIT OCTET STRING ( SIZE( 4 ) ) OPTIONAL, ccbs-Monitoring [2] IMPLICIT ENUMERATED { stopMonitoring ( 0 ), startMonitoring ( 1 ), ... } OPTIONAL, extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT setReportingStateRes SEQUENCE { ccbs-SubscriberStatus [0] IMPLICIT ENUMERATED { ccbsNotIdle ( 0 ), ccbsIdle ( 1 ), ccbsNotReachable ( 2 ), ... } OPTIONAL, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- unidentifiedSubscriber -- localValue : 5, -- unexpectedDataValue -- localValue : 36, -- dataMissing -- localValue : 35, -- resourceLimitation -- localValue : 51, -- facilityNotSupported -- localValue : 21} ::= localValue : 73 statusReport OPERATION ARGUMENT statusReportArg SEQUENCE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), eventReportData [1] IMPLICIT SEQUENCE { ccbs-SubscriberStatus [0] IMPLICIT ENUMERATED { ccbsNotIdle ( 0 ),
3162
3GPP
3163 Release 4
20130 20131 20132 20133 20134 20135 20136 20137 20138 20139 20140 20141 20142 20143 20144 20145 20146 20147 20148 20149 20150 20151 20152 20153 20154 20155 20156 20157 20158 20159 20160 20161 20162 20163 20164 20165 20166 20167 20168 20169 20170 20171 20172 20173 20174 20175 20176 20177 20178 20179 20180 20181 20182 20183 20184 20185 20186 20187 20188 20189 20190 20191 20192 20193 20194 20195 20196 20197 20198 20199 20200 20201 20202 20203 20204 20205 20206
1196
3GPP TS 29.002 V4.17.0 (2006-06)
ccbsIdle ( 1 ), ccbsNotReachable ( 2 ), ... } OPTIONAL, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, callReportdata [2] IMPLICIT SEQUENCE { monitoringMode [0] IMPLICIT ENUMERATED { a-side ( 0 ), b-side ( 1 ), ... } OPTIONAL, callOutcome [1] IMPLICIT ENUMERATED { success ( 0 ), failure ( 1 ), busy ( 2 ), ... } OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT statusReportRes SEQUENCE { extensionContainer [0] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- unknownSubscriber -- localValue : 1, -- systemFailure -- localValue : 34, -- unexpectedDataValue -- localValue : 36, -- dataMissing -- localValue : 35} ::= localValue : 74 remoteUserFree OPERATION ARGUMENT remoteUserFreeArg SEQUENCE {
3164
3GPP
3165 Release 4
20207 20208 20209 20210 20211 20212 20213 20214 20215 20216 20217 20218 20219 20220 20221 20222 20223 20224 20225 20226 20227 20228 20229 20230 20231 20232 20233 20234 20235 20236 20237 20238 20239 20240 20241 20242 20243 20244 20245 20246 20247 20248 20249 20250 20251 20252 20253 20254 20255 20256 20257 20258 20259 20260 20261 20262 20263 20264 20265 20266 20267 20268 20269 20270 20271 20272 20273 20274 20275 20276 20277 20278 20279 20280 20281 20282 20283
1197
3GPP TS 29.002 V4.17.0 (2006-06)
imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), callInfo [1] IMPLICIT SEQUENCE { protocolId ENUMERATED { gsm-0408 ( 1 ), gsm-0806 ( 2 ), gsm-BSSMAP ( 3 ), ets-300102-1 ( 4 ) }, signalInfo OCTET STRING ( SIZE( 1 .. 200 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, ccbs-Feature [2] IMPLICIT SEQUENCE { ccbs-Index [0] IMPLICIT INTEGER ( 1 .. 5 ) OPTIONAL, b-subscriberNumber [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, b-subscriberSubaddress [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, basicServiceGroup [3] CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ... }, translatedB-Number [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), replaceB-Number [4] IMPLICIT NULL OPTIONAL, alertingPattern [5] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, extensionContainer [6] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT remoteUserFreeRes SEQUENCE { ruf-Outcome [0] IMPLICIT ENUMERATED { accepted ( 0 ), rejected ( 1 ), noResponseFromFreeMS ( 2 ), noResponseFromBusyMS ( 3 ), udubFromFreeMS ( 4 ), udubFromBusyMS ( 5 ), ... }, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- unexpectedDataValue -- localValue : 36, -- dataMissing -- localValue : 35, -- incompatibleTerminal -- localValue : 28, -- absentSubscriber -- localValue : 27, -- systemFailure -- localValue : 34, -- busySubscriber -- localValue : 45} ::= localValue : 75
3166
3GPP
3167 Release 4
20284 20285 20286 20287 20288 20289 20290 20291 20292 20293 20294 20295 20296 20297 20298 20299 20300 20301 20302 20303 20304 20305 20306 20307 20308 20309 20310 20311 20312 20313 20314 20315 20316 20317 20318 20319 20320 20321 20322 20323 20324 20325 20326 20327 20328 20329 20330 20331 20332 20333 20334 20335 20336 20337 20338 20339 20340 20341 20342 20343 20344 20345 20346 20347 20348 20349 20350 20351 20352 20353 20354 20355 20356 20357 20358 20359 20360
1198
3GPP TS 29.002 V4.17.0 (2006-06)
istAlert OPERATION ARGUMENT istAlertArg SEQUENCE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT istAlertRes SEQUENCE { istAlertTimer [0] IMPLICIT INTEGER ( 15 .. 255 ) OPTIONAL, istInformationWithdraw [1] IMPLICIT NULL OPTIONAL, callTerminationIndicator [2] IMPLICIT ENUMERATED { terminateCallActivityReferred ( 0 ), terminateAllCallActivities ( 1 ), ... } OPTIONAL, extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- unexpectedDataValue -- localValue : 36, -- resourceLimitation -- localValue : 51, -- unknownSubscriber -- localValue : 1, -- systemFailure -- localValue : 34, -- facilityNotSupported -- localValue : 21} ::= localValue : 87 istCommand OPERATION ARGUMENT istCommandArg SEQUENCE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT istCommandRes SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL,
3168
3GPP
3169 Release 4
20361 20362 20363 20364 20365 20366 20367 20368 20369 20370 20371 20372 20373 20374 20375 20376 20377 20378 20379 20380 20381 20382 20383 20384 20385 20386 20387 20388 20389 20390 20391 20392 20393 20394 20395 20396 20397 20398 20399 20400 20401 20402 20403 20404 20405 20406 20407 20408 20409 20410 20411 20412 20413 20414 20415 20416 20417 20418 20419 20420 20421 20422 20423 20424 20425 20426 20427 20428 20429 20430 20431 20432 20433 20434 20435 20436 20437
1199
3GPP TS 29.002 V4.17.0 (2006-06)
... } ERRORS { -- unexpectedDataValue -- localValue : 36, -- resourceLimitation -- localValue : 51, -- unknownSubscriber -- localValue : 1, -- systemFailure -- localValue : 34, -- facilityNotSupported -- localValue : 21} ::= localValue : 88 registerSS OPERATION ARGUMENT registerSS-Arg SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ), basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, forwardedToNumber [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) OPTIONAL, forwardedToSubaddress [6] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, noReplyConditionTime [5] IMPLICIT INTEGER ( 5 .. 30 ) OPTIONAL, ... , defaultPriority [7] IMPLICIT INTEGER ( 0 .. 15 ) OPTIONAL, nbrUser [8] IMPLICIT INTEGER ( 1 .. 7 ) OPTIONAL, longFTN-Supported [9] IMPLICIT NULL OPTIONAL} RESULT ss-Info CHOICE { forwardingInfo [0] IMPLICIT SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ) OPTIONAL, forwardingFeatureList SEQUENCE ( SIZE( 1 .. 13 ) ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, forwardedToNumber [5] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, forwardedToSubaddress [8] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, forwardingOptions [6] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, noReplyConditionTime [7] IMPLICIT INTEGER ( 5 .. 30 ) OPTIONAL, ... , longForwardedToNumber [9] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 15 ) ) OPTIONAL}, ... }, callBarringInfo [1] IMPLICIT SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ) OPTIONAL, callBarringFeatureList SEQUENCE ( SIZE( 1 .. 13 ) ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ... }, ... }, ss-Data [3] IMPLICIT SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ss-SubscriptionOption CHOICE { cliRestrictionOption [2] IMPLICIT ENUMERATED { permanent ( 0 ), temporaryDefaultRestricted ( 1 ), temporaryDefaultAllowed ( 2 ) }, overrideCategory [1] IMPLICIT ENUMERATED { overrideEnabled ( 0 ), overrideDisabled ( 1 ) }} OPTIONAL, basicServiceGroupList SEQUENCE ( SIZE( 1 .. 13 ) ) OF CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ... , defaultPriority INTEGER ( 0 .. 15 ) OPTIONAL, nbrUser [5] IMPLICIT INTEGER ( 1 .. 7 ) OPTIONAL}} ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- bearerServiceNotProvisioned -- localValue : 10, -- teleserviceNotProvisioned -- localValue : 11, -- callBarred -- localValue : 13, -- illegalSS-Operation -- localValue : 16, -- ss-ErrorStatus -- localValue : 17,
3170
3GPP
3171 Release 4
20438 20439 20440 20441 20442 20443 20444 20445 20446 20447 20448 20449 20450 20451 20452 20453 20454 20455 20456 20457 20458 20459 20460 20461 20462 20463 20464 20465 20466 20467 20468 20469 20470 20471 20472 20473 20474 20475 20476 20477 20478 20479 20480 20481 20482 20483 20484 20485 20486 20487 20488 20489 20490 20491 20492 20493 20494 20495 20496 20497 20498 20499 20500 20501 20502 20503 20504 20505 20506 20507 20508 20509 20510 20511 20512 20513 20514
1200
3GPP TS 29.002 V4.17.0 (2006-06)
-- ss-Incompatibility -- localValue : 20} ::= localValue : 10 eraseSS OPERATION ARGUMENT ss-ForBS SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ), basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ... , longFTN-Supported [4] IMPLICIT NULL OPTIONAL} RESULT ss-Info CHOICE { forwardingInfo [0] IMPLICIT SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ) OPTIONAL, forwardingFeatureList SEQUENCE ( SIZE( 1 .. 13 ) ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, forwardedToNumber [5] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, forwardedToSubaddress [8] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, forwardingOptions [6] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, noReplyConditionTime [7] IMPLICIT INTEGER ( 5 .. 30 ) OPTIONAL, ... , longForwardedToNumber [9] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 15 ) ) OPTIONAL}, ... }, callBarringInfo [1] IMPLICIT SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ) OPTIONAL, callBarringFeatureList SEQUENCE ( SIZE( 1 .. 13 ) ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ... }, ... }, ss-Data [3] IMPLICIT SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ss-SubscriptionOption CHOICE { cliRestrictionOption [2] IMPLICIT ENUMERATED { permanent ( 0 ), temporaryDefaultRestricted ( 1 ), temporaryDefaultAllowed ( 2 ) }, overrideCategory [1] IMPLICIT ENUMERATED { overrideEnabled ( 0 ), overrideDisabled ( 1 ) }} OPTIONAL, basicServiceGroupList SEQUENCE ( SIZE( 1 .. 13 ) ) OF CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ... , defaultPriority INTEGER ( 0 .. 15 ) OPTIONAL, nbrUser [5] IMPLICIT INTEGER ( 1 .. 7 ) OPTIONAL}} ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- bearerServiceNotProvisioned -- localValue : 10, -- teleserviceNotProvisioned -- localValue : 11, -- callBarred -- localValue : 13, -- illegalSS-Operation -- localValue : 16, -- ss-ErrorStatus -- localValue : 17} ::= localValue : 11 activateSS OPERATION ARGUMENT ss-ForBS SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ), basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ... , longFTN-Supported [4] IMPLICIT NULL OPTIONAL}
3172
3GPP
3173 Release 4
20515 20516 20517 20518 20519 20520 20521 20522 20523 20524 20525 20526 20527 20528 20529 20530 20531 20532 20533 20534 20535 20536 20537 20538 20539 20540 20541 20542 20543 20544 20545 20546 20547 20548 20549 20550 20551 20552 20553 20554 20555 20556 20557 20558 20559 20560 20561 20562 20563 20564 20565 20566 20567 20568 20569 20570 20571 20572 20573 20574 20575 20576 20577 20578 20579 20580 20581 20582 20583 20584 20585 20586 20587 20588 20589 20590 20591
1201
3GPP TS 29.002 V4.17.0 (2006-06)
RESULT ss-Info CHOICE { forwardingInfo [0] IMPLICIT SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ) OPTIONAL, forwardingFeatureList SEQUENCE ( SIZE( 1 .. 13 ) ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, forwardedToNumber [5] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, forwardedToSubaddress [8] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, forwardingOptions [6] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, noReplyConditionTime [7] IMPLICIT INTEGER ( 5 .. 30 ) OPTIONAL, ... , longForwardedToNumber [9] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 15 ) ) OPTIONAL}, ... }, callBarringInfo [1] IMPLICIT SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ) OPTIONAL, callBarringFeatureList SEQUENCE ( SIZE( 1 .. 13 ) ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ... }, ... }, ss-Data [3] IMPLICIT SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ss-SubscriptionOption CHOICE { cliRestrictionOption [2] IMPLICIT ENUMERATED { permanent ( 0 ), temporaryDefaultRestricted ( 1 ), temporaryDefaultAllowed ( 2 ) }, overrideCategory [1] IMPLICIT ENUMERATED { overrideEnabled ( 0 ), overrideDisabled ( 1 ) }} OPTIONAL, basicServiceGroupList SEQUENCE ( SIZE( 1 .. 13 ) ) OF CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ... , defaultPriority INTEGER ( 0 .. 15 ) OPTIONAL, nbrUser [5] IMPLICIT INTEGER ( 1 .. 7 ) OPTIONAL}} ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- bearerServiceNotProvisioned -- localValue : 10, -- teleserviceNotProvisioned -- localValue : 11, -- callBarred -- localValue : 13, -- illegalSS-Operation -- localValue : 16, -- ss-ErrorStatus -- localValue : 17, -- ss-SubscriptionViolation -- localValue : 19, -- ss-Incompatibility -- localValue : 20, -- negativePW-Check -- localValue : 38, -- numberOfPW-AttemptsViolation -- localValue : 43} ::= localValue : 12 deactivateSS OPERATION ARGUMENT ss-ForBS SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ), basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ... , longFTN-Supported [4] IMPLICIT NULL OPTIONAL} RESULT ss-Info CHOICE { forwardingInfo [0] IMPLICIT SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ) OPTIONAL, forwardingFeatureList SEQUENCE ( SIZE( 1 .. 13 ) ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ),
3174
3GPP
3175 Release 4
20592 20593 20594 20595 20596 20597 20598 20599 20600 20601 20602 20603 20604 20605 20606 20607 20608 20609 20610 20611 20612 20613 20614 20615 20616 20617 20618 20619 20620 20621 20622 20623 20624 20625 20626 20627 20628 20629 20630 20631 20632 20633 20634 20635 20636 20637 20638 20639 20640 20641 20642 20643 20644 20645 20646 20647 20648 20649 20650 20651 20652 20653 20654 20655 20656 20657 20658 20659 20660 20661 20662 20663 20664 20665 20666 20667 20668
1202
3GPP TS 29.002 V4.17.0 (2006-06)
teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, forwardedToNumber [5] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, forwardedToSubaddress [8] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, forwardingOptions [6] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, noReplyConditionTime [7] IMPLICIT INTEGER ( 5 .. 30 ) OPTIONAL, ... , longForwardedToNumber [9] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 15 ) ) OPTIONAL}, ... }, callBarringInfo [1] IMPLICIT SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ) OPTIONAL, callBarringFeatureList SEQUENCE ( SIZE( 1 .. 13 ) ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ... }, ... }, ss-Data [3] IMPLICIT SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ss-SubscriptionOption CHOICE { cliRestrictionOption [2] IMPLICIT ENUMERATED { permanent ( 0 ), temporaryDefaultRestricted ( 1 ), temporaryDefaultAllowed ( 2 ) }, overrideCategory [1] IMPLICIT ENUMERATED { overrideEnabled ( 0 ), overrideDisabled ( 1 ) }} OPTIONAL, basicServiceGroupList SEQUENCE ( SIZE( 1 .. 13 ) ) OF CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ... , defaultPriority INTEGER ( 0 .. 15 ) OPTIONAL, nbrUser [5] IMPLICIT INTEGER ( 1 .. 7 ) OPTIONAL}} ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- bearerServiceNotProvisioned -- localValue : 10, -- teleserviceNotProvisioned -- localValue : 11, -- callBarred -- localValue : 13, -- illegalSS-Operation -- localValue : 16, -- ss-ErrorStatus -- localValue : 17, -- ss-SubscriptionViolation -- localValue : 19, -- negativePW-Check -- localValue : 38, -- numberOfPW-AttemptsViolation -- localValue : 43} ::= localValue : 13 interrogateSS OPERATION ARGUMENT ss-ForBS SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ), basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ... , longFTN-Supported [4] IMPLICIT NULL OPTIONAL} RESULT interrogateSS-Res CHOICE { ss-Status [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ), basicServiceGroupList [2] IMPLICIT SEQUENCE ( SIZE( 1 .. 13 ) ) OF CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )}, forwardingFeatureList [3] IMPLICIT SEQUENCE ( SIZE( 1 .. 13 ) ) OF SEQUENCE { basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, forwardedToNumber [5] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, forwardedToSubaddress [8] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, forwardingOptions [6] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, noReplyConditionTime [7] IMPLICIT INTEGER ( 5 .. 30 ) OPTIONAL,
3176
3GPP
3177 Release 4
20669 20670 20671 20672 20673 20674 20675 20676 20677 20678 20679 20680 20681 20682 20683 20684 20685 20686 20687 20688 20689 20690 20691 20692 20693 20694 20695 20696 20697 20698 20699 20700 20701 20702 20703 20704 20705 20706 20707 20708 20709 20710 20711 20712 20713 20714 20715 20716 20717 20718 20719 20720 20721 20722 20723 20724 20725 20726 20727 20728 20729 20730 20731 20732 20733 20734 20735 20736 20737 20738 20739 20740 20741 20742 20743 20744 20745
1203
3GPP TS 29.002 V4.17.0 (2006-06)
... , longForwardedToNumber [9] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 15 ) ) OPTIONAL}, genericServiceInfo [4] IMPLICIT SEQUENCE { ss-Status OCTET STRING ( SIZE( 1 ) ), cliRestrictionOption ENUMERATED { permanent ( 0 ), temporaryDefaultRestricted ( 1 ), temporaryDefaultAllowed ( 2 ) } OPTIONAL, ... , maximumEntitledPriority [0] IMPLICIT INTEGER ( 0 .. 15 ) OPTIONAL, defaultPriority [1] IMPLICIT INTEGER ( 0 .. 15 ) OPTIONAL, ccbs-FeatureList [2] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF SEQUENCE { ccbs-Index [0] IMPLICIT INTEGER ( 1 .. 5 ) OPTIONAL, b-subscriberNumber [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, b-subscriberSubaddress [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, basicServiceGroup [3] CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ... } OPTIONAL, nbrSB [3] IMPLICIT INTEGER ( 2 .. 7 ) OPTIONAL, nbrUser [4] IMPLICIT INTEGER ( 1 .. 7 ) OPTIONAL, nbrSN [5] IMPLICIT INTEGER ( 1 .. 7 ) OPTIONAL}} ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- bearerServiceNotProvisioned -- localValue : 10, -- teleserviceNotProvisioned -- localValue : 11, -- callBarred -- localValue : 13, -- illegalSS-Operation -- localValue : 16, -- ss-NotAvailable -- localValue : 18} ::= localValue : 14 processUnstructuredSS-Request OPERATION ARGUMENT ussd-Arg SEQUENCE { ussd-DataCodingScheme OCTET STRING ( SIZE( 1 ) ), ussd-String OCTET STRING ( SIZE( 1 .. 160 ) ), ... , alertingPattern OCTET STRING ( SIZE( 1 ) ) OPTIONAL, msisdn [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL} RESULT ussd-Res SEQUENCE { ussd-DataCodingScheme OCTET STRING ( SIZE( 1 ) ), ussd-String OCTET STRING ( SIZE( 1 .. 160 ) ), ... } ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- unknownAlphabet -- localValue : 71, -- callBarred -- localValue : 13} ::= localValue : 59 unstructuredSS-Request OPERATION ARGUMENT ussd-Arg SEQUENCE { ussd-DataCodingScheme OCTET STRING ( SIZE( 1 ) ), ussd-String OCTET STRING ( SIZE( 1 .. 160 ) ), ... , alertingPattern OCTET STRING ( SIZE( 1 ) ) OPTIONAL, msisdn [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL} RESULT ussd-Res SEQUENCE { ussd-DataCodingScheme OCTET STRING ( SIZE( 1 ) ), ussd-String OCTET STRING ( SIZE( 1 .. 160 ) ), ... } ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- absentSubscriber -- localValue : 27, -- illegalSubscriber -- localValue : 9, -- illegalEquipment -- localValue : 12, -- unknownAlphabet -- localValue : 71, -- ussd-Busy -- localValue : 72}
3178
3GPP
3179 Release 4
20746 20747 20748 20749 20750 20751 20752 20753 20754 20755 20756 20757 20758 20759 20760 20761 20762 20763 20764 20765 20766 20767 20768 20769 20770 20771 20772 20773 20774 20775 20776 20777 20778 20779 20780 20781 20782 20783 20784 20785 20786 20787 20788 20789 20790 20791 20792 20793 20794 20795 20796 20797 20798 20799 20800 20801 20802 20803 20804 20805 20806 20807 20808 20809 20810 20811 20812 20813 20814 20815 20816 20817 20818 20819 20820 20821 20822
1204
3GPP TS 29.002 V4.17.0 (2006-06)
::= localValue : 60 unstructuredSS-Notify OPERATION ARGUMENT ussd-Arg SEQUENCE { ussd-DataCodingScheme OCTET STRING ( SIZE( 1 ) ), ussd-String OCTET STRING ( SIZE( 1 .. 160 ) ), ... , alertingPattern OCTET STRING ( SIZE( 1 ) ) OPTIONAL, msisdn [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL} ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- absentSubscriber -- localValue : 27, -- illegalSubscriber -- localValue : 9, -- illegalEquipment -- localValue : 12, -- unknownAlphabet -- localValue : 71, -- ussd-Busy -- localValue : 72} ::= localValue : 61 registerPassword OPERATION ARGUMENT ss-Code OCTET STRING ( SIZE( 1 ) ) RESULT newPassword NumericString ( FROM ("0"|"1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9" )) (SIZE( 4 ) ) ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- callBarred -- localValue : 13, -- ss-SubscriptionViolation -- localValue : 19, -- pw-RegistrationFailure -- localValue : 37, -- negativePW-Check -- localValue : 38, -- numberOfPW-AttemptsViolation -- localValue : 43} LINKED { -- getPassword -- localValue : 18} ::= localValue : 17 getPassword OPERATION ARGUMENT guidanceInfo ENUMERATED { enterPW ( 0 ), enterNewPW ( 1 ), enterNewPW-Again ( 2 ) } RESULT currentPassword NumericString ( FROM ("0"|"1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9" )) (SIZE( 4 ) ) ::= localValue : 18 registerCC-Entry OPERATION ARGUMENT registerCC-EntryArg SEQUENCE { ss-Code [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ), ccbs-Data [1] IMPLICIT SEQUENCE { ccbs-Feature [0] IMPLICIT SEQUENCE { ccbs-Index [0] IMPLICIT INTEGER ( 1 .. 5 ) OPTIONAL, b-subscriberNumber [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, b-subscriberSubaddress [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, basicServiceGroup [3] CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ... }, translatedB-Number [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), serviceIndicator [2] IMPLICIT BIT STRING { clir-invoked (0 ), camel-invoked (1 )} ( SIZE( 2 .. 32 ) ) OPTIONAL, callInfo [3] IMPLICIT SEQUENCE { protocolId ENUMERATED { gsm-0408 ( 1 ), gsm-0806 ( 2 ), gsm-BSSMAP ( 3 ), ets-300102-1 ( 4 ) }, signalInfo OCTET STRING ( SIZE( 1 .. 200 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( {
3180
3GPP
3181 Release 4
20823 20824 20825 20826 20827 20828 20829 20830 20831 20832 20833 20834 20835 20836 20837 20838 20839 20840 20841 20842 20843 20844 20845 20846 20847 20848 20849 20850 20851 20852 20853 20854 20855 20856 20857 20858 20859 20860 20861 20862 20863 20864 20865 20866 20867 20868 20869 20870 20871 20872 20873 20874 20875 20876 20877 20878 20879 20880 20881 20882 20883 20884 20885 20886 20887 20888 20889 20890 20891 20892 20893 20894 20895 20896 20897 20898 20899
1205
3GPP TS 29.002 V4.17.0 (2006-06)
, ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, networkSignalInfo [4] IMPLICIT SEQUENCE { protocolId ENUMERATED { gsm-0408 ( 1 ), gsm-0806 ( 2 ), gsm-BSSMAP ( 3 ), ets-300102-1 ( 4 ) }, signalInfo OCTET STRING ( SIZE( 1 .. 200 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, ... } OPTIONAL, ... } RESULT registerCC-EntryRes SEQUENCE { ccbs-Feature [0] IMPLICIT SEQUENCE { ccbs-Index [0] IMPLICIT INTEGER ( 1 .. 5 ) OPTIONAL, b-subscriberNumber [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, b-subscriberSubaddress [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, basicServiceGroup [3] CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- callBarred -- localValue : 13, -- illegalSS-Operation -- localValue : 16, -- ss-ErrorStatus -- localValue : 17, -- ss-Incompatibility -- localValue : 20, -- shortTermDenial -- localValue : 29, -- longTermDenial -- localValue : 30, -- facilityNotSupported -- localValue : 21} ::= localValue : 76 eraseCC-Entry OPERATION ARGUMENT eraseCC-EntryArg SEQUENCE { ss-Code [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ), ccbs-Index [1] IMPLICIT INTEGER ( 1 .. 5 ) OPTIONAL, ... } RESULT eraseCC-EntryRes SEQUENCE { ss-Code [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ), ss-Status [1] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- callBarred -- localValue : 13, -- illegalSS-Operation -- localValue : 16, -- ss-ErrorStatus -- localValue : 17} ::= localValue : 77 sendRoutingInfoForSM OPERATION ARGUMENT
3182
3GPP
3183 Release 4
20900 20901 20902 20903 20904 20905 20906 20907 20908 20909 20910 20911 20912 20913 20914 20915 20916 20917 20918 20919 20920 20921 20922 20923 20924 20925 20926 20927 20928 20929 20930 20931 20932 20933 20934 20935 20936 20937 20938 20939 20940 20941 20942 20943 20944 20945 20946 20947 20948 20949 20950 20951 20952 20953 20954 20955 20956 20957 20958 20959 20960 20961 20962 20963 20964 20965 20966 20967 20968 20969 20970 20971 20972 20973 20974 20975 20976
1206
3GPP TS 29.002 V4.17.0 (2006-06)
routingInfoForSM-Arg SEQUENCE { msisdn [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), sm-RP-PRI [1] IMPLICIT BOOLEAN, serviceCentreAddress [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ), extensionContainer [6] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , gprsSupportIndicator [7] IMPLICIT NULL OPTIONAL, sm-RP-MTI [8] IMPLICIT INTEGER ( 0 .. 10 ) OPTIONAL, sm-RP-SMEA [9] IMPLICIT OCTET STRING ( SIZE( 1 .. 12 ) ) OPTIONAL} RESULT routingInfoForSM-Res SEQUENCE { imsi OCTET STRING ( SIZE( 3 .. 8 ) ), locationInfoWithLMSI [0] IMPLICIT SEQUENCE { networkNode-Number [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), lmsi OCTET STRING ( SIZE( 4 ) ) OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , gprsNodeIndicator [5] IMPLICIT NULL OPTIONAL, additional-Number [6] CHOICE { msc-Number [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), sgsn-Number [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) )} OPTIONAL}, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- facilityNotSupported -- localValue : 21, -- unknownSubscriber -- localValue : 1, -- teleserviceNotProvisioned -- localValue : 11, -- callBarred -- localValue : 13, -- absentsubscriberSM -- localValue : 6} ::= localValue : 45 mo-forwardSM OPERATION ARGUMENT mo-forwardSM-Arg SEQUENCE { sm-RP-DA CHOICE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), lmsi [1] IMPLICIT OCTET STRING ( SIZE( 4 ) ), serviceCentreAddressDA [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ), noSM-RP-DA [5] IMPLICIT NULL}, sm-RP-OA CHOICE { msisdn [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ),
3184
3GPP
3185 Release 4
20977 20978 20979 20980 20981 20982 20983 20984 20985 20986 20987 20988 20989 20990 20991 20992 20993 20994 20995 20996 20997 20998 20999 21000 21001 21002 21003 21004 21005 21006 21007 21008 21009 21010 21011 21012 21013 21014 21015 21016 21017 21018 21019 21020 21021 21022 21023 21024 21025 21026 21027 21028 21029 21030 21031 21032 21033 21034 21035 21036 21037 21038 21039 21040 21041 21042 21043 21044 21045 21046 21047 21048 21049 21050 21051 21052 21053
1207
3GPP TS 29.002 V4.17.0 (2006-06)
serviceCentreAddressOA [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ), noSM-RP-OA [5] IMPLICIT NULL}, sm-RP-UI OCTET STRING ( SIZE( 1 .. 200 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , imsi OCTET STRING ( SIZE( 3 .. 8 ) ) OPTIONAL} RESULT mo-forwardSM-Res SEQUENCE { sm-RP-UI OCTET STRING ( SIZE( 1 .. 200 ) ) OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- unexpectedDataValue -- localValue : 36, -- facilityNotSupported -- localValue : 21, -- sm-DeliveryFailure -- localValue : 32} ::= localValue : 46 mt-forwardSM OPERATION ARGUMENT mt-forwardSM-Arg SEQUENCE { sm-RP-DA CHOICE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), lmsi [1] IMPLICIT OCTET STRING ( SIZE( 4 ) ), serviceCentreAddressDA [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ), noSM-RP-DA [5] IMPLICIT NULL}, sm-RP-OA CHOICE { msisdn [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), serviceCentreAddressOA [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ), noSM-RP-OA [5] IMPLICIT NULL}, sm-RP-UI OCTET STRING ( SIZE( 1 .. 200 ) ), moreMessagesToSend NULL OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT mt-forwardSM-Res SEQUENCE { sm-RP-UI OCTET STRING ( SIZE( 1 .. 200 ) ) OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( {
3186
3GPP
3187 Release 4
21054 21055 21056 21057 21058 21059 21060 21061 21062 21063 21064 21065 21066 21067 21068 21069 21070 21071 21072 21073 21074 21075 21076 21077 21078 21079 21080 21081 21082 21083 21084 21085 21086 21087 21088 21089 21090 21091 21092 21093 21094 21095 21096 21097 21098 21099 21100 21101 21102 21103 21104 21105 21106 21107 21108 21109 21110 21111 21112 21113 21114 21115 21116 21117 21118 21119 21120 21121 21122 21123 21124 21125 21126 21127 21128 21129 21130
1208
3GPP TS 29.002 V4.17.0 (2006-06)
, ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- facilityNotSupported -- localValue : 21, -- unidentifiedSubscriber -- localValue : 5, -- illegalSubscriber -- localValue : 9, -- illegalEquipment -- localValue : 12, -- subscriberBusyForMT-SMS -- localValue : 31, -- sm-DeliveryFailure -- localValue : 32, -- absentsubscriberSM -- localValue : 6} ::= localValue : 44 reportSM-DeliveryStatus OPERATION ARGUMENT reportSM-DeliveryStatusArg SEQUENCE { msisdn OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), serviceCentreAddress OCTET STRING ( SIZE( 1 .. 20 ) ), sm-DeliveryOutcome ENUMERATED { memoryCapacityExceeded ( 0 ), absentSubscriber ( 1 ), successfulTransfer ( 2 ) }, absentSubscriberDiagnosticSM [0] IMPLICIT INTEGER ( 0 .. 255 ) OPTIONAL, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , gprsSupportIndicator [2] IMPLICIT NULL OPTIONAL, deliveryOutcomeIndicator [3] IMPLICIT NULL OPTIONAL, additionalSM-DeliveryOutcome [4] IMPLICIT ENUMERATED { memoryCapacityExceeded ( 0 ), absentSubscriber ( 1 ), successfulTransfer ( 2 ) } OPTIONAL, additionalAbsentSubscriberDiagnosticSM [5] IMPLICIT INTEGER ( 0 .. 255 ) OPTIONAL} RESULT reportSM-DeliveryStatusRes SEQUENCE { storedMSISDN OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- unknownSubscriber -- localValue : 1, -- messageWaitingListFull -- localValue : 33} ::= localValue : 47 informServiceCentre OPERATION ARGUMENT informServiceCentreArg SEQUENCE { storedMSISDN OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, mw-Status BIT STRING {
3188
3GPP
3189 Release 4
21131 21132 21133 21134 21135 21136 21137 21138 21139 21140 21141 21142 21143 21144 21145 21146 21147 21148 21149 21150 21151 21152 21153 21154 21155 21156 21157 21158 21159 21160 21161 21162 21163 21164 21165 21166 21167 21168 21169 21170 21171 21172 21173 21174 21175 21176 21177 21178 21179 21180 21181 21182 21183 21184 21185 21186 21187 21188 21189 21190 21191 21192 21193 21194 21195 21196 21197 21198 21199 21200 21201 21202 21203 21204 21205 21206 21207
1209
3GPP TS 29.002 V4.17.0 (2006-06)
sc-AddressNotIncluded (0 ), mnrf-Set (1 ), mcef-Set (2 ), mnrg-Set (3 )} ( SIZE( 6 .. 16 ) ) OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , absentSubscriberDiagnosticSM INTEGER ( 0 .. 255 ) OPTIONAL, additionalAbsentSubscriberDiagnosticSM [0] IMPLICIT INTEGER ( 0 .. 255 ) OPTIONAL} ::= localValue : 63 alertServiceCentre OPERATION ARGUMENT alertServiceCentreArg SEQUENCE { msisdn OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), serviceCentreAddress OCTET STRING ( SIZE( 1 .. 20 ) ), ... } ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36} ::= localValue : 64 readyForSM OPERATION ARGUMENT readyForSM-Arg SEQUENCE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), alertReason ENUMERATED { ms-Present ( 0 ), memoryAvailable ( 1 ) }, alertReasonIndicator NULL OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT readyForSM-Res SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- facilityNotSupported -- localValue : 21, -- unknownSubscriber -- localValue : 1} ::= localValue : 66 provideSubscriberInfo OPERATION
3190
3GPP
3191 Release 4
21208 21209 21210 21211 21212 21213 21214 21215 21216 21217 21218 21219 21220 21221 21222 21223 21224 21225 21226 21227 21228 21229 21230 21231 21232 21233 21234 21235 21236 21237 21238 21239 21240 21241 21242 21243 21244 21245 21246 21247 21248 21249 21250 21251 21252 21253 21254 21255 21256 21257 21258 21259 21260 21261 21262 21263 21264 21265 21266 21267 21268 21269 21270 21271 21272 21273 21274 21275 21276 21277 21278 21279 21280 21281 21282 21283 21284
1210
3GPP TS 29.002 V4.17.0 (2006-06)
ARGUMENT provideSubscriberInfoArg SEQUENCE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), lmsi [1] IMPLICIT OCTET STRING ( SIZE( 4 ) ) OPTIONAL, requestedInfo [2] IMPLICIT SEQUENCE { locationInformation [0] IMPLICIT NULL OPTIONAL, subscriberState [1] IMPLICIT NULL OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , currentLocation [3] IMPLICIT NULL OPTIONAL}, extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT provideSubscriberInfoRes SEQUENCE { subscriberInfo SEQUENCE { locationInformation [0] IMPLICIT SEQUENCE { ageOfLocationInformation INTEGER ( 0 .. 32767 ) OPTIONAL, geographicalInformation [0] IMPLICIT OCTET STRING ( SIZE( 8 ) ) OPTIONAL, vlr-number [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, locationNumber [2] IMPLICIT OCTET STRING ( SIZE( 2 .. 10 ) ) OPTIONAL, cellGlobalIdOrServiceAreaIdOrLAI [3] CHOICE { cellGlobalIdOrServiceAreaIdFixedLength [0] IMPLICIT OCTET STRING ( SIZE( 7 ) ), laiFixedLength [1] IMPLICIT OCTET STRING ( SIZE( 5 ) )} OPTIONAL, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , selectedLSA-Id [5] IMPLICIT OCTET STRING ( SIZE( 3 ) ) OPTIONAL, msc-Number [6] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, geodeticInformation [7] IMPLICIT OCTET STRING ( SIZE( 10 ) ) OPTIONAL, currentLocationRetrieved [8] IMPLICIT NULL OPTIONAL, sai-Present [9] IMPLICIT NULL OPTIONAL} OPTIONAL, subscriberState [1] CHOICE { assumedIdle [0] IMPLICIT NULL, camelBusy [1] IMPLICIT NULL, netDetNotReachable ENUMERATED { msPurged ( 0 ), imsiDetached ( 1 ), restrictedArea ( 2 ), notRegistered ( 3 ) }, notProvidedFromVLR [2] IMPLICIT NULL} OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { ,
3192
3GPP
3193 Release 4
21285 21286 21287 21288 21289 21290 21291 21292 21293 21294 21295 21296 21297 21298 21299 21300 21301 21302 21303 21304 21305 21306 21307 21308 21309 21310 21311 21312 21313 21314 21315 21316 21317 21318 21319 21320 21321 21322 21323 21324 21325 21326 21327 21328 21329 21330 21331 21332 21333 21334 21335 21336 21337 21338 21339 21340 21341 21342 21343 21344 21345 21346 21347 21348 21349 21350 21351 21352 21353 21354 21355 21356 21357 21358 21359 21360 21361
1211
3GPP TS 29.002 V4.17.0 (2006-06)
...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36} ::= localValue : 70 anyTimeInterrogation OPERATION ARGUMENT anyTimeInterrogationArg SEQUENCE { subscriberIdentity [0] CHOICE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), msisdn [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) )}, requestedInfo [1] IMPLICIT SEQUENCE { locationInformation [0] IMPLICIT NULL OPTIONAL, subscriberState [1] IMPLICIT NULL OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , currentLocation [3] IMPLICIT NULL OPTIONAL}, gsmSCF-Address [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT anyTimeInterrogationRes SEQUENCE { subscriberInfo SEQUENCE { locationInformation [0] IMPLICIT SEQUENCE { ageOfLocationInformation INTEGER ( 0 .. 32767 ) OPTIONAL, geographicalInformation [0] IMPLICIT OCTET STRING ( SIZE( 8 ) ) OPTIONAL, vlr-number [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, locationNumber [2] IMPLICIT OCTET STRING ( SIZE( 2 .. 10 ) ) OPTIONAL, cellGlobalIdOrServiceAreaIdOrLAI [3] CHOICE { cellGlobalIdOrServiceAreaIdFixedLength [0] IMPLICIT OCTET STRING ( SIZE( 7 ) ), laiFixedLength [1] IMPLICIT OCTET STRING ( SIZE( 5 ) )} OPTIONAL, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE {
3194
3GPP
3195 Release 4
21362 21363 21364 21365 21366 21367 21368 21369 21370 21371 21372 21373 21374 21375 21376 21377 21378 21379 21380 21381 21382 21383 21384 21385 21386 21387 21388 21389 21390 21391 21392 21393 21394 21395 21396 21397 21398 21399 21400 21401 21402 21403 21404 21405 21406 21407 21408 21409 21410 21411 21412 21413 21414 21415 21416 21417 21418 21419 21420 21421 21422 21423 21424 21425 21426 21427 21428 21429 21430 21431 21432 21433 21434 21435 21436 21437 21438
1212
3GPP TS 29.002 V4.17.0 (2006-06)
extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , selectedLSA-Id [5] IMPLICIT OCTET STRING ( SIZE( 3 ) ) OPTIONAL, msc-Number [6] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, geodeticInformation [7] IMPLICIT OCTET STRING ( SIZE( 10 ) ) OPTIONAL, currentLocationRetrieved [8] IMPLICIT NULL OPTIONAL, sai-Present [9] IMPLICIT NULL OPTIONAL} OPTIONAL, subscriberState [1] CHOICE { assumedIdle [0] IMPLICIT NULL, camelBusy [1] IMPLICIT NULL, netDetNotReachable ENUMERATED { msPurged ( 0 ), imsiDetached ( 1 ), restrictedArea ( 2 ), notRegistered ( 3 ) }, notProvidedFromVLR [2] IMPLICIT NULL} OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- ati-NotAllowed -- localValue : 49, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- unknownSubscriber -- localValue : 1} ::= localValue : 71 anyTimeSubscriptionInterrogation OPERATION ARGUMENT anyTimeSubscriptionInterrogationArg SEQUENCE { subscriberIdentity [0] CHOICE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), msisdn [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) )}, requestedSubscriptionInfo [1] IMPLICIT SEQUENCE { requestedSS-Info [1] IMPLICIT SEQUENCE { ss-Code OCTET STRING ( SIZE( 1 ) ), basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ... , longFTN-Supported [4] IMPLICIT NULL OPTIONAL} OPTIONAL, odb [2] IMPLICIT NULL OPTIONAL, requestedCAMEL-SubscriptionInfo [3] IMPLICIT ENUMERATED { o-CSI ( 0 ), t-CSI ( 1 ), vt-CSI ( 2 ),
3196
3GPP
3197 Release 4
21439 21440 21441 21442 21443 21444 21445 21446 21447 21448 21449 21450 21451 21452 21453 21454 21455 21456 21457 21458 21459 21460 21461 21462 21463 21464 21465 21466 21467 21468 21469 21470 21471 21472 21473 21474 21475 21476 21477 21478 21479 21480 21481 21482 21483 21484 21485 21486 21487 21488 21489 21490 21491 21492 21493 21494 21495 21496 21497 21498 21499 21500 21501 21502 21503 21504 21505 21506 21507 21508 21509 21510 21511 21512 21513 21514 21515
1213
3GPP TS 29.002 V4.17.0 (2006-06)
tif-CSI ( 3 ), gprs-CSI ( 4 ), sms-CSI ( 5 ), ss-CSI ( 6 ), m-CSI ( 7 ), d-csi ( 8 ) } OPTIONAL, supportedVLR-CAMEL-Phases [4] IMPLICIT NULL OPTIONAL, supportedSGSN-CAMEL-Phases [5] IMPLICIT NULL OPTIONAL, extensionContainer [6] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, gsmSCF-Address [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, longFTN-Supported [4] IMPLICIT NULL OPTIONAL, ... } RESULT anyTimeSubscriptionInterrogationRes SEQUENCE { callForwardingData [1] IMPLICIT SEQUENCE { forwardingFeatureList SEQUENCE ( SIZE( 1 .. 32 ) ) OF SEQUENCE { basicService CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), forwardedToNumber [5] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, forwardedToSubaddress [8] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, forwardingOptions [6] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ) OPTIONAL, noReplyConditionTime [7] IMPLICIT INTEGER ( 1 .. 100 ) OPTIONAL, extensionContainer [9] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , longForwardedToNumber [10] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 15 ) ) OPTIONAL}, notificationToCSE NULL OPTIONAL, extensionContainer [0] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL,
3198
3GPP
3199 Release 4
21516 21517 21518 21519 21520 21521 21522 21523 21524 21525 21526 21527 21528 21529 21530 21531 21532 21533 21534 21535 21536 21537 21538 21539 21540 21541 21542 21543 21544 21545 21546 21547 21548 21549 21550 21551 21552 21553 21554 21555 21556 21557 21558 21559 21560 21561 21562 21563 21564 21565 21566 21567 21568 21569 21570 21571 21572 21573 21574 21575 21576 21577 21578 21579 21580 21581 21582 21583 21584 21585 21586 21587 21588 21589 21590 21591 21592
1214
3GPP TS 29.002 V4.17.0 (2006-06)
callBarringData [2] IMPLICIT SEQUENCE { callBarringFeatureList SEQUENCE ( SIZE( 1 .. 32 ) ) OF SEQUENCE { basicService CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, password NumericString ( FROM ("0"|"1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9" )) (SIZE( 4 ) ) OPTIONAL, wrongPasswordAttemptsCounter INTEGER ( 0 .. 4 ) OPTIONAL, notificationToCSE NULL OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, odb-Info [3] IMPLICIT SEQUENCE { odb-Data SEQUENCE { 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 ) ), odb-HPLMN-Data BIT STRING { plmn-SpecificBarringType1 (0 ), plmn-SpecificBarringType2 (1 ), plmn-SpecificBarringType3 (2 ), plmn-SpecificBarringType4 (3 )} ( SIZE( 4 .. 32 ) ) OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( {
3200
3GPP
3201 Release 4
21593 21594 21595 21596 21597 21598 21599 21600 21601 21602 21603 21604 21605 21606 21607 21608 21609 21610 21611 21612 21613 21614 21615 21616 21617 21618 21619 21620 21621 21622 21623 21624 21625 21626 21627 21628 21629 21630 21631 21632 21633 21634 21635 21636 21637 21638 21639 21640 21641 21642 21643 21644 21645 21646 21647 21648 21649 21650 21651 21652 21653 21654 21655 21656 21657 21658 21659 21660 21661 21662 21663 21664 21665 21666 21667 21668 21669
1215
3GPP TS 29.002 V4.17.0 (2006-06)
, ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, notificationToCSE NULL OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camel-SubscriptionInfo [4] IMPLICIT SEQUENCE { o-CSI [0] IMPLICIT SEQUENCE { o-BcsmCamelTDPDataList SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { o-BcsmTriggerDetectionPoint ENUMERATED { collectedInfo ( 2 ), ... , routeSelectFailure ( 4 ) }, serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling [1] IMPLICIT ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , camelCapabilityHandling [0] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, notificationToCSE [1] IMPLICIT NULL OPTIONAL, csiActive [2] IMPLICIT NULL OPTIONAL} OPTIONAL, o-BcsmCamelTDP-CriteriaList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { o-BcsmTriggerDetectionPoint ENUMERATED { collectedInfo ( 2 ), ... , routeSelectFailure ( 4 ) }, destinationNumberCriteria [0] IMPLICIT SEQUENCE { matchType [0] IMPLICIT ENUMERATED { inhibiting ( 0 ), enabling ( 1 ) }, destinationNumberList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF
3202
3GPP
3203 Release 4
21670 21671 21672 21673 21674 21675 21676 21677 21678 21679 21680 21681 21682 21683 21684 21685 21686 21687 21688 21689 21690 21691 21692 21693 21694 21695 21696 21697 21698 21699 21700 21701 21702 21703 21704 21705 21706 21707 21708 21709 21710 21711 21712 21713 21714 21715 21716 21717 21718 21719 21720 21721 21722 21723 21724 21725 21726 21727 21728 21729 21730 21731 21732 21733 21734 21735 21736 21737 21738 21739 21740 21741 21742 21743 21744 21745 21746
1216
3GPP TS 29.002 V4.17.0 (2006-06)
OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, destinationNumberLengthList [2] IMPLICIT SEQUENCE ( SIZE( 1 .. 3 ) ) OF INTEGER ( 1 .. 15 ) OPTIONAL, ... } OPTIONAL, basicServiceCriteria [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, callTypeCriteria [2] IMPLICIT ENUMERATED { forwarded ( 0 ), notForwarded ( 1 ) } OPTIONAL, ... , o-CauseValueCriteria [3] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF OCTET STRING ( SIZE( 1 ) ) OPTIONAL, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL} OPTIONAL, d-CSI [2] IMPLICIT SEQUENCE { dp-AnalysedInfoCriteriaList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { dialledNumber OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camelCapabilityHandling [1] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [3] IMPLICIT NULL OPTIONAL, csi-Active [4] IMPLICIT NULL OPTIONAL, ... } OPTIONAL, t-CSI [3] IMPLICIT SEQUENCE { t-BcsmCamelTDPDataList SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { t-BcsmTriggerDetectionPoint ENUMERATED { termAttemptAuthorized ( 12 ), ... , tBusy ( 13 ), tNoAnswer ( 14 ) }, serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling [1] IMPLICIT ENUMERATED { continueCall ( 0 ),
3204
3GPP
3205 Release 4
21747 21748 21749 21750 21751 21752 21753 21754 21755 21756 21757 21758 21759 21760 21761 21762 21763 21764 21765 21766 21767 21768 21769 21770 21771 21772 21773 21774 21775 21776 21777 21778 21779 21780 21781 21782 21783 21784 21785 21786 21787 21788 21789 21790 21791 21792 21793 21794 21795 21796 21797 21798 21799 21800 21801 21802 21803 21804 21805 21806 21807 21808 21809 21810 21811 21812 21813 21814 21815 21816 21817 21818 21819 21820 21821 21822 21823
1217
3GPP TS 29.002 V4.17.0 (2006-06)
releaseCall ( 1 ), ... }, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , camelCapabilityHandling [0] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, notificationToCSE [1] IMPLICIT NULL OPTIONAL, csi-Active [2] IMPLICIT NULL OPTIONAL} OPTIONAL, t-BCSM-CAMEL-TDP-CriteriaList [4] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { t-BCSM-TriggerDetectionPoint ENUMERATED { termAttemptAuthorized ( 12 ), ... , tBusy ( 13 ), tNoAnswer ( 14 ) }, basicServiceCriteria [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, t-CauseValueCriteria [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ... } OPTIONAL, vt-CSI [5] IMPLICIT SEQUENCE { t-BcsmCamelTDPDataList SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { t-BcsmTriggerDetectionPoint ENUMERATED { termAttemptAuthorized ( 12 ), ... , tBusy ( 13 ), tNoAnswer ( 14 ) }, serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling [1] IMPLICIT ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { ,
3206
3GPP
3207 Release 4
21824 21825 21826 21827 21828 21829 21830 21831 21832 21833 21834 21835 21836 21837 21838 21839 21840 21841 21842 21843 21844 21845 21846 21847 21848 21849 21850 21851 21852 21853 21854 21855 21856 21857 21858 21859 21860 21861 21862 21863 21864 21865 21866 21867 21868 21869 21870 21871 21872 21873 21874 21875 21876 21877 21878 21879 21880 21881 21882 21883 21884 21885 21886 21887 21888 21889 21890 21891 21892 21893 21894 21895 21896 21897 21898 21899 21900
1218
3GPP TS 29.002 V4.17.0 (2006-06)
...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , camelCapabilityHandling [0] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, notificationToCSE [1] IMPLICIT NULL OPTIONAL, csi-Active [2] IMPLICIT NULL OPTIONAL} OPTIONAL, vt-BCSM-CAMEL-TDP-CriteriaList [6] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { t-BCSM-TriggerDetectionPoint ENUMERATED { termAttemptAuthorized ( 12 ), ... , tBusy ( 13 ), tNoAnswer ( 14 ) }, basicServiceCriteria [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, t-CauseValueCriteria [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ... } OPTIONAL, tif-CSI [7] IMPLICIT NULL OPTIONAL, tif-CSI-NotificationToCSE [8] IMPLICIT NULL OPTIONAL, gprs-CSI [9] IMPLICIT SEQUENCE { gprs-CamelTDPDataList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { gprs-TriggerDetectionPoint [0] IMPLICIT ENUMERATED { attach ( 1 ), attachChangeOfPosition ( 2 ), pdp-ContextEstablishment ( 11 ), pdp-ContextEstablishmentAcknowledgement ( 12 ), pdp-ContextChangeOfPosition ( 14 ), ... }, serviceKey [1] IMPLICIT INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultSessionHandling [3] IMPLICIT ENUMERATED { continueTransaction ( 0 ), releaseTransaction ( 1 ), ... }, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camelCapabilityHandling [1] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [3] IMPLICIT NULL OPTIONAL, csi-Active [4] IMPLICIT NULL OPTIONAL, ... } OPTIONAL, sms-CSI [10] IMPLICIT SEQUENCE { sms-CAMEL-TDP-DataList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { sms-TriggerDetectionPoint [0] IMPLICIT ENUMERATED { sms-CollectedInfo ( 1 ),
3208
3GPP
3209 Release 4
21901 21902 21903 21904 21905 21906 21907 21908 21909 21910 21911 21912 21913 21914 21915 21916 21917 21918 21919 21920 21921 21922 21923 21924 21925 21926 21927 21928 21929 21930 21931 21932 21933 21934 21935 21936 21937 21938 21939 21940 21941 21942 21943 21944 21945 21946 21947 21948 21949 21950 21951 21952 21953 21954 21955 21956 21957 21958 21959 21960 21961 21962 21963 21964 21965 21966 21967 21968 21969 21970 21971 21972 21973 21974 21975 21976 21977
1219
3GPP TS 29.002 V4.17.0 (2006-06)
... }, serviceKey [1] IMPLICIT INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultSMS-Handling [3] IMPLICIT ENUMERATED { continueTransaction ( 0 ), releaseTransaction ( 1 ), ... }, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camelCapabilityHandling [1] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [3] IMPLICIT NULL OPTIONAL, csi-Active [4] IMPLICIT NULL OPTIONAL, ... } OPTIONAL, ss-CSI [11] IMPLICIT SEQUENCE { ss-CamelData SEQUENCE { ss-EventList SEQUENCE ( SIZE( 1 .. 10 ) ) OF OCTET STRING ( SIZE( 1 ) ), gsmSCF-Address OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), extensionContainer [0] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , notificationToCSE [0] IMPLICIT NULL OPTIONAL, csi-Active [1] IMPLICIT NULL OPTIONAL} OPTIONAL, m-CSI [12] IMPLICIT SEQUENCE { mobilityTriggers SEQUENCE ( SIZE( 1 .. 10 ) ) OF OCTET STRING ( SIZE( 1 ) ), serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE {
3210
3GPP
3211 Release 4
21978 21979 21980 21981 21982 21983 21984 21985 21986 21987 21988 21989 21990 21991 21992 21993 21994 21995 21996 21997 21998 21999 22000 22001 22002 22003 22004 22005 22006 22007 22008 22009 22010 22011 22012 22013 22014 22015 22016 22017 22018 22019 22020 22021 22022 22023 22024 22025 22026 22027 22028 22029 22030 22031 22032 22033 22034 22035 22036 22037 22038 22039 22040 22041 22042 22043 22044 22045 22046 22047 22048 22049 22050 22051 22052 22053 22054
1220
3GPP TS 29.002 V4.17.0 (2006-06)
extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [2] IMPLICIT NULL OPTIONAL, csi-Active [3] IMPLICIT NULL OPTIONAL, ... } OPTIONAL, extensionContainer [13] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , specificCSIDeletedList [14] IMPLICIT BIT STRING { o-csi (0 ), ss-csi (1 ), tif-csi (2 ), d-csi (3 ), vt-csi (4 ), sms-csi (5 ), m-csi (6 ), gprs-csi (7 ), t-csi (8 )} ( SIZE( 8 .. 32 ) ) OPTIONAL} OPTIONAL, supportedVLR-CAMEL-Phases [5] IMPLICIT BIT STRING { phase1 (0 ), phase2 (1 ), phase3 (2 )} ( SIZE( 1 .. 16 ) ) OPTIONAL, supportedSGSN-CAMEL-Phases [6] IMPLICIT BIT STRING { phase1 (0 ), phase2 (1 ), phase3 (2 )} ( SIZE( 1 .. 16 ) ) OPTIONAL, extensionContainer [7] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- atsi-NotAllowed -- localValue : 60, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- unknownSubscriber -- localValue : 1, -- bearerServiceNotProvisioned -- localValue : 10, -- teleserviceNotProvisioned -- localValue : 11, -- callBarred -- localValue : 13, -- illegalSS-Operation -- localValue : 16, -- ss-NotAvailable -- localValue : 18, -- informationNotAvailable -- localValue : 62} ::= localValue : 62 anyTimeModification OPERATION ARGUMENT anyTimeModificationArg SEQUENCE { subscriberIdentity [0] CHOICE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), msisdn [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) )}, gsmSCF-Address [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), modificationRequestFor-CF-Info [2] IMPLICIT SEQUENCE {
3212
3GPP
3213 Release 4
22055 22056 22057 22058 22059 22060 22061 22062 22063 22064 22065 22066 22067 22068 22069 22070 22071 22072 22073 22074 22075 22076 22077 22078 22079 22080 22081 22082 22083 22084 22085 22086 22087 22088 22089 22090 22091 22092 22093 22094 22095 22096 22097 22098 22099 22100 22101 22102 22103 22104 22105 22106 22107 22108 22109 22110 22111 22112 22113 22114 22115 22116 22117 22118 22119 22120 22121 22122 22123 22124 22125 22126 22127 22128 22129 22130 22131
1221
3GPP TS 29.002 V4.17.0 (2006-06)
ss-Code [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ), basicService [1] CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, ss-Status [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ) OPTIONAL, forwardedToNumber [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) OPTIONAL, forwardedToSubaddress [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, noReplyConditionTime [5] IMPLICIT INTEGER ( 1 .. 100 ) OPTIONAL, modifyNotificationToCSE [6] IMPLICIT ENUMERATED { deactivate ( 0 ), activate ( 1 ) } OPTIONAL, extensionContainer [7] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, modificationRequestFor-CB-Info [3] IMPLICIT SEQUENCE { ss-Code [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ), basicService [1] CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, ss-Status [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ) OPTIONAL, password [3] IMPLICIT NumericString ( FROM ("0"|"1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9" )) (SIZE( 4 ) ) OPTIONAL, wrongPasswordAttemptsCounter [4] IMPLICIT INTEGER ( 0 .. 4 ) OPTIONAL, modifyNotificationToCSE [5] IMPLICIT ENUMERATED { deactivate ( 0 ), activate ( 1 ) } OPTIONAL, extensionContainer [6] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, modificationRequestFor-CSI [4] IMPLICIT SEQUENCE { requestedCamel-SubscriptionInfo [0] IMPLICIT ENUMERATED { o-CSI ( 0 ), t-CSI ( 1 ), vt-CSI ( 2 ), tif-CSI ( 3 ), gprs-CSI ( 4 ), sms-CSI ( 5 ), ss-CSI ( 6 ), m-CSI ( 7 ), d-csi ( 8 ) }, modifyNotificationToCSE [1] IMPLICIT ENUMERATED { deactivate ( 0 ), activate ( 1 ) } OPTIONAL, modifyCSI-State [2] IMPLICIT ENUMERATED { deactivate ( 0 ), activate ( 1 ) } OPTIONAL, extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL,
3214
3GPP
3215 Release 4
22132 22133 22134 22135 22136 22137 22138 22139 22140 22141 22142 22143 22144 22145 22146 22147 22148 22149 22150 22151 22152 22153 22154 22155 22156 22157 22158 22159 22160 22161 22162 22163 22164 22165 22166 22167 22168 22169 22170 22171 22172 22173 22174 22175 22176 22177 22178 22179 22180 22181 22182 22183 22184 22185 22186 22187 22188 22189 22190 22191 22192 22193 22194 22195 22196 22197 22198 22199 22200 22201 22202 22203 22204 22205 22206 22207 22208
1222
3GPP TS 29.002 V4.17.0 (2006-06)
... } OPTIONAL, extensionContainer [5] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, longFTN-Supported [6] IMPLICIT NULL OPTIONAL, ... } RESULT anyTimeModificationRes SEQUENCE { ss-InfoFor-CSE [0] CHOICE { forwardingInfoFor-CSE [0] IMPLICIT SEQUENCE { ss-Code [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ), forwardingFeatureList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 32 ) ) OF SEQUENCE { basicService CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), forwardedToNumber [5] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, forwardedToSubaddress [8] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, forwardingOptions [6] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ) OPTIONAL, noReplyConditionTime [7] IMPLICIT INTEGER ( 1 .. 100 ) OPTIONAL, extensionContainer [9] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , longForwardedToNumber [10] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 15 ) ) OPTIONAL}, notificationToCSE [2] IMPLICIT NULL OPTIONAL, extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, callBarringInfoFor-CSE [1] IMPLICIT SEQUENCE { ss-Code [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ), callBarringFeatureList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 32 ) ) OF SEQUENCE { basicService CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL,
3216
3GPP
3217 Release 4
22209 22210 22211 22212 22213 22214 22215 22216 22217 22218 22219 22220 22221 22222 22223 22224 22225 22226 22227 22228 22229 22230 22231 22232 22233 22234 22235 22236 22237 22238 22239 22240 22241 22242 22243 22244 22245 22246 22247 22248 22249 22250 22251 22252 22253 22254 22255 22256 22257 22258 22259 22260 22261 22262 22263 22264 22265 22266 22267 22268 22269 22270 22271 22272 22273 22274 22275 22276 22277 22278 22279 22280 22281 22282 22283 22284 22285
1223
3GPP TS 29.002 V4.17.0 (2006-06)
... } OPTIONAL, ... }, password [2] IMPLICIT NumericString ( FROM ("0"|"1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9" )) (SIZE( 4 ) ) OPTIONAL, wrongPasswordAttemptsCounter [3] IMPLICIT INTEGER ( 0 .. 4 ) OPTIONAL, notificationToCSE [4] IMPLICIT NULL OPTIONAL, extensionContainer [5] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }} OPTIONAL, camel-SubscriptionInfo [1] IMPLICIT SEQUENCE { o-CSI [0] IMPLICIT SEQUENCE { o-BcsmCamelTDPDataList SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { o-BcsmTriggerDetectionPoint ENUMERATED { collectedInfo ( 2 ), ... , routeSelectFailure ( 4 ) }, serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling [1] IMPLICIT ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , camelCapabilityHandling [0] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, notificationToCSE [1] IMPLICIT NULL OPTIONAL, csiActive [2] IMPLICIT NULL OPTIONAL} OPTIONAL, o-BcsmCamelTDP-CriteriaList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { o-BcsmTriggerDetectionPoint ENUMERATED { collectedInfo ( 2 ), ... , routeSelectFailure ( 4 ) }, destinationNumberCriteria [0] IMPLICIT SEQUENCE { matchType [0] IMPLICIT ENUMERATED { inhibiting ( 0 ), enabling ( 1 ) }, destinationNumberList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, destinationNumberLengthList [2] IMPLICIT SEQUENCE ( SIZE( 1 .. 3 ) ) OF INTEGER ( 1 .. 15 ) OPTIONAL, ... } OPTIONAL, basicServiceCriteria [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF
3218
3GPP
3219 Release 4
22286 22287 22288 22289 22290 22291 22292 22293 22294 22295 22296 22297 22298 22299 22300 22301 22302 22303 22304 22305 22306 22307 22308 22309 22310 22311 22312 22313 22314 22315 22316 22317 22318 22319 22320 22321 22322 22323 22324 22325 22326 22327 22328 22329 22330 22331 22332 22333 22334 22335 22336 22337 22338 22339 22340 22341 22342 22343 22344 22345 22346 22347 22348 22349 22350 22351 22352 22353 22354 22355 22356 22357 22358 22359 22360 22361 22362
1224
3GPP TS 29.002 V4.17.0 (2006-06)
CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, callTypeCriteria [2] IMPLICIT ENUMERATED { forwarded ( 0 ), notForwarded ( 1 ) } OPTIONAL, ... , o-CauseValueCriteria [3] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF OCTET STRING ( SIZE( 1 ) ) OPTIONAL, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL} OPTIONAL, d-CSI [2] IMPLICIT SEQUENCE { dp-AnalysedInfoCriteriaList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { dialledNumber OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camelCapabilityHandling [1] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [3] IMPLICIT NULL OPTIONAL, csi-Active [4] IMPLICIT NULL OPTIONAL, ... } OPTIONAL, t-CSI [3] IMPLICIT SEQUENCE { t-BcsmCamelTDPDataList SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { t-BcsmTriggerDetectionPoint ENUMERATED { termAttemptAuthorized ( 12 ), ... , tBusy ( 13 ), tNoAnswer ( 14 ) }, serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling [1] IMPLICIT ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE {
3220
3GPP
3221 Release 4
22363 22364 22365 22366 22367 22368 22369 22370 22371 22372 22373 22374 22375 22376 22377 22378 22379 22380 22381 22382 22383 22384 22385 22386 22387 22388 22389 22390 22391 22392 22393 22394 22395 22396 22397 22398 22399 22400 22401 22402 22403 22404 22405 22406 22407 22408 22409 22410 22411 22412 22413 22414 22415 22416 22417 22418 22419 22420 22421 22422 22423 22424 22425 22426 22427 22428 22429 22430 22431 22432 22433 22434 22435 22436 22437 22438 22439
1225
3GPP TS 29.002 V4.17.0 (2006-06)
extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , camelCapabilityHandling [0] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, notificationToCSE [1] IMPLICIT NULL OPTIONAL, csi-Active [2] IMPLICIT NULL OPTIONAL} OPTIONAL, t-BCSM-CAMEL-TDP-CriteriaList [4] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { t-BCSM-TriggerDetectionPoint ENUMERATED { termAttemptAuthorized ( 12 ), ... , tBusy ( 13 ), tNoAnswer ( 14 ) }, basicServiceCriteria [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, t-CauseValueCriteria [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ... } OPTIONAL, vt-CSI [5] IMPLICIT SEQUENCE { t-BcsmCamelTDPDataList SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { t-BcsmTriggerDetectionPoint ENUMERATED { termAttemptAuthorized ( 12 ), ... , tBusy ( 13 ), tNoAnswer ( 14 ) }, serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling [1] IMPLICIT ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE {
3222
3GPP
3223 Release 4
22440 22441 22442 22443 22444 22445 22446 22447 22448 22449 22450 22451 22452 22453 22454 22455 22456 22457 22458 22459 22460 22461 22462 22463 22464 22465 22466 22467 22468 22469 22470 22471 22472 22473 22474 22475 22476 22477 22478 22479 22480 22481 22482 22483 22484 22485 22486 22487 22488 22489 22490 22491 22492 22493 22494 22495 22496 22497 22498 22499 22500 22501 22502 22503 22504 22505 22506 22507 22508 22509 22510 22511 22512 22513 22514 22515 22516
1226
3GPP TS 29.002 V4.17.0 (2006-06)
... } OPTIONAL, ... } OPTIONAL, ... , camelCapabilityHandling [0] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, notificationToCSE [1] IMPLICIT NULL OPTIONAL, csi-Active [2] IMPLICIT NULL OPTIONAL} OPTIONAL, vt-BCSM-CAMEL-TDP-CriteriaList [6] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { t-BCSM-TriggerDetectionPoint ENUMERATED { termAttemptAuthorized ( 12 ), ... , tBusy ( 13 ), tNoAnswer ( 14 ) }, basicServiceCriteria [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, t-CauseValueCriteria [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ... } OPTIONAL, tif-CSI [7] IMPLICIT NULL OPTIONAL, tif-CSI-NotificationToCSE [8] IMPLICIT NULL OPTIONAL, gprs-CSI [9] IMPLICIT SEQUENCE { gprs-CamelTDPDataList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { gprs-TriggerDetectionPoint [0] IMPLICIT ENUMERATED { attach ( 1 ), attachChangeOfPosition ( 2 ), pdp-ContextEstablishment ( 11 ), pdp-ContextEstablishmentAcknowledgement ( 12 ), pdp-ContextChangeOfPosition ( 14 ), ... }, serviceKey [1] IMPLICIT INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultSessionHandling [3] IMPLICIT ENUMERATED { continueTransaction ( 0 ), releaseTransaction ( 1 ), ... }, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camelCapabilityHandling [1] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [3] IMPLICIT NULL OPTIONAL, csi-Active [4] IMPLICIT NULL OPTIONAL, ... } OPTIONAL, sms-CSI [10] IMPLICIT SEQUENCE { sms-CAMEL-TDP-DataList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { sms-TriggerDetectionPoint [0] IMPLICIT ENUMERATED { sms-CollectedInfo ( 1 ), ... }, serviceKey [1] IMPLICIT INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultSMS-Handling [3] IMPLICIT ENUMERATED { continueTransaction ( 0 ),
3224
3GPP
3225 Release 4
22517 22518 22519 22520 22521 22522 22523 22524 22525 22526 22527 22528 22529 22530 22531 22532 22533 22534 22535 22536 22537 22538 22539 22540 22541 22542 22543 22544 22545 22546 22547 22548 22549 22550 22551 22552 22553 22554 22555 22556 22557 22558 22559 22560 22561 22562 22563 22564 22565 22566 22567 22568 22569 22570 22571 22572 22573 22574 22575 22576 22577 22578 22579 22580 22581 22582 22583 22584 22585 22586 22587 22588 22589 22590 22591 22592 22593
1227
3GPP TS 29.002 V4.17.0 (2006-06)
releaseTransaction ( 1 ), ... }, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camelCapabilityHandling [1] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [3] IMPLICIT NULL OPTIONAL, csi-Active [4] IMPLICIT NULL OPTIONAL, ... } OPTIONAL, ss-CSI [11] IMPLICIT SEQUENCE { ss-CamelData SEQUENCE { ss-EventList SEQUENCE ( SIZE( 1 .. 10 ) ) OF OCTET STRING ( SIZE( 1 ) ), gsmSCF-Address OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), extensionContainer [0] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , notificationToCSE [0] IMPLICIT NULL OPTIONAL, csi-Active [1] IMPLICIT NULL OPTIONAL} OPTIONAL, m-CSI [12] IMPLICIT SEQUENCE { mobilityTriggers SEQUENCE ( SIZE( 1 .. 10 ) ) OF OCTET STRING ( SIZE( 1 ) ), serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { ,
3226
3GPP
3227 Release 4
22594 22595 22596 22597 22598 22599 22600 22601 22602 22603 22604 22605 22606 22607 22608 22609 22610 22611 22612 22613 22614 22615 22616 22617 22618 22619 22620 22621 22622 22623 22624 22625 22626 22627 22628 22629 22630 22631 22632 22633 22634 22635 22636 22637 22638 22639 22640 22641 22642 22643 22644 22645 22646 22647 22648 22649 22650 22651 22652 22653 22654 22655 22656 22657 22658 22659 22660 22661 22662 22663 22664 22665 22666 22667 22668 22669 22670
1228
3GPP TS 29.002 V4.17.0 (2006-06)
...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [2] IMPLICIT NULL OPTIONAL, csi-Active [3] IMPLICIT NULL OPTIONAL, ... } OPTIONAL, extensionContainer [13] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , specificCSIDeletedList [14] IMPLICIT BIT STRING { o-csi (0 ), ss-csi (1 ), tif-csi (2 ), d-csi (3 ), vt-csi (4 ), sms-csi (5 ), m-csi (6 ), gprs-csi (7 ), t-csi (8 )} ( SIZE( 8 .. 32 ) ) OPTIONAL} OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- atm-NotAllowed -- localValue : 61, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- unknownSubscriber -- localValue : 1, -- bearerServiceNotProvisioned -- localValue : 10, -- teleserviceNotProvisioned -- localValue : 11, -- callBarred -- localValue : 13, -- illegalSS-Operation -- localValue : 16, -- ss-SubscriptionViolation -- localValue : 19, -- ss-ErrorStatus -- localValue : 17, -- ss-Incompatibility -- localValue : 20, -- informationNotAvailable -- localValue : 62} ::= localValue : 65 noteSubscriberDataModified OPERATION ARGUMENT noteSubscriberDataModifiedArg SEQUENCE { imsi OCTET STRING ( SIZE( 3 .. 8 ) ), msisdn OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), forwardingInfoFor-CSE [0] IMPLICIT SEQUENCE { ss-Code [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ), forwardingFeatureList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 32 ) ) OF SEQUENCE { basicService CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), forwardedToNumber [5] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, forwardedToSubaddress [8] IMPLICIT OCTET STRING ( SIZE( 1 .. 21 ) ) OPTIONAL, forwardingOptions [6] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ) OPTIONAL, noReplyConditionTime [7] IMPLICIT INTEGER ( 1 .. 100 ) OPTIONAL, extensionContainer [9] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF
3228
3GPP
3229 Release 4
22671 22672 22673 22674 22675 22676 22677 22678 22679 22680 22681 22682 22683 22684 22685 22686 22687 22688 22689 22690 22691 22692 22693 22694 22695 22696 22697 22698 22699 22700 22701 22702 22703 22704 22705 22706 22707 22708 22709 22710 22711 22712 22713 22714 22715 22716 22717 22718 22719 22720 22721 22722 22723 22724 22725 22726 22727 22728 22729 22730 22731 22732 22733 22734 22735 22736 22737 22738 22739 22740 22741 22742 22743 22744 22745 22746 22747
1229
3GPP TS 29.002 V4.17.0 (2006-06)
SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , longForwardedToNumber [10] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 15 ) ) OPTIONAL}, notificationToCSE [2] IMPLICIT NULL OPTIONAL, extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, callBarringInfoFor-CSE [1] IMPLICIT SEQUENCE { ss-Code [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ), callBarringFeatureList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 32 ) ) OF SEQUENCE { basicService CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, password [2] IMPLICIT NumericString ( FROM ("0"|"1"|"2"|"3"|"4"|"5"|"6"|"7"|"8"|"9" )) (SIZE( 4 ) ) OPTIONAL, wrongPasswordAttemptsCounter [3] IMPLICIT INTEGER ( 0 .. 4 ) OPTIONAL, notificationToCSE [4] IMPLICIT NULL OPTIONAL, extensionContainer [5] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, odb-Info [2] IMPLICIT SEQUENCE { odb-Data SEQUENCE { 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 ),
3230
3GPP
3231 Release 4
22748 22749 22750 22751 22752 22753 22754 22755 22756 22757 22758 22759 22760 22761 22762 22763 22764 22765 22766 22767 22768 22769 22770 22771 22772 22773 22774 22775 22776 22777 22778 22779 22780 22781 22782 22783 22784 22785 22786 22787 22788 22789 22790 22791 22792 22793 22794 22795 22796 22797 22798 22799 22800 22801 22802 22803 22804 22805 22806 22807 22808 22809 22810 22811 22812 22813 22814 22815 22816 22817 22818 22819 22820 22821 22822 22823 22824
1230
3GPP TS 29.002 V4.17.0 (2006-06)
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 ) ), odb-HPLMN-Data BIT STRING { plmn-SpecificBarringType1 (0 ), plmn-SpecificBarringType2 (1 ), plmn-SpecificBarringType3 (2 ), plmn-SpecificBarringType4 (3 )} ( SIZE( 4 .. 32 ) ) OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, notificationToCSE NULL OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camel-SubscriptionInfo [3] IMPLICIT SEQUENCE { o-CSI [0] IMPLICIT SEQUENCE { o-BcsmCamelTDPDataList SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { o-BcsmTriggerDetectionPoint ENUMERATED { collectedInfo ( 2 ), ... , routeSelectFailure ( 4 ) }, serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling [1] IMPLICIT ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... },
3232
3GPP
3233 Release 4
22825 22826 22827 22828 22829 22830 22831 22832 22833 22834 22835 22836 22837 22838 22839 22840 22841 22842 22843 22844 22845 22846 22847 22848 22849 22850 22851 22852 22853 22854 22855 22856 22857 22858 22859 22860 22861 22862 22863 22864 22865 22866 22867 22868 22869 22870 22871 22872 22873 22874 22875 22876 22877 22878 22879 22880 22881 22882 22883 22884 22885 22886 22887 22888 22889 22890 22891 22892 22893 22894 22895 22896 22897 22898 22899 22900 22901
1231
3GPP TS 29.002 V4.17.0 (2006-06)
extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , camelCapabilityHandling [0] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, notificationToCSE [1] IMPLICIT NULL OPTIONAL, csiActive [2] IMPLICIT NULL OPTIONAL} OPTIONAL, o-BcsmCamelTDP-CriteriaList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { o-BcsmTriggerDetectionPoint ENUMERATED { collectedInfo ( 2 ), ... , routeSelectFailure ( 4 ) }, destinationNumberCriteria [0] IMPLICIT SEQUENCE { matchType [0] IMPLICIT ENUMERATED { inhibiting ( 0 ), enabling ( 1 ) }, destinationNumberList [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, destinationNumberLengthList [2] IMPLICIT SEQUENCE ( SIZE( 1 .. 3 ) ) OF INTEGER ( 1 .. 15 ) OPTIONAL, ... } OPTIONAL, basicServiceCriteria [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, callTypeCriteria [2] IMPLICIT ENUMERATED { forwarded ( 0 ), notForwarded ( 1 ) } OPTIONAL, ... , o-CauseValueCriteria [3] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF OCTET STRING ( SIZE( 1 ) ) OPTIONAL, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL} OPTIONAL, d-CSI [2] IMPLICIT SEQUENCE { dp-AnalysedInfoCriteriaList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { dialledNumber OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camelCapabilityHandling [1] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL,
3234
3GPP
3235 Release 4
22902 22903 22904 22905 22906 22907 22908 22909 22910 22911 22912 22913 22914 22915 22916 22917 22918 22919 22920 22921 22922 22923 22924 22925 22926 22927 22928 22929 22930 22931 22932 22933 22934 22935 22936 22937 22938 22939 22940 22941 22942 22943 22944 22945 22946 22947 22948 22949 22950 22951 22952 22953 22954 22955 22956 22957 22958 22959 22960 22961 22962 22963 22964 22965 22966 22967 22968 22969 22970 22971 22972 22973 22974 22975 22976 22977 22978
1232
3GPP TS 29.002 V4.17.0 (2006-06)
extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [3] IMPLICIT NULL OPTIONAL, csi-Active [4] IMPLICIT NULL OPTIONAL, ... } OPTIONAL, t-CSI [3] IMPLICIT SEQUENCE { t-BcsmCamelTDPDataList SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { t-BcsmTriggerDetectionPoint ENUMERATED { termAttemptAuthorized ( 12 ), ... , tBusy ( 13 ), tNoAnswer ( 14 ) }, serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling [1] IMPLICIT ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , camelCapabilityHandling [0] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, notificationToCSE [1] IMPLICIT NULL OPTIONAL, csi-Active [2] IMPLICIT NULL OPTIONAL} OPTIONAL, t-BCSM-CAMEL-TDP-CriteriaList [4] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { t-BCSM-TriggerDetectionPoint ENUMERATED { termAttemptAuthorized ( 12 ), ... , tBusy ( 13 ), tNoAnswer ( 14 ) }, basicServiceCriteria [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, t-CauseValueCriteria [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ... } OPTIONAL, vt-CSI [5] IMPLICIT SEQUENCE { t-BcsmCamelTDPDataList SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { t-BcsmTriggerDetectionPoint ENUMERATED { termAttemptAuthorized ( 12 ),
3236
3GPP
3237 Release 4
22979 22980 22981 22982 22983 22984 22985 22986 22987 22988 22989 22990 22991 22992 22993 22994 22995 22996 22997 22998 22999 23000 23001 23002 23003 23004 23005 23006 23007 23008 23009 23010 23011 23012 23013 23014 23015 23016 23017 23018 23019 23020 23021 23022 23023 23024 23025 23026 23027 23028 23029 23030 23031 23032 23033 23034 23035 23036 23037 23038 23039 23040 23041 23042 23043 23044 23045 23046 23047 23048 23049 23050 23051 23052 23053 23054 23055
1233
3GPP TS 29.002 V4.17.0 (2006-06)
... , tBusy ( 13 ), tNoAnswer ( 14 ) }, serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultCallHandling [1] IMPLICIT ENUMERATED { continueCall ( 0 ), releaseCall ( 1 ), ... }, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , camelCapabilityHandling [0] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, notificationToCSE [1] IMPLICIT NULL OPTIONAL, csi-Active [2] IMPLICIT NULL OPTIONAL} OPTIONAL, vt-BCSM-CAMEL-TDP-CriteriaList [6] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { t-BCSM-TriggerDetectionPoint ENUMERATED { termAttemptAuthorized ( 12 ), ... , tBusy ( 13 ), tNoAnswer ( 14 ) }, basicServiceCriteria [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF CHOICE { ext-BearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) ), ext-Teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 5 ) )} OPTIONAL, t-CauseValueCriteria [1] IMPLICIT SEQUENCE ( SIZE( 1 .. 5 ) ) OF OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ... } OPTIONAL, tif-CSI [7] IMPLICIT NULL OPTIONAL, tif-CSI-NotificationToCSE [8] IMPLICIT NULL OPTIONAL, gprs-CSI [9] IMPLICIT SEQUENCE { gprs-CamelTDPDataList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { gprs-TriggerDetectionPoint [0] IMPLICIT ENUMERATED { attach ( 1 ), attachChangeOfPosition ( 2 ), pdp-ContextEstablishment ( 11 ), pdp-ContextEstablishmentAcknowledgement ( 12 ), pdp-ContextChangeOfPosition ( 14 ), ... }, serviceKey [1] IMPLICIT INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultSessionHandling [3] IMPLICIT ENUMERATED { continueTransaction ( 0 ), releaseTransaction ( 1 ), ... }, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( {
3238
3GPP
3239 Release 4
23056 23057 23058 23059 23060 23061 23062 23063 23064 23065 23066 23067 23068 23069 23070 23071 23072 23073 23074 23075 23076 23077 23078 23079 23080 23081 23082 23083 23084 23085 23086 23087 23088 23089 23090 23091 23092 23093 23094 23095 23096 23097 23098 23099 23100 23101 23102 23103 23104 23105 23106 23107 23108 23109 23110 23111 23112 23113 23114 23115 23116 23117 23118 23119 23120 23121 23122 23123 23124 23125 23126 23127 23128 23129 23130 23131 23132
1234
3GPP TS 29.002 V4.17.0 (2006-06)
, ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camelCapabilityHandling [1] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [3] IMPLICIT NULL OPTIONAL, csi-Active [4] IMPLICIT NULL OPTIONAL, ... } OPTIONAL, sms-CSI [10] IMPLICIT SEQUENCE { sms-CAMEL-TDP-DataList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { sms-TriggerDetectionPoint [0] IMPLICIT ENUMERATED { sms-CollectedInfo ( 1 ), ... }, serviceKey [1] IMPLICIT INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), defaultSMS-Handling [3] IMPLICIT ENUMERATED { continueTransaction ( 0 ), releaseTransaction ( 1 ), ... }, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, camelCapabilityHandling [1] IMPLICIT INTEGER ( 1 .. 16 ) OPTIONAL, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [3] IMPLICIT NULL OPTIONAL, csi-Active [4] IMPLICIT NULL OPTIONAL, ... } OPTIONAL, ss-CSI [11] IMPLICIT SEQUENCE { ss-CamelData SEQUENCE { ss-EventList SEQUENCE ( SIZE( 1 .. 10 ) ) OF OCTET STRING ( SIZE( 1 ) ), gsmSCF-Address OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), extensionContainer [0] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL,
3240
3GPP
3241 Release 4
23133 23134 23135 23136 23137 23138 23139 23140 23141 23142 23143 23144 23145 23146 23147 23148 23149 23150 23151 23152 23153 23154 23155 23156 23157 23158 23159 23160 23161 23162 23163 23164 23165 23166 23167 23168 23169 23170 23171 23172 23173 23174 23175 23176 23177 23178 23179 23180 23181 23182 23183 23184 23185 23186 23187 23188 23189 23190 23191 23192 23193 23194 23195 23196 23197 23198 23199 23200 23201 23202 23203 23204 23205 23206 23207 23208 23209
1235
3GPP TS 29.002 V4.17.0 (2006-06)
pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , notificationToCSE [0] IMPLICIT NULL OPTIONAL, csi-Active [1] IMPLICIT NULL OPTIONAL} OPTIONAL, m-CSI [12] IMPLICIT SEQUENCE { mobilityTriggers SEQUENCE ( SIZE( 1 .. 10 ) ) OF OCTET STRING ( SIZE( 1 ) ), serviceKey INTEGER ( 0 .. 2147483647 ), gsmSCF-Address [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, notificationToCSE [2] IMPLICIT NULL OPTIONAL, csi-Active [3] IMPLICIT NULL OPTIONAL, ... } OPTIONAL, extensionContainer [13] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , specificCSIDeletedList [14] IMPLICIT BIT STRING { o-csi (0 ), ss-csi (1 ), tif-csi (2 ), d-csi (3 ), vt-csi (4 ), sms-csi (5 ), m-csi (6 ), gprs-csi (7 ), t-csi (8 )} ( SIZE( 8 .. 32 ) ) OPTIONAL} OPTIONAL, allInformationSent [4] IMPLICIT NULL OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT
3242
3GPP
3243 Release 4
23210 23211 23212 23213 23214 23215 23216 23217 23218 23219 23220 23221 23222 23223 23224 23225 23226 23227 23228 23229 23230 23231 23232 23233 23234 23235 23236 23237 23238 23239 23240 23241 23242 23243 23244 23245 23246 23247 23248 23249 23250 23251 23252 23253 23254 23255 23256 23257 23258 23259 23260 23261 23262 23263 23264 23265 23266 23267 23268 23269 23270 23271 23272 23273 23274 23275 23276 23277 23278 23279 23280 23281 23282 23283 23284 23285 23286
1236
3GPP TS 29.002 V4.17.0 (2006-06)
noteSubscriberDataModifiedRes SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- unknownSubscriber -- localValue : 1} ::= localValue : 5 ss-InvocationNotification OPERATION ARGUMENT ss-InvocationNotificationArg SEQUENCE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), msisdn [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), ss-Event [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), ss-EventSpecification [3] IMPLICIT SEQUENCE ( SIZE( 1 .. 2 ) ) OF OCTET STRING ( SIZE( 1 .. 20 ) ) OPTIONAL, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , b-subscriberNumber [5] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, ccbs-RequestState [6] IMPLICIT ENUMERATED { request ( 0 ), recall ( 1 ), active ( 2 ), completed ( 3 ), suspended ( 4 ), frozen ( 5 ), deleted ( 6 ) } OPTIONAL} RESULT ss-InvocationNotificationRes SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- unknownSubscriber -- localValue : 1} ::= localValue : 72 prepareGroupCall OPERATION ARGUMENT prepareGroupCallArg SEQUENCE { teleservice OCTET STRING ( SIZE( 1 .. 5 ) ), asciCallReference OCTET STRING ( SIZE( 1 .. 8 ) ), codec-Info OCTET STRING ( SIZE( 5 .. 10 ) ),
3244
3GPP
3245 Release 4
23287 23288 23289 23290 23291 23292 23293 23294 23295 23296 23297 23298 23299 23300 23301 23302 23303 23304 23305 23306 23307 23308 23309 23310 23311 23312 23313 23314 23315 23316 23317 23318 23319 23320 23321 23322 23323 23324 23325 23326 23327 23328 23329 23330 23331 23332 23333 23334 23335 23336 23337 23338 23339 23340 23341 23342 23343 23344 23345 23346 23347 23348 23349 23350 23351 23352 23353 23354 23355 23356 23357 23358 23359 23360 23361 23362 23363
1237
3GPP TS 29.002 V4.17.0 (2006-06)
cipheringAlgorithm OCTET STRING ( SIZE( 1 ) ), groupKeyNumber [0] IMPLICIT INTEGER ( 0 .. 15 ) OPTIONAL, groupKey [1] IMPLICIT OCTET STRING ( SIZE( 8 ) ) OPTIONAL, priority [2] IMPLICIT INTEGER ( 0 .. 15 ) OPTIONAL, uplinkFree [3] IMPLICIT NULL OPTIONAL, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT prepareGroupCallRes SEQUENCE { groupCallNumber OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- noGroupCallNumberAvailable -- localValue : 50, -- unexpectedDataValue -- localValue : 36} ::= localValue : 39 sendGroupCallEndSignal OPERATION ARGUMENT sendGroupCallEndSignalArg SEQUENCE { imsi OCTET STRING ( SIZE( 3 .. 8 ) ) OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT sendGroupCallEndSignalRes SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 40 processGroupCallSignalling OPERATION ARGUMENT processGroupCallSignallingArg SEQUENCE {
3246
3GPP
3247 Release 4
23364 23365 23366 23367 23368 23369 23370 23371 23372 23373 23374 23375 23376 23377 23378 23379 23380 23381 23382 23383 23384 23385 23386 23387 23388 23389 23390 23391 23392 23393 23394 23395 23396 23397 23398 23399 23400 23401 23402 23403 23404 23405 23406 23407 23408 23409 23410 23411 23412 23413 23414 23415 23416 23417 23418 23419 23420 23421 23422 23423 23424 23425 23426 23427 23428 23429 23430 23431 23432 23433 23434 23435 23436 23437 23438 23439 23440
1238
3GPP TS 29.002 V4.17.0 (2006-06)
uplinkRequest [0] IMPLICIT NULL OPTIONAL, uplinkReleaseIndication [1] IMPLICIT NULL OPTIONAL, releaseGroupCall [2] IMPLICIT NULL OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 41 forwardGroupCallSignalling OPERATION ARGUMENT forwardGroupCallSignallingArg SEQUENCE { imsi OCTET STRING ( SIZE( 3 .. 8 ) ) OPTIONAL, uplinkRequestAck [0] IMPLICIT NULL OPTIONAL, uplinkReleaseIndication [1] IMPLICIT NULL OPTIONAL, uplinkRejectCommand [2] IMPLICIT NULL OPTIONAL, uplinkSeizedCommand [3] IMPLICIT NULL OPTIONAL, uplinkReleaseCommand [4] IMPLICIT NULL OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , stateAttributes [5] IMPLICIT SEQUENCE { downlinkAttached [5] IMPLICIT NULL OPTIONAL, uplinkAttached [6] IMPLICIT NULL OPTIONAL, dualCommunication [7] IMPLICIT NULL OPTIONAL, callOriginator [8] IMPLICIT NULL OPTIONAL} OPTIONAL} ::= localValue : 42 updateGprsLocation OPERATION ARGUMENT updateGprsLocationArg SEQUENCE { imsi OCTET STRING ( SIZE( 3 .. 8 ) ), sgsn-Number OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), sgsn-Address OCTET STRING ( SIZE( 5 .. 17 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , sgsn-Capability [0] IMPLICIT SEQUENCE { solsaSupportIndicator NULL OPTIONAL, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL,
3248
3GPP
3249 Release 4
23441 23442 23443 23444 23445 23446 23447 23448 23449 23450 23451 23452 23453 23454 23455 23456 23457 23458 23459 23460 23461 23462 23463 23464 23465 23466 23467 23468 23469 23470 23471 23472 23473 23474 23475 23476 23477 23478 23479 23480 23481 23482 23483 23484 23485 23486 23487 23488 23489 23490 23491 23492 23493 23494 23495 23496 23497 23498 23499 23500 23501 23502 23503 23504 23505 23506 23507 23508 23509 23510 23511 23512 23513 23514 23515 23516 23517
1239
3GPP TS 29.002 V4.17.0 (2006-06)
pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , superChargerSupportedInServingNetworkEntity [2] CHOICE { sendSubscriberData [0] IMPLICIT NULL, subscriberDataStored [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 6 ) )} OPTIONAL, gprsEnhancementsSupportIndicator [3] IMPLICIT NULL OPTIONAL, supportedCamelPhases [4] IMPLICIT BIT STRING { phase1 (0 ), phase2 (1 ), phase3 (2 )} ( SIZE( 1 .. 16 ) ) OPTIONAL, supportedLCS-CapabilitySets [5] IMPLICIT BIT STRING { lcsCapabilitySet1 (0 ), lcsCapabilitySet2 (1 )} ( SIZE( 2 .. 16 ) ) OPTIONAL} OPTIONAL, informPreviousNetworkEntity [1] IMPLICIT NULL OPTIONAL} RESULT updateGprsLocationRes SEQUENCE { hlr-Number OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- unexpectedDataValue -- localValue : 36, -- unknownSubscriber -- localValue : 1, -- roamingNotAllowed -- localValue : 8} ::= localValue : 23 sendRoutingInfoForGprs OPERATION ARGUMENT sendRoutingInfoForGprsArg SEQUENCE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), ggsn-Address [1] IMPLICIT OCTET STRING ( SIZE( 5 .. 17 ) ) OPTIONAL, ggsn-Number [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT sendRoutingInfoForGprsRes SEQUENCE { sgsn-Address [0] IMPLICIT OCTET STRING ( SIZE( 5 .. 17 ) ), ggsn-Address [1] IMPLICIT OCTET STRING ( SIZE( 5 .. 17 ) ) OPTIONAL, mobileNotReachableReason [2] IMPLICIT INTEGER ( 0 .. 255 ) OPTIONAL, extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS {
3250
3GPP
3251 Release 4
23518 23519 23520 23521 23522 23523 23524 23525 23526 23527 23528 23529 23530 23531 23532 23533 23534 23535 23536 23537 23538 23539 23540 23541 23542 23543 23544 23545 23546 23547 23548 23549 23550 23551 23552 23553 23554 23555 23556 23557 23558 23559 23560 23561 23562 23563 23564 23565 23566 23567 23568 23569 23570 23571 23572 23573 23574 23575 23576 23577 23578 23579 23580 23581 23582 23583 23584 23585 23586 23587 23588 23589 23590 23591 23592 23593 23594
1240
3GPP TS 29.002 V4.17.0 (2006-06)
-- absentSubscriber -- localValue : 27, -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- unknownSubscriber -- localValue : 1, -- callBarred -- localValue : 13} ::= localValue : 24 failureReport OPERATION ARGUMENT failureReportArg SEQUENCE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), ggsn-Number [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), ggsn-Address [2] IMPLICIT OCTET STRING ( SIZE( 5 .. 17 ) ) OPTIONAL, extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT failureReportRes SEQUENCE { ggsn-Address [0] IMPLICIT OCTET STRING ( SIZE( 5 .. 17 ) ) OPTIONAL, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- unknownSubscriber -- localValue : 1} ::= localValue : 25 noteMsPresentForGprs OPERATION ARGUMENT noteMsPresentForGprsArg SEQUENCE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), sgsn-Address [1] IMPLICIT OCTET STRING ( SIZE( 5 .. 17 ) ), ggsn-Address [2] IMPLICIT OCTET STRING ( SIZE( 5 .. 17 ) ) OPTIONAL, extensionContainer [3] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT noteMsPresentForGprsRes SEQUENCE { extensionContainer [0] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) ,
3252
3GPP
3253 Release 4
23595 23596 23597 23598 23599 23600 23601 23602 23603 23604 23605 23606 23607 23608 23609 23610 23611 23612 23613 23614 23615 23616 23617 23618 23619 23620 23621 23622 23623 23624 23625 23626 23627 23628 23629 23630 23631 23632 23633 23634 23635 23636 23637 23638 23639 23640 23641 23642 23643 23644 23645 23646 23647 23648 23649 23650 23651 23652 23653 23654 23655 23656 23657 23658 23659 23660 23661 23662 23663 23664 23665 23666 23667 23668 23669 23670 23671
1241
3GPP TS 29.002 V4.17.0 (2006-06)
extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- unknownSubscriber -- localValue : 1} ::= localValue : 26 provideSubscriberLocation OPERATION ARGUMENT provideSubscriberLocation-Arg SEQUENCE { locationType SEQUENCE { locationEstimateType [0] IMPLICIT ENUMERATED { currentLocation ( 0 ), currentOrLastKnownLocation ( 1 ), initialLocation ( 2 ), ... , activateDeferredLocation ( 3 ), cancelDeferredLocation ( 4 ) }, ... , deferredLocationEventType [1] IMPLICIT BIT STRING { msAvailable (0 )} ( SIZE( 1 .. 16 ) ) OPTIONAL}, mlc-Number OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), lcs-ClientID [0] IMPLICIT SEQUENCE { lcsClientType [0] IMPLICIT ENUMERATED { emergencyServices ( 0 ), valueAddedServices ( 1 ), plmnOperatorServices ( 2 ), lawfulInterceptServices ( 3 ), ... }, lcsClientExternalID [1] IMPLICIT SEQUENCE { externalAddress [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) OPTIONAL, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, lcsClientDialedByMS [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) OPTIONAL, lcsClientInternalID [3] IMPLICIT ENUMERATED { broadcastService ( 0 ), o-andM-HPLMN ( 1 ), o-andM-VPLMN ( 2 ), anonymousLocation ( 3 ), targetMSsubscribedService ( 4 ), ... } OPTIONAL, lcsClientName [4] IMPLICIT SEQUENCE { dataCodingScheme [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ), nameString [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 160 ) ) ( SIZE( 1 .. 63 ) ), ... } OPTIONAL, ... , lcsAPN [5] IMPLICIT OCTET STRING ( SIZE( 2 .. 63 ) ) OPTIONAL} OPTIONAL, privacyOverride [1] IMPLICIT NULL OPTIONAL, imsi [2] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ) OPTIONAL, msisdn [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, lmsi [4] IMPLICIT OCTET STRING ( SIZE( 4 ) ) OPTIONAL, imei [5] IMPLICIT OCTET STRING ( SIZE( 8 ) ) OPTIONAL, lcs-Priority [6] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, lcs-QoS [7] IMPLICIT SEQUENCE { horizontal-accuracy [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, verticalCoordinateRequest [1] IMPLICIT NULL OPTIONAL, vertical-accuracy [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, responseTime [3] IMPLICIT SEQUENCE { responseTimeCategory ENUMERATED {
3254
3GPP
3255 Release 4
23672 23673 23674 23675 23676 23677 23678 23679 23680 23681 23682 23683 23684 23685 23686 23687 23688 23689 23690 23691 23692 23693 23694 23695 23696 23697 23698 23699 23700 23701 23702 23703 23704 23705 23706 23707 23708 23709 23710 23711 23712 23713 23714 23715 23716 23717 23718 23719 23720 23721 23722 23723 23724 23725 23726 23727 23728 23729 23730 23731 23732 23733 23734 23735 23736 23737 23738 23739 23740 23741 23742 23743 23744 23745 23746 23747 23748
1242
3GPP TS 29.002 V4.17.0 (2006-06)
lowdelay ( 0 ), delaytolerant ( 1 ), ... }, ... } OPTIONAL, extensionContainer [4] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, extensionContainer [8] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , supportedGADShapes [9] IMPLICIT BIT STRING { ellipsoidPoint (0 ), ellipsoidPointWithUncertaintyCircle (1 ), ellipsoidPointWithUncertaintyEllipse (2 ), polygon (3 ), ellipsoidPointWithAltitude (4 ), ellipsoidPointWithAltitudeAndUncertaintyElipsoid (5 ), ellipsoidArc (6 )} ( SIZE( 7 .. 16 ) ) OPTIONAL, lcs-ReferenceNumber [10] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL} RESULT provideSubscriberLocation-Res SEQUENCE { locationEstimate OCTET STRING ( SIZE( 1 .. 20 ) ), ageOfLocationEstimate [0] IMPLICIT INTEGER ( 0 .. 32767 ) OPTIONAL, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , add-LocationEstimate [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 91 ) ) OPTIONAL, deferredmt-lrResponseIndicator [3] IMPLICIT NULL OPTIONAL} ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- facilityNotSupported -- localValue : 21, -- unidentifiedSubscriber -- localValue : 5, -- illegalSubscriber -- localValue : 9, -- illegalEquipment -- localValue : 12, -- absentSubscriber -- localValue : 27, -- unauthorizedRequestingNetwork -- localValue : 52, -- unauthorizedLCSClient -- localValue : 53, -- positionMethodFailure -- localValue : 54} ::= localValue : 83 sendRoutingInfoForLCS OPERATION ARGUMENT routingInfoForLCS-Arg SEQUENCE { mlcNumber [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), targetMS [1] CHOICE {
3256
3GPP
3257 Release 4
23749 23750 23751 23752 23753 23754 23755 23756 23757 23758 23759 23760 23761 23762 23763 23764 23765 23766 23767 23768 23769 23770 23771 23772 23773 23774 23775 23776 23777 23778 23779 23780 23781 23782 23783 23784 23785 23786 23787 23788 23789 23790 23791 23792 23793 23794 23795 23796 23797 23798 23799 23800 23801 23802 23803 23804 23805 23806 23807 23808 23809 23810 23811 23812 23813 23814 23815 23816 23817 23818 23819 23820 23821 23822 23823 23824 23825
1243
3GPP TS 29.002 V4.17.0 (2006-06)
imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), msisdn [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) )}, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } RESULT routingInfoForLCS-Res SEQUENCE { targetMS [0] CHOICE { imsi [0] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ), msisdn [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) )}, lcsLocationInfo [1] IMPLICIT SEQUENCE { networkNode-Number OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), lmsi [0] IMPLICIT OCTET STRING ( SIZE( 4 ) ) OPTIONAL, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , gprsNodeIndicator [2] IMPLICIT NULL OPTIONAL, additional-Number [3] CHOICE { msc-Number [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), sgsn-Number [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) )} OPTIONAL}, extensionContainer [2] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- unexpectedDataValue -- localValue : 36, -- facilityNotSupported -- localValue : 21, -- unknownSubscriber -- localValue : 1, -- absentSubscriber -- localValue : 27, -- unauthorizedRequestingNetwork -- localValue : 52} ::= localValue : 85 subscriberLocationReport OPERATION ARGUMENT subscriberLocationReport-Arg SEQUENCE { lcs-Event ENUMERATED { emergencyCallOrigination ( 0 ), emergencyCallRelease ( 1 ), mo-lr ( 2 ), ... , deferredmt-lrResponse ( 3 ) }, lcs-ClientID SEQUENCE { lcsClientType [0] IMPLICIT ENUMERATED { emergencyServices ( 0 ), valueAddedServices ( 1 ), plmnOperatorServices ( 2 ),
3258
3GPP
3259 Release 4
23826 23827 23828 23829 23830 23831 23832 23833 23834 23835 23836 23837 23838 23839 23840 23841 23842 23843 23844 23845 23846 23847 23848 23849 23850 23851 23852 23853 23854 23855 23856 23857 23858 23859 23860 23861 23862 23863 23864 23865 23866 23867 23868 23869 23870 23871 23872 23873 23874 23875 23876 23877 23878 23879 23880 23881 23882 23883 23884 23885 23886 23887 23888 23889 23890 23891 23892 23893 23894 23895 23896 23897 23898 23899 23900 23901 23902
1244
3GPP TS 29.002 V4.17.0 (2006-06)
lawfulInterceptServices ( 3 ), ... }, lcsClientExternalID [1] IMPLICIT SEQUENCE { externalAddress [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) OPTIONAL, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } OPTIONAL, lcsClientDialedByMS [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) OPTIONAL, lcsClientInternalID [3] IMPLICIT ENUMERATED { broadcastService ( 0 ), o-andM-HPLMN ( 1 ), o-andM-VPLMN ( 2 ), anonymousLocation ( 3 ), targetMSsubscribedService ( 4 ), ... } OPTIONAL, lcsClientName [4] IMPLICIT SEQUENCE { dataCodingScheme [0] IMPLICIT OCTET STRING ( SIZE( 1 ) ), nameString [2] IMPLICIT OCTET STRING ( SIZE( 1 .. 160 ) ) ( SIZE( 1 .. 63 ) ), ... } OPTIONAL, ... , lcsAPN [5] IMPLICIT OCTET STRING ( SIZE( 2 .. 63 ) ) OPTIONAL}, lcsLocationInfo SEQUENCE { networkNode-Number OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), lmsi [0] IMPLICIT OCTET STRING ( SIZE( 4 ) ) OPTIONAL, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , gprsNodeIndicator [2] IMPLICIT NULL OPTIONAL, additional-Number [3] CHOICE { msc-Number [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), sgsn-Number [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) )} OPTIONAL}, msisdn [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, imsi [1] IMPLICIT OCTET STRING ( SIZE( 3 .. 8 ) ) OPTIONAL, imei [2] IMPLICIT OCTET STRING ( SIZE( 8 ) ) OPTIONAL, na-ESRD [3] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, na-ESRK [4] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL, locationEstimate [5] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) OPTIONAL, ageOfLocationEstimate [6] IMPLICIT INTEGER ( 0 .. 32767 ) OPTIONAL, slr-ArgExtensionContainer [7] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, slr-Arg-PCS-Extensions [1] IMPLICIT SEQUENCE { ... , na-ESRK-Request [0] IMPLICIT NULL OPTIONAL} OPTIONAL, ... } OPTIONAL, ... , add-LocationEstimate [8] IMPLICIT OCTET STRING ( SIZE( 1 .. 91 ) ) OPTIONAL, deferredmt-lrData [9] IMPLICIT SEQUENCE { deferredLocationEventType BIT STRING { msAvailable (0 )} ( SIZE( 1 .. 16 ) ), terminationCause [0] IMPLICIT ENUMERATED {
3260
3GPP
3261 Release 4
23903 23904 23905 23906 23907 23908 23909 23910 23911 23912 23913 23914 23915 23916 23917 23918 23919 23920 23921 23922 23923 23924 23925 23926 23927 23928 23929 23930 23931 23932 23933 23934 23935 23936 23937 23938 23939 23940 23941 23942 23943 23944 23945 23946 23947 23948 23949 23950 23951 23952 23953 23954 23955 23956 23957 23958 23959 23960 23961 23962 23963 23964 23965 23966 23967 23968 23969 23970 23971 23972 23973 23974 23975 23976 23977 23978 23979
1245
3GPP TS 29.002 V4.17.0 (2006-06)
normal ( 0 ), errorundefined ( 1 ), internalTimeout ( 2 ), congestion ( 3 ), mt-lrRestart ( 4 ), privacyViolation ( 5 ), ... , shapeOfLocationEstimateNotSupported ( 6 ) } OPTIONAL, lcsLocationInfo [1] IMPLICIT SEQUENCE { networkNode-Number OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), lmsi [0] IMPLICIT OCTET STRING ( SIZE( 4 ) ) OPTIONAL, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , gprsNodeIndicator [2] IMPLICIT NULL OPTIONAL, additional-Number [3] CHOICE { msc-Number [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ), sgsn-Number [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) )} OPTIONAL} OPTIONAL, ... } OPTIONAL, lcs-ReferenceNumber [10] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL} RESULT subscriberLocationReport-Res SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , na-ESRK [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) ( SIZE( 1 .. 9 ) ) OPTIONAL} ERRORS { -- systemFailure -- localValue : 34, -- dataMissing -- localValue : 35, -- resourceLimitation -- localValue : 51, -- unexpectedDataValue -- localValue : 36, -- unknownSubscriber -- localValue : 1, -- unauthorizedRequestingNetwork -- localValue : 52, -- unknownOrUnreachableLCSClient -- localValue : 58} ::= localValue : 86 systemFailure ERROR PARAMETER systemFailureParam CHOICE { networkResource ENUMERATED { plmn ( 0 ), hlr ( 1 ), vlr ( 2 ), pvlr ( 3 ), controllingMSC ( 4 ), vmsc ( 5 ), eir ( 6 ), rss ( 7 ) }, extensibleSystemFailureParam SEQUENCE { networkResource ENUMERATED { plmn ( 0 ), hlr ( 1 ), vlr ( 2 ), pvlr ( 3 ), controllingMSC ( 4 ), vmsc ( 5 ), eir ( 6 ),
3262
3GPP
3263 Release 4
23980 23981 23982 23983 23984 23985 23986 23987 23988 23989 23990 23991 23992 23993 23994 23995 23996 23997 23998 23999 24000 24001 24002 24003 24004 24005 24006 24007 24008 24009 24010 24011 24012 24013 24014 24015 24016 24017 24018 24019 24020 24021 24022 24023 24024 24025 24026 24027 24028 24029 24030 24031 24032 24033 24034 24035 24036 24037 24038 24039 24040 24041 24042 24043 24044 24045 24046 24047 24048 24049 24050 24051 24052 24053 24054 24055 24056
1246
3GPP TS 29.002 V4.17.0 (2006-06)
rss ( 7 ) } OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }} ::= localValue : 34 dataMissing ERROR PARAMETER dataMissingParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 35 unexpectedDataValue ERROR PARAMETER unexpectedDataParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 36 facilityNotSupported ERROR PARAMETER facilityNotSupParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , shapeOfLocationEstimateNotSupported [0] IMPLICIT NULL OPTIONAL} ::= localValue : 21 incompatibleTerminal ERROR PARAMETER incompatibleTerminalParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE {
3264
3GPP
3265 Release 4
24057 24058 24059 24060 24061 24062 24063 24064 24065 24066 24067 24068 24069 24070 24071 24072 24073 24074 24075 24076 24077 24078 24079 24080 24081 24082 24083 24084 24085 24086 24087 24088 24089 24090 24091 24092 24093 24094 24095 24096 24097 24098 24099 24100 24101 24102 24103 24104 24105 24106 24107 24108 24109 24110 24111 24112 24113 24114 24115 24116 24117 24118 24119 24120 24121 24122 24123 24124 24125 24126 24127 24128 24129 24130 24131 24132 24133
1247
3GPP TS 29.002 V4.17.0 (2006-06)
extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 28 resourceLimitation ERROR PARAMETER resourceLimitationParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 51 unknownSubscriber ERROR PARAMETER unknownSubscriberParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , unknownSubscriberDiagnostic ENUMERATED { imsiUnknown ( 0 ), gprsSubscriptionUnknown ( 1 ), ... , npdbMismatch ( 2 ) } OPTIONAL} ::= localValue : 1 numberChanged ERROR PARAMETER numberChangedParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 44 unknownMSC ERROR ::= localValue : 3 unidentifiedSubscriber ERROR PARAMETER unidentifiedSubParam SEQUENCE {
3266
3GPP
3267 Release 4
24134 24135 24136 24137 24138 24139 24140 24141 24142 24143 24144 24145 24146 24147 24148 24149 24150 24151 24152 24153 24154 24155 24156 24157 24158 24159 24160 24161 24162 24163 24164 24165 24166 24167 24168 24169 24170 24171 24172 24173 24174 24175 24176 24177 24178 24179 24180 24181 24182 24183 24184 24185 24186 24187 24188 24189 24190 24191 24192 24193 24194 24195 24196 24197 24198 24199 24200 24201 24202 24203 24204 24205 24206 24207 24208 24209 24210
1248
3GPP TS 29.002 V4.17.0 (2006-06)
extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 5 unknownEquipment ERROR ::= localValue : 7 roamingNotAllowed ERROR PARAMETER roamingNotAllowedParam SEQUENCE { roamingNotAllowedCause ENUMERATED { plmnRoamingNotAllowed ( 0 ), operatorDeterminedBarring ( 3 ) }, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 8 illegalSubscriber ERROR PARAMETER illegalSubscriberParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 9 illegalEquipment ERROR PARAMETER illegalEquipmentParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 12 bearerServiceNotProvisioned ERROR PARAMETER
3268
3GPP
3269 Release 4
24211 24212 24213 24214 24215 24216 24217 24218 24219 24220 24221 24222 24223 24224 24225 24226 24227 24228 24229 24230 24231 24232 24233 24234 24235 24236 24237 24238 24239 24240 24241 24242 24243 24244 24245 24246 24247 24248 24249 24250 24251 24252 24253 24254 24255 24256 24257 24258 24259 24260 24261 24262 24263 24264 24265 24266 24267 24268 24269 24270 24271 24272 24273 24274 24275 24276 24277 24278 24279 24280 24281 24282 24283 24284 24285 24286 24287
1249
3GPP TS 29.002 V4.17.0 (2006-06)
bearerServNotProvParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 10 teleserviceNotProvisioned ERROR PARAMETER teleservNotProvParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 11 noHandoverNumberAvailable ERROR ::= localValue : 25 subsequentHandoverFailure ERROR ::= localValue : 26 targetCellOutsideGroupCallArea ERROR PARAMETER targetCellOutsideGCA-Param SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 42 tracingBufferFull ERROR PARAMETER tracingBufferFullParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 40 noRoamingNumberAvailable ERROR
3270
3GPP
3271 Release 4
24288 24289 24290 24291 24292 24293 24294 24295 24296 24297 24298 24299 24300 24301 24302 24303 24304 24305 24306 24307 24308 24309 24310 24311 24312 24313 24314 24315 24316 24317 24318 24319 24320 24321 24322 24323 24324 24325 24326 24327 24328 24329 24330 24331 24332 24333 24334 24335 24336 24337 24338 24339 24340 24341 24342 24343 24344 24345 24346 24347 24348 24349 24350 24351 24352 24353 24354 24355 24356 24357 24358 24359 24360 24361 24362 24363 24364
1250
3GPP TS 29.002 V4.17.0 (2006-06)
PARAMETER noRoamingNbParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 39 absentSubscriber ERROR PARAMETER absentSubscriberParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , absentSubscriberReason [0] IMPLICIT ENUMERATED { imsiDetach ( 0 ), restrictedArea ( 1 ), noPageResponse ( 2 ), ... , purgedMS ( 3 ) } OPTIONAL} ::= localValue : 27 busySubscriber ERROR PARAMETER busySubscriberParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , ccbs-Possible [0] IMPLICIT NULL OPTIONAL, ccbs-Busy [1] IMPLICIT NULL OPTIONAL} ::= localValue : 45 noSubscriberReply ERROR PARAMETER noSubscriberReplyParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... }
3272
3GPP
3273 Release 4
24365 24366 24367 24368 24369 24370 24371 24372 24373 24374 24375 24376 24377 24378 24379 24380 24381 24382 24383 24384 24385 24386 24387 24388 24389 24390 24391 24392 24393 24394 24395 24396 24397 24398 24399 24400 24401 24402 24403 24404 24405 24406 24407 24408 24409 24410 24411 24412 24413 24414 24415 24416 24417 24418 24419 24420 24421 24422 24423 24424 24425 24426 24427 24428 24429 24430 24431 24432 24433 24434 24435 24436 24437 24438 24439 24440 24441
1251
3GPP TS 29.002 V4.17.0 (2006-06)
::= localValue : 46 callBarred ERROR PARAMETER callBarredParam CHOICE { callBarringCause ENUMERATED { barringServiceActive ( 0 ), operatorBarring ( 1 ) }, extensibleCallBarredParam SEQUENCE { callBarringCause ENUMERATED { barringServiceActive ( 0 ), operatorBarring ( 1 ) } OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , unauthorisedMessageOriginator [1] IMPLICIT NULL OPTIONAL}} ::= localValue : 13 forwardingFailed ERROR PARAMETER forwardingFailedParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 47 or-NotAllowed ERROR PARAMETER or-NotAllowedParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 48 forwardingViolation ERROR PARAMETER forwardingViolationParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE {
3274
3GPP
3275 Release 4
24442 24443 24444 24445 24446 24447 24448 24449 24450 24451 24452 24453 24454 24455 24456 24457 24458 24459 24460 24461 24462 24463 24464 24465 24466 24467 24468 24469 24470 24471 24472 24473 24474 24475 24476 24477 24478 24479 24480 24481 24482 24483 24484 24485 24486 24487 24488 24489 24490 24491 24492 24493 24494 24495 24496 24497 24498 24499 24500 24501 24502 24503 24504 24505 24506 24507 24508 24509 24510 24511 24512 24513 24514 24515 24516 24517 24518
1252
3GPP TS 29.002 V4.17.0 (2006-06)
... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 14 cug-Reject ERROR PARAMETER cug-RejectParam SEQUENCE { cug-RejectCause ENUMERATED { incomingCallsBarredWithinCUG ( 0 ), subscriberNotMemberOfCUG ( 1 ), requestedBasicServiceViolatesCUG-Constraints ( 5 ), calledPartySS-InteractionViolation ( 7 ) } OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 15 ati-NotAllowed ERROR PARAMETER ati-NotAllowedParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 49 atsi-NotAllowed ERROR PARAMETER atsi-NotAllowedParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 60 atm-NotAllowed ERROR PARAMETER atm-NotAllowedParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE {
3276
3GPP
3277 Release 4
24519 24520 24521 24522 24523 24524 24525 24526 24527 24528 24529 24530 24531 24532 24533 24534 24535 24536 24537 24538 24539 24540 24541 24542 24543 24544 24545 24546 24547 24548 24549 24550 24551 24552 24553 24554 24555 24556 24557 24558 24559 24560 24561 24562 24563 24564 24565 24566 24567 24568 24569 24570 24571 24572 24573 24574 24575 24576 24577 24578 24579 24580 24581 24582 24583 24584 24585 24586 24587 24588 24589 24590 24591 24592 24593 24594 24595
1253
3GPP TS 29.002 V4.17.0 (2006-06)
... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 61 informationNotAvailable ERROR PARAMETER informationNotAvailableParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 62 noGroupCallNumberAvailable ERROR PARAMETER noGroupCallNbParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 50 illegalSS-Operation ERROR PARAMETER illegalSS-OperationParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 16 ss-ErrorStatus ERROR PARAMETER ss-Status OCTET STRING ( SIZE( 1 ) ) ::= localValue : 17 ss-NotAvailable ERROR PARAMETER ss-NotAvailableParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE {
3278
3GPP
3279 Release 4
24596 24597 24598 24599 24600 24601 24602 24603 24604 24605 24606 24607 24608 24609 24610 24611 24612 24613 24614 24615 24616 24617 24618 24619 24620 24621 24622 24623 24624 24625 24626 24627 24628 24629 24630 24631 24632 24633 24634 24635 24636 24637 24638 24639 24640 24641 24642 24643 24644 24645 24646 24647 24648 24649 24650 24651 24652 24653 24654 24655 24656 24657 24658 24659 24660 24661 24662 24663 24664 24665 24666 24667 24668 24669 24670 24671 24672
1254
3GPP TS 29.002 V4.17.0 (2006-06)
... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 18 ss-SubscriptionViolation ERROR PARAMETER ss-SubscriptionViolationParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 19 ss-Incompatibility ERROR PARAMETER ss-IncompatibilityCause SEQUENCE { ss-Code [1] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, basicService CHOICE { bearerService [2] IMPLICIT OCTET STRING ( SIZE( 1 ) ), teleservice [3] IMPLICIT OCTET STRING ( SIZE( 1 ) )} OPTIONAL, ss-Status [4] IMPLICIT OCTET STRING ( SIZE( 1 ) ) OPTIONAL, ... } ::= localValue : 20 unknownAlphabet ERROR ::= localValue : 71 ussd-Busy ERROR ::= localValue : 72 pw-RegistrationFailure ERROR PARAMETER pw-RegistrationFailureCause ENUMERATED { undetermined ( 0 ), invalidFormat ( 1 ), newPasswordsMismatch ( 2 ) } ::= localValue : 37 negativePW-Check ERROR ::= localValue : 38 numberOfPW-AttemptsViolation ERROR ::= localValue : 43 shortTermDenial ERROR PARAMETER shortTermDenialParam SEQUENCE { ... } ::= localValue : 29 longTermDenial ERROR PARAMETER longTermDenialParam SEQUENCE { ... } ::= localValue : 30 subscriberBusyForMT-SMS ERROR PARAMETER subBusyForMT-SMS-Param SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { ,
3280
3GPP
3281 Release 4
24673 24674 24675 24676 24677 24678 24679 24680 24681 24682 24683 24684 24685 24686 24687 24688 24689 24690 24691 24692 24693 24694 24695 24696 24697 24698 24699 24700 24701 24702 24703 24704 24705 24706 24707 24708 24709 24710 24711 24712 24713 24714 24715 24716 24717 24718 24719 24720 24721 24722 24723 24724 24725 24726 24727 24728 24729 24730 24731 24732 24733 24734 24735 24736 24737 24738 24739 24740 24741 24742 24743 24744 24745 24746 24747 24748 24749
1255
3GPP TS 29.002 V4.17.0 (2006-06)
...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , gprsConnectionSuspended NULL OPTIONAL} ::= localValue : 31 sm-DeliveryFailure ERROR PARAMETER sm-DeliveryFailureCause SEQUENCE { sm-EnumeratedDeliveryFailureCause ENUMERATED { memoryCapacityExceeded ( 0 ), equipmentProtocolError ( 1 ), equipmentNotSM-Equipped ( 2 ), unknownServiceCentre ( 3 ), sc-Congestion ( 4 ), invalidSME-Address ( 5 ), subscriberNotSC-Subscriber ( 6 ) }, diagnosticInfo OCTET STRING ( SIZE( 1 .. 200 ) ) OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 32 messageWaitingListFull ERROR PARAMETER messageWaitListFullParam SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 33 absentsubscriberSM ERROR PARAMETER absentSubscriberSM-Param SEQUENCE { absentSubscriberDiagnosticSM INTEGER ( 0 .. 255 ) OPTIONAL, extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... , additionalAbsentSubscriberDiagnosticSM [0] IMPLICIT INTEGER ( 0 .. 255 ) OPTIONAL} ::= localValue : 6 unauthorizedRequestingNetwork ERROR PARAMETER unauthorizedRequestingNetwork-Param SEQUENCE { extensionContainer SEQUENCE {
3282
3GPP
3283 Release 4
24750 24751 24752 24753 24754 24755 24756 24757 24758 24759 24760 24761 24762 24763 24764 24765 24766 24767 24768 24769 24770 24771 24772 24773 24774 24775 24776 24777 24778 24779 24780 24781 24782 24783 24784 24785 24786 24787 24788 24789 24790 24791 24792 24793 24794 24795 24796 24797 24798 24799 24800 24801 24802 24803 24804 24805 24806 24807 24808 24809 24810 24811 24812 24813 24814 24815 24816 24817 24818 24819 24820 24821 24822 24823 24824 24825 24826
1256
3GPP TS 29.002 V4.17.0 (2006-06)
privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 52 unauthorizedLCSClient ERROR PARAMETER unauthorizedLCSClient-Param SEQUENCE { unauthorizedLCSClient-Diagnostic [0] IMPLICIT ENUMERATED { noAdditionalInformation ( 0 ), clientNotInMSPrivacyExceptionList ( 1 ), callToClientNotSetup ( 2 ), privacyOverrideNotApplicable ( 3 ), disallowedByLocalRegulatoryRequirements ( 4 ), ... } OPTIONAL, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 53 positionMethodFailure ERROR PARAMETER positionMethodFailure-Param SEQUENCE { positionMethodFailure-Diagnostic [0] IMPLICIT ENUMERATED { congestion ( 0 ), insufficientResources ( 1 ), insufficientMeasurementData ( 2 ), inconsistentMeasurementData ( 3 ), locationProcedureNotCompleted ( 4 ), locationProcedureNotSupportedByTargetMS ( 5 ), qoSNotAttainable ( 6 ), positionMethodNotAvailableInNetwork ( 7 ), positionMethodNotAvailableInLocationArea ( 8 ), ... } OPTIONAL, extensionContainer [1] IMPLICIT SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 54 unknownOrUnreachableLCSClient ERROR PARAMETER unknownOrUnreachableLCSClient-Param SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) ,
3284
3GPP
3285 Release 4
24827 24828 24829 24830 24831 24832 24833 24834 24835 24836 24837 24838 24839 24840 24841 24842 24843 24844 24845 24846 24847 24848 24849 24850 24851 24852 24853 24854 24855
1257
3GPP TS 29.002 V4.17.0 (2006-06)
extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 58 mm-EventNotSupported ERROR PARAMETER mm-EventNotSupported-Param SEQUENCE { extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, ... } ::= localValue : 59 END
3286
3GPP
3287 Release 4
1258
3GPP TS 29.002 V4.17.0 (2006-06)
24856 24857
24858 24859 24860 24861 24862 24863 24864 24865 24866 24867 24868 24869 24870 24871 24872 24873 24874 24875 24876 24877 24878 24879 24880 24881 24882 24883 24884 24885 24886 24887 24888 24889 24890 24891 24892 24893 24894 24895 24896 24897 24898 24899 24900 24901 24902 24903 24904 24905 24906 24907 24908 24909 24910 24911 24912 24913 24914 24915 24916 24917 24918 24919 24920 24921 24922 24923 24924 24925 24926 24927
B.2
Fully Expanded ASN.1 Source of MAPDialogueInformation
-- Expanded ASN1 Module 'MAP-DialogueInformation' --SIEMENS ASN.1 Compiler R6.0 (Production_6.0) -Date: 2006-06-08 Time: 12:09:56 MAP-DialogueInformation{ 0 identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) modules (3) mapDialogueInformation (3) version7 (7) } DEFINITIONS ::= BEGIN EXPORTS map-DialogueAS, MAP-DialoguePDU; map-DialogueAS OBJECT IDENTIFIER ::= { ccitt (0) identified-organization (4) etsi (0) mobileDomain (0) gsm-Network (1) 1 mapDialoguePDU (1) version1 (1) } MAP-DialoguePDU ::= CHOICE { map-open [0] IMPLICIT SEQUENCE { destinationReference [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) OPTIONAL, originationReference [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) OPTIONAL, ... , extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL}, map-accept [1] IMPLICIT SEQUENCE { ... , extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL}, map-close [2] IMPLICIT SEQUENCE { ... , extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL}, map-refuse [3] IMPLICIT SEQUENCE { reason ENUMERATED { noReasonGiven ( 0 ),
3288
3GPP
3289 Release 4
24928 24929 24930 24931 24932 24933 24934 24935 24936 24937 24938 24939 24940 24941 24942 24943 24944 24945 24946 24947 24948 24949 24950 24951 24952 24953 24954 24955 24956 24957 24958 24959 24960 24961 24962 24963 24964 24965 24966 24967 24968 24969 24970 24971 24972 24973 24974 24975 24976 24977 24978 24979 24980 24981 24982 24983 24984 24985 24986 24987 24988 24989 24990 24991 24992 24993 24994 24995 24996 24997 24998 24999 25000 25001 25002 25003 25004
1259
3GPP TS 29.002 V4.17.0 (2006-06)
invalidDestinationReference ( 1 ), invalidOriginatingReference ( 2 ) }, ... , extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, alternativeApplicationContext OBJECT IDENTIFIER OPTIONAL}, map-userAbort [4] IMPLICIT SEQUENCE { map-UserAbortChoice CHOICE { userSpecificReason [0] IMPLICIT NULL, userResourceLimitation [1] IMPLICIT NULL, resourceUnavailable [2] IMPLICIT ENUMERATED { shortTermResourceLimitation ( 0 ), longTermResourceLimitation ( 1 ) }, applicationProcedureCancellation [3] IMPLICIT ENUMERATED { handoverCancellation ( 0 ), radioChannelRelease ( 1 ), networkPathRelease ( 2 ), callRelease ( 3 ), associatedProcedureFailure ( 4 ), tandemDialogueRelease ( 5 ), remoteOperationsFailure ( 6 ) }}, ... , extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL}, map-providerAbort [5] IMPLICIT SEQUENCE { map-ProviderAbortReason ENUMERATED { abnormalDialogue ( 0 ), invalidPDU ( 1 ) }, ... , extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL}} MAP-OpenInfo ::= SEQUENCE { destinationReference [0] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) OPTIONAL, originationReference [1] IMPLICIT OCTET STRING ( SIZE( 1 .. 20 ) ) OPTIONAL, ... , extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL,
3290
3GPP
3291 Release 4
25005 25006 25007 25008 25009 25010 25011 25012 25013 25014 25015 25016 25017 25018 25019 25020 25021 25022 25023 25024 25025 25026 25027 25028 25029 25030 25031 25032 25033 25034 25035 25036 25037 25038 25039 25040 25041 25042 25043 25044 25045 25046 25047 25048 25049 25050 25051 25052 25053 25054 25055 25056 25057 25058 25059 25060 25061 25062 25063 25064 25065 25066 25067 25068 25069 25070 25071 25072 25073 25074 25075 25076 25077 25078 25079 25080 25081
1260
3GPP TS 29.002 V4.17.0 (2006-06)
... } OPTIONAL} MAP-AcceptInfo ::= SEQUENCE { ... , extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL} MAP-CloseInfo ::= SEQUENCE { ... , extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL} MAP-RefuseInfo ::= SEQUENCE { reason ENUMERATED { noReasonGiven ( 0 ), invalidDestinationReference ( 1 ), invalidOriginatingReference ( 2 ) }, ... , extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL, alternativeApplicationContext OBJECT IDENTIFIER OPTIONAL} Reason ::= ENUMERATED { noReasonGiven ( 0 ), invalidDestinationReference ( 1 ), invalidOriginatingReference ( 2 ) } MAP-UserAbortInfo ::= SEQUENCE { map-UserAbortChoice CHOICE { userSpecificReason [0] IMPLICIT NULL, userResourceLimitation [1] IMPLICIT NULL, resourceUnavailable [2] IMPLICIT ENUMERATED { shortTermResourceLimitation ( 0 ), longTermResourceLimitation ( 1 ) }, applicationProcedureCancellation [3] IMPLICIT ENUMERATED { handoverCancellation ( 0 ), radioChannelRelease ( 1 ), networkPathRelease ( 2 ), callRelease ( 3 ), associatedProcedureFailure ( 4 ), tandemDialogueRelease ( 5 ), remoteOperationsFailure ( 6 ) }}, ... , extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( {
3292
3GPP
3293 Release 4
25082 25083 25084 25085 25086 25087 25088 25089 25090 25091 25092 25093 25094 25095 25096 25097 25098 25099 25100 25101 25102 25103 25104 25105 25106 25107 25108 25109 25110 25111 25112 25113 25114 25115 25116 25117 25118 25119 25120 25121 25122 25123 25124 25125 25126 25127 25128 25129 25130 25131 25132 25133 25134 25135 25136 25137 25138 25139 25140 25141 25142
1261
3GPP TS 29.002 V4.17.0 (2006-06)
, ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL} MAP-UserAbortChoice ::= CHOICE { userSpecificReason [0] IMPLICIT NULL, userResourceLimitation [1] IMPLICIT NULL, resourceUnavailable [2] IMPLICIT ENUMERATED { shortTermResourceLimitation ( 0 ), longTermResourceLimitation ( 1 ) }, applicationProcedureCancellation [3] IMPLICIT ENUMERATED { handoverCancellation ( 0 ), radioChannelRelease ( 1 ), networkPathRelease ( 2 ), callRelease ( 3 ), associatedProcedureFailure ( 4 ), tandemDialogueRelease ( 5 ), remoteOperationsFailure ( 6 ) }} 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 ENUMERATED { abnormalDialogue ( 0 ), invalidPDU ( 1 ) }, ... , extensionContainer SEQUENCE { privateExtensionList [0] IMPLICIT SEQUENCE ( SIZE( 1 .. 10 ) ) OF SEQUENCE { extId MAP-EXTENSION .&extensionId ( { , ...} ) , extType MAP-EXTENSION .&ExtensionType ( { , ...} { @extId } ) OPTIONAL} OPTIONAL, pcs-Extensions [1] IMPLICIT SEQUENCE { ... } OPTIONAL, ... } OPTIONAL} MAP-ProviderAbortReason ::= ENUMERATED { abnormalDialogue ( 0 ), invalidPDU (1)} END
3294
3GPP
3295 Release 4
1262
3GPP TS 29.002 V4.17.0 (2006-06)
25143 25144
Annex C : Void
3296
3GPP
3297 Release 4
1263
3GPP TS 29.002 V4.17.0 (2006-06)
25145 25146 25147
Annex D (informative): Clause mapping table D.1 Mapping of Clause numbers
Table D.1: Clause mapping from Version 5.9.0 to Version 6.0.0
Old Clause No (V5.9.0) New Clause No (V6.0.0) Old Clause No (V5.9.0) New Clause No (V6.0.0)
25148 The clause numbers have been modified according to table D.1. 25149
1.1 1.2 2.* 3.* 4.* 5.* 6.* 7.* 8.* 9.* 10.* new11.* old11.* 12.* 13.* 14.* 15.* 16.*
25150
2 3 4.* 5.* 6.* 7.* 8.* 9.* 10.* 11.* 12.* 13.* 14.* 15.* 16.* 17.* 18.* 19.*
17.* 18.* 19.* 19.0.* 19.1.* 19.2.* 19.3.* 19.4.* 19.5.* 19.6.* 19.7.* 19.8.* 19.9.* 19.10.* 19.11.* 20.* new22.* old21.*
20.* 21.* 22.* 22.1.* 22.2.* 22.3.* 22.4.* 22.5.* 22.6.* 22.7.* 22.8.* 22.9.* 22.10.* 22.11.* 22.12.* 23.* 24.* 25.*
3298
3GPP
3299 Release 4
1264
3GPP TS 29.002 V4.17.0 (2006-06)
25151 25152
Annex E (informative): Change History
TSG# 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 3.1.0 the 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 3.1.0 ack 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 3.1.0 the 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 3.1.0 Resume 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 3.2.0 UUS from 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 CR
3300
3GPP
3301 Release 4
TSG# 05 06 06 06 06 06 06 06 06 06 06 06 06 TDoc N2-99D35 SPEC 29.002 VERS 3.1.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.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 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 048 059 063 066 079 080 083 084 086 087 089 090 094 095 099 100 101 102 103 104 105 107 1 5 1 2 1 1 2 1 2 1 CR 047 033 032 070 075 077 069 060 045 050 073 074 068
1265
3GPP TS 29.002 V4.17.0 (2006-06)
NEW_VERS 3.2.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 3.3.0 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 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 MNP Super Charger TEI GPRS Follow Me GPRS USSD & Follow Me Location Services Security QoS enhancements CAMEL Phase 3 TEI Super-Charger WORKITEM
N2-99G06 29.002 N2-99G18 29.002 N2-99G50 29.002 N2-99J88 N2-99K12 N2-99K24 N2-99K52 N2-99K58 N2-99K60 N2-99L20 N2-99J52 N2-99J92 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002 29.002
REV PHAS CAT SUBJECT E R99 Clarification of returning the MSISDN in SRIack 3 R99 C Introduction of the Super-Charger Concept in TS 29.002 2 R99 C Introduction of White Book SCCP in MAP R99 A Addition of GGSN number for the SRIforGPRS 1 R99 B Introduction of Follow Me R99 A Use of SSN for GPRS R99 A Correction of the USSD procedure in the HLR. 1 R99 C MAP Impacts for Location Services (LCS) 4 R99 B Authentication Enhancements 5 R99 C QoS-Subscribed field modification 1 R99 C Introduction of CAMEL Phase 3 in 3GPP TS 29.002 R99 D Restructuring of MAP Location Management Procedures for the Circuit Switched Domain R99 B Update of SDLs to support SuperCharger New version created to fix a CR 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 B B B B C F A B D A F B C C B C B F B F C D 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
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 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
3302
3GPP
3303 Release 4
TSG# 07 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 N4000543 N4000539 N4000491 N4000540 TDoc SPEC VERS 3.3.1 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 152 153 158 159 1 1 CR 110 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
1266
3GPP TS 29.002 V4.17.0 (2006-06)
NEW_VERS 3.4.0 3.4.0 3.4.0 3.4.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 3.5.0 4.0.0 4.0.1 4.1.0 4.1.0 4.1.0 4.1.0 Core Network Security TEI TEI Handover WORKITEM Security TEI ASCI Phase 2 LCS 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
N229.002 000454 N2B00035 29.002 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 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
REV PHAS CAT SUBJECT E 1 R99 B Introduction of Authentication Failure Report R99 B Use of MAP private extensions to implement region-specific requirements R99 A Prioritisation of MAP application context related to VGCS/VBS R99 F Correction of SS-Codes for 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 F D 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
Deletion of informative Annexe C
Aligning 29.002 with 25.413 (UTRAN Iu Interface RANAP Signalling)
3304
3GPP
3305 Release 4
TSG# 09 09 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 TDoc N4000541 N4000744 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 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 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.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 CR 160 161 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 1 1 2 2 1 2 1 1 1 3 1 2 1 1
1267
3GPP TS 29.002 V4.17.0 (2006-06)
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.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 WORKITEM Security Security 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
REV PHAS CAT SUBJECT E R00 A AUTS and AUTN parameter length 2 1 2 1 1 2 R00 R00 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 A A 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
Clarification on Authentication Failure Report ack
Correction on Location Information Optionality of parameters in GPRSCSI 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
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
3306
3GPP
3307 Release 4
TSG# 11 TDoc N4010362 N4010365 N4010393 N4010428 N4010446 N4010484 N4010728 N4010730 N4010733 N4010735 N4010739 NP010247 SPEC 29.002 VERS 4.2.1 CR 248
1268
REV PHAS CAT E Rel-4 A SUBJECT
3GPP TS 29.002 V4.17.0 (2006-06)
NEW_VERS 4.3.0 WORKITEM CAMEL 3
11
29.002
4.2.1
250
Rel-4
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
Correction to description of SSCSI in HLR to VLR information flow 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
4.3.0
Handover
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
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
4.3.0 4.3.0 4.3.0 4.3.0 4.3.0
266 168 267 268 289 5 3 3 2
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
LCS Security SEC1 - EHCS LCS1 SEC1
3308
3GPP
3309 Release 4
TSG# TDoc SPEC 29.002 29.002 29.002 29.002 29.002 29.002 29.002 VERS 4.4.0 4.4.1 4.4.1 4.4.1 4.4.1 4.4.1 4.4.1 CR
1269
REV PHAS CAT E Rel-4 Rel-4 F 1 2 2 2 Rel-4 Rel-4 Rel4 Rel-4 Rel-4 F F F F A SUBJECT
3GPP TS 29.002 V4.17.0 (2006-06)
NEW_VERS 4.4.1 4.5.0 4.5.0 4.5.0 4.5.0 4.5.0 4.5.0 WORKITEM
13 13 13 13 13 13
N4010840 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
290 291 292 295 302 306
Corrupted headers fixed Clarifications on long forwardedto numbers 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
TEI4 LCS1 LCS1 LCS1 SEC1-EHCS CAMEL3
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
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
29.002 29.002
4.5.0 4.5.0
344 347
Rel-4 Rel-4
F A
4.6.0 4.6.0
LCS1 CAMEL
3310
3GPP
3311 Release 4
TSG# 14 14 14 14 14 15 15 15 15 15 16 16 TDoc N4011437 N4011433 N4011439 N4011423 N4011394 N4020210 N4020067 N4020247 N4020182 N4020249 N4020529 N4020621 N4020640 N4020745 N4020749 N4020332 N4020409 N4020498 N4020510 N4020528 N4020742 N4021042 N4021417 N4021289 N4021562 N4021572 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 4.5.0 4.5.0 4.5.0 4.5.0 4.5.0 4.6.0 4.6.0 4.6.0 4.6.0 4.6.0 4.7.0 4.7.0 CR 349 354 359 360 364 372 385 389 402 406 427 452 1 2 1 1
1270
REV PHAS CAT E 2 Rel-4 F 1 2 1 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 Rel-4 A A F A A F F A F F A SUBJECT
3GPP TS 29.002 V4.17.0 (2006-06)
NEW_VERS 4.6.0 4.6.0 4.6.0 4.6.0 4.6.0 4.7.0 4.7.0 4.7.0 4.7.0 4.7.0 4.8.0 4.8.0 TEI4 Handover TEI TEI-4 CAMEL phase 3 CAMEL3 TEI4 TEI4 TEI TEI4 LCS1 Multicall WORKITEM
Handling of MNRR in the HLR & SMS-GMSC
Minimum MAP application context for G2G inter-MSC handover
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 Inclusion of complete ODB data in ATSI and NSDC 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 Handling the MNRR flag in the HLR & SMS-GMSC Clarify conditions to trigger restart of MTLR-Deferred procedure Clarfication of introducing Session related and unrelated class Corrections on the introduction of LCS for PS domain Check of NAM and Requesting Node Type on receipt of SendAuthenticationInfo Corrections in SS-code chapter Clarifications on Send Identification ODB correction Correction to segmentation of OCSI and T-CSI Addtion of reference number to deferred location request procedure Correction to the Service Handover parameters
16 16 16
29.002 29.002 29.002
4.7.0 4.7.0 4.7.0
459 439 445 2 1
Rel-4 Rel-4 Rel-4
A A A
4.8.0 4.8.0 4.8.0
TEI TEI Handover
16 16
29.002 29.002
4.7.0 4.7.0
409 424
Rel-4 Rel-4
F F
4.8.0 4.8.0
TEI_4 LCS1
16
29.002
4.7.0
419
Rel-4
4.8.0
LCS1-PS
16 16
29.002 29.002
4.7.0 4.7.0
429 397
1 3
Rel-4 Rel-4
F C
4.8.0 4.8.0
LCS TEI4
16 17 18 18 18
29.002 29.002 29.002 29.002 29.002
4.7.0 4.8.0 4.9.0 4.9.0 4.9.0
447 478 507 498 510
Rel-4 Rel-4 Rel-4 Rel-4
F A A A F
4.8.0 4.9.0 4.10.0 4.10.0 4.10.0
TEI TEI CAMEL3 CAMEL3 LCS1
Rel-4
18
29.002
4.9.0
515
Rel4
4.10.0
Multicall
3312
3GPP
3313 Release 4
TSG# 19 TDoc N4030299 N4030303 N4030285 NP030068 N4030690 NP030214 N4031041 N4031051 N4040331 N4040518 C4051330 C4060703 SPEC 29.002 VERS 4.10.0 CR 531
1271
REV PHAS CAT E 1 Rel-4 A SUBJECT
3GPP TS 29.002 V4.17.0 (2006-06)
NEW_VERS 4.11.0 WORKITEM Multicall
19 19
29.002 29.002
4.10.0 4.10.0
539 549
2 1
Rel-4 Rel-4
A A
19
29.002
4.10.0
543
Rel-4
20 20 21 21 23 24
29.002 29.002 29.002 29.002 29.002 29.002
4.11.0 4.11.0 4.12.0 4.12.0 4.13.0 4.14.0
534 631 582 662 706 713
Rel-4 Rel-4
F A F A F A
2 1 2 1
Rel-4 Rel-4 Rel-4 Rel-4
29 32
29.002 29.002
4.15.0 4.16.0
774 0815
Rel-4 Rel-4
F F
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 Correction to interactions between CAMEL control of MO SMS and barring Additional SGSN Related Access Type Detach 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 Correction to Insert Subscriber Data message for LCS SS Introduction of North American Interim Location Based Routing of Emergency Call Subscribed Charging Characteristics Removal of MAPsec material
4.11.0 4.11.0
TEI TEI
4.11.0
CAMEL3
4.12.0 4.12.0 4.13.0 4.13.0 4.14.0 4.15.0
SEC1-EHCS TEI MAP Security ASCI LCS LCS
4.16.0 4.15.0
TEI
SEC7-TCAP
25153 25154
3314
3GPP
You might also like
- Shoe Dog: A Memoir by the Creator of NikeFrom EverandShoe Dog: A Memoir by the Creator of NikeRating: 4.5 out of 5 stars4.5/5 (537)
- The Yellow House: A Memoir (2019 National Book Award Winner)From EverandThe Yellow House: A Memoir (2019 National Book Award Winner)Rating: 4 out of 5 stars4/5 (98)
- Never Split the Difference: Negotiating As If Your Life Depended On ItFrom EverandNever Split the Difference: Negotiating As If Your Life Depended On ItRating: 4.5 out of 5 stars4.5/5 (838)
- Hidden Figures: The American Dream and the Untold Story of the Black Women Mathematicians Who Helped Win the Space RaceFrom EverandHidden Figures: The American Dream and the Untold Story of the Black Women Mathematicians Who Helped Win the Space RaceRating: 4 out of 5 stars4/5 (890)
- Grit: The Power of Passion and PerseveranceFrom EverandGrit: The Power of Passion and PerseveranceRating: 4 out of 5 stars4/5 (587)
- The Subtle Art of Not Giving a F*ck: A Counterintuitive Approach to Living a Good LifeFrom EverandThe Subtle Art of Not Giving a F*ck: A Counterintuitive Approach to Living a Good LifeRating: 4 out of 5 stars4/5 (5794)
- The Little Book of Hygge: Danish Secrets to Happy LivingFrom EverandThe Little Book of Hygge: Danish Secrets to Happy LivingRating: 3.5 out of 5 stars3.5/5 (399)
- Elon Musk: Tesla, SpaceX, and the Quest for a Fantastic FutureFrom EverandElon Musk: Tesla, SpaceX, and the Quest for a Fantastic FutureRating: 4.5 out of 5 stars4.5/5 (474)
- A Heartbreaking Work Of Staggering Genius: A Memoir Based on a True StoryFrom EverandA Heartbreaking Work Of Staggering Genius: A Memoir Based on a True StoryRating: 3.5 out of 5 stars3.5/5 (231)
- The Emperor of All Maladies: A Biography of CancerFrom EverandThe Emperor of All Maladies: A Biography of CancerRating: 4.5 out of 5 stars4.5/5 (271)
- The Hard Thing About Hard Things: Building a Business When There Are No Easy AnswersFrom EverandThe Hard Thing About Hard Things: Building a Business When There Are No Easy AnswersRating: 4.5 out of 5 stars4.5/5 (344)
- On Fire: The (Burning) Case for a Green New DealFrom EverandOn Fire: The (Burning) Case for a Green New DealRating: 4 out of 5 stars4/5 (73)
- Devil in the Grove: Thurgood Marshall, the Groveland Boys, and the Dawn of a New AmericaFrom EverandDevil in the Grove: Thurgood Marshall, the Groveland Boys, and the Dawn of a New AmericaRating: 4.5 out of 5 stars4.5/5 (265)
- The World Is Flat 3.0: A Brief History of the Twenty-first CenturyFrom EverandThe World Is Flat 3.0: A Brief History of the Twenty-first CenturyRating: 3.5 out of 5 stars3.5/5 (2219)
- Team of Rivals: The Political Genius of Abraham LincolnFrom EverandTeam of Rivals: The Political Genius of Abraham LincolnRating: 4.5 out of 5 stars4.5/5 (234)
- The Gifts of Imperfection: Let Go of Who You Think You're Supposed to Be and Embrace Who You AreFrom EverandThe Gifts of Imperfection: Let Go of Who You Think You're Supposed to Be and Embrace Who You AreRating: 4 out of 5 stars4/5 (1090)
- The Unwinding: An Inner History of the New AmericaFrom EverandThe Unwinding: An Inner History of the New AmericaRating: 4 out of 5 stars4/5 (45)
- The Sympathizer: A Novel (Pulitzer Prize for Fiction)From EverandThe Sympathizer: A Novel (Pulitzer Prize for Fiction)Rating: 4.5 out of 5 stars4.5/5 (119)
- Her Body and Other Parties: StoriesFrom EverandHer Body and Other Parties: StoriesRating: 4 out of 5 stars4/5 (821)
- Microsoft Azure Commercial FedRAMP Penetration Test Report SummaryDocument47 pagesMicrosoft Azure Commercial FedRAMP Penetration Test Report SummarycnbirdNo ratings yet
- ISTJ in The Workplace - 16personalitiesDocument5 pagesISTJ in The Workplace - 16personalitiestoorialiceNo ratings yet
- Brocade 48000 Harware GuideDocument122 pagesBrocade 48000 Harware GuideMeghanath ChalasaniNo ratings yet
- ABM Fundamentals of ABM 1 CGDocument5 pagesABM Fundamentals of ABM 1 CGMaria Angelica BermilloNo ratings yet
- SPCC DocumentationDocument33 pagesSPCC DocumentationKumar Dzhunushaliev100% (1)
- Chapter 8 - Securing Information SystemsDocument16 pagesChapter 8 - Securing Information SystemsHASNAT ABULNo ratings yet
- Cisco Access Control Lists (ACL)Document3 pagesCisco Access Control Lists (ACL)Arslan SaleemNo ratings yet
- File Attachment in PeoplesoftDocument19 pagesFile Attachment in PeoplesoftAlexvalenciaayolaNo ratings yet
- ZLT S20 4G CAT4 Indoor CPE DatasheetDocument4 pagesZLT S20 4G CAT4 Indoor CPE DatasheetM. Rafael Gutiérrez D.67% (3)
- Sym WPS PB103Document4 pagesSym WPS PB103husseinNo ratings yet
- CCK-Types of Wireless NetworksDocument18 pagesCCK-Types of Wireless NetworksOmar PerezNo ratings yet
- ToadForOracle 13.1 UserGuideDocument150 pagesToadForOracle 13.1 UserGuidennikNo ratings yet
- User AnalysisDocument4 pagesUser AnalysisBharath SrinivasanNo ratings yet
- EMPTECH - NOTES Google DocsLOSITODocument7 pagesEMPTECH - NOTES Google DocsLOSITOAlliah AbordoNo ratings yet
- Diagnostics InformationDocument10 pagesDiagnostics InformationabyzNo ratings yet
- RtiDocument14 pagesRtiPRAMOD PANDITNo ratings yet
- 1 Isp Network Design PDFDocument97 pages1 Isp Network Design PDFSourav SatpathyNo ratings yet
- PMA Controller July 2011Document21 pagesPMA Controller July 2011nasir_khan_240% (1)
- Social Media test10-UmbelinaLima PDFDocument5 pagesSocial Media test10-UmbelinaLima PDFUmbelina Barros LimaNo ratings yet
- Backstory TemplateDocument4 pagesBackstory TemplateD kingNo ratings yet
- ApuntesDocument2 pagesApuntesMarta Relats AndrésNo ratings yet
- Upgrade Huawei E303 FirmDocument6 pagesUpgrade Huawei E303 Firmdurmotz50% (2)
- D8TDocument35 pagesD8Tmiguel100% (4)
- IC-3005 Series Manual PDFDocument116 pagesIC-3005 Series Manual PDFDedu TelespanNo ratings yet
- Eliana DeLeon Resume Final DraftDocument1 pageEliana DeLeon Resume Final DraftAnonymous lClZaFz9u8No ratings yet
- Career Planning & Development in ROBIDocument22 pagesCareer Planning & Development in ROBIshironamhin_92No ratings yet
- Check Point R7x XX R8x XX Releases Maps May 2017Document9 pagesCheck Point R7x XX R8x XX Releases Maps May 2017Syedtouseef ullaNo ratings yet
- Offensive Security: Penetration Test Report For OSCP ExamDocument17 pagesOffensive Security: Penetration Test Report For OSCP ExamBlack BoxNo ratings yet
- 23.1 AI For Enterprise Opportunities InfographicsDocument2 pages23.1 AI For Enterprise Opportunities InfographicsErick Poumián PalomecNo ratings yet
- CCNA 1 (v5.1 + v6.0) Chapter 1 Exam Answers 2020 - 100% FullDocument25 pagesCCNA 1 (v5.1 + v6.0) Chapter 1 Exam Answers 2020 - 100% FullwuillianbarretoNo ratings yet
