https://eureka.patsnap.com/resources/blog/rd-blog/genome-assembly-algorithm-using-overlap-graph-construction-patent-landscape/ · Patsnap · data cut-off null · downloaded from the live page
Patent Landscape · Bioinformatics

Genome assembly algorithm patents built on overlap graph construction

A data-backed look at genome assembly algorithm patents built on overlap, de Bruijn and assembly graph methods: who holds the claims, how filings have moved

34
Published Records
US
Leading Jurisdiction
10
Filers Listed (max 100)
2016
Peak Filing Year

  • Filings peaked in 2016 at 16 records and the field has since cooled sharply, with the 2021-to-2024 window showing a full -100% drop to zero completed filings by 2024.
  • One applicant holds a visible lead of 14 records against a ranked field of 10 companies, with the fifth-place holder at just 2 and the tenth at 1, a steep drop-off past the top of the table.
  • G16B bioinformatics classifications cover 91.2% of the 34 records in scope while adjacent classes like C40B combinatorial libraries and C04B materials sit far lower, each near 14.7%.
Check your own idea
Published byPatsnap Research··6 min readSourced from Patsnap Eureka
Overview

What this landscape covers

This landscape tracks patent families describing genome assembly algorithms built on overlap graph, de Bruijn graph or assembly graph construction, the computational core of reconstructing a genome from short or long sequencing reads. The scope spans 2015 through the 2026 data cut-off, though publication lag means the most recent one to two years are still filling in. 34 published records sit inside this search, concentrated overwhelmingly in bioinformatics classifications with smaller footprints in enzymatic synthesis, digital data processing and DNA measurement techniques.

The dataset is small enough that individual filing decisions move the picture noticeably, a single applicant's continuation strategy can shift the yearly trend line more than any market-wide shift in sequencing technology. Read the ranking and the trend together: a leader with 14 records inside a field of only 34 total families says more about claim breadth than about market size.

Filing activity and technology composition, 2014–2026
  1. PACIFIC BIOSCIENCES OF CALIFORNIA INC14
  2. 10X GENOMICS INC7
  3. GUARDANT HEALTH INC5
  4. GRAIL INC3
  5. BIOMARKER TECH2
  6. LEIGHTON1
  7. EKIM BARIS1
  8. CHIKHI RAYAN1
  9. DALIAN UNIV1
  10. ILLUMINA INC1

Ordered by volume only, not by importance or claim strength. Counted in published records, so one invention filed in several countries counts more than 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 10 of the 10 filers returned for this search; the data endpoint returns at most 100 entities, so even that 10 is not the complete set of filers. A single record 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 Genome Assembly Algorithm Using Overlap Graph Construction Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit). 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 data

Filing trend and technology composition

Two views of the same 34-record dataset: how filing activity has moved year over year, and which IPC subclasses the claims actually sit in.

Filing trend, 2014–2026

Filings opened this window at 2 in 2014, climbed to a peak of 16 in 2016, and fell to 0 completed filings by 2024, a -100% move from the 5 filings recorded in 2021. Treat 2025 and 2026 as undercounted rather than as a continuation of that decline, since publication typically lags filing by around 18 months.

Filing trend, 2014–202605101520220142015162016201720182019202020212022202320242025020262022 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.

Technology composition by IPC subclass

G16B bioinformatics classifications appear on 91.2% of the 34 records in scope, confirming this is fundamentally a computational-methods field rather than a wet-lab one. Below that, C12P enzymatic synthesis (26.5%), G06F digital data processing (23.5%) and G01N material analysis (17.6%) each mark a smaller adjacent claim surface, with C04B, C12Q and C40B tied at 14.7% apiece, each a narrower niche worth checking individually before assuming it is open.

Technology composition by IPC subclassG16B · Bioinformatics3191.2%C12P · Fermentation & enzymatic synth…926.5%G06F · Electric digital data processi…823.5%G01N · Material analysis & testing617.6%C04B · Ceramics, cement & refractories514.7%C12Q · Measuring & testing involving …514.7%C40B · Combinatorial chemistry librar…514.7%

Shares are the percentage of the 34 published records in scope. One published record 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 Genome Assembly Algorithm Using Overlap Graph Construction Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit). Counts cover published records only and move as new filings publish.

Go deeper on Genome Assembly Algorithm Using Overlap Graph Construction Patent Landscape with Eureka

This page is one run against one query. Ask Eureka your own question about genome assembly algorithm using overlap graph construction patent landscape and every answer comes back with the patent numbers behind it.

Try Eureka
Representative filing

A representative claim in this space

Representative record
US20160350478A12016-12-01

De novo diploid genome assembly and haplotype sequence reconstruction

PACIFIC BIOSCIENCES OF CALIFORNIA, INC.

The filing describes generating a fused assembly graph from reads of both haplotypes, building haplotype-specific assembly graphs from phased reads, merging them into a single haplotype-resolved graph, and removing cross-phasing edges to reconstruct haplotype-resolved sequence, a diploid-aware approach to the overlap/assembly-graph problem.Filed by Pacific Biosciences of California, published 2016-12-01.

US20160350478A1, patent drawing 1US20160350478A1, 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 Genome Assembly Algorithm Using Overlap Graph Construction Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit). 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

What the numbers indicate

Four read-throughs of the filing and classification data that matter for anyone deciding where to file or whom to watch.

Leader concentration
14 vs. 2
leader records vs. fifth place

One applicant dominates a thin field

The top-ranked assignee holds 14 of the records inside a ranked field of only 10 companies; fifth place holds just 2 and tenth place holds 1. That gap suggests one applicant built a genuinely broad claim position early, rather than the field being evenly contested.

Ranking covers 10 companies only
Peak and decline
16 → 0
2016 peak to 2024 filings

Activity peaked in 2016 and has not returned

Filings hit a peak of 16 in 2016 and the 2021-to-2024 span shows a full -100% drop to zero completed filings. Because publication lags filing by roughly 18 months, 2025 and 2026 figures are not yet reliable evidence of continued decline.

2024 is the most recent complete year
Classification spread
91.2%
of 34 records classed G16B

This is a bioinformatics claim space first

G16B covers 91.2% of the 34 records in scope, meaning nearly every filing routes through bioinformatics classification regardless of its underlying wet-lab or hardware content. Secondary classes like C12P, G06F and G01N mark where sequencing chemistry and data processing intersect with the algorithm claims.

Classes overlap; shares exceed 100% combined
Filing geography
US 10 · EP 9
leading receiving offices

Filing is split between the US and Europe, with PCT close behind

The United States and the European Patent Office lead as receiving offices at 10 and 9 records respectively, with WIPO/PCT filings at 5 and China at 4. That spread points to applicants seeking protection across both major sequencing markets rather than concentrating in one jurisdiction.

Canada and Singapore each show 2 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 genome assembly algorithm using overlap graph construction 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 Genome Assembly Algorithm Using Overlap Graph Construction Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit). Counts cover published records only and move as new filings publish.Run this in Eureka MCP
Next steps

Where to take this

The dataset points to a narrow, top-heavy field with a specific technical core. These are reasonable next moves for a team acting on it.

Map the leader's claim boundaries precisely

With 14 of 34 records held by a single applicant, the practical question is not whether that applicant is active but exactly which graph-construction steps its claims cover and where they stop.

Explore claim scope in Eureka

Check the smaller IPC branches before assuming they're open

C04B, C12Q and C40B each sit at 14.7% of records, thin enough to look like white space, but each needs individual review rather than a blanket assumption of low density.

Run a branch-level search in Eureka

Treat 2025–2026 filing counts as incomplete

Any internal trend analysis built on this data should note the roughly 18-month publication lag rather than reading the most recent years as a real slowdown.

Track filings as they update 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 Genome Assembly Algorithm Using Overlap Graph Construction Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit). Counts cover published records only and move as new filings publish.Run this in Eureka MCP
FAQ

Common questions on this landscape

Answers are grounded in the same dataset. Derived from one Patsnap search for Genome Assembly Algorithm Using Overlap Graph Construction Patent Landscape, covering all matching records regardless of filing date (the search string sets no date limit). Counts cover published records only and move as new filings publish.Run this in Eureka MCP

Research Genome Assembly Algorithm Using Overlap Graph Construction Patent Landscape in depth with Eureka

Go past this page: query the whole genome assembly algorithm using overlap graph construction 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:(("genome assembly" OR "de novo assembly") AND ("overlap graph" OR "de Bruijn graph" OR "assembly graph"))

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 (G16B) carries 91.2% of the published records, 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. 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 10 of the 10 filers returned, ordered by count alone; the data endpoint returns at most 100 entities, so even that 10 is not every filer. One published record 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 shortly before the publication date shown above.

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.