IP Library Granted Patent US 12,021,933
Granted Patent B2
US 12,021,933 · App. 17/686,966 · Granted Jun 25, 2024

Network connection status detection

Inventors: Darjus Ilcevic (Vilnius, LT); Gvidas Uzkuras (Vilnius, LT)
Assignee: Oversec, UAB
H04L67/145H04L67/141H04L63/08
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,021,933
App. No.
17/686,966
Granted
Jun 25, 2024
Kind
B2
Abstract

Virtual private network (VPN) service provider infrastructure (SPI) receives a request to access a VPN from a client device. The VPN SPI selects an Internet Protocol (IP) address for access to the VPN by the client device from a pool of IP addresses. The VPN SPI provides access to the VPN for the client device via the IP address. The VPN SPI receives one or more handshake notifications from the client device. The VPN SPI determines that a threshold time period has passed since a latest-in-time handshake notification of the one or more handshake notifications. The VPN SPI disconnects the client device from the VPN in response to determining that the threshold time period has passed. The VPN SPI adds the IP address to the pool of IP addresses in response to disconnecting the client device from the VPN.

Claims (45)

1. A method comprising:

establishing, by a network device, a connection to a client device;

transmitting, by the network device, requests for handshake notifications from the client device according to a schedule, wherein the schedule corresponds to a connected phase, wherein, upon the client device forgoing responding to the requests, the schedule switches to a connection lost phase specifying that a time difference between transmission, by the network device, of at least one pair of successive requests is an exponential function of a number of requests sent since the connection was lost;

receiving, at the network device, the handshake notifications from the client device;

determining that no handshake notification was received during at least a threshold time period;

in response to determining that no handshake notification was received during at least the threshold time period: terminating the connection to the client device.

2. The method of claim 1 , wherein the network device comprises at least one of a router, a server, or a network infrastructure device.

3. The method of claim 1 , wherein the handshake notifications comprise at least one of an echo request packet, an echo reply, a data upload, or a data download.

4. The method of claim 1 , wherein determining that no handshake notification was received during at least a threshold time period comprises:

computing a time difference between a current time and a time of a latest handshake notification; and

determining that the time difference exceed the threshold time period.

5. The method of claim 1 , wherein the connection to the client device is established in response to a request for network access from the client device.

6. The method of claim 1 , wherein terminating the connection to the client device comprises reallocating at least one network connection resource allocated to the client device to another device or to a pool of available resources.

7. The method of claim 1 , further comprising:

authenticating the client device to verify that the client device has permission to connect to the network device.

8. A network device comprising:

a non-transitory memory storing instructions; and

at least one processor that executes the instructions to:

establish a connection to a client device;

transmit requests for handshake notifications from the client device according to a schedule, wherein the schedule corresponds to a connected phase, wherein, upon the client device forgoing responding to the requests, the schedule switches to a connection lost phase specifying that a time difference between transmission, by the network device, of at least one pair of successive requests is an exponential function of a number of requests sent since the connection was lost;

receive the handshake notifications from the client device;

determine that no handshake notification was received during at least a threshold time period;

in response to determining that no handshake notification was received during at least the threshold time period: terminate the connection to the client device.

9. The network device of claim 8 , wherein the network device comprises at least one of a router, a server, or a network infrastructure device.

10. The network device of claim 8 , wherein the handshake notifications comprise at least one of an echo request packet, an echo reply, a data upload, or a data download.

11. The network device of claim 8 , wherein determining that no handshake notification was received during at least a threshold time period comprises:

computing a time difference between a current time and a time of a latest handshake notification; and

determining that the time difference exceed the threshold time period.

12. The network device of claim 8 , wherein the connection to the client device is established in response to a request for network access from the client device.

13. The network device of claim 8 , wherein terminating the connection to the client device comprises reallocating at least one network connection resource allocated to the client device to another device or to a pool of available resources.

14. The network device of claim 8 , wherein the at least one processor further executes the instructions to:

authenticate the client device to verify that the client device has permission to connect to the network device.

15. At least one non-transitory computer readable medium storing instructions that, when executed by a network device, cause the network device to perform operations comprising:

establishing, by a network device, a connection to a client device;

transmitting, by the network device, requests for handshake notifications from the client device according to a schedule, wherein the schedule corresponds to a connected phase, wherein, upon the client device forgoing responding to the requests, the schedule switches to a connection lost phase specifying that a time difference between transmission, by the network device, of at least one pair of successive requests is an exponential function of a number of requests sent since the connection was lost;

receiving, at the network device, the handshake notifications from the client device;

determining that no handshake notification was received during at least a threshold time period;

in response to determining that no handshake notification was received during at least the threshold time period: terminating the connection to the client device.

16. The at least one computer readable medium of claim 15 , wherein the network device comprises at least one of a router, a server, or a network infrastructure device.

17. The at least one computer readable medium of claim 15 , wherein the handshake notifications comprise at least one of an echo request packet, an echo reply, a data upload, or a data download.

18. The at least one computer readable medium of claim 15 , wherein determining that no handshake notification was received during at least a threshold time period comprises:

computing a time difference between a current time and a time of a latest handshake notification; and

determining that the time difference exceed the threshold time period.

19. The at least one computer readable medium of claim 15 , wherein the connection to the client device is established in response to a request for network access from the client device.

20. The at least one computer readable medium of claim 15 , wherein terminating the connection to the client device comprises reallocating at least one network connection resource allocated to the client device to another device or to a pool of available resources.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 12, 2025
From: OVERSEC, UAB
To: UAB 360 IT
Reel/Frame 070202/0565 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 4, 2022
From: ILCEVIC, DARJUS; UZKURAS, GVIDAS
To: OVERSEC, UAB
Reel/Frame 059175/0378 →
Continuity (1)
Related Publication 20230283676A1 · Sep 7, 2023