Lattice Technologies v. Alarm.com: Emergency Response Patent Case Transferred to Richmond
Lattice Technologies LLC filed suit against Alarm.com, Inc. in the Virginia Eastern District Court on 15 January 2025, asserting US8098153B2 — a patent covering systems and methods for delivering emergency response to users via carried devices. Within just 7 days, the court ordered an intradistrict transfer to the Richmond Division, where the case continues as 3:25cv51-DJN.
Emergency Response Patent Suit Rapidly Rerouted to Richmond Division
On 15 January 2025, Lattice Technologies LLC initiated a patent infringement action against smart-home technology company Alarm.com, Inc. in the Virginia Eastern District Court (Case No. 2:25-cv-00033). The suit asserts US8098153B2, a patent directed at systems and methods of providing emergency response to a user carrying a user device — technology squarely relevant to Alarm.com’s connected security and monitoring platform.
The case did not proceed substantively in its original division. Within 7 days of filing, the court entered an intradistrict transfer order, reassigning the matter to the Richmond Division under case number 3:25cv51-DJN, before Judge David J. Novak. An intradistrict transfer moves a case between divisions of the same federal district court rather than to a separate court, preserving the same governing circuit precedent while changing the presiding judge and physical forum.
A 7-day turnaround to transfer is notably swift, suggesting the reassignment was triggered by administrative division-assignment rules or a standing order rather than contested motion practice. No merits rulings, claim construction, or cost determinations were made in the original proceeding. The substantive litigation — and any assessment of infringement, validity, or damages — will now unfold entirely in the Richmond Division, and the public record at the original docket number is effectively closed.
Filing to Case Transferred in 7 days
7 days in original court before intradistrict transfer to Richmond Division
Intradistrict transfer to Richmond: what the move means for both parties
Intradistrict transfer shifts venue within the same federal district
An intradistrict transfer reassigns a case from one division to another within the same federal district court — here, from the Eastern District’s original filing division to its Richmond Division. Critically, the governing circuit (the Fourth Circuit) and applicable substantive law remain unchanged. The transfer is administrative in nature and does not reflect any ruling on the merits, personal jurisdiction, or proper venue.
No merits ruling madeRichmond Division: what changes for each side
The Richmond Division assignment brings a specific presiding judge (3:25cv51-DJN) and Richmond-based logistics, including local rules, scheduling norms, and a different jury pool. For Alarm.com, this may affect litigation costs and travel. For Lattice Technologies, the change is largely neutral at this stage — the infringement claims are fully preserved and the case restarts on the Richmond docket without any concession on the merits.
Same circuit, new divisionAll claims carry forward intact to Richmond
Because the transfer is intradistrict and administrative, nothing filed before the transfer is abandoned. The asserted patent (US8098153B2), the accused emergency-response functionality, and all pleadings are carried into the Richmond proceedings. Alarm.com retains all defences — invalidity, non-infringement, and any Rule 12 motions — that would have been available in the original division.
Claims fully preservedAlarm.com’s emergency response features remain under scrutiny
US8098153B2 covers emergency response delivery to users via carried devices — a capability central to Alarm.com’s security monitoring and dispatch services. The transfer does not resolve the underlying IP risk. Competitors and partners in the connected-security and smart-home monitoring sector should note that the patent remains asserted and fully enforceable while the Richmond litigation unfolds. Licensing exposure cannot be ruled out pending claim construction.
Patent risk persistsFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | Lattice Technologies LLC | Company | Patent assertion entity — holder of US8098153B2 covering emergency response via user-carried devicesSearch in Eureka ↗ |
| Defendant | Alarm.com, Inc. | Company | Alarm.com, Inc. — smart home security and monitoring platform providerSearch in Eureka ↗ |
| Plaintiff counsel | Isaac Philip Rabicoff | Attorney | Counsel for Lattice Technologies LLCSearch in Eureka ↗ |
| Plaintiff law firm | Rabicoff Law LLC | Law Firm | Representing Lattice Technologies LLCSearch in Eureka ↗ |
| Presiding judge | Judge N/A | Judge | Virginia Eastern District CourtSearch in Eureka ↗ |
Official order — verbatim text
The transfer order — ‘Intradistrict Transfer to Richmond Division assigned case number 3:25cv51-DJN’ — is purely administrative and carries no substantive legal weight on the merits of the infringement claims. It does not reflect any ruling on the validity of US8098153B2, the strength of Lattice’s infringement theory, or any defence raised by Alarm.com. Both parties enter the Richmond proceedings on equal procedural footing, with no findings having been made at the original docket.
US8098153B2 — Emergency Response System for User-Carried Devices
US8098153B2 (application number US11/981463) protects a system and method of providing emergency response to a user carrying a user device. The patent covers the architecture and workflow by which a carried device — such as a smartphone or wearable — can trigger, route, or coordinate emergency response services. This positions the patent at the intersection of connected-device communication protocols and public-safety dispatch, a technically active and commercially significant domain as mobile and IoT devices become primary interfaces for emergency services.
For a company like Alarm.com, whose platform integrates smart sensors, mobile applications, and professional monitoring services, the asserted claims present meaningful exposure if the claim construction captures how user-carried devices interact with its dispatch and alert infrastructure. The patent’s application-date vintage (filing number US11/981463 suggests mid-2000s prosecution) means it predates the smartphone-era smart-home boom, potentially giving its claims broad coverage over now-standard emergency-response architectures. Competitors across personal safety apps, wearables, and connected security platforms should treat this patent as a sector-wide FTO concern.
Should your product team run an FTO against US8098153B2?
Any product that enables emergency response through a user-carried device — including smartphone SOS features, wearable panic buttons, smart-home security apps, or professional monitoring integrations — sits within the potential scope of US8098153B2. The Alarm.com case signals active enforcement. R&D teams building or scaling emergency-alert, dispatch-routing, or user-location-based response features should assess whether their implementation reads on the asserted claims before launch or next funding round.
PatSnap Eureka’s FTO Search Agent can map US8098153B2’s independent claims against your product architecture, identify prosecution history estoppel that may narrow scope, surface related family members and continuations, and benchmark against prior art that could support an IPR or inter partes challenge. Running a structured FTO now — before claim construction in Richmond — is significantly less costly than defending or designing around an adverse ruling.
Run a freedom-to-operate analysis on US8098153B2 to assess your product’s exposure
Run FTO in Eureka →Similar Patent Cases: Emergency Response & Connected-Device Technology
Cases involving emergency response and user-carried device patents in the Eastern District of Virginia and comparable federal venues, with infringement actions against smart-home and security platform defendants.
What this case signals for the connected-security and emergency-response IP landscape
A 7-day filing-to-transfer signals process efficiency — but the underlying patent assertion against a major smart-home platform is far from resolved.
Emergency response patents are live enforcement targets in smart-home tech
The assertion of US8098153B2 against Alarm.com’s platform demonstrates that utility patents protecting emergency-response workflows for mobile and carried devices remain active enforcement tools. Companies building dispatch, SOS, or monitoring features on IoT or smart-home infrastructure should map exposure against this patent family before scaling deployment.
Richmond Division (E.D. Va.) is a high-velocity patent docket — expect tight scheduling
The Eastern District of Virginia — including its Richmond Division — is known for expedited scheduling. Alarm.com should anticipate compressed discovery timelines and early claim-construction hearings. IP teams monitoring this case should track the Richmond docket actively: key procedural milestones are likely to arrive faster than in many other districts.
Lattice v Alarm.com — key questions answered
The intradistrict transfer moves the case from its original Eastern District of Virginia filing division to the Richmond Division (3:25cv51-DJN), before a new judge. It is administrative — no merits, jurisdiction, or venue challenges were decided. All infringement claims under US8098153B2 carry forward intact, and both parties retain all available defences.
US8098153B2 protects a system and method for providing emergency response to a user carrying a user device. Alarm.com operates a connected-security platform that includes mobile apps, professional monitoring, and emergency dispatch integration — functionality that may intersect with the patent’s claims, depending on how the Richmond court construes the asserted claims at Markman.
Following the 22 January 2025 transfer order, the case is now before the Richmond Division of the Eastern District of Virginia under case number 3:25cv51-DJN. The original docket (2:25-cv-00033) is closed. All future substantive proceedings — scheduling, claim construction, discovery, and any trial — will occur in Richmond.
A 7-day transfer timeline suggests the reassignment was triggered by an administrative standing order or local division-assignment rule rather than contested motion practice. No substantive pleadings, motions, or orders on the merits were entered in the original division. This is consistent with clerical or divisional-assignment procedures common in the Eastern District of Virginia.
The Richmond Division of the E.D. Va. is known for its relatively fast scheduling and experienced patent docket. Alarm.com should anticipate compressed timelines for claim construction and discovery compared to some other districts. The transfer does not prejudice any defences, but it does mean the litigation will move quickly — early engagement with Richmond-experienced patent counsel is advisable.
PatSnap Eureka searches patents and litigation data to answer instantly.