Showing posts with label 3GPP. Show all posts
Showing posts with label 3GPP. Show all posts

Monday, July 11, 2022

For the first time ever, Apple is suing over a standard-essential patent: in a Munich case against Ericsson, Apple is asserting a 4G SEP acquired from Intel

There are more and more firsts in the Ericsson v. Apple 5G patent dispute:

  • the first-ever Colombian standard-essential patent (SEP) judgment (Ericsson is now enforcing a 5G injunction, which Apple desperately sought to prevent),

  • the first-ever "emergency motion" for an antisuit damages order (Apple's reaction to the Colombian decision), and now...

    ...TA-DA...

  • the first-ever SEP lawsuit brought by Apple, which has been on the receiving end of SEP assertions for well over a decade but is only now striking back with a SEP for the first time in its history.

The venue is--of course--Munich, the world's #1 SEP injunction hotspot (while I haven't found out yet whether Apple is seeking an injunction, I'm sure it's either doing so now or would do so a little later).

The patent-in-suit is EP3178199 on "virtualized network function management." The company that filed for it, and obtained it, is Intel. A few months after the application was granted, Apple bought Intel's baseband chipset division, and in a subsequent transaction acquired many of Intel's cellular SEPs, such as this one. The database of the European Telecommunications Standards Institute (ETSI) shows that Intel declared the underlying patent application essential to the LTE (Long-Term Evolution, commonly known as 4G) standard, more specifically to its Evolved Packet System RAN part. RAN stands for Radio Access Network. The relevant 3GPP specification, no. 32.842, is titled "Telecommunication management; Study on network management of virtualized networks." That technical report was approved in 2015. All five IPR (intellectual property right) declarations related to that one were made by Intel, and Intel didn't subsequently declare any of those rights non-essential. So there is a FRAND commitment in place.

The Munich I Regional Court has assigned this case to its 21st Civil Chamber (Presiding Judge: Dr. Georg Werner). The case no. is 21 O 1970/22, and the first hearing (with the second one being a full trial) slated for February 15, 2023.

The same division will hear another Apple v. Ericsson countersuit on March 1, 2023: case no. 21 O 3471/22 over EP2946486 on an "apparatus, system and method of wireless backhaul and access communication via a common antenna array." This is a homegrown Apple patent, and appears to be a non-SEP.

At least one of Ericsson's cases has also been assigned to the Munich court's 21st Civil Chamber and will be heard in September 2022.

The two Munich complaints by Apple against Ericsson are not the only countersuits--just the most recently discovered ones. There is also a Mannheim case over another homegrown non-SEP, which will go to trial in October 2022, and a complaint with the United States International Trade Commission (USITC, or just ITC) seeking an import ban on mobile base stations implementing mmWave, but those patents haven't been declared essential to a standard.

Apple and Ericsson are not the only companies contributing to the continued growth of the Munich patent (and especially SEP) docket. In my next post I'll report on several new automotive SEP assertions that have very recently been brought there.

Tuesday, April 13, 2021

Fortress-funded VoiceAge suing Apple, Lenovo, Motorola Mobility, HMD in Munich over standard-essential patents: next hearing scheduled for April 28 (Apple)

Intel is currently defending itself against another case brought by a Fortress-funded non-practicing entity (NPE) in the Western District of Texas, and last month the chipset maker filed a second amended antitrust complaint against Fortress in the Northern District of California. There's one particular Fortress entity that brought (literally) dozens of patent infringement complaints against Apple: Uniloc, whose former CEO is now running WSOU (doing business as Brazos), an entity that brought about 200 patent lawsuits last year in the U.S. alone (plus an unknown but likely staggering number in other jurisdictions). Whatever policy positions I've expressed on the NPE business model doesn't prevent me from recognizing that Fortress Investment has financed a number of different NPEs, and they aren't all like Uniloc.

I've done some research on NPE activity in Germany, and found out that VoiceAge EVS--which has offices in Newport Beach as well as Ratingen (near Dusseldorf)--is a big fan of the Munich I Regional Court (Landgericht München I). Munich has become the best forum choice for patent plaintiffs seeking injunctions.

The patents VoiceAge is asserting in Munich are

  • EP2102619 on a "method and device for coding transition frames in speech signals" and

  • EP3132443 on "methods, encoder and decoder for predictive encoding and decoding of sound signals upon transition between frames having different sampling rates."

Both have been declared essential to 3GPP TS (technical specification) 26.445, Codec for Enhanced Voice Services (EVS) (thus the "EVS" at the end of VoiceAge's company name).

Last June, the Munich court held an early first hearing in two cases (case nos. 7 O 14091/19 and 7 O 15350/19) against HMD, a company that makes phones with a Nokia trademark license (but is otherwise independent from Nokia). Rumor in the German patent litigation community has it that it went pretty well for VoiceAge. The second hearing--the actual trial--will be held on June 24. HMD has raised a FRAND defense.

On the same day, the court's 7th Civil Chamber (Presiding Judge: Dr. Matthias Zigann) will also hear VoiceAge's cases over the same patents against Apple, Lenovo, and Motorola Mobility (which Lenovo acquired from Google). The case numbers are 7 O 8369/20, 7 O 11111/20, 7 O 7366/20, 7 O 8367/20, 7 O 10318/20, and 7 O 8368/20).

The court's 21st Civil Chamber (Presiding Judge: Tobias Pichlmaier) scheduled an early first hearing in a VoiceAge v. Apple case (case no. 21 O 13503/20). It remains to be seen whether that hearing can be held. The Munich court postponed at least one other case scheduled for the week before that VoiceAge hearing (as you might have guessed, due to the pandemic). Whether it is responsible to go forward with patent hearings and trials depends on a number of factors. I'm far more concerned about automotive patent cases like Nokia v. Daimler, as they typically involve numerous suppliers and really have the potential to become superspreader events. If the room is large enough, ventilation is ensured, and people have to wear N95 masks, a hearing like VoiceAge EVS v. Apple might be possible.

Wildanger represents VoiceAge in Germany (see Juve Patent). I heard that Freshfields Bruckhaus Deringer represents Apple (Freshfields is Apple's go-to patent litigation firm in Germany).

Share with other professionals via LinkedIn:

Monday, July 29, 2019

Gaming the system: Qualcomm leverages 3GPP working group chairmanship to distort patent portfolio valuations

If you are already familiar with SEP portfolio valuation methods and their inherent shortcomings, you may wish to skip the introductory part (Basics) and jump straight to the part where I discuss specific issues with Qualcomm's conduct in connection with what is arguably the most central standardization process in the field of cellular telecommunications.

Basics

The valuation of standard-essential patent (SEP) portfolios is often performed in two steps: first, the value of all SEPs reading on the relevant standard is determined; second, the relative value of a given company's contributions to the standard is measured. In antitrust or contract cases raising FRAND questions, the inquiry may be limited to the second part, as a disproportionately high share of industry-wide royalties collected by one SEP holder can in and of itself serve to establish overcharging and unreasonableness. The latter is a huge problem for Qualcomm in the FTC antitrust case, given that Qualcomm collects approximately 25% of all wireless SEP royalties while being far below that percentage when it comes to its ownership position in wireless SEPs relative to the rest of the industry. Even Ericsson, a company that just suported Qualcomm's now-fully-briefed Ninth Circuit motion to stay the FTC's antitrust remedies, gave testimony in the FTC case that undermines Qualcomm's royalty demands. Ericsson believes to be the leader, and expressed the view that even Nokia's SEP portfolio appears more valuable than Qualcomm's.

For the purpose of determining the relative value of a given company's contributions to a standard, two inherently imperfect indicators are commonly looked at:

  1. the number of declared-essential patent families; and

  2. the number of contributions to the standardization discussion (so-called change requests).

Either approach is purely quantitative, not qualitative. But a qualitative analysis is rather costly and time-consuming even with respect to a single patent, making it practically impossible for a large portfolio. And the valuation of change requests can also be difficult, except for requests that are obviously devoid of any technical value, such as reports of mere typos or punctuation mistakes.

The specific problems of the first approach (counting declared-essential patent families) include the well-known problem of massive overdeclaration (driven by both the desire to capture as much of the value of a standard and the potential liability for undeclaring) and that of "opportunistic patenting". To explain the latter, I'll quote an instructive passage from Just-in-time inventions and the development of standards: How firms use opportunistic strategies to obtain standard-essential patents (SEPs), a paper authored by Byeongwoo Kang and Rudi Bekkers on behalf of the Eindhoven Center for Innovation Studies (ECIS) that examined the patenting behavior of participants in standard-setting and identified unusual filing activity around key standard-setting meetings:

"Our data reveals a strong relationship between patent timing and the occurrence of meetings. We observed a remarkable phenomenon that we call 'just-in-time-inventions': the patent intensity of about-to-become claimed essential patents is much higher during or just before these meetings than in other periods. At the same time, they are of considerably lower technical value ('merit'). This suggests that the just-in-time inventions are only beneficial to their owners, whereas for the public they merely invoke unnecessary costs. Finally, we observed that the phenomenon of just-in-time inventions is highly concentrated among specific types of firms, above all vertically integrated ones, and the incumbent champions of the previous technology standard." (emphasis added)

The market-driven and reality-centric solution to the problems I just outlined would be exactly what the FTC proposed in its opening statement in the FTC v. Qualcomm antitrust trial in January: SEP holders like Qualcomm should have to negotiate without undue leverage and, if necessary, prove the value of exemplary patents in court, where the validity and infringement of those patents can be challenged. The FTC didn't say so, but in the industry's opinion Qualcomm's SEPs tend to be very broad, making many of them more susceptible to invalidity than non-infringement contentions. Qualcomm's "No License-No Chips" policy has enabled the San Diego chipmaker to pretty much avoid "the moment of truth," and until earlier this decade, SEP holders drew enormous leverage from the threat of injunctive relief.

But most of the time, portfolio valuation--be it in negotiation or in portfolio-related litigation--is based on those two imperfect methods: DEP (declared-essential patent) counts and CR (change request) counts.

Specific issues

Qualcomm employee Wanshi Chen (the latter being the family name) is the chairman of the 3GPP RAN1 ("R1") working group ("WG"). That WG is "responsible for the specification of the physical layer of the radio [i]nterface" for all the major cellular standards from 3G to 4G (LTE) to 5G. 3GPP means "Third Generation Partnership Project." According to its website,

"The 3rd Generation Partnership Project (3GPP) unites [Seven] telecommunications standard development organizations (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC), known as 'Organizational Partners' and provides their members with a stable environment to produce the Reports and Specifications that define 3GPP technologies.

"The project covers cellular telecommunications network technologies, including radio access, the core transport network, and service capabilities - including work on codecs, security, quality of service - and thus provides complete system specifications. The specifications also provide hooks for non-radio access to the core network, and for interworking with Wi-Fi networks.

"3GPP specifications and studies are contribution-driven, by member companies, in Working Groups and at the Technical Specification Group level."

For a company seeking to exercise a maximum of control over cellular standards development, it's hard, if not impossible, to think of a more influential position than the chairmanship of the RAN1 WG. For an overview of 3GPP WGs I recommend table 1 on page 6 of a document (PDF) available on Ericsson's website. 3GPP members have full access to certain stats on the "3GPP meetings for group R1" webpage. RAN1 WG meetings attract substantially more participants (typically around 450) than meetings held by other WGs.

Unfortunately, Mr. Chen's conduct raises very serious questions. There are extremely strong indications that he has been leveraging this position for the purpose of distorting DEP and CR counts to an extent that other industry players may view as a downright betrayal of the trust that was once placed in him. As in some other patent-related contexts, the proverbial fox appears to have been put in charge of the hen house.

Issue #1: sky-high number of SEP declarations

First, there's a conspicuously high number of SEP declarations by Mr. Chen compared to other current and recent 3GPP WG chairmen, as shown by the high-rising bluish line on the following chart based on IPlytics data (click on the image to enlarge; this post continues below the chart):

Mr. Chen was a very active patentee even before, but his current position gives him privileged access to information and generally a lot of influence over the standardization process.

The raw data underlying the chart comes from all SEP records where the chairmen or vice chairmen are listed as inventors or co-inventors. IPlytics is a particularly popular tool for researching patent databases. I have recently seen IPlytics-based charts in various articles and tweets by top-notch analysts. So far I have heard only good things about their service.

The number of SEP declarations per month was calculated by counting each patent family at most once per generation (taken from the "technology generation" field); if a declaration involves multiple generations, then the highest generation was used. For each patent family, the earliest declaration date of all patents with the same generation was used. The chart then shows the cumulative number of declarations on a monthly basis.

Mr. Chen was elected RAN1 chair in August of 2017. The chart shows filings by other chairmen and vice chairmen (of RAN1 as well as RAN2 and SA2) who held those positions for a comparable period of time. The chart furthermore shows the numbers for some ex-RAN1 chairmen. Note that Mr. Chen, prior to becoming cahirman, served as vice chairmen form August 2013 to August 2017. The following table shows the periods of chairmanship or vice-chairmanship for the relevant persons (format: MM/YY):

NameWGchairmanvice chairman
Wanshi ChenRAN108/17-NOW08/13-08/17
Havish KoorapatyRAN110/17-NOW---
Younsun KimRAN1---08/17-NOW
Richard BurbidgeRAN208/15-NOW---
Frank MademannSA204/15-04/19---
Satoshi NagataRAN108/13-08/1711/11-08/13
Matthew BakerRAN108/09-08/1308/13-08/17

The disproportionately high number of SEP declarations by Mr. Chen strongly suggests that he's taking advantage of his current chairmanship and already did so with respect to his prior vice-chairmanship.

Issue #2: rule changes for correction requests

Correction requests are one type of contribution to a standard-setting process. Their primary purpose is to fix issues as early as possible, ideally before any user of standards-compliant devices will be affected. Under 3GPP rules, any formal changes to a specification of an already-adopted standard require the submission of CRs in the sense of correction requests.

It's a well-known fact that some participants in standard-setting like to inflate the number of CRs such as by filing separate CRs even when they could--and conveniently would be--combined. And there can be duplicative or conflicting CRs, which is why it's undoubtedly necessary to consolidate overlapping CRs at the editorial stage. But Mr. Chen imposed new rules that were simply designed to deprive participants of the credit they deserve for valuable contributions, while crediting mostly just the section editors, not the original contributors.

Here's an example of a CR that an editor employed by Motorola Mobility submitted, but a proposal of the verry same substance had previously been rejected only because of the new rules imposed on the RAN1 WG by the Qualcomm-employed chairman (this post continues below the document):

36213_CR1162_(Rel-15)_R1-18... by Florian Mueller on Scribd

Instead of allowing submitters to use the standard form all the time, Mr. Chen insisted on a limit of one submission per company during a given period, and even required submissions to be made in standard text files (as opposed to using the submission form, as Motorola Mobility did in the above example, which resulted in rejection only because they used the standard form)--and the net effect is basically that the editor will then submit the CR in the name of the editor's company, without any credit to the original submitter.

I've obtained an email sent by Mr. Chen to the entire WG on June 26, 2018 ("Draft agenda for RAN1#94"), in which he reminded everyone of the rule that they should not use the standard CR template and of the one-CR-per-company limit:

---START QUOTE---

  • For those agenda items marked with “no individual CRs” – PLEASE, no individual CRs, only text proposals. Please also do NOT use CR template for your contribution. Rather, just use regular word document with proposals & TPs embedded instead.

  • For those agenda items marked with “single contribution restriction” – PLEASE, follow it STRICTLY. For example:

    • If any companies have with more than one contribution in the respective agenda items, the 2nd contribution and onward will be marked in red color and will NOT be treated.

    • The contribution itself CAN NOT be a “shell” contribution, which only contains references to other multiple contributions located e.g., in “others’ section. Each contribution has to be self-contained. The “shell” contributions will be marked in red color and will NOT be treated.

---END QUOTE---

Mr. Chen's overly strict rules were criticized by ETSI's Kai-Erik Sunell in an email on August 30, 2018 for being inconsistent with standard 3GPP rules:

"P.S. Frankly speaking, it is difficult for me to understand why you are asked to prepare these corrections on behalf of other companies. 3GPP working methods do not define any 'CR editors' and all 36.xxx specifications are already under change control which means that the rapporteurs of these specifications cannot serve as specification editors anymore. You (and everyone else) are, of course, welcome to serve as informal 'CR editor' if you like to volunteer for something like that but then, please, fill in all the coversheet fields as if the CR captured your own corrections. Please see below an extract from TR 21.900 Technical Specification Group working methods, subclause 4.1.2, https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=555"

Mr. Sunell's title at ETSI is Mobile Competence Center Technical Officer. But ultimately the chairman decides the rules, and apparently the rules haven't really improved since.

"Credit where credit is due" is a good principle. It doesn't make sense that the RAN1 WG would credit only section editors of the specification but not the original submitters.

Of course, it does make sense for Qualcomm's purposes. But will the rest of the industry let one company set the rules for the most important 3GPP WG just because it decreases some other major patent holders' CR percentages? And how about Mr. Chen's disproportionately high number of SEP declarations?

I would encourage the membership of the RAN1 WG to raise the issues internally, and to think about the extent to which Qualcomm's corporate interests as a major patent holder and monetizer are aligned with the interests of the industry at large in encouraging and fairly crediting (with a view to future patent valuation discussions) all contributors.

Share with other professionals via LinkedIn:

Friday, July 13, 2012

HTC allegedly wants 'to extort a license from Apple to its patents on unique proprietary features'

Three weeks ago I reported on Apple's FRAND-related contract and antitrust counterclaims against HTC, which were removed from an ITC investigation to the United States District Court for the Eastern District of Virginia. At the time, only the legal concepts at the heart of Apple's counterclaims and a rough outline of the case-specific issues (Apple says that HTC and ADC, the company from which it acquired the two relevant and allegedly 4G/LTE-essential patents, failed to disclose those patents to standard-setting organizations and make a FRAND commitment) were known because Apple, out of an abundance of caution (ITC protective orders for confidential business information are very strict), requested that its entire counterclaims filing be sealed. But a competition watcher working for MLex, a great subscription-based service for antitrust issues, formally opposed the sealing of the document, and HTC has now made a redacted version available through a public filing.

The issues raised by Apple in this litigation validate lawmakers' and regulators' concerns over ITC import bans based on standard-essential patents (SEPs). In a nutshell, the story that Apple's counterclaims filing tells is that

  • ADC Telecommunications participated in various 4G/LTE standard-setting processes but never disclosed those two SEPs (thus never made a FRAND licensing promise) throughout the years,

  • only to pitch them to HTC (and possibly other companies who declined or made lower bids) as a strategic weapon to threaten Apple with injunctions against its 4G/LTE-compatible products and force it into a cross-license agreement under which HTC would get a license to Apple's iPhone- and iPad-related non-standard-essential patents.

Apple says HTC's objective is "to delay, disrupt or eliminate Apple products from competing in the downstream markets and/or to attempt to extort Apple to give up its own valuable, patented technology on unique product features in unrelated technology markets". Allegedly, the relevant patents "were being offered to HTC to attempt to extort a license from Apple to its patents on unique proprietary features that were not related to standards". In order to thwart this scheme, Apple wants an injunction against HTC's assertion of those two 4G/LTE patents.

Apple believes that ADC and HTC set the price of the two patents ($75 million) just below one of the thresholds for a review of the transaction by U.S. antitrust authorities. In some transactions involving standard-essential patents that were notified, the U.S. Department of Justice conditioned clearance on FRAND-related commitments -- something that ADC and HTC wanted to avoid. Apple argues that the transaction value was nevertheless above at least one other threshold.

Apple says that "on May 25, 2012, HTC served responses to Apple's contention interrogatories, and for the first time specifically accused Apple of infringing the ADC patents based solely on the fact that Apple devices contain baseband chips that implement the LTE standard". I see company argue on the basis of specifications of standards (as opposed to the technical details of a particular implementation, which would have to be reverse-engineered) all the time in Germany. Apple is right that someone who does this implies that his patent is standard-essential: it's allegedly infringed by all implementations of the standard, obviating a reverse engineering effort.

The 4G/LTE standard was developed by the 3rd Generation Partnership Project (3GPP), whose "organizational partners" include six standards bodies such as ETSI and ATIS. "By virtue of its membership in one of the 3GPP organizational partners, a member company participates in 3GPP", Apple's filing says. If you're interested in further detail on this, here's how Apple's filing describes ADC's and later HTC's alleged efforts to hide the two SEPs at issue from the 3GPP:

"25. On information and belief, from at least 2000 to through at least 2005, ADC was a participant in the 3GPP standardization process through its membership in at least ETSI. ADC regularly sent a representative to 3GPP meetings. On information and belief, ADC continued as a member of ETSI even after its representatives ceased personal participation in 3GPP meetings. On information and belief, those individuals that participated in meetings included Tim Lock and Samuel Sida, who were employees of ADC Telecommunications Ltd., a subsidiary of ADC located in the United Kingdom. On information and belief, those ADC employees participated in 3GPP working group meetings, through ADC's membership in at least ETSI.

26. On information and belief, ADC and later HTC, as members of ETSI, have participated in 3GPP standard-setting working groups in formulating LTE standards. On information and belief, HTC began participating as a member of 3GPP in August 2008. HTC continues to participate in 3GPP meetings on continued standardization relevant to LTE. Early meetings in this process evaluated competing technologies for use in the standards, and sought to choose from among several options that could serve the functions to be standardized. On information and belief, ADC participated in meetings of working groups that specifically discussed technology for use in standards that later became known as the '36 Series.' The '36 Series' is an LTE standard that currently includes, among other requirements, TS 36.100, 101, 211, 212, 213, 221, 300, 321, 331 and 523, and relate to TR 25.892 (hereinafter individually and collectively referred to as the 'LTE Standard'). Work on new LTE standards continues to evolve from this earlier work. The working group originating work on the LTE Standard was setting the direction for the future development of standards for LTE compliant networks and products, which has continued and continues through the present time. On information and belief, had ADC disclosed its IPR either at the inception of this work when it actively attended meetings, or any time afterward when it was aware that the standards were under consideration, then either the working group, 3GPP, and ETSI or any or all of them, could have considered alternatives rather than the product specification chosen, or developed or modified the specifications to avoid the IPR now alleged to be essential, or ADC would have been required to commit to license on FRAND terms.

27. On information and belief, despite being an active member of 3GPP and ETSI at the time the standards for LTE were being developed, ADC failed to disclose the '219 and the '944 patents, or the patent applications that resulted in those patents, or any of the patents and patent applications or other IPR related to the '219 and '944 patents, at any time, even though its representatives in the process believed the '219 and '944 patents, or the related patents and patent applications, were Essential IPR and covered or may have covered all or part of the standards in development.

28. On information and belief, working groups began working on aspects of the LTE Standard at least since May 2005. The 36 Series LTE Standard, which implements technologies that are purportedly covered by the ’219 and ’944 patents, was frozen or 'locked in' by no later than December 2008. On information and belief, ADC knew the LTE Standard was in development even after it no longer actively attended meetings, and believed its IPR would block implementation of the standard, as the standard was brought to completion. Since then and to the present day, working groups continue to work on enhancements, which build on the previously adopted standard. HTC continues to participate in this work, but has not disclosed the '219 and '944 patents (or any of the related patents or patent applications) even though it now effectively alleges in this Investigation they are each essential to implementation of the LTE Standard.

Based on internal HTC documents and discovery obtained in the present [ITC] Investigation, [redacted]. Ultimately, ADC took no affirmative steps in response and continued to remain silent as to the existence of the '219 and '944 patents or their applications, or related patents and patent applications or IPRs, to the SSOs, notwithstanding ADC’s knowledge of the work on the LTE standard then in progress.

30. [redacted] Since commencing its participation in 3GPP and ETSI, HTC has disclosed certain IPR as Essential IPR to 3GPP and ETSI. For example, on March 22, 2012, HTC submitted to ETSI an 'IPR Information Statement and Licensing Declaration' disclosing a number of patent publications as Essential IPR for the LTE Series 36 standards. [redacted] This disclosure omitted the previously acquired ’219 and ’944 patents, [redacted] Since having acquired the '219 and '944 patents from ADC in April 2011, HTC has failed to disclose those purportedly essential patents to 3GPP and ETSI in any filing or working group meeting. HTC continues to participate in 3GPP working groups and other groups, including those that deal with evolution and expansion of standards relevant to LTE compliant networks and products."

HTC is going to deny all of this, but Apple made these allegations after it obtained a lot of information through the discovery of documents in the ITC investigation that gave rise to these counterclaims.

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

Share with other professionals via LinkedIn: