In video coding, valuable inventions do not always reside in the encoder or decoder. Sometimes the innovation is embodied in the encoded output itself: the arrangement of syntax elements, flags, parameters, and coded data that make up a compliant bitstream. A carefully drafted bitstream claim can therefore reach a commercially important point in the video-delivery chain—the transmission, storage, or distribution of encoded content—rather than only the manufacture or operation of encoding and decoding products.

That distinction can matter. Video coding standards are deployed across devices, networks, platforms, and content libraries, and licensing programs may place independent value on patent claims that read on encoded streams or their distribution. For a company contributing technology to a coding standard, bitstream coverage may add a meaningful dimension to an international patent portfolio.

But there is a catch: a claim strategy that works in Europe, Asia, or another jurisdiction may encounter very different treatment in the United States.

The U.S. Patentability Problem

Claims directed to bitstreams are routinely pursued—and may be allowed—in many patent systems. That international experience should not, however, create an expectation that corresponding claims will be granted by the U.S. Patent and Trademark Office. U.S. law presents at least two recurring obstacles: subject-matter eligibility under 35 U.S.C. § 101 and the treatment of information under the printed-matter doctrine.

At a high level, a bitstream is structured data. That is precisely its technical value: the particular organization and meaning of the bits allow a decoder to reconstruct pictures efficiently and correctly. Yet a claim that merely recites information, without adequately connecting that information to a machine or a technological operation, may be viewed in the United States as claiming data in the abstract.

Under the Alice/Mayo framework, a claim directed to an abstract idea must include additional elements sufficient to integrate that idea into a practical application or otherwise provide an inventive concept. In computer-related cases, the analysis often turns on whether the claim reflects an improvement to computer functionality or another technical field, or instead merely uses a generic computer as a vehicle for information processing. A bare claim to a sequence of bits, defined only by the information those bits represent, can struggle to clear that threshold.

This does not mean that every bitstream claim is ineligible. It means that the technical relationship should be visible in the claim—not left solely in the specification or assumed from the technology. For example, a claim may be stronger when its limitations show how the bitstream causes a decoder to operate, enables a particular decoding process, reduces processing or signaling demands, improves compression, or otherwise changes the operation of computer hardware.

When the Bits Are Given No Patentable Weight

An equally frustrating problem can arise during prior-art examination. An examiner may characterize the recited organization or meaning of the bits as “nonfunctional descriptive material” under the printed-matter doctrine. Despite its name, the doctrine is not limited to ink on paper. It can apply to information stored or represented electronically.

The critical question is whether the claimed information has a functional relationship with its substrate or with other elements of the claim. If the relationship is functional, the information-related limitations should receive patentable weight. If it is not, an examiner may treat those limitations as incapable of distinguishing the claim from the prior art.

The practical result can look circular. The claim contains detailed limitations defining a novel bitstream syntax, but the examiner gives those limitations no patentable weight. Once those limitations are set aside, almost any conventional storage medium or data transmission may appear to anticipate or render obvious what remains. Applicants may also face separate § 101 or § 112 issues depending on whether the claim clearly identifies a statutory category, defines the claimed structure, and is supported by the disclosure.

The governing principles are more nuanced than a blanket rule that “data is not patentable.” The USPTO’s own guidance recognizes that a data structure may be functionally related to a computer-readable medium or computing process. The challenge is making that relationship sufficiently concrete in the claim language and prosecution record.

Claim Format Can Change the Conversation

There is no universal drafting formula, and examiner practice is not perfectly uniform. In difficult cases, amendments may be needed to address the particular examiner’s understanding of the claim and its technological function. Nevertheless, thoughtful claim architecture can reduce the risk from the outset.

One option is to frame the invention as a computer-implemented method involving the bitstream. Rather than claiming only an abstract arrangement of bits, the claim may recite generating, encoding, transmitting, receiving, parsing, or decoding the bitstream using one or more processors, together with the technical operations that give the syntax its function. This approach can make the connection between the data and the operation of computing hardware more explicit.

Another option is a Beauregard-style claim directed to a non-transitory computer-readable medium storing instructions that cause a processor to perform a claimed method. In the right case, this format places the invention within a recognized statutory category and ties the claimed subject matter to computer operation. But the format is not magic. Merely placing an abstract process on a computer-readable medium does not necessarily cure an Alice problem, and a medium “storing a bitstream” may still invite a printed-matter rejection if the functional relationship is unclear.

A robust application may therefore pursue several complementary claim types. Encoder, decoder, method, system, computer-readable-medium, and bitstream-oriented claims can protect different actors and stages of the commercial chain. The specification should support those claims by explaining not only what each syntax element represents, but what the claimed organization causes the encoder or decoder to do and what technical benefit follows.

An Upstream Strategy Requires Early Planning

Bitstream claims can be commercially significant, particularly in standards-driven industries where encoded content moves through a long and complex distribution chain. They can also be among the most jurisdiction-sensitive claims in a global portfolio.

The best time to address that sensitivity is before filing. Patent drafters should identify the desired point of enforcement, preserve support for multiple claim formats, and describe the functional relationship between the bitstream and the machines that create, carry, and consume it. During U.S. prosecution, applicants should also be prepared to distinguish a functional data structure from information that merely happens to be stored on a generic medium.

For companies developing video coding technology, the lesson is not to abandon bitstream claims. It is to approach them with a jurisdiction-specific strategy. A bitstream may travel effortlessly across borders; the claims covering it do not.

Principal Attorney