10. Appendix B - Example MM7 creation Appendix C Message size definition Appendix D Acronyms and definitions...

Size: px

Start display at page:

Download "10. Appendix B - Example MM7 creation Appendix C Message size definition Appendix D Acronyms and definitions..."

Marjory Curtis
6 years ago
Views:

1 9.10 My SMIL messages are garbled after the first section when they arrive on the handset. What should I do? Can I send messages overseas? Are Delivery reports supported Are alpha senders allowed? How is message size determined Are binary data encoding methods other than BASE64 supported? Is the message size on the handset an accurate measure of the MMS Access Manager message size? Appendix B - Example MM7 creation Step1 constructing valid MM Step 2: Insert your SMIL Step 3: Adding content End the MM7 with closing SMIL boundary Putting it all together Appendix C Message size definition Appendix D Acronyms and definitions...41 References [1] 3GPP TS V6.8.0 MMS Functional description stage 2 [2] IETF; RFC 2616: HTTP/1.1 (URL: Telstra MMS Access Manager Technical Guide updated October 2009 Page 3 of 42

8 Linked ID Not Supported Not used in the Telstra network Date and Time Optional Time stamp of submission Message Subject Optional Message content Optional AuxApplicInfo Optional Identifies the subscriber s handset user agent. Priority Optional MMS Relay/Server ID Optional Identifies the MMSC that generated the message MM7_deliver.RES This transaction is sent by the customer server in response to a MM7_deliver.REQ Item Type Description Transaction ID Mandatory Unique identifier used to correlate the MM7_deliver.REQ with the MM7_ deliver.res Message Type Mandatory MM7_ deliver.res MM7 version Mandatory The interface version that is supported Request Status Mandatory Status of the request Request Status Text Optional Textual description of the request status Service Code Optional Not used by Telstra MM7_cancel.REQ Not supported by Telstra. MM7_cancel.RES Not supported by Telstra. MM7_replace.REQ Not supported by Telstra. MM7_replace.RES Not supported by Telstra. Telstra MMS Access Manager Technical Guide updated October 2009 Page 14 of 42

16 </To> <Number>Phone number</number> </Recipients> <MessageClass>Informational</MessageClass> <DeliveryReport>false</DeliveryReport> <ReadReply>false</ReadReply> <Priority>Normal</Priority> <Subject>text</Subject> <Content href="cid:mms-79" allowadaptations="true" /> </SubmitReq> </env:body> </env:envelope> --boundary-mm7-soap Content-Type: multipart/related; start="<mms.smil>"; type="application/smil"; boundary="boundary-mm7-mime " Content-ID: <mms-79> --boundary-mm7-mime Content-Type: application/smil; charset="us-ascii"; name="mms.smil" Content-ID: <mms.smil> <smil xmlns=" </smil> <head> </head> <body> </body> <meta name="title" content="text" /> <meta name="author" content="whoever" /> <layout type="text/smil-basic-layout"> </layout> <par dur="10s"> </par> <root-layout /> <region id="textregion" height="99%" width="99%" top="1%" left="1%" fit="scroll" /> <text src="text.txt" region="textregion" begin="0s" end="10s" /> --boundary-mm7-mime Content-Type: text/plain; name="text.txt" Content-Location: text.txt Content-ID: <text.txt> Content-Transfer-Encoding: base64 dgv4dcbvbmx5icxqzmxmampmbgtkamzsa3nqzge= --boundary-mm7-mime boundary-mm7-soap Telstra MMS Access Manager Technical Guide updated October 2009 Page 24 of 42

29 --NextPart_ Content-Type: multipart/related;type="application/smil";start="<smil.txt>"; boundary="----=_part_160_ " <mime content here> =_Part_160_ NextPart_ MM7_deliver.RES The following PDU is an example of the required response to a MM7_deliver.REQ. HTTP/ OK Content-Type: text/plain Connection: close Content-Length: 667 <?xml version='1.0'?> <env:envelope xmlns:env=" <env:header> <mm7:transactionid xmlns:mm7=" 4" env:mustunderstand="1"> vas00001-sub </mm7:transactionid> </env:header> <env:body> <DeliverRsp xmlns=" MM7-1-4"> <MM7Version>6.8.0</MM7Version> <Status> <StatusCode>1000</StatusCode> <StatusText>Success</StatusText> <Details>Transactional</Details> </Status> </DeliverRsp> </env:body> </env:envelope> Telstra MMS Access Manager Technical Guide updated October 2009 Page 29 of 42

30 7.5 MM7_delivery_report example Following are examples of MM7_delivery_report.REQ and MM7_delivery_report.RES PDUs. These are the PDUs sent to the VAS if a delivery report has been requested for a message and if the VAS has sent to a Telstra subscriber from a non-alpha source. MM7_delivery_report.REQ The following PDU is an example of what will be sent to a VAS. POST / HTTP/1.0 Host: Connection: close Content-type: text/xml Content-Length: 940 <?xml version='1.0'?> <env:envelope xmlns:env=" <env:header> <mm7:transactionid xmlns:mm7=" 4" env:mustunderstand="1">832309d</mm7:transactionid> </env:header> <env:body> <DeliveryReportReq xmlns=" <MM7Version>6.8.0</MM7Version><MMSRelayServerID>TARAL</MMSRelayServerID> <MessageID>T*4*T\*4\* </MessageID> <Recipient> <RFC2822Address>+614BBBBBBBB/TYPE=PLMN@mm7.mms.telstra.com</RFC2822Ad dress> </Recipient> <Sender> <RFC2822Address>+614AAAAAAAA/TYPE=PLMN@mm7.mms.telstra.com</RFC2822Ad dress> </Sender> <Date> T12:20:36+11:00</Date> <MMStatus>Retrieved</MMStatus> <StatusText>The message was retrieved by the recipient</statustext> </DeliveryReportReq> </env:body> </env:envelope> Telstra MMS Access Manager Technical Guide updated October 2009 Page 30 of 42

31 MM7_delivery_report.RES The following PDU is an example of the required response to a MM7_delivery_report.RES. HTTP/ OK Connection: close Date: Tue, 30 Oct :20:36 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Type: text/html <?xml version='1.0'?> <env:envelope xmlns:env=" <env:header> <mm7:transactionid xmlns:mm7=" 4" env:mustunderstand="1">832309d</mm7:transactionid> </env:header> <env:body> <DeliveryReportRsp xmlns=" 4"><MM7Version>6.8.0</MM7Version> <Status><StatusCode>1000</StatusCode> <StatusText>Message OK</StatusText> </Status> </DeliveryReportRsp> </env:body> </env:envelope> ( oad100.html) 8. Toolkits 8.1 MM7 Telstra does not provide support for any 3rd party MM7 toolkits however the following vendors may provide toolkits on request: Airwide Solutions ( Comverse ( 8.2 SMIL Player/composer Ambulant produce a freeware SMIL player that allows you to play SMIL presentations: LimSee2 is a freeware SMIL Authoring tool for creating SMIL ( x.php?goto=home) 8.3 Base64 Encoder. There are many base64 encoders/decoders available via the internet for a simple command line version for testing try: to encode: base64.exe e sourcefile to decode: base64.exe e sourcefile destfile destfile Telstra MMS Access Manager Technical Guide updated October 2009 Page 31 of 42

32 9. Appendix A Frequently asked questions 9.1 What type of devices can MMS Access Manager send to? MMS Access Manager can deliver to any MMS capable device. This includes MMS capable standard GSM/3G devices. It is also dependent on the handset being correctly configured as well as having GPRS/1x access. 9.2 Where do messages go if the subscriber is not MMS capable? If the subscriber is a Telstra customer and has a non-mms capable phone, they will be informed via SMS that a MMS has been sent to them which can be viewed via the web (this is referred to as the legacy experience). For non-telstra subscribers the behaviour in this case is dependent on the individual carrier and is not controlled by Telstra. 9.3 Will Telstra alter the content of messages submitted? Part of the functionality of an MMSC is to vary content if required to suit the end device; this will include dropping content if the device is not capable (e.g. drop video for a non-video capable handset), reducing the size or quality of content to suit the end device, or changing the coding format (e.g. converting a GIF to a JPG). 9.4 Does Telstra support DRM? If messages are submitted with DRM, Telstra will not alter this and deliver it to the end device. For non-telstra subscribers the behaviour in this case is dependent on the individual carrier and is not controlled by Telstra. 9.5 What should I do if the message is being rejected with invalid address? Ensure the MSISDN being used is in correct international format. Ensure you have been authorised to use the Sender Address in the submission. This includes alphas. 9.6 What should I do if the destination handset is not receiving the message? Ensure that the destination is MMS capable and the device is turned on also confirm that the customer is not barred from either MMS or GPRS. Send the customer a message via a handset and see that they get it. Try sending your MM7 transaction to another subscriber with a different model of handset and see if the problem continues. 9.7 What version of MM7 should I be using? Version or version For messages sent from Telstra and for Delivery Reports version will be used. Telstra MMS Access Manager Technical Guide updated October 2009 Page 32 of 42

33 9.8 What should I do if I m having problems with the Target URL? Unless you are using a secured network layer (VPN) the correct access method is HTTPS. Ensure that you are posting your MM7 to on port 443. For customers using HTTP over a secured network layer the URL is on port Can messages be delivered to/from imode subscribers? Yes, messages can be delivered to, and from, imode subscribers. imode recipients, however, do not support alpha senders or delivery reports My SMIL messages are garbled after the first section when they arrive on the handset. What should I do? Make sure you have the correct MM7 boundary (i.e. make sure it is consistent throughout the entire MM7 packet) Can I send messages overseas? MMS Access Manager can be used to send messages to a limited set of countries. For specific country details please visit ts/messaging/internationalmms.htm However, if you are using an alpha sender to send messages, you will not be able to send messages internationally Are Delivery reports supported Delivery reports are supported when sending messages to Telstra subscribers from a MSISDN source address. They are not supported when sending messages from non-msisdn (e.g. alpha) sources. N.B. additional charges will be incurred whenever a Delivery Report is requested whether or not the Delivery Report is ever submitted to the VASP Are alpha senders allowed? Alpha senders are only supported when sending messages to Telstra destinations. They are not supported when sending messages to other carriers. When sending from an alpha sender it is not possible for the recipient to respond to the message and Delivery Reports are not supported. An alpha sender must: only contain a combination of upper and lower case letters and digits start with a letter be between 1 and 10 characters in length 9.14 How is message size determined? Message size is determined as per the definition in 11. Appendix C Message size definition Are binary data encoding methods other than BASE64 supported? No. When submitting to MMS Access Manager all binary data must be encoded using BASE Is the message size on the handset an Telstra MMS Access Manager Technical Guide updated October 2009 Page 33 of 42

34 accurate measure of the MMS Access Manager message size? No. For MMS Access Manager message size is defined as per Appendix C Message Size Definition. This is calculated differently from the way handsets calculate message size and will generally be 30-40% larger than the handset size (though the actual difference will depend on the specific message). Telstra MMS Access Manager Technical Guide updated October 2009 Page 34 of 42

35 10. Appendix B - Example MM7 creation The following is a step by step procedure to create and send an MM7 transaction in its rawest format. In order to create and send MM7 you will need several key components VASP ID [Provided by Telstra] VAS ID [Provided by Telstra] Source Address [Provided by Telstra] Destination address Content Once you have all of these things use the following step by step procedure to create a sample MMS Message Step1 Constructing valid MM7. The following is a template for creating your own MM7 transaction. Note that the from Sender and Recipient addresses should be a mobile number in 614XXYYYZZZ format. This is the start of your MM7 transaction. Content-Type: multipart/related; type="text/xml"; start="mms-mm7-79"; boundary="boundary-mm7-soap " SOAPAction: "" --boundary-mm7-soap Content-Type: text/xml; charset="us-ascii" Content-ID: <mms-mm7-79> <?xml version="1.0"?> <env:envelope xmlns:env=" xmlns:xsd=" xmlns:xsi=" <env:header> <mm7:transactionid xmlns:mm7=" env:mustunderstand="1" xsi:type="xsd:string"> </mm7:transactionid> </env:header> <env:body> <SubmitReq xmlns=" <MM7Version>5.3.0</MM7Version> <SenderIdentification> <VASPID>InsertYourVASPID</VASPID> <VASID>InsertYourVASID</VASID> <SenderAddress> Telstra MMS Access Manager Technical Guide updated October 2009 Page 35 of 42

36 </SenderAddress> </SenderIdentification> <Recipients> <To> </To> InsertYourFromAddress <Number>InsertYourDestinationAddress</Number> </Recipients> <MessageClass>Informational</MessageClass> <DeliveryReport>false</DeliveryReport> <ReadReply>false</ReadReply> <Priority>Normal</Priority> <Subject>text</Subject> <Content href="cid:mms-79" allowadaptations="true" /> </SubmitReq> </env:body> </env:envelope> --boundary-mm7-soap Content-Type: multipart/related; start="<mms.smil>"; type="application/smil"; boundary="boundary-mm7-mime " Content-ID: <mms-79> 10.2 Step 2: Insert your SMIL Depending on your type of content, your SMIL will vary. You can also use a SMIL editor to create this component. For this example we will presume your content consists of 5 slides - slide 1 is Text [show for 1 seconds] - slide 2 is an image [show for 2 seconds] - slide 3 is audio [show for 3 seconds] - slide 4 is another image [show for 2 seconds] - slide 5 is more text [show for 1 seconds] The following SMIL will create the template for this. --boundary-mm7-mime Content-Type: application/smil; charset="us-ascii"; name="mms.smil" Content-ID: <mms.smil> <smil xmlns=" <head> </head> <body> <meta name="title" content="text" /> <meta name="author" content="whoever" /> <layout type="text/smil-basic-layout"> <root-layout /> </layout> <par dur="1s"> </par> <region id="imageregion" height="100%" width="100%" top="0%" left="0%" fit="meet" /> <region id="textregion" height="99%" width="99%" top="1%" left="1%" fit="scroll" /> <text src="page1_text.txt" region="textregion" begin="0s" end="3s" /> Telstra MMS Access Manager Technical Guide updated October 2009 Page 36 of 42

37 </smil> </body> <par dur="2s"> </par> <par dur="3s"> </par> <par dur="2s"> </par> <par dur="1s"> </par> <text src="page2_image.jpg" region="imageregion" begin="0s" end="3s" /> <text src="page3_audio.wav" region="imageregion" begin="0s" end="3s" /> <text src="page4_image.jpg" region="imageregion" begin="0s" end="3s" /> <text src="page4_text.txt" region="textregion" begin="0s" end="3s" /> 10.3 Step 3: Adding content Now that we have the template we need to add the base64 encoded content. Using a base64 encoder (like the one referenced in section 0) we will convert our 4 content types into base64. Base64 e Page1.txt Page1_Base64.txt Base64 e homer.jpg Page2_Base64.jpg Base64 e audio.wav Page3_Base64.wav Base64 e bart.jpg Page4_Base64.jpg Base64 e Page5.txt Page5_Base64.txt We start with 5 files (Page1.txt, Homer.jpg, bart.jpg, audio.wav and page5.txt) and end up with 5 separate files all base64 encoded. Now open all these files and paste their contents into the MM7 transaction: --boundary-mm7-mime Content-Type: text/plain; name="page1_base64.txt" Content-Location: Page1_Base64.txt Content-ID: <Page1_Base64.txt> Content-Transfer-Encoding: base64 <insert contents of file Page1_Base64.txt> --boundary-mm7-mime Content-Type: image/jpg; name="page2_base64.jpg" Content-Location: Page2_Base64.jpg Content-ID: <Page2_Base64.jpg> Content-Transfer-Encoding: base64 <insert contents of file Page2_Base64.jpg> --boundary-mm7-mime Content-Type: audio/wav; name="page3_base64.wav" Content-Location: Page3_Base64.wav Content-ID: <Page3_Base64.wav> Content-Transfer-Encoding: base64 <insert contents of file Page3_Base64.wav> --boundary-mm7-mime Content-Type: image/jpg; name="page4_base64.jpg" Telstra MMS Access Manager Technical Guide updated October 2009 Page 37 of 42

38 Content-Location: Page4_Base64.jpg Content-ID: <Page4_Base64.jpg> Content-Transfer-Encoding: base64 <insert contents of file Page4_Base64.jpg> --boundary-mm7-mime Content-Type: text/plain; name="page5_base64.txt" Content-Location: Page5_Base64.txt Content-ID: <Page5_Base64.txt> Content-Transfer-Encoding: base64 <insert contents of file Page5_Base64.txt> 10.4 End the MM7 with closing SMIL boundary Now that all the attachments are in place, put in a final closing tab. --boundary-mm7-mime boundary-mm7-soap Putting it all together The final product should now look like one big chunk of MM7: Content-Type: multipart/related; type="text/xml"; start="mms-mm7-79"; boundary="boundary-mm7-soap " SOAPAction: "" --boundary-mm7-soap Content-Type: text/xml; charset="us-ascii" Content-ID: <mms-mm7-79> <?xml version="1.0"?> <env:envelope xmlns:env=" xmlns:xsd=" xmlns:xsi=" <env:header> <mm7:transactionid xmlns:mm7=" env:mustunderstand="1" xsi:type="xsd:string"> </mm7:transactionid> </env:header> <env:body> <SubmitReq xmlns=" <MM7Version>5.3.0</MM7Version> <SenderIdentification> <VASPID>InsertYourVASPID</VASPID> <VASID>InsertYourVASID</VASID> <SenderAddress> InsertYourFromAddress </SenderAddress> Telstra MMS Access Manager Technical Guide updated October 2009 Page 38 of 42

39 </SubmitReq> </env:body> </env:envelope> </SenderIdentification> <Recipients> <To> </To> </Recipients> <Number>InsertYourDestinationAddress</Number> <MessageClass>Informational</MessageClass> <DeliveryReport>false</DeliveryReport> <ReadReply>false</ReadReply> <Priority>Normal</Priority> <Subject>text</Subject> <Content href="cid:mms-79" allowadaptations="true" /> --boundary-mm7-soap Content-Type: multipart/related; start="<mms.smil>"; type="application/smil"; boundary="boundary-mm7-mime " Content-ID: <mms-79> --boundary-mm7-mime Content-Type: application/smil; charset="us-ascii"; name="mms.smil" Content-ID: <mms.smil> <smil xmlns=" <head> </smil> </head> <body> </body> <meta name="title" content="text" /> <meta name="author" content="whoever" /> <layout type="text/smil-basic-layout"> <root-layout /> </layout> <region id="imageregion" height="100%" width="100%" top="0%" left="0%" fit="meet" /> <region id="textregion" height="99%" width="99%" top="1%" left="1%" fit="scroll" /> <par dur="1s"> <text src="page1_text.txt" region="textregion" begin="0s" end="1s" /> </par> <par dur="2s"> <text src="page2_image.jpg" region="imageregion" begin="0s" end="2s" /> </par> <par dur="3s"> </par> <par dur="2s"> </par> <par dur="1s"> </par> <text src="page3_audio.mp3" region="imageregion" begin="0s" end="3s" /> <text src="page4_image.jpg" region="imageregion" begin="0s" end="2s" /> <text src="page4_text.txt" region="textregion" begin="0s" end="1s" /> --boundary-mm7-mime Content-Type: text/plain; name="page1_base64.txt" Content-Location: Page1_Base64.txt Content-ID: <Page1_Base64.txt> Content-Transfer-Encoding: base64 <insert contents of file Page1_Base64.txt> Telstra MMS Access Manager Technical Guide updated October 2009 Page 39 of 42

40 --boundary-mm7-mime Content-Type: image/jpg; name="page2_base64.jpg" Content-Location: Page2_Base64.jpg Content-ID: <Page2_Base64.jpg> Content-Transfer-Encoding: base64 <insert contents of file Page2_Base64.jpg> --boundary-mm7-mime Content-Type: audio/mp3; name="page3_base64.mp3" Content-Location: Page3_Base64.mp3 Content-ID: <Page3_Base64.mp3> Content-Transfer-Encoding: base64 <insert contents of file Page3_Base64.wav> --boundary-mm7-mime Content-Type: image/jpg; name="page4_base64.jpg" Content-Location: Page4_Base64.jpg Content-ID: <Page4_Base64.jpg> Content-Transfer-Encoding: base64 <insert contents of file Page4_Base64.jpg> --boundary-mm7-mime Content-Type: text/plain; name="page5_base64.txt" Content-Location: Page5_Base64.txt Content-ID: <Page5_Base64.txt> Content-Transfer-Encoding: base64 <insert contents of file Page5_Base64.txt> --boundary-mm7-mime boundary-mm7-soap Appendix C Message size definition For messages submitted by a VAS the message size is defined as the sum of the subject information element size and the sizes of all the multimedia element(s) and text element(s) including any presentation object (i.e. the SMIL). The size of each multimedia, text or presentation element is taken to be the size of the encoded content as it is submitted to the MMSC. This includes all MIME boundaries and headers. For multimedia elements this also includes any overhead incurred by the encoding scheme used (i.e.. BASE64). Telstra MMS Access Manager Technical Guide updated October 2009 Page 40 of 42

41 12. Appendix D Acronyms and definitions The following words, acronyms and abbreviations are referred to in this document. Item 3GPP 3GP CDMA DRM GPRS GSM HTTP HTTPS IPSEC imode Legacy MM7 MMS MMSC MSISDN PDU SOAP Description 3rd Generate Partnership Program. 3GPP formalises the MMS protocol standards. 3GPP also may refer to the 3GPP video format (see 3GP) A file format which is used to deliver audio and video formats to mobile devices. Code Division Multiple Access. This is one of Telstra s mobile networks. Digital Rights Management used to provide copyright protection for content (e.g. MMS s) General Packet Radio System this is the carriage required for delivery of MMS Messages to/from a handset via MMS in a GSM network. If a subscriber does not have GPRS setup or enabled, MMS will not work. Global System for Mobiles Hypertext transport protocol the protocol which MMS messages are transported on in the MM1 and MM7 reference points HTTP with security this is an encrypted for of HTTP that uses SSL to secure data between the client and server. Internet Protocol Security A Protocol to allow transmission of WAP type services over a packet network, the imode standard supports a type of MMS called i-mms. The Legacy experience is used in reference to customers who cannot receive an MMS (due to non capable handset, barring or incorrect activation). In this case we forward a text message to the customer with a URL and password and allow the customer to view it online. MM7 is the reference point from 3GPP spec s for customers submitting messages to a telecommunications service provider Protocol to enable transmitting video, images, text and audio messages over wireless networks. Multimedia Messaging Service Centre this is the infrastructure in the telecommunications service provider to send and receive messages to and from subscriber handsets Mobile Station International ISDN Number (i.e. a mobile number) Protocol Data Unit Simple Object Access Protocol Telstra MMS Access Manager Technical Guide updated October 2009 Page 41 of 42

42 VASP VPN WAP WSP 1xRTT Value Added Service Provider this is the name used to describe a customer submitting messages via MM7 (i.e. Access Manager Customers). Virtual Private Network. This is a secure tunnel to connect to private networks (Telstra and the Customer) over a public network (Internet). Wireless Application Protocol A standard protocol used to enable mobile devices to access the internet. Wireless Session Protocol Built atop WAP to allow session oriented connections. Single Carrier (1x) Radio Transmission Technology the CDMA equivalent of GPRS. Telstra MMS Access Manager Technical Guide updated October 2009 Page 42 of 42

3GPP2 MMS STANDARDS AND FEATURES

3GPP2 MMS STANDARDS AND FEATURES Edwin Sandberg Ericsson Multimedia Messaging and VAS 3GPP2 MMS STANDARDS AND FEATURES APRIL 2003 1 Presentation Outline Use cases for MMS MMS reference architecture MMS