Synchronized connection closing

US10771597B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10771597-B2
Application numberUS-201616069108-A
CountryUS
Kind codeB2
Filing dateJan 11, 2016
Priority dateJan 11, 2016
Publication dateSep 8, 2020
Grant dateSep 8, 2020

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A method for a network element in a network, through which network element a communications device can communicate with the network via one or more connections, the method comprising: detecting traffic for the one or more connections from the communications device; in response to no traffic being detected on a connection for a first time period, closing each connection for which no traffic has been detected for a second time period, among the one or more connections. Corresponding network element is also provided.

First claim

Opening claim text (preview).

The invention claimed is: 1. A method performed by a network element in a network, wherein a communications device can communicate with the network via the network element, the method comprising: detecting traffic for a first connection established by the communication device; detecting traffic for a second connection established by the communication device; and in response to no traffic being detected on the first connection, the second connection, or another connection established by the communication device for a first time period, a) determining, at the end of a second time period that is subsequent to the first time period, whether or not to close the first connection and b) separately determining, at the end of the second time period, whether or not to close the second connection, wherein determining whether or not to close the first connection comprises determining whether the first connection was idle during the entire second time period, determining whether or not to close the second connection comprises determining whether the second connection was idle during the entire second time period, and the method further comprises: closing the first connection if it was determined that the first connection was idle during the entire second time period, otherwise refraining from closing the first connection; and closing the second connection if it was determined that the second connection was idle during the entire second time period, otherwise refraining from closing the second connection. 2. The method of claim 1 , wherein closing the first connection comprises sending a first close request to the communications device. 3. The method of claim 1 , further comprising: determining that the first connection was idle during the entire second time period; determining that the second connection was not idle during the entire second time period; closing the first connection as a result of determining that the first connection was idle during the entire second time period; and refraining from closing the second connection as a result of determining that the first connection was idle during the entire second time period. 4. The method of claim 1 , wherein the first and second connections are Transmission Control Protocol (TCP) connections. 5. The method of claim 2 , wherein the close request comprises a Transmission Control Protocol (TCP) FIN message. 6. The method of claim 2 , wherein the close request comprises a Transmission Control Protocol (TCP) RST message. 7. The method of claim 1 , wherein the first connection has a first keep alive interval, the second connection has a second keep alive interval the second keep alive interval is not greater than the first keep alive interval, and the second time period has the same duration as the second keep alive interval. 8. The method of claim 1 , further comprising: allowing the communications device to establish a plurality of new connections for at least part of the connection-closed applications with the communications device simultaneously after closings of connections. 9. The method of claim 1 , wherein the network element is a Transmission Control Protocol (TCP) proxy. 10. The method of claim 7 , further comprising: determining that the second keep alive interval is not greater than the first keep alive interval, and as a result of determining that the second keep alive interval is not greater than the first keep alive interval, configuring the second time period to have the same duration as the second keep alive interval. 11. A network element in a network, through which network element a communications device can communicate with the network via one or more connections, the network element comprising: a memory; and processing circuitry coupled to the memory, wherein the network element is configured to: detect traffic for a first connection established by the communication device; detect traffic for a second connection established by the communication device; and in response to no traffic being detected on the first connection, the second connection, or another connection established by the communication device for a first time period, a) determine, at the end of a second time period that is subsequent to the first time period, whether or not to close the first connection and b) separately determine, at the end of the second time period, whether or not to close the second connection, wherein the network element is configured to determine whether or not to close the first connection by performing a process that comprises determining whether the first connection was idle during the entire second time period, the network element is configured to determine whether or not to close the second connection by performing a process that comprises determining whether the second connection was idle during the entire second time period, and the network element is further configured to: close the first connection if it was determined that the first connection was idle during the entire second time period, otherwise refraining from closing the first connection; and close the second connection if it was determined that the second connection was idle during the entire second time period, otherwise refraining from closing the second connection. 12. The network element of claim 11 , wherein the network element is configured to close a connection by sending a close request to the communications device. 13. The network element of claim 11 , wherein the network element is further configured to: close the first connection as a result of determining that the first connection was idle during the entire second time period; and refrain from closing the second connection as a result of determining that the first connection was idle during the entire second time period. 14. The network element of claim 11 , wherein the first and second connections are Transmission Control Protocol (TCP) connections. 15. The network element of claim 11 , wherein the close request comprises a Transmission Control Protocol FIN message. 16. The network element of claim 11 , wherein the close request comprises a Transmission Control Protocol RST message. 17. The network element of claim 11 , wherein the first connection has a first keep alive interval, the second connection has a second keep alive interval the second keep alive interval is not greater than the first keep alive interval, and the second time period has the same duration as the second keep alive interval. 18. The network element of claim 11 , wherein the network element is further configured to allow the communications device to establish a plurality of new connections for at least part of the connection-closed applications with the communications device simultaneously after closings of connections. 19. The network element of claim 11 , wherein the network element is a Transmission Control Protocol (TCP) proxy. 20. The network element of claim 17 , wherein the network element is further configured to: determine whether the second keep alive interval is not greater than the first keep alive interval, and as a result of determining that the second keep alive interval is not greater than the first keep alive interval, configure the second time period to have the same duration as the second keep alive interval. 21. A network element in a network, through which network element a communications device can communicate with the network via one or more connections, the network element com

Assignees

Inventors

Classifications

  • H04L43/10Primary

    Active monitoring, e.g. heartbeat, ping or trace-route · CPC title

  • Termination or inactivation of sessions, e.g. event-controlled end of session · CPC title

  • avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session · CPC title

  • Maintenance of established connections · CPC title

  • H04L69/163Primary

    In-band adaptation of TCP data exchange; In-band control procedures · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10771597B2 cover?
A method for a network element in a network, through which network element a communications device can communicate with the network via one or more connections, the method comprising: detecting traffic for the one or more connections from the communications device; in response to no traffic being detected on a connection for a first time period, closing each connection for which no traffic has …
Who is the assignee on this patent?
Ericsson Telefon Ab L M
What technology area does this patent fall under?
Primary CPC classification H04L43/10. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Sep 08 2020 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).