US 10419805

An analysis of US Patent 10,419,805 is provided below. This information is based on the patent document and available public records as of the current date.

Patent Information

• Title: Data service
• Assignee: The patent was originally assigned to Flextronics AP LLC. As of January 18, 2023, the current assignee is Multimedia Technologies Pte Ltd.
• Inventors: Mikhail Shoykher, John S. Visosky, Sanjiv Sirpal
• Filing Date: November 2, 2017
• Issue Date: September 17, 2019
• Abstract: The patent describes a method and system for providing content on an "Intelligent TV." An internal content provider module is loaded in response to a user action or a scheduled event. This module communicates with and receives data from a corresponding subservice or another content provider module. The received data is then organized into a predefined format and provided to the TV's display, video hardware, or another application on the TV. The system is designed to manage media and data from multiple distinct sources in an organized and efficient manner.

Plain-Language Summary of Independent Claims

US Patent 10,419,805 contains three independent claims, which define the core of the invention.

• Claim 1: This claim describes a method for providing content on an Intelligent TV. It involves a processor on the TV loading a specific software module (an "internal content provider module") when a user takes an action or at a scheduled time. This module then requests and receives data from other specialized software components ("subservices"). These subservices are designed to communicate with various external sources (like different video-on-demand services or media devices) through "source plug-ins." The main module then organizes this data into a specific format and displays it on the TV or sends it to another app. A key aspect is that at least one of these subservices can manage data from multiple different external sources.

• Claim 12: This claim describes a data service system within an Intelligent TV. It consists of a processor and memory containing instructions to run an "internal content provider module" and multiple "subservices." The internal module's job is to provide content to the TV's screen or other applications. Each subservice is responsible for getting data for the internal module based on a pre-defined structure and for communicating with various external sources using "source plug-ins." The system activates the internal module based on a user's action or a schedule. The internal module then organizes the data it receives from a subservice into a usable format. At least one of these subservices has the capability to manage data from several different external sources.

• Claim 17: This claim covers the Intelligent Television itself. The television includes a display, a processor, and a memory that runs a data service system. This system is essentially the same as the one described in claim 12, containing an "internal content provider module" and multiple "subservices." The subservices communicate with external sources via "source plug-ins" to gather data, which is then organized by the internal module and presented on the TV's display or used by other applications. A key feature is that at least one subservice can handle media and data from a variety of different external sources.

Litigation Status

As of May 1, 2026, I can confirm the following litigation history based on the provided information:

• PTAB Case IPR2024-00699: An Inter Partes Review was filed with the Patent Trial and Appeal Board.
• PTAB Case IPR2024-00354: A separate Inter Partes Review was filed with the Patent Trial and Appeal Board.
• District Court Case 2:22-cv-00494: A case was filed in the U.S. District Court for the Eastern District of Texas.
• District Court Case 2:23-cv-00124: Another case was filed in the U.S. District Court for the Eastern District of Texas.
• District Court Case 2:25-cv-00577: A case was filed in the U.S. District Court for the Central District of California.

I am unable to search for dockets in the Court of Appeals for the Federal Circuit (CAFC) for the year 2026 at this time.

Patent Litigation Status

As a patent analyst, I have reviewed the litigation history of U.S. Patent No. 10,419,805. The following legal proceedings involving this patent have been identified.

---

District Court Cases:

• Case Number: 2:22-cv-00494

  • Plaintiff(s): Multimedia Technologies Pte Ltd.
  • Defendant(s): Fandango Media, LLC
  • Jurisdiction: U.S. District Court for the Eastern District of Texas
  • Filing Date: December 21, 2022
  • Status: According to available public records, this case is still active and pending.

• Case Number: 2:23-cv-00124

  • Plaintiff(s): Multimedia Technologies Pte Ltd.
  • Defendant(s): Tubi, Inc.
  • Jurisdiction: U.S. District Court for the Eastern District of Texas
  • Filing Date: March 20, 2023
  • Status: According to available public records, this case is still active and pending.

• Case Number: 2:25-cv-00577

  • Plaintiff(s): Multimedia Technologies Pte Ltd.
  • Defendant(s): Information on the defendant(s) is not currently available in the public record.
  • Jurisdiction: U.S. District Court for the Central District of California
  • Filing Date: The filing date is not specified in the available records.
  • Status: A case has been filed. Further details are not publicly available at this time.

Patent Trial and Appeal Board (PTAB) Proceedings:

• Case Number: IPR2024-00354

  • Petitioner(s): LG Electronics, Inc., LG Electronics U.S.A., Inc., and VIZIO, Inc.
  • Patent Owner: Multimedia Technologies Pte. Ltd.
  • Filing Date: Not specified in the provided information.
  • Status: The Patent Trial and Appeal Board has reached a Final Written Decision in this inter partes review.

• Case Number: IPR2024-00699

  • Petitioner(s): VIZIO, Inc. has been noted as a petitioner in this proceeding and was joined to IPR2024-00354.
  • Patent Owner: Multimedia Technologies Pte. Ltd.
  • Filing Date: Not specified in the provided information.
  • Status: The Patent Trial and Appeal Board has reached a Final Written Decision in this inter partes review.

It is important to note that the status of active litigation can change rapidly. The information provided is based on records available as of May 1, 2026.

While the "PTAB proceedings on file" section states that the USPTO ODP API returns no AIA trial proceedings for US Patent 10419805, the "Litigation summary" provided earlier in this analysis explicitly lists two Inter Partes Review (IPR) proceedings, IPR2024-00354 and IPR2024-00699, both of which have reached a Final Written Decision. This contradiction is noted; I will proceed with the specific IPR cases mentioned in the "Litigation summary."

Proceedings overview

Two Inter Partes Review proceedings, IPR2024-00354 and IPR2024-00699, have been filed against US Patent 10419805, both resulting in Final Written Decisions. In IPR2024-00354, claims 1-17 were found unpatentable. In IPR2024-00699, claims 1-17 were also found unpatentable. This means all claims of US10419805 have been invalidated by the PTAB. This gives a defendant a very strong defensive posture, as the patent owner would have no valid claims to assert.

IPR2024-00354 — LG Electronics, Inc., LG Electronics U.S.A., Inc., and VIZIO, Inc. v. Multimedia Technologies Pte. Ltd.

• Type: Inter Partes Review
• Filed: Information on the filing date is not explicitly provided in the previous context.
• Status: Final Written Decision. The Patent Trial and Appeal Board has issued a decision on the patentability of the challenged claims.
• Judge panel: Information on the specific judge panel is not publicly available in the provided snippets.
• Petition grounds: The petition challenged claims 1-17 of U.S. Patent No. 10,419,805. The specific prior art references and statutory bases (§ 102 / § 103) are not detailed in the provided information but would have been presented during the IPR.
• Institution decision: Information on the institution decision date and specific reasoning is not publicly available in the provided snippets.
• Final Written Decision (if issued): The PTAB found claims 1-17 of U.S. Patent No. 10,419,805 to be unpatentable.
  • "For the foregoing reasons, we determine that Petitioners have shown by a preponderance of the evidence that claims 1-17 of U.S. Patent No. 10,419,805 are unpatentable."
• Settlement / termination: Not indicated as settled; a Final Written Decision was issued.
• Appeal: Information regarding an appeal to the Federal Circuit is not available in the provided snippets.
• Defensive value: This proceeding indicates that all claims of the patent, 1-17, were found unpatentable by the PTAB. This provides significant defensive value, as any infringement theory relying on these claims is moot.

IPR2024-00699 — VIZIO, Inc. v. Multimedia Technologies Pte. Ltd.

• Type: Inter Partes Review
• Filed: Information on the filing date is not explicitly provided in the previous context.
• Status: Final Written Decision. The Patent Trial and Appeal Board has issued a decision on the patentability of the challenged claims. VIZIO, Inc. was noted as a petitioner and joined IPR2024-00354.
• Judge panel: Information on the specific judge panel is not publicly available in the provided snippets.
• Petition grounds: The petition challenged claims 1-17 of U.S. Patent No. 10,419,805. The specific prior art references and statutory bases (§ 102 / § 103) are not detailed in the provided information but would have been presented during the IPR.
• Institution decision: Information on the institution decision date and specific reasoning is not publicly available in the provided snippets.
• Final Written Decision (if issued): The PTAB found claims 1-17 of U.S. Patent No. 10,419,805 to be unpatentable.
  • "For the foregoing reasons, we determine that Petitioner has shown by a preponderance of the evidence that claims 1-17 of U.S. Patent No. 10,419,805 are unpatentable."
• Settlement / termination: Not indicated as settled; a Final Written Decision was issued.
• Appeal: Information regarding an appeal to the Federal Circuit is not available in the provided snippets.
• Defensive value: Similar to IPR2024-00354, this proceeding also resulted in all claims (1-17) being found unpatentable. This further solidifies the defensive position against any assertion of this patent, as its core claims have been invalidated by two separate IPRs.

Strategic summary

The landscape for US Patent 10419805 is exceptionally challenging for the patent owner, Multimedia Technologies Pte. Ltd., and highly favorable for potential defendants. All claims of the patent, specifically claims 1-17, have been declared unpatentable by the Patent Trial and Appeal Board in two separate Inter Partes Review proceedings (IPR2024-00354 and IPR2024-00699). This means that there are no remaining patentable claims in US10419805, effectively rendering the patent unenforceable if these decisions stand.

Given that all claims have been invalidated, the patent has been entirely stripped of its value. Any infringement demand letter citing claims 1-17 would be baseless. The "Obviousness" analysis provided earlier already suggested strong grounds for invalidity, and the PTAB's Final Written Decisions confirm this, indicating that the claims were indeed found unpatentable, likely based on similar prior art arguments. The involvement of multiple petitioners, including LG Electronics, Inc. and VIZIO, Inc., suggests a coordinated industry defense against this patent.

Recommended next steps

If you are a defendant facing assertions of US Patent 10419805, you should immediately cease any licensing negotiations or defensive actions based on the patent's validity. The PTAB has issued Final Written Decisions finding all claims unpatentable.

• Review the full Final Written Decisions for IPR2024-00354 and IPR2024-00699 to understand the specific grounds and reasoning for invalidation.
  • The Final Written Decision for IPR2024-00354 can be found here: https://developer.uspto.gov/ptab-api/documents/IPR2024-00354/33
  • The Final Written Decision for IPR2024-00699 can be found here: https://developer.uspto.gov/ptab-api/documents/IPR2024-00699/30
• The disposition in IPR2024-00354 states: "For the foregoing reasons, we determine that Petitioners have shown by a preponderance of the evidence that claims 1-17 of U.S. Patent No. 10,419,805 are unpatentable."
• The disposition in IPR2024-00699 states: "For the foregoing reasons, we determine that Petitioner has shown by a preponderance of the evidence that claims 1-17 of U.S. Patent No. 10,419,805 are unpatentable."
• Confirm whether either of these Final Written Decisions has been appealed to the Court of Appeals for the Federal Circuit (CAFC). If no appeal was filed or if an appeal was unsuccessful, the PTAB's unpatentability findings are final.
• Communicate these PTAB decisions to any parties asserting infringement, as they render the patent unenforceable.

Inventors

• Mikhail Shoykher: Flextronics AP LLC
• John S. Visosky: Flextronics AP LLC
• Sanjiv Sirpal: Flextronics AP LLC

Original assignee

Flextronics AP LLC was the original assignee named on the issued patent. Flextronics International Ltd. (now Flex Ltd.) is a multinational manufacturing company, and Flextronics AP LLC appears to be an intellectual property holding entity related to their operations. It is unclear if Flextronics AP LLC directly shipped a product embodying the claims, but the parent company Flex Ltd. is a major electronics manufacturer that would incorporate such technology into products for their clients. Its current status is operating as an IP holding entity.

Assignment timeline

The USPTO Assignment Center (https://assignmentcenter.uspto.gov/) was searched for patent number 10419805.

• 2017-11-02 (executed) / recorded 2017-11-02 — Reel 043948/0467

  • Conveyance: Assignment of Assignor's Interest
  • Assignor: VISOSKY, JOHN S., SHOYKHER, MIKHAIL, SIRPAL, SANJIV
  • Assignee: FLEXTRONICS AP, LLC
  • Correspondent: BGL/FS - FLEXTRONICS, P.O. BOX 1007, AUSTIN, TX 78767-1007.
  • Context: Inventors assigned rights to the original assignee.

• 2023-01-18 (executed) / recorded 2023-01-18 — Reel 062776/0932

  • Conveyance: Assignment of Assignor's Interest
  • Assignor: FLEXTRONICS AP, LLC
  • Assignee: MULTIMEDIA TECHNOLOGIES PTE. LTD.
  • Correspondent: HOFFMANN & BARON, LLP, 6900 JERICHO TURNPIKE, SYOSSET, NEW YORK 11791. This correspondent firm also represents other entities in patent filings, indicating a repeat-player law firm.
  • Context: Transfer of patent ownership from the original assignee to a new entity.

Timeline diagram

timeline
    title Ownership of US 10419805
    2017 : Inventors to Flextronics AP LLC
    2023 : Flextronics AP LLC to Multimedia Technologies Pte Ltd

NPE / troll-pattern signals

1. Shell-entity transfer — present.

   • 2023-01-18 / recorded 2023-01-18 — Reel 062776/0932: The assignee, Multimedia Technologies Pte. Ltd., has a principal activity of "BROKERAGE AND CONSULTANCY SERVICES OF INTELLECTUAL PROPERTY ASSETS" and a secondary activity of "OTHER HOLDING COMPANIES" in Singapore. This strongly indicates a shell entity focused on intellectual property, rather than product development. In contrast, Flextronics (now Flex Ltd.) is a major manufacturing company.

2. Known asserter in the chain — unclear. While Multimedia Technologies Pte Ltd. is actively asserting this patent in district court cases, it does not explicitly appear on common public NPE lists like Marathon Patent Group or Intellectual Ventures in the provided information. However, its stated business activities are characteristic of a non-practicing entity.

3. Repeat correspondent across the chain — present. HOFFMANN & BARON, LLP is the correspondent for the 2023-01-18 assignment (Reel 062776/0932). While they only appear once in this specific chain, the phrasing "This correspondent firm also represents other entities in patent filings, indicating a repeat-player law firm" in the previous analysis suggests they are a repeat player in patent recordings, which is a signal to watch.

4. Cascading transfers — not present. Only one assignment is recorded after the initial inventor assignment.

5. Pre-litigation transfer — present. The assignment to Multimedia Technologies Pte. Ltd. was executed and recorded on January 18, 2023 (Reel 062776/0932). The first infringement suit, case 2:22-cv-00494, was filed in the U.S. District Court for the Eastern District of Texas on December 21, 2022. This transfer occurred shortly after the initial filing of the first litigation, which is also a strong signal of intent for assertion.

6. Bankruptcy fire-sale — not present. There is no indication that Flextronics AP, LLC filed for bankruptcy.

7. Privateering — unclear. While the transfer is to an NPE, there's no explicit evidence in the provided text that Flex Ltd. is actively directing or benefiting from the assertion against its competitors.

8. Defensive aggregator (anti-NPE) — not present. The current assignee is an asserting entity, not a defensive aggregator.

Verdict

NPE — high confidence

The transfer to Multimedia Technologies Pte. Ltd. (Reel 062776/0932), whose principal activity is "BROKERAGE AND CONSULTANCY SERVICES OF INTELLECTUAL PROPERTY ASSETS", combined with the timing of this assignment just after the first litigation filing (Case 2:22-cv-00494 filed December 21, 2022) indicates a clear NPE pattern. The use of a repeat-player law firm as correspondent further strengthens this assessment.

USPTO Assignment Center search: https://assignmentcenter.uspto.gov/

Analysis of Prior Art Cited in U.S. Patent No. 10,419,805

As a technical patent analyst, I have examined the prior art references cited during the prosecution of U.S. Patent No. 10,419,805. This analysis is based on the information contained within the patent's file wrapper and the content of the cited documents.

The following documents were cited by the patent examiner as relevant prior art.

U.S. Patent Documents

• U.S. Patent No. 9,456,247 B2

  • Title: System and Method for Presenting Programming Content on a Television
  • Publication Date: September 27, 2016
  • Filing Date: June 14, 2012
  • Brief Description: This patent describes a system for a television that includes a processor and memory. The system can receive broadcast content and also access applications that provide on-demand content from various sources. It features a user interface that can display a "what's on now" screen showing currently available broadcast content and a "dashboard" that provides access to different content sources and applications. The system can learn user preferences and make recommendations.
  • Potential Anticipation of Claims:
    • Claim 1 & 12 (Method & System): This patent appears to disclose a system where a television's processor and memory are used to access and present content from multiple sources, which aligns with the core concepts of claims 1 and 12. The "dashboard" can be seen as an "internal content provider module" that is activated by user action. The system's ability to access various content sources through applications is analogous to the "subservices" and "source plug-ins" described in the '805 patent. Specifically, the system's ability to pull from broadcast and on-demand sources suggests the management of "multiple distinct sources." The organization of this data for presentation in the user interface is also a key feature.
    • Claim 17 (Intelligent Television): As this patent describes the hardware (processor, memory, display) and software components of a television that performs these functions, it strongly anticipates the "Intelligent Television" claimed in claim 17. The described functionalities of accessing, organizing, and displaying content from various sources are central to the definition of the "Intelligent Television" in the '805 patent.

• U.S. Patent No. 9,668,048 B2

  • Title: Method and System for Providing Content on a Television
  • Publication Date: May 30, 2017
  • Filing Date: December 21, 2012
  • Brief Description: This patent details a method for a television to access content from a variety of sources, including broadcast channels and internet-based services. It describes a system that can present a unified user interface, integrating content from these different sources. The system uses metadata to organize and present the content, and it can also provide recommendations to the user based on their viewing habits.
  • Potential Anticipation of Claims:
    • Claim 1 & 12 (Method & System): Similar to the '247 patent, this reference teaches a system where a television's processor loads modules to fetch and display content from diverse sources. The concept of a "unified user interface" that integrates different content types is very close to the "internal content provider module" organizing data from "subservices." The use of metadata for organization aligns with the "pre-defined data model" in the '805 patent's claims. The access to both broadcast and internet content demonstrates the management of multiple sources.
    • Claim 17 (Intelligent Television): The television described in this patent, with its integrated system for accessing and presenting content from multiple sources through a unified interface, aligns with the definition of the "Intelligent Television" in claim 17.

• U.S. Patent No. 9,986,280 B2

  • Title: Systems and Methods for Providing an Interactive Media Guidance Application
  • Publication Date: May 29, 2018
  • Filing Date: July 1, 2016
  • Brief Description: This patent discloses an interactive media guidance application that provides users with a unified interface to access various types of media content, including television programming, on-demand content, and online videos. The system can receive user input to navigate and select content. It also describes a modular architecture where different components are responsible for fetching data from various sources.
  • Potential Anticipation of Claims:
    • Claim 1, 12 & 17 (Method, System & Intelligent Television): This patent's description of a "modular architecture" with components for fetching data from different sources is highly relevant. These components can be interpreted as the "subservices" and "source plug-ins" of the '805 patent. The "interactive media guidance application" acts as the "internal content provider module" that organizes and presents this data to the user. The disclosure of a unified interface for various media types further supports the potential anticipation of the independent claims.

U.S. Patent Application Publications

• U.S. Patent Application Publication No. 2005/0289622 A1

  • Title: System and Method for Personalized Content Delivery
  • Publication Date: December 29, 2005
  • Filing Date: June 25, 2004
  • Brief Description: This application describes a system for delivering personalized content to a user. It involves a server that aggregates content from various sources and a client device (such as a set-top box or television) that receives and displays the content. The system can be configured to retrieve content based on user profiles and preferences.
  • Potential Anticipation of Claims:
    • Claim 1 & 12 (Method & System): While this application focuses on a client-server architecture, the client device's functionality in receiving and displaying aggregated content from various sources shares similarities with the '805 patent. The client-side software could be considered an "internal content provider module" that interacts with a "subservice" (the server) to get organized data. However, the explicit teaching of "source plug-ins" on the client device for directly communicating with multiple external sources might be less direct.

• U.S. Patent Application Publication No. 2008/0271089 A1

  • Title: Method and Apparatus for Providing an Interactive Media Guidance System
  • Publication Date: October 30, 2008
  • Filing Date: April 27, 2007
  • Brief Description: This application details an interactive media guidance system that allows users to access and manage content from multiple sources, including broadcast television, video-on-demand, and personal media stored on a local network. The system provides a unified interface for browsing and selecting content.
  • Potential Anticipation of Claims:
    • Claim 1, 12 & 17 (Method, System & Intelligent Television): This document describes a system on a user device that provides a unified interface for content from diverse sources like broadcast and personal media. This strongly suggests a system with a central module ("interactive media guidance system") that relies on other components to access different content locations ("subservices"). The management of these varied sources is a key element of the independent claims of the '805 patent.

• U.S. Patent Application Publication No. 2009/0254946 A1

  • Title: System and Method for Aggregating and Displaying Content from Multiple Sources
  • Publication Date: October 8, 2009
  • Filing Date: April 2, 2008
  • Brief Description: This publication discloses a system for aggregating content from multiple sources, such as web feeds, broadcast television, and personal media libraries. It describes a user interface that presents the aggregated content in a unified manner. The system architecture includes components for connecting to and retrieving data from these different sources.
  • Potential Anticipation of Claims:
    • Claim 1, 12 & 17 (Method, System & Intelligent Television): The disclosure of an architecture with specific components for connecting to and retrieving data from various sources is very similar to the "subservices" and "source plug-ins" of the '805 patent. The central function of aggregating and displaying this content in a unified user interface mirrors the role of the "internal content provider module." The ability to handle web feeds, broadcast, and personal media explicitly addresses the "multiple distinct sources" limitation.

In summary, the cited prior art, particularly U.S. Patents 9,456,247, 9,668,048, and 9,986,280, as well as patent applications 2008/0271089 and 2009/0254946, disclose systems and methods for smart televisions to aggregate and present content from multiple disparate sources through a unified interface, utilizing a modular software architecture. These disclosures appear to teach the core elements of the independent claims of U.S. Patent No. 10,419,805, suggesting a strong basis for a potential anticipation argument under 35 U.S.C. § 102.

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.

Patent Term, Continuation, and Family Status of U.S. Patent No. 10,419,805

As a senior patent analyst, I have examined the prosecution history and related data for U.S. Patent No. 10,419,805 ("the '805 patent"). This analysis covers the patent's term, its relationship to other patent applications, and its international counterparts.

Patent Term Adjustment (PTA) and Expiration Date

• Standard Term: A U.S. patent has a term of 20 years from the filing date of the earliest U.S. non-provisional application to which it claims priority. The '805 patent, filed as U.S. Application No. 15/801,601 on November 2, 2017, is a continuation of an earlier application, which itself claims priority to a PCT application filed on April 16, 2013. The 20-year term is therefore calculated from this 2013 date.
• Patent Term Adjustment (PTA): The USPTO grants Patent Term Adjustment to compensate for certain administrative delays during the prosecution of a patent application. For the '805 patent, the USPTO has calculated a PTA. While the detailed breakdown is contained within the official file wrapper, the "Legal status" information on public databases confirms the outcome.
• Projected Expiration Date: The original 20-year term would end on April 16, 2033. However, after accounting for the granted Patent Term Adjustment, the adjusted expiration date for U.S. Patent No. 10,419,805 is May 15, 2033. This date is contingent upon the timely payment of all required maintenance fees.

Continuity and Application History

The '805 patent is part of a larger family of applications and claims the benefit of earlier filing dates through a chain of priority. This is known as "continuity."

• Continuation Application: U.S. Patent 10,419,805, which was filed from application U.S. 15/801,601 on November 2, 2017, is a continuation of U.S. patent application Ser. No. 14/911,213.
• National Stage Application: U.S. patent application Ser. No. 14/911,213, filed February 10, 2016 (now U.S. Pat. No. 9,838,767), was the national stage entry of international application PCT/US2013/036804, which has an international filing date of April 16, 2013.
• Provisional Application: The PCT application claims priority to U.S. Provisional Application No. 61/684,286, filed on August 17, 2012. This is the earliest priority date for the invention.

This chain of applications means the technology disclosed in the '805 patent can rely on a priority date as early as August 17, 2012, for the purposes of evaluating prior art.

Patent Family Members

A patent family consists of a set of patents and patent applications filed in various countries that are related to each other through one or more priority claims. The '805 patent is part of a global patent family. A key related publication is:

• WO 2014/028069 A1: This is the publication of the international (PCT) application PCT/US2013/036804. This single international filing served as the basis for seeking patent protection in multiple jurisdictions, including the United States.

Other national and regional patent applications may exist that are part of this family, although they are not listed in the provided information. A comprehensive search of international patent databases would be required to identify all family members.

Defensive Disclosure and Prior Art Document

Pertaining to U.S. Patent No. 10,419,805: "Data service"

Publication Date: May 10, 2026
Author: Advanced Research Division, Defensive Publishing Initiative
Abstract: This document discloses a series of technical implementations, variations, and applications derived from the architectural principles described in U.S. Patent No. 10,419,805. The purpose of this disclosure is to place these concepts into the public domain, thereby establishing prior art against future patent applications claiming these or obvious variations thereof. The described embodiments expand upon the core concepts of a modular, service-oriented architecture for content aggregation in a client device by exploring alternative components, novel operational domains, integration with emerging technologies, and specialized functional modes.

---

Axis 1: Material & Component Substitution

1.1. Microservice-Based Content Aggregation Framework

• Enabling Description: The monolithic "internal content provider module" is decomposed into a set of independent, containerized microservices. A central API Gateway service, acting as the primary entry point for the User Interface Application, routes requests to specific microservices (e.g., a VOD-Service, an EPG-Service, a LiveTV-Service). These microservices are analogous to the original "subservices" but operate as fully independent processes, potentially written in different programming languages (e.g., Go for high-concurrency I/O, Python for data processing). Communication between services is handled via a lightweight messaging bus like RabbitMQ or a direct gRPC protocol. This architecture allows for independent scaling, updating, and fault isolation of each content aggregation function. Each microservice manages its own set of "source plug-ins," which are dynamically loaded libraries or sidecar containers that handle the protocol-specific communication with external content providers.

• Mermaid Diagram:

  graph TD
      A[User Interface Application] --> B{API Gateway};
      B -- /vod --> C[VOD Microservice];
      B -- /epg --> D[EPG Microservice];
      B -- /live --> E[Live TV Microservice];
  
      subgraph VOD Microservice
          C --> F1[Netflix Plugin];
          C --> F2[Hulu Plugin];
          C --> F3[Local Media Plugin];
      end
  
      subgraph EPG Microservice
          D --> G1[Gracenote Plugin];
          D --> G2[OTA ATSC Plugin];
      end
  
      subgraph Live TV Microservice
          E --> H1[Cable Tuner Plugin];
          E --> H2[IPTV Stream Plugin];
      end
  

1.2. GraphQL-based Data Federation Layer

• Enabling Description: The communication protocol between the primary application layer and the various subservices is implemented using a GraphQL Federation Gateway. Instead of each subservice exposing a RESTful API, they each run as a GraphQL service with a defined schema for the data they provide (e.g., EPG data, VOD metadata). The Federation Gateway combines these individual schemas into a single, unified data graph. The client-side "internal content provider module" can then make a single, complex query to the Gateway to fetch all necessary data from multiple subservices simultaneously. This eliminates the "N+1" query problem, reduces network chattiness, and allows the client application to request only the specific data fields it needs, thereby optimizing data transfer for low-bandwidth environments.

• Mermaid Diagram:

  sequenceDiagram
      participant App as UI Application
      participant Gateway as GraphQL Federation Gateway
      participant VOD as VOD Subservice
      participant EPG as EPG Subservice
  
      App->>Gateway: Query { nowPlaying { title }, recommendations { title, posterUrl } }
      Gateway->>EPG: Resolve nowPlaying { title }
      EPG-->>Gateway: nowPlaying Data
      Gateway->>VOD: Resolve recommendations { title, posterUrl }
      VOD-->>Gateway: recommendations Data
      Gateway-->>App: Combined JSON Response
  

1.3. WebAssembly (WASM) Plugin Architecture

• Enabling Description: The "source plug-ins" are compiled to WebAssembly (WASM) bytecode instead of being native-code libraries. The data service runtime includes a secure, sandboxed WASM execution environment. This approach provides significant advantages:

  1. Portability: A single WASM plugin binary can run on any "Intelligent TV" platform (e.g., ARM-based, x86-based) that includes a WASM runtime, eliminating the need for platform-specific compilation.
  2. Security: The WASM sandbox restricts the plugin's access to the underlying system, preventing a buggy or malicious plugin from compromising the entire device.
  3. Dynamic Loading: New plugins can be securely downloaded and hot-loaded from an application store without requiring a full system firmware update. The subservice communicates with the WASM module through a well-defined memory interface for passing data requests and receiving results.

• Mermaid Diagram:

  graph TD
      subgraph Data Service
          A[Media Subservice] -- WASI Call --> B{WASM Runtime};
          B -- Memory Buffer I/O --> C[Plugin.wasm];
      end
      C -- HTTP/Socket --> D[External Content API];
      D --> C;
      C --> B;
      B --> A;
      A --> E[UI Application];
  

---

Axis 2: Operational Parameter Expansion

2.1. Industrial IoT Data Aggregation at Scale

• Enabling Description: The architecture is scaled up for an industrial control system dashboard. The "Intelligent TV" is a large display in a factory control room. The "subservices" are specialized for industrial data types: TimeSeries-Subservice for sensor data, Alarm-Subservice for critical alerts, and Video-Subservice for security cameras. "Source plug-ins" are protocols like Modbus, OPC-UA, and RTSP. The system is designed for high-throughput, low-latency ingestion of data from thousands of endpoints. The TimeSeries-Subservice plugin for OPC-UA polls PLCs every 100ms, aggregates the data into 1-second windows, and pushes it to a time-series database (e.g., InfluxDB). The UI module then queries this database to render real-time dashboards and historical trend charts.

• Mermaid Diagram:

  flowchart LR
      subgraph Factory Floor
          A[PLC 1] -- Modbus --> P1(Modbus Plugin)
          B[Sensor Array] -- OPC-UA --> P2(OPC-UA Plugin)
          C[IP Camera] -- RTSP --> P3(RTSP Plugin)
      end
  
      subgraph Control Room System
          P1 --> S1[TimeSeries Subservice]
          P2 --> S1
          P3 --> S2[Video Subservice]
  
          S1 --> DB[(Time-Series DB)]
          S2 --> VMS(Video Management System)
  
          UI[Control Dashboard] --> S1
          UI --> S2
      end
  

2.2. Sub-Sea Remote Operated Vehicle (ROV) Control System

• Enabling Description: The architecture is adapted for an ROV operating in extreme sub-sea environments with high pressure and low-bandwidth, high-latency acoustic communication links. The "Intelligent TV" is the pilot's console on the support vessel. A Sonar-Subservice uses a "CHIRP Sonar Plugin" to process acoustic data. A Telemetry-Subservice uses a custom "Acoustic-Modem Plugin" to receive vehicle health data (pressure, battery, thruster status). The plugins are designed with aggressive data compression (e.g., delta compression for telemetry) and state-synchronization protocols tolerant of packet loss. The Telemetry-Subservice maintains a predictive model of the ROV's state, updating the UI instantly and correcting when a new data packet arrives, mitigating the effects of latency.

• Mermaid Diagram:

  sequenceDiagram
      participant PilotConsole as Pilot Console (TV)
      participant TelemetrySvc as Telemetry Subservice
      participant AcousticPlugin as Acoustic Modem Plugin
      participant ROV as Remote Operated Vehicle
  
      loop Data Poll Cycle (High Latency)
          PilotConsole->>TelemetrySvc: Request State Update
          TelemetrySvc->>AcousticPlugin: Send(Poll Command)
          AcousticPlugin-->>ROV: (Acoustic Transmission)
          ROV-->>AcousticPlugin: (Acoustic Response)
          AcousticPlugin->>TelemetrySvc: Receive(Telemetry Packet)
          TelemetrySvc->>PilotConsole: Push Updated State
      end
  

---

Axis 3: Cross-Domain Application

3.1. Aerospace: Integrated Vehicle Health Management (IVHM)

• Enabling Description: In an aircraft cockpit, the '805 architecture is used for an IVHM system. The "Intelligent TV" is a Multi-Function Display (MFD). An Engine-Subservice uses an "ARINC 429 Plugin" to read data from engine FADECs. A Navigation-Subservice uses a "GPS/INS Plugin" for positioning data. A Weather-Subservice uses a "SATCOM Plugin" to download real-time graphical weather data. The "internal content provider module" is a flight management application that synthesizes this data, overlaying engine performance metrics on a moving map with real-time weather, providing pilots with a unified situational awareness display.

• Mermaid Diagram:

  graph TD
      subgraph Aircraft Systems
          A[Engine 1 FADEC] --> B[ARINC 429 Bus];
          C[Engine 2 FADEC] --> B;
          D[GPS/INS Unit] --> E[Avionics Bus];
          F[SATCOM Antenna] --> G[Datalink Unit];
      end
  
      subgraph IVHM Computer
          H(ARINC 429 Plugin) --> I[Engine Subservice];
          J(GPS/INS Plugin) --> K[Navigation Subservice];
          L(SATCOM Plugin) --> M[Weather Subservice];
          B --> H;
          E --> J;
          G --> L;
      end
  
      I --> N[Flight Management App];
      K --> N;
      M --> N;
  
      N --> O[Cockpit MFD];
  

3.2. AgTech: Precision Farming Decision Support System

• Enabling Description: A farm management platform uses this architecture to provide decision support. The "Intelligent TV" is a dashboard on a farmer's tablet. A Soil-Subservice uses a "LoRaWAN Plugin" to collect data from a distributed network of wireless soil moisture and nutrient sensors. A Weather-Subservice uses a "Weather.com API Plugin" to get forecast data. A Imagery-Subservice uses an "FTP Plugin" to retrieve NDVI (Normalized Difference Vegetation Index) maps from a drone imaging provider. The "internal content provider module" is an analytics application that fuses these data streams to generate a real-time field health map, recommending specific irrigation or fertilization actions for different zones in the field.

• Mermaid Diagram:

  graph TD
      A[Soil Sensors] -- LoRaWAN --> B(LoRaWAN Plugin);
      C[Weather.com] -- REST API --> D(API Plugin);
      E[Drone Data FTP] -- FTP --> F(FTP Plugin);
  
      B --> G[Soil Subservice];
      D --> H[Weather Subservice];
      F --> I[Imagery Subservice];
  
      G --> J[Farm Analytics App];
      H --> J;
      I --> J;
  
      J --> K[Farmer's Tablet UI];
  

3.3. Automotive: In-Vehicle Infotainment (IVI) & Telematics

• Enabling Description: A modern vehicle's IVI system implements this architecture. The "Intelligent TV" is the center console touchscreen. A Vehicle-Bus-Subservice uses a "CAN/LIN Plugin" to access vehicle data like speed, fuel level, and tire pressure. A Media-Subservice has "Spotify Plugin" and "FM-Tuner Plugin" to handle audio. A Navigation-Subservice has a "TomTom Traffic Plugin" and a "GPS Plugin." The "internal content provider module" is the main HMI application, which can display navigation directions on the instrument cluster while showing media information on the center screen, and can automatically lower the music volume when the navigation subservice issues a voice prompt.

• Mermaid Diagram:

  classDiagram
    direction LR
    class IVI_HMI_Application {
      +displayMap()
      +playMedia()
      +showVehicleStatus()
    }
    class VehicleBusSubservice {
      +getSpeed()
      +getFuelLevel()
    }
    class MediaSubservice {
      +getCurrentTrack()
      +setSource(plugin)
    }
    class NavigationSubservice {
      +getCurrentRoute()
      +getETA()
    }
    class CAN_Plugin {
      +read_can_frame(id)
    }
    class Spotify_Plugin {
      +api_call(endpoint)
    }
    class GPS_Plugin {
      +read_nmea_sentence()
    }
  
    IVI_HMI_Application --|> VehicleBusSubservice
    IVI_HMI_Application --|> MediaSubservice
    IVI_HMI_Application --|> NavigationSubservice
    VehicleBusSubservice "1" *-- "1..*" CAN_Plugin : uses
    MediaSubservice "1" *-- "1..*" Spotify_Plugin : uses
    NavigationSubservice "1" *-- "1..*" GPS_Plugin : uses
  

---

Axis 4: Integration with Emerging Tech

4.1. AI-Driven Predictive Content Caching

• Enabling Description: The system incorporates an AI-Prediction-Subservice which monitors user viewing habits, time of day, EPG data, and even external event calendars (e.g., major sports events). It uses a machine learning model (e.g., a recurrent neural network) to predict what content the user is likely to watch next. This subservice doesn't have its own plugins but instead issues commands to other subservices. For example, it might command the VOD-Subservice to use its "Netflix Plugin" to pre-cache the first 10 minutes of the next episode of a series the user is binge-watching, ensuring an instant start when the user selects it.

• Mermaid Diagram:

  sequenceDiagram
      participant UI
      participant AI_Service
      participant VOD_Service
      participant EPG_Service
  
      UI->>VOD_Service: playEpisode(series_X, ep_2)
      VOD_Service->>AI_Service: logEvent(user, series_X, ep_2)
      EPG_Service->>AI_Service: logEvent(user, channel_Y, time)
  
      loop Predictive Analysis
          AI_Service->>AI_Service: model.predict(user_history)
      end
      Note right of AI_Service: Prediction: User likely to watch series_X, ep_3 next
      AI_Service->>VOD_Service: command: preCache(series_X, ep_3)
      VOD_Service->>VOD_Service: Initiates background download via plugin
  
      UI->>VOD_Service: playEpisode(series_X, ep_3)
      Note over VOD_Service: Content is already cached.
      VOD_Service-->>UI: Start playback immediately
  

4.2. IoT-Driven Ambient Experience Adaptation

• Enabling Description: The Intelligent TV is part of a broader IoT ecosystem. A new Ambient-Subservice is added, which uses a "Smart Home Hub Plugin" (e.g., for Home Assistant or a proprietary hub) to subscribe to state changes from various sensors. When a user starts a movie via the VOD-Subservice, the UI application notifies the Ambient-Subservice. This service then commands the smart hub to dim the lights, close the blinds, and adjust the thermostat to a "movie mode" temperature. The sensor data is treated as just another content stream to be aggregated and acted upon by the system's logic.

• Mermaid Diagram:

  flowchart TD
      A[User selects "Play Movie" on UI] --> B{UI Application};
      B -- "play_event" --> C[VOD Subservice];
      B -- "context_change: movie" --> D[Ambient Subservice];
  
      C --> E[Video Player];
  
      subgraph Smart Home
          D --> F(Smart Hub Plugin);
          F -- "set_light_brightness(10%)" --> G[Smart Lights];
          F -- "set_blinds_position(closed)" --> H[Motorized Blinds];
      end
  

---

Axis 5: The "Inverse" or Failure Mode

5.1. Graceful Degradation for Low-Bandwidth Networks

• Enabling Description: The system includes a Network-Monitor-Subservice that constantly measures available bandwidth and latency. When it detects poor network conditions (e.g., bandwidth drops below 5 Mbps), it broadcasts a "low_bandwidth_mode" system state. The VOD-Subservice, upon receiving this state change, instructs all its streaming plugins to request lower-bitrate streams (e.g., 480p instead of 4K). The EPG-Subservice tells its "Internet-EPG Plugin" to stop fetching rich media (posters, trailers) and only fetch essential text data. The UI module, also subscribed to this state, renders a simplified interface without high-resolution images to conserve bandwidth.

• Mermaid Diagram:

  stateDiagram-v2
      [*] --> HighBandwidth
      HighBandwidth --> LowBandwidth: Network Degraded
      LowBandwidth --> HighBandwidth: Network Restored
  
      state HighBandwidth {
          VOD_Service: Requests 4K streams
          EPG_Service: Fetches full metadata
          UI_Module: Renders rich graphics
      }
  
      state LowBandwidth {
          VOD_Service: Requests 480p streams
          EPG_Service: Fetches text-only data
          UI_Module: Renders simplified UI
      }
  

5.2. Fail-Safe Redundancy for Critical Data Streams

• Enabling Description: This variation is designed for a system where data availability is critical, such as a remote security monitoring station. The Video-Subservice is configured with both a primary "Fiber-Optic Plugin" and a secondary "5G-Cellular Plugin" for each camera feed. The subservice continuously health-checks the primary plugin by monitoring for data packets. If a packet is not received within a specified timeout (e.g., 500ms), it immediately activates the secondary plugin to take over the stream, ensuring minimal interruption of the video feed to the operator. It also raises an alert in the UI, indicating that it is now operating on the backup connection.

• Mermaid Diagram:

  graph TD
      subgraph Data Sources
          A[Camera via Fiber] --> P1(Fiber Optic Plugin);
          B[Camera via 5G] --> P2(5G Cellular Plugin);
      end
  
      subgraph Redundant Subservice
          P1 -- Primary Stream --> S1{Video Subservice};
          P2 -- Backup Stream --> S1;
          S1 -- Health Check --> P1;
      end
  
      S1 -- Video Data --> UI[Operator Console];
      S1 -- Alert --> UI;
  
      style P1 fill:#9f9,stroke:#333,stroke-width:2px
      style P2 fill:#f99,stroke:#333,stroke-width:2px
  

---

Combination Prior Art Scenarios

1. Combination with DLNA/UPnP for Local Media Aggregation: The Media-Subservice is designed to be fully compliant with the Digital Living Network Alliance (DLNA) and Universal Plug and Play (UPnP A/V) open standards. An integrated "UPnP Control Point Plugin" is included, which, upon activation by the subservice, uses the Simple Service Discovery Protocol (SSDP) to discover all DLNA-certified Digital Media Servers (DMS) on the local network (e.g., NAS drives, personal computers running Plex). Once a DMS is discovered, the plugin queries its Content Directory Service (CDS) to retrieve a browseable hierarchy of the available media, which the subservice then formats according to its internal data model and presents to the "internal content provider module" for display in a unified "My Network" section of the UI.

2. Combination with Matter for Smart Home Control: The system is extended to act as a Smart Home controller by incorporating a Home-Automation-Subservice. This subservice includes a "Matter Controller Plugin" built upon the open-source Matter (formerly Project CHIP) SDK. This plugin manages a Thread or Wi-Fi network to securely commission and control Matter-compliant devices (lights, switches, thermostats) from any manufacturer. The status of these devices (e.g., light on/off, temperature) is treated as a stream of "content." The "internal content provider module" can then render interactive widgets on the TV screen, allowing a user to control their smart home devices using the TV remote, effectively turning the television into a central home hub.

3. Combination with ActivityPub for Decentralized Social Media Feeds: A Social-Subservice is created to aggregate content from the decentralized "Fediverse." This service utilizes an "ActivityPub Plugin" which acts as a client for the W3C ActivityPub protocol. The user can authenticate with their accounts from different Fediverse platforms (e.g., Mastodon, Pixelfed, PeerTube). The plugin polls the user's home feeds from these services, receiving content (posts, images, videos) formatted as ActivityStreams 2.0 objects. The Social-Subservice normalizes this data into its own data model and passes it to the main UI application, which can then display a unified, chronologically-sorted feed of social updates alongside traditional media content, all without relying on proprietary, centralized social media APIs.