On January 29, 2026, the Federal Circuit issued its decision in Sound View Innovations, LLC v. Hulu, LLC, affirming summary judgment of noninfringement based on the required sequence of steps in a method claim. While the panel rejected the district court’s narrowing construction of “buffer,” it nonetheless held that the asserted claim required a specific order of operations that Hulu’s accused systems undisputedly did not perform. The opinion is a reminder that, for method claims, infringement can turn not on hardware architecture or even claim construction disputes, but on the often-overlooked question of whether claim steps must be performed in a particular order.
Background of the ’213 Patent and the Dispute
The asserted patent, U.S. Patent No. 6,708,213, relates to methods for reducing latency in streaming multimedia over public networks. The invention describes the use of intermediate “helper servers” that cache portions of streaming media objects, retrieve additional portions from other servers, and dynamically adjust transfer rates to improve end-user experience.
Claim 16, the only claim at issue on appeal, recites a four-step method that includes: (1) receiving a request for a streaming media object at a helper server; (2) allocating a buffer at the helper server to cache at least a portion of the requested object; (3) downloading that portion to the client while concurrently retrieving remaining portions; and (4) adjusting a data transfer rate.
Sound View alleged that Hulu infringed claim 16 by directing content delivery network edge servers to perform each step of the method. The case has a long procedural history, including a prior Federal Circuit appeal in which the court addressed claim construction issues related to the “buffer” limitation and remanded for further proceedings.
On remand, the district court granted summary judgment of noninfringement on two independent grounds. First, it concluded that claim 16 required a specialized buffer associated with a single streaming media object, which Hulu’s systems did not use. Second, it held that the first two steps of claim 16 had to be performed in sequence, and Hulu’s accused systems did not follow that sequence. Sound View appealed both rulings.
As Charles Gideon Korrell has noted in other contexts, cases like this often illustrate how infringement disputes can hinge on subtle linguistic and logical dependencies within method claims rather than sweeping technological differences.
The Federal Circuit Rejects a “Specialized Buffer” Requirement
The panel, in an opinion by Judge Chen, first addressed the buffer construction. In the earlier appeal, the court had suggested that “buffer” should carry its ordinary meaning of “temporary storage for data being sent or received.” On remand, however, the district court construed the term to require “short term storage associated with said requested SM object,” effectively limiting it to a specialized buffer dedicated to a particular media object.
The Federal Circuit disagreed. Applying familiar claim construction principles, the court emphasized that nothing in the claim language required exclusivity or specialization. Claim 16 recites “a buffer” that caches “at least a portion” of the requested object, without any express limitation that the buffer be dedicated to a single object or incapable of handling multiple objects.
The specification did not compel a narrower reading either. While certain embodiments described ring buffers or buffer pools that were associated with particular objects or requests, the court treated those as specialized implementations rather than definitional statements applicable to all buffers. Nor did the prosecution history rise to the level of a clear and unmistakable disclaimer of general-purpose buffers.
Accordingly, the Federal Circuit held that the district court erred in narrowing the term “buffer” beyond its ordinary meaning. Standing alone, this holding would have favored Sound View. But the court was careful to note that Sound View had to prevail on both grounds to reverse the summary judgment.
Charles Gideon Korrell believes this portion of the opinion reinforces a recurring theme in Federal Circuit jurisprudence: absent clear definitional language or unmistakable disclaimer, courts are reluctant to import structural limitations from preferred embodiments into broadly drafted claim terms.
Implicit Ordering in Method Claims Takes Center Stage
The decisive issue on appeal was whether claim 16 requires its first two steps to be performed in the order written. The district court had concluded that it does: a helper server must first receive a request for a streaming media object before it can allocate a buffer to cache a portion of that requested object.
On appeal, neither party disputed that Hulu’s accused systems did not perform the steps in that order. The only question was whether the claim required such an order at all.
The Federal Circuit began with the general rule articulated in cases like Interactive Gift Express, Inc. v. Compuserve Inc.: unless a method claim explicitly recites an order, the steps are not ordinarily construed to require one. But that rule has a well-established exception. As explained in Mformation Technologies, Inc. v. Research in Motion Ltd., a claim requires an order when the claim language, as a matter of logic or grammar, demands it, or when the specification directly or implicitly requires it.
Here, the court found both grammar and logic dispositive. The first step recites “receiving a request for an SM object.” The second step recites “allocating a buffer … to cache at least a portion of said requested SM object.” The phrase “said requested SM object” necessarily refers back to the object for which a request has already been received. Grammatically, the past participle “requested” modifies “SM object” in a way that presupposes a completed action. Logically, an object cannot be “requested” until a request has occurred.
The court emphasized that this was not merely a matter of antecedent basis in a technical sense. The word “requested” functioned as a status indicator. Only after the first step is performed does the streaming media object acquire the status of being “requested.” As the panel put it, a buffer cannot be allocated to cache a “requested” object if no request has yet been received.
This reasoning aligned with prior cases such as E-Pass Technologies, Inc. v. 3Com Corp. and Altiris, Inc. v. Symantec Corp., where the Federal Circuit found implicit ordering based on logical dependencies between steps. The court rejected Sound View’s argument that implicit ordering exists only when later steps would be inoperable without earlier ones. Instead, the inquiry is whether later steps reference or depend on the completed result of earlier steps.
Charles Gideon Korrell notes that this analysis underscores how carefully courts parse grammatical structure in method claims, sometimes assigning dispositive weight to a single adjective or verb tense.
Rejected Arguments Based on Other Claims and Embodiments
Sound View advanced several additional arguments, none of which persuaded the panel.
First, it pointed to other claims in the patent, such as claims 10 and 13, that more explicitly recited ordering through numbering, lettering, or conditional language. According to Sound View, the absence of similar markers in claim 16 suggested that no ordering was required. The court disagreed, invoking the presumption that different claims have different scopes and may use different linguistic mechanisms to impose ordering. Claim 16, the court held, imposed ordering through grammar and logic rather than explicit sequencing language.
Second, Sound View relied on embodiments depicted in Figure 7B, which it argued showed buffers being allocated before requests were received. The court found this unavailing. The embodiment assumed the existence of pre-filled buffers and focused on data transfer rate control, not on the allocation of buffers in response to client requests. Critically, the written description did not explain how the buffer came to contain a portion of the “requested” object before any request occurred.
Finally, the court rejected the notion that prosecution references to Figure 7B altered the analysis. Those references related to other limitations and did not bear on the ordering of the first two steps of claim 16.
Practical Takeaways for Drafting and Litigation
The Federal Circuit’s decision in Sound View v. Hulu offers several practical lessons.
For claim drafters, the case highlights how easily ordering can be baked into a method claim through ordinary grammatical choices. Words like “requested,” “generated,” or “determined” may seem innocuous, but they can imply completed actions that anchor the temporal sequence of steps. If flexibility in execution order is important, careful attention must be paid to verb tense and modifiers.
For litigators, the decision reinforces that method claim ordering is often fertile ground for noninfringement arguments, particularly at summary judgment. Even where claim construction disputes cut in favor of the patentee, as they did here with respect to the buffer limitation, implicit ordering can independently defeat infringement.
Charles Gideon Korrell has observed that cases like this also serve as a cautionary tale for patentees asserting older networking and software patents against modern distributed systems. Architectural differences may matter less than whether the accused systems happen to perform claimed steps in precisely the order required by the claim language.
Conclusion
In the end, Sound View Innovations v. Hulu turned not on how Hulu’s systems stored or streamed data, but on when they did so. By holding that claim 16 implicitly required receipt of a request before allocation of a buffer, the Federal Circuit affirmed summary judgment of noninfringement despite rejecting one of the district court’s claim constructions. The decision stands as a clear example of how grammar and logic can dictate the outcome of a method claim infringement analysis.