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

• US 9,923,995 B1
• Filed: 09/03/2017
• Issued: 03/20/2018
• Est. Priority Date: 02/27/2010
• Status: Active Grant

• Current Assignee: Jenam Tech, LLC (Oso IP, LLC)
• Original Assignee: Sitting Man LLC
• Inventors: Morris, Robert Paul
• Primary Examiner(s): Meky, Moustafa M
• Application Number:
  US15/694,802
• Time in Patent Office: 198 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

Methods and systems are described for sharing information for detecting an idle connection. In one aspect, a second node receives a packet in a connection. A portion in the packet is detected identifying metadata for a period, detectable by a first node. The second node modifies a timeout associated with the connection based on the metadata. In another aspect, a first node receives information for detecting a period. A packet is generated including a portion identifying metadata for the period based on the information, and sent to the second node.

Claims

1. An apparatus comprising:

a non-transitory memory storing instructions; and

one or more processors in communication with the non-transitory memory, wherein the one or more processors execute the instructions for;

receiving, by a second node from a first 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, by the second node and based on the metadata, a timeout attribute associated with the TCP-variant connection.

2. The apparatus of claim 1 wherein the apparatus is configured such that the timeout attribute is an attribute of a keep-alive.

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

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

in response to the receiving, send, by the second node to the first 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 second node includes a client, the client being configured such that the receiving is performed subsequent to sending, by the second node to the first node, another TCP-variant packet in advance of the TCP-variant connection being established including other metadata for the idle time period.

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

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

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

7. The apparatus of claim 1 wherein the apparatus is configured such that the timeout attribute is used to keep the TCP-variant connection open when inactive, and to prevent one or more other nodes from closing the TCP-variant connection when inactive.

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

9. The apparatus of claim 8 wherein the apparatus is configured such that the algorithm is determined based on at least one particular attribute.

10. The apparatus of claim 1 wherein the apparatus is configured such that the modification of the timeout attribute results from a negotiation between the first node and the second node via a negotiation protocol of a TCP-variant protocol.

11. The apparatus of claim 1 wherein the one or more processors execute the instructions for:

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 first and second nodes without signaling another one of the first and second nodes that is related to the detection of the idle time period.

12. The apparatus of claim 1 wherein the apparatus is configured such that 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 apparatus of claim 1 wherein the one or more processors execute 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 first node and the second node, of the timeout attribute, where the timeout attribute is not available when establishing the TCP connection, but is available when establishing the TCP-variant connection so that the TCP-variant connection is capable of being at least partially closed when inactive based on the timeout attribute.

14. The apparatus of claim 1 wherein the apparatus is configured such that the TCP-variant packet and the metadata included therewith are received by the second node from the first node, without any prior signaling from the second node to the first node.

15. An apparatus comprising:

a non-transitory memory storing instructions; and

one or more processors in communication with the non-transitory memory, wherein the one or more processors execute the instructions for;

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 a first node to a second 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 second node, for use by the second node in modifying, based on the metadata, a timeout attribute associated with the TCP-variant connection.

16. The apparatus of claim 15 wherein the apparatus is configured such that modifying the timeout attribute reduces a number of keep-alive signals that are required to be communicated.

17. The apparatus of claim 15 wherein the apparatus is configured such that the TCP-variant packet and the metadata included therewith are sent by the first node to the second node, without any prior signaling received by the first node from the second node.

18. The apparatus of claim 15 wherein the metadata includes a first value and the timeout attribute is capable of being modified, by the second node, to include a second value that is different than the first value of the metadata.

19. The apparatus of claim 15 wherein the apparatus is configured such that the timeout attribute is specified in a number of seconds.

20. The apparatus of claim 15 wherein the apparatus is configured such that the modification of the timeout attribute results from a negotiation between the first node and the second node.

21. The apparatus of claim 15 wherein the one or more processors execute the instructions for:

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

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

22. The apparatus of claim 15 wherein the apparatus is configured such that 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.

23. The apparatus of claim 15 wherein the one or more processors execute 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 first node and the second node, of the timeout attribute, where a negotiated timeout attribute is not available when establishing the TCP connection, but is available when establishing the TCP-variant connection so that the TCP-variant connection is at least partially closed when inactive based on the negotiated timeout attribute.

24. The apparatus of claim 15 wherein the apparatus is configured such that the TCP-variant packet and the metadata included therewith are sent by the first node to the second node, in response to receiving, by the first node from the second node, another TCP-variant packet with other metadata.

25. An apparatus comprising:

a non-transitory memory storing a network application; and

one or more processors in communication with the non-transitory memory, wherein the one or more processors execute the network application such that the network application is configured to operate 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, the apparatus, when operating in accordance with the non-TCP protocol, configured to;

receive, by a second node from a first node, a non-TCP packet during a setup of a non-TCP connection;

identify 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

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

wherein the apparatus, when operating in accordance with the TCP protocol, is configured to perform a three-way TCP handshake for establishing a TCP connection that is different than the non-TCP connection.

26. The apparatus of claim 25 wherein the apparatus is configured such that:

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

the determination of the timeout attribute results from a negotiation between the first node and the second 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.

27. The apparatus of claim 25 wherein the apparatus is configured for:

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

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

28. An apparatus comprising:

a non-transitory memory storing a network application; and

one or more processors in communication with the non-transitory memory, wherein the one or more processors execute the network application such that the network application is configured to operate 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, the apparatus, when operating in accordance with the non-TCP protocol, configured to;

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

generate, 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

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

wherein the apparatus, when operating in accordance with the TCP protocol, is configured to perform a three-way TCP handshake for establishing a TCP connection that is separate from the non-TCP connection.

29. The apparatus of claim 28 wherein the apparatus is configured such that:

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

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

wherein the apparatus is further configured for;

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 TCP-variant connection by one of the first and second nodes without communication between the second node and the first node that is related to the detection of the idle time period.

30. The apparatus of claim 29 wherein at least one of:

the apparatus is at least one component of the first node;

the communication includes only receiving;

the communication includes only sending;

the communication includes receiving and sending;

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

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

the non-TCP packet is sent from the first node to the second 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;

the TCP protocol operates directly above the IP layer;

the 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 first node where the non-TCP packet including data is sent by another node;

or

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