https://eureka.patsnap.com/resources/blog/rd-blog/stream-processing-gpu-accelerated-operator-execution-patent-landscape/ · Patsnap · data cut-off 2026-10-21 · downloaded from the live page
Patent Landscape · Updated 2026

Stream Processing GPU-Accelerated Operator Execution Patents

A 73-family dataset on GPU-accelerated stream processing operators, led by a single filer with 8.2% share and a long tail of small filers.

155
Published Records
73
Simple Patent Families
50%
In Force at Cut-off
US
Leading Jurisdiction

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

  • 73 simple patent families and 155 published records make up this dataset, with no date limit applied to the search.
  • VIA Tech Inc holds the largest single share named on 6 of 73 simple patent families (8.2%), ahead of every other listed filer.
  • 60 of 65 listed filers hold 2 or fewer simple patent families each, the long tail of this filer list.
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:(("stream processing" OR "stream processor") AND (GPU OR "graphics processing unit") AND (operator OR execut*)), which returned 155 published records collapsing to 73 simple patent families. No date limit was applied, so the set spans whatever filing dates the matching records happen to carry; the filing-trend chart below shows a recent window only, not the full history. At retrieval, 78 of the 155 records (50%) were granted and still in force.

With 73 families in scope, this is a small pool. Treat the figures here as a starting point for further search rather than a map of the field: a handful of documents moving year to year, or a single filer's count, is not enough to read a trend or a competitive structure into.

Records vs. families in scope
  1. VIA TECH INC6
  2. AMAZON TECH INC3
  3. INTEL CORP3
  4. ALIBABA (CHINA) CO LTD3
  5. NVIDIA CORP3
  6. NAT INNOVATION INST OF DEFENSE TECH PLA ACAD OF MILITARY SCI2
  7. SINVENT AS2
  8. Guangzhou Forlinx Embedded Technology Co., Ltd.1
  9. MANIKANTH RAMAGANI1
  10. CHINA MOBILE QUANTONG SYST INTEGRATION CO LTD1

Counted over all 155 published records, including filings from before 2007; the filing-trend chart below covers only the 133 records from 2007 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. 2 rows in this table share the name MOBILE (CHINA MOBILE QUANTONG SYST INTEGRATION CO LTD, CHINA MOBILE COMM GRP CO LTD). They are left as separate rows, so the largest-filer figure above is per legal entity, not per group. Rows that look related still cannot be added together: one family can name several of them. 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 30 of the 65 filers returned for this search; the data endpoint returns at most 100 entities, so even that 65 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 Stream Processing GPU-Accelerated Operator Execution Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-21. 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
Data

Filing trend and technology composition

Two views of the same 73-family dataset: when the underlying records were filed, and which IPC subclasses they carry.

Filing trend by earliest filing year (published records) (133 of 155 published records)

The series runs from 2007 (13 records) to 2026 (6 records). Records filed from 2022 onward are still publishing and are understated on the chart; this is a publication-lag effect, not a change in filing activity. 2007 sits at the edge of the shown window, with 22 earlier records outside the chart, so it should not be read as a the highest year shown.

Filing trend by earliest filing year (published records) (133 of 155 published records)048111513200720092011201320152017201920212023202562022 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 2007-2026 (133 records); the 155 total quoted above includes earlier filings outside the window. 2007 is the highest year shown, but it is also the first year in the window: earlier filings sit outside this chart, so this is not necessarily the historical peak.

Technology composition by IPC subclass

G06F (Electric digital data processing) appears on 48 of 73 families (65.8%), G06T (Image data processing & generation) on 29 (39.7%), and H04N (Pictorial communication) on 13 (17.8%). Families can carry more than one subclass, so these shares add to more than 100%; 25 subclasses appear in total across the dataset.

Technology composition by IPC subclassG06F · Electric digital data processi…4865.8%G06T · Image data processing & genera…2939.7%H04N · Pictorial communication (video…1317.8%G06N · Computing based on AI models79.6%H04L · Digital information transmissi…56.8%G06Q · Business, commerce & admin dat…34.1%A61B · Diagnosis & surgery22.7%G06K · Data recognition & presentation22.7%Other1926.0%

Shares are the percentage of the 73 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 Stream Processing GPU-Accelerated Operator Execution Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-21. Counts cover published records only and move as new filings publish.

Go deeper on Stream Processing GPU-Accelerated Operator Execution Patent Landscape with Eureka

This page is one run against one query. Ask Eureka your own question about stream processing gpu-accelerated operator execution patent landscape and every answer comes back with the patent numbers behind it.

Try Eureka
Example Record

A record from the result set

First record returned (database default order)
US20250022091A12025-01-16

Optimized numerical computation framework for a graphics processing unit

BAYRIS INC.

The abstract describes performing a numerical operation inside a GPU kernel on a matrix referencing a numeric array. It describes creating a first object in the GPU's fast memory that represents the matrix and is accessible to a GPU program performing operations on it in-kernel, and a second object in global memory holding metadata about the reference matrix to facilitate access.This is simply the first record the search returns under the database's default order, not the most cited, newest, or broadest filing. What its granted claims actually require has to be read from the claim set itself; an abstract and a family count cannot establish that.

US20250022091A1, patent drawing 1US20250022091A1, 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 Stream Processing GPU-Accelerated Operator Execution Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-21. 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 →
Insights

Reading the filer and technology figures

Three figures from the dataset, reported without rolling filer rows together or reading a trend into a small pool.

Largest filer
8.2%
of 73 simple patent families

VIA Tech Inc named on 6 of 73 families

VIA Tech Inc is named on 6 of the 73 simple patent families in scope (8.2%), the largest single-row share in the listed filers. This is a count of named families, not a measure of claim scope, validity or commercial activity.

Filer list, 65 entities, organisations only
Long tail
60 of 65
listed filers hold 2 or fewer families

Filing spread across the listed filers

60 of the 65 listed filers hold 2 or fewer simple patent families each. The listed rows are organisations only and sum to more than the 73-family total because one family can name several filers, so the rows are not additive into a combined share.

Counted in simple patent families
Technology composition
65.8%
of 73 families carry G06F

G06F appears on the most families of any subclass shown

G06F (Electric digital data processing) is carried by 48 of the 73 families (65.8%), G06T by 29 (39.7%), and H04N by 13 (17.8%). Families can carry more than one subclass, so these percentages add to more than 100% and are not mutually exclusive groupings.

25 subclasses recorded in total
Legal status
50%
of 155 records in force at retrieval

78 of 155 records granted and in force

78 of the 155 published records (50%) were granted and still in force at the 2026-10-21 retrieval date. The remainder cover pending, withdrawn, refused, lapsed or not-determinable status, which are not broken out separately in this dataset.

Status as of 2026-10-21
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 stream processing gpu-accelerated operator execution 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 Stream Processing GPU-Accelerated Operator Execution Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-21. Counts cover published records only and move as new filings publish.Run this in Eureka MCP
Next Steps

Where to take this from here

This page is a starting point built from one search string over a small pool of families. The next steps depend on what you need to check.

Pull the granted claims

A family count and an abstract cannot establish what any single filing blocks or permits. Read the granted claim set directly for any record that matters to a design decision.

Open in Patsnap Eureka

Widen or adjust the search

With 73 families and 25 subclasses in play, adjacent search terms may surface records this string missed, particularly around smaller IPC classes that sit outside the ones discussed here.

Refine the search in Patsnap Eureka

Track individual filers

Filer rows here are organisations only and are not rolled up to corporate group. Checking a specific name against its own filing history, rather than this list's ranking, gives a cleaner read.

Explore filer profiles in Patsnap 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 Stream Processing GPU-Accelerated Operator Execution Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-21. 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 Stream Processing GPU-Accelerated Operator Execution Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit), retrieved 2026-10-21. Counts cover published records only and move as new filings publish.Run this in Eureka MCP

Research Stream Processing GPU-Accelerated Operator Execution Patent Landscape in depth with Eureka

Go past this page: query the whole stream processing gpu-accelerated operator execution 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:(("stream processing" OR "stream processor") AND (GPU OR "graphics processing unit") AND (operator OR execut*))

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 65.8% 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 155 records and 73 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 30 of the 65 filers returned, ordered by count alone; the data endpoint returns at most 100 entities, so even that 65 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-21.

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

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.