https://eureka.patsnap.com/resources/blog/rd-blog/variable-byte-integer-coding-patent-landscape-patent-landscape/ · Patsnap · data cut-off 2026-08-31 · downloaded from the live page
Patent Landscape · High-Performance & Advanced Computing

Variable Byte Integer Coding Patents: Who Holds the Claims

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.

34
Published Records
76%
Top-5 Share of All Records
-100%
Filing Growth 2021→2024
GB
Leading Jurisdiction

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.

Check your own idea
Published byPatsnap Research··6 min readSourced from Patsnap Eureka
Overview

What the variable byte integer coding patent record shows

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.

Filing activity and technology composition, 2015–2026
  1. 1ADOBE INC10
  2. 2MICROSOFT TECHNOLOGY LICENSING LLC6
  3. 3INTEL CORP5
  4. 4PONY AI INC3
  5. 5DOWLING TERENCE S2
  6. 6NCHAIN HLDG LTD2
  7. 7ANSYS INC1
  8. 8JEYAPRAKASH R1
  9. 9GUANGZHOU JIZHI INFORMATION TECH1
  10. 10NAT UNIV OF DEFENSE TECH1
Source: Patsnap Eureka. Assignee ranking and totals. Derived from a Patsnap search on Variable Byte Integer Coding Patent Landscape covering 2015–2026, data cut-off 2026-08-31. Counts reflect published records only and shift as new filings publish.Run this in Eureka MCP
The Numbers

Filing trend and technology composition

Two views of the same 34-record dataset: activity over time, and the IPC subclasses the records are actually filed under.

Filing activity: a 2007 peak, then a long tail

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.

Filing activity: a 2007 peak, then a long tail035810920072009201120132015201720192021202320250Most recent year is partial — publication lag means later filings are not yet visible.

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.

IPC composition: a data-handling primitive, not a dedicated codec class

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.

IPC composition: a data-handling primitive, not a dedicated codec classG06F · Electric digital data processi…1338.2%G06T · Image data processing & genera…926.5%H04L · Digital information transmissi…617.6%G06K · Data recognition & presentation411.8%G01C · Distance, navigation & gyrosco…38.8%G05D · Control of non-electric variab…25.9%G06N · Computing based on AI models25.9%H03M · Coding & code conversion25.9%Other514.7%

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%.

Source: Patsnap Eureka. Filing trend and technology composition. Derived from a Patsnap search on Variable Byte Integer Coding Patent Landscape covering 2015–2026, data cut-off 2026-08-31. Counts reflect published records only and shift as new filings publish.

Go deeper on Variable Byte Integer Coding Patent Landscape with Eureka

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 Eureka
Representative Filing

A representative claim in this space

Representative Patent
US20180095760A12018-04-05

Instruction set for variable length integer coding — Intel Corporation (US20180095760A1, filed 2018-04-05)

INTEL CORPORATION

Instruction 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.

US20180095760A1 — patent drawing 1US20180095760A1 — patent drawing 2
View full record
Source: Patsnap Eureka. Citation counts and representative records. Derived from a Patsnap search on Variable Byte Integer Coding Patent Landscape covering 2015–2026, data cut-off 2026-08-31. Counts reflect published records only and shift 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 →
Signal Check

What the concentration and composition figures mean for filing decisions

Four figures worth weighing before drafting a claim in this space.

Concentration
76.5%
of 34 records held by top 5 assignees

The top of the field is already dense

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.

Top 5 = 26 of 34 records
Long tail
14 companies
make up the entire ranked list

Beyond the leaders, filers hold single records

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.

Leader: 10 records · 10th place: 1 record
Technology mix
38.2%
of records classed under G06F

Claims cluster around data processing, not codecs

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.

G06F 38.2% · G06T 26.5% · H03M 5.9%
Filing pace
-100%
2021 → 2024 filing change

Recent-year counts understate real activity

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.

2021: 2 records · 2024: 0 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 variable byte integer coding 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 a Patsnap search on Variable Byte Integer Coding Patent Landscape covering 2015–2026, data cut-off 2026-08-31. Counts reflect published records only and shift as new filings publish.Run this in Eureka MCP
Next Steps

Where to take this analysis next

The dataset points to a few concrete follow-ups depending on what you are trying to decide.

Map the instruction-set boundary

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 →

Check the image and navigation branches

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 →

Watch the long tail for lapses

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 →
Source: Patsnap Eureka. Forward-looking reading of the same dataset. Derived from a Patsnap search on Variable Byte Integer Coding Patent Landscape covering 2015–2026, data cut-off 2026-08-31. Counts reflect published records only and shift as new filings publish.Run this in Eureka MCP
FAQ

Common questions about variable byte integer coding patents

Answers are grounded in the same dataset. Derived from a Patsnap search on Variable Byte Integer Coding Patent Landscape covering 2015–2026, data cut-off 2026-08-31. Counts reflect published records only and shift as new filings publish.Run this in Eureka MCP

Research Variable Byte Integer Coding Patent Landscape in depth with Eureka

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.

Try Eureka

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.