Prior art

To identify the most relevant prior art for US Patent 8,543,710 under 35 U.S.C. § 102, this analysis focuses on the four key prior art references previously identified in the "Obviousness Analysis" as foundational for the patent's subject matter. While these references contribute to an obviousness argument when combined, a direct anticipation analysis requires that every element of a claim be found, either explicitly or inherently, in a single prior art reference.

A review of the independent claims (1, 8, and 15) and their dependent claims against these four references reveals that none of the individual prior art documents fully anticipates any of the independent claims. Each reference discloses specific elements or aspects of the claimed invention, but not the complete combination, particularly the unique interplay of all quarantine control functions (destination and protocol restriction) combined with a gateway-rendered, interactive web page for remediation.

Below are the details for each of the most relevant prior art references and an assessment of which claim elements they potentially anticipate:

Most Relevant Prior Art

1. US20040064836A1 to Ludvig

   • Full Citation: Ludvig Edward A., "Systems and methods for generating a walled garden program for substantially optimized bandwidth delivery," US20040064836A1, published April 1, 2004.
   • Publication/Filing Date: Priority Date: September 30, 2002; Publication Date: April 1, 2004.
   • Brief Description: Ludvig describes systems and methods for delivering content and managing bandwidth, particularly through the use of a "walled garden program." This program defines and limits the content or websites a user can access, often for content control or bandwidth optimization.
   • Potential Anticipation (35 U.S.C. § 102):
     • Anticipates Claim 1, element 3(a) (Destination Restriction/Walled Garden): Ludvig explicitly teaches the concept of a "walled garden program" that restricts network traffic to one or more specific external network destination addresses.
     • Does not anticipate any complete claim: This reference does not teach the specific context of "quarantine control functions" as a result of aberrant client behavior, nor does it teach restricting traffic to selected network protocols (Claim 1, element 3(b)) in conjunction with the walled garden for quarantine. It also does not describe rendering a web page from the gateway that offers an action to obtain unrestricted access responsive to a quarantine function (Claim 1, element 4).

2. US6636894B1 to Nomadix

   • Full Citation: Nomadix, Inc., "Systems and methods for redirecting users having transparent computer access to a network using a gateway device having redirection capability," US6636894B1, published October 21, 2003.
   • Publication/Filing Date: Priority Date: December 8, 1998; Publication Date: October 21, 2003.
   • Brief Description: Nomadix describes a network access gateway that intercepts traffic from client devices and redirects initial web requests to a specific web server (often within or affiliated with the gateway) to display an informational or authentication page. This mechanism controls user access, often requiring authentication (e.g., login, payment) before full, unrestricted network access is granted.
   • Potential Anticipation (35 U.S.C. § 102):
     • Anticipates Claim 1, element 1 (Network Access Gateway): Nomadix clearly describes a gateway device that functions between a local network and the Internet.
     • Anticipates Claim 1, element 4 (Web Page Rendering & Action Offer): Nomadix explicitly teaches rendering a web page from the gateway to the client device, which offers choices of action, such as requiring authentication to obtain full access to the network.
     • Does not anticipate any complete claim: While Nomadix teaches gateway-based redirection and an offer for action to gain access, it does not explicitly teach the "quarantine control functions" of restricting network traffic to specific external destination addresses (Claim 1, element 3(a)) AND restricting that traffic to selected network protocols (Claim 1, element 3(b)) as a quarantine measure for abnormal client behavior.

3. US20030055994A1 to Zone Labs

   • Full Citation: Zone Labs, Inc., "System and methods providing anti-virus cooperative enforcement," US20030055994A1, published March 20, 2003.
   • Publication/Filing Date: Priority Date: July 6, 2001; Publication Date: March 20, 2003.
   • Brief Description: Zone Labs describes a system for detecting malicious software and enforcing security policies across a network. It focuses on identifying compromised client machines and taking actions to mitigate threats, including limiting their network access to protect other machines or prevent the spread of infection.
   • Potential Anticipation (35 U.S.C. § 102):
     • Anticipates Claim 1, element 2 (Selecting a client device): Zone Labs teaches detecting and identifying client devices with malicious software and enforcing policies on them, which involves selecting a client device for special handling.
     • Anticipates Claim 1, element 3 (Performing quarantine control functions) generally: Zone Labs teaches limiting functionality or access of a compromised client, aligning with the general idea of quarantine control functions.
     • Does not anticipate any complete claim: While it teaches restricting network access due to infection, it does not explicitly describe (in a single instance) the combination of a gateway-based "walled garden" (Claim 1, element 3(a)), specific protocol restrictions (Claim 1, element 3(b)), and the rendering of an interactive web page from the gateway offering remediation actions (Claim 1, element 4).

4. US6219706B1 to Cisco Technology, Inc.

   • Full Citation: Cisco Technology, Inc., "Access control for networks," US6219706B1, published April 17, 2001.
   • Publication/Filing Date: Priority Date: October 16, 1998; Publication Date: April 17, 2001.
   • Brief Description: Cisco describes a method and apparatus for controlling access to network resources using access control lists (ACLs) on network devices like routers. ACLs are used to filter network traffic based on various criteria, including source/destination IP addresses and specific protocols/ports, to enforce security policies.
   • Potential Anticipation (35 U.S.C. § 102):
     • Anticipates Claim 1, element 1 (Network Access Gateway): Cisco's system operates on network devices such as routers, which function as gateways controlling network access.
     • Anticipates Claim 1, element 3(a) (Destination Restriction) generally: ACLs are used to permit or deny traffic to specific network destination addresses.
     • Anticipates Claim 1, element 3(b) (Protocol Restriction): ACLs are used to permit or deny traffic based on protocols, thereby restricting traffic to selected network protocols.
     • Does not anticipate any complete claim: This patent focuses on general-purpose network access control and filtering via ACLs. It does not teach "quarantine control functions" specifically for a client device identified with aberrant behavior, nor does it teach the dynamic selection of a client device for this purpose. Critically, it does not teach rendering a web page from the network access gateway device that offers a user an action to obtain unrestricted access in response to these restrictions.