How MMS is encapsulated (2)

I,
MMS

Encapsulation (
Encapsulation

)--
Mime

For smil
Language description MMS
When sending via wireless networks, we must put SMIL in some way
Together with the affiliated content, one side can use a Unit
(Overall) Form for smil
Reference of each part of the file
Become valid.

This
The solution is mime.
(Multipart Internet Mail Extensions
) Specification, the initial role of this specification is in email
Of
Plain text
Add different content to the subject. For example, send an email with an attachment
At this time, you use MIME
. Mime
All independent texts,
Images, sounds, video content, and smil
The file itself is bundled together. This specification is called mime encapsulation aggregate documents.
, Use
Tell the Receiving Terminal This MMS
Is related to each other (related to one another
) And mutual reference
(Referenced to one another
).

 

1. Mime

Encapsulation example

The following is based on RFC
Mime provided in the document
Encapsulation example:

Content-Type: multipart/related; boundary = "Boundary-Example "; <br/> type = "text/html" <br/> -- boundary-example <br/> Content-Type: text/html; charset = "US-ASCII" <br/> ...... ...... <br/> ...... ...... <br/> -- boundary-example <br/> Content-Type: image/GIF <br/> content-ID: <97116092511xyz@foo.bar.net> <br/> content-location: fiction1/fiction2 <br/> -- boundary-example <br/> Content-Type: image/GIF <br/> content-ID: <97116092811xyz@foo.bar.net> <br/> content-location: fiction1/fiction3 <br/> -- boundary-example --

• Content-Type
  

Content-Type in the Information Header
The content of different parts of the terminal message used for notification reception is correlated and may be indexed (refer to one another
).

• Boundary
  

Boundary
Used to separate different message parts
. The first part is an html
Type message. Here, only the relevant part is obtained. The second and third sections omit the actual images
The entity of the image.

• 
  Location and ID
  

In HTML
We can see that we can use two methods to index different parts of the message content. The two different methods are content-id.
And content-location
.

If you want to use the content-ID
Point to (refer
) The other part of the message body can use "CID ".

About mime
For more information, see the RFC in the appendix.
Documentation (rfc2387
And rfc2357
).

 

2.

Exploitation
Mime

Encapsulation
MMS

Example

The following is an example of using mime
Encapsulate MMS
Example:

Content-Type: multipart/related; <br/> type = "application/smil"; Start = "<AAAA> "; boundary = "---- = _ blank" <br/> ------ = _ part_24362_271418.1110357304160 <br/> Content-Type: text/X-vcalendar; charset = UTF-8; name = "slide1.vcs" <br/> content-ID: <slide1.vcs> <br/> content-location: slide1.vcs <br/> content-transfer-encoding: base64 <br/> encoding + encoding <br/> tkq6vknbtevorefsdqo = <br/> ------ = _ part_24362_271418.1110357304160 <br/> Content-Type: application/SMIL; charset = UTF-8; name = "20050309163706. SMIL "<br/> content-ID: <AAAA> <br/> content-transfer-encoding: base64 <br/> phntaww + pghlywq + signature <br/> signature + <br/> ------ = _ part_24362_271418.1110357304160 --

The illustration shows the relationship between each part:

3.

A complete
Mime

Encapsulation
MMS

Example

The following table provides a complete mime
Encapsulate MMS
Example:

Mime object <br/> date: Fri, 14 Dec 2001 15:13:21-0500 (EST) <br/> X-MMS-expiry: Thu, 20 Dec 2001 21:52:25-0500 (EST) <br/> X-MMS-delivery-time: Wed, 19 Dec 2001 21:52:25-0800 (PST) <br/> X-MMS-priority: normal <br/> X-MMS-sender-visibility: show <br/> X-MMS-message-class: Personal <br/> X-MMS-delivery-Report: yes <br/> X-Mms-3GPP-MM3-Version: 4.3.0 <br/> from: mms-email-sample@sample-email.ericsson.com <br/> to: + 12345@mmc.sample-mms.ericsson.com <br/> subject: Sample SMIL <br/> mime-version: 1.0 <br/> Content-Type: multipart/related; boundary = "---- <br/> = _ mime_boundary_mms_reference_sample_001" <br/> MIME headers </P> <p> "---- = _ blank" <br/> mime start boundary </ p> <p> content-ID: <index. SMIL> <br/> Content-Type: Application/SMIL; charset = "US-ASCII"; name = index. SMIL <br/> <SMIL> <br/> <pead> <br/> <layout> <root-layout/> <br/> <Region ID = "region1_2" Top = "0" Left = "0" Height = "100%" width = "100%"/> <br/> <Region ID = "region1_1" Top = "0" Left =" 0 "Height =" 100% "width =" 100% "/> <br/> </layout> <br/> </pead> <br/> <body> <br/> <par dur = "2000 ms"> <br/> <text src = "CID: image "mce_src =" CID: image "region =" region1_2 "/> <br/> </PAR> <br/> <par dur =" 2000 ms "> <br/> <br/> </PAR> <br/> </body> <br/> </SMIL> <br /> SMIL document </P> <p> "---- = _ mime_boundary_mms_reference_sample_001" <br/> mime boundary </P> <p> Content-Type: text/plain; name1_mms.txt <br/> content-transfer-encoding: 7bit <br/> content-ID: <TXT> <br/> content-Disposition: attachment; filename=mms.txt <br/> This is a sample MMS Message, for use as a reference. <br/> text document </P> <p> "---- = _ mime_boundary_mms_reference_sample_001" <br/> mime boundary <br/> Content-Type: image/GIF; name‑sample.gif <br/> content-transfer-encoding: base64 <br/> content-ID: <image> <br/> content-Disposition: attachment; filename=sample.gif <br/> images/videos/2iq1j <br/> m66yeq4cxm/6ys <br/> <entire encoded image not shown for the sake of brevity> <br/> images = <br/> image </P> <p> "---- = _ mime_boundary_mms_reference_sample_001" <br/> mime boundary <br/>

 

Ii. MMS
Mime
Structure

In summary, each MMS
Information according to mime
Shows the basic structure of the specification:

As shown in the figure below, each MMS
Both by MMS Header
And MMS body
Component, MMS Header
According to WAP-209
Protocol and rfc2387
Is composed of a series of domains. The following table lists some of the domains (Representation of the demo content), some of which are mandatory (
In bold)
.

X-MMS-message-type <br/> M-send-req </P> <p> X-MMS-transaction-id <br/> 1234 </P> <p> X-MMS-version <br/> 1.0 <br/> date <br/> Friday, march 20 06:43:40 GMT <br/> from <br/> MMS-Editor @ toolkit <br/> to <br/> 33333333333333 </P> <p> CC <br/> 33333333333333 </P> <p> BCC </P> <p> subject <br/> test </P> <p> X-MMS-message-class <br/> personal </P> <p> X-MMS-expiry <br/> Saturday, 19 August 05 06:43:40 GMT <br/> X-MMS-delivery-time <br/> Friday, march 20 06:43:40 GMT </P> <p> X-MMS-priority <br/> low </P> <p> X-MMS-sender-visibility <br/> show </P> <p> X-MMS-delivery-Report <br/> NO </P> <p> X-MMS-read-reply <br/> NO </P> <p> Content-Type <br/> application/vnd. WAP. multipart. related; Start = "<presentation-part>" type = "application/smil"