https://eureka.patsnap.com/resources/blog/rd-blog/database-cardinality-estimation-using-machine-learning-models-patent-landscape/ · Patsnap · data cut-off 2026-10-15 · downloaded from the live page
Patent Landscape · Database Technologies

Database Cardinality Estimation Using Machine Learning: Patent Snapshot

21 patent families on ML-based database cardinality estimation, led by IBM with 4 families, mapped across filers, IPC classes and receiving offices.

40
Published Records
21
Simple Patent Families
63%
In Force at Cut-off
US
Leading Jurisdiction

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

  • 21 simple patent families sit behind 40 published records on machine-learning approaches to database cardinality estimation.
  • International Business Machine Corporation holds the largest single share named on 4 of the 21 families (19.0%), with 19 of the 20 listed filers holding 2 or fewer families each.
  • 25 of 40 records (63%) were granted and still in force at the 2026-10-15 retrieval date.
Check your own idea
Published byPatsnap Research··6 min readSourced from Patsnap Eureka
Overview

What this dataset covers

This dataset gathers records whose title, abstract or claims combine database or query optimizer language with cardinality estimation and a machine-learning term such as neural network or learned model. It spans 21 simple patent families and 40 published records, with no date limit applied to the search string itself. The filing-trend chart shown further down covers a recent window only and should not be read as the full span of activity.

21 families is a small pool. The figures below describe what this particular search returned, who filed, which IPC classes recur, where records were filed, and should be read as a starting point for further search rather than a complete map of the field.

Records vs. families in scope
  1. INTERNATIONAL BUSINESS MACHINE CORPORATION4
  2. WUHAN UNIV2
  3. GOOGLE LLC2
  4. UNIV OF ELECTRONICS SCI & TECH OF CHINA2
  5. NORTHEASTERN UNIV CHINA1
  6. TRANSWARP TECHNOLOGY (SHANGHAI) CO LTD1
  7. YANGTZE RIVER DELTA RES INST OF NPU TAICANG1
  8. SAP SE1
  9. IBM CN1
  10. ORACLE INT CORP1

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 20 of the 20 filers returned for this search; the data endpoint returns at most 100 entities, so even that 20 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 Database Cardinality Estimation Using Machine Learning Models Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-15. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
The Numbers

Filing activity and technology split

Three views of the same 21-family pool: how records have published over time, which IPC subclasses recur, and where applications were filed.

Published records by earliest filing year

Records run from a single filing in 2015 up to a peak of 12 in 2024. 2022 onward is still filling in: recent years understate eventual totals because of publication lag, so no slowdown or acceleration should be read from the most recent bars.

Published records by earliest filing year03691212015201620172018201920202021202220231220242025020262022 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.

IPC subclass composition

G06F (electric digital data processing) appears on all 21 families in scope; G06N (computing based on AI models) appears on 11 of the 21 (52.4%). Because a family can carry both classes, these shares add up to more than 100% and are not mutually exclusive groupings.

IPC subclass compositionG06F · Electric digital data processi…21100.0%G06N · Computing based on AI models1152.4%G06K · Data recognition & presentation14.8%

Shares are the percentage of the 21 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 Database Cardinality Estimation Using Machine Learning Models Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-15. Counts cover published records only and move as new filings publish.

Go deeper on Database Cardinality Estimation Using Machine Learning Models Patent Landscape with Eureka

This page is one run against one query. Ask Eureka your own question about database cardinality estimation using machine learning models patent landscape and every answer comes back with the patent numbers behind it.

Try Eureka
Spotlight Record

A record from this result set

From the result set
US20240045871A12024-02-08

Cardinality estimation method and device for skyline query based on deep learning

ZHEJIANG UNIVERSITY

The abstract describes parsing historical query log information to build a training set, constructing data distribution learning models from that set, using the trained model's parameters to initialise a cardinality estimation model, and then training that model to produce cardinality estimates from input query points for Skyline queries.Returned first under this search's default ordering, not as the most cited, newest or broadest record. It should not be read as typical of the other 20 families in scope.

US20240045871A1, patent drawing 1US20240045871A1, 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 Database Cardinality Estimation Using Machine Learning Models Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-15. 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 →
Patterns In The Data

What the figures show

Three figures worth sitting with before treating this dataset as more than a starting point.

Filer concentration
4 of 21 families
largest single filer share

International Business Machine Corporation named on 4 of 21 families

International Business Machine Corporation is named on 4 of the 21 simple patent families in scope, a 19.0% share. 19 of the 20 listed filers hold 2 or fewer families each. Filer rows are not rolled up to corporate group and can overlap (one family can name several filers), so this single-row figure is the only share that can be quoted here.

Filer list, 20 entities, counted in simple patent families
Legal status
25 of 40
records granted and in force

63% of records were granted and in force at retrieval

25 of the 40 published records (63%) were granted and still in force as of the 2026-10-15 retrieval date. The remaining records are pending, withdrawn, refused, lapsed or not determinable, and that breakdown is not available here. In-force status is a snapshot at one date, not a measure of claim strength or commercial value.

Legal status at retrieval, counted in published records
Technology composition
100% / 52.4%
G06F / G06N family share

G06F appears on every family; G06N on just over half

G06F (electric digital data processing) is present on all 21 families in scope. G06N (computing based on AI models) is present on 11 of the 21 (52.4%). These shares add up to more than 100% because a family can carry both classes at once, so the two figures describe overlapping groups, not a partition.

IPC subclass tagging, counted in simple patent families
Filing offices
21 US / 11 CN
records by receiving office

Records were filed across six offices, led by the United States

Across the 40 published records, the United States received 21, China 11, the EPO 4, WIPO (PCT) 2, and Austria and Germany 1 each. These figures count where an application was filed, not where any filer is based, and the dataset provides no nationality information for any filer.

Receiving office, counted in published records (sums to the record total)
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 database cardinality estimation using machine learning models 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 Database Cardinality Estimation Using Machine Learning Models Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-15. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
Where To Go From Here

Next steps for a deeper read

This page surfaces a small, specific slice of filings. Turning it into a working view of freedom-to-operate or white space takes a closer read of individual records.

Pull the granted claims

A family count or an abstract cannot establish what a granted claim covers. Before concluding anything about scope, read the claim set of any record that looks relevant.

Explore records in Eureka

Check legal status per record

63% of records are shown as granted and in force at retrieval, but that status changes continuously and is not broken out by filer here. Verify status on the specific records that matter to you.

Check status in Eureka

Widen or narrow the search string

With 21 families, this result is sensitive to the exact terms used. Adjusting the search string can surface adjacent filings that this particular combination of terms missed.

Refine the search in 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 Database Cardinality Estimation Using Machine Learning Models Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-15. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
FAQ

Common questions

Answers are grounded in the same dataset. Derived from one Patsnap search for Database Cardinality Estimation Using Machine Learning Models Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-15. Counts cover published records only and move as new filings publish.Run this in Eureka MCP

Research Database Cardinality Estimation Using Machine Learning Models Patent Landscape in depth with Eureka

Go past this page: query the whole database cardinality estimation using machine learning models 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:(("database" OR "query optimizer") AND ("cardinality estimation") AND ("machine learning" OR "neural network" OR "learned model"))

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 40 records and 21 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 20 of the 20 filers returned, ordered by count alone; the data endpoint returns at most 100 entities, so even that 20 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-15.

Legal status. "In force" counts documents whose legal status at retrieval was granted and maintained (25 of 40). 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.