Showing posts with label Tizen. Show all posts
Showing posts with label Tizen. Show all posts

Monday, January 27, 2014

Samsung's patent deal with Google suggests concern about ability to settle with Apple soon

Late on Sunday, Samsung and Google announced a ten-year global patent license agreement. As the announcement notes, they already have a "long-term cooperative partnership" in place, so there was no immediate threat of litigation between them anyway.

The press release quotes IP executives from both companies who suggest that this agreement should serve as a model for the wider industry, as an alternative to patent litigation. Those quotes show that the intention here is primarily to make those look bad who enforce their patents. Samsung is embroiled in disputes with Apple and Ericsson, and Google's Motorola Mobility with Apple and Microsoft. But Apple also struck a ten-year license deal with HTC in late 2012, one of 23 announced or publicly-discoverable royalty-bearing Android patent license agreements (most of which relate to Microsoft's patents). Recently Samsung and Nokia announced an extension of a license deal as well, and it may also cover Android but the scope was not specified. In other words, the fact that Google and Samsung enter into a long-term cross-license agreement does not make them IP innovators or thought leaders.

Samsung and Google own a lot of patents, but they haven't been able to gain much leverage from those patents against Apple, Microsoft and others. They have, however, lost a number of lawsuits, and just last week a U.S. judge found Samsung to fringe yet another Apple patent and invalidated one of Samsung's patents-in-suit, ahead of a trial scheduled to start on March 31. One way to sum up the announcement would be this: "If you can't beat 'em, just try to make 'em look bad".

It's not just about making the enforcers look bad but also about giving the impression of being willing licensees. Prior to this announcement, the last Google patent license agreement with another major industry player that was announced was a deal with Yahoo that cleared the path for Google's IPO about a decade ago.

There could also be antitrust considerations. Both companies face antitrust investigations because of their assertions of standard-essential patents. They both rely largely on the same law firm in that context and make similar royalty demands (Samsung is known to demand 2.4% of Apple's sales, while Motorola Mobility wants 2.25%). Through this cross-license deal among friends they may hope to somehow validate their supra-FRAND demands in the eyes of regulators, but I believe competition enforcers won't be overly impressed.

I've been somewhat skeptical of the prospects of a near-term Apple-Samsung settlement for some time (see my comments to the Korea Times). I'm now even more skeptical because I believe Samsung would rather announce the really big news of a deal with Apple than engage in a PR ploy with a close ally.

As long as Samsung primarily makes Android-based devices, it doesn't need a deal with Google, or vice versa, to avoid litigation between the two. If Samsung switched to an alternative platform like Tizen, then the agreement might make a difference, but since the scope was not announced, it's possible that Google reserved the right to sue Samsung over non-Android devices.

If you'd like to be updated on the smartphone patent disputes and other intellectual property matters I cover, please subscribe to my RSS feed (in the right-hand column) and/or follow me on Twitter @FOSSpatents and Google+.

Share with other professionals via LinkedIn:


Thursday, January 3, 2013

Based on Google's stance on API copyrightability, Samsung could make Android apps run on Tizen

Samsung today confirmed its plan to release during the course of 2013 multiple mobile phones running the Tizen platform, which is supported by companies including Intel, Vodafone and NTT DoCoMo, and Linux-based like Android. A Bloomberg report on this announcement says "Samsung looks to reduce its reliance on Google (GOOG) Inc.'s Android operating system after the Internet search company acquired handset maker Motorola Mobility Holdings Inc. for $12.5 billion in May".

Samsung is rightly concerned about what Google will ultimately do with Motorola Mobility. Google's plan to use MMI's patents to bring about global patent peace has not worked out at all. And there comes a point at which Android will be perceived by many consumers as a Samsung platform -- because of the ubiquity of the Korean electronics giant's gadgets. Also, more and more end users become accustomed to Samsung's proprietary extensions on top of Android, named Touchwiz.

At some point Samsung may determine that Tizen meets its strategic needs better than Android does. For example, Samsung may want more freedom to partner with other providers of online services and/or to increasingly promote its own offerings. This would lead to a potentially irreconcilable conflict between the two companies.

In this scenario Google might hope that Samsung is going to remain focused on Android (and play by Google's rules) because of the huge number of existing apps. Even Samsung's strategy of hedging its bets with Tizen is not going to make the whole app developer community flock to that platform. But with both Android and Tizen being based on Linux, wouldn't it make a lot of sense to create an interface that enables most (or, at some point, all) existing Android apps to run on Tizen? Sort of an emulator? In that case, Samsung's customers could switch from Android to Tizen in a fairly smooth transition. Samsung would have to leave the Open Handset Alliance (OHA) for fragmentation of Android, but that wouldn't really matter at that point.

Over time, the Tizen engine for Android apps could even have unique functionality that would render apps optimized for Tizen incompatible with Android.

Granted, this is speculative. But this has happened before. When Google launched Android, it understood that it needed a large and diverse choice of apps, and in order to attract app developers, it provided them with a programming environment derived from Java. And it did this without a license from Sun Microsystems, which became a wholly-owned Oracle subsidiary three years ago. At the same time, it also hijacked Linux, using large amounts of Linux API material.

When Oracle decided to take legal action against this allegedly "lawless conduct", Google defended itself primarily with the argument that any material it appropriated was not protected under copyright law. Google didn't deny that it used Java API material: it merely disputed that there was anything unlawful about it.

Judge William Alsup in the Northern District of California sided with Google on this one. Oracle appealed his ruling to the United States Court of Appeals for the Federal Circuit. The appeal focuses exclusively on the copyright part of the case (which originally also involved seven patents).

As the saying goes, "live by the sword, die by the sword". Google would have to contradict its own positions on API copyrightability if Samsung decided to do to Android what Google did (and continues to be doing) to Java.

If Oracle's appeal succeeds and some or all of the appropriated API material is declared copyrightable, Google will have to work out a deal with Oracle. But in that event it will also be in a position to make it much harder for Samsung to supplant Android with Tizen.

If you'd like to be updated on the smartphone patent disputes and other intellectual property matters I cover, please subscribe to my RSS feed (in the right-hand column) and/or follow me on Twitter @FOSSpatents and Google+.

Share with other professionals via LinkedIn: