https://eureka.patsnap.com/resources/blog/rd-blog/spike-train-temporal-coding-decoder-for-brain-computer-interface-prosthetic-limb-control-p-patent-landscape/ · Patsnap · data cut-off 2026-10-21 · downloaded from the live page
Patent Landscape · Patent snapshot · 2026

Spike Train Temporal Coding Decoder Patents for Brain Computer Interface Prosthetic Limb Control

A 3-family dataset on spike-train BCI decoders shows two filers and a 2022 filing window still filling in.

10
Published Records
3
Simple Patent Families
US
Leading Jurisdiction
2022
Peak Filing Year

10 published records collapse into 3 simple (DOCDB) families; the difference is the same invention filed in more than one country.

  • Only 3 simple patent families and 10 published records match this search string. At all filing dates, with no date limit applied to the query.
  • California Inst of Tech is named on 2 of the 2 families. A 66.7% share of this single row; the other listed filer, University of Southern California, appears on the remainder.
  • United States is the most common receiving office. With 5 of the 10 published records, ahead of Europe (EPO) and WIPO (PCT) at 2 each.
Check your own idea
Published byPatsnap Research··6 min readSourced from Patsnap Eureka
Overview

What this dataset covers

This search looked for records combining spike train or temporal coding language with a decoder and a brain computer interface, BCI, or prosthetic term, inside the title, abstract and claims. It returned 10 published records that de-duplicate down to 3 simple patent families, with no date limit set on the query.

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

Records vs. families in scope
  1. CALIFORNIA INST OF TECH2
  2. UNIV OF SOUTHERN CALIFORNIA1

Counted over all 10 published records, including filings from before 2022; the filing-trend chart below covers only the 1 records from 2022 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 2 of the 2 filers returned for this search; the data endpoint returns at most 100 entities, so even that 2 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 Spike Train Temporal Coding Decoder for Brain Computer Interface Prosthetic Limb Control 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
The numbers

Filings, classes and offices

Three figures anchor this dataset: how filings are spread across years, which IPC subclasses recur, and which offices received the applications.

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

The chart shows 2022 as the highest year in this window at 1 record, with 2026 at 0. Records from 2022 onward are still filling in as they publish, so no trend or slowdown can be read from this stretch; filings before 2022 sit outside the chart.

Filing trend (published records, by earliest filing year) (1 of 10 published records)0011112022202320242025020262022 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 2022-2026 (1 records); the 10 total quoted above includes earlier filings outside the window. 2022 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.

IPC subclass composition (share of 3 simple patent families)

A61B (Diagnosis & surgery) appears on all 3 families, A61F (Implants & prostheses) on 2 of 2 (66.7%), and G06F (Electric digital data processing) and G06N (Computing based on AI models) each on 1 of 3 (33.3%). A single family can carry more than one class, so these shares add up to over 100%.

IPC subclass composition (share of 3 simple patent families)A61B · Diagnosis & surgery3100.0%A61F · Implants & prostheses266.7%G06F · Electric digital data processi…133.3%G06N · Computing based on AI models133.3%

Shares are the percentage of the 3 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 Spike Train Temporal Coding Decoder for Brain Computer Interface Prosthetic Limb Control 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 Spike Train Temporal Coding Decoder for Brain Computer Interface Prosthetic Limb Control Patent Landscape with Eureka

This page is one run against one query. Ask Eureka your own question about spike train temporal coding decoder for brain computer interface prosthetic limb control patent landscape and every answer comes back with the patent numbers behind it.

Try Eureka
Representative filing

One record from the result set

From the result set
WO2023092008A12023-05-25

WO2023092008A1, Rapid adaptation of brain-computer interfaces to new neuronal ensembles or participants via generative modelling

UNIVERSITY OF SOUTHERN CALIFORNIA

An apparatus and method for training a brain computer interface (BCI) decoder to output kinematics data from neural spike trains is disclosed. A neural spike synthesizer generator based on an LSTM neural network provides a direct mapping from input kinematics data from a first session with a first subject to a first synthesized spike train. The generator is then adapted to produce a second synthesized spike train suitable for a second subject, using observed real neural data from that subject or session plus fine tuning.This is simply the first record returned under the database's default ordering, not the most cited, newest or broadest filing in the set. Nothing about the field as a whole should be inferred from a single abstract.

WO2023092008A1, patent drawing 1WO2023092008A1, 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 Spike Train Temporal Coding Decoder for Brain Computer Interface Prosthetic Limb Control 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 →
Reading the data

What the figures show

These cards each report one figure from the dataset and what it is counted in. None of them should be read as a ranking of quality or a measure of the field's size.

Scope
3 families / 10 records
simple patent families / published records

Two counting units, same search

The search string matched 10 published records, which de-duplicate to 3 simple patent families once the same invention filed in multiple places is collapsed. No date limit was set on the query, so this is every matching record the search returns, not a window.

Counted at retrieval on 2026-10-21.
Filers
2 of 2 families
largest single-row share

California Inst of Tech named on 2 of 2 families

The listed filer table returns 2 organisation-level rows. California Inst of Tech is named on 2 of the 2 simple patent families (66.7%), and University of Southern California is the other listed row. Filings held by named individuals are removed from this list but remain inside the totals, and rows are never summed because one family can name more than one filer.

Organisation rows only; individual filers excluded from the list, included in totals.
Classes
A61B on all 3
share of 3 simple patent families

A61B appears on every family in scope

A61B (Diagnosis & surgery) is attached to all 3 families, A61F (Implants & prostheses) to 2 of 2, and G06F and G06N each to 1 of 3. These shares sum to more than 100% because a single family can carry multiple IPC subclasses.

Shares use the 3-family total as denominator throughout.
Offices
5 of 10 records
United States receiving office

United States is the most common receiving office

Of 10 published records, 5 were filed at the United States office, 2 at the EPO, 2 via WIPO (PCT), and 1 in Australia. This counts where applications were filed, not where any filer is based, the dataset holds no nationality information for filers.

Receiving-office counts sum to the 10-record total, not the family 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 spike train temporal coding decoder for brain computer interface prosthetic limb control 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 Spike Train Temporal Coding Decoder for Brain Computer Interface Prosthetic Limb Control 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

A 3-family dataset is a starting point, not a complete picture. These paths help narrow or widen the search before drawing conclusions from it.

Pull the granted claims

Family counts and abstracts cannot establish what any claim set actually covers. Reading the granted claims of California Inst of Tech's and University of Southern California's families directly is the only way to assess scope.

Open the record viewer →

Widen or vary the search string

A 3-family result is sensitive to the exact terms used. Running adjacent phrasing for spike-train decoding or BCI control in Patsnap Eureka can surface records this string did not catch.

Try a broader query in Eureka →

Track future publications

Records filed from 2022 onward are still filling in as they publish. Revisiting this search periodically will pick up records not yet visible at this retrieval date.

Set up a monitoring search →
Source: Patsnap Eureka. Suggested next steps. No new data: every figure named here is one of those above. Derived from one Patsnap search for Spike Train Temporal Coding Decoder for Brain Computer Interface Prosthetic Limb Control 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

Common questions about this dataset

Answers are grounded in the same dataset. Derived from one Patsnap search for Spike Train Temporal Coding Decoder for Brain Computer Interface Prosthetic Limb Control 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 Spike Train Temporal Coding Decoder for Brain Computer Interface Prosthetic Limb Control Patent Landscape in depth with Eureka

Go past this page: query the whole spike train temporal coding decoder for brain computer interface prosthetic limb control 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:(("spike train" OR "temporal coding") AND decoder AND ("brain computer interface" OR BCI OR prosthetic))

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

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.