Patent Armory v. Mercury Systems: 5-Patent Call Routing Suit Transferred in 2 Days
Patent Armory, Inc. asserted five patents covering intelligent communication routing and telephony control systems against Mercury Systems, Inc. in the Virginia Eastern District Court. The case was transferred intradistrict to the Richmond Division just two days after filing — one of the fastest venue reassignments on record for a multi-patent infringement action.
Five-Patent Routing Suit Redirected to Richmond Before It Begins
On September 9, 2024, Patent Armory, Inc. filed a patent infringement action against Mercury Systems, Inc. in the Virginia Eastern District Court, asserting five United States patents: US9456086B1, US10491748B1, US7269253B1, US7023979B1, and US10237420B1. The asserted patents collectively cover intelligent communication routing systems, telephony control with intelligent call routing, and method and system frameworks for matching entities in an auction context — a portfolio suggesting a focus on intelligent network routing and communications infrastructure.
Just two days after filing, on September 11, 2024, the court ordered an intradistrict transfer to the Richmond Division, reassigning the matter as case number 3:24cv645. The basis of termination is recorded as ‘Case Transferred,’ meaning no merits adjudication occurred in the Alexandria or Norfolk docket — the action simply relocated within the same district. Both parties retain all claims and defences in the transferred proceeding.
A two-day turnaround from filing to transfer is notable: it suggests the assignment was a routine administrative division allocation rather than a contested venue dispute. The public record for this docket is silent on whether Mercury Systems had appeared or filed any responsive pleading before transfer. The substantive litigation — including any invalidity challenges, claim construction, and infringement analysis — will now proceed before the Richmond Division of the Eastern District of Virginia, a venue well known for its historically active patent docket.
Filing to Case Transferred in 2 days
Case resolved by intradistrict transfer — 2 days from filing to close, well below the district median.
Intradistrict transfer to Richmond: what the reassignment means for both parties
Intradistrict transfer reassigns venue within the same district
An intradistrict transfer moves a case from one divisional seat to another within the same federal district court. Unlike an inter-district transfer under 28 U.S.C. § 1404(a), it does not require a showing of convenience or change of jurisdiction. Here, the Alexandria/Norfolk docket was closed and the action re-docketed as 3:24cv645 in the Richmond Division — same judges pool, same governing circuit precedent, but a different divisional assignment.
Administrative reassignmentRichmond Division: a proven patent litigation venue
The Richmond Division of the Eastern District of Virginia is historically associated with faster-than-average patent schedules, sometimes styled informally as a ‘rocket docket.’ For Patent Armory, this venue could accelerate claim construction and trial timelines. For Mercury Systems, rapid scheduling means less discovery runway — early claim construction positioning and prior art development will be critical from the outset of the transferred proceeding.
Faster docket risk for defendantAll substantive issues remain live in the transferred case
The transfer carries no merits ruling. Patent Armory’s five-patent infringement claims survive intact, and Mercury Systems has not yet been recorded as having filed a responsive pleading in this docket. The parties will need to re-engage on scheduling, initial disclosures, and any early dispositive motions — including potential IPR petitions at the USPTO — before the Richmond Division. Monitoring case 3:24cv645 is the key action item for interested parties.
Case live in Richmond as 3:24cv645Five-patent assertion suggests a structured enforcement campaign
Asserting five patents spanning intelligent routing, telephony control, and auction-based matching systems in a single complaint is consistent with a portfolio-level enforcement strategy. Patent assertion entities typically group patents to increase licensing pressure and complicate invalidity challenges. Mercury Systems — a defence electronics company — may face exposure across multiple product lines if the routing and communications patents are read broadly. An FTO analysis across all five asserted patents is advisable.
PAE portfolio enforcement patternFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | Patent Armory, Inc. | Company | Patent assertion entity — holder of US9456086B1 and 4 further communication routing patentsSearch in Eureka ↗ |
| Defendant | Mercury Systems, Inc., | Company | Mercury Systems, Inc. — defence and commercial electronics technology companySearch in Eureka ↗ |
| Plaintiff counsel | Isaac Philip Rabicoff | Attorney | Counsel for Patent Armory, Inc.Search in Eureka ↗ |
| Plaintiff law firm | Rabicoff Law LLC | Law Firm | Representing Patent Armory, Inc.Search in Eureka ↗ |
| Presiding judge | Judge N/A | Judge | Virginia Eastern District CourtSearch in Eureka ↗ |
Official order — verbatim text
The verdict entry records a purely administrative intradistrict transfer — no infringement finding, no validity ruling, and no substantive merits adjudication of any kind. The phrasing ‘Intradistrict Transfer to Richmond Division’ confirms that the Alexandria docket was closed solely for case management purposes. All claims remain live. This entry provides no indication of the merits strength of either party’s position; analysis of the underlying infringement allegations must await substantive filings in case 3:24cv645.
US9456086B1 and Four Further Patents — Intelligent Communication Routing Portfolio
The five asserted patents span two core technical domains. US9456086B1 (App. No. 12/719827) and US10491748B1 (App. No. 15/797070) cover intelligent communication routing systems and methods, while US7269253B1 (App. No. 11/387305) and US7023979B1 (App. No. 10/385389) address telephony control systems with intelligent call routing — application dates in the mid-2000s place these in the pre-VoIP maturity era. US10237420B1 (App. No. 15/856729) covers a method and system for matching entities in an auction, suggesting applicability to advertising or lead-generation routing contexts.
The portfolio’s breadth — spanning routing logic, telephony control, and auction-based matching — is strategically significant. Legacy telephony and routing patents from mid-2000s application dates have been increasingly mobilised by PAEs against enterprise and defence technology companies whose products may implement functionally similar network communication handling. Mercury Systems’ communications and processing products for defence platforms could plausibly be read within the scope of one or more of these claims, though infringement requires detailed claim mapping. Competitors in network routing, unified communications, and defence electronics should assess exposure across the full five-patent set.
Should your product team run an FTO against US9456086B1 and related patents?
Any organisation developing or deploying intelligent call routing, telephony control systems, or network-based entity matching platforms should treat this five-patent portfolio as a credible FTO priority. Patent Armory’s filing against Mercury Systems — a defence electronics company rather than a pure telecom operator — signals that the claims may be drafted broadly enough to reach non-traditional communication routing implementations. R&D teams working on routing algorithms, VoIP infrastructure, or auction-based lead routing should flag these patent numbers for immediate claim mapping.
PatSnap Eureka’s FTO Search Agent can map your product’s technical features against all five asserted patent claim sets simultaneously, identifying overlapping claim language and flagging prosecution history estoppel that may limit scope. Eureka also surfaces related family members and continuation applications that may not yet be asserted but could represent future enforcement risk. Running a consolidated FTO across the full Patent Armory portfolio — not just the asserted patents — is the most efficient risk management approach given the PAE enforcement pattern evident here.
Run a freedom-to-operate analysis on US9456086B1 to assess your product’s exposure
Run FTO in Eureka →Similar Intelligent Communication Routing Patent Cases in the Eastern District of Virginia
Explore related PAE-filed infringement actions involving intelligent call routing and telephony control patents litigated in the Eastern District of Virginia.
What this case signals for the intelligent communications IP landscape
A five-patent filing against a defence electronics company in the Eastern District of Virginia suggests escalating PAE activity in communications routing IP.
PAE enforcement in communications routing is accelerating
Patent Armory’s multi-patent complaint targeting intelligent call routing and telephony control systems reflects a broader trend of patent assertion entities aggregating older communications infrastructure patents — many with application dates in the mid-2000s — and deploying them against technology and defence companies. Firms in adjacent sectors should audit exposure to similar legacy routing IP.
Richmond Division scheduling demands early IPR strategy
The Eastern District of Virginia’s Richmond Division is known for compressed litigation timelines. Mercury Systems and similarly situated defendants should treat IPR petition windows as a near-term strategic priority. The one-year bar from service of a complaint means the clock starts running from the moment of proper service in the transferred case.
Patent v Mercury — key questions answered
Patent Armory, Inc. filed a five-patent infringement action against Mercury Systems, Inc. on September 9, 2024 in the Virginia Eastern District Court. Two days later, on September 11, 2024, the court ordered an intradistrict transfer to the Richmond Division, where the case continues as 3:24cv645. No merits ruling was issued.
Patent Armory asserted five patents: US9456086B1, US10491748B1, US7269253B1, US7023979B1, and US10237420B1. These cover intelligent communication routing systems, telephony control with intelligent call routing, and a method and system for matching entities in an auction. All five remain live in the transferred proceeding.
An intradistrict transfer moves the case from one divisional seat to another within the same federal district — here from the Alexandria or Norfolk docket to the Richmond Division. No merits adjudication occurred. The case re-docketed as 3:24cv645 and all claims and defences carry over intact to the Richmond Division.
The Richmond Division of the Eastern District of Virginia has historically maintained faster-than-average patent litigation schedules, often described informally as a ‘rocket docket.’ This typically means compressed discovery timelines and earlier trial dates compared to many other federal districts, which creates pressure on defendants to prepare invalidity and non-infringement positions quickly.
The five-patent portfolio asserted against Mercury Systems — covering intelligent routing, telephony control, and auction-based entity matching — is broad enough to warrant attention from companies in unified communications, VoIP infrastructure, network routing, and defence electronics. A freedom-to-operate analysis mapping product features against the asserted claims is advisable, particularly given the mid-2000s application dates which may cover foundational routing architectures still in use.
PatSnap Eureka searches patents and litigation data to answer instantly.