Wireless communication device use of application server applications

• US 20060190526A1
• Filed: 02/22/2005
• Published: 08/24/2006
• Est. Priority Date: 02/22/2005
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Nextair Corporation
• Inventors: Neil, Tim, Grenier, Steve, Neil, Scott
• Granted Patent: US 7,668,937 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability

Abstract

To enable use of an application on an application server at a mobile communication device, at a transaction server, a message received from the mobile is pushed out to the application. Any return messages is routed back to the mobile. The transaction server may use a queue to store all messages destined to a given application and attempt to push all messages on a given queue on receipt of a further message for the queue.

Claims

1. A method of enabling use of an application server application by a wireless communication device comprising, at a transaction server:

on receipt of a given message from said wireless communication device for said application on said application server, pushing said given message, and each message queued on a queue for said application, toward a destination for said application of said application server.

2. The method of claim 1 further comprising queuing said given message on said queue prior to pushing said given message, and wherein said pushing comprises, for each message on said queue,

dequeuing said each message from said queue and pushing said each message.

3. The method of claim 2 further comprising, prior to said dequeuing and pushing, acquiring a lock for said destination on said application server, said lock preventing other use of said destination.

4. The method of claim 2 further comprising, after said dequeuing said each message from said queue and pushing said each message, releasing said lock for said destination on said application server.

5. The method of claim 2 wherein messages on said queue are queued on a first in first out (FIFO) basis and wherein a trailing message in said queue is not pushed until a message in said queue immediately preceding said trailing message is considered to have successfully reached said destination.

6. The method of claim 5 further comprising:

if a particular message pushed toward said destination does not successfully reach said destination, ceasing said dequeuing and pushing and re-queuing said particular message on said queue.

7. The method of claim 6 further comprising, on dequeuing said each message and prior to pushing said each message, logging said event and wherein said re-queuing said particular message comprises utilizing said log to identify messages to re-queue.

8. The method of claim 1 further comprising:

timing a retry interval and, on expiry of said retry interval, for each message on said queue;

dequeuing said each message from said queue and pushing said each message toward said destination for said application of said application server.

9. The method of claim 1 wherein said destination is a Component Object Model (COM) interface, a Distributed Component Object Model (DCOM) interface, a Simple Object Access Protocol (SOAP) interface, a .NET interface, or a .NETRemoting interface.

10. The method of claim 3 wherein said acquiring a lock comprises sending a lock request to a remote lock server.

11. The method of claim 1 wherein said each message is an extensible markup language (XML) package.

12. The method of claim 2 further comprising:

receiving a polling request from said application server, said polling request establishing a transaction; and

dequeuing said each message from said queue and sending said each message toward said destination for said application of said application server in the context of said transaction.

13. The method of claim 1 further comprising:

receiving from said application server a message for said mobile communication device; and

forwarding said application server message to said wireless communication device.

14. The method of claim 1 wherein said pushing said each message toward said destination for said application of said application server comprising sending said each message to a universal resource locator (URL).

15. A method, at a transaction server, of enabling use of an application on an application server at a mobile communication device, comprising:

receiving from said mobile a mobile data containing package;

pushing said mobile data containing package to said application server;

receiving from said application server a server data containing package;

forwarding said server data containing package to said mobile.

16. A transaction server enabling use of at least one application server application by a wireless communication device, comprising:

a memory storing at least one queue, with one queue being provided for each of said at least one application on said application server;

a processor for, on receipt of a given message from said wireless communication device for a given application on said application server;

pushing said given message, and each message queued on a queue for said application, toward a destination for said application of said application server.

17. The transaction server of claim 16 wherein said processor is further for queuing said given message on said queue prior to pushing said given message, and wherein said pushing by said processor comprises, for each message on said queue, dequeuing said each message from said queue and pushing said each message.

18. The transaction server of claim 16 wherein said processor is further for, prior to said dequeuing and pushing, acquiring a lock for said destination on said application server, said lock preventing other use of said destination.

19. The transaction server of claim 17 wherein messages on each of said at least one queue are queued on a first in first out basis and wherein said processor is for refraining from pushing a trailing message in said queue until said processor considers a message in said queue immediately preceding said trailing message has successfully reached said destination.

20. The transaction server of claim 19 wherein said processor is further for, if a given message pushed from said given queue toward said destination does not successfully reach said destination, ceasing said dequeuing and pushing and re-queuing said given message on said given queue.

21. A computer readable medium containing computer executable instructions for enabling use of an application server application by a wireless communication device, said computer executable instructions, when controlling a processor of a transaction server, causing said transaction server to:

on receipt of a given message from said wireless communication device for said application on said application server, push said given message, and each message queued on a queue for said application, toward a destination for said application of said application server.