 2 bit pattern: 00, 01, 10, or 11), and a byte equal to 0x03 is inserted to replace these bit patterns with the patterns: '00000000 00000000 00000011 000000xx', and finally, when the last byte of the RBSP data is equal to 0x00 (which can only occur when the RBSP ends in a cabac_zero_word), a final byte equal to 0x03 is appended to the end of the data. The last zero byte of a byte-aligned three-byte sequence 0x000000 in the RBSP (which is replaced by the four-byte sequence 0x00000300) is taken into account when searching the RBSP data for the next occurrence of byte-aligned bits with the binary patterns specified above. The resulting sequence of bytes is then prefixed as follows: If nal_unit_type is not equal to 14 or 20, the sequence of bytes is prefixed with the first byte of the NAL unit containing the syntax elements forbidden zero bit nal_ref_idc, and nal_unit_type, where nal_unit_type indicates the type of RBSP data structure the NAL unit contains. Otherwise (nal_unit_type is equal to 14 or 20), the sequence of bytes is prefixed with the first four bytes of the NAL unit, where the first byte contains the syntax elements forbidden_zero_bit,nal_ref_idc, and nal_unit_type and the following three bytes contain the syntax structure nal_unit_header_svc_extension) The syntax element nal_unit_type in the first byte indicates the presence of the syntax structure nal_unit_header_svC_extension() in the following three bytes and the type of RBSP data structure the NAL unit contains. The process specified above results in the construction of the entire NAL unit. Rec. ITU-T H.264 (01/2012) This process can allow any SODB to be represented in a NAL unit while ensuring that no byte-aligned start code prefix is emulated within the NAL unit, no sequence of 8 zero-valued bits followed by a start code prefix, regardless of byte-alignment, is emulated within the NAL unit. 7.4.1.2 Order of NAL units and association to coded pictures, access units, and video sequences This clause specifies constraints on the order of NAL units in 