| WAP Gateway optional? |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
Hi, Can we directly connect to the MMSC without the need of a WAP gateway if we do not have to browse the internet. Instead I use WSP to connect to MMSC. I suppose a WAP gateway is used for content transfer from the internet to mobile devices. Sorry if it is an irrelevant question | |||
| Bryce Norwood - NowSMS Support |
It depends on your environment. Almost all mobile phones on the market today include a WAP gateway setting in their MMS configuration options. The phone talks WSP to this WAP gateway IP address, and uses it as a proxy for talking to the MMSC. Some MMSCs might be able to accept WSP connections (there's no reason that an MMSC could not be developed that included a WSP handler), but I would expect most to only accept HTTP connections and leave WSP to a WAP gateway. -bn | |||
| vsr |
Dear Anonymous  Could you tell what "WSP" you use? Is it some API, library, etc.? | |||
| Anonymous |
Hi vsr, WSP - the Wireless Session Protocol. I actually read the MMS specs and read about the client transactions. I have a few more questions. - where does the WAP gateway, if present reside. Should it be at the service provider or within one's company. - I also read at forum.nokia.com that an MMS Client should encode and decode the messages. what then, in this scenario is the role of a gateway? - Is a WAP browser mandatory for viewing MMS messages or would a smil player suffice? - Are WSP- POST/Get messages sent only thro' a browser or can the MMS Client initiate wap connections to the gateway? I'm a bit confused with the tonnes of information i get on the internet, each site and tools have their own interpretation. Perhaps i have not understood them . | |||
| vsr |
WAP gateway resides on service provider's side. Generally, it's role is to accept your WSP request and translate it to HTTP request to server. I case of MMS, "server" is MMS server. In case of WAP browser the gateway processes WSP GETs and POSTs and translates them to HTTP requests to web servers providing WML content. The MMS client initiates direct wap connections to the gateway with no need for WAP browser. | |||
| Kent Williams |
where does the WAP gateway, if present reside. Should it be at the service provider or within one's company It depends on your requirements, and how much control you need over the overall environment. The gateway can be anywhere that allows IP connectivity between the mobile devices and the gateway. I also read at forum.nokia.com that an MMS Client should encode and decode the messages. what then, in this scenario is the role of a gateway? The MMS client logically is encoding/decoding an MMS message and using HTTP GET and POST transactions to interact with an MMSC (as well as receiving notifications via WAP push, which is usually occurring over SMS). However, the HTTP GET and POST are transacted through a WAP gateway. So while the MMS client is logically performing HTTP GET and POST transactions, it must use a WAP client stack to implement WSP GET and POST instead (at least this is a requirement on most operator networks). Is a WAP browser mandatory for viewing MMS messages or would a smil player suffice? Most MMS clients are completely separate from the WAP browser, and not integrated. The only integration that exists, if any, is that MMS notification messages that are sent to the client are encapsulated inside of a WAP push message. Therefore, the MMS client either needs to receive WAP push messages directly, or it needs a hook into a WAP push receiver in the device that dispatches the MMS notifications to the MMS client. This area is a bit messy for MMS client developers. Are WSP- POST/Get messages sent only thro' a browser or can the MMS Client initiate wap connections to the gateway? Generally the MMS client is going to do this itself. If a WAP browser is present that exposes an API, then you may want to use this, but otherwise, the MMS client would do it independent of the WAP browser. - Kent Williams Now Wireless Support | |||
| argh |
Hi everybody, could any body tell me about the code to make a WSP GET or POST request ? | |||
| argh |
Hi everybody, could any body tell me about the code to make a WSP GET or POST request ? | |||
| Bryce Norwood - NowSMS Support |
Well, it depends on how indepth you want to get ... But, basically, the WSP (Wireless Session Protocol) is implemented on top of the WTP (Wireless Transport Protocol), which is implemented on top of the WDP (Wireless Datagram Protocol). These are all WAP (Wireless Application Protocol) specifications, published by the Open Mobile Alliance (www.openmobilealliance.org). In a TCP/IP environment, WDP is implemented on top of UDP. WTP manages transaction retry logic, as well as segmentation and re-assembly for transactions to occur over WDP. (For example, a large response to a GET or POST, or a large POST request might be segmented into multiple WDP packets by the WTP layer.) WSP manages session logic. A device issues a WSP connect, and then it can issue WSP GET or POST requests over the session. WSP requests are sent as WTP transactions over the WTP layer which maps them to WDP, which ultimately results in UDP packets in the TCP/IP environment. Aside from the specifications themselves, if you really want to get into this area, you'll want to use a good traffic analyser like Ethereal, and sit it between an existing WAP client and WAP gateway. Or maybe a web search will reveal a company that will license a library to handle this for you. (This is less likely if you are working on an embedded platform, of course.) -bn | |||
