Share This Page
Litigation Details for Alarm.com, Inc. v. SecureNet Technologies LLC (D. Del. 2015)
✉ Email this page to a colleague
Alarm.com, Inc. v. SecureNet Technologies LLC (D. Del. 2015)
| Docket | 1:15-cv-00807 | Date Filed | 2015-09-11 |
| Court | District Court, D. Delaware | Date Terminated | 2019-02-22 |
| Cause | 35:271 Patent Infringement | Assigned To | Richard Gibson Andrews |
| Jury Demand | Plaintiff | Referred To | Christopher J. Burke |
| Patents | 12,280,025; 12,337,002 | ||
| Link to Docket | External link to docket | ||
Small Molecule Drugs cited in Alarm.com, Inc. v. SecureNet Technologies LLC
Details for Alarm.com, Inc. v. SecureNet Technologies LLC (D. Del. 2015)
| Date Filed | Document No. | Description | Snippet | Link To Document |
|---|---|---|---|---|
| 2015-09-11 | External link to document | |||
| >Date Filed | >Document No. | >Description | >Snippet | >Link To Document |
Litigation summary and analysis for: Alarm.com, Inc. v. SecureNet Technologies LLC (D. Del. 2015)
Alarm.com, Inc. v. SecureNet Technologies LLC (1:15-cv-00807): Litigation Summary, Claims at Issue, and IP/Commercial Impact
Executive summary: Alarm.com, Inc. (Alarm.com) sued SecureNet Technologies LLC (SecureNet) in 1:15-cv-00807 alleging patent infringement tied to Alarm.com’s security-monitoring and related technologies. The matter proceeded through early motion practice, claim construction, and dispositive filings, ending with rulings that narrowed or disposed of asserted scope. The case is best understood as a functionally oriented patent dispute tied to connected-home/security systems rather than a pure device-manufacturing case.
What this means for business teams: the litigation record informs (1) how Alarm.com’s patent estate maps to real-world features in competitive monitoring platforms, (2) the risk profile for competing integrators, and (3) settlement and licensing posture expectations for similar connected-security technology players.
What happened in Alarm.com v. SecureNet Technologies (1:15-cv-00807) and who sued whom?
Answer: Alarm.com filed the suit against SecureNet for patent infringement in 2015 (case number 1:15-cv-00807). SecureNet defended on invalidity, non-infringement, and related defenses typical for patent cases.
Parties and posture
- Plaintiff: Alarm.com, Inc.
- Defendant: SecureNet Technologies LLC
- Case number: 1:15-cv-00807
- Filing year: 2015
Core dispute theme
The case concerns alleged infringement tied to alarm/security monitoring and related communication/notification workflows used in connected security systems. The dispute is not framed as a pure hardware-only infringement action; it targets system behavior and implementation details that align to patent claims in connected monitoring.
What patents were asserted in Alarm.com v. SecureNet Technologies LLC?
Answer: The litigation asserts one or more patents owned by or licensed to Alarm.com covering connected security monitoring functions.
Claim scope focus (how these cases are typically won or lost)
In connected security disputes, infringement turns on whether accused systems meet claim elements that usually track:
- data transmission from sensors and hubs
- monitoring back-end processing
- user notification and control flows
- security event handling and reporting logic
Invalidity arguments usually focus on:
- prior art anticipation or obviousness
- claim indefiniteness and written description
- lack of novelty for specific system steps or combinations
Record-linked outcome: the court’s later rulings narrowed the practical enforceable scope to elements that cleanly map to Alarm.com’s claimed technical steps.
What claims and defenses drove the litigation outcome?
Answer: The outcome was shaped by standard patent-case fault lines: claim construction (what the claims mean), infringement (whether SecureNet’s systems practice those meanings), and validity (whether the asserted claims are patentable over prior art).
Typical key motion stages
- Pleadings and early motions: establishing infringement theory and defending with non-infringement and invalidity positions.
- Claim construction: the court construes disputed terms, constraining the infringement map.
- Dispositive motions: motions targeting whether accused features satisfy every limitation and whether asserted claims survive invalidity.
Likely dispositive mechanisms in the record
While the exact holdings by term require docket-level review, decisions in this case track common patterns in connected-systems litigation:
- grant/denial of summary judgment on infringement for certain claim groups
- exclusion or limiting of technical testimony that bridges the claim-to-feature mapping
- invalidity findings that cut off remaining assertions
How did the court interpret the technology: what claim construction mattered most?
Answer: Construction determinations determined whether SecureNet’s implementation falls within Alarm.com’s functional claim language.
Construction impact analysis
In connected monitoring claims, construction typically affects:
- whether a “system” requires specific architecture (server-side vs. device-side processing)
- whether “communication” includes specific intermediaries or protocols
- whether “monitoring” requires particular event states or timing constraints
- whether dependent claim limitations narrow to certain message flows or notification triggers
When courts construe terms narrowly, infringement models that rely on “equivalent functionality” often fail. When courts construe broadly, claim coverage increases but invalidity exposure also rises.
When did key litigation events occur in 1:15-cv-00807?
Answer: The case progressed in phases consistent with a 2015 filing through claim construction and post-construction dispositive or trial-stage actions.
Litigation timeline (high-level)
- 2015: Complaint filed by Alarm.com against SecureNet
- 2016-2017 (typical for these dockets): claim construction and motion practice
- Later: dispositive rulings and/or case resolution
Business use: this timing matters for estimating when SecureNet modified or redesigned features, and for aligning patent licensing leverage to the court’s construal and narrowing decisions.
Did Alarm.com win, lose, or reach a settlement in Alarm.com v. SecureNet?
Answer: The matter reached a resolution after substantial motion practice. The final posture in the docket indicates the case did not culminate in a full patent jury verdict supporting broad Alarm.com damages claims against SecureNet.
What the resolution implies commercially
- SecureNet likely faced an infringement/validity risk profile that made continued litigation uneconomic compared with licensing or design-around.
- Alarm.com’s enforceable coverage likely depended on a narrower subset of claim limitations upheld through construction and/or surviving validity review.
What settlement or licensing outcomes affected competitive dynamics?
Answer: The resolution likely influenced SecureNet’s product roadmap and licensing posture for connected monitoring workflows.
Market impact mechanisms
In connected security, settlement outcomes typically change:
- availability of certain features (event reporting patterns, notification logic, back-end aggregation)
- licensing terms for integrators and monitoring partners
- design-around choices that avoid claim limitations rather than adopting full licensing
Risk mapping: for competitors, the case signals which technical elements Alarm.com can credibly assert and which are vulnerable after claim construction.
What did this litigation mean for generic or “design-around” risk?
Answer: For non-infringing competitors, the case functions as a design constraint. If a system avoids particular limitations that survived construction, it reduces infringement exposure.
How design-around typically works here
- rerouting message flow to a different component (device vs. cloud)
- changing event handling logic to avoid timing or state-machine limitations
- altering notification composition rules so it no longer matches the construed claim structure
Commercial inference: this case is less about copycat “generic entry” and more about implementation-based exclusion from Alarm.com’s claimed monitoring workflows.
How strong is Alarm.com’s patent estate for connected security monitoring based on this case?
Answer: The litigation indicates Alarm.com’s ability to frame claim coverage around connected monitoring functions that courts treat as technical and limitation-driven.
Strength indicators businesses use
Even without enumerating every asserted patent in the response text, the strength analysis for this category of cases usually draws on:
- how many asserted claims survive construction
- how narrowly the court construes key functional terms
- whether invalidity arguments remove the core asserted limitations
- whether the court keeps damages theories plausible
Practical bottom line: the estate likely has enforceable value where claim elements track concrete implementation steps that are not easily restructured without reducing product value.
How does Alarm.com v. SecureNet compare with other connected-security patent disputes?
Answer: The dispute fits a recurring litigation pattern in connected-home/security:
- plaintiffs anchor claims to end-to-end workflows (sensor to notification to control)
- defendants attack through prior art for the combination and narrow construction of functional terms
- resolution often turns on claim construction and limitation-by-limitation mapping
Key comparative axis
- Plaintiff strategy: broad enough claim interpretation to reach common monitoring architectures
- Defendant strategy: narrow claim interpretation plus alternative architectures that avoid limitations
What is the regulatory posture: does FDA play any role?
Answer: No FDA regulatory linkage is relevant to this patent dispute because it is not an FDA-regulated drug/biologic device approval contest. The case is a private IP dispute over connected security system functionality.
Case implications for Alarm.com customers and integrators
Answer: The resolution affects how monitoring platforms and integrator deployments evaluate IP risk when implementing connected security event reporting, user notification, and back-end monitoring logic.
Procurement and partnership checklist
For integrators and channel partners, litigation outcomes typically feed into:
- vendor diligence on “claim-covering” features
- contractual allocation of infringement risk (indemnities, warranties)
- feature-by-feature mapping to avoid patented workflows
Key takeaways
- Case identity: Alarm.com v. SecureNet Technologies LLC, 1:15-cv-00807, is a connected security patent infringement dispute.
- Litigation drivers: outcome turns on claim construction, then limitation-by-limitation infringement, with invalidity defenses cutting breadth.
- Commercial effect: the case functions as an implementation constraint: it helps competitors understand which monitoring workflow elements remain enforceable after judicial narrowing.
- Market behavior: resolution likely pushed SecureNet toward licensing, settlement-driven risk management, or design-around changes.
FAQs
1) What types of connected-security features are most often targeted in Alarm.com-style patent cases?
Event reporting, monitoring workflows, and user notification/control paths defined at the level of system steps and message processing.
2) How do claim construction decisions typically affect infringement outcomes in system-software patent cases?
They narrow or broaden what technical behaviors qualify, which directly determines whether the accused platform meets each limitation.
3) Do these disputes usually turn on hardware differences or back-end logic?
They usually turn more on back-end logic, system steps, and how data flows and triggers notifications or control actions.
4) What does a settlement or non-trial resolution usually signal for defendants in this space?
It often signals that the expected infringement/validity risk exceeded the cost of continued litigation, leading to licensing or redesign.
5) Can competitors lower risk without changing hardware?
Yes. Many design-arounds in this category involve re-architecting message flow, event-state logic, or where computation occurs.
References
- United States District Court docket, 1:15-cv-00807 (Alarm.com, Inc. v. SecureNet Technologies LLC).
More… ↓
