One-way bus bridge

• US 9,237,126 B2
• Filed: 09/09/2011
• Issued: 01/12/2016
• Est. Priority Date: 09/09/2010
• Status: Active Grant

• Current Assignee: Gerald R. Mcevoy
• Original Assignee: Gerald R. Mcevoy
• Inventors: McEvoy, Gerald R.
• Primary Examiner(s): MISIURA, BRIAN THOMAS
• Application Number:
  US13/229,640
• Publication Number:
  US 20120179852A1
• Time in Patent Office: 1,586 Days
• Field of Search: 710306-316, 370/230, 726/3, 726/4, 726/26, 709/217, 709/220, 709/223, 709/230
• US Class Current: 1/1
• CPC Class Codes: G06F 13/1673 using buffers
• CPC Class Codes: G06F 13/4027 using bus bridges G06F13/4022 takes precedence
• CPC Class Codes: G06F 13/405 where the bridge performs a synchronising function
• CPC Class Codes: G06F 13/4286 using a handshaking protocol, e.g. RS232C link
• CPC Class Codes: H04L 63/0209 Architectural arrangements, e.g. perimeter networks or demilitarized zones
• CPC Class Codes: H04L 63/0227 Filtering policies mail message filtering H04L51/212

Abstract

A one-way bus bridge pair that transfers secure data in one direction, the bus bridge pair including a transmitting bus bridge, a receiving bus bridge, and a link. The link can connect the transmitting bus bridge and receiving bus bridge. The transmitting bus bridge may be arranged not to receive any data from the receiving bus bridge, and the receiving bus bridge may be arranged not to send any data to the transmitting bus bridge.

Claims

1. A one-way bus bridge pair that transfers data securely in a single direction at bus level utilizing bus architecture, the bus bridge pair comprising:

a transmitting bus bridge;

a receiving bus bridge;

a transfer medium connecting the transmitting bus bridge and the receiving bus bridge,

wherein the receiving bus bridge is arranged in one-way communication with the transmitting bus bridge using bus layer protocol to extend the transmitting bus bridge to the receiving bus bridge across the transfer medium without using network layer protocol, and

wherein the transmitting bus bridge is devoid of physical capabilities to accept any data from the receiving bus bridge, and the receiving bus bridge is devoid of physical capabilities to send any data to the transmitting bus bridge,

wherein;

the transmitting bus bridge includes a transmitter, wherein the transmitter is connected to a first bus via a first interface; and

the receiving bus bridge includes a receiver, wherein the receiver is connected to a second bus via a second interface allowing the one-way extension of the transmitting bus bridge to the receiving bus bridge,

wherein;

the transmitter;

accepts an input data from the first bus of a first computing device; and

delivers the input data to the receiver via the one-way communication over the transfer medium utilizing the bus architecture and the bus layer protocol and without using the network layer protocol; and

the receiver;

obtains the input data from the first bus via the one-way communication over the transfer medium; and

supplies the input data to the second bus of a second computing device, and

wherein the transmitter of the transmitting bus bridge uses a program direct interprocess communication using shared memory between the first computing device and the second computing device.

2. The one-way bus bridge pair of claim 1, wherein the input data comprises at least a command from a device driver.

3. The one-way bus bridge pair of claim 1, wherein the first interface comprises a Peripheral Component Interconnect (PCI) interface.

4. The one-way bus bridge pair of claim 1, wherein the second interface comprises a PCI interface.

5. The one-way bus bridge pair of claim 1, wherein the first interface comprises a Peripheral Component Interconnect Express (PCIe) interface.

6. The one-way bus bridge pair of claim 1, wherein the second interface comprises a PCIe interface.

7. The one-way bus bridge pair of claim 1, wherein the first interface comprises a mini-Peripheral Component Interconnect Express (PCIe) interface.

8. The one-way bus bridge pair of claim 1, wherein the second interface comprises a mini-PCIe interface.

9. The one-way bus bridge pair of claim 1, wherein the first interface comprises an InfiniBand interface.

10. The one-way bus bridge pair of claim 1, wherein the second interface comprises an InfiniBand interface.

11. The one-way bus bridge pair of claim 1, wherein the receiving bus bridge further comprises at least one buffer;

and

wherein the buffer is used to store the input data.

12. The one-way bus bridge pair of claim 11, wherein the buffer connects the receiver and the second interface.

13. The one-way bus bridge pair of claim 1, wherein the transmitter is directly connected to the first interface.

14. The one-way bus bridge pair of claim 1, wherein the first bus is directly connected to the first interface.

15. The one-way bus bridge pair of claim 1, wherein the receiver is directly connected to the second interface.

16. The one-way bus bridge pair of claim 1, wherein the second bus is directly connected to the second interface.

17. The one-way bus bridge pair of claim 1,

wherein the transfer medium includes a single direction fiber optic connection connecting the transmitting bus bridge to the receiving bus bridge for the one-way communication utilizing the bus architecture and the bus layer protocol and without using the network layer protocol.

18. The one-way bus bridge pair of claim 1,

wherein the transfer medium includes a single direction copper cable connection connecting the transmitting bus bridge to the receiving bus bridge for the one-way communication utilizing the bus architecture and the bus layer protocol and without using the network layer protocol.

19. The one-way bus bridge pair of claim 1,

wherein the transfer medium includes a single direction wireless connection connecting the transmitting bus bridge to the receiving bus bridge for the one-way communication utilizing the bus architecture and the bus layer protocol and without using the network layer protocol.

20. The one-way bus bridge pair of claim 2, wherein the device driver supports a UNIX-based operating system.

21. The one-way bus bridge pair of claim 2, wherein the device driver supports a Linux-based operating system.

22. The one-way bus bridge pair of claim 2, wherein the device driver supports a Microsoft Windows-based operating system.

23. The one-way bus bridge pair of claim 2, wherein the device driver supports an Apple-based operating system.

24. The one-way bus bridge pair of claim 1, wherein the secure data comprises Personally Identifiable Information (PII).

25. The one-way bus bridge pair of claim 1, wherein the secure data comprises Secure Disk Replication.

26. The one-way bus bridge pair of claim 1, wherein the secure data comprises Secure Database Backup.

27. The one-way bus bridge pair of claim 1, wherein the secure data comprises continuance of operation (COOP) data.

28. The one-way bus bridge pair of claim 1, wherein the secure data comprises Secure Network Access.

29. The one-way bus bridge pair of claim 1, wherein the transmitter includes a controlling device, wherein the controlling device controls the one-way communication between the transmitting bus bridge and the receiving bus bridge utilizing the bus architecture and the bus layer protocol and without using the network layer protocol.

30. The one-way bus bridge pair of claim 1, wherein the receiver includes a controlling device, wherein the controlling device controls the one-way communication between the transmitting bus bridge and the receiving bus bridge utilizing the bus architecture and the bus layer protocol and without using the network layer protocol.

31. The one-way bus bridge pair of claim 29, wherein the controlling device includes a logic device.

32. The one-way bus bridge pair of claim 30, wherein the controlling device includes a logic device.

33. The one-way bus bridge pair of claim 31, wherein the logic device includes a field programmable gate array (FPGA).

34. The one-way bus bridge pair of claim 32, wherein the logic device includes a field programmable gate array (FPGA).

59. The one-way bus bridge pair of claim 1, wherein the transmitter of the transmitting bus bridge uses one-way native format communication to the second computing device.

35. A one-way bus bridge pair that transfers data securely in a single direction at bus level utilizing bus architecture, the bus bridge pair comprising:

a transmitting bus bridge;

a receiving bus bridge; and

a transfer medium connecting the transmitting bus bridge and the receiving bus bridge,

wherein the receiving bus bridge is arranged in one-way communication with the transmitting bus bridge using bus layer protocol to extend the transmitting bus bridge to the receiving bus bridge across the transfer medium without using network layer protocol, and

wherein the transmitting bus bridge is devoid of physical capabilities to accept any data from the receiving bus bridge, and the receiving bus bridge is devoid of physical capabilities to send any data to the transmitting bus bridge,

wherein;

the transmitting bus bridge includes a transmitter, wherein the transmitter is connected to a first bus via a first interface; and

the receiving bus bridge includes a receiver, wherein the receiver is connected to a second bus via a second interface allowing the one-way extension of the transmitting bus bridge to the receiving bus bridge,

wherein;

the transmitter;

accepts an input data from the first bus of a first computing device; and

delivers the input data to the receiver via the one-way communication over the transfer medium utilizing the bus architecture and the bus layer protocol and without using the network layer protocol; and

the receiver;

obtains the input data from the first bus via the one-way communication over the transfer medium; and

supplies the input data to the second bus of a second computing device,

wherein the input data comprises at least a command from a device driver, and

wherein the device driver includes at least a pseudo-device.

36. The one-way bus bridge pair of claim 35, wherein the pseudo-device includes at least a disk drive.

37. The one-way bus bridge pair of claim 35, wherein the pseudo-device includes at least a memory device.

38. The one-way bus bridge pair of claim 35, wherein the pseudo-device includes at least an audio device.

39. The one-way bus bridge pair of claim 35, wherein the pseudo-device includes at least a video device.

40. The one-way bus bridge pair of claim 35, wherein the pseudo-device includes at least a network device.

41. The one-way bus bridge pair of claim 35, wherein the pseudo-device includes at least a memory mapping device.

61. The one-way bus bridge pair of claim 35, further comprising:

a second transfer medium connecting the transmitting bus bridge and the receiving bus bridge,

wherein the receiving bus bridge is arranged to have a second, direct one-way communication with the transmitting bus bridge using the bus layer protocol to extend the receiving bus bridge to the transmitting bus bridge across the second transfer medium without using network layer protocol, and

wherein the receiving bus bridge is physically prohibited from accepting any data from the transmitting bus bridge via the second, direct one-way communication, and the transmitting bus bridge is physically prohibited from sending any data via the second, direct one-way communication to the receiving bus bridge.

42. A one-way bus bridge pair that transfers secure data in a single direction at bus level utilizing bus architecture, the bus bridge pair comprising:

a transmitting bus bridge;

a receiving bus bridge;

a transfer medium connecting the transmitting bus bridge and the receiving bus bridge,

wherein the receiving bus bridge is arranged in direct one-way communication with the transmitting bus bridge using bus layer protocol to extend the transmitting bus bridge to the receiving bus bridge across the transfer medium without using network layer protocol, and

wherein the transmitting bus bridge is physically prohibited from accepting any data from the receiving bus bridge, and the receiving bus bridge is physically prohibited from sending any data to the transmitting bus bridge; and

a second transfer medium connecting the transmitting bus bridge and the receiving bus bridge,

wherein the receiving bus bridge is arranged to have a second, direct one-way communication with the transmitting bus bridge using the bus layer protocol to extend the receiving bus bridge to the transmitting bus bridge across the second transfer medium without using network layer protocol, and

wherein the receiving bus bridge is physically prohibited from accepting any data from the transmitting bus bridge via the second, direct one-way communication, and the transmitting bus bridge is physically prohibited from sending any data via the second, direct one-way communication to the receiving bus bridge.

43. The one-way bus bridge pair of claim 42, wherein:

the transmitting bus bridge includes a transmitter, wherein the transmitter is connected to a first bus via a first interface; and

the receiving bus bridge includes a receiver, wherein the receiver is connected to a second bus via a second interface allowing the one-way extension of the transmitting bus bridge to the receiving bus bridge.

44. The one-way bus bridge pair of claim 42, wherein:

the transmitter;

accepts an input data from the first bus of a first computing device; and

delivers the input data to the receiver via the direct one-way communication utilizing the bus architecture and the bus layer protocol and without using the network layer protocol; and

the receiver;

accepts the input data from the first bus via the direct one-way communication utilizing the bus architecture and the bus layer protocol and without using the network layer protocol; and

delivers the input data to the second bus of a second computing device.

45. The one-way bus bridge pair of claim 44, wherein the input data comprises at least a command from a device driver.

46. The one-way bus bridge pair of claim 42, wherein the second, direct one-way communication carries at least an acknowledgement data type.

47. The one-way bus bridge pair of claim 42, wherein the second, direct one-way communication is controlled by at least a controlling device.

48. The one-way bus bridge pair of claim 47, wherein the controlling device includes at least a logic device.

49. The one-way bus bridge pair of claim 42, wherein the second, direct one-way communication at the bus level carries at least an error code data type.

50. The one-way bus bridge pair of claim 46, wherein the acknowledgement data type causes a retransmission of data across the direct one-way communication utilizing the bus architecture and the bus layer protocol and without using the network layer protocol.

51. The one-way bus bridge pair of claim 46, wherein the acknowledgement data type includes at least a single byte of data.

52. The one-way bus bridge pair of claim 49, wherein the error code data type causes a retransmission of data across the direct one-way communication utilizing the bus architecture and the bus layer protocol and without using the network layer protocol.

53. The one-way bus bridge pair of claim 49, wherein the error code data type includes at least a single byte of data.

62. The one-way bus bridge pair of claim 42, wherein the transmitter of the transmitting bus bridge uses a program direct interprocess communication using shared memory between the first computing device and the second computing device.

54. A secure one-way bus bridge system for one-way bus level communication utilizing bus architecture and bus layer protocol, the system comprising:

a transmitting bus bridge;

a receiving bus bridge;

a transfer medium connecting the transmitting bus bridge and the receiving bus bridge,

wherein the receiving bus bridge is arranged in one-way communication with the transmitting bus bridge using the bus layer protocol to extend the transmitting bus bridge to the receiving bus bridge across the transfer medium without using the network layer protocol, and

wherein the transmitting bus bridge is physically arranged not to accept any data from the receiving bus bridge, and the receiving bus bridge is physically arranged not to send any data to the transmitting bus bridge; and

a second transfer medium connecting the transmitting bus bridge and the receiving bus bridge,

wherein the receiving bus bridge is arranged to have a second, direct one-way communication with the transmitting bus bridge using the bus layer protocol to extend the receiving bus bridge to the transmitting bus bridge across the second transfer medium without using network layer protocol, and

wherein the receiving bus bridge is physically prohibited from accepting any data from the transmitting bus bridge via the second, direct one-way communication, and the transmitting bus bridge is physically prohibited from sending any data via the second, direct one-way communication to the receiving bus bridge.

55. The one-way bus bridge system of claim 54, wherein:

the transmitting bus bridge includes a transmitter, wherein the transmitter is connected to a first bus via a first interface; and

the receiving bus bridge includes a receiver, wherein the receiver is connected to a second bus via a second interface allowing the one-way extension of the transmitting bus bridge to the receiving bus bridge.

56. The one-way bus bridge system of claim 55, wherein:

the transmitter;

accepts an input data from the first bus of a first part of a computing device; and

delivers the input data to the receiver; and

the receiver;

obtains the input data from the first bus; and

supplies the input data to the second bus of a second part of the computing device.

63. The one-way bus bridge pair of claim 54, wherein the transmitter of the transmitting bus bridge uses a program direct interprocess communication using shared memory between the first computing device and the second computing device.

57. A method of securely transporting data in native format one-way across two or more computing systems at bus level utilizing bus architecture and bus layer protocol, comprising:

providing a transmitting bus bridge;

providing a receiving bus bridge; and

providing a transfer medium connecting the transmitting bus bridge and the receiving bus bridge;

arranging the receiving bus bridge in one-way communication with the transmitting bus bridge using the bus layer protocol to extend the transmitting bus bridge to the receiving bus bridge across the transfer medium without using the network layer protocol;

physically arranging the transmitting bus bridge not to accept any data from the receiving data to the transmitting bus bridge,

wherein the transmitting bus bridge includes a transmitter, and the receiving bus bridge includes a receiver,

connecting the transmitter to a first bus via a first interface;

connecting the receiver to a second bus via a second interface;

receiving an input data from the first bus of a first part of a computing device;

sending the input data to the receiver;

receiving the input data from the first bus; and

sending the input data to the second bus of a second part of the computing device.

58. The method of claim 57, further comprising:

receiving an input data from the first bus of a first computing device;

sending the input data to the receiver;

receiving the input data from the first bus; and

sending the input data to the second bus of a second computing device.

60. A one-way bus bridge pair that transfers data securely in a single direction utilizing bus architecture, the bus bridge pair comprising:

a transmitting bus bridge including a transmitter that is connected to a first bus of a first computing device via a first interface;

a receiving bus bridge including a receiver that is connected to a second bus of a second computing device via a second interface allowing one-way extension of the transmitting bus bridge to the receiving bus bridge; and

a transfer medium connecting the transmitter of the transmitting bus bridge and the receiver of the receiving bus bridge,

wherein the receiver is arranged in one-way communication with the transmitter using bus layer protocol to extend the first bus to the second bus across the transfer medium without using network layer protocol,

wherein the transmitter is devoid of physical capabilities to accept any data from the receiver, and the receiver is devoid of physical capabilities to send any data to the transmitter,

wherein the transmitter includes a first controller programmed to control the transmission of data to the receiver, wherein the first controller is programmed to accept an input data from the first bus and deliver the input date to the receiver via the one-way communication over the transfer medium utilizing the bus architecture and the bus layer protocol and without using the network layer protocol,

wherein the receiver includes a second controller programmed to control the receiver to receive the data from the transmitter, wherein the second controller is programmed to obtain the input data from the first bus via the one-way communication over the transfer medium and supply the input data to the second bus utilizing the bus architecture and the bus layer protocol and without using the network layer protocol, and

wherein the transmitter of the transmitting bus bridge uses a program direct interprocess communication using shared memory between the first computing device and the second computing device.