Archives For google

Last year, Microsoft’s new CEO, Satya Nadella, seemed to break with the company’s longstanding “complain instead of compete” strategy to acknowledge that:

We’re going to innovate with a challenger mindset…. We’re not coming at this as some incumbent.

Among the first items on his agenda? Treating competing platforms like opportunities for innovation and expansion rather than obstacles to be torn down by any means possible:

We are absolutely committed to making our applications run what most people describe as cross platform…. There is no holding back of anything.

Earlier this week, at its Build Developer Conference, Microsoft announced its most significant initiative yet to bring about this reality: code built into its Windows 10 OS that will enable Android and iOS developers to port apps into the Windows ecosystem more easily.

To make this possible… Windows phones “will include an Android subsystem” meant to play nice with the Java and C++ code developers have already crafted to run on a rival’s operating system…. iOS developers can compile their Objective C code right from Microsoft’s Visual Studio, and turn it into a full-fledged Windows 10 app.

Microsoft also announced that its new browser, rebranded as “Edge,” will run Chrome and Firefox extensions, and that its Office suite would enable a range of third-party services to integrate with Office on Windows, iOS, Android and Mac.

Consumers, developers and Microsoft itself should all benefit from the increased competition that these moves are certain to facilitate.

Most obviously, more consumers may be willing to switch to phones and tablets with the Windows 10 operating system if they can continue to enjoy the apps and extensions they’ve come to rely on when using Google and Apple products. As one commenter said of the move:

I left Windows phone due to the lack of apps. I love the OS though, so if this means all my favorite apps will be on the platform I’ll jump back onto the WP bandwagon in a heartbeat.

And developers should invest more in development when they can expect additional revenue from yet another platform running their apps and extensions, with minimal additional development required.

It’s win-win-win. Except perhaps for Microsoft’s lingering regulatory strategy to hobble Google.

That strategy is built primarily on antitrust claims, most recently rooted in arguments that consumers, developers and competitors alike are harmed by Google’s conduct around Android which, it is alleged, makes it difficult for OS makers (like Cyanogen) and app developers (like Microsoft Bing) to compete.

But Microsoft’s interoperability announcements (along with a host of other rapidly evolving market characteristics) actually serve to undermine the antitrust arguments that Microsoft, through groups like FairSearch and ICOMP, has largely been responsible for pushing in the EU against Google/Android.

The reality is that, with innovations like the one Microsoft announced this week, Microsoft, Google and Apple (and Samsung, Nokia, Tizen, Cyanogen…) are competing more vigorously on several fronts. Such competition is evidence of a vibrant marketplace that is simply not in need of antitrust intervention.

The supreme irony in this is that such a move represents a (further) nail in the coffin of the supposed “applications barrier to entry” that was central to the US DOJ’s antitrust suit against Microsoft and that factors into the contemporary Android antitrust arguments against Google.

Frankly, the argument was never very convincing. Absent unjustified and anticompetitive efforts to prop up such a barrier, the “applications barrier to entry” is just a synonym for “big.” Admittedly, the DC Court of Appeals in Microsoft was careful — far more careful than the district court — to locate specific, narrow conduct beyond the mere existence of the alleged barrier that it believed amounted to anticompetitive monopoly maintenance. But central to the imposition of liability was the finding that some of Microsoft’s conduct deterred application developers from effectively accessing other platforms, without procompetitive justification.

With the implementation of initiatives like the one Microsoft has now undertaken in Windows 10, however, it appears that such concerns regarding Google and mobile app developers are unsupportable.

Of greatest significance to the current Android-related accusations against Google, the appeals court in Microsoft also reversed the district court’s finding of liability based on tying, noting in particular that:

If OS vendors without market power also sell their software bundled with a browser, the natural inference is that sale of the items as a bundle serves consumer demand and that unbundled sale would not.

Of course this is exactly what Microsoft Windows Phone (which decidedly does not have market power) does, suggesting that the bundling of mobile OS’s with proprietary apps is procompetitive.

Similarly, in reviewing the eventual consent decree in Microsoft, the appeals court upheld the conditions that allowed the integration of OS and browser code, and rejected the plaintiff’s assertion that a prohibition on such technological commingling was required by law.

The appeals court praised the district court’s recognition that an appropriate remedy “must place paramount significance upon addressing the exclusionary effect of the commingling, rather than the mere conduct which gives rise to the effect,” as well as the district court’s acknowledgement that “it is not a proper task for the Court to undertake to redesign products.”  Said the appeals court, “addressing the applications barrier to entry in a manner likely to harm consumers is not self-evidently an appropriate way to remedy an antitrust violation.”

Today, claims that the integration of Google Mobile Services (GMS) into Google’s version of the Android OS is anticompetitive are misplaced for the same reason:

But making Android competitive with its tightly controlled competitors [e.g., Apple iOS and Windows Phone] requires special efforts from Google to maintain a uniform and consistent experience for users. Google has tried to achieve this uniformity by increasingly disentangling its apps from the operating system (the opposite of tying) and giving OEMs the option (but not the requirement) of licensing GMS — a “suite” of technically integrated Google applications (integrated with each other, not the OS).  Devices with these proprietary apps thus ensure that both consumers and developers know what they’re getting.

In fact, some commenters have even suggested that, by effectively making the OS more “open,” Microsoft’s new Windows 10 initiative might undermine the Windows experience in exactly this fashion:

As a Windows Phone developer, I think this could easily turn into a horrible idea…. [I]t might break the whole Windows user experience Microsoft has been building in the past few years. Modern UI design is a different approach from both Android and iOS. We risk having a very unhomogenic [sic] store with lots of apps using different design patterns, and Modern UI is in my opinion, one of the strongest points of Windows Phone.

But just because Microsoft may be willing to take this risk doesn’t mean that any sensible conception of competition law and economics should require Google (or anyone else) to do so, as well.

Most significantly, Microsoft’s recent announcement is further evidence that both technological and contractual innovations can (potentially — the initiative is too new to know its effect) transform competition, undermine static market definitions and weaken theories of anticompetitive harm.

When apps and their functionality are routinely built into some OS’s or set as defaults; when mobile apps are also available for the desktop and are seamlessly integrated to permit identical functions to be performed on multiple platforms; and when new form factors like Apple MacBook Air and Microsoft Surface blur the lines between mobile and desktop, traditional, static anticompetitive theories are out the window (no pun intended).

Of course, it’s always been possible for new entrants to overcome network effects and scale impediments by a range of means. Microsoft itself has in the past offered to pay app developers to write for its mobile platform. Similarly, it offers inducements to attract users to its Bing search engine and it has devised several creative mechanisms to overcome its claimed scale inferiority in search.

A further irony (and market complication) is that now some of these apps — the ones with network effects of their own — threaten in turn to challenge the reigning mobile operating systems, exactly as Netscape was purported to threaten Microsoft’s OS (and lead to its anticompetitive conduct) back in the day. Facebook, for example, now offers not only its core social media function, but also search, messaging, video calls, mobile payments, photo editing and sharing, and other functionality that compete with many of the core functions built into mobile OS’s.

But the desire by apps like Facebook to expand their networks by being on multiple platforms, and the desire by these platforms to offer popular apps in order to attract users, ensure that Facebook is ubiquitous, even without any antitrust intervention. As Timothy Bresnahan, Joe Orsini and Pai-Ling Yin demonstrate:

(1) The distribution of app attractiveness to consumers is skewed, with a small minority of apps drawing the vast majority of consumer demand. (2) Apps which are highly demanded on one platform tend also to be highly demanded on the other platform. (3) These highly demanded apps have a strong tendency to multihome, writing for both platforms. As a result, the presence or absence of apps offers little reason for consumers to choose a platform. A consumer can choose either platform and have access to the most attractive apps.

Of course, even before Microsoft’s announcement, cross-platform app development was common, and third-party platforms like Xamarin facilitated cross-platform development. As Daniel O’Connor noted last year:

Even if one ecosystem has a majority of the market share, software developers will release versions for different operating systems if it is cheap/easy enough to do so…. As [Torsten] Körber documents [here], building mobile applications is much easier and cheaper than building PC software. Therefore, it is more common for programmers to write programs for multiple OSes…. 73 percent of apps developers design apps for at least two different mobiles OSes, while 62 percent support 3 or more.

Whether Microsoft’s interoperability efforts prove to be “perfect” or not (and some commenters are skeptical), they seem destined to at least further decrease the cost of cross-platform development, thus reducing any “application barrier to entry” that might impede Microsoft’s ability to compete with its much larger rivals.

Moreover, one of the most interesting things about the announcement is that it will enable Android and iOS apps to run not only on Windows phones, but also on Windows computers. Some 1.3 billion PCs run Windows. Forget Windows’ tiny share of mobile phone OS’s; that massive potential PC market (of which Microsoft still has 91 percent) presents an enormous ready-made market for mobile app developers that won’t be ignored.

It also points up the increasing absurdity of compartmentalizing these markets for antitrust purposes. As the relevant distinctions between mobile and desktop markets break down, the idea of Google (or any other company) “leveraging its dominance” in one market to monopolize a “neighboring” or “related” market is increasingly unsustainable. As I wrote earlier this week:

Mobile and social media have transformed search, too…. This revolution has migrated to the computer, which has itself become “app-ified.” Now there are desktop apps and browser extensions that take users directly to Google competitors such as Kayak, eBay and Amazon, or that pull and present information from these sites.

In the end, intentionally or not, Microsoft is (again) undermining its own case. And it is doing so by innovating and competing — those Schumpeterian concepts that were always destined to undermine antitrust cases in the high-tech sector.

If we’re lucky, Microsoft’s new initiatives are the leading edge of a sea change for Microsoft — a different and welcome mindset built on competing in the marketplace rather than at regulators’ doors.

Recent years have seen an increasing interest in incorporating privacy into antitrust analysis. The FTC and regulators in Europe have rejected these calls so far, but certain scholars and activists continue their attempts to breathe life into this novel concept. Elsewhere we have written at length on the scholarship addressing the issue and found the case for incorporation wanting. Among the errors proponents make is a persistent (and woefully unsubstantiated) assertion that online data can amount to a barrier to entry, insulating incumbent services from competition and ensuring that only the largest providers thrive. This data barrier to entry, it is alleged, can then allow firms with monopoly power to harm consumers, either directly through “bad acts” like price discrimination, or indirectly by raising the costs of advertising, which then get passed on to consumers.

A case in point was on display at last week’s George Mason Law & Economics Center Briefing on Big Data, Privacy, and Antitrust. Building on their growing body of advocacy work, Nathan Newman and Allen Grunes argued that this hypothesized data barrier to entry actually exists, and that it prevents effective competition from search engines and social networks that are interested in offering services with heightened privacy protections.

According to Newman and Grunes, network effects and economies of scale ensure that dominant companies in search and social networking (they specifically named Google and Facebook — implying that they are in separate markets) operate without effective competition. This results in antitrust harm, they assert, because it precludes competition on the non-price factor of privacy protection.

In other words, according to Newman and Grunes, even though Google and Facebook offer their services for a price of $0 and constantly innovate and upgrade their products, consumers are nevertheless harmed because the business models of less-privacy-invasive alternatives are foreclosed by insufficient access to data (an almost self-contradicting and silly narrative for many reasons, including the big question of whether consumers prefer greater privacy protection to free stuff). Without access to, and use of, copious amounts of data, Newman and Grunes argue, the algorithms underlying search and targeted advertising are necessarily less effective and thus the search product without such access is less useful to consumers. And even more importantly to Newman, the value to advertisers of the resulting consumer profiles is diminished.

Newman has put forth a number of other possible antitrust harms that purportedly result from this alleged data barrier to entry, as well. Among these is the increased cost of advertising to those who wish to reach consumers. Presumably this would harm end users who have to pay more for goods and services because the costs of advertising are passed on to them. On top of that, Newman argues that ad networks inherently facilitate price discrimination, an outcome that he asserts amounts to antitrust harm.

FTC Commissioner Maureen Ohlhausen (who also spoke at the George Mason event) recently made the case that antitrust law is not well-suited to handling privacy problems. She argues — convincingly — that competition policy and consumer protection should be kept separate to preserve doctrinal stability. Antitrust law deals with harms to competition through the lens of economic analysis. Consumer protection law is tailored to deal with broader societal harms and aims at protecting the “sanctity” of consumer transactions. Antitrust law can, in theory, deal with privacy as a non-price factor of competition, but this is an uneasy fit because of the difficulties of balancing quality over two dimensions: Privacy may be something some consumers want, but others would prefer a better algorithm for search and social networks, and targeted ads with free content, for instance.

In fact, there is general agreement with Commissioner Ohlhausen on her basic points, even among critics like Newman and Grunes. But, as mentioned above, views diverge over whether there are some privacy harms that should nevertheless factor into competition analysis, and on whether there is in fact  a data barrier to entry that makes these harms possible.

As we explain below, however, the notion of data as an antitrust-relevant barrier to entry is simply a myth. And, because all of the theories of “privacy as an antitrust harm” are essentially predicated on this, they are meritless.

First, data is useful to all industries — this is not some new phenomenon particular to online companies

It bears repeating (because critics seem to forget it in their rush to embrace “online exceptionalism”) that offline retailers also receive substantial benefit from, and greatly benefit consumers by, knowing more about what consumers want and when they want it. Through devices like coupons and loyalty cards (to say nothing of targeted mailing lists and the age-old practice of data mining check-out receipts), brick-and-mortar retailers can track purchase data and better serve consumers. Not only do consumers receive better deals for using them, but retailers know what products to stock and advertise and when and on what products to run sales. For instance:

  • Macy’s analyzes tens of millions of terabytes of data every day to gain insights from social media and store transactions. Over the past three years, the use of big data analytics alone has helped Macy’s boost its revenue growth by 4 percent annually.
  • Following its acquisition of Kosmix in 2011, Walmart established @WalmartLabs, which created its own product search engine for online shoppers. In the first year of its use alone, the number of customers buying a product on Walmart.com after researching a purchase increased by 20 percent. According to Ron Bensen, the vice president of engineering at @WalmartLabs, the combination of in-store and online data could give brick-and-mortar retailers like Walmart an advantage over strictly online stores.
  • Panera and a whole host of restaurants, grocery stores, drug stores and retailers use loyalty cards to advertise and learn about consumer preferences.

And of course there is a host of others uses for data, as well, including security, fraud prevention, product optimization, risk reduction to the insured, knowing what content is most interesting to readers, etc. The importance of data stretches far beyond the online world, and far beyond mere retail uses more generally. To describe even online giants like Amazon, Apple, Microsoft, Facebook and Google as having a monopoly on data is silly.

Second, it’s not the amount of data that leads to success but building a better mousetrap

The value of knowing someone’s birthday, for example, is not in that tidbit itself, but in the fact that you know this is a good day to give that person a present. Most of the data that supports the advertising networks underlying the Internet ecosphere is of this sort: Information is important to companies because of the value that can be drawn from it, not for the inherent value of the data itself. Companies don’t collect information about you to stalk you, but to better provide goods and services to you.

Moreover, data itself is not only less important than what can be drawn from it, but data is also less important than the underlying product it informs. For instance, Snapchat created a challenger to  Facebook so successfully (and in such short time) that Facebook attempted to buy it for $3 billion (Google offered $4 billion). But Facebook’s interest in Snapchat wasn’t about its data. Instead, Snapchat was valuable — and a competitive challenge to Facebook — because it cleverly incorporated the (apparently novel) insight that many people wanted to share information in a more private way.

Relatedly, Twitter, Instagram, LinkedIn, Yelp, Pinterest (and Facebook itself) all started with little (or no) data and they have had a lot of success. Meanwhile, despite its supposed data advantages, Google’s attempts at social networking — Google+ — have never caught up to Facebook in terms of popularity to users (and thus not to advertisers either). And scrappy social network Ello is starting to build a significant base without data collection for advertising at all.

At the same time it’s simply not the case that the alleged data giants — the ones supposedly insulating themselves behind data barriers to entry — actually have the type of data most relevant to startups anyway. As Andres Lerner has argued, if you wanted to start a travel business, the data from Kayak or Priceline would be far more relevant. Or if you wanted to start a ride-sharing business, data from cab companies would be more useful than the broad, market-cross-cutting profiles Google and Facebook have. Consider companies like Uber, Lyft and Sidecar that had no customer data when they began to challenge established cab companies that did possess such data. If data were really so significant, they could never have competed successfully. But Uber, Lyft and Sidecar have been able to effectively compete because they built products that users wanted to use — they came up with an idea for a better mousetrap.The data they have accrued came after they innovated, entered the market and mounted their successful challenges — not before.

In reality, those who complain about data facilitating unassailable competitive advantages have it exactly backwards. Companies need to innovate to attract consumer data, otherwise consumers will switch to competitors (including both new entrants and established incumbents). As a result, the desire to make use of more and better data drives competitive innovation, with manifestly impressive results: The continued explosion of new products, services and other apps is evidence that data is not a bottleneck to competition but a spur to drive it.

Third, competition online is one click or thumb swipe away; that is, barriers to entry and switching costs are low

Somehow, in the face of alleged data barriers to entry, competition online continues to soar, with newcomers constantly emerging and triumphing. This suggests that the barriers to entry are not so high as to prevent robust competition.

Again, despite the supposed data-based monopolies of Facebook, Google, Amazon, Apple and others, there exist powerful competitors in the marketplaces they compete in:

  • If consumers want to make a purchase, they are more likely to do their research on Amazon than Google.
  • Google flight search has failed to seriously challenge — let alone displace —  its competitors, as critics feared. Kayak, Expedia and the like remain the most prominent travel search sites — despite Google having literally purchased ITA’s trove of flight data and data-processing acumen.
  • People looking for local reviews go to Yelp and TripAdvisor (and, increasingly, Facebook) as often as Google.
  • Pinterest, one of the most highly valued startups today, is now a serious challenger to traditional search engines when people want to discover new products.
  • With its recent acquisition of the shopping search engine, TheFind, and test-run of a “buy” button, Facebook is also gearing up to become a major competitor in the realm of e-commerce, challenging Amazon.
  • Likewise, Amazon recently launched its own ad network, “Amazon Sponsored Links,” to challenge other advertising players.

Even assuming for the sake of argument that data creates a barrier to entry, there is little evidence that consumers cannot easily switch to a competitor. While there are sometimes network effects online, like with social networking, history still shows that people will switch. MySpace was considered a dominant network until it made a series of bad business decisions and everyone ended up on Facebook instead. Similarly, Internet users can and do use Bing, DuckDuckGo, Yahoo, and a plethora of more specialized search engines on top of and instead of Google. And don’t forget that Google itself was once an upstart new entrant that replaced once-household names like Yahoo and AltaVista.

Fourth, access to data is not exclusive

Critics like Newman have compared Google to Standard Oil and argued that government authorities need to step in to limit Google’s control over data. But to say data is like oil is a complete misnomer. If Exxon drills and extracts oil from the ground, that oil is no longer available to BP. Data is not finite in the same way. To use an earlier example, Google knowing my birthday doesn’t limit the ability of Facebook to know my birthday, as well. While databases may be proprietary, the underlying data is not. And what matters more than the data itself is how well it is analyzed.

This is especially important when discussing data online, where multi-homing is ubiquitous, meaning many competitors end up voluntarily sharing access to data. For instance, I can use the friend-finder feature on WordPress to find Facebook friends, Google connections, and people I’m following on Twitter who also use the site for blogging. Using this feature allows WordPress to access your contact list on these major online players.

Friend-Finder

Further, it is not apparent that Google’s competitors have less data available to them. Microsoft, for instance, has admitted that it may actually have more data. And, importantly for this discussion, Microsoft may have actually garnered some of its data for Bing from Google.

If Google has a high cost per click, then perhaps it’s because it is worth it to advertisers: There are more eyes on Google because of its superior search product. Contra Newman and Grunes, Google may just be more popular for consumers and advertisers alike because the algorithm makes it more useful, not because it has more data than everyone else.

Fifth, the data barrier to entry argument does not have workable antitrust remedies

The misguided logic of data barrier to entry arguments leaves a lot of questions unanswered. Perhaps most important among these is the question of remedies. What remedy would apply to a company found guilty of leveraging its market power with data?

It’s actually quite difficult to conceive of a practical means for a competition authority to craft remedies that would address the stated concerns without imposing enormous social costs. In the unilateral conduct context, the most obvious remedy would involve the forced sharing of data.

On the one hand, as we’ve noted, it’s not clear this would actually accomplish much. If competitors can’t actually make good use of data, simply having more of it isn’t going to change things. At the same time, such a result would reduce the incentive to build data networks to begin with. In their startup stage, companies like Uber and Facebook required several months and hundreds of thousands, if not millions, of dollars to design and develop just the first iteration of the products consumers love. Would any of them have done it if they had to share their insights? In fact, it may well be that access to these free insights is what competitors actually want; it’s not the data they’re lacking, but the vision or engineering acumen to use it.

Other remedies limiting collection and use of data are not only outside of the normal scope of antitrust remedies, they would also involve extremely costly court supervision and may entail problematic “collisions between new technologies and privacy rights,” as the last year’s White House Report on Big Data and Privacy put it.

It is equally unclear what an antitrust enforcer could do in the merger context. As Commissioner Ohlhausen has argued, blocking specific transactions does not necessarily stop data transfer or promote privacy interests. Parties could simply house data in a standalone entity and enter into licensing arrangements. And conditioning transactions with forced data sharing requirements would lead to the same problems described above.

If antitrust doesn’t provide a remedy, then it is not clear why it should apply at all. The absence of workable remedies is in fact a strong indication that data and privacy issues are not suitable for antitrust. Instead, such concerns would be better dealt with under consumer protection law or by targeted legislation.

The Wall Street Journal reported yesterday that the FTC Bureau of Competition staff report to the commissioners in the Google antitrust investigation recommended that the Commission approve an antitrust suit against the company.

While this is excellent fodder for a few hours of Twitter hysteria, it takes more than 140 characters to delve into the nuances of a 20-month federal investigation. And the bottom line is, frankly, pretty ho-hum.

As I said recently,

One of life’s unfortunate certainties, as predictable as death and taxes, is this: regulators regulate.

The Bureau of Competition staff is made up of professional lawyers — many of them litigators, whose existence is predicated on there being actual, you know, litigation. If you believe in human fallibility at all, you have to expect that, when they err, FTC staff errs on the side of too much, rather than too little, enforcement.

So is it shocking that the FTC staff might recommend that the Commission undertake what would undoubtedly have been one of the agency’s most significant antitrust cases? Hardly.

Nor is it surprising that the commissioners might not always agree with staff. In fact, staff recommendations are ignored all the time, for better or worse. Here are just a few examples: R.J Reynolds/Brown & Williamson merger, POM Wonderful , Home Shopping Network/QVC merger, cigarette advertising. No doubt there are many, many more.

Regardless, it also bears pointing out that the staff did not recommend the FTC bring suit on the central issue of search bias “because of the strong procompetitive justifications Google has set forth”:

Complainants allege that Google’s conduct is anticompetitive because if forecloses alternative search platforms that might operate to constrain Google’s dominance in search and search advertising. Although it is a close call, we do not recommend that the Commission issue a complaint against Google for this conduct.

But this caveat is enormous. To report this as the FTC staff recommending a case is seriously misleading. Here they are forbearing from bringing 99% of the case against Google, and recommending suit on the marginal 1% issues. It would be more accurate to say, “FTC staff recommends no case against Google, except on a couple of minor issues which will be immediately settled.”

And in fact it was on just these minor issues that Google agreed to voluntary commitments to curtail some conduct when the FTC announced it was not bringing suit against the company.

The Wall Street Journal quotes some other language from the staff report bolstering the conclusion that this is a complex market, the conduct at issue was ambiguous (at worst), and supporting the central recommendation not to sue:

We are faced with a set of facts that can most plausibly be accounted for by a narrative of mixed motives: one in which Google’s course of conduct was premised on its desire to innovate and to produce a high quality search product in the face of competition, blended with the desire to direct users to its own vertical offerings (instead of those of rivals) so as to increase its own revenues. Indeed, the evidence paints a complex portrait of a company working toward an overall goal of maintaining its market share by providing the best user experience, while simultaneously engaging in tactics that resulted in harm to many vertical competitors, and likely helped to entrench Google’s monopoly power over search and search advertising.

On a global level, the record will permit Google to show substantial innovation, intense competition from Microsoft and others, and speculative long-run harm.

This is exactly when you want antitrust enforcers to forbear. Predicting anticompetitive effects is difficult, and conduct that could be problematic is simultaneously potentially vigorous competition.

That the staff concluded that some of what Google was doing “harmed competitors” isn’t surprising — there were lots of competitors parading through the FTC on a daily basis claiming Google harmed them. But antitrust is about protecting consumers, not competitors. Far more important is the staff finding of “substantial innovation, intense competition from Microsoft and others, and speculative long-run harm.”

Indeed, the combination of “substantial innovation,” “intense competition from Microsoft and others,” and “Google’s strong procompetitive justifications” suggests a well-functioning market. It similarly suggests an antitrust case that the FTC would likely have lost. The FTC’s litigators should probably be grateful that the commissioners had the good sense to vote to close the investigation.

Meanwhile, the Wall Street Journal also reports that the FTC’s Bureau of Economics simultaneously recommended that the Commission not bring suit at all against Google. It is not uncommon for the lawyers and the economists at the Commission to disagree. And as a general (though not inviolable) rule, we should be happy when the Commissioners side with the economists.

While the press, professional Google critics, and the company’s competitors may want to make this sound like a big deal, the actual facts of the case and a pretty simple error-cost analysis suggests that not bringing a case was the correct course.

Microsoft and its allies (the Microsoft-funded trade organization FairSearch and the prolific Google critic Ben Edelman) have been highly critical of Google’s use of “secret” contracts to license its proprietary suite of mobile apps, Google Mobile Services, to device manufacturers.

I’ve written about this at length before. As I said previously,

In order to argue that Google has an iron grip on Android, Edelman’s analysis relies heavily on ”secret” Google licensing agreements — “MADAs” (Mobile Application Distribution Agreements) — trotted out with such fanfare one might think it was the first time two companies ever had a written contract (or tried to keep it confidential).

For Edelman, these agreements “suppress competition” with “no plausible pro-consumer benefits.”

Microsoft (via another of its front groups, ICOMP) responded in predictable fashion.

While the hysteria over private, mutually beneficial contracts negotiated between sophisticated corporations was always patently absurd (who ever heard of sensitive commercial contracts that weren’t confidential?), Edelman’s claim that the Google MADAs operate to “suppress competition” with “no plausible pro-consumer benefits” was the subject of my previous post.

I won’t rehash all of those arguments here, but rather point to another indication that such contract terms are not anticompetitive: The recent revelation that they are used by others in the same industry — including, we’ve learned (to no one’s surprise), Microsoft.

Much like the release of Google’s MADAs in an unrelated lawsuit, the ongoing patent licensing contract dispute between Microsoft and Samsung has obliged the companies to release their own agreements. As it happens, they are at least as restrictive as the Google agreements criticized by Edelman — and, in at least one way, even more so.

Some quick background: As I said in my previous post, it is no secret that equipment manufacturers have the option to license a free set of Google apps (Google Mobile Services) and set Google as the default search engine. However, Google allows OEMs to preinstall other competing search engines as they see fit. Indeed, no matter which applications come pre-installed, the user can easily download Yahoo!, Microsoft’s Bing, Yandex, Naver, DuckDuckGo and other search engines for free from the Google Play Store.

But Microsoft has sought to impose even-more stringent constraints on its device partners. One of the agreements disclosed in the Microsoft-Samsung contract litigation, the “Microsoft-Samsung Business Collaboration Agreement,” requires Samsung to set Bing as the search default for all Windows phones and precludes Samsung from pre-installing any other search applications on Windows-based phones. Samsung must configure all of its Windows Phones to use Microsoft Search Services as the

default Web Search  . . . in all instances on such properties where Web Search can be launched or a Query submitted directly by a user (including by voice command) or automatically (including based on location or context).

Interestingly, the agreement also requires Samsung to install Microsoft Search Services as a non-default search option on all of Samsung’s non-Microsoft Android devices (to the extent doing so does not conflict with other contracts).

Of course, the Microsoft-Samsung contract is expressly intended to remain secret: Its terms are declared to be “Confidential Information,” prohibiting Samsung from making “any public statement regarding the specific terms of [the] Agreement” without Microsoft’s consent.

Meanwhile, the accompanying Patent License Agreement provides that

all terms and conditions in this Agreement, including the payment amount [and the] specific terms and conditions in this Agreement (including, without limitation, the amount of any fees and any other amounts payable to Microsoft under this Agreement) are confidential and shall not be disclosed by either Party.

In addition to the confidentiality terms spelled out in these two documents, there is a separate Non-Disclosure Agreement—to further dispel any modicum of doubt on that score. Perhaps this is why Edelman was unaware of the ubiquity of such terms (and their confidentiality) when he issued his indictment of the Google agreements but neglected to mention Microsoft’s own.

In light of these revelations, Edelman’s scathing contempt for the “secrecy” of Google’s MADAs seems especially disingenuous:

MADA secrecy advances Google’s strategic objectives. By keeping MADA restrictions confidential and little-known, Google can suppress the competitive response…Relatedly, MADA secrecy helps prevent standard market forces from disciplining Google’s restriction. Suppose consumers understood that Google uses tying and full-line-forcing to prevent manufacturers from offering phones with alternative apps, which could drive down phone prices. Then consumers would be angry and would likely make their complaints known both to regulators and to phone manufacturers. Instead, Google makes the ubiquitous presence of Google apps and the virtual absence of competitors look like a market outcome, falsely suggesting that no one actually wants to have or distribute competing apps.

If, as Edelman claims, Google’s objectionable contract terms “serve both to help Google expand into areas where competition could otherwise occur, and to prevent competitors from gaining traction,” then what are the very same sorts of terms doing in Microsoft’s contracts with Samsung? The revelation that Microsoft employs contracts similar to — and similarly confidential to — Google’s highlights the hypocrisy of claims that such contracts serve anticompetitive aims.

In fact, as I discussed in my previous post, there are several pro-competitive justifications for such agreements, whether undertaken by a market leader or a newer entrant intent on catching up. Most obviously, such contracts help to ensure that consumers receive the user experience they demand on devices manufactured by third parties. But more to the point, the fact that such arrangements permeate the market and are adopted by both large and small competitors is strong indication that such terms are pro-competitive.

At the very least, they absolutely demonstrate that such practices do not constitute prima facie evidence of the abuse of market power.

[Reminder: See the “Disclosures” page above. ICLE has received financial support from Google in the past, and I formerly worked at Microsoft. Of course, the views here are my own, although I encourage everyone to agree with them.]

Microsoft wants you to believe that Google’s business practices stifle competition and harm consumers. Again.

The latest volley in its tiresome and ironic campaign to bludgeon Google with the same regulatory club once used against Microsoft itself is the company’s effort to foment an Android-related antitrust case in Europe.

In a recent polemicMicrosoft consultant (and business school professor) Ben Edelman denounces Google for requiring that, if device manufacturers want to pre-install key Google apps on Android devices, they “must install all the apps Google specifies, with the prominence Google requires, including setting these apps as defaults where Google instructs.” Edelman trots out gasp-worthy “secret” licensing agreements that he claims support his allegation (more on this later).

Similarly, a recent Wall Street Journal article, “Android’s ‘Open’ System Has Limits,” cites Edelman’s claim that limits on the licensing of Google’s proprietary apps mean that the Android operating system isn’t truly open source and comes with “strings attached.”

In fact, along with the Microsoft-funded trade organization FairSearch, Edelman has gone so far as to charge that this “tying” constitutes an antitrust violation. It is this claim that Microsoft and a network of proxies brought to the Commission when their efforts to manufacture a search-neutrality-based competition case against Google failed.

But before getting too caught up in the latest round of anti-Google hysteria, it’s worth noting that the Federal Trade Commission has already reviewed these claims. After a thorough, two-year inquiry, the FTC found the antitrust arguments against Google to be without merit. The South Korea Fair Trade Commission conducted its own two year investigation into Google’s Android business practices and dismissed the claims before it as meritless, as well.

Taking on Edelman and FairSearch with an exhaustive scholarly analysis, German law professor Torsten Koerber recently assessed the nature of competition among mobile operating systems and concluded that:

(T)he (EU) Fairsearch complaint ultimately does not aim to protect competition or consumers, as it pretends to. It rather strives to shelter Microsoft from competition by abusing competition law to attack Google’s business model and subvert competition.

It’s time to take a step back and consider the real issues at play.

In order to argue that Google has an iron grip on Android, Edelman’s analysis relies heavily on ”secret” Google licensing agreements — “MADAs” (Mobile Application Distribution Agreements) — trotted out with such fanfare one might think it was the first time two companies ever had a written contract (or tried to keep it confidential).

For Edelman, these agreements “suppress competition” with “no plausible pro-consumer benefits.” He writes, “I see no way to reconcile the MADA restrictions with [Android openness].”

Conveniently, however, Edelman neglects to cite to Section 2.6 of the MADA:

The parties will create an open environment for the Devices by making all Android Products and Android Application Programming Interfaces available and open on the Devices and will take no action to limit or restrict the Android platform.

Professor Korber’s analysis provides a straight-forward explanation of the relationship between Android and its OEM licensees:

Google offers Android to OEMs on a royalty-free basis. The licensees are free to download, distribute and even modify the Android code as they like. OEMs can create mobile devices that run “pure” Android…or they can apply their own user interfaces (IO) and thereby hide most of the underlying Android system (e.g. Samsung’s “TouchWiz” or HTC’s “Sense”). OEMs make ample use of this option.

The truth is that the Android operating system remains, as ever, definitively open source — but Android’s openness isn’t really what the fuss is about. In this case, the confusion (or obfuscation) stems from the casual confounding of Google Apps with the Android Operating System. As we’ll see, they aren’t the same thing.

Consider Amazon, which pre-loads no Google applications at all on its Kindle Fire and Fire Phone. Amazon’s version of Android uses Microsoft’s Bing as the default search engineNokia provides mapping services, and the app store is Amazon’s own.

Still, Microsoft’s apologists continue to claim that Android licensees can’t choose to opt out of Google’s applications suite — even though, according to a new report from ABI Research, 20 percent of smartphones shipped between May and July 2014 were based on a “Google-less” version of the Android OS. And that number is consistently increasing: Analysts predict that by 2015, 30 percent of Android phones won’t access Google Services.

It’s true that equipment manufacturers who choose the Android operating system have the option to include the suite of integrated, proprietary Google apps and services licensed (royalty-free) under the name Google Mobile Services (GMS). GMS includes Google Search, Maps, Calendar, YouTube and other apps that together define the “Google Android experience” that users know and love.

But Google Android is far from the only Android experience.

Even if a manufacturer chooses to license Google’s apps suite, Google’s terms are not exclusive. Handset makers are free to install competing applications, including other search engines, map applications or app stores.

Although Google requires that Google Search be made easily accessible (hardly a bad thing for consumers, as it is Google Search that finances the development and maintenance of all of the other (free) apps from which Google otherwise earns little to no revenue), OEMs and users alike can (and do) easily install and access other search engines in numerous ways. As Professor Korber notes:

The standard MADA does not entail any exclusivity for Google Search nor does it mandate a search default for the web browser.

Regardless, integrating key Google apps (like Google Search and YouTube) with other apps the company offers (like Gmail and Google+) is an antitrust problem only if it significantly forecloses competitors from these apps’ markets compared to a world without integrated Google apps, and without pro-competitive justification. Neither is true, despite the unsubstantiated claims to the contrary from Edelman, FairSearch and others.

Consumers and developers expect and demand consistency across devices so they know what they’re getting and don’t have to re-learn basic functions or program multiple versions of the same application. Indeed, Apple’s devices are popular in part because Apple’s closed iOS provides a predictable, seamless experience for users and developers.

But making Android competitive with its tightly controlled competitors requires special efforts from Google to maintain a uniform and consistent experience for users. Google has tried to achieve this uniformity by increasingly disentangling its apps from the operating system (the opposite of tying) and giving OEMs the option (but not the requirement) of licensing GMS — a “suite” of technically integrated Google applications (integrated with each other, not the OS).  Devices with these proprietary apps thus ensure that both consumers and developers know what they’re getting.

Unlike Android, Apple prohibits modifications of its operating system by downstream partners and users, and completely controls the pre-installation of apps on iOS devices. It deeply integrates applications into iOS, including Apple Maps, iTunes, Siri, Safari, its App Store and others. Microsoft has copied Apple’s model to a large degree, hard-coding its own applications (including Bing, Windows Store, Skype, Internet Explorer, Bing Maps and Office) into the Windows Phone operating system.

In the service of creating and maintaining a competitive platform, each of these closed OS’s bakes into its operating system significant limitations on which third-party apps can be installed and what they can (and can’t) do. For example, neither platform permits installation of a third-party app store, and neither can be significantly customized. Apple’s iOS also prohibits users from changing default applications — although the soon-to-be released iOS 8 appears to be somewhat more flexible than previous versions.

In addition to pre-installing a raft of their own apps and limiting installation of other apps, both Apple and Microsoft enable greater functionality for their own apps than they do the third-party apps they allow.

For example, Apple doesn’t make available for other browsers (like Google’s Chrome) all the JavaScript functionality that it does for Safari, and it requires other browsers to use iOS Webkit instead of their own web engines. As a result there are things that Chrome can’t do on iOS that Safari and only Safari can do, and Chrome itself is hamstrung in implementing its own software on iOS. This approach has led Mozilla to refuse to offer its popular Firefox browser for iOS devices (while it has no such reluctance about offering it on Android).

On Windows Phone, meanwhile, Bing is integrated into the OS and can’t be removed. Only in markets where Bing is not supported (and with Microsoft’s prior approval) can OEMs change the default search app from Bing. While it was once possible to change the default search engine that opens in Internet Explorer (although never from the hardware search button), the Windows 8.1 Hardware Development Notes, updated July 22, 2014, state:

By default, the only search provider included on the phone is Bing. The search provider used in the browser is always the same as the one launched by the hardware search button.

Both Apple iOS and Windows Phone tightly control the ability to use non-default apps to open intents sent from other apps and, in Windows especially, often these linkages can’t be changed.

As a result of these sorts of policies, maintaining the integrity — and thus the brand — of the platform is (relatively) easy for closed systems. While plenty of browsers are perfectly capable of answering an intent to open a web page, Windows Phone can better ensure a consistent and reliable experience by forcing Internet Explorer to handle the operation.

By comparison, Android, with or without Google Mobile Services, is dramatically more open, more flexible and customizable, and more amenable to third-party competition. Even the APIs that it uses to integrate its apps are open to all developers, ensuring that there is nothing that Google apps are able to do that non-Google apps with the same functionality are prevented from doing.

In other words, not just Gmail, but any email app is permitted to handle requests from any other app to send emails; not just Google Calendar but any calendar app is permitted to handle requests from any other app to accept invitations.

In no small part because of this openness and flexibility, current reports indicate that Android OS runs 85 percent of mobile devices worldwide. But it is OEM giant Samsung, not Google, that dominates the market, with a 65 percent share of all Android devices. Competition is rife, however, especially in emerging markets. In fact, according to one report, “Chinese and Indian vendors accounted for the majority of smartphone shipments for the first time with a 51% share” in 2Q 2014.

As he has not been in the past, Edelman is at least nominally circumspect in his unsubstantiated legal conclusions about Android’s anticompetitive effect:

Applicable antitrust law can be complicated: Some ties yield useful efficiencies, and not all ties reduce welfare.

Given Edelman’s connections to Microsoft and the realities of the market he is discussing, it could hardly be otherwise. If every integration were an antitrust violation, every element of every operating system — including Apple’s iOS as well as every variant of Microsoft’s Windows — should arguably be the subject of a government investigation.

In truth, Google has done nothing more than ensure that its own suite of apps functions on top of Android to maintain what Google sees as seamless interconnectivity, a high-quality experience for users, and consistency for application developers — while still allowing handset manufacturers room to innovate in a way that is impossible on other platforms. This is the very definition of pro-competitive, and ultimately this is what allows the platform as a whole to compete against its far more vertically integrated alternatives.

Which brings us back to Microsoft. On the conclusion of the FTC investigation in January 2013, a GigaOm exposé on the case had this to say:

Critics who say Google is too powerful have nagged the government for years to regulate the company’s search listings. But today the critics came up dry….

The biggest loser is Microsoft, which funded a long-running cloak-and-dagger lobbying campaign to convince the public and government that its arch-enemy had to be regulated….

The FTC is also a loser because it ran a high profile two-year investigation but came up dry.

EU regulators, take note.

Critics of Google have argued that users overvalue Google’s services in relation to the data they give away.  One breath-taking headline asked Who Would Pay $5,000 to Use Google?, suggesting that Google and its advertisers can make as much as $5,000 off of individuals whose data they track. Scholars, such as Nathan Newman, have used this to argue that Google exploits its users through data extraction. But, the question remains: how good of a deal is Google? My contention is that Google’s value to most consumers far surpasses the value supposedly extracted from them in data.

First off, it is unlikely that Google and its advertisers make anywhere close to $5,000 off the average user. Only very high volume online purchasers who consistently click through online ads are likely anywhere close to that valuable. Nonetheless, it is true that Google and its advertisers must be making money, or else Google would be charging users for its services.

PrivacyFix, a popular extension for Google Chrome, calculates your worth to Google based upon the amount of searches you have done. Far from $5,000, my total only comes in at $58.66 (and only $10.74 for Facebook). Now, I might not be the highest volume searcher out there. My colleague, Geoffrey Manne states that he is worth $125.18 on Google (and $10.74 for Facebook). But, I use Google search everyday for work in tech policy, along with Google Docs, Google Calendar, and Gmail (both my private email and work emails)… for FREE!*

The value of all of these services to me, or even just Google search alone, easily surpasses the value of my data attributed to Google. This is likely true for the vast majority of other users, as well. While not a perfect analogue, there are paid specialized search options out there (familiar to lawyers) that do little tracking and are not ad-supported: Westlaw, Lexis, and Bloomberg. But, the price for using these services are considerably higher than zero:

legalsearchcosts

Can you imagine having to pay anywhere near $14 per search on Google? Or a subscription that costs $450 per user per month like some firms pay for Bloomberg? It may be the case that the costs are significantly lower per search for Google than for specialized legal searches (though Google is increasingly used by young lawyers as more cases become available). But, the “price” of viewing a targeted ad is a much lower psychic burden for most people than paying even just a few cents per month for an ad-free experience. For instance, consumers almost always choose free apps over the 99 cent alternative without ads.

Maybe the real question about Google is: Great Deal or Greatest Deal?

* Otherwise known as unpriced for those that know there’s no such thing as a free lunch.

On July 24, the Federal Trade Commission issued a modified complaint and consent order in the Google/Motorola case. The FTC responded to the 25 comments on the proposed Order by making several amendments, but the Final Order retains the original order’s essential restrictions on injunctions, as the FTC explains in a letter accompanying the changes. With one important exception, the modifications were primarily minor changes to the required process by which Google/Motorola must negotiate and arbitrate with potential licensees. Although an improvement on the original order, the Complaint and Final Order’s continued focus on the use of injunctions to enforce SEPs presents a serious risk of consumer harm, as I discuss below.

The most significant modification in the new Complaint is the removal of the original UDAP claim. As suggested in my comments on the Order, there is no basis in law for such a claim against Google, and it’s a positive step that the FTC seems to have agreed. Instead, the FTC ended up resting its authority solely upon an Unfair Methods of Competition claim, even though the Commission failed to develop any evidence of harm to competition—as both Commissioner Wright and Commissioner Ohlhausen would (sensibly) require.

Unfortunately, the FTC’s letter offers no additional defense of its assertion of authority, stating only that

[t]he Commission disagrees with commenters who argue that the Commission’s actions in this case are outside of its authority to challenge unfair methods of competition under Section 5 and lack a limiting principle. As reflected in the Commission’s recent statements in Bosch and the Commission’s initial Statement in this matter, this action is well within our Section 5 authority, which both Congress and the Supreme Court have expressly deemed to extend beyond the Sherman Act.

Another problem, as noted by Commissioner Ohlhausen in her dissent from the original order, is that

the consent agreement creates doctrinal confusion. The Order contradicts the decisions of federal courts, standard-setting organizations (“SSOs”), and other stakeholders about the availability of injunctive relief on SEPs and the meaning of concepts like willing licensee and FRAND.

The FTC’s statements in Bosch and this case should not be thought of as law on par with actual court decisions unless we want to allow the FTC to determine the scope of its own authority unilaterally.

This is no small issue. On July 30, the FTC used the Google settlement, along with the settlement in Bosch, as examples of the FTC’s authority in the area of policing SEPs during a hearing on the issue. And as FTC Chairwoman Ramirez noted in response to questions for the record in a different hearing earlier in 2013,

Section 5 of the FTC Act has been developed over time, case-by-case, in the manner of common law. These precedents provide the Commission and the business community with important guidance regarding the appropriate scope and use of the FTC’s Section 5 authority.

But because nearly all of these cases have resulted in consent orders with an administrative agency and have not been adjudicated in court, they aren’t, in fact, developed “in the manner of common law.” Moreover, settlements aren’t binding on anyone except the parties to the settlement. Nevertheless, the FTC has pointed to these sorts of settlements (and congressional testimony summarizing them) as sufficient guidance to industry on the scope of its Section 5 authority. But as we noted in our amicus brief in the Wyndham litigation (in which the FTC makes this claim in the context of its “unfair or deceptive acts or practices” authority):

Settlements (and testimony summarizing them) do not in any way constrain the FTC’s subsequent enforcement decisions; they cannot alone be the basis by which the FTC provides guidance on its unfairness authority because, unlike published guidelines, they do not purport to lay out general enforcement principles and are not recognized as doing so by courts and the business community.

Beyond this more general problem, the Google Final Order retains its own, substantive problem: considerable constraints upon injunctions. The problem with these restraints are twofold: (1) Injunctions are very important to an efficient negotiation process, as recognized by the FTC itself; and (2) if patent holders may no longer pursue injunctions consistently with antitrust law, one would expect a reduction in consumer welfare.

In its 2011 Report on the “IP Marketplace,” the FTC acknowledged the important role of injunctions in preserving the value of patents and in encouraging efficient private negotiation.

Second, the credible threat of an injunction deters infringement in the first place. This results from the serious consequences of an injunction for an infringer, including the loss of sunk investment. Third, a predictable injunction threat will promote licensing by the parties. Private contracting is generally preferable to a compulsory licensing regime because the parties will have better information about the appropriate terms of a license than would a court, and more flexibility in fashioning efficient agreements. But denying an injunction every time an infringer’s switching costs exceed the economic value of the invention would dramatically undermine the ability of a patent to deter infringement and encourage innovation. For this reason, courts should grant injunctions in the majority of cases.

Building on insights from Commissioner Wright and Professor Kobayashi, I argued in my comments that injunctions create conditions that

increase innovation, the willingness to license generally and the willingness to enter into FRAND commitments in particular–all to the likely benefit of consumer welfare.

Monopoly power granted by IP law encourages innovation because it incentivizes creativity through expected profits. If the FTC interprets its UMC authority in a way that constrains the ability of patent holders to effectively police their patent rights, then less innovation would be expected–to the detriment of consumers as well as businesses.

And this is precisely what has happened. Innovative technology companies are responding to the current SEP enforcement environment exactly as we would expect them to—by avoiding the otherwise-consumer-welfare enhancing standardization process entirely.

Thus, for example, at a recent event sponsored by Global Competition Review (gated), representatives from Nokia, Ericsson, Siemens and Qualcomm made no bones about the problems they see and where they’re headed if they persist:

[Jenni Lukander, global head of competition law at Nokia] said the problem of “free-riding”, whereby technology companies adopt standard essential patents (SEPs) without complying with fair, reasonable and non-discriminatory (FRAND) licensing terms was a “far bigger problem” than patent holders pursuing injunctive relief. She said this behaviour was “unsustainable”, as it discouraged innovation and jeopardised standardisation.

Because of the current atmosphere, Lukander said, Nokia has stepped back from the standardisation process, electing either not to join certain standard-setting organisations (SSOs) or not to contribute certain technologies to these organisations.

The fact that every licence negotiation takes places “under the threat of injunction litigation” is not a sign of failure, said Lukander, but an indicator of the system working “as it was designed to work”.

This, said [Dan Hermele, director of IP rights and licensing for Qualcomm Europe], amounted to “reverse hold-up”. “The licensor is pressured to accept less than reasonable licensing terms due to the threat of unbalanced regulatory intervention,” he said, adding that the trend was moving to an “infringe and litigate model”, which threatened to harm innovators, particularly small and medium-sized businesses, “for whom IPR is their life blood”.

Beat Weibel, chief IP counsel at Siemens, said…innovation can only be beneficial if it occurs within a “safe and strong IP system,” he said, where a “willing licensee is favoured over a non-willing licensee” and the enforcer is not a “toothless tiger”.

It remains to be seen if the costs to consumers from firms curtailing their investments in R&D or withholding their patents from the standard-setting process will outweigh the costs (yes, some costs do exist; the patent system is not frictionless and it is far from perfect, of course) from the “over”-enforcement of SEPs lamented by critics. But what is clear is that these costs can’t be ignored. Reverse hold-up can’t be wished away, and there is a serious risk that the harm likely to be caused by further eroding the enforceability of SEPs by means of injunctions will significantly outweigh whatever benefits it may also confer.

Meanwhile, stay tuned for tomorrow’s TOTM blog symposium on “Regulating the Regulators–Guidance for the FTC’s Section 5 Unfair Methods of Competition Authority” for much more discussion on this issue.

I filed comments today on the FTC’s proposed Settlement Order in the Google standards-essential patents (SEPs) antitrust case. The Order imposes limits on the allowable process for enforcing FRAND licensing of SEPs, an area of great complexity and vigorous debate among industry, patent experts and global standards bodies. The most notable aspect of the order is its treatment of the process by which Google and, if extended, patent holders generally may attempt to enforce their FRAND-obligated SEPs through injunctions.

Unfortunately, the FTC’s enforcement action in this matter had no proper grounding in antitrust law. Under Supreme Court doctrine there is no basis for liability under Section 2 of the Sherman Act because the exercise of lawfully acquired monopoly power is not actionable under the antitrust laws. Apparently recognizing this, the Commission instead brought this action under Section 5 of the FTC Act. But Section 5 provides no basis for liability either, where, as here, there is no evidence of consumer harm. The Commission’s Order continues its recent trend of expanding its Section 5 authority without judicial oversight, charting a dangerously unprincipled course.

The standard-setting organizations (SSOs) that govern the SEPs in this case have no policies prohibiting the use of injunctions. Even if an SSO agreement (or a specific license) did disallow them, seeking an injunction would be a simple breach of contract. Reading a limitation on injunctions into the SSO agreement is in severe tension with the normal rules of contract interpretation. To turn Motorola’s effort to receive a reasonable royalty for its patents by means of an injunction into an antitrust problem seems directly to undermine the standard-setting process. It also seems to have no basis in law.

My comments rely heavily on Bruce Kobayashi and Josh Wright’s article, Federalism, Substantive Preemption, and Limits on Antitrust: An Application to Patent Holdup, published in Competition Policy and Patent Law Under Uncertainty: Regulating Innovation (Manne & Wright, eds.).

For previous posts on the topic see, e.g.:

The suit against Google was to be this century’s first major antitrust case and a model for high technology industries in the future. Now that we have passed the investigative hangover, the mood has turned reflective, and antitrust experts are now looking to place this case into its proper context. If it were brought, would the case have been on sure legal footing? Was this a prudent move for consumers? Was the FTC’s disposition of the case appropriate?

Join me this Friday, January 11, 2013 at 12:00 pm – 1:45 pm ET for an ABA Antitrust Section webinar to explore these questions, among others. I will be sharing the panel with an impressive group:

Hill B. Welford will moderate. Registration is open to everyone here and the outlay is zero. Remember — these events are not technically free because you have to give up some of your time, but I would be delighted if you did.

The Federal Trade Commission yesterday closed its investigation of Google’s search business (see my comment here) without taking action. The FTC did, however, enter into a settlement with Google over the licensing of Motorola Mobility’s standards-essential patents (SEPs). The FTC intends that agreement to impose some limits on an area of great complexity and vigorous debate among industry, patent experts and global standards bodies: The allowable process for enforcing FRAND (fair, reasonable and non-discriminatory) licensing of SEPs, particularly the use of injunctions by patent holders to do so. According to Chairman Leibowitz, “[t]oday’s landmark enforcement action will set a template for resolution of SEP licensing disputes across many industries.” That effort may or may not be successful. It also may be misguided.

In general, a FRAND commitment incentivizes innovation by allowing a SEP owner to recoup its investments and the value of its technology through licensing, while, at the same, promoting competition and avoiding patent holdup by ensuring that licensing agreements are reasonable. When the process works, and patent holders negotiate licensing rights in good faith, patents are licensed, industries advance and consumers benefit.

FRAND terms are inherently indeterminate and flexible—indeed, they often apply precisely in situations where licensors and licensees need flexibility because each licensing circumstance is nuanced and a one-size-fits-all approach isn’t workable. Superimposing process restraints from above isn’t necessarily the best thing in dealing with what amounts to a contract dispute. But few can doubt the benefits of greater clarity in this process; the question is whether the FTC’s particular approach to the problem sacrifices too much in exchange for such clarity.

The crux of the issue in the Google consent decree—and the most controversial aspect of SEP licensing negotiations—is the role of injunctions. The consent decree requires that, before Google sues to enjoin a manufacturer from using its SEPs without a license, the company must follow a prescribed path in licensing negotiations. In particular:

Under this Order, before seeking an injunction on FRAND-encumbered SEPs, Google must: (1) provide a potential licensee with a written offer containing all of the material license terms necessary to license its SEPs, and (2) provide a potential licensee with an offer of binding arbitration to determine the terms of a license that are not agreed upon. Furthermore, if a potential licensee seeks judicial relief for a FRAND determination, Google must not seek an injunction during the pendency of the proceeding, including appeals.

There are a few exceptions, summarized by Commissioner Ohlhausen:

These limitations include when the potential licensee (a) is outside the jurisdiction of the United States; (b) has stated in writing or sworn testimony that it will not license the SEP on any terms [in other words, is not a “willing licensee”]; (c) refuses to enter a license agreement on terms set in a final ruling of a court – which includes any appeals – or binding arbitration; or (d) fails to provide written confirmation to a SEP owner after receipt of a terms letter in the form specified by the Commission. They also include certain instances when a potential licensee has brought its own action seeking injunctive relief on its FRAND-encumbered SEPs.

To the extent that the settlement reinforces what Google (and other licensors) would do anyway, and even to the extent that it imposes nothing more than an obligation to inject a neutral third party into FRAND negotiations to assist the parties in resolving rate disputes, there is little to complain about. Indeed, this is the core of the agreement, and, importantly, it seems to preserve Google’s right to seek injunctions to enforce its patents, subject to the agreement’s process requirements.

Industry participants and standard-setting organizations have supported injunctions, and the seeking and obtaining of injunctions against infringers is not in conflict with SEP patentees’ obligations. Even the FTC, in its public comments, has stated that patent owners should be able to obtain injunctions on SEPs when an infringer has rejected a reasonable license offer. Thus, the long-anticipated announcement by the FTC in the Google case may help to provide some clarity to the future negotiation of SEP licenses, the possible use of binding arbitration, and the conditions under which seeking injunctive relief will be permissible (as an antitrust matter).

Nevertheless, U.S. regulators, including the FTC, have sometimes opined that seeking injunctions on products that infringe SEPs is not in the spirit of FRAND. Everyone seems to agree that more certainty is preferable; the real issue is whether and when injunctions further that aim or not (and whether and when they are anticompetitive).

In October, Renata Hesse, then Acting Assistant Attorney General for the Department of Justice’s Antitrust Division, remarked during a patent roundtable that

[I]t would seem appropriate to limit a patent holder’s right to seek an injunction to situations where the standards implementer is unwilling to have a neutral third-party determine the appropriate F/RAND terms or is unwilling to accept the F/RAND terms approved by such a third-party.

In its own 2011 Report on the “IP Marketplace,” the FTC acknowledged the fluidity and ambiguity surrounding the meaning of “reasonable” licensing terms and the problems of patent enforcement. While noting that injunctions may confer a costly “hold-up” power on licensors that wield them, the FTC nevertheless acknowledged the important role of injunctions in preserving the value of patents and in encouraging efficient private negotiation:

Three characteristics of injunctions that affect innovation support generally granting an injunction. The first and most fundamental is an injunction’s ability to preserve the exclusivity that provides the foundation of the patent system’s incentives to innovate. Second, the credible threat of an injunction deters infringement in the first place. This results from the serious consequences of an injunction for an infringer, including the loss of sunk investment. Third, a predictable injunction threat will promote licensing by the parties. Private contracting is generally preferable to a compulsory licensing regime because the parties will have better information about the appropriate terms of a license than would a court, and more flexibility in fashioning efficient agreements.

* * *

But denying an injunction every time an infringer’s switching costs exceed the economic value of the invention would dramatically undermine the ability of a patent to deter infringement and encourage innovation. For this reason, courts should grant injunctions in the majority of cases.…

Consistent with this view, the European Commission’s Deputy Director-General for Antitrust, Cecilio Madero Villarejo, recently expressed concern that some technology companies that complain of being denied a license on FRAND terms never truly intend to acquire licenses, but rather “want[] to create conditions for a competition case to be brought.”

But with the Google case, the Commission appears to back away from its seeming support for injunctions, claiming that:

Seeking and threatening injunctions against willing licensees of FRAND-encumbered SEPs undermines the integrity and efficiency of the standard-setting process and decreases the incentives to participate in the process and implement published standards. Such conduct reduces the value of standard setting, as firms will be less likely to rely on the standard-setting process.

Reconciling the FTC’s seemingly disparate views turns on the question of what a “willing licensee” is. And while the Google settlement itself may not magnify the problems surrounding the definition of that term, it doesn’t provide any additional clarity, either.

The problem is that, even in its 2011 Report, in which FTC noted the importance of injunctions, it defines a willing licensee as one who would license at a hypothetical, ex ante rate absent the threat of an injunction and with a different risk profile than an after-the-fact infringer. In other words, the FTC’s definition of willing licensee assumes a willingness to license only at a rate determined when an injunction is not available, and under the unrealistic assumption that the true value of a SEP can be known ex ante. Not surprisingly, then, the Commission finds it easy to declare an injunction invalid when a patentee demands a (higher) royalty rate in an actual negotiation, with actual knowledge of a patent’s value and under threat of an injunction.

As Richard Epstein, Scott Kieff and Dan Spulber discuss in critiquing the FTC’s 2011 Report:

In short, there is no economic basis to equate a manufacturer that is willing to commit to license terms before the adoption and launch of a standard, with one that instead expropriates patent rights at a later time through infringement. The two bear different risks and the late infringer should not pay the same low royalty as a party that sat down at the bargaining table and may actually have contributed to the value of the patent through its early activities. There is no economically meaningful sense in which any royalty set higher than that which a “willing licensee would have paid” at the pre-standardization moment somehow “overcompensates patentees by awarding more than the economic value of the patent.”

* * *

Even with a RAND commitment, the patent owner retains the valuable right to exclude (not merely receive later compensation from) manufacturers who are unwilling to accept reasonable license terms. Indeed, the right to exclude influences how those terms should be calculated, because it is quite likely that prior licensees in at least some areas will pay less if larger numbers of parties are allowed to use the same technology. Those interactive effects are ignored in the FTC calculations.

With this circular logic, all efforts by patentees to negotiate royalty rates after infringement has occurred can be effectively rendered anticompetitive if the patentee uses an injunction or the threat of an injunction against the infringer to secure its reasonable royalty.

The idea behind FRAND is rather simple (reward inventors; protect competition), but the practice of SEP licensing is much more complicated. Circumstances differ from case to case, and, more importantly, so do the parties’ views on what may constitute an appropriate licensing rate under FRAND. As I have written elsewhere, a single company may have very different views on the meaning of FRAND depending on whether it is the licensor or licensee in a given negotiation—and depending on whether it has already implemented a standard or not. As one court looking at the very SEPs at issue in the Google case has pointed out:

[T]he court is mindful that at the time of an initial offer, it is difficult for the offeror to know what would in fact constitute RAND terms for the offeree. Thus, what may appear to be RAND terms from the offeror’s perspective may be rejected out-of-pocket as non-RAND terms by the offeree. Indeed, it would appear that at any point in the negotiation process, the parties may have a genuine disagreement as to what terms and conditions of a license constitute RAND under the parties’ unique circumstances.

The fact that many firms engaged in SEP negotiations are simultaneously and repeatedly both licensors and licensees of patents governed by multiple SSOs further complicates the process—but also helps to ensure that it will reach a conclusion that promotes innovation and ensures that consumers reap the rewards.

In fact, an important issue in assessing the propriety of injunctions is the recognition that, in most cases, firms would rather license their patents and receive royalties than exclude access to their IP and receive no compensation (and incur the costs of protracted litigation, to boot). Importantly, for firms that both license out their own patents and license in those held by other firms (the majority of IT firms and certainly the norm for firms participating in SSOs), continued interactions on both sides of such deals help to ensure that licensing—not withholding—is the norm.

Companies are waging the smartphone patent wars with very different track records on SSO participation. Apple, for example, is relatively new to the mobile communications space and has relatively few SEPs, while other firms, like Samsung, are long-time players in the space with histories of extensive licensing (in both directions). But, current posturing aside, both firms have an incentive to license their patents, as Mark Summerfield notes:

Apple’s best course of action will most likely be to enter into licensing agreements with its competitors, which will not only result in significant revenues, but also push up the prices (or reduce the margins) on competitive products.

While some commentators make it sound as if injunctions threaten to cripple smartphone makers by preventing them from licensing essential technology on viable terms, companies in this space have been perfectly capable of orchestrating large-scale patent licensing campaigns. That these may increase costs to competitors is a feature—not a bug—of the system, representing the return on innovation that patents are intended to secure. Microsoft has wielded its sizeable patent portfolio to drive up the licensing fees paid by Android device manufacturers, and some commentators have even speculated that Microsoft makes more revenue from Android than Google does. But while Microsoft might prefer to kill Android with its patents, given the unlikeliness of this, as MG Siegler notes,

[T]he next best option is to catch a free ride on the Android train. Patent licensing deals already in place with HTC, General Dynamics, and others could mean revenues of over $1 billion by next year, as Forbes reports. And if they’re able to convince Samsung to sign one as well (which could effectively force every Android partner to sign one), we could be talking multiple billions of dollars of revenue each year.

Hand-wringing about patents is the norm, but so is licensing, and your smartphone exists, despite the thousands of patents that read on it, because the firms that hold those patents—some SEPs and some not—have, in fact, agreed to license them.

The inability to seek an injunction against an infringer, however, would ensure instead that patentees operate with reduced incentives to invest in technology and to enter into standards because they are precluded from benefiting from any subsequent increase in the value of their patents once they do so. As Epstein, Kieff and Spulber write:

The simple reality is that before a standard is set, it just is not clear whether a patent might become more or less valuable. Some upward pressure on value may be created later to the extent that the patent is important to a standard that is important to the market. In addition, some downward pressure may be caused by a later RAND commitment or some other factor, such as repeat play. The FTC seems to want to give manufacturers all of the benefits of both of these dynamic effects by in effect giving the manufacturer the free option of picking different focal points for elements of the damages calculations. The patentee is forced to surrender all of the benefit of the upward pressure while the manufacturer is allowed to get all of the benefit of the downward pressure.

Thus the problem with even the limited constraints imposed by the Google settlement: To the extent that the FTC’s settlement amounts to a prohibition on Google seeking injunctions against infringers unless the company accepts the infringer’s definition of “reasonable,” the settlement will harm the industry. It will reinforce a precedent that will likely reduce the incentives for companies and individuals to innovate, to participate in SSOs, and to negotiate in good faith.

Contrary to most assumptions about the patent system, it needs stronger, not weaker, property rules. With a no-injunction rule (whether explicit or de facto (as the Google settlement’s definition of “willing licensee” unfolds)), a potential licensee has little incentive to negotiate with a patent holder and can instead refuse to license, infringe, try its hand in court, avoid royalties entirely until litigation is finished (and sometimes even longer), and, in the end, never be forced to pay a higher royalty than it would have if it had negotiated before the true value of the patents was known.

Flooding the courts and discouraging innovation and peaceful negotiations hardly seem like benefits to the patent system or the market. Unfortunately, the FTC’s approach to SEP licensing exemplified by the Google settlement may do just that. Continue Reading…