throbber
IN THE UNITED STATES DISTRICT COURT
`FOR THE DISTRICT OF DELAWARE
`
`IOENGINE, LLC,
`
`
`Plaintiff,
`
`
`v.
`
`PAYPAL HOLDINGS, INC.,
`
`
`Defendant.
`
`
`
`
`
`)
`)
`)
`)
`)
`)
`)
`)
`)
`)
`
`C.A. No. 18-452 CFC
`
`JURY TRIAL DEMANDED
`
`CONFIDENTIAL
`
`PLAINTIFF IOENGINE, LLC’S INITIAL CLAIM CHARTS
`
`Pursuant to Paragraph 4(c) and note 3 of the District of Delaware’s Default Standard for
`
`Discovery, Including Discovery of Electronically Stored Information (the “Default Standard for
`
`Discovery”), Plaintiff IOENGINE, LLC (“IOENGINE” or “Plaintiff’) hereby provides its Initial
`
`Claim Charts relating to each accused PayPal Holdings, Inc. (“PayPal” or “Defendant”) product
`
`or service (the “Accused Products”) and the asserted claims of U.S. Patent Nos. 8,539,047 (the
`
`“‘047 Patent”), 9,059,969 (the “‘969 Patent”), and 9,774,703 (the “‘703 Patent”) (collectively the
`
`“Patents-in-Suit”).
`
`PRELIMINARY STATEMENT
`
`IOENGINE has made a reasonable and good faith effort to identify infringing aspects of
`
`PayPal’s Accused Products. Discovery in this matter, however, has not been completed, and
`
`IOENGINE’s Claim Charts are based upon present knowledge and belief. Furthermore, should
`
`discovery uncover information relevant to the Accused Products, such that different versions or
`
`features of the Accused Products necessitate different or additional analysis, including
`
`infringement analysis under the doctrine of equivalents and direct and indirect infringement
`
`PayPal Ex. 1038, p. 1
`PayPal v. IOENGINE
`
`

`

`CONFIDENTIAL
`
`theories, IOENGINE reserves the right to amend, supplement, modify, and/or to provide further
`
`contentions and claims charts. See, e.g., Default Standard for Discovery, ¶ 4 n.3.
`
`Accordingly, these Claim Charts, attached hereto as Exhibits A-L, reflect IOENGINE’s
`
`current infringement analysis based on the limited information that has been produced by PayPal
`
`by the date for PayPal’s disclosures pursuant to Paragraph 4(b) of the Default Standard for
`
`Discovery, (which production was deficient at least for the reasons described in IOENGINE’s
`
`letters to Travis Jenson, counsel for PayPal, on September 27, 2018 and October 5, 2018 and as
`
`discussed in the parties’ September 11, 2018 and October 10, 2018 teleconferences), and the
`
`limited public information that is available upon a reasonable search.1 These Claim Charts are
`
`not intended to be exhaustive of all citations and/or evidence that IOENGINE may rely upon to
`
`show infringement at trial. These Claim Charts, and the citations included herein, are intended to
`
`provide evidence sufficient to relate each of the Accused Products to the asserted claims of the
`
`Patents-in-Suit. IOENGINE notes that, to the extent that the Accused Products are provided or
`
`used on or through multiple platforms and/or in different environments, the attached charts are
`
`intended to be representative of the corresponding functionality across all such multiple
`
`platforms/environments. Any examples provided herein are intended as examples, and do not
`
`limit or comprise the entirety of IOENGINE’s allegations of infringement. IOENGINE reserves
`
`the right to amend, supplement, modify, and/or provide further claim charts pursuant to Default
`
`Standard for Discovery, ¶ 4 n.3 or in accordance with any scheduling order that may be entered
`
`
`1 PayPal produced additional documents on October 18, 2018, nearly four weeks later than its
`documents were due under Paragraph 4(b) of the Default Standard for Discovery. IOENGINE
`will supplement these contentions, as necessary, following an appropriate review time for those
`documents.
`
`2
`
`PayPal Ex. 1038, p. 2
`PayPal v. IOENGINE
`
`

`

`CONFIDENTIAL
`
`by the Court, including based on any further discovery provided by PayPal, any expert discovery
`
`or report, or any other permissible reason.
`
`PayPal directly infringes the device and system claims at least by making, using, selling
`
`and offering for sale, devices and services with the identified functionalities in these Claim
`
`Charts. PayPal also infringes under the Doctrine of Equivalents, as any differences between the
`
`claimed inventions and the Accused Products are not substantial and the Accused Products
`
`perform substantially the same identified functionalities, in substantially the same way, to obtain
`
`or achieve the same result as the claimed limitations. With respect to the method claims, at least
`
`the use by PayPal of the identified functionalities in these Claim Charts constitutes direct
`
`infringement by PayPal. In addition, to the extent PayPal contends that PayPal itself is not
`
`performing one or more of the method steps—including when claimed program code is running
`
`on an end-user’s terminal or when claimed program code utilizes the end-user’s terminal to
`
`perform claimed functionality—the performance of method steps and use of claimed systems by
`
`end users is attributable to PayPal such that PayPal is liable as a direct infringer. PayPal is also
`
`liable for contributory infringement and/or inducement of infringement due to, for example,
`
`providing/selling the devices, program code, services and instructions that cause, induce, and/or
`
`contribute to direct infringement by PayPal’s Point of Sale “Partners,” and by users of these
`
`Partners’ and PayPal’s mobile payment apps.2 PayPal also jointly infringes the Patents-in-Suit
`
`
`2 PayPal has refused to produce documentation related to any POS Partner Apps (e.g., the Lavu
`Point of Sale App, TouchBistro App, Vend Register App, ERPLY cloud-based POS software,
`Brightpearl POS system, and TouchPoint POS system). See, e.g., PayPal’s Responses and
`Objections to IOENGINE’s First Set of Requests for Production of Documents, at 5-6. On
`September 11, 2018 the parties met and conferred on PayPal’s refusal to produce such
`documents, during which PayPal represented that the POS Partner Apps operate, from PayPal’s
`perspective, in the same way as the PayPal Here App. As such, references and citations to the
`PayPal Here App in these Claim Charts also apply to the POS Partner Apps, and any differences
`
`3
`
`PayPal Ex. 1038, p. 3
`PayPal v. IOENGINE
`
`

`

`CONFIDENTIAL
`
`by, for example, directing and controlling the infringing use of the Accused Products by PayPal’s
`
`Point of Sale “Partners” and users of these Partners’ and PayPal’s mobile payment apps.
`
`Additionally, the Accused Products constitute a material part of the invention and are not staple
`
`articles or commodities of commerce suitable for substantial non-infringing use. PayPal had
`
`actual knowledge of the Patents-in-Suit and notice of infringement at least as of the filing of the
`
`Complaint (and the date that IOENGINE sent a letter attaching a copy of the Complaint and the
`
`Patents-in-Suit to Louise Pentland, Esq. and Wanji Walcott, Esq., Executive Vice President,
`
`Chief Business Affairs and Legal Officer at PayPal, and Senior Vice President, General Counsel
`
`at PayPal, respectively by email and Federal Express. See D.I. 17, Declaration of Noah M.
`
`Leibowitz, at Ex. A), which included detailed descriptions of direct infringement of each of the
`
`Patents-in-Suit by each of the Accused Products.
`
`For each of IOENGINE’s Claim Charts below, the Accused Products listed share the
`
`same or substantially similar functionality, and any differences are immaterial to an analysis of
`
`whether or not those products infringe the Patents-in-Suit. Therefore, these charts also apply to
`
`any such products that similarly infringe the Patents-in-Suit.
`
`CLAIM CHARTS
`
`As used herein, “Infringed” means and includes infringement of a Patent-in-Suit both
`
`directly (alone or jointly) and indirectly (by way of inducement and contributory infringement),
`
`literally and/or under the Doctrine of Equivalents.
`
`As presently advised, IOENGINE relates the following claims of the Patents-in-Suit to
`
`PayPal’s Accused Products as follows:
`
`
`are immaterial to an analysis of whether or not POS Partner Apps participate in infringement of
`the Patents-in-Suit, jointly or otherwise.
`
`4
`
`PayPal Ex. 1038, p. 4
`PayPal v. IOENGINE
`
`

`

`CONFIDENTIAL
`
`a) at least claims 1, 3-4, 6-10, 12-21, 23-25, and 27-28 of the ‘047 Patent are Infringed by
`
`the PayPal Chip Card Reader, as illustrated by the exemplary Claim Chart attached hereto
`
`as Exhibit A;
`
`b) at least claims 1, 6-10, 12-21, 23-25, and 27-28 of the ‘047 Patent are Infringed by the
`
`PayPal Mobile Card Reader, as illustrated by the exemplary Claim Chart attached hereto
`
`as Exhibit B;
`
`c) at least claims 1, 3-4, 6-10, 12-21, 23-25, and 27-28 of the ‘047 Patent are Infringed by
`
`the PayPal Chip and Swipe Reader, as illustrated by the exemplary Claim Chart attached
`
`hereto as Exhibit C;
`
`d) at least claims 1, 3-4, 6-10, 12-21, 23-25, and 27-28 of the ‘047 Patent are Infringed by
`
`the PayPal Chip and Tap Reader, as illustrated by the exemplary Claim Chart attached
`
`hereto as Exhibit D;
`
`e) at least claims 1-8, 10, 13-16, 19-21, 24-25, and 27-28 of the ‘969 Patent are Infringed by
`
`the PayPal Chip Card Reader, as illustrated by the exemplary Claim Chart attached hereto
`
`as Exhibit E;
`
`f) at least claims 1-6, 8, 10, 13-16, 19-21, 24-25, and 28 of the ‘969 Patent are Infringed by
`
`the PayPal Mobile Card Reader, as illustrated by the exemplary Claim Chart attached
`
`hereto as Exhibit F;
`
`g) at least claims 1-8, 10, 13-16, 19-21, 24-25, and 27-28 of the ‘969 Patent are Infringed by
`
`the PayPal Chip and Swipe Reader, as illustrated by the exemplary Claim Chart attached
`
`hereto as Exhibit G;
`
`5
`
`PayPal Ex. 1038, p. 5
`PayPal v. IOENGINE
`
`

`

`CONFIDENTIAL
`
`h) at least claims 1-8, 10, 13-16, 19-21, 24-25, and 27-28 of the ‘969 Patent are Infringed by
`
`the PayPal Chip and Tap Reader, as illustrated by the exemplary Claim Chart attached
`
`hereto as Exhibit H;
`
`i) at least claims 55-63, 65, 67-68, 70-72, 74-75, 77-78, 81-87, 89-90, 92-98, 100-101, 103-
`
`112, 114, 116-117, 119-121, 123-124, and 129 of the ‘703 Patent are Infringed by the
`
`PayPal Chip Card Reader and/or by the PayPal Here Mobile Payment System Utilizing
`
`the PayPal Chip Card Reader, as illustrated by the exemplary Claim Chart attached hereto
`
`as Exhibit I;
`
`j) at least claims 55-59, 63, 65, 67-68, 70-72, 74-75, 77-78, 81-87, 89-90, 92-98, 100-101,
`
`103-108, 112, 114, 116-117, 119-121, 123-124, and 129 of the ‘703 Patent are Infringed
`
`by the PayPal Chip Card Reader and/or by the PayPal Here Mobile Payment System
`
`Utilizing the PayPal Mobile Card Reader, as illustrated by the exemplary Claim Chart
`
`attached hereto as Exhibit J;
`
`k) at least claims 55-63, 65, 67-68, 70-72, 74-75, 77-78, 81-87, 89-90, 92-98, 100-101, 103-
`
`112, 114, 116-117, 119-121, 123-124, and 129 of the ‘703 Patent are Infringed by the
`
`PayPal Chip Card Reader and/or by the PayPal Here Mobile Payment System Utilizing
`
`the PayPal Chip and Swipe Reader, as illustrated by the exemplary Claim Chart attached
`
`hereto as Exhibit K; and
`
`l) at least claims 55-63, 65, 67-68, 70-72, 74-75, 77-78, 81-87, 89-90, 92-98, 100-101, 103-
`
`112, 114, 116-117, 119-121, 123-124, and 129 of the ‘703 Patent are Infringed by the
`
`PayPal Chip Card Reader and/or by the PayPal Here Mobile Payment System Utilizing
`
`the PayPal Chip and Tap Reader, as illustrated by the exemplary Claim Chart attached
`
`hereto as Exhibit L.
`
`6
`
`PayPal Ex. 1038, p. 6
`PayPal v. IOENGINE
`
`

`

`CONFIDENTIAL
`
`
`
`SMITH, KATZENSTEIN & JENKINS,
`LLP
`
`
`/s/ Eve H. Ormerod
`Neal C. Belgam (No. 2721)
`Eve H. Ormerod (No. 5369)
`1000 West Street, Suite 1501
`Wilmington, DE 19801
`(302) 652-8400
`nbelgam@skjlaw.com
`eormerod@skjlaw.com
`
`Counsel for Plaintiff IOENGINE, LLC
`
`DATED: October 29, 2018
`
`OF COUNSEL:
`
`Noah M. Leibowitz
`Gregory T. Chuebon
`Dechert LLP
`1095 Avenue of the Americas
`New York, NY 10036
`(212) 698-3500
`noah.leibowitz@dechert.com
`greg.chuebon@dechert.com
`
`Derek J. Brader
`Dechert LLP
`Cira Centre
`2929 Arch Street
`Philadelphia, PA 19104-2808
`(215) 994-2437
`derek.brader@dechert.com
`\
`
`7
`
`PayPal Ex. 1038, p. 7
`PayPal v. IOENGINE
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket