Reading a Codec Patent Claim Against Your Own Streaming Stack
Imagine you receive a demand letter that says "Can you take a look at this?" When you open it, you see that it has an infringement claim chart, where your services are infringing on some video coding patent. The chart refers to the standard documents and the vendor diagrams, but it does not refer to your source code. And no one else besides you has ever seen your source code before.
What the claim actually asks
The way the codec claims are stated is similar to a recipe most of the time:
- Divide the frame into blocks.
- Predict each block based on its neighbours.
- Transform the difference that remains.
- Place a flag into the bitstream to inform the decoder of what has taken place.
Each of these steps is an element of the claim, and this is the rule everything else hangs on. Infringement basically means the accused system does all of them. If you just miss even one, the whole claim collapses. You need to keep this in mind before you read another line of the chart.
Most of the charts we have seen till now generally take a shortcut here and point at the standard. The reasoning here is if you implement H.265 or AV1, you must be doing what the claim describes. Courts have accepted this when the standard forces the step, but when the standard leaves the step optional, they have been far less friendly to it. And a real stack often skips a good chunk of what the standard allows, depending on the profile. Preset and hardware limits also do that. What surprised me when I first read about this is that a standard being widely used doesn’t automatically mean every optional feature in it is switched on.
The encoder
Most of these statements have the encoder in mind, so I'd begin with this one. Besides, we should start with real settings rather than theoretical ones. Obtain the command lines or API calls and get the ladder definitions. Then try to establish what coding tools are turned on by each preset because this is exactly what a chart cannot establish without inside information. You'll definitely need some sample encoding and logging for sure. This is how I learned about an update that changed our outputs but didn't tell us why until we checked the logs.
Software and hardware implementations of the encoder are not entirely the same thing. A software preset implemented on CPUs and a hardware encoder integrated into a cloud processor will differ from each other in their choice. So, a claim chart that does not account for that. Preset names aren't necessarily safe either. “Fast” in one release can enable tools that “fast” in the next release leaves off.
First, find out who owns the code. Many services license the encoder and you might not be able to open the code at all. So, you should state this clearly at an early stage. Read the contract before answering anything to anyone.
The packager
A packager is mainly concerned with wrapping. It does nothing but split the stream into chunks and generates manifests. The Packager does not work with the actual encoded video data. Some claims can be made in this domain because of their relation to signalling. The parameter set or the SEI message can traverse all your pipeline untouched. Did you make it or did you just carry it? It is crucial to distinguish between the two. Therefore, it is better to seek legal counsel before making any assumptions. One should obviously keep one sample segment from each version. Open it using a bitstream analyzer to see exactly what is within it. Only a real file can settle the arguments that a diagram alone begins to raise.
The player
We all know decoder claims refer to the player, so consider exactly what you are shipping. A chip in your phone made by another company decodes. Your application requests video to be played and receives pixels back. But who executes all those steps you list in your claims? If several entities execute the steps, the standard approach under the law is to figure out who directs or controls the execution of the other steps. And if the claims relate to the whole system, the standard is to find out who put the system to work. Diagram the steps from your claims before making any claims about those steps. Identify each step in your claim.
Capability versus operation
One more thing matters here. Some claims about software cover code that seldom has the capability. Others require the steps. The wording used in the claim is something that decides which one it is. If the claim needs a feature switched on then configuration is your evidence. But if it only needs the capability then the code itself is the evidence. You should read the verbs very carefully.
What to do this week
Before doing anything, first snapshot the configurations and encoder versions before anyone tunes anything. Just make a simple record of who made what change and when. It takes the speculation out of chat channels. A statement that we probably infringe is not a scientific fact.
You should date your facts as well. The pipeline from 2021 is not your current pipeline. Since damages are based on past events, so are your records.
Then move to building your own table, keep one row per claim element and one column each for encoder and packager and player. Fill every cell with evidence and a source file. Mark the empty cells honestly. Lastly, hand the table to counsel before the first call with the other side.
[Editor's note: This is a contributed article from Lumenci. Streaming Media accepts vendor bylines based solely on their value to our readers.]
Related Articles
Navigating the ever-changing world of video codec licensing can be complex. This article breaks down major IP-related events from the past 18 months, including the new European SEP licensing rules, Avanci's new video patent pool, and the Sisvel-RPX deal. Explore who's making deals, what technologies are involved, and the implications for royalty-free models
15 May 2024
John C. Simmons, Principal Engineer at John Simmons Consulting, LLC, discusses patent licensing for streaming, which is especially relevant now in light of the recent German court decision in the Broadcom v. Netflix case and Avanci's announced launch of a video streaming patent pool.
23 Oct 2023