Obviousness

Obviousness Analysis of US Patent 12,452,192 under 35 U.S.C. § 103

This analysis evaluates whether the invention claimed in US Patent 12,452,192 would have been obvious to a person having ordinary skill in the art at the time of the invention. The analysis is based on combinations of the prior art references identified in the preceding section.

A person having ordinary skill in the art (PHOSITA) in the relevant field of computer networking and network optimization as of the patent's priority date (April 7, 2015) would possess a Bachelor's degree in Computer Science or a related discipline, coupled with several years of industry experience. This experience would include designing or managing wide-area networks (WANs), virtual private networks (VPNs), and understanding network performance metrics and optimization techniques like load balancing and dynamic routing.

The core concept of the independent claims (1, 8, and 15) of patent '192 is a system where a central control server monitors the performance of various access point servers, creates a ranked list based on these performance metrics, and provides this list to an endpoint device, which then automatically connects to the best-ranked server.

---

Ground 1: Claims 1, 8, and 15 are obvious over US 8,631,114 B1 (Google) in view of either US 9,237,492 B2 (Akamai) or US 9,912,636 B2 (Aryaka).

1. Scope and Content of the Prior Art:

• Google '114 discloses a system where a "master server" (analogous to the '192 patent's control server) provides a list of available servers to a client device (endpoint). The key difference is that the client in Google '114 is responsible for probing the servers on the list to measure performance (e.g., round-trip time) and then selecting the best one for connection. The performance analysis is decentralized and performed by the client after receiving a non-ranked list.
• Akamai '492 teaches a centralized "mapping system" (control server) that collects performance data from numerous clients regarding various "name servers" (access point servers). It aggregates this data to determine which servers are optimal and provides clients with a list of these optimal servers, avoiding the need for each client to perform its own extensive testing.
• Aryaka '636 teaches a "central controller" (control server) in an SD-WAN environment that continuously monitors performance metrics (latency, jitter, packet loss) across its network of Points of Presence, or "POPs" (access point servers). It uses this centralized data to dynamically select the optimal path for traffic.

2. Motivation to Combine:
A PHOSITA starting with the system in Google '114 would recognize its inherent inefficiencies. Requiring every client to independently probe a list of servers generates significant, redundant network traffic and places a computational burden on each client device. Furthermore, the client's decision is based only on a snapshot of network conditions from its own limited perspective.

The motivation to improve the Google '114 system would be to increase efficiency, reduce connection latency, and make more intelligent server selections based on a global view of network health. A PHOSITA would naturally look to solve this problem by centralizing the performance monitoring and analysis.

Both Akamai '492 and Aryaka '636 teach the very solution needed to overcome the deficiencies in Google '114. Akamai '492 explicitly teaches centralizing performance data collection to provide clients with a pre-vetted list of optimal servers. Aryaka '636 teaches a similar concept in the highly analogous SD-WAN context, where a central controller uses global performance data to make routing decisions.

Therefore, a PHOSITA would have been motivated to modify the Google '114 system by replacing the client-side probing mechanism with the centralized monitoring and ranking logic taught by Akamai '492 or Aryaka '636. This modification would have been a predictable improvement, resulting in a system where a control server monitors access points, ranks them by performance, and provides this ranked list to the endpoint device for selection, as claimed in US 12,452,192. This combination of known elements would have yielded the claimed invention with a reasonable expectation of success.

---

Ground 2: Claims 1, 8, and 15 are obvious over US 9,237,492 B2 (Akamai).

1. Scope and Content of the Prior Art:

• Akamai '492 discloses nearly all elements of the '192 patent's claims. It features a central system ("mapping system") that collects real-world performance data (latency, packet loss) and uses this data to provide clients with a list of optimal servers ("name servers") for their location and network conditions.

2. Obviousness Rationale:
An argument can be made that Akamai '492 anticipates the '192 patent. However, for the purpose of an obviousness analysis, any minor differences would have been obvious to a PHOSITA. The '192 patent claims a "global virtual network" with "access point servers" and the creation of a "tunnel." The Akamai '492 patent focuses on selecting "name servers" for DNS resolution.

A PHOSITA would have readily recognized that the problem of selecting the best initial connection point is not unique to DNS. The same challenge exists for any distributed network service, including a GVN or VPN. Applying the proven method from Akamai '492 for selecting an optimal DNS server to the analogous problem of selecting an optimal GVN access point server would have been a straightforward and obvious extension of the prior art. The motivation is clear: to improve the performance, reliability, and user experience of the GVN, which are the same goals addressed by the Akamai system.

Creating a "ranked list" as claimed in the '192 patent is an obvious implementation of providing a list of "optimal" servers as taught by Akamai '492. To determine which servers are optimal, a system must necessarily compare and rank them based on performance metrics. Thus, the distinction is merely semantic. The application of Akamai's established server-selection architecture to the GVN context would have been an obvious design choice for a skilled network engineer in 2015.