Mobile Messaging Technologies and Services: SMS, EMS and MMS ...

Recommendations

Info

Short Message Service 119 the USIM). A characteristic of this protocol is that the mobile equipment remains the ‘‘master’’ during the communications and is the element which initiates all commands to the SIM. In this protocol, there is no means for the SIM to issue commands to the mobile equipment. In order to cope with this limitation, the concept of a proactive command was introduced. A SIM making use of proactive commands is known as a proactive SIM. With proactive commands, the SIM is able to issue a command to the mobile equipment by specifying the proactive command in the response to a normal command previously submitted by the mobile equipment to the SIM. Upon receipt of such a response, the mobile equipment executes the specified command and provides the execution results to the SIM as part of a normal command. 3.18.2 SIM Data Download As shown in Section 3.7.7, two specific values can be assigned to the TP-Protocol- Identifier parameter (0x7C and 0x7F) for SIM data download. Upon receipt of a message containing one of these two values, the receiving mobile equipment provides the message to the SIM. The message is provided to the SIM by the use of a SAT command known as an ENVELOPE (SMS-PP DOWNLOAD) command. The subscriber is not notified of the receipt of the message by the mobile equipment. 3.18.3 SIM Interactions: Example In order to illustrate the use of SIM proactive commands and SIM data download messages, a simple scenario is described in this section. A SIM application maintains a SIM elementary file in which the subscriber geographical location is regularly updated. For the purpose of collecting statistics on subscriber moves, an application hosted in a remote server (external SME) regularly queries the mobile station for the subscriber location. For this purpose, the external SME submits a ‘‘querying’’ message to the SMSC. The SMSC delivers the message to the recipient mobile station. Upon receipt, the mobile equipment detects that the message is a SIM data download message and therefore provides the message to the SIM as part of an ENVELOPE SAT command. The SIM analyzes the message payload and generates an additional message that contains the results of the transaction (subscriber location, e.g., retrieved with a GPS module connected to the mobile equipment). The SIM issues the message to the mobile equipment via the SEND SHORT MESSAGE proactive command. Upon receipt of the proactive command, the mobile equipment submits the message to the SMSC which in turn delivers the message to the external SME. Finally, the external SME analyzes the payload of the ‘‘result’’ message and updates a database. The flow of interactions for such a scenario is depicted in Figure 3.42. 3.19 SMS and AT Commands Technical specification [3GPP-27.005] defines interface protocols for control of SMS functions between the MS and an external Terminal Equipment (TE) via an asynchronous interface. The MS and the TE are connected with a serial cable, an infrared link, or any other similar link as shown in Figure 3.43.
Recipient MS SIM SMSC ME External SME Message submission TP-Protocol-Identifier=SIM data download The remote application initiates the transaction by submitting a message to the service center. Message delivery TP-Message-Type-Indicator=SMS-DELIVER TP-Protocol-Identifier=SIM data download ENVELOPE (SMSPP DOWNLOAD + TPDU) The SIM performs a treatment on the incoming message payload and provides the results as part of the outgoing message. Acknowledgment Delivery report Proactive command (SEND SHORT MESSAGE + TPDU) Message submission TP-Message-Type-Indicator=SMS-SUBMIT Message delivery Submission report The remote application analyzes the transaction result generated by the SIM. Terminal response Figure 3.42 Example of interactions between an external SME and a SIM
Page 2:
MOBILE MESSAGING TECHNOLOGIES AND S
Page 6 and 7:
MOBILE MESSAGING TECHNOLOGIES AND S
Page 8:
Be liberal in what you accept, and
Page 11 and 12:
viii Contents 1.6.8 WTP Segmentatio
Page 13 and 14:
x Contents 3.15.6 User-Data-Header
Page 15 and 16:
xii Contents 5.13 Message Reports .
Page 17 and 18:
xiv Contents 6.8.6 Delivery Report
Page 19 and 20:
xvi Preface dedicated to the Short
Page 22:
Typographic conventions In this boo
Page 25 and 26:
2 Mobile Messaging Technologies and
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Gateway MSC (GMSC) interconnects th
Page 35 and 36:
12 Mobile Messaging Technologies an
Page 37 and 38:
Gateway MSC (GMSC) interconnects th
Page 39 and 40:
Figure 1.8 UMTS architecture (2nd p
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Figure 1.14 OMA digital rights mana
Page 52 and 53:
2 Standardization Standardization o
Page 54 and 55:
Standardization 31 2.1 Messaging Ro
Page 56 and 57:
Standardization 33 2.3 Third Genera
Page 58 and 59:
Standardization 35 responsible for
Page 60 and 61:
Standardization 37 Table 2.3 Specif
Page 62 and 63:
Standardization 39 2.6.1 IETF Docum
Page 64 and 65:
Standardization 41 A candidate reco
Page 66 and 67:
Standardization 43 2.9.1 OMA Organi
Page 68 and 69:
Standardization 45 required for ena
Page 70 and 71:
3 Short Message Service The Short M
Page 72 and 73:
Short Message Service 49 Figure 3.1
Page 74 and 75:
Short Message Service 51 SIM Lock O
Page 76 and 77:
Short Message Service 53 reception,
Page 78 and 79:
Short Message Service 55 3.4.2 Stat
Page 80 and 81:
Short Message Service 57 network ca
Page 82 and 83:
Short Message Service 59 Originator
Page 84 and 85:
Short Message Service 61 SMS- SUBMI
Page 86 and 87:
Short Message Service 63 sub-part c
Page 88 and 89:
Short Message Service 65 TP-Data-Co
Page 90 and 91:
Short Message Service 67 manipulate
Page 92 and 93: Short Message Service 69 The partia
Page 94 and 95: Short Message Service 71 Table 3.7
Page 96 and 97: Validity period format bits 2, 1, 0
Page 98 and 99: Short Message Service 75 3.9.6 Dest
Page 100 and 101: Short Message Service 77 Originator
Page 102 and 103: Short Message Service 79 The differ
Page 106 and 107: Short Message Service 83 Originator
Page 110 and 111: Short Message Service 87 3.12.2 Neg
Page 112 and 113: Short Message Service 89 3.13 Statu
Page 114 and 115: Short Message Service 91 Short mess
Page 118 and 119: Short Message Service 95 3.14.1 TPD
Page 120 and 121: Short Message Service 97 User-Data-
Page 122 and 123: Short Message Service 99 concatenat
Page 124 and 125: Short Message Service 101 IEI ... .
Page 126 and 127: Short Message Service 103 IEI IEDL
Page 128 and 129: Short Message Service 105 IEI Table
Page 130 and 131: Short Message Service 107 IEI IEDL
Page 132 and 133: Short Message Service 109 IEI Table
Page 134 and 135: Figure 3.37 IE/enhanced voice mail
Page 138 and 139: Short Message Service 115 Ancillary
Page 140 and 141: Short Message Service 117 External
Page 144 and 145: Short Message Service 121 Mobile St
Page 146 and 147: Short Message Service 123 Originato
Page 148 and 149: Short Message Service 125 user@doma
Page 150 and 151: Table 3.40 TPDU parameters Abbrevia
Page 152: Short Message Service 129 than text
Page 155 and 156: 132 Mobile Messaging Technologies a
Page 183 and 184: Second Short Message TPDU TP-User-D
Page 187 and 188: First message segment TP-User-Data
Page 193 and 194:
170 Mobile Messaging Technologies a
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Figure 5.3 MMS standard sets
Page 249 and 250:
Figure 5.4 Availability of MMS stan
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Figure 5.13 Structure of a multipar
Page 281 and 282:
Page 283 and 284:
Table 5.9 Message content classes f
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 316 and 317:
6 Multimedia Messaging Service, Tra
Page 318 and 319:
Multimedia Messaging Service 295 21
Page 320 and 321:
Multimedia Messaging Service 297 VA
Page 322 and 323:
Multimedia Messaging Service 299 In
Page 324 and 325:
Multimedia Messaging Service 301 Fi
Page 326 and 327:
Multimedia Messaging Service 303 Ta
Page 328 and 329:
Multimedia Messaging Service 305 Re
Page 330 and 331:
Multimedia Messaging Service 307 Re
Page 332 and 333:
Page 334 and 335:
Figure 6.11 Structure of an MMS not
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
Page 344 and 345:
Figure 6.16 Hexadecimal trace dump
Page 346 and 347:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
Page 354 and 355:
Page 356 and 357:
Page 358 and 359:
Page 360 and 361:
Page 362 and 363:
Multimedia Messaging Service 339 In
Page 364 and 365:
Table 6.24 MM1 PDU parameters with
Page 366 and 367:
Table 6.24 (Continued ) Parameter n
Page 368 and 369:
Table 6.24 (Continued ) Parameter n
Page 370 and 371:
Multimedia Messaging Service 347 As
Page 372 and 373:
Multimedia Messaging Service 349 6.
Page 374 and 375:
Multimedia Messaging Service 351 MM
Page 376 and 377:
Page 378 and 379:
Multimedia Messaging Service 355 de
Page 380 and 381:
Page 382 and 383:
Page 384 and 385:
Multimedia Messaging Service 361 te
Page 386 and 387:
Multimedia Messaging Service 363 SO
Page 388 and 389:
Multimedia Messaging Service 365 PD
Page 390 and 391:
Table 6.34 MM7 message submission r
Page 392 and 393:
Page 394 and 395:
Page 396 and 397:
Multimedia Messaging Service 373 HT
Page 398 and 399:
Page 400 and 401:
Table 6.38 MM7 message cancel reque
Page 402 and 403:
Page 404 and 405:
Page 406 and 407:
Page 408 and 409:
Table 6.45 MM7 read-report response
Page 410 and 411:
Multimedia Messaging Service 387 To
Page 412 and 413:
Multimedia Messaging Service 389 me
Page 414 and 415:
Page 416:
Multimedia Messaging Service 393 pa
Page 419 and 420:
Page 421 and 422:
Page 424 and 425:
Appendices Appendix A SMS TP-PID Va
Page 426 and 427:
Appendices 403 All other octet valu
Page 428 and 429:
Appendices 405 Table C.1 GSM 7 bit
Page 430 and 431:
Appendices 407 C.3 Universal Charac
Page 432 and 433:
Appendices 409 Table E.1 Content ty
Page 434 and 435:
Table F.1 (Continued ) Name B.E. De
Page 436 and 437:
Appendices 413 Error codes for whic
Page 438 and 439:
Appendices 415 code can indicate th
Page 440 and 441:
Acronyms and Abbreviations 3G Third
Page 442 and 443:
Acronyms and Abbreviations 419 GRX
Page 444 and 445:
Acronyms and Abbreviations 421 PAP
Page 446 and 447:
Acronyms and Abbreviations 423 TP-O
Page 448 and 449:
Index 3G services 11 3GPP file form
Page 450 and 451:
Index 427 Extended EMS 153 Animatio
Page 452 and 453:
Index 429 Mobile Message Access Pro
Page 454 and 455:
Index 431 Synchronized Multimedia I
show all

Mobile Messaging Technologies and Services: SMS, EMS and MMS ...

Create successful ePaper yourself

Delete template?

Save as template?