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 →A patent landscape review of variable byte integer coding (varint, LEB128, VByte) covering 34 records: filing trends, assignee concentration, IPC composition and where the open claim space sits.
Filing growth = 2021 (2 records) → 2024 (0); 2024 is the last year we treat as complete. Top-5 share = the 5 largest assignees ÷ all 34 records in scope (CR5), not the ranked leaders only.
Variable byte integer coding — the family of techniques behind varint, LEB128, ULEB128, SLEB128 and related VByte schemes — compresses integers into a variable number of bytes using a continuation bit, trading a small amount of decode complexity for smaller storage and faster transmission. It shows up wherever integers need to move cheaply: serialization formats, columnar databases, sensor and navigation payloads, and instruction-level encode/decode support inside processors. The 34 records in scope span filings from 2015 through the current data cut-off, with receiving offices concentrated in the United Kingdom, the United States, China and WIPO PCT filings.
Because the underlying continuation-bit mechanism is simple and long established, most of the recent claim activity is not about the coding scheme itself but about where it is embedded — an instruction set, a navigation stack, a blockchain transaction format, or an image pipeline. That context is where the enforceable boundaries actually sit.
Two views of the same 34-record dataset: activity over time, and the IPC subclasses the records are actually filed under.
Filings peaked in 2007 at 9 records. The tracked 2021→2024 window shows a -100% swing on this dataset's own figures. Because publication lags filing by roughly 18 months, 2025 and 2026 are necessarily undercounted here and should not be read as a slowdown.
Publication lags filing by roughly 18 months, so 2025 onwards are still filling in. Growth rates on this page therefore end at 2024; running them to the last bar would understate the field.
G06F (electric digital data processing) covers 38.2% of the 34 records, ahead of G06T (image data processing, 26.5%) and H04L (digital information transmission, 17.6%). Dedicated coding classes such as H03M sit at just 5.9%, confirming that variable byte integer coding is claimed almost entirely as a supporting mechanism inside a larger system rather than as its own invention target.
Shares are the percentage of the 34 records in scope. A patent can carry several IPC classes, so the shares add up to more than 100%.
This page is one run against one query. Ask Eureka your own question about variable byte integer coding patent landscape and every answer comes back with the patent numbers behind it.
Try EurekaInstruction sets for variable length integer (varint) coding and associated methods and apparatus. The instruction set includes a varint size encode instruction, a varint encode instruction, a varint size decode instruction, and a varint decode instruction, intended for inclusion in processor instruction set architectures such as x86 and Arm-based designs.Abstract condensed from the published filing; see the full record for complete claim language.


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 →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 →Four figures worth weighing before drafting a claim in this space.
Just five assignees account for 76.5% of all 34 records in scope, and the top ten reach 94.1%. A field this size with concentration this high means a new filer is working around a small number of established positions, not competing in open territory.
The ranking is the complete list the dataset returns — 14 companies, with the leader at 10 records and the tenth-place assignee at just 1. That tail is not a sign of an open field; it is evidence that most entrants filed once and did not return.
G06F carries 38.2% of the 34 records and G06T a further 26.5%, while the dedicated coding class H03M holds only 5.9%. The coding mechanism itself is rarely the invention; it is almost always a component inside a data-processing or image-processing claim.
The dataset shows filings falling from 2 in 2021 to 0 in 2024, a -100% move on the numbers as tracked. Given the roughly 18-month gap between filing and publication, 2025-2026 figures are still incomplete and should not be read as the field going quiet.
Eureka can read the same corpus for gaps instead of for coverage: under-claimed branches adjacent to variable byte integer coding patent landscape, with the prior art for and against each one.
The dataset points to a few concrete follow-ups depending on what you are trying to decide.
Intel's varint instruction set claims sit at the processor-architecture level; anyone building software-only encode/decode should check how close a software implementation runs to those instruction-level claims before shipping.
Explore the claim space in Eureka →G06T and G01C carry a meaningful share of records despite being adjacent to the core coding technique — worth a closer look if your application touches image pipelines or navigation payloads.
Run a freedom-to-operate scan in Eureka →With 14 assignees holding the entire ranked field and most holding a single record, some of these single-filing positions may be worth monitoring for abandonment or non-renewal.
Track assignee activity in Eureka →The dataset's assignee ranking lists 14 companies total, with a clear leader holding 10 of the 34 records in scope. The top five assignees combined account for 76.5% of all records, and the top ten reach 94.1%, so the field is concentrated rather than evenly spread. Beyond the leader, most of the remaining assignees hold only a handful of filings each, down to a single record at the tenth position.
The IPC composition suggests the coding mechanism is rarely claimed on its own. Only 5.9% of the 34 records sit in H03M, the dedicated coding and code-conversion class, while 38.2% fall under G06F (general digital data processing) and 26.5% under G06T (image data processing). In practice, most filings claim varint-style coding as a component inside a larger data-handling, imaging or navigation system rather than as a standalone codec invention.
That Intel filing claims a set of processor-level instructions for encoding and decoding varints — a varint size encode instruction, a varint encode instruction, and matching decode instructions — intended for inclusion in instruction set architectures such as x86 and Arm-based designs. It blocks implementations that add dedicated hardware instructions for varint encode/decode at the ISA level, not general software libraries that perform the same encoding in software. Anyone designing custom silicon or microcode for integer compression should check how closely their instruction design tracks this claim structure.
On the tracked figures, filings fell from 2 in 2021 to 0 in 2024, a -100% change over that span, and the historical peak was 9 filings back in 2007. However, patent publication lags actual filing by roughly 18 months, so the 2025 and 2026 figures in any such dataset are structurally incomplete and should not be read as proof the field has gone quiet. A fairer read is that the coding technique itself is mature and well settled, so most recent activity shows up embedded in newer application areas rather than as fresh coding-scheme filings.
The technology composition points to areas outside the dense G06F and G06T clusters: classes like G05D (control of non-electric variables) and G06N (AI-model computing) each carry only 5.9% and 5.9% of the 34 records respectively, and G01C (navigation and gyroscopes) sits at 8.8%. These lighter-claimed branches — applying variable byte coding inside control systems, AI model serialization, or navigation payload compression — carry less prior art density than the core data-processing cluster, though a freedom-to-operate check against the instruction-set claims is still advisable before filing there.
Go past this page: query the whole variable byte integer coding patent landscape corpus yourself, in your own scope.
Every answer comes back with patent numbers you can open.
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 inherent limitations: recent filings (typically the most recent 18–24 months) are under-counted due to standard publication lag; counts may be reported at either a patent-family or a patent-record basis and are not always directly comparable; classification, applicant-name, and citation data may contain errors, duplicates, or omissions; and the underlying search query defines and constrains the scope shown. 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, or validity search, nor does it constitute legal, financial, investment, or professional advice, and it should not be relied upon as such. Any patent, commercial, or strategic decision should be verified independently 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.
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.
This page