Methods, systems, and computer program products for sharing information for detecting an idle TCP connection

• US 10,375,215 B1
• Filed: 07/19/2018
• Issued: 08/06/2019
• Est. Priority Date: 02/27/2010
• Status: Active Grant

• Current Assignee: Jenam Tech, LLC (Oso IP, LLC)
• Original Assignee: Jenam Tech, LLC (Oso IP, LLC)
• Inventors: Morris, Robert Paul
• Primary Examiner(s): Meky, Moustafa M
• Application Number:
  US16/040,522
• Time in Patent Office: 383 Days
• CPC Class Codes: G06F 9/50 Allocation of resources, e.g. of the central processing unit [CPU]
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Abstract

A computer-implemented method is provided, comprising causing access to be provided, to a client computer, to code that causes the client computer to operate in accordance with a protocol that is separate from TCP, in order to establish a protocol connection with another server computer, by: receiving a packet, detecting an idle time period parameter field in the packet, identifying metadata in the idle time period parameter field for an idle time period, where, after the idle time period is detected, the second protocol connection is deemed inactive, and creating or modifying, by the client computer and based on the metadata, a timeout attribute associated with the second protocol connection.

Claims

1. A computer-implemented method, comprising:

at a server node;

causing data to be sent to a client node; and

providing access, to the client node, to code that, in response to being used by the client node, causes the client node to;

receive, by the client node, a transmission control protocol (TCP)-variant packet,

detect an idle time period parameter field in the TCP-variant packet,

identify metadata in the idle time period parameter field for an idle time period, during which, no packet is communicated in a TCP-variant connection to keep the TCP-variant connection active, and

determine, based on the metadata, a timeout attribute associated with the TCP-variant connection.

2. The method of claim 1 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to operate such that one or more keep-alive packets are communicated, based on the idle time period.

3. The method of claim 1 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to operate such that one or more keep-alive packets are communicated, based on a keep-alive period.

4. The method of claim 1 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to operate such that one or more keep-alive packets are communicated, based on a keep-alive period that is, in turn, based on the idle time period.

5. The method of claim 4 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to operate such that the keep-alive period is not user-configurable.

6. The method of claim 4 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to operate such that the keep-alive period is not configurable, while the idle time period is configurable.

7. The method of claim 4 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to operate such that the one or more keep-alive packets are empty.

8. The method of claim 4 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to operate such that the keep-alive period is administered using a keep-alive timer.

9. The method of claim 8 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to operate such that the keep-alive timer is separate from an idle timer that is used to administer the idle time period.

10. The method of claim 4 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to operate such that the one or more keep-alive packets are conditionally communicated based on at least one keep-alive attribute.

11. The method of claim 10 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to operate such that the keep-alive attribute is separate from the timeout attribute.

12. The method of claim 1 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to operate such that a negotiation is performed between another server node and the client node as to the idle time period.

13. The method of claim 1 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to operate such that the TCP-variant packet is received for the purpose of negotiating a duration of the idle time period.

14. The method of claim 1 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to operate such that the TCP-variant packet is received for informational purposes and not for negotiating a duration of the idle time period.

15. The method of claim 1 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to determine, based on the metadata, the timeout attribute associated with the TCP-variant connection, without an ability to negotiate, with another server node, a duration of the idle time period.

16. The method of claim 1 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to determine, based on the metadata, the timeout attribute associated with the TCP-variant connection, after negotiating, with another server node, a duration of the idle time period.

17. The method of claim 1 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to determine, based on the metadata, the timeout attribute associated with the TCP-variant connection, after sending, to another server node, a different TCP-variant packet with different metadata in an idle time period parameter field thereof.

18. The method of claim 1 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to operate such that a duration of the idle time period is configured by an application via an analog of a socket.

19. The method of claim 1 wherein the code, to which the access is provided, is configured such that, in response to being used by the client node, causes the client node to operate such that the metadata is identified by an application via an analog of a socket.

20. A computer-implemented method comprising:

at a server computer including a non-transitory memory storing a network application, and one or more processors in communication with the non-transitory memory for executing the network application to operate in accordance with a first protocol including a transmission control protocol (TCP);

causing a TCP connection to be established with a client computer;

causing first data to be communicated from the server computer to the client computer utilizing the TCP connection in accordance with the TCP protocol and a hypertext transfer protocol (HTTP), for being presented to a user of the client computer;

receiving second data, from the user of the client computer, utilizing the TCP connection in accordance with the TCP protocol and the HTTP protocol; and

permitting access to code that, based on use by the client computer, results in the client computer operating in accordance with a second protocol that is separate from the TCP, in order to establish a second protocol connection with another server computer, by;

identifying idle information for detecting an idle time period, based on which, the second protocol connection is subject to deactivation,

generating a second protocol packet including an idle time period parameter field identifying metadata for the idle time period based on the idle information, and

sending, from the client computer to the another server computer, the second protocol packet to provide the metadata for the idle time period to the another server computer, for use by the another server computer in creating or modifying, based on the metadata, a timeout attribute associated with the second protocol connection.

21. The computer-implemented method of claim 20 wherein:

the use of the code by the client computer results in the client computer utilizing the second protocol instead of the TCP in order to send, from the client computer to the another server computer, the second protocol packet, where the second protocol packet is not sent based on establishing the TCP connection in accordance with the TCP, but is sent based on establishing the second protocol connection so as to permit the second protocol connection to be at least partially closed in response to being inactive based on the timeout attribute;

the access to the code is permitted by permitting the client computer to receive the code from the server computer utilizing the TCP connection and the HTTP protocol;

the timeout attribute is specified in a number of seconds;

the use of the code by the client computer results in the client computer operating such that the timeout attribute is used to keep the second protocol connection open in response to being inactive, and to prevent the another server computer from closing the second protocol connection in response to being inactive; and

the use of the code by the client computer results in the client computer operating such that the identifying the idle information is performed at a non-TCP layer other than a TCP layer, where the non-TCP layer is above an Internet Protocol (IP) layer and below an HTTP application layer.

22. The method of claim 21 wherein the code, to which the access is permitted, is configured to, based on use by the client computer, result in the client computer operating such that one or more keep-alive packets are communicated, based on a keep-alive period that is, in turn, based on the idle time period.

23. The method of claim 22 wherein the code, to which the access is permitted, is configured to, based on use by the client computer, result in the client computer operating such that the keep-alive period is not configurable, while the idle time period is configurable.

24. The method of claim 22 wherein the code, to which the access is permitted, is configured to, based on use by the client computer, result in the client computer operating such that the keep-alive period is administered using a keep-alive timer that is separate from an idle timer that is used to administer the idle time period.

25. The method of claim 22 wherein the code, to which the access is permitted, is configured to, based on use by the client computer, result in the client computer operating such that the one or more keep-alive packets are conditionally communicated based on at least one keep-alive attribute.

26. The method of claim 25 wherein the code, to which the access is permitted, is configured to, based on use by the client computer, result in the client computer operating such that the keep-alive attribute is separate from the timeout attribute.

27. The method of claim 21 wherein the code, to which the access is permitted, is configured to, based on use by the client computer, result in the client computer operating such that the second protocol packet is sent for the purpose of negotiating a duration of the idle time period.

28. The method of claim 21 wherein the code, to which the access is permitted, is configured to, based on use by the client computer, result in the client computer operating such that the second protocol packet is sent for informational purposes and not for negotiating a duration of the idle time period.

29. The method of claim 21 wherein the code, to which the access is permitted, is configured to, based on use by the client computer, result in the client computer operating such that a duration of the idle time period is configured by a particular application via an analog of a socket.

30. The method of claim 29 wherein the code, to which the access is permitted, is configured to, based on use by the client computer, result in the client computer operating such that one or more keep-alive packets are communicated, based on a keep-alive period that is, in turn, based on the idle time period.

31. A computer-implemented method comprising:

at a server computer including a non-transitory memory storing instructions, and one or more processors in communication with the non-transitory memory for executing the instructions such that the server computer operates in accordance with a first protocol including a transmission control protocol (TCP) in order to set up a TCP connection with a client computer;

causing first data to be communicated from the server computer to the client computer utilizing the TCP connection in accordance with the TCP protocol and a hypertext transfer protocol (HTTP), for being presented to a user of the client computer;

receiving, at the server computer, second data of the user of the client computer, utilizing the TCP connection in accordance with the TCP protocol and the HTTP protocol; and

permitting access to code that causes the client computer to operate in accordance with a second protocol that is different from the TCP and that operates above an Internet Protocol (IP) layer and below an HTTP application layer, in order to setup a second protocol connection with another server computer, by;

receiving, by the client computer from the another server computer, a packet,

identifying metadata, that specifies a number of seconds or minutes, in an idle time period parameter field in the packet for an idle time period during which, no packet is communicated that meets each of the following criteria;

a) communicated via the second protocol connection, and b) causes the second protocol connection to be kept at least partially alive, and

determining, by the client computer and based on the metadata, a timeout attribute associated with the second protocol connection.

32. The method of claim 31 wherein the code, to which the access is permitted, is configured to cause the client computer to operate such that:

one or more keep-alive packets are communicated, based on a keep-alive period that is, in turn, based on the idle time period;

the keep-alive period is not configurable, while the idle time period is configurable; and

the one or more keep-alive packets are conditionally communicated based on at least one keep-alive attribute.

33. The method of claim 32 wherein the code, to which the access is permitted, is configured to cause the client computer to determine, based on the metadata, the timeout attribute associated with the second protocol connection, without an ability to negotiate, with the another server computer, a duration of the idle time period.

34. The method of claim 32 wherein the code, to which the access is permitted, is configured to cause the client computer to determine, based on the metadata, the timeout attribute associated with the second protocol connection, after negotiating, with the another server computer, a duration of the idle time period.

35. The method of claim 32 wherein the code, to which the access is permitted, is configured to cause the client computer to operate such that a duration of the idle time period is configured by an application via an analog of a socket.

36. The method of claim 31 wherein the code, to which the access is permitted, is configured to cause the client computer to operate such that at least one of:

the access to the code is permitted by sending the code from the server computer to the client computer;

the access to the code is permitted by receiving the code from the another server computer;

the communication includes only receiving;

the communication includes only sending;

the communication includes receiving and sending;

the second protocol includes a variant to the TCP;

the second protocol includes an extension to the TCP;

the second protocol includes a non-TCP protocol;

the second protocol connection includes a first connection that is set up;

the second protocol connection includes an initial connection that is set up;

the metadata specifies a number of seconds;

the metadata specifies a number of minutes;

the packet is informational;

the packet is received directly by the another server computer from the client computer;

the packet is received by the another server computer from the client computer via at least one other intermediate computer;

the timeout attribute is capable being the same as the metadata;

the timeout attribute is capable being different from the metadata;

the timeout attribute specifies a time duration;

the determining the timeout attribute includes at least one of modifying, creating, or deleting the timeout attribute;

the second protocol operates directly above the IP layer;

the second protocol operates directly below a HTTP application layer;

the code includes machine code or program code;

the code includes at least one instruction;

the code is used in connection with a link component;

the code includes a readable instruction;

the code includes a data structure;

the code includes a program component;

the code is a readable instruction;

the code is a data structure;

the code is a program component;

the code is software;

the code includes one or more links;

the code includes at least one of;

a readable instruction, a data structure, or a program component;

the code resides at the server computer that is different from the another server computer, and is fetched from the server computer by the client computer;

or

during the idle time period, a data-equipped second protocol packet is capable of being received by the client computer in another connection separate from the second protocol connection.

37. The method of claim 31 wherein the code, to which the access is permitted, is configured to cause the client computer to operate such that the access to the code is permitted by sending the code from the server computer to the client computer.

38. The method of claim 31 wherein the code, to which the access is permitted, is configured to cause the client computer to operate such that the access to the code is permitted by receiving the code at the client computer from the another server computer.

39. The method of claim 31 wherein the access to the code is permitted by the server computer allowing the code to be communicated to the client computer from the another server computer.