• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Carrier support for PushRegistry & inbound connections

 
Daniel Tamez
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,
Background: I am looking at porting our existing WAP application to J2ME. One of the must have features is the ability to push messages to the J2ME application in a timely manner and that can interact with the midlet. Obviously the PushRegistry seems the best way to implement this. We need to be able to support as many different devices as possible (and requiring a MIDP 2.0 phone cuts it down alot to start with) and as many carriers as possible.

My question: assuming we can convince the end users (contracted partners) to purchase MIDP 2.0 capable phones which carriers actually allow us to initiate communication from an enterprise application on the internet to a mobile device and if so what stipulations do they require for such communication (pay for public IP per device per month, limited to SMS...)

Any real world experience (pro or con) with carriers - support for inbound connections or even OTA deployment for that matter would be much appreciated.

Danny
 
William Frantz
Ranch Hand
Posts: 102
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I can give you lots of information about Sprint but I don't even know what country you are in. What carriers are you interested in?

You can (sort-of) launch Java applications on Sprint phones, even pre-MIDP 2.0 thanks to Sprint's custom extensions. For an example, see the following:

http://sprintdevelopers.com/postp353.html

William Frantz
http://sprintdevelopers.com
 
Daniel Tamez
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Wow - that is really dissapointing and seems like a big work around for something that should be supported by MIDP 2.0 phones.

Our company is worldwide but this app will be primarily in the US then Canada and Mexico next.

Carriers we were interested in were mainly: Sprint, Nextel, ATT/Cingular, T-Mobile.

Anyone else have experience with any of these carriers (OTA support and PushRegistry support)?

Thanks,

Danny
 
Yuri Magrisso
Ranch Hand
Posts: 58
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Daniel,

If you need to send messages to the phone in a limited time frame, say when the user is chatting in his chat application, you should consider MIDlet initiated TCP/IP connections.
You can keep the connection alive during the time you need to send messages back to the MIDlet. This will make your application independent of providers, because you don't need public IP.
The socket connection is obligatory in MIDP 2, but a lot of Motorola MIDP 1 phones support it too.

Hope it helps,
Yuri
 
Daniel Tamez
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Unfortunately the main business reasons for the communication will be initiated by the enterprise side of the application rather than the remote side. But that's still good information and I appreciate the help.

Anyone else care to share experiences with different carriers and OTA deployment or PushRegistry support?

Thanks in advance,

Danny
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic