Inputs to this process are bits from the RBSP. Outputs of this process are syntax element values. Syntax elements coded as ue(v), me(v), or se(v) are Exp-Golomb-coded. Syntax elements coded as te(v) are truncated Exp-Golomb-coded. The parsing process for these syntax elements begins with reading the bits starting at the current location in the bitstream up to and including the first non-zero bit, and counting the number of leading bits that are equal to 0. This process is specified as follows: leadingZeroBits=-1 for(b=0;!b;leadingZeroBits++) (9-1) The variable codeNum is then assigned as follows: codeNum = leadingZeroBits -1+read_bits(leadingZeroBits) (9-2) Rec. ITU-T H.264 (01/2012) where the value returned from read_bits( leadingZeroBits ) is interpreted as a binary representation of an unsigned integer with most significant bit written first. Table 9-1 illustrates the structure of the Exp-Golomb code by separating the bit string into "prefix" and "suffix" bits. The "prefix" bits are those bits that are parsed in the above pseudo-code for the computation of leadingZeroBits, and are shown as either 0 or 1 in the bit string column of Table 9-1. The "suffix" bits are those bits that are parsed in the computation of codeNum and are shown as Xi in Table 9-1, with i being in the range 0 to leadingZeroBits 1, inclusive. Each Xi can take on values 0 or 1. Table 9-1- Bit strings with "prefix" and "suffix" bits and assignment to codeNum ranges (informative) Bit string form Range of codeNum 0 1 x0 0 0 1 x 1 X0 0 0 0 1 x 2 X 1 X 0 7..14 00001X3X2 X1 X0 15..30 X4 X3 X2 X1 X0 31..62 Table 9-2 illustrates explicitly the assignment of bit strings to codeNum values. Table 9-2- Exp-Golomb bit strings and codeNum in explicit form and used as ue(v) (informative) Bit string codeNum 00100 00101 00110 00111 0001000 0001001 0001010 Depending on the descriptor, the value of a syntax element is derived as follows: If the syntax element is coded as ue(v), the value of the syntax element is equal to codeNum. Otherwise, if the syntax eleme