We don't often write about claim construction opinions, because they can be very fact-specific. But Judge Hall's opinion yesterday in Apple Inc. v. Masimo Corporation, C.A. No. 22-1377-JLH (D. Del.) included some generally applicable points worth noting.
Sometimes a Reservation of Rights Actually Works
There's a reason we've all seen countless discovery documents, disclosures, expert reports, and briefs that are larded up with endless reservations of rights: sometimes they work!
This is one of those times. The patentee (Apple) had filed a response to invalidity contentions regarding a design patent in an IPR. In it, Apple described the scope of its patent, but included a reservation stating that it wasn't taking claim …
One of these guys forgot to come armed.AI-Generated, displayed with permission
Attorneys spend a lot of time threatening fee awards when dealing with an NPE, even though they can be challenging to get. So I always think it's interesting to see what kinds of behavior will support a fee award.
Last week, Judge Williams issued a memorandum order granting fees in Extremity Medical, LLC v. Nextremity Solutions, LLC, C.A. No. 22-239-GBW (D. Del.). The Court listed three bases for its fee award. First, the patentee made zero showing of any pre-suit investigation of invalidity:
[T]here is no dispute that Defendants notified Plaintiff of [prior art references] Marcus and Chandran several years prior to the date …
When re-filing things that were pulled from PACER, the Court has said that parties should remove the old CM/ECF headers:
CORRECTING ENTRY: The redacted public version of D.I. 157 at D.I. 161 has been replaced with a version that does not contain CM/ECF headers. Counsel is reminded to remove CM/ECF headers from previously-filed documents when filing.
ESCO Group LLC v. Deere & Company, C.A. No. 20-1679-WCB (D. Del. Feb. 9, 2023).
That way, when the document is later pulled from the docket, you don't get the overlapping and unreadable headers at the top.
If you don't redact them, it can end up looking something like this:
I believe it used to be possible to remove these …
Long answer - also yes, also obviously, but the timing is important.
AI-Generated, displayed with permission
The issue came to the fore in I-Mab Biopharma v. Inhibrx, Inc., C.A. No. 22-276-CJB (D. Del. Sept. 19, 2024) (Mem. Ord.). I-mAB is a DTSA action alleging the theft of about a dozen separate trade secrets. A few months back, the plaintiff went through a restructuring that resulted in several related entities now owning some or all of the trade secrets. The plaintiff then moved to add these entities as co-plaintiffs. Judge Burke denied the motion due to the potential for delay, given that the case was scheduled for trial int he near future.
Earlier this year Judge Hall bifurcated the upcoming patent trial in Apple Inc. v. Masimo Corporation, C.A. No. 22-1377-JLH (D. Del.), keeping Apple's patent claims, the related invalidity and unenforceability defenses, and a portion of a Walker Process anti-trust counterclaim—but moving other claims to a later trial:
ORAL ORDER: Having held a case management conference on March 20, 2024, . . . IT IS HEREBY ORDERED that a 5-day jury trial is scheduled beginning October 21, 2024, with a pretrial conference scheduled for October 4, 2024 at 11:00 AM in courtroom 6D. The remaining claims and defenses in C.A. No. 22-1377 and C.A. No. 22-1378 shall be joined and/or bifurcated for trial such …
"Your honor, we'd like to drop most of our claims." "Ok, but you're not picking them back up."AI-Generated, displayed with permission
True D. Del. patent litigators know that, no matter which side you're on, you're going to have to narrow your claims and defenses before trial. It's just unwise and unworkable to go into a five-day trial with 100 claims, or with 30 prior art references and hundreds (or millions) of potential obviousness combinations. There isn't time to cover it all.
That said, sometimes the parties in patent cases delay case narrowing for a long time. And while the Court will often narrowing, it doesn't do that in every case. Instead, judges sometimes take the approach that …
The Court has held in the past that motions in limine cannot be used to bring stealth summary judgment or Daubert motions after the deadlines for those motions (we first posted about this issue over four years ago—wow).
Last week, this issue came up again, this time with a party overtly asking the Court for two additional MILs, beyond the default three, specifically to address summary judgment issues. Unsurprisingly, the Court did not grant the motion:
Defendants seek . . . permission to file two motions in limine beyond the three motions in limine permitted by the Scheduling Order. . . . In Defendants' words: "Two requests will seek to exclude certain exhibits and testimony …
I attended the 2024 Delaware Regional Federal Circuit Bench and Bar today. It was a great program with many judges speaking on panels, plus an interview with Judge Dyk of the Federal Circuit and remarks by Senator Chris Coons. Here are some notes about interesting points from the conference, in case you missed it.
New Judges for the District of Delaware
Of particular interest to District of Delaware attorneys (and litigants) is the great news about two potential new judges. Senator Coons relayed the news—which we here at IP/DE had not picked up on—that the U.S. Senate has unanimously approved the JUDGES act …
AI refuses to draw a judge without an old-school judicial wig. This is the best I could do.AI-Generated, displayed with permission
Chief Judge Connolly held a second Mavexar-related hearing yesterday, this time in Swirlate IP LLC v. Quantela, Inc., C.A. No. 22-235-CFC (D. Del.). This was after the one in the Backertop action that we just posted about.
Chief Judge Connolly questioned both the out-of-town attorney who represented Swirlate as lead counsel in the action, and the sole member of the Swirlate NPE
The Court addressed several topics with the attorney, including:
Gaps and redactions in the court-ordered document production, which was supposed to include communications with his client.
"A POSITA would be motivated to combine cocktail sauce and raspberry jam, as both are red-colored foodstuffs safe for human consumption that come in glass containers with metal, screw-on lids."AI-Generated, displayed with permission
Judge Andrews issued a lengthy summary judgment and Daubert opinion on Thurday in Acceleration Bay, LLC v. Amazon Web Services, Inc., C.A. No. 22-904-RGA (D. Del.). The opinion hits multiple interesting issues, and we may have a couple of posts on it this week.
But the one ruling that jumped out to me was the Court's rejection of the fairly typical, low-effort motivation-to-combine language that many experts rely on in their obviousness opinions.
Motivation to combine is often an afterthought. I've seen many initial contentions that address it only in a short paragraph that basically just lists characteristics of each reference (same field, same problem, etc.). Expert reports sometimes uncritically adopt paragraphs like that no elaboration.
If you've ever been involved in reading or writing invalidity contentions, you've probably seen motivation-to-combine paragraphs just like this one, from Thursday's opinion:
As those charts show, [the first reference] ATT Maxemchuk builds upon [the second reference] ’882 Maxemchuk and informs a POSITA of additional details related to ’882 Maxemchuk’s grid-based mesh network. A POSITA would be motivated to combine these references for several reasons. Both references are in the network architecture field and are directed to improving mesh networks. Both teach the simplification of routing of data that arises from the grid-based mesh network. And both disclose the same grid-based mesh network. In addition, ATT Maxemchuk includes additional implementation details for the grid-based mesh network that ’882 Maxemchuk describes.
The paragraph gives just four one-sentence reasons for its statement that a person of skill in the art would combine the references. Three of the reasons are about general similarities between the references.
The fourth sentence is a bit more helpful, and says that the first reference provides "additional implementation details" for part of the second reference.
The Court found that this paragraph—which the parties agreed was representative—simply could not provide support for a motivation to combine the references. The Court granted summary judgment of no obviousness:
Mr. Greene “fails to explain why a person of ordinary skill in the art would have combined elements from specific references in the way the claimed invention does.” . . . His opinion does nothing more than explain why the prior art references are analogous to each other and to the claimed invention. . . . Plaintiff’s “assertions that the references were analogous art, . . . without more, is an insufficient articulation for motivation to combine.” . . .
As Defendant’s invalidity contentions rely on Mr. Greene’s testimony, Mr. Greene’s failure to opine on a POSA’s motivation to combine the asserted prior art references proves fatal to Defendant’s obviousness theory. I grant summary judgment of nonobviousness as to all asserted obviousness defenses.
Acceleration Bay, LLC v. Amazon Web Services, Inc., C.A. No. 22-904-RGA, at 37-38 (D. Del. Sept. 12, 2024).
This blog is for general informational purposes. It is not an offer to perform legal services, and should not be considered a substitute for legal advice. Nothing in this blog should be construed as forming an attorney-client relationship. If you have legal questions, please consult counsel in your jurisdiction.
