IP Library Granted Patent US 8,139,581
Granted Patent B1
US 8,139,581 · App. 11/788,157 · Granted Mar 20, 2012

Concurrent data transfer involving two or more transport layer protocols over a single one-way data link

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,139,581
App. No.
11/788,157
Granted
Mar 20, 2012
Kind
B1
Abstract

A data transfer application for concurrent transfer of data streams based on two or more transport layer protocols via a single one-way data link. The present invention provides a great degree of routing flexibility by providing seamless network connectivity under a plurality of transport layer protocols, such as TCP and UDP, between multiple source and destination platforms over a single one-way data link.

Claims (63)

1. An apparatus for transferring data across a single one-way link, comprising:

a data transmitter capable of receiving data streams based on two or more different types of transport layer protocols from source platforms and transferring the data streams across the one-way link concurrently; and

a data receiver for receiving the data streams from the one-way link and forwarding the data streams to destination platforms,

wherein:

the data transmitter is configured to assign a channel number to each of the data streams based on IP information of the corresponding source platform and port information of the data transmitter and replace the IP information of the corresponding source platform with the channel number, and

the data receiver is configured to map the channel numbers to IP information of the destination platforms and port information of the data receiver,

wherein the IP information of the destination platforms remain undisclosed at the source platforms and no IP information is sent across the one-way link.

2. The apparatus of claim 1 , wherein each of the data transmitter and the data receiver hosts sockets corresponding to the two or more different types of transport layer protocols to receive the data streams.

3. The apparatus of claim 2 , wherein the sockets comprise one or more UDP ports and one or more TCP ports.

4. The apparatus of claim 2 , wherein the sockets for the data transmitter comprise:

one or more TCP ports;

a first UDP socket;

two or more UDP ports open to receive UDP datagram streams from two or more UDP sources; and

a multiplexer for routing the UDP datagram streams concurrently to the first UDP socket.

5. The apparatus of claim 4 , wherein the sockets for the data receiver comprise:

one or more TCP ports;

a second UDP socket; and

a demultiplexer for routing the UDP datagram streams concurrently to their intended destinations.

6. The apparatus of claim 1 , wherein the data transmitter is configured to remove IP information associated with the data streams.

7. The apparatus of claim 1 , wherein the two or more different types of transport layer protocols comprise UDP and TCP.

8. The apparatus of claim 1 , wherein the data transmitter is configured to assign a different priority on each of the data streams for transfer through the one-way link to satisfy a desired level of quality of service.

9. The apparatus of claim 1 , wherein the data transmitter is configured to assign a different priority on each of the two or more different types of transport layer protocols for transfer through the one-way link to satisfy a desired level of quality of service.

10. A one-way data transfer system, comprising

two or more source platforms;

two or more destination platforms;

a one-way link for unidirectional transfer;

a data transmitter capable of receiving data streams based on two or more different types of transport layer protocols from the two or more source platforms and transferring the data streams across the one-way link concurrently; and

a data receiver for receiving the data streams from the one-way link and forwarding the data streams to the two or more destination platforms,

wherein: the data transmitter is configured to assign a channel number to each of the data streams based on IP information of the corresponding source platform and port information of the data transmitter and replace the IP information of the corresponding source platform with the channel number, and

the data receiver is configured to map the channel numbers to IP information of the destination platforms and port information of the data receiver,

wherein the IP information of the destination platforms remain undisclosed at the source platforms and no IP information is sent across the one-way link.

11. The one-way data transfer system of claim 10 , wherein each of the data transmitter and the data receiver hosts sockets corresponding to the two or more different types of transport layer protocols to receive the data streams.

12. The one-way data transfer system of claim 11 , wherein the sockets comprise one or more UDP ports and one or more TCP ports.

13. The one-way data transfer system of claim 11 , wherein the sockets for the data transmitter comprise:

one or more TCP ports;

a first UDP socket;

two or more UDP ports open to receive UDP datagram streams from the two or more source platforms; and

a multiplexer for routing the UDP datagram streams concurrently to the first UDP socket.

14. The one-way data transfer system of claim 13 , wherein the sockets for the data receiving application comprise:

one or more TCP ports;

a second UDP socket; and

a demultiplexer for routing the UDP datagram streams concurrently to the two or more destination platforms.

15. The one-way data transfer system of claim 10 , wherein the data transmitter is configured to remove IP information associated with the data streams.

16. The one-way data transfer system of claim 10 , wherein the two or more different types of transport layer protocols comprise UDP and TCP.

17. The one-way data transfer system of claim 10 , wherein the data transmitter is configured to assign a different priority on each of the data streams for transfer through the one-way link to satisfy a desired level of quality of service.

18. The one-way data transfer system of claim 10 , wherein the data transmitter is configured to assign a different priority on each of the two or more different types of transport layer protocols for transfer through the one-way link to satisfy a desired level of quality of service.

19. A non-transitory machine readable medium having instructions stored on a send node and a receive node interconnected by a single one-way link for unidirectional transfer from the send node to the receive node, the instructions, when executed by the send node, causing the send node to:

maintain two or more open sockets to receive data streams based on two or more different types of transport layer protocols from source platforms;

receive the data streams;

assign a channel number to each of the data streams based on IP information of the corresponding source platform and port information of the send node;

replace the IP information of the corresponding source platform with the channel number; and

transfer the data streams concurrently across the one-way link, and the instructions, when executed by the receive node, causing the receive node to:

map the channel numbers to IP information of destination platforms and port information of the receive node; and

forward each of the data streams received from the send node to the corresponding destination platform in accordance with the mapping,

wherein the IP information of the destination platforms remain undisclosed at the source platforms and no IP information is sent across the one-way link.

20. The non-transitory machine readable medium of claim 19 , wherein the two or more different types of transport layer protocols comprise UDP and TCP.

21. The non-transitory machine readable medium of claim 19 , wherein the two or more open sockets comprise one or more UDP ports and one or more TCP ports.

22. The non-transitory machine readable medium of claim 21 , wherein the instructions, when executed by the send node, cause the send node to route the data streams received by the one or more UDP ports into a single UDP socket.

23. The non-transitory machine readable medium of claim 22 , wherein the instructions, when executed by the receive node, cause the receive node to demultiplex the data streams received from the send node.

24. The non-transitory machine readable medium of claim 23 , wherein the step to map the channel numbers comprises the step to read a demultiplexing configuration file to determine a downstream routing configuration for the received data streams.

25. The non-transitory machine readable medium of claim 19 , wherein the instructions, when executed by the send node, cause the send node to remove IP information from the data streams prior to transferring the data streams concurrently across the one-way link.

26. The non-transitory machine readable medium of claim 19 , wherein the step to transfer the data streams by the send node comprises the steps to assign a different priority on each of the data streams to satisfy a desired level of quality of service, and to transfer the data streams across the one-way link based on the different priorities.

27. The non-transitory machine readable medium of claim 19 , wherein the step to transfer the data streams by the send node comprises the steps to assign a different priority on each of the two or more different types of transport layer protocols to satisfy a desired level of quality of service, and to transfer the data streams across the one-way link based on the different priorities.

Assignments (8)
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 →
SECURITY INTEREST Recorded Sep 11, 2024
From: OWL CYBER DEFENSE SOLUTIONS, LLC
To: RGA REINSURANCE COMPANY
Reel/Frame 068938/0313 →
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 Jul 3, 2007
From: MRAZ, RONALD; HOPE, JAMES
To: OWL COMPUTING TECHNOLOGIES, INC.
Reel/Frame 019537/0389 →