Alphabet's Google violated a software developer's patent rights with its remote-streaming technology and must pay $338.7 million in damages, a federal jury in Waco, Texas decided on Friday.
It details a process of synchronising videos between multiple devices and a content server, as well as a few different variations of the idea - it doesn’t just cover what Chromecast does.
The telling point here is that Google didn’t even try to argue that they didn’t use this method. Instead, they tried to argue that the patent was invalid. Apparently, they did not manage to invalidate the patent.
After looking at the patent it’s clear it’s way too vague, generic and obvious. It should never have been granted. (I Am Not A patent Lawyer). For one the XMBC web interface from 2009ish is prior art.
Technically the Kodi remote control app would be in violation of the patent, except it doesn’t use any “back end server system”.
If you replace the words “display” and “video” with “speaker” and “audio” then the Spotify app would be in violation as well, as it allows changing the playback device to any of your logged in devices.
Come to think of it, if you use Firefox on mobile to access YouTube, then “send tab to other device”, and send it to a desktop computer connected to a big screen, it could be interpreted as violating the patent as it’s using Mozilla’s “back end server” to relay the message
XMBC web interface just streams to a different client. Here, we have a client requesting to stream to another client, and synchronised by the server. The key part is the synchronisation between multiple clients.
The patent also deals with a few other types of concurrent streams for other applications, beyond what Chromecast does.
Come to think of it, if you use Firefox on mobile to access YouTube, then “send tab to other device”, and send it to a desktop computer connected to a big screen, it could be interpreted as violating the patent as it’s using Mozilla’s “back end server” to relay the message
That may well also violate the patent. It would likely depend on whether the devices are synchronised, or if the desktop is just getting a link and streaming separately.
Just because lots of people use it without paying doesn’t make a patent invalid. You only have to look at what happened with the patent for WiFi.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
The full patent goes into detail (pdf): https://image-ppubs.uspto.gov/dirsearch-public/print/downloadPdf/8356251
It details a process of synchronising videos between multiple devices and a content server, as well as a few different variations of the idea - it doesn’t just cover what Chromecast does.
The telling point here is that Google didn’t even try to argue that they didn’t use this method. Instead, they tried to argue that the patent was invalid. Apparently, they did not manage to invalidate the patent.
After looking at the patent it’s clear it’s way too vague, generic and obvious. It should never have been granted. (I Am Not A patent Lawyer). For one the XMBC web interface from 2009ish is prior art.
Technically the Kodi remote control app would be in violation of the patent, except it doesn’t use any “back end server system”.
If you replace the words “display” and “video” with “speaker” and “audio” then the Spotify app would be in violation as well, as it allows changing the playback device to any of your logged in devices.
Come to think of it, if you use Firefox on mobile to access YouTube, then “send tab to other device”, and send it to a desktop computer connected to a big screen, it could be interpreted as violating the patent as it’s using Mozilla’s “back end server” to relay the message
XMBC web interface just streams to a different client. Here, we have a client requesting to stream to another client, and synchronised by the server. The key part is the synchronisation between multiple clients.
The patent also deals with a few other types of concurrent streams for other applications, beyond what Chromecast does.
That may well also violate the patent. It would likely depend on whether the devices are synchronised, or if the desktop is just getting a link and streaming separately.
Just because lots of people use it without paying doesn’t make a patent invalid. You only have to look at what happened with the patent for WiFi.