IP Library Granted Patent US 10,938,778
Granted Patent B2
US 10,938,778 · App. 15/968,962 · Granted Mar 2, 2021

Route reply back interface for cloud internal communication

Inventors: Otto Airamo (Helsinki, FI); Ville Mattila (Helsinki, FI); Tuomo Syvänne (Helsinki, FI)
Assignee: Forcepoint LLC
H04L61/2592H04L9/14H04L61/2517H04L61/2535H04L63/0428H04L67/141H04L67/2814H04L69/161H04L67/42
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 10,938,778
App. No.
15/968,962
Granted
Mar 2, 2021
Kind
B2
Abstract

A method, system, and computer-usable medium are disclosed for responsive to a connection from a client to a server for establishing communications between the client and the server, store information regarding state of the connection and responsive to receiving a reply from the server to the client, route the reply to the client based on the information regarding the state of the connection.

Claims (35)

1. A computer-implemented method for managing network communication, comprising:

in response to a connection from a client to a server for establishing communications between the client and the server, storing information regarding state of the connection;

translating a client network address of the connection into a trans late d client network address based on identifying characteristics of a network tunnel through which the connection is established so as to distinguish the client from another client with the same client network address connecting to the server through another network tunnel;

in response to receiving a reply from the server to the client, routing the reply to the client via the translated client network address based on the information regarding the state of the connection; and

injecting protocol-independent header information into a datagram of the traffic between the client and the server, the protocol-independent header information including identifying information of the client, wherein the protocol-independent header information within the datagram is encrypted with a user-specific key.

2. The method of claim 1 , wherein the information regarding the state of the connection comprises an indication that a route reply back interface is being used for the connection and a source interface of the connection.

3. The method of claim 2 , wherein the information regarding the state of the connection includes information regarding a protocol, source address, and source port of the connection.

4. The method of claim 1 , further comprising:

storing information regarding the translated client network address as part of the information regarding state of the connection.

5. The method of claim 1 , wherein the user-specific key is defined by user-specific information within the protocol-independent header information, such that the user-specific information may be used to decrypt encrypted protocol-independent header information.

6. The method of claim 5 , wherein encrypting the protocol-independent header information with the user-specific key comprises encrypting the protocol-independent header information with a key selected from a plurality of keys associated with a user, wherein the user-specific key selected from the plurality of keys is defined by a key identifier associated with the user within the protocol-independent header information.

7. A system comprising:

a processor; and

a non-transitory, computer-readable storage medium embodying computer program code comprising instructions executable by the processor and configured for:

responsive to a connection from a client to a server for establishing communications between the client and the server, storing information regarding state of the connection;

translating a client network address of the connection into a translated client network address based on identifying characteristics of a network tunnel through which the connection is established so as to distinguish the client from another client with the same client network address connecting to the server through another network tunnel;

responsive to receiving a reply from the server to the client, routing the reply to the client via the translated client network address based on the information regarding the state of the connection; and

injecting protocol-independent header information into a datagram of the traffic between the client and the server, the protocol-independent header information including identifying information of the client, wherein the protocol-independent header information within the datagram is encrypted with a user-specific key.

8. The system of claim 7 , wherein the information regarding the state of the connection comprises an indication that a route reply back interface is being used for the connection and a source interface of the connection.

9. The system of claim 8 , wherein the information regarding the state of the connection includes information regarding a protocol, source address, and source port of the connection.

10. The system of claim 7 , the instructions for further:

storing information regarding the translated client network address as part of the information regarding state of the connection.

11. The system of claim 7 , wherein the user-specific key is defined by user-specific information within the protocol-independent header information, such that the user-specific information may be used to decrypt encrypted protocol-independent header information.

12. The system of claim 11 , wherein encrypting the protocol-independent header information with the user-specific key comprises encrypting the protocol-independent header information with a key selected from a plurality of keys associated with a user, wherein the user-specific key selected from the plurality of keys is defined by a key identifier associated with the user within the protocol-independent header information.

13. A non-transitory, computer-readable storage medium embodying computer program code, the computer program code comprising computer executable instructions configured for:

responsive to a connection from a client to a server for establishing communications between the client and the server, storing information regarding state of the connection;

translating a client network address of the connection into a trans late d client network address based on identifying characteristics of a network tunnel through which the connection is established so as to distinguish the client from another client with the same client network address connecting to the server through another network tunnel;

responsive to receiving a reply from the server to the client, routing the reply to the client via the translated client network address based on the information regarding the state of the connection; and

injecting protocol-independent header information into a datagram of the traffic between the client and the server, the protocol-independent header information including identifying information of the client, wherein the protocol-independent header information within the datagram is encrypted with a user-specific key.

14. The computer-readable storage medium of claim 13 , wherein the information regarding the state of the connection comprises an indication that a route reply back interface is being used for the connection and a source interface of the connection.

15. The computer-readable storage medium of claim 14 , wherein the information regarding the state of the connection includes information regarding a protocol, source address, and source port of the connection.

16. The computer-readable storage medium of claim 13 , the instructions for further:

storing information regarding the translated client network address as part of the information regarding state of the connection.

17. The computer-readable storage medium of claim 13 , wherein the user-specific key is defined by user-specific information within the protocol-independent header information, such that the user-specific information may be used to decrypt encrypted protocol-independent header information.

18. The computer-readable storage medium of claim 17 , wherein encrypting the protocol-independent header information with the user-specific key comprises encrypting the protocol-independent header information with a key selected from a plurality of keys associated with a user, wherein the user-specific key selected from the plurality of keys is defined by a key identifier associated with the user within the protocol-independent header information.

Assignments (10)
RELEASE OF SECURITY INTEREST Recorded Apr 2, 2025
From: UBS AG, STAMFORD BRANCH
To: FORCEPOINT, LLC; BITGLASS, LLC
Reel/Frame 070706/0263 →
SECURITY INTEREST Recorded Apr 1, 2025
From: FORCEPOINT LLC; BITGLASS, LLC
To: SOCIÉTÉ GÉNÉRALE
Reel/Frame 070703/0887 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 19, 2021
From: FORCEPOINT FEDERAL HOLDINGS LLC
To: FORCEPOINT LLC
Reel/Frame 057001/0057 →
CHANGE OF NAME Recorded May 12, 2021
From: FORCEPOINT LLC
To: FORCEPOINT FEDERAL HOLDINGS LLC
Reel/Frame 056214/0798 →
PATENT SECURITY AGREEMENT Recorded Jan 20, 2021
From: REDOWL ANALYTICS, INC.; FORCEPOINT LLC
To: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT
Reel/Frame 055052/0302 →
RELEASE OF SECURITY INTEREST IN PATENTS Recorded Jan 8, 2021
From: RAYTHEON COMPANY
To: FORCEPOINT LLC
Reel/Frame 055479/0676 →
RELEASE OF SECURITY INTEREST IN PATENTS Recorded Jan 8, 2021
From: RAYTHEON COMPANY
To: FORCEPOINT LLC
Reel/Frame 055492/0266 →
PATENT SECURITY AGREEMENT SUPPLEMENT Recorded Mar 15, 2019
From: FORCEPOINT LLC
To: RAYTHEON COMPANY
Reel/Frame 048613/0636 →
PATENT SECURITY AGREEMENT SUPPLEMENT Recorded Jul 6, 2018
From: FORCEPOINT LLC
To: RAYTHEON COMPANY
Reel/Frame 046495/0561 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 2, 2018
From: AIRAMO, OTTO; MATTILA, VILLE; SYVÄNNE, TUOMO
To: FORCEPOINT LLC
Reel/Frame 045693/0024 →