CAFC Affirms PTAB Win for Netflix

The U.S. Court of Appeals for the Federal Circuit (CAFC) issued a decision today in VL Collective IP, LLC v. Netflix, Inc., affirming a Patent Trial and Appeal Board (PTAB) final written decision that found all challenged claims of a content delivery patent owned by VL Collective IP, LLC (VideoLabs) unpatentable. The court rejected VideoLabs’ argument that the Board misconstrued a key claim term, and found that neither the claim language nor the patent specification supported the narrower reading VideoLabs proposed.

VideoLabs owns U.S. Patent No. 7,440,559, which describes a system for controlling the flow of multimedia content between a content provider, referred to as a server, and a user device, referred to as a terminal. The patent discloses a content flow manager that regulates the delivery of content to a terminal based on status information received from that terminal, and in some configurations, from the server as well. At issue, Claim 1, treated as representative, recites a processor configured to receive content status information from a remote terminal and server status information regarding available content. Based on both sets of status information, the processor sends the terminal a response instructing it to perform actions that control the flow of multimedia content.

Netflix, Inc. petitioned for inter partes review (IPR) of claims 1 through 24 of the ‘559 patent on three separate grounds. It argued that the claims were anticipated by a published patent application referred to as Cassin, obvious over a combination of Cassin and a separate patent referred to as Huston, and independently obvious over Huston alone. The Board did not expressly construe any claim terms in its final written decision, noting that neither side had asked it to do so. In October 2024, the Board sided with Netflix on all three grounds, determining that claims 1 through 24 were unpatentable.

On appeal, VideoLabs raised two arguments, both centered on claim 1’s requirement that the processor send the terminal “a response to the content status that instructs the terminal to perform one or more actions” to control content flow based on the terminal and server status information. VideoLabs contended the Board implicitly construed “instructs” too broadly in finding that Cassin taught the limitation, when the term should require an affirmative order or command rather than content the terminal could simply accept or reject. VideoLabs then argued that the claimed “response to the content status” must be triggered specifically by the terminal’s transmission of content status information. It contended that Huston did not meet this standard because its response was prompted by the availability of new content at an origin server, rather than by status information supplied by the terminal. VideoLabs pointed to the specification’s description of what it called “a message sent as part of a call-and-response protocol” in support of its reading.

Moreover, VideoLabs had argued that reading “response” to require a triggering relationship was necessary to avoid rendering the term redundant with the claims’ separate “based upon” language, and pointed to dictionary definitions of “response” and “respond” in further support.

The court disagreed with VideoLabs on each point, noting that several claims, including claim 1, require the processor to receive both terminal status information and separate server status information and to base its response on both. The court found that this structure weighed against reading “content status” as necessarily the trigger for the response. The court also found that treating “based upon” as governing the content of the communication did not require “response” to mean anything more than a communication sent after the terminal transmits its content status. As the court explained, “nothing in the claims necessitates that ‘response’ means more than merely a communication sent after the terminal sends content status.”

The specification, according to the court, describes the content flow manager receiving terminal status information “periodically” and responding after both terminal and server status information have been provided, without requiring that the terminal’s transmission be the direct cause of the response. The court stated, “that the response occurs ‘after’ the content status provided by the terminal is received does not mean that the content status necessarily ‘triggers’ the response.” The court added that the dictionary definitions VideoLabs relied upon did not themselves require that a response be prompted or triggered by another action.

After rejecting VideoLabs’ construction, the court affirmed the Board’s determination that Huston rendered claims 1 through 24 obvious. Since that finding independently supported unpatentability across all challenged claims, the court found it unnecessary to reach VideoLabs’ separate argument concerning the term “instructs” and the Board’s reliance on Cassin. VideoLabs’ counsel had acknowledged during oral argument that affirmance on the Huston ground would moot the Cassin issue.

Ultimately, the court rejected VideoLabs’ remaining arguments and affirmed the Board’s decision.

Image Source: Deposit Photos
Image ID:103763568
Copyright:bigfatnapoleon