Sisvel patent pools formed for VP9 and AV1

[hajj_3]

bad news, it looks like vp9 and av1 may violate some patents, as a result patent pools have been launched for vp9 and av1:

A list of the patents in the patent pools are not available yet.

There are no costs for content distributors thankfully.

http://sisvel.com/licensing-programs/audio-and-video-coding-decoding/video-coding-platform/introduction
http://sisvel.com/news-events/news/sisvel-announces-the-launch-of-its-video-coding-licensing-platform
https://www.streamingmedia.com/Articles/News/Online-Video-News/Sisvel-Launches-Patent-Pools-for-VP9-and-AV1-130840.aspx
https://www.streamingmedia.com/Articles/News/Online-Video-News/No-Content-Royalties-in-Sisvel-VP9-AV1-Patent-Pools-130849.aspx

[nevcairiel]

This is just a patent troll company. They are not giving out any tangible information whatsoever, like the patents they claim are relevant, or even a number of patents. Don't give them any attention.

[hajj_3]

This is just a patent troll company. They are not giving out any tangible information whatsoever, like the patents they claim are relevant, or even a number of patents. Don't give them any attention.

It doesn't look like that, JVCKENWOOD, Phillips, Toshiba and others are in this patent pool. They said in one of the links that they will publish a list of their patents.

[Quikee]

This was expected that somebody will try to assert their patents against AV1, if not for other reason just to try to cover AV1 in uncertainty. I'm sure these patents aren't new so I'm sure AOM is already aware of them an has some sort of an answer. Let's see what will happen next..

[utack]

Sisvel CEO confirmed that at the moment they have no clue which patents they manage are applicable (at 15:56):
https://www.youtube.com/watch?v=lqR63-Xwv6o

[dapperdan]

Reminds me of the story about when IBM told Sun they infringed some patents and Sun engineers pointed out they didn't infringe:

OK, maybe you don't infringe these seven patents. But we have 10,000 U.S. patents. Do you really want us to go back to Armonk [IBM headquarters in New York] and find seven patents you do infringe? Or do you want to make this easy and just pay us $20 million?"

[benwaggoner]

Yet another patent pool that doesn't offer any information to allow evaluation of their IP claims or their license. Timed to coincide with NAB I presume. This is profoundly unhelpful.

[birdie]

So, has HEVC adoption stalled and they are resorting to the lowest tactics in order to sow FUD in regard to AV1 and open a litigation against Google? Almost expected.

[benwaggoner]

So, has HEVC adoption stalled and they are resorting to the lowest tactics in order to sow FUD in regard to AV1 and open a litigation against Google? Almost expected.
I'm not aware of any indication that Sisvel is part of any "they" involved with HEVC. Is there some?

[z_thunder]

Hi Ben, hi all,
scope of this post is try and clarify some of the issues that are being debated in this thread.
My name is Giovanni Ballocca and I’m currently with Sisvel Technology (just to be clear on my position).
I can understand your doubts springing from the current lack of a patent list, but there’s a reason behind that I’m willing to explain.
We’ve been working for some months now to the creation of this licensing program having in mind that the technologies covered, even though not international standards, have been designed in the perspective of a global outreach.
We have, therefore, decided to use the same level of care that we normally apply when dealing with any other standard covered technology (Sisvel has been running licensing program on technologies standardized by the DVB and other SDOs for a long time).
This typically requires a facilitation phase to aggregate a critical mass of IP that ensures the program is not technically irrelevant; appropriate royalty determination; public patent call to open the process to all the interested actors; third party evaluation of the patents (it cannot be us to decide whether or not a patent is necessary to practice a given specification).
As you might have probably heard from the news, we just opened the patent call (other patent owners have shown a definite interest in joining the program) and are in the third party evaluation phase. Only the patent evaluated necessary to perform the specs will be published in the list and this will happen by the end of Q2 2019.
No licensing discussions will be started before the list of patents is made available.
Regarding the specific date for the launch of the program, there is no specific intention to target the NAB or any other event: if you consider the calendar of tradeshows in the CE and ICT space with global relevance it’s almost impossible to announce anything without the risk to collide with some external event. By the way, being involved in other broadcast related business, we’ll be present at the NAB and available chats and clarifications if needed.
I’ll be happy to provide further clarifications where possible.
G.

[dapperdan]

Seems slightly odd to have already published the price they intend to charge but they're not actually figured if they have something to offer in exchange. You'd think the price would in some way depend on the quality and quantity of IP being licensed, cost to work around etc

[Gser]

Seems slightly odd to have already published the price they intend to charge but they're not actually figured if they have something to offer in exchange. You'd think the price would in some way depend on the quality and quantity of IP being licensed, cost to work around etc

Ah I see you are new. Patent trolls use completely arbitrary fantasy numbers to justify prices, they use these inflated prices to attract costumers i.e. more members in the patent pool. Essentially they are running a scam. IF they are smart scammers they ask for prices that they know people can pay. They get no money otherwise, pricing is usually based like this. If they have in any way a legimate case, they will settle out of court for a percentage of profits. If the case ends up in court and it is not a paid shill of the copyright troll they will ask for examples of similar cases and base judgement on that.

[mandarinka]

This seems like a common thing with in the more "religious" following of open source and related things that something happens, but you guys misuse the "patent troll" term a lot.

Patent trolling is something completely different. Patent troll has a few patents, lies in wait till the technology is broadly deployed in for-revenue shipping devices, then attacks a specific rich company and demands large sums for those specific patents at court. The payouts are large if successful.

This is plain IP pool - patent trolls don't offer mild/fair per-product fees to everyone, they only extort you at court when they target you. Note also how this is formed and made clear early in AV1 life, before any phone, standalone media player or processor/GPU could ship with AV1 support - patent troll would wait for a moment when a lot of devices would be out in the wild and make base for large damage claims. If they were patent troll, they would just foil themselves, because patent troll only reveals its hand after patent X ships in a lot of devices and products and company Y makes a lot of money on it, so that troll can ask court to grant it a share of that revenue. Just apply logic ffs.

What is so hard in seeing that some companies that didn't want to contribute to AV1/AOM/Google for free but still do video research have patented their results and see them being used/adapted in AV1, and thus they try to get a compensation?

Inb4 you believe that the MPEG-LA settlement with Google over VP8/VP9 was completely bogus and just an extortion that Google decided to pay away despite it being totally dishonest and nono of the patents were valid. People, chill and try to look at these things without the "free things are supreme, infallible and perfect, and everybody else never invents anything and only trolls and runs conspiracies against the true religion blah blah etc" bias.

Sorry for ranting and touching people's bubbles, but sometimes you have to go against popular opinions when they are incorrect and unfair. I like open source and open source media software a lot myself but we need to be honest.

[iwod]

This seems like a common thing with in the more "religious" following of open source and related things that something happens, but you guys misuse the "patent troll" term a lot.

Patent trolling is something completely different. Patent troll has a few patents, lies in wait till the technology is broadly deployed in for-revenue shipping devices, then attacks a specific rich company and demands large sums for those specific patents at court. The payouts are large if successful.

This is plain IP pool - patent trolls don't offer mild/fair per-product fees to everyone, they only extort you at court when they target you. Note also how this is formed and made clear early in AV1 life, before any phone, standalone media player or processor/GPU could ship with AV1 support - patent troll would wait for a moment when a lot of devices would be out in the wild and make base for large damage claims. If they were patent troll, they would just foil themselves, because patent troll only reveals its hand after patent X ships in a lot of devices and products and company Y makes a lot of money on it, so that troll can ask court to grant it a share of that revenue. Just apply logic ffs.

What is so hard in seeing that some companies that didn't want to contribute to AV1/AOM/Google for free but still do video research have patented their results and see them being used/adapted in AV1, and thus they try to get a compensation?

Inb4 you believe that the MPEG-LA settlement with Google over VP8/VP9 was completely bogus and just an extortion that Google decided to pay away despite it being totally dishonest and nono of the patents were valid. People, chill and try to look at these things without the "free things are supreme, infallible and perfect, and everybody else never invents anything and only trolls and runs conspiracies against the true religion blah blah etc" bias.

Sorry for ranting and touching people's bubbles, but sometimes you have to go against popular opinions when they are incorrect and unfair. I like open source and open source media software a lot myself but we need to be honest.

I think you did it much better than what I could do and I don't consider any of the above "ranting". Merely pointing out a few facts and truth.

I am also glad to see more people are finally speaking out. ( May be out of intense frustration )

[dapperdan]

Google and the rest of AOM don't want to use their IP. If it was easy to know what they claimed ownership of, they would have avoided it. They've already spent literally millions on trying to avoid using unlicensed IP by accident

Changing AV1 now has a definite monetary cost. If it didn't, there would be no point announcing the patents because Google would just remove them. So they are by your own idiosyncratic definition, patent trolls. Google et all are now faced with trading off the cost of fighting or settling this against the cost to redo the standard to work around the patents.

Video codec patents are broken. People at the top of MPEG seems to have accepted this, so it's hardly just the crazy hippies holding this view. It's people actual job to write vague patents, the vaguer the patent the better they are doing their job and the more likely their company will make money. This is not something to celebrate.

[mandarinka]

Seriously, do you want everybody in the world to check what Google is doing, do IPR analysis on everything for them at your own expense and then warn them for free?
Before such tools are finalised, so you might end up analysing an experiment that will just get dropped for unrelated reasons? (It also doesn't help both VP9 and AV1 were relatively rushed through development.) If that is anybody's due dilligence, definitely not not of an outsider IP owner. Again, try to look at it without pro-free bias.

[dapperdan]

No, I want a functional IP system where you won't accidentally use someone's IP if you don't intend to and the people given 20 years of legal monopoly have to provide some clarity about what they want protected in exchange for that benefit.

Mozilla, Xiph etc. are quite happy to avoid IP that's not available under terms they can accept. Apparently it's impossible for them to do so with any certainty under the current system since there's so many vague patents.

If a patent isn't clear enough for Google's army of lawyers to find and avoid it then it's not clear enough to be worth legal protection.

[mandarinka]

I'm not sure it's as clear-cut. For example, the alt-ref thing in VP9/AV1 is really a copy of b-frame mechanism that is designed in a roundabout way to not look totally like b-frames, at a glance. Is that an example of "quite happy to avoid IP that's not available under terms they can accept" in a good sense? Sounds more like use the idea but dodge the responsibility to me, but well, maybe they changed enough details to get away with it.
As for the unclearness - it's perfectly possible the patents just weren't discovered or they weren't careful enough in trying to stay clear. I don't think it's a responsibility of patent holder to reach out to everybody in the world to informa them about it, that's pretty much not viable after all.
Also you call a video compression patent a monopoly and paint is as some injustice. But look at it from the inventor's point of view. They invested money and work. They are probably willing to offer it to multiple parties and not having a monopoly. But Google/AOM will only accept it for free. How can you think that refusing to grant the technology to them in such a situation is unjust? AOM's insistence of being royalty free is their choice, they have no right to push that onto IP holders that aren't okay with that. It's normal to want to be compensated for your property/work.

I think we are starting to hijack this thread though, so better stop this debate (which has been here over and over in the past).

[xiphmont]

This seems like a common thing with in the more "religious" following of open source and related things that something happens, but you guys misuse the "patent troll" term a lot.

In this case, I respectfully disagree. Basing your standard business practice around abusing patent hold-up is the very definition of a patent troll. There are ways to make it more egregious; a few are found here though certainly not all. Regardless, Sisvel is trolling. They don't have to, they didn't have to, but they are.

[mandarinka]

"They didn't have to." (Or let me paraphrase it, you seem to be suggesting they "shouldn't be doing this".)

If you say that to somebody who might have a legitimate claim to the IP and your reason in the end is that you are the one that has to pay, don't you think that is rather hypocritical and self-centered?
You aren't even impartial here as AOM member/AV1 creator but I don't think you would be in position to tell them that even if you were. So really, trying to paint this position with moral colors, I strongly think that is dishonest and biased, even if you probably don't see that.

[nevcairiel]

If you say that to somebody who might have a legitimate claim to the IP

But they stated themselves that they don't even know yet what patents are applicable. That means there could also be none. So they are charging money before they even know if they have a case to do so. How is that good practice, or not trolling?

[mandarinka]

But they stated themselves that they don't even know yet what patents are applicable. That means there could also be none.

Eh, I don't think that is quite correct. The list is not published/finalised, so it's probably a case of the usual business communication "we don't commit to anything yet". There are four major companies quoted as backers in their press release, so it is safe to assume that their IP for example will land there.
They say the list will be published when the call for other pool members ends...

[bstrobl]

VP9 has already existed for several years. Seems kind of convenient for them to pop up less than a year after AV1s introduction, while covering VP9 in their terms as well. If it just covered AV1 it may not seem that out of place but at this stage they have had enough time, especially since VP9 already had other patent pools pop up to try to claim their rights.

[soresu]

AV1 was openly developed, with all tools expressed in the specification.

The standardisation process towards bit sream freeze was telegraphed well in advance for any interested patent parties to have found applicable patents and demanded compensation or withdrawl.
For this consortium to have waited until software and hardware was well into development implies a definitive desire to increase the pressure on AOMedia contributors in order to defray the cost of said software and hardware development.

I think it does bare in mind remembering that not only Google was supposed to be contributing legal protection to AV1 by reviewing patent IP, there were other significant parties involved like Cisco and Microsoft.
Wasnt ANS left out of AV1 because of precisely this problem?

[soresu]

I guess at least there is no small corporate backing behind AOMedia to provide legal assistance here, the founding members alone can contribute a very significant defence if needed, and I would assume their own IP review pre bit stream freeze was probably significant enough to address any less than iron clad attempt to shake them down.

[Quikee]

Wasn't ANS left out of AV1 because of precisely this problem?

No.. it was left out because it wasn't a good fit for hardware. But Google filed a patent for "ANS in video compression", which is what pissed people of.

[utack]

https://aomedia.org/the-alliance-for-open-media-statement/

[mandarinka]

Wasnt ANS left out of AV1 because of precisely this problem?
I don't think so. What I heard is that the guy behind it wanted to contribute it, but actually, Google at the same time he was in the AV1 development discussions with them, they tried to patent his idea for themselves behind his back (like, wtf?!). I'm not sure if he even succeeded at preventing that, but if the snafu kept ANS out, it was not the inventor's fault.

[dapperdan]

https://xiphmont.dreamwidth.org/84214.html

Xiphmont's post about the ANS patent thing has all the nuance that gets lost in the retelling of this story.

[soresu]

Interesting read about the performance claims not adding up, I got the initial impression that it was some big advance in efficiency over CABAC with less complexity.

As you say it pays to read up on these things, and yes I always did get Monty's impression that Google's patent filing was specifically a pre-emptive protection against patent trolling over AV1, as indeed alot of AOMedia's mandate was during AV1s initial development.

[mandarinka]

https://xiphmont.dreamwidth.org/84214.html

Xiphmont's post about the ANS patent thing has all the nuance that gets lost in the retelling of this story.

For saying how he doesn't want to defend Google he sure seems to. It baffled me a bit when he basically addressed the whole matter by telling Duda to shut up go smoke cannabis instead. Maybe it's the classical case of poor joke that wasn't really meant to offend but was too dumb, but well... it involuntarily kind of started shifting my impression of the guy as I read that.

Also I think that the compression efficiency or usefulness of the algorithm has zero importance in the matter of Google's patenting attempt at all, so why bring it up.

[schweinsz]

I'm not sure it's as clear-cut. For example, the alt-ref thing in VP9/AV1 is really a copy of b-frame mechanism that is designed in a roundabout way to not look totally like b-frames, at a glance. Is that an example of "quite happy to avoid IP that's not available under terms they can accept" in a good sense? Sounds more like use the idea but dodge the responsibility to me, but well, maybe they changed enough details to get away with it.
As for the unclearness - it's perfectly possible the patents just weren't discovered or they weren't careful enough in trying to stay clear. I don't think it's a responsibility of patent holder to reach out to everybody in the world to informa them about it, that's pretty much not viable after all.
Also you call a video compression patent a monopoly and paint is as some injustice. But look at it from the inventor's point of view. They invested money and work. They are probably willing to offer it to multiple parties and not having a monopoly. But Google/AOM will only accept it for free. How can you think that refusing to grant the technology to them in such a situation is unjust? AOM's insistence of being royalty free is their choice, they have no right to push that onto IP holders that aren't okay with that. It's normal to want to be compensated for your property/work.

I think we are starting to hijack this thread though, so better stop this debate (which has been here over and over in the past).
The b-frame is invented more 30 years ago, while the multiple references and the multiple hypothesis inter prediction are invented more than 20 years ago. To the best of my knowledge, the hierarchical b coding structure is invented more than 24 years ago.

[hajj_3]

HEVC patent pool news: https://www.streamingmedia.com/Articles/News/Online-Video-News/Balance-of-Power-Shifts-Among-HEVC-Patent-Pools-136123.aspx

Also 'unifiedpatents' has now challenged a total of 42% of Velos Media patent pool's h265 patents: https://www.unifiedpatents.com/insights/2020/1/7/another-velos-media-patent-challenged-as-likely-unpatentable

[hajj_3]

Sisvel has published a list of their patents.

List of VP9 patents: https://www.sisvel.com/images/documents/Video-Coding-Platform/PatentList_VP9.pdf
List of AV1 patents: https://www.sisvel.com/images/documents/Video-Coding-Platform/PatentList_AV1.pdf

[hajj_3]

2 companies have now licenced sisvel's patents: https://www.sisvel.com/news-events/news/sisvel-announces-the-first-licensees-of-its-video-coding-licensing-platform

[benwaggoner]

2 companies have now licenced sisvel's patents: https://www.sisvel.com/news-events/news/sisvel-announces-the-first-licensees-of-its-video-coding-licensing-platform
I note that Mitsubishi Electric is the original holder of all the Xylene S.A. patents asserted in the docs, which are a good chunk of them.

I don't recall having heard about Tremmen Tecnologica. Their site is Spanish only and they don't have a Wikipedia entry even.

[hajj_3]

Interdigital has filed a lawsuit against Lenovo regarding VP9 & AV1 patent infringement: https://insight.rpxcorp.com/litigation_documents/15358454

These are the patent numbers and anticipated expiration dates (according to google patents):

US10,250,877 - 2035-05-22
US8,674,859 - 2030-06-22
US9,674,556 - 2027-10-25
US9,173,054 - 2029-12-22
US8,737,933 - 2029-12-22

[Zarxrax]

From: https://insight.rpxcorp.com/litigati...ments/15358454
The ’877 Patent is entitled “Method and Device for Coding an Image Block,
Corresponding Decoding Method and Decoding Device” and issued on April 2, 2019, to
inventors Philippe Bordes, Pierre Andrivon, and Philippe Salmon.

From: https://en.wikipedia.org/wiki/AV1
On 25 June 2018, a validated version 1.0.0 of the specification was released.

Sounds legit.

[rwill]

'Issued' does not equal 'Filed' Mr. Gump.

[Avclover]

Interestingly, a new patent pool called Avanci video announced last week that they will ask video streaming operators to take a license for AV1 among other modern day codecs. 25 licensors are listed...

https://www.avanci.com/video/

[hajj_3]

Interestingly, a new patent pool called Avanci video announced last week that they will ask video streaming operators to take a license for AV1 among other modern day codecs. 25 licensors are listed...

https://www.avanci.com/video/

they haven't listed their patents yet or how much they are charging. It is annoying that they are trying to charge for streaming.

[Avclover]

I understood, new Avanci programs first find the suitable rates in initial discussion with licensees and (unlike the late Velos pool) publish them when first agreements are signed.

[hajj_3]

nokia has filed lots of lawsuits against Amazon and HP in various countries about video codec patents and streaming patents: https://www.nokia.com/blog/nokia-seeks-compensation-for-amazons-use-of-our-patented-multimedia-inventions/

nokia vs amazon u.s lawsuit document: https://www.courtlistener.com/docket/67928543/1/nokia-technologies-oy-v-amazoncom-inc/
nokia vs hp u.s lawsuit document: https://www.courtlistener.com/docket/67928650/1/nokia-technologies-oy-v-hp-inc/

patents nokia is suing hp over and their expiry dates as nokia listed in the court filing:

US7,532,808 - 2025-12-11 -h264
US8,204,134 - 2028-01-21 -h264
US7,724,818 - 2026-05-03 -h264+h265
US10,536,714 - 2032-11-01 -h265
US11,805,267 - 2032-01-06 -h265
US8,077,991 - 2030-10-12 -h265
US8,050,321 - 2027-05-19 -h264+h265
US6,950,469 - expired on 2023-08-06 -h264
US7,280,599 - expired on 2022-05-14 -h264
US8,036,273 - expired on 2021-09-17 -h264

patents nokia is suing amazon over, nokia did not list the expiration dates in this lawsuit therefore i am getting them off google patents:

US7,532,808 - 2025-12-11? -h264
US8,050,321 - 2027-05-19? -h264+h265?
US7,724,818 - 2026-05-03? -h264+h265?
US6,950,469 - expired 2023-08-06?
US7,280,599 - expired 2022-05-14?
US8,036,273 - expired 2021-09-17?
US6,856,701 - expired 2021-11-27?
US9,800,891 - expired 2021-01-19?
US6,968,005 - expired 2023-01-19?
US8,144,764 - expired 2024-10-15? -h264
US8,175,148 - 2026-12-03? -h264+h265?
US8,077,991 - 2030-10-12? -h265
US9,571,833 - 2034-10-13? -h265
US11,805,267 - 2032-01-06? -h265
US9,390,137 - 2033-08-01?

nokia is not a part of the via-la licensing for H264 (formerly known as mpeg-la) therefore none of these patents are listed in the via-la licensing list of H264 patents. I haven't checked for other codecs.

[oibaf]

Here https://www.unifiedpatents.com/insights it looks like many VP9/AV1 (as well as HEVC and other codecs) are being challenged / revoked / invalidated, here are some related posts:

https://www.unifiedpatents.com/insights/2023/8/25/gevc-patent-in-sisvel-av1-pool-appears-not-essential
https://www.unifiedpatents.com/insights/2023/7/12/gevc-video-codec-patent-japanese-opposition-success
https://www.unifiedpatents.com/insights/2023/7/12/kaist-etri-av1hevc-patent-patent-japanese-opposition-success
https://www.unifiedpatents.com/insights/2023/7/7/interdigital-av1vp9-patent-japanese-opposition-success
https://www.unifiedpatents.com/insights/2023/7/7/two-xylene-jp-patents-revoked-in-japan
https://www.unifiedpatents.com/insights/2023/6/30/etri-video-codec-patent-reexam-granted
https://www.unifiedpatents.com/insights/2023/6/15/interdigital-sisvels-av1-pool-us-9675556
https://www.unifiedpatents.com/insights/2023/6/16/interdigital-video-codec-patent-reexam-granted
https://www.unifiedpatents.com/insights/2023/6/15/interdigital-sisvels-av1-pool-us-9227243
https://www.unifiedpatents.com/insights/2023/5/23/interdigital-hybrid-coding-patent-challenged-in-reexam
https://www.unifiedpatents.com/insights/2023/4/17/ip-bridge-patent-confirmed-invalid


Note however, that some of the invalidated patents still appears on SISVEL AV1 patents. For example U.S. Patent 7,515,635 was invalidated (April 2023) according to https://www.unifiedpatents.com/insights?offset=1682606261693 , however it is still listed in https://www.sisvel.com/xlin7ipl485u/5VKBBH3LSEwAyT151R2j3E/82fc563e7d116627d61083d8c249daaa/PatentList_AV1.pdf (dated September 2023)

[hajj_3]

Here is a list of all the active AV1 patents in the sisvel patent pool for the EU and their expiration dates, 11 out of 24 of them are currently being challenged in court:

EP1590964 - 2023-12-16
EP1611740 - 2024-02-24
EP1627360 - 2024-03-30 - court
EP3862973 - 2024-03-30 - court
EP1636987 - 2024-06-03
EP1781042 - 2025-08-16
EP1982524 - 2026-12-22 - court
EP2950543 - 2026-12-22 - court
EP1972156 - 2027-01-12
EP2255537 - 2029-02-20
EP2279620 - 2029-04-07
EP2359601 - 2029-10-20
EP2988500 - 2030-03-16 - court
EP2443835 - 2030-06-17 - court
EP2571269 - 2031-05-12 - court
EP3119091 - 2031-05-12 - court
EP3128755 - 2031-05-12 - court
EP2608540 - 2031-08-17
EP2627085 - 2031-10-04 - court
EP2996334 - 2031-12-21
EP2656507 - 2031-12-21
EP3595281 - 2032-05-17
EP2721819 - 2032-06-18 - court
EP2907306 - 2033-10-14

[hajj_3]

Note however, that some of the invalidated patents still appears on SISVEL AV1 patents. For example U.S. Patent 7,515,635 was invalidated (April 2023) according to https://www.unifiedpatents.com/insights?offset=1682606261693 , however it is still listed in https://www.sisvel.com/xlin7ipl485u/5VKBBH3LSEwAyT151R2j3E/82fc563e7d116627d61083d8c249daaa/PatentList_AV1.pdf (dated September 2023)

That patent is being appealed according to google patents: "2023-06-30 US case filed in Court of Appeals for the Federal Circuit".

[oibaf]

Here is a similar list (active EU patents, with their expected expiration dates) for the Sisvel VP9 patent pool, updated as of November 10, 2023 (https://www.sisvel.com/xlin7ipl485u/6OckyYnH49V6byT7dW7YsF/019ee9f0f495dc57b5eaa7b42720b867/PatentList_VP9.pdf):

2025-08-16: EP1781042 (https://patents.google.com/patent/EP1781042B1/de)
2030-06-17: EP2443835 (https://patents.google.com/patent/EP2443835A1/de) - court
2031-05-12: EP2571269 (https://patents.google.com/patent/EP2571269B1/de) - court
2031-05-12: EP3119091 (https://patents.google.com/patent/EP3119091B1/de) - court
2031-05-12: EP3128755 (https://patents.google.com/patent/EP3128755B1/de) - court
2031-08-17: EP2608540 (https://patents.google.com/patent/EP2608540B1/de) - on November 2023, the European Patent Office announced the revocation (https://www.unifiedpatents.com/insights/2023/11/27/ideahub-former-etri-hevc-patent-revoked-in-epo) of all claims of EP3402195 (https://patents.google.com/patent/EP3402195B1/de) which is in the same family of EP2608540 (https://portal.unifiedpatents.com/patents/patent/EP-3402195-B1).

[oibaf]

Ideahub (former ETRI) HEVC Patent Revoked in EPO (https://www.unifiedpatents.com/insights/2023/11/27/ideahub-former-etri-hevc-patent-revoked-in-epo) - On November 22, 2023, the European Patent Office announced the revocation of all claims of EP 3402195. The EP ‘195 patent is currently owned by Ideahub Inc. but was previously owned by the Electronics and Telecommunications Research Institute (ETRI). [...]

According to this (https://portal.unifiedpatents.com/patents/patent/EP-3402195-B1) the EP 3402195 (https://patents.google.com/patent/EP3402195B1/de) patent is in the same family of EP 2608540 (https://patents.google.com/patent/EP2608540B1/de), which is listed in Sisvel patent pool for both AV1 and VP9 (and the farthest patent for VP9).

[benwaggoner]

It is emotionally satisfying to see all these low quality patents used parasitically dropping like flies. Unified Patents does heroic work for us all.

[oibaf]

BTW, these VP9 European patents were in Sisvel 2023-10-19 list, but were removed in their 2023-11-10 list (https://forum.doom9.org/showthread.php?p=1993936#post1993936):


2030-06-29: EP2449782 (https://patents.google.com/patent/EP2449782B1/de)
2030-06-29: EP3288268 (https://patents.google.com/patent/EP3288268B1/de)
2030-08-11: EP2465265 (https://patents.google.com/patent/EP2465265B1/de)
2031-06-07: EP2719182 (https://patents.google.com/patent/EP2719182A1/de)

[hajj_3]

Interestingly, a new patent pool called Avanci video announced last week that they will ask video streaming operators to take a license for AV1 among other modern day codecs. 25 licensors are listed...

https://www.avanci.com/video/
there are 27 licensors now.

[hajj_3]

Here is a list of all the active AV1 patents in the sisvel patent pool for the EU and their expiration dates. 1 is no longer listed as an active lawsuit not sure if invalidated or not. I have added expired labels too:

EP1590964 - 2023-12-16 - EXPIRED
EP1611740 - 2024-02-24 - EXPIRED
EP1627360 - 2024-03-30 - court - EXPIRED
EP3862973 - 2024-03-30 - court - EXPIRED
EP1636987 - 2024-06-03 - EXPIRED
EP1781042 - 2025-08-16
EP1982524 - 2026-12-22 - court
EP2950543 - 2026-12-22 - court
EP1972156 - 2027-01-12
EP2255537 - 2029-02-20
EP2279620 - 2029-04-07
EP2359601 - 2029-10-20
EP2988500 - 2030-03-16 - court - no longer listed as court case, not sure if patent has been invalidated or not
EP2443835 - 2030-06-17 - court
EP2571269 - 2031-05-12 - court
EP3119091 - 2031-05-12 - court
EP3128755 - 2031-05-12 - court
EP2608540 - 2031-08-17
EP2627085 - 2031-10-04 - court
EP2996334 - 2031-12-21
EP2656507 - 2031-12-21
EP3595281 - 2032-05-17
EP2721819 - 2032-06-18 - court
EP2907306 - 2033-10-14

Sisvel updated their vp9 and av1 patents on October 21 2024, not sure what changes have been made.

[oibaf]

Here are all the VP9 patents with known, future expiration date, as well as priority date (second field) and presence of litigation, according to Google Patents:

VP9 Part 1:

2025-02-19 : 2001-09-14 : US8798173 (https://patents.google.com/patent/US8798173/en) : litigation
2025-05-04 : 2002-05-01 : US7319415 (https://patents.google.com/patent/US7319415/en) :
2025-05-11 : 2004-05-19 : US10499058 (https://patents.google.com/patent/US10499058/en) :
2025-05-11 : 2004-05-19 : US10728554 (https://patents.google.com/patent/US10728554/en) :
2025-05-11 : 2004-05-19 : US10951893 (https://patents.google.com/patent/US10951893/en) :
2025-08-16 : 2004-08-16 : CN1922888 (https://patents.google.com/patent/CN1922888/en) :
2025-08-16 : 2004-08-16 : EP1781042 (https://patents.google.com/patent/EP1781042/en) :
2025-09-02 : 2001-07-12 : US9497471 (https://patents.google.com/patent/US9497471/en) :
2025-11-07 : 2001-07-12 : US10297008 (https://patents.google.com/patent/US10297008/en) :
2025-12-11 : 2004-05-19 : US9294771 (https://patents.google.com/patent/US9294771/en) :
2026-02-09 : 2004-05-19 : US11812020 (https://patents.google.com/patent/US11812020/en) :
2026-02-13 : 2002-04-19 : US7515635 (https://patents.google.com/patent/US7515635/en) : litigation
2026-09-03 : 2002-04-19 : US8009733 (https://patents.google.com/patent/US8009733/en) : litigation
2026-09-10 : 2002-04-19 : US8184697 (https://patents.google.com/patent/US8184697/en) : litigation
2026-10-08 : 2002-04-19 : US8204112 (https://patents.google.com/patent/US8204112/en) : litigation
2026-11-05 : 2002-04-19 : US8223841 (https://patents.google.com/patent/US8223841/en) : litigation
2027-01-12 : 2006-01-12 : CN101375609 (https://patents.google.com/patent/CN101375609/en) :
2027-01-12 : 2006-01-12 : JP5280860 (https://patents.google.com/patent/JP5280860/en) :
2027-03-23 : 2006-08-17 : US11330274 (https://patents.google.com/patent/US11330274/en) : litigation
2027-03-23 : 2006-08-17 : US9736484 (https://patents.google.com/patent/US9736484/en) : litigation
2027-03-23 : 2006-08-17 : US9819942 (https://patents.google.com/patent/US9819942/en) : litigation
2027-05-01 : 2002-01-09 : US8401080 (https://patents.google.com/patent/US8401080/en) : litigation
2027-05-13 : 2006-08-17 : US10499064 (https://patents.google.com/patent/US10499064/en) : litigation
2027-06-19 : 2006-08-17 : US9225982 (https://patents.google.com/patent/US9225982/en) : litigation
2027-07-04 : 2006-08-17 : US9154784 (https://patents.google.com/patent/US9154784/en) : litigation
2028-02-02 : 2006-08-17 : US11949881 (https://patents.google.com/patent/US11949881/en) : litigation
2028-06-19 : 2007-06-29 : CN101790848 (https://patents.google.com/patent/CN101790848/en) :
2028-06-19 : 2007-06-29 : JP5613561 (https://patents.google.com/patent/JP5613561/en) :
2028-11-12 : 2008-03-07 : US10334271 (https://patents.google.com/patent/US10334271/en) :
2028-11-12 : 2008-03-07 : US10341679 (https://patents.google.com/patent/US10341679/en) :
2029-02-22 : 2004-05-07 : US7894530 (https://patents.google.com/patent/US7894530/en) :
2029-09-01 : 2008-09-08 : US9674551 (https://patents.google.com/patent/US9674551/en) :
2029-09-01 : 2008-09-08 : US9838696 (https://patents.google.com/patent/US9838696/en) :
2029-09-01 : 2008-09-08 : US9854250 (https://patents.google.com/patent/US9854250/en) :
2029-09-24 : 2008-10-01 : US9148660 (https://patents.google.com/patent/US9148660/en) :
2029-09-24 : 2008-10-01 : US9491467 (https://patents.google.com/patent/US9491467/en) :
2029-10-01 : 2008-10-01 : CN103384333 (https://patents.google.com/patent/CN103384333/en) : litigation
2029-10-01 : 2008-10-01 : CN104219523 (https://patents.google.com/patent/CN104219523/en) : litigation
2029-10-01 : 2008-10-01 : US10917647 (https://patents.google.com/patent/US10917647/en) : litigation
2029-10-01 : 2008-10-01 : US9369737 (https://patents.google.com/patent/US9369737/en) : litigation
2029-10-01 : 2008-10-01 : US9407937 (https://patents.google.com/patent/US9407937/en) : litigation
2029-10-01 : 2008-10-01 : US9942554 (https://patents.google.com/patent/US9942554/en) : litigation
2029-10-07 : 2008-10-14 : US9628815 (https://patents.google.com/patent/US9628815/en) :
2029-10-23 : 2008-10-31 : CN102273206 (https://patents.google.com/patent/CN102273206/en) :
2029-10-23 : 2008-10-31 : CN103297784 (https://patents.google.com/patent/CN103297784/en) :
2029-10-23 : 2008-10-31 : CN103297785 (https://patents.google.com/patent/CN103297785/en) :
2029-10-23 : 2008-10-31 : CN103327338 (https://patents.google.com/patent/CN103327338/en) :
2029-10-23 : 2008-10-31 : CN103354614 (https://patents.google.com/patent/CN103354614/en) :
2029-10-23 : 2008-10-31 : US9392300 (https://patents.google.com/patent/US9392300/en) :
2029-11-04 : 2008-09-03 : US10298954 (https://patents.google.com/patent/US10298954/en) :
2029-11-10 : 2008-09-03 : US9654798 (https://patents.google.com/patent/US9654798/en) :
2029-11-21 : 2008-10-01 : US10321137 (https://patents.google.com/patent/US10321137/en) : litigation
2030-01-07 : 2008-06-26 : US9992510 (https://patents.google.com/patent/US9992510/en) :
2030-01-15 : 2009-01-23 : CN102362498 (https://patents.google.com/patent/CN102362498/en) :
2030-01-15 : 2009-01-23 : CN104935939 (https://patents.google.com/patent/CN104935939/en) :
2030-01-15 : 2009-01-23 : CN105072448 (https://patents.google.com/patent/CN105072448/en) :
2030-01-15 : 2009-01-23 : CN105072449 (https://patents.google.com/patent/CN105072449/en) :
2030-01-15 : 2009-01-23 : US9070179 (https://patents.google.com/patent/US9070179/en) :
2030-01-15 : 2009-01-23 : US9363531 (https://patents.google.com/patent/US9363531/en) :
2030-01-15 : 2009-01-23 : US9420304 (https://patents.google.com/patent/US9420304/en) :
2030-01-15 : 2009-01-23 : US9445118 (https://patents.google.com/patent/US9445118/en) :
2030-01-18 : 2008-10-01 : US10178393 (https://patents.google.com/patent/US10178393/en) : litigation
2030-02-05 : 2006-01-12 : US8611413 (https://patents.google.com/patent/US8611413/en) :
2030-02-23 : 2009-02-23 : CN102369733 (https://patents.google.com/patent/CN102369733/en) : litigation
2030-02-23 : 2009-02-23 : CN105959689 (https://patents.google.com/patent/CN105959689/en) : litigation
2030-02-23 : 2009-02-23 : CN105959690 (https://patents.google.com/patent/CN105959690/en) : litigation
2030-02-23 : 2009-02-23 : CN105959691 (https://patents.google.com/patent/CN105959691/en) : litigation
2030-02-23 : 2009-02-23 : CN105959692 (https://patents.google.com/patent/CN105959692/en) : litigation
2030-02-23 : 2009-02-23 : CN106101705 (https://patents.google.com/patent/CN106101705/en) : litigation
2030-02-23 : 2009-02-23 : JP6164600 (https://patents.google.com/patent/JP6164600/en) : litigation
2030-02-23 : 2009-02-23 : JP6164660 (https://patents.google.com/patent/JP6164660/en) : litigation
2030-02-23 : 2009-02-23 : JP6846988 (https://patents.google.com/patent/JP6846988/en) : litigation
2030-02-23 : 2009-02-23 : JP6851263 (https://patents.google.com/patent/JP6851263/en) : litigation
2030-02-23 : 2009-02-23 : JP6851264 (https://patents.google.com/patent/JP6851264/en) : litigation
2030-02-23 : 2009-02-23 : JP6851265 (https://patents.google.com/patent/JP6851265/en) : litigation
2030-02-23 : 2009-02-23 : JP7171646 (https://patents.google.com/patent/JP7171646/en) : litigation
2030-02-23 : 2009-02-23 : US10462494 (https://patents.google.com/patent/US10462494/en) : litigation
2030-02-23 : 2009-02-23 : US11076175 (https://patents.google.com/patent/US11076175/en) : litigation
2030-02-23 : 2009-02-23 : US9838719 (https://patents.google.com/patent/US9838719/en) : litigation
2030-02-23 : 2009-02-23 : US9838721 (https://patents.google.com/patent/US9838721/en) : litigation
2030-02-23 : 2009-02-23 : US9838722 (https://patents.google.com/patent/US9838722/en) : litigation
2030-02-23 : 2009-02-23 : US9888259 (https://patents.google.com/patent/US9888259/en) : litigation
2030-04-13 : 2009-02-23 : US11659210 (https://patents.google.com/patent/US11659210/en) : litigation
2030-04-26 : 2008-10-01 : US11683502 (https://patents.google.com/patent/US11683502/en) : litigation
2030-05-13 : 2008-06-26 : US9369714 (https://patents.google.com/patent/US9369714/en) :
2030-06-13 : 2008-10-31 : US9955182 (https://patents.google.com/patent/US9955182/en) :
2030-06-17 : 2009-06-19 : CN102804768 (https://patents.google.com/patent/CN102804768/en) : litigation
2030-06-17 : 2009-06-19 : EP2443835 (https://patents.google.com/patent/EP2443835/en) : litigation
2030-06-25 : 2009-07-03 : CN102498718 (https://patents.google.com/patent/CN102498718/en) :
2030-06-27 : 2008-10-31 : US9781445 (https://patents.google.com/patent/US9781445/en) :
2030-06-27 : 2008-10-31 : US9794590 (https://patents.google.com/patent/US9794590/en) :
2030-07-04 : 2006-08-17 : US8548060 (https://patents.google.com/patent/US8548060/en) : litigation
2030-07-27 : 2007-06-29 : US9100038 (https://patents.google.com/patent/US9100038/en) :
2030-09-03 : 2009-09-14 : CN102598669 (https://patents.google.com/patent/CN102598669/en) :
2030-09-03 : 2009-09-14 : CN104506875 (https://patents.google.com/patent/CN104506875/en) :
2030-09-03 : 2009-09-14 : CN104506876 (https://patents.google.com/patent/CN104506876/en) :
2030-09-03 : 2009-09-14 : CN104539957 (https://patents.google.com/patent/CN104539957/en) :
2030-09-03 : 2009-09-14 : CN104539974 (https://patents.google.com/patent/CN104539974/en) :
2030-09-03 : 2009-09-14 : US9584810 (https://patents.google.com/patent/US9584810/en) :
2030-09-24 : 2010-01-07 : CN102763416 (https://patents.google.com/patent/CN102763416/en) :
2030-09-24 : 2010-01-07 : CN103024391 (https://patents.google.com/patent/CN103024391/en) :
2030-09-24 : 2010-01-07 : US9143777 (https://patents.google.com/patent/US9143777/en) :
2030-09-24 : 2010-01-07 : US9148659 (https://patents.google.com/patent/US9148659/en) :
2030-09-24 : 2010-01-07 : US9154779 (https://patents.google.com/patent/US9154779/en) :
2030-09-24 : 2010-01-07 : US9294768 (https://patents.google.com/patent/US9294768/en) :
2030-09-24 : 2010-01-07 : US9392282 (https://patents.google.com/patent/US9392282/en) :
2030-10-01 : 2009-10-01 : US9565444 (https://patents.google.com/patent/US9565444/en) :
2030-10-01 : 2009-10-01 : US9609334 (https://patents.google.com/patent/US9609334/en) :
2030-10-01 : 2009-10-01 : US9609335 (https://patents.google.com/patent/US9609335/en) :
2030-10-06 : 2009-09-14 : US9621895 (https://patents.google.com/patent/US9621895/en) :
2030-10-12 : 2009-02-23 : US9485512 (https://patents.google.com/patent/US9485512/en) : litigation
2030-11-05 : 2004-08-16 : US9402087 (https://patents.google.com/patent/US9402087/en) :

[oibaf]

VP9 Part 2:

2031-01-19 : 2008-10-14 : US9137546 (https://patents.google.com/patent/US9137546/en) :
2031-03-18 : 2008-10-01 : US8818114 (https://patents.google.com/patent/US8818114/en) :
2031-03-31 : 2010-04-09 : CA2795425 (https://patents.google.com/patent/CA2795425/en) :
2031-03-31 : 2010-04-09 : CN106998473 (https://patents.google.com/patent/CN106998473/en) :
2031-03-31 : 2010-04-09 : CN107046644 (https://patents.google.com/patent/CN107046644/en) :
2031-03-31 : 2010-04-09 : US10390011 (https://patents.google.com/patent/US10390011/en) :
2031-03-31 : 2010-04-09 : US10412385 (https://patents.google.com/patent/US10412385/en) :
2031-03-31 : 2010-04-09 : US10469839 (https://patents.google.com/patent/US10469839/en) :
2031-03-31 : 2010-04-09 : US10554970 (https://patents.google.com/patent/US10554970/en) :
2031-03-31 : 2010-04-09 : US9973753 (https://patents.google.com/patent/US9973753/en) :
2031-04-08 : 2010-04-13 : CN105120287 (https://patents.google.com/patent/CN105120287/en) : litigation
2031-04-08 : 2010-04-13 : CN106231329 (https://patents.google.com/patent/CN106231329/en) : litigation
2031-04-08 : 2010-04-13 : CN106231330 (https://patents.google.com/patent/CN106231330/en) : litigation
2031-04-08 : 2010-04-13 : CN106231334 (https://patents.google.com/patent/CN106231334/en) : litigation
2031-04-08 : 2010-04-13 : CN106231338 (https://patents.google.com/patent/CN106231338/en) : litigation
2031-04-11 : 2010-04-13 : CN108471534 (https://patents.google.com/patent/CN108471534/en) : litigation
2031-04-11 : 2010-04-13 : CN108471537 (https://patents.google.com/patent/CN108471537/en) : litigation
2031-04-11 : 2010-04-13 : CN108471538 (https://patents.google.com/patent/CN108471538/en) : litigation
2031-04-11 : 2010-04-13 : CN108777793 (https://patents.google.com/patent/CN108777793/en) : litigation
2031-04-11 : 2010-04-13 : JP6700341 (https://patents.google.com/patent/JP6700341/en) : litigation
2031-04-11 : 2010-04-13 : JP6700342 (https://patents.google.com/patent/JP6700342/en) : litigation
2031-04-11 : 2010-04-13 : US10123025 (https://patents.google.com/patent/US10123025/en) : litigation
2031-04-11 : 2010-04-13 : US10129549 (https://patents.google.com/patent/US10129549/en) : litigation
2031-04-11 : 2010-04-13 : US10148968 (https://patents.google.com/patent/US10148968/en) : litigation
2031-04-11 : 2010-04-13 : US10477223 (https://patents.google.com/patent/US10477223/en) : litigation
2031-04-11 : 2010-04-13 : US10587884 (https://patents.google.com/patent/US10587884/en) : litigation
2031-04-13 : 2010-04-13 : JP6909818 (https://patents.google.com/patent/JP6909818/en) : litigation
2031-04-13 : 2010-04-13 : US10248966 (https://patents.google.com/patent/US10248966/en) : litigation
2031-04-13 : 2010-04-13 : US10460344 (https://patents.google.com/patent/US10460344/en) : litigation
2031-04-13 : 2010-04-13 : US10672028 (https://patents.google.com/patent/US10672028/en) : litigation
2031-04-21 : 2010-04-13 : US10750191 (https://patents.google.com/patent/US10750191/en) : litigation
2031-05-12 : 2010-05-12 : CN102986219 (https://patents.google.com/patent/CN102986219/en) : litigation
2031-05-12 : 2010-05-12 : CN105163131 (https://patents.google.com/patent/CN105163131/en) : litigation
2031-05-12 : 2010-05-12 : EP2571269 (https://patents.google.com/patent/EP2571269/en) : litigation
2031-05-12 : 2010-05-12 : EP3119091 (https://patents.google.com/patent/EP3119091/en) : litigation
2031-05-12 : 2010-05-12 : EP3128755 (https://patents.google.com/patent/EP3128755/en) : litigation
2031-05-12 : 2010-05-12 : US9532065 (https://patents.google.com/patent/US9532065/en) : litigation
2031-05-12 : 2010-05-12 : US9787988 (https://patents.google.com/patent/US9787988/en) : litigation
2031-05-16 : 2008-10-01 : US8867854 (https://patents.google.com/patent/US8867854/en) : litigation
2031-05-25 : 2010-05-12 : US9479791 (https://patents.google.com/patent/US9479791/en) : litigation
2031-06-11 : 2009-06-19 : US8891628 (https://patents.google.com/patent/US8891628/en) : litigation
2031-06-22 : 2009-03-23 : US9031125 (https://patents.google.com/patent/US9031125/en) :
2031-06-23 : 2013-08-30 : JP5679019 (https://patents.google.com/patent/JP5679019/en) :
2031-06-23 : 2013-08-30 : JP5725107 (https://patents.google.com/patent/JP5725107/en) :
2031-06-23 : 2013-08-30 : JP5725108 (https://patents.google.com/patent/JP5725108/en) :
2031-06-23 : 2014-09-05 : JP5839094 (https://patents.google.com/patent/JP5839094/en) :
2031-06-23 : 2015-09-09 : JP5839143 (https://patents.google.com/patent/JP5839143/en) :
2031-06-23 : 2015-09-09 : JP5839144 (https://patents.google.com/patent/JP5839144/en) :
2031-07-14 : 2010-07-20 : CN103004206 (https://patents.google.com/patent/CN103004206/en) : litigation
2031-07-21 : 2010-09-30 : CA2813232 (https://patents.google.com/patent/CA2813232/en) : litigation
2031-07-21 : 2010-09-30 : CA3033984 (https://patents.google.com/patent/CA3033984/en) : litigation
2031-07-21 : 2010-09-30 : CN103222265 (https://patents.google.com/patent/CN103222265/en) : litigation
2031-07-21 : 2010-09-30 : CN106454379 (https://patents.google.com/patent/CN106454379/en) : litigation
2031-07-21 : 2010-09-30 : CN106488249 (https://patents.google.com/patent/CN106488249/en) : litigation
2031-07-21 : 2010-09-30 : CN106713930 (https://patents.google.com/patent/CN106713930/en) : litigation
2031-07-21 : 2010-09-30 : CN106713931 (https://patents.google.com/patent/CN106713931/en) : litigation
2031-07-21 : 2010-09-30 : JP5486091 (https://patents.google.com/patent/JP5486091/en) : litigation
2031-07-21 : 2010-09-30 : JP6071922 (https://patents.google.com/patent/JP6071922/en) : litigation
2031-07-21 : 2010-09-30 : JP6312787 (https://patents.google.com/patent/JP6312787/en) : litigation
2031-08-17 : 2010-08-17 : EP2608540 (https://patents.google.com/patent/EP2608540/en) :
2031-08-17 : 2010-08-17 : JP6163176 (https://patents.google.com/patent/JP6163176/en) :
2031-08-17 : 2010-08-17 : US10212422 (https://patents.google.com/patent/US10212422/en) :
2031-08-17 : 2010-08-17 : US9838691 (https://patents.google.com/patent/US9838691/en) :
2031-10-10 : 2010-10-08 : US10812811 (https://patents.google.com/patent/US10812811/en) : litigation
2031-11-04 : 2010-11-04 : CN103299623 (https://patents.google.com/patent/CN103299623/en) :
2031-11-04 : 2010-11-04 : CN106851320 (https://patents.google.com/patent/CN106851320/en) :
2031-11-04 : 2010-11-04 : CN107071487 (https://patents.google.com/patent/CN107071487/en) :
2031-11-04 : 2010-11-04 : CN107071489 (https://patents.google.com/patent/CN107071489/en) :
2031-11-04 : 2010-11-04 : CN107071491 (https://patents.google.com/patent/CN107071491/en) :
2031-11-04 : 2010-11-04 : CN107071492 (https://patents.google.com/patent/CN107071492/en) :
2031-11-04 : 2010-11-04 : JP6856554 (https://patents.google.com/patent/JP6856554/en) :
2031-11-08 : 2010-08-17 : US10827174 (https://patents.google.com/patent/US10827174/en) :
2031-11-12 : 2010-01-07 : US9113139 (https://patents.google.com/patent/US9113139/en) :
2031-11-26 : 2010-08-17 : US10939106 (https://patents.google.com/patent/US10939106/en) :
2031-11-27 : 2009-07-03 : US10051283 (https://patents.google.com/patent/US10051283/en) :
2032-01-31 : 2011-01-31 : CA2826157 (https://patents.google.com/patent/CA2826157/en) : litigation
2032-01-31 : 2011-01-31 : CN103583044 (https://patents.google.com/patent/CN103583044/en) : litigation
2032-01-31 : 2011-01-31 : JP5911890 (https://patents.google.com/patent/JP5911890/en) : litigation
2032-01-31 : 2011-01-31 : JP6203878 (https://patents.google.com/patent/JP6203878/en) : litigation
2032-01-31 : 2011-01-31 : JP6550429 (https://patents.google.com/patent/JP6550429/en) : litigation
2032-02-24 : 2008-10-31 : US8976863 (https://patents.google.com/patent/US8976863/en) :
2032-03-20 : 2010-09-30 : US9900611 (https://patents.google.com/patent/US9900611/en) : litigation
2032-04-12 : 2011-04-12 : CN103548356 (https://patents.google.com/patent/CN103548356/en) :
2032-04-12 : 2011-04-12 : CN107623857 (https://patents.google.com/patent/CN107623857/en) :
2032-04-12 : 2011-04-12 : CN107888929 (https://patents.google.com/patent/CN107888929/en) :
2032-04-12 : 2011-04-12 : US10575014 (https://patents.google.com/patent/US10575014/en) :
2032-04-12 : 2011-04-12 : US10992956 (https://patents.google.com/patent/US10992956/en) :
2032-04-12 : 2011-04-12 : US11523133 (https://patents.google.com/patent/US11523133/en) :
2032-05-18 : 2010-09-30 : US9894375 (https://patents.google.com/patent/US9894375/en) : litigation
2032-05-21 : 2010-09-30 : US9900612 (https://patents.google.com/patent/US9900612/en) : litigation
2032-05-23 : 2010-02-17 : US9794556 (https://patents.google.com/patent/US9794556/en) :
2032-05-26 : 2010-09-30 : US9894376 (https://patents.google.com/patent/US9894376/en) : litigation
2032-06-14 : 2010-01-07 : US9113138 (https://patents.google.com/patent/US9113138/en) :
2032-06-14 : 2011-06-23 : CN103621087 (https://patents.google.com/patent/CN103621087/en) :
2032-06-14 : 2011-06-23 : CN105791834 (https://patents.google.com/patent/CN105791834/en) :
2032-06-14 : 2011-06-23 : CN105812806 (https://patents.google.com/patent/CN105812806/en) :
2032-06-14 : 2011-06-23 : CN105812807 (https://patents.google.com/patent/CN105812807/en) :
2032-06-14 : 2011-06-23 : CN107071428 (https://patents.google.com/patent/CN107071428/en) :
2032-06-20 : 2011-06-24 : CN107094252 (https://patents.google.com/patent/CN107094252/en) : litigation
2032-06-20 : 2011-06-24 : US10362311 (https://patents.google.com/patent/US10362311/en) : litigation
2032-06-20 : 2011-06-24 : US9319694 (https://patents.google.com/patent/US9319694/en) : litigation
2032-06-20 : 2011-06-24 : US9380308 (https://patents.google.com/patent/US9380308/en) : litigation
2032-06-20 : 2011-06-24 : US9654783 (https://patents.google.com/patent/US9654783/en) : litigation
2032-06-20 : 2011-06-24 : US9661335 (https://patents.google.com/patent/US9661335/en) : litigation
2032-10-14 : 2010-07-20 : US9185409 (https://patents.google.com/patent/US9185409/en) : litigation
2032-10-31 : 2009-08-21 : US9154806 (https://patents.google.com/patent/US9154806/en) :
2032-11-08 : 2011-11-08 : CN110198441 (https://patents.google.com/patent/CN110198441/en) :
2032-11-08 : 2011-11-08 : CN110198447 (https://patents.google.com/patent/CN110198447/en) :
2032-11-08 : 2011-11-08 : CN110198450 (https://patents.google.com/patent/CN110198450/en) :
2032-11-08 : 2011-11-08 : CN110267048 (https://patents.google.com/patent/CN110267048/en) :
2032-11-08 : 2011-11-08 : CN110446038 (https://patents.google.com/patent/CN110446038/en) :
2032-11-08 : 2011-11-08 : JP6746749 (https://patents.google.com/patent/JP6746749/en) :
2032-11-08 : 2011-11-08 : JP7025491 (https://patents.google.com/patent/JP7025491/en) :
2032-11-08 : 2011-11-08 : JP7271768 (https://patents.google.com/patent/JP7271768/en) :
2032-11-08 : 2011-11-08 : JP7358573 (https://patents.google.com/patent/JP7358573/en) :
2032-11-08 : 2011-11-08 : JP7358582 (https://patents.google.com/patent/JP7358582/en) :
2032-11-08 : 2011-11-08 : JP7414909 (https://patents.google.com/patent/JP7414909/en) :
2032-11-08 : 2011-11-08 : US10038907 (https://patents.google.com/patent/US10038907/en) :
2032-11-08 : 2011-11-08 : US10536706 (https://patents.google.com/patent/US10536706/en) :
2032-11-08 : 2011-11-08 : US10694191 (https://patents.google.com/patent/US10694191/en) :
2032-11-08 : 2011-11-08 : US10863181 (https://patents.google.com/patent/US10863181/en) :
2032-11-08 : 2011-11-08 : US11206411 (https://patents.google.com/patent/US11206411/en) :
2032-11-08 : 2011-11-08 : US9854249 (https://patents.google.com/patent/US9854249/en) :
2032-11-21 : 2009-09-14 : US9154809 (https://patents.google.com/patent/US9154809/en) :
2032-12-05 : 2010-09-30 : US9369730 (https://patents.google.com/patent/US9369730/en) : litigation
2032-12-08 : 2011-11-08 : US10805612 (https://patents.google.com/patent/US10805612/en) :
2032-12-28 : 2012-04-20 : US8774540 (https://patents.google.com/patent/US8774540/en) :
2032-12-30 : 2009-10-01 : US9549190 (https://patents.google.com/patent/US9549190/en) :
2033-02-04 : 2011-01-31 : US10244252 (https://patents.google.com/patent/US10244252/en) : litigation
2033-06-25 : 2012-06-29 : CN104488270 (https://patents.google.com/patent/CN104488270/en) :
2033-06-25 : 2012-06-29 : US10341661 (https://patents.google.com/patent/US10341661/en) :
2033-06-25 : 2012-06-29 : US9628799 (https://patents.google.com/patent/US9628799/en) :
2033-06-25 : 2012-06-29 : US9635363 (https://patents.google.com/patent/US9635363/en) :
2033-06-25 : 2012-06-29 : US9641845 (https://patents.google.com/patent/US9641845/en) :
2033-06-25 : 2012-06-29 : US9723311 (https://patents.google.com/patent/US9723311/en) :
2033-09-06 : 2010-08-17 : US9699449 (https://patents.google.com/patent/US9699449/en) :
2033-09-06 : 2012-06-29 : US9497465 (https://patents.google.com/patent/US9497465/en) :
2033-11-18 : 2012-06-29 : US11595655 (https://patents.google.com/patent/US11595655/en) :

[oibaf]

Also here are all the AV1 patents with known, future expiration date, as well as priority date (second field) and presence of litigation, according to Google Patents:

AV1 Part 1:

2024-11-26 : 2002-01-23 : US7421138 (https://patents.google.com/patent/US7421138/en) :
2025-03-20 : 2004-05-21 : US7480335 (https://patents.google.com/patent/US7480335/en) :
2025-05-04 : 2002-05-01 : US7319415 (https://patents.google.com/patent/US7319415/en) :
2025-05-11 : 2004-05-19 : US10499058 (https://patents.google.com/patent/US10499058/en) :
2025-05-11 : 2004-05-19 : US10728554 (https://patents.google.com/patent/US10728554/en) :
2025-05-11 : 2004-05-19 : US10951893 (https://patents.google.com/patent/US10951893/en) :
2025-08-16 : 2004-08-16 : CN1922888 (https://patents.google.com/patent/CN1922888/en) :
2025-08-16 : 2004-08-16 : EP1781042 (https://patents.google.com/patent/EP1781042/en) :
2025-09-02 : 2001-07-12 : US9497471 (https://patents.google.com/patent/US9497471/en) :
2025-10-26 : 2004-06-03 : US7679676 (https://patents.google.com/patent/US7679676/en) :
2025-11-07 : 2001-07-12 : US10297008 (https://patents.google.com/patent/US10297008/en) :
2025-12-11 : 2004-05-19 : US9294771 (https://patents.google.com/patent/US9294771/en) :
2026-02-09 : 2004-05-19 : US11812020 (https://patents.google.com/patent/US11812020/en) :
2026-02-13 : 2002-04-19 : US7515635 (https://patents.google.com/patent/US7515635/en) : litigation
2026-05-02 : 2001-07-12 : US10504205 (https://patents.google.com/patent/US10504205/en) :
2026-05-02 : 2003-01-30 : US9036715 (https://patents.google.com/patent/US9036715/en) :
2026-07-29 : 2003-05-15 : US7742655 (https://patents.google.com/patent/US7742655/en) : litigation
2026-09-03 : 2002-04-19 : US8009733 (https://patents.google.com/patent/US8009733/en) : litigation
2026-09-10 : 2002-04-19 : US8184697 (https://patents.google.com/patent/US8184697/en) : litigation
2026-10-08 : 2002-04-19 : US8204112 (https://patents.google.com/patent/US8204112/en) : litigation
2026-10-19 : 2005-10-21 : JP5620641 (https://patents.google.com/patent/JP5620641/en) :
2026-10-19 : 2005-10-21 : JP5674752 (https://patents.google.com/patent/JP5674752/en) :
2026-10-19 : 2005-10-21 : JP5756537 (https://patents.google.com/patent/JP5756537/en) :
2026-10-19 : 2005-10-21 : US10187660 (https://patents.google.com/patent/US10187660/en) :
2026-10-19 : 2005-10-21 : US8520729 (https://patents.google.com/patent/US8520729/en) :
2026-10-19 : 2005-10-21 : US9118892 (https://patents.google.com/patent/US9118892/en) :
2026-11-05 : 2002-04-19 : US8223841 (https://patents.google.com/patent/US8223841/en) : litigation
2026-11-17 : 2005-10-21 : US9838714 (https://patents.google.com/patent/US9838714/en) :
2026-12-22 : 2006-01-09 : CN103957409 (https://patents.google.com/patent/CN103957409/en) : litigation
2026-12-22 : 2006-01-09 : CN103974064 (https://patents.google.com/patent/CN103974064/en) : litigation
2026-12-22 : 2006-01-09 : CN103974065 (https://patents.google.com/patent/CN103974065/en) : litigation
2026-12-22 : 2006-01-09 : EP1982524 (https://patents.google.com/patent/EP1982524/en) : litigation
2026-12-22 : 2006-01-09 : EP2950543 (https://patents.google.com/patent/EP2950543/en) : litigation
2026-12-22 : 2006-01-09 : EP1982524 (https://patents.google.com/patent/EP1982524/en) : litigation
2026-12-22 : 2006-01-09 : EP2950543 (https://patents.google.com/patent/EP2950543/en) : litigation
2027-01-12 : 2006-01-12 : CN101375609 (https://patents.google.com/patent/CN101375609/en) :
2027-01-12 : 2006-01-12 : EP1972156 (https://patents.google.com/patent/EP1972156/en) :
2027-01-12 : 2006-01-12 : JP5280860 (https://patents.google.com/patent/JP5280860/en) :
2027-01-27 : 2004-11-22 : US7574060 (https://patents.google.com/patent/US7574060/en) :
2027-01-29 : 2002-10-03 : US7596178 (https://patents.google.com/patent/US7596178/en) :
2027-03-23 : 2006-08-17 : US9736484 (https://patents.google.com/patent/US9736484/en) : litigation
2027-03-23 : 2006-08-17 : US9819942 (https://patents.google.com/patent/US9819942/en) : litigation
2027-04-24 : 2006-01-09 : US10070150 (https://patents.google.com/patent/US10070150/en) : litigation
2027-05-01 : 2002-01-09 : US8401080 (https://patents.google.com/patent/US8401080/en) : litigation
2027-06-19 : 2006-08-17 : US9225982 (https://patents.google.com/patent/US9225982/en) : litigation
2027-07-04 : 2006-08-17 : US9154784 (https://patents.google.com/patent/US9154784/en) : litigation
2028-02-02 : 2006-08-17 : US11949881 (https://patents.google.com/patent/US11949881/en) : litigation
2028-05-20 : 2003-04-10 : US7899113 (https://patents.google.com/patent/US7899113/en) :
2028-06-19 : 2007-06-29 : CN101790848 (https://patents.google.com/patent/CN101790848/en) :
2028-06-19 : 2007-06-29 : JP5613561 (https://patents.google.com/patent/JP5613561/en) :
2028-10-12 : 2006-01-09 : US10027983 (https://patents.google.com/patent/US10027983/en) : litigation
2028-11-07 : 2003-01-30 : US8005148 (https://patents.google.com/patent/US8005148/en) :
2028-11-12 : 2008-03-07 : US10334271 (https://patents.google.com/patent/US10334271/en) :
2028-11-12 : 2008-03-07 : US10341679 (https://patents.google.com/patent/US10341679/en) :
2028-11-29 : 2006-01-09 : US10021425 (https://patents.google.com/patent/US10021425/en) : litigation
2029-02-20 : 2008-02-21 : CN101953166 (https://patents.google.com/patent/CN101953166/en) :
2029-02-20 : 2008-02-21 : EP2255537 (https://patents.google.com/patent/EP2255537/en) :
2029-02-20 : 2008-02-21 : JP5498963 (https://patents.google.com/patent/JP5498963/en) :
2029-02-20 : 2008-02-21 : US8917945 (https://patents.google.com/patent/US8917945/en) :
2029-02-20 : 2008-02-21 : US8971648 (https://patents.google.com/patent/US8971648/en) :
2029-02-22 : 2004-05-07 : US7894530 (https://patents.google.com/patent/US7894530/en) :
2029-04-07 : 2008-04-15 : CN102067602 (https://patents.google.com/patent/CN102067602/en) :
2029-04-07 : 2008-04-15 : EP2279620 (https://patents.google.com/patent/EP2279620/en) :
2029-06-17 : 2008-06-24 : US9300981 (https://patents.google.com/patent/US9300981/en) :
2029-06-17 : 2008-06-24 : US9313525 (https://patents.google.com/patent/US9313525/en) :
2029-06-17 : 2008-06-24 : US9319714 (https://patents.google.com/patent/US9319714/en) :
2029-08-04 : 2008-08-04 : US10574994 (https://patents.google.com/patent/US10574994/en) :
2029-08-04 : 2008-08-04 : US10645392 (https://patents.google.com/patent/US10645392/en) :
2029-08-04 : 2008-08-04 : US11539959 (https://patents.google.com/patent/US11539959/en) :
2029-08-04 : 2008-08-04 : US9060168 (https://patents.google.com/patent/US9060168/en) :
2029-08-04 : 2008-08-04 : US9357230 (https://patents.google.com/patent/US9357230/en) :
2029-08-04 : 2008-08-04 : US9667993 (https://patents.google.com/patent/US9667993/en) :
2029-08-04 : 2008-08-04 : US9843807 (https://patents.google.com/patent/US9843807/en) :
2029-08-07 : 2008-08-04 : US11025912 (https://patents.google.com/patent/US11025912/en) :
2029-09-01 : 2008-09-08 : US9674551 (https://patents.google.com/patent/US9674551/en) :
2029-09-01 : 2008-09-08 : US9838696 (https://patents.google.com/patent/US9838696/en) :
2029-09-01 : 2008-09-08 : US9854250 (https://patents.google.com/patent/US9854250/en) :
2029-09-24 : 2008-10-01 : US9148660 (https://patents.google.com/patent/US9148660/en) :
2029-09-24 : 2008-10-01 : US9491467 (https://patents.google.com/patent/US9491467/en) :
2029-10-01 : 2008-10-01 : CN103384333 (https://patents.google.com/patent/CN103384333/en) : litigation
2029-10-01 : 2008-10-01 : CN104219523 (https://patents.google.com/patent/CN104219523/en) : litigation
2029-10-01 : 2008-10-01 : US9369737 (https://patents.google.com/patent/US9369737/en) : litigation
2029-10-01 : 2008-10-01 : US9407937 (https://patents.google.com/patent/US9407937/en) : litigation
2029-10-01 : 2008-10-01 : US9942554 (https://patents.google.com/patent/US9942554/en) : litigation
2029-10-07 : 2008-10-14 : US9628815 (https://patents.google.com/patent/US9628815/en) :
2029-10-20 : 2008-10-31 : CN102204256 (https://patents.google.com/patent/CN102204256/en) :
2029-10-20 : 2008-10-31 : EP2359601 (https://patents.google.com/patent/EP2359601/en) :
2029-10-23 : 2008-10-31 : US9392300 (https://patents.google.com/patent/US9392300/en) :
2029-11-04 : 2008-09-03 : US10298954 (https://patents.google.com/patent/US10298954/en) :
2029-11-10 : 2008-09-03 : US9654798 (https://patents.google.com/patent/US9654798/en) :
2029-11-21 : 2008-10-01 : US10321137 (https://patents.google.com/patent/US10321137/en) : litigation
2029-12-12 : 2008-10-01 : US8363965 (https://patents.google.com/patent/US8363965/en) : litigation
2030-01-07 : 2008-06-26 : US9992510 (https://patents.google.com/patent/US9992510/en) :
2030-01-15 : 2009-01-23 : CN102362498 (https://patents.google.com/patent/CN102362498/en) :
2030-01-15 : 2009-01-23 : CN104935939 (https://patents.google.com/patent/CN104935939/en) :
2030-01-15 : 2009-01-23 : CN105072448 (https://patents.google.com/patent/CN105072448/en) :
2030-01-15 : 2009-01-23 : CN105072449 (https://patents.google.com/patent/CN105072449/en) :
2030-01-15 : 2009-01-23 : US9070179 (https://patents.google.com/patent/US9070179/en) :
2030-01-15 : 2009-01-23 : US9363531 (https://patents.google.com/patent/US9363531/en) :
2030-01-15 : 2009-01-23 : US9420304 (https://patents.google.com/patent/US9420304/en) :
2030-01-15 : 2009-01-23 : US9445118 (https://patents.google.com/patent/US9445118/en) :
2030-01-18 : 2008-10-01 : US10178393 (https://patents.google.com/patent/US10178393/en) : litigation
2030-02-05 : 2006-01-12 : US8611413 (https://patents.google.com/patent/US8611413/en) :
2030-02-23 : 2009-02-23 : CN102369733 (https://patents.google.com/patent/CN102369733/en) : litigation
2030-02-23 : 2009-02-23 : CN105959689 (https://patents.google.com/patent/CN105959689/en) : litigation
2030-02-23 : 2009-02-23 : CN105959690 (https://patents.google.com/patent/CN105959690/en) : litigation
2030-02-23 : 2009-02-23 : CN105959691 (https://patents.google.com/patent/CN105959691/en) : litigation
2030-02-23 : 2009-02-23 : CN105959692 (https://patents.google.com/patent/CN105959692/en) : litigation
2030-02-23 : 2009-02-23 : JP6164600 (https://patents.google.com/patent/JP6164600/en) : litigation
2030-02-23 : 2009-02-23 : JP6164660 (https://patents.google.com/patent/JP6164660/en) : litigation
2030-02-23 : 2009-02-23 : JP6846988 (https://patents.google.com/patent/JP6846988/en) : litigation
2030-02-23 : 2009-02-23 : JP6851263 (https://patents.google.com/patent/JP6851263/en) : litigation
2030-02-23 : 2009-02-23 : JP6851264 (https://patents.google.com/patent/JP6851264/en) : litigation
2030-02-23 : 2009-02-23 : JP6851265 (https://patents.google.com/patent/JP6851265/en) : litigation
2030-02-23 : 2009-02-23 : JP7171646 (https://patents.google.com/patent/JP7171646/en) : litigation
2030-02-23 : 2009-02-23 : US10462494 (https://patents.google.com/patent/US10462494/en) : litigation
2030-02-23 : 2009-02-23 : US11076175 (https://patents.google.com/patent/US11076175/en) : litigation
2030-02-23 : 2009-02-23 : US9838719 (https://patents.google.com/patent/US9838719/en) : litigation
2030-02-23 : 2009-02-23 : US9838721 (https://patents.google.com/patent/US9838721/en) : litigation
2030-02-23 : 2009-02-23 : US9838722 (https://patents.google.com/patent/US9838722/en) : litigation
2030-02-23 : 2009-02-23 : US9888259 (https://patents.google.com/patent/US9888259/en) : litigation
2030-03-16 : 2009-03-23 : AU2010228415 (https://patents.google.com/patent/AU2010228415/en) :
2030-03-16 : 2009-03-23 : AU2016201339 (https://patents.google.com/patent/AU2016201339/en) :
2030-03-16 : 2009-03-23 : AU2017265185 (https://patents.google.com/patent/AU2017265185/en) :
2030-03-16 : 2009-03-23 : CA2756419 (https://patents.google.com/patent/CA2756419/en) :
2030-03-16 : 2009-03-23 : CA2921802 (https://patents.google.com/patent/CA2921802/en) :
2030-03-16 : 2009-03-23 : CA3000726 (https://patents.google.com/patent/CA3000726/en) :
2030-03-16 : 2009-03-23 : CA3000728 (https://patents.google.com/patent/CA3000728/en) :
2030-03-16 : 2009-03-23 : CN102362500 (https://patents.google.com/patent/CN102362500/en) :
2030-03-16 : 2009-03-23 : CN104065961 (https://patents.google.com/patent/CN104065961/en) :
2030-03-16 : 2009-03-23 : EP2988500 (https://patents.google.com/patent/EP2988500/en) :
2030-03-16 : 2009-03-23 : JP5586101 (https://patents.google.com/patent/JP5586101/en) :
2030-03-16 : 2009-03-23 : JP5779270 (https://patents.google.com/patent/JP5779270/en) :
2030-03-16 : 2009-03-23 : JP6000398 (https://patents.google.com/patent/JP6000398/en) :
2030-03-16 : 2009-03-23 : JP6220023 (https://patents.google.com/patent/JP6220023/en) :
2030-03-16 : 2009-03-23 : JP6405432 (https://patents.google.com/patent/JP6405432/en) :
2030-03-16 : 2009-03-23 : US10063855 (https://patents.google.com/patent/US10063855/en) :
2030-03-16 : 2009-03-23 : US10284846 (https://patents.google.com/patent/US10284846/en) :
2030-03-16 : 2009-03-23 : US10284847 (https://patents.google.com/patent/US10284847/en) :
2030-03-16 : 2009-03-23 : US10284848 (https://patents.google.com/patent/US10284848/en) :
2030-03-16 : 2009-03-23 : US9549186 (https://patents.google.com/patent/US9549186/en) :
2030-03-17 : 2014-01-30 : JP5753595 (https://patents.google.com/patent/JP5753595/en) :
2030-03-17 : 2015-03-16 : JP5977852 (https://patents.google.com/patent/JP5977852/en) :
2030-03-17 : 2016-07-22 : JP6229023 (https://patents.google.com/patent/JP6229023/en) :
2030-04-13 : 2009-02-23 : US11659210 (https://patents.google.com/patent/US11659210/en) : litigation
2030-04-13 : 2010-04-13 : CN102939750 (https://patents.google.com/patent/CN102939750/en) : litigation
2030-04-13 : 2010-04-13 : CN105872562 (https://patents.google.com/patent/CN105872562/en) : litigation
2030-04-13 : 2010-04-13 : CN106028045 (https://patents.google.com/patent/CN106028045/en) : litigation
2030-04-13 : 2010-04-13 : CN106067983 (https://patents.google.com/patent/CN106067983/en) : litigation
2030-04-13 : 2010-04-13 : US10855991 (https://patents.google.com/patent/US10855991/en) : litigation
2030-05-13 : 2008-06-26 : US9369714 (https://patents.google.com/patent/US9369714/en) :
2030-06-13 : 2008-10-31 : US9955182 (https://patents.google.com/patent/US9955182/en) :
2030-06-17 : 2009-06-19 : CN102804768 (https://patents.google.com/patent/CN102804768/en) : litigation

[oibaf]

AV1 Part 2:

2030-06-17 : 2009-06-19 : EP2443835 (https://patents.google.com/patent/EP2443835/en) : litigation
2030-06-25 : 2009-07-03 : CN102484711 (https://patents.google.com/patent/CN102484711/en) :
2030-06-25 : 2009-07-03 : CN102498718 (https://patents.google.com/patent/CN102498718/en) :
2030-06-27 : 2008-10-31 : US9781445 (https://patents.google.com/patent/US9781445/en) :
2030-06-27 : 2008-10-31 : US9794590 (https://patents.google.com/patent/US9794590/en) :
2030-07-04 : 2006-08-17 : US8548060 (https://patents.google.com/patent/US8548060/en) : litigation
2030-07-27 : 2007-06-29 : US9100038 (https://patents.google.com/patent/US9100038/en) :
2030-08-24 : 2006-01-09 : US9749660 (https://patents.google.com/patent/US9749660/en) : litigation
2030-08-25 : 2008-06-24 : US9363532 (https://patents.google.com/patent/US9363532/en) :
2030-09-03 : 2009-09-14 : CN102598669 (https://patents.google.com/patent/CN102598669/en) :
2030-09-03 : 2009-09-14 : CN104506875 (https://patents.google.com/patent/CN104506875/en) :
2030-09-03 : 2009-09-14 : CN104506876 (https://patents.google.com/patent/CN104506876/en) :
2030-09-03 : 2009-09-14 : CN104539957 (https://patents.google.com/patent/CN104539957/en) :
2030-09-03 : 2009-09-14 : CN104539974 (https://patents.google.com/patent/CN104539974/en) :
2030-09-03 : 2009-09-14 : US9584810 (https://patents.google.com/patent/US9584810/en) :
2030-09-24 : 2010-01-07 : CN102763416 (https://patents.google.com/patent/CN102763416/en) :
2030-09-24 : 2010-01-07 : CN103024391 (https://patents.google.com/patent/CN103024391/en) :
2030-09-24 : 2010-01-07 : US9143777 (https://patents.google.com/patent/US9143777/en) :
2030-09-24 : 2010-01-07 : US9148659 (https://patents.google.com/patent/US9148659/en) :
2030-09-24 : 2010-01-07 : US9154779 (https://patents.google.com/patent/US9154779/en) :
2030-09-24 : 2010-01-07 : US9294768 (https://patents.google.com/patent/US9294768/en) :
2030-09-24 : 2010-01-07 : US9392282 (https://patents.google.com/patent/US9392282/en) :
2030-10-01 : 2009-10-01 : US9609334 (https://patents.google.com/patent/US9609334/en) :
2030-10-01 : 2009-10-01 : US9609335 (https://patents.google.com/patent/US9609335/en) :
2030-10-06 : 2009-09-14 : US9621895 (https://patents.google.com/patent/US9621895/en) :
2030-10-12 : 2009-02-23 : US9485512 (https://patents.google.com/patent/US9485512/en) : litigation
2030-10-13 : 2008-02-21 : US8787685 (https://patents.google.com/patent/US8787685/en) :
2030-10-21 : 2009-10-21 : CN102668565 (https://patents.google.com/patent/CN102668565/en) :
2030-10-21 : 2009-10-21 : CN104661026 (https://patents.google.com/patent/CN104661026/en) :
2030-10-21 : 2009-10-21 : CN104935934 (https://patents.google.com/patent/CN104935934/en) :
2030-10-21 : 2009-10-21 : CN104935935 (https://patents.google.com/patent/CN104935935/en) :
2030-10-21 : 2009-10-21 : CN104954799 (https://patents.google.com/patent/CN104954799/en) :
2030-10-21 : 2009-10-21 : US9344731 (https://patents.google.com/patent/US9344731/en) :
2030-10-21 : 2009-10-21 : US9344732 (https://patents.google.com/patent/US9344732/en) :
2030-11-05 : 2004-08-16 : US9402087 (https://patents.google.com/patent/US9402087/en) :
2030-11-30 : 2008-08-04 : US9445121 (https://patents.google.com/patent/US9445121/en) :
2031-01-19 : 2008-10-14 : US9137546 (https://patents.google.com/patent/US9137546/en) :
2031-02-02 : 2008-04-15 : US8787693 (https://patents.google.com/patent/US8787693/en) :
2031-03-14 : 2010-03-17 : CA2793168 (https://patents.google.com/patent/CA2793168/en) :
2031-03-14 : 2010-03-17 : CN102792696 (https://patents.google.com/patent/CN102792696/en) :
2031-03-14 : 2010-03-17 : CN104768020 (https://patents.google.com/patent/CN104768020/en) :
2031-03-14 : 2010-03-17 : CN105187842 (https://patents.google.com/patent/CN105187842/en) :
2031-03-14 : 2010-03-17 : EP2549758 (https://patents.google.com/patent/EP2549758/en) :
2031-03-14 : 2010-03-17 : US10298953 (https://patents.google.com/patent/US10298953/en) :
2031-03-14 : 2010-03-17 : US10390042 (https://patents.google.com/patent/US10390042/en) :
2031-03-14 : 2010-03-17 : US10715829 (https://patents.google.com/patent/US10715829/en) :
2031-03-18 : 2008-10-01 : US8818114 (https://patents.google.com/patent/US8818114/en) :
2031-03-31 : 2010-04-09 : CA2795425 (https://patents.google.com/patent/CA2795425/en) :
2031-03-31 : 2010-04-09 : CN106998473 (https://patents.google.com/patent/CN106998473/en) :
2031-03-31 : 2010-04-09 : CN107046644 (https://patents.google.com/patent/CN107046644/en) :
2031-03-31 : 2010-04-09 : US10390011 (https://patents.google.com/patent/US10390011/en) :
2031-03-31 : 2010-04-09 : US10412385 (https://patents.google.com/patent/US10412385/en) :
2031-03-31 : 2010-04-09 : US10469839 (https://patents.google.com/patent/US10469839/en) :
2031-03-31 : 2010-04-09 : US10554970 (https://patents.google.com/patent/US10554970/en) :
2031-03-31 : 2010-04-09 : US9973753 (https://patents.google.com/patent/US9973753/en) :
2031-04-08 : 2010-04-13 : CN102893608 (https://patents.google.com/patent/CN102893608/en) : litigation
2031-04-08 : 2010-04-13 : CN105120287 (https://patents.google.com/patent/CN105120287/en) : litigation
2031-04-08 : 2010-04-13 : CN106231324 (https://patents.google.com/patent/CN106231324/en) : litigation
2031-04-08 : 2010-04-13 : CN106231329 (https://patents.google.com/patent/CN106231329/en) : litigation
2031-04-08 : 2010-04-13 : CN106231330 (https://patents.google.com/patent/CN106231330/en) : litigation
2031-04-08 : 2010-04-13 : CN106231334 (https://patents.google.com/patent/CN106231334/en) : litigation
2031-04-08 : 2010-04-13 : CN106231335 (https://patents.google.com/patent/CN106231335/en) : litigation
2031-04-08 : 2010-04-13 : CN106231338 (https://patents.google.com/patent/CN106231338/en) : litigation
2031-04-08 : 2010-04-13 : CN106358045 (https://patents.google.com/patent/CN106358045/en) : litigation
2031-04-08 : 2010-04-13 : US10856013 (https://patents.google.com/patent/US10856013/en) : litigation
2031-04-11 : 2010-04-09 : CN102939761 (https://patents.google.com/patent/CN102939761/en) : litigation
2031-04-11 : 2010-04-09 : CN104902283 (https://patents.google.com/patent/CN104902283/en) : litigation
2031-04-11 : 2010-04-09 : CN104994395 (https://patents.google.com/patent/CN104994395/en) : litigation
2031-04-11 : 2010-04-09 : CN104994396 (https://patents.google.com/patent/CN104994396/en) : litigation
2031-04-11 : 2010-04-09 : CN106060566 (https://patents.google.com/patent/CN106060566/en) : litigation
2031-04-11 : 2010-04-09 : JP5583840 (https://patents.google.com/patent/JP5583840/en) : litigation
2031-04-11 : 2010-04-09 : JP6313497 (https://patents.google.com/patent/JP6313497/en) : litigation
2031-04-11 : 2010-04-09 : US10075734 (https://patents.google.com/patent/US10075734/en) : litigation
2031-04-11 : 2010-04-09 : US9838711 (https://patents.google.com/patent/US9838711/en) : litigation
2031-04-11 : 2010-04-13 : CN108471534 (https://patents.google.com/patent/CN108471534/en) : litigation
2031-04-11 : 2010-04-13 : CN108471537 (https://patents.google.com/patent/CN108471537/en) : litigation
2031-04-11 : 2010-04-13 : US10129549 (https://patents.google.com/patent/US10129549/en) : litigation
2031-04-11 : 2010-04-13 : US10341668 (https://patents.google.com/patent/US10341668/en) : litigation
2031-04-11 : 2010-04-13 : US10477223 (https://patents.google.com/patent/US10477223/en) : litigation
2031-04-11 : 2010-04-13 : US10587884 (https://patents.google.com/patent/US10587884/en) : litigation
2031-04-13 : 2010-04-13 : US10460344 (https://patents.google.com/patent/US10460344/en) : litigation
2031-04-13 : 2010-04-13 : US10748183 (https://patents.google.com/patent/US10748183/en) : litigation
2031-05-12 : 2010-05-12 : CN102986219 (https://patents.google.com/patent/CN102986219/en) : litigation
2031-05-12 : 2010-05-12 : CN105163131 (https://patents.google.com/patent/CN105163131/en) : litigation
2031-05-12 : 2010-05-12 : EP2571269 (https://patents.google.com/patent/EP2571269/en) : litigation
2031-05-12 : 2010-05-12 : EP3119091 (https://patents.google.com/patent/EP3119091/en) : litigation
2031-05-12 : 2010-05-12 : EP3128755 (https://patents.google.com/patent/EP3128755/en) : litigation
2031-05-12 : 2010-05-12 : US9532065 (https://patents.google.com/patent/US9532065/en) : litigation
2031-05-12 : 2010-05-12 : US9787988 (https://patents.google.com/patent/US9787988/en) : litigation
2031-05-16 : 2008-10-01 : US8867854 (https://patents.google.com/patent/US8867854/en) : litigation
2031-05-22 : 2001-03-02 : US8374237 (https://patents.google.com/patent/US8374237/en) :
2031-05-25 : 2010-05-12 : US9479791 (https://patents.google.com/patent/US9479791/en) : litigation
2031-06-11 : 2009-06-19 : US8891628 (https://patents.google.com/patent/US8891628/en) : litigation
2031-06-22 : 2009-03-23 : US9031125 (https://patents.google.com/patent/US9031125/en) :
2031-06-22 : 2009-07-03 : US9185425 (https://patents.google.com/patent/US9185425/en) :
2031-06-23 : 2013-08-30 : JP5679019 (https://patents.google.com/patent/JP5679019/en) :
2031-06-23 : 2013-08-30 : JP5725107 (https://patents.google.com/patent/JP5725107/en) :
2031-06-23 : 2013-08-30 : JP5725108 (https://patents.google.com/patent/JP5725108/en) :
2031-06-23 : 2014-09-05 : JP5839094 (https://patents.google.com/patent/JP5839094/en) :
2031-06-23 : 2015-09-09 : JP5839143 (https://patents.google.com/patent/JP5839143/en) :
2031-06-23 : 2015-09-09 : JP5839144 (https://patents.google.com/patent/JP5839144/en) :
2031-07-14 : 2010-07-20 : CN103004206 (https://patents.google.com/patent/CN103004206/en) : litigation
2031-07-21 : 2010-09-30 : CA2813232 (https://patents.google.com/patent/CA2813232/en) : litigation
2031-07-21 : 2010-09-30 : CA3033984 (https://patents.google.com/patent/CA3033984/en) : litigation
2031-07-21 : 2010-09-30 : CN103222265 (https://patents.google.com/patent/CN103222265/en) : litigation
2031-07-21 : 2010-09-30 : CN106454379 (https://patents.google.com/patent/CN106454379/en) : litigation
2031-07-21 : 2010-09-30 : CN106488249 (https://patents.google.com/patent/CN106488249/en) : litigation
2031-07-21 : 2010-09-30 : CN106713930 (https://patents.google.com/patent/CN106713930/en) : litigation
2031-07-21 : 2010-09-30 : CN106713931 (https://patents.google.com/patent/CN106713931/en) : litigation
2031-07-21 : 2010-09-30 : JP5486091 (https://patents.google.com/patent/JP5486091/en) : litigation
2031-07-21 : 2010-09-30 : JP6071922 (https://patents.google.com/patent/JP6071922/en) : litigation
2031-07-21 : 2010-09-30 : JP6312787 (https://patents.google.com/patent/JP6312787/en) : litigation
2031-07-21 : 2010-09-30 : JP6768017 (https://patents.google.com/patent/JP6768017/en) : litigation
2031-08-17 : 2010-08-17 : CN103069800 (https://patents.google.com/patent/CN103069800/en) :
2031-08-17 : 2010-08-17 : CN105939476 (https://patents.google.com/patent/CN105939476/en) :
2031-08-17 : 2010-08-17 : CN106028037 (https://patents.google.com/patent/CN106028037/en) :
2031-08-17 : 2010-08-17 : CN106028038 (https://patents.google.com/patent/CN106028038/en) :
2031-08-17 : 2010-08-17 : CN106412587 (https://patents.google.com/patent/CN106412587/en) :
2031-08-17 : 2010-08-17 : EP2608540 (https://patents.google.com/patent/EP2608540/en) :
2031-08-17 : 2010-08-17 : JP6163176 (https://patents.google.com/patent/JP6163176/en) :
2031-08-17 : 2010-08-17 : JP6293943 (https://patents.google.com/patent/JP6293943/en) :
2031-08-17 : 2010-08-17 : JP6615922 (https://patents.google.com/patent/JP6615922/en) :
2031-08-17 : 2010-08-17 : JP6615923 (https://patents.google.com/patent/JP6615923/en) :
2031-08-17 : 2010-08-17 : JP6620181 (https://patents.google.com/patent/JP6620181/en) :
2031-08-17 : 2010-08-17 : US10212422 (https://patents.google.com/patent/US10212422/en) :
2031-08-17 : 2010-08-17 : US9838691 (https://patents.google.com/patent/US9838691/en) :
2031-08-25 : 2010-04-09 : US9781448 (https://patents.google.com/patent/US9781448/en) : litigation
2031-09-26 : 2008-10-31 : US9549184 (https://patents.google.com/patent/US9549184/en) :
2031-09-29 : 2010-10-06 : AU2015200190 (https://patents.google.com/patent/AU2015200190/en) :
2031-09-29 : 2010-10-06 : AU2015202089 (https://patents.google.com/patent/AU2015202089/en) :
2031-09-29 : 2010-10-06 : AU2016253586 (https://patents.google.com/patent/AU2016253586/en) :
2031-09-29 : 2010-10-06 : CA2813377 (https://patents.google.com/patent/CA2813377/en) :
2031-09-29 : 2010-10-06 : CN105338364 (https://patents.google.com/patent/CN105338364/en) :
2031-09-29 : 2010-10-06 : CN106131569 (https://patents.google.com/patent/CN106131569/en) :
2031-09-29 : 2010-10-06 : CN106210737 (https://patents.google.com/patent/CN106210737/en) :
2031-09-29 : 2010-10-06 : CN106210738 (https://patents.google.com/patent/CN106210738/en) :
2031-09-29 : 2010-10-06 : JP5575910 (https://patents.google.com/patent/JP5575910/en) :
2031-09-29 : 2010-10-06 : JP5774753 (https://patents.google.com/patent/JP5774753/en) :
2031-09-29 : 2010-10-06 : JP5982537 (https://patents.google.com/patent/JP5982537/en) :
2031-09-29 : 2010-10-06 : US10440383 (https://patents.google.com/patent/US10440383/en) :
2031-09-29 : 2010-10-06 : US8873874 (https://patents.google.com/patent/US8873874/en) :
2031-10-04 : 2010-10-04 : CN103262541 (https://patents.google.com/patent/CN103262541/en) : litigation
2031-10-04 : 2010-10-04 : CN106101730 (https://patents.google.com/patent/CN106101730/en) : litigation
2031-10-04 : 2010-10-04 : CN106131576 (https://patents.google.com/patent/CN106131576/en) : litigation
2031-10-04 : 2010-10-04 : CN106131577 (https://patents.google.com/patent/CN106131577/en) : litigation
2031-10-04 : 2010-10-04 : CN106254890 (https://patents.google.com/patent/CN106254890/en) : litigation
2031-10-04 : 2010-10-04 : EP2627085 (https://patents.google.com/patent/EP2627085/en) : litigation
2031-10-04 : 2010-10-04 : JP5612215 (https://patents.google.com/patent/JP5612215/en) : litigation
2031-10-04 : 2010-10-04 : JP5998180 (https://patents.google.com/patent/JP5998180/en) : litigation
2031-10-04 : 2010-10-04 : JP6437494 (https://patents.google.com/patent/JP6437494/en) : litigation
2031-10-04 : 2010-10-04 : JP6855419 (https://patents.google.com/patent/JP6855419/en) : litigation
2031-10-04 : 2010-10-04 : JP7284137 (https://patents.google.com/patent/JP7284137/en) : litigation

[oibaf]

AV1 Part 3:

2031-10-04 : 2010-10-04 : US10110912 (https://patents.google.com/patent/US10110912/en) : litigation
2031-10-04 : 2010-10-04 : US10560709 (https://patents.google.com/patent/US10560709/en) : litigation
2031-10-04 : 2010-10-04 : US10567782 (https://patents.google.com/patent/US10567782/en) : litigation
2031-10-04 : 2010-10-04 : US10674169 (https://patents.google.com/patent/US10674169/en) : litigation
2031-10-04 : 2010-10-04 : US11223839 (https://patents.google.com/patent/US11223839/en) : litigation
2031-10-04 : 2010-10-04 : US9860546 (https://patents.google.com/patent/US9860546/en) : litigation
2031-10-13 : 2010-03-17 : US10178407 (https://patents.google.com/patent/US10178407/en) :
2031-11-04 : 2010-11-04 : CN103299623 (https://patents.google.com/patent/CN103299623/en) :
2031-11-04 : 2010-11-04 : CN107071487 (https://patents.google.com/patent/CN107071487/en) :
2031-11-04 : 2010-11-04 : CN107071489 (https://patents.google.com/patent/CN107071489/en) :
2031-11-04 : 2010-11-04 : CN107071491 (https://patents.google.com/patent/CN107071491/en) :
2031-11-04 : 2010-11-04 : CN107071492 (https://patents.google.com/patent/CN107071492/en) :
2031-11-04 : 2010-11-04 : JP6856554 (https://patents.google.com/patent/JP6856554/en) :
2031-11-07 : 2016-04-13 : JP6134418 (https://patents.google.com/patent/JP6134418/en) :
2031-11-08 : 2010-08-17 : US10827174 (https://patents.google.com/patent/US10827174/en) :
2031-11-12 : 2010-01-07 : US9113139 (https://patents.google.com/patent/US9113139/en) :
2031-11-26 : 2010-08-17 : US10939106 (https://patents.google.com/patent/US10939106/en) :
2031-11-27 : 2009-07-03 : US10051283 (https://patents.google.com/patent/US10051283/en) :
2031-12-06 : 2010-12-06 : CN103238327 (https://patents.google.com/patent/CN103238327/en) :
2031-12-06 : 2010-12-06 : CN105611292 (https://patents.google.com/patent/CN105611292/en) :
2031-12-06 : 2010-12-06 : US9510017 (https://patents.google.com/patent/US9510017/en) :
2031-12-15 : 2010-12-15 : CN103262538 (https://patents.google.com/patent/CN103262538/en) :
2031-12-15 : 2010-12-15 : CN105828085 (https://patents.google.com/patent/CN105828085/en) :
2031-12-15 : 2010-12-15 : CN105847832 (https://patents.google.com/patent/CN105847832/en) :
2031-12-15 : 2010-12-15 : CN105847833 (https://patents.google.com/patent/CN105847833/en) :
2031-12-15 : 2010-12-15 : CN105847834 (https://patents.google.com/patent/CN105847834/en) :
2031-12-20 : 2011-01-07 : JP5859691 (https://patents.google.com/patent/JP5859691/en) :
2031-12-21 : 2010-12-21 : CN104811702 (https://patents.google.com/patent/CN104811702/en) :
2031-12-21 : 2010-12-21 : CN104811714 (https://patents.google.com/patent/CN104811714/en) :
2031-12-21 : 2010-12-21 : EP2656507 (https://patents.google.com/patent/EP2656507/en) :
2031-12-21 : 2010-12-21 : EP2996334 (https://patents.google.com/patent/EP2996334/en) :
2031-12-21 : 2010-12-21 : EP3373579 (https://patents.google.com/patent/EP3373579/en) :
2031-12-21 : 2010-12-21 : EP3373581 (https://patents.google.com/patent/EP3373581/en) :
2031-12-21 : 2010-12-21 : JP5960316 (https://patents.google.com/patent/JP5960316/en) :
2031-12-21 : 2010-12-21 : US10205963 (https://patents.google.com/patent/US10205963/en) :
2031-12-21 : 2010-12-21 : US10805632 (https://patents.google.com/patent/US10805632/en) :
2031-12-21 : 2010-12-21 : US10841611 (https://patents.google.com/patent/US10841611/en) :
2031-12-22 : 2010-04-09 : US9549204 (https://patents.google.com/patent/US9549204/en) : litigation
2031-12-25 : 2010-12-15 : US9888248 (https://patents.google.com/patent/US9888248/en) :
2031-12-28 : 2010-12-28 : CN103314581 (https://patents.google.com/patent/CN103314581/en) : litigation
2031-12-28 : 2010-12-28 : CN106412577 (https://patents.google.com/patent/CN106412577/en) : litigation
2031-12-28 : 2010-12-28 : CN106454339 (https://patents.google.com/patent/CN106454339/en) : litigation
2031-12-28 : 2010-12-28 : CN106488228 (https://patents.google.com/patent/CN106488228/en) : litigation
2031-12-28 : 2010-12-28 : CN106851268 (https://patents.google.com/patent/CN106851268/en) : litigation
2031-12-28 : 2010-12-28 : CN107071407 (https://patents.google.com/patent/CN107071407/en) : litigation
2031-12-28 : 2010-12-28 : CN107071408 (https://patents.google.com/patent/CN107071408/en) : litigation
2031-12-28 : 2010-12-28 : CN107105230 (https://patents.google.com/patent/CN107105230/en) : litigation
2032-01-01 : 2010-12-21 : US10771812 (https://patents.google.com/patent/US10771812/en) :
2032-01-12 : 2011-01-14 : CN103404035 (https://patents.google.com/patent/CN103404035/en) :
2032-01-12 : 2011-01-14 : JP6849835 (https://patents.google.com/patent/JP6849835/en) :
2032-01-12 : 2011-01-14 : US10404272 (https://patents.google.com/patent/US10404272/en) :
2032-01-12 : 2011-01-14 : US10644719 (https://patents.google.com/patent/US10644719/en) :
2032-01-28 : 2010-12-21 : US10834423 (https://patents.google.com/patent/US10834423/en) :
2032-01-31 : 2011-01-31 : CA2826157 (https://patents.google.com/patent/CA2826157/en) : litigation
2032-01-31 : 2011-01-31 : CN103583044 (https://patents.google.com/patent/CN103583044/en) : litigation
2032-01-31 : 2011-01-31 : JP5911890 (https://patents.google.com/patent/JP5911890/en) : litigation
2032-01-31 : 2011-01-31 : JP6203878 (https://patents.google.com/patent/JP6203878/en) : litigation
2032-01-31 : 2011-01-31 : JP6550429 (https://patents.google.com/patent/JP6550429/en) : litigation
2032-02-24 : 2008-10-31 : US8976863 (https://patents.google.com/patent/US8976863/en) :
2032-03-20 : 2010-09-30 : US9900611 (https://patents.google.com/patent/US9900611/en) : litigation
2032-04-10 : 2010-10-04 : US9544595 (https://patents.google.com/patent/US9544595/en) : litigation
2032-04-12 : 2011-04-12 : CN103548356 (https://patents.google.com/patent/CN103548356/en) :
2032-04-12 : 2011-04-12 : CN107623857 (https://patents.google.com/patent/CN107623857/en) :
2032-04-12 : 2011-04-12 : CN107888929 (https://patents.google.com/patent/CN107888929/en) :
2032-04-12 : 2011-04-12 : US10575014 (https://patents.google.com/patent/US10575014/en) :
2032-04-12 : 2011-04-12 : US10992956 (https://patents.google.com/patent/US10992956/en) :
2032-04-12 : 2011-04-12 : US11523133 (https://patents.google.com/patent/US11523133/en) :
2032-04-24 : 2011-04-27 : JP5880613 (https://patents.google.com/patent/JP5880613/en) :
2032-04-25 : 2011-04-27 : US10911774 (https://patents.google.com/patent/US10911774/en) :
2032-04-25 : 2011-04-27 : US11445212 (https://patents.google.com/patent/US11445212/en) :
2032-04-25 : 2011-04-27 : US11812052 (https://patents.google.com/patent/US11812052/en) :
2032-05-08 : 2008-06-24 : US8976862 (https://patents.google.com/patent/US8976862/en) :
2032-05-17 : 2011-05-27 : CN103563347 (https://patents.google.com/patent/CN103563347/en) :
2032-05-17 : 2011-05-27 : CN103873738 (https://patents.google.com/patent/CN103873738/en) :
2032-05-17 : 2011-05-27 : CN105933573 (https://patents.google.com/patent/CN105933573/en) :
2032-05-17 : 2011-05-27 : CN106101483 (https://patents.google.com/patent/CN106101483/en) :
2032-05-17 : 2011-05-27 : CN106357955 (https://patents.google.com/patent/CN106357955/en) :
2032-05-17 : 2011-05-27 : EP3595281 (https://patents.google.com/patent/EP3595281/en) :
2032-05-17 : 2011-05-27 : JP5833233 (https://patents.google.com/patent/JP5833233/en) :
2032-05-17 : 2011-05-27 : JP6224052 (https://patents.google.com/patent/JP6224052/en) :
2032-05-17 : 2011-05-27 : JP6561098 (https://patents.google.com/patent/JP6561098/en) :
2032-05-17 : 2011-05-27 : JP6905010 (https://patents.google.com/patent/JP6905010/en) :
2032-05-17 : 2011-05-27 : JP7145290 (https://patents.google.com/patent/JP7145290/en) :
2032-05-17 : 2011-05-27 : JP7422832 (https://patents.google.com/patent/JP7422832/en) :
2032-05-17 : 2011-05-27 : US11736703 (https://patents.google.com/patent/US11736703/en) :
2032-05-17 : 2011-05-27 : US9111330 (https://patents.google.com/patent/US9111330/en) :
2032-05-18 : 2010-09-30 : US9894375 (https://patents.google.com/patent/US9894375/en) : litigation
2032-05-21 : 2010-09-30 : US9900612 (https://patents.google.com/patent/US9900612/en) : litigation
2032-05-23 : 2010-02-17 : US9794556 (https://patents.google.com/patent/US9794556/en) :
2032-05-26 : 2010-09-30 : US9894376 (https://patents.google.com/patent/US9894376/en) : litigation
2032-06-14 : 2010-01-07 : US9113138 (https://patents.google.com/patent/US9113138/en) :
2032-06-14 : 2011-06-23 : CN103621087 (https://patents.google.com/patent/CN103621087/en) :
2032-06-14 : 2011-06-23 : CN105791834 (https://patents.google.com/patent/CN105791834/en) :
2032-06-14 : 2011-06-23 : CN105812806 (https://patents.google.com/patent/CN105812806/en) :
2032-06-14 : 2011-06-23 : CN105812807 (https://patents.google.com/patent/CN105812807/en) :
2032-06-14 : 2011-06-23 : CN107071428 (https://patents.google.com/patent/CN107071428/en) :
2032-06-14 : 2011-06-23 : US8938003 (https://patents.google.com/patent/US8938003/en) :
2032-06-18 : 2011-06-16 : CN103748886 (https://patents.google.com/patent/CN103748886/en) : litigation
2032-06-18 : 2011-06-16 : CN107517383 (https://patents.google.com/patent/CN107517383/en) : litigation
2032-06-18 : 2011-06-16 : CN107613307 (https://patents.google.com/patent/CN107613307/en) : litigation
2032-06-18 : 2011-06-16 : CN107770559 (https://patents.google.com/patent/CN107770559/en) : litigation
2032-06-18 : 2011-06-16 : EP2721819 (https://patents.google.com/patent/EP2721819/en) : litigation
2032-06-18 : 2011-06-16 : JP5952900 (https://patents.google.com/patent/JP5952900/en) : litigation
2032-06-18 : 2011-06-16 : US10057603 (https://patents.google.com/patent/US10057603/en) : litigation
2032-06-18 : 2011-06-16 : US10313672 (https://patents.google.com/patent/US10313672/en) : litigation
2032-06-18 : 2011-06-16 : US10432939 (https://patents.google.com/patent/US10432939/en) : litigation
2032-06-18 : 2011-06-16 : US10630987 (https://patents.google.com/patent/US10630987/en) : litigation
2032-06-20 : 2011-06-20 : CA3011851 (https://patents.google.com/patent/CA3011851/en) : litigation
2032-06-20 : 2011-06-20 : CA3011853 (https://patents.google.com/patent/CA3011853/en) : litigation
2032-06-20 : 2011-06-20 : CA3011863 (https://patents.google.com/patent/CA3011863/en) : litigation
2032-06-20 : 2011-06-20 : US10205964 (https://patents.google.com/patent/US10205964/en) : litigation
2032-06-20 : 2011-06-20 : US11689742 (https://patents.google.com/patent/US11689742/en) : litigation
2032-06-20 : 2011-06-24 : CN107094252 (https://patents.google.com/patent/CN107094252/en) : litigation
2032-06-20 : 2011-06-24 : US10362311 (https://patents.google.com/patent/US10362311/en) : litigation
2032-06-20 : 2011-06-24 : US9319694 (https://patents.google.com/patent/US9319694/en) : litigation
2032-06-20 : 2011-06-24 : US9654783 (https://patents.google.com/patent/US9654783/en) : litigation
2032-06-20 : 2011-06-24 : US9661335 (https://patents.google.com/patent/US9661335/en) : litigation
2032-08-07 : 2010-03-17 : US9113171 (https://patents.google.com/patent/US9113171/en) :
2032-09-24 : 2012-09-24 : JP5798539 (https://patents.google.com/patent/JP5798539/en) :
2032-09-25 : 2011-11-07 : CN103891288 (https://patents.google.com/patent/CN103891288/en) :
2032-09-25 : 2011-11-07 : US10104392 (https://patents.google.com/patent/US10104392/en) :
2032-09-25 : 2011-11-07 : US10104393 (https://patents.google.com/patent/US10104393/en) :
2032-09-25 : 2011-11-07 : US9788005 (https://patents.google.com/patent/US9788005/en) :
2032-10-14 : 2010-07-20 : US9185409 (https://patents.google.com/patent/US9185409/en) : litigation
2032-10-31 : 2009-08-21 : US9154806 (https://patents.google.com/patent/US9154806/en) :
2032-11-09 : 2011-11-11 : US10574982 (https://patents.google.com/patent/US10574982/en) :
2032-11-21 : 2009-09-14 : US9154809 (https://patents.google.com/patent/US9154809/en) :
2032-12-05 : 2010-09-30 : US9369730 (https://patents.google.com/patent/US9369730/en) : litigation
2032-12-28 : 2012-04-20 : US8774540 (https://patents.google.com/patent/US8774540/en) :
2032-12-30 : 2009-10-01 : US9549190 (https://patents.google.com/patent/US9549190/en) :
2033-01-16 : 2009-10-21 : US9137545 (https://patents.google.com/patent/US9137545/en) :
2033-01-18 : 2010-12-15 : US9270996 (https://patents.google.com/patent/US9270996/en) :
2033-02-04 : 2011-01-31 : US10244252 (https://patents.google.com/patent/US10244252/en) : litigation
2033-02-12 : 2009-12-03 : US9473777 (https://patents.google.com/patent/US9473777/en) :
2033-03-28 : 2011-05-27 : US11218709 (https://patents.google.com/patent/US11218709/en) :
2033-06-17 : 2012-09-24 : AU2013319537 (https://patents.google.com/patent/AU2013319537/en) :
2033-06-17 : 2012-09-24 : AU2016202132 (https://patents.google.com/patent/AU2016202132/en) :
2033-06-17 : 2012-09-24 : CA2885802 (https://patents.google.com/patent/CA2885802/en) :
2033-06-17 : 2012-09-24 : CN104604238 (https://patents.google.com/patent/CN104604238/en) :
2033-06-17 : 2012-09-24 : CN106131558 (https://patents.google.com/patent/CN106131558/en) :
2033-06-17 : 2012-09-24 : CN106131559 (https://patents.google.com/patent/CN106131559/en) :
2033-06-17 : 2012-09-24 : EP2899982 (https://patents.google.com/patent/EP2899982/en) :
2033-06-17 : 2012-09-24 : US10110918 (https://patents.google.com/patent/US10110918/en) :
2033-06-17 : 2012-09-24 : US10123042 (https://patents.google.com/patent/US10123042/en) :
2033-06-25 : 2012-06-29 : CN104488270 (https://patents.google.com/patent/CN104488270/en) :
2033-06-25 : 2012-06-29 : US10341661 (https://patents.google.com/patent/US10341661/en) :
2033-06-25 : 2012-06-29 : US9628799 (https://patents.google.com/patent/US9628799/en) :
2033-06-25 : 2012-06-29 : US9635363 (https://patents.google.com/patent/US9635363/en) :
2033-06-25 : 2012-06-29 : US9641845 (https://patents.google.com/patent/US9641845/en) :
2033-06-25 : 2012-06-29 : US9723311 (https://patents.google.com/patent/US9723311/en) :
2033-06-29 : 2012-09-24 : US9736494 (https://patents.google.com/patent/US9736494/en) :
2033-07-17 : 2009-11-24 : US9288495 (https://patents.google.com/patent/US9288495/en) :
2033-09-06 : 2010-08-17 : US9699449 (https://patents.google.com/patent/US9699449/en) :
2033-09-06 : 2012-06-29 : US9497465 (https://patents.google.com/patent/US9497465/en) :

[oibaf]

AV1 Part 4:

2033-09-14 : 2011-11-07 : US9615088 (https://patents.google.com/patent/US9615088/en) :
2033-10-14 : 2012-10-15 : CN104813657 (https://patents.google.com/patent/CN104813657/en) :
2033-10-14 : 2012-10-15 : EP2907306 (https://patents.google.com/patent/EP2907306/en) :
2033-10-14 : 2012-10-15 : JP7028398 (https://patents.google.com/patent/JP7028398/en) :
2033-11-18 : 2012-06-29 : US11595655 (https://patents.google.com/patent/US11595655/en) :
2034-01-31 : 2010-12-06 : US9521427 (https://patents.google.com/patent/US9521427/en) :
2034-02-15 : 2011-04-27 : US10425657 (https://patents.google.com/patent/US10425657/en) :
2034-04-26 : 2011-06-16 : US9918090 (https://patents.google.com/patent/US9918090/en) : litigation
2035-09-23 : 2014-10-16 : JP6625628 (https://patents.google.com/patent/JP6625628/en) :
2036-05-19 : 2016-05-19 : JP6635551 (https://patents.google.com/patent/JP6635551/en) :
2036-11-18 : 2015-11-20 : US11425370 (https://patents.google.com/patent/US11425370/en) :
2036-11-18 : 2015-11-20 : US11516463 (https://patents.google.com/patent/US11516463/en) :
2036-11-18 : 2015-11-20 : US11758128 (https://patents.google.com/patent/US11758128/en) :
2036-11-24 : 2016-11-22 : US11218725 (https://patents.google.com/patent/US11218725/en) :
2036-11-24 : 2016-11-22 : US11711540 (https://patents.google.com/patent/US11711540/en) :
2037-03-27 : 2016-04-12 : CN109314789 (https://patents.google.com/patent/CN109314789/en) :
2037-03-27 : 2016-04-12 : US10757406 (https://patents.google.com/patent/US10757406/en) :
2037-03-27 : 2016-04-12 : US11272174 (https://patents.google.com/patent/US11272174/en) :
2037-04-26 : 2016-04-29 : US11140397 (https://patents.google.com/patent/US11140397/en) :
2037-04-28 : 2016-04-29 : CN109328461 (https://patents.google.com/patent/CN109328461/en) :
2037-04-28 : 2016-04-29 : US10805607 (https://patents.google.com/patent/US10805607/en) :
2037-04-28 : 2016-04-29 : US11363280 (https://patents.google.com/patent/US11363280/en) :
2037-10-10 : 2016-10-04 : US11902579 (https://patents.google.com/patent/US11902579/en) :
2037-10-10 : 2016-10-04 : US11902668 (https://patents.google.com/patent/US11902668/en) :
2037-10-10 : 2016-10-04 : US11910018 (https://patents.google.com/patent/US11910018/en) :
2037-10-10 : 2016-10-04 : US11949994 (https://patents.google.com/patent/US11949994/en) :
2037-10-10 : 2016-10-04 : US11956548 (https://patents.google.com/patent/US11956548/en) :
2037-10-10 : 2016-10-04 : US11956549 (https://patents.google.com/patent/US11956549/en) :
2037-10-10 : 2016-10-04 : US12003771 (https://patents.google.com/patent/US12003771/en) :
2037-10-10 : 2016-10-04 : US12015854 (https://patents.google.com/patent/US12015854/en) :
2037-10-10 : 2016-10-04 : US12069304 (https://patents.google.com/patent/US12069304/en) :
2037-10-10 : 2016-10-04 : US12096028 (https://patents.google.com/patent/US12096028/en) :
2037-10-10 : 2016-10-04 : US12108158 (https://patents.google.com/patent/US12108158/en) :
2037-10-10 : 2017-07-17 : JP7457861 (https://patents.google.com/patent/JP7457861/en) :
2037-10-12 : 2016-10-14 : CN109937570 (https://patents.google.com/patent/CN109937570/en) :
2037-10-12 : 2016-10-14 : US11902521 (https://patents.google.com/patent/US11902521/en) :
2037-10-12 : 2016-10-14 : US11909970 (https://patents.google.com/patent/US11909970/en) :
2037-10-13 : 2016-10-04 : US11539979 (https://patents.google.com/patent/US11539979/en) :
2037-10-28 : 2015-11-20 : US10944962 (https://patents.google.com/patent/US10944962/en) :
2037-11-22 : 2016-11-22 : US10848758 (https://patents.google.com/patent/US10848758/en) :
2037-11-22 : 2016-11-22 : US11343490 (https://patents.google.com/patent/US11343490/en) :
2037-11-22 : 2016-11-22 : US11825077 (https://patents.google.com/patent/US11825077/en) :
2037-12-26 : 2016-10-14 : US11039148 (https://patents.google.com/patent/US11039148/en) :
2038-01-16 : 2017-01-16 : CN110199520 (https://patents.google.com/patent/CN110199520/en) :
2038-01-16 : 2017-01-16 : US10951884 (https://patents.google.com/patent/US10951884/en) :
2038-01-16 : 2017-01-16 : US11665337 (https://patents.google.com/patent/US11665337/en) :
2038-01-30 : 2016-10-14 : US11057624 (https://patents.google.com/patent/US11057624/en) :
2038-05-20 : 2016-10-14 : US11792409 (https://patents.google.com/patent/US11792409/en) :
2038-06-03 : 2016-10-14 : US11659178 (https://patents.google.com/patent/US11659178/en) :

[hajj_3]

there are 27 licensors now.

28 avanci patent licensing pool licensors now. still no list of patents published or licensing cost.

[Avclover]

The next patent pool including AV1 about to start: https://accessadvance.com/2025/01/16/access-advance-announces-video-distribution-patent-pool-in-response-to-market-demand/

This means there are now three competing patent pools asking for money for "royalty-free" AV1...

[kurkosdr]

The next patent pool including AV1 about to start: https://accessadvance.com/2025/01/16/access-advance-announces-video-distribution-patent-pool-in-response-to-market-demand/

This means there are now three competing patent pools asking for money for "royalty-free" AV1...
And the fact none of those patent pools will go after the biggest user of AV1 (Google) tells you a lot about the sincerity behind those patent pools (and patent claims therein).

That said, OEMs like Samsung will pay up anyway because they are very risk-averse when it comes to IP. They are used to paying various royalties not just for video compression but also for wireless communications, storage, and wireless charging, so it's just another royalty for them.

So, everyone is happy, I guess. Google gets to stream AV1 without paying royalties to any patent pool, and Sisvel and Access Advance get to collect royalties from OEMs.

[hajj_3]

28 avanci patent licensing pool licensors now. still no list of patents published or licensing cost.

34 now.

[oibaf]

And the fact none of those patent pools will go after the biggest user of AV1 (Google) tells you a lot about the sincerity behind those patent pools (and patent claims therein).

That said, OEMs like Samsung will pay up anyway because they are very risk-averse when it comes to IP. They are used to paying various royalties not just for video compression but also for wireless communications, storage, and wireless charging, so it's just another royalty for them.

So, everyone is happy, I guess. Google gets to stream AV1 without paying royalties to any patent pool, and Sisvel and Access Advance get to collect royalties from OEMs.

Any source on who is paying or not paying these licenses?
Where did you find out that Google is not paying, while Samsung is paying?

[rwill]

And the fact none of those patent pools will go after the biggest user of AV1 (Google) tells you a lot about the sincerity behind those patent pools (and patent claims therein).

Any source on who the patent pools will go after and who not?

[kurkosdr]

Any source on who is paying or not paying these licenses?
Where did you find out that Google is not paying, while Samsung is paying?

Google maintains VP9 and AV1 are royalty-free, so it's safe to assume they aren't paying.
https://www.webmproject.org/about/faq/
And if they did, they are a public company that has to disclose such things, so we'd know:

About Samsung, I don't know, keep in mind I mentioned "OEMs like Samsung" in my previous post, not Samsung per-se, but I admit it's bad wording in retrospect. But Sisvel did manage to get some OEMs to sign up:
https://www.sisvel.com/news/sisvel-first-licensees-of-video-coding-licensing-platform/
https://www.businesswire.com/news/home/20211223005052/en/Sisvel-Signs-an-Agreement-Under-the-VP9-Patents-With-Panasonic-Corporation
Which, let's be real, is the companies Sisvel is really targeting, not Google.

Any source on who the patent pools will go after and who not?
No, I can't predict the future. But the fact those companies are letting Google build its services and products on what they claim is treasured intellectual property without doing anything about it for several years tells you a lot about how BS the claims are.

We've been here before with Microsoft claiming the Linux kernel infringes on Microsoft patents, without ever taking action against Linux, despite Linux eating their lunch in the server space.

Personally, I am an "I'll believe it when I see it" kind of person, so I will admit Sisvel's patent pools have any relevance to the VP9 and AV1 standards when I see a single successful patent lawsuit.

[hajj_3]

About Samsung, I don't know, keep in mind I mentioned "OEMs like Samsung" in my previous post, not Samsung per-se, but I admit it's bad wording in retrospect. But Sisvel did manage to get some OEMs to sign up:
https://www.sisvel.com/news/sisvel-first-licensees-of-video-coding-licensing-platform/
https://www.businesswire.com/news/home/20211223005052/en/Sisvel-Signs-an-Agreement-Under-the-VP9-Patents-With-Panasonic-Corporation
Which, let's be real, is the companies Sisvel is really targeting, not Google.

The licensees are also licensors. They licenced it in order to to try to give Sisvel's patent pool legitimacy.

[hajj_3]

Sisvel AV1 patent list was updated on 15th Jan 2025: https://www.sisvel.com/xlin7ipl485u/5VKBBH3LSEwAyT151R2j3E/7c28169befdd698856426a32a4c583f4/PatentList_AV1.pdf
Sisvel VP9 patent list was updated on 10th Jan 2025: https://www.sisvel.com/xlin7ipl485u/6OckyYnH49V6byT7dW7YsF/6106557ea446fdd2ef037580207deae8/PatentList_VP9.pdf

Not sure what changes there are since the list from October 2024.

[hajj_3]

Sisvel AV1 patent list was updated on 11th April 2025: https://www.sisvel.com/xlin7ipl485u/5VKBBH3LSEwAyT151R2j3E/0260413403f3ba69563d37a26bef3dd6/PatentList_AV1.pdf

There are 7 additional pages!!!

[oibaf]

Sisvel AV1 patent list was updated on 11th April 2025: https://www.sisvel.com/xlin7ipl485u/5VKBBH3LSEwAyT151R2j3E/0260413403f3ba69563d37a26bef3dd6/PatentList_AV1.pdf

There are 7 additional pages!!!

Do you know what they mean with "Family members" patents? Are they needed or not? If not, why they are there?

[benwaggoner]

Do you know what they mean with "Family members" patents? Are they needed or not? If not, why they are there?
It's common to get multiple patents that are slight variations on the same application. Together they get called a family.

For example I have 64 patent families: https://patents.google.com/?inventor=Benjamin+Waggoner&num=100&oq=inventor:(Benjamin+Waggoner)

But 94 patent publications: https://patents.google.com/?inventor=Benjamin+Waggoner&num=100&oq=inventor:(Benjamin+Waggoner)&dups=language

(and woah, that number snuck up on me. Almost 100!)

For example my "Object tracking in zoomed video" patent family has a bunch of different actual patent publications with variations and for different regions:

https://patents.google.com/patent/US10664140B2/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language
https://patents.google.com/patent/AU2015231761B2/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language
https://patents.google.com/patent/CA2942377C/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language
https://patents.google.com/patent/US9626084B2/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language
https://patents.google.com/patent/US20170177197A1/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language
https://patents.google.com/patent/WO2015142621A1/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language
https://patents.google.com/patent/EP3120228A1/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language
https://patents.google.com/patent/CA2942377A1/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language
https://patents.google.com/patent/EP3120228A4/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language


I'm hardly a patent law expert, so I am sure others understand how that became eight publications better than I do.

It's not one of my most important ones, but I imagine the "Jeffery P. Bezos" as a co-inventor probably made a difference ;).

(and no, I have never met him or directly collaborated with him).

[oibaf]

Interesting read! :)

Anyway, including all the "Family members" patents, there are not many changes between the active patents of the "15th Jan" and the "11th April" versions: 5 patents removed and 7 added. The 7 pages difference is likely due to page formatting issues (bigger font size or similar).

[hajj_3]

Sisvel AV1 patent list was updated on 23rd May 2025: https://www.sisvel.com/xlin7ipl485u/5VKBBH3LSEwAyT151R2j3E/7ad18eadc48ef2eb8aa60d9570560600/PatentList_AV1.pdf

There are 3 additional pages

[oibaf]

Sisvel AV1 patent list was updated on 23rd May 2025: https://www.sisvel.com/xlin7ipl485u/5VKBBH3LSEwAyT151R2j3E/7ad18eadc48ef2eb8aa60d9570560600/PatentList_AV1.pdf

There are 3 additional pages

They removed this https://www.unifiedpatents.com/insights/2025/5/23/kaistetri-patent-revocation-confirmed-by-epo-appeal and added a bunch of others...

[hajj_3]

Sisvel VP9 patent list was updated on June 18th, it has added 2 new pages: https://www.sisvel.com/xlin7ipl485u/6OckyYnH49V6byT7dW7YsF/b57043de3bc4f186389982a6d32ebcee/PatentList_VP9.pdf
Sisvel AV1 patent list was updated on June 18th, it has removed 7 pages: https://www.sisvel.com/xlin7ipl485u/5VKBBH3LSEwAyT151R2j3E/697d2a37cf81a5f9c2d156af2f75c4af/PatentList_AV1.pdf

[hajj_3]

Sisvel VP9 patent list was updated on July 30th: https://www.sisvel.com/xlin7ipl485u/6OckyYnH49V6byT7dW7YsF/c63ad018677e960bf18d6932bf89659e/PatentList_VP9.pdf
Sisvel AV1 patent list was updated on July 30th: https://www.sisvel.com/xlin7ipl485u/5VKBBH3LSEwAyT151R2j3E/0d53b51b72393178a998d8ccd6fba5af/PatentList_AV1.pdf

[hajj_3]

Sisvel AV1 patent list was updated on August 4th: https://www.sisvel.com/xlin7ipl485u/5VKBBH3LSEwAyT151R2j3E/00387f8eb8ea751a23b88a2f4b85441a/PatentList_AV1.pdf

[CruNcher]

It's common to get multiple patents that are slight variations on the same application. Together they get called a family.

For example I have 64 patent families: https://patents.google.com/?inventor=Benjamin+Waggoner&num=100&oq=inventor:(Benjamin+Waggoner)

But 94 patent publications: https://patents.google.com/?inventor=Benjamin+Waggoner&num=100&oq=inventor:(Benjamin+Waggoner)&dups=language

(and woah, that number snuck up on me. Almost 100!)

For example my "Object tracking in zoomed video" patent family has a bunch of different actual patent publications with variations and for different regions:

https://patents.google.com/patent/US10664140B2/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language
https://patents.google.com/patent/AU2015231761B2/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language
https://patents.google.com/patent/CA2942377C/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language
https://patents.google.com/patent/US9626084B2/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language
https://patents.google.com/patent/US20170177197A1/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language
https://patents.google.com/patent/WO2015142621A1/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language
https://patents.google.com/patent/EP3120228A1/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language
https://patents.google.com/patent/CA2942377A1/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language
https://patents.google.com/patent/EP3120228A4/en?inventor=Charles+Benjamin+Franklin+Waggoner&num=100&dups=language


I'm hardly a patent law expert, so I am sure others understand how that became eight publications better than I do.

It's not one of my most important ones, but I imagine the "Jeffery P. Bezos" as a co-inventor probably made a difference ;).

(and no, I have never met him or directly collaborated with him).

Wow where you busy

but i really often ask the question for what silly low complex things you can apply patents for

[A user can select an object represented in video content in order to set a magnification level with respect to that object. A portion of the video frames containing a representation of the object is selected to maintain a presentation size of the representation corresponding to the magnification level. The selection provides for a "smart zoom" feature enabling an object of interest, such as a face of an actor, to be used in selecting an appropriate portion of each frame to magnify, such that the magnification results in a portion of the frame being selected that includes the one or more objects of interest to the user. Pre-generated tracking data can be provided for some objects, which can enable a user to select an object and then have predetermined portion selections and magnifications applied that can provide for a smoother user experience than for dynamically-determined data.]

When you translate this into normal speech it seems to explain a click zoom track in realtime, every AI Model does this meanwhile.

[benwaggoner]

Wow where you busy
Eh, a little less than 10 a year granted. I've filed some that haven't been. I've got enough in flight that I hope to hit 100 sometime next year.

but i really often ask the question for what silly low complex things you can apply patents for

[A user can select an object represented in video content in order to set a magnification level with respect to that object. A portion of the video frames containing a representation of the object is selected to maintain a presentation size of the representation corresponding to the magnification level. The selection provides for a "smart zoom" feature enabling an object of interest, such as a face of an actor, to be used in selecting an appropriate portion of each frame to magnify, such that the magnification results in a portion of the frame being selected that includes the one or more objects of interest to the user. Pre-generated tracking data can be provided for some objects, which can enable a user to select an object and then have predetermined portion selections and magnifications applied that can provide for a smoother user experience than for dynamically-determined data.]

When you translate this into normal speech it seems to explain a click zoom track in realtime, every AI Model does this meanwhile.
IIRC (that was an early one) the meat is how to automate the zooming and scaling during playback without user input, and how to generate the metadata which makes that possible.

[hajj_3]

VP9 patents were updated within the last few days, the date listed on the pdf is messed up though, 1 extra page added: https://www.sisvel.com/xlin7ipl485u/6OckyYnH49V6byT7dW7YsF/23b9ed941e8e86908956f00e03a9f3c3/PatentList_VP9.pdf
AV1 patents were updated within the last few days, the date listed on the pdf is messed up though, 3 pages removed: https://www.sisvel.com/xlin7ipl485u/5VKBBH3LSEwAyT151R2j3E/79282044422fa21cfdd2d8f8ec61040f/PatentList_AV1.pdf

[oibaf]

VP9 patents were updated within the last few days, the date listed on the pdf is messed up though, 1 extra page added: https://www.sisvel.com/xlin7ipl485u/6OckyYnH49V6byT7dW7YsF/23b9ed941e8e86908956f00e03a9f3c3/PatentList_VP9.pdf
AV1 patents were updated within the last few days, the date listed on the pdf is messed up though, 3 pages removed: https://www.sisvel.com/xlin7ipl485u/5VKBBH3LSEwAyT151R2j3E/79282044422fa21cfdd2d8f8ec61040f/PatentList_AV1.pdf

Note that after some pages there are expired patents, so if you exclude them:
VP9 still has the same pages (29)
AV1 has just 1 page removed (67)

[hajj_3]

Dolby has now sued Snapchat in USA and brazil over AV1 and H.265 patents: https://ipfray.com/dolby-sues-snapchat-over-av1-and-hevc-patent-infringement-in-u-s-and-brazil-access-advance-vdp-license-would-resolve-issue/

[hajj_3]

4 pages have been added to AV1: https://www.sisvel.com/xlin7ipl485u/5VKBBH3LSEwAyT151R2j3E/13d414e7dc7f0896835a6df5273aaccc/PatentList_AV1.pdf
3 pages have been added to VP9: https://www.sisvel.com/xlin7ipl485u/6OckyYnH49V6byT7dW7YsF/888a656fe1d1a62223d95d1bddfa1d9b/PatentList_VP9.pdf

VP9 has 32 pages of unexpired patents
AV1 has 70 pages of unexpired patents

[kurkosdr]

Dolby has now sued Snapchat in USA and brazil over AV1 and H.265 patents: https://ipfray.com/dolby-sues-snapchat-over-av1-and-hevc-patent-infringement-in-u-s-and-brazil-access-advance-vdp-license-would-resolve-issue/
Finally! After years of various patent holders complaining that companies using AV1 are allegedly infringing on their patents (while doing nothing about it for some reason), some company is asserting its perceived patent rights against AV1 where it matters: in court (not in blog posts or YouTube videos like Sisvel is doing).

So, let's see how it goes.

I find it weird that they are going after Snap and not Google (the biggest user of AV1), but anyway, Snap is a reasonably big company, they can afford lawyers.

[rwill]

I don't know anything about this but I blame the unaffiliated Nokia for going after HEVC users, thus pushing the industry in the arms of AOM and endangering the legitimate HEVC patent pools their business.

[kurkosdr]

I don't know anything about this but I blame the unaffiliated Nokia for going after HEVC users, thus pushing the industry in the arms of AOM and endangering the legitimate HEVC patent pools their business.
VP9 and AV1 would happen anyway, since the various HEVC patent holders didn't agree to waive royalties for free-to-view video streaming (which made it unsuitable for the business model of services like YouTube and Twitch), and Google knew that would happen. VP9 was a thing long before the whole HEVC patent mess happened. H.264 is the exception, not the rule, MPEG-4 Visual also failed for free-to-view video streaming because patent holders also didn't waive royalties (and VP6 and VP7 in FLV files were used instead, with some WMV on some websites). And let's not forget that Google was threatening to remove H.264 decoding from Chrome entirely and go VP8-only until they got an indefinite waiver of royalties for free-to-view streaming from all H.264 patent holders. This is how important that waiver is.

The real problem caused by the HEVC patent mess is that even pay-to-view video streaming services decided to stay away from VVC (even on devices that support it) and either stayed on HEVC or went to AV1 plus HEVC (for old devices that don't support AV1), which translates to loss of royalties for patent holders. Another issue caused by the HEVC patent mess is that some PCs manufactured today ship with HEVC decoding disabled for royalty reasons, but with AV1 decoding enabled, which erodes the status of HEVC as the lowest common denominator for HDR and 4K content.

In other words, patent holders knew they would lose YouTube anyway (again, H.264 is the exception, not the rule), but they didn't expect to lose pay-to-view video streaming services to AV1 (which is what the patent mess of HEVC caused). Couldn't have happened to nicer people /s

[birdie]

Access Advance LLC announces two new members, Meta (https://www.businesswire.com/news/home/20260702726559/en/Access-Advance-Welcomes-Meta-Platforms-Inc.-and-Alibaba-Group-to-the-Video-Distribution-Patent-Pool) and Alibaba (https://www.afp.com/en/infos/access-advance-and-alibaba-announce-alibabas-expanded-participation-vdp-pool), as licensees of VP9, AV1, HEVC and VVC. Weird. Is it FUD? I don't know.

[Z2697]

FUD or not (for including VP9 and AV1 in the news), I think they are just there for the MPEG series.

[kurkosdr]

Access Advance LLC announces two new members, Meta (https://www.businesswire.com/news/home/20260702726559/en/Access-Advance-Welcomes-Meta-Platforms-Inc.-and-Alibaba-Group-to-the-Video-Distribution-Patent-Pool) and Alibaba (https://www.afp.com/en/infos/access-advance-and-alibaba-announce-alibabas-expanded-participation-vdp-pool), as licensees of VP9, AV1, HEVC and VVC. Weird. Is it FUD? I don't know.

Today I learned that Access Advance has a patent pool that charges "content fees" for organizations streaming VP9 and AV1 video:
https://accessadvance.com/licensing-programs/vdp-pool/
Our innovative pool license covers standard essential patents (SEPs) for all four major video codecs currently used by video distribution providers: HEVC (H.265), VVC (H.266), VP9, and AV1.
Royalty rates are determined by the size of the licensee’s streaming business using three criteria to ensure fair treatment across different business models: Average monthly active users, average monthly video subscribers, and semi-annual video streaming revenue.

And yet, none of the companies (https://accessadvance.com/vdp-pool-licensors/) whose patents are included in the pool will go after the biggest distributor of VP9 and AV1 video: Google (Alphabet).

So, those companies are claiming that Google has built its Youtube video streaming service on top of their private intellectual property (and is making a crapload of money in the process), but won't go after Google legally. And that, despite VP9 being 13 years old already, which means they had plenty of time to do so. This is why I am posting ranty posts about patents: This is a clown show, not how multinational corporations are supposed to operate if they had valid claims.

[hajj_3]

dolby suing another company over AV1 patents: https://michael7924.substack.com/p/dolby-launches-first-upc-av1-lawsuit

[kurkosdr]

dolby suing another company over AV1 patents: https://michael7924.substack.com/p/dolby-launches-first-upc-av1-lawsuit
And to my non-surprise, it's some second-tier hardware vendor... not Google, the company that has built a video streaming empire on what Dolby claims is their intellectual property and allegedly owes Dolby a lot of money in past-infringement compensation (remember, Dolby didn't participate in the creation of the AV1 standard, they have no FRAND obligations to AV1 implementers).

And yet, Dolby isn't chasing that supposed infringement and the substantial money they are supposedly owed. What a clown show.

[CruNcher]

Sisvel Main Investors are Italian Mafia Families with a lot of Influence the Next Generation of them after they mainly disappeared for decades in silence
Some of them where also involved in the Development and financing of MPEG and distributed also through investments in Media and Television

You really have to ask yourself what is going on here currently, it feels like a War has started of very old structures that where mainly sleeping.

FEAR rescue our Investments that can be rescued.

Only Logic Explanation MPEG is about to collapse

[kurkosdr]

Sisvel Main Investors are Italian Mafia Families with a lot of Influence the Next Generation of them after they mainly disappeared for decades in silence
Some of them where also involved in the Development and financing of MPEG and distributed also through investments in Media and Television

You really have to ask yourself what is going on here currently, it feels like a War has started of very old structures that where mainly sleeping.

FEAR rescue our Investments that can be rescued.

Only Logic Explanation MPEG is about to collapse
Most of the companies listed in the patent pool are not even Italian. There is no reason to resort to conspiracy theories here, this is the same FUD we saw during the SCO vs Linux drama: "Mr Google, I claim that you violate some patents of mine, but I am not going to take you to court, I will instead sue some second-tier user of the technology to try and extract a settlement from them and try to scare you into submission".

This is why I am so passionate about this: It's a misuse of the patent system, misusing a system designed to protect inventors to intimidate and harass competition.

If the companies listed in the Sisvel pool (or this new "video distribution" Access Advance pool) had taken Google to court even within the first 10 years of VP9's existence, I would at least give those companies the benefit of the doubt.

[CruNcher]

Yes its Mafias Methods you can never leave your old genetics fully behind you can only repackage it and give it a nicer name and see if society accepts it.

Access Advance LLC announces two new members, Meta (https://www.businesswire.com/news/home/20260702726559/en/Access-Advance-Welcomes-Meta-Platforms-Inc.-and-Alibaba-Group-to-the-Video-Distribution-Patent-Pool) and Alibaba (https://www.afp.com/en/infos/access-advance-and-alibaba-announce-alibabas-expanded-participation-vdp-pool), as licensees of VP9, AV1, HEVC and VVC. Weird. Is it FUD? I don't know.

Alibaba really ?
what for a patent do they defend ?
Meta together with MediaTek was clear but Alibaba ?
Ok they are hyper active on AI Video Codecing (Diffusion Latent Space Research) but general Video Codec and ground Research work for it ?
Where they involved maybe in one of the Lower Complex Chinese Codecs and derive a patent violation out of that ?
Seeing all these Cloud Companies that came to the Game way later and now saying they did base fundamental ground work is weird.

Google ok different story they where the first realizing we need the Research capabilities and bought On2 Darpa was very clear with that future goal owning more Research capabilities.
And Darpa let also some Ground Work disappear (people thought they where snake oil and business unusable because they didn't understood the fundamental changes for the future, that is the challenge understanding someones fundamental ground work and predicting its outcome correctly, Darpa are the best at it conducting this evaluation) we saw coming back into Google.

[Z2697]

Well you gotta see all the chinese encoders winning the MSU comparison...
This is not good, whichever contry it is, doesn't really matter, it just means there's more closed source and even not available anywhere encoder that's flooding the once trusted contest (so no one cares about it now).

[kurkosdr]

Well you gotta see all the chinese encoders winning the MSU comparison...
This is not good, whichever contry it is, doesn't really matter, it just means there's more closed source and even not available anywhere encoder that's flooding the once trusted contest (so no one cares about it now).
I haven't been following along, are those Chinese closed-source encoders available for general use so they can be tested on a wide variety of content?

If not, it could as well be a piece of software that spits out a pre-encoded clip (of the test samples used). But if they are legit, that's a major challenge for the incumbent encoders.

Also, I think you are in the wrong thread.

[CruNcher]

Ehh surely the Chinese do not need such tricks lol Strongene was very impressive and their Cloud Services have not so low quality standards at all and yeah i know that Tencent is very active in Video Encoding and they also working heavily with Bytedance on Seedance and Seedream
And they overall deliver a solid foundation in many spaces when it comes to computer vision they are top notch i would say they overrun the Russian by now and Russia most probably lost a lot of its IT future on the Battlefield that China is catching up now heavily.

MSU results in honor but trusting them has become complicated.
And this has become a Game of Cloud Marketing.

[kurkosdr]

Yes its Mafias Methods you can never leave your old genetics fully behind you can only repackage it and give it a nicer name and see if society accepts it.
Oh ffs, Mafia's methods involve organized violence and lawbreaking, this is the exact opposite: Using the law (or more accurately, the threat of legal action) to harass competitors. This is why some of us like what Google is doing here: Google is not getting intimidated by this foul play.

Again, if those companies named in the pools are reasonably confident that Google has built the world's biggest streaming service on their private intellectual property, they are free to use the courts to sue Google for patent infringement. They don't even get to be penalized if they lose. But for some reason they don't.

[CruNcher]

Of course the Darpa is not interested what Mafias think and when you attack one of their structures out of foreign space you better be prepared even if it's just a Public structure
it isn't anymore the Department of Defense but the Department of WAR

Also about "THE LAW" you should realize it is heavily under attack as we know it and Maat is raging and she won't watch this for long and sooner or later she will let the feather fall.
And than Grace with those who think they can easily do this.

[hajj_3]

3 pages have been removed from AV1: https://www.sisvel.com/xlin7ipl485u/5VKBBH3LSEwAyT151R2j3E/67e8f262a9decea41b92c32f7c42afde/PatentList_AV1.pdf
1 page has been added from VP9: https://www.sisvel.com/xlin7ipl485u/6OckyYnH49V6byT7dW7YsF/888a656fe1d1a62223d95d1bddfa1d9b/PatentList_VP9.pdf

VP9 has 32 pages of unexpired patents
AV1 has 67 pages of unexpired patents

[oibaf]

Access Advance has a patent pool that charges "content fees" for organizations streaming VP9 and AV1 video:
https://accessadvance.com/licensing-programs/vdp-pool/


https://www.linkedin.com/pulse/streaming-media-connect-session-interdigital-vs-disney-jan-ozer-xa3ge

Konstantinos Poulinakis recently reported that, based on his analysis of the Access Advance Video Distribution Patent Pool, patents covering AV1 and VP9 account for just 3.2% and 1.3% of the pool, respectively. Yet the pool charges the same royalty regardless of which covered codec is used.