View source for Arithmetic coding

{{short description|Form of entropy encoding used in data compression}}
{{Use dmy dates|date=December 2019}}
{{more footnotes needed|date=September 2016}}
'''Arithmetic coding''' ('''AC''') is a form of [[entropy encoding]] used in [[lossless data compression]]. Normally, a [[String (computer science)|string of characters]] is represented using a fixed number of [[bit]]s per character, as in the [[American Standard Code for Information Interchange|ASCII]] code. When a string is converted to arithmetic encoding, frequently used characters will be stored with fewer bits and not-so-frequently occurring characters will be stored with more bits, resulting in fewer bits used in total. Arithmetic coding differs from other forms of entropy encoding, such as [[Huffman coding]], in that rather than separating the input into component symbols and replacing each with a code, arithmetic coding encodes the entire message into a single number, an [[arbitrary-precision arithmetic|arbitrary-precision]] fraction ''q'', where {{nowrap|0.0 ≤ ''q'' &lt; 1.0}}.<!-- <ref name="LiDrew2014">{{cite book|author1=Ze-Nian Li|author2=Mark S. Drew|author3=Jiangchuan Liu|title=Fundamentals of Multimedia|url=https://books.google.com/books?id=R6vBBAAAQBAJ|date=9 April 2014|publisher=Springer Science & Business Media|isbn=978-3-319-05290-8}}</ref> -->

[[File:Arithmetic coding example.svg|400px|thumb|right|An arithmetic coding example assuming a fixed probability distribution of three symbols "A", "B", and "C". Probability of "A" is 50%, probability of "B" is 33% and probability of "C" is 17%. Furthermore, we assume that the recursion depth is known in each step. In step one we code "B" which is inside the interval &#91;0.5,&nbsp;0.83): The binary number "0.10''x''" is the shortest code that represents an interval that is entirely inside &#91;0.5,&nbsp;0.83). "''x''" means an arbitrary bit sequence. There are two extreme cases: the smallest ''x'' stands for zero which represents the left side of the represented interval. Then the left side of the interval is dec(0.10)&nbsp;=&nbsp;0.5. At the other extreme, ''x'' stands for a finite sequence of ones which has the upper limit dec(0.11)&nbsp;=&nbsp;0.75. Therefore, "0.10''x''" represents the interval &#91;0.5,&nbsp;0.75) which is inside &#91;0.5,&nbsp;0.83). Now we can leave out the "0." part since all intervals begin with&nbsp;"0." and we can ignore the "''x''" part because no matter what bit-sequence it represents, we will stay inside &#91;0.5,&nbsp;0.75).]]

==Implementation details and examples==
[[File:arithmetic_coding_visualisation.svg|thumb|300px|Encoding the message "WIKI" with arithmetic coding
{|
! style="text-align:right; vertical-align:top;"|1.
| The letter frequencies are found.
|-
! style="text-align:right; vertical-align:top;"|2.
| The interval [0, 1) is partitioned in the ratio of the frequencies.
|-
! style="text-align:right; vertical-align:top;"|3–5.
| The corresponding interval is iteratively partitioned for each letter in the message.
|-
! style="text-align:right; vertical-align:top;"|6.
| Any value in the final interval is chosen to represent the message.
|-
! style="text-align:right; vertical-align:top;"|2*–6*.
| The partitioning and value if the message were "KIWI" instead.
|} ]]
[[File:Arithmetic_coding_visualisation_circle.svg|thumb|300px|The above example visualised as a circle, the values in red encoding "WIKI" and "KIWI" – in [http://upload.wikimedia.org/wikipedia/commons/8/81/Arithmetic_coding_visualisation_circle.svg the SVG image], hover over an interval to highlight it and show its statistics]]

===Equal probabilities===
In the simplest case, the probability of each symbol occurring is equal. For example, consider a set of three symbols, A, B, and C, each equally likely to occur. Encoding the symbols one by one would require 2 bits per symbol, which is wasteful: one of the bit variations is never used. That is to say, symbols A, B and C might be encoded respectively as 00, 01 and 10, with 11 unused.

A more efficient solution is to represent a sequence of these three symbols as a rational number in base 3 where each digit represents a symbol. For example, the sequence "ABBCAB" could become 0.011201<sub>3</sub>, in arithmetic coding as a value in the interval &#91;0,&nbsp;1). The next step is to encode this [[Ternary numeral system|ternary]] number using a fixed-point binary number of sufficient precision to recover it, such as 0.0010110001<sub>2</sub> – this is only 10 bits; 2 bits are saved in comparison with naïve block encoding. This is feasible for long sequences because there are efficient, in-place algorithms for converting the base of arbitrarily precise numbers.

To decode the value, knowing the original string had length&nbsp;6, one can simply convert back to base&nbsp;3, round to 6 digits, and recover the string.

===Defining a model===

In general, arithmetic coders can produce near-optimal output for any given set of symbols and probabilities. (The optimal value is −log<sub>2</sub>''P'' bits for each symbol of probability ''P''; see ''[[Source coding theorem]]''.) Compression algorithms that use arithmetic coding start by determining a [[model (abstract)|model]] of the data – basically a prediction of what patterns will be found in the symbols of the message. The more accurate this prediction is, the closer to optimal the output will be.

'''Example''': a simple, static model for describing the output of a particular monitoring instrument over time might be:
*60% chance of symbol NEUTRAL
*20% chance of symbol POSITIVE
*10% chance of symbol NEGATIVE
*10% chance of symbol END-OF-DATA. ''(The presence of this symbol means that the stream will be 'internally terminated', as is fairly common in data compression; when this symbol appears in the data stream, the decoder will know that the entire stream has been decoded.)''

Models can also handle alphabets other than the simple four-symbol set chosen for this example. More sophisticated models are also possible: ''higher-order'' modelling changes its estimation of the current probability of a symbol based on the symbols that precede it (the ''context''), so that in a model for English text, for example, the percentage chance of "u" would be much higher when it follows a "Q" or a "q". Models can even be ''[[adaptive coding|adaptive]]'', so that they continually change their prediction of the data based on what the stream actually contains. The decoder must have the same model as the encoder.

===Encoding and decoding: overview===

In general, each step of the encoding process, except for the last, is the same; the encoder has basically just three pieces of data to consider:
* The next symbol that needs to be encoded
* The current [[interval (mathematics)|interval]] (at the very start of the encoding process, the interval is set to <nowiki>[0,1]</nowiki>, but that will change)
* The probabilities the model assigns to each of the various symbols that are possible at this stage (as mentioned earlier, higher-order or adaptive models mean that these probabilities are not necessarily the same in each step.)

The encoder divides the current interval into sub-intervals, each representing a fraction of the current interval proportional to the probability of that symbol in the current context. Whichever interval corresponds to the actual symbol that is next to be encoded becomes the interval used in the next step.

'''Example''': for the four-symbol model above:
* the interval for NEUTRAL would be <nowiki>[0, 0.6)</nowiki>
* the interval for POSITIVE would be <nowiki>[0.6, 0.8)</nowiki>
* the interval for NEGATIVE would be <nowiki>[0.8, 0.9)</nowiki>
* the interval for END-OF-DATA would be <nowiki>[0.9, 1)</nowiki>.

When all symbols have been encoded, the resulting interval unambiguously identifies the sequence of symbols that produced it. Anyone who has the same final interval and model that is being used can reconstruct the symbol sequence that must have entered the encoder to result in that final interval.

It is not necessary to transmit the final interval, however; it is only necessary to transmit ''one fraction'' that lies within that interval. In particular, it is only necessary to transmit enough digits (in whatever base) of the fraction so that all fractions that begin with those digits fall into the final interval; this will guarantee that the resulting code is a [[prefix code]].

===Encoding and decoding: example===
[[Image:Arithmetic encoding.svg|400px|thumb|right|A diagram showing decoding of 0.538 (the round dot) in the example model. The region is divided into subregions proportional to symbol frequencies, then the subregion containing the point is successively subdivided in the same way.]]
Consider the process for decoding a message encoded with the given four-symbol model. The message is encoded in the fraction 0.538 (using decimal for clarity, instead of binary; also assuming that there are only as many digits as needed to decode the message.)

The process starts with the same interval used by the encoder: <nowiki>[0,1)</nowiki>, and using the same model, dividing it into the same four sub-intervals that the encoder must have. The fraction 0.538 falls into the sub-interval for NEUTRAL, <nowiki>[0, 0.6)</nowiki>; this indicates that the first symbol the encoder read must have been NEUTRAL, so this is the first symbol of the message.

Next divide the interval <nowiki>[0, 0.6)</nowiki> into sub-intervals:
* the interval for NEUTRAL would be <nowiki>[0, 0.36)</nowiki>, ''60% of <nowiki>[0, 0.6)</nowiki>''.
* the interval for POSITIVE would be <nowiki>[0.36, 0.48)</nowiki>, ''20% of <nowiki>[0, 0.6)</nowiki>''.
* the interval for NEGATIVE would be <nowiki>[0.48, 0.54)</nowiki>, ''10% of <nowiki>[0, 0.6)</nowiki>''.
* the interval for END-OF-DATA would be <nowiki>[0.54, 0.6)</nowiki>, ''10% of <nowiki>[0, 0.6)</nowiki>''.

Since 0.538 is within the interval <nowiki>[0.48, 0.54)</nowiki>, the second symbol of the message must have been NEGATIVE.

Again divide our current interval into sub-intervals:
* the interval for NEUTRAL would be <nowiki>[0.48, 0.516)</nowiki>.
* the interval for POSITIVE would be <nowiki>[0.516, 0.528)</nowiki>.
* the interval for NEGATIVE would be <nowiki>[0.528, 0.534)</nowiki>.
* the interval for END-OF-DATA would be <nowiki>[0.534, 0.540)</nowiki>.

Now 0.538 falls within the interval of the END-OF-DATA symbol; therefore, this must be the next symbol. Since it is also the internal termination symbol, it means the decoding is complete. If the stream is not internally terminated, there needs to be some other way to indicate where the stream stops. Otherwise, the decoding process could continue forever, mistakenly reading more symbols from the fraction than were in fact encoded into it.

===Sources of inefficiency===

The message 0.538 in the previous example could have been encoded by the equally short fractions 0.534, 0.535, 0.536, 0.537 or 0.539. This suggests that the use of decimal instead of binary introduced some inefficiency. This is correct; the information content of a three-digit decimal is <math>3 \times \log_2(10) \approx 9.966</math> [[bit]]s; the same message could have been encoded in the binary fraction 0.10001001 (equivalent to 0.53515625 decimal) at a cost of only 8 bits.

This 8 bit output is larger than the information content, or [[information entropy|entropy]], of the message, which is

:<math qid=Q2651> \sum -\log_2(p_i) = -\log_2(0.6) - \log_2(0.1) - \log_2(0.1) = 7.381 \text{ bits}.</math>

But an integer number of bits must be used in the binary encoding, so an encoder for this message would use at least 8 bits, resulting in a message 8.4% larger than the entropy contents. This inefficiency of at most 1 bit results in relatively less overhead as the message size grows.

Moreover, the claimed symbol probabilities were <nowiki>[0.6,&nbsp;0.2,&nbsp;0.1,&nbsp;0.1)</nowiki>, but the actual frequencies in this example are <nowiki>[0.33,&nbsp;0,&nbsp;0.33,&nbsp;0.33)</nowiki>. If the intervals are readjusted for these frequencies, the entropy of the message would be 4.755 bits and the same NEUTRAL NEGATIVE END-OF-DATA message could be encoded as intervals <nowiki>[0,&nbsp;1/3); [1/9,&nbsp;2/9); [5/27,&nbsp;6/27);</nowiki> and a binary interval of <nowiki>[0.00101111011, 0.00111000111)</nowiki>. This is also an example of how statistical coding methods like arithmetic encoding can produce an output message that is larger than the input message, especially if the probability model is off.

==Adaptive arithmetic coding==
{{See also|Context-adaptive binary arithmetic coding}}

One advantage of arithmetic coding over other similar methods of data compression is the convenience of adaptation. ''Adaptation'' is the changing of the frequency (or probability) tables while processing the data. The decoded data matches the original data as long as the frequency table in decoding is replaced in the same way and in the same step as in encoding. The synchronization is, usually, based on a combination of symbols occurring during the encoding and decoding process.

==Precision and renormalization==
The above explanations of arithmetic coding contain some simplification. In particular, they are written as if the encoder first calculated the fractions representing the endpoints of the interval in full, using infinite [[precision (arithmetic)|precision]], and only converted the fraction to its final form at the end of encoding. Rather than try to simulate infinite precision, most arithmetic coders instead operate at a fixed limit of precision which they know the decoder will be able to match, and round the calculated fractions to their nearest equivalents at that precision. An example shows how this would work if the model called for the interval {{math|[0,1)}} to be divided into thirds, and this was approximated with 8 bit precision. Note that since now the precision is known, so are the binary ranges we'll be able to use.

{| class="wikitable"
! rowspan="2" | Symbol
!Probability 
! colspan="2" | Interval reduced to eight-bit precision
! Range 
|-
!(expressed as fraction)
!(as fractions)
!(in binary)
!(in binary)
|- align="center"
|A
|1/3
|{{math|[0, 85/256)}}
|<span style="font-family:monospace">[0.00000000, 0.01010101)</span>
|<span style="font-family:monospace">00000000 – 01010100</span>
|- align="center"
|B
|1/3
|{{math|[85/256, 171/256)}}
|<span style="font-family:monospace">[0.01010101, 0.10101011)</span>
|<span style="font-family:monospace">01010101 – 10101010</span>
|- align="center"
|C
|1/3
|{{math|[171/256, 1)}}
|<span style="font-family:monospace">[0.10101011, 1.00000000)</span>
|<span style="font-family:monospace">10101011 – 11111111</span>
|}

A process called ''renormalization'' keeps the finite precision from becoming a limit on the total number of symbols that can be encoded. Whenever the range is reduced to the point where all values in the range share certain beginning digits, those digits are sent to the output. For however many digits of precision the computer ''can'' handle, it is now handling fewer than that, so the existing digits are shifted left, and at the right, new digits are added to expand the range as widely as possible. Note that this result occurs in two of the three cases from our previous example.

{| class="wikitable"
!Symbol
!Probability
!Range
!Digits that can be sent to output
!Range after renormalization
|- align="center"
|A
|1/3
|{{mono|'''0'''0000000 – '''0'''1010100}}
|'''0'''
|{{mono|0000000'''0''' – 1010100'''1'''}}
|- align="center"
|B
|1/3
|{{mono|01010101 – 10101010}}
|{{CNone|None}}
|{{mono|01010101 – 10101010}}
|- align="center"
|C
|1/3
|{{mono|'''1'''0101011 – '''1'''1111111}}
|'''1'''
|{{mono|0101011'''0''' – 1111111'''1'''}}
|}

==Arithmetic coding as a generalized change of radix==
Recall that in the case where the symbols had equal probabilities, arithmetic coding could be implemented by a simple change of base, or radix. In general, arithmetic (and range) coding may be interpreted as a ''generalized'' change of [[radix]]. For example, we may look at any sequence of symbols:

:<math>\mathrm{DABDDB}</math>

as a number in a certain base presuming that the involved symbols form an ordered set and each symbol in the ordered set denotes a sequential integer A&nbsp;=&nbsp;0, B&nbsp;=&nbsp;1, C&nbsp;=&nbsp;2, D&nbsp;=&nbsp;3, and so on. This results in the following frequencies and cumulative frequencies:

{| class="wikitable" style="text-align:center;"
!Symbol
!Frequency of occurrence
!Cumulative frequency
|-
|A
|1
|0
|-
|B
|2
|1
|-
|D
|3
|3
|}

The ''cumulative frequency'' for an item is the sum of all frequencies preceding the item. In other words, cumulative frequency is a running total of frequencies.

In a positional [[numeral system]] the radix, or base, is numerically equal to a number of different symbols used to express the number. For example, in the decimal system the number of symbols is 10, namely 0, 1, 2, 3, 4, 5, 6, 7, 8, and 9. The radix is used to express any finite integer in a presumed multiplier in polynomial form. For example, the number 457 is actually 4×10<sup>2</sup>&nbsp;+&nbsp;5×10<sup>1</sup>&nbsp;+&nbsp;7×10<sup>0</sup>, where base 10 is presumed but not shown explicitly.

Initially, we will convert DABDDB into a base-6 numeral, because 6 is the length of the string. The string is first mapped into the digit string 301331, which then maps to an integer by the polynomial:

:<math>6^5 \times 3 + 6^4 \times 0 + 6^3 \times 1 + 6^2 \times 3 + 6^1 \times 3 + 6^0 \times 1 = 23671</math>

The result 23671 has a length of 15 bits, which is not very close to the theoretical limit (the [[Entropy (information theory)|entropy]] of the message), which is approximately 9 bits.

To encode a message with a length closer to the theoretical limit imposed by information theory we need to slightly generalize the classic formula for changing the radix. We will compute lower and upper bounds ''L'' and ''U'' and choose a number between them. For the computation of ''L'' we multiply each term in the above expression by the product of the frequencies of all previously occurred symbols:

:<math>\begin{align}
  L = {} &(6^5 \times 3) + {}\\
                  & 3 \times (6^4 \times 0) + {}\\
                  & (3 \times 1) \times (6^3 \times 1) + {}\\
                  & (3 \times 1 \times 2) \times (6^2 \times 3) + {}\\
                  & (3 \times 1 \times 2 \times 3) \times (6^1 \times 3) + {}\\
                  & (3 \times 1 \times 2 \times 3 \times 3) \times (6^0 \times 1) {}\\
             = {} & 25002
\end{align}</math>

The difference between this polynomial and the polynomial above is that each term is multiplied by the product of the frequencies of all previously occurring symbols. More generally, ''L'' may be computed as:

:<math> L = \sum_{i=1}^n n^{n-i} C_i { \prod_{k=1}^{i-1} f_k } </math>

where <math>\scriptstyle C_i</math> are the cumulative frequencies and <math>\scriptstyle f_k</math> are the frequencies of occurrences. Indexes denote the position of the symbol in a message. In the special case where all frequencies <math>\scriptstyle f_k</math> are 1, this is the change-of-base formula.

The upper bound ''U'' will be ''L'' plus the product of all frequencies; in this case ''U'' = ''L'' + (3 × 1 × 2 × 3 × 3 × 2) = 25002 + 108 = 25110. In general, ''U'' is given by:

:<math> U = L + \prod_{k=1}^{n} f_k </math>

Now we can choose any number from the interval [''L'', ''U'') to represent the message; one convenient choice is the value with the longest possible trail of zeroes, 25100, since it allows us to achieve compression by representing the result as 251×10<sup>2</sup>. The zeroes can also be truncated, giving 251, if the length of the message is stored separately. Longer messages will tend to have longer trails of zeroes.

To decode the integer 25100, the polynomial computation can be reversed as shown in the table below. At each stage the current symbol is identified, then the corresponding term is subtracted from the result.

{| class="wikitable" style="text-align:center;"
!Remainder
!Identification
!Identified symbol
!Corrected remainder
|-
|25100
|style="text-align:right;"|25100 / 6<sup>5</sup> = 3
|D
|style="text-align:right;"|(25100 − 6<sup>5</sup> × 3) / 3 = 590
|-
|590
|style="text-align:right;"|590 / 6<sup>4</sup> = 0
|A
|style="text-align:right;"|(590 − 6<sup>4</sup> × 0) / 1 = 590
|-
|590
|style="text-align:right;"|590 / 6<sup>3</sup> = 2
|B
|style="text-align:right;"|(590 − 6<sup>3</sup> × 1) / 2 = 187
|-
|187
|style="text-align:right;"|187 / 6<sup>2</sup> = 5
|D
|style="text-align:right;"|(187 − 6<sup>2</sup> × 3) / 3 = 26{{figure space}}
|-
|26
|style="text-align:right;"|26 / 6<sup>1</sup> = 4
|D
|style="text-align:right;"|(26 − 6<sup>1</sup> × 3) / 3 = 2{{figure space}}{{figure space}}
|-
|2
|style="text-align:right;"|2 / 6<sup>0</sup> = 2
|B
|—
|}

During decoding we take the floor after dividing by the corresponding power of 6. The result is then matched against the cumulative intervals and the appropriate symbol is selected from look up table. When the symbol is identified the result is corrected. The process is continued for the known length of the message or while the remaining result is positive. The only difference compared to the classical change-of-base is that there may be a range of values associated with each symbol. In this example, A is always 0, B is either 1 or 2, and D is any of 3, 4, 5. This is in exact accordance with our intervals that are determined by the frequencies. When all intervals are equal to 1 we have a special case of the classic base change.

===Theoretical limit of compressed message===
The lower bound ''L'' never exceeds ''n''<sup>''n''</sup>, where ''n'' is the size of the message, and so can be represented in <math>\log_2(n^n) = n \log_2(n)</math> bits. After the computation of the upper bound ''U'' and the reduction of the message by selecting a number from the interval [''L'',&nbsp;''U'') with the longest trail of zeros we can presume that this length can be reduced by <math>\textstyle \log_2\left(\prod_{k=1}^n f_k\right)</math> bits. Since each frequency in a product occurs exactly the same number of times as the value of this frequency, we can use the size of the alphabet ''A'' for the computation of the product

:<math> \prod_{k=1}^n f_k = \prod_{k=1}^A f_k^{f_k}.</math>

Applying log<sub>2</sub> for the estimated number of bits in the message, the final message (not counting a logarithmic overhead for the message length and frequency tables) will match the number of bits given by [[entropy (information theory)|entropy]], which for long messages is very close to optimal:

:<math>-\left[\sum_{i=1}^A f_i \log_2(f_i)\right] n = n H</math>
In other words, the efficiency of arithmetic encoding approaches the theoretical limit of <math>H</math> bits per symbol, as the message length approaches infinity.

==== Asymptotic equipartition ====
We can understand this intuitively. Suppose the source is ergodic, then it has the [[asymptotic equipartition property]] (AEP). By the AEP, after a long stream of <math>n</math> symbols, the interval of <math>(0, 1)</math> is almost partitioned into almost equally-sized intervals.

Technically, for any small <math>\epsilon > 0</math>, for all large enough <math>n</math>, there exists <math>2^{nH(X)(1+O(\epsilon))}</math> strings <math>x_{1:n}</math>, such that each string has almost equal probability <math>Pr(x_{1:n}) = 2^{-nH(X)(1+ O(\epsilon))} </math>, and their total probability is <math>1-O(\epsilon)</math>.

For any such string, it is arithmetically encoded by a binary string of length <math>k</math>, where <math>k</math> is the smallest <math>k</math> such that there exists a fraction of form <math>\frac{?}{2^k}</math> in the interval for <math>x_{1:n}</math>. Since the interval for <math>x_{1:n}</math> has size <math>2^{-nH(X)(1+ O(\epsilon))} </math>, we should expect it to contain one fraction of form <math>\frac{?}{2^k}</math> when <math>k = nH(X)(1+O(\epsilon))</math>.

Thus, with high probability, <math>x_{1:n}</math> can be arithmetically encoded with a binary string of length <math>nH(X) ( 1 + O(\epsilon))</math>.

==Connections with other compression methods==

===Huffman coding===
{{Main|Huffman coding}}
Because arithmetic coding doesn't compress one datum at a time, it can get arbitrarily close to entropy when compressing [[Independent and identically distributed random variables|IID]] strings. By contrast, using the extension of [[Huffman coding]] (to strings) does not reach entropy unless all probabilities of alphabet symbols are powers of two, in which case both Huffman and arithmetic coding achieve entropy.

When naively Huffman coding binary strings, no compression is possible, even if entropy is low (e.g. ({0, 1}) has probabilities {0.95, 0.05}). Huffman encoding assigns 1 bit to each value, resulting in a code of the same length as the input. By contrast, arithmetic coding compresses bits well, approaching the optimal compression ratio of

:<math> 1 - [-0.95 \log_2(0.95) + -0.05 \log_2(0.05)] \approx 71.4\%.</math>

One simple way to address Huffman coding's suboptimality is to concatenate symbols ("blocking") to form a new alphabet in which each new symbol represents a sequence of original symbols – in this case bits – from the original alphabet. In the above example, grouping sequences of three symbols before encoding would produce new "super-symbols" with the following frequencies:
* {{samp|000}}: 85.7%
* {{samp|001}}, {{samp|010}}, {{samp|100}}: 4.5% each
* {{samp|011}}, {{samp|101}}, {{samp|110}}: 0.24% each
* {{samp|111}}: 0.0125%

With this grouping, Huffman coding averages 1.3 bits for every three symbols, or 0.433 bits per symbol, compared with one bit per symbol in the original encoding, i.e., <math>56.7\%</math> compression. Allowing arbitrarily large sequences gets arbitrarily close to entropy – just like arithmetic coding – but requires huge codes to do so, so is not as practical as arithmetic coding for this purpose.

An alternative is [[Run-length encoding|encoding run lengths]] via Huffman-based [[Golomb coding|Golomb-Rice codes]]. Such an approach allows simpler and faster encoding/decoding than arithmetic coding or even Huffman coding, since the latter requires a table lookups. In the {0.95, 0.05} example, a Golomb-Rice code with a four-bit remainder achieves a compression ratio of <math>71.1\%</math>, far closer to optimum than using three-bit blocks. Golomb-Rice codes only apply to [[Bernoulli process|Bernoulli]] inputs such as the one in this example, however, so it is not a substitute for blocking in all cases.

==History and patents==

Basic algorithms for arithmetic coding were developed independently by [[Jorma J. Rissanen]], at [[IBM Research]], and by Richard C. Pasco, a Ph.D. student at [[Stanford University]]; both were published in May 1976. Pasco cites a pre-publication draft of Rissanen's article and comments on the relationship between their works:<ref>{{cite thesis |type=PhD |last=Pasco |first=Richard Clark |date=May 1976 |title=Source coding algorithms for fast data compression |publisher=Stanford Univ|citeseerx=10.1.1.121.3377 }}</ref>
{{blockquote|
One algorithm of the family was developed independently by Rissanen [1976]. It shifts the code element to the most significant end of the accumulator, using a pointer obtained by addition and exponentiation. We shall now compare the alternatives in the three choices, and see that it is preferable to shift the code element rather than the accumulator, and to add code elements to the least significant end of the accumulator.}}

Less than a year after publication, IBM filed for a US [[patent]] on Rissanen's work. Pasco's work was not patented.

A variety of specific techniques for arithmetic coding have historically been covered by US patents, although various well-known methods have since passed into the public domain as the patents have expired. Techniques covered by patents may be essential for implementing the algorithms for arithmetic coding that are specified in some formal international standards. When this is the case, such patents are generally available for licensing under what is called "reasonable and non-discriminatory" ([[Reasonable and non-discriminatory licensing|RAND]]) licensing terms (at least as a matter of standards-committee policy). In some well-known instances, (including some involving IBM patents that have since expired), such licenses were available for free, and in other instances, licensing fees have been required. The availability of licenses under RAND terms does not necessarily satisfy everyone who might want to use the technology, as what may seem "reasonable" for a company preparing a proprietary commercial software product may seem much less reasonable for a [[free software]] or [[Open-source software|open source]] project.

At least one significant compression software program, [[bzip2]], deliberately discontinued the use of arithmetic coding in favor of Huffman coding due to the perceived patent situation at the time. Also, encoders and decoders of the [[JPEG]] file format, which has options for both Huffman encoding and arithmetic coding, typically only support the Huffman encoding option, which was originally because of patent concerns; the result is that nearly all JPEG images in use today use Huffman encoding<ref>{{cite web|url=http://www.faqs.org/faqs/compression-faq/part1/section-17.html|title=What is JPEG?|website=comp.compression Frequently Asked Questions (part 1/3)}}</ref> although JPEG's arithmetic coding patents<ref>{{cite web |url=http://www.itu.int/rec/T-REC-T.81-200401-I!Cor1/dologin.asp?lang=e&id=T-REC-T.81-200401-I!Cor1!PDF-E&type=items |title=Recommendation T.81 (1992) Corrigendum 1 (01/04) |date=9 November 2004 |work=Recommendation T.81 (1992) |publisher=International Telecommunication Union |access-date=3 February 2011}}</ref> have expired due to the age of the JPEG standard (the design of which was approximately completed by 1990).<ref>{{cite book|title=JPEG Still Image Data Compression Standard|first1=W. B.|last1=Pennebaker|first2=J. L.|last2=Mitchell|publisher=Kluwer Academic Press|year=1992|isbn=0442012721}}</ref> [[JPEG XL]], as well as archivers like PackJPG, Brunsli and Lepton, that can losslessly convert Huffman encoded files to ones with arithmetic coding (or [[asymmetric numeral systems]] in case of JPEG XL), show up to 25% size saving.

The JPEG [[image compression]] format's arithmetic coding algorithm is based on the following cited patents (since expired).<ref name="t81">{{cite web |title=T.81 – DIGITAL COMPRESSION AND CODING OF CONTINUOUS-TONE STILL IMAGES – REQUIREMENTS AND GUIDELINES |url=https://www.w3.org/Graphics/JPEG/itu-t81.pdf |publisher=[[CCITT]] |date=September 1992 |access-date=12 July 2019}}</ref>

* {{US patent|4652856}} – ([[IBM]]) Filed 4 February 1986, granted 24 March 1987 – Kottappuram M. A. Mohiuddin, Jorma Johannes Rissanen – Multiplication-free multi-alphabet arithmetic code
* {{US patent|4905297}} – (IBM) Filed 18 November 1988, granted 27 February 1990 – Glen George Langdon, Joan L. Mitchell, William B. Pennebaker, Jorma Johannes Rissanen – Arithmetic coding encoder and decoder system
* {{US patent|4935882}} – (IBM) Filed 20 July 1988, granted 19 June 1990 – William B. Pennebaker, Joan L. Mitchell – Probability adaptation for arithmetic coders
* [https://patents.google.com/patent/JPH02202267A/en JP Patent 1021672] – ([[Mitsubishi Electric|Mitsubishi]]) Filed 21 January 1989, granted 10 August 1990 – Toshihiro Kimura, Shigenori Kino, Fumitaka Ono, Masayuki Yoshida – Coding system
* [https://patents.google.com/patent/JPH0834434B2/en JP Patent 2-46275] – (Mitsubishi) Filed 26 February 1990, granted 5 November 1991 – Fumitaka Ono, Tomohiro Kimura, Masayuki Yoshida, Shigenori Kino – Coding apparatus and coding method

Other patents (mostly also expired) related to arithmetic coding include the following.

* {{US patent|4122440}} – (IBM) Filed 4 March 1977, granted 24 October 1978 – Glen George Langdon, Jorma Johannes Rissanen – Method and means for arithmetic string coding
* {{US patent|4286256}} – (IBM) Filed 28 November 1979, granted 25 August 1981 – Glen George Langdon, Jorma Johannes Rissanen – Method and means for arithmetic coding utilizing a reduced number of operations
* {{US patent|4467317}} – (IBM) Filed 30 March 1981, granted 21 August 1984 – Glen George Langdon, Jorma Johannes Rissanen – High-speed arithmetic compression coding using concurrent value updating
* {{US patent|4891643}} – (IBM) Filed 15 September 1986, granted 2 January 1990 – Joan L. Mitchell, William B. Pennebaker – Arithmetic coding data compression/de-compression by selectively employed, diverse arithmetic coding encoders and decoders
* [https://patents.google.com/patent/JPS63281524A/en JP Patent 11782787] – ([[NEC]]) Filed 13 May 1987, granted 18 November 1988 – Michio Shimada – Data compressing arithmetic encoding device
* [https://patents.google.com/patent/JPS63314918A/en JP Patent 15015487] – ([[KDDI]]) Filed 18 June 1987, granted 22 December 1988 – Shuichi Matsumoto, Masahiro Saito – System for preventing carrying propagation in arithmetic coding
* {{US patent|4933883}} – (IBM) Filed 3 May 1988, granted 12 June 1990 – William B. Pennebaker, Joan L. Mitchell – Probability adaptation for arithmetic coders
* {{US patent|4989000}} – (IBM) Filed 19 June 1989, granted 29 January 1991 – Dan S. Chevion, Ehud D. Karnin, Eugeniusz Walach – Data string compression using arithmetic encoding with simplified probability subinterval estimation
* {{US patent|5099440}} – (IBM) Filed 5 January 1990, granted 24 March 1992 – William B. Pennebaker, Joan L. Mitchell – Probability adaptation for arithmetic coders
* {{US patent|5272478}} – ([[Ricoh]]) Filed 17 August 1992, granted 21 December 1993 – James D. Allen – Method and apparatus for entropy coding

Note: This list is not exhaustive. See the following links for a list of more US patents.<ref>{{cite web|url=http://www.faqs.org/faqs/compression-faq/part1/|website=comp.compression|title=Frequently Asked Questions}}</ref> The [[Dirac (codec)|Dirac codec]] uses arithmetic coding and is not patent pending.<ref>{{Cite web|url=https://lwn.net/Articles/272520/|title=Dirac video codec 1.0 released [LWN.net]|website=lwn.net}}</ref>

Patents on arithmetic coding may exist in other jurisdictions; see [[software patent]]s for a discussion of the patentability of software around the world.

==Benchmarks and other technical characteristics==
Every programmatic implementation of arithmetic encoding has a different compression ratio and performance. While compression ratios vary only a little (usually under 1%),<ref>For instance, {{harvtxt|Howard|Vitter|1994}} discuss versions of arithmetic coding based on real-number ranges, integer approximations to those ranges, and an even more restricted type of approximation that they call binary quasi-arithmetic coding. They state that the difference between real and integer versions is negligible, prove that the compression loss for their quasi-arithmetic method can be made arbitrarily small, and bound the compression loss incurred by one of their approximations as less than 0.06%. See: {{citation
 | last1 = Howard
 | first1 = Paul G.
 | last2 = Vitter
 | first2 = Jeffrey S.
 | doi = 10.1109/5.286189
 | issue = 6
 | journal = Proceedings of the IEEE
 | pages = 857–865
 | title = Arithmetic coding for data compression
 | url = http://home.tiscali.nl/rajduim/Video%20Compression%20Docs/Arithmetic%20Coding%20For%20Data%20Compression%20(2).pdf
 | volume = 82
 | year = 1994
 | access-date = 17 October 2013
 | archive-url = https://web.archive.org/web/20131018025150/http://home.tiscali.nl/rajduim/Video%20Compression%20Docs/Arithmetic%20Coding%20For%20Data%20Compression%20(2).pdf
 | archive-date = 18 October 2013
 | url-status = dead
 | hdl = 1808/7229
 | hdl-access = free
 }}.</ref> the code execution time can vary by a factor of 10. Choosing the right encoder from a list of publicly available encoders is not a simple task because performance and compression ratio depend also on the type of data, particularly on the size of the alphabet (number of different symbols). One of two particular encoders may have better performance for small alphabets while the other may show better performance for large alphabets. Most encoders have limitations on the size of the alphabet and many of them are specialized for alphabets of exactly two symbols (0 and 1).

==Notes==
<references/>

==References==
* {{cite book
 |last=MacKay 
 |first=David J.C. 
 |author-link=David MacKay (scientist) 
 |title=Information Theory, Inference, and Learning Algorithms 
 |chapter=Chapter 6: Stream Codes 
 |chapter-url=http://www.inference.phy.cam.ac.uk/mackay/itila/book.html 
 |chapter-format=PDF/[[PostScript]]/[[DjVu]]/[[LaTeX]] 
 |access-date=30 December 2007 
 |date=September 2003 
 |publisher=[[Cambridge University Press]] 
 |isbn=0-521-64298-1 
 |archive-url=https://web.archive.org/web/20071222053346/http://www.inference.phy.cam.ac.uk/mackay/itila/book.html 
 |archive-date=22 December 2007 
 |url-status=dead 
}}
*{{Cite book | last1=Press | first1=WH | last2=Teukolsky | first2=SA | last3=Vetterling | first3=WT | last4=Flannery | first4=BP | year=2007 | title=Numerical Recipes: The Art of Scientific Computing | edition=3rd | publisher=Cambridge University Press | location=New York | isbn=978-0-521-88068-8 | chapter=Section 22.6. Arithmetic Coding | chapter-url=http://apps.nrbook.com/empanel/index.html#pg=1181 | access-date=18 August 2011 | archive-date=11 August 2011 | archive-url=https://web.archive.org/web/20110811154417/http://apps.nrbook.com/empanel/index.html#pg=1181 | url-status=dead }}
* {{cite journal
  | doi = 10.1147/rd.203.0198
  | last = Rissanen
  | first = Jorma
  | author-link = Jorma Rissanen
  | title = Generalized Kraft Inequality and Arithmetic Coding
  | journal = IBM Journal of Research and Development
  | volume = 20
  | issue = 3
  | pages = 198–203
  |date=May 1976
  | url = http://domino.watson.ibm.com/tchjr/journalindex.nsf/4ac37cf0bdc4dd6a85256547004d47e1/53fec2e5af172a3185256bfa0067f7a0?OpenDocument
  | access-date = 21 September 2007 }}
* {{cite journal
  | doi = 10.1147/rd.232.0149
  | last = Rissanen
  | first = J.J.
  | author2 = Langdon G.G., Jr
  | title = Arithmetic coding
  | journal = IBM Journal of Research and Development
  | volume = 23
  | issue = 2
  | pages = 149–162
  | date = March 1979
  | s2cid = 39909636
 | url = http://researchweb.watson.ibm.com/journal/rd/232/ibmrd2302G.pdf
  | access-date = 22 September 2007
  | archive-url = https://web.archive.org/web/20070928023306/http://researchweb.watson.ibm.com/journal/rd/232/ibmrd2302G.pdf
  | archive-date = 28 September 2007
  | url-status = dead
  }}
* {{cite journal
  | last = Witten
  | first = Ian H.
  |author2= Neal, Radford M.|author3= Cleary, John G.
  | title = Arithmetic Coding for Data Compression
  | journal = [[Communications of the ACM]]
  | volume = 30
  | issue = 6
  | pages = 520–540
  |date=June 1987
  | url = http://www.stanford.edu/class/ee398a/handouts/papers/WittenACM87ArithmCoding.pdf
  | access-date = 21 September 2007
  | doi = 10.1145/214762.214771| s2cid = 3343393
 | archive-url= https://web.archive.org/web/20070928023306/http://www.stanford.edu/class/ee398a/handouts/papers/WittenACM87ArithmCoding.pdf| archive-date= 28 September 2007 | url-status= live}}

* Rodionov Anatoly, Volkov Sergey (2010) "p-adic arithmetic coding" Contemporary Mathematics Volume 508, 2010 Contemporary Mathematics
* Rodionov Anatoly, Volkov Sergey (2007) "p-adic arithmetic coding", [https://arxiv.org/abs//0704.0834v1 P-adic arithmetic coding]
*  LANGUAGE MODELING IS COMPRESSION https://arxiv.org/pdf/2309.10668

==External links==
* {{DADS|Arithmetic coding|arithmeticCoding}}
* [http://www.gtoal.com/wordgames/documents/arithmetic-encoding.mai Newsgroup posting] with a short worked example of arithmetic encoding (integer-only).
* [https://web.archive.org/web/20030228094950/http://planetmath.org/encyclopedia/ArithmeticEncoding.html PlanetMath article on arithmetic coding]
* [http://ezcodesample.com/reanatomy.html Anatomy of Range Encoder] The article explains both range and arithmetic coding. It has also code samples for 3 different arithmetic encoders along with performance comparison.
*[http://hpl.hp.com/techreports/2004/HPL-2004-76.pdf Introduction to Arithmetic Coding] {{Webarchive|url=https://web.archive.org/web/20201109031919/http://hpl.hp.com/techreports/2004/HPL-2004-76.pdf |date=9 November 2020 }}. 60 pages.
* [[Eric Bodden]], Malte Clasen and Joachim Kneis: [http://www.sable.mcgill.ca/publications/techreports/#report2007-5 Arithmetic Coding revealed]. Technical Report 2007-5, Sable Research Group, McGill University.
* [https://web.archive.org/web/19990428180948/http://dogma.net/markn/articles/arith/part1.htm Arithmetic Coding + Statistical Modeling = Data Compression] by Mark Nelson.
* [https://marknelson.us/posts/2014/10/19/data-compression-with-arithmetic-coding.html Data Compression With Arithmetic Coding] by Mark Nelson (2014)
* [https://github.com/jkbonfield/rans_static Fast implementation of range coding and rANS] by James K. Bonfield
{{Compression Methods}}

[[Category:Entropy coding]]
[[Category:Data compression]]