October 7th, 2014
A decision by the Supreme Court of the United States on June 6, 2011 has a great impact on the interpretation of the Bayh Dole Act as well as assignment of contracts relating not just to the Bayh Dole Act but to assignments in general. The case, Board of Trustees of the Leland Stanford Junior University v. roche Molecular Systems, Inc., et al., is of particular interest because the assignment of inventions has an impact on contractor relations with the government. Without an assignment of rights by the inventor to the contractor or subcontractor, the contractor or subcontractor cannot grant to the government rights that the government may have in an invention funded by the government, more specifically the confirmatory license discussed in Protecting Your IP Under Government Contracts, Part 1.
This decision points out that the Bayh Dole Act does not automatically vest title to the contractor in federally funded inventions. Title or ownership belongs to the inventor unless the inventor assigns his or her title by contract to another individual or company. The Bayh Dole Act specifically recites that the contractor in federally funded inventions may elect to retain title to any subject invention; that is an invention that has either been conceived or actually reduced to practice under the federal contract. Read the rest of this entry »
September 15th, 2014
If the contractor or subcontractor of a government contract elects to retain title to a subject invention, there are requirements that the contractor must meet. A few of the more important requirements for obtaining rights to inventions under government contracts are as follows:
- Identify publications, offers for sale and public use of the subject invention.
- Require employees (other than clerical or non-technical) by written agreement to disclose promptly in writing to personnel identified as responsible for the administration of patent matters each subject invention made under the contract in order that the contractor can comply with the appropriate disclosure provisions. The contractor must also execute all papers necessary to file provisional or patent applications on subject inventions and to establish the government’s rights in the subject inventions.
- Notify the contracting officer of a decision not to file a provisional or non-provisional patent application on the subject invention, not to continue prosecution of a patent application, not to pay a maintenance fee on an issued patent, or defend re-examination or an opposition proceeding on a patent in any country, not less than 30 days before expiration of such a response or filing period.
- Execute and promptly deliver to the contracting federal agency all instruments necessary to establish or confirm the rights the government has throughout the world in those subject inventions to which the contractor elects to retain title.
- Convey title to the contracting agency (U.S. Government) if the contractor or subcontractor does not elect to take title or does not fulfill the relevant requirements above when requested by the government, to enable the government to obtain patent protection throughout the world in that subject invention.
- Include in the specification of a provisional or non-provisional application the statement: “This invention was made with Government support under (identify the contract) awarded by (identify the agency). The Government has certain rights in the invention.”
In addition, when dealing with a government contract the contractor agrees that neither it nor any assignee will grant any person exclusive right to use or sell the subject invention unless such person agrees to manufacture substantially in the United States. Since many components cannot be manufactured within the United States, it is possible for the contractor to obtain a waiver from the government to such a manufacturing provision.
In my next post I will review Board of Trustees of the Leland Stanford Junior University v. Roche Molecular Systems, Inc., et al., a case that was particularly impactful on the interpretation of the Bayh Dole Act and assignment of contracts in general.
June 30th, 2014
In our last post we looked at some key definitions (Invention, Subject Invention, and Made), so now let’s look at the application of those definitions.
If a subject invention falls under or is made under a government contract, the subject invention, at the time of the contract, may be either in the form of a disclosure, a patent application or even a patent. The important factor deals with the actual reduction to practice of the invention. Did the actual reduction to practice take place prior to the contract?
For a contractor or subcontractor to exclude the invention from being a subject invention, first actual reduction to practice of the invention must have taken place prior to the contract. In order to exclude such an invention from being a subject invention, it is extremely helpful for the contractor or subcontractor to have sufficient evidence to support the conception and actual reduction to practice of the invention to be excluded as subject inventions, in that both conception and first actual reduction to practice have taken place prior without the use of government funds and prior to or subsequent to the contract. If this is not the case, and the conception or first actual reduction to practice takes place under the contract, and the contractor or subcontractor must disclose this invention to the government as being a subject invention.
June 25th, 2014
The recent US Supreme Court decision in Limelight Networks v. Akamai Technologies relates to joint infringement. Usually, infringement of a method or process claim in a patent occurs when one entity practices all the steps in the method or process. However, in many systems, for example communication systems, the system includes a server that is owned by one entity, and client systems (Blackberry®s for example) that are owned by another entity. A method or process claim, if written in the most straightforward and logical manner, would be performed in part by the entity that owns the server and in another part by the entity that owns the client system. Infringement of that method or process claim would require joint infringement, where the two entities cooperate in performing the steps of the process. Under present law, direct infringement may not be possible since present law requires that one entity perform all steps in the method or process unless one party is under control or direction of the other party.
Akamai owns a patent having a claim for a method for delivering electronic data using a content delivery network (CDN). Limelight operates a CDN. When Akamai sued Limelight Networks for infringement, Limelight Networks claimed noninfringement since Limelight performs all the steps of the method claim except for one: the step of “tagging” is performed by the user. On appeal, the US Court of Appeals for the Federal Circuit, in a ruling including the entire court, found that, although direct infringement may not have been possible, Limelight could be liable as an inducer of infringement. As stated in the US Supreme Court decision in Limelight Networks v. Akamai Technologies, the entity that owns the server cannot be considered to be inducing infringement since inducing infringement requires that someone be infringing the entire claim.
Unless there is a different ruling on direct infringement, and that ruling stands the test of the US Supreme Court, patent drafters will have to write separate claims: one set of claims where the actions occur only at the server, and another set of claims were the actions occur only at the client. The structure of such claims is awkward, the number of claims is twice that needed, and the Examiner will attempt restriction.
Until the law changes, we will need to write method claims that are performed by only one party.