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 simple patent family and record cover cobot joint-current collision detection, filed in China via CN120735010A in 2025.
1 published records collapse into 1 simple (DOCDB) families; the difference is the same invention filed in more than one country.
This search combines cobot or collaborative robot language with joint-current or motor-current terms and collision- or contact-detection language. It returns one simple patent family and one published record: CN120735010A, filed in 2025 by Jiaxing Jingfeng Intelligent Technology Co., Ltd. and describing an integrated drive-and-control system for collaborative robots with a collision-detection module based on joint current rate-of-change and position-tracking error.
With only one family in scope, this page is a starting point for a search rather than a map of the field. A single document cannot establish a trend, a concentration pattern, or how crowded this specific technique is elsewhere; it simply shows what this search string, run today, returns.
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 describe the one record this search returns, broken out by filing year and IPC subclass.
The earliest-filing-year series shows 2025 = 1 and 2026 = 0 records. The window from 2022 onward is still filling in as later filings publish, so recent years understate eventual totals; a single data point here cannot show acceleration, deceleration or maturity.
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.
The one family in scope carries both B25J (Manipulators & robots) and G05B (Control & regulating systems), each at 100.0% of the one simple patent family. Because a single record can carry multiple classes, these two shares both reach 100% rather than splitting between them.
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 collaborative robot joint current based collision detection algorithm patent landscape and every answer comes back with the patent numbers behind it.
Try EurekaThe abstract describes an integrated drive-and-control system for collaborative robots: an integrated main controller running a real-time multitask operating system, distributed drive units connected over a high-speed bus (each with a power conversion circuit, a current-loop closed control module and a motor-state detection interface), a safety coordination bus using a time-sensitive networking protocol, and a dynamic collision-detection module integrated in the main controller that generates a safety response by fusing the rate of change of joint current with position-tracking error.This is the first record returned by the database's default ordering, not the most cited, newest or broadest filing in the set.
View full record in EurekaSelected 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 everything this search currently returns.
The search returns one simple patent family and one published record, CN120735010A, filed in 2025. No date limit was applied, so this is every matching record regardless of filing date, not a window bounded to recent years.
Jiaxing Jingfeng Intelligent Technology Co., Ltd. is named on 1 of the 1 simple patent families in scope (100.0%). The listed-filer table excludes individual inventors, who remain inside the total count, so this single row does not represent every name behind the one family.
The family carries both B25J (Manipulators & robots) and G05B (Control & regulating systems), each at 100.0% of the one simple patent family in scope. Both reach 100% because a single record can carry more than one classification.
The search returned exactly one receiving office across its one published record: China. 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 collaborative robot joint current based collision detection algorithm patent landscape, with the prior art for and against each one.
A one-family result is a narrow signal. These are ways to broaden or verify it.
Joint-current and motor-current collision detection may be described with other phrasing elsewhere in the corpus, torque sensing, current-spike detection, safety stop logic. Broadening the string is likely to surface more than one family.
Explore broader queries in Eureka →An abstract describes what a filing discusses, not what its claims legally cover. Reading the granted claim set of CN120735010A directly is the only way to understand its actual scope.
Open the full record in Eureka →The 2026 figure of zero records reflects publication lag rather than an absence of filing activity, since filings from the last couple of years are still publishing.
Set up monitoring in Eureka →This specific search string, combining cobot or collaborative-robot language with joint-current or motor-current terms and collision- or contact-detection language, returns one simple patent family and one published record as of the retrieval date. That does not mean only one patent exists on this technique anywhere; it means this exact combination of search terms, run against this database, surfaced one matching document. Related filings may use different terminology (torque sensing, current-spike detection, force estimation) and would not appear under this string. Treat this as a starting point for a broader search rather than a complete count.
The one simple patent family in scope is held by Jiaxing Jingfeng Intelligent Technology Co., Ltd., named on 100.0% of the one family returned. The listed-filer table excludes individual inventors, who are still counted inside the overall total, so this single organisation row is the only named entity visible in the filer list. No nationality or regional affiliation can be read from this data; the only location information available is that the record was filed in China, which describes the receiving office, not the filer's origin.
The abstract for CN120735010A describes an integrated drive-and-control system for collaborative robots, including a real-time multitask main controller, distributed drive units linked over a high-speed bus, a time-sensitive-networking safety bus, and a dynamic collision-detection module that fuses the rate of change of joint current with position-tracking error to generate a safety response. An abstract summarises the disclosure; it does not state what the granted claims legally require or how far they reach. Anyone assessing freedom to operate or infringement risk needs to read the granted claim set directly rather than rely on the abstract or the family count.
The filing-trend data shows one published record with an earliest filing year of 2025 and zero in 2026. A series this short cannot support a conclusion about growth, decline, or maturity; it is also affected by publication lag, since filings from 2022 onward are typically still filling in as later applications publish. No growth rate is calculable or shown on this page because the dataset is too thin to produce a percentage.
No. A small result count from one search string most often means the terminology used did not match how other filers phrased similar inventions, not that the underlying technique is unclaimed. Collision detection based on motor or joint current is a known approach described in broader robotics and control literature, and filings covering it may simply use different vocabulary than this search string captures. Confirming whether a particular design is open requires broader searching and a claims-level review, not an inference from one dataset.
Go past this page: query the whole collaborative robot joint current based collision detection algorithm 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:((cobot OR "collaborative robot*") AND ("joint current" OR "motor current") AND ("collision detection" OR "contact detection"))
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 (B25J) 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-20.
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.
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