Qualcomm now wants justice to force Apple suppliers to pay royalties

, my friends and my friends: apparently this fight between Apple and Qualcomm It is far from over much to the contrary: I suspect we are still in the early chapters of this Mexican soap opera. In today's episode we will see one more plot twist In this exciting story full of traits, twists and machinations from the exciting legal world.

If you remember correctly, in the previous episode we saw Qualcomm sue four Apple vendors (Foxconn, Pegatron, Wistron and Compal Electronics) because companies stopped passing on their royalties microchip giant; This is, of course, Ma's own decision to stop the transfer of this value to them.

Now, Qualcomm is not happy to include four companies other than Apple in the cake of the court battle: it wants to force suppliers to re-pay these royalties for better or worse, with or without Apple's money.


According to the financial newspaper Barron’s, the San Diego company has updated one of its current lawsuits with alleged evidence that Apple has instructed its suppliers not to pay any money Qualcomm covers them, further claiming that Ma has committed them to cover any monetary loss suffered. in the meantime.

Qualcomm says this is a strategy Cupertino designed to force a deal between the companies as soon as possible, as the microchip maker's loss of millions of dollars would make it difficult to move the millionaire process forward. According to the company's general counsel, Don Rosenberg, in a statement to the Axios:

We are confident that our contracts will be considered valid and enforceable, but in the meantime it is fair and equitable for companies that license our technologies to pay for the properties they are enjoying.

Neither Apple nor its suppliers have officially commented on this latest news. It should not be long, however, until we have the next update of this case, surely, the next chapter of the soap opera should see some counterattack of the Ma class before the recent attacks of Qualcomm. Let's wait.

via MacRumors