throbber
Case 5:19-cv-00036-RWS Document 212 Filed 03/06/20 Page 1 of 6 PageID #: 8836
`
`
`
`
`MAXELL, LTD.,
`
`v.
`
`APPLE INC.,
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`TEXARKANA DIVISION
`
`
`Case No. 5:19-cv-00036-RWS
`
`Plaintiff,
`
`Defendant.
`
`LEAD CASE
`
`JURY TRIAL DEMANDED
`
`
`
`
`
`
`
`
`
`
`MAXELL, LTD.’S OPPOSED MOTION FOR EXTENSION OF TIME TO
`SUPPLEMENT INFRINGEMENT CONTENTIONS PURSUANT TO P.R. 3-1(g)
`
`
`
`
`
`
`
`
`
`
`
`PUBLIC VERSION
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 212 Filed 03/06/20 Page 2 of 6 PageID #: 8837
`
`
`
`
`
`
`Pursuant to the Court’s Order (D.I. 204) and in view of the state of the discovery
`
`described below, Maxell seeks a 10-day extension of time to supplement its infringement
`
`contentions pursuant to P.R. 3-1(g) on March 23, 2020 as opposed to March 13, 2020.
`
`In the Order, the Court states that, “[b]ased on Apple’s representation [that it completed
`
`its source code production on February 12], Maxell’s 30-day deadline began to run on February
`
`12, 2020. Accordingly, Maxell’s deadline to serve revised infringement contentions pursuant to
`
`this Order is March 13, 2020.” D.I. 204 at 5. But the representation the Court relied upon in
`
`setting its deadline was not accurate. Apple did not complete its source code production on
`
`February 12. It in fact made at least one additional production on February 19. See Ex. B (2/20/20
`
`Email Zhou to Siddiqui).
`
`In addition to producing source code after February 12, Apple has not provided an up-
`
`to-date response to Maxell’s interrogatory which requests that Apple identify, for each directory
`
`of source code made available, the accused products and/or operating system versions to which
`
`each directory corresponds. Apple admits that its most recent response to this interrogatory,
`
`dated February 6, 2020, addresses only “source code made available for inspection as of January
`
`31” and does not identify the corresponding accused products/operating system versions
`
`associated with any code produced after that date. See Ex. C (2/18/20 Email Pensabene to
`
`Siddiqui). This means that as of the filing of this Motion, Apple has not provided the necessary
`
`information for Maxell to conduct a meaningful source code review and provide citations in its
`
`supplemental contentions, for at least the source code produced since January 31. Apple also
`
`admits that it still has not produced source code for Express Transit mode, an accused
`
`functionality for the ’794 Patent and a deficiency Maxell identified as early as October 11, 2019.
`
`See Ex. A (2/26/20 Ltr. Pensabene to Beaber at fn. 1); Ex. D (10/11/19 Ltr. Beaber to Zhou at
`
`
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 212 Filed 03/06/20 Page 3 of 6 PageID #: 8838
`
`
`
`
`2).1
`
`Moreover, based on Apple’s February 6 supplemental interrogatory response linking
`
`source code to accused products/operating system versions, it appears that Apple still has not
`
`produced source code for any accused functionality2 for iPadOS, which is the operating system
`
`for eleven accused iPad products.3 Maxell identified this deficiency to Apple as early as
`
`November 14, 2019. Ex. E (11/14/19 Ltr. Beaber to Beasley and Zhou).
`
`The requested extension is necessary in view of the above-stated facts regarding Apple’s
`
`source code production. Perhaps recognizing the faults in its source code production, and the
`
`fact that it produced source code after its represented date of February 12, even Apple relayed to
`
`Maxell that it expected Maxell to serve supplemental contentions by March 23—the date Maxell
`
`now requests of the Court. Ex. A (2/26/20 Ltr. Pensabene to Beaber at 2-3). In view of Apple’s
`
`correspondence, Maxell was surprised to learn Apple opposes this modest extension. Ex. F
`
`(3/2/2020 Email Pensabene to Miller).
`
`Apple asserts that the Court’s Order requires that Maxell must serve its supplemental
`
`contentions by March 13 and then, if Maxell wishes to address the code that Apple produced on
`
`February 19, Maxell should seek leave to do so. Id. Given that it is already known and admitted
`
`that Apple produced source code after the date represented to and relied upon by the Court, it is
`
`highly inefficient to require Maxell to prepare back-to-back supplemental contentions and go
`
`
`1 Apple states
`
`
`
`
`
`. See Ex. A.
`2 These include, at least, Maps, AirDrop, FaceTime, Find My Friends, Bluetooth pairing, and
`Camera functionality.
`3 These include the “12.9-inch iPad Pro, 11-inch iPad Pro, 10.5-inch iPad Pro, 9.7-inch iPad
`Pro, iPad (7th generation), iPad (6th generation), iPad (5th generation), iPad mini (5th
`generation), iPad mini 4, iPad Air (3rd generation), and iPad Air 2”). See
`https://www.apple.com/ipados/.
`
`
`
`2
`
`PUBLIC VERSION
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 212 Filed 03/06/20 Page 4 of 6 PageID #: 8839
`
`
`
`
`through the process of seeking leave of Court to do so. Maxell should not be required to expend
`
`this additional effort based on Apple’s failure to meet its own deadline. It is also contrary to the
`
`applicable rule: Maxell “need not comply with P.R. 3-1 for those claim elements until 30 days
`
`after source code for each Accused Instrumentality is produced by the opposing party.” P.R. 3-
`
`1(g). Apple’s source code production was not completed on February 12.
`
`Maxell will endeavor to supplement its P.R. 3-1 Disclosures as ordered by the Court to
`
`the best of Maxell’s ability, even given the remaining holes in Apple’s source code production
`
`and related interrogatory response. However, Maxell’s agreement to supplement its P.R. 3-1
`
`Disclosures is not a concession that Maxell has not been prejudiced as a result of Apple’s
`
`piecemeal and belated source code production. Indeed, Maxell has been (and continues to be)
`
`prejudiced by Apple’s discovery conduct and despite agreeing to supplement, reserves its rights
`
`to seek adequate remedies and relief.
`
`
`
`Dated: March 3, 2020
`
`
`By:
`
`
`
`
`3
`
`/s/ Jamie B. Beaber
`Geoff Culbertson
`Kelly Tidwell
`Patton, Tidwell & Culbertson, LLP
`2800 Texas Boulevard (75503)
`Post Office Box 5398
`Texarkana, TX 75505-5398
`Telephone: (903) 792-7080
`Facsimile: (903) 792-8233
`gpc@texarkanalaw.com
`kbt@texarkanalaw.com
`
`Jamie B. Beaber
`Alan M. Grimaldi
`Kfir B. Levy
`James A. Fussell, III
`Baldine B. Paul
`Tiffany A. Miller
`Saqib J. Siddiqui
`Bryan C. Nese
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 212 Filed 03/06/20 Page 5 of 6 PageID #: 8840
`
`
`
`
`
`
`
`
`William J. Barrow
`Alison T. Gelsleichter
`Clark S. Bakewell
`MAYER BROWN LLP
`1999 K Street, NW
`Washington, DC 20006
`Telephone: (202) 263-3000
`Facsimile: (202) 263-3300
`jbeaber@mayerbrown.com
`agrimaldi@mayerbrown.com
`klevy@mayerbrown.com
`jfussell@mayerbrown.com
`bpaul@mayerbrown.com
`tmiller@mayerbrown.com
`ssiddiqui@mayerbrown.com
`bnese@mayerbrown.com
`wbarrow@mayerbrown.com
`agelsleichter@mayerbrown.com
`cbakewell@mayerbrown.com
`
`Robert G. Pluta
`Amanda Streff Bonner
`Mayer Brown LLP
`71 S. Wacker Drive
`Chicago, IL 60606
`(312) 782-0600
`rpluta@mayerbrown.com
`asbonner@mayerbrown.com
`
`Counsel for Plaintiff Maxell, Ltd.
`
`CERTIFICATE OF CONFERENCE
`
`I certify that Plaintiff Maxell, Ltd. has complied with the requirements of Local Rule CV-
`7(h). Specifically, Maxell sent Apple an email on February 29, 2020 stating its intention to move
`for the extension requested herein and sought Apple’s position on such motion. Apple responded
`via email on March 2, 2020 stating it would oppose any such request. On March 3, 2020, the
`parties held a telephonic meet and confer, which was attended by lead and local counsel for both
`parties. Maxell and Apple were not able to reach agreement related to the extension requested
`by Maxell in this Motion.
`
`
`/s/ Jamie B. Beaber
`Jamie B. Beaber
`
`
`
`
`
`/s/ Geoff Culbertson
`Geoff Culbertson
`
`
`
`
`
`4
`
`
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 212 Filed 03/06/20 Page 6 of 6 PageID #: 8841
`
`
`
`
`CERTIFICATE OF SERVICE
`
`The undersigned certifies that all counsel of record who are deemed to have consented to
`electronic service are being served this 3rd day of March, 2020, with a copy of this document via
`electronic mail.
`
`
`/s/ Jamie B. Beaber
`Jamie B. Beaber
`
`
`
`
`
`
`
`CERTIFICATE OF AUTHORIZATION TO FILE UNDER SEAL
`
`I hereby certify that the foregoing document is authorized to be filed under seal pursuant
`to the Protective Order entered in this case.
`
`
`/s/ Jamie B. Beaber
`Jamie B. Beaber
`
`
`
`
`
`
`
`
`
`5
`
`PUBLIC VERSION
`
`

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