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, September 16, 2021

China extends hand to EU over standard-essential patent enforcement, prefers dialog over escalation: judges from three jurisdictions spoke at today's Renmin University conference

China's response to the EU's request for information via the World Trade Organization (WTO) regarding standard-essential patent (SEP) enforcement was rather succinct. But that is only because China is confident of its compliance with the TRIPS Agreement--and should not be confused for an unwillingness to discuss SEP enforcement policies with a major trading partner.

In 2012, seven judges of the United States Court of Appeals for the Federal Circuit attended what the U.S. appeals court's website still describes as "an historic three-day conference to discuss the adjudication of intellectual property disputes." That event took place at Renmin University of China (RUC), as did the first International Symposium on Judicial Protection of Intellectual Property Rights--Transnational Dialogue and Normative Coordination a few years ago. Today, RUC hosted the "sequel" to that event, and I followed it via Zoom because it represented a splendid opportunity to listen to multiple patent-specialized judges from China, the UK, and Germany.

If the European Commission that if they missed any details in China's official answer, the EU might just ask for a recording of today's conference (approximately five hours).

The presentations by multiple Chinese judges as well as two German (Judge Klaus Bacher of the Federal Court of Justice and Judge Tobias Pichlmaier of the Munich I Regional Court) and two British judges (Justices Richard Meade and James Mellor, both of the England & Wales High Court of Justice) summarized and explained various landmark SEP rulings I've previously looked at, all the way up to the very recent jurisdictional decision in OPPO v. Sharp. No surprises there, obviously. Those presentations were all well-structured and informative. Judge Bacher didn't mention that his court expects implementers to take global portfolio licenses--maybe he omitted it because it was so obvious to him, but in this international context it bears reiterating. I think Justice Meade stole the other European judges the show in terms of content, structure, and presentation (despite not switching into full-screen mode): low-key but world-class.

Several Chinese judges (and academics) were very good. My favorite among them was Judge Zhonglin He, Deputy Chief of the Intellectual Property Court of the Supreme People's Court, who delivered the closing remarks. He made it perfectly clear that they're more than willing to talk to the EU and prefer cooperation over confrontation. In a very credible way, he stressed that the Chinese courts won't issue SEP rulings just for the sake of preserving and exercising jurisdiction. They're not maximalists but look at the specific circumstances of each case.

The differences between Chinese, British and German judicial approaches to SEP cases crystallized today:

  • The German approach is very inflexible. They order anti-antisuit injunctions without ever asking the question of whethera foreign court may actually have good reasons to declare itself the proper forum for the adjudication of a global dispute, while they (the German courts) simply exercise global jurisdiction by forcing defendants into global portfolio licenses under the threat of an injunction. What Judge Bacher said about the Huawei v. ZTE framework

    pronounced by the European Court of Justice in 2015 sounded like a step-by-step, sequential analysis, but has nothing to do with the judicial reality in Germany, which cuts corners by importing virtually everything into the first step (the sincerity of an implementer's willingness to take a license).
  • The British judges were very forthright about how things work in the UK. With respect to the availability of injunctions (not only but also in the SEP context), there is a framework that looks like eBay v. MercExchange, but normally an injunction issues (even in favor of non-practicing entities). Antisuit injunctions are available, but international comity is considered. Where the UK judiciary goes further in a procedural sense than its German counterparts is that British judges set global rates even if only the patentee asks them to do so--but in practice, what German courts do has the same effect, just that implementers will, on average, end up paying more as German courts only throw out facially absurd royalty demands.

  • China's approach is very case-specific, and what positively surprised me is that the Chinese judges who spoke at today's conference sounded as policy-focused as pragmatic. Their policy focus is to provide guidance to the parties to SEP disputes, enabling them to reach an agreement. European companies and officials always take note when a Chinese court determines that it is in the position to set a global rate or to hand down an antisuit injunction--but it's not like anybody with even a tenuous connection with China could just go there and have a global dispute adjudicated in China. The underlying rationale is actually very nuanced. It may seem counterintuitive, but the way those Chinese judges spoke today was actually closer to how U.S. judges discuss patent issues than what I typically hear from British and German judges.

Today's conference wasn't going to solve the problems at hand, which are forum-shopping by parties and forum-selling by some (European) judges. But I believe it made an important contribution. I saw that some of the European judges, above all Judge Pichlmaier, followed large parts of the symposium.

It would be great if someone--ideally a political body or renowned academic institution--could organize such a gathering of judges in Europe and invite Chinese judges and academics to speak. To an EU event I would also recommend to invite U.S. judges, such as Judge James L. Robart of the United States District Court for the Western District of Washington, a thought leader on FRAND since his landmark Microsoft v. Motorola case.

There is, however, only so much that judicial dialog can achieve. Ultimately, when the judges go home from such a conference, they have to apply their national laws, and structural differences are a barrier to harmonization. Policy makers should engage in similar discussion.

At the next event of this kind, the focus should be on potential solutions that would satisfactorily address the problem of extraterritorial overreach in the SEP enforcement context.

Share with other professionals via LinkedIn:

Wednesday, September 15, 2021

Intellectual property rights might not entitle Apple to any 'commission' on app revenues, but in any event nowhere near 30%: court misunderstood Epic's lawyers

For a blog with "patents" in the name it would actually have made a lot of sense to start the discussion of the Epic Games v. Apple ruling with the intellectual property aspects of the case. But I had to combat disinformation of app developers regarding the practical effects of the injunction (should it ever be enforced).

The court ruling is unfair to Epic with respect to what it actually wanted and argued. (Some would argue that it's unfair in other ways, too, but I wish to keep a narrow focus in this post.)

In the decision, Judge Yvonne Gonzalez Rogers accuses Epic of "overreach" and suggests that Epic wanted Apple to receive nothing from app developers, though even her own decision notes that "Epic Games does not venture to argue that Apple is not entitled to be paid for its intellectual property." The passage I just quoted is an understatement. Epic's counsel unequivocally said during closing argument that Apple is entitled to reasonable and non-discriminatory compensation for any intellectual property, but an antitrust case is always about putting an end to illegal practices (without necessarily replacing them with an alternative compensation scheme right away). It was not about a free ride. It was about not letting Apple (ab)use its App Store monopoly, and subsequently one could still talk about IP (but not in that same case).

I have no idea what Epic's appeal will focus on, but I wouldn't be surprised if the appeals court agreed with Epic that a sequential approach is precisely the way antitrust law works: you stop the illegal practice first, and then the defendant can come up with a new practice, which may invite further challenges (but those won't happen, or at least won't have merit, if the new practice is reasonable and non-discriminatory). The appeals court may tell the district judge that the purpose of a unilateral conduct case is not to replace an illegal practice with a legal one.

One question that some people are asking themselves already is whether Apple will seek its App Store commission on payments made outside an iOS app but because of an app linking out to, for example, a website. As I explained in my previous two posts, there's no way that Apple would have to tolerate alternative payment systems. The court made it clear that it's just about generating awareness for offerings on other platforms while Apple remains free to require the exclusive use of its own IAP system, and Apple will benefit from the legal standard, which allows Apple to interpret the injunction (in light of the underlying order) in the way most favorable to its own interests, as long as it's not unreasonable.

In practical terms, it would be possible but a real hassle for Apple to have to collect app commissions from developers that are generated through other payment systems. Apple couldn't possibly audit each and every developer's books. Maybe it could impose some severe penalties for fraud and then just perform audits in suspicious cases plus a few random audits. But we don't really have to think too much about that. Again, the injunction--if and when it actually gets enforced--is not going to be a major problem for Apple. They can reasonably interpret the court ruling as not having to condone any "end run" around its IAP rule, such as a mere web shop where users purchase digital items they consume on iOS.

With some console makers not allowing cross-wallet/cross-purchase (or seeking an additional compensation for cross-play), Apple could take the same position now. That would have political implications, but the Epic v. Apple ruling doesn't prohibit it.

As some people are discussing now, the court says that Apple could collect a commission even on sales through other app stores--though it would then be an IP license fee in the form of a percentage of sales, which is why the term "commission" doesn't fit. I think the court should have defined the term more narrowly. (On a previous occasion I also criticized Apple for broadening its meaning.)

What the court got absolutely right is that the 30% cut is not a market rate for the intellectual property in question. The court even takes note of "Apple’s low apparent investment in App Store-specific intellectual property." The commission is practically imposed and enforced because of Apple's app distribution monopoly. The term "gatekeeper" (which is very popular in EU tech policy and law) doesn't appear in that ruling, but that's what it's all about.

That leads us to an interesting question: what is the commission rate going to be in a future scenario (it's really a question of when--not if--this happens) where new legislation and/or a successful appeal by Epic would do away with the gatekeeper toll and would instead leave Apple with only one tool at its disposal--IP enforcement--to collect money from developers?

What if (actually, when) developers can publish iOS apps without depending on Apple's app review because they can go through alternative app stores (and "sideloading")?

The Epic v. Apple ruling explains the following:

"Apple distributes its basic developer tools for free but charges an annual fee for membership in its developer program to distribute apps and which allows access to, for instance, more advanced APIs (many of which are protected by patents, copyrights, and trademarks) and beta software."

"Apple’s intellectual property as it relates to the iOS ecosystem generally are significant. The record is undisputed that Apple holds approximately 1,237 U.S. patents with 559 patent applications pending. With respect to the App Store itself, Apple holds an additional 165 U.S. patents with 91 more U.S. patent applications pending. Other than these patents, Apple does not identify specifically how the rest of its intellectual property portfolio impacts the technology at issue in this case nor does it specifically justify its 30% commission based on the value of the intellectual property. It only assumes it justifies the rate."

Given this year's Supreme Court decision in Oracle v. Google, I can't see how developers' use of Apple's APIs would not constitute fair use. Google even got away with incorporating APIs into a new product that competed with (and ultimately displaced in the mobile market) the original platform (Java). Developers, however, don't use Apple's APIs to build a new operating system: instead, they build applications, with a strong presumption in each case that it constitutes transformative use.

Patent counts mean little. Epic wasn't going to turn this antitrust dispute over Apple's App Store monopoly into a declaratory judgment case over Apple's iOS and App Store patents.

If Apple had to resort to patent litigation against app developers in order to collect a commission, it would have to overcome developers' non-infringement and invalidity defenses. Developers would likely also raise equitable defenses, but let's not get into that here.

Those patent numbers may seem staggering, but they could melt down very quickly as most of those patents might simply never be infringed by a developer and others might get invalidated once challenged. If any valid patents are actually infringed, the next question is whether developers could work around them. Let's assume, just hypothetically, that there would be one or more valid patents left that are infringed and cannot be worked around. Then we get to the remedies stage.

Seriously, Apple wouldn't get anywhere near 30% (or even 15%) of developers' revenues in the form of damages or ongoing royalties.

The only way Apple could theoretically still get its 30% cut would be if it obtained an injunction. In the U.S., Apple would have to meet the eBay v. MercExchange standard. Developers would argue that Apple actually benefits from the availability of apps and makes money on its devices. That would up the eBay ante for Apple. In some other jurisdictions, particularly Germany, Apple could obtain injunctions more easily, but it probably has fewer patents there.

Even if Apple obtained an injunction, it might then face an antitrust challenge to its rates--with the same arguments Apple makes against standard-essential patent (SEP) holders. Sure, Apple would argue that it never made a FRAND licensing promise with respect to its iOS IP. But in Europe, SEP case law is antitrust-, not contract-based, and Apple made the same arguments there (and it also brought antitrust claims in the U.S. over SEPs, such as against Samsung, though in vain, and against Qualcomm, though the San Diego Apple v. Qualcomm case settled during opening arguments).

To sum it up, Apple needs the gatekeeper's leverage to collect its 30% (or 15% under the Small Business Program) commission from app developers. On an IP basis, at least in the U.S. (where it would likely be denied patent injunctions against developers), Apple would get nothing or a much smaller amount. In light of the risk-opportunity ratio, Apple might not even have an incentive to bring any IP infringement litigation against developers.

Share with other professionals via LinkedIn:

Monday, September 13, 2021

App developers must know that any alleged ambiguity in the Epic Games v. Apple injunction favors Apple, not them: there won't be IAP alternatives, not even in WebView

This is a follow-up to my previous post on this topic: "No, the Epic v. Apple injunction absolutely positively DOESN'T allow developers to incorporate 'buttons' for alternative IN-APP payment mechanisms".

The original version of that post said Daring Fireball's John Gruber was "right for the wrong reasons." He did state reasons on Twitter that didn't convince me because it sounded like Apple's app review practices were going to inform the interpretation of the Epic v. Apple injunction. But John also referred at some point to Apple telling him that the ruling is unambiguous, such as in this tweet, though I disagree with the pages referenced there as that's the Sherman Act--not California UCL--analysis.

It's regrettable (to put it mildly) that The Verge's Nilay Patel just keeps digging himself an ever bigger hole instead of acting responsibly and admitting his error. The man is actually a lawyer by training (and journalist by vocation), so it shouldn't be hard for him to figure out that his analysis was fundamentally flawed because he focused myopically on the wording of the injunction while ignoring the underlying Rule 52 order. And a few hours ago the intellectual bankruptcy of his argument became even more obvious in the following tweet:

So let me set the record straight on this:

Nilay Patel himself says his "whole argument" is that the wording is allegedly "ambiguous." I don't even agree because the ruling is clear enough if one reads the relevant parts of the 185-page Rule 52 order. But if we assume--only arguendo--that Nilay Patel is right and it is ambiguous, it means he loses the argument anyway.

Under controlling Ninth Circuit law, Apple will only be held in contempt of court if it "(1) [] violate[s] the court order, (2) beyond substantial compliance, (3) not based on a good faith and reasonable interpretation of the order, (4) by clear and convincing evidence." In re Dual-Deck Video Cassette Recorder Antitrust Litig., 10 F.3d 693, 695 (9th Cir. 1993)

By coincidence, that case was also an antitrust case as its caption shows. And the same appeals court--the one with which Epic filed its appeal yesterday--clarified that the standard involves "disobedience to a specific and definite court order." (id.)

The bottom line is that any alleged ambiguity would favor Apple, not developers.

I am a developer, and a complainant against Apple in another App Store context. I wish I had better news for the wider developer community. But someone has to counter all that disinformation out there. It hurts me to see people fantasizing and theorizing about out-of-this-world crap that's simply not going to help anyone.

The question is not whether a developer's interpretation of the injunction is somewhat reasonable. It's whether Apple's interpretation is so unreasonable as to constitute disobedience to a specific and definite court order.

That threshold is very high.

Apple may have political reasons (in light of legislative and regulatory proceedings in various jurisdictions) to make concessions to developers. But in legal terms, Apple is free to interpret the injunction in its favor, provided that its interpretation is reasonable.

For the reasons I explained in my previous post, it's not just one reasonable interpretation, but the only one, to understand that the court explicitly did not enable alternative IAP mechanisms. It's all just about informing users of alternative platforms, such as that the same in-game item or currency might be available at a lower cost on, say, a Samsung phone via the Galaxy Store.

WebView (i.e., opening web pages within an app) is not going to be the answer. Any purchases made in a WebView would reasonably be considered in-app purchases and, therefore, wouldn't have to be condoned by Apple under a reasonable (in my view, even the only reasonable) interpretation of the order.

As I cover competition and IP cases across various jurisdictions, I'd just like to point out in closing that the Ninth Circuit standard for civil contempt is consistent with what I see everywhere else: it's par for the course that an injunction is interpreted in defendant's favor and that the evidentiary standard for a violation is also exacting. It's that ancient concept of "in dubio pro reo."

Apple won't even have to approve linking out to websites that merely sell digital items consumed in an iOS app. The clear purpose of the injunction is to have some competitive constraint on Apple by making customers aware of lower prices on other platforms. That platform may be the World Wide Web, but then whatever you purchase there must also be consumable there. For example, a game must be playable as a browser game. If all you get in the browser is the in-game shop, but not the actual game, it won't qualify under a--in my view, the only or at least the most--reasonable interpretation of the order.

In other contexts than anti-steering, the order mentions Apple's argument that it allows "cross-wallet" and "cross-purchases." Cross-wallet means that Fortnite gamers could buy V-Bucks (the virtual in-game currency) on another platform, such as a Windows PC, and then use those virtual bucks on iOS. Sony and Nintendo don't allow that--they insist that whatever you consume on their platforms has been purchased on their platforms (earning them their commission). Apple does. Cross-purchases are the same for digital items such as a powerful weapon. Here, too, Apple is more flexible than some others.

What if Apple now disallowed cross-wallet and cross-purchases?

It would minimize the practical impact of the injunction because game makers could point users to other platforms on which they may find the same offerings at a lower cost, but those purchases couldn't be consumed on iOS.

It wouldn't be a violation of the order (considering the exacting standard I outlined above).

It would be politically problematic, and Apple couldn't do so with respect to "reader" apps under its recent Japanese settlement that has worldwide effect but doesn't cover games.

In legal terms, any modification of Apple's IAP-related terms that disadvantages developers over the status quo would potentially serve as an indication of Apple's market power and the absence of sufficient competitive constraints, meaning that future antitrust decisions could--but, to be clear, won't necessarily--have different outcomes under the Sherman Act, even in the same district.

Apple will now have to decide whether to appeal an injunction and seek a stay of its enforcement. That would be the most obvious thing to do. What sometimes happens is that parties don't try to get a jury verdict overturned because it largely favors them, and in order to do away with the remainder they'd have to argue that the jury made a decision that no reasonable jury could have made (while defending their victory against the other party's claims that the jury was unreasonable). Here, we're talking about a bench trial, so the standard is different, making it easier to "have your cake and eat it."

The injunction won't take effect for about three months, and I guess Apple will appeal it and seek a stay, which may very well be granted.

Assuming that--sooner or later--the current injunction does become enforceable, this post and the previous one hopefully helped many developers understand that most of them won't really benefit to any non-negligible extent. Should Apple play hardball and disallow cross-wallet/cross-purchase, developers may even be worse off than before.

Share with other professionals via LinkedIn:

Saturday, September 11, 2021

No, the Epic v. Apple injunction absolutely positively DOESN'T allow developers to incorporate 'buttons' for alternative IN-APP payment mechanisms

[Update] I've provided further information (specifically on the standard for contempt of court) in a September 13 post. [/Update]

This here is a follow-up to my commentary on the Epic Games v. Apple ruling that came down yesterday. I just visited my favorite IT news aggregator website and saw an article by The Verge's Nilay Patel with the following conclusion, which is off base:

"That means that a fair reading of the plain text of this injunction suggests that buttons in iOS apps can direct users to purchasing mechanisms in the app — if the button just kicks you out to the web, it would be an external link!"

Sorry, that's utter nonsense. On Twitter, Daring Fireball's John Gruber tried to convince Nilay Patel that he was wrong. In the end, Nilay Patel still stressed that it's up to the court to interpret its injunction. Well, John Gruber was right, and Nilay Patel arrives at the wrong result though he is right that the court--not Apple--will ultimately interpret the wording of the injunction. I've been rooting for Epic, and I wish everyone were as honest as Epic Games CEO Tim Sweeney after losing a court battle. But I'm absolutely committed to telling people the truth.

That article by The Verge (a website that actually did a great job covering the Epic Games v. Apple dispute) is simply what happens when one writes about a single-page document (the injunction per se) as if it existed in a vacuum--though it must actually be read against the background of the underlying 185-page Rule 52 post-trial order, just like patent claims are interpreted in light of the patent specification.

Nilay Patel's theory is absurd. It cannot possibly be reconciled with the part of the court ruling that deals with Apple's anti-steering provision. I'm wondering why no one in that Twitter debate (unless I missed it) brought it up. So I decided to write this post to put an end to that phantom debate.

Let's bear in mind that only Epic's tenth claim succeeded at all. Not only Epic's federal antitrust claims but also various state law claims failed. The failed state law claims include a couple that were very specifically about offering different IAP systems: Count 8 alleged unreasonable restraints of trade in the iOS IAP processing market under the California Cartwright Act, and Count 9 presented a tying claim related to IAP. Epic's tenth and last claim--based on California UCL--broadly raised the issue of Epic being "unreasonably prevented from freely distributing mobile apps or its in-app payment processing tool, and forfeit[ing] a higher commission rate on the in-app purchases than it would pay absent Apple’s conduct." But the court found for Epic under its tenth claim only with respect to the anti-steering provisions.

Section VI of the Rule 52 order addresses Epic's Count 10. Section VI.C ("Unfair Practices" is where Epic wins its consolation prize, so that's the part to focus on. The following sentence, found near the bottom of page 162 (PDF page 163), should end the debate:

"On the present record, however, Epic Games' claims based on the app distribution and in-app payment processing restrictions fail for the same reasons as stated for the Sherman Act."

Very clearly, this means that even the sole count on which Epic prevailed (in part) failed to do away with Apple's IAP rule, which is that you must use Apple's IAP system for accepting payments in your iOS native app.

Then, on the next page, the court distinguishes the IAP restrictions--which Nilay Patel erroneusly argued the injunction has annulled--from the anti-steering provisions:

"Epic Games did challenge and litigate the anti-steering provisions albeit the record was less fulsome. While its strategy of seeking broad sweeping relief failed, narrow remedies are not precluded."

The "broad sweeping relief" would have included both alternative methods of distributing apps to iOS users and alternative IAP systems. The "narrow remed[y]" the court gave Epic is just about providing information (including links) on external payment options (websites and apps for other platforms, such as Android, personal computers, or consoles).

The following sentence is the last one to start on that same page, and again clarifies what the court means by "anti-steering":

"Thus, developers cannot communicate lower prices on other platforms either within iOS or to users obtained from the iOS platform." (emphasis added)

Other platforms are key here because Apple does face competition from other device makers and platform operators, but--as Epic argued--not in the aftermarket of iOS app distribution.

The court goes on to explain the importance of "commercial speech, which includes price advertising" and, on page 164 (PDF page 165) says that "the ability of developers to provide cross-platform information is crucial."

Perfectly consistently, the court, when talking about the importance of users being able to make informed choices, recalls that "the Supreme Court has recognized that such information costs may create the potential for anticompetitive exploitation of consumers."

Information about lower prices on other platforms--not alternative IAP systems on iOS itself.

After the Tethering Test, the court performs a Balancing Test. In that one, the injunction ordered against Apple is distinguished from the one denied in the Amex decision by the Supreme Court:

"Here, the information base is distinctly different. In retail brick-and-mortar stores, consumers do not lack knowledge of options. Technology platforms differ. Apple created a new and innovative platform which was also a black box. It enforced silence to control information and actively impede users from obtaining the knowledge to obtain digital goods on other platforms. Thus, the closer analogy is not American Express’ prohibiting steering towards Visa or Mastercard but a prohibition on letting users know that these options exist in the first place." (emphases added)

Section VI.D (Remedies) is equally consistent in stressing that this is about information, not alternative IAP systems:

"Apple contractually enforces silence, in the form of anti-steering provisions, and gains a competitive advantage. Moreover, it hides information for consumer choice which is not easily remedied with money damages."(emphases added)

In summary, what Nilay Patel calls a "close read" and "fair reading" is nonsense because the Rule 52 order couldn't be clearer. In that one, the court made it unmistakably clear that the injunction it ordered is meant to be narrower than the permission of alternative IAP systems that Epic sought, and leaves no doubt that developers shall merely be allowed to provide users with information about prices on other platforms (WWW, Android, PCs, consoles...) to have at least a minimal competitive constraint on Apple. Just transparency. That's it.

Share with other professionals via LinkedIn:

Federal judge awards Epic Games a mere consolation prize against Apple, which regrettably succeeded with its 'web apps are viable' lie

Yesterday's Epic Games v. Apple ruling by Judge Yvonne Gonzalez Rogers of the United States District Court for the Northern District of California (judgment, permanent injunction, and detailed Rule 52 order) amerely defers the resolution of the real competition issues facing iOS app distribution. It's one of those situations in which either side "gets something" and could claim victory, as Apple apparently does though the stock market initially disagreed (I, personally don't think the decision should have moved the stock at all). This makes it all the more remarkable that Epic doesn't engage in spin but concedes defeat. It's not that Epic achieved nothing; but for the time being, all it got is a consolation prize, and that's why Fortnite won't return to iOS at this stage.

Let me just share a few short observations for now as an exhaustive analysis would take a lot more time:

  • Epic are--for the time being--losers, but Apple are liars in the web apps context. They shamelessly took advantage of the fact that courts need to rely on expert testimony--which I almost mispelled as "testimoney" as expert witnesses say a lot of things when the pay is good--as soon as it comes to technical questions, and the biggest and most impactful lie here was that Apple portrayed HTML 5 web apps as a viable alternative to native apps for game distribution. I know exactly how the HTML 5 version of my Viral Days game feels and performs (it's just terrible); and I know how easy it would be for Apple with its death grip on iOS to always ensure that web apps would fail to meet customer expectations. I can't blame the judge for not knowing this. She's a judge, not a programmer. From my vantage point, based mostly on Epic's proposed findings of fact and conclusions of law, Epic had made the case for the insufficiency of web apps pretty well, though I raised three issues (two of them IP-related) shortly before the trial that I thought Epic should have brought up.

  • Epic v. Apple has been a greater success in terms of revelations (such as Tim Cook's admission that he doesn't receive reports on developer satisfaction) than in terms of remedies. An anti-anti-steering order (meaning that Epic got what AmEx was denied) may help Spotify to some degree, but doesn't solve the fundamental problems.

  • Epic could have succeeded--and on appeal still could succeed--even under the market definition adopted by Judge YGR: digital mobile gaming transaction. In my recollection of the late-May closing argument, that's a market definition Epic's counsel could actually live with. Without the word "mobile" in it, the definition would be too broad and Apple would be in the clear. But the aforementioned web apps lie and other smokescreens regarding alternative ways to distribute games to iOS users worked.

  • Originally, Judge YGR didn't want to make the factual findings herself. She'd much have preferred for a jury to decide because appeals courts afford way more deference to jury verdicts than judicial findings of fact. It was already obvious to me last year that she didn't want this case to be the next FTC v. Qualcomm, where one of her colleagues in the same district found in plaintiff's favor and the appeals court threw out the whole thing. So what Judge YGR has rendered here is a decision that gives either party plenty of ammunition at the appellate stage (e.g., "Apple's slow innovation stems in part from its low investment in the App Store"), though the worst part for Epic is clearly that the judge says the Fortnite maker has "failed to prove [its Sherman Act Section 2] claim for myriad reasons." In some contexts, the ruling leaves open the possibility of certain claims being proven with more or better evidence. Some of the rationale could even be described as displaying a great deal of insecurity along the lines of "maybe I should ... but I'm not sure I can." Anything could still happen before the Ninth Circuit. It could nix Epic's consolation prize based on California Unfair Competition Law but could also reverse key conclusions that enabled Apple's acquittal. Should the appeals court find that Apple has actually violated the antitrust laws (and not merely committed an "incipient" antitrust violation as Judge YGR put it), Epic could theoretically still prevail 100%.

  • What's disappointing is that the judge actually saw--as her world-class examination of Apple CEO Tim Cook on the last day of testimony showed--that Apple doesn't face sufficient competitive constraints with respect to developers, and knows that many developers are unhappy, but that this realization didn't dissuade her from a negative finding on Epic's Section 2 claim.

  • Apple's minimalist concessions have worked so far. The remedy imposed here bears a strong resemblance to how Apple resolved its Japanese antitrust issue relating to "reader" apps. But there's so much going on around the globe that Apple is merely delaying the inevitable because dilatory tactics are profitable. United States Senators from both sides of the aisle have responded to the decision by stating their resolve to take action. Before this case has been decided by a final court of appeal, new legislation may already address some of the issues and allow alternative payment options.

  • The ruling says: "Here, Epic Games has provided requests for its remedy which principally appear to eliminate app review." As I am pursuing my own complaints over Apple's app review, yesterday's decision obviously does nothing to address my primary concern. I still believe that alternative app stores are needed, and that anything less won't do.

Share with other professionals via LinkedIn:

Wednesday, September 8, 2021

China to EU: we comply with the TRIPS Agreement and if you have any questions about standard-essential patent enforcement, let's have bilateral talks

On July 6, the European Commission, which represents the EU at the World Trade Organization (WTO) level, filed an elaborate five-page "request for information pursuant to Article 63.3 of the TRIPS Agreement" (TRIPS = Trade-Related Aspects of Intellectual Property Rights) as a formal "communication from the European Union to China." Styled as a request for information for transparency's sake, the EU was expressing concerns over China's standard-essential patent (SEP) case law, particularly global FRAND rate-setting decisions and antisuit injunctions.

The very recent OPPO v. Sharp decision by the Supreme People's Court (SPC) of the People's Republic of China (PRC) already demonstrated that the Chinese judiciary considers it stance on SEPs to be balanced and perfectly compatible with the concept of international comity (which in this context means that courts in one country respect their counterparts in another).

Even clearer is the message that the Chinese government has for the EU. China does not believe to be under any obligation whatsoever to respond to the EU Commission's request for information. The five-page questionnaire drew a five-paragraph response that fits on a single page. The final paragraph invites the EU to have a direct conversation rather than a further exchange at the WTO level:

"5. China and the European Union have established the China-EU IP Working Group, and China stands ready to have further discussions through such existing bilateral channel."

The first paragraph of China's response is a declaration of its commitment to IPR protection and a reference to the bilateral contacts mentioned in the final paragraph. The second paragraph disputes a formal obligation to respond.

In the remaining two paragraphs, one can find absolutely nothing about SEPs or antisuit injunctions. Zero. Nada. It's just about China's rules for publishing judgments online and a clarification that any guidelines found in cases designated as "typical" or "big" cases still aren't generally applicable. In other words, decisions are still made on a case-by-case basis, even if some judgments have a higher profile than others.

Brevity is the soul of wit. If China had filed 10 or 20 pages defending its case law, that would have been weaker than this terse reply. It would have been defensive.

The EU now has four options:

  1. The Commission's DG TRADE can say "alright, this went nowhere, we barked up the wrong tree." And let it go. Considering the effort that must have gone into the EU's five-page request, there's likely more to come though.

  2. The Commission can accept China's invitation, sit down, and talk. Diplomacy. Bilateralism.

  3. The Commission could bring a more formal complaint to accuse China of non-compliance with TRIPS, triggering a WTO dispute settlement procedure.

  4. Theoretically, the EU could start an all-out trade war (with punitive tariffs etc.). I can't imagine that as the next step, but they might threaten with it at some point.

I'm just a neutral observer who understands the interests of European companies in patent enforcement as well as China's interests in being a key SEP jurisdiction (given that most smartphones are made there, many SEPs belong to Chinese companies, and for a number of device makers China is the largest market). Both sides have legitimate interests, but equally legitimate questions can be asked about the EU's request for information:

  • Why are they concerned only about Chinese FRAND determinations and antisuit injunctions when

    • a U.S. court already entered an antisuit injunction almost ten years ago (Microsoft v. Motorola, a masterpiece of a decision) that prevented the enforcement of European (in that case, German) SEP injunctions, and

    • the UK Supreme Court (shortly before the UK formally left the EU) held in Unwired Planet v. Huawei that British courts can present implementers with the alternatives of accepting a global license agreement "made in Britain" or being forced out of the UK market?

  • Why is it OK for European courts (particularly the ones in Germany) to enjoin Chinese and other companies unless they take a global license? The fact that German courts don't set the rate is secondary. A SEP holder can ask for anything that is not facially absurd, provided that the implementer is deemed an unwilling licensee.

    This also affects U.S. companies such as Apple when they get sued in Germany--and they don't get help from their courts, which decline to make global FRAND determinations unless both parties ask them to.

Given that U.S. courts exercise more restraint than their counterparts in the EU, the UK, and China, I'm not even sure it was a good idea for the EU Commission to make extraterritorial overreach in SEP enforcement a WTO issue--and even less so in light of the Biden Administration's rather implementer-friendly leanings.

Let there be no doubt: there are problems that need to be solved. I would encourage the EU and China to talk to each other, and I would also encourage the U.S. and the UK (which may override its top court's case law by legislative means) to engage in discussions with the EU (and vice versa).

What is not a solution is for the pot to call the kettle black. Given that the EU has some sweeping to do in front of its own door, China rightfully gave short shrift to an insinuation of non-compliance with the TRIPS Agreement. But that doesn't have to prevent the parties from engaging in constructive dialog, or multilateral talks that would also involve the United States and the United Kingdom.

Share with other professionals via LinkedIn: