Mobile messaging technologies and services sms ems and mms phần 3 ppsx

3.9 Message Submission In the context of SMS, the term submis sion refers to the transfer of a message segment from the originator SME to the serving SMSC (Figure 3.12). Once the message segment has been successfully received by the serving SMSC, the originator SMSC queries the HLR in order to route forward the message segment towards the recipient SME. At the transfer layer, a message segment is conveyed as part of a TPDU of type SMS- SUBMIT. The TPDU can contain the following parameters: † Message type (SMS-SUBMIT ) † Request for rejecting duplicated messages † Message validity period † Request for reply path † Request for a status report † Message reference † Address of the recipient SME † Protocol identifier † Data coding scheme † User data header † User data (with associated length). Upon receipt of the message by the serving SMSC, the SMSC provides a submission report to the originator SME. Two types of reports can be provided: a positive submission report for a successful submission or a negative submission report for a failed submission. If the submis- sion report is not received after a given period of time, then the originator SME concludes that the message submission has failed. 3.9.1 TPDU Layout A the transfer layer, the TPDU of type SMS-SUBMIT has the layout shown in Figure 3.13. In this chapter, a specific graphical convention is used for the representation of TPDU layouts. Mandatory parameters are represented by grey-shaded boxes and optional parameters are represented by white boxes. Mobile Messaging Technologies and Services56 Figure 3.12 Message submission 3.9.2 TPDU Parameters The TPDU of type SMS-SUBMIT contain s the parameters listed in Table 3.7. The SMS standard defines thr ee representations for numeric values and alphanumeric values assigned to TPDU parameters. These representations (integer representation, octet representation and semi-octet representation) are defined in Appendix B. 3.9.3 Rejection of Duplicates It sometimes happens that a submission report gets lost. In this case, the originator SME has no means to determine if the message, for which the submission report has been lost, has been successfully submitted to the serving SMSC or not. If the originator SME re-transmits the Short Message Service 57 Figure 3.13 TPDU layout/type SMS-SUBMIT Mobile Messaging Technologies and Services58 Table 3.7 Message submission/TPDU parameters a Abbreviation Reference P R Description TP-MTI TP-Message-Type-Indicator X 2 bits Message type (bits 0 and 1 of first octet) Bit 1 Bit 0 Message type 0 0 SMS-DELIVER 0 0 SMS-DELIVER-REP 1 0 SMS-STATUS-REP 1 0 SMS-COMMAND 0 1 SMS-SUBMIT 0 1 SMS-SUBMIT-REP TP-RD TP-Reject-Duplicates X 1 bit Indication of whether the SMSC shall accept or reject duplicated message segments. A message segment is a duplicate of an original message segment if it has the same TP-MR, TP-DA and TP-OA. TP-VPF TP-Validity-Period-Format X 2 bits Presence and format of the TP-VP field (bits 3 and 4 of first octet). Bit 4 Bit 3 0 0 TP-VP not present. 0 1 TP-VP – enhanced format 1 0 TP-VP – relative format 1 1 TP-VP – absolute format Short Message Service 59 TP-RP TP-Reply-Path X 1 bit Reply path (bit 7 of first octet). bit 7 at 0: reply-path is not set. bit 7 at 1: reply-path is set. TP-UDHI TP-User-Data-Header- Indicator W 1 bit Presence of a user data header in the user data part (bit 6 of first octet). bit 6 at 0: no user data header. bit 6 at 1: a user data header is present TP-SRR TP-Status-Report-Request W 1 bit Request for a status report. bit 5 at 0: no status report requested. bit 5 at 1: a status report is requested. TP-MR TP-Message-Reference X 1 octet Integer rep. Message segment reference number in the range 0…255 (decimal values) TP-DA TP-Destination-Address X 2–12 octets The destination address identifies the originating SME. The address format is defined in Section 3.9.6 TP-PID TP-Protocol-Identifier X 1 octet Protocol identifier as defined in Section 3.7.7 TP-DCS TP-Data-Coding-Scheme X 1 octet Data coding scheme as defined in Section 3.7 TP-VP TP-Validity-Period W 1 octet or 7 octets Validity period identifies the time from when the message is no longer valid TP-UDL TP-User-Data-Length X 1 octet Integer rep. The user data length is expressed in septets (GSM 7-bit default alphabet) or octets (UCS2 or 8-bit encoding) TP-UD TP-User-Data W TP-DCS dependent The user data and user data header are defined in Section 3.15 a In the table field names, P stands for Provision and R for Representation. In the table body, X stands for Mandatory whereas W stands for Optional. message, while the first submission attempt was successful, the message will be transmitted twice to the message recipient. To avoi d this situation, the originator SME has the ability to inform the SMSC that a previous submission was attempted for the message being submitted. In this case, if the SMSC detects that the previous submission had been successful, then the message is automatically discarded and not transmitted to the recipient SME. This ensures that the recipient SME receives the message only once. Two parameters are associated with this ability to reject duplicates. The first parameter is the TP-Reject-Duplicates. This Boolean flag is set to 1 (true) for the new submission attempt and set to 0 (false) otherwise. The second parameter is the TP-Message- Reference which allows the SMSC to identify that the message, for which the TP- Reject-Duplicates is set , has already been successfully submitted. 3.9.4 Validity Period The validity period of a message indicates the time after which the message content is no longer valid. The value assigned to the TP-Validity-Period parameter can take three different forms (as indicated by the field TP-Validity-Period -Format): † Relative format (1 octet, integer representation). The value assigned to the TP- Validity-Period parame ter in a relative format defines the length of the validity period starting from the time the mes sage was received by the serving SMSC. The repre- sentation of the value assigned to the TP-Validity-Period parameter is as follows: Mobile Messaging Technologies and Services60 Figure 3.14 TP-Validity-Period in the enhanced format TP-Validity-Period Validity period value 0–143(TP-Validity-Period)×5minutes 144–167(12hours+ (TP-Validity-Period2143)×30minutes) 168–196(TP-Validity-Period2166)×1day 197–255(TP-Validity-Period2192)×1week † Absolute format (7 octets, semi-octet representation). The value assigned to the TP- Validity-Period parameter, in an absolute format, defines the date when the validity period terminates. The 7-octet value is an absolute time representation as defined in Section 3.9.5. † Enhanced format (7 octets). The first octet of the 7-octet TP-Validity-Period, in the enhanced format, indicates how the following 6 octets are used. The presence of all octets is mandatory even if they are not all used. The first octet is structured as shown in Figure 3.14. Note that the value assigned to the TP-Validity-Period parameter is always expressed with either 1 octet or 7 octets, depending on its format. Any reserved or unused bit is set to 0. 3.9.5 Absolute Time Representation Values assigned to several TPDU parameters represent an absolute time definition. This is the case for the TP-Validity-Period, TP-Service-Centre-Time-Stamp and the TP-Discharge-Time. For these parameters, the absolute time representation is decom- posed into a sequence of time-related parameters, as described in Figure 3.15, which shows theabsolutetime23rdDecember01,9:53:42AM,GMT+ 1hour.Notethatthetimezoneis expressed in quarters of an hour. 3.9.6 Destination Address The value assigned to the TP-Destination-Address parameter represents the address of the recipient SME. This value is formatted as shown in the following section. 3.9.7 SME Addressing Values assigned to the following parame ters represent SME addresses: † TP-Destination-Address † TP-Recipient-Address † TP-Originating-Address. An SME address is decomposed into four sub-parameters: † Address length (represents the number of useful semi-octets in the address value sub- parameter, the maximum length is 20 semi-octets) † Type of number † Numbering plan identification † Address value. Short Message Service 61 The values assigned to the three addressing parameters are formatted as shown in Figure 3.16. The values listed in Table 3.8 can be assigned to the type-of-number sub-parameter. The values listed in Table 3.9 can be assigned to the numbering-plan-identification sub-parameter. At the transfer layer, SMS does not offer the group sending feature which consists of submitting one message addressed to several recipients by submitting one message only to the SMSC. Howeve r, this feature is sometimes emulated at the application layer at the cost of submitting one message to the SMSC for each recipient. 3.10 Message Submission Report After the submission of a mes sage segment from an originator SME to the serving SMSC, the SMSC acknowledges the submission by sending a report back to the originator SME. This report indicates the status of the submission. A positive submission report is sent back if the Mobile Messaging Technologies and Services62 Figure 3.15 Absolute time definition Short Message Service 63 Figure 3.16 SMS addressing Table 3.8 SMS addressing/type of number Bit 6 Bit 5 Bit 4 Description 0 0 0 Unknown (address sub-parameters are organized according to the network dialling plan) 0 0 1 International number 0 1 0 National number 0 1 1 Network specific number (administration/service number specific to the serving network) 1 0 0 Subscriber number 1 0 1 Alphanumeric (coded in GSM 7-bit default alphabet) 1 1 0 Abbreviated number 1 1 1 Reserved Table 3.9 SMS addressing/numbering plan identification a Bit 3 Bit 2 Bit 1 Bit 0 Description 0 0 0 0 Unknown 0 0 0 1 ISDN/telephone numbering plan 0 0 1 1 Data numbering plan (X.121) 0 1 0 0 Telex numbering plan 0 1 0 1 SMSC specific plan (external SMEs attached to the service centre) 0 1 1 0 SMSC specific plan (external SMEs attached to the service centre) 1 0 0 0 National numbering plan 1 0 0 1 Private numbering plan 1 0 1 0 ERMES numbering plan a All other values that can be assigned to this sub-parameter are reserved. submission was successful, otherwise a negative submission report is generat ed (Figure 3.17). Note that, with existing network configurations, submission reports are not always used. Instead, the acknowledgement of a message submission is often limited to a lower layer confirmation (relay layer). If provided, the submission report is conveyed in the form of a TPDU of type SMS-SUBMIT-REPORT at the transfer layer. 3.10.1 Positive Submission Report The positive submission report can contain several of the following parameters: † Message type (SMS-SUBMIT -REPORT) † Parameter indicator (presence of protocol identifier, data coding scheme and user data length) † Protocol identifier † Data coding scheme † Service centre time stamp (time at which the SMSC received the associa ted message) † User data header † User data (with associated length). Upon receipt of the submission report, the originator SME may indicate to the subscriber whether or not the submission was successful. If the submission was not successful, then the originator may request the subscriber to modify the message in order to re-attempt the message submission. After message submission, if the originator SME does not receive a submission report from the serving SMSC, then the SME can conclude that either: † The message submission has failed, or † The submission report has been lost. In this situation, the originator SME may attempt another message submission. For this purpose, the originator SME can indicate for the new message submission that the message had already been submitted previously. This notice allows the serving SMSC to discard the newly submitted message if the first submission attempt was successful. The rejection o f duplicate messages is described in Section 3.9.3. The positive submission report TPDU has layout shown in Figure 3.18. The positive submission report TPDU can contain several of the parameters listed in Table 3.10. Mobile Messaging Technologies and Services64 Figure 3.17 Submission report 3.10.2 Negative Submission Report Upon reception of a message segment, the serving SMSC may not be able to rout e forward the message (message badly formatted, SMSC busy, etc.). In this situation, the SMSC sends a negative submission report back to the originator SME. At the transfer layer, a negative submission report is transported as a TPDU of type SMS-SUBMIT-REPORT. This TPDU can contain several of the following parameters: † Message type (SMS-SUBMIT-REPORT) † Parameter indicator (presence of protocol identifier, data coding scheme and user data length) † Protocol identifier † Failure cause Short Message Service 65 Figure 3.18 Positive submission report/layout [...]... N/A N/A N/A N/A SMS EMS 1 EMS 1 EMS 1 EMS 1 EMS 1 EMS 1 EMS 1 EMS 1 EMS 1 EMS 1 EMS 2 EMS 2 EMS 2 EMS 1 EMS 2 EMS 2 EMS 2 N/A SMS SMS SMS N/A SMS N/A N/A N/A N/A No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No N/A No Yes No N/A No N/A N/A N/A N/A Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No N/A Yes Yes Yes N/A No N/A N/A N/A N/A 3. 15.8 4 .3 and 5.20 4.5.1... for future EMS features RFC 822 Email header Hyperlink format element Reply address element Reserved for future use (U)SIM toolkit security header SME to SME specific use Reserved for future use SMSC specific use Reserved for future use 99 SMS No Yes 3. 15.2 99 N/A 99 SMS N/A SMS Yes N/A No Yes N/A Yes 3. 15 .3 – 3. 15.4 99 SMS No Yes 3. 15.4 99 99 SMS SMS No Yes Yes Yes 3. 15.5 3. 15.6 99 SMS No Yes 3. 15.2 99... available Error in SME Values specific to each SMSC Unused status index values are reserved Short Message Service 81 Figure 3. 27 Status report/layout 82 Mobile Messaging Technologies and Services 3. 13. 1 TPDU Layout The layout of the status report TPDU is shown in Figure 3. 27 3. 13. 2 TPDU Parameters The status report TPDU contains the parameters listed in Table 3. 18 3. 13. 3 Discharge Time If the associated message... type (bits 0 and 1 of first octet) Bit 1 Bit 0 Message type Description In the table field names, P stands for Provision and R for Representation In the table body, X stands for Mandatory whereas W stands for Optional TP-Message-Type-Indicator TP-MTI a Reference Abbreviation Table 3. 20 SMS command/TPDU parameters a 86 Mobile Messaging Technologies and Services Short Message Service 87 Figure 3. 30 TP-User-Data... element was introduced b This table field indicates whether the information element is related to SMS control (SMS) , basic EMS (EMS 1) or extended EMS (EMS 2) c iMelody format with a maximum size of 128 octets Mobile Messaging Technologies and Services 90 Figure 3. 32 How to read the IE description table 3. 15.2 Concatenation of Message Segments The concatenation information element indicates that a message... in Section 3. 10 .3 Service centre time stamp represents the time the SMSC received the message The structure of the SMSC time stamp is defined in Section 3. 10 .3 Protocol identifier as defined in Section 3. 7.7 Bit 1 Message type (bits 0 and 1 of first octet) Description In the table field names, P stands for Provision and R for Representation In the table body, X stands for Mandatory whereas W stands for Optional... defined in Section 3. 9.7 Service centre time stamp represents the time the SMSC received the message The structure of the SMSC time stamp is defined below See description in Section 3. 13. 3 0 SMS- DELIVER 0 0 SMS- DELIVER-REP 0 0 SMS- STATUS-REP 1 0 SMS- COMMAND 1 1 SMS- SUBMIT 0 1 SMS- SUBMIT-REP 0 Presence of more messages to send at the SMSC (bit 2 of first octet) Bit 2 at 0: more messages are waiting Bit 2... parameter: Figure 3. 22 Message delivery/layout Reference TP-Message-Type-Indicator TP-More-Messages-to-Send TP-Reply-Path TP-User-Data-Header-Indicator TP-MTI TP -MMS TP-RP TP-UDHI Message delivery/TPDU parameters a Abbreviation Table 3. 13 R 2 bits 1 bit 1 bit 1 bit P X X X W 0 0 SMS- DELIVER 0 0 SMS- DELIVER-REP 0 0 SMS- DELIVER-REP 0 1 SMS- STATUS-REP 0 1 SMS- COMMAND 1 0 SMS- SUBMIT 1 0 SMS- SUBMIT-REP Presence... Abbreviation Table 3. 16 78 Mobile Messaging Technologies and Services Short Message Service 79 Figure 3. 26 Status report 3. 13 Status Report Upon delivery of a message segment to a recipient SME, the serving SMSC may generate a status report and transfer it back to the originator SME The status report is sent only if the originator SME requested it during the message submission The serving SMSC generates... The user data and user data header are defined in Section 3. 15 Data coding scheme as defined in Section 3. 7 0 0 SMS- DELIVER 0 0 SMS- DELIVER-REP 0 1 SMS- STATUS-REP 0 1 SMS- COMMAND 1 0 SMS- SUBMIT 1 0 SMS- SUBMIT-REP Presence of a user data header in the user data part (bit 6 of first octet) Bit 6 at 0: no user data header Bit 6 at 1: a user data header is present Presence of TP-PID, TP-DCS and TP-UDL fields . report is sent back if the Mobile Messaging Technologies and Services6 2 Figure 3. 15 Absolute time definition Short Message Service 63 Figure 3. 16 SMS addressing Table 3. 8 SMS addressing/type of number Bit. the serving SMSC or not. If the originator SME re-transmits the Short Message Service 57 Figure 3. 13 TPDU layout/type SMS- SUBMIT Mobile Messaging Technologies and Services5 8 Table 3. 7 Message. (bits 0 and 1 of first octet) Bit 1 Bit 0 Message type 0 0 SMS- DELIVER 0 0 SMS- DELIVER-REP 0 0 SMS- DELIVER-REP 1 0 SMS- STATUS-REP 1 0 SMS- COMMAND 0 1 SMS- SUBMIT 0 1 SMS- SUBMIT-REP TP -MMS TP-More-Messages-to-Send X