Patent 10419805

Obviousness

Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.

Active provider: Google · gemini-2.5-pro

Obviousness

Combinations of prior art that suggest the claimed invention would have been obvious under 35 U.S.C. § 103.

✓ Generated

Obviousness Analysis of U.S. Patent No. 10,419,805 under 35 U.S.C. § 103

This analysis assesses the obviousness of the independent claims of U.S. Patent No. 10,419,805 ("the '805 patent") in light of the prior art cited during its prosecution. The standard for obviousness under 35 U.S.C. § 103 is whether the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art (PHOSITA). A PHOSITA in this field would likely be a software engineer or system architect with experience in developing applications for televisions, set-top boxes, and digital media devices, possessing knowledge of common software architecture patterns, data aggregation, and user interface design.

The core of the invention claimed in the '805 patent is a specific software architecture for an "Intelligent TV" that uses an "internal content provider module" to orchestrate data retrieval from multiple sources via "subservices" and "source plug-ins." This structure aims to provide an organized and efficient way to aggregate and display content from disparate sources.

The independent claims (1, 12, and 17) can be rendered obvious by combining the teachings of U.S. Patent No. 9,456,247 B2 (D'Angelo '247) with the teachings of U.S. Patent Application Publication No. 2009/0254946 A1 (Craner).


Primary Reference: D'Angelo '247 (U.S. Patent No. 9,456,247 B2)

D'Angelo '247 discloses a "smart television" system that provides a user with a "dashboard" for accessing content from a variety of sources. This system teaches several key elements of the '805 patent's claims:

  • An Intelligent TV with a processor and display: D'Angelo '247 explicitly describes a television with a processor and memory for executing applications and presenting a user interface on its screen.
  • An "internal content provider module" loaded by user action: The "dashboard" in D'Angelo '247 functions as an internal content provider module. It is the central user interface from which a user can access different content. The user's action of navigating to this dashboard initiates the process of gathering and displaying content options.
  • Accessing data from multiple distinct sources: D'Angelo '247 clearly describes a system that integrates content from both traditional broadcast television and internet-based "on-demand" applications (e.g., Netflix, Hulu). This directly corresponds to the concept of managing data from a "plurality of distinct sources."
  • Organizing and providing content to a display: The dashboard in D'Angelo '247 aggregates and organizes information from these different sources into a unified view for the user, fulfilling the requirement of organizing data into a format for presentation.

While D'Angelo '247 discloses the high-level functionality, it does not explicitly describe the specific software architecture using the terms "subservices" or "source plug-ins." It describes distinct applications, but not the modular, layered communication structure claimed in the '805 patent.


Secondary Reference: Craner (U.S. Patent App. Pub. No. 2009/0254946 A1)

Craner discloses a system and method for aggregating content from multiple sources, such as web feeds, broadcast television, and personal media libraries, and presenting it in a unified user interface. The key contribution of Craner for an obviousness combination is its disclosure of a specific, modular architecture to achieve this aggregation.

  • Modular architecture with source-specific components: Craner explicitly describes an architecture that includes distinct "components for connecting to and retrieving data" from different sources. This architecture is directly analogous to the "subservices" and "source plug-ins" recited in the '805 claims. A "subservice" can be seen as the component managing a type of content (e.g., video, news), and the "source plug-in" is the specific piece of code that interfaces with a particular external source (e.g., a specific web feed's API or a broadcast tuner).

Motivation to Combine D'Angelo '247 and Craner

A person of ordinary skill in the art, when faced with the task of building the smart TV system described in D'Angelo '247, would have been motivated to implement the underlying software using the modular architecture taught by Craner for several compelling reasons:

  1. Scalability and Extensibility: The primary motivation would be to create a scalable system. The smart TV market in the pre-2012 era was rapidly evolving, with new content services and sources emerging frequently. A PHOSITA would recognize that hard-coding the logic for each content source into the main "dashboard" application (as might be inferred from D'Angelo '247) would be inefficient and difficult to maintain. The plug-in architecture taught by Craner provides an obvious solution. By creating separate, self-contained "plug-ins" or modules for each content source, developers could easily add support for new services (e.g., a new streaming video provider) or update existing ones without altering the core application. This is a standard and well-understood software engineering practice for building flexible systems.

  2. Improved Maintainability: Separating the concerns of the user interface (D'Angelo's dashboard) from the data fetching logic (Craner's source-specific components) makes the system easier to debug and maintain. If a particular content source changes its API, only the corresponding plug-in needs to be updated, not the entire television application. This modularity was a well-established design principle at the time of the invention.

  3. Predictable Result: Combining Craner's modular, plug-in based data-fetching architecture with D'Angelo's '247 user-facing dashboard system would have been a straightforward integration for a POSITA. The result would be a system where a central UI module (the "internal content provider module") requests data from specialized service modules ("subservices"), which in turn use source-specific drivers ("source plug-ins") to retrieve the content. This combination would predictably result in the very system claimed in the '805 patent: a more robust, scalable, and maintainable version of the smart TV experience described in D'Angelo '247.

Conclusion on Obviousness

The combination of D'Angelo '247 and Craner teaches all elements of the independent claims of the '805 patent.

  • Claims 1, 12, and 17 recite a method, system, and television, respectively, that load an "internal content provider module" (the dashboard from D'Angelo '247). This module communicates with "subservices" that use "source plug-ins" to manage and retrieve data from "a plurality of distinct sources" (the modular, source-specific data retrieval components from Craner, applied to the multiple sources of D'Angelo '247). The module then organizes and presents this data (as shown in the unified dashboard of D'Angelo '247).

A person of ordinary skill in the art would have found it obvious to implement the functional system of D'Angelo '247 using the well-known and advantageous modular, plug-in style architecture described by Craner to enhance scalability and maintainability. Therefore, the independent claims of U.S. Patent No. 10,419,805 would have been obvious over the combination of these prior art references.

Generated 5/10/2026, 2:44:03 PM