Dow Jones & Co., Inc. v. Ablaise Ltd.

606 F.3d 1338, 95 U.S.P.Q. 2d (BNA) 1366, 2010 U.S. App. LEXIS 10916, 2010 WL 2143164
CourtCourt of Appeals for the Federal Circuit
DecidedMay 28, 2010
Docket2009-1524
StatusPublished
Cited by74 cases

This text of 606 F.3d 1338 (Dow Jones & Co., Inc. v. Ablaise Ltd.) is published on Counsel Stack Legal Research, covering Court of Appeals for the Federal Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Dow Jones & Co., Inc. v. Ablaise Ltd., 606 F.3d 1338, 95 U.S.P.Q. 2d (BNA) 1366, 2010 U.S. App. LEXIS 10916, 2010 WL 2143164 (Fed. Cir. 2010).

Opinion

MICHEL, Chief Judge.

This appeal arises from a decision of the United States District Court for the District of Columbia granting summary judgment of invalidity against appellants Ablaise Ltd. and General Inventions Institute A, Inc.’s (collectively, “Ablaise”) U.S. Patent Nos. 6,961,737 (the '737 patent) and 6,295,530 (the '530 patent). Specifically, the district court held that the asserted claims of the '737 patent were invalid as obvious under 35 U.S.C. § 103 and that the asserted claims of the '530 patent were invalid under 35 U.S.C. § 102 as anticipated by prior art. Additionally, Ablaise appeals the district court’s denial of its motion to dismiss appellees’ Dow Jones & Co., Inc. and Dow Jones Reuters Interactive, LLC’s (d/b/a Factiva) (collectively, “Dow Jones”) claim against the '530 patent on the grounds that Ablaise’s proffer of a covenant not to sue Dow Jones for infringement of that patent divested the court of subject matter jurisdiction. For the reasons set forth below, we reverse the district court’s denial of Ablaise’s motion to dismiss Dow Jones’ invalidity claim against the '530 patent and affirm the district court’s grant of summary judgment that the asserted claims of the '737 patent are invalid as obvious. Because the district court lacked subject matter jurisdiction to hear Dow Jones’ claim against the '530 patent, this court cannot reach the question of whether the asserted claims of that patent are invalid.

I.

A. The Patents-in-suit

The '737 and '530 patents-in-suit both claim a method for generating computer web pages that are generated and customized for the specific individual viewing them based upon information encoded in the signal sent to the location generating the pages.

In the early 1990s, the continuing development and increasing availability of the Internet and the arrival of more powerful personal computers (“PCs”) set the stage for the advent of the World Wide Web (the “Web”). The functioning of the Web depends upon a basic technology, Hypertext Transfer Protocol (“HTTP”) and a computer language, Hypertext Markup Language (“HTML”). HTTP is an Internet protocol that enables a Web browser (a program installed upon an individual’s PC) to request a Web server (a Web site at which information is stored) to send specific content in the form of a Web page to the user’s Web browser. This content includes information, in the form of HTML content, which specifies the formatting of the layout and informational content of the web page displayed on the PC user’s computer screen.

HTML is a language embodying sets of instructions that control the format of a Web page displayed on the browser application of a user’s PC. HTML employs particular instructions, known as “tags” to determine the appearance of a Web page. A tag is designated by placing the instruction within the symbols < >. For example, the tag <b> indicates that the text following the tag should be in boldface type and the tag </b> indicates the end of the boldface text sequence. It is undisputed that by May 15, 1995 (the priority date claimed by the '737 patent and the ’530 patent), HTML was well known to persons of ordinary skill in the art of Web design.

*1341 In the nascent days of the Web, Web pages were typically constructed and stored as single, invariant handcoded pages. Thus, for a company making its catalogue available on the Web, each product in the catalog required that its own page be individually constructed and stored separately. Needless to say, for a company that offered hundreds or thousands of changing products, constructing a page for each was extremely labor-intensive. Moreover, each Web page so constructed and stored would appear identical upon every user’s screen, regardless of the user’s preferences or her PC’s capabilities.

A more flexible and less costly solution to this situation is to dynamically generate Web pages upon user demand (colloquially referred to as being generated “on the fly”). In this method, the HTML formatting information for a given Web page would be generated automatically only after the page was requested by the PC user. It is undisputed by the parties that by May 15, 1995, the ability of Web Site developers to construct Web pages on the fly by using programs known as Common Gateway Interfaces (“CGI programs” or “CGI scripts”) was well known in the art. CGI programs are standard protocols that define how the software of a Web server delegates the generation of Web pages to the browser on a user’s PC. Using a CGI program, a person of ordinary skill in the art could create individualized, dynamically-generated Web pages for each end user.

The '737 and '530 patents each claim methods for using a Web server to send individualized content and formatting instructions in the form of Web pages that are generated on the fly in response to user preference information encoded in the user’s HTTP request for the specific Web page. At issue in this appeal are claims 1, 3, 4, and 6 of the '737 patent and claims 1-3 of the '530 patent. However, in the district court, both parties focused on the first claim of each patent, agreeing that if that claim is invalid, the remaining asserted claims are also invalid. Claim 1 of the '737 patent discloses:

A method for serving pages of viewable data to browsing devices connected to a network, wherein a page of said viewable data comprises content data defining text and/or graphics and formatting data which specifies locations of said text and/or graphics within a page, and said viewable data is displayed at a browsing device such that locations of said text and/or graphics depend on said formatting data, said method comprising:
identifying requests from browsing devices that define a request for specified content data; storing content data;
storing executable functions;
maintaining a user database comprising information relating to user preferences;
and in response to identifying a request for specified content data and a user identifier;
(a) reading user preference information from said user database in response to a received user identifier;
(b) selecting stored content data in dependence upon the content data specified in a received request;
(c) receiving format identifiers identifying the type of formatting required;
(b) selecting a set of stored functions in dependence upon a received format identifier and said read user information; and
(e) executing said set of functions to generate viewable data comprising *1342 said selected content data and formatting data.

’737 patent col.19 1.65-col.20 1.16. Claim 4 teaches a “serving device” that performs the method recited in claim 1.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Cite This Page — Counsel Stack

Bluebook (online)
606 F.3d 1338, 95 U.S.P.Q. 2d (BNA) 1366, 2010 U.S. App. LEXIS 10916, 2010 WL 2143164, Counsel Stack Legal Research, https://law.counselstack.com/opinion/dow-jones-co-inc-v-ablaise-ltd-cafc-2010.