Iterated Prisoner’s Dilemma in software patents

This post contains some thoughts around software-patent strategies for large tech companies, in particular how the ability to block others’ applications seems to set up an Iterated Prisoner’s Dilemma and may change the strategic landscape for patents entirely.

Joel Spolsky writes of recent successes in blocking bad patent applications:

Micah showed me a document from the USPTO confirming that they had rejected the patent application, and the rejection relied very heavily on the document I found. This was, in fact, the first “confirmed kill” of Ask Patents, and it was really surprisingly easy.

and suggests that this may lead to a “Mexican Standoff” among major software companies:

My dream is that when big companies hear about how friggin’ easy it is to block a patent application, they’ll use Ask Patents to start messing with their competitors. How cool would it be if Apple, Samsung, Oracle and Google got into a Mexican Standoff on Ask Patents? If each of those companies had three or four engineers dedicating a few hours every day to picking off their competitors’ applications, the number of granted patents to those companies would grind to a halt. Wouldn’t that be something!

It seems to me that this would be something of a Prisoner’s Dilemma situation for the companies: Presumably, each of them is best off if it is the only one that can get any software patents (it defects by blocking the others, they cooperate by not setting up a patent-blocking team), better off if everyone can get patents (everyone cooperates by not having a blocking team), and worst off if nobody can get patents (everyone has a blocking team which they have to pay for). It is Iterated because the decision to block or not block can be made anew every month, or quarter, or whatever. So the question is, will these companies filled with smart people be able to recognise an IPD, and will they cooperate?

Some factors to consider: Setting up a patent-blocking team requires some small amount of effort, so inertia is in favour of cooperation. On the other hand, many individual engineers at these places are likely out of sympathy with the patents that their managers insist on, and may be delighted to push the ‘D’ button under the guise of sabotaging their competitors. (And at least some of the major tech companies have 20% time or equivalents, so there wouldn’t even be much inertia to overcome—just decide to do it!)

Another point is that this is a multiplayer game, but it only takes two companies to block everyone: For example, Google blocks everyone except Google, and then exactly one company needs to retaliate to make the block complete. This does of course raise the question of who is going to step forward and pay for the retaliation; but on the other hand, the cost appears small. The free-rider problem exists, but it does not seem to be large.

Another point: The ease of patent-blocking may change the strategic landscape entirely, by making it not worth the effort to file for patents in the first place. It appears to me that everyone involved knows that these patents are worthless. They file them for some mix of prestige, “everyone does it”, and ability to retaliate if someone else sues using _their_ worthless overbroad patents. Presumably it is only worth expending engineer time on this because the patents are very likely to be granted; conversely, it’s only worth having patent-blocking teams if a lot of worthless applications are filed. The equilibrium is not clear to me, but it seems that it will have to shift at least slightly in the directions of having engineers do more bug-fixing and less patent-filing.