Wireless internet gateway limiting message distribution
First Claim
1. A wireless Internet gateway method, comprising:
- interfacing with at least one physical application server;
providing a Java Remote Method Invocation (RMI) handler to communicate using RMI protocol with said at least one physical application server;
passing a text message to a generic protocol destination interface; and
passing said text message from said generic protocol destination interface to a destination handler;
wherein said at least one physical application server provides a communication path to a physical Internet Protocol (IP) network using a protocol supported by said at least one physical application server independent of said RMI protocol.
2 Assignments
0 Petitions
Accused Products
Abstract
A wireless Internet gateway bridges wireless devices to the Internet, e.g., via a short message service center (SMSC). The gateway provides a portal to SMPP, HTTP, TNPP, or other protocol messages using Java Remote Method Invocation (RMI) techniques. Application servers insert RMI objects containing messages in a message queue handler of the gateway. The RMI objects are queued and passed either directly to a destination delivery handler (e.g., SMPP, SMTP, HTTP or TNPP protocol handler), or passed through a generic destination interface. An SMTP handler provides direct communication of SMTP protocol messages (i.e., email) to the message queue. An SMPP link proxy module provides direct access between a local application server and the destination delivery handler. The messages are packaged into relevant messages of the particular destination protocol (e.g., SMPP), and transmitted to the relevant network element (e.g., to an SMSC).
-
Citations
8 Claims
-
1. A wireless Internet gateway method, comprising:
-
interfacing with at least one physical application server; providing a Java Remote Method Invocation (RMI) handler to communicate using RMI protocol with said at least one physical application server; passing a text message to a generic protocol destination interface; and passing said text message from said generic protocol destination interface to a destination handler; wherein said at least one physical application server provides a communication path to a physical Internet Protocol (IP) network using a protocol supported by said at least one physical application server independent of said RMI protocol. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
Specification