@@ -142,7 +142,9 @@ <h2><a>Navigator</a> Interface</h2>
142
142
143
143
<!------------------------ Interface MessagingManager ------------------------------->
144
144
< section >
145
- < h2 > < a > MessagingManager</ a > Interface</ h2 > < p > The < a > MessagingManager</ a > interface
145
+ < h2 > < a > MessagingManager</ a > Interface</ h2 >
146
+
147
+ < p > The < a > MessagingManager</ a > interface
146
148
represents the initial entry point for getting access to the mobile messaging
147
149
services, i.e. SMS and MMS.
148
150
@@ -466,10 +468,11 @@ <h2><a>SmsManager</a> Interface</h2>
466
468
(e.g. 'sms_sim1').</ dd >
467
469
468
470
< dt > SmsSegmentInfo getSegmentInfoForText ()</ dt >
469
- < dd > This method returns an SmsSegmentInfo object including information on
470
- the number of concatenated SMS segments needed to send the text in the
471
- < code > text</ code > parameter, the number of characters available per segment
472
- and the maximum number of available characters in the last segment.
471
+ < dd > This method returns an < code > SmsSegmentInfo</ code > object including
472
+ information on the number of concatenated SMS segments needed to send the
473
+ text in the < code > text</ code > parameter, the number of characters available
474
+ per segment and the maximum number of available characters in the last
475
+ segment.
473
476
< dl class ='parameters '>
474
477
< dt > DOMString text</ dt >
475
478
< dd >
@@ -619,7 +622,9 @@ <h3>Steps</h3>
619
622
< ol >
620
623
< li > Set the < code > state</ code > of the < code > SmsMessage</ code > to 'sent'.
621
624
< li > Set the < code > timestamp</ code > of the < code > SmsMessage</ code > to the
622
- timestamp when the SMS message was actually sent.
625
+ timestamp when the SMS message reached the Short Message Center, i.e. the
626
+ value of the TP-Service-Centre-Time-Stamp (TP-SCTS) parameter returned in
627
+ the SMS-SUBMIT-REPORT Protocol Data Unit.
623
628
< li > Set the < code > readyState</ code > of the < code > MessagingRequest</ code >
624
629
object to 'done'.
625
630
< li > Set the < code > result</ code > of the < code > MessagingRequest</ code >
@@ -675,8 +680,9 @@ <h3>Steps</h3>
675
680
sender of the SMS message, i.e. the value of the TP Originating Address
676
681
(TP-OA) field of the SMS message.
677
682
< li > Set the < code > timestamp</ code > of the < code > SmsMessage</ code > to the
678
- timestamp of the SMS message, i.e. the value if the TP Service Centre
679
- Time Stamp (TP-SCTS) field of the SMS message.
683
+ timestamp of the SMS message, i.e. the value of the
684
+ TP-Service-Centre-Time-Stamp (TP-SCTS) parameter received in the SMS
685
+ DELIVER Protocol Data Unit.
680
686
< li > Set the < code > read</ code > of the < code > SmsMessage</ code > to 'false'.
681
687
< li > Set the < code > to</ code > of the < code > SmsMessage</ code > to the
682
688
recipient of the SMS message, i.e. the value of the TP Destination
@@ -1039,7 +1045,8 @@ <h3>Steps</h3>
1039
1045
< ol >
1040
1046
< li > Set the < code > state</ code > of the < code > MmsMessage</ code > to 'sent'.
1041
1047
< li > Set the < code > timestamp</ code > of the < code > MmsMessage</ code > to the
1042
- timestamp when the MMS message was actually sent.
1048
+ timestamp when the MMS message was sent, i.e. the date when the M-Send.req
1049
+ Protocol Data Unit was send from the MMS Client to the MMS Server.
1043
1050
< li > Set the < code > readyState</ code > of the < code > MessagingRequest</ code >
1044
1051
object to 'done'.
1045
1052
< li > Set the < code > result</ code > of the < code > MessagingRequest</ code >
@@ -1078,6 +1085,10 @@ <h3>Steps</h3>
1078
1085
< ol >
1079
1086
< li > Set the < code > from</ code > of the < code > MmsMessage</ code > to the
1080
1087
value of the 'From' field of the MMS notification, if present.
1088
+ < li > Set the < code > timestamp</ code > of the < code > MmsMessage</ code > to
1089
+ the timestamp of the binary SMS message used to transport the MMS
1090
+ notification, i.e. the value of the TP-Service-Centre-Time-Stamp
1091
+ (TP-SCTS) parameter received in the SMS-DELIVER Protocol Data Unit.
1081
1092
< li > Add a new element in the < code > to</ code > array of the
1082
1093
< code > MmsMessage</ code > for each of recipients in the 'To' field of the
1083
1094
MMS notification, if present.
@@ -1099,7 +1110,7 @@ <h3>Steps</h3>
1099
1110
Once the MMS has been fetched continue with following steps.
1100
1111
< li > Run the < dfn id ="dfn-fill-mms-message "> steps for filling the
1101
1112
< code > MmsMessage</ code > object with the data contained in the MMS
1102
- message</ dfn > .
1113
+ message enclosed in the M-Retrieve.conf Protocol Data Unit </ dfn > .
1103
1114
< ol >
1104
1115
< li > Set the < code > from</ code > of the < code > MmsMessage</ code > to the
1105
1116
value of the 'From' field of the MMS message.
@@ -1415,8 +1426,9 @@ <h2><a>SmsMessage</a> Interface</h2>
1415
1426
(TP-OA) of the SMS message.</ dd >
1416
1427
1417
1428
< dt > readonly attribute Date timestamp</ dt >
1418
- < dd > MUST return the time the message was sent at, i.e. the TP Service Centre
1419
- Time Stamp (TP-SCTS) of the SMS message.</ dd >
1429
+ < dd > MUST return the time the message reached the Short Message Center,
1430
+ indicated in the TP-Service-Centre-Time-Stamp (TP-SCTS) parameter of the SMS
1431
+ message.</ dd >
1420
1432
1421
1433
< dt > readonly attribute boolean read</ dt >
1422
1434
< dd > MUST return 'true' if the message has been marked as read, or 'false'
0 commit comments