Wireless Internet Gateway Limiting Message Distribution

• US 20160014575A1
• Filed: 09/15/2015
• Published: 01/14/2016
• Est. Priority Date: 04/25/2000
• Status: Active Grant

• Current Assignee: Artax LLC (IPValuation Partners, LLC)
• Original Assignee: TeleCommunication Systems Inc (Comtech Telecommunications Corporation)
• Inventors: Smith, Richard A.
• Granted Patent: US 9,900,754 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/105 Multiple levels of security
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04M 15/61 based on the service used
• CPC Class Codes: H04W 12/088 using filters or firewalls
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/14 Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
• CPC Class Codes: H04W 88/16 Gateway arrangements

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).

Claims

1-32. -32. (canceled)

33. A method of providing two-way text messaging with a physical wireless Internet gateway server, comprising:

passing a text message to a listener agent associated with a destination mobile device registered therewith, rather than delivered into a message queue associated with said destination mobile device; and

delivering said text message together with a return path iMessageReceiver object through which a response can be made;

wherein text messages are received from, and sent to, a wireless device external to the physical wireless internet gateway server, in a protocol independent manner.

34. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 33, further comprising:

returning a response to said text message to said return path iMessageReceiver object.

35. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 33, wherein:

said text message is delivered using at least three parameters.

36. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 35, wherein said at least three parameters include:

an identity of said return path iMessageReceiver object;

an identity of a sending mobile device; and

a body of said text message.

37. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 35, wherein said at least three parameters include:

a message priority level.

38. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 35, wherein said at least three parameters include:

a phone number of an initiating mobile device.

39. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 35, wherein said at least three parameters include:

a validity time relating to said text message.

40. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 35, wherein said at least three parameters include:

a delivery receipt request.

41. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 33, further comprising:

logging details about said text message, in a messages database.

42. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 33, further comprising:

storing said text message in a message cache.

43. A method of providing two-way text messaging with a physical wireless Internet gateway server, comprising:

injecting a text message into a Java Remote Method Invocation (RMI) object;

passing said RMI object including said text message to a listener agent associated with a destination mobile device registered therewith, rather than delivered into a message queue associated with said destination mobile device; and

delivering said RMI object including said text message, together with a return path iMessageReceiver object through which a response can be made;

wherein text messages are received from, and sent to, a wireless device external to the physical wireless internet gateway server, in a protocol independent manner.

44. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 43, further comprising:

returning a response to said text message to said return path iMessageReceiver object.

45. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 43, wherein:

said text message is delivered using at least three parameters.

46. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 45, wherein said at least three parameters include:

an identity of said return path iMessageReceiver object;

an identity of a sending mobile device; and

a body of said text message.

47. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 45, wherein said at least three parameters include:

a message priority level.

48. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 45, wherein said at least three parameters include:

a phone number of an initiating mobile device.

49. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 45, wherein said at least three parameters include:

a validity time relating to said text message.

50. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 45, wherein said at least three parameters include:

a delivery receipt request.

51. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 43, further comprising:

logging details about said text message, in a messages database.

52. The method of providing two-way text messaging with a physical wireless Internet gateway server according to claim 43, further comprising:

storing said text message in a message cache.