| WAP PUSH PO-TCP Port |  Search
|
|
NowSMS Support Forums ⬆ WAP Technical Discussions (unsupported) ⬆ Archive through March 07, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Comete |
Hi.. Please help me to get the answer of the PO-TCP port question. I want to know which port should be used in a terminal WAP Push client. For PO-TCP, the PPG will build PO-TCP to different vender's terminal. So, all push terminal should have the same IP port to make the whole Push system working. But which port the terminal should listen for PO-TCP request from PPG. Thanks!/Comete | |||
| Kent Williams |
Hi Comete, That is a good question. I am a bit unclear on this matter, but I believe it is 4035 (or 4036 for TLS). That is what I have written in my notes. But searching for a reference to back me up on that leaves me a little unsure of where I got that information in the first place. The IANA registration information seems to back this up: http://www.iana.org/assignments/port-numbers But I can't find the port number referenced in the WAP specs anywhere. If you look at the IANA assignments, I'd put my money on 4035/4036 being correct. The traditional WAP push ports (2948/2949) are registered for both UDP and TCP ... and it seems odd they are registered for TCP as well as UDP, but I don't think they would be used for PO-TCP. As PO-TCP is HTTP based, the description of ports 4035/4036 seems to match PO-TCP. - Kent Williams Now Wireless Support | |||
| Comete |
Hi Williams, thank you very much for your helping and instruct about the Push technical issue. It is truth that the WAP Spec from WAP forum don;t provide clear and whole WAP detail technique. I am design a real Push Client and solution for a China Operator.we plan to support TO-TCP and PO-TCP. I wonder do ur WAP PPG product support the SIR? If PO-TCP take the 4035 port, and which port do u think the TO-TCP should take ? it should be 2948 or 4035? and I found there are a named "simple-push" port in the IANA list, could you pl explain to me what is the simple push? thank you very much!! Comete | |||
| Kent Williams |
Hi Comete, At present, we're not doing any SIR (session initiation request), PO-TCP or TO-TCP support. We strictly use WSP for push, although we would like to implement support for these additional protocols (it is difficult to develop them without a client, as it is difficult for you to develop the client without a gateway). One of the challenges for push going forward is how a PPG can know what type of push to initiate for a device. It is no problem if the device has connected to the gateway/proxy using it as a WSP or HTTP proxy, because then the gateway knows the device capabilities. But what if a PPG needs to send a push to a device on another network? (I think push will be too limited if it can only be initiated from the network on which a device is subscribed.) Of course, SIR over SMS is the solution, because an SIR request can specify settings for both OTA-WSP and OTA-HTTP. But I have doubts that today's terminals can actually handle SIR for OTA-WSP. So how does a PPG know whether to send an SIR request vs. a simple WSP push over SMS? This is a difficult question for us. The transition to OTA-HTTP may be difficult for this reason. Back to your question. I think TO-TCP should use the same ports, by default (4035). It is, after all, basically the same protocol. But I expect it will be an implementation decision on each network. A client should have configuration for both address and port if it will be using TO-TCP. I am concerned that TO-TCP is not practical for a PPG implementation, however. I have not studied TO-TCP very much, as I have assumed PO-TCP and SIR would be the primary solutions. I cannot imagine the TCP/IP overhead that would exist on a network if TO-TCP were deployed, or how a PPG could cope with millions of devices connecting in this fashion. TO-TCP simply does not seem practical. The "simple-push" port in the IANA list appears to be for something else other than WAP. It was registered by somebody at j2medeveloper.com, but that does not appear to be an official standards body site. - Kent Williams Now Wireless Support | |||
| Anonymous |
sfbsfab  | |||
| Anonymous |
Hi All, The TO-TCP should use the port given in the contact points in the SIR. If that is not available it should use the default IANA registered ports as described by Kent Williams. Another point to note is the fact that PPG will initiate the push OTA process for TO-TCP. Hence TO-TCP will probably be used only after receiving an SIR that has OTA-HTTP contact points. Hope it is useful. | |||
| Shiv Jatan Kumar Unregistered guest |
Hi Please help me how to create a SIR Format for TO-TCP Method, its not clear in the PUSH OTA Protocol. should it be send in PDU Format. | |||
| Anonymous |
deleted by admin 303 | |||
