Print 32 comment(s) - last by nocturne_81.. on Sep 29 at 9:02 AM

Meeting of the Larrys: Larry Page and Larry Ellison, CEOs of Google and Oracle met, but were unable to work out a mutually acceptable Java licensing arrangement for Oracle.  (Source: Business Insider/The New York Post)

Google could remove Java from the Android project, leaving an interface that partners who license J2ME could plug the technology into. That would be okay for Samsung, Motorola, LG Electronics, and Sony who are all J2ME licensees, but it could hurt HTC, the second largest Android manufacturer.  (Source: Linux Tux)
Settlement talks reach impasse; Oracle demands double-dip licensing fees on the OS and handset levels

Bloomberg reports that another round of talks between software giants Google Inc. (GOOG) and Oracle Corp. (ORCL) ended at an impasse.  Oracle Corp. is currently suing Google for using pieces of its patented Java2ME (J2ME) code in Android via the Apache Project's Java Standard Edition "Harmony" (J2SE).  

Google CEO Larry Page sat with Oracle CEO Larry Ellison for 10 hours trying to work out an acceptable licensing agreement.  The talks ended with no deal reached, with both parties agreeing to talk to court officials about "when further discussions will take place and whether the further attendance of Mr. Ellison and Mr. Page will be required."

I. Oracle's Plan For Double-Dip License Fees

The case represents a substantial risk for both firms.

Working in Oracle's favor is the fact that the judge has suggested that Google's infringement of the Java technology 
was "brazen".  But Google has some advantages of its own.  It dug up documents from the former CEO of Sun Microsystems -- the company Oracle acquired the Java intellectual property from in 2010 -- praising Google's use of Java in Android, and casting doubt on whether Sun was opposed to the unpaid use.  

Furthermore, Google succeeded in convincing the judge to toss out the $6.1B USD that Oracle wanted -- a figure which included speculative future damages.  Oracle has since revised its estimate downwards to $2.3B USD, a figure that still includes a $1.2B USD speculative damages total for 2012, which Google contends is unfair.

If the pair can't settle up, the case will likely go to trial.  If that happens Oracle will be seeking one thing -- a permanent injunction banning U.S. Android sales.  Unlike Apple, Inc. (
AAPL) who is seeking a similar injunction in hopes of permanently preventing U.S. Android sales, Oracle's "permanent" injunction bid would be in hopes of forcing Google into a lucrative licensing deal.  Oracle could ask for a royalty as high as $15-20 per device license, on top of the identical fee it already charges Android handset makers like Samsung Electronics Comp., Ltd.'s (SEO 005930).

This is an important aspect to understand of why Oracle's campaign is more harmful to Android, than Microsoft's licensing efforts -- Oracle is double-dipping, seeking fees both at the OS and handset levels, where as Microsoft is content to stick with handset licensing.

Google offers Android licenses to handset manufacturers for free, though it does earn a certain amount of revenue via its cut of app sales and Android-targeted licensing.  The question becomes how much of that revenue can Oracle take before Android starts to become a losing proposition for Google.

If Google is unable to beat Oracle in court, it will surely regret rejecting Sun's 2006 offer to license Java2ME to Android for $100M USD.

II. Google Could Remove Java from Android

One possible way Google could shirk the licensing fees, though, is to remove all the J2SE/J2ME code, leaving a naked interface for partners to implement their own build of J2ME.  As most Android partners -- such as Samsung and Google subsidiary Motorola Mobility – are J2ME licensees, Oracle likely couldn't do anything about this scheme.  The one major player who would be hurt by such an arrangement would be HTC Corp. (SEO:066570).  The Taiwanese manufacturer, believed to be the second largest Android handset maker, does not license J2ME.  Thus it would likely be summarily sued by Oracle, should it try to plug in the technology.

If Google adopts such a strategy (and there's no clear reason why it wouldn't other than to protect HTC), it would still have to pay the damages for past infringement, but it would be spared from the ongoing double-dip licensing scheme.  That would mean a big loss for Oracle, as the license fees comprise the majority of the money Oracle hopes to pocket in future years as a result of the case.

One thing to recall is that Google is sitting on a $39B USD cash surplus [source], so it can afford to stomach some damages.  But licensing fees?  Those it should be far more concerned about, as they affect its ongoing bottom line.

Comments     Threshold

This article is over a month old, voting and posting comments is disabled

code conversion?
By Darksurf on 9/23/2011 1:07:30 PM , Rating: 2
I haven't really looked too much into the new version of C++ (C++0x), but I wonder it has grown enough to compare with java and even have easy conversion over. Considering java and C++ are similar (or cousins as I like to call them due to their similarities, yet differences), if C++0x has acquired the ease-ability of java, wouldn't that make migration less painful and actually have benefit of the speed C? I'm not sure on what we would do with apps tho, but at least the main android OS would be covered.

RE: code conversion?
By 2PM on 9/23/2011 2:00:41 PM , Rating: 2
speed doesn't come with the syntax. the C/C++ code is usually compiled to the machine native binary, which is (sometimes) faster than the code that's compiled to run in a runtime environment, such as JVM or Dalvik. C++ on a mobile platforms doesn't make much sense, because that code won't work on all different devices.

RE: code conversion?
By dcollins on 9/23/2011 2:08:38 PM , Rating: 2
No, this wouldn't work at all. Java runs in a Virtual Machine, C++ is compiled directly to machine code. Google would have to rethink its entire security model which is based about sandboxing code within the java virtual machine, not to mention ALL existing Android program would need to be rewritten. Not feasible at all.

Jason, your idea of removing the offending header files from Android is ludicrous. How would Google develop and test the OS internally? It would mean Google would not be able to ship a working operating system to handset makers. Hey, here's 95% of an operating system, you provide the remaining 5%! I don't think that would go over very well considering handset makers are already having difficulty integrating upstream changes into their existing android distributions.

“Then they pop up and say ‘Hello, surprise! Give us your money or we will shut you down!' Screw them. Seriously, screw them. You can quote me on that.” -- Newegg Chief Legal Officer Lee Cheng referencing patent trolls

Copyright 2016 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki