<p>
    But software patents are also detrimental to <strong>competition</strong>. Especially if they are <em>used</em> in an anticompetitive way. The <a href="http://en.wikipedia.org/wiki/European_Union_Microsoft_competition_case">Microsoft case</a>, once again, gives us good food for thought and leads me to think that there is more than one antitrust concern over the sale of <strong>Nortel patents</strong>. May I attempt a few short answers to reasonable questions that are lingering around when I mention the antitrust issue. I plead guilty of omitting much of the necessary background.
  </p>
  
  <p>
    <!--break-->
  </p>
  
  <h3>
    Q: Nortel patents were there already, why should they create concerns?
  </h3>
  
  <p>
    <b>A</b>: because they have not been paid for their &#8220;market&#8221; value, but because of their <b>strategic</b> value. Buyers (or some of them) are arguably not interested in trading them at fair market value (estimated USD 800M), but as a way to stifle the competition from a <strong>disruptor</strong> with a different business model. You can't compete with a <strong>free product</strong> and you cannot trade your product for free? Make it a paid-for product and it's not that much of a disruptor anymore.
  </p>
  
  <h3>
    Q: But why should Google not pay for patents if anybody else is doing it?
  </h3>
  
  <p>
    <b>A</b>: Again, we must think out of the box. Google has bought a company, On2, just to have all of their rights on a codec, and donated it as <a href="http://www.webmproject.org/">WebM</a>. It bid <strong>3.14</strong> (or pi) <strong>billion USD</strong> to have the same Nortel patents, four times their estimated market value (for the same and opposite reasons as the successful bidders). And it still planned to keep Android [F|f]ree. If the consortium valued them even more, it's because it thinks it can extract much more value out of them. That is, as I said, unrelated to the remuneration on the investment to produce an innovative idea (if any), it is about the <strong>strategic</strong> value.
  </p>
  
  <p>
    <strong>Controlling a platform</strong> is much more lucrative than just the revenues deriving from selling some software. There is the <strong>network effect</strong>, everything is about network effects. Network effects are the air that inflates the IT bubble.
  </p>
  
  <h3>
    Q: yet isn't the &#8220;fair market price&#8221; the one that is set&#8230; by the market?
  </h3>
  
  <p>
    <b>A</b>: This is true, but only if the market is <strong>free</strong> to set the price and if you are trading <em>quid pro quo</em>. If you want to trade your patent rights in a normal fashion, you have a straightforward and correct game: you threaten litigation and ask for a price. If the price is too high, you face the risk to be forced to litigate, then you could face counterclaims an lose your patents, or simply lose the case and have no royalties. So you set a price as high as possible, but eventually settle for something reasonable, because if you set it too high you increase the odds of losing much more than your marginal gain. There is <em>some </em>balance in it, marketwise.
  </p>
  
  <p>
    In the game where platform dominance and fighting against a disruptor are concerned, the <strong> game</strong> is totally <strong>different</strong>. You have more than an <strong>incentive</strong> to set the price <strong> arbitrarily high</strong>, eventually hoping the price is not met, or not bothering at all to set a price. This is the fundamental premise of all the antitrust-based forced licensing decisions, form <em>Magill</em> to <em>Microsoft</em>. You can end up with <strong>4 different scenarios</strong>, at least, or some combination and permutations:
  </p>
  
  <p>
    <strong>Scenario 1</strong>: the disruptor <strong>pays</strong> the arbitrarily high price, you gain an awful lot of money, yet this is your <strong>worst-case</strong> scenario, because still the disruptor might remain in good business.
  </p>
  
  <p>
    <strong>Scenario 2</strong>: you don't trade with the disruptor, but with its <strong>clients</strong>. Maybe you start with setting some example by convincing the least reluctant to give in first.  You therefore extract revenues from the clients of the disruptor <em>and</em> increase the cost its product. So you get paid <em>and</em> you diminish the attractiveness of the product for the disruptor. It's a win-win strategy: if the clients pay the price, you get paid and the product is less appealing; if you further increase the price, you don't get paid because you scare the client the disruptor out of its competing product, and you win even bigger.
  </p>
  
  <p>
    <strong>Scenario 3</strong>: the disruptor refuses to pay, you <strong>sue</strong> it and you <strong>win</strong>: best case scenario, you put the disruptor out of business. The disruptor hence must find a way around your patents (and facing possible new litigation for a patent which held through judicial scrutiny) or it shall pay through the nose, if you are gracious enough to set a price, whatever price.
  </p>
  
  <p>
    <strong>Scenario 4</strong>: the disruptor refuses to pay, you <strong>sue</strong> it and you <strong>lose</strong>. Yet again you win overall, because you have engaged your opponent through an ordeal of immense magnitude, scaring the hell out of its clients as in Scenario 2, you have obtained some revenues nonetheless through Scenario 2 and you have implanted the idea that your opponent's product is not that convenient as the price tag might suggest. This is a classic <a href="http://en.wikipedia.org/wiki/Fear,_uncertainty_and_doubt">FUD</a> strategy, and if your opponent is lucky enough, it will only last one-two years, reducing much of the snowball effect of its disruptive competition.
  </p>
  
  <p>
    In all cases, the value extracted from the patents is totally unrelated to the merit of the patent, and it is not a fair market price. The situation presents a <strong>huge incentive</strong> to increase the price to a multiple of its fair market value.
  </p>
  
  <p>
    <em>As always, comments are welcome through my identi.ca federated instance: <a href="http://status.piana.eu/carlopiana">http://status.piana.eu/carlopiana</a></em>
  </p>
</div>