Tag.java

1
package fr.sii.ogham.testing.sms.simulator.bean;
2
3
/**
4
 * Optional Parameter tags
5
 * 
6
 * @author Aurélien Baudet
7
 *
8
 */
9
public enum Tag {
10
	/**
11
	 * <p>
12
	 * The payload_type parameter defines the higher layer PDU type contained in
13
	 * the message payload.
14
	 * </p>
15
	 * <table><caption>payload_type</caption>
16
	 * <thead>
17
	 * <tr>
18
	 * <th>Field Name</th>
19
	 * <th>Size octets</th>
20
	 * <th>Type</th>
21
	 * <th>Description</th>
22
	 * </tr>
23
	 * </thead> <tbody>
24
	 * <tr>
25
	 * <td>Parameter Tag</td>
26
	 * <td>2</td>
27
	 * <td>Integer</td>
28
	 * <td>payload_type</td>
29
	 * </tr>
30
	 * <tr>
31
	 * <td>Length</td>
32
	 * <td>2</td>
33
	 * <td>Integer</td>
34
	 * <td>Length of Value part in octets</td>
35
	 * </tr>
36
	 * <tr>
37
	 * <td>Value</td>
38
	 * <td>1</td>
39
	 * <td>Integer</td>
40
	 * <td>
41
	 * <p>
42
	 * 0 - Default. In the case of a WAP application, the default higher layer
43
	 * message type is a WDP message. See [WDP] for details.
44
	 * </p>
45
	 * <p>
46
	 * 1 - WCMP message. Wireless Control Message Protocol formatted data. See
47
	 * [WCMP] for details.
48
	 * </p>
49
	 * <p>
50
	 * values - 2 to 255 are reserved
51
	 * </p>
52
	 * </td>
53
	 * </tr>
54
	 * </tbody>
55
	 * </table>
56
	 */
57
	PAYLOAD_TYPE("payload_type", 0x0019),
58
	/**
59
	 * <p>
60
	 * The privacy_indicator indicates the privacy level of the message.
61
	 * </p>
62
	 */
63
	PRIVACY_INDICATOR("privacy_indicator", 0x0201),
64
	/**
65
	 * <p>
66
	 * A reference assigned by the originating SME to the short message.
67
	 * </p>
68
	 * <table><caption>user_message_reference</caption>
69
	 * <thead>
70
	 * <tr>
71
	 * <th>Field Name</th>
72
	 * <th>Size octets</th>
73
	 * <th>Type</th>
74
	 * <th>Description</th>
75
	 * </tr>
76
	 * </thead> <tbody>
77
	 * <tr>
78
	 * <td>Parameter Tag</td>
79
	 * <td>2</td>
80
	 * <td>Integer</td>
81
	 * <td>user_message_reference</td>
82
	 * </tr>
83
	 * <tr>
84
	 * <td>Length</td>
85
	 * <td>2</td>
86
	 * <td>Integer</td>
87
	 * <td>Length of value part in octets</td>
88
	 * </tr>
89
	 * <tr>
90
	 * <td>Value</td>
91
	 * <td>2</td>
92
	 * <td>Integer</td>
93
	 * <td>All values allowed.</td>
94
	 * </tr>
95
	 * </tbody>
96
	 * </table>
97
	 */
98
	USER_MESSAGE_REFERENCE("user_message_reference", 0x0204),
99
	/**
100
	 * <p>
101
	 * A response code set by the user in a User Acknowledgement/Reply message.
102
	 * The response codes are application specific.
103
	 * </p>
104
	 * <table><caption>user_response_code</caption>
105
	 * <thead>
106
	 * <tr>
107
	 * <th>Field Name</th>
108
	 * <th>Size octets</th>
109
	 * <th>Type</th>
110
	 * <th>Description</th>
111
	 * </tr>
112
	 * </thead> <tbody>
113
	 * <tr>
114
	 * <td>Parameter Tag</td>
115
	 * <td>2</td>
116
	 * <td>Integer</td>
117
	 * <td>user_response_code</td>
118
	 * </tr>
119
	 * <tr>
120
	 * <td>Length</td>
121
	 * <td>2</td>
122
	 * <td>Integer</td>
123
	 * <td>Length of value part in octets</td>
124
	 * </tr>
125
	 * <tr>
126
	 * <td>Value</td>
127
	 * <td>1</td>
128
	 * <td>Integer</td>
129
	 * <td>0 to 255 (IS-95 CDMA)<br>
130
	 * 0 to 15 (CMT-136 TDMA)</td>
131
	 * </tr>
132
	 * </tbody>
133
	 * </table>
134
	 */
135
	USER_RESPONSE_CODE("user_response_code", 0x0205),
136
	/**
137
	 * <p>
138
	 * The source_port parameter is used to indicate the application port number
139
	 * associated with the source address of the message.
140
	 * </p>
141
	 * <table><caption>source_port</caption>
142
	 * <thead>
143
	 * <tr>
144
	 * <th>Field Name</th>
145
	 * <th>Size octets</th>
146
	 * <th>Type</th>
147
	 * <th>Description</th>
148
	 * </tr>
149
	 * </thead> <tbody>
150
	 * <tr>
151
	 * <td>Parameter Tag</td>
152
	 * <td>2</td>
153
	 * <td>Integer</td>
154
	 * <td>source_port</td>
155
	 * </tr>
156
	 * <tr>
157
	 * <td>Length</td>
158
	 * <td>2</td>
159
	 * <td>Integer</td>
160
	 * <td>Length of value part in octets</td>
161
	 * </tr>
162
	 * <tr>
163
	 * <td>Value</td>
164
	 * <td>2</td>
165
	 * <td>Integer</td>
166
	 * <td>All values allowed.</td>
167
	 * </tr>
168
	 * </tbody>
169
	 * </table>
170
	 */
171
	SOURCE_PORT("source_port", 0x020A),
172
	/**
173
	 * <p>
174
	 * The destination_port parameter is used to indicate the application port
175
	 * number associated with the destination address of the message.
176
	 * </p>
177
	 * <table><caption>destination_port</caption>
178
	 * <thead>
179
	 * <tr>
180
	 * <th>Field Name</th>
181
	 * <th>Size octets</th>
182
	 * <th>Type</th>
183
	 * <th>Description</th>
184
	 * </tr>
185
	 * </thead> <tbody>
186
	 * <tr>
187
	 * <td>Parameter Tag</td>
188
	 * <td>2</td>
189
	 * <td>Integer</td>
190
	 * <td>destination_port</td>
191
	 * </tr>
192
	 * <tr>
193
	 * <td>Length</td>
194
	 * <td>2</td>
195
	 * <td>Integer</td>
196
	 * <td>Length of value part in octets</td>
197
	 * </tr>
198
	 * <tr>
199
	 * <td>Value</td>
200
	 * <td>2</td>
201
	 * <td>Integer</td>
202
	 * <td>All values allowed.</td>
203
	 * </tr>
204
	 * </tbody>
205
	 * </table>
206
	 */
207
	DESTINATION_PORT("destination_port", 0x020B),
208
	/**
209
	 * <p>
210
	 * The sar_msg_ref_num parameter is used to indicate the reference number
211
	 * for a particular concatenated short message.
212
	 * </p>
213
	 * <table><caption>sar_msg_ref_num</caption>
214
	 * <thead>
215
	 * <tr>
216
	 * <th>Field Name</th>
217
	 * <th>Size octets</th>
218
	 * <th>Type</th>
219
	 * <th>Description</th>
220
	 * </tr>
221
	 * </thead> <tbody>
222
	 * <tr>
223
	 * <td>Parameter Tag</td>
224
	 * <td>2</td>
225
	 * <td>Integer</td>
226
	 * <td>sar_msg_ref_num</td>
227
	 * 
228
	 * </tr>
229
	 * <tr>
230
	 * <td>Length</td>
231
	 * <td>2</td>
232
	 * <td>Integer</td>
233
	 * <td>Length of value part in octets</td>
234
	 * </tr>
235
	 * <tr>
236
	 * <td>Value</td>
237
	 * <td>2</td>
238
	 * <td>Integer</td>
239
	 * <td>This parameter shall contain a originator generated reference number
240
	 * so that a segmented short message may be reassembled into a single
241
	 * original message. This allows the parallel transmission of several
242
	 * segmented messages. This reference number shall remain constant for every
243
	 * segment which makes up a particular concatenated short message. When
244
	 * present, the PDU must also contain the sar_total_segments and
245
	 * sar_segment_seqnum parameters. Otherwise this parameter shall be
246
	 * ignored.</td>
247
	 * </tr>
248
	 * </tbody>
249
	 * </table>
250
	 */
251
	SAR_MSG_REF_NUM("sar_msg_ref_num", 0x020C),
252
	/**
253
	 * <p>
254
	 * The language_indicator parameter is used to indicate the language of the
255
	 * short message.
256
	 * </p>
257
	 * <table><caption>lang_indicator</caption>
258
	 * <thead>
259
	 * <tr>
260
	 * <th>Field Name</th>
261
	 * <th>Size octets</th>
262
	 * <th>Type</th>
263
	 * <th>Description</th>
264
	 * </tr>
265
	 * </thead> <tbody>
266
	 * <tr>
267
	 * <td>Parameter Tag</td>
268
	 * <td>2</td>
269
	 * <td>Integer</td>
270
	 * <td>language_indicator</td>
271
	 * </tr>
272
	 * <tr>
273
	 * <td>Length</td>
274
	 * <td>2</td>
275
	 * <td>Integer</td>
276
	 * <td>Length of value part in octets</td>
277
	 * </tr>
278
	 * <tr>
279
	 * <td>Value</td>
280
	 * <td>1</td>
281
	 * <td>Integer</td>
282
	 * <td>0 = unspecified (default)<br>
283
	 * 1 = english <br>
284
	 * 2 = french <br>
285
	 * 3 = spanish <br>
286
	 * 4 = german <br>
287
	 * 5 = Portuguese <br>
288
	 * refer to [CMT-136] for other values</td>
289
	 * </tr>
290
	 * </tbody>
291
	 * </table>
292
	 */
293
	LANGUAGE_INDICATOR("lang_indicator", 0x020D),
294
	/**
295
	 * <p>
296
	 * The sar_total_segments parameter is used to indicate the total number of
297
	 * short messages within the concatenated short message.
298
	 * </p>
299
	 * <table><caption>sar_total_segments</caption>
300
	 * <thead>
301
	 * <tr>
302
	 * <th>Field Name</th>
303
	 * <th>Size octets</th>
304
	 * <th>Type</th>
305
	 * <th>Description</th>
306
	 * </tr>
307
	 * </thead> <tbody>
308
	 * <tr>
309
	 * <td>Parameter Tag</td>
310
	 * <td>2</td>
311
	 * <td>Integer</td>
312
	 * <td>sar_total_segments</td>
313
	 * </tr>
314
	 * <tr>
315
	 * <td>Length</td>
316
	 * <td>2</td>
317
	 * <td>Integer</td>
318
	 * <td>Length of value part in octets</td>
319
	 * </tr>
320
	 * <tr>
321
	 * <td>Value</td>
322
	 * <td>1</td>
323
	 * <td>Integer</td>
324
	 * <td>This parameter shall contain a value in the range 1 to 255 indicating
325
	 * the total number of fragments within the concatenated short message. The
326
	 * value shall start at 1 and remain constant for every short message which
327
	 * makes up the concatenated short message. When present, the PDU must also
328
	 * contain the sar_msg_ref_num and sar_segment_seqnum parameters. Otherwise
329
	 * this parameter shall be ignored.</td>
330
	 * </tr>
331
	 * </tbody>
332
	 * </table>
333
	 */
334
	SAR_TOTAL_SEGMENTS("sar_total_segments", 0x020E),
335
	/**
336
	 * <p>
337
	 * The sar_segment_seqnum parameter is used to indicate the sequence number
338
	 * of a particular short message within the concatenated short message.
339
	 * </p>
340
	 * <table><caption>sar_segment_seqnum</caption>
341
	 * <thead>
342
	 * <tr>
343
	 * <th>Field Name</th>
344
	 * <th>Size octets</th>
345
	 * <th>Type</th>
346
	 * <th>Description</th>
347
	 * </tr>
348
	 * </thead> <tbody>
349
	 * <tr>
350
	 * <td>Parameter Tag</td>
351
	 * <td>2</td>
352
	 * <td>Integer</td>
353
	 * <td>ar_segment_seqnum</td>
354
	 * </tr>
355
	 * <tr>
356
	 * <td>Length</td>
357
	 * <td>2</td>
358
	 * <td>Integer</td>
359
	 * <td>Length of value part in octets</td>
360
	 * </tr>
361
	 * <tr>
362
	 * <td>Value</td>
363
	 * <td>1</td>
364
	 * <td>Integer</td>
365
	 * <td>This octet shall contain a value in the range 1 to 255 indicating the
366
	 * sequence number of a particular message within the concatenated short
367
	 * message. The value shall start at 1 and increment by one for every
368
	 * message sent within the concatenated short message. When present, the PDU
369
	 * must also contain the sar_total_segments and sar_msg_ref_num parameters.
370
	 * Otherwise this parameter shall be ignored.</td>
371
	 * </tr>
372
	 * </tbody>
373
	 * </table>
374
	 */
375
	SAR_SEGMENT_SEQNUM("sar_segment_seqnum", 0x020F),
376
	/**
377
	 * <p>
378
	 * The source_subaddress parameter specifies a subaddress associated with
379
	 * the originator of the message.
380
	 * </p>
381
	 */
382
	SOURCE_SUBADDRESS("source_subaddress", 0x0202),
383
	/**
384
	 * <p>
385
	 * The dest_subaddress parameter specifies a subaddress associated with the
386
	 * destination of the message.
387
	 * </p>
388
	 * <table><caption>dest_subaddress</caption>
389
	 * <thead>
390
	 * <tr>
391
	 * <th>Field Name</th>
392
	 * <th>Size octets</th>
393
	 * <th>Type</th>
394
	 * <th>Description</th>
395
	 * </tr>
396
	 * </thead> <tbody>
397
	 * <tr>
398
	 * <td>Parameter Tag</td>
399
	 * <td>2</td>
400
	 * <td>Integer</td>
401
	 * <td>dest_subaddress</td>
402
	 * </tr>
403
	 * <tr>
404
	 * <td>Length</td>
405
	 * <td>2</td>
406
	 * <td>Integer</td>
407
	 * <td>Length of Value part in octets</td>
408
	 * </tr>
409
	 * <tr>
410
	 * <td>Value</td>
411
	 * <td>Var 2 - 23</td>
412
	 * <td>Octet String</td>
413
	 * <td>See 5.3.2.15 for parameter encoding.</td>
414
	 * </tr>
415
	 * </tbody>
416
	 * </table>
417
	 */
418
	DEST_SUBADDRESS("dest_subaddress", 0x0203),
419
	/**
420
	 * <p>
421
	 * The callback_num parameter associates a call back number with the
422
	 * message. In TDMA networks, it is possible to send and receive multiple
423
	 * callback numbers to/from TDMA mobile stations.
424
	 * </p>
425
	 * <table><caption>callback_num</caption>
426
	 * <thead>
427
	 * <tr>
428
	 * <th>Field Name</th>
429
	 * <th>Size octets</th>
430
	 * <th>Type</th>
431
	 * <th>Description</th>
432
	 * </tr>
433
	 * </thead> <tbody>
434
	 * <tr>
435
	 * <td>Parameter Tag</td>
436
	 * <td>2</td>
437
	 * <td>Integer</td>
438
	 * <td>&nbsp;</td>
439
	 * </tr>
440
	 * <tr>
441
	 * <td>Length</td>
442
	 * <td>2</td>
443
	 * <td>Integer</td>
444
	 * <td>Length of Value part in octets</td>
445
	 * </tr>
446
	 * <tr>
447
	 * <td>Value</td>
448
	 * <td>Var 4 - 19</td>
449
	 * <td>Octet String</td>
450
	 * <td>
451
	 * <p>
452
	 * <b>Bits 7.............0</b>
453
	 * </p>
454
	 * <p>
455
	 * 0000000D (octet 1)
456
	 * </p>
457
	 * <p>
458
	 * 00000TTT (octet 2)
459
	 * </p>
460
	 * <p>
461
	 * 0000NNNN (octet 3)
462
	 * </p>
463
	 * <p>
464
	 * XXXXXXXX (octet 4)
465
	 * </p>
466
	 * <p>
467
	 * :
468
	 * </p>
469
	 * <p>
470
	 * :
471
	 * </p>
472
	 * <p>
473
	 * XXXXXXXX (octet N)
474
	 * </p>
475
	 * <p>
476
	 * The originating SME can set a Call Back Number for the receiving Mobile
477
	 * Station. The first octet contains the Digit Mode Indicator. Bit D=0
478
	 * indicates that the Call Back Number is sent to the mobile as DTMF digits
479
	 * encoded in TBCD. Bit D=1 indicates that the Call Back Number is sent to
480
	 * the mobile encoded as ASCII digits. The 2nd octet contains the Type of
481
	 * Number (TON). Encoded as in section 5.2.5.
482
	 * </p>
483
	 * <p>
484
	 * The third octet contains the Numbering Plan Indicator (NPI). Encoded as
485
	 * specified in section 5.2.6
486
	 * </p>
487
	 * <p>
488
	 * The remaining octets contain the Call Back Number digits encoded as ASCII
489
	 * characters
490
	 * </p>
491
	 * </td>
492
	 * </tr>
493
	 * </tbody>
494
	 * </table>
495
	 */
496
	CALLBACK_NUM("callback_num", 0x0381),
497
	/**
498
	 * <p>
499
	 * The message_payload parameter contains the user data.
500
	 * </p>
501
	 * <table><caption>message_payload</caption>
502
	 * <thead>
503
	 * <tr>
504
	 * <th>Field Name</th>
505
	 * <th>Size octets</th>
506
	 * <th>Type</th>
507
	 * <th>Description</th>
508
	 * </tr>
509
	 * </thead> <tbody>
510
	 * <tr>
511
	 * <td>Parameter Tag</td>
512
	 * <td>2</td>
513
	 * <td>Integer</td>
514
	 * <td>message_payload</td>
515
	 * </tr>
516
	 * <tr>
517
	 * <td>Length</td>
518
	 * <td>2</td>
519
	 * <td>Integer</td>
520
	 * <td>Set to length of user data</td>
521
	 * </tr>
522
	 * <tr>
523
	 * <td>Value</td>
524
	 * <td>Variable</td>
525
	 * <td>Octet String</td>
526
	 * <td>Short message user data. The maximum size is SMSC and network
527
	 * implementation specific.</td>
528
	 * </tr>
529
	 * </tbody>
530
	 * </table>
531
	 */
532
	MESSAGE_PAYLOAD("message_payload", 0x0424),
533
	/**
534
	 * <p>
535
	 * The sc_interface_version parameter is used to indicate the SMPP version
536
	 * supported by the SMSC. It is returned in the bind response PDUs.
537
	 * </p>
538
	 * <table><caption>sc_interface_version</caption>
539
	 * <thead>
540
	 * <tr>
541
	 * <th>Field Name</th>
542
	 * <th>Size octets</th>
543
	 * <th>Type</th>
544
	 * <th>Description</th>
545
	 * </tr>
546
	 * </thead> <tbody>
547
	 * <tr>
548
	 * <td>Parameter Tag</td>
549
	 * <td>2</td>
550
	 * <td>Integer</td>
551
	 * <td>sc_interface_version</td>
552
	 * </tr>
553
	 * <tr>
554
	 * <td>Length</td>
555
	 * <td>2</td>
556
	 * <td>Integer</td>
557
	 * <td>Length of value part in octets</td>
558
	 * </tr>
559
	 * <tr>
560
	 * <td>Value</td>
561
	 * <td>1</td>
562
	 * <td>Integer</td>
563
	 * <td>values as per 5.2.4. (interface_version)</td>
564
	 * </tr>
565
	 * </tbody>
566
	 * </table>
567
	 */
568
	SC_INTERFACE_VERSION("sc_interface_version", 0x0210),
569
	/**
570
	 * <p>
571
	 * The display_time parameter is used to associate a display time of the
572
	 * short message on the MS.
573
	 * </p>
574
	 * <table><caption>display_time</caption>
575
	 * <thead>
576
	 * <tr>
577
	 * <th>Field Name</th>
578
	 * <th>Size octets</th>
579
	 * <th>Type</th>
580
	 * <th>Description</th>
581
	 * </tr>
582
	 * </thead> <tbody>
583
	 * <tr>
584
	 * <td>Parameter Tag</td>
585
	 * <td>2</td>
586
	 * <td>Integer</td>
587
	 * <td>display_time</td>
588
	 * </tr>
589
	 * <tr>
590
	 * <td>Length</td>
591
	 * <td>2</td>
592
	 * <td>Integer</td>
593
	 * <td>Length of value part in octets</td>
594
	 * </tr>
595
	 * <tr>
596
	 * <td>Value</td>
597
	 * <td>1</td>
598
	 * <td>Integer</td>
599
	 * <td>0 = Temporary<br>
600
	 * 1 = Default (default)<br>
601
	 * 2 = Invoke<br>
602
	 * values 3 to 255 are reserved</td>
603
	 * </tr>
604
	 * </tbody>
605
	 * </table>
606
	 */
607
	DISPLAY_TIME("display_time", 0x1201),
608
	/**
609
	 * <p>
610
	 * The ms_validity parameter is used to provide an MS with validity
611
	 * information associated with the received short message.
612
	 * </p>
613
	 * <table><caption>ms_validity</caption>
614
	 * <thead>
615
	 * <tr>
616
	 * <th>Field Name</th>
617
	 * <th>Size octets</th>
618
	 * <th>Type</th>
619
	 * <th>Description</th>
620
	 * </tr>
621
	 * </thead> <tbody>
622
	 * <tr>
623
	 * <td>Parameter Tag</td>
624
	 * <td>2</td>
625
	 * <td>Integer</td>
626
	 * <td>ms_validity</td>
627
	 * </tr>
628
	 * <tr>
629
	 * <td>Length</td>
630
	 * <td>2</td>
631
	 * <td>Integer</td>
632
	 * <td>Length of value part in octets</td>
633
	 * </tr>
634
	 * <tr>
635
	 * <td>Value</td>
636
	 * <td>1</td>
637
	 * <td>Integer</td>
638
	 * <td>0 = Store Indefinitely (default)<br>
639
	 * 1 = Power Down <br>
640
	 * 2 = SID based registration area <br>
641
	 * 3 = Display Only <br>
642
	 * values 4 to 255 are reserved</td>
643
	 * </tr>
644
	 * </tbody>
645
	 * </table>
646
	 */
647
	MS_VALIDITY("ms_validity", 0x1204),
648
	/**
649
	 * <p>
650
	 * The dpf_result parameter is used in the data_sm_resp PDU to indicate if
651
	 * delivery pending flag (DPF) was set for a delivery failure of the short
652
	 * message..
653
	 * </p>
654
	 * <p>
655
	 * If the dpf_result parameter is not included in the data_sm_resp PDU, the
656
	 * ESME should assume that DPF is not set.
657
	 * </p>
658
	 * <p>
659
	 * Currently this parameter is only applicable for the Transaction message
660
	 * mode.
661
	 * </p>
662
	 * <table><caption>dpf_result</caption>
663
	 * <thead>
664
	 * <tr>
665
	 * <th>Field Name</th>
666
	 * <th>Size octets</th>
667
	 * <th>Type</th>
668
	 * <th>Description</th>
669
	 * </tr>
670
	 * </thead> <tbody>
671
	 * <tr>
672
	 * <td>Parameter Tag</td>
673
	 * <td>2</td>
674
	 * <td>Integer</td>
675
	 * <td>dpf_result</td>
676
	 * </tr>
677
	 * <tr>
678
	 * <td>Length</td>
679
	 * <td>2</td>
680
	 * <td>Integer</td>
681
	 * <td>Length of value part in octets</td>
682
	 * </tr>
683
	 * <tr>
684
	 * <td>Value</td>
685
	 * <td>1</td>
686
	 * <td>Integer</td>
687
	 * <td>0 = DPF not set<br>
688
	 * 1 = DPF set<br>
689
	 * values 2 to 255 are reserved</td>
690
	 * </tr>
691
	 * </tbody>
692
	 * </table>
693
	 */
694
	DPF_RESULT("dpf_result", 0x0420),
695
	/**
696
	 * <p>
697
	 * An ESME may use the set_dpf parameter to request the setting of a
698
	 * delivery pending flag (DPF) for certain delivery failure scenarios, such
699
	 * as
700
	 * </p>
701
	 * <ul>
702
	 * <li>MS is unavailable for message delivery (as indicated by the HLR)</li>
703
	 * </ul>
704
	 * <p>
705
	 * The SMSC should respond to such a request with an alert_notification PDU
706
	 * when it detects that the destination MS has become available.
707
	 * </p>
708
	 * <p>
709
	 * The delivery failure scenarios under which DPF is set is SMSC
710
	 * implementation and network implementation specific. If a delivery pending
711
	 * flag is set by the SMSC or network (e.g. HLR), then the SMSC should
712
	 * indicate this to the ESME in the data_sm_resp message via the dpf_result
713
	 * parameter.
714
	 * </p>
715
	 * <table><caption>set_dpf</caption>
716
	 * <thead>
717
	 * <tr>
718
	 * <th>Field Name</th>
719
	 * <th>Size octets</th>
720
	 * <th>Type</th>
721
	 * <th>Description</th>
722
	 * </tr>
723
	 * </thead> <tbody>
724
	 * <tr>
725
	 * <td>Parameter Tag</td>
726
	 * <td>2</td>
727
	 * <td>Integer</td>
728
	 * <td>set_dpf</td>
729
	 * </tr>
730
	 * <tr>
731
	 * <td>Length</td>
732
	 * <td>2</td>
733
	 * <td>Integer</td>
734
	 * <td>length of value part in octets</td>
735
	 * </tr>
736
	 * <tr>
737
	 * <td>Value</td>
738
	 * <td>1</td>
739
	 * <td>Integer</td>
740
	 * <td>0 = Setting of DPF for delivery failure to MS not requested<br>
741
	 * 1 = Setting of DPF for delivery failure requested (default) <br>
742
	 * values 2 to 255 are reserved</td>
743
	 * </tr>
744
	 * </tbody>
745
	 * </table>
746
	 */
747
	SET_DPF("set_dpf", 0x0421),
748
	/**
749
	 * <p>
750
	 * The ms_availability_status parameter is used in the alert_notification
751
	 * operation to indicate the availability state of the MS to the ESME.
752
	 * </p>
753
	 * <p>
754
	 * If the SMSC does not include the parameter in the alert_notification
755
	 * operation, the ESME should assume that the MS is in an "available" state.
756
	 * </p>
757
	 * <table><caption>ms_availability_status</caption>
758
	 * <thead>
759
	 * <tr>
760
	 * <th>Field Name</th>
761
	 * <th>Size octets</th>
762
	 * <th>Type</th>
763
	 * <th>Description</th>
764
	 * </tr>
765
	 * </thead> <tbody>
766
	 * <tr>
767
	 * <td>Parameter Tag</td>
768
	 * <td>2</td>
769
	 * <td>Integer</td>
770
	 * <td>ms_availability_status</td>
771
	 * </tr>
772
	 * <tr>
773
	 * <td>Length</td>
774
	 * <td>2</td>
775
	 * <td>Integer</td>
776
	 * <td>Length of value part in octets</td>
777
	 * </tr>
778
	 * <tr>
779
	 * <td>Value</td>
780
	 * <td>1</td>
781
	 * <td>Integer</td>
782
	 * <td>0 = Available (Default)<br>
783
	 * 1 = Denied (e.g. suspended, no SMS capability, etc.)<br>
784
	 * 2 = Unavailable values 3 to 255 are reserved</td>
785
	 * </tr>
786
	 * </tbody>
787
	 * </table>
788
	 */
789
	MS_AVAILABILITY_STATUS("ms_availability_status", 0x0422),
790
	/**
791
	 * <p>
792
	 * The network_error_code parameter is used to indicate the actual network
793
	 * error code for a delivery failure. The network error code is technology
794
	 * specific.
795
	 * </p>
796
	 * <table><caption>network_error_code</caption>
797
	 * <thead>
798
	 * <tr>
799
	 * <th>Field Name</th>
800
	 * <th>Size octets</th>
801
	 * <th>Type</th>
802
	 * <th>Description</th>
803
	 * </tr>
804
	 * </thead> <tbody>
805
	 * <tr>
806
	 * <td>Parameter Tag</td>
807
	 * <td>2</td>
808
	 * <td>Integer</td>
809
	 * <td>network_error_code</td>
810
	 * </tr>
811
	 * <tr>
812
	 * <td>Length</td>
813
	 * <td>2</td>
814
	 * <td>Integer</td>
815
	 * <td>Length of value part in octets</td>
816
	 * </tr>
817
	 * <tr>
818
	 * <td>Value</td>
819
	 * <td>3</td>
820
	 * <td>Octet String</td>
821
	 * <td>
822
	 * <p>
823
	 * The first octet indicates the network type. The following values are
824
	 * defined:
825
	 * </p>
826
	 * <ul>
827
	 * <li>1 = ANSI-136</li>
828
	 * <li>2 = IS-95</li>
829
	 * <li>3 = GSM</li>
830
	 * <li>4 = Reserved</li>
831
	 * <li>All other values reserved.</li>
832
	 * </ul>
833
	 * <p>
834
	 * The remaining two octets specify the actual network error code
835
	 * appropriate to the network type.
836
	 * </p>
837
	 * </td>
838
	 * </tr>
839
	 * </tbody>
840
	 * </table>
841
	 */
842
	NETWORK_ERROR_CODE("network_error_code", 0x0423),
843
	/**
844
	 * <p>
845
	 * The delivery_failure_reason parameter is used in the data_sm_resp
846
	 * operation to indicate the outcome of the message delivery attempt (only
847
	 * applicable for transaction message mode). If a delivery failure due to a
848
	 * network error is indicated, the ESME may check the network_error_code
849
	 * parameter (if present) for the actual network error code.
850
	 * </p>
851
	 * <p>
852
	 * The delivery_failure_reason parameter is not included if the delivery
853
	 * attempt was successful.
854
	 * </p>
855
	 * <table><caption>delivery_failure_reason</caption>
856
	 * <thead>
857
	 * <tr>
858
	 * <th>Field Name</th>
859
	 * <th>Size octets</th>
860
	 * <th>Type</th>
861
	 * <th>Description</th>
862
	 * </tr>
863
	 * </thead> <tbody>
864
	 * <tr>
865
	 * <td>Parameter Tag</td>
866
	 * <td>2</td>
867
	 * <td>Integer</td>
868
	 * <td>delivery_failure_reason</td>
869
	 * </tr>
870
	 * <tr>
871
	 * <td>Length</td>
872
	 * <td>2</td>
873
	 * <td>Integer</td>
874
	 * <td>Length of value part in octets</td>
875
	 * </tr>
876
	 * <tr>
877
	 * <td>Value</td>
878
	 * <td>1</td>
879
	 * <td>Integer</td>
880
	 * <td>0 = Destination unavailable<br>
881
	 * 1 = Destination Address Invalid (e.g.<br>
882
	 * suspended, no SMS capability, etc.)<br>
883
	 * 2 = Permanent network error<br>
884
	 * 3 = Temporary network error<br>
885
	 * values 4 to are 255 reserved</td>
886
	 * </tr>
887
	 * </tbody>
888
	 * </table>
889
	 */
890
	DELIVERY_FAILURE_REASON("delivery_failure_reason", 0x0425),
891
	/**
892
	 * <p>
893
	 * The more_messages_to_send parameter is used by the ESME in the submit_sm
894
	 * and data_sm operations to indicate to the SMSC that there are further
895
	 * messages for the same destination SME. The SMSC may use this setting for
896
	 * network resource optimization.
897
	 * </p>
898
	 * <table><caption>more_messages_to_send</caption>
899
	 * <thead>
900
	 * <tr>
901
	 * <th>Field Name</th>
902
	 * <th>Size octets</th>
903
	 * <th>Type</th>
904
	 * <th>Description</th>
905
	 * </tr>
906
	 * </thead> <tbody>
907
	 * <tr>
908
	 * <td>Parameter Tag</td>
909
	 * <td>2</td>
910
	 * <td>Integer</td>
911
	 * <td>more_messages_to_send</td>
912
	 * </tr>
913
	 * <tr>
914
	 * <td>Length</td>
915
	 * <td>2</td>
916
	 * <td>Integer</td>
917
	 * <td>Length of value part in octets</td>
918
	 * </tr>
919
	 * <tr>
920
	 * <td>Value</td>
921
	 * <td>1</td>
922
	 * <td>&nbsp;</td>
923
	 * <td>0 = No more messages to follow; 1 = More messages to follow (default)
924
	 * values 2 to 255 are reserved</td>
925
	 * </tr>
926
	 * </tbody>
927
	 * </table>
928
	 */
929
	MORE_MESSAGES_TO_SEND("more_messages_to_send", 0x0426),
930
	/**
931
	 * <p>
932
	 * The message_state optional parameter is used by the SMSC in the
933
	 * deliver_sm and data_sm PDUs to indicate to the ESME the final message
934
	 * state for an SMSC Delivery Receipt.
935
	 * </p>
936
	 * <table><caption>message_state</caption>
937
	 * <thead>
938
	 * <tr>
939
	 * <th>Field Name</th>
940
	 * <th>Size octets</th>
941
	 * <th>Type</th>
942
	 * <th>Description</th>
943
	 * </tr>
944
	 * </thead> <tbody>
945
	 * <tr>
946
	 * <td>Parameter Tag</td>
947
	 * <td>2</td>
948
	 * <td>Integer</td>
949
	 * <td>message_state</td>
950
	 * </tr>
951
	 * <tr>
952
	 * <td>Length</td>
953
	 * <td>2</td>
954
	 * <td>Integer</td>
955
	 * <td>Length of value part in octets</td>
956
	 * </tr>
957
	 * <tr>
958
	 * <td>Value</td>
959
	 * <td>1</td>
960
	 * <td>&nbsp;</td>
961
	 * <td>Values as per section 5.2.28</td>
962
	 * </tr>
963
	 * </tbody>
964
	 * </table>
965
	 */
966
	MESSAGE_STATE("message_state", 0x0427),
967
	/**
968
	 * <table><caption>callback_num_pres_ind</caption>
969
	 * <thead>
970
	 * <tr>
971
	 * <th>Field Name</th>
972
	 * <th>Size octets</th>
973
	 * <th>Type</th>
974
	 * <th>Description</th>
975
	 * </tr>
976
	 * </thead> <tbody>
977
	 * <tr>
978
	 * <td>Parameter Tag</td>
979
	 * <td>2</td>
980
	 * <td>Integer</td>
981
	 * <td>callback_num_pres_ind</td>
982
	 * </tr>
983
	 * <tr>
984
	 * <td>Length</td>
985
	 * <td>2</td>
986
	 * <td>Integer</td>
987
	 * <td>Length of Value part in octets</td>
988
	 * </tr>
989
	 * <tr>
990
	 * <td>Value</td>
991
	 * <td>1</td>
992
	 * <td>Bit mask</td>
993
	 * <td>
994
	 * <p>
995
	 * <b> Bits 7............0<br>
996
	 * 0000ppss </b>
997
	 * </p>
998
	 * <p>
999
	 * This parameter controls the presentation indication and screening of the
1000
	 * CallBackNumber at the mobile station.If present, the callback_num
1001
	 * parameter must also be present.
1002
	 * </p>
1003
	 * <p>
1004
	 * The Presentation Indicator is encoded in bits 2 and 3 as follows:
1005
	 * </p>
1006
	 * <p>
1007
	 * 00 = Presentation Allowed
1008
	 * </p>
1009
	 * <p>
1010
	 * 01 = Presentation Restricted
1011
	 * </p>
1012
	 * <p>
1013
	 * 10 = Number Not Available
1014
	 * </p>
1015
	 * <p>
1016
	 * 11 = Reserved
1017
	 * </p>
1018
	 * 
1019
	 * <p>
1020
	 * The Screening Indicator is encoded in bits 0 and 1 as follows:
1021
	 * </p>
1022
	 * <p>
1023
	 * 00 = User provided, not screened
1024
	 * </p>
1025
	 * <p>
1026
	 * 01 = User provided, verified and passed
1027
	 * </p>
1028
	 * <p>
1029
	 * 10 = User provided, verified and failed
1030
	 * </p>
1031
	 * <p>
1032
	 * 11 = Network Provided.
1033
	 * </p>
1034
	 * </td>
1035
	 * </tr>
1036
	 * </tbody>
1037
	 * </table>
1038
	 */
1039
	CALLBACK_NUM_PRES_IND("callback_num_pres_ind", 0x0302),
1040
	/**
1041
	 * <p>
1042
	 * The callback_num_atag parameter associates an alphanumeric display with
1043
	 * the call back number.
1044
	 * </p>
1045
	 * <table><caption>callback_num_atag</caption>
1046
	 * <thead>
1047
	 * <tr>
1048
	 * <th>Field Name</th>
1049
	 * <th>Size octets</th>
1050
	 * <th>Type</th>
1051
	 * <th>Description</th>
1052
	 * </tr>
1053
	 * </thead> <tbody>
1054
	 * <tr>
1055
	 * <td>Parameter Tag</td>
1056
	 * <td>2</td>
1057
	 * <td>Integer</td>
1058
	 * <td>callback_num_atag</td>
1059
	 * </tr>
1060
	 * <tr>
1061
	 * <td>Length</td>
1062
	 * <td>2</td>
1063
	 * <td>Integer</td>
1064
	 * <td>Length of Value part in octets</td>
1065
	 * </tr>
1066
	 * <tr>
1067
	 * <td>Value</td>
1068
	 * <td>Var max 65</td>
1069
	 * <td>Octet string</td>
1070
	 * <td>
1071
	 * <p>
1072
	 * Alphanumeric display tag for call back number
1073
	 * </p>
1074
	 * 
1075
	 * <pre class="aclSourceCodeInTable">
1076
	Bits 7...............0
1077
	EEEEEEEE (octet 1)
1078
	XXXXXXXX (octet 2)
1079
	:
1080
	:
1081
	XXXXXXXX (octet N)
1082
	 * </pre>
1083
	 * <p>
1084
	 * The first octet contains the encoding scheme of the Alpha Tag display
1085
	 * characters. This field contains the same values as for Data Coding Scheme
1086
	 * (see section 5.2.19). The following octets contain the display
1087
	 * characters: There is one octet per display character for 7-bit and 8-bit
1088
	 * encoding schemes. There are two octets per display character for 16-bit
1089
	 * encoding schemes.
1090
	 * </p>
1091
	 * </td>
1092
	 * </tr>
1093
	 * </tbody>
1094
	 * </table>
1095
	 */
1096
	CALLBACK_NUM_ATAG("callback_num_atag", 0x0303),
1097
	/**
1098
	 * <p>
1099
	 * The number_of_messages parameter is used to indicate the number of
1100
	 * messages stored in a mailbox.
1101
	 * </p>
1102
	 * <table><caption>number_of_messages</caption>
1103
	 * <thead>
1104
	 * <tr>
1105
	 * <th>Field Name</th>
1106
	 * <th>Size octets</th>
1107
	 * <th>Type</th>
1108
	 * <th>Description</th>
1109
	 * </tr>
1110
	 * </thead> <tbody>
1111
	 * <tr>
1112
	 * <td>Parameter Tag</td>
1113
	 * <td>2</td>
1114
	 * <td>Integer</td>
1115
	 * <td>number_of_messages</td>
1116
	 * </tr>
1117
	 * <tr>
1118
	 * <td>Length</td>
1119
	 * <td>2</td>
1120
	 * <td>Integer</td>
1121
	 * <td>Length of Value part in octets</td>
1122
	 * </tr>
1123
	 * <tr>
1124
	 * <td>Value</td>
1125
	 * <td>1</td>
1126
	 * <td>Integer</td>
1127
	 * <td>0 to 99 = allowed values. Values 100 to 255 are reserved</td>
1128
	 * </tr>
1129
	 * </tbody>
1130
	 * </table>
1131
	 */
1132
	NUMBER_OF_MESSAGES("number_of_messages", 0x0304),
1133
	/**
1134
	 * <p>
1135
	 * The sms_signal parameter is used to provide a TDMA MS with alert tone
1136
	 * information associated with the received short message.
1137
	 * </p>
1138
	 * <table><caption>sms_signal</caption>
1139
	 * <thead>
1140
	 * <tr>
1141
	 * <th>Field Name</th>
1142
	 * <th>Size octets</th>
1143
	 * <th>Type</th>
1144
	 * <th>Description</th>
1145
	 * </tr>
1146
	 * </thead> <tbody>
1147
	 * <tr>
1148
	 * <td>Parameter Tag</td>
1149
	 * <td>2</td>
1150
	 * <td>Integer</td>
1151
	 * <td>sms_signal</td>
1152
	 * </tr>
1153
	 * <tr>
1154
	 * <td>Length</td>
1155
	 * <td>2</td>
1156
	 * <td>Integer</td>
1157
	 * <td>Length of Value part in octets</td>
1158
	 * </tr>
1159
	 * <tr>
1160
	 * <td>Value</td>
1161
	 * <td>2</td>
1162
	 * <td>Integer</td>
1163
	 * <td>Encoded as per [CMT-136]</td>
1164
	 * </tr>
1165
	 * </tbody>
1166
	 * </table>
1167
	 */
1168
	SMS_SIGNAL("sms_signal", 0x1203),
1169
	/**
1170
	 * <p>
1171
	 * The alert_on_message_delivery parameter is set to instruct a MS to alert
1172
	 * the user (in a MS implementation specific manner) when the short message
1173
	 * arrives at the MS.
1174
	 * </p>
1175
	 * <table><caption>alert_on_message_delivery</caption>
1176
	 * <thead>
1177
	 * <tr>
1178
	 * <th>Field Name</th>
1179
	 * <th>Size octets</th>
1180
	 * <th>Type</th>
1181
	 * <th>Description</th>
1182
	 * </tr>
1183
	 * </thead> <tbody>
1184
	 * <tr>
1185
	 * <td>Parameter Tag</td>
1186
	 * <td>2</td>
1187
	 * <td>Integer</td>
1188
	 * <td>alert_on_message_delivery</td>
1189
	 * </tr>
1190
	 * <tr>
1191
	 * <td>Length</td>
1192
	 * <td>2</td>
1193
	 * <td>Integer</td>
1194
	 * <td>Length of Value part in octets (= 0)</td>
1195
	 * </tr>
1196
	 * <tr>
1197
	 * <td>Value</td>
1198
	 * <td>0</td>
1199
	 * <td>No Value</td>
1200
	 * <td>&nbsp;</td>
1201
	 * </tr>
1202
	 * </tbody>
1203
	 * </table>
1204
	 */
1205
	ALERT_ON_MESSAGE_DELIVERY("alert_on_message_delivery", 0x130C),
1206
	/**
1207
	 * <p>
1208
	 * The its_reply_type parameter is a required parameter for the CDMA
1209
	 * Interactive Teleservice as defined by the Korean PCS carriers [KORITS].
1210
	 * It indicates and controls the MS user's reply method to an SMS delivery
1211
	 * message received from the ESME.
1212
	 * </p>
1213
	 * <table><caption>its_reply_type</caption>
1214
	 * <thead>
1215
	 * <tr>
1216
	 * <th>Field Name</th>
1217
	 * <th>Size octets</th>
1218
	 * <th>Type</th>
1219
	 * <th>Description</th>
1220
	 * </tr>
1221
	 * </thead> <tbody>
1222
	 * <tr>
1223
	 * <td>Parameter Tag</td>
1224
	 * <td>2</td>
1225
	 * <td>Integer</td>
1226
	 * <td>its_reply_type</td>
1227
	 * </tr>
1228
	 * <tr>
1229
	 * <td>Length</td>
1230
	 * <td>2</td>
1231
	 * <td>Integer</td>
1232
	 * <td>Length of Value part in octets</td>
1233
	 * </tr>
1234
	 * <tr>
1235
	 * <td>Value</td>
1236
	 * <td>1</td>
1237
	 * <td>Integer</td>
1238
	 * <td>
1239
	 * 
1240
	 * <pre class="aclSourceCodeInTable">
1241
	 * 0 = Digit 
1242
	1 = Number 
1243
	2 = Telephone No. 
1244
	3 = Password 
1245
	4 = Character Line 
1246
	5 = Menu 
1247
	6 = Date 
1248
	7 = Time 
1249
	8 = Continue 
1250
	values 9 to 255 are reserved
1251
	 * </pre>
1252
	 * 
1253
	 * </td>
1254
	 * </tr>
1255
	 * </tbody>
1256
	 * </table>
1257
	 */
1258
	ITS_REPLY_TYPE("its_reply_type", 0x1380),
1259
	/**
1260
	 * <p>
1261
	 * The its_session_info parameter is a required parameter for the CDMA
1262
	 * Interactive Teleservice as defined by the Korean PCS carriers [KORITS].
1263
	 * It contains control information for the interactive session between an MS
1264
	 * and an ESME.
1265
	 * </p>
1266
	 * <table><caption>its_session_info</caption>
1267
	 * <thead>
1268
	 * <tr>
1269
	 * <th>Field Name</th>
1270
	 * <th>Size octets</th>
1271
	 * <th>Type</th>
1272
	 * <th>Description</th>
1273
	 * </tr>
1274
	 * </thead> <tbody>
1275
	 * <tr>
1276
	 * <td>Parameter Tag</td>
1277
	 * <td>2</td>
1278
	 * <td>Integer</td>
1279
	 * <td>its_session_info</td>
1280
	 * </tr>
1281
	 * <tr>
1282
	 * <td>Length</td>
1283
	 * <td>2</td>
1284
	 * <td>Integer</td>
1285
	 * <td>Length of Value part in octets</td>
1286
	 * </tr>
1287
	 * <tr>
1288
	 * <td>Value</td>
1289
	 * <td>2</td>
1290
	 * <td>Octet String</td>
1291
	 * <td>
1292
	 * 
1293
	 * <pre class="aclSourceCodeInTable">
1294
	 * Bits 7...............0 
1295
	SSSS SSSS (octet 1) 
1296
	NNNN NNNE (octet 2)
1297
	 * </pre>
1298
	 * <p>
1299
	 * Octet 1 contains the session number (0 - 255) encoded in binary. The
1300
	 * session number remains constant for each session.
1301
	 * </p>
1302
	 * <p>
1303
	 * The sequence number of the dialogue unit (as assigned by the ESME) within
1304
	 * the session is encoded in bits 7..1 of octet 2.
1305
	 * </p>
1306
	 * <p>
1307
	 * The End of Session Indicator indicates the message is the end of the
1308
	 * conversation session and is encoded in bit 0 of octet 2 as follows: 0 =
1309
	 * End of Session Indicator inactive. 1 = End of Session Indicator active.
1310
	 * </p>
1311
	 * </td>
1312
	 * </tr>
1313
	 * </tbody>
1314
	 * </table>
1315
	 */
1316
	ITS_SESSION_INFO("its_session_info", 0x1383),
1317
	/**
1318
	 * <p>
1319
	 * The ussd_service_op parameter is required to define the USSD service
1320
	 * operation when SMPP is being used as an interface to a (GSM) USSD system.
1321
	 * </p>
1322
	 * <table><caption>ussd_service_op</caption>
1323
	 * <thead>
1324
	 * <tr>
1325
	 * <th>Field Name</th>
1326
	 * <th>Size octets</th>
1327
	 * <th>Type</th>
1328
	 * <th>Description</th>
1329
	 * </tr>
1330
	 * </thead> <tbody>
1331
	 * <tr>
1332
	 * <td>Parameter Tag</td>
1333
	 * <td>2</td>
1334
	 * <td>Integer</td>
1335
	 * <td>ussd_service_op</td>
1336
	 * </tr>
1337
	 * <tr>
1338
	 * <td>Length</td>
1339
	 * <td>2</td>
1340
	 * <td>Integer</td>
1341
	 * <td>Length of Value part in octets</td>
1342
	 * </tr>
1343
	 * <tr>
1344
	 * <td>Value</td>
1345
	 * <td>1</td>
1346
	 * <td>Octet String</td>
1347
	 * <td>
1348
	 * 
1349
	 * <pre class="aclSourceCodeInTable">
1350
	 * 0 = PSSD indication 
1351
	1 = PSSR indication 
1352
	2 = USSR request 
1353
	3 = USSN request 
1354
	4 to 15 = reserved 
1355
	
1356
	16 = PSSD response 
1357
	17 = PSSR response 
1358
	18 = USSR confirm 
1359
	19 = USSN confirm 
1360
	
1361
	20 to 31 = reserved 
1362
	32 to 255 = reserved for vendor specific 
1363
	USSD operations
1364
	 * </pre>
1365
	 * 
1366
	 * </td>
1367
	 * </tr>
1368
	 * </tbody>
1369
	 * </table>
1370
	 */
1371
	USSD_SERVICE_OP("ussd_service_op", 0x0501),
1372
	/**
1373
	 * Billing information passed from ESME to MC <br>
1374
	 * <br>
1375
	 * Bits 7......0 <br>
1376
	 * 0XXXXXXX (Reserved) <br>
1377
	 * 1XXXXXXX (Vendor Specific) <br>
1378
	 * The first octet represents the Billing Format tag and indicates the
1379
	 * format of the billing information in the remaining octets. <br>
1380
	 * The remaining octets contain the billing information. <br>
1381
	 * <br>
1382
	 * Wireless Network Technology: Generic
1383
	 *
1384
	 */
1385
	BILLING_IDENTIFICATION("billing_identification", 0x060B),
1386
	/**
1387
	 * <p>
1388
	 * The dest_addr_subunit parameter is used to route messages when received
1389
	 * by a mobile station, for example to a smart card in the mobile station or
1390
	 * to an external device connected to the mobile station.
1391
	 * </p>
1392
	 * <table><caption>dest_addr_subunit</caption>
1393
	 * <thead>
1394
	 * <tr>
1395
	 * <th>Field Name</th>
1396
	 * <th>Size octets</th>
1397
	 * <th>Type</th>
1398
	 * <th>Description</th>
1399
	 * </tr>
1400
	 * </thead> <tbody>
1401
	 * <tr>
1402
	 * <td>Parameter Tag</td>
1403
	 * <td>2</td>
1404
	 * <td>Integer</td>
1405
	 * <td>dest_addr_subunit</td>
1406
	 * </tr>
1407
	 * <tr>
1408
	 * <td>Length</td>
1409
	 * <td>2</td>
1410
	 * <td>Integer</td>
1411
	 * <td>Length of Value part in octets</td>
1412
	 * </tr>
1413
	 * <tr>
1414
	 * <td>Value</td>
1415
	 * <td>1</td>
1416
	 * <td>Integer</td>
1417
	 * <td>0x00 = Unknown (default)<br>
1418
	 * 0x01 = MS Display <br>
1419
	 * 0x02 = Mobile Equipment<br>
1420
	 * 0x03 = Smart Card 1 (expected to be SIM if<br>
1421
	 * a SIM exists in the MS)<br>
1422
	 * 0x04 = External Unit 1<br>
1423
	 * 5 to 255 = reserved</td>
1424
	 * </tr>
1425
	 * </tbody>
1426
	 * </table>
1427
	 */
1428
	DEST_ADDR_SUBUNIT("dest_addr_subunit", 0x0005),
1429
	/**
1430
	 * The dest_network_type parameter is used to indicate a network type
1431
	 * associated with the destination address of a message. In the case that
1432
	 * the receiving system (e.g. SMSC) does not support the indicated network
1433
	 * type, it may treat this a failure and return a response PDU reporting a
1434
	 * failure.
1435
	 */
1436
	DEST_NETWORK_TYPE("dest_network_type", 0x0006),
1437
	/**
1438
	 * <p>
1439
	 * The dest_bearer_type parameter is used to request the desired bearer for
1440
	 * delivery of the message to the destination address. In the case that the
1441
	 * receiving system (e.g. SMSC) does not support the indicated bearer type,
1442
	 * it may treat this a failure and return a response PDU reporting a
1443
	 * failure.
1444
	 * </p>
1445
	 * <table><caption>dest_bearer_type</caption>
1446
	 * <thead>
1447
	 * <tr>
1448
	 * <th>Field Name</th>
1449
	 * <th>Size octets</th>
1450
	 * <th>Type</th>
1451
	 * <th>Description</th>
1452
	 * </tr>
1453
	 * </thead> <tbody>
1454
	 * <tr>
1455
	 * <td>Parameter Tag</td>
1456
	 * <td>2</td>
1457
	 * <td>Integer</td>
1458
	 * <td>dest_bearer_type</td>
1459
	 * </tr>
1460
	 * <tr>
1461
	 * <td>Length</td>
1462
	 * <td>2</td>
1463
	 * <td>Integer</td>
1464
	 * <td>Length of Value part in octets</td>
1465
	 * </tr>
1466
	 * <tr>
1467
	 * <td>Value</td>
1468
	 * <td>1</td>
1469
	 * <td>Integer</td>
1470
	 * <td>0x00 = Unknown<br>
1471
	 * 0x01 = SMS<br>
1472
	 * 0x02 = Circuit Switched Data (CSD)<br>
1473
	 * 0x03 = Packet Data<br>
1474
	 * 0x04 = USSD<br>
1475
	 * 0x05 = CDPD<br>
1476
	 * 0x06 = DataTAC<br>
1477
	 * 0x07 = FLEX/ReFLEX<br>
1478
	 * 0x08 = Cell Broadcast (cellcast)<br>
1479
	 * 9 to 255 = reserved</td>
1480
	 * </tr>
1481
	 * </tbody>
1482
	 * </table>
1483
	 */
1484
	DEST_BEARER_TYPE("dest_bearer_type", 0x0007),
1485
	/**
1486
	 * <p>
1487
	 * This parameter defines the telematic interworking to be used by the
1488
	 * delivering system for the destination address. This is only useful when a
1489
	 * specific dest_bearer_type parameter has also been specified as the value
1490
	 * is bearer dependent. In the case that the receiving system (e.g. SMSC)
1491
	 * does not support the indicated telematic interworking, it may treat this
1492
	 * a failure and return a response PDU reporting a failure.
1493
	 * </p>
1494
	 * <table><caption>dest_telematics_id</caption>
1495
	 * <thead>
1496
	 * <tr>
1497
	 * <th>Field Name</th>
1498
	 * <th>Size octets</th>
1499
	 * <th>Type</th>
1500
	 * <th>Description</th>
1501
	 * </tr>
1502
	 * </thead> <tbody>
1503
	 * <tr>
1504
	 * <td>Parameter Tag</td>
1505
	 * <td>2</td>
1506
	 * <td>Integer</td>
1507
	 * <td>dest_telematics_id</td>
1508
	 * </tr>
1509
	 * <tr>
1510
	 * <td>Length</td>
1511
	 * <td>2</td>
1512
	 * <td>Integer</td>
1513
	 * <td>Length of Value part in octets</td>
1514
	 * </tr>
1515
	 * <tr>
1516
	 * <td>Value</td>
1517
	 * <td>2</td>
1518
	 * <td>Integer</td>
1519
	 * <td>to be defined</td>
1520
	 * </tr>
1521
	 * </tbody>
1522
	 * </table>
1523
	 */
1524
	DEST_TELEMATICS_ID("dest_telematics_id", 0x0008),
1525
	/**
1526
	 * <p>
1527
	 * The source_addr_subunit parameter is used to indicate where a message
1528
	 * originated in the mobile station, for example a smart card in the mobile
1529
	 * station or an external device connected to the mobile station.
1530
	 * </p>
1531
	 * <table><caption>source_addr_subunit</caption>
1532
	 * <thead>
1533
	 * <tr>
1534
	 * <th>Field Name</th>
1535
	 * <th>Size octets</th>
1536
	 * <th>Type</th>
1537
	 * <th>Description</th>
1538
	 * </tr>
1539
	 * </thead> <tbody>
1540
	 * <tr>
1541
	 * <td>Parameter Tag</td>
1542
	 * <td>2</td>
1543
	 * <td>Integer</td>
1544
	 * <td>source_addr_subunit</td>
1545
	 * </tr>
1546
	 * <tr>
1547
	 * <td>Length</td>
1548
	 * <td>2</td>
1549
	 * <td>Integer</td>
1550
	 * <td>Length of Value part in octets</td>
1551
	 * </tr>
1552
	 * <tr>
1553
	 * <td>Value</td>
1554
	 * <td>1</td>
1555
	 * <td>Integer</td>
1556
	 * <td>see 5.3.2.1</td>
1557
	 * </tr>
1558
	 * </tbody>
1559
	 * </table>
1560
	 */
1561
	SOURCE_ADDR_SUBUNIT("source_addr_subunit", 0x000D),
1562
	/**
1563
	 * <p>
1564
	 * The source_network_type parameter is used to indicate the network type
1565
	 * associated with the device that originated the message.
1566
	 * </p>
1567
	 * <table><caption>source_network_type</caption>
1568
	 * <thead>
1569
	 * <tr>
1570
	 * <th>Field Name</th>
1571
	 * <th>Size octets</th>
1572
	 * <th>Type</th>
1573
	 * <th>Description</th>
1574
	 * </tr>
1575
	 * </thead> <tbody>
1576
	 * <tr>
1577
	 * <td>Parameter Tag</td>
1578
	 * <td>2</td>
1579
	 * <td>Integer</td>
1580
	 * <td>source_network_type</td>
1581
	 * </tr>
1582
	 * <tr>
1583
	 * <td>Length</td>
1584
	 * <td>2</td>
1585
	 * <td>Integer</td>
1586
	 * <td>Length of Value part in octets</td>
1587
	 * </tr>
1588
	 * <tr>
1589
	 * <td>Value</td>
1590
	 * <td>1</td>
1591
	 * <td>Integer</td>
1592
	 * <td>see 5.3.2.3</td>
1593
	 * </tr>
1594
	 * </tbody>
1595
	 * </table>
1596
	 */
1597
	SOURCE_NETWORK_TYPE("source_network_type", 0x000E),
1598
	/**
1599
	 * <p>
1600
	 * The source_bearer_type parameter indicates the wireless bearer over which
1601
	 * the message originated.
1602
	 * </p>
1603
	 * <table><caption>source_bearer_type</caption>
1604
	 * <thead>
1605
	 * <tr>
1606
	 * <th>Field Name</th>
1607
	 * <th>Size octets</th>
1608
	 * <th>Type</th>
1609
	 * <th>Description</th>
1610
	 * </tr>
1611
	 * </thead> <tbody>
1612
	 * <tr>
1613
	 * <td>Parameter Tag</td>
1614
	 * <td>2</td>
1615
	 * <td>Integer</td>
1616
	 * <td>source_bearer_type</td>
1617
	 * </tr>
1618
	 * <tr>
1619
	 * <td>Length</td>
1620
	 * <td>2</td>
1621
	 * <td>Integer</td>
1622
	 * <td>Length of Value part in octets</td>
1623
	 * </tr>
1624
	 * <tr>
1625
	 * <td>Value</td>
1626
	 * <td>1</td>
1627
	 * <td>Integer</td>
1628
	 * <td>see 5.3.2.5</td>
1629
	 * </tr>
1630
	 * </tbody>
1631
	 * </table>
1632
	 */
1633
	SOURCE_BEARER_TYPE("source_bearer_type", 0x000F),
1634
	/**
1635
	 * <p>
1636
	 * The source_telematics_id parameter indicates the type of telematics
1637
	 * interface over which the message originated.
1638
	 * </p>
1639
	 * <table><caption>source_telematics_id</caption>
1640
	 * <thead>
1641
	 * <tr>
1642
	 * <th>Field Name</th>
1643
	 * <th>Size octets</th>
1644
	 * <th>Type</th>
1645
	 * <th>Description</th>
1646
	 * </tr>
1647
	 * </thead> <tbody>
1648
	 * <tr>
1649
	 * <td>Parameter Tag</td>
1650
	 * <td>2</td>
1651
	 * <td>Integer</td>
1652
	 * <td>source_telematics_id</td>
1653
	 * </tr>
1654
	 * <tr>
1655
	 * <td>Length</td>
1656
	 * <td>2</td>
1657
	 * <td>Integer</td>
1658
	 * <td>Length of Value part in octets</td>
1659
	 * </tr>
1660
	 * <tr>
1661
	 * <td>Value</td>
1662
	 * <td>1</td>
1663
	 * <td>Integer</td>
1664
	 * <td>see 5.3.2.7</td>
1665
	 * </tr>
1666
	 * </tbody>
1667
	 * </table>
1668
	 */
1669
	SOURCE_TELEMATICS_ID("source_telematics_id", 0x0010),
1670
	/**
1671
	 * <p>
1672
	 * This parameter defines the number of seconds which the sender requests
1673
	 * the SMSC to keep the message if undelivered before it is deemed expired
1674
	 * and not worth delivering. If the parameter is not present, the SMSC may
1675
	 * apply a default value.
1676
	 * </p>
1677
	 * <table><caption>qos_time_to_live</caption>
1678
	 * <thead>
1679
	 * <tr>
1680
	 * <th>Field Name</th>
1681
	 * <th>Size octets</th>
1682
	 * <th>Type</th>
1683
	 * <th>Description</th>
1684
	 * </tr>
1685
	 * </thead> <tbody>
1686
	 * <tr>
1687
	 * <td>Parameter Tag</td>
1688
	 * <td>2</td>
1689
	 * <td>Integer</td>
1690
	 * <td>qos_time_to_live</td>
1691
	 * </tr>
1692
	 * <tr>
1693
	 * <td>Length</td>
1694
	 * <td>2</td>
1695
	 * <td>Integer</td>
1696
	 * <td>Length of Value part in octets</td>
1697
	 * </tr>
1698
	 * <tr>
1699
	 * <td>Value</td>
1700
	 * <td>4</td>
1701
	 * <td>Integer</td>
1702
	 * <td>number of seconds for message to be retained by the receiving
1703
	 * system.</td>
1704
	 * </tr>
1705
	 * </tbody>
1706
	 * </table>
1707
	 */
1708
	QOS_TIME_TO_LIVE("qos_time_to_live", 0x0017),
1709
	/**
1710
	 * <p>
1711
	 * The additional_status_info_text parameter gives an ASCII textual
1712
	 * description of the meaning of a response PDU. It is to be used by an
1713
	 * implementation to allow easy diagnosis of problems.
1714
	 * </p>
1715
	 * <table><caption>additional_status_info</caption>
1716
	 * <thead>
1717
	 * <tr>
1718
	 * <th>Field Name</th>
1719
	 * <th>Size octets</th>
1720
	 * <th>Type</th>
1721
	 * <th>Description</th>
1722
	 * </tr>
1723
	 * </thead> <tbody>
1724
	 * <tr>
1725
	 * <td>Parameter Tag</td>
1726
	 * <td>2</td>
1727
	 * <td>Integer</td>
1728
	 * <td>additional_status_info_text</td>
1729
	 * </tr>
1730
	 * <tr>
1731
	 * <td>Length</td>
1732
	 * <td>2</td>
1733
	 * <td>Integer</td>
1734
	 * <td>Length of Value part in octets</td>
1735
	 * </tr>
1736
	 * <tr>
1737
	 * <td>Value</td>
1738
	 * <td>1 - 256</td>
1739
	 * <td>C Octet String</td>
1740
	 * <td>Free format text to allow implementations to supply the most useful
1741
	 * information for problem diagnosis. Maximum length is 256 octets.</td>
1742
	 * </tr>
1743
	 * </tbody>
1744
	 * </table>
1745
	 */
1746
	ADDITIONAL_STATUS_INFO("additional_status_info", 0x001D),
1747
	/**
1748
	 * <p>
1749
	 * The receipted_message_id parameter indicates the ID of the message being
1750
	 * receipted in an SMSC Delivery Receipt. This is the opaque SMSC message
1751
	 * identifier that was returned in the message_id parameter of the SMPP
1752
	 * response PDU that acknowledged the submission of the original message.
1753
	 * </p>
1754
	 * <table><caption>receipted_message_id</caption>
1755
	 * <thead>
1756
	 * <tr>
1757
	 * <th>Field Name</th>
1758
	 * <th>Size octets</th>
1759
	 * <th>Type</th>
1760
	 * <th>Description</th>
1761
	 * </tr>
1762
	 * </thead> <tbody>
1763
	 * <tr>
1764
	 * <td>Parameter Tag</td>
1765
	 * <td>2</td>
1766
	 * <td>Integer</td>
1767
	 * <td>receipted_message_id</td>
1768
	 * </tr>
1769
	 * <tr>
1770
	 * <td>Length</td>
1771
	 * <td>2</td>
1772
	 * <td>Integer</td>
1773
	 * <td>Length of Value part in octets</td>
1774
	 * </tr>
1775
	 * <tr>
1776
	 * <td>Value</td>
1777
	 * <td>1 - 65</td>
1778
	 * <td>C Octet String</td>
1779
	 * <td>SMSC handle of the message being receipted.</td>
1780
	 * </tr>
1781
	 * </tbody>
1782
	 * </table>
1783
	 */
1784
	RECEIPTED_MESSAGE_ID("receipted_message_id", 0x001E),
1785
	/**
1786
	 * <p>
1787
	 * The ms_msg_wait_facilities parameter allows an indication to be provided
1788
	 * to an MS that there are messages waiting for the subscriber on systems on
1789
	 * the PLMN. The indication can be an icon on the MS screen or other MMI
1790
	 * indication.
1791
	 * </p>
1792
	 * <p>
1793
	 * The ms_msg_wait_facilities can also specify the type of message
1794
	 * associated with the message waiting indication.
1795
	 * </p>
1796
	 */
1797
	MS_MSG_WAIT_FACILITIES("ms_msg_wait_facilities", 0x0030);
1798
1799
	private final String tagName;
1800
	private final short code;
1801
1802
	Tag(String tagName, int code) {
1803
		this.code = (short) code;
1804
		this.tagName = tagName;
1805
	}
1806
1807
	/**
1808
	 * @return the tag name
1809
	 */
1810
	public String getTagName() {
1811 3 1. getTagName : replaced return value with "" for fr/sii/ogham/testing/sms/simulator/bean/Tag::getTagName → SURVIVED
2. getTagName : replaced return value with "" for fr/sii/ogham/testing/sms/simulator/bean/Tag::getTagName → NO_COVERAGE
3. getTagName : replaced return value with "" for fr/sii/ogham/testing/sms/simulator/bean/Tag::getTagName → KILLED
		return tagName;
1812
	}
1813
1814
	/**
1815
	 * @return the code of the tag
1816
	 */
1817
	public short getCode() {
1818 3 1. getCode : replaced short return with 0 for fr/sii/ogham/testing/sms/simulator/bean/Tag::getCode → NO_COVERAGE
2. getCode : replaced short return with 0 for fr/sii/ogham/testing/sms/simulator/bean/Tag::getCode → KILLED
3. getCode : replaced short return with 0 for fr/sii/ogham/testing/sms/simulator/bean/Tag::getCode → KILLED
		return code;
1819
	}
1820
1821
}

Mutations

1811

1.1
Location : getTagName
Killed by : none
replaced return value with "" for fr/sii/ogham/testing/sms/simulator/bean/Tag::getTagName → SURVIVED

2.2
Location : getTagName
Killed by : none
replaced return value with "" for fr/sii/ogham/testing/sms/simulator/bean/Tag::getTagName → NO_COVERAGE

3.3
Location : getTagName
Killed by : oghamtesting.it.assertion.FluentSmsAssertionsSpec
replaced return value with "" for fr/sii/ogham/testing/sms/simulator/bean/Tag::getTagName → KILLED

1818

1.1
Location : getCode
Killed by : oghamcloudhopper.it.TlvMessagePayloadTest.simple(oghamcloudhopper.it.TlvMessagePayloadTest)
replaced short return with 0 for fr/sii/ogham/testing/sms/simulator/bean/Tag::getCode → KILLED

2.2
Location : getCode
Killed by : none
replaced short return with 0 for fr/sii/ogham/testing/sms/simulator/bean/Tag::getCode → NO_COVERAGE

3.3
Location : getCode
Killed by : oghamtesting.it.assertion.FluentSmsAssertionsSpec
replaced short return with 0 for fr/sii/ogham/testing/sms/simulator/bean/Tag::getCode → KILLED

Active mutators

Tests examined


Report generated by PIT OGHAM