Patent Grant
8055500
1. Field of the Invention
An embodiment of the present invention relates to a method, medium, and apparatus encoding/decoding audio data, and more particularly, to a method, medium, and apparatus encoding/decoding audio data with extension data that can be used to extend the audio data.
2. Description of the Related Art
When encoding and/or decoding audio data, the audio data can be processed using extension data that provides information for extending the available uses for the audio data. As an example, extension data may include data for extending a channel of audio data, data for extending a bandwidth of audio data, data for generating a code for checking for transmission errors in the received audio data, etc. In addition, extension data may further include metadata of audio data, a fill element of audio data, etc.
A portion of the syntax identified by reference numeral 100 in
However, multi-channel audio coding, which can be a very useful Spectral Band Replication (SBR) tool, cannot be implemented by the conventional syntax of
An embodiment of the present invention provides an apparatus, medium, and method allows for nearly unlimited extensibility of audio data while providing backward compatibility.
Additional aspects and/or advantages of the invention will be set forth in part in the description which follows and, in part, will be apparent from the description, or may be learned by practice of the invention.
To achieve at least the above and/or other aspects and advantages, embodiments of the present invention include an encoding method, including encoding audio data using at least one encoding method, and encoding at least one extension data for the audio data using at least one encoding method.
In the encoding of the audio data, the audio data may be hierarchically encoded using a first encoding method, and in the encoding of the at least one extension data, the at least one extension data may be encoded using at least one encoding method, including the first encoding method.
In addition, the encoding of the at least one extension data may include encoding data for extending a channel of the audio data. Further, the encoding of the at least one extension data may include encoding data for extending a bandwidth of the audio data. Still further, the encoding of the at least one extension data may include at least one of hierarchically encoding data for extending a channel of the audio data and encoding data for extending a bandwidth of the audio data.
The encoding of the at least one extension data may still further include encoding data for extending a bandwidth of the audio data and encoding a code for checking for transmission errors of the audio data.
The method may further include generating a code indicating a type of the at least one extension data, wherein the encoding of at the least one extension data is performed using at least one encoding method according to the generated code.
Here, the type of the at least one extension data may be at least one selected from a type of data for extending a channel of the audio data, a type of data for extending a bandwidth of the audio data, a type of data for checking for transmission errors of the audio data, metadata of the audio data, and a fill element of the audio data.
The method may further include generating a first code indicating a start of an encoded portion of the at least one extension data, and generating a second code indicating a type of the at least one extension data.
Here, the method may further include inserting a third code indicating an end of an encoded portion of the audio data, immediately after the encoded portion of the audio data, wherein the generating of the first code further includes inserting the first code after the inserted third code, and the generating of the second code further includes inserting the second code after the inserted first code.
The first code may be a 4-bit code with four consecutive identical bits, and the second code may be a different 4-bit code.
In addition, the method may include inserting a code indicating a type of different extension data after an encoded portion of the at least one extension data, and encoding the at least one extension data, wherein the adding of the code and the encoding of the least one extension data are repeatedly performed until all extension data are encoded.
To achieve at least the above and/or other aspects and advantages, embodiments of the present invention include at least one medium including computer readable code to control at least one processing element to implement an embodiment of the present invention.
To achieve at least the above and/or other aspects and advantages, embodiments of the present invention include at least one medium including bitstream information to control a decoding apparatus to decode encoded audio data, the bistream including the encoded audio data encoded using at least one encoding method, and at least one encoded extension data for the audio data using at least one encoding method.
The bitstream information may further include at least one code with information for any of a start of an encoded portion of the at least one extension data, information identifying a type of the at least one encoded extension data, and information of an end of an encoded portion of the audio data.
Here, the code indicating the end of the encoded portion of the audio data may immediately follow the encoded portion of the audio data, followed immediately by the code for the start of the encoded portion of the at least one extension data, followed immediately by the code identifying the type of the at least one encoded extension data.
To achieve at least the above and/or other aspects and advantages, embodiments of the present invention include an encoding apparatus, including a first encoding unit to encode audio data using at least one encoding method, and a second encoding unit to encode at least one extension data for the audio data using at least one encoding method.
To achieve at least the above and/or other aspects and advantages, embodiments of the present invention include a decoding method, including decoding audio data using at least one decoding method, and decoding at least one extension data for the audio data using at least one decoding method.
Here, in the decoding of the audio data, the audio data may be hierarchically decoded using a first decoding method, and in the decoding of the at least one extension data, the at least one extension data may be decoded using at least one decoding method, including the first decoding method.
The decoding of the at least one extension data may include decoding data for extending a channel of the audio data. In addition, the decoding of the at least one extension data may include decoding data for extending a bandwidth of the audio data. Still further, the decoding of the at least one extension data may include at least one of hierarchically decoding data for extending a channel of the audio data and decoding data for extending a bandwidth of the audio data.
The decoding of the at least one extension data may further include decoding data for extending a bandwidth of the audio data and decoding a code for checking for transmission errors of the audio data.
In addition, the method may include detecting a code indicating a type of the at least one extension data, wherein, when the code indicating the type of the at least one extension data is detected, the decoding of the at least one extension data is performed using at least one decoding method according to the generated code.
Here, the type of the at least one extension data may be at least one selected from a type of data for extending a channel of the audio data, a type of data for extending a bandwidth of the audio data, a type of data for checking for transmission errors of the audio data, metadata of the audio data, and a fill element of the audio data.
The decoding method may further include detecting a first code indicating a start of an encoded portion of the at least one extension data, and detecting a second code indicating a type of the at least one extension data.
Here, the decoding method may further include detecting a third code indicating an end of an encoded portion of the audio data, immediately after the encoded portion of the audio data, wherein the detecting of the first code further includes detecting the first code after the third code if the third code is detected, and the detecting of the second code further includes detecting the second code after the first code if the first code is detected.
The first code may be a 4-bit code with four consecutive identical bits, and the second code may be a different 4-bit code.
The decoding method may further include detecting a code indicating a type of different extension data after an encoded portion of the at least one extension data, and decoding the at least one extension data using a decoding method according to the detected code if the code indicating the type of the different extension data is detected, wherein the detecting of the code and the decoding of the at least one extension data are repeatedly performed until all of the at least one extension data are decoded.
To achieve at least the above and/or other aspects and advantages, embodiments of the present invention include a decoding apparatus, including a first decoding unit to decode audio data using at least one decoding method, and a second decoding unit to decode at least one extension data for the audio data using at least one decoding method.
These and/or other aspects and advantages of the invention will become apparent and more readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawings of which:
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like reference numerals refer to the like elements throughout. Embodiments are described below to explain the present invention by referring to the figures.
The audio data encoding unit 200 may encode audio data input through an input data IN and then hierarchically encode the audio data, for example.
Here, the audio data encoding unit 200 may perform bit sliced arithmetic coding (BSAC), as only an example of hierarchical coding. Audio data having a frequency band corresponding to a base layer may initially be encoded, and then audio data having a frequency band corresponding to an upper layer next to the base layer may then be encoded. In an embodiment, this encoding may be repeated until audio data having frequency bands corresponding to all the remaining layers are completely encoded. In particular, a lower frequency band that is detectable by human ears may be assigned to be the base layer, and a higher frequency band may be assigned to be an upper layer. In addition, according to an embodiment, a lower bit rate may be assigned to the lower layer, thereby increasing the transmission reliability of the lower layer, as the base layer most affecting a human's hearing, for example, and allowing smooth transmission in inferior transmission environments. In addition, the number of upper layers and corresponding bit rates may be assigned depending on the audio data transmission environment to provide fine grain scalability (FGS).
When an audio data input to the audio data encoding unit 200 is a multi-channel signal, the audio data encoding unit 200 may select on the multi-channel signal to obtain a stereo signal, and encode the audio data. For example, the audio signal may be encoded after the multi-channel signal is selected into a front-right channel audio signal and a front-left channel audio signal.
Once the audio data encoding unit 200 has completed the encoding of the audio data, the termination code generating unit 210 may generate a termination code to indicate the termination of a payload of the encoded data. In an embodiment, the termination code may be located immediately after the payload of the encoded audio data. In such an embodiment, such as in the syntax of
When extension data of the audio data, e.g., as encoded by the audio data encoding unit 200, is encoded, the start code generating unit 220 may generate a start code to identify a start of a payload of the extension data. As an example, the start code generated by the start code generating unit 220 may be inserted into a start portion of the payload of the extension data. Again, in an embodiment, such as the syntax of
The extension data encoding unit 230 may encode extension data of encoded audio data, e.g., as encoded by the audio data encoding unit 200. Here, the extension data refers to data used to process audio data so as to extend the available applications of the audio data. For example, the extension data may include at least one of data for extending the bandwidth of the audio data, data for extending the bandwidth of the audio data, data for generating a code for checking for transmission errors of the data, etc. When extending the bandwidth of the audio data, a Spectral Band Replication (SBR) tool may be used, and a cyclic redundancy checksum (CRC) code may be used as a code for checking for transmission errors of the data, for example.
The extension data encoding unit 230 may further include an extension type code generating portion 232, a bandwidth extension data encoding portion 234, an error check code generating portion 236, and a channel extension data encoding portion 238, for example.
Here, the extension type code generating portion 232 may generate an extension type code to indicate the type of extension data to be encoded by the extension data encoding unit 230. Again, the extension type code is data indicating whether the available applications of the audio data will be extended for a specific purpose. The extension type code generating portion 232 may generate an extension type code that corresponds to the type of the extension data and may be located before the payload of the extension data. Here, the extension type code generating portion 232 may repeatedly generate extension type codes until all the extension data are encoded. For example, in the syntax of
Thus, in this embodiment, one of the reserved values from ‘0010’ to ‘1100’ may be designated as a type of extension data. For example, extension data of audio data may indicate that the audio data is metadata or a fill element, with examples of the metadata of the audio data including a type or words of audio data, etc, and the fill element referring to insignificant bits added to a bitstream to meet a predetermined packet size.
Here, in addition to the above, alternative extension data of audio data may include any other type, in addition to the above-listed extension types.
The bandwidth extension data encoding portion 234 may encode only a predetermined bandwidth of the audio data or a multi-channel audio data, e.g., as encoded by the audio data encoding unit 200, so that the bandwidth of the audio data can be extended in the decoding unit. In particular, the bandwidth extension data encoding portion 234 may encode audio data having a low-frequency band and a multi-channel audio data so that an audio signal having a high-frequency band can be decoded in the decoding unit.
In a method of extending the bandwidth of the audio data, a SBR tool may be used. Here, the SBR tool is a tool of estimating audio data having a high frequency band corresponding to an upper layer separately from audio data having a low frequency band corresponding to a base layer, using the fact that the low frequency band and the high frequency band of the audio data are highly correlated. In other words, information indicating a correlations between the audio data having a maximum frequency of f1 in the base layer and the audio data having a maximum frequency of Fn in the upper layer is encoded. Here, the maximum frequency fn of the audio data may be equal to or greater than a maximum frequency fk of an uppermost layer. In general, the original audio data may include audio data that is not included in the uppermost layer, as the maximum frequency fn of the audio signal may be greater than the maximum frequency fk of the uppermost layer.
Again referring to
The channel extension data encoding portion 238 may further encode data that may be used to extend the channel of the audio data in the decoding unit.
In an one embodiment, the bitstream formatter 240 may generate a bitstream from the payload and the codes generated by the encoding in the audio data encoding unit 200, the termination code generating unit 210, the start code generating unit 220, and the extension data encoding unit 230, for example, and output the bitstream through an output terminal OUT. The bitstream formatter 240 may generate the bitstream by sequentially multiplexing the payload of the audio data and the termination code, for example. Here, when the extension data is encoded, in addition to the payload of the audio data and the termination code, a start code, a code indicating the type of a first extension data, a payload of the encoded first extension data, a code indicating the type of a second extension data, a payload of the encoded second extension data, . . . , a code indicating the type of an Nth extension data, and a payload of the encoded Nth extension data may be sequentially multiplexed to generate the bitsteam.
Referring to
In an embodiment of such a hierarchical encoding, in operation 500, the audio data may be encoding using BSAC, for example. Data having a frequency band corresponding to a base layer, among the audio data, may be encoded first, and data having a frequency band corresponding to an upper layer, e.g., next to the base layer, may be next encoded. Thereafter, encoding may be repeatedly performed until data corresponding to all the remaining layers are completely encoded. Here, a low frequency bandwidth, e.g., which may be detectable by human ears, may be determined to be the base layer, and a higher frequency band may be determined to be the upper layer. In one embodiment, a lower bit rate may be allocated to the lower layer, thereby increasing the transmission reliability in the lower layer, such as the base layer, thereby allowing smooth transmission in a very poor transmission environments. In addition, the number of upper layers and the corresponding bit rates may be determined according to the corresponding transmission environments of the audio data, thereby ensuring fine grain scalability (FGS).
According to an embodiment, in operation 500, when the input audio signal is a multi-channel signal, the encoding may be performed after the multi-channel signal is selected into a stereo signal. For example, after selecting the audio signal of a FR channel and the audio signal of a FL channel, audio data corresponding to a stereo may be encoded.
When the encoding of the audio signal has completed, a termination code indicating an end of the payload of the encoded audio data may be generated, in operation 510. Here, the termination code may be located immediately after the payload of the encoded audio data, for example. According to an embodiment shown in the syntax of
After operation 510, it may be determined whether to encode extension data of the encoded audio data, e.g., as encoded in operation 500, in operation 520. Here, as noted above, the extension data refers to data used to process the audio data so as to extend the available uses of the audio data for a specific purpose.
If it is determined in operation 520 to encode the extension data, a start code to indicate a start of a payload of the extension data may be generated, in operation 530. According to an embodiment, this start code may be inserted where the payload of the extension data starts. In addition, according to the embodiment shown in the syntax of
After operation 530, an extension type code indicating the type of the extension data to be encoded may be generated, in operation 540. Here, the extension type code may be data indicating whether the available uses of the audio data will be extended for a specific purpose.
Extension data corresponding to the extension type code, generated in operation 540, may further be encoded, in operation 550.
After operation 550, it may be determined whether there is additional extension data to be encoded, in operation 560.
If it is determined that there is additional extension data to be encoded, operations 540 to 560 may be repeatedly performed, for example.
If it is determined that there is no additional extension data to be encoded, a bitstream may be generated, according to an embodiment, by sequentially multiplexing the payload of the encoded audio data and the termination code, in operation 570. When all the extension data are encoded, the bitstream may be generated by sequentially multiplexing the start code, an extension type code indicating the type of a first extension data, a payload of the of the encoded first extension data, an extension type code indicating the type of a second extension data, . . . , an extension type code indicating the type of an Nth extension data, and a payload of the encoded Nth extension data, in addition to the above-described payload and the termination code, for example.
According to this embodiment, after the above operation 530, it is determined whether the extension data to be encoded is data for extending the channel of the audio data encoded by BSAC, which is simply expressed as ‘BSAC channel extension’, operation 600.
If it is determined that the extension data is data for the ‘BSAC channel extension’, code ‘1111’ may be generated as a value of “extension_type”, indicating the type of the audio data, in operation 610. After operation 610, the extension data for extending the channel of the audio data may be encoded, in operation 620. A payload of the extension data, e.g., as encoded in operation 620, may be located immediately after the extension type code ‘1111’, e.g., as generated in operation 610.
If it is determined that the extension data is not data for expanding the channel of the audio data, it is determined whether the extension data to be encoded is data for extending the bandwidth of the audio data, which may be simply expressed as ‘BSAC SBR enhancement’, in operation 601.
If it is determined that the extension data is data for extending the bandwidth of the audio data, code ‘0000’ may be generated as a value of “extension_type”, indicating the type of the audio data, in operation 611. After operation 611, the extension data for extending the bandwidth of the audio data may be encoded, in operation 621. According to an embodiment, the payload of the extension data, e.g., as encoded in operation 621, may be located immediately after the extension type code ‘0000’ generated in operation 611.
If it is determined that the extension data is not data for extending the bandwidth of the audio data, it is determined whether the extension data to be encoded is data for extending the bandwidth of the audio data and generating a CRC code for checking for transmission errors of the extension data of extending the bandwidth of audio data, which may simply be expressed as ‘BSAC SBR enhancement with CRC’, in operation 602.
If it is determined that the extension data to be encoded includes data for extending the bandwidth of the audio data and data for generating a CRC code for checking for transmission errors of the audio data, code ‘0001’ may be generated as a value of “extension_type”, indicating the type of the extension data, in operation 612. After operation 612, the data for extending the bandwidth of the audio data may be encoded, in operation 622, and the data for generating the CRC code for checking for transmission errors of the extension data of extending the bandwidth of audio data may be encoded, in operation 623. According to an embodiment, the payload of the extension data, e.g., as encoded in operations 622 and 623, may be located immediately after the extension type code ‘0001’ generated in operation 612.
If it is determined that the extension data to be encoded is not data for extending the bandwidth of the audio data and generating a CRC code for checking for transmission errors of the extension data of extending the bandwidth of audio data, it may be determined whether the extension data to be encoded is data for extending the channel and the bandwidth of the audio data in operation 603.
If it is determined that the extension data includes data for extending the channel of the audio data and data for extending the bandwidth of the audio data, code ‘1110’ may be generated as a value of “extension_type”, indicating the type of the extension data, in operation 613. After operation 613, the data for extending the channel of the audio data may be encoded, in operation 624, and the data for extending the bandwidth of the audio data may be encoded, in operation 625. According to an embodiment, the payload of the extension data, e.g., as encoded in operations 624 and 625, may be located immediately after the extension code type ‘1110’ generated in operation 613.
If it is determined that the extension data does not include data for extending the channel of the audio data and data for extending the bandwidth of the audio data, it may be determined in operation 604 whether the extension data to be encoded includes data for extending the channel of the audio data, data for extending the bandwidth of the audio data, and data for generating a CRC code for checking a transmission error of the extension data of extending the bandwidth of audio data, which may be simply expressed as ‘BSAC channel extension with SBR_CRC’, for example.
If it is determined that the extension data includes data for extending the channel of the audio data, data for extending the bandwidth of the audio data, and data for extending the bandwidth of the audio data, code ‘1101’, as a value of “extension_type”, indicating the type of the extension data, may be generated in operation 614. After operation 614, the data for extending the channel of the audio data may be encoded, in operation 626, the data for extending the bandwidth of the audio data may be encoded, in operation 627, and the data for generating a CRC code for checking a transmission error of the extension data of extending the bandwidth of audio data may be encoded, in operation 628. According to an embodiment, the payload of the extension data, e.g., as encoded in operations 626, 627, and 628, may be immediately located after the extension code type ‘1101’ generated in operation 614.
If it is determined that the extension data does not include data for extending the channel of the audio data, data for extending the bandwidth of the audio data, and data for generating a CRC code for checking a transmission error of the audio data, a predetermined code ‘0010’ or ‘1100’ may be generated in operation 615. A type of extension data corresponding to the code generated in operation 615 may further be encoded in operation 629.
The bitstream deformatter 700 may receive and deformat a bitstream, e.g., as transmitted from an encoding unit through an input terminal IN, and output a payload.
The audio data decoding unit 710 may decode audio data in the payload output from the bitstream deformatter. According to an embodiment, the audio data decoding unit 710 may decode hierarchically encoded audio data.
The audio data decoding unit 710 may decode hierarchically encoded audio data using a BSAC method, for example. Here, according to an embodiment of the present invention, the audio data decoding unit 710 may perform a process indicated by reference numeral 1100 in the syntax shown in
Once the decoding of the audio data is completed, the audio data decoding unit 710 may align the decoded audio data in units of bytes. After the decoded data are aligned in units of bytes, the audio data decoding unit 710 may then fill the remaining portion with dummy data. According to an embodiment, the audio data decoding unit 710 may further perform a process indicated by reference numeral 1105 in the syntax shown in
If it is determined that there is an undecoded payload, after the decoding in the audio data decoding unit 710, the termination code detecting unit 720 may detect a termination code indicating the end of the payload of the encoded data in the deformatted payload. According to an embodiment, in a syntax using BSAC, the termination code may be implemented as ‘zero_code’. Here, this ‘zero_code’ may be required to terminate arithmetic decoding and may include 32 consecutive ‘0’s. The termination code detecting unit 720 may, thus, perform a process indicated by reference numeral 1105 shown in the syntax of
The start code detecting unit 730 may detect a start code indicating a start of extension data in the payload deformatted by the bitstream deformatter 700. According to an embodiment, in a syntax using BSAC, the start code may be implemented as ‘sync_word’, with this ‘sync_word’ being a 4-bit code having 4 consecutive ‘1’s. The start code detecting unit 730 may, thus, perform a process indicated by reference numeral 1120 shown in the syntax of
If is determined that the number of bits in the undecoded payload is greater than a predetermined value, the extension type code detecting unit 740 may detect an extension type code indicating the type of the extension data. Here, as noted above, the extension type code is data indicating whether the available uses of the audio data will be extended for a specific purpose. The extension type code detecting unit 740 may, thus, perform a process indicated by reference numeral 1130 shown in the syntax of
The determination as to whether the number of bits in the undecoded payload is greater than a predetermined value may be performed by the extension type code detecting unit 740, e.g., according to a process indicated by reference numeral 1125 shown in the syntax of
The extension data decoding unit 750 may decode extension data corresponding to the extension type code detected by the extension type code detecting unit 740. The extension data decoding unit 750 may, thus, perform processes indicated by reference numerals 1140 through 1197 shown in the syntax of
The extension data decoding unit 750 may determine whether the extension code type detected by the extension type code detecting unit 740 is defined in the decoding unit. This, thus, may be performed according to a process indicated by reference numeral 1196 shown in the syntax of
If it is determined that the extension type code is defined in the decoding unit, one of a first extension data decoding portion 751, . . . , and an Nth extension data decoding portion 758, in the extension data decoding unit 750, decodes extension data corresponding to the extension type code detected by the extension type code detecting unit 740.
If the number of bits in the undecoded payload is determined to be greater than the predetermined value, after the extension data decoding unit 750 decodes the extension data, the extension type code detecting unit 740 and the extension data decoding unit 750 may repeatedly perform the above-described processes. If the number of bits in the undecoded payload is determined to be equal to or greater than the predetermined value, the data alignment unit 760 may align the extension data decoded by the extension data decoding unit 750 in units of bytes. The data alignment unit 760 may further fill the remaining bytes with dummy data. This process, thus, may be indicated by reference numeral 1198 shown in the syntax of
If the extension type code, e.g., detected by the extension type code detecting unit 740, is ‘1111’, a channel extension data decoding portion 800 may decode extension data for extending the channel of the audio data.
If the extension type code, e.g., detected by the extension type code detecting unit 740, is ‘0000’, an SBR data decoding portion 820 may decode extension data for extending the bandwidth of the audio data using an SBR tool, for example.
If the extension type code, e.g., detected by the extension type code detecting unit 740, is ‘0001’, a CRC data decoding portion 810 may decode extension data for generating a CRC code for checking for transmission errors of the extension data of extending the bandwidth of audio data, and the SBR data decoding portion 820 may decode the extension data for extending the bandwidth of the audio data using an SBR tool, for example.
If the extension type code, e.g., detected by the extension type code detecting unit 740, is ‘1110’, the channel extension data decoding portion 800 may decode extension data for expanding the channel of the audio signal, and the SBR data decoding portion 820 may decode extension data for extending the bandwidth of the audio data using an SBR tool, for example.
If the extension type code, e.g., detected by the extension type code detecting unit 740, is ‘1101’, the channel extension data decoding portion 800 may decode extension data for expanding the channel of the audio data, the CRC data decoding portion 810 may decode extension data for generating a CRC code for checking for transmission errors of the extension data of extending the bandwidth of audio data, and the SBR data decoding portion 820 may decode extension data for expanding the bandwidth of the audio data using an SBR tool, for example.
Initially, a transmitted bitstream may be deformatted, and a payload in the bitstream output, in operation 900.
Audio data in the payload, output in operation 900, may be decoded, in operation 903. Here, according to an embodiment, in operation 903, hierarchically encoded audio data may be decoded.
In operation 903, such encoded audio data may be decoded according to a BSAC method, e.g., according to a process indicated by reference numeral 1100 shown in the syntax of
The audio data decoded in operation 903 may be aligned in units of bytes, in operation 905, with remaining portions of the audio data that are not aligned being filled with dummy data. Here, according to an embodiment, operation 905 may be performed according to a process indicated by reference numeral 1105 shown in the context of
After operation 905, it may be determined whether there is undecoded data in the payload, e.g., output in operation 900, in operation 910. Here, according to an embodiment, operation 910 may be performed according to a process indicated by reference numeral 1110 shown in syntax of
If it is determined that the payload does not include undecoded data, the decoding of the bitstream, e.g., as received in operation 900, may be terminated.
If it is determined that the payload includes undecoded data, a termination code indicating a end of the payload of the encoded audio data may be detected from the payload, e.g., as deformatted in operate 900, in operation 915. In a syntax using BSAC, the termination code may be implemented as ‘zero_code’. Here, this ‘zero_code’ may be required for arithmetic decoding and have 32 consecutive ‘0’s. According to an embodiment, operation 915 may be performed according to a process indicated by reference numeral 1105 shown in the syntax of
After operation 915, a start code indicating a start of the extension data may be detected in the deformatted payload, in operation 920. In a syntax using BSAC, the start code may be implemented as ‘sync_word’, with this ‘sync_word’ being a 4-bit code having 4 consecutive 1's. According to an embodiment, operation 920 may be performed according to a process indicated by reference numeral 1120 shown in the syntax of
After operation 920, it may be determined whether the number of bits in the undecoded payload is greater than a predetermined value, in operation 925. Here, according to an embodiment, operation 925 may be performed according to a process indicated by reference numeral 1125 shown in the syntax of
If it is determined that the number of bits in the undecoded payload is equal to or smaller than the predetermined value, extension data to be decoded in operation 940 may be aligned in units of bytes, in operation 950. The remaining portion of bytes, in which the extension data is not aligned in units of bytes, may be filled with dummy data. According to an embodiment, operation 950 may be performed according to a process indicated by reference numeral 1198 shown in the syntax of
If it is determined that the number of bits in the undecoded payload is greater than the predetermined value, an extension type code indicating the type of the extension data encoded in the encoding unit may be detected, in operation 930. Here, as noted above, the extension type code is data indicating whether the available uses of the audio data will be extended for a specific purpose. According to an embodiment, operation 930 may be performed according to a process indicated by reference numeral 1130 shown in the syntax of
It may further be determined whether the extension type code, detected in operation 930, is defined in the decoding unit, in operation 935. Here, according to an embodiment, operation 935 may be performed according to a process indicated by reference numeral 1196 shown in the syntax of
If it is determined that the detected extension type code is defined in the decoding unit, extension data corresponding to the extension type code detected in operation 930 may be decoded, in operation 940. Here, according to an embodiment, operation 940 may be performed according to processes indicated by reference numerals 1140 through 1195 shown in the syntax of
If it is determined that the detected extension type code is not defined in the decoding unit, a number of bits that is equal to the number of bits of the extension data, corresponding to the extension type code detected in operation 930, may be discarded, in operation 945. Here, according to an embodiment, operation 945 may be performed according to a process indicated by reference numeral 1197 shown in the syntax of
After operation 940 or operation 950, operation 925 may be repeatedly performed.
It may be determined whether the extension type code, e.g., detected in operation 930, is ‘1111’, in operation 1000. Here, according to an embodiment, operation 1000 may be performed according to a process indicated by reference numeral 1140 shown in the syntax of
If it is determined that the extension type code is ‘1111’, extension data for extending the channel of the audio data may be decoded, in operation 1001. Here, according to an embodiment, operation 1001 may be performed according to a process indicated by reference numeral 1145 shown in the syntax of
If it is determined that the extension type code is not ‘1111’, it may be determined whether the extension type code detected in operation 930 is ‘1010’, in operation 1010. Here, according to an embodiment, operation 1010 may be performed according to a process indicated by reference numeral 1150 shown in the syntax of
If it is determined that the extension type code is ‘0000’, extension data for extending the bandwidth of the audio data may be decoded, in operation 1011. Here, according to an embodiment, operation 1011 may be performed according to a process indicated by reference numeral 1155 shown in the syntax of
If it is determined that the extension type code is not ‘1010’, it may be determined whether the extension type code detected in operation 930 is ‘0001’, in operation 1020. Here, according to an embodiment, operation 1020 may be performed according to a process indicated by reference numeral 1160 shown in the syntax of
If it is determined that the extension type code is ‘0001’, extension data for generating a CRC code for checking for transmission errors of the extension data of extending the bandwidth of audio data may be decoded, in operation 1021. After operation 1021, extension data for extending the bandwidth of the audio data may be decoded, in operation 1022. Here, according to an embodiment, operations 1021 and 1022 may be performed according to a process indicated by reference numeral 1165 shown in the syntax of
If it is determined that the extension type code is not ‘0001’, it may be determined whether the extension type code detected in operation 930 is ‘1110’, in operation 1030. Here, according to an embodiment, operation 1030 may be performed according to a process indicated by reference numeral 1170 shown in the syntax of
If it is determined that the extension type code is ‘1110’, extension data for extending the channel of the audio data may be decoded, in operation 1031. After operation 1031, extension data for extending the bandwidth of the audio data may be decoded, in operation 1032. Here, according to an embodiment, operation 1031 may be performed according to a process indicated by reference numeral 1175 shown in the syntax of
If it is determined that the extension type code is not ‘1110’, it may be determined whether the extension type code detected in operation 930 is ‘1101’, in operation 1040. Here, according to an embodiment, operation 1040 may be performed according to a process indicated by reference numeral 1185 shown in the syntax of
If it is determined that the extension type code is ‘1101’, extension data for extending the channel of the audio data may be decoded, in operation 1041. After operation 1041, extension data for generating a CRC code for checking for transmission errors of the extension data of extending the bandwidth of audio data may be decoded, in operation 1042. After operation 1042, extension data for extending the bandwidth of the audio data may be decoded, in operation 1043. Here, according to an embodiment, operation 1041 may be performed according to a process indicated by reference numeral 1190 shown in the syntax of
In addition to the above described embodiments, embodiments of the present invention can also be implemented through computer readable code/instructions in/on a medium, e.g., a computer readable medium, to control at least one processing element to implement any above described embodiment. The medium can correspond to any medium/media permitting the storing and/or transmission of the computer readable code.
The computer readable code can be recorded/transferred on a medium in a variety of ways, with examples of the medium including magnetic storage media (e.g., ROM, floppy disks, hard disks, etc.), optical recording media (e.g., CD-ROMs, or DVDs), for example. The media may also be a distributed network, so that the computer readable code is stored/transferred and executed by the distributed network. Still further, as only an example, the processing element could include a processor or a computer processor, and processing elements may be distributed and/or included in a single device.
According to an embodiment of the present invention, audio data may be hierarchically encoded, and at least one extension data of the audio data encoded using at least one encoding method and decoded in a similar manner, thereby ensuring FGS and unlimited extendibility of the audio data.
In addition, according to an embodiment of the present invention, a 4-bit sync_word indicating a start of encoded extension data and a 4-bit extension_type indicating a type of the extension data, which form a 8-bit extension type code, have been set forth. Therefore, as an example, embodiments of the present invention have backward compatibility relating to the conventional syntax of
Although a few embodiments of the present invention have been shown and described, it would be appreciated by those skilled in the art that changes may be made in these embodiments without departing from the principles and spirit of the invention, the scope of which is defined in the claims and their equivalents.
| Number | Date | Country | Kind |
|---|---|---|---|
| 10-2006-0049081 | May 2006 | KR | national |
| 10-2006-0049082 | May 2006 | KR | national |
| 10-2006-0067705 | Jul 2006 | KR | national |
This application claims the priority of U.S. Provisional Application No. 60/725,317, filed on Oct. 12, 2005, and No. 60/726,159, filed on Oct. 14, 2005, and priority of Korean Patent Application Nos. 10-2006-0049081 and 10-2006-0049082, both filed on May 30, 2006, and No 10-2006-0067705, filed Jul. 19, 2006, in the Korean Intellectual Property Office, the disclosures of which are incorporated herein in their entirety by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5956674 | Smyth et al. | Sep 1999 | A |
| 6182031 | Kidder et al. | Jan 2001 | B1 |
| 6349284 | Park et al. | Feb 2002 | B1 |
| 6446037 | Fielder et al. | Sep 2002 | B1 |
| 7260225 | Teichmann et al. | Aug 2007 | B2 |
| 20040068399 | Ding | Apr 2004 | A1 |
| 20050081134 | Schroeder | Apr 2005 | A1 |
| 20060015332 | Chen et al. | Jan 2006 | A1 |
| 20060023888 | Henn et al. | Feb 2006 | A1 |
| Number | Date | Country |
|---|---|---|
| 1532809 | Sep 2004 | CN |
| 1589468 | Mar 2005 | CN |
| 1 536 410 | Jun 2005 | EP |
| 1020040086878 | Oct 2004 | KR |
| 0048402 | Aug 2000 | WO |
| 03077235 | Sep 2003 | WO |
| 03081196 | Oct 2003 | WO |
| 2004008806 | Jan 2004 | WO |
| 2004097796 | Nov 2004 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20070083363 A1 | Apr 2007 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60725317 | Oct 2005 | US | |
| 60726159 | Oct 2005 | US |
