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 →A single-family dataset on haptic rendering algorithms for virtual object stiffness, with the filer, IPC split and filing record it contains.
1 published records collapse into 1 simple (DOCDB) families; the difference is the same invention filed in more than one country.
This search looks for records whose title, abstract or claims combine haptic rendering and algorithm with stiffness and either virtual object or simulation. It returns 1 simple patent family and 1 published record, filed with the United States receiving office. The search sets no date limit, so this is every matching record the query found, not a slice bounded by a start year.
With a single family in scope, this page is a starting point for a more targeted search rather than a map of the field. A pool this small cannot support a concentration reading, a trend reading, or a white-space claim; the numbers here describe exactly what the search string returned, nothing more.
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: a filing-trend series counted in published records, and an IPC breakdown counted in simple patent families.
The one published record in this set carries an earliest filing year of 2024, the peak year so far at a count of 1. The chart's window from 2022 onward is still filling in as later filings publish, so no rise, fall or plateau can be read from it; the series simply counts documents, not inventions, and one invention can appear more than once if filed in several countries.
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.
G06F (Electric digital data processing) and G06T (Image data processing & generation) each appear on the single family in scope, 100.0% of the 1 simple patent family. Because a record can carry more than one IPC class, these two shares add to more than 100%, that is expected, not an error.
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 haptic rendering algorithm for virtual object stiffness simulation patent landscape and every answer comes back with the patent numbers behind it.
Try EurekaThe abstract describes a haptic rendering method using multiple virtual coupling systems with energy consistency, applied to human-computer interaction in virtual reality. It covers six-degree-of-freedom force synthesis for operations such as pressing and inserting during large-deformation contact between a tool and a soft body, with each simulated object split into a graphical part and a physical part linked through virtual coupling.This is simply the first record the search returns under the database's default order, not the most cited, newest or broadest filing. Its number, assignee and filing date are shown separately on the page.


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 summarise the result set: the scale of the pool, the one listed filer, and the IPC split. None of them supports a conclusion about the wider field.
The search returns 1 simple patent family and 1 published record with no date limit applied. That is the entire set returned by this query string, not a filtered subset of a larger field.
Beihang University is named on 1 of the 1 simple patent family in scope, a 100.0% share of this single-row result. The filer list excludes individual inventors, who are still counted in the total but do not appear as named rows.
G06F (electric digital data processing) and G06T (image data processing & generation) are each attached to the single family in scope, 100.0% apiece of the 1 family. The shares add to more than 100% because one record can carry both classes.
The one published record in this set was filed with the United States receiving office, the only office the search returned. This describes where the application was filed, not where the filer is based.
Eureka can read the same corpus for gaps instead of for coverage: under-claimed branches adjacent to haptic rendering algorithm for virtual object stiffness simulation patent landscape, with the prior art for and against each one.
A one-family result is a narrow window. These paths widen or sharpen the search before drawing further conclusions.
Synonyms for haptic rendering, stiffness modeling and virtual coupling may surface related families this exact string misses.
Refine the search in Eureka →The one record shown here is described only by its abstract. Reading the granted claim set is the only way to know what it actually covers.
Open the full record in Eureka →The chart on the page shows every subclass the search touched, including ones not discussed in this text. Reviewing them directly may reveal related filings.
Explore IPC coverage in Eureka →This search returns 1 simple patent family and 1 published record, with no date limit applied to the query. That means the result reflects every record this specific search string matched at the time of retrieval, not a count bounded to a particular year range. A different phrasing of the search terms could return a different number, since the result depends on exactly which words and fields the string matches.
Beihang University is named on the 1 simple patent family in this result, a 100.0% share of the single row returned. The filer list excludes individual inventors, who remain counted in the total but are not shown as named organisation rows. With only one family in scope, this single result cannot be read as evidence of a position across a wider field.
Its abstract describes a haptic rendering method using multiple virtual coupling systems with energy consistency, applied to six-degree-of-freedom force synthesis during large-deformation contact between a tool and a soft body in virtual reality. An abstract summarises the invention in prose; it is not the claim set, which is the only part of the document that defines legal scope. Anyone assessing what the patent covers, or whether a given design falls inside or outside it, needs to read the granted claims directly rather than infer scope from the abstract or from the fact that it is one of only 1 family on this topic.
In this dataset, the single family in scope carries two IPC subclasses: G06F (electric digital data processing) and G06T (image data processing & generation), each on 100.0% of the 1 family. These two classes are the only ones with enough presence in this result to characterise; other subclasses the search touched are shown on the page's chart but are not discussed here because the pool is too thin to say anything reliable about them.
No growth rate is shown on this page. The filing-trend series counts just one published record, with an earliest filing year of 2024, which is too thin a dataset to read a trend, acceleration or slowdown from. Readers should also note that recent filing years are understated in any patent dataset because of publication lag, typically 18 months and up to 30 months for applications entering national phase via PCT.
Go past this page: query the whole haptic rendering algorithm for virtual object stiffness simulation 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:(("haptic rendering" AND algorithm) AND stiffness AND ("virtual object" OR simulation))
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 (G06F) 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. Legal status was not available for this search, so no in-force figure is shown. 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.
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