# US 2014/0157398 A1 · Systems and Methods for Providing a Multiple Secure Link Architecture

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2014/0157398 A1
- Document ID: US20140157398A1
- Status: Published application
- Kind: A1
- Application number: 14/174,452
- Filed: 2014-02-06
- Published: 2014-06-05
- Earliest claimed: 2012-02-06
- Assignees: Acceleration Systems, LLC
- Applicants: Acceleration Systems, LLC
- Inventors: Jack D. McKinney
- Web page: https://patentgrep.com/patent/US20140157398A1

## CPC

- H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling}
- H04L 63/0272: {Virtual private networks}
- H04L 61/2525: {Translation at a client}
- H04L 61/2592: using tunnelling or encapsulation
- H04L 12/4641: {Virtual LANs, VLANs, e.g. virtual private networks [VPN] (LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272)}
- H04L 61/2514: between local and global IP addresses
- H04L 61/5092: by self-assignment, e.g. picking addresses at random and testing if they are already in use
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Some embodiments disclosed herein include a MSL twin network address translator (NAT) that includes logic that, when executed by a processor, causes the MSL twin NAT to receive inbound datagram from MSL VPN and record a new VPN owner private IP address from a source IP address in the inbound datagram. In some embodiments the logic causes the MSL twin NAT to assign a new UPIP for the inbound datagram and client workstation and facilitate sending the inbound datagram to the client workstation.

## Claims

### Claim 1

A system for providing a multiple secure link (MSL) architecture, comprising:
a MSL virtual private network (VPN) component that includes first logic that, when executed by a processor, causes the system to perform the following:
create a VPN tunnel between a client workstation and an owner gateway;
send an outbound datagram from the client workstation to the owner gateway;
receive an inbound datagram from the owner gateway to the client workstation, wherein the inbound datagram includes a source IP address and a destination internet protocol (IP) address that is set to a VPN owner private IP address; and
send the inbound datagram with the destination IP address; and
a MSL twin network address translator (NAT) that includes second logic that, when executed by the processor, causes the system to perform at least the following:
receive the inbound datagram from MSL VPN;
record a new VPN owner private IP address from the source IP address in the inbound datagram;
assign a new UPIP for the inbound datagram and the client workstation; and
facilitate sending the inbound datagram to the client workstation.

### Claim 2 (depends on 1)

The system of claim 1, wherein the first logic further causes the system to perform the following:
encrypt the outbound datagram and transfer the outbound datagram to the owner gateway; and
receive the inbound datagram in an encrypted form from the owner gateway and decrypt the inbound datagram.

### Claim 3 (depends on 1)

The system of claim 1, wherein the second logic further causes the system to map a UPIP address in the outbound datagram to a private IP address.

### Claim 4 (depends on 1)

The system of claim 1, wherein the system is configured to simultaneously facilitate a plurality of independent VPN connections with different owner gateways.

### Claim 5 (depends on 1)

The system of claim 1, further comprising a MSL VPN user interface component that includes third logic that, when executed by the processor, causes the system to provide a user interface for establishing the VPN tunnel to the client workstation.

### Claim 6 (depends on 1)

The system of claim 1, further comprising a MSL management component that includes fourth logic that, when executed by the processor, causes the system to create the VPN tunnel.

### Claim 7 (depends on 1)

The system of claim 1, wherein the second logic further causes the system to forward the inbound datagram to a commercial off the shelf (COTS) Clear Text Process component for processing the inbound datagram.

### Claim 8 (depends on 1)

The system of claim 1, wherein the MSL twin NAT and the MSL VPN reside on the client workstation and wherein the client workstation further includes a MSL VPN user interface component and a MSL management component.

### Claim 9 (depends on 1)

The system of claim 1, further comprising an MSL server, wherein the MSL VPN and the MSL twin NAT reside on the MSL server that is remote from the client workstation, wherein the system further comprises includes an MSL VPN user interface component, a first MSL VPN component, and a first MSL management component that reside on the client workstation, and wherein the system further comprises a commercial off the shelf (COTS) clear text process component, a COTS VPN component, and a second MSL management component that reside on the MSL server.

### Claim 10 (depends on 1)

The system of claim 1, further comprising an MSL gateway router that includes the MSL VPN and the MSL twin NAT, wherein the system further comprises a first COTS VPN component, a MSL management component that reside on the client workstation, and wherein the system further comprises a second COTS VPN component and an MSL server management component that reside on the MSL gateway router.

### Claim 11 (depends on 1)

The system of claim 1, further comprising a MSL appliance and a MSL server, wherein the MSL VPN component and the MSL twin NAT reside on the MSL server, wherein the system further comprises a first COTS VPN component and a MSL VPN user interface component that reside on the client workstation, wherein the system further comprises a first MSL server management component, a second COTS VPN component, a third COTS VPN component, and a COTS clear text process client component that reside on the MSL appliance, and wherein the system further comprises a second MSL server management component, a fourth COTS VPN component, and a second COTS clear text process client that reside on the MSL server.

### Claim 12 (depends on 1)

The system of claim 1, further comprising a MSL network operations center (NOC), wherein the MSL twin NAT and the MSL VPN component reside on the NOC, wherein the system further comprises a COTS VPN client, a MSL VPN user interface component, and a MSL management component that reside on the client workstation, and wherein the system further comprises a COTS VPN component, a COTS clear text process component, a session manager component, and a login manager component that reside on the MSL NOC.

### Claim 13

A MSL virtual private network (VPN) component that includes logic that, when executed by a processor, causes the MSL VPN to perform the following:
create a VPN tunnel between a client workstation and an owner gateway;
send an outbound datagram from the client workstation to the owner gateway;
receive a inbound datagram from the owner gateway to the client workstation, wherein the inbound datagram includes a source IP address and a destination internet protocol (IP) address that is set to a VPN owner private IP address; and
send the inbound datagram with the destination IP address.

### Claim 14 (depends on 13)

The MSL VPN of claim 13, wherein the MSL VPN is configured to simultaneously facilitate a plurality of independent VPN connections with different owner gateways.

### Claim 15 (depends on 13)

The MSL VPN of claim 13, wherein the logic causes the MSL VPN to perform the following:
encrypt the outbound datagram and transfer the outbound datagram to the owner gateway; and
receive the inbound datagram in an encrypted form from the owner gateway and decrypt the inbound datagram.

### Claim 16

A MSL twin network address translator (NAT) that includes logic that, when executed by a processor, causes the MSL twin NAT to perform at least the following:
receive inbound datagram from MSL VPN;
record a new VPN owner private IP address from a source IP address in the inbound datagram;
assign a new UPIP for the inbound datagram and client workstation; and
facilitate sending the inbound datagram to the client workstation.

### Claim 17 (depends on 16)

The MSL twin NAT of claim 16, wherein the MSL VPN is configured to simultaneously facilitate a plurality of independent VPN connections with different owner gateways.

### Claim 18 (depends on 16)

The MSL twin NAT of claim 16, wherein the logic further causes the MSL twin NAT to map a UPIP address in an outbound datagram to a private IP address.

### Claim 19 (depends on 16)

The MSL twin NAT of claim 16, wherein the logic further causes the MSL twin NAT to receive a UPIP address for an owner gateway.

### Claim 20 (depends on 16)

The MSL twin NAT of claim 16, wherein the logic further causes the MSL twin NAT to forward the inbound datagram to a commercial off the shelf (COTS) Clear Text Process component for processing the inbound datagram.