System and Method for Maintaining Connectivity to Remote Application Servers

• US 20120005501A1
• Filed: 07/01/2011
• Published: 01/05/2012
• Est. Priority Date: 07/01/2011
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Maciocco, Christian, Gobriel, Sameh, Fleming, Kristoffer, Prat, Gideon, Tai, Tsung-Yuan Charlie
• Granted Patent: US 8,239,698 B2
• Time in Patent Office: Days
• US Class Current: 713/320
• CPC Class Codes: G06F 1/3209 Monitoring remote activity, e.g. over telephone lines or network connections
• CPC Class Codes: G06F 1/3234 Power saving characterised by the action undertaken
• CPC Class Codes: G06F 1/3287 by switching off individual functional units in the computer system
• CPC Class Codes: H04L 12/12 Arrangements for remote connection or disconnection of substations or of equipment thereof
• 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/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04W 52/0206 in access points, e.g. base stations access point devices per se H04W88/08
• CPC Class Codes: H04W 76/25 Maintenance of established connections
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management
• CPC Class Codes: Y02D 30/70 in wireless communication networks

Abstract

A system and method for maintaining connectivity between a host system running an Always-On-Always-Connected (AOAC) application and an associated remote application server. The system further includes circuitry configured to establish a communication link between the host system and the remote application server. The circuitry is configured periodically transmit keep-alive messages to the remote application server after the host system transitions to and remains in a low-power state. The keep-alive messages are configured to maintain connectivity and presence of the AOAC application with the remote application server while the host system is in the low-power state.

Claims

1. A system, comprising:

a host system configured to operate in a first power state and a low-power state, said host system further configured to execute at least one Always-On-Always-Connected (AOAC) application while in said first power state;

circuitry configured to establish a communication link between said host system and an associated remote application server, said circuitry further configured to periodically transmit keep-alive messages to said remote application server while said host remains in said low-power state, said keep-alive messages configured to maintain connectivity and presence of said AOAC application with said remote application server while said host system is in said low-power state; and

memory configured to store said keep-alive messages, said memory configured to be accessible to said circuitry while said host system remains in said low-power state.

2. The system of claim 1, wherein said host system is configured to initiate generating said keep-alive message prior to transitioning to said low-power state.

3. The system of claim 1, wherein low-power state includes the S3 state as defined by the Advanced Configuration and Power Interface (ACPI) specification, and wherein first power state includes the S0 state as defined by the ACPI specification.

4. The system of claim 1, wherein said circuitry includes media access control (MAC) circuitry comprising transmit MAC circuitry and physical interface (PHY) circuitry comprising transmit circuitry, wherein said transmit MAC circuitry is configured to receive an AOAC command from a device driver operating on said host system, and, in response to said AOAC command, said transmit MAC circuitry and at least said transmit circuitry are configured to periodically transmit keep-alive messages stored in said memory to said remote application server while said host remains in said low-power state.

5. The system of claim 1, wherein said circuitry is further configured to transition said host system from said low-power state to a second power state when a remaining number of keep-alive messages in said memory reaches a threshold;

wherein said host system is further configured to generate additional keep-alive messages while in said second power state and transition back to said low-power state thereafter, and wherein said circuitry is further configured to transmit said additional keep-alive messages while said host system is in said low-power state, thereby maintaining connectivity and presence of said AOAC application with said remote application server while said host system is in said low-power state.

6. The system of claim 1, wherein said host system generates a list of pre-built keep-alive messages prior to said host system transitioning to said low-power state.

7. The system of claim 1, wherein said host system generates a general keep-alive message and a list of security tokens prior to said host system transitioning to said low-power state, and wherein said circuitry is further configured to recover said general keep-alive message and said list of security tokens, and assemble said general keep-alive message with a respective one of said security tokens from said list to generate a keep-alive message for transmission to said remote application server at the appropriate time.

8. The system of claim 1, wherein said circuitry is configured to transition said host system from said low-power state to a second power state based on a packet received from said remote application server.

9. An apparatus, comprising:

circuitry configured to establish a communication link between a host system executing an Always-On-Always-Connected (AOAC) application and a remote application server associated with said AOAC application, said circuitry further configured periodically transmit keep-alive messages to said remote application server after said host remains transitions from a first power state to a low-power state, said keep-alive messages configured to maintain connectivity and presence of said AOAC application with said remote application server while said host system is in said low-power state;

wherein said keep-alive messages are stored in memory accessible to said circuitry while said host system remains in said low-power state.

10. The apparatus of claim 9, wherein low-power state includes the S3 state as defined by the Advanced Configuration and Power Interface (ACPI) specification, and wherein first power state includes the S0 state as defined by the ACPI specification.

11. The apparatus of claim 9, wherein said circuitry includes media access control (MAC) circuitry comprising transmit MAC circuitry and physical interface (PHY) circuitry comprising transmit circuitry, wherein said transmit MAC circuitry is configured to receive an AOAC command from a device driver operating on said host system, and, in response to said AOAC command, said transmit MAC circuitry and at least said transmit circuitry are configured to periodically transmit keep-alive messages stored in said memory to said remote application server while said host remains in said low-power state.

12. The apparatus of claim 9, wherein said circuitry is configured to transition said host system from said low-power state to a second power state when a remaining number of keep-alive messages in said memory reaches a threshold;

wherein circuitry is further configured to initiate the generates of additional keep-alive messages while said host system is operating in said second power state; and

wherein said circuitry is further configured to transmit said additional keep-alive messages after said host system transition back to said low-power state, thereby maintaining connectivity and presence of said AOAC application with said remote application server while said host system is in said low-power state.

13. The apparatus of claim 9, wherein said circuitry is configured to recover a general keep-alive message and said list of security tokens from said host system and assemble said general keep-alive message with a respective one of said security tokens from said list to generate a keep-alive message for transmission to said remote application server at the appropriate time.

14. The apparatus of claim 9, wherein said circuitry is configured to transition said host system from said low-power state to a second power state based on a packet received from said remote application server.

15. A computer readable non-transitory medium having instructions stored thereon, the instructions when executed by a processor cause the processor to:

establish a communication link between a host system executing an Always-On-Always-Connected (AOAC) application and a remote application server associated with said AOAC application;

receive an indication to transition a host system from a first power state to a low-power state;

initiate the generation of a plurality of keep-alive messages associated with said AOAC application;

transition said host system from said first power state to said low-power state; and

periodically transmit said keep-alive messages from circuitry to said remote application server while said host system is in said low-power state, said keep-alive messages configured to maintain connectivity and presence of said AOAC application with said remote application server while said host system is in said low-power state.

16. The medium of claim 15, wherein said instructions when executed by said processor results in the following:

storing at least a portion of said keep-alive messages in memory accessible to said circuitry while said host system remains in said low-power state.

17. The medium of claim 15, wherein said instructions when executed by said processor results in the following:

generating a general keep-alive message and a list of security tokens prior to said host system transitioning to said low-power state;

recovering said general keep-alive message and said list of security tokens and assembling said general keep-alive message with a respective one of said security tokens from said list to generate said keep-alive message after said host system transitions to said low-power state.

18. The medium of claim 15, wherein said instructions when executed by said processor results in the following:

transition said host system from said low-power state to a second power state when a remaining number of keep-alive messages in said memory reaches a threshold; and

generate additional keep-alive messages while in said second power state and transition back to said low-power state thereafter, and wherein said NIC is further configured to transmit said additional keep-alive messages while said host system is in said low-power state, thereby maintaining connectivity and presence of said AOAC application with said remote application server while said host system is in said low-power state.

19. The medium of claim 15, wherein said instructions when executed by said processor results in the following:

transition said host system from said low-power state to a second power state based on a packet received from said remote application server.

20. The medium of claim 15, wherein low-power state includes the S3 state as defined by the Advanced Configuration and Power Interface (ACPI) specification, and wherein first power state includes the S0 state as defined by the ACPI specification.