Messaging Proxy System

• US 20090157836A1
• Filed: 02/17/2009
• Published: 06/18/2009
• Est. Priority Date: 07/07/2000
• Status: Abandoned Application

• Current Assignee: Taiwan Semiconductor Manufacturing Company Limited
• Original Assignee: Softwired AG
• Inventors: Maffeis, Silvano
• Application Number:
  US12/371,924
• Publication Number:
  US 20090157836A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• 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/2876 Pairs of inter-processing entities at each side of the network, e.g. split proxies
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• 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 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/169 Special adaptations of TCP, UDP or IP for interworking of IP based networks with other networks protocols for interworking, protocol conversion H04L69/08
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: H04W 88/02 Terminal devices
• CPC Class Codes: H04W 88/182 Network node acting on behalf of an other network entity, e.g. proxy

Abstract

A messaging proxy system is disclosed for the purpose of delivering data in the form of a portable message format from a producer running on a mobile or non-mobile computer, over any wireless network, by passing this data through an intermediary proxy computer program, to one or more recipients running on mobile or non-mobile computers. The system includes a message proxy computer program with at least one pluggable transport protocol adapter. The proxy contains a command subsystem for sending and receiving command- and message-tokens to and from the mobile clients. The system further includes a thin messaging middleware client to run on mobile devices. The thin messaging middleware client includes at least one pluggable protocol adapter. The client also comprises a command subsystem for sending and receiving command- and message-tokens to and from the proxy. The proxy also contains a communication subsystem for sending and receiving messages via a state of the art message oriented middleware.

Claims

1. A method for delivering data between an application serving as client and running on a mobile wireless device and a message oriented middleware application running on a computer of a wired network,

comprising the steps of

implementing, on the mobile wireless device, a messaging system Application Programming Interface (API);

running a message proxy on a computer connected to the wired network, the proxy maintaining client subscriptions to topics and queues, and receiving and forwarding messages;

and at least one of the following two steps of

the client calling a command provided by the messaging system API;

the proxy receiving a message on behalf of the client;

and further comprising the step of

the proxy acting towards the message oriented middleware on behalf of the client as if the client was accessing the message oriented middleware directly.

2. The method of claim 1, wherein a thin message client is installed on the mobile wireless device

and implements the API of the messaging system,

comprising the steps of

the client calling a command provided by the thin message client API;

a command subsystem of the thin message client creating a code information representing the command;

sending the code information to the message proxy using wireless communication;

simultaneously or subsequently, transmitting message data to the message proxy;

the message proxy maintaining message system state information associated with the client;

creating, by the message proxy, at least one MOM command referred to by the code information; and

the message proxy forwarding the message data to the message oriented middleware application, using said at least one MOM command.

3. The method of claim 1, wherein a thin message client is installed on the mobile wireless device

and implements the API of the messaging system,

comprising the steps of

the proxy receiving a message on behalf of the client;

the proxy creating a code information representing the message;

the proxy sending the code information to the thin message client using wireless communication;

the thin message client creating, from the code information, a message; and

the client processing the message.

4. The method of claim 1, comprising the step of

at least one of the clients and the proxy storing messages in a local database, such that they will not be lost when a client is disconnected from the proxy.

5. The method of claim 1, comprising the steps of

the message proxy starting, at runtime, a pluggable transport protocol adapter enabling communication over a given transport protocol;

the message proxy sending and receiving messages to and from message clients by means of the transport protocol adapter, using wireless protocols.

6. The method of claim 5, wherein said at least one transport protocol adapter supports HTTP or SMS or WAP or WDP or GPRS or UMTS.

7. The method of claim 2, wherein the command provided by the thin message client API and represented by code information or tokens is one of “

subscribe”

, “

unsubscribe”

, “

create topic”

, “

publish”

.

8. The method of claim 1, wherein the API client library is a JMS (Java Messaging System) library.

9. A system for delivering data between an application serving as client and running on a mobile wireless device and a message oriented middleware application running on a computer of a wired network,

comprising

a messaging system Application Programming Interface (API) implemented on the mobile wireless device;

a message proxy implemented on a computer connected to the wired network, the proxy being configured to maintain client subscriptions to topics and queues, and to receive and forward messages;

the proxy being configured to act towards the message oriented middleware on behalf of the client as if the client was accessing the message oriented middleware directly;

in at least one of the cases of

the client calling a command provided by the messaging system API;

the proxy receiving a message on behalf of the client.

10. The system of claim 9, wherein the message proxy comprises a wireless transport protocol adapter implemented before start-up of the message proxy and a wireless transport protocol adapter implemented by a program code at run-time of the message proxy.