https://www.patsnap.com/resources/blog/rd-blog/lidar-point-cloud-processing-patent-landscape/ · Patsnap · data cut-off 2026-07-31 · downloaded from the live page
Patent Landscape · Lidar
Lidar Point Cloud Processing Patents: Who Files, What They Claim
  • 34.9% of all 2,741 records sit with just five assignees, so the ground segmentation and clustering claim space is already dense at the top before you even look at the long tail.
  • Filings peaked at 532 in 2023 and the 2021→2024 span shows a -16% pull-back, though 2025-26 counts are still filling in given the usual 18-month publication lag.
  • G01S and G06T lead composition at 28.6% and 23.6% of records respectively, but B60W joint vehicle-control claims still touch over a fifth of the corpus, showing how tightly point cloud work is bound to drive-control filings.
Get a prior-art report on your approach
2,741
Published Records
35%
Top-5 Share of All Records
-16%
Filing Growth 2021→2024
US
Leading Jurisdiction

Filing growth compares 2021 (359 records) with 2024 (300) — a three-year span. 2024 is the most recent year we treat as complete: publication lags filing by roughly 18 months, so 2025 onwards are still filling in and any growth rate that ends there would understate the field. Top-5 share is the combined record count of the five largest assignees divided by all 2,741 records in scope (CR5), not by the ranked leaders only.

Published byPatsnap Research··7 min readSourced from Patsnap Eureka
Overview

What this landscape covers

This landscape tracks patent filings at the intersection of lidar point cloud generation and the processing steps that turn raw returns into usable objects: ground segmentation, clustering, sensor fusion, motion compensation, and the compute-latency and annotation-cost problems that come with running these pipelines at scale. The scope spans 2,741 published records filed or published between 2015 and the 2026 data cut-off.

Records are drawn from filings that explicitly combine point cloud or object-detection lidar language with a downstream processing step, so the set captures the engineering layer between sensor output and perception decisions rather than lidar hardware alone.

Filing activity and technology composition, 2015-2026
  1. 1GM CRUISE HOLDINGS LLC377
  2. 2STRONG FORCE VCN PORTFOLIO 2019 LLC198
  3. 3MOTIONAL AD LLC174
  4. 4WAYMO LLC113
  5. 5GM GLOBAL TECHNOLOGY OPERATIONS LLC94
  6. 6CREATEAI INC90
  7. 7NVIDIA CORP86
  8. 8TUSIMPLE INC78
  9. 9STRONG FORCE TX PORTFOLIO 2018 LLC72
  10. 10AURORA OPERATIONS INC70
Source: Patsnap Eureka. Assignee ranking and totals. Derived from a Patsnap search on Lidar Point Cloud Processing covering 2015–2026, data cut-off 2026-07-31. Counts reflect published records only and shift as new filings publish.Run this in Eureka MCP

Let an AI agent run this analysis on your own technology

Pick a task. Every answer cites the patents behind it.

10,000 free credits to start
The data

Filing trend and technology composition

Two views of the same 2,741 records: how filing activity has moved year over year, and which IPC subclasses carry the work.

Filing trend, 2017-2026

Annual publications rose from 91 in 2017 to a peak of 532 in 2023. The 2021-to-2024 window shows a -16% change (359 to 300), which reads as a genuine pull-back rather than noise since both years are past the publication lag window; 2025 and 2026 figures will keep revising upward as later filings publish.

Filing trend, 2017-2026015030045060091201720182019202020212022532202320242025372026Most recent year is partial — publication lag means later filings are not yet visible.

Technology composition by IPC subclass

G01S (radar, sonar and positioning) and G06T (image data processing) are the two largest classes, at 28.6% and 23.6% of the 2,741 records respectively. G06V recognition and B60W joint vehicle control each clear a fifth of the corpus, and G06N AI-model computing sits close behind — evidence that point cloud processing claims are rarely written in isolation from perception and control claims. Because records can carry multiple classes, these shares sum to well over 100%.

Technology composition by IPC subclassG01S · Radar, sonar & positioning78428.6%G06T · Image data processing & genera…64623.6%G06V · Image/video recognition60222.0%B60W · Hybrid/joint vehicle control57921.1%G06N · Computing based on AI models48317.6%G05D · Control of non-electric variab…47917.5%G06F · Electric digital data processi…35813.1%G06Q · Business, commerce & admin dat…32011.7%Other2,36286.2%

Shares are the percentage of the 2,741 records in scope. A patent can carry several IPC classes, so the shares add up to more than 100%.

Source: Patsnap Eureka. Filing trend and technology composition. Derived from a Patsnap search on Lidar Point Cloud Processing covering 2015–2026, data cut-off 2026-07-31. Counts reflect published records only and shift as new filings publish.

Go deeper on Lidar Point Cloud Processing with Eureka

This page is one run against one query. Ask Eureka your own question about lidar point cloud processing and every answer comes back with the patent numbers behind it.

Try Eureka
Key patents

A representative filing

Representative record
US20230141421A12023-05-11

Point cloud motion compensation method and apparatus, storage medium, and lidar (US20230141421A1)

SUTENG INNOVATION TECHNOLOGY CO., LTD.

The filing covers a method for compensating point cloud motion by combining millimeter-wave radar point cloud data, timestamped and carrying a motion parameter for a target object, with a separately obtained lidar point cloud data frame from scanning the same working region. The two data sources are aligned to correct for the time-of-flight and motion artefacts that arise when a lidar performs a rotating or scanning capture while the target itself is moving.Filed by Suteng Innovation Technology; published 2023-05-11.

US20230141421A1 — patent drawing 1US20230141421A1 — patent drawing 2
View full record
Most-cited records in scope
#Publication no.Patent titleCitations
1US20190258251A1Systems and methods for safe and reliable autonomous vehicles1,044
2US20200284883A1Component for a lidar sensor system, lidar sensor system, lidar sensor device, method for a lidar sensor syst…1,013
3US20210157312A1Intelligent vibration digital twin systems and methods for industrial environments715
4US20210342836A1Systems and methods for controlling rights related to digital knowledge464
5US20220366494A1Market orchestration system for facilitating electronic marketplace transactions437
6US20220108262A1Industrial digital twin systems and methods with echelons of executive, advisory and operations messaging and…386
7US20160068267A1Context-based flight mode selection356
8US20210133670A1Control tower and enterprise management platform with a machine learning/artificial intelligence managing sen…339
9US20230123322A1Predictive Model Data Stream Prioritization337
10US20220187847A1Robot Fleet Management for Value Chain Networks336

Citation counts favour older filings simply because they have had longer to accumulate citations inside this corpus; treat them as a signal of influence, not of current technical importance.

Each row carries its publication number; clicking a row searches Eureka by that number.

Source: Patsnap Eureka. Citation counts and representative records. Derived from a Patsnap search on Lidar Point Cloud Processing covering 2015–2026, data cut-off 2026-07-31. Counts reflect published records only and shift as new filings publish.Run this in Eureka MCP
Run it yourself

Put your own technology through the same analysis


  
Where to run it
Fastest

Eureka on the web

When you want the answer in the next five minutes.

The agent works the prompt against patents and technical literature, citing every source.

Run your analysis now →
For builders

MCP server & REST API

When it has to run inside your own pipeline.

Patent search, landscape analysis and assignee resolution as MCP tools. Drop them into any agent framework, or call REST directly.

Browse MCP servers →
Insights

What the numbers mean for a filing decision

Read together, the concentration figures, the trend, and the receiving-office split point to a field where the core motion-compensation and fusion claims are already staked out, while procedural and cost-reduction angles remain more open.

Concentration
34.9%
of 2,741 records held by top 5 assignees

The top of the field is dense

Five assignees hold 956 of the 2,741 records in scope, 34.9% of the total. That concentration sits mostly in core detection and motion-compensation claims tied to autonomous-vehicle programs, which makes those specific claim constructions expensive ground to file into without a clear design-around.

Top 5 combined, 956 of 2,741 records
Momentum
-16%
change in filings, 2021 to 2024

Growth has cooled from its 2023 peak

Annual filings peaked at 532 in 2023, and the last fully comparable span shows a -16% move from 359 filings in 2021 to 300 in 2024. That is a real pull-back in a maturing filing base, not a data artefact, though the 2025-26 counts shown elsewhere on this page will still revise upward as later filings publish.

2021: 359 → 2024: 300
Composition
28.6%
of records classed under G01S

Positioning and imaging classes dominate

G01S (radar, sonar and positioning) leads at 28.6% of the 2,741 records, closely trailed by G06T image-data processing at 23.6%. The overlap with B60W vehicle-control classes at 21.1% shows most point cloud processing patents are written as part of a larger autonomous-driving claim set rather than as standalone sensing patents.

G01S 784 records, G06T 646 records
Jurisdiction
1,657
records with a US receiving office

Filing activity is US-centred

The United States receives more than five times the filings of the next-largest office (EPO, 318), with PCT applications at 266. Anyone building a global filing strategy in this space should expect the densest prior art, and the sharpest competitive activity, in US filings first.

US 1,657, EPO 318, WIPO/PCT 266
Eureka AI Agent
Looking for what nobody has claimed yet?

Eureka can read the same corpus for gaps instead of for coverage: under-claimed branches adjacent to lidar point cloud processing, with the prior art for and against each one.

Find the white space →
Source: Patsnap Eureka. Co-assignee relationships and derived observations. Derived from a Patsnap search on Lidar Point Cloud Processing covering 2015–2026, data cut-off 2026-07-31. Counts reflect published records only and shift as new filings publish.Run this in Eureka MCP
Players

Who is filing, and where the field is still open

The ranked leaders are dominated by autonomous-vehicle platform companies and their component suppliers, with a long tail of single- or few-filing entrants behind them.

Leader
377
records

One assignee holds a clear lead

The top-ranked assignee holds 377 records, well ahead of the fifth-place assignee at 94 and the tenth-place assignee at 70. That gap between first place and the rest of the top ten suggests one program has filed far more broadly across the point cloud processing stack than any single competitor.

Leader: 377 records; 10th place: 70 records
Mid-field
49.3%
of 2,741 records held by top 10

The top ten already cover half the field

The ten highest-ranked assignees together hold 1,352 of the 2,741 records in scope, 49.3% of the total. Filing into this space now means either designing around that half of the corpus or picking a sub-area the leaders have not yet claimed densely.

Top 10 combined, 1,352 of 2,741 records
Momentum
-71% YoY
in latest-year filings for one leading assignee

Recent-year activity is cooling across the board

Several of the most active historical filers show falling or flat latest-year counts, with year-on-year drops as steep as -71% for one and -100% for another. Given the publication lag, this understates true recent activity, but it is consistent with a field where the earliest movers have already staked their core claims and are filing less broadly now.

Latest-year filings down across multiple ranked leaders
🔍
Under-claimed sub-areas
Branches with comparatively thin, specific claim coverage relative to the core detection and fusion filings
Annotation-cost reduction for point cloud labellingCompute-latency optimisation for onboard clusteringCross-sensor motion-compensation calibrationLow-density edge-case ground segmentationCommerce and admin data uses of point cloud output
Rank all filers by momentum →
Recent-year filing momentum
AssigneeRecent yearYoY
STRONG FORCE TX PORTFOLIO 2018 LLC2-33%
NVIDIA Corp2-71%
Waymo LLC1-67%
GM Cruise Holdings LLC0—
Strong Force VCN Portfolio 2019 LLC0-100%
TuSimple Inc0—
Motional AD LLC0-100%
GM Global Technology Operations LLC0-100%
Source: Patsnap Eureka. Assignee-level momentum. Derived from a Patsnap search on Lidar Point Cloud Processing covering 2015–2026, data cut-off 2026-07-31. Counts reflect published records only and shift as new filings publish.Run this in Eureka MCP
What's next

Where to take this analysis

The figures above describe the field as it stands at this data cut-off. Turning that into a filing or freedom-to-operate decision means going claim by claim.

Map claims against the leader's portfolio

Start with the 377-record leader and the next four ranked assignees, since together they hold 34.9% of all records in scope, and check which specific claim language recurs across their filings.

Explore assignee portfolios in Eureka

Test a white-space claim before drafting

Annotation-cost reduction and compute-latency optimisation show thinner, more specific coverage than core detection claims; running a candidate claim against the corpus early avoids drafting into occupied space.

Run a claim search in Eureka
Source: Patsnap Eureka. Forward-looking reading of the same dataset. Derived from a Patsnap search on Lidar Point Cloud Processing covering 2015–2026, data cut-off 2026-07-31. Counts reflect published records only and shift as new filings publish.Run this in Eureka MCP
FAQ

Common questions about this landscape

Answers are grounded in the same dataset. Derived from a Patsnap search on Lidar Point Cloud Processing covering 2015–2026, data cut-off 2026-07-31. Counts reflect published records only and shift as new filings publish.Run this in Eureka MCP

Research Lidar Point Cloud Processing in depth with Eureka

Go past this page: query the whole lidar point cloud processing corpus yourself, in your own scope.
Every answer comes back with patent numbers you can open.

Try Eureka

Disclaimer. This page is generated from Patsnap Eureka data drawn from a limited snapshot of global patent and scientific-literature records, and is provided for general information and reference only.

Patent data carries inherent limitations: recent filings (typically the most recent 18–24 months) are under-counted due to standard publication lag; counts may be reported at either a patent-family or a patent-record basis and are not always directly comparable; classification, applicant-name, and citation data may contain errors, duplicates, or omissions; and the underlying search query defines and constrains the scope shown. As a result, the analysis may be incomplete or inaccurate and may not reflect the full technology landscape.

Nothing on this page constitutes an exhaustive prior-art, novelty, freedom-to-operate, or validity search, nor does it constitute legal, financial, investment, or professional advice, and it should not be relied upon as such. Any patent, commercial, or strategic decision should be verified independently and reviewed with qualified patent, legal, and domain professionals. Patsnap makes no warranties, express or implied, as to the accuracy, completeness, or fitness for any particular purpose of the information presented.

Machine translation. Assignee and organisation names originally recorded in Chinese, Japanese or Korean have been rendered into English by an AI translation step so that the tables stay readable. These renderings are best-effort and may not match a company's registered English name; the original name is what the underlying patent record carries, and it is what any Eureka query launched from this page uses.

Help us improve

Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.