throbber
Case 5:19-cv-00036-RWS Document 245 Filed 03/26/20 Page 1 of 11 PageID #: 9509
`
`
`
`
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`TEXARKANA DIVISION
`
`
`MAXELL, LTD.,
`
`v.
`
`APPLE INC.,
`
`
`Plaintiff,
`
`Defendant.
`
`Case No. 5:19-cv-00036-RWS
`
`JURY TRIAL DEMANDED
`
`
`
`
`
`
`
`
`MAXELL, LTD.’S OPPOSITION TO APPLE INC.’S MOTION TO COMPEL
`COMPLETE RESPONSES TO INTERROGATORY NOS. 6, 10, 12, 17, AND 19
`
`
`
`
`
`
`
`
`
`PUBLIC VERSION
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 245 Filed 03/26/20 Page 2 of 11 PageID #: 9510
`
`
`
`
`Table of Contents
`
`A. Maxell Has Appropriately Responded to Interrogatory Nos. 6, 12, and 19 ............. 1
`B. Maxell Properly Relies on Rule 33(d) for Interrogatory Nos. 10 and 17 .................. 4
`C. Maxell Has Not “Selectively Responded” with Information on Behalf of Hitachi... 6
`
`i
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 245 Filed 03/26/20 Page 3 of 11 PageID #: 9511
`
`
`
`
`Apple’s motion is an attempt to show it is an aggrieved party, to distract the Court from
`
`Apple’s own discovery misconduct. While Maxell has spent well over half a year pushing Apple
`
`for relevant discovery regarding the design and operation of the accused products and
`
`functionalities, Apple has demanded discovery that is plainly outside the scope of the case, or very
`
`clearly outside Maxell’s possession, custody and control, to deflect from the relevant discovery it
`
`has and continues to improperly withhold. Here, for example, Apple (1) demands that Maxell
`
`provide a basis for a position Maxell does not hold and is not asserting and (2) insists again that
`
`Maxell provide information that is Hitachi’s and not Maxell’s (or within Maxell’s possession,
`
`custody or control). Finally, Apple requested Maxell provide all communications between Maxell
`
`and certain other entities, but then claims Maxell’s production of these very communications is
`
`not responsive and now demands Maxell summarize these for Apple.
`
`Apple’s motion is a clear attempt to distract from its own discovery misconduct by lobbing
`
`accusations at Maxell. These allegations are unsupported by the record and should be rejected.
`
`A. Maxell Has Appropriately Responded to Interrogatory Nos. 6, 12, and 19
`
`Interrogatory No. 6 requests that Maxell provide, “for each claim limitation of the
`
`asserted claims,” “in chart or table format,” support for the contention that each claim limitation
`
`meets the written description and enablement requirements of 35 U.S.C. § 112, ¶ 1. The request
`
`relates to every claim limitation of every asserted claim. But the Asserted Patents are presumed
`
`valid, and Apple has not alleged lack of enablement or written description for each asserted
`
`limitation. See Ex. A (Excerpts of Apple Invalidity Contentions). Apple’s demand that Maxell
`
`provide support for claim limitations that even Apple has not challenged improperly seeks to shift
`
`the burden to Maxell to demonstrate validity and is overly broad, unduly burdensome, and not
`
`proportional to the needs of the case. Maxell should not have to defend against claims that have
`
`not been put at issue.
`
`
`
`1
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 245 Filed 03/26/20 Page 4 of 11 PageID #: 9512
`
`
`
`
`Courts facing similar interrogatories have not required responses. One such court held:
`
`Although this interrogatory is framed in terms of claim-by-claim priority dates, the
`request for mapping claim elements to particular portions of specifications, albeit to
`justify the associated priority dates, seems to make it more like some sort of written
`description contentions. And, although the Court does not find parties are absolutely
`precluded from seeking discovery in a chart format…, the Court recognizes that
`demanding this level of specificity in a claim chart, particularly the mapping it
`demands, is a significant burden. It … is the type of “scorched earth,” “no stone
`unturned” (potentially numerous times) approach to discovery the changes to Rule
`26 were intended to curb. Given the other avenues for discovering this information
`already provided and the burden imposed in responding to it, the Court finds no
`further response to the interrogatory is required.
`
`Finjan, Inc. v. ESET, LLC, No. 3:17-cv-00183-CAB-BGS, 2018 WL 4772124, at *5 (S.D. Cal.
`
`Oct. 3, 2018), adopted by, No. 3:17-CV-00183-CAB-BGS, 2018 WL 6075797 (S.D. Cal. Nov. 21,
`
`2018)). Building off such rationale, and relying on the fact that the defendants did not limit their
`
`interrogatory to the claims for which they asserted § 112 support to be lacking, this Court has
`
`similarly held that such element-by-element mapping is not proportional to the needs of the case.
`
`Sol IP, LLC v. AT&T Mobility LLC, No. 2:18-cv-00526-RWS-RSP, 2020 WL 60140, at *2 (E.D.
`
`Tex., Jan. 5, 2020). Noteworthy, both of these cases dealt with the establishment of priority dates,
`
`not the broader blanket validity analysis Apple is pushing here.1
`
`Interrogatory No. 12 asks that Maxell state the date that it first became aware of Apple’s
`
`manufacture, use, or sale each accused product. Although Apple’s heading asserts “Maxell Has
`
`Not Responded (At All) To” Interrogatory No. 12, even the body of Apple’s motion demonstrates
`
`that to be untrue. Maxell has responded as to Maxell’s first awareness: “Maxell became aware of
`
`[Apple’s infringement] when it took over the negotiations with Defendant and continued its
`
`investigation thereafter, resulting in the filing of the Complaint for this litigation . . . . Maxell
`
`
`1 Apple complains that Maxell’s fact witnesses do not have information responsive to this interrogatory,
`but Maxell made inventors available for deposition, who could have been questioned on these topics.
`Experts will also be available to address the issue to the extent raised by Apple in its expert reports.
`2
`
`
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 245 Filed 03/26/20 Page 5 of 11 PageID #: 9513
`
`
`
`
`further incorporates herein by reference its response, including any supplements or amendments
`
`thereto, to Defendant’s Interrogatory No. 1.” D.I. 224 at Ex. A (“Page 40”). Apple’s complaint is
`
`not that Maxell has not responded, but rather that Maxell has not identified when Hitachi became
`
`aware of the accused products. But, outside of the information regarding the first licensing meeting
`
`in June 2013 that was transferred to Maxell from Hitachi Consumer Electronics (HCE) and
`
`Maxell’s subsequent actions (all of which was detailed in Maxell’s response to Interrogatory No.
`
`1, incorporated by reference), Maxell is not in possession, custody, or control of information
`
`related to Hitachi’s investigation and knowledge. This issue was already addressed by the Court
`
`in its denial of Apple’s prior motion to compel. D.I. 202.
`
`Interrogatory No. 19 states “To the extent Maxell contends that Maxell has complied with
`
`35 U.S.C. § 287 with respect to [Practicing/Licensed Products] or that its compliance with 35
`
`U.S.C. § 287 for the [Practicing/Licensed Products] was not required, state the complete factual
`
`and legal bases for such contention.” Importantly, this interrogatory covers only constructive
`
`notice through marking and Maxell very clearly responded that it is not relying on constructive
`
`notice under 35 U.S.C. § 287 in this litigation:
`
`Maxell is not relying on compliance with the marking of its products or its licensees’
`products to satisfy 35 U.S.C. § 287 for purposes of notice in this litigation. As noted in
`responses to other interrogatories and in its Complaint, Maxell has relied on the notice
`provision of 35 U.S.C. § 287.
`
`D.I. 224. at Ex. C (“Page 8”). Maxell also clarified this in correspondence and during a meet and
`
`confer. See, e.g., Ex. B, 2/19/20 Ltr. Beaber to Pensabene (“Given Maxell’s position that it is not
`
`‘contending’ that it complied with the marking requirement or that compliance was not required
`
`for purposes of notice in this litigation, no further information in response was required.”). Maxell
`
`should not be forced to address how it can prove constructive notice when it has committed not to
`
`rely on constructive notice. As it states in its response, Maxell has relied on the actual notice
`
`
`
`3
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 245 Filed 03/26/20 Page 6 of 11 PageID #: 9514
`
`
`
`
`provision of 35 U.S.C. § 287. In view of Maxell’s clearly stated position, the information Apple
`
`seeks is not relevant to any claim or defense. Apple’s continued demand is unquestionably overly
`
`broad, unduly burdensome, and not proportional to the needs of the case.
`
`B. Maxell Properly Relies on Rule 33(d) for Interrogatory Nos. 10 and 17
`
`Interrogatory No. 10 asks Maxell to “[d]escribe in detail all communications” between
`
`Maxell and any third-party regarding the subject matter of the Asserted Patents as well as the
`
`identity of any license agreements relating to the patents. In response, Maxell identified (1) in
`
`narrative format, the licenses which may cover the Asserted Patents and where in its production
`
`such licenses could be found, (2) in narrative format, the entities that Maxell or HCE offered to
`
`license and/or engaged in licensing or settlement discussions, but with whom no license was
`
`concluded, (3) in narrative format, the complaints filed by Maxell in furtherance of its licensing
`
`efforts, (4) where in its production the exact communications of which Apple was asking could be
`
`found, and (5) where deposition testimony of its corporate representative, which touched on this
`
`topic, could be located. Ex. C. In other words, Maxell provided a narrative response and an
`
`identification pursuant to Rule 33(d) of the exact communications requested in the interrogatory.
`
`Maxell’s response, in part through the identified documents, therefore provides all the details of
`
`the communications, including the identity of persons involved, dates of communications,
`
`products/patents discussed, outcome of communications, and resulting royalty rates and terms.
`
`Although Maxell did not exclusively do so, this is precisely the type of interrogatory for
`
`which it is appropriate to rely on Rule 33(d). The interrogatory seeks details on every
`
`communication. The best response to this is to produce every communication, which is what
`
`Maxell did. Anything less would be less than a full response. For example, had Maxell created an
`
`index of the produced communications from scratch, that would have provided a limited summary
`
`of the information that the documents themselves convey.
`4
`
`
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 245 Filed 03/26/20 Page 7 of 11 PageID #: 9515
`
`
`
`
`To the extent that is what Apple seeks, the burden of doing so is the same for Apple as for
`
`Maxell. Apple’s “unfamiliarity” would not prevent it from being able to review the precise
`
`communications it requested. The communications do not use proprietary or internal codes or
`
`nomenclature.2 And Apple’s request for oral communications is redundant because relevant oral
`
`communications were memorialized in the written communications. Finally, Maxell has not sought
`
`to avoid responding based on knowledge being held by an attorney versus Maxell itself.
`
`Interrogatory No. 17 seeks the basis and support for Maxell’s claim that it is entitled to
`
`damages for infringement prior to the filing of this lawsuit, including an identification of the
`
`specific time period for which damages are recoverable. In response, Maxell incorporated by
`
`reference its response to Interrogatory No. 1 (which set forth details regarding Maxell’s actual
`
`notice of infringement to Apple) and its response confirming it is not relying on constructive notice
`
`in this case. Maxell further identified the specific time periods before March 15, 2019 for which it
`
`contends damages are recoverable for each asserted patent (which correspond to the actual notice
`
`dates), the assignment documents between HCE, Hitachi Maxell, and Maxell, Ltd., and the prior
`
`negotiation materials between Apple, HCE, Maxell, and MCA. Apple’s characterization of
`
`Maxell’s response as “a non-descript list of bates ranges” is simply wrong.3
`
`Apple apparently asserts Maxell’s response is deficient because Maxell has not identified
`
`the specific terms of the assignments that convey the rights to collect past damages. Apple argues
`
`it is not in the same position as Maxell to determine what agreements Maxell contends entitle it to
`
`collect past damages. But Maxell’s response does not task Apple with doing so. Maxell identified
`
`
`2 Apple asserts that Maxell is in a better place to ascertain facts surrounding the communications. But
`many communications originate from Hitachi, Ltd./HCE. With respect to such communications, Maxell’s
`knowledge is limited to the materials received from Hitachi/HCE, which were produced.
`3 Even where Maxell identified documents, Maxell described each of the categories of documents
`identified, meaning even the list of identified materials is very much the opposite of “non-descript.”
`5
`
`
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 245 Filed 03/26/20 Page 8 of 11 PageID #: 9516
`
`
`
`
`only a few assignments: the 2013 Agreement between HCE and Hitachi Maxell and related IP
`
`Memorandum of Understanding (although in Japanese, Maxell produced English translations),
`
`2017 Patent Assignment Agreement between Hitachi Maxell and Maxell, Ltd., and the public
`
`versions of such assignments recorded with the PTO. Apple need not wade through thousands of
`
`pages and make wild guesses. Maxell identified the agreements it contends entitle it to collect past
`
`damages. As such, Maxell has provided a fulsome and complete response.
`
`The cases Apple cited do not support Apple’s demand. In Mancini, the plaintiff attempted
`
`to respond with “all facts can be found within the entire universe of documents involved in the
`
`underlying litigation, including expert reports, discovery responses, pleadings and depositions.”
`
`Mancini v. Ins. Corp. of New York, No. CIV. 07CV1750-L NLS, 2009 WL 1765295, at *2 (S.D.
`
`Cal. June 18, 2009). That is light years from Maxell’s narrow but complete response, citing only
`
`a handful of assignment documents that support the contention addressed by the interrogatory.
`
`Fleming dealt with an interrogatory requesting where in each conception document each claim
`
`limitation was found. Fleming v. Escort, Inc., No. CV 09-105-S-BLW, 2011 WL 573599, at *2
`
`(D. Idaho Feb. 13, 2011). It appears the interrogatory in Fleming specifically sought the detailed
`
`information, unlike here where Apple’s current demand, which goes beyond the interrogatory
`
`itself, is more of an afterthought intended to manufacture a discovery dispute.
`
`C.
`
`Maxell Has Not “Selectively Responded” with Information on Behalf of
`Hitachi
`
`Apple’s continued accusations regarding Maxell’s treatment of Hitachi information has
`
`reached the point of harassment. Apple already moved to compel Maxell to produce materials on
`
`behalf of Hitachi. In response, Maxell set forth the history of its relationship with Hitachi,
`
`including the transfer of materials related to the assignment of the asserted patents. D.I. 166 at 1-
`
`2. And Maxell made clear it has produced the relevant materials it received from Hitachi in this
`
`
`
`6
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 245 Filed 03/26/20 Page 9 of 11 PageID #: 9517
`
`
`
`
`case and has no ability to demand additional materials from Hitachi. Id. at 2. This was true for the
`
`documents Apple sought in its prior motion and it is true for the information Apple seeks now.
`
`Maxell is not “selectively responding” to anything. It is providing the information it has within its
`
`possession, custody, or control—which is all Maxell can do. This was acknowledged by the Court
`
`in denying Apple’s prior motion. See D.I. 202 at 12 (holding that Apple had not demonstrated that
`
`Maxell has sufficient control over documents in Hitachi’s possession and noting “the Court is
`
`unsure what more Maxell could do to obtain the documents requested.”).
`
`Apple provides no facts or evidence on which to raise this issue anew. That Maxell
`
`coordinated the depositions of inventors in their individual capacity was already before the Court.
`
`The inventors’ deposition testimony does not change the calculus. Mssrs. Takizawa and Nakano
`
`are not employees of Hitachi, Ltd. They are employees of Hitachi Industry & Control Solutions
`
`Ltd. (“HiCS”), a subsidiary. Ex. D, Takizawa Tr. at 10:3-8; Ex. E, Nakano Tr. at 9:21-24. Both
`
`deponents made it clear their trip was covered by Maxell/Mayer Brown, not Hitachi Ltd. Ex. D at
`
`20:15-21:5, 22:1-8; Ex. E at 29:16-30:8. Both individuals confirmed their employment did not
`
`require them to attend the deposition. Ex. D at 142:3-15; Ex. E at 29:3-12. And Apple’s assertion
`
`that the inventors “expect to receive a bounty” is both a mischaracterization of the facts and
`
`irrelevant to the issue of control. See, e.g., Ex. E at 70:20-24 (statement that inventor did not “know
`
`for sure” if he would receive monetary compensation if Maxell is successful). With respect to work
`
`being performed between HiCS and Maxell, the Court has already noted that a business
`
`relationship between Maxell and a Hitachi subsidiary, unrelated to the asserted patents, does not
`
`establish control. D.I. 202 at 8.
`
`In view of the foregoing, Apple’s motion to compel should be denied in full.
`
`7
`
`
`
`
`
`
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 245 Filed 03/26/20 Page 10 of 11 PageID #: 9518
`
`
`
`
`Dated: March 24, 2020
`
`
`By:
`
`
`
`
`
`
`
`
`8
`
`/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
`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
`
`PUBLIC VERSION
`
`

`

`Case 5:19-cv-00036-RWS Document 245 Filed 03/26/20 Page 11 of 11 PageID #: 9519
`
`
`
`
`rpluta@mayerbrown.com
`asbonner@mayerbrown.com
`
`Counsel for Plaintiff Maxell, Ltd.
`
`
`
`
`
`
`
`
`CERTIFICATE OF SERVICE
`
`The undersigned certifies that all counsel of record who are deemed to have consented to
`electronic service are being served this 24th day of March 2020, with a copy of this document via
`electronic mail.
`
`
`/s/ Jamie B. Beaber
`Jamie B. Beaber
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`9
`
`
`
`
`
`
`
`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