IP Intelligence

IP Intelligence

Insight on Intellectual Property

Addressing Section 101 Issues Through Reissue

The contraction of patent eligible subject matter under 35 U.S.C. 101 that Alice, Mayo, Bilski, and other recent court cases have triggered has placed a cloud of uncertainty over a large number of patents.  [1]  Fortunately, though, the law provides patent owners with a process for taking remedial steps to address Section 101 risks in their patent portfolios.  A viable remedial measure that may help minimize subject matter eligibility attacks is filing a reissue application. This article briefly discusses patent eligibility and how a reissue may be a good way to address the negative impact of these recent cases on issued patents.

Judge Moore’s warning that Alice “is the death of hundreds of thousands of patents, including all business method, financial system, and software patents as well as many computer implemented and telecommunications patents…” looks more and more like an accurate assessment of Alice’s impact. [2]  Since Alice was decided earlier this summer, the Federal Circuit has affirmed summary judgment of invalidity on patent eligibility grounds in Planet Bingo v. VKGS (Fed. Cir. 2014) available here) and, remarkably (at least to this author) affirmed judgment of invalidity in another case based on the pleadings.  See buySAFE v. Google (Fed. Cir. 2014) available here.  The USPTO has been at it as well, issuing examination guidelines in light of Alice as we have reported here and hereAlice and its growing progeny have left us with the following test, although vague, for patent eligibility under Section 101: (1) determine whether the patent claim is directed to subject matter in one of the three excluded categories (abstract idea, law of nature, or natural phenomena), and (2) if so, determine whether the additional elements of the claim supply an inventive concept that is significantly more than the ineligible matter itself.  Recitation of a general purpose computer, in and of itself, is not normally enough to supply the so-called inventive concept to a claim directed to patent ineligible matter. [1]  A reissue application may be an avenue to add the so-called “inventive concept” to a claim with patent eligibility risk under Alice. Continue Reading

Challenging Delegated Top-Level Domains: ICANN’s Trademark Post Delegation Dispute Resolution Procedure

This year, hundreds of new generic top-level domains (gTLDs) are changing the landscape of the Internet.  The long-awaited result of ICANN’s new gTLD program, top-level domains such as .NYC, .WINE, and .WTF will now join the familiar ranks of domains such as .COM and .NET.  As we’ve written about previously, ICANN provided brand owners, trademark holders, and distinct communities the opportunity to object to proposed gTLDs before they were approved or “delegated” to registry operators.  The window for filing these objections ended in March of 2013 and the final objections were resolved in early 2014.  While some top-level domains were successfully blocked by this objection process, the majority of objected-to domains were cleared for delegation.  However, even though ICANN’s gTLD Objection Procedure has closed, brand owners may now have a second opportunity to object to top-level domain registry operators’ complicity or participation in trademark infringement, whether stemming from use of a gTLD string itself or second-level domains registered in the domain. Continue Reading

Public Comments to USPTO’s Preliminary Examination Instructions in View of Supreme Court Decision in Alice Case

As reported here last month, the USPTO recently issued a memorandum to the Examination Corps, entitled “Preliminary Examination Instructions in view of the Supreme Court Decision in Alice Corporation Pty. Ltd. v. CLS Bank International, et al.” The memorandum provides preliminary instructions to the Patent Examining Corps relating to subject matter eligibility of claims involving abstract ideas, particularly computer-implemented abstract ideas. The USPTO requested public comments, and the comment period closed last week on July 31, 2014.[1]

Two of the country’s leading IP bar associations, AIPLA[2] and IPO[3], submitted comments. The following is a brief summary of these comments:

AIPLA Comments

AIPLA’s comments were submitted in a 10-page letter that included 12 subheadings (recited below). In addition, the following specific interrelated points were emphasized as underlying most of the issues identified:

  1. There’s been no substantive change in the law. The opinion in Alice applies settled principles for applying the abstract idea exception to patent eligibility of process claims, making no substantive changes to that law. It applied pre-existing law and appears to be limited to the particular facts of the case.
  2. Care must be taken to avoid extending the holding in Alice. The Office does not have substantive rule-making authority, and AIPLA urges the Office to exercise caution in instructing Examiners on Alice to ensure that adequate attention is given to the factual context of the Court’s reasoning and to discourage extrapolations that lead to new and unsupported rules of law. The Federal Circuit, and many others, have struggled over the years to understand and explain the decisions of the Supreme Court on subject matter eligibility, and they have often ended up being corrected by the Supreme Court.
  3. The Office and its examiners must tread carefully.” Though the Court declined to explain, and thus “delimit,” what an “abstract idea” might be, it also warned, “we tread carefully in construing this exclusionary principle lest it swallow all of patent law.” Alice, 573 U.S. ___ (slip. op. at 6) (citing Diamond v. Chakrabarty, 447 U.S. 303 (1980)). This is an admonition and should be observed by the Office and Examiners alike.

The 12 sub-sections are directed to the following points:

  1. Alice made no major changes to the framework for determining patent eligibility.
  2. Alice does not require substantive changes to current examination guidance.
  3. Prior guidance remains viable; the two-part Mayo framework is not exclusive, and may not be appropriate for every claim.
  4. Generalizations and overly broad interpretations should be avoided.
  5. Examiners should be instructed to err on the side of finding eligible subject matter.
  6. The burden rests on the Office to fully support a rejection under section 101 and to take into account evidence submitted by an applicant.
  7. Abstract ideas are those that have always existed or been long prevalent.
  8.  Claim as a whole must be considered when evaluated whether it is directed to an abstract idea.
  9. Guidance to examiners should emphasize adherence to the concrete examples of “abstract idea” found in current case law as opposed to any extension of or addition to the narrow pool of ineligible subject matter.
  10. A complete examination is required.
  11. Each claim type should receive a separate analysis for “something more”.
  12. The “something more” requirement must consider a claim as a whole.

IPO Comments

In its 4-page submission, IPO first reminded the USPTO of its overarching view, expressed in the organization’s amicus brief to the U.S. Supreme Court in the Alice case. In sum, IPO stated that: (1) patent eligibility for computer-implemented inventions is vital to IPO members and the broader U.S. economy; (2) nearly every economic sector depends on computer-implemented innovations that improve products and services, increase productivity and efficiency, and strengthen competitiveness; (3) the patentability of new and useful technological advancements should not be constrained by overbroad subject matter rejections; and (4) the standard of patentability for computer-implemented inventions should not be higher than the standard applied to innovations in other technological fields.

In addition, IPO’s comments included the following main points:

  1. Prima Facie Case of Patent-Ineligible Subject Matter

IPO urges that the final instructions should require examiners to make a detailed prima facie showing that each part of the two-part test[4] has been met. Per IPO, examiners should be instructed to support any conclusions with reasoned logic rather than general statements parroting language from stock rejections. Similar to the detailed analysis required to prove prima facie obviousness, it is not enough for an examiner to merely assert that a claim recites an abstract idea and nothing “significantly more.” The USPTO training materials showing examples of improper rejections under section 103 are instructive. In the final instructions, the Office should provide some reliable “indicia of abstractness” to ensure uniform and comprehensive application of the two-part test.

IPO also argues that examiners should not automatically conclude that any business method or software-related claim is directed to an abstract idea. Alice did not create a per se excluded category of business methods or software, or impose any special requirements for eligibility of business methods or software. The final instructions should emphasize this point and provide examples of business method and software claims that are not directed to abstract ideas.

In respect to Part 2 of the two-part test, the question is not whether an abstract idea is “present,” but whether the claim is “directed to” an abstract idea. Part 2 should be amended accordingly.

In evaluating whether the claim amounts to “significantly more” than the abstract idea, examiners should again avoid conflating section 101 with sections 102 and 103. To this end, the final instructions should clearly explain what will qualify as significantly more. The final instructions should explain whether “significantly more” is the only criterion for establishing patent-eligibility of a claim directed to an abstract idea. Alice listed other criteria including:

an ‘inventive concept’ sufficient to ‘transform’ the claimed abstract idea into a patent-eligible application;

additional features’ to ensure ‘that the claim is more than a drafting effort designed to monopolize the abstract idea’;

application[s] of such concepts ‘to a new and useful end’… remain eligible for patent protection; and

distinguish[ing] between patents that claim the ‘building blocks’ of human ingenuity and those that integrate the building blocks into something more, thereby ‘transforming’ them into a patent-eligible invention.

Alice Corp. (emphasis added) (internal citations omitted).

The preliminary instructions correctly state that, in evaluating whether added limitations qualify as “significantly more,” the claims should be considered as a whole by considering all claim limitations, both individually and in combination.

The preliminary instructions provide three examples of limitations that would qualify as “significantly more”: (1) improvements to another technology or technical field; (2) improvements to the functioning of the computer itself; or (3) meaningful limitations beyond generally linking use of an abstract idea to a particular technological environment. The final instructions should ideally include even more examples of limitations that would qualify as “significantly more.” The final instructions should also require examiners to identify all claim limitations and articulate detailed reasons why they are not “improvements” under examples (1) or (2) or “meaningful” under example (3).

  1. Scope of Examination Under Preliminary Instructions

There is some concern that examiners may be using introductory statements in the preliminary instructions to support claim rejections under section 101. Examiners should avoid extending the scope of the preliminary instructions beyond the two-part test and the precise and narrow holding in Alice. In Alice, the Supreme Court stated, “the claims at issue amount to ‘nothing significantly more’ than an instruction to apply the abstract idea…using some unspecified, generic computer.” [Citation omitted.] This statement is repeated in the introductory section of the preliminary instructions. Examiners should not use this as a basis to reject every claim directed to an abstract idea that includes a generic (or conventional) computer, since the statement does not mean that a conventional computer is never significant to the claim as a whole.

  1. Miscellaneous Suggestions

The preliminary instructions should remind examiners to avoid focusing on issues of patent-eligibility under section 101 to the detriment of other patentability requirements. Examiners should also be instructed to review the disclosure as a whole and, where appropriate, proactively suggest language that would be acceptable to overcome subject matter rejections. The Office should implement the final instructions and provide adequate training and resources as soon as possible.

[1] The comments are purportedly available for public inspection at the Office of the Commissioner for Patents, located in Madison East, Tenth Floor, 600 Dulany Street, Alexandria, Virginia, and will be available via the USPTO Internet Web site.

[2] AIPLA is a national bar association with approximately 15,000 members engaged in private and corporate practice, in government service, and in academia. AIPLA members represent a wide and diverse spectrum of individuals, companies and institutions involved directly or indirectly in the practice of patent, copyright and trademark law, as well as other fields of law affecting intellectual property.

[3] IPO is a trade association representing companies and individuals in all industries and fields of technology who own or are interested in intellectual property rights. IPO’s membership includes more than 200 companies and more than 12,000 individuals who are involved in the association either through their companies or through other classes of membership.

[4] “Part 1: Determine whether the claim is directed to an abstract idea.” “Part 2: If an abstract idea is present in the claim, determine whether any element, or combination of elements, in the claim is sufficient to ensure that the claim amounts to significantly more than the abstract idea itself.” USPTO memo of June 25, 2014 (emphasis in original).

Nominations Open for ABA Journal’s Top 100 Legal Blogs – IP Intelligence

The American Bar Association Journal announced that it is compiling its annual list of the 100 best legal blogs and invites readers to submit a nomination:

Use the form below to tell us about a blog—not your own—that you read regularly and think other lawyers should know about. If there is more than one blog you want to support, feel free to send us additional amici through the form. We may include some of the best comments in our Blawg 100 coverage. But keep your remarks pithy—you have a 500-character limit.

We invite our readers to recommend the IP Intelligence: Insight on Intellectual Property blog and other favorite legal blogs for selection by the ABA. Submissions are accepted through August 8, 2014.

Partner Alan Friel Named Influential Lawyer by LA Business Journal

Partner Alan Friel was named among the “Most Influential Lawyers: Digital Media and E-Commerce Law” in the Los Angeles Business Journal’s July 21, 2014, issue. The list recognizes 30 Los Angeles attorneys who have demonstrated outstanding achievements in digital media and e-commerce law. Friel is noted in the publication as a “sought after counselor, speaker, and thought leader” who adds “strength to the firm’s capacity” in advertising, retail, e-commerce, digital media and technology, and privacy and data security.

View the list.

USPTO Issues “Preliminary Examination Instructions in view of the Supreme Court Decision in Alice Corporation Pty. Ltd. v. CLS Bank International, et al.”

On June 25, 2014, the USPTO issued a memorandum to the Examination Corps, entitled “Preliminary Examination Instructions in view of the Supreme Court Decision in Alice Corporation Pty. Ltd. v. CLS Bank International, et al.” This memorandum provides preliminary instructions, effective June 25, 2014, to the Patent Examining Corps relating to subject matter eligibility of claims involving abstract ideas, particularly computer-implemented abstract ideas. (A copy of the Preliminary Examination Instructions can be found here.) The memorandum states that the instructions are preliminary in nature, and that further guidance will be issued. In addition, the USPTO is requesting comments regarding their guidance to the examining corps.

In summary, the memorandum provides instructions to the Patent Examining Corps relating to subject matter eligibility of claims involving “abstract ideas,” particularly computer-implemented abstract ideas, under 35 U.S.C. § 101. The eligibility framework for claims involving abstract ideas is the same as the current framework for claims directed to laws of nature and natural phenomena.

According to the memorandum:

1)      Alice Corp. establishes that the same analysis should be used for all types of judicial exceptions, whereas prior USPTO guidance applied a different analysis to claims involving abstract ideas than to claims involving laws of nature.

2)      Alice Corp. also establishes that the same analysis should be used for all categories of claims (e.g., product and process claims), whereas prior guidance applied a different analysis to product claims involving abstract ideas than to process claims.

Assuming the claim falls within one of the statutory categories (i.e., process, machine, manufacture, or composition of matter), the examiner should determine whether the claim is directed to a judicial exception (i.e., law of nature, natural phenomenon, and abstract idea) using Part I of the two-part analysis summarized below, and, if so, determine whether the claim is a patent-eligible application of an exception using Part 2.

Two-part Analysis for Abstract Ideas

The Examining Corps are instructed to analyze all claims (product and process) using the following two-part analysis:

Part 1: Determine whether the claim is directed to an abstract idea.

Per the decision in Alice Corp., abstract ideas are excluded from eligibility based on a concern that monopolization of the basic tools of scientific and technological work might impede innovation more than it would promote it. At the same time, the courts have tread carefully in construing this exclusion because, at some level, all inventions embody, use, reflect, rest upon, or apply abstract ideas and the other exceptions. Thus, an invention is not rendered ineligible simply because it involves an abstract concept. In fact, inventions that integrate the building blocks of human ingenuity into something more by applying the abstract idea in a meaningful way are eligible.

Examples of abstract ideas referenced in Alice Corp. include:

  • Fundamental economic practices;
  • Certain methods of organizing human activities;
  • An idea of itself; and
  • Mathematical relationships/formulas.

Claims that include abstract ideas like these should be examined under Part 2 to determine whether the abstract idea has been applied in an eligible manner. If an abstract idea is present in the claim, proceed to Part 2 below. If not, proceed with examination of the claim for compliance with the other statutory requirements for patentability.

Part 2: If an abstract idea is present in the claim, determine whether any element in the claim is sufficient to ensure that the claim amounts to significantly more than the abstract idea itself. In other words, are there other limitations in the claim that show a patent-eligible application of the abstract idea, e.g., more than a mere instruction to apply the abstract idea?

Limitations referenced in Alice Corp. that may be enough to qualify as “significantly more” when recited in a claim with an abstract idea include:

  • Improvements to another technology or technical field;
  • Improvements to the functioning of the computer itself; and
  • Meaningful limitations beyond generally linking the use of an abstract idea to a particular technological environment.

Limitations referenced in Alice Corp. that are not enough to qualify as “significantly more” when recited in a claim with an abstract idea include:

  • Adding the words “apply it” (or an equivalent) with an abstract idea, or mere instructions to implement an abstract idea on a computer; and
  • Requiring no more than a generic computer to perform generic computer functions that are well-understood, routine, and conventional activities previously known to the industry.

If there are no meaningful limitations in the claim that transform the exception into a patent eligible application such that the claim amounts to significantly more than the exception itself, the claim should be rejected under 35 U.S.C. § 101 as being directed to non-statutory subject matter.

After conducting the two-part analysis, proceed with examination of the claim, regardless of whether a rejection under § 101 has been made, to determine patentability in accordance with the other requirements of 35 U.S.C. § 101 (utility and double patenting), non-statutory double patenting, and §§112, 102, and 103.

What CLS Bank Taketh, Copyright May Giveth Back

CLS Bank and Its Impact on Software Patents

Courts, commentators and clients will be struggling for some time to assess the impact on software patents of Thursday’s Supreme Court decision in Alice v. CLS Bank.  Interpreted one way, the decision kills patents directed at computer-implemented business methods.  Interpreted another way, it’s business as usual for patentees.  The Supreme Court found that using a computer to implement an abstract idea was not sufficiently inventive to justify patent protection.  It is not clear, however, whether the decision has much reach beyond the facts of the CLS Bank case itself.  Part of the problem is how miserable the patents at issue really were.  The patentee’s inspiration was to employ a third party to collect financial information on the parties to a transaction in order to verify that they had sufficient funds to close a deal.  This is otherwise known as employing an escrow agent or clearing house, and it is a method of mitigating risk in transactions that appears to be several thousand years old.  The patentee claimed their idea was eligible for a patent, however, because it used a computer program to download the financial data, perform the calculations, and send notifications regarding the financial risk (although it had never actually implemented any of the claimed systems).  The Supreme Court found that the idea to use an escrow agent in a financial transaction was an unpatentable “abstract” (and ancient) idea.  The decision to use generic computer functions to perform that role did not elevate the concept to a patentable invention.  It is easy to confine the Court’s decision to the facts of the case, mostly because the Court declined to “delimit the precise contours of the ‘abstract ideas’ category in this case.”

However, the Court made several comments in the offing that some may use to attack a broader range of software patents.  The Court found that the use of a “generic computer to perform generic computer functions” to implement an abstract idea was not a sufficiently “inventive concept” to warrant patent protection.  That much is unremarkable.  How the Court determined what counts as a “generic computer function,” however, is.  The Court determined, without the support of factual findings below, that certain computer functions were “well-understood, routine, [and] conventional,” including keeping electronic records, obtaining data, adjusting account balances, and issuing automated instructions.  What is more, the Court suggested that software patents that “purport to improve the functioning of the computer itself” or “effect an improvement in any other technology or technical field” are potentially patentable.  By contrast, those software patents that are not sufficiently technical would appear to be imperiled.  It is not clear, however, where the lines have been drawn for a computer-implemented method to be sufficiently technical, or when a non-technical method uses software in a sufficiently non-generic way.  The ambiguity is worsened by the Court’s express refusal to “delimit” what counts as an abstract idea.  What is clear is that at least some courts will give software patents greater scrutiny in the future.

Oracle v. Google and Its Impact on Software Copyright

At nearly the same time as this potential roll-back of patent protection for software, last month’s Federal Circuit opinion in Oracle v. Google may signal an expansion of copyright protection.  There the Court found that “a set of commands to instruct a computer to carry out desired operations may contain expression that is eligible for copyright protection.  … [A]n original work—even one that serves a function—is entitled to copyright protection as long as the author had multiple ways to express the underlying idea.”  This decision has challenged the perceived separation between copyright and patent law, and revealed that software developers may have more robust rights in their source code than previously thought.

Oracle v. Google involved Google’s attempt to make its Android platform compatible with programs coded in Java.  To do so, Google needed to use certain programming gateways that enable interoperability, called application program interfaces (APIs).  The APIs themselves consist of two kinds of source code— a) short phrases that identify an ensuing function called “headers” or “declarations;” and b) implementing code, often consisting of thousands of line of code, that actually performs the calculations or functions called for in the header.  Google copied the headers for 37 Java APIs, but created its own implementing code.  Oracle claimed that Google’s copying infringed Oracle’s copyright in the API’s by both—a) exactly copying the headers; and b) effectively paraphrasing (i.e. non-literally copying) Oracle’s implementing code by copying the structure, sequence, and organization (“SSO”) of the APIs.

The District Court in the case noted that “an exclusive right to a functional system, process, or method of operation  belongs in the realm of patents, not copyright.”  Keeping this separation is important because, among other things, “copyright exclusivity lasts 95 years whereas patent exclusivity lasts twenty years.”  This separation is largely maintained through the “idea/expression dichotomy,” codified at section 102(b) of the Copyright Act:

In no case does copyright protection for an original work of authorship extend to any idea, procedure, process, system, method of operation, concept, principle, or discovery, regardless of the form in which it is described, explained, illustrated, or embodied in such work.

This separation is also supported by the legal doctrine of “merger,” whereby a particular expression of an idea is not given copyright protection when there are a limited number of ways to express that idea.  Because the header lines of code had to be copied exactly to ensure proper functioning with the Java programming language, the District Court found that the merger doctrine barred copyright protection for the header code.

Also at issue in the case, however, was the overall SSO of the APIs.  Although Google had written its own implementing code, it grouped the methods at issue in the same fashion (into packages, subdivided in classes, subdivided in methods) as the Oracle APIs.  Although the District Court acknowledged that the SSO of the APIs resembled a copyrightable taxonomy, and that the SSO was original, creative, and subject to multiple forms of expression, the court nonetheless found that the SSO operated as a “command structure”—a method of operation of using a “long hierarchy of over six thousand commands to carry out pre-assigned functions.”  Because of the functional nature of the SSO, the court found it was not copyrightable under section 102(b) of the Act.  Threaded throughout the court’s decision was a concern that granting Oracle control over the API’s functionality would disrupt the widespread interoperability that defines both the internet and mobile device industries, and would give Oracle a monopoly power not intended by Congress.

The Federal Circuit reversed.  As regards the Java API headers, the Court found that the merger doctrine did not apply because there were numerous ways to express the short phrases necessary to define the ensuing method of the API—albeit numerous ways that existed when the APIs were first coded.  That is, the Court found that the merger doctrine required analysis of the options available to the software coder at the time of the coding, not those options available to an infringer many years later.  Implied in the decision is that there is no fundamental right to code in Java.  If there becomes only one way to code API headers to ensure interoperation with Java, that is Google’s tough cookies (pun intended)—Google is free to program its own Java-like language from scratch and hope that it catches on.  But because there was sufficient creative selection in the header code when Java was first coded, the merger doctrine did not apply.  Because Google admitted direct copying, it was infringer.

Even more significant, however, was the Federal Circuit’s analysis on whether the overall SSO of the APIs was protected by copyright.  Here the Court purportedly applied what is known as the “abstraction-filtration-comparison test.”  This test is an exacting analysis that requires a court to break a copyrighted down into its constituent parts, sift out non-protectable information such as ideas and facts, and then compares the remaining expressive content with the allegedly infringing program.  However, when it came time to apply this analysis to the SSO, very little filtration occurred.  Rather, the Court concluded, as noted above, that “an original work—even one that serves a function—is entitled to copyright protection as long as the author had multiple ways to express the underlying idea.”

There is an inherent tension, if not outright contradiction, in the Copyright Act between section 102(b)’s prohibition against protecting a “method of operation” and the Act’s definition in section 101 of “computer program” as a “set of statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result.”  While the Court made some attempt to harmonize these two provisions, at the end of the day it resolved the tension by coming down solidly in favor of copyright creep—“The problem with the district court’s approach is that computer programs are by definition functional—they are all designed to accomplish some task.  … If we were to accept the district court’s suggestion that a computer program is uncopyrightable simply because it ‘carr[ies] out pre-assigned functions,’ no computer program is protectable.”

To summarize, the district court found that the Java APIs were not copyrightable because the SSO functioned as a command structure, no matter how expressive and original the expression was; the Federal Circuit found that the Java APIs were copyrightable because they were expressive and original, no matter how functional the SSO’s command structure was.

Does Copyright Fill a Void?

If one assumes that CLS Bank spells the death of computer-implemented business method patents, it does not mean that companies that create software are left unprotected for their labor.  Copyright protection is available for the software’s source code and object code.  If the Federal Circuit’s opinion in Oracle v. Google influences other courts, which it historically has in a number of important jurisdictions, there may be protection available for the command structure of the software, even if not literally copied by an infringer and even if that command structure forecloses the use of certain kinds of functionality.  There are also protections available for various user-facing elements like screen displays, user interfaces, and icon designs in copyright, but also things like design patents and trade dress as well.  And, unlike patent law, these protections will not be subject to attack simply because the software is performing “generic” functions or implements an “abstract idea.”

There remain, however, some important differences between patent and copyright law:

  • Copyright law protects only “expression,” and thus only source code that was actually created.  Thus a claimant will have to actually write the code at issue.  By contrast, patent law generally extends to the idea of the invention, even if the invention has not been used in the marketplace.  The inventor in CLS Bank, for example, did not actually produce the claimed computer system.
  • Copyright law requires a showing of access and actual copying, which necessarily requires knowledge of the existence of the source code.  By contrast a patent can be infringed even if the infringer did not know of the preexisting invention.
  • Although copyright law will apparently extend to protect expression even if that expression is incidentally functional, it will not protect the underlying idea.  A rival could attempt to replicate a program’s functionality, so long as the rival coded from scratch and did not try and copy the SSO of the copyrighted program.  Note however that there is an advantage of being the first to market—even Google with its apparently limitless resources took 2 ½ years to create its version of the implementation code of the Java APIs.

All of this begs the question—would the plaintiff in CLS Bank have fared better if it had copyrighted its computer program rather than patented it?  No—CLS Bank created its own program with no apparent access, or even knowledge of, the Alice Corp. system.  However, companies that are actually producing software programs and placing them into the marketplace can enjoy robust protection for their work with the right intellectual property strategy in place.

Lanham Act Claims for Misleading Product Description Can Coexist with FDCA Labeling Regulations, Court Finds

A unanimous Supreme Court (8-0, Justice Breyer recusing) ruled on June 12, 2014 in POM Wonderful v. Coca-Cola that one competitor may sue another for unfair competition under the Lanham Act for allegedly false or misleading product descriptions, notwithstanding that product labeling is regulated under the federal Food, Drug, and Cosmetic Act (FDCA).

Coca-Cola’s Minute Maid division makes and sells a juice blend that is labeled as “pomegranate blueberry,” even though the product contains just 0.3% pomegranate juice and 0.2% blueberry juice. Frustrated that the Coca-Cola product was made with predominantly less expensive apple and grape juices, yet connoted that it might have the same flavor profile as POM Wonderful’s own 85% pomegranate-15% blueberry drink, POM sued Coca-Cola under Section 43 of the Lanham Act for false or misleading product description.

The district court held that because Coca-Cola’s label conformed to FDCA regulations, POM’s Lanham Act suit was precluded, and the Ninth Circuit affirmed.  After a star-studded oral argument in the Supreme Court in which Seth Waxman represented POM and Kathleen Sullivan argued for Coca-Cola, the latter being taken to task by Justice Kennedy when Sullivan suggested that POM didn’t sufficiently credit consumers’ intelligence—“Don’t make me feel bad, because I thought this was pomegranate juice”—the Court reversed.

Following its expansive view of Lanham Act standing from the Lexmark Int’l v. Static Control Components case, decided earlier this Term, the Court noted that POM was bringing suit as a competitor of Coca-Cola; “though in the end consumers also benefit from the Act’s proper enforcement, the cause of action is for competitors, not consumers.” This observation at the outset distinguished the POM Wonderful case from the flood of consumer suits that have been brought in recent years against food and beverage companies for allegedly misleading product labeling, many of which have been found to be pre-empted by the FDCA.

Turning to the statutory interpretation of the FDCA, the Court noted that the FDA apparently does not exercise significant oversight over the content of fruit juice labels; the relevant regulation only requires that a fruit juice blend label must either declare the percentage content of the named juice, or indicate that the named juice is present as a flavor or flavoring. Neither the text of the Lanham Act or the FDCA contain any provision addressing or referring to the interplay between the two.

The Court found that harmonizing the FDCA and Lanham Act did not require preclusion of POM’s Lanham Act claim. Noting that the two statutes have co-existed since the Lanham Act was passed in 1946, the Court observed that Congress could have enacted a provision expressly preempting Lanham Act claims in favor of the FDCA, and the fact that it had not served as “powerful evidence that Congress did not intend FDA oversight to be the exclusive means” of ensuring proper food and beverage labeling. Far from interfering with the proper operation of the FDCA, the Court found, competitors’ Lanham Act claims might in fact further the same objectives: “Allowing Lanham Act suits takes advantage of synergies of multiple methods of regulation,” and competitors’ “awareness of unfair competition practices may be far more immediate and accurate than that of agency rulemakers and regulators.”

The Court’s view of the Lanham Act being a complement to, rather than precluded by, FDCA labeling regulations means that competitors bringing a false labeling claim have one less procedural hurdle to overcome. Conversely, brands should carefully consider the fact that FDCA-compliant labeling is insufficient to stave off unfair competition claims.

Second Circuit Finds That, Once Again, Book Scanning Is Fair Use

The Second Circuit Court of Appeals has delivered a resounding reaffirmation of fair use principles in the latest decision to go against the Authors Guild in its longstanding battle against book digitization.  The unanimous opinion of the three-judge panel in Authors Guild, Inc. v. HathiTrust, No. 12-4547-cv (2d Cir. June 10, 2014) affirmed nearly all of an October 2012 district court ruling that a book scanning project of a consortium of universities called HathiTrust was protected by the fair use doctrine.

HathiTrust works with Google to digitize the books held in the member institutions’ libraries.  The scanned books are hosted by the HathiTrust Digital Library (“HDL”), which allows the public to search for particular terms in the database.  Unless the copyright owner allows broader use, the search results only show the frequency and page numbers on which the search terms appear.  HDL also allows people who can demonstrate that they are unable to read a work in print to access full copies of copyrighted works.  The third feature of HDL at issue is that it preserves the books in order to permit member institutions to create a replacement copy of a copyrighted work if the institution already owned an original copy that was lost, stolen or destroyed and unavailable at a “fair” price.

The Authors Guild sued HathiTrust for copyright infringement in 2011, and was later joined by several other groups representing authors (collectively, the “Authors”).  The Second Circuit spent little time in affirming the district court’s finding that the Authors Guild, the Australian Society for Authors Limited and the Writers’ Union of Canada did not have standing to assert copyright claims of its members based on a straightforward application of section 501 of the Copyright Act.  The Court did find, however, that four other authors’ groups did have standing on the basis that foreign law conferred on them exclusive rights to assert copyright claims of their foreign members.

Turning to the issues of book digitization, the Court applied the four fair use factors to each of the disputed features of HDL.  In examining HDL’s full‐text searchable database, the Court found that it was “a quintessentially transformative use,” and, indeed, that it “adds a great deal more to the copyrighted works at issue than” other transformative uses approved by the Second Circuit.  The Court did, however, take issue with the district court’s implication that a use may become transformative by “making an invaluable contribution to the progress of science and cultivation of the arts,” noting that a transformative use is one “that serves a new and different function from the original work and is not a substitute for it.”  Nevertheless, the Court affirmed the fair use finding below because HDL’s copying of the entire work was reasonably necessary to enable the full-search functionality—swiftly disposing of the Authors’ argument that copying the works on secondary servers and back-up tapes was excessive—and the database did not serve as a substitute for the original copyrighted works such that it affected their market or value.  The Second Circuit rejected the Authors’ market-harm arguments in no uncertain terms, finding the risk of a data breach enabling worldwide distribution of the works to be too speculative to be a cognizable injury (particularly in the face of “essentially unrebutted” evidence of HDL’s extensive security procedures) and the lost licensing revenue argument to be irrelevant where, as here, the transformative use does not serve as a substitute for the original work.

Although the Court did not find that the accessibility feature offered by the HDL was a transformative use because the purpose of making text available for reading or listening is unchanged from the original copyrighted work, it nevertheless found it was a fair use by citing to the legislative history of the Copyright Act.  The Second Circuit quoted extensively from the House Committee Report that accompanied the Copyright Act, which noted that there was little to no market for books accessible to the print disabled, and in light of this, making a single copy of a copyrighted work accessible to blind persons “would properly be considered a fair use under section 107.”

Finally, the Court vacated the district court’s judgment as to the preservation feature of the HDL and remanded.  Given the application of section 501, the Court did not believe that the record showed that plaintiffs owned any copyrighted works that would potentially be subject to copying and replacement by any of the member institutions. The district court is left to determine whether the Authors have standing to pursue claims with respect to the preservation feature of the HDL.

While this decision is an unqualified victory for proponents of the fair use doctrine, there are intriguing portions that may telegraph the Court’s thinking with respect to the Authors Guild’s separate appeal of a district court ruling that Google’s Google Books project was protected by fair use.  The district court there based much of its fair use conclusions on its finding that Google Books made invaluable contributions to education and culture.  The Second Circuit’s strong language here regarding transformative use and that it must serve a new and different function from the original work may signal that the Court will find that the fair use factors do not align in favor of a project that allows users to access actual portions of copyrighted works rather than just the frequency of search terms within the work.

Rising up from the Trenches: Ninth Circuit Broadly Interprets Breach of Contract Exclusion in Trademark Infringement Case

On May 23, 2014, the Ninth Circuit upheld a California district court decision that broadly interpreted the breach of contract exclusion in a commercial general liability policy to preclude coverage for all personal and advertising injury having even a minimal factual connection or incidental relationship to a breach of contract.  Trenches Inc. v. Hanover Ins. Co., No. 12-56642 (9th Cir. May 23, 2014).

The story began when Hoodz International and Hoodz North America entered into franchise agreements with Trenches, Inc., Trenches Holdings, Inc., and their executives.  Those agreements gave Trenches the right to operate a Hoodz franchise in the commercial kitchen exhaust cleaning business.  Hoodz had the right to terminate the agreement if Trenches or its executives had any felony convictions and obligated Trenches to stop using Hoodz’s trademarks in the event of a termination.

After learning about felony convictions against certain Trenches executives, Hoodz simultaneously terminated the franchise agreements and filed a lawsuit against Trenches. The parties reached a settlement a few days later, in which Hoodz agreed to conditionally reinstate the franchise agreements to allow Trenches to sell the franchises, and Trenches agreed to give Hoodz the right to enforce the post-termination obligations under the franchise agreements.  Shortly thereafter, Hoodz terminated the conditional agreement and sued Trenches again, this time alleging that Trenches continued using Hoodz’s trademarks in violation of its post-termination obligations.

Hoodz brought seven claims, including claims for breach of both the franchise and settlement agreements as well as a claim for trademark infringement and unfair competition, which was based on Trenches’ use of Hoodz’s trademark outside the scope of the settlement agreement.  Trenches tendered Hoodz’s complaint to Hanover Insurance Co., which denied the claim.  When Hanover refused to reconsider its denial, Trenches filed a coverage action.  Hanover then filed a motion to dismiss, claiming that the underlying suit did not come within coverage and that even it did, it fell within the policy’s exclusions.

On Hanover’s motion to dismiss, the district court first ruled that contrary to Hanover’s assertions, the claim fell within the policy’s personal and advertising injury coverage.  The policy covered claims arising out of “[t]he use of another’s advertising idea in your ‘advertisement…’” and the underlying complaint alleged both that Hoodz widely advertised and promoted its trademark and that Trenches used Hoodz’s trademark without permission in its own advertising.  Since Hoodz’s trademark was its advertising idea and Trenches allegedly used it in its advertising, the claim fell within personal and advertising injury coverage.

Nonetheless, the district court granted Hanover’s motion to dismiss because the underlying suit fell within the policy’s breach of contract exclusion, which applied to “[p]ersonal and advertising injury arising out of a breach of contract, except an implied contract to use another’s advertising idea in your ‘advertisement.’”  The court rejected Trenches’ position that the exclusion only applied to claims that would not have occurred but for the breach, and instead ruled that under California law, it applied to “any personal and advertising injury that bears a minimal connection or incidental relationship to the breach of contract.”  The court further noted that the exclusion applied if all claims arise out of the same factual situation, regardless of whether the claims had a separate and independent legal basis.  Since Hoodz’s trademark infringement and unfair competition claim arose out of the same factual situation as its breach of contract claim, the district court ruled that it fell within the breach of contract exclusion and was not covered by the policy.  Trenches appealed, but the Ninth Circuit affirmed the district court’s decision in a two page decision.

Breach of contract exclusions are designed to preclude coverage for those who do not fulfill obligations they assumed under a contract. This case is an example of just how broadly courts interpret those exclusions.