2:17-cv-00268
Product Association Tech LLC v. Polyvore Inc
I. Executive Summary and Procedural Information
- Parties & Counsel:
- Plaintiff: Product Association Technologies LLC (Texas)
- Defendant: Polyvore, Inc. (Delaware)
- Plaintiff’s Counsel: Kizzia Johnson, PLLC
- Case Identification: 2:17-cv-00268, E.D. Tex., 04/05/2017
- Venue Allegations: Venue is alleged to be proper because Defendant is deemed to reside in the district and has allegedly committed acts of infringement in the district.
- Core Dispute: Plaintiff alleges that Defendant’s online shopping portal infringes a patent related to methods for using product codes to retrieve and display product information over the Internet.
- Technical Context: The case concerns early e-commerce architecture for linking from a retailer or aggregator website to an authoritative source of product information, such as a manufacturer's server.
- Key Procedural History: The patent-in-suit is subject to a terminal disclaimer, which may limit its enforceable term to that of an earlier patent in its family.
Case Timeline
| Date | Event |
|---|---|
| 1998-03-27 | U.S. Patent No. 6,154,738 Priority Date |
| 2000-11-28 | U.S. Patent No. 6,154,738 Issue Date |
| 2016-10-26 | Date of Accused Infringement Activity |
| 2017-04-05 | Complaint Filing Date |
II. Technology and Patent(s)-in-Suit Analysis
U.S. Patent No. 6,154,738 - "Methods and Apparatus for Disseminating Product Information via the Internet Using Universal Product Codes," issued November 28, 2000
The Invention Explained
- Problem Addressed: The patent's background section identifies the difficulty for consumers and resellers in locating detailed, up-to-date product information online, particularly when the uniform resource locator (URL) of the manufacturer's website is not known (’738 Patent, col. 1:40-52).
- The Patented Solution: The invention proposes a system where a standardized "universal product code" (such as a UPC) is embedded in a hyperlink on a web page. When a user activates the link, a request containing the product code is sent to a "cross-referencing resource." This resource looks up the code, identifies the correct Internet address for the server holding the product's information (e.g., the manufacturer's server), and sends a redirection message back to the user's browser, which then automatically fetches and displays the information from that address (’738 Patent, Abstract; col. 2:13-25). Figure 2 illustrates this architecture, showing a "Cross-Reference Table" (215) that maps product codes to Internet addresses.
- Technical Importance: The technology aimed to streamline e-commerce by allowing retailers to link to authoritative manufacturer data without having to host and maintain that information themselves, using product codes as a standardized access key (’738 Patent, col. 2:26-34).
Key Claims at a Glance
- The complaint asserts at least independent Claim 1 (Compl. ¶13).
- The essential elements of independent Claim 1 include:
- Establishing a cross-referencing resource with a database of cross-references between product code values and Internet addresses.
- Transmitting a web page containing a hyperlink that includes a specific universal product code value.
- A user's web browser receiving the web page and, upon activation of the hyperlink, transmitting a first request message (containing the product code) to the cross-referencing resource.
- The cross-referencing resource processing the first request to identify the corresponding Internet address and returning a redirection message to the browser.
- The browser automatically responding by transmitting a second request message to that identified Internet address.
- A web server at that address responding with product information, which the browser then automatically displays to the user.
- The complaint states that Plaintiff may assert other claims from the ’738 Patent (Compl. ¶13).
III. The Accused Instrumentality
Product Identification
- The accused instrumentalities are the "Polyvore shopping portal, www.polyvore.com, and any similar products and services" offered by the Defendant (collectively, "Products") (Compl. ¶14).
Functionality and Market Context
- The complaint describes the accused Products as an online ordering and e-commerce platform that disseminates product information online (Compl. ¶15). The system allegedly uses a database to create a correspondence between a product code (e.g., "130016-006-01") and an Internet address for a destination site that provides information about the product associated with that code (e.g., a "LANCASTER PARIS Pur Smooth Leather Bucket Bag") (Compl. ¶16). A screenshot provided in the complaint shows a product search results page from the Polyvore website (Compl. p. 5).
IV. Analysis of Infringement Allegations
’738 Patent Infringement Allegations
| Claim Element (from Independent Claim 1) | Alleged Infringing Functionality | Complaint Citation | Patent Citation |
|---|---|---|---|
| establishing a cross-referencing resource connected to the Internet which includes a database containing a plurality of cross-references...between a group of one or more universal product code values and an associated Internet address | The Polyvore platform allegedly includes or uses a database containing cross-references that specify a correspondence between a product code value and an associated Internet address for a source of product information. | ¶16 | col. 2:17-25 |
| transmitting via the Internet a Web page containing at least one hyperlink including a reference to separately stored information, said reference including a particular universal product code value that uniquely designates a selected product | The Products allegedly transmit a web page displaying products, where a hyperlink for a selected product includes a reference that contains a product code designating that product. A screenshot shows a search results page with a hyperlink for a handbag. | ¶18, p. 5 | col. 2:13-19 |
| employing a Web browser program to receive said Web page and display said Web page to a user | The Products allegedly employ a web browser program to receive and display the web page. | ¶19 | col. 2:17-19 |
| further employing said Web browser to respond to the activation of said hyperlink...by transmitting a first request message to said cross-referencing resource | When a user clicks a hyperlink, the browser allegedly transmits a first request message to the cross-referencing resource (the Polyvore database). | ¶19 | col. 2:19-22 |
| processing said first request message at said cross-referencing resource by referring to said database to identify the particular Internet address which corresponds to said particular universal product code value | The first request is allegedly processed by the Polyvore database by using the product code value to identify the corresponding Internet address. | ¶20 | col. 2:38-43 |
| and returning a redirection message to said Web browser which contains said particular Internet address | The system allegedly returns a redirection message containing the identified Internet address to the web browser. | ¶20 | col. 2:41-43 |
| employing said Web browser to automatically respond to said redirection message by transmitting a second request message to said particular Internet address | The web browser allegedly responds to the redirection message by automatically transmitting a second request to the destination address. | ¶21 | col. 2:43-45 |
| employing a Web server connected to the Internet at said particular Internet address to respond to said second request message by returning product information...to said Web browser | A server at the destination site allegedly responds by providing product information concerning the selected product (e.g., the Lancaster bag). A screenshot shows this product information page. | ¶22, p. 6 | col. 2:23-25 |
| and employing said Web browser program to automatically display said product information from said Web server to said user | The web browser allegedly causes the received product information to be automatically displayed to the user. | ¶22 | col. 2:43-45 |
Identified Points of Contention
- Scope Questions: The patent defines "universal product codes" to include standard codes like UPCs as well as "any other multi-industry or single industry standard product designation system" (’738 Patent, col. 4:55-57). The complaint alleges that Polyvore's proprietary identifier (e.g., "130016-006-01") meets this definition (Compl. ¶16). This raises the question of whether a platform-specific, internal product code can be construed as a "single industry standard product designation system" as contemplated by the patent.
- Technical Questions: The complaint's visual evidence shows a hyperlink that appears to redirect through an affiliate marketing network (
click.linksynergy.com) before reaching the final product page (forzieri.com) (Compl. p. 5). The infringement analysis may turn on whether this multi-hop architecture, involving an intermediary affiliate server, aligns with the two-request sequence ("first request" to a "cross-referencing resource" followed by a "second request" to a "particular Internet address") recited in Claim 1.
V. Key Claim Terms for Construction
The Term: "universal product code"
Context and Importance: The viability of the infringement claim hinges on whether the product identifiers used by Polyvore fall within the scope of this term. Practitioners may focus on this term because the accused system allegedly uses a proprietary code, not a publicly recognized standard like a UPC.
Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The patent provides an explicit definition that includes not only UPCs and EANs but also "any other multi-industry or single industry standard product designation system" (’738 Patent, col. 4:55-57). Plaintiff may argue this language is intentionally broad to capture any coding system used consistently within a given commercial context or industry, such as an e-commerce platform.
- Evidence for a Narrower Interpretation: The specification’s examples and context focus on codes managed by external, inter-company standards bodies like the Uniform Code Council and EAN International (’738 Patent, col. 4:49-55). Defendant may argue that the term requires a code that is "universal" or "standard" across multiple entities, not one that is proprietary to a single platform.
The Term: "cross-referencing resource"
Context and Importance: The accused system appears to involve multiple components, including the Polyvore platform, an affiliate network server, and a third-party retailer's server (Compl. ¶16, ¶20, p. 5). Defining which of these components, alone or in combination, constitutes the "cross-referencing resource" is critical to mapping the accused system to the claim steps.
Intrinsic Evidence for Interpretation:
- Evidence for a Broader Interpretation: The Abstract states the resource "may take the form of an independent HTTP server, an LDAP directory server, or the existing Internet Domain Name Service (DNS)," suggesting flexibility in its implementation and that it is defined by its function of translating a code to an address (’738 Patent, Abstract).
- Evidence for a Narrower Interpretation: Figures in the patent, such as Figure 2, depict a relatively centralized architecture with a distinct "Cross-Reference Table" (215) and "Query Handler" (204). Defendant may argue that the claim requires a more discrete component that performs the lookup, rather than a distributed process that spans multiple, unaffiliated third-party systems like an affiliate network.
VI. Other Allegations
The complaint does not contain counts for indirect or willful infringement.
VII. Analyst’s Conclusion: Key Questions for the Case
- A core issue will be one of definitional scope: can the term "universal product code," which the patent defines with reference to industry-wide standards like UPCs, be construed to cover a proprietary, platform-specific identifier used within the accused e-commerce system?
- A key evidentiary question will be one of architectural mapping: does the accused system's multi-step redirection process, which appears to route through an intermediary affiliate marketing server, perform the same sequence of steps as the more direct, two-request method recited in Claim 1, or is there a fundamental mismatch in technical operation?