https://eureka.patsnap.com/resources/blog/rd-blog/database-adaptive-runtime-join-algorithm-selection-patent-landscape/ · Patsnap · data cut-off 2026-10-15 · downloaded from the live page
Patent Landscape · 2026

Database Adaptive Runtime Join Algorithm Selection Patents

Six simple patent families and 10 published records cover adaptive runtime join algorithm selection, with no single filer ahead of the rest.

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

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

  • Six filers share the top spot. Each is named on 1 of the 6 simple patent families in scope, so no single filer in this dataset holds more than the others.
  • Small pool. The search returned 6 simple patent families from 10 published records, with no date limit applied to the search string.
  • G06F covers most of the set. 5 of the 6 simple patent families (83.3%) carry a G06F classification, the electric digital data processing subclass.
Check your own idea
Published byPatsnap Research··6 min readSourced from Patsnap Eureka
Overview

What this dataset covers

This page reports results for the search string TAC:(("database" OR "query execution") AND ("join algorithm") AND (adapt* OR runtime OR dynamic*)), which returned 10 published records that de-duplicate to 6 simple patent families. The search string carries no date limit, so the records span whatever filing years the matching text happens to fall in rather than a chosen window. 4 of the 10 records (40%) were granted and in force at the 2026-10-15 retrieval date; the rest are pending, withdrawn, refused, lapsed or not determinable, and that breakdown is not separated out further here.

At 6 simple patent families, this is a small pool. The numbers below describe what the search returned, not the shape of a field, treat this page as a starting point for a closer search rather than a map of who files in this space.

Records vs. families in scope
  1. OPENDR LLC1
  2. WELLS FARGO BANK NA1
  3. SOFTBANK GROUP CORP1
  4. INTERNATIONAL BUSINESS MACHINE CORPORATION1
  5. 10353744 CANADA LTD1
  6. INFOSYS LTD1

Counted over all 10 published records, including filings from before 2009; the filing-trend chart below covers only the 6 records from 2009 onward, so the two charts are not the same set of documents. 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 6 of the 6 filers returned for this search; the data endpoint returns at most 100 entities, so even that 6 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 Adaptive Runtime Join Algorithm Selection 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

Let an AI agent run this analysis on your own technology

Pick a task. Every answer cites the patents behind it.

10,000 free credits to start
The numbers

Filing volume and technology split

Figures below are counted in the unit stated next to each one, published records and simple patent families are not interchangeable here.

Filing trend by earliest filing year (published records) (6 of 10 published records)

The earliest record in this trend is filed in 2009 and the series runs through 2026, with 2023 the peak so far at 2 published records. Records from 2022 onward are still filling in as later filings publish, so the right edge of the chart understates the eventual count rather than showing a drop-off.

Filing trend by earliest filing year (published records) (6 of 10 published records)011221200920112013201520172019202122023202512022 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. This chart covers 2009-2026 (6 records); the 10 total quoted above includes earlier filings outside the window.

IPC subclass composition (share of 6 simple patent families)

G06F (electric digital data processing) appears on 5 of the 6 simple patent families (83.3%), the highest share of any subclass here. G06N (computing based on AI models), G06Q (business, commerce & admin data processing) and H04L (digital information transmission) each appear on 1 of the 6 families (16.7%). Because a family can carry more than one classification, these shares add up to more than 100% and are not a partition of the set.

IPC subclass composition (share of 6 simple patent families)G06F · Electric digital data processi…583.3%G06N · Computing based on AI models116.7%G06Q · Business, commerce & admin dat…116.7%H04L · Digital information transmissi…116.7%

Shares are the percentage of the 6 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 Adaptive Runtime Join Algorithm Selection 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 Adaptive Runtime Join Algorithm Selection Patent Landscape with Eureka

This page is one run against one query. Ask Eureka your own question about database adaptive runtime join algorithm selection patent landscape and every answer comes back with the patent numbers behind it.

Try Eureka
Record on file

A record from the result set

First record returned
CA3143821C2026-08-25

CA3143821C, Data query method and device, computer equipment and storage medium

10353744 CANADA LTD.

The abstract describes a data query method that analyzes a query request to obtain a join algorithm and a corresponding scenario. For full outer join, left outer join or right outer join scenarios where summary values in one datasheet are sequenced and the other are not, the method performs summarizing, sequencing and a limit operation in the database holding the first datasheet to produce a first result set, then uses dimension values from that result set as a dynamic filtering condition for further processing.Filed by 10353744 Canada Ltd., dated 2026-08-25. Shown as the first record returned by the search's default ordering, not as the most cited, newest or broadest filing in scope.

View 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 Adaptive Runtime Join Algorithm Selection 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 →
Signals in the data

What the figures show

Three readings from the dataset, each tied to the unit it was counted in.

Filer concentration
1 of 6 families
largest single-row share

Six filers tied at 1 family each

OPENDR LLC, Wells Fargo Bank NA, SoftBank Group Corp, International Business Machine Corporation, 10353744 Canada Ltd. and Infosys Ltd. are each named on 1 of the 6 simple patent families in scope (16.7%). No filer in the listed set is named on more than one family, so none ranks above the others.

Filer rows, simple patent families
Technology split
83.3%
families carrying G06F

G06F appears on 5 of 6 families

G06F (electric digital data processing) is the classification with the highest share among the four discussed here, appearing on 5 of the 6 simple patent families. G06N, G06Q and H04L each appear on 1 family. Shares add up to more than 100% because a family can carry several classifications.

IPC subclasses, simple patent families
Legal status
4 of 10
records granted and in force

40% of records are in force at retrieval

4 of the 10 published records were granted and in force on 2026-10-15. The remainder fall into pending, withdrawn, refused, lapsed or not-determinable states that are not broken out individually in this dataset. In-force status is a snapshot at the retrieval date and will change over time.

Published records, legal status at retrieval
Filing geography
3 offices
receiving offices returned

Records filed across three receiving offices

Counted by published record, filings went to the United States (6), Europe/EPO (3) and Canada (1), summing to the 10-record total since one invention can file at more than one office. This reflects where applications were filed, not where any filer is based.

Receiving offices, published records
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 adaptive runtime join algorithm selection 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 Adaptive Runtime Join Algorithm Selection 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
Next steps

Where to take this further

This page is a first look drawn from a small, text-matched pool. The following moves narrow or widen the picture before anyone relies on it.

Pull the granted claims

An abstract and a family count describe what a filing discusses, not what its claims require. Reading CA3143821C or any other record in scope means opening the granted claim set directly.

Open Eureka to read claims

Widen or vary the search string

With only 6 simple patent families returned, adjacent phrasing for join selection, query optimisation or runtime plan adaptation may sit outside this exact string and change the picture.

Rebuild the search in Eureka

Track legal status changes

4 of 10 records were in force at the 2026-10-15 retrieval date; status changes continuously as applications prosecute, lapse or get challenged.

Monitor status 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 Adaptive Runtime Join Algorithm Selection 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

Questions about this dataset

Answers are grounded in the same dataset. Derived from one Patsnap search for Database Adaptive Runtime Join Algorithm Selection 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 Adaptive Runtime Join Algorithm Selection Patent Landscape in depth with Eureka

Go past this page: query the whole database adaptive runtime join algorithm selection 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 execution") AND ("join algorithm") AND (adapt* OR runtime OR dynamic*))

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 83.3% 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 10 records and 6 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 6 of the 6 filers returned, ordered by count alone; the data endpoint returns at most 100 entities, so even that 6 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 (4 of 10). 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.