ISO 23002-4:2010 pdf free download – Information technology一MPEG video technologies- Part 4: Video tool library.
This part of ISO/IEC 23002 defines the MPEG video tool library, which contains tools drawn from existing MPEG coding standards, such as ISO/IEC 14496-2 and ISO/IEC 14496-10, and ISO/IEC 23001-4 defines the methods capable of describing codec configurations in the reconfigurable video coding (RVC) framework.
This part of ISO/IEC 23002 primarily addresses reconfigurable video aspects and will only focus on the description of representation of video codec configurations under the RVC framework, but could be extended to a more generic reconfigurable media coding (RMC) framework.
The objective of RVC is to offer a framework that is capable of configuring and specifying video codecs as a collection of “higher level” modules by using video coding tools. The video coding tools are defined in video tool libraries. This part of ISO/IEC 23002 defines the MPEG video tool library. The RVC framework principle could also support non-MPEG tool libraries, provided that their developers have taken care to obey the appropriate rules of operation.
For the purpose of framework deployment, an appropriate description is needed to describe configurations of decoders composed of or instantiated from a subset of video tools from either one or more libraries. As illustrated in Figure 1, the configuration information consists of
— bitstream syntax description, and
— network of functional units (FUs) description (also referred to as the decoder configuration)
that together constitute the entire decoder description.
Bitstreams of existing MPEG standards are specified by specific syntax structures and decoders are composed of various coding tools. Therefore, RVC includes support for bitstream syntax descriptions as well as video coding tools. As depicted in Figure 1, a typical RVC decoder requires two types of information, namely the decoder description and the encoded media (e.g. video bitstreams) data.
A.1 Naming convention
This Annex introduces the convention used to name FUs. Each FU has a unique name in this part of
ISO/IEC 23002.
The skeleton of FU name is in the following format:
This part is compulsory. It specifies if this Functional Unit implements a specific coding algorithm or not. If the FU is a video coding tool, the “ALGO” tag must be used (stands for “algorithmic content”). If not, the “MGNT” tag must be used (stands for “data management”).
(Name)
This part is compulsory. This field corresponds to the name of the Functional Unit. It must describe as much as possible the action performed by the Functional Unit. In case of an “ALGO” type it may be related to the standard sub-clause title or to the (shorter) common name to refer to such specific algorithm. For the other Functional Unit, one would try to put a name which can be understood by the entire MPEG community.