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 →One granted family covers RGB-D and laser line-feature localization.
1 published records collapse into 1 simple (DOCDB) families; the difference is the same invention filed in more than one country. In force = 1 of 1 records still granted and maintained at the data cut-off; the rest are pending, withdrawn, refused or lapsed.
This dataset is built from a search string combining line or edge feature matching with visual localization or relocalization and spatial computing or SLAM terminology. It returns one simple patent family, published as one record, filed at the China receiving office and currently granted and in force. The family carries IPC subclasses G01C (distance, navigation & gyroscopes) and G01S (radar, sonar & positioning), both at 100% of the single family in scope.
With only one family in scope, this page is a starting point for a more targeted search rather than a map of the field. A single record cannot establish who else is filing in this space, how concentrated it is, or where the open ground sits; broadening the search string or date range is the next step before drawing any conclusion from these figures.
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 1 of the 1 filers returned for this search; the data endpoint returns at most 100 entities, so even that 1 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.
The figures below are drawn directly from the search result: one published record, one simple patent family, tagged with two IPC subclasses.
Earliest filing year series runs from 2018, where the single published record in this set sits, through 2026 at zero. The window from 2022 onward is still filling in because of publication lag, so no slowdown or acceleration can be read from this trend. The trend counts published documents, not inventions, so it cannot distinguish one invention filed widely from several distinct ones.
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.
G01C and G01S each cover 100.0% of the 1 simple patent family in scope, because the single family in this dataset carries both classifications. Shares are read against the family total and are expected to add to more than 100% when a record carries more than one class.
Shares are the percentage of the 1 patent families in scope. One patent family can carry several IPC classes, so the shares add up to more than 100%.
This page is one run against one query. Ask Eureka your own question about spatial computing visual localization using line feature matching patent landscape and every answer comes back with the patent numbers behind it.
Try EurekaThe abstract describes a combined localization method using RGB-D visual data for motion estimation via line feature matching, alongside a laser-based EKF-SLAM method for motion estimation. When both algorithms succeed at the same timestamp, the system produces two pose estimates and combines them through filtering for an optimal estimate; when visual localization fails, for example under low-texture conditions, the laser-derived pose is used as the global filter's optimal pose.This is the first record returned by the database's default ordering, not the most cited, newest or broadest filing in scope. It should not be read as representative of the dataset.


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.
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 →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 →Three figures summarize the scope of this search result. Each is reported as counted, with its unit and denominator stated.
The search returns 1 simple patent family, published as 1 record, with no date limit applied to the search string. This is too small a pool to characterize a field or a trend from.
1 of the 1 published records carried granted, in-force status when this data was retrieved on 2026-10-16. The remaining status categories (pending, withdrawn, refused, lapsed) are not broken out for this record set.
The listed filer is named on 1 of the 1 simple patent families in scope (100.0%), the only share this page can quote for a single row. The filer list excludes individual inventors, who remain inside the total and are not shown as separate rows here.
Both G01C (distance, navigation & gyroscopes) and G01S (radar, sonar & positioning) are attached to the single family in scope, each reaching 100.0% of the 1-family denominator. The two shares add to more than 100% because one family can carry both classes.
Eureka can read the same corpus for gaps instead of for coverage: under-claimed branches adjacent to spatial computing visual localization using line feature matching patent landscape, with the prior art for and against each one.
A one-family result is a narrow slice of a broader search space. These next steps widen the lens before any conclusion about filers or technology trends is drawn.
Line and edge feature matching are two of several visual localization approaches; adjacent terms such as feature point matching or keyframe-based relocalization may surface families this string did not catch.
Explore related search terms in Patsnap EurekaG01C and G01S cover navigation and positioning broadly. Reviewing adjacent IPC subclasses directly, rather than relying on this search string, can confirm whether other relevant filings sit just outside this result set.
Review IPC subclass coverage in Patsnap EurekaA family count and an abstract describe what a filing discusses, not what its claims legally cover. Reading CN109633664A's granted claim set directly is the only way to establish its actual scope.
Open the full record in Patsnap EurekaThis particular search string returns exactly 1 simple patent family, published as 1 record, with no date restriction applied. That does not mean only one invention has ever combined line feature matching with visual localization or SLAM; it means only one matched this specific combination of search terms in the database searched. A broader or differently worded search string could return a different count, so this figure should be read as a property of the search, not a census of the technology.
The single listed organisational filer is named on 1 of the 1 simple patent families in scope, a 100.0% share of this one-family set. The filer list in this dataset excludes individual inventors, who remain counted in the overall total even though they do not appear as separate rows. No nationality or country of origin can be inferred for this filer from the data available here; only the receiving office, China, is known, and that reflects where the application was filed, not who filed it.
Its abstract describes a combined localization method that pairs RGB-D visual localization, using line feature matching for motion estimation, with a laser-based EKF-SLAM method. When both methods succeed at the same moment the system fuses the two pose estimates through filtering; when visual localization fails, for example under low-texture conditions, the laser-derived pose is used instead. What its granted claims actually require, and how far they reach, can only be established by reading the claim set itself, not from this abstract or from the family count.
No. The search string used here is narrow, combining line or edge feature matching with visual localization or relocalization and spatial computing or SLAM terminology, and it returns one family. Relevant filings using different terminology, such as feature point matching or keyframe-based relocalization, would not be captured by this exact string. This page is best treated as a starting point for a broader search rather than a complete landscape of the underlying technology.
The single family in scope carries two IPC subclasses: G01C, covering distance, navigation and gyroscopes, and G01S, covering radar, sonar and positioning equipment. Both reach 100.0% of the 1-family denominator because the one family in this dataset is tagged with both classes simultaneously. These two shares sum to more than 100% by design, since IPC shares in this dataset are measured against the family total rather than partitioned across classes.
At the retrieval date of 2026-10-16, the single record in this dataset was granted and in force, a 100% figure against the 1 record in scope. Legal status reflects a snapshot at that specific date and changes continuously as renewal fees are paid, patents lapse, or other status events occur. In-force status says nothing about the breadth of what the patent's claims cover or whether it would affect any particular product or design.
Go past this page: query the whole spatial computing visual localization using line feature matching patent landscape corpus yourself, in your own scope.
Every answer comes back with patent numbers you can open.
Search. Every figure on this page comes from one Patsnap search, run once and not edited afterwards. This is the exact search string:
TAC:(("line feature matching" OR "edge feature matching") AND ("visual localization" OR relocalization) AND ("spatial computing" OR SLAM))
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 100.0% 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 1 records and 1 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 1 of the 1 filers returned, ordered by count alone; the data endpoint returns at most 100 entities, so even that 1 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-16.
Legal status. "In force" counts documents whose legal status at retrieval was granted and maintained (1 of 1). 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.
This page