IP Library Granted Patent US 8,831,222
Granted Patent B2
US 8,831,222 · App. 13/705,885 · Granted Sep 9, 2014

Bilateral communication using multiple one-way data links

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 8,831,222
App. No.
13/705,885
Granted
Sep 9, 2014
Kind
B2
Abstract

A bilateral data transfer system comprising a first node, a second node, a first one-way link for unidirectional transfer of first data from the first node to the second node, and a second one-way link for unidirectional transfer of second data from the second node to the first node, wherein the unidirectional transfer of the first data across the first one-way link and the unidirectional transfer of the second data across the second one-way link are independently administered by the bilateral data transfer system. Under such bilateral data transfer system, each of the one-way data links may be subject to separately administered security restrictions and data filtering processes, enabling secure bilateral communications across different network security domains.

Claims (37)

1. A bilateral data transfer system comprising:

a first one-way link for unidirectional transfer of data from an input end thereof to an output end thereof;

a second one-way link for unidirectional transfer of data from an input end thereof to an output end thereof;

a first node coupled to the input end of the first one-way link and to the output end of the second one-way link, the first node configured to transfer first data over the first one-way link, to receive second data over the second one-way link, and to prevent cross-talk within the first node between the first data to be transferred over the first one-way link and the second data received over the second one-way link; and

a second node coupled to the output end of the first one-way link and to the input end of the second one-way link, the second node configured to receive the first data from the first node over the first one-way link, to transfer the second data to the first node over the second one-way link, and to prevent cross-talk within the second node between the first data received over the first one-way link and the second data to be transferred over the second one-way link.

2. A bilateral data transfer system, comprising:

a first one-way link for unidirectional transfer of data from an input end thereof to an output end thereof;

a second one-way link for unidirectional transfer of data from an input end thereof to an output end thereof;

a first node coupled to the input end of the first one-way link and to the output end of the second one-way link, the first node configured to transfer first data over the first one-way link, to receive second data over the second one-way link, and to prevent cross-talk within the first node between the first data to be transferred over the first one-way link and the second data received over the second one-way link; and

a second node coupled to the output end of the first one-way link and to the input end of the second one-way link, the second node configured to receive the first data from the first node over the first one-way link, to transfer the second data to the first node over the second one-way link, and to prevent cross-talk within the second node between the first data received over the first one-way link and the second data to be transferred over the second one-way link;

wherein the first data comprises a request for data from a remote terminal client coupled to the first node and the second data comprises requested data from a remote terminal server coupled to the second node.

3. A bilateral data transfer system comprising:

a first one-way link for unidirectional transfer of data from an input end thereof to an output end thereof;

a second one-way link for unidirectional transfer of data from an input end thereof to an output end thereof; and

a first node coupled to the input end of the first one-way link and to the output end of the second one-way link, the first node configured to transfer first data over the first one-way link, to receive second data over the second one-way link, and to prevent cross-talk within the first node between the first data to be transferred over the first one-way link and the second data received over the second one-way link.

4. A bilateral data transfer system, comprising:

a first one-way link for unidirectional transfer of data from an input end thereof to an output end thereof;

a second one-way link for unidirectional transfer of data from an input end thereof to an output end thereof; and

a first node coupled to the input end of the first one-way link and to the output end of the second one-way link, the first node configured to transfer first data over the first one-way link, to receive second data over the second one-way link, and to prevent cross-talk within the first node between the first data to be transferred over the first one-way link and the second data received over the second one-way link;

wherein the first data comprises a request for data from a remote terminal client coupled to the first node and the second data comprises requested data from a remote terminal server coupled to the second node.

5. The bilateral data transfer system of claim 3 , further comprising:

a second node coupled to the output end of the first one-way link and to the input end of the second one-way link, the second node configured to receive the first data from the first node over the first one-way link, to transfer the second data to the first node over the second one-way link, and to prevent cross-talk within the second node between the first data received over the first one-way link and the second data to be transferred over the second one-way link.

6. A bilateral data transfer system comprising:

a first one-way link for unidirectional transfer of data from an input end thereof to an output end thereof;

a second one-way link for unidirectional transfer of data from an input end thereof to an output end thereof;

a second node coupled to the output end of the first one-way link and to the input end of the second one-way link, the second node configured to receive first data over the first one-way link, to transfer second data over the second one-way link, and to prevent cross-talk within the second node between the first data received over the first one-way link and the second data to be transferred over the second one-way link.

7. A bilateral data transfer system, comprising:

a first one-way link for unidirectional transfer of data from an input end thereof to an output end thereof;

a second one-way link for unidirectional transfer of data from an input end thereof to an output end thereof;

a second node coupled to the output end of the first one-way link and to the input end of the second one-way link, the second node configured to receive first data over the first one-way link, to transfer second data over the second one-way link, and to prevent cross-talk within the second node between the first data received over the first one-way link and the second data to be transferred over the second one-way link;

wherein the first data comprises a request for data from a remote terminal client coupled to the first node and the second data comprises requested data from a remote terminal server coupled to the second node.

8. The bilateral data transfer system of claim 6 , further comprising:

a first node coupled to the input end of the first one-way link and to the output end of the second one-way link, the first node configured to transfer the first data to the second node over the first one-way link, to receive the second data from the second node over the second one-way link, and to prevent cross-talk within the first node between the first data to be transferred over the first one-way link and the second data received over the second one-way link.

9. The bilateral data transfer system of claim 4 , further comprising:

a second node coupled to the output end of the first one-way link and to the input end of the second one-way link, the second node configured to receive the first data from the first node over the first one-way link, to transfer the second data to the first node over the second one-way link, and to prevent cross-talk within the second node between the first data received over the first one-way link and the second data to be transferred over the second one-way link.

10. The bilateral data transfer system of claim 7 , further comprising:

a first node coupled to the input end of the first one-way link and to the output end of the second one-way link, the first node configured to transfer the first data to the second node over the first one-way link, to receive the second data from the second node over the second one-way link, and to prevent cross-talk within the first node between the first data to be transferred over the first one-way link and the second data received over the second one-way link.

Assignments (8)
SECURITY INTEREST Recorded Sep 11, 2024
From: OWL CYBER DEFENSE SOLUTIONS, LLC
To: RGA REINSURANCE COMPANY
Reel/Frame 068938/0313 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS RECORDED AT REEL 041136, FRAME 0223 Recorded Sep 11, 2024
From: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
To: OWL CYBER DEFENSE SOLUTIONS, LLC
Reel/Frame 068945/0922 →
MERGER AND CHANGE OF NAME Recorded Sep 2, 2022
From: OWL CYBER DEFENSE SOLUTIONS, LLC; TRESYS TECHNOLOGY, LLC
To: OWL CYBER DEFENSE SOLUTIONS, LLC
Reel/Frame 060978/0964 →
CHANGE OF NAME Recorded Jun 20, 2017
From: OWL COMPUTING TECHNOLOGIES, LLC
To: OWL CYBER DEFENSE SOLUTIONS, LLC
Reel/Frame 042902/0582 →
CORRECTIVE ASSIGNMENT TO CORRECT TO REMOVE THIS DOCUMENT SERVES AS AN OATH/DECLARATION (37 CFR 1.63) FROM THE COVER SHEET PREVIOUSLY RECORDED AT REEL: 041765 FRAME: 0034. ASSIGNOR(S) HEREBY CONFIRMS THE MERGER EFFECTIVE DATE 02/03/2017. Recorded Apr 21, 2017
From: OWL COMPUTING TECHNOLOGIES, INC.
To: OWL COMPUTING TECHNOLOGIES, LLC
Reel/Frame 042344/0033 →
MERGER Recorded Mar 28, 2017
From: OWL COMPUTING TECHNOLOGIES, INC.
To: OWL COMPUTING TECHNOLOGIES, LLC
Reel/Frame 041765/0034 →
SECURITY INTEREST Recorded Jan 31, 2017
From: OWL COMPUTING TECHNOLOGIES, INC.
To: BANK OF AMERICA, N.A.
Reel/Frame 041136/0223 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 20, 2016
From: MENOHER, JEFFREY; HOPE, JAMES; MRAZ, RONALD
To: OWL COMPUTING TECHNOLOGIES, INC.
Reel/Frame 040689/0418 →