IP Library Granted Patent US 11,716,395
Granted Patent B2
US 11,716,395 · App. 17/589,862 · Granted Aug 1, 2023

Minimizing connection delay for a data session

Inventors: Kevin Cunningham (Swarthmore, PA); Alexander Gizis (Philadelphia, PA); Brian Prodoehl (Plymouth Meeting, PA)
Assignee: CONNECTIFY, INC.
H04L67/145H04L63/0435H04L63/061H04L63/0807
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 11,716,395
App. No.
17/589,862
Granted
Aug 1, 2023
Kind
B2
Abstract

One example process may include identifying a paused active communication session between a client device and a server, releasing communication session resources dedicated to the communication session to a session resource pool, and re-establishing the active data session responsive to receiving a message from the client device including one or more session re-establishment parameters.

Claims (52)

1. A method comprising

identifying a paused active communication session between a client device and a server after a timeout period of inactivity;

storing session information associated with the client device and the paused active communication session in memory;

releasing communication session resources, comprising an Internet protocol (IP) address and port and memory allocated to the paused active communication session, to a session resource pool;

receiving a message from the client device comprising one or more communication session re-establishment parameters matching one or more stored communication session parameters associated with the stored session information; and

re-establishing the active communication session responsive to receiving the message, wherein the paused active communication session is re-established when the message is identified as including a session credential necessary to authenticate the client device.

2. The method of claim 1 , wherein the message is identified as including a session credential necessary to authenticate the client device, and wherein the session credential was stored in one or more of the server memory and the client device memory during the initial communication session.

3. The method of claim 2 , wherein the session credential comprises one or more of a username and password, an encryption key and an authentication token.

4. The method of claim 1 , comprising

updating a profile comprising data session parameters necessary to re-establish the active data session;

responsive to receiving the message, allocating session resources from another paused data session different from the paused data session; and

populating a container or virtual machine with the data session parameters identified from the profile.

5. The method of claim 1 , comprising

establishing a UDP session between the client device and the server; and

establishing a TCP session between the client device and the server after the UDP session is established.

6. The method of claim 1 , wherein communication session parameters include one or more of an active process, an allocated container, one or more IP addresses, and one or more ports.

7. The method of claim 1 , wherein the message comprises an encryption key that was previously used during the communication session.

8. The method of claim 1 comprising

pausing the active communication session between the client device and a server;

responsive to receiving the message from the client device, re-establishing the active data session on a new channel based on a previously known encryption key associated with the client device; and

encrypting subsequent communications based on the encryption key.

9. A server comprising

a memory configured to store instructions and a processor configured to execute the instructions to perform:

identify a paused active communication session between a client device and the server after a timeout period of inactivity;

store session information associated with the client device and the paused active communication session in memory;

release communication session resources, comprising an Internet protocol (IP) address and port and memory allocated to the paused active communication session, to a session resource pool;

receive a message from the client device comprising one or more communication session re-establishment parameters matching one or more stored communication session parameters associated with the stored session information; and

re-establish the active communication session responsive to receiving the message, wherein the paused active communication session is re-established when the message is identified as including a session credential necessary to authenticate the client device.

10. The server of claim 9 , wherein the processor is further configured to

update a profile comprising data session parameters necessary to re-establish the active data session;

responsive to the message being received, allocate session resources from another paused data session different from the paused data session; and

populate a container or virtual machine with the data session parameters identified from the profile.

11. The server of claim 9 , wherein the processor is further configured to

establish a UDP session between the client device and the server; and

establish a TCP session between the client device and the server after the UDP session is established.

12. The server of claim 9 , wherein communication session parameters include one or more of an active process, an allocated container, one or more IP addresses, and one or more ports.

13. The server of claim 9 , wherein the message comprises an encryption key that was previously used during the communication session.

14. The server of claim 9 , wherein the processor is further configured to

pause the active communication session between the client device and the server;

responsive to receiving the message from the client device, re-establish the active data session on a new channel based on a previously known encryption key associated with the client device; and

encrypt subsequent communications based on the encryption key.

15. The server of claim 9 , wherein the message is identified as including a session credential necessary to authenticate the client device, and wherein the session credential was stored in one or more of the server memory and the client device memory during the initial communication session.

16. A non-transitory computer readable storage medium configured to store instructions that when executed cause a processor to perform:

identifying a paused active communication session between a client device and a server after a timeout period of inactivity;

storing session information associated with the client device and the paused active communication session in memory;

releasing communication session resources, comprising an Internet protocol (IP) address and port and memory allocated to the paused active communication session, to a session resource pool;

receiving a message from the client device comprising one or more communication session re-establishment parameters matching one or more stored communication session parameters associated with the stored session information; and

re-establishing the active communication session responsive to receiving the message, wherein the paused active communication session is re-established when the message is identified as including a session credential necessary to authenticate the client device.

17. The non-transitory computer readable storage medium of claim 16 , wherein the processor is further configured to perform:

updating a profile comprising data session parameters necessary to re-establish the active data session;

responsive to receiving the message, allocating session resources from another paused data session different from the paused data session; and

populating a container or virtual machine with the data session parameters identified from the profile.

Assignments (2)
CHANGE OF ASSIGNEE ADDRESS Recorded Sep 21, 2025
From: CONNECTIFY, INC.
To: CONNECTIFY, INC.
Reel/Frame 072957/0512 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 31, 2022
From: CUNNINGHAM, KEVIN; GIZIS, ALEXANDER; PRODOEHL, BRIAN
To: CONNECTIFY, INC.
Reel/Frame 058837/0391 →
Continuity (2)
Provisional Application 63143427 · Jan 29, 2021
Related Publication 20220247823A1 · Aug 4, 2022
Cited By (1)
US 12,200,068