Source files of fsfe.org, pdfreaders.org, freeyourandroid.org, ilovefs.org, drm.info, and test.fsfe.org. Contribute: https://fsfe.org/contribute/web/ https://fsfe.org
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

ps.en.xhtml 32KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626
  1. <?xml version="1.0" encoding="UTF-8" ?>
  2. <html>
  3. <head>
  4. <meta name="author-name-1" content="Georg Greve" />
  5. <meta name="author-link-1" content="/about/greve'/greve.html" />
  6. <meta name="publication-date" content="2008-12-02" />
  7. <meta name="pdf-link" content="/projects/os/ps.en.pdf" />
  8. <title>FSFE - Analysis on balance - Standardisation and Patents</title>
  9. </head>
  10. <body>
  11. <h1>Analysis on balance:<br />Standardisation and Patents</h1>
  12. <p class="indent"><em>This paper provides an analysis of the
  13. interaction of patents and standards and finishes with some
  14. concrete proposals to address the most pressing issues. It was
  15. written under the assumption of very little background knowledge,
  16. and therefore provides some of the background necessary to
  17. understand the issue. An expert in the field should be able to
  18. skip the Background section.
  19. </em></p>
  20. <h2>Introduction</h2>
  21. <p>Software patents have been a hugely controversial debate, with
  22. lines of battle drawn primarily between large corporations holding
  23. large patent portfolios and engaged in multiple cross-licensing
  24. deals, and the Have-Nots, entrepreneurs, small and medium
  25. enterprises, and software users from the student using GNU/Linux all
  26. the way to institutional users in governments.</p>
  27. <p>This debate got a lot quieter with the rejection of the software
  28. patent directive in 2005. Its place in the headlines was taken by
  29. other debates, such as standardisation. Open Standards have been a
  30. buzzword for years, but never has this term been discussed more
  31. intensively.</p>
  32. <p>On Wednesday, 19 November 2008, both debates met in Brussels at a
  33. workshop titled
  34. "<a href="http://ec.europa.eu/enterprise/newsroom/cf/itemshortdetail.cfm?item_id=3371">IPR
  35. in ICT standardisation</a>", although "Patents in ICT
  36. standardisation" would have been a more suitable name because the
  37. discussion was exlusively about the interaction of patents and
  38. ICT standardisation.</p>
  39. <p>Patents and standards are fundamentally at odds, so many people
  40. call for a balance between patents and standards. This article
  41. comments upon the workshop and explains why standards should prevail
  42. over patents at least in the area of software.</p>
  43. <h2>Background: Patents &amp; Standards 101</h2>
  44. <p>The idea of patents is not new. Its roots lie in the royal
  45. "litterae patentes" that conferred exclusive rights to certain
  46. people. Democratic governments eventually took the position of the
  47. monarchs, and patent legislation has evolved over time, but the
  48. fundamental characteristics of what is a patent have not
  49. changed.</p>
  50. <p>Succinctly put, a patent is a monopoly granted for a limited time
  51. by the government on behalf of its citizens.</p>
  52. <p>The term monopoly has many negative connotations, and for good
  53. reason. A monopoly stifles innovation and increases price due to the
  54. absence of competition. On these grounds a monopoly is generally
  55. understood to be to the detriment of economy and society. It is not
  56. illegal to obtain a monopoly, but society has a legitimate interest
  57. in limiting abuse of the power that a monopoly confers, and seeks to
  58. achieve this through antitrust law.</p>
  59. <p>The monopoly right created by a patent brings with it all side
  60. effects of a monopoly. It is granted by the state because it is
  61. understood that the absence of patents might prevent publication of
  62. breakthroughs, which is understood to be more harmful than granting
  63. the patent monopoly.</p>
  64. <p>This initial patent deal is based upon disclosure, so that others
  65. can learn from and build upon a new idea. Lack of useful disclosure
  66. or advancement of public knowledge translates into the granting of a
  67. monopoly with no return for society.</p>
  68. <p>Like patents, standards are closely related to disclosure. The root
  69. of the word standard appears to go back to heraldry, where it refers
  70. to a symbol that is used to make a rallying point visible in
  71. battle.</p>
  72. <p>Modern use of the term keeps that meaning of publicly visible point
  73. of reference, although it has been transferred to other areas. So
  74. among other things it is understood as "<em>something established by
  75. authority, custom, or general consent as a model or example</em>" or also
  76. "<em>a structure built for or serving as a base or support.</em>"
  77. (from <a href="http://www.merriam-webster.com/dictionary/standard">Merriam-Webster
  78. On-line dictionary</a>).</p>
  79. <p>In Information and Communication Technologies, a standard has both
  80. the above meanings. According to
  81. the <a href="http://www.bsi-global.com/en/Standards-and-Publications/About-standards/What-is-a-standard/">British
  82. Standards Institution</a> (BSI), a standard is "<em>an agreed, repeatable
  83. way of doing something. It is a published document that contains a
  84. technical specification or other precise criteria designed to be
  85. used consistently as a rule, guideline, or definition. [...] Any
  86. standard is a collective work. Committees of manufacturers, users,
  87. research organizations, government departments and consumers work
  88. together to draw up standards that evolve to meet the demands of
  89. society and technology. [...]</em>"</p>
  90. <p>The underlying idea is that a standard establishes common ground,
  91. it provides the means for interoperability and competition. This is
  92. especially true for ICT due to their strong networking effects. If
  93. all participants in an ICT market adhere to the same standards and
  94. make an effort to guarantee interoperability, not only can customers
  95. choose freely between various products and services, they can also
  96. exchange information with one another without problems.</p>
  97. <p>In contrast, absence or failure of standardisation warps networking
  98. effects in a way that monopolisation becomes almost certain. Users
  99. of one product or service could only interoperate with users of the
  100. same product or service. Over time, one solution would attain such
  101. a large user base that other users are de-facto left with the choice
  102. to join this group, or be unable to communicate fully with the
  103. majority of users. This could for instance be achieved by bundling
  104. software with a predominant hardware platform.</p>
  105. <p>So standards are largely an instrument to enable competition for
  106. the public benefit. The purpose of standards is intrinsicly
  107. anti-monopolistic.</p>
  108. <p>It is also pro-innovative. Since deviation from a standard
  109. automatically breaks it, standardisation and innovation seem opposed
  110. goals, and to some extent they are. But where all changes are done
  111. in consensus between implementors, the result is an updated version
  112. of the standard available to all. The second path is innovation on
  113. top of the standard, using the standard as a base for innovation
  114. rather than innovating inside the standard.</p>
  115. <p>Due to its global, consensus-driven nature, the first process is
  116. comparatively slow. Another problem is the substantial barrier to
  117. entry into the standards process. As a result, large companies are
  118. overrepresented in comparison to small and medium enterprises (SME).</p>
  119. <p>The second path is open to everyone, private person, SME, or large
  120. industry. It is also limited only by the speed of development of the
  121. team making the innovation. If the innovation was made by just one
  122. party, there will be a temporary monopoly. But given a certain
  123. maturity, the innovation is then likely to be formalised into a
  124. standard again, forming the base for the next innovation to be built
  125. on top.</p>
  126. <p>While the first path allows primarily for slow, small improvements,
  127. the second path allows for full participation of the economic
  128. majority and is much better suited for groundbreaking ideas and
  129. arguably the more important to protect for society.</p>
  130. <h2>Conflict: Fundamentally opposed instruments</h2>
  131. <p>The fundamentally different goals for patents and standards
  132. surfaced multiple times during the debate, for instance in the
  133. speech of Mr Karsten Meinhold, chairman of the ETSI IPR Special
  134. Committee,
  135. <a href="http://ec.europa.eu/enterprise/newsroom/cf/document.cfm?action=display&amp;doc_id=3635&amp;userservice_id=1&amp;request.id=0">
  136. who summarised it</a> as "<em>IPRs and Standards serve different
  137. purposes: IPRs are destined for private exclusive use, Standards are
  138. intended for public, collective use</em>".</p>
  139. <p>Both patents and standards derive their justification from the
  140. public benefit, yet upholding one deprives the other of its
  141. function. Standards seek to counteract monopolies, patents establish
  142. them. Or, as Tomoko Miyamoto, Senior Counsellor of the Patent Law
  143. Section in the World Intellectual Property Organization (WIPO) said
  144. in
  145. <a href="http://ec.europa.eu/enterprise/newsroom/cf/document.cfm?action=display&amp;doc_id=3633&amp;userservice_id=1&amp;request.id=0">
  146. her presentation</a>:
  147. Patent thickets and patent hold-ups may arise from
  148. certain forms of legitimate exploitation of the exclusive rights
  149. conferred by patents.</p>
  150. <p>In other words: Conferring these exclusive rights is the intended
  151. function of the patent system, and legitimate usage of these rights
  152. brings about consequences of patent thickets and patent
  153. hold-ups. Allowing patents on standards consequently is an
  154. intentional act to grant monopolies on standards to certain parties
  155. that includes the right to block implementation by other
  156. parties.</p>
  157. <h2>Ex-Ante Disclosure</h2>
  158. <p>There are multiple attempts through which the standardisation
  159. community has tried to mitigate these effects over the years. One of
  160. these mechanisms is called "Ex-Ante Disclosure." The parties working
  161. on a standard use this mechanism to commit to licensing terms while
  162. the standard is still being drafted. If these terms are not
  163. acceptable to the other parties working on the standard, the
  164. technology that is covered by the patent is not included in the
  165. standard.</p>
  166. <p>What are acceptable terms is highly subjective. A large corporation
  167. with big patent portfolio and existing cross-licensing agreement
  168. with the holder of the relevant patents might consider adding one
  169. more patent to the agreement a minor inconvenience. The same
  170. situation looks substantially different from the perspective of a
  171. small or medium enterprise that typically has at most a small patent
  172. portfolio and has to expect extortionate licensing.</p>
  173. <p>Since SMEs are strongly underrepresented in standardisation, Ex-Ante
  174. Disclosure is likely to bring more satisfactory results to large
  175. corporations with large patent portfolios that compete in the same
  176. area. The economic majority generally has no say about the
  177. acceptability of the terms.</p>
  178. <p>Another issue of ex-ante disclosure is difficult enforcement, as
  179. Suzanne Michel, Assistant Director Office of Policy and Coordination
  180. of the U.S. Federal Trade Commission
  181. (FTC)
  182. <a href="http://ec.europa.eu/enterprise/newsroom/cf/document.cfm?action=display&amp;doc_id=3631&amp;userservice_id=1&amp;request.id=0">
  183. pointed out in her presentation</a>.
  184. The FTC had found that <a href="http://en.wikipedia.org/w/index.php?title=Rambus&amp;oldid=251605519">Rambus
  185. Incorporated</a> had joined and attended standardisation meetings of
  186. the <a href="http://en.wikipedia.org/wiki/JEDEC">Joint Electron
  187. Device Engineering Council (JEDEC)</a> in order to modify their
  188. patent applications to cover technology that was under discussion
  189. for inclusion in future standards. In the opinion of the FTC, this
  190. behaviour was deceptive, violated JEDEC's disclosure policy, and
  191. illegaly gave Rambus monopoly power.</p>
  192. <p>The <a href="http://en.wikipedia.org/wiki/United_States_Court_of_Appeals_for_the_District_of_Columbia_Circuit">D.C. Circuit
  193. Court</a> disagreed with the interpretation of the FTC in their
  194. April 2008 decision. According to Ms Michel, the court said that
  195. avoiding so-called
  196. "<a href="http://en.wikipedia.org/wiki/Reasonable_and_Non_Discriminatory_Licensing">Reasonable
  197. and Non-Discriminatory</a>" (RAND) licensing terms does not
  198. constitute abuse, and that there is no proof that JEDEC would have
  199. avoided technologies if it had known that Rambus was planning to
  200. use its patents to the fullest extent allowed by law. The court
  201. also expressed reluctance to make patents unenforceable based on
  202. vague disclosure policies.</p>
  203. <p>Both patents and standards derive their justification from the
  204. public benefit. There was no additional disclosure of new technology
  205. provided by the patents that Rambus filed on the standards that were
  206. about to be published. Giving Rambus monopoly power over standards
  207. developed by JEDEC is also detrimental to public interest. So it
  208. seems likely that a full public interest evaluation of this
  209. situation would give that indeed the public interest did not prevail
  210. in this case.</p>
  211. <p>So it would appear that the FTC was correct in its evaluation, and
  212. so was the court, because establishing time-limited monopolies is
  213. the very purpose and function of patent law. The role of courts does
  214. not extend to the undoing of laws and most legislators have not
  215. given the public interest conflict between patents and standards
  216. consideration.</p>
  217. <p>JEDEC has meanwhile updated its disclosure policy, which may help
  218. to avoid similar issues in the future. Considering the value that
  219. patent law has in relation to standardisation for many courts, only
  220. a future court case can demonstrate whether the issue has been
  221. resolved in a way that holds up to formal legal review.</p>
  222. <h2>(F)RAND</h2>
  223. <p>This is true for all standardisation bodies that require ex-ante
  224. disclosure, which most of them don't. Instead the majority of bodies
  225. appear to rely on purely voluntary disclosure and the assurance that
  226. patent holders involved in the process will agree to so-called RAND
  227. or FRAND
  228. ("<a href="http://en.wikipedia.org/wiki/Fair,_Reasonable_and_Non_Discriminatory_Licensing">Fair,
  229. Reasonable and Non Discriminatory</a>") terms.</p>
  230. <p>One common criticism of (F)RAND terms is the lack of a definition
  231. of what is reasonable and for whom. During the 2006 Internet
  232. Governance Forum (IGF) in Athens, Susy Struble of Sun Microsystems
  233. <a href="http://www.youtube.com/watch?v=CNUdqEqjbOQ">pointed out</a>
  234. that what is reasonable for one party may not be reasonable to
  235. another.</p>
  236. <p>Licensing practices do indeed vary, and are influenced by various
  237. factors, including, but not limited to, whether or
  238. not a company has a stake in the relevant market, and how
  239. aggressively it pursues its patent revenues.</p>
  240. <p>Additionally, patents can be sold or acquired as part of a business
  241. restructuring or acquisition. A future patent holder may consider
  242. different terms reasonable, so could a patent holder who did not
  243. participate in the standardisation process and never committed even
  244. to RAND terms.</p>
  245. <p>RAND terms generally amount to a vague assurance to license upon
  246. request. Such an assurance does not constitute a perpetual license
  247. on the patent and is not valid for the new holder of a patent. So a
  248. new holder can choose freely how to enforce the patent, including
  249. patent hold-ups on all existing implementations of the standard.</p>
  250. <p>As Ms Miyamoto from WIPO pointed out, a patent hold-up is a
  251. legitimate and intended use of the patent system. So even in a RAND
  252. regime, there is a substantial amount of uncertainty that invariably
  253. favors large companies, which not only have deeper pockets, they
  254. also have larger legal departments and patent portfolios.</p>
  255. <p>It is this uncertainty that has caused great frustration among SMEs,
  256. which Charles Schulz of Ars Aperta summarised as RAND referring to
  257. "RANDom licensing at the sight of competitors."
  258. In
  259. <a href="http://ec.europa.eu/enterprise/newsroom/cf/document.cfm?action=display&amp;doc_id=3639&amp;userservice_id=1&amp;request.id=0">
  260. his presentation</a>,
  261. Mr Schulz also pointed out that (F)RAND terms are
  262. discriminating against Free Software. Even RAND terms linked to zero
  263. royalties, the so called RF-on-RAND ("Royalty Free on RAND"),
  264. RAND-RF ("RAND Royalty Free") or RAND-Z ("RAND with Zero royalties")
  265. terms often exhibit the same problems because they do not permit
  266. sublicensing.</p>
  267. <p>Free Software
  268. (<a href="/about/basics/freesoftware">a.k.a. Open
  269. Source, FOSS or FLOSS</a>) is based on the principle that every
  270. living person and every legal entity can be a user, developer,
  271. distributor, or any combination of the above. Only conditions which
  272. permit this to take place are acceptable to Free Software, which is
  273. <a href="http://www.flossimpact.eu/">estimated</a> to reach 32% of
  274. all IT services and 4% of European GDP by 2010.</p>
  275. <p>In
  276. <a href="http://ec.europa.eu/enterprise/newsroom/cf/document.cfm?action=display&amp;doc_id=3641&amp;userservice_id=1&amp;request.id=0">
  277. her presentation</a>,
  278. Amy Marasco, General Manager Standards Strategy of
  279. Microsoft, emphasised that she does not consider Free Software a
  280. business model. That is true to the same extent that proprietary
  281. software itself is not a business model. Business models are what is
  282. built on top of both Free Software and/or proprietary software.</p>
  283. <p>Ms Marasco continued to point out that all these business models
  284. are legitimate. And while there are strong differences in opinion
  285. about which software model is the better and more sustainable choice
  286. for economy and society, from the perspective of a political
  287. analysis of standards, all business models based upon proprietary
  288. software, Free Software, or a mixture of the two need to be
  289. considered valid and legitimate.</p>
  290. <p>As mentioned before, the Free Software related parts of European
  291. GDP are estimated to reach 4% by 2010. All parties agree that all
  292. business models, including those incorporating Free Software, are
  293. legitimate. This raises the question whether it can be considered
  294. Fair, Reasonable and Non-Discriminatory to exclude this legitimate
  295. part of economy by choice of patent licensing terms.</p>
  296. <h2>Harm from exclusion?</h2>
  297. <p>The situation bears an odd semblance to the situation with
  298. <a href="http://en.wikipedia.org/wiki/Counterfeit_drugs">counterfeit
  299. pharmaceuticals</a>, where the argument for patent enforcement is
  300. generally accompanied by public health considerations. But only
  301. effective pharmaceuticals that are identical to the patented product
  302. would actually violate the patent. Health risks arise primarily
  303. where the patents are not being violated.</p>
  304. <p>In standards, the situation is somewhat similar. If patents are
  305. part of a standard, only an implementation that is covered by the
  306. patents provides an effective antidote to monopolisation. Having to
  307. circumvent patents will generally break standards compliance and harm the
  308. public benefit that is the driving force behind standardisation.</p>
  309. <p>So patents in standards have the potential to make full
  310. interoperability impossible for legitimate businesses in some
  311. markets. As the aforementioned
  312. BSI <a href="http://www.bsi-global.com/en/Standards-and-Publications/About-standards/What-is-a-standard/">points
  313. out</a>: "Standards are designed for voluntary use and do not impose
  314. any regulations. However, laws and regulations may refer to certain
  315. standards and make compliance with them compulsory."</p>
  316. <p>Once a technology has been standardised, certain choices are no
  317. longer made for technological quality. Even where a better solution
  318. exists that would have the additional value of not violating a
  319. potential patent on the standard, an implementor would choose to
  320. follow the technologically inferior standard in order to have full
  321. access to the market. Such a case reverts the initial idea of
  322. patenting: The technology is valuable because it is patented, not
  323. patented because it is valuable.</p>
  324. <p>There are also cases where certain standardisation organisations,
  325. e.g. the <a href="http://www.iso.org">International Organisation for
  326. Standardisation</a> (ISO) have a privileged position with
  327. governments for procurement decisions. Due to patents and
  328. insufficient (F)RAND conditions, not all standards privileged in
  329. this way can be implemented by all legitimate market participants
  330. that should be able to compete in public tenders.</p>
  331. <p>So through the special privilege for organisations like ISO which
  332. accept terms insufficient to guarantee competition, the monopoly
  333. right conferred by patents translates into an oligopoly or even a
  334. monopoly for public procurement. This exclusion of competition from
  335. tenders by means of patents on standards is detrimental to the
  336. public benefit because it leads to higher prices and consequently
  337. higher taxes.</p>
  338. <p>Remedies for this situation would have to address the way in which
  339. governments grant procurement preferences to standards, the way in
  340. which patents are handled in standards, the patent system itself, or
  341. a combination of all of the above.</p>
  342. <h2>Attempted remedies</h2>
  343. <p>Good patent research costs around 100.000 EUR per case according to
  344. Rigo Wenning, Legal Counsel &amp; Patent Policy Team Contact of the
  345. W3C/ERCIM who spoke about
  346. "<a href="http://ec.europa.eu/enterprise/newsroom/cf/document.cfm?action=display&amp;doc_id=3636&amp;userservice_id=1&amp;request.id=0">
  347. Standards, Patents and the Dynamics of Innovation on the Web</a>." The W3C is
  348. indeed the only Standards Setting Organisation (SSO) that has a
  349. sufficient patent policy for its standards in order to accomodate
  350. all legitimate business models.</p>
  351. <p>From the perspective of most SMEs, 100.000 EUR patent research costs
  352. are prohibitively expensive. But even large companies will find this
  353. cost considerable, which is only one of the cost generators. More
  354. damage can be caused by injunctions against a product, or claims for
  355. damages. In
  356. his
  357. <a href="http://ec.europa.eu/enterprise/newsroom/cf/document.cfm?action=display&amp;doc_id=3646&amp;userservice_id=1&amp;request.id=0">
  358. presentation of IBM's "SoftIP"</a> concept, Roger Burt, Senior Counsel of IBM
  359. Europe introduces the issues with a quote from a BSA et al. Amicus
  360. brief in eBay v MercExchange. The quote summarises the problems of
  361. large industry rather well:</p>
  362. <quote class="indent"><em>"Technology products typically consist of hundreds or
  363. thousands of patented components. It therefore is impossible for
  364. technology companies to investigate all of the patents, and pending
  365. patent applications that may be relevant to a new invention (product),
  366. notwithstanding their best efforts to do so. When, as frequently
  367. occurs, the claim of infringement is not made until after the new
  368. product is released or the industry standard has been adopted,
  369. designing around the claim is no longer a realistic option. Because an
  370. injunction will issue automatically upon a finding of infringement –
  371. even if the claim relates to an insignificant part of the product –
  372. the target of the claim is forced to pay an extortionate settlement in
  373. order to preserve its business."</em></quote>
  374. <p>Another attempt to keep patents fees from becoming exorbitant even
  375. for the largest corporations was introduced by Tim Frain, Director
  376. IPR regulatory affairs, Nokia in his presentation about
  377. "<a href="http://ec.europa.eu/enterprise/newsroom/cf/document.cfm?action=display&amp;doc_id=3649&amp;userservice_id=1&amp;request.id=0">
  378. FRAND Best Practice</a>."
  379. Mr Frain advocates a system based on "Aggregated
  380. Reasonable Terms" &amp; "Proportionality" (ART+P).</p>
  381. <p>The underlying idea of this approach is that if every patent holder
  382. individually charges patent fees they consider Fair, Reasonable and
  383. Non-Discriminatory, the resulting fees may easily add up to 50% or
  384. more of the cost for the end product. So all patent holders should
  385. commit ex-ante that the aggregate licensing cost for all patents
  386. should be reasonable. As an example, Mr Frain cited that in Nokia's
  387. view, the patent licensing fees on the communication technology for
  388. mobile phones should be below 10% per handset.</p>
  389. <p>Both approaches are attempts to control the use of monopolies
  390. granted by patents and as such are trying to get voluntary buy-in
  391. from other parties to not exercise rights that the patent system has
  392. granted them.</p>
  393. <p>Unfortunately they both fall short of the criterion of
  394. non-discrimination against legitimate business models, and the ART+P
  395. approach also has the practical weakness that convergence joins more
  396. than one kind of technology per device, so the total patent
  397. royalties on a smart phone may still reach 50% even if the costs for
  398. GSM &amp; Co are limited to 10%. But even these 10% can be
  399. considerable for laptops with included UMTS modems, or embedded
  400. devices, an area in which the profit margins are typically far below
  401. 10%.</p>
  402. <p>To put it in the form of a controversial question: Is it fair and
  403. reasonable that patent holders receive a higher monopoly rent than
  404. an innovative company stands to gain by bringing out a new product
  405. and bearing all the risk associated with it?</p>
  406. <h2>Cui bono?</h2>
  407. <p>So who benefits? As explained before, patents are designed as a trade-off. Their
  408. benefits are often explained with the lone inventor having a genius
  409. idea. Would it be fair if this inventor published the idea only to
  410. see a large company bring it to market faster than the inventor
  411. could, with no financial reward for the inventor? Most people would
  412. agree this is not fair.</p>
  413. <p>In the absence of patents, such an inventor could only choose
  414. between accepting fate, or keeping the innovation secret for as long
  415. as possible while trying to bring it to market. Patents grant a
  416. temporary monopoly for the inventor in return for publication, such
  417. that the inventor can find investors, set up a company, finish
  418. product development, bring it to market, and enjoy a head start
  419. before others can compete normally.</p>
  420. <p>This mechanism seems to have worked reasonably well for some time
  421. in the past. But some basic parameters have changed, while patents
  422. have been extended in an essentially unreflected way to more
  423. areas. This is particularly true for software, where patents play no
  424. meaningful role in disclosure, breaking the patent deal for society
  425. whereas the time of bringing new innovation to the market and the
  426. time between groundbreaking discoveries has been decreasing.</p>
  427. <p><a href="http://en.wikipedia.org/wiki/Ray_Kurzweil">Raymond
  428. Kurzweil</a> found an exponential pattern in innovation reaching back
  429. all the way to single-cell organisms. Concluding that this must be
  430. a universal principle, Mr Kurzweil has been
  431. making <a href="http://en.wikipedia.org/wiki/Predictions_made_by_Raymond_Kurzweil">predictions</a>
  432. for the future of which several have turned out to be largely
  433. accurate so far. When applying this principle to patents, from the
  434. constant duration of the monopoly guaranteed follows an
  435. exponential growth of the value of an individual patent.</p>
  436. <p>The price that society is paying for granting patents has been
  437. <a href="http://en.wikipedia.org/wiki/Exponential_growth">growing
  438. exponentially</a> since the time that the initial patent bargain was
  439. struck. This would explain why the price for the patent system seems
  440. increasingly exorbitant with growing calls for reform, which have
  441. led to the recent announcement of the
  442. "<a href="http://www.ftc.gov/opa/2008/11/ipmarketplace.shtm">First
  443. in Series of Hearings on Evolving Intellectual Property
  444. Marketplace</a>" by the U.S. Federal Trade Commission (FTC).</p>
  445. <p>Remedies to this problem could be to decrease the lifespan of
  446. patents, adapt them to the specific situation in the field, and
  447. exclude fields from patenting in which patents provide no meaningful
  448. disclosure.</p>
  449. <p>When it comes to standards, it was An Baisheng, Deputy Director of
  450. the Division of Technical Regulations Department for WTO Affairs of
  451. the Chinese Ministry of Commerce who raised the question of public
  452. vs private benefit in his presentation titled
  453. "<a href="http://ec.europa.eu/enterprise/newsroom/cf/document.cfm?action=display&amp;doc_id=3632&amp;userservice_id=1&amp;request.id=0">
  454. Strike the Right Balance between Public and Private Interests in IPR in ICT
  455. Standardization</a>".</p>
  456. <p>Taking our "lone inventor" scenario above, the question that we'd
  457. have to ask for patents on standards is: Would it be fair if our
  458. inventor could prevent someone else from bringing to market an
  459. innovation of their own that somehow interacts with the initial
  460. invention? To make it less abstract: Should a patent on a typewriter
  461. extend to carbon copy paper that has the right size to be used in
  462. that typewriter? Most people would agree this goes too far.</p>
  463. <h2>Potential Remedies</h2>
  464. <h3>1. Interoperability trumps patent</h3>
  465. <p>During the software patent debate in the European Union there was
  466. consensus among SME, Free Software and big businesses
  467. representatives from companies such as IBM or Sun Microsystems that
  468. patents which limit or prevent interoperability should be unenforceable.</p>
  469. <p>In the European Union, this could be introduced into the ongoing
  470. Community Patent debate. On a global level, WIPO should consider
  471. this as part of its ongoing Development Agenda discussions.</p>
  472. <p>Once implemented, this would solve the most harmful side-effects
  473. for all legitimate business models and give interoperability and
  474. competition preference over monopoly rights. Considering the
  475. extraordinary networking effects that exist in this market, such a
  476. preference seems justified.</p>
  477. <h3>2. Update policy in SSOs</h3>
  478. <p>Secondly, Standard Setting Organisations (SSOs) could update their
  479. patent policies to ensure that their standards are usable in all
  480. business models. Many SSO representatives in the meeting maintained
  481. that it was not their place to mandate certain patent policies. At
  482. the same time,
  483. the <a href="http://www.itu.int/ITU-T/dbase/patent/patent-policy.html">Common
  484. Patent Policy</a> of ITU-T, ITU-R, ISO and IEC already states the
  485. principle that "<em>a patent embodied fully or partly in a
  486. Recommendation | Deliverable must be accessible to everybody without
  487. undue constraints.</em>" As this analysis demonstrates, current
  488. application of RAND falls short of that principle.</p>
  489. <p>There is additional precedence supplied by the common way in which
  490. SSOs protect standards against potential later claims from Copyright
  491. holders by requiring all participants to a standardisation process
  492. to assign their copyright to the SSO. Applying appropriate similar
  493. measures on patents for similar reasons seems justified.</p>
  494. <h3>3. Provide intermediate and migration possibilities</h3>
  495. <p>Many patent-encumbered standards already exist, and even if WIPO
  496. ends up agreeing on a general interoperability preference, it will
  497. take decades for this to become local law.</p>
  498. <p>As an intermediate solution, (F)RAND needs to be enforced in a way
  499. that the license terms do not discriminate against any valid business
  500. model, as is still common today. A potential solution could be to
  501. tie (F)RAND royalties to the downstream licensing revenue.</p>
  502. <p>Business models that are based on proprietary licensing based on
  503. copyright or patents for revenue would continue to operate as they
  504. do today. Business models that do not rely on such licensing revenue
  505. would be enabled to interoperate and compete.</p>
  506. <p>Taking this step would also realign ITU-T, ITU-R, ISO and IEC again
  507. with their declared Common Patent Policy.</p>
  508. <h3>4. Update governmental procurement guidelines</h3>
  509. <p>Governments and Inter-Governmental Organisations should update
  510. their procurement guidelines to procure only products based upon
  511. standards that do not discriminate against any legitimate business
  512. model. This means a review of blanket approval for certain standard
  513. setting organisations, and only a limited approval for organisations
  514. that have not updated their patent policies appropriately by the
  515. time of the review.</p>
  516. <hr />
  517. <p><em>DISCLAIMER: This paper was written from the
  518. perspective of an expert in the field of software. The conclusions
  519. may apply in their entirety, partially, or not at all to areas
  520. other than software.
  521. </em></p>
  522. </body>
  523. <timestamp>$Date$ $Author$</timestamp>
  524. </html>
  525. <!--
  526. Local Variables: ***
  527. mode: xml ***
  528. End: ***
  529. -->