Lidar patents: claim the system, not just the part

A strong lidar patent claims the invention at more than one level: the component (a beam scanner, a detector, a laser source), the full sensing system, and the methods the sensor and its host run in the field. A competitor can often swap out a single component. Swapping out the way the whole system behaves is much harder.

This article is for founders and engineering leads at autonomy, robotics and optical sensing companies. I explain why component claims are easy to design around, how to layer claims for beam steering, detectors and signal processing, who infringes each claim type under U.S. law, and how to keep processing claims eligible and definite. If your invention lives on a photonic chip, my earlier post on claiming a photonic integrated circuit covers the device and fabrication side. Here the focus is the sensor as your customers use it.

Key takeaways

• A lidar patent built only on one component, such as a MEMS mirror or a SPAD array, is usually the easiest kind for a competitor to design around.
• Layer the claims: component, system, sensor-side method, host-side method and, where it fits, the vehicle or robot.
• For every claim, name the single company that would perform every element. If no single company does, the claim may be hard to enforce.
• Signal-processing claims hold up better when they are tied to the sensor hardware and to a technical improvement that the specification explains.
• “A processor configured to” language needs an algorithm in the specification, or the claim can become indefinite.

Why is a component-only lidar patent easy to design around?

A component claim covers one way of doing one job. Lidar has many interchangeable ways to do each job: steer a beam, detect a photon, encode a pulse. A competitor who reads a component-only lidar patent can often pick another architecture and still deliver the same range, resolution and frame rate to the same customer.

Lidar measures distance by sending out laser light and timing or analyzing the light that comes back. NOAA describes lidar as a remote sensing method that uses pulsed laser light to measure ranges. Beam steering can be mechanical rotation, a MEMS mirror, a polygon scanner, an optical phased array or a flash design with no scanning. Detection can use avalanche photodiodes, single-photon avalanche diode (SPAD) arrays or coherent receivers. Ranging can be pulsed time-of-flight or frequency-modulated continuous wave (FMCW).

Suppose your team claims a MEMS mirror with a new torsion hinge that survives vehicle vibration. That claim has value, but a competitor using an optical phased array never touches it. If the real advance is what the mirror lets you do, such as revisiting a region of interest within one frame, then the claim that matters describes that behavior at the system level.

What should a lidar patent claim at each level?

Think of the claim set as layers, each protecting against a different design-around and reaching a different infringer. A layered lidar patent usually has component, system and method claims, and sometimes an application claim. The table compares them.

Beam steering

Claim the steering hardware if it is new. Then claim what the steering enables. Examples: a scan pattern that changes density based on earlier returns, synchronization between the scan position and the active detector region, or a method of correcting pointing error using a reference return. These system and method claims can cover a competitor who reaches the same behavior with a different scanner.

Detectors

A new SPAD pixel or readout circuit deserves its own claims. The broader claim usually describes how the receiver is used: activating only the pixels that match the expected return location, setting the time gate from the scan state, or combining histograms across pixels to reject sunlight. Write those as receiver-plus-controller system claims and as method claims.

Signal processing

Processing is often where performance comes from: rejecting crosstalk from other lidar units with coded pulses, extracting per-point velocity from FMCW returns, flagging returns from rain or dust. Claim these as the sensor’s processing and as the host computer’s processing, because different companies may run each.

Who infringes a lidar system or method claim?

Direct infringement requires one actor who makes, uses, sells or imports the whole claimed invention, or who performs every step of a claimed method. Lidar products are built by chains of companies, so a well-drafted claim names elements that one company in that chain will actually provide or perform.

Under 35 U.S.C. § 271(a), whoever without authority makes, uses, offers to sell, sells or imports a patented invention in the United States infringes. For system claims, the Federal Circuit held in Centillion Data Systems v. Qwest (2011) that “use” means putting the system as a whole into service, which requires controlling the system and obtaining benefit from it. There, the customers used the system; the supplier that provided only the back end did not.

For method claims, the en banc court in Akamai Technologies v. Limelight Networks (2015) held that every step must be performed by or attributable to a single entity. Steps by others count when that entity directs or controls them, when the actors form a joint enterprise, or when it conditions a benefit on performing steps and sets their manner or timing.

Here is the lidar problem. If one method claim recites emitting and detecting light (inside the sensor module) and then classifying objects (in the OEM’s perception stack), the module maker and the OEM each perform only part. That divided infringement can leave no single direct infringer. The fix is drafting: separate method claims for what the sensor does and what the host computer does.

Indirect infringement is a backup, not a plan

Section 271(b) makes a party who actively induces infringement liable, and § 271(c) reaches sellers of components especially made for an infringing use that are not staple articles with substantial noninfringing uses. Both have limits. The Supreme Court held in Limelight Networks v. Akamai (2014) that there is no inducement liability without an underlying direct infringement. In June 2026, in Hikma Pharmaceuticals v. Amarin, the Court unanimously held that inducement requires affirmative, culpable encouragement and that ordinary acts of product distribution are not enough. That was a drug-labeling case, but the rule is general. A claim that reaches the competitor directly is worth more than a theory that its customers infringe.

Exhaustion and your own sales

Once you or a licensee sells an authorized product, patent rights in that item are exhausted. In Quanta Computer v. LG Electronics (2008), the Supreme Court held that exhaustion also applies to method patents when the item sold substantially embodies the method. System and method claims remain valuable against competitors’ sensors and the companies that integrate them.

How do you claim lidar signal processing so it survives § 101?

Tie the processing to the sensor hardware and to a technical improvement in sensing, and explain that improvement in the specification. Claims that only recite math or a result read as abstract. Claims that recite a specific sensor arrangement and how its raw data is used to measure better have fared well.

Section 101 of the Patent Act excludes abstract ideas, such as mathematical concepts, from patent eligibility. In Thales Visionix v. United States (2017), the Federal Circuit upheld claims to a tracking system using two inertial sensors, one on a helmet and one on a moving platform, and a method of computing orientation from their signals. The court said that needing a mathematical equation “does not doom the claims to abstraction.” In Contour IP Holding v. GoPro (2024), it held claims to a camera that generates two parallel video streams of different quality were not abstract, because they recited specific technical means.

USPTO practice points the same way. A December 5, 2025 USPTO memorandum revised the MPEP’s eligibility guidance after Ex parte Desjardins. It tells examiners to check whether the specification describes an improvement and whether the claim includes the components or steps that provide it, and not to evaluate claims at too high a level of generality. A conclusory statement of improvement does not count. Explain why your crosstalk filter cuts false returns, with physics and test data, not just that it does.

Watch “configured to” and “module” language

A claim element written as a generic placeholder plus a function, such as “a processing module configured to reject crosstalk,” may be read as a means-plus-function limitation under 35 U.S.C. § 112(f). The en banc Federal Circuit in Williamson v. Citrix Online (2015) held that such terms can trigger § 112(f) even without the word “means.” For computer-implemented functions, MPEP 2181 requires the specification to disclose an algorithm for performing the function. Without one, the claim is indefinite. Put the algorithm in the application: equations, flowcharts and parameter ranges.

Worked example: layering claims for an adaptive-scan lidar

Take a common invention: a solid-state lidar that spots a possible obstacle in a coarse scan, then scans that region densely in the same frame while activating only the matching detector pixels. Here is how I would build the claim set from the inside out.

1. Component claim. If the scanner or the addressable SPAD array is new, claim its structure on its own terms.
2. System claim. Claim a transmitter, a beam scanner, a pixelated receiver and a controller that sets a denser scan pattern for a region identified from earlier returns and activates the receiver pixels that correspond to it. Avoid architecture words such as “MEMS” in the independent claim unless the advance depends on them.
3. Sensor-side method claim. Recite the steps the sensor itself performs: coarse scan, identifying a region from returns, dense scan, and gated detection. One company, the sensor operator, performs all of them.
4. Host-side method claim. If the vehicle computer selects the region, claim the host’s steps separately: receiving the coarse point cloud, selecting a region, sending a scan command and fusing the dense returns.
5. Application claim. Consider a claim to a vehicle or mobile robot that includes the sensor and adjusts its path based on the dense scan.
6. Dependent fallbacks. Add specifics that a reviewer could find in a competitor’s datasheet or teardown: scan-density ratio, timing within one frame, gate width, pixel grouping.
7. Specification support. Describe at least two steering architectures and two detector types, so broad system claims are not limited to your own build.

A pre-filing checklist for a lidar patent application

Before filing, test the draft claims against how the product will be sold, integrated and used in the field. This short list often changes which claims go into the application and how they are worded.

1. Map the value chain: who makes the chip, the module, the perception software and the vehicle or robot.
2. For each independent claim, name the one company that would make, use or sell every element, or perform every step.
3. Check each claim against at least two competing architectures. Does it still read on them?
4. Make sure every claim element is detectable from a product, its documentation or its output.
5. Describe the technical improvement and its physical cause in the specification, with data where you have it.
6. Give an algorithm for every processing function the claims recite.
7. Line the filing up with papers, conference talks and customer demos. My post on patent filing timing covers how disclosures start the clock.

Diligence teams ask the same questions, as I discuss in what investors ask about your patents.

Frequently asked questions

What parts of a lidar system can be patented?

Almost any new and nonobvious part can be: laser sources, beam steering hardware, detectors and readout circuits, optics, packaging, calibration methods and signal processing. The system as a whole and the methods it performs can also be patented. The strongest portfolios usually combine component claims with system and method claims that describe how the sensor is used.

Should a lidar startup claim the component or the whole system?

Usually both. A component claim protects your specific hardware and reaches anyone who makes or sells it. A system claim covers the combination and the behavior that customers buy, so it is harder to design around. Method claims add coverage for how the sensor and host computer operate. Each layer covers a gap the others leave.

Can lidar signal processing be patented in the United States?

Yes, when the claims are tied to the sensor and to a technical improvement in measurement, rather than to math alone. Federal Circuit decisions such as Thales Visionix (2017) upheld claims to sensor configurations and how their data is processed. Explain the improvement and its cause in the specification, and disclose the algorithms the claims rely on.

Who infringes a lidar method patent if a supplier and an OEM each perform some steps?

Possibly no one directly. Under the Federal Circuit’s 2015 Akamai decision, all steps must be performed by or attributable to one entity, for example through direction or control. When a sensor supplier and a vehicle maker each perform part, liability is uncertain. Drafting separate sensor-side and host-side method claims avoids most of this problem.

Does selling my lidar modules limit my patent rights?

For the units you sell, yes. An authorized sale exhausts the patent rights in that item, and the Supreme Court held in Quanta (2008) that this extends to method claims the item substantially embodies. Your claims still apply to competitors’ sensors and to companies that build them into vehicles or robots.

Talking it through

The best time to layer a lidar claim set is before the first filing, while the engineers can still describe the alternatives. If you are weighing what to claim for a new scanner, detector or processing method, or want a review of an existing portfolio against your photonics and optics roadmap, I’m happy to talk it through.

This article is general information, not legal advice, and reading it does not create an attorney-client relationship. Patent law changes and every situation differs. Please talk to a patent attorney about yours.

Message Alexander on LinkedIn