GRACEFUL DEGRADATION OF WEBSOCKET CONNECTIONS TO NONPERSISTENT HTTP-BASED COMMUNICATIONS

• US 20140156725A1
• Filed: 12/01/2012
• Published: 06/05/2014
• Est. Priority Date: 12/01/2012
• Status: Active Grant

• Current Assignee: Qualcomm Innovation Center Incorporated (Qualcomm, Inc.)
• Original Assignee: Qualcomm Innovation Center Incorporated (Qualcomm, Inc.)
• Inventors: Mandyam, Giridhar D.
• Granted Patent: US 9,143,550 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 1/3212 Monitoring battery levels, e.g. power saving mode being initiated when battery voltage goes below a certain level
• CPC Class Codes: H04L 65/1083 In-session procedures
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/145 avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions
• CPC Class Codes: H04W 28/0221 power availability or consumption
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

Systems, methods, and apparatus for enabling communications between a client and server are herein disclosed such that a connection between the client and server can be switched from a persistent to a nonpersistent connection. Persistent connections tend to drain battery power and cause other degradations, and thus switching to nonpersistent connections, at least temporarily, can preserve battery power and enable other advantages.

Claims

1. A method for switching between a persistent communication protocol between a client and a server and a nonpersistent communication protocol between the client and the server, the method comprising:

establishing a persistent connection between the client and the server;

determining that the server can switch between the persistent and the nonpersistent communication protocols;

monitoring a battery of the client;

when a power level of the battery falls below a first threshold, terminating the persistent connection; and

initiating one or more nonpersistent connections between the client and the server.

2. The method of claim 1, further comprising monitoring the battery of the client after the initiating, and when the power of the battery rises above a second threshold, reestablishing the persistent connection.

3. The method of claim 1, further comprising polling the server to determine if there is data at the server waiting for the client, and initiating another nonpersistent connection between the client and the server in order to receive the data from the server.

4. The method of claim 1, wherein each of the one or more nonpersistent connections is an Asynchronous JavaScript and XML (AJAX) connection.

5. The method of claim 1, wherein the one or more nonpersistent connections are periodically established, and where the period enables the client to enter a power saving mode.

6. The method of claim 5, wherein the power saving mode is a dormancy state.

7. The method of claim 1, wherein the persistent connection is implemented via an API.

8. The method of claim 1, wherein the persistent connection is implemented via WebSockets.

9. The method of claim 1, wherein a radio of the client is active less often when communicating via the one or more nonpersistent connections than when communicating via the persistent connection, thus conserving battery power.

10. The method of claim 1, wherein the terminating of the persistent connection is a partial tearing down of the persistent connection.

11. The method of claim 10, wherein a WebSocket object persists while the persistent connection is terminated, the WebSocket object facilitating reestablishment of the persistent connection at a later time.

12. A client configured to partake in a communication connection with a server, the client comprising:

a protocol switching checker module that determines if the server can support, and switch between, persistent and nonpersistent communication protocols;

a persistent connection module that establishes a persistent connection between the client and the server;

a client state monitor that monitors a state of the client and initiates termination of the persistent connection when the state meets a predefined criterion; and

a nonpersistent connection module that establishes at least one nonpersistent connection between the client and the server once the state meets the predefined criterion.

13. The client of claim 12, wherein the state is a battery state.

14. The client of claim 13, wherein the predefined criterion is a battery power threshold.

15. The client of claim 12, wherein the state is a modem state.

16. The client of claim 15, wherein the predefined criterion is a change of the modem state from operating via a first network type to operating via a second network type.

17. The client of claim 12, wherein the persistent connection module is part of an operating system.

18. The client of claim 17, wherein the persistent connection module is part of an API of the operating system.

19. The client of claim 18, wherein the API remains open when the state meets the predefined criterion and the persistent connection is switched to the one or more nonpersistent connections.

20. The client of claim 12, where the client state monitor is part of a web runtime engine.

21. The client of claim 20, wherein the persistent connection is a WebSockets connection.

22. The client of claim 21, wherein a WebSocket object of the WebSockets connection remains open when the persistent connection is switched to the one or more nonpersistent connections.

23. The client of claim 12, wherein the client state monitor accesses hardware data that is not accessible to an application layer of an abstraction stack.

24. A websocket decision engine of a web runtime engine of a client comprising:

a means for establishing a persistent connection with a server;

a means for monitoring a state of the client;

a means for terminating the persistent connection when the state of the client meets a predefined criterion; and

a means for replacing the persistent connection with a nonpersistent connection subsequent to the state of the client meeting the predefined criterion.

25. The web runtime engine of claim 24, wherein the state of the client is a battery level.

26. The web runtime engine of claim 24, wherein the state of the client is a modem state.

27. The web runtime engine of claim 24, wherein the websocket decision engine further maintains a JavaScript WebSocket object associated with the persistent connection after termination of the persistent connection.

28. The web runtime engine of claim 24, wherein the terminating of the persistent connection is performed without informing a web application of the termination, where the web application runs on the web runtime engine.

29. A non-transitory, tangible computer readable storage medium of a server, encoded with processor readable instructions to perform a method for carrying out communication between a client and the server, the method comprising:

receiving a connection request from a client including a query as to whether the server is able to engage in nonpersistent as well as persistent connections;

returning a response to the client acknowledging that the server can engage in both nonpersistent and persistent connections;

engaging in persistent communication with the client via a persistent connection;

listening for a request for nonpersistent communication from the client once the persistent communication ends;

receiving the request for nonpersistent communication from the client; and

engaging in nonpersistent communication with the client.

30. The non-transitory, tangible computer readable storage medium of claim 29, wherein the server retains a session identification associated with the persistent connection and uses the session identification to maintain continuity with the nonpersistent communication.

31. The non-transitory, tangible computer readable storage medium of claim 30, wherein the nonpersistent communication involves an AJAX request from the client to the server, and wherein the AJAX request includes a message from the client.