Obviousness

Obviousness Analysis of U.S. Patent 9,961,097 Under 35 U.S.C. § 103

As of May 31, 2026, an analysis of U.S. Patent 9,961,097 ("the '097 patent") under 35 U.S.C. § 103 suggests that its independent claims (Claims 1, 19, and 23) would likely have been obvious to a person having ordinary skill in the art (POSITA) at the time of the invention (priority date of December 17, 1998). This conclusion is drawn from a combination of the prior art references cited during the patent's examination, coupled with the general knowledge and motivations of a POSITA in the networking and web technology fields.

Identified Combinations of Prior Art

The following combinations of prior art references, along with general knowledge in the field, would render the independent claims of the '097 patent obvious:

1. Combination of U.S. Patent 6,144,998 (Web-based remote control) and U.S. Patent 5,850,520 (Personalized online services).

• Motivation for Combination: A POSITA in 1998, observing the growing demand for remote monitoring and control of home environments, and seeking to improve existing web-based remote control systems, would naturally look to enhance user experience through personalization and centralized access management. U.S. Patent 6,144,998 (the '998 patent) teaches the fundamental concept of remotely controlling devices via a web browser and a central server. U.S. Patent 5,850,520 (the '520 patent) describes a system for providing personalized online services, including user authentication and dynamic content generation based on user profiles. The motivation would be to combine the remote device control capabilities of '998 with the personalized, secure access and multi-user/multi-resource management features of '520 to create a more sophisticated and scalable system for remote premises access.

• Obviousness Argument:

  • Core System Architecture (First hardware, access browser, second hardware, first network, connection gateway): The '998 patent explicitly teaches a user device (first hardware) with a web browser (access browser module) connecting to a "control server" (second hardware processing circuitry) over a network (first network) to monitor and control remote devices. It would be an obvious architectural decision for a POSITA designing a system for a "user premises" with potentially multiple, diverse networked components to introduce a local "connection gateway" at the premises. This gateway would act as a hub or router, aggregating communication from the local devices and presenting a single point of contact to the external "control server." The '097 patent itself describes the connection gateway as "a hub and Internet connection mechanism for connected devices." This is a well-understood function of networking hardware, facilitating communication across different local network protocols (e.g., HomePnP, Bluetooth, HAVi, as mentioned in the '097 patent's description).
  • External Location and On-Demand Communication: The '998 patent's "control server" is external to the devices and communicates with them as needed for monitoring and control, inherently an "on-demand" interaction. Interposing a local premises gateway would simply mean the external server communicates with this gateway on-demand.
  • No Direct Communicative Coupling: By introducing a premises gateway as an intermediary, the external "control server" would naturally communicate with the gateway, which then communicates with the individual networked components. This results in the "without a direct communicative coupling between the second hardware processing circuitry and the at least one networked component" feature, as a consequence of this obvious architectural choice.
  • Plurality of Premises and Authentication-Based Access: The '520 patent teaches the concept of personalized access where user authentication determines which specific resources or services a user can access. Applying this to a remote control system (from '998) for "a plurality of user premises" would be a straightforward extension. A POSITA would be motivated to use the authentication data to identify which specific premises (and its associated gateway) the user is authorized to access, leveraging the personalized access taught by '520.
  • Establishing a "New Communication Session": The act of a user initiating a request via a browser, leading to the central server connecting to the remote gateway, would naturally involve establishing a communication session. The term "new" simply refers to a session initiated in response to the user's current request.
  • Storing Information and Single Authentication for Review: The '520 patent discloses user profiles and personalized data storage. The '998 patent involves monitoring, which generates data. Combining these, it would be obvious to a POSITA to store monitored "event information" or "surveillance data" (as described in '097) in the central network (e.g., an extranet as defined in '097) and associate it with the user's profile. The provision of accessing this stored data for "subsequent review by a user associated with the user premises, without requiring the user to provide the authentication data" during the same browser session is a well-known and desirable feature in web application security and user experience (e.g., single sign-on or session management), making it an obvious design choice for a personalized remote monitoring service. The initial authentication granting authority to access both live control and previously stored data is a logical and convenient extension of personalized access.

2. Combination of U.S. Patent 6,144,998, U.S. Patent 5,850,520, and U.S. Patent 6,292,834 (Persistent network connection).

• Motivation for Combination: While the first combination addresses many aspects, a common challenge for remote access to home devices is that the premises network or its local gateway might not have a persistently active or publicly routable IP address. A POSITA seeking to build a robust remote access system would recognize this and be motivated to incorporate solutions for establishing on-demand connections to such intermittently connected or dynamically addressed remote endpoints. U.S. Patent 6,292,834 (the '834 patent) directly addresses this problem by teaching a "rendezvous server" that facilitates establishing connections to local devices from a wide area network.

• Obviousness Argument:

  • All arguments from Combination 1 apply.
  • "Second hardware processing circuitry configured to communicate on-demand with the connection gateway" and "establishing a new communication session": The '834 patent's "rendezvous server" performs a function analogous to a component within the '097 patent's "second hardware processing circuitry" (e.g., the communications server within the extranet). It maintains current connection information for a local device and facilitates the establishment of a connection to it. Applying this teaching to the '998 system, the central "control server" would consult an '834-like rendezvous mechanism to initiate an "on-demand" connection to the premises gateway when a user requests access to their property. This directly addresses the '097 patent's description of the "user premises network... normally in an unconnected state in relation to the provider network" and the "service node... instruct[ing] a communications server... to initiate a connection to the gateway." The establishment of a "new communication session" upon verification of authentication data would be a direct implementation of these combined teachings.

Conclusion on Obviousness

The independent claims of U.S. Patent 9,961,097, which describe a system for remote premises access involving a user's browser, an external network with a communications server, and a premises gateway, appear to be obvious when viewed through the lens of the cited prior art and common engineering principles available at the time of the invention. The combination of web-based remote control (from '998), personalized and authenticated access to resources (from '520), and mechanisms for establishing on-demand connections to intermittently available remote networks (from '834), would have naturally led a POSITA to the claimed invention. The specific architectural choices, such as using a premises gateway as a hub and enabling single authentication for both live and stored data, represent obvious design implementations to enhance convenience, security, and scalability in such a system.