throbber
Case 5:19-cv-00036-RWS Document 229 Filed 03/13/20 Page 1 of 10 PageID #: 9030
`
`IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`TEXARKANA DIVISION
`
`MAXELL, LTD.,
`
`
`
`Plaintiff
`
`Civil Action No. 5:19-cv-00036-RWS
`
`v.
`
`APPLE INC.,
`
`
`
`Defendant.
`
`JURY TRIAL DEMANDED
`
`
`
`
`
`
`APPLE INC.’S MOTION FOR PROTECTIVE ORDER
`REGARDING CERTAIN MAXELL RULE 30(B)(6) DEPOSITION TOPICS
`
`
`
`

`

`Case 5:19-cv-00036-RWS Document 229 Filed 03/13/20 Page 2 of 10 PageID #: 9031
`
`
`
`Maxell served Apple with an 84-topic Rule 30(b)(6) deposition notice that included
`
`overly-broad and (at best) marginally-relevant topics. Despite this, the parties are in agreement
`
`about the scope of testimony (if any) Apple will provide on the topics in Maxell’s notice except
`
`for the 15 that are the subject of this motion.1 Those 15 topics: (1) are redundant of Apple’s
`
`written discovery responses, which are more comprehensive than any testimony that a corporate
`
`witness could provide; (2) fail to identify the testimony sought with the required “reasonable
`
`particularity” that would permit Apple to prepare a witness to testify; (3) seek plainly privileged
`
`information from Apple’s in-house or outside counsel; and/or (4) seek discovery about
`
`discovery. Maxell agreed to a 60-hour limit on Apple depositions in this case. D.I. 42 at 4. But
`
`even a minimum inquiry into the full scope of the topics discussed below would exceed that
`
`limit, to say nothing of the time required to address Maxell’s other Rule 30(b)(6) topics and
`
`numerous Rule 30(b)(1) deponents. A protective order is, therefore, warranted.
`
`I.
`
`LEGAL STANDARD
`
`“‘Good cause’ [for a protective order] exists when justice requires the protection of ‘a
`
`party or person from [] oppression, or undue burden or expense.’” Ferko v. Nat’l Ass’n for Stock
`
`Car Auto Racing, Inc., 218 F.R.D. 125, 133 (E.D. Tex. 2003). Rule 26, however, does not
`
`permit a “‘scorched earth,’ ‘no stone unturned’ (potentially numerous times) approach to
`
`discovery.” Finjan, Inc. v. ESET, LLC, No. 17CV183 CAB (BGS), 2018 WL 4772124, at *5
`
`(S.D. Cal. Oct. 3, 2018).
`
`
`1 The parties have worked together to narrow the disputes at issue. Apple is confining this
`motion to the disputes it understands, based on the parties’ meet-and-confer history, to be live
`and contested. Should Maxell raise additional disputes not addressed in the parties’ recent meet-
`and-confer, Apple will discuss them with Maxell as soon as possible, attempt to reach
`agreement, and raise with the Court if necessary.
`
`1
`
`

`

`Case 5:19-cv-00036-RWS Document 229 Filed 03/13/20 Page 3 of 10 PageID #: 9032
`
`
`
`II.
`
`ARGUMENT
`
`A.
`
`Topics 1, 3, and 8 Are Redundant of Apple’s Discovery Responses
`
`Topic 1 seeks model numbers and code names for more than 120 Apple desktops,
`
`laptops, iPods, iPhones, iPads, and Watches. And Topic 8 seeks, for each of these Accused
`
`Products, “the preinstalled Version of iOS and all compatible Versions of iOS,” totaling over
`
`3,961 combinations of Accused Products and operating systems. Ex. A 2/7/20 Pensabene Ltr. at
`
`1. But Apple has already provided the information requested by Topics 1 and 8 in its 27 page-
`
`long comprehensive response to Interrogatory No. 1. Topic 3 seeks, for each Accused Product,
`
`the supplier name, product name, internal model number, and supplier model number for all
`
`accused components.
`
`
`
`
`
`Given the minutiae called for by these topics, all already provided by Apple’s
`
`interrogatory responses, these topics plainly warrant a protective order. Beyond being
`
`impossible, asking an Apple witness to memorize information that took months to compile, and
`
`has already been provided to Maxell, is a textbook invitation of undue burden and harassment
`
`not required by Rule 30(b)(6). Bayer Healthcare Pharm., Inc. v. River's Edge Pharm., LLC, No.
`
`1:11-CV-01634-RLV, 2013 WL 11901530, at *2 (N.D. Ga. Apr. 26, 2013) (“There is no
`
`requirement that a Rule 30(b)(6) witness memorize thousands of pages of documents and be able
`
`to recall in exacting detail the minutia of such voluminous records.”).
`
`Attempting to agree on the scope of these topics, and to understand whether it was
`
`possible to reasonably prepare an Apple witness or witnesses to testify, Apple invited Maxell to
`
`clarify the information it was seeking, for example, if there were any perceived discrepancies in
`
`the information that an Apple witness could explain. Maxell declined.
`
`2
`
`

`

`Case 5:19-cv-00036-RWS Document 229 Filed 03/13/20 Page 4 of 10 PageID #: 9033
`
`
`
`B.
`
`Topics 4, 7, 29, and 58 Are Irrelevant and Lack Reasonable Particularity
`
`Apple is already producing witnesses in response to other topics to testify about the
`
`relevant technical operations of the accused functionality and components, as identified in
`
`Maxell’s infringement contentions, including any technical requirements for such functionality.
`
`These topics, however, are essentially boundless and extend far beyond any specific issues, the
`
`subject of which might be relevant, and seek the impossible, i.e., a witness to testify about every
`
`communication Apple has had with virtually every one of its suppliers.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` Topic 7 seeks all communications concerning
`
`all of the source code Apple has produced in this case. Topic 29 seeks all facts concerning the
`
`negotiations and communications with third parties related to the research and development of
`
`the accused features. Maxell has not limited these topics to any particular time, components, or
`
`subjects of communication.
`
`To avoid requiring court intervention, Apple asked that Maxell identify the specific
`
`components and the specific types communications in which it was interested so that Apple
`
`could consider whether it could designate any witness to address Maxell’s inquiries.
`
`
`
`
`
`
`
`3
`
`

`

`Case 5:19-cv-00036-RWS Document 229 Filed 03/13/20 Page 5 of 10 PageID #: 9034
`
`
`
` This did not meaningfully limit the scope of the topics “with particularity.”
`
`DarbeeVision, Inc. v. C&A Mktg., Inc., No. CV 18-0725 AG (SSX), 2019 WL 2902697, at *8
`
`(C.D. Cal. Jan. 28, 2019) (explaining that “[i]t is not realistic to expect a 30(b)(6) witness to be
`
`able to testify about every possible internal communication” and strongly encouraging the parties
`
`to “meet and confer . . . so that Defendant will know what specific information Plaintiff wants
`
`and can prepare the witness accordingly”).
`
`C.
`
`Topics 38 and 41 Improperly Seek Discovery About Discovery
`
`Apple has already agreed that its witnesses will be prepared to discuss the identity and
`
`storage of documents (including source code) related to the substantive subject matter of their
`
`testimony (Ex. D, 2/14/20 Meet and Confer Tr. at 48:2-24), but Maxell’s notice seeks far more
`
`and intrudes into attorney work product. Topics 38 and 41 inquire about “Defendant’s efforts to
`
`preserve, identify, collect, and produce relevant and/or responsive information and Documents in
`
`the Litigation” and “Defendant’s efforts to collect source code of the Accused Products.”
`
`“In cases that involve reams of documents and extensive document discovery, the
`
`selection and compilation of documents is often more crucial than legal research,” and an
`
`attorney’s selection and review of those documents reflects “legal theories and thought
`
`processes, which are protected as work product.” Shelton v. Am. Motors Corp., 805 F.2d 1323,
`
`1329 (8th Cir. 1986). Accordingly, “courts will not compel” disclosure based solely on Maxell’s
`
`“mere suspicion” that Apple “has not produced adequate documents.” Alley v. MTD Prod., Inc.,
`
`No. 3:17-CV-3, 2018 WL 4689112, at *2 (W.D. Pa. Sept. 28, 2018) (denying 30(b)(6) topics
`
`regarding Defendants’ systems for creating, storing, retrieving, and retaining documents). Such
`
`requests are more properly resolved as “part of the general discovery meet-and-confer process
`
`without the need for formal ‘discovery-on-discovery’ requests.” United Ass’n of Journeyman &
`
`Apprentices of the Plumbing & Pipe Fitting Indus., Underground Util./landscape Local Union
`
`4
`
`

`

`Case 5:19-cv-00036-RWS Document 229 Filed 03/13/20 Page 6 of 10 PageID #: 9035
`
`
`
`No. 355 v. Maniglia Landscape, Inc., No. 17-CV-03037-RS (LB), 2019 WL 7877821, at *2
`
`(N.D. Cal. July 25, 2019). Apple’s counsel has kept Maxell’s counsel more-than-sufficiently
`
`appraised of Apple’s participation in the discovery process, even though Maxell has not seemed
`
`genuinely interested in actually discussing this with Apple. See, e.g., Ex. C, 3/4/20 Pensabene
`
`Ltr. at 1 (noting “Maxell is not actually interested in resolving (or even discussing) the issues
`
`raised in [Maxell’s] February 26 letter despite Apple’s willingness to do so.”).
`
`
`
`
`
`
`
`
`
`
`
` “None of these
`
`requests bear on plaintiff’s underlying claim” and “plaintiff’s meandering attempt to prove
`
`defendant’s noncompliance with its discovery obligations” should be rejected. Id.
`
`D.
`
`Topics 39 and 56 Seek Common Interest Privileged Communications
`
`Topic 39 seeks communications between Apple and its suppliers concerning the “search
`
`for and/or production of relevant and/or responsive information and Documents” in this
`
`litigation. Topic 56 seeks Apple’s communications with “any third party regarding the Patents-
`
`in-Suit and/or this Litigation.” This is not the first time that Maxell has sought to pry into
`
`Apple’s privileged information—Maxell’s first Rule 30(b)(1) notice in this case was to Apple’s
`
`in-house counsel, which Maxell withdrew only after Apple moved to quash it. D.I. 116.
`
`Maxell’s current request for a corporate designee to testify about Apple’s discussions
`
`with third parties about the present litigation seeks privileged information about Apple’s
`
`communications with its suppliers. See, e.g., Johnson Matthey Inc. v. Noven Pharmaceuticals,
`
`5
`
`

`

`Case 5:19-cv-00036-RWS Document 229 Filed 03/13/20 Page 7 of 10 PageID #: 9036
`
`
`
`Inc., No. 2:07-CV-260-CE, slip. op. at 3-4 (E.D. Tex. Aug. 28, 2009) dkt. 164 (finding common
`
`interest privilege between defendants and their suppliers); Mobile Micromedia Sols. LLC v.
`
`Nissan N. Am., Inc., No. 5:05-CV-230, 2007 WL 9724766, at *5 (E.D. Tex. Nov. 14, 2007), on
`
`reconsideration in part, No. 5:05-CV-230, 2007 WL 9724765 (E.D. Tex. Dec. 27, 2007)
`
`(“Nissan and its suppliers were potential co-defendants in Mobile’s lawsuit and acted under a
`
`threat of imminent litigation by Mobile”).
`
`
`
`
`
`
`
`
`
`
`
`
`
`E.
`
`Topic 63 Improperly Seeks Apple’s Legal Contentions
`
`Apple’s technical witnesses will testify regarding the accused functionality and
`
`alternative ways to implement such functionality. But topic 63 goes further, seeking Apple’s
`
`legal contentions concerning “any acceptable, non-infringing alternatives.” To the extent
`
`discoverable, this is already stated in Apple’s response to Interrogatory No. 8. A deposition
`
`regarding such contentions is unnecessary. Where “the proposed deposition topics are complex
`
`and highly technical, or involve legal issues that require the assistance of an attorney, the
`
`interrogatory is the preferred device.” DarbeeVision, No. CV 18-0725 AG (SSX), 2019 WL
`
`2902697, at *7 (collecting cases); BB&T Corp. v. United States, 233 F.R.D. 447, 449 (M.D.N.C.
`
`2006) (“[U]ntil a party has first shown that the interrogatory process cannot be used, it may not
`
`seek to use depositions for contention discovery.”).
`
`F.
`
`Topics 78, 79, and 80 Are Overbroad and Seek Irrelevant Information
`
`Apple’s technical and marketing witnesses will testify regarding the departments
`
`6
`
`

`

`Case 5:19-cv-00036-RWS Document 229 Filed 03/13/20 Page 8 of 10 PageID #: 9037
`
`
`
`involved in development and marketing of the Accused Products. However, Topics 78 and 79
`
`are far broader, seeking Apple’s “corporate structure and organization” including “all
`
`departments and divisions” that in any way touch the Accused Products and “any other
`
`subsidiaries, affiliates, or related Entities as they relate to the Accused Products.” These topics
`
`are irrelevant and Maxell has made no proffer to the contrary. Even if these topics were
`
`marginally relevant, Maxell’s demand that Apple educate a witness on all departments and
`
`divisions that in any way touch the over 120 desktops, laptops, iPods, iPhones, iPads, and
`
`Watches sold over a six year period exemplifies a “‘scorched earth,’ ‘no stone unturned’ . . .
`
`approach to discovery.” Sol IP, No. 218CV00526RWSRSP, 2020 WL 60140, at *2.
`
`Topic 80 likewise seeks “facts related to any agreement to indemnify in connection with
`
`the Litigation.” Maxell has not, and cannot, articulate any basis for relevance. Regardless, there
`
`are no such agreements about which testimony may be provided.
`
`III. CONCLUSION
`
`Apple respectfully requests that the Court grant a protective order on topics 1, 3, 4, 7, 8,
`
`29, 38, 39, 41, 56, 58, 63, 78, 79, and 80.
`
`
`
`
`
`
`
`7
`
`

`

`Case 5:19-cv-00036-RWS Document 229 Filed 03/13/20 Page 9 of 10 PageID #: 9038
`
`March 12, 2020
`
`/s/ Luann L. Simmons
`
`Luann L. Simmons (Pro Hac Vice)
`lsimmons@omm.com
`O’MELVENY & MYERS LLP
`Two Embarcadero Center
`28th Floor
`San Francisco, CA 94111
`Telephone: 415-984-8700
`Facsimile: 415-984-8701
`
`Xin-Yi Zhou (Pro Hac Vice)
`vzhou@omm.com
`Anthony G. Beasley (TX #24093882)
`tbeasley@omm.com
`O’MELVENY & MYERS LLP
`400 S. Hope Street
`Los Angeles, CA 90071
`Telephone: 213-430-6000
`Facsimile: 213-430-6407
`
`Laura Bayne Gore (Pro Hac Vice)
`lbayne@omm.com
`O’MELVENY & MYERS LLP
`Times Square Tower, 7 Times Square
`New York, NY 10036
`Telephone: 212-326-2000
`Facsimile: 212-326-2061
`
`Melissa R. Smith (TX #24001351)
`melissa@gilliamsmithlaw.com
`GILLIAM & SMITH, LLP
`303 South Washington Avenue
`Marshall, Texas 75670
`Telephone: (903) 934-8450
`Facsimile: (903) 934-9257
`
`Attorneys for Defendant Apple Inc.
`
`8
`
`

`

`Case 5:19-cv-00036-RWS Document 229 Filed 03/13/20 Page 10 of 10 PageID #: 9039
`
`CERTIFICATE OF SERVICE
`
`The undersigned hereby certifies that all counsel of record who are deemed to have
`
`consented to electronic service are being served with a copy of this document via the Court's
`
`CM/ECF system per Local Rule CV-5(a)(3) on March 12, 2020.
`
`/s/ Melissa R. Smith
`Melissa R. Smith
`
`
`
`
`
`
`
`
`
`
`
`CERTIFICATE OF CONFERENCE
`
`On February 14, 2020, pursuant to Local Rule CV-7(h), counsel for Defendants met and
`
`conferred with counsel for Plaintiff, and counsel for Plaintiff indicated that Plaintiff is opposed to
`
`the relief sought by this Motion.
`
`/s/ Melissa R. Smith
`Melissa R. Smith
`
`9
`
`

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