Locus Location Systems LLC v. Pctel Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: Locus Location Systems, LLC (Florida)
  • Defendant: PCTEL, Inc. (Delaware)
  • Plaintiff's Counsel: Young Conaway Stargatt & Taylor, LLP
• Case Identification: 1:26-cv-00487, D. Del., 04/27/2026
• Venue Allegations: Venue is asserted in the District of Delaware based on Defendant's incorporation in the state and alleged acts of infringement committed within the district.
• Core Dispute: Plaintiff alleges that Defendant's SeeHawk® Monitor line of products, used for automated spectrum monitoring, infringes a patent related to the over-the-air analysis of radio performance.
• Technical Context: The technology concerns non-disruptive, real-time diagnostic systems for mission-critical two-way radio networks, such as those used by public safety and military agencies.
• Key Procedural History: The complaint alleges that Plaintiff met with Defendant on March 30, 2018, to discuss Plaintiff's technology and disclosed the existence of its patents. Plaintiff alleges that Defendant, lacking a comparable solution at the time, subsequently developed the accused product by copying the patented technology. This meeting is cited as evidence of pre-suit knowledge for the willfulness allegation.

Case Timeline

Date	Event
2009-10-18	U.S. Patent No. 8,565,096 Priority Date
2013-10-22	U.S. Patent No. 8,565,096 Issue Date
2018-03-30	Meeting between Locus and PCTEL representatives
2026-04-27	Complaint Filing Date

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 8565096 - "Method and System for Analyzing Radio Performance During Over-the-Air Operation"

• Patent Identification: U.S. Patent No. 8565096, "Method and System for Analyzing Radio Performance During Over-the-Air Operation", issued October 22, 2013.

The Invention Explained

• Problem Addressed: The patent describes the problem of diagnosing performance issues in communications transmitting devices, such as two-way radios. Prior methods often failed to detect that a device was not operating according to its specifications until it failed completely, requiring it to be taken out of service for diagnosis and repair '096 Patent, col. 1:16-28 This presents significant risks, especially in mission-critical networks '096 Patent, col. 2:6-13
• The Patented Solution: The invention provides a system that analyzes the performance of radios "during normal operation" by capturing and measuring live, over-the-air transmissions '096 Patent, abstract '096 Patent, col. 2:10-13 The system employs sensors to receive radio-frequency (RF) signals, an analyzer to measure signal parameters and determine operational "health," and uses an identifier embedded in the transmission to correlate the analysis with a specific device '096 Patent, abstract '096 Patent, col. 4:4-9 The results are then displayed on a graphical user interface, allowing network operators to identify radios needing maintenance before they fail '096 Patent, col. 4:29-39
• Technical Importance: The technology enabled a shift from reactive repair to proactive, predictive maintenance for radio networks, improving reliability without service disruption Compl. ¶¶12-13 Compl. ¶21

Key Claims at a Glance

• The complaint asserts at least independent claim 1 of the '096 Patent Compl. ¶42
• The essential elements of independent claim 1 are:
  • An apparatus for determining operating characteristics of RF transmitting devices during normal over-the-air operation, where each signal includes a device identifier.
  • At least one RF signal sensor for receiving the RF signals.
  • An analyzer for measuring signal parameters and determining operating characteristics.
  • The analyzer uses the device identifier to correlate the characteristics to a specific device.
  • The analyzer collects operating characteristics for identified devices "more frequently" than for other devices.
  • A graphical user interface for displaying the operating characteristics.
• The complaint does not explicitly reserve the right to assert dependent claims, but infringement of "one or more claims" is broadly alleged Compl. ¶62

III. The Accused Instrumentality

Product Identification

The accused instrumentality is PCTEL's SeeHawk® Monitor system, which includes components identified as Remote Test Units (RTUs), Platform Manager, and SeeHawk Central Compl. ¶¶35-36

Functionality and Market Context

The complaint alleges the SeeHawk® Monitor is an "automated system for ensuring reliable critical communications" by monitoring spectrum, reporting radio metrics, and automating uplink testing Compl. ¶45 The system allegedly uses RTUs installed at radio sites to "receive and monitor spectrum and radios," measuring parameters such as RF power Compl. ¶37 The data is allegedly correlated to specific radios using a radio ID, and the "Platform Manager" and "SeeHawk Central" software are used to display and report the results via a graphical user interface Compl. ¶38 The complaint further alleges the system can be configured to schedule testing at "selectable cadences for specific radios or sites" Compl. ¶39 The complaint includes a diagram from a PCTEL brochure depicting the SeeHawk® Monitor system architecture Compl. p. 11, FIG. 1

IV. Analysis of Infringement Allegations

'096 Patent Infringement Allegations

Claim Element (from Independent Claim 1)	Alleged Infringing Functionality	Complaint Citation	Patent Citation
An apparatus for determining operating characteristics of radio-frequency (RF) transmitting devices while the devices are in normal operation transmitting over-the-air RF signals each including an identifier of the transmitting device...	PCTEL's SeeHawk® Monitor is alleged to be such an apparatus, determining operating characteristics of RF transmitting devices during normal operation (Compl. ¶44). The system is described as working with signals that have a "radio ID" Compl. ¶45	¶44; ¶45	col. 7:8-14
at least one RF signal sensor receiving the RF signals, the at least one sensor responsive to the RF signals received;	The SeeHawk® Monitor system utilizes Remote Test Units (RTUs) that are "installed at radio sites" to "receive and monitor spectrum and radios," which allegedly function as the claimed RF signal sensors (Compl. ¶37; Compl. ¶48; Compl. ¶49).	¶37; ¶48; ¶49	col. 7:15-16
an analyzer measuring signal parameters of received RF signals and determining operating characteristics of the transmitting devices from the signal parameters...	The system allegedly "measures RF power, and performs spectrum analysis and protocol-specific measurements," thereby measuring signal parameters and determining device operating characteristics like "frequency offset" (Compl. ¶37; Compl. ¶46; Compl. ¶50).	¶37; ¶46; ¶50	col. 7:17-20
the analyzer: using the identifier from the received RF signals to correlate operating characteristics to the particular one of the transmitting devices;	The accused system's "Radio Metrics" functions allegedly "allow sorting and filtering by radio ID," which is presented as evidence of using an identifier to correlate data to a specific device (Compl. ¶38; Compl. ¶53; Compl. ¶55). The complaint provides a visual of this function described in a brochure (Compl. p. 12, FIG. 3).	¶38; ¶53; ¶55	col. 7:21-24
...and collecting operating characteristics for identified transmitting devices more frequently than operating characteristics for other transmitting devices;	The complaint alleges the "Platform Manager can be configured to conduct testing and/or monitoring as selectable cadences for specific radios or RTUs," thereby collecting data more frequently for targeted devices Compl. ¶39 Compl. ¶57 A brochure image shows the Platform Manager scheduling tests (Compl. p. 15, FIG. 6).	¶39; ¶57	col. 7:25-28
and a graphical user interface displaying the operating characteristics for each transmitting device.	The "Platform Manager and SeeHawk Central software" are alleged to "display and report" results via a graphical user interface, showing metrics, test results, and performance problems (Compl. ¶38; Compl. ¶54; Compl. ¶59). A brochure screenshot shows the display of radio metrics (Compl. p. 17, FIG. 8).	¶38; ¶54; ¶59	col. 7:33-35

• Identified Points of Contention:
  • Scope Questions: A potential dispute may arise over whether the accused "Platform Manager" software, which is allegedly "configured" to schedule tests Compl. ¶57, is part of the claimed "analyzer" that performs the "collecting." The case may explore whether a user-configured scheduling system meets the claim limitation of the apparatus itself collecting data more frequently for certain devices.
  • Technical Questions: The complaint alleges the system can be configured for more frequent collection for specific devices Compl. ¶57 A key question will concern the evidence that this functionality is actually used as intended by customers, or whether the mere capability and instruction to do so is sufficient to meet the claim limitation.

V. Key Claim Terms for Construction

• The Term: 'analyzer'

  • Context and Importance: The definition of "analyzer" is critical because Claim 1 requires the "analyzer" to perform three distinct functions: measuring, correlating, and collecting more frequently. The complaint appears to map these functions across different components of the SeeHawk® Monitor system (RTUs, Platform Manager). The scope of this term will determine whether these distributed functions can be attributed to a single claimed "analyzer."
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent specification describes a "DiagnostX Analyzer (DA)" that "performs calculations and determines" if a radio is out of spec '096 Patent, col. 4:20-24 The patent also describes the overall "system" as being able to target specific radios for more frequent data collection '096 Patent, col. 4:45-49 A party could argue "analyzer" refers to the system's collective analysis logic, not just a single physical or software component.
    • Evidence for a Narrower Interpretation: The patent's block diagram depicts the "DiagnostX Analyzer (DA)" as a distinct module separate from the "Sensor" and "DiagnostX Viewer (DV)" '096 Patent, FIGURE A party could argue this suggests a more narrowly defined component responsible only for measurement and calculation, and that other functions like scheduling and display are performed by separate components not encompassed by the term "analyzer."

• The Term: 'collecting operating characteristics for identified transmitting devices more frequently'

  • Context and Importance: This limitation appears central to the patent's novelty, distinguishing it from a simple, uniform monitoring system. The infringement allegation hinges on the "Platform Manager" software's ability to schedule tests at "selectable cadences" Compl. ¶57
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification states that "performance data for the targeted radios can be collected more frequently than the other radios in the database" '096 Patent, col. 4:48-49 This language, focusing on the result ("can be collected"), may support an interpretation where user-initiated scheduling that achieves this result meets the claim limitation.
    • Evidence for a Narrower Interpretation: The claim requires the analyzer to perform the "collecting." A party might argue this requires an active, automated decision-making process within the analyzer itself, rather than the execution of a pre-set schedule configured by a human user. They could argue that merely providing scheduling options does not constitute the analyzer "collecting... more frequently" in the manner claimed.

VI. Other Allegations

• Indirect Infringement: The complaint alleges both induced and contributory infringement. Inducement is based on allegations that PCTEL actively encourages and instructs customers on how to use the accused system in an infringing manner through "user manuals, marketing materials, and technical support" Compl. ¶63
• Willful Infringement: Willfulness is alleged based on PCTEL's purported pre-suit knowledge of the '096 Patent. The complaint specifically cites a March 30, 2018 meeting where Locus representatives allegedly informed PCTEL of the patented technology, after which PCTEL allegedly "copied" it Compl. ¶32 Compl. ¶34 Compl. ¶67

VII. Analyst's Conclusion: Key Questions for the Case

The resolution of this case may turn on the following central questions:

1. Definitional Scope: A core issue will be the construction of the term analyzer. The court will need to determine if this single claim term can encompass multiple, potentially distributed software and hardware components of the accused SeeHawk® Monitor system, including the RTUs and the Platform Manager.

2. Functional Infringement: A key evidentiary question will be one of functional operation. Does the accused system's capability to be configured by a user to test certain radios at "selectable cadences" satisfy the claim limitation that the analyzer itself "collect[s]" data "more frequently" for identified devices, or is there a technical and legal distinction between providing a scheduling tool and performing the claimed function?

3. Willfulness and Copying: The case presents a pointed question of intent. The factual evidence surrounding the March 30, 2018 meeting will be critical in determining whether PCTEL had pre-suit knowledge of the patent and whether its subsequent development of the SeeHawk® Monitor constitutes willful infringement or copying, potentially exposing it to enhanced damages.