https://eureka.patsnap.com/resources/blog/rd-blog/visibility-graph-based-robot-path-planning-algorithm-patent-landscape/ · Patsnap · data cut-off 2026-10-20 · downloaded from the live page
Patent Landscape · Robotics & Autonomous Systems

Visibility Graph Based Robot Path Planning Algorithm Patents

A dataset of 11 patent families and 16 records on visibility-graph robot path planning, with no single filer ahead of the rest.

16
Published Records
11
Simple Patent Families
38%
In Force at Cut-off
CN
Leading Jurisdiction

16 published records collapse into 11 simple (DOCDB) families; the difference is the same invention filed in more than one country. In force = 6 of 16 records still granted and maintained at the data cut-off; the rest are pending, withdrawn, refused or lapsed.

  • 11 simple patent families and 16 published records sit behind this search. No date limit was applied, so this is every matching record the search string returns regardless of filing date.
  • 11 filers are listed, and 11 of them hold 1 family each at the top of the count. There is no single filer ahead of the rest; the largest row is named on 1 of the 11 families (9.1%).
  • G01C (distance, navigation & gyroscopes) appears on 7 of the 11 families. 63.6% of the families in scope, the highest share of any subclass here.
Check your own idea
Published byPatsnap Research··6 min readSourced from Patsnap Eureka
Overview

What this dataset covers

This page reports results for the search string TAC:((robot* OR manipulator) AND "visibility graph" AND ("path planning" OR navigation)), which returned 11 simple patent families across 16 published records. No date limit was set on the query, so the result spans whatever filing dates the matching documents carry; the filing-trend chart below shows a recent window only, not the full set. Filer, classification and receiving-office figures are all counted from the same 11 families and 16 records described here.

11 families is a small pool. Treat this page as a starting point for a further search, not as a map of a field, absence of a name or a classification here is far more likely to reflect the search terms than an absence of filing activity.

Records and families in scope
  1. Inner Mongolia Bazhua Intelligent Technology Co., Ltd.1
  2. ZHEJIANG UNIV OF TECH1
  3. FUZHOU UNIV1
  4. NANJING INST OF TECH1
  5. LANZHOU UNIV OF ARTS & SCI1
  6. AVIDBOTS CORP1
  7. JIANGSU MARITIME INST1
  8. NANJING NORMAL UNIVERSITY1
  9. SHANDONG UNIV1
  10. MICROSOFT TECHNOLOGY LICENSING LLC1

Ordered by volume only, not by importance or claim strength. Counted in simple (DOCDB) patent families, so one invention filed in several countries counts once. Names come from Patsnap's standardised assignee field as recorded on each document; subsidiaries and group companies are not merged. The icon before each name is read from the name itself (words such as University, Institute or Ltd); the data carries no organisation-type field, so treat it as a reading aid rather than a classification. Filings held by named individuals rather than organisations are removed where they can be identified; that identification is not exhaustive, so an individually held filing can still appear below. Either way those filings stay inside the totals above. This table shows the top 11 of the 11 filers returned for this search; the data endpoint returns at most 100 entities, so even that 11 is not the complete set of filers. A single family can name more than one filer, so these counts overlap and do not add up to the total.

Source: Patsnap Eureka. Assignee ranking and totals. Derived from one Patsnap search for Visibility Graph Based Robot Path Planning Algorithm Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-20. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
Data

Filings, classes and receiving offices

Figures below are drawn directly from the search result: 16 published records, 11 simple patent families, and the classification and office breakdowns that accompany them.

Filing trend by earliest filing year (published records)

The chart counts published records by earliest filing year, from 2019 (2 records) through 2026 (1 record), with a peak of 3 records reached in both 2023 and 2024. Years from 2022 onward are shaded because records filed in that stretch are still publishing; the line should not be read as a rise or fall in activity.

Filing trend by earliest filing year (published records)012232201920202021202232023320242025120262022 onwards are shaded as still filling in: a filing is only visible once it publishes, up to 30 months after filing.

Counted in published records by earliest filing year, not de-duplicated into families. A filing is counted in the year it was filed, but it only becomes visible after it publishes: roughly 18 months for most routes, and up to 30 months where a PCT application enters national phase. 2022 onwards are therefore still filling in and are shaded; no growth figure on this page uses them. Because this series counts documents rather than inventions, a rise can mean more inventions or the same inventions filed in more countries; this dataset cannot separate the two.

Technology composition (IPC subclass, share of 11 families)

G01C (distance, navigation & gyroscopes) is named on 7 of the 11 families (63.6%) and G05D (control of non-electric variables) on 3 of the 11 (27.3%). Because a family can carry more than one IPC subclass, these shares add up to more than 100% and are not mutually exclusive.

Technology composition (IPC subclass, share of 11 families)G01C · Distance, navigation & gyrosco…763.6%G05D · Control of non-electric variab…327.3%A47L · Cleaning & washing appliances19.1%G01S · Radar, sonar & positioning19.1%G06F · Electric digital data processi…19.1%G06K · Data recognition & presentation19.1%

Shares are the percentage of the 11 patent families in scope. One patent family can carry several IPC classes, so the shares add up to more than 100%.

Source: Patsnap Eureka. Filing trend and technology composition. Derived from one Patsnap search for Visibility Graph Based Robot Path Planning Algorithm Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-20. Counts cover published records only and move as new filings publish.

Go deeper on Visibility Graph Based Robot Path Planning Algorithm Patent Landscape with Eureka

This page is one run against one query. Ask Eureka your own question about visibility graph based robot path planning algorithm patent landscape and every answer comes back with the patent numbers behind it.

Try Eureka
Record in focus

One record from the result set

First record returned, database default order
WO2020181729A12020-09-17

WO2020181729A1, distributed parallel-computing path planning method and system

JIANGSU MARITIME INSTITUTE

The abstract describes a mobile robot that reads laser sensor data on a timer, stores it locally, and packages it into messages sent to a cloud service. The cloud side pulls messages from a queue, groups the lidar data, builds an environment map and search interval in parallel for each group, and uses an improved A* approach to build a visibility graph and find a path in parallel before merging the result and returning it to the robot, which then moves toward the target point.Filed by Jiangsu Maritime Institute, dated 2020-09-17. This is the first record the search returns under the database's default ordering, not the most cited, newest or broadest filing in the set.

WO2020181729A1, patent drawing 1WO2020181729A1, patent drawing 2
View full record

Selected as the first record the search returns under the database default order, then shown in full. It is not ranked by citations, claim breadth or commercial importance, and it is not a judgement about which filing in this space matters most.

Source: Patsnap Eureka. The first record the search returned, shown in full. Derived from one Patsnap search for Visibility Graph Based Robot Path Planning Algorithm Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-20. Counts cover published records only and move 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 figures show

Three figures from the dataset, reported as counts rather than as a ranking of significance.

Scale
11 families / 16 records
simple patent families / published records

A small, de-duplicated result set

The search returns 11 simple patent families and 16 published records with no date limit applied. A family can publish as more than one record where it was filed in more than one office, which is why the record count is higher than the family count.

Counted across the full, unrestricted result set.
Filer spread
11 filers on 1 family each
of the 11 listed filers

No single filer ahead of the rest

Among the 11 listed filers, 11 hold 1 or 2 families each and the largest single row. The filer list excludes named individuals, who are still counted in the totals above, so the listed rows do not account for every family.

Rows are not summed; each share belongs to its own row only.
Classification
G01C: 63.6% of families
share of the 11 simple patent families

G01C carries the largest share of the IPC mix

G01C (distance, navigation & gyroscopes) is named on 7 of the 11 families (63.6%), and G05D (control of non-electric variables) on 3 of the 11 (27.3%). Families can carry more than one IPC subclass, so these two shares are not mutually exclusive and add to more than 100% together.

Shares are measured against the 11-family total, not against each other.
Filing locations
China: 8 of 16 records
published records by receiving office

Five receiving offices appear in the record set

Across the 16 published records, the receiving offices are: China (8), United States (3), WIPO/PCT (2), South Africa (2) and the EPO (1). This describes where applications were filed, not where any filer is located or incorporated.

Counted in published records; one invention can appear at more than one office.
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 visibility graph based robot path planning algorithm patent landscape, with the prior art for and against each one.

Find the white space →
Source: Patsnap Eureka. Derived observations on the same dataset. Derived from one Patsnap search for Visibility Graph Based Robot Path Planning Algorithm Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-20. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
Next steps

Where to take this next

This page reports counts. Turning a count into a filing or freedom-to-operate decision takes a closer read of the underlying claims.

Read the granted claims, not just the abstract

A family count or an abstract cannot establish what a patent covers. Pulling the granted claim set for any record named here is the only way to see what it actually requires.

Open Patsnap Eureka

Run a wider or adjacent search

11 families is a narrow result for a search string this specific. Varying the keywords or classification scope may surface related filings that this exact string did not catch.

Explore in Patsnap Eureka
Source: Patsnap Eureka. Suggested next steps. No new data: every figure named here is one of those above. Derived from one Patsnap search for Visibility Graph Based Robot Path Planning Algorithm Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-20. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
FAQ

Questions practitioners ask

Answers are grounded in the same dataset. Derived from one Patsnap search for Visibility Graph Based Robot Path Planning Algorithm Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-20. Counts cover published records only and move as new filings publish.Run this in Eureka MCP

Research Visibility Graph Based Robot Path Planning Algorithm Patent Landscape in depth with Eureka

Go past this page: query the whole visibility graph based robot path planning algorithm patent landscape corpus yourself, in your own scope.
Every answer comes back with patent numbers you can open.

Try Eureka
How this page was built, and what the numbers do and do not mean

Search. Every figure on this page comes from one Patsnap search, run once and not edited afterwards. This is the exact search string:

TAC:((robot* OR manipulator) AND "visibility graph" AND ("path planning" OR navigation))

Reading the field codes: TAC searches the title, abstract and claims of each record, not the full description. The search string sets no date limit, so the scope is every matching record in the database regardless of when it was filed. It is not restricted to recent years. How this string was built matters for how far the counts can be pushed. It was generated in batch from a topic list rather than hand-crafted for this page, and the result set is not manually screened. A keyword search over title, abstract and claims both over-captures (unrelated filings that happen to use the same words) and under-captures (the same invention written in different words). This page cannot measure either effect, so read every figure here as what this particular string returned, not as what exists in the field. One subclass (G01C) carries 63.6% of the patent families, so this search returned a classification-tight set.

What is being counted. Two different units appear on this page and they are not interchangeable. The filer list and the technology split are counted in simple (DOCDB) patent families: one invention counts once however many countries it was filed in. The total, the jurisdiction split and the filing-year chart are counted in published records: the same invention counts once per publication. For this search that is 16 records and 11 families. Record counts reward filing in many jurisdictions; family counts do not. Shares are only ever taken against a denominator in the same unit, and each one names it.

Who the filers are. Names come from Patsnap's standardised assignee field, as recorded on the documents themselves. They are not rolled up to corporate group: a parent and its subsidiaries appear as separate entries, and a portfolio acquired from another company stays under the name on the document unless the assignment is reflected there. This list is meant to carry organisations, not people. Filings held by a named individual are identified by matching the assignee against the inventors on the same search, and, for names written in Chinese, Japanese or Korean characters, by the name carrying no organisational suffix; those are removed from the list. Neither test is exhaustive: the inventor list it matches against is itself capped, and a personal name written in Latin script with no organisational wording in it cannot be told apart from a short company name by rule. So an individually held filing can still appear in the list. Those filings stay inside every total and share on this page either way, so the listed entries can add up to less than the total. A record shown in full further down still names its assignee exactly as the patent office records it, including where that is a person: that name is how the record is identified and checked. What is left out of the ranking is people as ranked entries, not people as cited sources. The table shows the top 11 of the 11 filers returned, ordered by count alone; the data endpoint returns at most 100 entities, so even that 11 is not every filer. One patent family can name several filers and each is counted separately, so these rows are not slices of a divided whole: adding them together over-counts, and this page deliberately publishes no combined "top five" share for that reason. See every filer, individuals included

Dates. The year chart counts by earliest filing year, not publication year. A filing only becomes visible once it publishes: roughly 18 months for most routes, and up to 30 months where a PCT application enters national phase. Measured across these pages, the year four back from today still holds only about 89% of its eventual count. 2022 onwards are therefore shaded on the chart as still filling in. The data behind this page was retrieved on 2026-10-20.

Legal status. "In force" counts documents whose legal status at retrieval was granted and maintained (6 of 16). Everything else is pending, withdrawn, refused, lapsed or not determinable, and those states are not broken out here because the underlying codes do not separate them cleanly. Legal status changes continuously and is reported per document, not per family. Get the status breakdown in Eureka

Classification. The technology split uses IPC subclasses (four characters, for example H01M). A single record usually carries several, so the shares add up to more than 100% and a record can appear in more than one bar. Subclass is a coarse grouping; it describes the field a record was classified into, not what the claims cover. Break the classes down to subgroup level

Who wrote the words. The tables, charts, counts, shares and patent numbers on this page are produced directly from the search result by a program; none of them are written or estimated by a language model. The surrounding prose, headings, FAQ answers and the answers in the question panel are drafted by a language model that is given those same figures and is not permitted to introduce others. Prose can still mis-describe a correct figure, so where the two disagree, the tables and charts are the record.

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 limitations that apply to every figure above. Recent filings are under-counted, because an application is not public until roughly 18 months after filing and database loading adds further delay. The search string defines and constrains everything shown: records that use different terminology, or that sit outside the fields searched, are absent and cannot be counted. Applicant names, classification codes, legal-status codes and citation records are taken as recorded and may contain errors, duplicates, omissions or stale entries. Ordering by volume is not a measure of quality, scope, enforceability or commercial value, and a larger portfolio is not a stronger one. 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, validity or infringement search, nor does it constitute legal, financial, investment, or professional advice, and it should not be relied upon as such. No attorney-client relationship is created by it. Any patent, commercial, or strategic decision should be verified independently against the primary records 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.

The question panel. The answers behind the suggested questions on this page were written when the page was generated, not in response to your click. The progress steps that play before an answer appears are an animation of how that analysis was done; nothing is being searched or computed at that moment. Typing your own question instead opens Patsnap Eureka, which does run it live.

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.