retracile.net - Blog
https://clementofrome.com/blog
en-USTrac 1.0.13retracile.nethttps://clementofrome.com/chrome/site/logo2.png
https://clementofrome.com/blog
On Variable-length Integer EncodingretracileFri, 20 Jan 2012 02:34:16 GMT
https://clementofrome.com/blog/2012/01/20/20.30
https://clementofrome.com/blog/2012/01/20/20.30<p>
Suppose you want to represent data in a serialized form with the length prepended to the data. You can do something like what Pascal does with strings, and prefix it with an 8-bit length. But that only gives you 0 through 255 bytes of data. So you need something larger, such as a 64-bit value. But then a single-byte data value takes up 9 bytes including the length indicator. We'd really want small data values to use a small amount of overhead to encode the length, and we'd want the large data values to be representable, too. And thus, we want a variable-length encoding of the length. And the length is an integer, so we want a variable-length encoding of an integer. We'll start with representing a non-negative value, but a variable-length encoding of a signed integer may be worth a look too.
</p>
<p>
You can find some interesting articles on wikipedia about <a class="ext-link" href="http://en.wikipedia.org/wiki/Universal_code_%28data_compression%29"><span class="icon"></span>universal codes</a> which are variable-length encodings of integers, but they focus on representations of integers in bit-streams. Given our usecase, we're really dealing with <em>byte</em>-streams.
</p>
<p>
So let's start with a simple idea:
Count the number of leading 1 bits and call that <tt>N</tt>. The total size of the numeric representation is 2<sup>N</sup> bytes. Take those bytes, mask off the <tt>N</tt> leading 1 bits, and interpret the number as a binary integer.
</p>
<p>
Let's try that:
</p>
<pre class="wiki">0b00000000 = 0
0b00000001 = 1
:
0b01111111 = 127
0b10000000 00000000 = 0
0b10000000 00000001 = 1
:
0b10111111 11111111 = 16383
</pre><p>
That gives us a way to represent any non-negative integer value. But there is one undesirable characteristic of this approach: there are multiple correct ways to represent any given number. For instance, the number 0 can be represented in a single byte as 0b00000000 or in two bytes as 0b10000000 00000000. This introduces ambiguity when encoding the value 0. There may be situations where this is a desirable property, but in this case, I want there to be one and only one representation of each integer.
</p>
<p>
A simple solution is to make the representations not overlap by adding the number of valid shorter representations to the integer representation. That is, interpret the 2-byte value as an integer, then add the number of valid 1-byte values to it, And for the 4-byte value, add the number of valid 2-byte and 1-byte values to it. An alternative way to state this is to add the largest number you can represent in the 2<sup>(N-1)</sup>-byte representation (plus one) to the integer.
</p>
<p>
That gives us:
</p>
<pre class="wiki">0b00000000 = 0
0b00000001 = 1
:
0b01111111 = 127
0b10000000 00000000 = 128
0b10000000 00000001 = 129
:
0b10111111 11111111 = 16511
0b11000000 00000000 00000000 00000000 = 16512
0b11000000 00000000 00000000 00000001 = 16513
:
0b11011111 11111111 11111111 11111111 = 536887423
</pre><p>
Here is a <a class="attachment" href="https://clementofrome.com/attachment/blog/2012/01/20/20.30/varlenint.py" title="Attachment 'varlenint.py' in Blog: On Variable-length Integer Encoding">simplistic Python implementation</a><a class="trac-rawlink" href="https://clementofrome.com/raw-attachment/blog/2012/01/20/20.30/varlenint.py" title="Download"></a>. One of the nice things about using Python is that it can natively handle huge integers, so only the serialization aspect is needed.
</p>
<p>
This approach can be generalized in a couple of ways.
</p>
<p>
The first is that this could be done using leading 0 bits instead of leading 1 bits. I prefer the leading 1 bits because the 1-byte values 0-127 are the same as your normal unsigned char. But whether it is defined as the number of leading 1-bits or 0-bits, it still gives us a way to determine the value of N.
</p>
<p>
The second is in the translation of N into a representation size in bytes. I chose 2<sup>N</sup>, but it could just as easily be any function of N. If you wanted to have the size of the representation grow more slowly, you could use f(N) = N + 1. I like f(N) = 2<sup>N</sup> in part because it gives 1-byte, 2-byte, 4-byte, 8-byte representations that fit well into the natural integer sizes on modern computers.
</p>
<p>
This can also be generalized to signed integers as long as you define a mapping from the set of non-negative integers to the set of integers. A trivial solution would be to take the least significant bit to be a sign bit, though this gives you a way to represent negative zero. I suppose you could use that as a representation of Not-a-Number (<tt>NaN</tt>) or something along those lines. Alternatively, use a two's complement representation, though care would have to be taken with sign-extending the value and adding to that the largest magnitude negative or positive value that would overflow the next-smaller representation. This is left as an exercise to the reader.
</p>
<p>
Returning to our original problem statement, we now have a way to prepend a length to a data value while having the overhead cost low for small values while still supporting very large values. One byte of overhead to represent the length for data of 0 through 127 bytes is acceptable. Two bytes for 128 through 16511 bytes is also fine. By the time the overhead reaches 8 bytes, you're dealing with half a gigabyte of data.
</p>
<p>
But such a representation has additional possible uses. One that I have toyed with is using such a representation for a binary network communication protocol. Each message you define gets assigned an integer value, and you don't have to commit to a specific maximum number of message types when you define your protocol. Were I to use this for a protocol, I would want to make a 'version check' message have a numeric value < 128 so it fits in a single byte. And most messages would get a number that would map to a 2-byte value. That way, as messages are determined to be bandwidth "hot spots", they can be moved to a <128 value to cut a byte off their representation. The other thing I would probably do with protocol numbers would be to define a different <tt>f(N)</tt> that would grow the size of the integer representation more slowly. For that matter, it would be possible to map f(0) -> 1, f(1)->2, f(2)->2, f(3)->2, f(4)->3, etc; this would complicate some of the math, but would allow packing more values into 2 bytes. (The number of values represented by the second and third 2-byte representations would be half or a quarter of what the first 2-byte representation supported.) In a case like this, I would probably only define f(N) for the values of N I actually expect to use, and extend the definition as need arose.
</p>
<p>
Network protocols is another case where the unique nature of the representation is important. When you are dealing with systems that you want to secure (such as a network protocol), you do not want the ambiguity in the encoding process that a non-unique encoding implies. You want one and only one representation of each possible value so any attacker has no flexibility in doing something strange like using 256 bytes to represent the number 0.
</p>
<p>
I was prompted to post this by <a class="ext-link" href="http://programmers.stackexchange.com/q/130391/4070"><span class="icon"></span>a question on programmers.stackexchange.com</a>.
</p>
programmingnumbers