Overview
ISO/IEC 23004-3:2007 - "Information technology - Multimedia Middleware - Part 3: Component model" defines the component model and core framework for MPEG Multimedia Middleware (M3W). The standard specifies the realization technology, runtime concepts and the support application programming interfaces (APIs) required to instantiate, bind and interact with components and services in an M3W environment. It describes units such as the Unit of Trading (M3W component), Unit of Loading (executable component) and Unit of Instantiation (Service) and standard interfaces for navigation, binding and attribute access (for example rcIUnknown and rcIServiceGeneric).
Key topics and requirements
- Component model definition: what constitutes an M3W component and logical relationships among components, services and executable artifacts.
- Instantiation and execution framework: runtime concepts for creating and managing service instances, including a Runtime Environment logical component and interfaces to inspect/manipulate a registry of executable components.
- Service Manager role: optional logical component enabling instantiation and binding of multiple realization elements based on a logical component UUID.
- Remote invocation (REMI): interfaces for remote method invocation, split into REMI-P (publish/provide operations remotely) and REMI-R (invoke operations on remote services), plus guidance on proxies, wrappers and parameter marshalling.
- Standard interfaces & navigation: interface navigation (rcIUnknown, rcIServiceGeneric), binding semantics (rcIServiceGeneric), and access to public attributes required for interoperability.
- Metadata and UUID-based lookup: use of service and logical component metadata to support instantiation and binding by UUID.
- Execution and development frameworks: iterator idioms, packaging and behaviour of realization elements, and execution lifecycle considerations.
Practical applications and who uses it
ISO/IEC 23004-3:2007 is aimed at implementers and integrators building interoperable multimedia middleware and services:
- Middleware vendors implementing M3W-compliant runtimes and Service Managers.
- Device manufacturers creating multimedia devices that must instantiate or invoke remote multimedia services.
- Application developers who consume M3W APIs to manage multimedia components across devices and networks.
- System integrators designing distributed multimedia solutions that require standard component instantiation, binding and remote invocation.
- Standards bodies and researchers working on multimedia interoperability and API harmonization (MPEG-related ecosystems).
Practical benefits include simplified service lifecycle management, standardized remote method invocation, and clearer packaging/instantiation rules for distributing multimedia components across heterogeneous platforms.
Related standards
- ISO/IEC 23004-1: Architecture (context for the component model)
- ISO/IEC 23004-2: Multimedia API
- Other parts of ISO/IEC 23004 series (Resource & Quality Management, Component Download, Fault & System Integrity Management)
Keywords: ISO/IEC 23004-3:2007, Multimedia Middleware, M3W, component model, Runtime Environment, Service Manager, REMI-P, REMI-R, UUID, remote method invocation, multimedia API.
