A Blog About Intellectual Property Litigation and the District of Delaware


Entries for tag: Discovery Dispute

Check the Docket Before Failing to Appear for a Hearing

Emily DiBenedetto, April 25, 2023
Stipulation Meet-and-Confer

Broken Communication
Reid Naaykens, Unsplash

Parties can freely stipulate to many things in the District of Delaware, and often stipulations to extend deadlines are filed close to the last minute, especially where the parties are working toward agreement but ultimately cannot agree on the final filing in time (or else are having trouble connecting with the other side).

However, stipulations filed close to the Delaware witching hour (5:00PM EST) can be fraught with risk of the Court's denial, as we’ve seen in past heart-stopping examples. We’ve warned before that requests to move Court-scheduled conferences are in the “iffy” category, and combined with last minute filing, can end in disappointment for everyone, as shown in an oral order from Judge Noreika last week in Neurocrine Biosciences, Inc. v. Lupin Limited et al., C.A. 21-1042, D.I. 197 (D. Del. Jul. 16, 2021):

On April 17, 2023, the Court instructed the parties to talk to each other about their disputes so that a follow-up call with the Court (set for April 21, 2023) would be more productive than the prior call. On April 21, 2023, a few hours before the set call, the parties submitted a stipulation requesting the April 21 call be delayed. After further inquiries, it became clear that, in the five days after the Court directed the parties to TALK, they did not do so. The Court intended to address that during the April 21 call, but no counsel appeared for the call (notwithstanding that the Court had not granted the request for a delay). THEREFORE, IT IS HEREBY ORDERED that, should the parties not inform the Court that they have resolved their dispute in full by Tuesday April 25, 2023, lead trial counsel SHALL appear in person in Courtroom 4A on April 26, 2023 at 3:00 p.m. ORDERED by Judge Maryellen Noreika on 4/21/2023.

Judge Noreika previously indicated frustration with the magnitude of this particular discovery dispute (on search methods to find responsive documents), so the parties were on thin ice long before ...

View

I Don't Wanna Wait, For Our Cases To Be Oveeerrrrrrr

Nathan R. Hoeschen, April 25, 2023
Discovery Dispute

It begins with a series of interminably long emails. I say that you really should be producing these documents—I cite cases, exhaustively describe the items sought, and cite check the whole thing like it's headed to the Supreme Court. You respond by pointing out that I am just hopelessly misguided, and have perhaps been drinking. You also cite cases.

Eventually everyone gets on the phone to hash things out. Two hours later you agree to take my positions "under advisement" and call it a day.

Meet and confer accomplished.

Why is this one so creepy? It's just supposed to be werewolves shaking hands
Why is this one so creepy? It's just supposed to be werewolves shaking hands AI-Generated, displayed with permission

It's not always that bad, but there is definite potential for one or both parties to drag the process out. It's rare to see any consequences to this sort of slow-rolling, as it's usually invisible to the Court.

Every now and then, though, someone gets called out for it, and yesterday was one of those days. The dispute in TwinStrand Biosciences, Inc. v. Guardant Health, Inc., C.A. No. 21-1126-GBW-SRF (D. Del. Apr. 24, 2023) (Oral Order) was your usual request that a party supplement an interrogatory. Judge Fallon granted the motion, but took the unusual step of noting the somewhat tortured history of the parties' correspondence

Guardant's second supplemental response to Interrogatory No. 6 provides some of this information for only one of the Asserted Patents. Guardant represented that it would produce and identify documents responsive to the Interrogatory under Fed. R. Civ. P. 33(d) as discovery continued. Guardant's responses to Plaintiffs' requests for supplementation of Interrogatory No. 6 during the meet and confer process suggest that Guardant may have additional responsive information that has not yet been disclosed. (As of March 17, 2023, Guardant represented it "will provide our position or a supplementation in due course"); (As of April 4, 2023, Guardant was "considering [Plaintiffs'] proposal and hope[s] to have a response soon."). Otherwise, Guardant could have put the matter to rest and avoided burdening the Court by simply confirming that it had no additional information responsive to Interrogatory No. 6.

The phrasing here is not quite a rebuke, but parties generally like to keep their name as far removed from ...

View

How Much is Too Much? The Answer: Three Discovery Dispute Teleconferences in Two Months (Involving Nine Disputes)

Andrew E. Russell, March 24, 2023
Discovery Dispute Congestion

"From now on, your discovery disputes will be heard at the summit . . . " Alexander Milo, Unsplash

It's always good to know the limits when it comes to discovery disputes. In some cases, parties just can't seem to work together on discovery, and the parties end up bringing a lot of disputes.

At some point, the number of disputes may push the Court over the line. Famously (in Delaware—so perhaps not "famously" at all), former Chief Judge Sleet used to limit parties to three discovery disputes in patent cases before requiring them to seek leave. I don't know of any similar explicit limits set by any of our current judges, but pushing things too far can still …

View

Judge Noreika: "The Court Will Not Act as a Negotiator to Whittle Down Overly Broad [Discovery] Requests."

Andrew E. Russell, March 17, 2023
Meet-and-Confer Discovery Dispute

Attorneys
AI-Generated, displayed with permission

Judge Norieka issued a notable oral order earlier this week in Neurocrine Biosciences, Inc. v. Lupin Limited, C.A. No. 21-1042-MN (D. Del.).

The context is not fully clear from the docket, but it looks like the parties contacted the Court to initiate a discovery dispute regarding the sufficiency of the plaintiff's document collection efforts. But, instead of issuing the typical order starting the process, Judge Noreika ordered the parties to meet-and-confer again and set some expectations as to how the Court will handle the dispute:

ORAL ORDER - The parties have requested a discovery dispute teleconference regarding Defendants' request for discovery into the search methods Plaintiff used to find responsive documents. IT IS HEREBY ORDERED that the parties shall meet and confer again. Thereafter, on or before 5:00 PM on 3/20/2023 [five days from the order], the parties shall provide the Court with the current version of the discovery requests, explaining what part or parts remain in dispute. The Court will not act as a negotiator to whittle down overly broad requests. Therefore, Defendants should propose requests of appropriate scope with the understanding that the Court may simply deny requests that are overly broad on their face.

It looks like the Court may be trying out a more efficient way to resolve disputes over discovery requests.

View

A Citation for the Petty

Nathan R. Hoeschen, Feb. 23, 2023
Discovery Dispute Scheduling Order

Delaware regulars will know that a stipulation to extend a deadline will—with certain limited exceptions—usually be granted as a matter of course. Moreover, the common wisdom is that one ought to agree to a short extension of a discovery or briefing deadline, absent some strong reason not to. Such is the DELAWARE WAY (TM).

Sometimes, though, a request for an extension just rubs you the wrong way. Maybe they ask late, maybe they jerked you around when you asked for an extension last time, maybe you saw them double-dip a chip at the last bar mixer and you just can't get over it. In those times, it's nice to be able to point to case where the court denied a …

View

Another Order to Produce Litigation Funding Discovery—This Time Against What Looks Like a Practicing Entity

Andrew E. Russell, Dec. 5, 2022
Litigation Funding Discovery Dispute

Money
Pepi Stojanovski, Unsplash

Last week, Chief Magistrate Judge Thynge issued an opinion addressing a motion by accused infringers to compel the patentee to produce litigation funding discovery and opinion letters relating to the patents-in-suit.

While it involves litigation funding discovery, this case is a bit different from the recent Mavexar hearings. Here, the patentee is MHL Custom, Inc. who, it appears, is a practicing company and not an NPE. Beyond that, the case is still active (unlike some of the Mavexar cases) and the discovery is sought by the defendant, not the Court itself. In other words, this is a more typical ruling.

But the opinion is still notable. The Court granted the accused infringers' motion for three categories …

View

A Handy Transcript

Andrew E. Russell, Nov. 9, 2022
Contentions KB

Bookmarks
Chiara F, Unsplash

I thought I'd share an old transcript that has come in handy a number of times since it issued back in 2013, where Judge Andrews made a helpful ruling about how and when patentees must respond to conception date interrogatories—an issue that comes up frequently.

In Vehicle Interface Techs., LLC v. Jaguar Land Rover N. Am., LLC, C.A. No. 12-1285-RGA (D. Del.), the defendant filed a discovery dispute to compel a full response to an interrogatory asking for the date of conception and reduction to practice.

The patentee had responded, but the answer was not very helpful. According to the discovery dispute letter:

[The patentee] stated that the sole inventor . . …
View

Disagreement With the Substance of Infringement Contentions Does Not Mean Those Contentions Are Inadequte—And Can't Be the Basis to Withhold Discovery

Andrew E. Russell, Oct. 31, 2022
Motion to Strike MTC

"I'm a motion to strike, not a stealth motion for summary judgment" Braydon Anderson, Unsplash

One of the more common District of Delaware questions you get as local counsel is "can we move to strike opposing counsel's (infringement or invalidity) contentions?"

That may seem like a simple question, but the answer depends many things, like: What is wrong with those contentions? How were our contentions in comparison? Which judge is this in front of? How long ago did they serve them? (And, sometimes, things like: Why are you asking this now, when we are two weeks from trial?)

Challenging contention disclosures can be tough even if you have what seem like fairly good arguments. The Court is generally not …

View

Non-Infringement Is No Reason to Withhold Core Technical Documents, At Least When the Infringement Allegation is Not Baseless

Andrew E. Russell, Sept. 7, 2022
Infringement Contentions Core Technical Documents

Television
Ajeet Mestry, Unsplash

Last week Magistrate Judge Burke ruled on a core technical documents dispute in The Nielsen Company (US), LLC v. TVision Insights, Inc., C.A. No. 21-1592 (D. Del.). The defendants sought to avoid production of core technical documents for a product that was accused but that could not infringe. Judge Burke rejected that position:

Defendant shall produce core technical documents for the Logitech-based system. . . . [I]f the Court did not allow discovery of properly-accused products every time a defendant said that its product did not infringe the patent-in-suit, there would be little to no discovery permitted in the patent cases in this Court.

He suggested that the infringement allegation here was not completely baseless, and that whether the product meets the claims depends on claim construction:

The real dispute here appears to be about whether a product can infringe the relevant patent if it contains a two-dimensional and three-dimensional sensor that are implemented in one piece of hardware. . . . It strikes the Court that that issue may get resolved via claim construction, or, if not, then pursuant to a later dispute (perhaps at summary judgment) regarding infringement. But those steps in the case are still to come.

He also rejected the ...

View

Source Code Is Not a Core Technical Document

Andrew E. Russell, May 18, 2022
Source Code Discovery Dispute

Source Code
Markus Spiske, Unsplash

Delaware's Default Standard requires defendants to produce "core technical documents" on the accused products, even absent discovery requests from the plaintiff.

These core technical documents "includ[e] but [are] not limited to operation manuals, product literature, schematics, and specifications." Often parties interpret this as a relatively light production of just the core non-public material that a plaintiff needs to make out its infringement contentions.

Sometimes, however, plaintiffs will push back and demand production of source code, saying that a defendant must produce source code as part of its core technical documents.

This is a recurring issue, so I thought it was worth noting that, in Judge Fallon's discovery dispute order that we discussed earlier, she also …

View
Newer
Older

Archive