Book a demo

Cut patent&paper research from weeks to hours with PatSnap Eureka AI!

Try now
SAP SE v. TMX Group | Data Processing Patent Transfer | PatSnap
Explore in Eureka
Case ID2:25-cv-01038
FiledFeb 2025
ClosedAug 2025
Patent Litigation

SAP SE v. TMX Group: Patent MDL Transfer to Delaware After 173 Days

SAP SE and affiliates filed suit against TMX Group and related entities alleging infringement of eight patents covering data processing, access, and transfer techniques used in trading and market analytics platforms. After 173 days, the JPML transferred this action—one of four across three districts—to the District of Delaware for coordinated MDL proceedings under Judge Maryellen Noreika.

Resolution time
173days
173 days from filing to transfer — shorter than a typical MDL formation cycle
Patents asserted
3
US8782059B2, US8577927B2, US9009354B2 and 5 further patents asserted across consolidated actions
Outcome
Case Transferred
JPML centralized 4 actions in D. Delaware; Judge Noreika assigned
Cost ruling
Not Determined
Cost and merits rulings deferred to transferee MDL court in Delaware
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

JPML Centralises SAP’s Eight-Patent Data Analytics Campaign in Delaware

SAP SE, together with Business Objects Software Ltd. and Sybase, Inc., filed this patent infringement action against TMX Group Limited in the Eastern District of Pennsylvania on 27 February 2025. The asserted patents — including US8782059B2, US8577927B2, and US9009354B2 — cover data processing, access, and transfer techniques that SAP alleges are deployed within TMX’s trading and market analytics platforms, including TMX Analytics, TMX Datalinx, TMX ESG Data Hub, and TMX Grapevine.

The case closed on 19 August 2025 when the Judicial Panel on Multidistrict Litigation ordered transfer to the District of Delaware under 28 U.S.C. § 1407. The JPML found that four pending actions in three districts — the Eastern District of Pennsylvania, the Northern District of Illinois, and the District of Delaware — shared common factual questions arising from allegations against related TMX entities. Crucially, the parties in this action stipulated to substitute TSX Inc. for TMX Group as defendant before the transfer was finalised.

The 173-day path to transfer is consistent with efficient JPML practice, particularly given that motions to dismiss were already briefed and pending across all three districts at the time of centralisation. The public record does not reveal which specific claims drove forum selection or how claim construction will be framed in Delaware; those determinations now rest with Judge Noreika. The MDL structure suggests SAP is pursuing a coordinated, multi-defendant enforcement strategy across the TMX corporate family.

Case at a glance
Case no.2:25-cv-01038
PlaintiffSAP SE
CourtPennsylvania Eastern
JudgeGERALD A. MCHUGH
FiledFebruary 27, 2025
ClosedAugust 19, 2025
Duration173 days
OutcomeCase Transferred
Verdict causeInfringement Action
BasisCase Transferred
Prior Art Intelligence
See what prior art exists on this patent.
Eureka scans millions of patents and papers to surface prior art that may have invalidated these claims before costly litigation begins.
Check Prior Art
Case data sourced from PACER / Pennsylvania Eastern District Court via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Case Transferred in 173 days

173 days from filing to transfer — shorter than a typical MDL formation cycle

Case timeline: Complaint filed FEB 27 2025, MAY–JUN — 173 days total Horizontal timeline showing the three key events in SAP SE v TMX GROUP LIMITED from filing to resolution. Source: PACER, Pennsylvania Eastern District Court. FEB 27 2025 Complaint filed Pre-trial proceedings AUG 19 2025 Case Transferred 173 DAYS TOTAL
Transfer terms

JPML transfer to Delaware: what the MDL order means for both parties

Legal mechanism

What a § 1407 transfer actually means

Under 28 U.S.C. § 1407, the Judicial Panel on Multidistrict Litigation can centralise related actions before a single district court for coordinated pretrial proceedings. Transfer does not resolve the merits — it consolidates discovery, claim construction, and validity rulings to eliminate duplication. Once pretrial proceedings conclude, individual actions are typically remanded to their original courts for trial, unless resolved earlier.

Procedural consolidation only
Venue implications

Delaware becomes the operative battlefield

The JPML selected the District of Delaware as transferee court because at least one plaintiff and one defendant are incorporated there, making it convenient for the several international parties. Pending motions to dismiss — already fully briefed — will now be addressed by Judge Noreika. Delaware’s well-developed patent jurisprudence and familiarity with complex corporate IP disputes typically signals a rigorous but commercially sophisticated forum for both sides.

D. Delaware — Judge Noreika assigned
What happens next

Claim construction and validity now centralised

With all four actions consolidated, the most consequential near-term proceedings are the pending motions to dismiss and, subsequently, Markman claim construction hearings covering up to eight patents. Four of the eight patents appear in three of the four actions, meaning a single adverse claim construction ruling could materially affect SAP’s position across multiple cases simultaneously. TMX entities benefit from a unified defence strategy under a single judge.

8 patents — unified Markman proceeding ahead
Commercial implications

MDL scope signals a broad enforcement campaign

The centralisation of four actions targeting related TMX entities — TSX Alpha, TMX Group, TSX Inc., and Trayport — across trading and market analytics products suggests SAP is pursuing portfolio-level enforcement rather than a single-product dispute. Competitors and licensees in the financial data and market infrastructure space should treat this MDL as a signal that SAP’s data processing IP is being actively asserted at scale.

Portfolio enforcement — financial data sector
Legal analysis based on PACER docket records for case 2:25-cv-01038 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffSAP SEIndividualEnterprise software and IP licensor — holder of US8782059B2 and related data processing patentsSearch in Eureka ↗
DefendantTMX GROUP LIMITEDCompanyCanadian financial markets infrastructure group operating trading and market analytics platformsSearch in Eureka ↗
Plaintiff counselABED BALBAKYAttorneyCounsel for SAP SESearch in Eureka ↗
Plaintiff counselAleksander J. GoraninAttorneyCounsel for SAP SESearch in Eureka ↗
Plaintiff counselBrianna VinciAttorneyCounsel for SAP SESearch in Eureka ↗
Plaintiff counselJames L. Davis , Jr.AttorneyCounsel for SAP SESearch in Eureka ↗
Plaintiff counselJAMES R. BATCHELDERAttorneyCounsel for SAP SESearch in Eureka ↗
Plaintiff counselKATHRYN C. THORNTONAttorneyCounsel for SAP SESearch in Eureka ↗
Plaintiff counselMEREDITH E. COXAttorneyCounsel for SAP SESearch in Eureka ↗
Plaintiff counselTYLER MARANDOLAAttorneyCounsel for SAP SESearch in Eureka ↗
Plaintiff law firmDuane Morris LLPLaw FirmRepresenting SAP SESearch in Eureka ↗
Plaintiff law firmRopes & Gray, LLPLaw FirmRepresenting SAP SESearch in Eureka ↗
Defendant counselADAM R. BRAUSAAttorneyCounsel for TMX GROUP LIMITEDSearch in Eureka ↗
Defendant counselCATHERINE J. CANBYAttorneyCounsel for TMX GROUP LIMITEDSearch in Eureka ↗
Defendant counselCHELSEA NICHOLSAttorneyCounsel for TMX GROUP LIMITEDSearch in Eureka ↗
Defendant counselDANIEL J. BROWNAttorneyCounsel for TMX GROUP LIMITEDSearch in Eureka ↗
Defendant counselDARALYN J. DURIEAttorneyCounsel for TMX GROUP LIMITEDSearch in Eureka ↗
Defendant counselElizabeth Christine KnuppelAttorneyCounsel for TMX GROUP LIMITEDSearch in Eureka ↗
Defendant counselJOHN S. DOUGLASSAttorneyCounsel for TMX GROUP LIMITEDSearch in Eureka ↗
Defendant counselREGAN J. RUNDIOAttorneyCounsel for TMX GROUP LIMITEDSearch in Eureka ↗
Defendant counselRYAN J. MALLOYAttorneyCounsel for TMX GROUP LIMITEDSearch in Eureka ↗
Defendant counselTANNYR M. PASVANTISAttorneyCounsel for TMX GROUP LIMITEDSearch in Eureka ↗
Defendant law firmHANGLEY ARONCHICK SEGAL PUDLIN & SCHILLERLaw FirmRepresenting TMX GROUP LIMITEDSearch in Eureka ↗
Defendant law firmMCCARTER & ENGLISHLaw FirmRepresenting TMX GROUP LIMITEDSearch in Eureka ↗
Defendant law firmMorrison & Foerster LLPLaw FirmRepresenting TMX GROUP LIMITEDSearch in Eureka ↗
Presiding judgeJudge GERALD A. MCHUGHJudgePennsylvania Eastern District CourtSearch in Eureka ↗
Official verdict

Official order — verbatim text

“Before the Panel: * Defendants1 in these patent infringement actions move under 28 U.S.C. § 1407 to centralize this litigation in the District of Delaware or, alternatively, the Northern District of Illinois or the Eastern District of Pennsylvania. This litigation consists of four actions pending in the District of Delaware, the Northern District of Illinois, and the Eastern District of Pennsylvania, as listed on Schedule A. Plaintiffs2 oppose centralization. On the basis of the papers filed and the hearing session held, we find that the actions listed on Schedule A involve common questions of fact, and that centralization in the District of Delaware will serve the convenience of the parties and witnesses and promote the just and efficient conduct of this litigation. These actions share factual questions arising from allegations that defendants, all of which are related companies, infringed one or more of eight patents concerning data processing, access, and transfer techniques used by defendants as part of their trading and market analytics platforms. Centralization is warranted to eliminate duplicative discovery; prevent inconsistent pretrial rulings (particularly with respect to claim construction and issues of patent validity); and conserve the resources of the parties, their counsel, and the judiciary. In opposing centralization, patentholder plaintiffs argue that no patent is common to all actions, each case involves a unique defendant and unique allegedly infringing products, and the patents are not sufficiently related to warrant centralization. We do not find these arguments persuasive. While no patent is common to all actions, four of the eight patents are involved in three of the four actions. Defendants are separate companies, but they are related, sharing the same parent company. The two Northern District of Illinois actions, which together involve seven of the eight patents, have been consolidated. This suggests that there are enough similarities among * Judge David C. Norton did not participate in the decision of this matter. 1 TSX Alpha U.S., Inc. (TXS Alpha), TMX Group Limited (TMX Group), and Trayport Limited (Trayport). Since the close of briefing, the parties in the Eastern District of Pennsylvania action have stipulated to replace defendant TMX Group with TSX Inc. 2 SAP SE, Business Objects Software Ltd., and Sybase, Inc. Case PAE/2:25-cv-01038 Document 15 Filed 08/11/25 Page 1 of 3 Case 2:25-cv-01038-GAM Document 52 Filed 08/19/25 Page 1 of 3 PANEL ON MULTIDISTRICT LITIGATION Karen K. Caldwell Chair Nathaniel M. Gorton Matthew F. Kennelly Roger T. Benitez Dale A. Kimball Madeline Cox Arleo Case PAE/2:25-cv-01038 Document 15 Filed 08/11/25 Page 2 of 3 – 2 – the patents that centralization of all of the actions in the various districts may offer important efficiencies. Plaintiffs also argue that informal coordination among the parties and the involved courts is preferable to Section 1407 centralization. To be sure, only four actions are pending in three districts, and two of them have been consolidated. Despite the low number of cases and involved courts, we see a significant possibility of duplicative pretrial proceedings, conflicting schedules, and inconsistent rulings absent centralization—particularly with respect to complex and time-consuming tasks such as claim construction and ruling on issues of patent validity. Indeed, motions to dismiss have been briefed and are pending in all three districts. The efficiencies to be gained, for both the parties and the judicial system, by having a single court overseeing claim construction and discovery relating to the patents are substantial. In these circumstances, centralization is superior to any voluntary efforts by the parties and the judges presiding over these cases. The District of Delaware is an appropriate transferee district for this litigation. At least one plaintiff and one defendant are incorporated there, and it is convenient to the several international parties. Judge Maryellen Noreika has not yet had the opportunity to serve as a transferee judge, and we are confident she will steer this litigation on a prudent and expeditious course. IT IS THEREFORE ORDERED that the actions listed on Schedule A and pending outside the District of Delaware are transferred to the District of Delaware and, with the consent of that court, assigned to the Honorable Maryellen Noreika for coordinated or consolidated pretrial proceedings.”
Source: PACER Docket, Case 2:25-cv-01038, Pennsylvania Eastern District Court

The JPML order is procedural rather than merits-based: it makes no finding on infringement, validity, or damages. The Panel’s determination that ‘centralization is superior to any voluntary efforts’ is significant — it signals the court views the patent overlap and corporate relatedness of defendants as substantial enough to override plaintiffs’ preference for separate proceedings. The substitution of TSX Inc. for TMX Group in this action, noted in the order, suggests ongoing party alignment that may affect claim scope and damages calculations in Delaware.

PACER case 2:25-cv-01038 · Public docket record Explore in Eureka ↗
Patent at issue

US8782059B2, US8577927B2 & US9009354B2 — Data Processing & Transfer Patents

Publication No.US8782059B2
Application No.US11/480415
Patent details
Productdata processing and access techniques for enterprise and market data systems
Cited in actionFebruary 27, 2025

Publication No.US8577927B2
Application No.US13/021546
Patent details
Productdata transfer and synchronisation methods for networked database platforms
Cited in actionFebruary 27, 2025

Publication No.US9009354B2
Application No.US13/721506
Patent details
Productdata access and query processing techniques for analytical computing environments
Cited in actionFebruary 27, 2025

The three patents identified in this action — US8782059B2 (application no. US11/480415), US8577927B2 (application no. US13/021546), and US9009354B2 (application no. US13/721506) — represent successive generations of SAP’s foundational data processing and transfer technology portfolio, with the earliest application tracing to a mid-2000s filing window consistent with Sybase-era database engineering. The patents collectively cover techniques for processing, accessing, and transferring data in high-throughput computing environments — capabilities central to the operation of financial trading platforms and real-time market analytics services.

SAP’s decision to assert these patents against TMX’s suite of products — including TMX Analytics, Datalinx, ESG Data Hub, and Grapevine — suggests the claims are drafted broadly enough to reach commercial data distribution and analytics infrastructure well beyond traditional enterprise software deployments. For financial market operators, exchange technology vendors, and market data redistributors, these patents represent a material freedom-to-operate risk. The MDL consolidation means that any validity challenge or narrowing claim construction will now be decided once, with binding effect across all related defendants.

Patent data sourced from USPTO via PatSnap Eureka patent database Search patent records in Eureka ↗
Freedom to operate

Should you run an FTO against US8782059B2 and related SAP data patents?

Any organisation operating trading platforms, market analytics services, financial data redistribution infrastructure, or enterprise data processing pipelines that overlap with TMX’s product categories — TMX Analytics, Datalinx, ESG Data Hub, Grapevine — should treat this MDL as a trigger for a formal freedom-to-operate review. SAP is actively enforcing this portfolio at scale, and the Delaware MDL will produce claim constructions with industry-wide relevance. Acting before Markman rulings maximise your design-around options.

PatSnap Eureka’s FTO Search Agent enables R&D and IP teams to map the full claim landscape of US8782059B2, US8577927B2, and US9009354B2 against your specific product architecture. Eureka identifies prior art, prosecution history estoppel, and design-around pathways — giving in-house counsel and product teams the analytical foundation to make informed build-versus-licence decisions before Delaware’s coordinated pretrial proceedings crystallise the risk.

PatSnap Eureka FTO Search

Run a freedom-to-operate analysis on US8782059B2 to assess your product’s exposure

Run FTO in Eureka →
Related litigation

Similar Data Processing Patent Infringement Cases in Federal Court

Explore related patent infringement actions asserting data processing and transfer patents in federal district courts, including the District of Delaware MDL docket.

🔍
Access 40+ similar cases in PatSnap Eureka
SAP SE patent enforcement history, Pennsylvania Eastern case history, SAP SE’s full IP portfolio, and comparable case analysis
SAP data patent actionsTMX entity prior IP disputesDelaware MDL patent casesSybase portfolio enforcement
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the financial data analytics IP landscape

SAP’s multi-defendant MDL filing marks an escalation in enterprise software patent enforcement against financial market infrastructure providers.

JPML centralisation accelerates high-stakes claim construction rulings

With motions to dismiss already briefed in all three original districts, Judge Noreika will face immediate substantive decisions. A unified Markman hearing covering eight data processing patents could set binding interpretations that ripple across SAP’s entire enforcement campaign — and across the financial data industry more broadly.

TMX’s corporate structure became a centralisation argument

The JPML specifically noted that the defendants are related companies sharing a common parent. IP counsel advising multi-entity corporate groups should note that shared parentage can override the ‘unique defendant, unique product’ argument when a plaintiff asserts overlapping patent portfolios across the group.

🔒
Full strategic analysis in PatSnap Eureka
Unlock gated analysis on SAP’s financial data patent enforcement strategy and Delaware district court MDL implications.
Sybase patent lineage riskDesign-around windowsDelaware MDL enforcement model
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

SE v TMX — key questions answered

Still have questions? PatSnap Eureka can answer them instantly from patent and litigation data. Ask Eureka ↗
PatSnap Eureka

Monitor SAP’s eight-patent data analytics MDL before claim construction locks in

Judge Noreika’s Markman rulings will define the risk landscape for the entire financial data infrastructure sector. Use PatSnap Eureka to run FTO analysis against SAP’s asserted portfolio and track Delaware MDL developments in real time.

Ask anything about this case.
PatSnap Eureka searches patents and litigation data to answer instantly.
Powered by PatSnap Eureka
Link copied to clipboard

Related Litigation Cases

Help us improve this page

Found incorrect or outdated information? Let us know and we'll get it fixed.