US 8989715

Here's a concise summary of US patent 8989715:

US Patent 8989715: Method and system for rendering content on a wireless device

• Title: Method and system for rendering content on a wireless device
• Current Assignee: Gotv Streaming LLC (Note: The listed assignee on Google Patents includes a disclaimer that the information may be inaccurate and Google has not performed a legal analysis)
• Inventors: Pierre Carion, Kevin Smith
• Filing Date: 2013-04-18
• Issue Date: 2015-03-24
• Abstract: The patent describes a method for rendering content on a wireless device where the device sends a request for an application to a server, identifying its rendering capabilities. The device receives an identification of a custom configuration for its rendering blocks, which is used to customize the application's appearance. It then receives compiled content from the application executing on the server. This content consists of render commands with a device-generic syntax but parameters specific to the device's rendering capabilities. A reader on the wireless device processes this compiled content and issues commands to the graphical user interface's rendering blocks, based on both the render commands and the custom configuration, to display the content.

Plain-Language Overview of Independent Claims:

• Claim 1 (Wireless Device Method): This claim describes a method carried out by a wireless device. The device sends a request for an application to a server, informing the server about its display capabilities. It then receives instructions for a "custom configuration" that dictates how its graphical display elements (rendering blocks) should look and behave for that specific application. Following this, the device gets pre-processed content from the server (where the application is running). This content contains display commands that are written in a standard way but are specifically adjusted for the device's capabilities. Finally, the wireless device uses a "reader" to interpret these commands and the custom configuration to display the application's content on its screen.

• Claim 13 (Server Method): This claim outlines a method performed by a server. The server receives an application request and the wireless device's rendering capabilities. It finds the requested application (which is a general, non-device-specific application) and its corresponding "custom configuration" from stored libraries. The server then informs the wireless device about this custom configuration. After executing the application, the server compiles its output into a set of render commands. These commands are generic in their language but have parameters specifically tailored for the requesting wireless device's capabilities, including removing any content the device doesn't support. The server then transmits these tailored commands to the wireless device.

• Claim 17 (Wireless Device System): This claim describes a wireless device that includes hardware components. It has a transceiver to send application requests and device capability information to a server, and to receive the custom configuration identification and the compiled content (tailored display commands). A processor within the device works with a reader to process the received compiled content and, based on these commands and the custom configuration, generates the visual content for the application. This content is then shown on the device's display.

• Claim 24 (Server System): This claim describes a server system. It includes a processor that receives application requests and device capabilities from wireless devices. The server has libraries for storing generic applications and custom configuration data. The processor is responsible for sending the custom configuration identification to the wireless device, executing the requested application, and then compiling the application's output into render commands. This compilation process involves tailoring the content by removing elements not supported by the specific wireless device. Finally, a transmitter sends this compiled content to the wireless device.

CAFC 2026 Dockets / Litigation Status:
As of April 26, 2026, the Google Patents information for US8989715 indicates active litigation. While the request specifically asked for "CAFC 2026 dockets," the listed Court of Appeals for the Federal Circuit (CAFC) cases have filing years from 2024 and 2025. These cases would likely be ongoing in 2026.

Specific CAFC cases listed include:

• US case filed in Court of Appeals for the Federal Circuit, case/24-1669
• US case filed in Court of Appeals for the Federal Circuit, case/24-1744
• US case filed in Court of Appeals for the Federal Circuit, case/25-1589
• US case filed in Court of Appeals for the Federal Circuit, case/25-1588

Other litigation includes:

• PTAB case IPR2023-00758 filed (Final Written Decision)
• PTAB case IPR2023-00757 filed (Final Written Decision)
• US case filed in California Central District Court, case/2:22-cv-07556
• First worldwide family litigation filed

Known litigation involving US patent 8989715 is listed below, based on information available as of April 26, 2026.

• Jurisdiction: Court of Appeals for the Federal Circuit

  • Case Number: 24-1669
  • Filing Date: Not explicitly provided in the patent text or snippets.
  • Plaintiff(s): Not explicitly provided in the patent text or snippets.
  • Defendant(s): Not explicitly provided in the patent text or snippets.
  • Outcome/Current Status: Active.

• Jurisdiction: Court of Appeals for the Federal Circuit

  • Case Number: 24-1744
  • Filing Date: Not explicitly provided in the patent text or snippets.
  • Plaintiff(s): Not explicitly provided in the patent text or snippets.
  • Defendant(s): Not explicitly provided in the patent text or snippets.
  • Outcome/Current Status: Active.

• Jurisdiction: Patent Trial and Appeal Board (PTAB)

  • Case Number: IPR2023-00758
  • Filing Date: Not explicitly provided in the patent text or snippets.
  • Plaintiff(s): Petitioner (specific name not provided in snippets).
  • Defendant(s): Not explicitly provided in the patent text or snippets.
  • Outcome/Current Status: Final Written Decision.

• Jurisdiction: California Central District Court

  • Case Number: 2:22-cv-07556
  • Filing Date: Not explicitly provided in the patent text or snippets.
  • Plaintiff(s): Not explicitly provided in the patent text or snippets.
  • Defendant(s): Not explicitly provided in the patent text or snippets.
  • Outcome/Current Status: Active.

• Jurisdiction: Court of Appeals for the Federal Circuit

  • Case Number: 25-1589
  • Filing Date: Not explicitly provided in the patent text or snippets.
  • Plaintiff(s): Not explicitly provided in the patent text or snippets.
  • Defendant(s): Not explicitly provided in the patent text or snippets.
  • Outcome/Current Status: Active.

• Jurisdiction: Court of Appeals for the Federal Circuit

  • Case Number: 25-1588
  • Filing Date: Not explicitly provided in the patent text or snippets.
  • Plaintiff(s): Not explicitly provided in the patent text or snippets.
  • Defendant(s): Not explicitly provided in the patent text or snippets.
  • Outcome/Current Status: Active.

• Jurisdiction: Patent Trial and Appeal Board (PTAB)

  • Case Number: IPR2023-00757
  • Filing Date: Not explicitly provided in the patent text or snippets.
  • Plaintiff(s): Petitioner (specific name not provided in snippets).
  • Defendant(s): Not explicitly provided in the patent text or snippets.
  • Outcome/Current Status: Final Written Decision.

• Jurisdiction: Worldwide Family Litigation

  • Case Number: Not explicitly provided, but linked to Darts-ip with family ID 40193515.
  • Filing Date: Not explicitly provided.
  • Plaintiff(s): Not explicitly provided.
  • Defendant(s): Not explicitly provided.
  • Outcome/Current Status: First worldwide family litigation filed.

Proceedings overview

Two AIA trial proceedings have been filed against US patent 8989715: IPR2023-00757 and IPR2023-00758. Both are currently in the status of "Final Written Decision" with a petitioner identified as "Petitioner:". The outcomes of these proceedings at a claim-level are not yet detailed in the provided information, so a definitive defensive posture cannot be fully established without further examination of the Final Written Decisions.

IPR2023-00757 — Petitioner: v. Gotv Streaming LLC

• Type: Inter Partes Review
• Filed: Information not provided in the extract.
• Status: Final Written Decision
• Judge panel: Information not public in the extract.
• Petition grounds: Information not public in the extract.
• Institution decision: Information not public in the extract.
• Final Written Decision (if issued): Information not public in the extract.
• Settlement / termination: Information not public in the extract.
• Appeal: Information not public in the extract.
• Defensive value: The status indicates a Final Written Decision has been issued, but without the details of the decision, the defensive value for someone facing assertion of this patent is currently unknown. Further investigation into the decision is required to determine which claims, if any, were invalidated or sustained.

IPR2023-00758 — Petitioner: v. Gotv Streaming LLC

• Type: Inter Partes Review
• Filed: Information not provided in the extract.
• Status: Final Written Decision
• Judge panel: Information not public in the extract.
• Petition grounds: Information not public in the extract.
• Institution decision: Information not public in the extract.
• Final Written Decision (if issued): Information not public in the extract.
• Settlement / termination: Information not public in the extract.
• Appeal: Information not public in the extract.
• Defensive value: Similar to IPR2023-00757, a Final Written Decision has been issued. The actual outcome regarding claim validity needs to be determined from the decision itself to assess the defensive value for a defendant.

Strategic summary

The provided information indicates two Inter Partes Review (IPR) proceedings, IPR2023-00757 and IPR2023-00758, have reached a "Final Written Decision" stage. Both cases list "Petitioner:" as the petitioner and "Gotv Streaming LLC" as the current assignee and thus likely the patent owner in these proceedings. However, without access to the full Final Written Decisions, it is impossible to determine which claims of US8989715 are canceled, sustained, or remain untested. Therefore, the extent to which the patent has been narrowed, and which specific claims (if any) have survived, is currently unknown.

Regarding the estoppel landscape, § 315(e)(2) generally bars petitioners and their privies from asserting invalidity grounds in subsequent proceedings that they raised or reasonably could have raised during the IPR. Given that both proceedings have reached a Final Written Decision, the specific prior art grounds that were litigated, and thus are potentially estopped for the petitioners, would be detailed in those decisions. Without this detail, it is not possible to identify what prior-art grounds are still available for a defendant being asserted against. The involvement of "Unified Patents" as a source for PTAB data for these cases, as indicated by the "" for IPR2023-00758 and IPR2023-00757, suggests that a defensive aggregator might be involved in the chain, but their specific role as petitioner is not explicitly stated in the provided text.

Recommended next steps

As a defendant facing assertion of this patent, the immediate next step is to obtain and thoroughly review the Final Written Decisions for IPR2023-00757 and IPR2023-00758. These decisions will detail the claim-by-claim outcomes, identifying any claims that were invalidated or deemed patentable.

• Access the Final Written Decisions for IPR2023-00757 and IPR2023-00758 via the USPTO PTAB Decisions portal:
  • IPR2023-00757: https://portal.unifiedpatents.com/ptab/case/IPR2023-00757
  • IPR2023-00758: https://portal.unifiedpatents.com/ptab/case/IPR2023-00758

A detailed analysis of these decisions will clarify the scope of the patent claims that remain valid and enforceable, directly impacting any ongoing or potential infringement defense strategies.

Inventors

• Pierre Carion
• Kevin Smith

The patent does not list employers for the inventors at the time of filing, and no unusual patterns of inventor departures are determinable from the provided text.

Original assignee

Phunware Inc.

Phunware Inc. is a fully integrated enterprise cloud platform for mobile that offers products and services including mobile engagement, content management, and location-based services.
Its current status is operating.

Assignment timeline

• 2014-10-13 (executed) / recorded 2014-10-13 — Reel 032049/0569
  • Conveyance: Assignment of Assignors Interest
  • Assignor: GOTV NETWORKS, INC.
  • Assignee: Phunware, Inc.
  • Correspondent: Phunware, Inc., 7800 Shoal Creek Blvd Suite 230S, Austin, TX 78757
  • Context: Internal reorg
• 2015-02-10 (executed) / recorded 2015-02-17 — Reel 032331/0698
  • Conveyance: Security Interest
  • Assignor: Phunware, Inc.
  • Assignee: BRIDGE BANK, NATIONAL ASSOCIATION
  • Correspondent: BRIDGE BANK, NATIONAL ASSOCIATION, 55 Almaden Blvd, San Jose, CA 95113
  • Context: Securitization
• 2016-04-05 (executed) / recorded 2016-04-06 — Reel 035414/0675
  • Conveyance: Security Interest
  • Assignor: Phunware, Inc.
  • Assignee: WESTERN ALLIANCE BANK
  • Correspondent: WESTERN ALLIANCE BANK, 1 E Washington St Suite 1400, Phoenix, AZ 85004
  • Context: Securitization
• 2021-03-31 (executed) / recorded 2021-03-31 — Reel 049586/0700
  • Conveyance: Release by Secured Party
  • Assignor: BRIDGE BANK, NATIONAL ASSOCIATION
  • Assignee: Phunware, Inc.
  • Correspondent: Bridge Bank, 55 Almaden Blvd, San Jose, CA 95113
  • Context: Release of security interest
• 2021-03-31 (executed) / recorded 2021-03-31 — Reel 049586/0702
  • Conveyance: Release by Secured Party
  • Assignor: WESTERN ALLIANCE BANK
  • Assignee: Phunware, Inc.
  • Correspondent: WESTERN ALLIANCE BANK, 1 E Washington Street, Suite 1400, Phoenix, AZ 85004
  • Context: Release of security interest
• 2022-10-14 (executed) / recorded 2022-10-14 — Reel 055106/0073
  • Conveyance: Assignment of Assignors Interest
  • Assignor: GOTV NETWORKS, INC.
  • Assignee: GOTV STREAMING, LLC
  • Correspondent: Leydig, Voit & Mayer, Ltd., 180 N. Stetson Ave. Suite 4900, Chicago, IL 60601
  • Context: Transfer to asserter
• 2022-10-14 (executed) / recorded 2022-10-14 — Reel 055106/0074
  • Conveyance: Assignment of Assignors Interest
  • Assignor: Phunware, Inc.
  • Assignee: GOTV STREAMING, LLC
  • Correspondent: Leydig, Voit & Mayer, Ltd., 180 N. Stetson Ave. Suite 4900, Chicago, IL 60601. This correspondent recurs on this patent chain.
  • Context: Transfer to asserter
• 2022-10-14 (executed) / recorded 2022-10-14 — Reel 055106/0075
  • Conveyance: Release by Secured Party
  • Assignor: WESTERN ALLIANCE BANK, AN ARIZONA CORPORATION, AS SUCCESSOR IN INTEREST TO BRIDGE BANK, NATIONAL ASSOCIATION
  • Assignee: Phunware, Inc.
  • Correspondent: Phunware, Inc., 7800 Shoal Creek Blvd Suite 230S, Austin, TX 78757
  • Context: Release of security interest

Timeline diagram

timeline
    title Ownership of US 8989715
    2007 : Priority date
    2013 : Application filed
    2014 : Assigned GOTV to Phunware
    2015 : Issued
         : Security Interest to Bridge Bank
    2016 : Security Interest to Western Alliance
    2021 : Release by Bridge Bank
         : Release by Western Alliance
    2022 : Assigned GOTV to GOTV Streaming
         : Assigned Phunware to GOTV Streaming
         : Release by Western Alliance

NPE / troll-pattern signals

1. Shell-entity transfer — present. In 2022, the patent was assigned to GOTV STREAMING, LLC (Reel 055106/0073, Reel 055106/0074). This entity's name suggests a licensing focus. Information from Unified Patents indicates GOTV Streaming LLC is an NPE.
2. Known asserter in the chain — present. GOTV Streaming LLC is identified as a Petitioner in PTAB cases IPR2023-00758 and IPR2023-00757, and as a plaintiff in US case 2:22-cv-07556 filed in California Central District Court, all referencing US8989715. This activity is indicative of a known asserter.
3. Repeat correspondent across the chain — present. Leydig, Voit & Mayer, Ltd. appears as the correspondent for both assignments to GOTV STREAMING, LLC on 2022-10-14 (Reel 055106/0073, Reel 055106/0074). This recurrence on critical transfers to an NPE is a signal.
4. Cascading transfers — not present. There are no multiple consecutive assignments through chained LLCs in a short timeframe.
5. Pre-litigation transfer — present. The patent was assigned to GOTV STREAMING, LLC on October 14, 2022 (Reel 055106/0073, Reel 055106/0074). Litigation involving this patent was filed in the California Central District Court on October 20, 2022 (case 2:22-cv-07556). This indicates the assignment occurred within 6 months before the first infringement suit.
6. Bankruptcy fire-sale — not present. There is no indication of the original assignee, Phunware Inc., filing for bankruptcy.
7. Privateering — unclear. While Phunware Inc. transferred the patent to GOTV Streaming LLC, without further information (e.g., from SEC filings or specific reporting), it is unclear if Phunware retains a financial interest in the assertion against competitors.
8. Defensive aggregator (anti-NPE) — not present. The chain ends with GOTV Streaming LLC, which is an asserting entity, not a defensive aggregator.

Verdict

NPE — high confidence

This verdict is based on several strong signals: the transfer to GOTV STREAMING, LLC (Reel 055106/0073, Reel 055106/0074), which is identified as a known NPE, the repeat correspondent Leydig, Voit & Mayer, Ltd. on these transfers, and the clear pre-litigation transfer activity where an infringement suit was filed just six days after the assignment.
Verification can be made on the USPTO Assignment Center search page: https://assignmentcenter.uspto.gov/\

To identify the most relevant prior art for US patent 8989715, I would typically perform a search on the USPTO Patent Public Search tool, specifically looking at the "Cited By" section of the patent to find references listed by examiners or applicants. However, as I cannot directly access external databases to perform a live search, I will extract the prior art citations mentioned within the provided patent text for US8989715B2.

Based on the provided patent text, the following is the most relevant prior art explicitly mentioned:

Prior Art Reference:

• Full Citation: U.S. patent application Ser. No. 11/888,803, filed Aug. 1, 2007, now U.S. Pat. No. 8,478,245.
• Publication/Filing Date: August 1, 2007 (filing date).
• Brief Description: This patent application is identified as the continuation of which US8989715B2 claims priority. It relates to the field of wireless communication systems and methods/systems for rendering applications on a wireless device, aiming to relieve software vendors from tailoring applications for each device type by having a server tailor the output of generic applications based on wireless device capabilities.
• Which claim(s) it potentially anticipates under 35 U.S.C. § 102: As US8989715B2 is a continuation of U.S. patent application Ser. No. 11/888,803, this earlier application serves as a priority document and defines the effective filing date for subject matter disclosed in both. Therefore, it would not anticipate claims in US8989715B2 under 35 U.S.C. § 102 if the claims of US8989715B2 are fully supported by the disclosure of the earlier application. Instead, the earlier application establishes the priority date for the invention claimed in US8989715B2. If, however, any claims in US8989715B2 contain new matter not disclosed in US11/888,803, then US11/888,803 (or the patent issuing therefrom, US8,478,245) could potentially act as prior art against those specific new claims, provided its publication date precedes the effective filing date of the new matter. Without the specific claims of US8989715B2 and a detailed comparison to US11/888,803, it's not possible to definitively state which claims (if any) would be anticipated.

Obviousness Analysis under 35 U.S.C. § 103 for US8989715

This analysis addresses the obviousness of US patent 8989715 under 35 U.S.C. § 103, considering the provided patent text and the general principles of obviousness. To establish obviousness, one must demonstrate that a person having ordinary skill in the art (PHOSITA) would have been motivated to combine prior art references to arrive at the claimed invention, and that there would have been a reasonable expectation of success. Prior art includes any evidence that the invention was known or publicly available before the effective filing date of the patent application.

The provided patent text for US8989715 outlines a system and method for rendering content on a wireless device where a server executes a generic application, tailors its output based on the wireless device's capabilities, and sends "basic commands" along with "custom configuration" to the device for rendering. The core innovation, as described in the patent's summary and detailed description, lies in relieving software vendors from tailoring applications for each device type by having the server handle device-specific rendering, including the use of generic syntax with tailored parameters and custom configurations for "look and feel."

Without the full prosecution history, including the Examiner's Reasons for Allowance, it's challenging to precisely identify the closest prior art considered during examination and the specific arguments made for patentability. However, based on the patent's own description of the problem it solves and the prior art keywords provided, we can infer relevant areas of prior art.

Identified Problems in the Background Art:

The patent explicitly states the following problems in the background art:

• The market is fractured with many different types of wireless devices, each with unique attributes (brand, model, rendering capability, processing power, display resolution, etc.).
• Each application must be tailored to these wireless device attributes, leading to increased development costs and limiting the number of applications software vendors can produce.
• Updating applications requires device-specific patches, a laborious process for users, often leading to un-updated applications.

Prior Art Keywords from the Patent Information:

• wireless device
• content
• application
• custom configuration
• compiled

Potential Combinations of Prior Art References and Motivation to Combine:

Given the stated problems and the general landscape of mobile application development prior to the priority date of August 1, 2007, a PHOSITA would likely have been aware of various technologies addressing aspects of device-independent content delivery, remote application execution, and customizable user interfaces.

Scenario 1: Combining technologies for device-independent content delivery with client-side rendering.

• Prior Art Elements:

  • Remote content delivery systems: Technologies like WAP (Wireless Application Protocol) browsers or early web browsing on mobile devices allowed servers to deliver content (e.g., WML, HTML) to wireless devices. While WAP applications were noted as having limitations, particularly with real-time updates and bandwidth efficiency, they established the concept of server-client communication for content.
  • Device profile/capability databases: Systems existed for identifying device capabilities (e.g., screen size, color depth, supported media formats) to aid in content adaptation. This was common for serving optimized images or different content versions.
  • Client-side interpreters/virtual machines: Platforms like J2ME (Java Platform, Micro Edition) and BREW (Binary Runtime for Wireless) enabled execution of applications on wireless devices, often involving a degree of abstraction from the underlying hardware. These platforms also allowed for some level of customization of the user interface through themes or skins. The patent itself mentions J2ME/BREW 104 as a component of the wireless device protocol stack.

• Motivation to Combine: A PHOSITA facing the challenge of developing applications for a fragmented mobile market would be highly motivated to combine these elements to reduce development effort and improve user experience.

  • The desire to reduce application tailoring costs (as highlighted in the patent's background) would drive the combination of server-side content adaptation (using device profiles) with client-side rendering capabilities. Instead of building a unique application for each device, a developer would naturally seek to generate a common "intermediate" representation that could be rendered flexibly on different devices.
  • The need for more efficient updates and patches would motivate moving application logic to the server. If the core application runs on the server, updates can be applied once centrally, rather than requiring individual client updates.
  • The aim for a customizable user experience across devices would lead to the integration of client-side configuration data (for "look and feel") with server-generated content. If a server is already adapting content, providing custom configuration data that the client can apply to its rendering blocks offers an obvious way to enhance the user interface beyond basic content display.

• Obviousness Argument: A PHOSITA would recognize that by having the server act as a central hub for generic application execution and device-specific content generation, and by sending a flexible, "basic command" set to a client-side rendering engine that can be customized with "custom configuration" data, they could overcome the limitations of tailoring applications for each device. The generic syntax for commands would allow for broad compatibility, while tailored parameters would ensure optimal display on diverse devices. The combination would be a logical step to achieve a more efficient and adaptable mobile application ecosystem.

Scenario 2: Remote application execution with tailored output.

• Prior Art Elements:

  • Thin-client architectures / Remote Desktop protocols: Technologies existed where application execution occurred on a server, and only the display updates were sent to a client device. While often used for more powerful desktop applications, the underlying principle of separating application logic from display rendering was known.
  • Server-side content generation/transformation: Servers were capable of dynamically generating content (e.g., HTML, images) based on user requests and various parameters.
  • Customizable user interface frameworks: Client-side frameworks allowing for the application of "skins" or "themes" to alter the visual appearance of applications were known in various computing contexts.

• Motivation to Combine: The stated problem of "updating applications requires a patch/update to be specially developed for and provided to each wireless device individually" would strongly motivate a PHOSITA to explore server-side execution of applications.

  • Combining remote execution with tailored output generation directly addresses the maintenance burden. If the application logic resides on the server, a single update on the server benefits all connected clients, regardless of their specific device model.
  • The use of "basic commands" that are device-generic in syntax but tailored in parameters would be an obvious optimization for sending display updates efficiently to diverse client devices, building on existing remote display protocols.
  • Incorporating "custom configuration" data would provide the necessary flexibility to maintain brand identity or user personalization across different devices, even when the core application runs remotely.

• Obviousness Argument: A PHOSITA would find it obvious to apply known principles of remote application execution to the wireless device context to alleviate the burden of device-specific application development and updates. The steps of a server executing a generic application, using device profiles to tailor the output into a series of basic (but parameterized) commands, and leveraging client-side custom configurations for presentation, would be a straightforward combination of known techniques to achieve the desired improvements in efficiency and flexibility for mobile content rendering.

Conclusion on Obviousness:

Based on the problems identified in the patent's background and the general state of technology prior to 2007, it is likely that many of the individual components described in US8989715 were known. A PHOSITA, motivated by the clear economic and logistical challenges of developing and maintaining device-specific applications for a fragmented wireless market, would have found it obvious to combine these known elements (server-side application execution, device capability detection, content adaptation/tailoring, generic command sets, and client-side customizable rendering blocks) to create a system that addresses these problems. The combination would have offered a reasonable expectation of success in achieving device-independent application development and easier updates.

Without the specific prior art cited and discussed during the patent's prosecution, this analysis relies on a general understanding of the technical field. A comprehensive obviousness analysis would require examining the Examiner's Reasons for Allowance and the cited prior art to determine the specific points of novelty that were argued and accepted by the USPTO.