View source for 20240022626. DNS-BASED GSLB-AWARE SD-WAN FOR LOW LATENCY SAAS APPLICATIONS simplified abstract (VMWARE, INC.)

=DNS-BASED GSLB-AWARE SD-WAN FOR LOW LATENCY SAAS APPLICATIONS=


==Organization Name==

[[:Category:VMWARE, INC.|VMWARE, INC.]]


[[Category:VMWARE, INC.]]

==Inventor(s)==

[[:Category:Ankit Sinha of Bengaluru (IN)|Ankit Sinha of Bengaluru (IN)]][[Category:Ankit Sinha of Bengaluru (IN)]]

[[:Category:Navaneeth Krishnan Ramaswamy of Chennai (IN)|Navaneeth Krishnan Ramaswamy of Chennai (IN)]][[Category:Navaneeth Krishnan Ramaswamy of Chennai (IN)]]

[[:Category:Balaji Shanmugam of Bengaluru (IN)|Balaji Shanmugam of Bengaluru (IN)]][[Category:Balaji Shanmugam of Bengaluru (IN)]]

[[:Category:Sasikumar Balasubramanian of Chennai (IN)|Sasikumar Balasubramanian of Chennai (IN)]][[Category:Sasikumar Balasubramanian of Chennai (IN)]]

==DNS-BASED GSLB-AWARE SD-WAN FOR LOW LATENCY SAAS APPLICATIONS - A simplified explanation of the abstract==


This abstract first appeared for US patent application 20240022626 titled 'DNS-BASED GSLB-AWARE SD-WAN FOR LOW LATENCY SAAS APPLICATIONS

==Simplified Explanation==

The abstract of this patent application describes a method for routing data message traffic from an edge router at one location to a SaaS application server provided by a third-party at another location. The method involves querying a GSLB-aware DNS server for a cloud gateway that can be used to reach the destination network address of the SaaS application server. The DNS server provides an identifier for a cloud gateway that is closer to the second location than another cloud gateway in multiple locations. An optimized SD-WAN connection is then used to forward data messages for the first cloud gateway to the SaaS application server at the second location.

* The method involves routing data message traffic from an edge router to a SaaS application server at a different location.
* A GSLB-aware DNS server is used to find a cloud gateway that can be used to reach the destination network address of the SaaS application server.
* The DNS server provides an identifier for a cloud gateway that is closer to the second location than another cloud gateway.
* An optimized SD-WAN connection is used to forward data messages for the first cloud gateway to the SaaS application server at the second location.

Potential applications of this technology:

* Efficient routing of data message traffic between edge routers and SaaS application servers.
* Improved performance and reliability of SaaS applications by using optimized SD-WAN connections.
* Scalability for handling high volumes of data message traffic between different locations.

Problems solved by this technology:

* Efficiently routing data message traffic between different locations.
* Optimizing the selection of cloud gateways for reaching SaaS application servers.
* Improving the performance and reliability of SaaS applications.

Benefits of this technology:

* Faster and more reliable data message traffic routing.
* Improved performance and user experience for SaaS applications.
* Scalability for handling increasing data message traffic volumes.


==Original Abstract Submitted==

some embodiments of the invention provide a method of routing data message traffic from an edge router at a first location and a saas (software as a service) application server provided by a third-party at a second location. the method queries a (global server load balancing) gslb-aware dns (domain name system) server for a cloud gateway from multiple cloud gateways at multiple locations through which a particular destination network address for the saas application server can be reached. the method receives from the gslb-aware dns server an identifier for a first cloud gateway that is farther from the first location than a second cloud gateway in the multiple cloud gateways but closer to the second location than the second cloud gateway. the method uses an optimized sd-wan (software-defined wide-area network) connection to the first cloud gateway to forward data messages for the first cloud gateway to the saas application at the second location.



[[Category:H04L67/1004]]
[[Category:H04L61/4511]]
[[Category:H04L67/53]]
[[Category:H04L43/0864]]
[[Category:H04L43/10]]