Rembrandt Social Media, Lp v. Facebook, Inc.

640 F. App'x 943
CourtCourt of Appeals for the Federal Circuit
DecidedFebruary 25, 2016
Docket2014-1812
StatusUnpublished

This text of 640 F. App'x 943 (Rembrandt Social Media, Lp v. Facebook, Inc.) 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
Rembrandt Social Media, Lp v. Facebook, Inc., 640 F. App'x 943 (Fed. Cir. 2016).

Opinion

PROST, Chief Judge.

Rembrandt Social Media, LP (“Rembrandt”) appeals from a final decision of the United States District Court for the Eastern District of Virginia. Following a five-day jury trial, the district court held that asserted claims of U.S. Patent No. 6,415,316 (“'316 patent”) and U.S. Patent No. 6,289,362 (“'362 patent”) (collectively, “patents at issue”) were invalid and not infringed by Faeebook, Inc. (“Facebook”). We affirm the district court’s noninfringement determinations and do not reach the issues with respect to validity.

Background

The patents at issue relate to web-based diary systems that allow non-technical users to post content on the internet. Users post content, such as text, images, videos, or links to other web pages, to personal diary pages, which appear as web pages in a browser. '316 patent col. 6 1. 30-col. 7.1. 20.

The '316 patent discloses methods for displaying and updating a diary page. A *945 key limitation of the '316 patent is “assembling the cohesive diary page by dynamically combining the content data and the page design in accordance with the configuration information.” This generally refers to the way in which diary pages are assembled. In a preferred embodiment in the '316 patent, a “diary applet” performs this process by downloading diary content (“content data”) and information about how the page should be displayed (“page design” and “configuration information”) from a central diary server and generating an HTML document for the requested diary page. Id. at col. 6 11. 38-43. The generated page is then passed to the web browser for rendering and display. Id. at col. 711. 3-11.

Rembrandt asserts dependent claims 4, 20, and 26 of the '316 patent. Representative claim 4 (and claim 1, from which it depends) recites:

1. A method of organizing information for display, comprising: sending from a diary server to a user system, a .diary program capable of being executed by a browser in the user system;
sending diary information from the diary server to the user system, the information comprising content data including an associated time, a page design to specify the presentation of the content data, and configuration information for controlling behavior of a cohesive diary page, the configuration information including privacy level information; assembling the cohesive diary page by dynamically combining the content data and the page design in accordance mth the configuration information for the cohesive diary page to be displayed by the diary program running in the browser;
receiving by the diary server at least one request for at least one change concerning the diary information, from the diary program in the user system; and sending, by the diary server to the user system, new diary information for changing the cohesive diary page.
4. The method of claim 1 wherein the new diary information is for changing content of the diary page without changing a general appearance of the diary page.

Id. at col. 23 l. 44-col. 24. l. 44, col. 24 11. 47-49 (emphasis added).

The '362 patent also describes displaying and updating a diary page, but focuses more specifically on using an “annotated universal address” (“AUA”) to transfer and display content. '362 patent col. 1 1. 65-col. 2 1. 2. An AUA is a data structure, which contains a “universal address (e.g., a uniform resource locator or URL)” for a piece of content and “annotations,” which provide information on how the piece of content should be handled, such as expiration date, size, or privacy level. Id. at col. 6 1. 53-col. 7 1. 15. Similar to the '316 patent, a key limitation is “dynamically generating a page definition,” which also refers to the way in which diary pages are assembled. In a preferred embodiment, a “diary applet” will generate a page with content retrieved using an AUA and infor-' mation about how the content should be displayed (“presentation context”). Id. at col. 7 ll. 32-65.

Rembrandt asserts dependent claim 8 of the '362 patent. Claim 8 (and claim 1, from which it depends) of the '362 patent reads:

1. . A computer-based method, comprising the steps of:
receiving from a client a request for access to a content object;
responsive to the request of the client, identifying an annotated universal address (AUA) having a universal address *946 identifying a-location of the content object and having an annotation authored by a content provider for controlling an aspect of a presentation of the object, the AUA being present in an AUA database containing one AUA; responsive to the request of the client, identifying a presentation context for controlling ion behavior of the object; and
transmitting to the client the presentation context, the AUA and an applet for dynamically generating a page definition for the presentation of the object, the page definition being generated from the presentation context and the AUA. 8. The method of claim 1 wherein the annotation further comprises: at least one content provider authored restriction concerning subsequent presentation of the object.

Id. at col. 19 ll. 49-67, col. 21 ll. 64-67 (emphases added).

This appeal primarily concerns Face-book’s BigPipe technology, which was introduced in 2009. BigPipe is an optimization feature which allows Facebook pages to display more quickly. It accomplishes this by breaking down a Facebook page into smaller chunks, called “page-lets,” that can be loaded in parallel. As pagelets are retrieved to a user’s computer, client-side BigPipe code inserts HTML pertaining to each pagelet into a single HTML document. If the HTML contains references to images, CSS, JavaScript, or other resources needed by the pagelet, the browser will download them. Once all of the HTML and supporting resources have been retrieved, the browser will' display the Facebook page.

Certain aspects of Facebook postings are also at issue. On Facebook, individual posts can be identified using a unique URL, or “permalink.” On the back-end, Facebook does not store permalinks in their entirety; instead, Facebook stores an identifier (such as an ID number) for each individual post and programmatically constructs permalinks using this information.

Procedural History

On February 4, 2013, Rembrandt sued Facebook in the United States District Court for the Eastern District of Virginia. Following claim construction briefing, the parties agreed on the following relevant constructions:

Cohesive diary page (’316 patent): A diary page in which the content data and the page design are fully integrated for display.
Content data (’316 patent): Information that may be displayed to a user that is independent of the page design. Dynamically generating a page definitions (’362 patent): Creating a page definition at the client at the time it is needed

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

Related

Cite This Page — Counsel Stack

Bluebook (online)
640 F. App'x 943, Counsel Stack Legal Research, https://law.counselstack.com/opinion/rembrandt-social-media-lp-v-facebook-inc-cafc-2016.