ONLINE MOBILE APPLICATIONS CAPABLE OF DEALING WITH OCCASIONAL DISCONNECTS

• US 20090228545A1
• Filed: 03/04/2009
• Published: 09/10/2009
• Est. Priority Date: 03/07/2008
• Status: Abandoned Application

• Current Assignee: Capgemini Us LLC (Capgemini SE)
• Original Assignee: Capgemini Us LLC (Capgemini SE)
• Inventors: Dai, Jun, Mendez, Jose A., Soltero, Carlos Juan
• Application Number:
  US12/397,985
• Publication Number:
  US 20090228545A1
• Time in Patent Office: Days
• US Class Current: 709/202
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• 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/59 Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable

Abstract

A technique for building applications consuming web services; where users can use the application while being online or offline, while maintaining the impression and feel of an online application, and without the requirements of a synchronization engine.

Claims

1. A system for providing seamless operation for a mobile application operating on a mobile device, the mobile application utilizing web services of a web server when the mobile device is connected to the web server, and the seamless operation being provided when the mobile device is disconnected from the web server, the system comprising:

an application logic unit that interfaces to the mobile application;

a cached service agent unit that is communicatively coupled to the application logic unit, a cache within a memory device and to a web server through a network, the cached service agent unit being implemented by a processing unit and operative to;

receiving a call generated as the result of an operation of the mobile device;

translating the call into a request and forwarding the request to a web server over the network;

receiving a response from the web server, the response being associated with the request;

generating an identifier that is associated with the request;

storing the identifier along with the response into the cache;

generating a result from the response associated with the call; and

communicating the result to the application logic unit.

2. The system of claim 1, wherein the application logic unit is implemented by a processing unit and is operative to:

detect an operation of the mobile application;

generate a call based on the detected operation;

provide the call to the cached service agent unit;

receive a result from the cached service agent unit, the result being received in response to the call; and

interfacing with the mobile application in a manner based on the result.

3. The system of claim 2, wherein if the cached service agent unit is not communicatively coupled to the web server, the cached service agent unit is further operative to:

examine the cache for a response associated with the generated identifier;

if a response is identified, generate a local result based on the identified response; and

provide the local result to application logic unit.

4. The system of claim 2, wherein the cached service agent unit is further operative to:

examine the cache for a response associated with the generated identifier;

if a response is identified, generate a local result based on the identified response; and

provide the local result to application logic unit.

5. The system of claim 4, wherein the application logic unit is further operative to:

receive the local result from the cached service agent unit, the local result being received in response to the call and being received prior to the result; and

interfacing with the mobile application in a manner based on the local result.

6. The system of claim 5, wherein the application logic unit is further operative to:

receive the result from the cached service agent unit, the result being received in response to the call and being received subsequently to receiving the local result; and

interfacing with the mobile application in a manner based on the result to update the mobile application is the result is different from the local result.

7. The system of claim 1, wherein the cache service agent unit further comprises a coordination agent unit that is operative to:

receive a batch of calls from the application logic unit;

store the batch of calls into a queue;

monitor the network connection to determine when the mobile application is connected to the web server;

if connectivity is available, processing the batch of calls in sequence one at a time; and

if connectivity is interrupted, identifying a last success point and, when connectivity is restored, continuing with processing the batch of calls in sequence from the last success point.

8. The system of claim 7, wherein if the cached service agent unit is not communicatively coupled to the web server, the cached service agent unit is further operative to:

examine the cache for a response associated with the generated identifier;

if a response is identified, generate a local result based on the identified response; and

provide the local result to application logic unit.

9. The system of claim 8, wherein the application logic unit is further operative to:

receive the local result from the cached service agent unit, the local result being received in response to the call and being received prior to the result; and

interfacing with the mobile application in a manner based on the local result.

10. The system of claim 9, wherein the application logic unit is further operative to:

receive the result from the cached service agent unit, the result being received in response to the call and being received subsequently to receiving the local result; and

interfacing with the mobile application in a manner based on the result to update the mobile application is the result is different from the local result.

11. A method for providing seamless operation of a web service dependent mobile application, the method comprising the steps of:

detecting an operation of the mobile application;

generating a call based on the detected operation;

translating the call into a request;

forwarding the request to a web server over a network;

receiving a response from the web server, the response being associated with the request;

generating an identifier that is associated with the request;

storing the identifier along with the response into a memory based cache;

generating a result from the response associated with the call; and

providing the result to the mobile application.

12. The method of claim 11, further comprising the steps of:

prior to performing the step of forwarding the request to a web server over a network, determining that there is no connectivity with the network;

examining the cache for a response associated with the identifier generated in the generating step;

if a response is identified, generating a local result based on the identified response; and

providing the local result to the mobile application.

13. The method of claim 12, further comprising the steps of:

subsequent to the step of providing the local result to the mobile application receiving the response from the web server and if the result for the received response would be different than the local result, continuing with the step of providing the result to the mobile application.

14. The method of claim 12, further comprising the steps of:

subsequent to the step of providing the local result to the mobile application, receiving the response from the web server and if the result for the received response is the same as the local result, skipping the step of providing the result to the mobile application.

15. The method of claim 11, wherein if connectivity with the network is interrupted, an offline mode of operation is activated which comprises the steps of:

examining the cache for a response associated with the generated identifier;

if a response is identified, generate a local result based on the identified response; and

provide the local result to application logic unit.

16. The method of claim 15, wherein when the offline mode of operation is activated, further comprising the steps of:

receiving an external notification;

in response to the external notification, exiting the offline mode of operation and preventing entrance to the offline mode of operation until particular criteria are satisfied.

17. A method for providing seamless operation of a web service dependent mobile application, the method comprising the steps of:

detecting an operation of the mobile application;

generating a plurality of calls based on the detected operation;

storing the plurality of calls into a queue;

receiving an indication that the plurality of calls are ready for execution;

for each call in the queue in sequence;

extracting the call from the queue;

translating the call into a request;

forwarding the request to a web server over a network;

generating a result from the response associated with the call; and

receiving a response from the web server, the response being associated with the request;

providing the result to the mobile application.

18. The method of claim 17, wherein if the connection to the network is interrupted, further comprising the steps of:

storing a last valid state that existed prior to the interrupted connection;

detecting the resumption of connectivity to the network; and

continuing the step of extracting the call from the queue starting at the last valid state.

19. The method of claim 18, further comprising the steps of:

generating an identifier that is associated with each request; and

storing the identifier along with the response into a memory based cache.