When a Butterfly Flaps its Wings in Cupertino, VVC’s Success May Be Assured

Given that VVC is top of mind right now, I just wanted to report that IAM has announced that it appears that Apple has purchased 14 VVC-related patents from a Korean inventor. IAM is connecting a lot of dots to (I think) make this claim, which goes something like this.

  • A Korean inventor set up a company that performs video-related research.
  • This company was a charter member of the VVC Advance pool from Access Advance.
  • This company has previously sold VVC-related patents to another company.
  • “The assets transferred to Apple do appear to be video-related, with most of the titles of the rights describing a method for encoding and decoding a video or image signal.”

I’m being vague because the article is subscription only and I don’t want to steal IAM’s thunder.

I asked a colleague knowledgeable in standards-based IP if it was possible to verify whether the patents Apple acquired were VVC-related. Here’s the response.

The assignment data is public, so you can independently corroborate this. Here’s one assignment to Apple.  Note that the execution date of the assignment is 12/1, a month before XRIS joined Access Advance’s VVC pool.  This is one of the patents Apple acquired.  Note the priority date here:  1/2/19 – about 9 months after JVET (the MPEG subcommittee that set VVC) announced the 13 core experiments for VVC, which directed development on VVC from 4/18 through its conclusion.  I’ve attached the JVET meeting minutes for the 4/18 meeting, which, again, set out the areas of innovation the SSO would focus on over the next 2 years.  Note, on page 133, that Bae-Keun Lee (then of KT) attended.  He is the inventor of the patents and apps Apple acquired.

So, to put all this together, Apple acquired assets from XRIS, at least some of which (I haven’t looked at them all) were filed right in the middle of VVC standardization by someone who participated in VVC standardization and which relate to video coding.  I think they’re likely to be VVC-essential patents.  Or at least, I think Apple thinks they are.

The same colleague opined that Apple was going all-in on VVC to support its planned VR/AR headset, which reportedly will have 12 cameras, necessitating some pretty intense video compression technology. While it is possible that Apple might develop chips for their own codec, it seems more likely that Apple would use a standards-based codec instead.

Apple has long been associated with VVC (see here) and already owns some VVC-related patents (see here), though the company doesn’t appear to have joined either the Access Advance or MPEG LA pool. Still, it’s one thing to monetize internal R&D and quite another to invest in third-party patents, though Apple has certainly done that in the past.

For perspective, we all remember the hubbub after Apple added HEVC to its product line (see, for example, here, here, and here). While this didn’t trigger the instant use of HEVC that many predicted, clearly if Apple had decided to support AV1 instead, the video codec landscape would look quite different today.

Let me be clear; the IAM article merely reports the Apple purchase and connects the dots as described, as did my colleague. Neither source stated that these purchases mean that Apple plans to support VVC in its full product line. But if the patents are VVC-related, and Apple does fully support VVC, it could be as seismic as Apple supporting HEVC.

About Jan Ozer

Avatar photo
I help companies train new technical hires in streaming media-related positions; I also help companies optimize their codec selections and encoding stacks and evaluate new encoders and codecs. I am a contributing editor to Streaming Media Magazine, writing about codecs and encoding tools. I have written multiple authoritative books on video encoding, including Video Encoding by the Numbers: Eliminate the Guesswork from your Streaming Video (https://amzn.to/3kV6R1j) and Learn to Produce Video with FFmpeg: In Thirty Minutes or Less (https://amzn.to/3ZJih7e). I have multiple courses relating to streaming media production, all available at https://bit.ly/slc_courses. I currently work as www.netint.com as a Senior Director in Marketing.

Check Also

Replace Bitrate Viewer with FFBitrateViewer

Recently I was asked to visually illustrate the data rate difference between two HEVC files, …

B-Frames, Ultra Low-Latency Encoding, and Parking Lot Rules

One of my sweetest memories of bringing up our two daughters was weekly trips to …

Figure 2. Cost per hour to produce a single 1080p stream using the x264 codec and FFmpeg. Graviton is clearly the most cost effective.

Which is the Best AWS CPU for FFmpeg?

If you encode with FFmpeg on AWS, you probably know that you have three CPU …

Leave a Reply

Your email address will not be published. Required fields are marked *