Messaging Proxy System

• US 20090178063A1
• Filed: 02/17/2009
• Published: 07/09/2009
• Est. Priority Date: 07/07/2000
• Status: Active Grant

• Current Assignee: Taiwan Semiconductor Manufacturing Company Limited
• Original Assignee: Softwired AG
• Inventors: Maffeis, Silvano
• Granted Patent: US 8,650,244 B2
• Time in Patent Office: Days
• US Class Current: 719/328
• 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 of providing an Application Programming Interface (API) for a wireless client accessing a computer of a wired network via a computer network server, the method comprising the steps of

selecting a first set of functionality of a programming library used by a message oriented middleware and implementing at least a client API to serve as a thin programming library and configuring and installing the thin programming library to operate on the wireless client;

selecting a second set of functionality of a message oriented middleware to serve as a message proxy, the message proxy being more complete than the thin programming library, and

configuring and installing the message proxy to operate on a computer network server remote from the wireless client;

configuring a command subsystem allowing the thin programming library to remote-control, via a wireless network, the message proxy operating on the computer network server; and

employing command tokens to communicate between the thin programming library operating on the wireless client and the message proxy operating on the computer network server to enable the wireless client to appear as though it has greater message oriented middleware functionality than provided by the thin programming library alone.

2. The method of claim 1 further comprising the step of providing data storage functionality to the thin programming library and the message proxy to ensure that messages are not lost due to temporary interruption of the communication between the thin programming library and the message proxy.

3. The method of claim 2 further comprising providing the data storage functionality by means of a pluggable database adapter that allows the client or the message proxy to use any of a plurality of database products.

4. The method of claim 1 further comprising implementing the client according to the JMS (Java Message Service) specification.

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

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

and

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