ISO/IEC 23004-4:2007
(Main)Information technology — Multimedia Middleware — Part 4: Resource and quality management
Information technology — Multimedia Middleware — Part 4: Resource and quality management
ISO/IEC 23004-4:2007 specifies the interfaces of the support application programming interface and the realization technology used for resource management in MPEG Multimedia Middleware (M3W). Resource management is an optional framework for M3W platforms. ISO/IEC 23004-4:2007 specifies entities and interfaces for resource budget creation, assignment and removal, entity and interfaces for assessing the feasibility and selecting resource configurations (resource configuration = set of assigned budgets), interfaces implemented by quality-aware entities (Quality-aware entities can provide multiple quality levels and know the resource needed to provide each quality level.), entity and interfaces for coordination of the "budget--quality level" negotiation (includes interfaces for registration and setting priorities).
Technologies de l'information — Intergiciel multimédia — Partie 4: Management des ressources et de la qualité
General Information
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 23004-4
First edition
2007-09-15
Information technology — Multimedia
Middleware —
Part 4:
Resource and quality management
Technologies de l'information — Intergiciel multimédia —
Partie 4: Management des ressources et de la qualité
Reference number
©
ISO/IEC 2007
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO/IEC 2007
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2007 – All rights reserved
Contents Page
Foreword .iv
Introduction.v
1 Scope.1
2 Organization of this document .1
3 Normative references.2
4 Terms and definitions .2
5 Overview of interface suites.2
5.1 Introduction.2
5.2 Resource management.2
5.3 Quality management .3
6 Resource management interface suite .6
6.1 Overview.6
6.2 Types and constants.6
6.3 Logical component.20
6.4 Roles.20
6.5 Interfaces.21
7 Overview of realization .29
8 Resource management.30
8.1 Overview.30
8.2 Responsibilities of roles in the Resource Management Framework .30
8.3 Realization of a resource chief .31
8.4 Composition of quality information.34
Annex A (informative) Dynamic view of the Resource and Power Management Framework.36
Annex B (informative) CPU chief details .38
Annex C (informative) Approach to power management.40
Annex D (informative) Composition of quality information example .43
Bibliography.47
© ISO/IEC 2007 – All rights reserved iii
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC 23004-4 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia information.
ISO/IEC 23004 consists of the following parts, under the general title Information technology — Multimedia
Middleware:
⎯ Part 1: Architecture
⎯ Part 2: Multimedia application programming interface
⎯ Part 3: Component model
⎯ Part 4: Resource and quality management
⎯ Part 5: Component download
⎯ Part 6: Fault management
⎯ Part 7: System integrity management
iv © ISO/IEC 2007 – All rights reserved
Introduction
MPEG, ISO/IEC JTC 1/SC 29/WG 11, has produced many important standards (MPEG-1, MPEG-2, MPEG-4,
MPEG-7, and MPEG-21). MPEG feels that it is important to standardize an application programming interface
(API) for Multimedia Middleware (M3W) that complies with the requirements found in the annex to the
Multimedia Middleware (M3W) Requirements Document Version 2.0 (ISO/IEC JTC 1/SC 29/WG 11 N 6981).
The objectives of Multimedia middleware (M3W) are to allow applications to execute multimedia functions with
a minimum knowledge of the middleware and to allow applications to trigger updates to the middleware to
extend the middleware API. The first goal can be achieved by standardizing the API that the middleware offers.
The second goal is much more challenging, as it requires mechanisms to manage the middleware API and to
ensure that this functions according to application needs. The second goal can support the first, by reducing
the needed standard APIs to those that provide middleware management. Consequently, applications can use
these standard management APIs to generate the multimedia system they require.
The aim of M3W is to define a component-based middleware layer in high-volume embedded appliances that
enables robust and reliable operation. These types of product are heavily resource constrained, with a high
pressure on silicon cost and power consumption. In order to be able to compete with dedicated hardware
solutions, the available resources will have to be used very cost-effectively, while enabling robustness and
meeting stringent timing requirements imposed by high-quality elements such as digital audio and video
processing.
High-volume embedded appliances are considered business-critical devices. Their failure can have important
economic implications for the producing company. Hence, they have stringent and demanding quality
requirements. Unfortunately, in the software industry misbehaving products are commonplace. However, this
is not the case with consumer electronics, home appliances and mobile devices. Users are accustomed to
robust and well-behaved devices.
In consumer electronics, there are demanding quality requirements and a need to use the available hardware
resources cost-effectively. The term “Application” is used to refer to the software entity that (indirectly)
provides certain functionality to an end-user; the Application may include Service Instances that are bound to
it. In order to ensure that an Application provides the correct service, it needs to be assigned the hardware
resources it requires. This can be achieved by assigning it the “worst case” resources required. However, with
many applications, the worst-case resource usage is much less than the mean case. If this worst-case
approach is followed, hardware resources will be wasted. On the other hand, problems may arise if the
running applications require more resources than can be made available. If the platform follows a typical fair
policy for the assignment, the behaviour of the system will be unpredictable, especially for applications that
must provide results according to some specified time constraints.
The goal of Resource Management is to assign budgets or resource reserves to Applications. These budgets
are guaranteed, so that they are available in any situation. This approach helps to enhance system
robustness, because an Application is unable to affect the resource reserves of others.
In order to benefit from Resource Management, Applications participating in Resource Management should be
resource-aware (RA). This means that they are aware of the resources they need during their execution and
should adapt their behaviour to the resources which are made available. This ensures that applications can
function correctly without exhausting all of the system resources that have been allocated to them.
Quality-Aware (QA) Applications are RA applications that are aware of the quality of service that they deliver.
Typically, they are capable of providing different quality levels. They are characterized by the quality they
provide and the resources needed for this purpose. Usually the higher the quality level, the higher the
resource needs. This type of Application is able to dynamically change the provided quality level, depending
on the assigned budgets.
© ISO/IEC 2007 – All rights reserved v
Often, QA and RA applications are real-time applications. The assigned budgets allow them to provide a
suitable output within some time interval. A hard real-time application can be viewed as QA with only two
quality levels: maximum quality or nothing. The Resource Management framework can also deal with Non
Resource-Aware Applications (NRA) in the sense that they are assigned a fixed budget all together.
The relation between the Resource Management framework and QA applications is based on a contract
model. The system provides resources and the Applications commit to generate the required results (outputs)
with a specific and stable quality. Budget assignment must be obtainable, which means that it should not be
possible to assign more resources than those actually available. Contracts are negotiated with the
Applications with the goal of maximizing overall system quality, as perceived by the user. In this process, the
“importance” of the Applications is a primary parameter for this operation.
Power is considered to be one of the most important resources to be managed in the next generation of
consumer electronics. Its importance is clear for mobile devices, where the goal is to maximize battery life. In
stationary devices, it is also relevant for environmental conditions, fan-less operation and to increase the
lifetime of the silicon devices. In addition, power management is related to heat control, so that the
temperature of different parts of the device can be maintained within a certain threshold.
The basic goals in M3W with respect to power management are as follows.
⎯ Reduce power consumption.
⎯ Increase battery life, for mobile devices.
⎯ Ensure a system-wide limit for heating: If it is detected that the temperature of the device it is too high, it
may be required to reduce it.
⎯ Take advantage of power-aware hardware and M3W components.
⎯ Ensure that the system and relevant Applications are always executed, in spite of the power saving policy
selected.
Power management is very much related to resource management. A number of techniques for reducing
power consumption are based on moving hardware components to less power-consuming modes of operation,
which implies reducing/modifying the available resources (CPU capacity, memory si
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.