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

• US 10,306,026 B1
• Filed: 07/19/2018
• Issued: 05/28/2019
• Est. Priority Date: 02/27/2010
• Status: Expired due to Fees

• 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,517
• Time in Patent Office: 313 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 method, comprising:

at a node;

receiving, from another node, a transmission control protocol (TCP)-variant packet in advance of a TCP-variant connection being established;

detecting an idle time period parameter field in the TCP-variant packet;

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

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

2. The method of claim 1 wherein the timeout attribute is an attribute of a keep-alive.

3. The method of claim 1 wherein at least one of:

the node includes a server, the server being configured to;

in response to the receiving, send, to the another node, another TCP-variant packet in advance of the TCP-variant connection being established, the another TCP-variant packet including other metadata for the idle time period;

or

the node includes a client, the client being configured such that the receiving is performed subsequent to sending, to the another node, another TCP-variant packet in advance of the TCP-variant connection being established including other metadata for the idle time period.

4. The method of claim 3 wherein, regardless as to whether the node is the server or the client, the metadata is the same as the other metadata.

5. The method of claim 3 wherein, regardless as to whether the node is the server or the client, the metadata is different from the other metadata.

6. The method of claim 1 wherein the timeout attribute is specified in at least one of a number of seconds or minutes.

7. The method of claim 1 wherein the timeout attribute is used to keep the TCP-variant connection open in response to being inactive, and to prevent one or more other nodes from closing the TCP-variant connection in response to being inactive.

8. The method of claim 1 wherein the metadata is used as input of an algorithm for determining a duration of time specified by the timeout attribute.

9. The method of claim 8 wherein the algorithm is determined based on at least one particular attribute.

10. The method of claim 1 wherein the modification of the timeout attribute results from a negotiation between the another node and the node via a negotiation protocol of a TCP-variant protocol.

11. The method of claim 1 and further comprising:

detecting the idle time period based on the timeout attribute; and

in response to detecting the idle time period, deactivating the TCP-variant connection by releasing a resource allocated for the TCP-variant connection by one of the nodes without signaling another one of the nodes that is related to the detection of the idle time period.

12. The method of claim 1 wherein at least one of the detecting or the identifying is performed at a TCP-variant layer other than a TCP layer, where the TCP-variant layer is above an Internet Protocol (IP) layer and below a hypertext transfer protocol (HTTP) application layer.

13. The method of claim 1 and further comprising:

executing a network application that is configured to perform a 3-way TCP handshake for establishing a TCP connection that is different than the TCP-variant connection, and wherein the network application is configured to establish the TCP-variant connection instead of the TCP connection in order to permit negotiation, between the another node and the node, of the timeout attribute, where the timeout attribute is not available in response to establishing the TCP connection, but is available in response to establishing the TCP-variant connection so that the TCP-variant connection is capable of being at least partially closed as a result of being inactive based on the timeout attribute.

14. The method of claim 1 wherein the TCP-variant packet and the metadata included therewith are received from the another node, without any prior signaling from the node to the another node.

15. The method of claim 1 wherein one or more keep-alive packets are communicated, based on the idle time period.

16. The method of claim 1 wherein one or more keep-alive packets are communicated, based on a keep-alive period.

17. The method of claim 1 wherein one or more keep-alive packets are communicated, based on a keep-alive period that is, in turn, based on the idle time period.

18. The method of claim 17 wherein the keep-alive period is not user-configurable.

19. The method of claim 17 wherein the keep-alive period is not configurable, while the idle time period is configurable.

20. The method of claim 17 wherein the one or more keep-alive packets are empty.

21. The method of claim 17 wherein the keep-alive period is administered using a keep-alive timer.

22. The method of claim 21 wherein the keep-alive timer is separate from an idle timer that is used to administer the idle time period.

23. The method of claim 17 wherein the one or more keep-alive packets are conditionally communicated based on at least one keep-alive attribute.

24. The method of claim 23 wherein the keep-alive attribute is separate from the timeout attribute.

25. The method of claim 1 wherein a negotiation is performed between the node and the another node as to the idle time period.

26. The method of claim 1 wherein the TCP-variant packet is received for the purpose of negotiating a duration of the idle time period.

27. The method of claim 1 wherein the TCP-variant packet is received for informational purposes and not for negotiating a duration of the idle time period.

28. The method of claim 1 wherein the node modifies, based on the metadata, the timeout attribute associated with the TCP-variant connection, without an ability to negotiate, with the another node, a duration of the idle time period.

29. The method of claim 1 wherein the node modifies, based on the metadata, the timeout attribute associated with the TCP-variant connection, in connection with negotiating, with the another node, a duration of the idle time period.

30. The method of claim 1 wherein the node modifies, based on the metadata, the timeout attribute associated with the TCP-variant connection, after sending, to the another node, a different TCP-variant packet with different metadata in an idle time period parameter field thereof.

31. The method of claim 1 wherein a duration of the idle time period is configured by an application via an analog of a socket.

32. The method of claim 1 wherein the metadata is identified by an application via an analog of a socket.

33. A method, comprising:

at a node;

receiving idle information for detecting an idle time period, during which, no packet is communicated in a transmission control protocol (TCP)-variant connection to keep the TCP-variant connection active;

generating a TCP-variant packet including an idle time period parameter field identifying metadata for the idle time period based on the idle information; and

sending, from the node to another node, the TCP-variant packet in advance of the TCP-variant connection being established to provide the metadata for the idle time period to the another node, for use by the another node in modifying, based on the metadata, a timeout attribute associated with the TCP-variant connection.

34. The method of claim 33 wherein modifying the timeout attribute reduces a number of keep-alive signals that are required to be communicated.

35. The method of claim 33 wherein the TCP-variant packet and the metadata included therewith are sent by the node to the another node, without any prior signaling received by the node from the another node.

36. The method of claim 33 wherein the metadata includes a first value and the timeout attribute is capable of being modified to include a second value that is different than the first value of the metadata.

37. The method of claim 33 wherein the timeout attribute is specified in a number of seconds.

38. The method of claim 33 wherein the modification of the timeout attribute results from a negotiation between the another node and the node.

39. The method of claim 33 and further comprising:

detecting the idle time period based on the idle information; and

in response to detecting the idle time period, deactivating the TCP-variant connection.

40. The method of claim 33 wherein at least the generating is performed at a TCP-variant layer other than a TCP layer, where the TCP-variant layer is above an Internet Protocol (IP) layer and below a hypertext transfer protocol (HTTP) application layer.

41. The method of claim 33 and further comprising:

executing a network application that is configured to perform, in another scenario, a 3-way TCP handshake for establishing a TCP connection that is different than the TCP-variant connection, and wherein the network application is configured to establish the TCP-variant connection instead of the TCP connection and thus permit a negotiation, between the another node and the node, of the timeout attribute, where a negotiated timeout attribute is not available in response to establishing the TCP connection, but is available in response to establishing the TCP-variant connection so that the TCP-variant connection is at least partially closed as a result of being inactive based on the negotiated timeout attribute.

42. The method of claim 33 wherein the TCP-variant packet and the metadata included therewith are sent by the node to the another node, in response to receiving, by the node from the another node, another TCP-variant packet with other metadata.

43. The method of claim 33 wherein one or more keep-alive packets are communicated, based on a keep-alive period that is, in turn, based on the idle time period.

44. The method of claim 43 wherein the keep-alive period is not user configurable.

45. The method of claim 43 wherein the keep-alive period is not configurable, while the idle time period is configurable.

46. The method of claim 43 wherein 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.

47. The method of claim 43 wherein the one or more keep-alive packets are conditionally communicated based on at least one keep-alive attribute.

48. The method of claim 47 wherein the keep-alive attribute is separate from the timeout attribute.

49. The method of claim 33 wherein the TCP-variant packet is sent for the purpose of negotiating a duration of the idle time period.

50. The method of claim 33 wherein the TCP-variant packet is sent for informational purposes and not for negotiating a duration of the idle time period.

51. The method of claim 33 wherein a duration of the idle time period is configured by an application via an analog of a socket.

52. A method comprising:

at a node configured to execute a network application such that the network application operates in accordance with a non-transmission control protocol (TCP) protocol that operates above an Internet Protocol (IP) layer and below a hypertext transfer protocol (HTTP) application layer;

receiving, from another node, a non-TCP packet during a setup of a non-TCP connection;

identifying metadata, that specifies at least one of a number of seconds or minutes, in an idle time period parameter field in the non-TCP packet, for an idle time period, where, as a result of a detection of the idle time period, the non-TCP connection is subject to deactivation; and

determining, based on the metadata, a timeout attribute associated with the non-TCP connection;

wherein, based on operating in accordance with the TCP protocol, a three-way TCP handshake is performed for establishing a TCP connection that is different than the non-TCP connection.

53. The method of claim 52 wherein:

the non-TCP packet and the idle time period parameter field included therewith are operable for being received from the another node, without any prior signaling from the node to the another node;

the determination of the timeout attribute results from a negotiation between the another node and the node; and

the metadata includes a first value and the timeout attribute is determined to include a second value that is different than the first value of the metadata.

54. The method of claim 52 and further comprising:

detecting the idle time period based on the timeout attribute; and

deactivating the non-TCP connection by communicating a particular packet between the another node and the node, in response to detecting the idle time period.

55. The method of claim 52 wherein one or more keep-alive packets are communicated, based on a keep-alive period that is, in turn, based on the idle time period.

56. The method of claim 55 wherein the keep-alive period is not configurable, while the idle time period is configurable.

57. The method of claim 55 wherein the one or more keep-alive packets are conditionally communicated based on at least one keep-alive attribute.

58. The method of claim 55 wherein the node determines, based on the metadata, the timeout attribute associated with the non-TCP connection, without an ability to negotiate, with the another node, a duration of the idle time period.

59. The method of claim 55 wherein the node determines, based on the metadata, the timeout attribute associated with the non-TCP connection, in connection with negotiating, with the another node, a duration of the idle time period.

60. The method of claim 55 wherein a duration of the idle time period is configured by an application via an analog of a socket.

61. A method comprising:

at a node configured to execute a network application such that the network application is operates in accordance with a non-transmission control protocol (TCP) protocol that operates above an Internet Protocol (IP) layer and below a hypertext transfer protocol (HTTP) application layer;

receiving idle information for use in detecting an idle time period that results in a non-TCP connection being subject to deactivation;

generating, based on the idle information, a non-TCP packet including an idle time period parameter field identifying metadata that is specified in at least one of a number of seconds or minutes; and

sending, from the node to another node and for establishing the non-TCP connection, the non-TCP packet to provide the metadata to the another node, for use by the another node in determining a timeout attribute associated with the non-TCP connection;

wherein a three-way TCP handshake is performed for establishing a TCP connection that is separate from the non-TCP connection.

62. The method of claim 61 wherein:

the determination of the timeout attribute results from a negotiation between the another node and the node;

during the idle time period, no non-TCP packet including data is communicated in the non-TCP connection, and further comprising;

detecting the idle time period based on the idle information; and

in response to detecting the idle time period, deactivating the non-TCP connection by at least partially closing the non-TCP connection by one of the nodes without communication between the node and the another node that is related to the detection of the idle time period.

63. The method of claim 62 wherein at least one of:

the communication includes only receiving;

the communication includes only sending;

the communication includes receiving and sending;

a non-TCP protocol includes a variant to the TCP;

the non-TCP packet is sent directly from the node to the another node;

the non-TCP packet is sent from the node to the another node via at least one other node;

the idle time period parameter field is part of a data portion in the non-TCP packet;

the idle time period parameter field is part of a header of the non-TCP packet;

the idle information is received based on a previous header;

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

the timeout attribute is capable being different from the metadata;

the idle time period is specified in a number of seconds;

the idle time period is specified in a number of minutes;

the timeout attribute specifies a duration;

the non-TCP packet is informational;

a TCP protocol operates directly above the IP layer;

a TCP protocol operates directly below the HTTP application layer;

the non-TCP protocol operates directly above the IP layer;

the non-TCP protocol operates directly below the HTTP application layer;

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

the network application provides the idle information to a ITP policy component via a settings service component interoperating with a sockets component;

during the idle time period, a non-TCP packet including data is received by the node where the non-TCP packet including data is sent by the another node;

during the idle time period, a non-TCP packet including data is received by the another node where the non-TCP packet including data is sent by the node;

or

during the idle time period, a non-TCP packet including data is received by the node where the non-TCP packet including data is sent in the TCP connection.

64. The method of claim 61 wherein:

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.

65. The method of claim 64 and further comprising:

configuring the node to cause the another node to determine, based on the metadata, the timeout attribute associated with the non-TCP connection, without an ability to negotiate, with the node, a duration of the idle time period.

66. The method of claim 64 and further comprising:

configuring the node to cause the another node to determine, based on the metadata, the timeout attribute associated with the non-TCP connection, in connection with negotiating, with the node, a duration of the idle time period.

67. The method of claim 64 wherein a duration of the idle time period is configured by an application via an analog of a socket.

68. A method comprising:

at a node configured with a network application that is configured to operate in accordance with a first protocol including a transmission control protocol (TCP) to establish a TCP connection;

based on operating in accordance with a second protocol, that is separate from the TCP, to establish a second protocol connection;

receiving, from another node, 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, in response to the idle time period being detected, the second protocol connection is deemed inactive; and

creating or modifying, based on the metadata, a timeout attribute associated with the second protocol connection.

69. The method of claim 68 wherein creating or modifying the timeout attribute renders one or more keep-alive packets in the second protocol connection unnecessary.

70. The method of claim 68 wherein at least one of:

the node includes a server, the server being configured to;

based on the receiving, send, to the another node, another packet in advance of the second protocol connection being established, another packet including other metadata for the idle time period;

or

the node includes a client, the client being configured such that the receiving is performed subsequent to sending, to the another node, another packet in advance of the second protocol connection being established including other metadata for the idle time period.

71. The method of claim 70 wherein the metadata is the same as the other metadata.

72. The method of claim 70 wherein the metadata is different from the other metadata.

73. The method of claim 70 wherein the metadata is based on the other metadata.

74. The method of claim 68 wherein the timeout attribute is specified in at least one of a number of seconds or minutes.

75. The method of claim 68 wherein the metadata is used as input of an algorithm for determining a duration of time associated with the timeout attribute.

76. The method of claim 75 wherein the algorithm is determined, in response to the identification of the metadata and based on at least one particular attribute not related to the metadata.

77. The method of claim 68 wherein the creation or the modification of the timeout attribute results from a negotiation between the another node and the node via a negotiation protocol specific to the second protocol.

78. The method of claim 68 and further comprising:

detecting the idle time period based on the timeout attribute; and

deactivating the second protocol connection in response to detecting the idle time period.

79. The method of claim 68 wherein the second protocol is utilized instead of the TCP in order to permit negotiation, between the another node and the node, of the timeout attribute, where a negotiated timeout attribute is not available based on operating in accordance with the TCP, but is available based on establishing the second protocol connection so as to permit the second protocol connection to be at least partially closed based on the negotiated timeout attribute in response to the second protocol connection being inactive.

80. The method of claim 68 wherein the timeout attribute is used to determine whether to at least partially close the second protocol connection when inactive.

81. The method of claim 68 wherein the packet and the metadata included therewith are received from the another node, without requiring any prior signaling from the node to the another node.

82. A method comprising:

at a node including a network application configured to operate in accordance with a first protocol including a transmission control protocol (TCP) to establish a TCP connection;

based on operating in accordance with a second protocol, that is separate from the TCP, to establish a second protocol connection;

receiving idle information for detecting an idle time period, in connection with 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 node to another node, the second protocol packet to provide the metadata for the idle time period to the another node, for use by the another node in creating or modifying, based on the metadata, a timeout attribute associated with the second protocol connection.

83. The method of claim 82 wherein the timeout attribute is an attribute of the idle time period.

84. The method of claim 82 wherein the second protocol packet and the metadata included therewith are sent by the node to the another node, without any prior signaling between the node and the another node.

85. The method of claim 82 wherein the metadata includes a first value and the timeout attribute is capable of being created or modified to include a second value that is different than the first value of the metadata.

86. The method of claim 82 wherein the timeout attribute is at least one of a number of seconds or minutes.

87. The method of claim 82 wherein the creation or the modification of the timeout attribute results from a negotiation between the another node and the node.

88. The method of claim 82 and further comprising:

detecting the idle time period; and

deactivating the second protocol connection by communicating a particular packet between the another node and the node, in response to detecting the idle time period.

89. The method of claim 82 wherein the second protocol is utilized instead of the TCP in order to permit negotiation, between the another node and the node, of the timeout attribute, where the negotiation of the timeout attribute is not available based on operating in accordance with the TCP, but is available in response to 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.

90. The method of claim 82 wherein the timeout attribute serves to keep the second protocol connection open in response to being inactive, and to prevent one or more other nodes from closing the second protocol connection in response to being inactive.

91. The method of claim 82 wherein the second protocol packet and the metadata included therewith are sent by the node to the another node, in response to receiving, by the node from the another node, another second protocol packet with other metadata.

92. A method comprising:

at a node with a network application that operates in accordance with a first protocol including a transmission control protocol (TCP) that operates above an Internet Protocol (IP) layer and below a hypertext transfer protocol (HTTP) application layer;

based on operating in accordance with a second protocol that is different from the TCP, to set up a second protocol connection, where the second protocol operates above the IP layer and below the HTTP application layer;

receiving, from another node, a packet;

identifying metadata, that specifies at least one of a number of seconds or minutes, in an idle time period parameter field in the packet for an idle time period and, 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, based on the metadata, a timeout attribute associated with the second protocol connection.

93. The method of claim 92 wherein:

nothing is communicated that meets each of the criteria, during the idle time period;

the determination of the timeout attribute results from a negotiation between the another node and the node; and

the metadata includes a first value and the timeout attribute is determined to include a second value that is different than the first value of the metadata.

94. The method of claim 92 and further comprising:

detecting the idle time period based on the timeout attribute; and

deactivating the second protocol connection by communicating a particular packet between the another node and the node, in response to detecting the idle time period.

95. The method of claim 94 wherein at least one of:

the communication includes only receiving;

the communication includes only sending;

the communication includes receiving and sending;

the particular packet is communicated between the another node and the node, by being communicated from the another node to the node;

the particular packet is communicated between the another node and the node, by being communicated from the node to the another node;

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 node from the another node;

the packet is received by the node from the another node via at least one other intermediate node;

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 TCP operates directly above the IP layer;

the TCP operates directly below the HTTP application layer;

the second protocol operates directly above the IP layer;

the second protocol operates directly below the HTTP application layer;

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

or

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

96. A method comprising:

at a node including a network application that operates in accordance with a first protocol including a transmission control protocol (TCP) that operates above an Internet Protocol (IP) layer and below a hypertext transfer protocol (HTTP) application layer to set up a TCP connection;

based on the network application operating in accordance with a second protocol, that is different from the TCP, to set up a second protocol connection, where the second protocol operates above the IP layer and below the HTTP application layer;

receiving idle information for use in detecting an idle time period during which no signal is communicated that meets each of the following criteria;

a) communicated in the second protocol connection, and b) results in the second protocol connection being at least partially kept alive;

generating, based on the idle information, a second protocol packet including an idle time period parameter field identifying metadata that is specified in at least one of a number of seconds or minutes; and

sending, from the node to another node and during the set up of the second protocol connection, the second protocol packet to provide the metadata to the another node, for use by the another node in determining a timeout attribute associated with the second protocol connection.

97. The method of claim 96 wherein:

the determination of the timeout attribute results from a negotiation between the another node and the node, and further comprising;

detecting the idle time period based on the idle information; and

releasing a resource allocated for the second protocol connection by one of the nodes without signaling another one of the nodes in connection with the detection of the idle time period.

98. The method of claim 96, wherein, based on the network application operating in accordance with the second protocol to set up the second protocol connection, the second protocol operates exclusively above the IP layer and below the HTTP application layer.