Overview
ISO/IEC 23004-8:2009 - "Information technology - Multimedia Middleware - Part 8: Reference software" explains the organization and contents of the reference software that accompanies the Multimedia Middleware (M3W) standard. It documents how the reference implementation is structured for Parts 1–7 (architecture, API, component model, resource management, component download, fault management and integrity management) and states that the electronic attachment provides the actual source code. Keywords: ISO/IEC 23004-8:2009, Multimedia Middleware, reference software, M3W, source code.
Key topics
The standard and its reference software address these technical areas:
- Directory organization: Reference implementation is organized into directories that map to ISO/IEC 23004 Parts 1–7 (e.g., 2_Multimedia-API, 3_ComponentModel).
- Multimedia API: Reference implementations for Audio/Video, Governance (Security Manager), and IPMP (DRM interfaces). The Audio/Video logical components use the UHAPI4Linux base.
- Component model: Core framework, REMI (remote method invocation) services, Service Manager and an IDL/IDL-compiler toolchain for generating C/C++ components.
- Resource management: Framework to optimize perceived Quality of Service under constrained resources.
- Component download: Framework supporting controlled download/upload scenarios for dynamic component delivery.
- Fault management: Policies and tools (e.g., middleman/wrapper generators) to add fault tolerance transparently.
- Integrity management: Tools to maintain and restore consistent software configurations on consumer devices.
- Conformance: How the reference software relates to conformance testing and compliance with the M3W parts.
Technical artefacts mentioned include IDL/RIDL components, ipmp_types.ridl for IPMP common types, and build instructions for example components.
Applications and who uses it
ISO/IEC 23004-8:2009 and its reference software are practical for:
- Middleware implementers and developers building M3W-compliant platforms or services (Audio/Video, Governance, IPMP).
- Device manufacturers integrating multimedia middleware, DRM/IPMP, and dynamic component download.
- System integrators and QA teams using the reference implementation to prototype applications (e.g., television UI) and validate conformance.
- Standards developers and researchers studying reference implementations and IDL-generated component patterns.
- Security and DRM engineers implementing IPMP tool suites (key management, license management, signature/certificate handling).
Example uses include building demo TV applications, testing service registration and download flows, creating fault-tolerant service wrappers, and validating resource-management policies.
Related standards
This part complements other M3W parts:
- ISO/IEC 23004-1 through -7 (Architecture; API; Component model; Resource & quality management; Component download; Fault management; System integrity management)
- Normative cross-references include ISO/IEC 23004-2, -3, -5 and -6 as cited in the document.
For implementers seeking source code and practical examples, consult the electronic attachment referenced by ISO/IEC 23004-8:2009.
