<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: WAP Push SMS encoding</title>
	<atom:link href="http://mobiletidings.com/2009/02/21/wap-push-over-sms-encodings/feed/" rel="self" type="application/rss+xml" />
	<link>http://mobiletidings.com/2009/02/21/wap-push-over-sms-encodings/</link>
	<description>A blog about Internet protocols, mobile technologies and things remotely related</description>
	<lastBuildDate>Sun, 13 Nov 2011 12:43:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Surya</title>
		<link>http://mobiletidings.com/2009/02/21/wap-push-over-sms-encodings/comment-page-1/#comment-3676</link>
		<dc:creator>Surya</dc:creator>
		<pubDate>Thu, 17 Feb 2011 01:41:25 +0000</pubDate>
		<guid isPermaLink="false">http://mobiletidings.com/?p=154#comment-3676</guid>
		<description>I wish to send wap push over smpp (using python http://code.google.com/p/smpplib/). I am not sure, if I need to build the message myself i.e. BRXML. Otherwise, in general, do we have to build our own BRXML no matter what generic SMPP library we use? Please suggest something.</description>
		<content:encoded><![CDATA[<p>I wish to send wap push over smpp (using python <a href="http://code.google.com/p/smpplib/" rel="nofollow">http://code.google.com/p/smpplib/</a>). I am not sure, if I need to build the message myself i.e. BRXML. Otherwise, in general, do we have to build our own BRXML no matter what generic SMPP library we use? Please suggest something.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nuno</title>
		<link>http://mobiletidings.com/2009/02/21/wap-push-over-sms-encodings/comment-page-1/#comment-1509</link>
		<dc:creator>Nuno</dc:creator>
		<pubDate>Sat, 05 Dec 2009 03:53:47 +0000</pubDate>
		<guid isPermaLink="false">http://mobiletidings.com/?p=154#comment-1509</guid>
		<description>Hello! How to wap push an URL pointing to a filename? In my nokia 5310 when i wap push just the site, it works, but when the URL points to a filename, it doesn&#039;t...am i doing something wrong?

Thanks a lot!

nuno</description>
		<content:encoded><![CDATA[<p>Hello! How to wap push an URL pointing to a filename? In my nokia 5310 when i wap push just the site, it works, but when the URL points to a filename, it doesn&#8217;t&#8230;am i doing something wrong?</p>
<p>Thanks a lot!</p>
<p>nuno</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeroen</title>
		<link>http://mobiletidings.com/2009/02/21/wap-push-over-sms-encodings/comment-page-1/#comment-1321</link>
		<dc:creator>Jeroen</dc:creator>
		<pubDate>Mon, 03 Aug 2009 17:21:23 +0000</pubDate>
		<guid isPermaLink="false">http://mobiletidings.com/?p=154#comment-1321</guid>
		<description>Franco,

No, WAP Push lets you send only one link. You can send more links in a single message as bookmarks, but that is probably not what you want.

Jeroen</description>
		<content:encoded><![CDATA[<p>Franco,</p>
<p>No, WAP Push lets you send only one link. You can send more links in a single message as bookmarks, but that is probably not what you want.</p>
<p>Jeroen</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Franco</title>
		<link>http://mobiletidings.com/2009/02/21/wap-push-over-sms-encodings/comment-page-1/#comment-1317</link>
		<dc:creator>Franco</dc:creator>
		<pubDate>Sat, 01 Aug 2009 18:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://mobiletidings.com/?p=154#comment-1317</guid>
		<description>Jeroen:
Is it possible to send two different href://..
using same wap push message?
If the answer is &#039;yes&#039; then how would one go about to be able to do it!!!.
regards
Franco</description>
		<content:encoded><![CDATA[<p>Jeroen:<br />
Is it possible to send two different href://..<br />
using same wap push message?<br />
If the answer is &#8216;yes&#8217; then how would one go about to be able to do it!!!.<br />
regards<br />
Franco</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Franco</title>
		<link>http://mobiletidings.com/2009/02/21/wap-push-over-sms-encodings/comment-page-1/#comment-1302</link>
		<dc:creator>Franco</dc:creator>
		<pubDate>Fri, 24 Jul 2009 00:00:30 +0000</pubDate>
		<guid isPermaLink="false">http://mobiletidings.com/?p=154#comment-1302</guid>
		<description>Jeroen:
I can not stop saying,
Thanks again.
Regards
Franco</description>
		<content:encoded><![CDATA[<p>Jeroen:<br />
I can not stop saying,<br />
Thanks again.<br />
Regards<br />
Franco</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeroen</title>
		<link>http://mobiletidings.com/2009/02/21/wap-push-over-sms-encodings/comment-page-1/#comment-1301</link>
		<dc:creator>Jeroen</dc:creator>
		<pubDate>Thu, 23 Jul 2009 18:13:37 +0000</pubDate>
		<guid isPermaLink="false">http://mobiletidings.com/?p=154#comment-1301</guid>
		<description>Franco,

What you have is an application of WAP push. MMS is based on (but not restricted to) SMIL documents. SMIL let&#039;s you combine your image, video and audio into one multi-media session. At some point I&#039;ll write more about MMS. 

As far as which is better... Your solution:
- Better reach (through email you can reach more devices and even PCs, not all devices support WAP push or MMS).
- Easier to build
- Cheaper (in general SMS costs are less than MMS costs and email is free)
- No mobile operator intervention

MMS:
- Supports only MMS capable devices
- Mobile operator controlled (unless you&#039;re not interested in MMS messages from your friends, you&#039;d have to use the MMSC of your operator)
- More expensive
- Harder to build (MMS messages are Mime multi-part messages that are encoded similar to WSP and WBXML)
- The user experience is probably somewhat better with MMS, after all MMS was designed just for mobile phones
- MMS messages arrive in your inbox (if configured to do so) and can be viewed offline

You decide,
Jeroen</description>
		<content:encoded><![CDATA[<p>Franco,</p>
<p>What you have is an application of WAP push. MMS is based on (but not restricted to) SMIL documents. SMIL let&#8217;s you combine your image, video and audio into one multi-media session. At some point I&#8217;ll write more about MMS. </p>
<p>As far as which is better&#8230; Your solution:<br />
- Better reach (through email you can reach more devices and even PCs, not all devices support WAP push or MMS).<br />
- Easier to build<br />
- Cheaper (in general SMS costs are less than MMS costs and email is free)<br />
- No mobile operator intervention</p>
<p>MMS:<br />
- Supports only MMS capable devices<br />
- Mobile operator controlled (unless you&#8217;re not interested in MMS messages from your friends, you&#8217;d have to use the MMSC of your operator)<br />
- More expensive<br />
- Harder to build (MMS messages are Mime multi-part messages that are encoded similar to WSP and WBXML)<br />
- The user experience is probably somewhat better with MMS, after all MMS was designed just for mobile phones<br />
- MMS messages arrive in your inbox (if configured to do so) and can be viewed offline</p>
<p>You decide,<br />
Jeroen</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Franco</title>
		<link>http://mobiletidings.com/2009/02/21/wap-push-over-sms-encodings/comment-page-1/#comment-1300</link>
		<dc:creator>Franco</dc:creator>
		<pubDate>Thu, 23 Jul 2009 16:41:01 +0000</pubDate>
		<guid isPermaLink="false">http://mobiletidings.com/?p=154#comment-1300</guid>
		<description>Jeroen:
I do the following -&gt;
1.- Have a wap site.
2.- Send a wap push either SL or SI
with a link to a xhtml page.
3.- when user receives message and via get
goes the the xhtml page which believe it or not
I use bgsound src to a 6.5KB midi file about the famous 20th century fox film theme and somehow, the midi
is effectively played(streamed) at my SonyEriccsson w200.
4.- The page shows a link to either an image(jpg), an audio file(.amr) or a video file (.3gp). When user clicks on it downloads the file and file is eventually saved successfully.
(I even send a voice mail notification with link to an audio file(.amr) and it simply works.)

My question is:
Is this wap push, is this MMS or is this better than MMS.

By the same token I do this with e-mail using e-mail notification and sendind a link to an e-mail wap site for user to retreive his or her mail.

Your thoughts are
strongly appreciated.
Regards
Franco</description>
		<content:encoded><![CDATA[<p>Jeroen:<br />
I do the following -&gt;<br />
1.- Have a wap site.<br />
2.- Send a wap push either SL or SI<br />
with a link to a xhtml page.<br />
3.- when user receives message and via get<br />
goes the the xhtml page which believe it or not<br />
I use bgsound src to a 6.5KB midi file about the famous 20th century fox film theme and somehow, the midi<br />
is effectively played(streamed) at my SonyEriccsson w200.<br />
4.- The page shows a link to either an image(jpg), an audio file(.amr) or a video file (.3gp). When user clicks on it downloads the file and file is eventually saved successfully.<br />
(I even send a voice mail notification with link to an audio file(.amr) and it simply works.)</p>
<p>My question is:<br />
Is this wap push, is this MMS or is this better than MMS.</p>
<p>By the same token I do this with e-mail using e-mail notification and sendind a link to an e-mail wap site for user to retreive his or her mail.</p>
<p>Your thoughts are<br />
strongly appreciated.<br />
Regards<br />
Franco</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeroen</title>
		<link>http://mobiletidings.com/2009/02/21/wap-push-over-sms-encodings/comment-page-1/#comment-1295</link>
		<dc:creator>Jeroen</dc:creator>
		<pubDate>Wed, 22 Jul 2009 01:18:51 +0000</pubDate>
		<guid isPermaLink="false">http://mobiletidings.com/?p=154#comment-1295</guid>
		<description>Been there, done that....

Good luck!</description>
		<content:encoded><![CDATA[<p>Been there, done that&#8230;.</p>
<p>Good luck!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sam</title>
		<link>http://mobiletidings.com/2009/02/21/wap-push-over-sms-encodings/comment-page-1/#comment-1294</link>
		<dc:creator>Sam</dc:creator>
		<pubDate>Wed, 22 Jul 2009 00:48:09 +0000</pubDate>
		<guid isPermaLink="false">http://mobiletidings.com/?p=154#comment-1294</guid>
		<description>Hi Jeroen,

Thanks - I&#039;ve just started going through the OMA-TS-MMS-ENC-V1_3-20080128-C.pdf again and now that I understand PDUs better it makes a lot more sense. Will try to form the M-Send.req etc and see if I can get something basic going. That WAP-PUSH code you have provided is a great stepping stone to understanding how the system comes together.

Cheers,
Sam</description>
		<content:encoded><![CDATA[<p>Hi Jeroen,</p>
<p>Thanks &#8211; I&#8217;ve just started going through the OMA-TS-MMS-ENC-V1_3-20080128-C.pdf again and now that I understand PDUs better it makes a lot more sense. Will try to form the M-Send.req etc and see if I can get something basic going. That WAP-PUSH code you have provided is a great stepping stone to understanding how the system comes together.</p>
<p>Cheers,<br />
Sam</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeroen</title>
		<link>http://mobiletidings.com/2009/02/21/wap-push-over-sms-encodings/comment-page-1/#comment-1293</link>
		<dc:creator>Jeroen</dc:creator>
		<pubDate>Tue, 21 Jul 2009 16:17:50 +0000</pubDate>
		<guid isPermaLink="false">http://mobiletidings.com/?p=154#comment-1293</guid>
		<description>Sam,

The MMS MM1 notification is done via a special WAP Push over SMS. I haven&#039;t written about this because of the following... MMS delivery includes 3 steps:
- The server sends a new message (MM1) notification (which usually originates from the MMSC)
- The client fetches the content of the message via GET
- The client acknowledges the successful retrieval to the MMSC
The last step is a direct interaction with an MMSC (the MMS URL that is configured on your phone). Of course you could just ignore this, but maybe the MMSC uses the acknowledgment for billing.... 

I&#039;ll probably write more about this later in the series.

Jeroen</description>
		<content:encoded><![CDATA[<p>Sam,</p>
<p>The MMS MM1 notification is done via a special WAP Push over SMS. I haven&#8217;t written about this because of the following&#8230; MMS delivery includes 3 steps:<br />
- The server sends a new message (MM1) notification (which usually originates from the MMSC)<br />
- The client fetches the content of the message via GET<br />
- The client acknowledges the successful retrieval to the MMSC<br />
The last step is a direct interaction with an MMSC (the MMS URL that is configured on your phone). Of course you could just ignore this, but maybe the MMSC uses the acknowledgment for billing&#8230;. </p>
<p>I&#8217;ll probably write more about this later in the series.</p>
<p>Jeroen</p>
]]></content:encoded>
	</item>
</channel>
</rss>

