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 →24 families and 91 records on MWPM/surface-code decoders, with Google LLC naming most families and a long tail of single-filing entities.
91 published records collapse into 24 simple (DOCDB) families; the difference is the same invention filed in more than one country. In force = 45 of 91 records still granted and maintained at the data cut-off; the rest are pending, withdrawn, refused or lapsed.
This landscape gathers records matching "minimum weight perfect matching" OR "MWPM decoder" combined with "surface code" OR "quantum error correction" in title/abstract/claims text. The search returns 91 published records, which de-duplicate to 24 simple patent families once filings for the same invention across different offices are merged. No filing-date restriction was applied to the search string itself; the filing-trend chart below shows a recent window only, not the full span of records in scope.
At 24 families, this is a small pool. The figures below describe what this particular search returned, not the shape of a wider field, and the page is best read as a starting point for further search rather than a finished map.
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 (11 here); 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 12 of the 12 filers returned for this search; the data endpoint returns at most 100 entities, so even that 12 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.
Pick a task. Every answer cites the patents behind it.
The two views below use different units, published records for the filing trend and receiving offices, simple patent families for the technology composition, and the two should not be combined.
Records climb from 18 in 2017 to a peak of 34 in 2024 before falling off toward 2026. The years from 2022 onward are still filling in: publication can lag filing by 18-30 months, so the most recent years understate their eventual counts and should not be read as a slowdown.
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.
G06N, covering computing based on AI models, appears on 21 of the 24 families (87.5%). Because a family can carry more than one IPC class, this and the other shares shown on the chart add up to more than 100%.
Shares are the percentage of the 24 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 minimum weight perfect matching decoder for surface code error correction patent landscape and every answer comes back with the patent numbers behind it.
Try EurekaThe abstract describes a quantum error correction method that corrects a stream of syndrome measurements from a quantum computer. It uses a layered representation of error propagation through quantum error detection circuits, where each layer represents the probability of local detection events tied to potential error processes during execution of a quantum algorithm. During execution, syndrome measurements are converted into detection events written to an array.This is simply the first record returned under the database's default ordering, not the most cited, newest or broadest filing in scope. It should not be read as typical of the wider set.


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 →Four figures from the search results, reported without added interpretation.
Google LLC appears on 7 of the 24 simple patent families in scope, a 29.2% share. This is a count of named families, not a measure of claim scope or commercial position, and filer rows are not rolled up to corporate group.
Of the 12 listed filers, 10 hold 2 or fewer simple patent families each. The listed filers are organisations only; individual-named filers are excluded from this list but remain inside the 24-family total.
The IPC subclass G06N, covering computing based on AI models, is recorded on 21 of the 24 simple patent families (87.5%). Other subclasses shown on the chart sit well below this share.
At retrieval, 45 of the 91 published records (49%) were granted and still in force. The remaining records are pending, withdrawn, refused, lapsed or not determinable, and this breakdown is not split out further on this page.
Eureka can read the same corpus for gaps instead of for coverage: under-claimed branches adjacent to minimum weight perfect matching decoder for surface code error correction patent landscape, with the prior art for and against each one.
This page is a starting point built from one search string; these are ways to extend it.
A family count or an abstract cannot establish what any single patent blocks. The next step for a freedom-to-operate question is reading the granted claim set of the specific record in question.
Explore in Patsnap Eureka →With only 24 families in scope, adjacent phrasing of decoder and error-correction terms may surface records this exact string missed.
Run a new search in Patsnap Eureka →This search returns 91 published records, which de-duplicate to 24 simple patent families once different filings of the same invention across offices are merged. There is no date limit on the underlying search string, so this figure reflects every matching record the database holds, not a particular year range. Because the search is built on specific keyword phrases, it should be read as one slice of the topic rather than an exhaustive count of every related filing.
Google LLC is named on 7 of the 24 simple patent families in scope, the highest share of any listed filer at 29.2%. Ten of the 12 listed filers hold 2 or fewer families each, so beyond the single largest row the filings are spread thinly. Filer rows are not rolled up to corporate group, and the listed filers are organisations only, with individually named inventors excluded from the list but still counted in the 24-family total.
Published records counted by earliest filing year rise from 18 in 2017 to a peak of 34 in 2024, with a drop-off visible toward 2026. Records from 2022 onward are still filling in, since publication can lag filing by 18 to 30 months, so the most recent years understate their eventual totals. This trend counts published documents rather than distinct inventions, and the same invention filed in multiple countries adds multiple marks to the line.
The IPC subclass G06N, covering computing based on AI models, is recorded on 21 of the 24 simple patent families in scope (87.5%). Because a single family can carry more than one IPC classification, the shares across all subclasses on the chart add up to more than 100%. This dataset is limited to 24 families, which is too small a pool to characterise as a technology field in a broader sense.
No. The filer table shows only the 12 entities the search endpoint returned for this specific string, and the data endpoint caps at 100 entities regardless of topic, so this is not a complete filer list. The search string itself targets specific phrases, so records using different terminology for the same underlying decoding approach may fall outside this set. Treat the page as a starting point for further search rather than a finished map of the area.
Go past this page: query the whole minimum weight perfect matching decoder for surface code error correction 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:(("minimum weight perfect matching" OR "MWPM decoder") AND ("surface code" OR "quantum error correction"))
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 (G06N) carries 87.5% 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 91 records and 24 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 (11 of them here). 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 12 of the 12 filers returned, ordered by count alone; the data endpoint returns at most 100 entities, so even that 12 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 (45 of 91). 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.
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