Public participation in patent examination

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

The involvement of the public in patent examination is used in some forms to help identifying relevant prior art and, more generally, to help assessing whether patent applications and inventions meet the requirements of patent law, such as novelty, inventive step or non-obviousness, and sufficiency of disclosure.

Rationale

The rationale for public participation in patent application review is that knowledgeable persons in fields relevant to a particular patent application will provide useful information to patent examiners if the proper forum is provided. One model for such a forum is a wiki model where the public may submit prior art and commentary relevant to a given patent application and patent examiners can consult that forum. The hoped-for effect is that patent examination will be more efficient and thorough thus patents that do issue will be of higher quality than is currently possible.[1]

History

In the 17th and 18th centuries, patent examination in France for novelty and utility was performed by the private French Academy under commission from the French government. The Academy sought the input of outside experts in the specific fields of the inventions. Galileo, for example, was consulted when a patent was applied for on a new method of determining longitude by measuring the position of the moon. Galileo’s conclusion was that the method would work in principle, but the measuring techniques were not accurate enough to provide meaningful results. A patent, therefore, was denied.[2]

Legal constraints

United States

In the United States, the third parties may not provide commentary or opinions directly to a patent examiner during the prosecution of a patent unless the patent applicant gives the examiner written permission to do so.[3] Rule 99, which previously allowed a member of the public to submit prior art to an examiner within two months of application publication, has been repealed by the AIA.[4] Rule 290 (37 CFR 1.290) and 35 USC 122(e) control the submission of prior art references by third parties after the publication of an application and before issuance of the patent. Prior art references must be cited before the earliest of 6 months from publication, the first rejection of any claim, or the notice of allowance.

History

Observations by third parties

The European Patent Convention (EPC) provides that any person may present observations concerning the patentability of an invention described in a European patent application.[5] This is a form of public participation to patent examination. Filing such observations by third parties at the European Patent Office (EPO) is free of charge, but the observations must include a statement of grounds.[5] The statement of grounds must be in English, French or German.[6] The person filing the observations does not become party to the proceedings.[5]

In the United States Patent and Trademark Office (USPTO), third parties may submit prior art relevant to a published patent application within two months of said publication or before a notice of allowance is given, whichever comes first. In contrast to European practice, however, third parties are not allowed to provide any additional explanation of the relevance of the prior art. The USPTO requires a fee.[7]

Some countries such as Australia can only accept but not grant patents after examination. The accepted patent is then advertised and public comment is sought. After the lapsing of a certain period (90 days in Australia) with no comment the patent is granted.[8]

In July 2012, a third party observation system was also introduced for Patent Cooperation Treaty (PCT) applications.[9] The observations have to relate to novelty and inventive step, and they may be submitted anonymously.[10] The observations can be made at any time from the publication of the PCT application until the expiration of 28 months from the priority date. No fee is due for filing the observations.[11]

Wiki review

The review of patent and patent applications through wiki projects was proposed in 2005 by patent attorney J. Matthew Buchanan on his blog.[12] A subsequent proposal was made in Fortune magazine in 2006.[13] The claimed purpose is to improve the quality of patent examination, as well as re-examination, through the involvement of the public, to help identifying relevant prior art. The USPTO has endorsed some of these projects.

According to Dave Kappos, former vice president for intellectual-property law at IBM and later head of the USPTO, "it's a very powerful concept because it leverages the enormous capabilities of the entire world of technical talent."[13]

Wikipedia itself has been used by US patent examiners as a reference to get a "quick outline of an unfamiliar topic".[14] Citations of Wikipedia as prior art, however, is not allowed in the US, due to the fluid and open nature of its editing.[15] Nonetheless, in the related area of trademark examination, entries from Wikipedia have been cited in precedential opinions by the Trademark Trial and Appeal Board of the USPTO.[16]

Blackboard patent

Wikipedia has also been used to collect early references related to controversial patents. History of virtual learning environments, for example, is an article that was created primarily to list prior art that would potentially invalidate U.S. Patent 6,988,138, “Internet-based education support system and methods”. This patent issued to Blackboard Inc. in June 2000. The Moodle wiki has a similar page.[17] Once the patent was issued, Blackboard Inc. sued its competitor Desire2Learn to stop them from infringing the patent. In July 2009, the Court of Appeals for the Federal Circuit held that all of the claims of the Blackboard patent were invalid either for being too vague or for being already in practice before Blackboard filed their application. Blackboard, however, has four continuation applications pending where it can correct the deficiencies in its claims and get new patents to issue.[18]

While the lawsuit was moving forward, the Software Freedom Law Center filed for a reexamination citing that new prior art had been discovered that raised a substantial new question of validity. The USPTO agreed and the patent is currently undergoing reexamination.[19]

USPTO community patent review (Peer to Patent)

On June 15, 2007, the United States Patent and Trademark Office began a two-year pilot community patent review called Peer to patent or Community Patent Review.[20] The program organizers anticipate having 250 pending software patent applications reviewed by members of the interested public. They can submit prior art along with commentary and vote on the most relevant prior art. Four months after a patent application is posted the most relevant prior art is provided to the patent examiner.

In the first five months of the program, over 20 applications have been opened to the public and 8 have completed reviews. Over 28,000 site visits have been recorded. 1,600 reviewers from more than 100 different countries have registered. Over one hundred thirty potential prior art references have been submitted. General Electric, Hewlett Packard, IBM, Intel, and Oracle Corporation each have volunteered some of their pending patent applications for review.

Patent examiners will have access to the commentary and will consider it in their examination. Applications that are part of the pilot program will get accelerated examination.[21]

Of the first 19 office actions received by Peer-to-Patent applications, 5 cited the prior art submitted by reviewers.[22]

A new pilot started on October 25, 2010, and will continue until September 30, 2011.[23]

IP.Com PatentDebate

IP.com PatentDebate is a blog type web site were the public can comment on all pending published US patent applications.[24] User registration is required. Unlike Peer to Patent, however, there is no formal relationship between the USPTO and PatentDebate. The site is sponsored at least in part by advertising.

Post issuance review

Article One Partners

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Article One Partners provides a community review format for enlisting members of the public to search for prior art for already issued patents. These patents are generally the subject of ongoing litigation. Anyone who signs up can earn cash rewards if they submit the most relevant prior art. Additionally, members can earn profit-sharing points for activities such as referring friends. The profit-sharing points earn them cash rewards.[25][26] Article One Partners was recognized as "2009 Startup of the Year" by Silicon Alley Insider.[27]

BountyQuest project

The now defunct BountyQuest[28] was an early attempt to recruit members of the public to search for prior art for issued patents. Bounties were offered by companies for any prior art that someone could find that would invalidate the claims of a given US patent. BountyQuest existed from 2000 to 2003.[29]

PatentFizz

PatentFizz provides a forum for commenting on issued patents and provides a simplified view of patents.[30][needs update]

Patexia

Patexia is a patent research company that provides patent valuation services to companies with intellectual property portfolios by crowdsourcing the search problem to technical and scientific subject matter experts. Patexia provides a free online search engine capable of searching patents and patent litigation by patent number, company, or keyword; an online news aggregator on innovation and IP topics; a contest platform with prizes for crowdsourced patent research; and a freelance marketplace to connect its subject matter experts to businesses for direct consultation to solve technical problems for clients.[31][non-primary source needed]

See also

References

  1. Schecter, Manny, Open Collaboration Is Medicine for Our Ailing Patent System, BNA's Patent, Trademark & Copyright Journal, Vol. 72, No. 1789, pp. 682-685, Oct. 20, 2006.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 5.2 Article 115 EPC
  6. Guidelines for Examination in the EPO, section e-v, 3 .
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Australia Patents Act 1990. Accessed October 6, 2012.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Practical Advice, Making third party observations, PCT Newsletter, July–August 2012, No. 07-08/2012, pp. 17-19.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 Nicholas Varchaver, Patent review goes Wiki, Fortune, VOL. 154, NO. 4 - August 21, 2006
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. "Online startup aims to improve patent quality" GMA News.tv Nov. 17, 2008.
  26. See also US application 2008270255  and WO application 2008119083 , patent applications on the system (title: "Requesting prior art from the public in exchange for a reward").
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Internet Archive. http://web.archive.org/web/*/http://www.bountyquest.com
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.

External links