Showing posts with label Open Standards. Show all posts
Showing posts with label Open Standards. Show all posts

Friday, September 17, 2021

OpenRAN is certain to increase standard-essential patent licensing costs: more SEPs, more SEP holders, more implementers, more injunctions

The stated goal of the O-RAN Alliance (O-RAN = OpenRAN = Open Radio Access Network) is to "enable a more competitive and vibrant RAN supplier ecosystem with faster innovation" by virtue of modularizing mobile network infrastructure through standardized interfaces. If OpenRAN (or "O-RAN") is clearly superior over the current architecture, it's striking that even the most optimistic projections come down to approximately 10% of the global RAN market by 2025.

There are hurdles to be taken and concerns to be addressed. In this post I can't talk about them all. To give just one example of a serious technical question, it is debatable whether a mobile network that runs partially on the cloud ("vRAN" or "virtual RAN") could ever match the reliability and performance of traditional equipment, and whether the optimized use of resources that cloud-based solutions potentially offer outweigh security and other risks. I may very well discuss some of those architectual and practical issues on other occasions.

Today I'm going to focus on what is--for this blog--the obvious starting point of the analysis: standard-essential patent (SEP) licensing and litigation. From that angle, O-RAN has zero upside--literally zero--but comes with a significant downside:

1. Not a single cent will be saved in 5G license fees

O-RAN relates to the infrastructure side. Communication between the network infrastructure and end user devices (such as handsets and connected cars) still relies on the same standards--presently, that means 5G first and foremost.

O-RAN doesn't make 5G cheaper. It has no impact on handsets, and the only way that carriers would pay lower 5G royalties would be if O-RAN delayed the rollout of 5G, which no one wants to happen.

2. Additional patents--partly from additional patentees--will have to be licensed, and they will not be free

Not only will there be more patents to be licensed but definitely more patents and--very likely--more holders of relevant patents.

On top of the standards that those mobile networks already have to implement, their infrastructure will have to implement the O-RAN interfaces. While the "Open" part of the standard's name does stand for a connection with open-source software, participants in the standard-setting process (such as ETSI members) will be entitled to FRAND royalties (and not FRAND-0, to be clear). Some relevant patents may end up belonging to companies that are not bound by a FRAND pledge. I don't even want to get into a doomsday scenario of different major markets in the world potentially going in different directions, which may result in a huge number of patents that are essential to a standard in one region but belong to patent holders who did not participate in the relevant standard-development process.

3. More implementers will have to take licenses

At the moment, the number of relevant implementers in the mobile infrastructure market is small: a few base station makers, and their suppliers, such as chipmakers. That number will go up with O-RAN, as the whole idea is to bring in more players (most of them U.S. based, as this is primarily an initiative by the U.S. government and U.S. carriers, with Apple apparently looking at O-RAN as an opportunity for infrastructure-side services that lock customers even more into the iOS ecosystem).

The more licensees there are, the more costly the licensing process becomes, which in the end increases costs.

4. Virtualization and modularization exacerbate the forum-shopping problem

Should parts of the functionality be moved to the cloud, the holders of certain types of patents may be able to choose between enforcing them where the servers are hosted or in the jurisdiction in which those cloud services are used by a carrier.

Even without virtualization, some forum-opportunities will likely result from the fact that different components are made in different jurisdictions, and that some patents may be infringed directly only by the carrier, but particular component makers may be liable for contributory infringement.

5. The availability of drop-in replacements weighs in favor of granting patent injunctions

Just like "plug & play" (relating to personal computer hardware) was derided as "plug & pray," it's doubtful that carriers will be comfortable replacing a patent-infringing O-RAN component with a rival offering. In some cases, carriers will have had reasons for choosing one particular component over the other options.

But patentees who prevail in infringement litigation will be able to leverage the O-RAN marketing promise against defendants. They'll argue that an injunction does not cause irreparable harm (and won't impact third parties) as a component held to infringe the patent(s)-in-suit could be replaced with another.

6. Today's leading infrastructure makers may step up patent monetization

Should O-RAN adversely impact mobile infrastructure sales by today's market leaders, they may further step up their patent enforcement.

I'm not saying that one should oppose O-RAN just over the foreseeable patent licensing and enforcement issues outlined herein. Patent licensing is sometimes just a cost of doing business. But when weighing off the pros and cons, the licensing and litigation aspects are undoubtedly in the "con" column.

Share with other professionals via LinkedIn:

Thursday, May 30, 2013

Software Freedom Law Center effectively blesses Microsoft's Android and Linux patent license deals

After many years of fundamentalist opposition to patent licensing it appears that Free Software advocates have become more pragmatic and now, at long last, tend to appreciate the benefits of patent license agreements and recognize what they usually denied in "open standards" policy debates around the world: that FRAND licensing terms for patents that read on Free and Open Source Software (FOSS) can actually contribute to the freedom of software distributors and users.

The Software Freedom Law Center (SFLC) is run by Professor Eben Moglen, Richard Stallman's co-author of the GPLv3, the most anti-patent FOSS license. SFLC provides legal advice and defines its mission as "helping [FOSS] projects reach their long-term goals safely and efficiently so hackers can concentrate on making great software". In a response to Open Source Initiative (OSI) chief Simon Phipps's criticism that Google's proposed VP8 patent license is overly restrictive by FOSS standards, SFLC's Senior Staff Counsel Aaron Williamson writes:

"Because the patent license does not restrict those freedoms, but rather affords some new, limited protections to users and developers within the field of use, it improves on the current situation. Without this license, the patent holders would be in a position to threaten those users and developers as well as others. [...] [U]ntil software patents no longer threaten FOSS, we will look for every opportunity to preserve community development from their destructive effects. The VP8 cross-license provides such an opportunity, in an area of particularly active patenting."

This is, in fact, a ringing endorsement of Microsoft's patent license agreements with Android and Linux device makers (note that Android includes Linux, which is distributed under the Free Software Foundation's GPL license). Last month ZTE became the 20th Android device maker known to have taken a royalty-bearing Android patent license from Microsoft, and Microsoft previously announced license deals involving non-Android variants of Linux (examples: Amazon, Brother, Casio, Kyocera, LG, Samsung).

The logic of the SFLC's defense of Google's proposed VP8 patent license agreement as being "compatible with FOSS licensing" also applies perfectly to Microsoft's Android and Linux patent license deals:

  • Just like the proposed VP8 patent license is a separate license from the software copyright license, Microsoft's Android and Linux patent license agreements are separate from the copyright licenses governing the open source distribution of Android/Linux.

  • Just like the licensees under Google's proposed VP8 license, Microsoft's licensees are "not [...] required to pass on any restrictions limiting users' rights to copy, modify, and redistribute free programs" (if Samsung et al. imposed any such restrictions, we would know). Instead, users "have the same rights as they would if the [device makers] had never accepted the patent license".

  • Just like video codecs are "an area of particularly active patenting", so are smartphones (which according to patent aggregator RPX potentially infringe a quarter million patents). In fact, smartphones are an area of far more active patenting because they include video codecs but also numerous other technologies in fields of active patenting.

  • Just like the proposed VP8 license, Microsoft's Android and Linux patent license agreements "do[] not restrict [FOSS] freedoms, but rather afford[] some new, limited protections to users and developers within the field of use", which in the SFLC's opinion "improves on the current situation".

Of course, the terms of Microsoft's agreements with Android/Linux device makers aren't known -- nor are the terms of Google's agreement with 11 MPEG LA patent licensors. All that we can see from the outside is what the respective licensees do or don't do. Do they impose restrictions? No. Do end users have to pay separately? No, someone takes care of this for them. Does this mean third parties can do anything they want without possibly needing a new license from the relevant patent holders? No. Nor are they free to "do anything" under the VP8 patent license agreement.

With a vocal part of the Free Software ecosystem agreeing that patent licenses are preferable over litigation, and confirming that patent licenses wich don't result in a modification of software copyright licenses actually "afford[] some new, limited protections to users and developers within the field of use", licensing is more popular than ever. Once Google's Motorola Mobility also takes such a patent license, it will be difficult to come up with anyone else who could lend a meaningful endorsement to this commercial practice (which is also accepted in all other fields of technology).

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:


Saturday, May 18, 2013

Google's FRAND-zero patent license for VP8 threatens to divide Web and FOSS communities

Google is already promoting the VP9 video codec, which may very well raise new patent issues, while pushing for adoption of VP8 as an Internet standard. But the patent license it has drafted for VP8 and just published doesn't meet the requirements of the Open Source Initiative's definition of open source, says the President of the OSI's Board of Directors, Simon Phipps, in a blog post. According to Mr. Phipps, the draft license "shows signs of unfamiliarity with the tenets of software freedom". The OSI can't speak for the Free Software Foundation, of course, but the two organizations share many values and the FSF's emphasis of software freedom ("[t]he issue is not about price") entails even stricter requirements for acceptable license terms. Simply put, if your proposal doesn't please Simon Phipps, know that Richard Stallman ("RMS") is harder to please.

Historically, the World Wide Web Consortium (W3C) has applied its royalty-free (RF) licensing requirements in ways that ensured compatibility of HTML-related essential patent licenses with the philosophies of Free and Open Source Software (FOSS) organizations, particularly the FSF and the OSI. The Web movement and the FOSS movement have succeeded symbiotically and in tandem: FOSS powers large parts of the Web and drove its adoption, while the Web has allowed FOSS to thrive and contributed greatly to its popularity. If Google wants the W3C to consider its proposed VP8 patent license an acceptable W3C RF license, it effectively asks the W3C to part ways with the FSF and the OSI, after approximately two decades of close and fruitful collaboration. This is utterly divisive.

Shortly after the announcement of an MPEG LA-Google license deal relating to VP8 I was confused about Google's intentions to comply with the W3C patent policy when I saw a Google employee link to a web page that involved FRAND licensing commitments when he said they were planning to comply with the W3C's patent policy. Now that Google's proposal has been published, the answer is that Google's proposed VP8 patent license is not a permissive RF license but a typical FRAND-zero (or, synonymously, "RAND-zero") license. Zero license fees to be paid by licensees (though Google presumably paid or pays MPEG LA) -- but reasonable and non-discriminatory terms (field-of-use restrictions, reciprocity) are imposed and, which Mr. Phipps considers the most significant issue with the proposal, "gaining benefit from the agreement requires individual execution of the license agreement".

The final two sentences of the OSI President's blog post declares Google the loser and VP8's rivals the winning camp:

"This document seems to me to be an effective outcome for those in MPEG-LA's patent-holder community who want to see VP8 disrupted. It has provoked an autoimmune response that must have Google's enemies smiling wickedly."

I don't want to speculate about the intentions of the 11 originally-unnamed, meanwhile-disclosed companies that contributed patents to the MPEG LA-Google deal, or of the MPEG LA pool firm. Frankly, it doesn't matter what company A or company B wants to achieve in this context. At least for now, Google's own license grant under Section 3 of that proposed agreement raises the same issues that Mr. Phipps criticizes with respect to the other patents involved -- Google isn't being more generous than the MPEG LA group in those respects. At any rate, conspiracy theories aren't even needed when simple business logic can explain everything. If a company believes that video codecs should be available on affordable terms, but that intellectual property holders should be compensated somehow, then it can be Google's best friend and will nevertheless attach certain conditions to a license grant. Such conditions can be monetary and non-monetary. The financial part has been resolved. While I doubt that the patent holders gave Google a freebie (considering that they don't even do this in connection with H.264, the standard they promote), Google can apparently afford those royalties without having to charge end users. There's major strategic value for Google to gain in controlling an Internet standard, as non-MPEG LA-contributor Nokia's comments on its decision to withhold a license implied. So Google picks up the bill. But the non-monetary terms shine through its proposed "VP8 Patent Cross-license Agreement".

Mr. Phipps says it's probably "unworkable" for the FOSS community, and at the very least unacceptable, that a licensee must identify itself and sign up to get a license, including downstream users since there's no right to sublicense. The FOSS approach is that someone just grants you a license and the downstream is automatically licensed, too, so you can share freely without any bureaucracy or loss of data privacy involved for anyone. But let's think about the modus operandi of those third-party patent holders, wholly apart from any theories of world domination or destruction. They want a reciprocal license (Section 5 of the proposed VP8 license). That's why Google calls this a "cross-license". It would be foolish for them to make their VP8-essential patents available when a beneficiary of their license grant can withhold a license. But they must have a reasonable degree of legal certainty that they can use the other party's back-licensing obligation as a defense to infringement claims. And that's why they need a formal cross-license agreement in place. Otherwise the licensee could later claim that it never consented to that license grant.

Google itself is a good example -- "good" only in terms of suitability, though bad in terms of behavior -- of why reciprocal-licensing commitments must be formalized. Courts in three different countries have already found Google to fail to honor grant-back obligations vis-à-vis Microsoft -- two of them formally ruled on this (England and Wales High Court, Mannheim Regional Court; both in connection with ActiveSync), and the third one (the United States District Court for the Western District of Washington) did not formally adjudge the issue because Google itself (only its Motorola Mobility subsidiary) was not a party to the relevant case, but nonetheless stated that Microsoft was an intended third-party beneficiary of the Google-MPEG LA agreement concerning H.264. And in those cases, Google had identified itself and formally signed license agreements, but it still disputed the applicability of those terms. Now imagine what would happen if someone with Google's mentality, which a U.S. judge described as "what's mine is mine and what's yours is negotiable" , refused to honor a grant-back obligation and claimed that there wasn't even an enforceable agreement in place... especially in jurisdictions that don't even recognize the concept of third-party beneficiaries to an agreement.

As for field-of-use restrictions, Mr. Phipps criticizes that the license doesn't cover you "[i]f you're writing any multipurpose code or if the way you're dealing with VP8 varies somewhat from the normal format -- perhaps you've added capabilities". Again, let me remind you that Google's own license grant under the proposed agreement comes with the same restrictions. Google itself apparently doesn't want people to modify VP8. It wants to control it. Just the way it controls Android through its arbitrarily-applied compatibility definition. Even if Google ultimately agreed with Mr. Phipps and allowed modifications with respect to its own patents, it would still have to convince those third-party patent holders to grant an equally permissive license. But in that case, someone could use patents that also read on, for example, H.264 and call it a modification of a licensed VP8 codec. Just like Mr. Phipps considers certain aspects of the proposed license "unworkable" for open source, so would it be unworkable for patent holders who generally license their patents on commercial terms to grant a license without any field-of-use restriction (and to an unidentifiable, unlimited number of beneficiaries).

The OSI President hopes that Google will improve this license agreement. But whether it can is another question. It can probably make improvements with respect to its own patents, and I believe that's what it should do at a minimum. This would affect its ability to monetize Motorola Mobility's H.264 declared-essential patents, but those have been found to have very little commercial value anyway. At least Google would show that it respects the FOSS philosophy.

Finally I'd like to talk about what the terms of the proposed license say about the need Google saw to take a license from those 11 MPEG LA contributors. After the announcement of the license deal some people argued that Google merely wanted to avoid litigation but that the agreement didn't constitute an admission of the very third-party patent infringement issues Google had denied for a long time. In other words, they said Google was paying for peace of mind, not for essential intellectual property.

It's true that sometimes license deals are struck even though the licensee is convinced of the merits of its case. That's the nuisance-value business model of certain patent trolls: they'll sue you over meritless claims and offer a license at much less than the cost of a proper defense (which is usually not recoverable in the United States). However, I believe that when all the parties to an agreement are not patent trolls but (as Judge Robart described Google in the MPEG LA H.264 context) "sophisticated, substantial technology firm[s]", then I believe there must be a strong presumption that a license deal doesn't just involve bogus claims. And that presumption is further strengthened if a licensee insisted over the years that certain claims had no merit.

Granted, a presumption, even a very strong one, still isn't proof. One needs to know the actual terms of an agreement to have clarity. None of them were announced two months ago. It's just clear that whatever Google pays is enough that Google can just absorb the costs for the downstream. The amount of money involved could be more, or even much more, than what is needed to prove that Google took those infringement allegations seriously, but if Google pays for it silently (because it can afford it), we won't know. Now at least some of the non-monetary terms are clear -- or they will be clear with definitive certainty if Google, despite criticism from Mr. Phipps and others who will agree with him (or even go beyond his criticism), can't offer a license to those third-party patents on permissive terms. The non-monetary terms demonstrate that Google took those infringement allegations seriously. Otherwise it wouldn't have drafted a license that threatens to divide the Web and FOSS communities, which in turn would have major impact on Google's own open source reputation. The non-monetary price Google is willing to pay here is so substantial that I believe it would have chosen to defend itself in court against any infringement claims (which it could have done proactively through declaratory judgment actions) if it had truly thought that all those infringement allegations were bogus, as it would have had all of us believe.

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:


Wednesday, March 28, 2012

Latest Nokia statement indicates potential for multi-year court battle over nano-SIM patents

After Apple made its royalty-free patent licensing offer related to nano-SIM, Nokia said it was not aware of "any Apple IP which it considers essential to its nano-SIM proposal" (though Apple declared a U.S. provisional patent application to be potentially essential) and reiterated, as its primary concern, its positions that its own proposal is superior and that "Apple's proposal does not meet the pre-agreed ETSI requirements". Today Nokia issued another statement according to which it won't make its patents available to implementers of the nano-SIM standard should Apple's proposal be "selected in violation of ETSI's rules".

Nokia claims to hold "more than 50 patent families covering SIM related technologies that [it] believe[s] may be essential to Apple's proposal". Nokia states that it will, however, honor its "existing commitments to license its standard essential patents under FRAND terms to earlier adopted ETSI standards".

If -- I repeat, if -- it is true that Apple's nano-SIM proposal "does not meet ETSI's technical requirements" and that it could only be adopted in contravention of ETSI's own rules, then Nokia certainly has the right to argue that its FRAND licensing obligation, which it has in its role as a member of the committee working on this particular standard, does not apply to nano-SIM. Given the complexity of the technical issues Nokia raises, a court battle over this question could take years. ETSI is based in France, so any disputes might have to be brought before French courts.

In such a litigation, it would have to be established whether Apple's proposal was in line with ETSI's rules. Another question would be whether Nokia would have an obligation under antitrust law to support such a new standard regardless of an alleged breach of rules.

And that may not even be the end of the story: assuming that Nokia was found to have a FRAND licensing obligation, there could be another multi-year dispute over the royalty rates Nokia would demand from implementers of a standard it vehemently opposed.

Nokia apparently hopes that the prospect of protracted litigation is going to dissuade enough ETSI members from voting in favor of Apple's proposal. Additionally, Nokia accuses Apple of "mis-using the standardization process, seeking to impose its own proprietary solution on the industry and using ETSI merely to rubber stamp its proposal". Given that Apple is willing to make its own IP essential to nano-SIM available on a reciprocal, royalty-free basis, I don't think it's accurate to label it a "proprietary solution". Also, it must have something to offer given that most European network operators support it, according to the Financial Times.

Nokia argues that Apple's approach "is not in the best interests of the industry or, more importantly, of consumers" and insists that "the integrity of ETSI's standardization process should be upheld, with pre-agreed requirements and selection criteria used to ensure fair selection of the best technology". In my personal opinion, pre-agreed criteria should be treated with a certain degree of flexibility when it comes to a vote, especially in an industry with fast-changing needs. And I like the idea of letting companies vote without uncertainty about whether the essential patents will or will not be available on FRAND licensing terms.

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:


Tuesday, March 27, 2012

Apple's U.S. patent application 61481114 might be essential to nano-SIM

Yesterday's news of Apple having offered to make, on a reciprocal basis, any of its intellectual property essential to nano-SIM available on a royalty-free basis has already drawn a lot of interest around the globe. One of the reactions was a response from Nokia consisting of two paragraphs. I'l quote and comment below each quoted paragraph:

"For Nokia, the principal issues remain the technical superiority of our proposal and that Apple's proposal does not meet the pre-agreed ETSI requirements."

I'm not going to take position on "technical superiority" per se. In yesterday's post I linked to a Financial Times article that mentioned concerns over Apple's intellectual property as well as the fact that Apple's opponents object on technical grounds. For those interested in further detail, I recommend this article by The Verge's Chris Ziegler. It compares the technical characteristics of the different proposals, and concludes that "Apple's design is in many ways the least controversial — it rocks the micro-SIM boat as little as possible, whereas Nokia is looking for a more thorough reboot of the now 20-year-old Subscriber Identity Module". (Obviously, "least controversial" is nonjudgmental on quality.)

Like in any situation in which royalty-bearing standards compete with royalty-free proposals, patent encumbrance must be justified with tangible benefits. I have consistently advocated a level playing field between royalty-bearing and royalty-free standards, letting them compete on the merits rather than exclude one business model categorically, but in any economic context, a premium cost must correspond to an appropriate level of premium quality or it's not worth it. That's one the hurdles that Nokia, Motorola and RIM face at this week's ETSI meeting. As a consumer, I wouldn't want to pay (indirectly) Nokia or anyone else patent royalties unless the cost I (indirectly) bear buys me a real benefit. Another success factor for Apple is the broadbased support it has among European mobile network operators.

This leads us to the second paragraph:

"With regard to intellectual property, we are not aware of any Apple IP which it considers essential to its nano-SIM proposal. In light of this, Apple's proposal for royalty free licensing seems no more than an attempt to devalue the intellectual property of others."

I trust Nokia that if they say they were "not aware of any Apple IP which it considers essential to [nano-SIM]", they really weren't, but a simple look-up of the ETSI IPR database, which Nokia is undoubtedly very well aware of because it's one of the biggest contributors, would have answered the question. In fact, several hours before I firstly saw Nokia's statement, a Dow Jones Newswires article on Apple's royalty-free offer had already referred to a document posted on ETSI's website. An updated version of the Dow Jones article can be found on the Wall Street Journal website -- the original one, however, appeared several hours prior to that version and already mentioned the ETSI document. And this link points to the relevant declaration by Apple. If you click on the "IPR information statement annex" tab, you get some additional information, including the number of Apple's U.S. provisional patent application that the declaration relates to: 61481114.

The problem with provisional patent applications is that they are never published. Within 12 months of filing, they must be converted into a "regular" patent application or else they just expire. Patent applications are in stealth mode for 18 months, so provisional applications never make it to the point of publication (except that "regular" patent applications later reference them because they are relevant to the priority date). Therefore, we can't see what's in that particular patent application (other than the title, "Compact Form Factor Integrated Circuit Card", which Apple's statement to ETSI contains), but frankly, the content of that application is not even the most important thing here. What really matters is that Apple's proposal is generous and in the public interest in this particular context.

The FT article showed that there was concern about Apple's patent-based control over the proposed standard. I don't know whether Nokia previously expressed that concern, contrary to its denial of awareness of essential Apple IPRs in the field, but somebody certainly must have told the press about it -- if not Nokia, then some of Apple's other rivals. The key thing is that Apple has not only alleviated but totally eliminated that concern now. The declaration published on the ETSI website relates to only one patent application, and it clearly shows that licenses are available on a reciprocal, royalty-free basis, but the most important thing is that the letter I saw makes the same commitment with respect to any Apple IPR essential to nano-SIM. No trap. No backdoor.

As long as Nokia adheres to FRAND licensing obligations, the Finnish company's position that it wants to cash in on its SIM card-related patents is just as legitimate, from a shareholder value point of view, as Apple's proposal that everyone adopt a royalty-free standard. But Nokia's desire to monetize standard-essential patents is not in the public interest unless its proposal offers major advantages that offset the cost of licensing and the higher transaction cost (which in connection with FRAND patents sometimes involves litigation as I see all the time now).

There are situations in which royalty-free is the way to go. For example, I wouldn't even want to think about what would have happened if Tim Berners-Lee had patented the World Wide Web and collected FRAND royalties on any technologies implementing it. SIM cards aren't comparable to the WWW, but they are such a basic component of wireless devices that a royalty-free standard would clearly be desirable unless it has major shortcomings.

Nokia owns many standard-essential patents, and it's understandable that it's concerned about anything that might "devalue" SEPs. However, since I monitor many litigations in this industry, I'm far more concerned about SEP holders that try to impose excessive license fees and other anti-competitive and anti-innovative terms and conditions than I am about devaluation. It appears that antitrust regulators have a similar perspective at this point.

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:


Monday, March 26, 2012

Apple offers royalty-free license to nano-SIM patents, a proposed standard backed by most European carriers

Last week, the Financial Times reported that Apple is at loggerheads with Motorola Mobility, RIM and Nokia over a proposed standard called "nano-SIM", a further miniaturization of the smart cards now known as "micro-SIM" cards. SIM stands for "subscriber identity module". Nano-SIM cards would be thinner and considerably smaller than micro-SIM cards. Apple has the support of "most of the European operators", according to the FT. The two camps are heading for a showdown later this week (on Thursday and Friday) at the Smart Card Platform Plenary meeting of the European Telecommunications Standards Institute (ETSI) in Sophia Antipolis (Southern France).

A perfectly reliable source that I can't disclose has shown me a letter dated March 19, 2012 that a senior Apple lawyer sent to ETSI. The letter addresses the primary concern of critics of the proposal. The FT said that "the Apple-led proposal has caused some concern among its rivals that the US group might eventually own the patents". But Apple's letter has removed this roadblock, if it ever was any, through an unequivocal commitment to grant royalty-free licenses to any Apple patents essential to nano-SIM, provided that Apple's proposal is adopted as a standard and that all other patent holders accept the same terms in accordance with the principle of reciprocity.

This shows that Apple is serious about establishing the nano-SIM standard rather than seeking to cash in on it. Last year I reported on two different stories (1, 2) about disagreements between Apple and the World Wide Web Consortium (W3C). Let's face it: Apple is a company that values its intellectual property and rarely gives it away for free. But as far as the evolution of SIM cards is concerned, Apple is clearly being generous and absolutely pro-competitive.

Apple's smart (card) move puts a lot of pressure on other companies in the industry. They can no longer claim that Apple will control this new standard, if it does become one, with its patent rights. Instead, they should now step up to the plate and match Apple's offer. In particular, Google is an outspoken advocate of open standards at the EU level, in its own name and through such organizations as Openforum Europe. Unless Chinese regulators still block the deal, it will soon own Motorola Mobility, and for that event, Google should now declare that it will support Apple's reciprocal, royalty-free licensing proposal, in the event that the nano-SIM standard gets adopted, and that it will support royalty-free licensing even if a competing standard won the vote. Openforum Europe, which constantly makes calls on European governments in connection with royalty-free standards, might encourage its member Google to do so, just to avoid the impression of open double standards...

Apple recently lodged a formal complaint over Motorola Mobility's alleged abuse of standard-essential patents with the European Commission. I watch Apple's litigation around the globe and I don't see them assert standard-essential patents, let alone seek injunctions based on them. In fact, another Apple letter to ETSI (which I published last month) takes a clear "no injunction" position on standards-essential patents. Wherever one stands on Apple's assertions of multitouch patents and other non-standard-essential intellectual property rights, Apple's attitude toward standard-essential patents sets an example that others, particularly Google, should follow.

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, February 9, 2012

Google tells European Commission on 'open standards': do as I say, not as I do

More than a year ago, I blogged a few times about the European Interoperability Framework 2.0, a set of IT procurement guidelines that was adopted in December 2010. The most controversial item, which delayed adoption by many months, was a passage that some stakeholders wanted to turn into a ringing endorsement of royalty-free (and generally restriction-free) standards. Ultimately, the relevant statement simply recognized that both FRAND-based as well as royalty-free standards can be implemented in open source, depending on their specific terms. That was a sensible acceptance of reality: both kinds of standards can be compatible or incompatible with different open source licenses.

Throughout and beyond that decision-making process, there was a group of companies that advocated royalty-free (and generally restriction-free) standards quite aggressively. And guess who was part of that small group? Google.

That same Google sent a letter to various standard-setting bodies yesterday according to which there's nothing wrong with demanding royalties of 2.25% of the "relevant end product", or with seeking injunctions against those who refuse to accede to those prohibitive terms.

This is quite a stretch.

There are basically three kinds of positions on industry standards (and, of course, any number of in-betweens):

  1. On one end of the spectrum, there's the position that Google took yesterday: ask for the moon, request injunctions, view patents on standards as a license to kill.

  2. On the opposite end, you have the royalty-free "open standards" movement, which includes Google and its lobbying fronts like OpenForum Europe. They claim that even moderate FRAND rates are totally unacceptable, and governments should discourage such standards altogether.

  3. In between those two extremes, there's a middle ground consisting of companies like Apple, Cisco and Microsoft (as well as many others) who are not against FRAND standards at all but do want the concept of FRAND to be applied in consistent, transparent and commercially reasonable ways.

    Looking at the trend in recent months, it appears that this group in the political center is the one that's growing while those advocating the two extremes are, slowly but surely, losing support.

It really strikes me that Google presents to the European Commission two diametrically opposed visions for open standards. When it addresses the institution as a policymaker (such as in connection with the European Interoperability Framework), it advocates a zero royalties/zero restrictions policy. When it issues a public statement concerning the post-acquisition use of patents in order to address regulatory concerns over FRAND abuse, Google promotes the other extreme. Why can't Google just join all the others who are already in the center of the spectrum? It would avoid contradicting itself, and enhance its credibility.

One thing can be ruled out as a credible explanation for the aforementioned contradiction: the $12.5 billion purchase price Google is offering for Motorola Mobility. If Google believes it needs royalties to generate a return on that investment, others can say the very same thing about the research and development expenditures related to, or acquisition costs of, their patents.

Everyone needs to recognize that holders of standard-essential patents wield a huge stick only as a result of a patent being included in a standard. It doesn't have to be particularly innovative: it just has to cover a mandatory part of a standard.

Some rent-seeking related to patents on standards is acceptable, but overcharging and injunctions are not.

In its "open standards" lobbying efforts, Google would disagree on the first part. As a party that wants to get a major acquisition cleared, Google disagrees on the second part.

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:

Friday, October 14, 2011

Study on the worldwide use of FRAND-committed patents

Many of my consulting projects over the last few years have related to FRAND (fair, reasonable and non-discriminatory) licensing obligations. The purpose of FRAND licensing commitments is to ensure access to intellectual property. It also protects third parties against overcharging and other abusive behavior.

I've written about FRAND issues before. In July I explained the basics of FRAND.

Call for input for a new study

I am working on a study on the worldwide use of FRAND-pledged standards-essential patents in litigation and licensing. In particular, I am looking into

  • the injunctive and/or monetary relief requested based on the alleged infringement of FRAND standard patents,

  • indications of the demands patent holders made in pre-lawsuit negotiations,

  • attempts to leverage such patents in order to receive licenses to unencumbered patents by insisting on a cross-license or by demanding unreasonably high royalty rates for a one-way license,

  • the time it takes until patent holders make an offer of FRAND terms when requested,

  • court rulings and reasonings (including early-stage decisions, for example, on motions to dismiss), and

  • antitrust complaints and investigations triggered by suspicions of FRAND abuse.

If you have information that may be pertinent to this research effort, please contact me via this form. I won't mention you to anyone or share your contact data.

I have been able to track down the most important U.S. lawsuits (and ITC investigations) relating to FRAND-committed patents and EU antitrust investigations involving such patents. I have also found out details about Samsung's assertions against Apple in Australia and the Netherlands. However, in most jurisdictions it's very difficult to get access to pleadings and decisions. That's why I would appreciate help from this blog's global audience (while 50% of my readers are residents of North America, 32% are in Europe and 11% in Asia).

Microsoft has commissioned this study. I will present my findings next year in a published report.

The industry at large relies and depends on FRAND commitments. So does Microsoft, which owns a significant number of standards-essential patents but licenses many more of them from other right holders. Given the strength of Microsoft's patent portfolio and the large scale of its inbound and outbound licensing activities, I am proud that they are interested in my analysis of, and perspective on, the related issues.

Microsoft and I agree on some issues and disagree on others. We were on opposing sides of the debate over a European patent bill years ago. We still have different positions on patent-eligible subject matter. But we do see eye to eye on the post-grant use of patents, i.e., how patents are and should be used after they have been issued, and on some related matters. I like the fact that Microsoft appreciates and respects a diversity of opinions, a fact that has enabled us to work together not only on this FRAND research project but also on a couple of other recent issues facing the industry.

Focus on FRAND

FRAND is one of my specialty areas. Prior to this project, 17 different companies in the financial services industry have hired me for advice in connection with transactions involving FRAND-committed patents to some degree. My work in that field was recently mentioned in the Wall Street Journal. I wish I could name all of my clients because they include some well-known investment banks. For an example, I had a conference call on September 9, 2011 with a large number of clients of a major European bank with a strong global presence. But in that particular industry, confidentiality comes first, and I respect that.

Not all of my clients ask me about FRAND. For instance, I recently contributed to a study on global patent strategies. And my first FRAND-related project ever had nothing to do with patents: on behalf of soccer club Real Madrid, I authored a 42-page paper on the obligation of sports bodies to grant FRAND licenses to teams participating in their tournaments and its relevance to broadcasting and other commercial rights.

"Freemium" business model

Most of the time I keep my consulting work separate from this blog, but in this case I felt that this is the right platform for a call for input.

I basically have a "freemium" ("free" + "premium") business model. If you read my blog, access is free. If you read statements I give to the media (proactively or in interviews), they are free to them, too. The premium part comes into play whenever I deal with professionals who ask for highly individualized explanations and for analysis that goes into greater depth.

I was involved in different roles with MySQL AB, an open source database company, from 2001 until its sale to Sun Microsystems in 2008. They were happy with converting one out of 1,000 non-paying MySQL users into a paying customer. Freemium worked for them then. It works for me now.

Prior to this blog, I also had consulting engagements. To give three examples, I helped MySQL founder Monty Widenius oppose Oracle's acquisition of MySQL as part of Sun in late 2009 and early 2010. I mentioned my work for a soccer club. I also received support from various companies for a campaign against software patents. But in between those projects I worked on other endeavors and "disappeared" from public debates. My blog provides me with a continuous presence, and I now have a much broader client base.

Projects range from short consultations on one topic to more extensive, or repeated, engagements.

All those clients are independent from each other, and I have enough of them to be independent from them. Each of them can expect honest answers and independent, relentless analysis from me. None of them controls my blogging and my public statements: my blog is my personal platform on which I express, exclusively, my own heartfelt convictions.

I now look forward to this FRAND-related research project and thank everyone in advance for their input.

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:

Friday, July 22, 2011

Apple says Samsung has "abusively" asserted UMTS patents to get away with "illicit" copying

Late on Thursday, Apple filed its answer to Samsung's counterclaims in their federal lawsuit in the Northern District of California. The 78-page document contains Apple's defenses and its counter-counterclaims, i.e., Apple's counterclaims to Samsung's counterclaims.

Just to make the procedural context clear: Samsung's counterclaims (to which Apple just responded) are essentially Samsung's original California countersuit against Apple. They recently consolidated that separate countersuit into Apple's lawsuit (which misled many people to think they just dismissed it) and actually increased the number of patents asserted against Apple in California by two. In my opinion, they filed a separate lawsuit initially because they wanted to strike back fast, and probably knew at the outset that the two lawsuits would be merged at some point.

Apple's answer to Samsung's counterclaims is yet another aggressive pleading in this dispute, but I found it pretty informative notwithstanding its accusatory repetitiveness. Let me start with a quick summary of the key points it raises before I elaborate on the FRAND standards issue in greater detail:

  • At least 10 courts in 8 countries on 3 continents

    My most recent battlemap was based on the information I've been able to research about the dispute. It showed eight courts in six countries on three continents, but I always suspected there might be even more going on. In its new filing, Apple claims that "Samsung has sued Apple for infringement and injunctions in no fewer than seven countries outside the United States." This means there are lawsuits in two more countries (and, as a result, at least two more courts) than previously known.

    I asked both Samsung's and Apple's PR departments a few weeks ago. Samsung responded to a couple of other questions in the past but never got back to me with a list of venues; Apple never responded in any way. But this week an Apple SEC filing revealed that France and the Netherlands were the missing countries (hat tip to EdibleApple).

    Since Samsung sued in Germany, the UK and Italy, France was the largest one of the European markets not previously named. The Netherlands is also a frequent venue for patent litigation, sometimes due to the fact that Rotterdam is the world's largest seaport and a key entry point for goods into Europe.

  • Accusations of illicit copying

    Apple continues to denounce Samsung's products as rip-offs -- they don't use that particular word, but they paraphrase it in various ways. In a previous filing they referred to Samsung as "the copyist" (Samsung countered by accusing Apple of seeking to avoid competition). Here are a couple of similar quotes from the new pleading:

    "Samsung has illicitly copied Apple's distinctive design features and innovative technologies instead of pursuing its own independent and costly product development. Samsung has launched one product after another that imitate the look, feel, and function of Apple's products by misappropriating Apple's protected designs and technologies."

    "Apple filed this case to stop Samsung's unauthorized copying of Apple's iPhone and iPad." [that one barely stops short of accusing Samsung of outright counterfeiting...]

    "Having failed to compete successfully with Apple's products (including its iPhone and iPad) by innovating and designing products that customers desire, Samsung has instead launched product after product that unlawfully misappropriate the distinctive designs and patented features that are hallmarks of Apple's success."

  • Apple's friend FRAND

    Besides the usual assertions that it doesn't infringe any valid patents, Apple raises, in great detail, an important legal issue called FRAND ("fair, reasonable and non-discriminatory"). I'll discuss that one in the (relatively long) remainder of the post. In a recent post -- on Samsung's motion to exclude some (or theoretically all) of Apple's outside lawyers from the case -- I already mentioned that Samsung fully expected Apple to raise a FRAND defense against some of its patents.

    Apple now claims that "Samsung has improperly used patents that it claims to be essential to the Universal Mobile Telecommunications Standard ('UMTS') in an attempt to disadvantage Apple", and asserts that Samsung does so in breach off a past commitment to license its declared-essential patents (essential with respect to UMTS).

    As I'll explain now, Apple argues that the related commitments limit the ways in which Samsung can use such patents in this dispute with Apple. In Apple's view, Samsung can at the most ask to be paid for Apple's use of such patents (if they're valid and infringed contrary to Apple's claims), but Apple says Samsung can't just ask for injunctions against Apple prior to offering FRAND licensing terms. In other words, it's all about whether those allegedly FRAND-committed UMTS patents have teeth in this dispute compared to the patents asserted by Apple.

    The most important legal issue in this context is the question of whether a patent holder can use FRAND-committed patents to force an (alleged) infringer to cross-license patents that are unencumbered by such a commitment. This is what Apple asserts:

    "At bottom, Samsung is attempting to coerce Apple into tolerating Samsung's infringement of its intellectual property and copying of the innovative features that distinguish Apple products by abusively asserting Declared-Essential Patents, in breach of its FRAND commitments."

    "After months of repeated Apple requests for a FRAND offer, Samsung has recently claimed that it is willing to quote Apple FRAND license terms, but it has not yet done so or given any indication what those terms will be. In particular, in breach of its FRAND commitments, Samsung has yet to provide license terms for its Declared-Essential Patents, standing alone, and has taken the position in prior talks with Apple that discussions over FRAND license terms need to be tied to a broader licensing deal that would include a cross-license to Apple non standards-essential patents – including patents covering the distinctive design and functions of the iPhone and iPad."

    This is a recurring legal issue. It came up in Apple's dispute with Nokia (which was, however, settled before any such decision was taken by a court). Apple raises a FRAND defense against Motorola. Microsoft sued Motorola pre-emptively early in their dispute to assert its rights under FRAND rules (in that case called RAND, which is however synonymous with FRAND). So this is an important concept to understand in connection with many smartphone and other patent disputes.

    In connection with this particular dispute, note that Apple doesn't claim that all 12 patents asserted by Samsung in that particular lawsuit are subject to FRAND commitments. The exact number is not specified, but there are indications in the text that Apple means seven of the twelve asserted patents (more or less). And those could be the seven most important one, so the FRAND issue could be outcome-determinative for the entire Apple-Samsung dispute.

I don't mean to jump to conclusions early in the process, but having read Apple's reasonably plausible theories concerning FRAND (even though I don't support the entirety of Apple's portrayal of Samsung as a total thief), I increasingly tend to believe that Samsung's counterclaims against Apple are fairly weak. I've been watching such processes for some time now and generally it's a sign of weakness if a party points FRAND patents against unencumbered patents. By contrast, Nokia sued Apple over FRAND patents only to secure a royalty payment on them, but asked for an injunction only for the event that Apple wouldn't pay FRAND royalties. The longer the dispute between Nokia and Apple took, the more Nokia relied on unencumbered patents, and ultimately emerged victorious. I see Motorola on the losing track against Microsoft, and Motorola appears to be doing something similar to what Samsung is doing.

While Samsung has 28,700 U.S. patents (far more than Apple) according to one of its recent pleadings, it may not have many that really matter to Apple, and that's why Samsung appears to have resorted to a legally very questionable use of FRAND patents -- that could be downright abuse (as Apple alleges) -- and lawsuits in many countries (breadth, not depth). Again, I don't agree with Apple on everything, but at the least I would say that I have serious doubt about the strength of Samsung's counterclaims against Apple at this stage. I will, of course, revisit the situation whenever anything new happens or surfaces.

The concept of FRAND business terms

A voluntary commitment (or, alternatively, a contractual or legal obligation) to do business on FRAND terms is not specific to smartphones or patents. It's a universal concept. In fact, I did a fair amount of work (officially on behalf of Real Madrid CF and in an informal alliance with FC Barcelona) on FRAND issues in connection with soccer broadcasting rights and the right of soccer clubs to participate in tournaments on FRAND terms. In that particular context -- and in some others -- I'm a big fan of FRAND.

So what does FRAND mean? To simplify this, let's not worry about the meaning of the "F" as in "fair". When Americans say "RAND", they mean essentially the same as what European law defines as "FRAND". RAND isn't unfair only because it doesn't explicitly mention the word "fair".

That leaves us with two components: "reasonable" and "non-discriminatory".

"Reasonable" means that business terms must be appropriate. There must be a valid reason for a certain price or a certain requirement, such as a limitation on someone's right to use a patent. "Asking for the moon" is unreasonable, and thus a violation of the FRAND idea.

"Non-discriminatory" means that there must be a valid reason for treating different business partners differently, but all other things being equal, you can't just discriminate based on race, gender, or any other motive that's unrelated to the transaction itself, such as discriminating against a competitor just because you don't like competition.

An example of discrimination is discriminatory pricing. If you made a FRAND commitment on the sale of, say, crude oil and you charge customer A $100.00 per barrel but customer B $150.00 for the same quantity, this could be a case of discrimination. If you have the same cost of supplying them and they buy similar quantities, it most probably is. If customer B buys much smaller quantities, the difference seems high but it might be justifiable on that basis. Or maybe customer B gets his oil shipped to a remote location that it's expensive to make deliveries to. That might also justify it. Or maybe there are several such factors that jointly serve as justification. But absent any sufficient justification, it's discrimination.

Discrimination is particularly easy to prove if there's a pattern. If a company conspicuously overcharges its competitors while it offers much more attractive prices to non-competitor customers, there's at least a strong suspicion of discrimination. Another example of such a pattern: a company consistently decides against job applicants with Asian names even though those are, on averagae, equally qualified as other candidates. Again, the pattern raises suspicion. That's not the same as conclusive evidence. There could still be a reason. If a basketball team recruits fewer Asian players than demographics suggest, it could be due to the fact that on average they aren't the tallest people (in exchange, Asian students outperform other groups in math contests).

When people are dissatisfied with a mere FRAND commitment in a certain context, such as industry standards, you may hear them say that FRAND is an "empty word [or term]". I don't agree. FRAND is very meaningful, and FRAND commitments and obligations help solve many problems on a daily basis. The term FRAND per se obviously doesn't say what the price per barrel of crude should be, recognizing that the circumstances of each sale can be different and there isn't one price that suits all situations. But FRAND is a framework. It's a line that one must not step over. There are many ways to meet FRAND criteria, but there are also clear types of behavior that courts have found (in different industries and jurisdictions) to be unfair and/or unreasonable, and anything unfair and/or unreasonable is a violation of a FRAND commitment or obligation.

Indeed, Apple's defenses against Samsung's counterclaims (i.e., Samsung's original California countersuit) don't say what terms Samsung must offer with respect to the patents in question. There are many roads that lead to Rome in terms of FRAND compliance. But Apple alleges in its defenses and counterclaims that some of Samsung's actions and demands cannot be reconciled with the concept of FRAND. They constitute -- Apple says -- a breach of a FRAND commitment. Apple wants the court to dismiss any Samsung demands that run counter to past FRAND commitments, and beyond that, to establish Samsung's breach and order damages. In other words, Apple wants the court to give meaning to FRAND.

FRAND-based industry standards

Last year I did several posts on FRAND in connection with industry standards, in particular, such industry standards that are considered open standards. There was a policy-making process going on in Europe in connection with software developed and purchased by governments. The European Commission ultimately determined that it considers standards "open" if their patent licensing terms are either royalty-free or FRAND-based, but in any case, they should be compatible with open source licenses. I had proposed that approach as a compromise.

In the build-up to that decision I also provided an overview of standards- and open source-related contexts in which the European Commission supported FRAND.

FRAND commitments in connection with standards are very common. Companies participating in a standard-setting process should not be allowed to abuse their involvement with the process by way of "patent hold-up" (that term also comes up in Apple's filing, but they didn't invent it, even though they lay exclusive claim to a term like "app store"). A FRAND commitment is designed to prohibit abuse. It can't prevent abuse from happening, but if and when it occurs, FRAND can be a powerful weapon to resolve the problem.

Standard-setting organizations typically structure FRAND commitments as contractual obligations. By the way, this also includes the Java Community Process.

FRAND is also a way for standard-setting organizations to comply with competition law. If you have a group setting an industry standard that collectively dominates a relevant market, you want to make sure it wouldn't be viewed as an (illegal) cartel under competition law. FRAND commitments can help to address that problem.

Apple's UMTS dispute with Samsung

At issue between Apple and Samsung are (more or less) seven patents that are apparently considered (at least by Samsung) essential to UMTS:

"At various times, Samsung declared seven of the Samsung Asserted Patents to the European Telecommunications Standards Institute ('ETSI'), a leading Standards Setting Organization ('SSO'), as purportedly essential to practice the UMTS standard ('Declared-Essential Patents').

Apple then complains about two problems -- it alleges Samsung's failure to abide by ETSI's rules and subsequently accuses Samsung of failure to honor its FRAND licensing commitments:

"Time and again, however, Samsung deliberately and deceptively failed to disclose its purported intellectual property rights ('IPR') to ETSI before its members decided to incorporate into the standard technologies purportedly covered by Samsung's patents, in violation of the ETSI's IPR policy. Furthermore, Samsung committed to license its Declared-Essential Patents on fair, reasonable, and non discriminatory ('FRAND') terms. In breach of those commitments, Samsung now seeks to enjoin Apple from selling its end products because those products contain UMTS chipsets – which Apples purchases from third parties – that are allegedly covered by Samsung's Declared-Essential Patents."

The "third parties" Apple mentions toward the end of the quoted passage include, primarily, Qualcomm. Several paragraphs in Apple's filing discuss the use of Qualcomm's chipsets in Apple's products and the related legal issues. Here's another sentence that makes reference to those third-party products:

"Samsung's allegations of infringement concern UMTS-compliant chipsets that Apple buys from large manufacturers and then incorporates in its end consumer products (including the iPhone and iPad) to provide cellular communication capability."

Let's look at a more specific allegation of how Samsung purportedly tried to game the standard-setting system. Apple alleges a failure on Samsung's part to declare essential patents in time. "Essential" means that a reasonable implementation of a standard is (more or less) impossible without a license to a certain patent. Standard-setting organizations want companies to tell them early and often if they have patents of that kind, and then they want to know whether they commit to license them on the terms for the relevant standard. (I recently reported on Apple's refusal to license one issued patent and a pending one under the W3C's terms.)

Apple alleges that Samsung "deceptively concealed certain of its IPR during the standards-setting process to maximize its chances of having the technology incorporated into the standard" and alleges the following:

"In fact, in some cases, a named inventor on the application for the concealed patent or other Samsung personnel participated in the relevant working group, championed Samsung's technical proposal, and affirmatively steered the SSO to standardize technology that Samsung now claims to be covered by its patents. Samsung disclosed certain of its IPR only after the relevant standard or standard specification was finalized."

That passage suggests Apple has evidence that could be quite important in this context.

The rights (and types of relief) Apple claims under FRAND

I said before that the core issue here is whether Samsung is free to use FRAND-committed patents against Apple in a way that could force Apple to cross-license its non-standars-related patents. In this context, a very important question is whether Samsung can obtain an injunction without previously offering Apple business terms within the FRAND framework. If Samsung can "only" ask for money while Apple can claim an absolute entitlement to an injunction (though there clearly are hurdles to be met under U.S. patent law at any rate), Apple is in a stronger position just because it patents-in-suit were never committed to FRAND. It's like Apple having a lethal weapon in its hands and Samsung being limited (with respect to the subset of its asserted patents that is subject to FRAND commitments) to the option of setting up a parking meter.

Apple's argument is that Samsung wants to use a partly FRAND-committed set of patents as a counterthreat against Apple -- in eight countries as I mentioned earlier on -- until Apple grants Samsung a license to its own patents, which are however not FRAND-committed (I haven't even seen Samsung make that claim, so it's a safe assumption Apple's asserted patents are unencumbered). By forcing Apple to cross-license, Samsung would effectively get away with what Apple portrays as a theft of intellectual property of major proportions. Here are some quotes that show Apple's line of thought:

"[...] Samsung has improperly used patents that it claims to be essential to the Universal Mobile Telecommunications Standard ('UMTS') in an attempt to disadvantage Apple."

"Samsung has abusively asserted patents in this action that it claims are standards-essential to further its strategy of copying Apple products. Apple has repeatedly demanded that Samsung put a halt to its persistent pattern of copying. In retaliation, and to deflect from its own copying and to pressure Apple to allow Samsung to continue to imitate, Samsung asserted counterclaims alleging that Apple infringes Samsung patents that are purportedly essential to the UMTS standard."

"Samsung's persistent attempt to compete with Apple by imitation rather than through its own innovation is manifest in its illegal efforts to coerce Apple into allowing Samsung to copy its iPhone and iPad with impunity. After Apple informally sought and eventually sued to halt Samsung's ongoing pattern of imitation and infringement regarding the iPhone and iPad, Samsung retaliated by bringing litigation and then counterclaims seeking to enjoin Apple from selling products that comply with the UMTS telecommunications standard. Samsung has done so notwithstanding that Apple is licensed or, in the alternative, has the irrevocable right to a FRAND license to Samsung’s Declared-Essential Patents by virtue of Samsung’s commitment to license those patents on FRAND terms."

"Thus, Samsung is seeking, unlawfully and in breach of its FRAND commitments, to leverage the monopoly power it wrongly obtained in the Input Technologies Markets (defined below) from its untimely disclosures and/or its false FRAND commitments to ETSI in a discriminatory manner to try to coerce Apple into tolerating Samsung’s pattern of repeatedly infringing Apple's designs, trademarks and non standards-essential patents or licensing to Samsung its proprietary technology (to which Samsung is not entitled). Left unaddressed, this conduct will chill innovation, quality, and price competition for end products that comply with the UMTS standard by allowing Samsung to free ride on Apple's massive investments in innovation and product development rather than invest in its own distinctive products that consumers desire."

The passages above show that Apple believes the relevant parts of Samsung's counterclaims against Apple should be doomed to fail because of the FRAND terms that govern the UMTS standard.

Apple's lawyers derive a variety of rights from this. Not only do they use FRAND as a defense but they also bring their own counter-counterclaims related to such theories as breach of contract, promissory estoppel, violation of Sections 1 and 2 of the Sherman Act and certain California laws, such as on unfair competition. Apple wants the court to declare that it's either already licensed to Samsung's declared-essential patents or at least has an entitlement to be licensed on FRAND terms, and that Samsung therefore has no right to seek an injunction (at least not prior to offering FRAND terms):

"There is a dispute between the parties whether Samsung is entitled to injunctive relief if it prevails on any of its patent infringement claims. Despite having admitted and contended in other litigation that a patent holder waives all rights to seek injunctive relief upon making a FRAND commitment, Samsung seeks injunctive relief against Apple in its Counterclaims. Apple contends, as Samsung has acknowledged in other litigation, that Samsung’s sole remedy in this case is to seek payment of royalties on FRAND terms."

In this wider context, Apple positions itself as a defender of the public interest:

"Apple seeks to bring this misconduct to an end and thereby prevent further harm to the wireless telecommunications industry, consumers, and Apple."

Apple even argues with "price competition" that FRAND-based standards allow. That is true. It's just funny that Apple would argue with this, given that Apple is not exactly known for bringing down prices in any particular market.

Samsung will now have to defend itself against Apple's counter-counterclaims and say what it believes to be entitled to in the event those patents are indeed standards-essential.

I will comment on this next time (at the latest) after Samsung's answer becomes available. That may take a few weeks, or even a couple of months.

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.


Share with other professionals via LinkedIn:

Saturday, July 9, 2011

Apple's latest patent foe: the World Wide Web Consortium (W3C)

It's not like Apple needs more hassle on the patent front. Think of its "global war" with Samsung (eight venues, six countries, three continents), its disputes with HTC and Motorola, the unresolved Kodak problem, Lodsys's lawsuit and assertions against app developers, and a few dozen trolls, one of whom was just handed a jury verdict worth $8 million for the infringement of two playlist patents.

And now the vaunted W3C (World Wide Web Consortium), which has hundreds of corporate members, has launched a frontal assault on one of Apple's patents and one of its patent applications with a public call for prior art.

Hat tip to Anant Puranik, who pointed me (via Twitter) to this informative post on his PatentsInd blog, which covers patent matters in India.

The related announcement by the W3C

Let me quickly copy the text of the W3C announcement. Don't worry if some of it is not immediately clear to you because this is related to how standardization bodies in general and the W3C in particular operate. I'll explain further below what this is all about. Here's the text:

This is a public call for prior art on patent Application No. 11/432,295 and on Patent 7,743,336. The W3C seeks information about access control systems available before October 2005 and content distribution systems before April 2006 that offer a viable solution that may apply to the use of access requests policy in Widgets. People who wish to provide feedback should refer to the call for prior art for more information. On 13 November 2009, pursuant to its rights under W3C's Patent Policy, Apple, Inc. disclosed US Published Patent Application No. 11/432,295 and US Published Patent Application 11/409,276 and claimed that it applies to the Web Applications WG's Widget Access Request Policy specification. Apple excluded all claims from the W3C Royalty-Free License commitment of the W3C Patent Policy given by Participants of the Web Applications Working Group. In accordance with the exception procedures of the Patent Policy, W3C launched a Patent Advisory Group (PAG) to determine possible solutions. The PAG has advised W3C to issue this call for prior art.

The W3C has a rigid "royalty-free" licensing policy. If patents are essential to its standards (meaning you can't implement the given standard in any reasonable way without infringing such a patent), they must be made available "to all, worldwide, whether or not they are W3C Members" on a royalty-free basis. The W3C allows patent holders to impose certain conditions, but generally, if you make a patent available to a W3C standard, you have to give up most of your rights. By contrast, most standard-setting organizations operate under a so-called FRAND (fair, reasonable and non-discriminatory) -- or just RAND, without explicitly stating "fair" -- regime. FRAND commitments ensure the availability of patents but patent holders still reserve far more rights than under the W3C's policy.

Apple wants to be able to sue over those patents

Apple is a member of the W3C and, in that role, disclosed the fact that it holds one U.S. patent and one U.S. patent application that Apple believes read on the W3c's "Widget Access Requests Policy" specification. At the same time, Apple exercised its right to withhold those intellectual property rights. In other words, Apple refuses to make those rights available on the W3C's liberal terms. Simply put, Apple doesn't want to be restricted in any way and may want to assert those patents in its various lawsuits.

This means the W3C can't formally adopt the "infringing" specification because its rules require patent-free or at least royalty-free standards. For now the Widget Access Request Policy is just a candidate recommendation, not a final specification yet.

If a patent holder refuses to accept the W3C's terms, the W3C may try to have that patent invalidated (or a patent application rejected). If that effort succeeds, the specification is, again, patent-unencumbered. If not, the W3C can still evaluate possible workarounds or, if there's no workaround, give up on a standard.

In this case, the W3C hopes to do away with Apple's relevant patent and patent application. It's an unpleasant situation for the W3C to have to confront one of its members, especially such a large and powerful one, but sometimes this can't be avoided.

Another W3C patent fight: video codecs

This isn't the only issue in connection with which Apple favors the rights of patent holders over unencumbered standards: the W3C's rigid "royalty-free" policy is also a big problem in the debate over video codecs -- MPEG LA vs. the Google-led WebM. MPEG LA is a licensing agency for many patent holders, not to be confused with the MPEG (Moving Picture Experts Group) standard-setting organization. MPEG has plans for a royalty-free video codec specification. The market-leading AVC/H.264 standard comes with royalty obligations except for limited fields of use. MPEG LA collects royalties on behalf of the holders of many (possibly all) patents essential to AVC/H.264. Google and its allies would like to turn WebM into a W3C standard (in fact, into the default video codec under HTML 5), claiming that it's "royalty-free".

However, Apple and other major players oppose Google's proposal. There's serious doubt that it's truly unencumbered by third-party patents. Since there are now 47 Android-related patent infringement lawsuits going on by my count and frequent reports of patent holders (such as Oracle) demanding or actually (such as Microsoft) collecting royalties from Android device makers, Google has lost its credibility whenever it claims that its "open source" technologies are truly unencumbered.

With the strategic importance that patents have now (also evidenced by the $4.5 billion paid for Nortel's patent portfolio), I guess the W3C is going to find it increasingly difficult to develop standards under its policy. There's still going to be some interest among industry players in the W3C's ability to develop its standards, but a company like Apple is certainly not the most generous contributor of patents to "free" standards, to put it mildly. And when you're embroiled in so much litigation, it's probably a bad time to ask you to give up rights that you may want to assert against the likes of Samsung and Motorola. That's the problem.

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.


Share with other professionals via LinkedIn:

Monday, March 14, 2011

Red Hat feeds the patent trolls and fools the FOSS community

I have dug up a court filing that reveals one of the best-kept secrets in the open source industry: Red Hat coughed up $4.2 million in June 2008 to settle a patent infringement suit that had been brought by FireStar Software.

In a world in which hundreds of thousands of software-related inventions have been patented, chances are that Red Hat has concluded more transactions of the FireStar kind. Red Hat settled another patent lawsuit (with Acacia subsidiary Software Tree LLC) in October 2010 and most likely made a payment (which might have been higher than in the FireStar case). The vast majority of all license deals are negotiated privately without litigation or announcements, so Red Hat may have quietly signed patent license agreements with a number of other right holders and never even talked about it. For example, just in connection with the acquisition of JBoss, Red Hat set aside $43 million for the settlement of claims that included (but were not limited to) the FireStar lawsuit.

While patent license agreements are just a routine deal for traditional IT companies, the significance of this finding lies in how it reflects on Red Hat's credibility:

  • In political and regulatory contexts, the market-leading Linux distributor insists on the false claim that open source licenses (especially the GPL) are absolutely incompatible with the payment of patent royalties (while this simply depends on the specific terms and conditions of a deal).

  • The GPL also serves as Red Hat's pretext for refusing to offer its customers implementations of patent-encumbered standards such as the popular AVC/H.264 video codec.

  • Another important credibility issue is that the world's largest open source company actually fails to be open about its patent-related dealings and positions, a fact that others have criticized before. It hides behind self-imposed confidentiality obligations and employs legalese terminology that in the eyes of many laypeople will appear far more favorable to Red Hat than a straightforward representation of the facts would.

I take the revelation of Red Hat's patent royalty payment as a confirmation that the open source industry actually accepts software patents as a fact of life and opposes them only as lip service to curry favor with the FOSS community. As much as I regret that, at this stage I just try to describe what's actually going on in the industry and to see through smokescreens.

Red Hat is a publicly traded company trying to make quarterly and annual numbers, not an open source project, let alone an activist group. Red Hat's shareholders support the community's causes only to the extent they consider such efforts economically advantageous from a very short-term perspective. If they can achieve the desired goodwill with make-belief at a lower cost, then that's what they'll do. Don't let them fool you. To them, this is just business.

They also put plain business interests above openness in connection with their hidden Linux kernel patches.

The payment was kept confidential but surfaced in a different lawsuit

In 2006, FireStar Software filed a lawsuit with the US District Court for the Eastern District of Texas, alleging the infringement of a patent related to linked databases (US Patent No. 6,101,502) by Hibernate, a JBoss product. When FireStar first approached JBoss, the company was in the process of being acquired by Red Hat, a fact that FireStar may have regarded as a financial opportunity.

The patent-in-suit was later assigned to a Texas company named Datatern. An investment group named Amphion Innovations US, which owns a stake in FireStar and set up its wholly-owned subsidiary DataTern as a patent licensing company (i.e., a non-practicing entity), also became a party to the suit.

The settlement related to any or all patents held by those companies that might be infringed by Red Hat's products. Red Hat published a redacted version of the settlement agreement and a "reader's guide" to it. the only part that had been redacted was Section 3, "PAYMENT". There were different references to that payment in the publicly available parts of the agreement (and the parties agreed to pay their own legal fees), but the amount was not stated anywhere else. Section 7 stipulates a confidentiality obligation concerning the section on payment.

Later the plaintiffs sued the law firm that had represented them against Red Hat for alleged malpractice. In connection with that case (case no. 2:09-cv-00038, Eastern District of Texas), the parties initially didn't mention the amount paid by Red Hat, but then an additional group of companies came in: IP Navigation Group and affiliated entities. Those companies belong to Erich Spangenberg. who according to law.com runs one of the "largest, and most litigious, patent-holding companies" and recommends a "sue first, ask questions later" approach. The article quotes patent defense company PatentFreedom, according to which "entities connected to Spangenberg have sued more than 500 [by now even more than 600] companies for patent infringement since 2005". This aggressive patent monetizer became involved with the FireStar/Red Hat dispute when the right holders were unhappy about the state of affairs and brought him in as additional firepower to pressure Red Hat into a settlement.

On October 1, 2009, Foley & Lardner (the firm that represented FireStar), amended its "counterclaims, third-party complaint, and cross-claims", and paragraph 11 of that document made the following revelation:

"Of the $4.2 million settlement that the Plutus Parties [Spangenberg] obtained on behalf of Plaintiffs [Amphion/Datatern], the Plutus Parties took $3.4 million."

Statements made in such a court filing must have evidentiary support, so we can rely on the accuracy of that information.

GPL compliance of patent royalty payment

In an effort to appease the FOSS community, in which there is a widespread belief that the GPL doesn't allow inbound patent licensing, Red Hat emphasized in its announcement that its settlement also covers "community members" (upstream and downstream) as "third party beneficiaries". Indeed, Section 9.12 of the settlement agreement contained some provisions. In the press release announcing the deal, Red Hat's patent attorney Richard Fontana said:

"Red Hat's settlement satisfies the most stringent patent provisions in open source licenses, is consistent with the letter and spirit of all versions of the GPL and provides patent safety for developers, distributors and users of open source software"

Eben Moglen of the Software Freedom Law Center reviewed the agreement and concluded that it would also be compatible with GPLv3 (although only GPLv2 was relevant to that particular deal). He liked the fact that its terms "provide additional protection to other members of the community upstream and downstream from Red Hat" and welcomed "Red Hat's efforts on the community's behalf."

Considering a $4.2 million payment compatible with the GPL is, however, in contradiction with what Red Hat and its lobbying fronts claim in different political and regulatory contexts. For example, when the European Commission was updating its European Interoperability Framework (a set of procurement guidelines), Red Hat and its different lobby groups claimed that only royalty-free standards are compatible with the GPL and other important FOSS licenses. I debunked that false claim and instead advocated a proper distinction between patent licensing terms and conditions that work for FOSS from those that don't. That is exactly the approach the EU took in the final version of those guidelines.

I believe Red Hat should have told European policymakers the truth about its FireStar settlement and unknown number of other patent license deals in place instead of trying to gain a political advantage with incorrect claims that royalties are inherently GPL-incompatible.

Patent royalties and the debate on video codecs

In the EU debate I mentioned before, Red Hat used MPEG's royalty-bearing codecs as an example of patent-encumbered statements that it claims it cannot implement because of the GPL. However, if Red Hat can pay $4.2 million to FireStar (and who knows how much to who knows how many other patent holders), why can't it pay a royalty to MPEG LA for an AVC/H.264 license? The maximum payment in the MPEG LA structure for such a license would be $6.5 million.

I looked into those terms last year, and the maximum amount has meanwhile been increased from $5 million to $6.5 million. The current amount was stated by Ed Bott on his ZDNet blog.

Where there's a will, there's a way -- and in this case I believe Red Hat simply doesn't want a solution. Unfortunately, this limits choice among codecs for its customers, for no good reason. Red Hat simply wants to maximize its profitability at the expense of innovation and progress.

Google argues that its WebM/VP8 codec is needed in order to have a video codec standard that is implementable in open source. It's uncertain whether Google's offering is indeed patent-unencumbered and therefore won’t be subject to royalties at some time down the road.

MPEG is already working on a royalty-free codec of its own. In my opinion, the open source industry should give AVC/H.264 serious consideration despite royalties. The price to be paid is limited, and one of the benefits is that it's a multi-vendor standard while WebM/VP8 is just one company's offering, even if seemingly available on open source terms.

Red Hat isn't forthcoming

Red Hat uses the word "open" a lot, but in connection with patent licensing it isn't really transparent. A few months ago, Red Hat settled litigation with an Acacia subsidiary named Software Tree LLC. Previously, Red Hat had fended off infringement allegations by a different Acacia company, IP Innovation LLC, because it was not found by a jury to infringe any valid patents. But Software Tree LLC asserted patents that had previously survived invalidation attempts and were considered reasonably strong by a Texas-based patent lawyer I asked.

Red Hat didn't announce any terms of the deal with Software Tree LLC, and its complete failure to be forthcoming had many people concerned. You can read some good questions and well-reasoned criticism from Open Source Initiative co-founder Bruce Perens on GigaOM and on other sides including internetnews.com (also picked up by LinuxWeeklyNews), Australia's iTWire, and techdirt.

The most likely explanation is that the deal was worse than the FireStar settlement, especially as far as the interests of the wider open source community are concerned. If Red Hat could have made the same claim about protection of other open source developers (upstream and downstream) as in the FireStar case, I guess it would have done so.

Even in the FireStar case, Red Hat should at least have made it clearer that it ended up paying significant royalties. Not huge, but definitely significant.

Richard Stallman, the president of the Free Software Foundation, also voiced a caveat concerning the FireStar announcement:

"If we can judge from Red Hat's statement, the deal is good for the free software community. I would not want to treat that as certain; they might have chosen not to mention some negative side."

Again, that related to Firestar. But I wonder what RMS thinks of Red Hat's refusal to disclose any information at all concerning its settlement with Software Tree LLC.

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.

Share with other professionals via LinkedIn: