# US 2019/0245931 A1 · System and method of providing secure data transfer > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2019/0245931 A1 - Document ID: US20190245931A1 - Status: Published application - Kind: A1 - Application number: 16/384,371 - Filed: 2019-04-15 - Published: 2019-08-08 - Earliest claimed: 2016-10-24 - Assignees: Signiant Inc. - Applicants: Signiant Inc. - Inventors: Ian Kennedy HAMILTON; Anthony VASILE - Web page: https://patentgrep.com/patent/US20190245931A1 ## CPC - H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70) - H04L 12/2856: {Access arrangements, e.g. Internet access (asynchronous transfer mode networks H04L12/5601; broadband local area networks H04L12/2801; optical access or distribution networks H04Q11/0067; access to open networks H04L12/5691; digital subscriber line end-user equipment and bit-level processing of data on a PSTN-based network H04M11/00; home network gateways H04L12/2834; wireless access networks H04W)} - H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling} - H04L 45/64: using an overlay routing layer - H04L 47/125: by balancing the load, e.g. traffic engineering - H04L 61/4511: using domain name system [DNS] - H04L 63/029: {Firewall traversal, e.g. tunnelling or, creating pinholes} - H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload} - H04L 63/166: {at the transport layer} - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP] - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - H04L 69/326: in the transport layer [OSI layer 4] (H04L69/16 takes precedence) - H04L 61/2592: using tunnelling or encapsulation - H04L 63/0272: {Virtual private networks} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A system and method is provided for providing secure accelerated data transfer. The system may transparently provide accelerated data transfer between a client and a remote system. The system may provide a method for determining a mapped domain name for identifying an ingress server. The system may provide a method for determining a tunnel route to an egress server selected for establishing a connection with the remote system. The system may provide a method of exchanging data between the client system and the remote system via the ingress server and the egress server. ## Claims ### Claim 1 A computer implemented method of facilitating data transfers between a client system and a remote system, wherein a domain name of the remote system is mapped to a mapped domain name via a mapping service, wherein requests to the mapped domain name are directed to an ingress system for establishing a connection with the remote system, the method being implemented in a cloud-based computer system comprising the ingress system and an egress system, the method comprising: receiving, by the ingress system, a request to establish communication with the remote system, wherein the request is directed from the mapped domain name; establishing, by the ingress system, a first data transfer connection with the client system; transmitting, by the ingress system to a tunnel routing service, a request to identify an egress system from among multiple egress systems for communicating with the remote system; receiving, by the ingress system from the tunnel routing service, an address of the egress system selected from among the multiple egress systems; establishing, by the ingress system, a data tunnel comprising a second data transfer connection with the egress system based on the address of the egress system received from the tunnel routing service; establishing, by the egress system, a third data transfer connection between the remote system and the egress system; and facilitating, by the ingress system and the egress system, data exchange between the client system and the remote system via the first data transfer connection, the data tunnel, and the third data transfer connection. ### Claim 2 (depends on 1) The computer implemented method of claim 1, wherein establishing the first data transfer connection includes establishing a cryptographically secure transport layer security data connection. ### Claim 3 (depends on 1) The computer implemented method of claim 1, the method further comprising: establishing a transport layer security data connection between the ingress system and the remote system across the second data transfer connection and the third data transfer connection. ### Claim 4 (depends on 1) The computer implemented method of claim 1, wherein selecting the egress system to correspond to the mapped domain name includes selecting the egress system based on at least one of data transfer rates, overall data throughput, and latency times. ### Claim 5 (depends on 1) The computer implemented method of claim 1, wherein the cloud-based computer system is further programmed with instructions that implement a second ingress system and a second egress system, the method further comprising: establishing, by the second ingress system and the second egress system, a second data tunnel between the client system and the remote system via the second ingress system and the second egress system. ### Claim 6 (depends on 1) The computer implemented method of claim 1, the method further comprising: establishing, by the ingress system, one or more fourth data transfer connections between the egress system and the ingress system in response to an increased traffic load. ### Claim 7 (depends on 1) The computer implemented method of claim 1, the method further comprising: determining the mapped domain name corresponding to the ingress system and the client system, based on at least one of data transfer rates, overall data throughput, and latency times between the client system and the ingress system. ### Claim 8 (depends on 1) The method of claim 1, wherein obtaining the destination domain name corresponding to the remote system comprises: obtaining, by the ingress system, the destination domain name from a predefined mapping of the destination domain name to a mapped domain name that corresponds to the destination domain name. ### Claim 9 (depends on 1) The method of claim 1, wherein facilitating the data exchange between the client system and the remote system comprises: receiving, by the ingress system, one or more data packets from the client system via the first data transfer connection; and transmitting, by the ingress system, the one or more data packets to the egress system via the data tunnel. ### Claim 10 (depends on 9) The method of claim 9, wherein receiving the one or more data packets from the client system comprises: receiving, by the ingress system, the one or more data packets from the client system via a hypertext transfer protocol. ### Claim 11 (depends on 9) The method of claim 9, wherein facilitating the data exchange between the client system and the remote system comprises: receiving, by the egress system, one or more second data packets from the remote system via the third data transfer connection; and transmitting, by the ingress system, the one or more second data packets to the ingress system via the data tunnel. ### Claim 12 (depends on 11) The method of claim 11, wherein receiving the one or more second data packets from the remote system comprises: receiving, by the egress system, the one or more second data packets from the remote system via a transmission control protocol. ### Claim 13 A system for establishing a secure data transfer connection between a client system and a remote system, wherein a domain name of the remote system is mapped to a mapped domain name via a mapping service, wherein requests to the mapped domain name are directed to an ingress system for establishing a connection with the remote system, the system comprising: a cloud-based computer system comprising the ingress system and an egress system, wherein the ingress system is programmed to: receive a request to establish communication with the remote system, wherein the request is directed from the mapped domain name; establish a first data transfer connection with the client system; transmit, to a tunnel routing service, a request to identify an egress system from among multiple egress systems for communicating with the remote system; receive, from the tunnel routing service, an address of the egress system selected from among the multiple egress systems; and establish a data tunnel comprising a second data transfer connection with the egress system based on the address of the egress system received from the tunnel routing service; wherein the egress system is programmed to: establish a third data transfer connection between the remote system and the egress system; and wherein the ingress system and the egress system facilitate data exchange between the client system and the remote system via the first data transfer connection, the data tunnel, and the third data transfer connection. ### Claim 14 (depends on 13) The system of claim 13, wherein the ingress system is further configured to establish the first data transfer connection as a cryptographically secure transport layer security data connection. ### Claim 15 (depends on 13) The system of claim 13, wherein the egress system is further configured to establish the third data transfer connection as a cryptographically secure transport layer security data connection. ### Claim 16 (depends on 13) The system of claim 13, wherein the tunnel routing service is further configured to select the egress system to correspond to the mapped domain name by determining the egress system based on at least one of data transfer rates, overall data throughput, and latency times. ### Claim 17 (depends on 13) The system of claim 13, wherein the cloud-based computer system is further programmed to implement a second ingress system and a second egress system, wherein the second ingress system and the second egress system are configured to establish a second data tunnel between the client system and the remote system via the second ingress system and the second egress system. ### Claim 18 (depends on 13) The system of claim 13, wherein the ingress system is further configured to establish one or more fourth data transfer connections between the egress system and the ingress system in response to an increased traffic load. ### Claim 19 (depends on 13) The system of claim 13, wherein the mapping service is further programmed to: determine the mapped domain name corresponding to the ingress system and the local client, based on at least one of data transfer rates, overall data throughput, and latency times between the local client and the ingress system. ### Claim 20 (depends on 13) The system of claim 13, wherein to obtain the destination domain name corresponding to the remote system, the ingress system is further programmed to: obtain the destination domain name from a predefined mapping of the destination domain name to a mapped domain name that corresponds to the destination domain name. ### Claim 21 (depends on 13) The system of claim 13, wherein to facilitate the data exchange between the client system and the remote system, the ingress system is further programmed to: receive one or more data packets from the client system via the first data transfer connection; and transmit the one or more data packets to the egress system via the data tunnel. ### Claim 22 (depends on 21) The system of claim 21, wherein to receive the one or more data packets from the client system, the ingress system is further programmed to: receive the one or more data packets from the client system via a hypertext transfer protocol. ### Claim 23 (depends on 21) The system of claim 21, wherein to facilitate the data exchange between the client system and the remote system, the egress system is further programmed to: receive one or more second data packets from the remote system via the third data transfer connection; and transmit the one or more second data packets to the ingress system via the data tunnel. ### Claim 24 (depends on 23) The system of claim 23, wherein to receive the one or more second data packets from the remote system, the egress system is further programmed to: receive the one or more second data packets from the remote system via a transmission control protocol.