Mobile messaging technologies and services sms ems and mms phần 9 doc

two distinct MMS environment s is provided in Section 6.33.5. The following sections present transaction flows for message forward, delivery repor t forward and read-reply report forward. 6.33.2 Routing Forward a Message The request for forwarding a message (MM4_forward.REQ request) over the MM4 inter- face allows a multimedia message to be transferred between two MMS environments. If requested by the originator MMSC, the recipient MMSC acknowledges the forward request with a forward response (MM4_forward.RES response). The transaction flow for the transfer of a message over the MM4 interface is shown in Figure 6.49. The MM4_forward.REQ request is composed of the information elements/parameters listed in Table 6.40. If requested by the originator MMSC, the recipient MMSC acknowl- edges the forward request with a forwar d response (MM4_forward.RES resp onse). The response is composed of the information elements/parameters listed in Table 6.41. Unlike forward requests, the addressing of forward responses is related to neither the message originator nor the message recipient. Instead, the addressing of a forward response is related to special system addresses. The value to be assigned to the To parameter is the value assigned to the X-MMS-Originator-System parameter of the corresponding forward request (usually a special system address identifying the originator MMSC). The value to be assigned to the Sender parameter is a special address identifying the recipient MMSC. It is suggested that special system addresses should be formatted in the form: system-user@mms-r elay-host.operatorX.net If the forward request has been processed without error by the recipient MMSC, the following value is assigned to the request status code information element (X-Mms- Request-Status-Code parame ter). † Ok: this status code indicates that the corresponding request has been processed without errors. If errors occurred during the processing of the forward request, the codes listed in Table 6.42 can be assigned to the request status code information element. 6.33.3 Routing Forward a Delivery Report The request for forwarding a delivery report (MM4_delivery_report.REQ request) over the MM4 interface allows the transfer of a delivery report between two MMS environ- ments. If requested by the recipient MMSC, the origina tor MMSC acknowledges the forward request with a forward response (MM4_delivery_report.RES response). The transac- tion flow for the transfer of a delivery report over the MM4 interface is shown in Figure 6.50. The MM4_delivery_report.REQ request is composed of the information elements/ parameters listed in Table 6.43. The MM4_delivery_report.RES response is composed of the information elements/parameters listed in Table 6.44. For the forward response, the value to be assigned to the To parameter is the value assigned to the Sender parameter of the corresponding forward request. The value to be assigned to the Sender parameter is the system address of the recipient MMSC. Mobile Messaging Technologies and Services296 Multimedia Messaging Service 297 Table 6.40 MM4 message forward request Stage 2 IE Description 3GPP status Stage 3 STD11 Header Rel-4 Rel-5 3GPP MMS version MMS version of the MMSC XXX-Mms-3GPP-MMS-Version Type: string Example: 5.2.0 Message type Type of MM4 operation (request for the forward of a message) XXX-Mms-Message-Type Type: string Value: MM4_forward.REQ Transaction identification Identification of the forward transaction XXX-Mms-Transaction-ID Type: string Message identification Identification of the multimedia message being forwarded XXX-Mms-Message-ID Type: string Recipient address Address(es) of the recipient(s) of the original message XXTo, Cc Types: string Sender address Address of the sender of the original message XXFrom Type: string Message subject Message subject a CCSubject Type: string Message class Class of the message a CCX-Mss-Message-Class Type: string Values: Personal Advertisement Informational Auto Message date and time Date and time the original message was handled (retrieved, expired, rejected, etc.) XXDate Type: date Time of expiry Time of expiry of the message a CCX-Mms-Expiry Type: date or duration Mobile Messaging Technologies and Services298 Table 6.40 (continued ) Stage 2 IE Description 3GPP status Stage 3 STD11 Header Rel-4 Rel-5 Delivery report Whether or not a delivery report is requested a CCX-Mms-Delivery-Report Values: Yes No Read-reply report Whether or not a read-reply report is requested a CCX-Mms-Read-Reply Values: Yes No Priority Priority of the message being forwarded a CCX-Mms-Priority Values: Low Normal High Sender visibility Whether or not the sender requested sender C C X-Mms-Sender-Visibility details to be hidden from recipients a Values: Hide Show Forward counter Counter indicating how many times the message C C X-Mms-Forward-Counter has been forwarded a Type: integer Previously sent by Address(es) of MMS user agents that have handled (submitted or forwarded) the message prior to the manipulation by the MMS user agent whose address is assigned to the sender information element WWX-Mms-Previously-Sent- By Type: string with index e.g.: 1, armel@armorepro.com 2, gwenael@le-bodic.net Previously sent date and time Date and time when the message was handled WWX-Mms-Previously-Sent- Date-and-Time Multimedia Messaging Service 299 Type: date with index e.g.: 1, Mon Jan 21 09:45:33 2002 2, Wed Jan 23 18:06:21 2002 Request for an acknowledgement Whether or not an acknowledgement for the forward request is requested WWX-Mms-Ack-Request Values: Yes No No corresponding information element Originator address as determined by the SMTP MAIL FROM command XXSender Type: string No corresponding System address to which the requested forward C C X-Mms-Originator-System information element response should be sent b Type: string No corresponding information element Each SMTP request/response has a unique reference assigned to the Message-ID parameter XXMessage-ID Type: string Content-type Message content type XXContent-Type Type: string Content Message content a C C Message body a Condition: available only if specified by the originator MMS user agent. b Condition: required if a forward response is requested. Mobile Messaging Technologies and Services300 Table 6.41 MM4 message forward response Stage 2 IE Description 3GPP status Stage 3 STD11 Header Rel-4 Rel-5 3GPP MMS version MMS version of the MMSC XXX-Mms-3GPP-MMS-Version Type: string Example: 5.2.0 Message type Type of MM4 operation (response for the forward of a message) XXX-Mms-Message-Type Value: MM4_forward.RES Transaction identification Identification of the forward transaction XXX-Mms-Transaction-ID Type: string Multimedia message identification Identification of the multimedia message being forwarded XXX-Mms-Message-ID Type: string Request status code Status code of the request to forward the message XXX-Mms-Request-Status- Code Values: Ok Error codes in Table 6.42 Status text Optional status text WWX-Mms-Status-Text Type: string No corresponding information element System address XXSender Type: string Address of the recipient MMSC No corresponding information element System address XXTo Type: string Address of the originator MMSC No corresponding information element Each SMTP request/response has a unique reference assigned to the Message-ID parameter XXMessage-ID Type: string No corresponding information element Date provided by the recipient MMSC XXDate Type: date 6.33.4 Routing Forward a Read-reply Report The request for forwarding a read-reply report (MM4_read_reply_report.REQ request) over the MM4 interface allows a read-reply report to be transferred between two distinct MMS environments. If requested by the recipient MMSC, the originator MMSC acknowledges the forward request with a forward response (MM4_read_reply_report. RES response). The transaction flow for the transfer of a read-reply report over the MM4 interface is shown in Figure 6.51. The MM4_read_reply_report.REQ request is composed of the information elements/parameters listed in Table 6.45. The MM4_read_ reply_report.RES response is composed of the information elements/parameters listed in Table 6.46. For the response, the value to be assigned to the To parameter is the v alue assigned to the Multimedia Messaging Service 301 Table 6.42 MM4 message forward response/error codes Status code Description Error-unspecified An unspecified error occurred during the processing of the request Error-service-denied The request was rejected due to a failure during service authentication or authorization Error-message-format- corrupt The content of the request is badly formatted Error-sending-address- unresolved The recipient MMS environment was unable to resolve one of the recipient addresses (values assigned to From, To and Cc parameters) Error-network-problem The recipient MMSC was unable to process the request due to capacity overload Error-content-not- accepted The request was not accepted because of issues with the associated message size or format, or because of copyright issues Error-unsupported-message The recipient MMSC does not support the request type Error-message-not-found This status code is now obsolete Figure 6.50 MM4 delivery report Mobile Messaging Technologies and Services302 Table 6.43 MM4 delivery report forward request Stage 2 IE Description 3GPP status Stage 3 STD11 Header Rel-4 Rel-5 3GPP MMS version MMS version of the MMSC XX X-Mms-3GPP-MMS-Version Type: string Example: 5.2.0 Message type Type of MM4 operation (request for the forward of a delivery report) XX X-Mms-Message-Type Value: MM4_delivery_report.REQ Transaction identification Identification of the forward transaction XX X-Mms-Transaction-ID Type: string Multimedia message identification Identification of the multimedia message to which the delivery report corresponds XX X-Mms-Message-ID Type: string Recipient address Address of the recipient of the original message XX From Type: string Sender address Address of the sender of the original message XX To Type: string Message date and time Date and time the original message was handled (retrieved, expired, rejected, etc.) XX Date Type: date Request for an acknowledgement Whether or not an acknowledgement of the forward request is requested WW X-Mms-Ack-Request Values: Multimedia Messaging Service 303 Yes No Message status code Status of the corresponding multimedia message XX X-Mms-MM-Status-Code Type: string Values: Expired Retrieved Rejected Deferred Indeterminate Forwarded Unrecognised Message status text Text corresponding to the status code WW X-MM-Status-Text Type: string No corresponding System address XX Sender information element Address to which the requested response should be sent Type: string No corresponding information element Each SMTP request/response has a unique reference assigned to the Message-ID parameter XX Message-ID Type: string Mobile Messaging Technologies and Services304 Table 6.44 MM4 delivery report forward response Stage 2 IE Description 3GPP status Stage 3 STD11 Header Rel-4 Rel-5 3GPP MMS version MMS version of the MMSC XXX-Mms-3GPP-MMS-Version Type: string Example: 5.2.0 Message type Type of MM4 operation (response for the forward of a delivery report) XXX-Mms-Message-Type Type: string Values: MM4_delivery_report.RES Transaction identification Identification of the forward transaction XXX-Mms-Transaction-ID Type: string Multimedia message identification Identification of the multimedia message being forwarded XXX-Mms-Message-ID Type: string Request status code Status code of the request to forward the message XXX-Mms-Request-Status- Code Values: Ok Error codes defined in Tables 6.42 Status text Address of the sender of the original message WWX-Mms-Status-Text Type: string No corresponding information element System address. Address of the recipient MMSC XXSender Type: string No corresponding information element System address. Address of the originator MMSC XXTo Type: string No corresponding information element Each SMTP request/response has a unique reference assigned to the Message-ID parameter XXMessage-ID Type: string No corresponding information element Date provided by the recipient MMSC XXDate Type: string Sender parameter of the corresponding forwar d request. The value to be assigned to the Sender parameter is the system address of the recipient MMSC. 6.33.5 Example for Message Transfer with SMTP Figure 6.52 shows the sequence of SMTP instructions required to open an SMTP session, transferring a message and tearing down the session. Note that values assigned to From, To and Cc fields are not used for routing purpose over SMTP. These values are transferred transparently over SMTP. Consequently, these values may be formatted as RFC 822 addresses or as MSISDN addresses. Values, used for routing purpose in SMTP, are those assigned to MAIL and RCPT fields. 6.33.6 Availability Matrix of PDU Parameters Table 6.47 indicates the set of parameters composing each request/response for operations that can be invoked over the MM4 interface (3GPP releases 4 and 5). 6.34 MM5 Interface MMSC–HLR The MM5 interface enables interactions between an MMSC and other network entities such as the HLR. Operations that can be invoked over the MM5 interface include: † Interrogating the HLR to obtain routing information for the purpose of forwarding a message from one MMSC to another one over the MM4 interface. † Determination of the recipient handset’s location (e.g. if the subscriber is roaming). † etc. If the MM5 interface is present in the MMSE, then it is usually implemented on the basis of existing MAP operations. At the time of writing, no technical realization of the MM5 inter- face has been specified by standardization organizations. Multimedia Messaging Service 305 Figure 6.51 MM4 read-reply report [...]... Sender Subject To X -MMS- 3GPP-Version X -MMS- Ack-Request X -MMS- Delivery-Report X -MMS- Expiry X -MMS- Forward-Counter X -MMS- Message-Class X -MMS- Message-ID X -MMS- Message-Type X -MMS- MM-Status-Code X -MMS- Originator-System X -MMS- Previously-Sent-By X -MMS- Previously-Sent-Dateand-Time X -MMS- Priority X -MMS- Read-Reply X -MMS- Read-Status X -MMS- Request-Status-Code X -MMS- Sender-Visibility X -MMS- Status-Text X -MMS- Transaction-ID... during 2003 6. 39 Pros and Cons of MMS MMS represents a huge evolutionary step from EMS in the messaging roadmap In comparison with SMS and EMS, MMS has the following advantages: † Multimedia messages can contain a wide range of content formats such as colour images/ animations, video, etc Additionally, messages can be organized as compact multimedia slideshows † Compared with other messaging technologies, ... Example: 5.2.0 X -Mms- Message-Type Type: string Value: M4_read_reply_report.RES X -Mms- Transaction-ID Type: string X -Mms- Request-Status-Code Values Ok Error codes in Table 6.42 X -Mms- Status-Text Type: string Sender Type: string To Type: string Message-ID Type: string Date Type: string Stage 3 STD11 Header 308 Mobile Messaging Technologies and Services Multimedia Messaging Service Figure 6.52 3 09 Example of... context of value added services, message submission refers to the submission of a message from an originator VAS application to an MMSC The message is addressed to a single recipient, to multiple recipients or to a distribution list managed by the MMSC If the Mobile Messaging Technologies and Services 314 Figure 6.56 MM7 message submission MMSC accepts the submission request, then the MMSC sends back a... Rel-4 X X X X X X 3GPP status From Type: string To Type: string Value: M4_read_reply_report.REQ X -Mms- Transaction-ID Type: string X -Mms- Message-ID Type: string Type: string Example: 5.2.0 X -Mms- Message-Type Type: string X -Mms- 3GPP -MMS- Version Stage 3 STD11 Header 306 Mobile Messaging Technologies and Services No corresponding information element No corresponding information element Each SMTP request/... is retained for the new message The transaction flow in Figure 6.61 shows Mobile Messaging Technologies and Services 318 Figure 6.57 Example of message submission request over the MM7 interface Multimedia Messaging Service Figure 6.58 3 19 Example of message submission response over the MM7 interface interactions between the MMSC and the VAS application for the replacement of a previously submitted multimedia... the Nokia MMSC is based on a set of Nokia proprietary commands conveyed over HTTP Multimedia Messaging Service 331 † MMS Java library: the Java library can be used for developing MMS- based applications in Java This library includes the following features: – message creation and encoding – message decoding – message sending to Nokia MMSC or to Nokia emulator MMSC † Developer’s suite for MMS: this is... communicating over the MM7 interface Mobile Messaging Technologies and Services 312 The support of the MM7 interface is optional for the MMSC However, if such an interface is supported, then message submission, message delivery, operations related to the provision of delivery reports and the management of errors are mandatory operations to be supported by the MMSC The support of other operations such... X -MMS- Sender-Visibility X -MMS- Status-Text X -MMS- Transaction-ID Table 6.47 310 Mobile Messaging Technologies and Services Multimedia Messaging Service 311 Table 6.48 Operations over the MM7 interface Operation Description 3GPP status Rel-5 Message submission Submission of a message from a VAS application to the MMSC Delivery of a message from an MMSC to a VAS application Cancel the delivery of a previously submitted... between MMS and the Email service has been significantly improved † MMS is well integrated with innovative devices /services such as camera accessories, remote photo albums † MMS is a future-proof technology and will be the subject of many evolutions in the near future Several of these evolutions are introduced in the next section On the other hand, the following drawbacks have been identified for MMS: . Sender parameter is the system address of the recipient MMSC. Mobile Messaging Technologies and Services2 96 Multimedia Messaging Service 297 Table 6.40 MM4 message forward request Stage 2 IE Description 3GPP. gwenael@le-bodic.net Previously sent date and time Date and time when the message was handled WWX -Mms- Previously-Sent- Date -and- Time Multimedia Messaging Service 299 Type: date with index e.g.: 1, Mon Jan 21 09: 45:33 2002 2,. parameters a MM4_Forward. REQ MM4_Forward. RES MM4_Delivery_ Report.REQ MM4_Delivery_ Report.RES MM4_Read_Reply_ Report.REQ MM4_Read_Reply_ Report.RES Cc W Content C Content-type X Date XXXXX X From XX X Message-ID XXXXX X Sender XXXXX X Subject C To WXXXX X X -MMS- 3GPP-Version XXXXX X X -MMS- Ack-Request WW W X -MMS- Delivery-Report C X -MMS- Expiry C X -MMS- Forward-Counter C X -MMS- Message-Class C X -MMS- Message-ID XXXXX X -MMS- Message-Type XXXXX X X -MMS- MM-Status-Code X X -MMS- Originator-System X X -MMS- Previously-Sent-By W X -MMS- Previously-Sent-Date- and- Time W X -MMS- Priority C X -MMS- Read-Reply C X -MMS- Read-Status X X -MMS- Request-Status-Code XX X X -MMS- Sender-Visibility C X -MMS- Status-Text WWWW W X -MMS- Transaction-ID XXXXX X a X,