Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 16500-2-02:2002 – Generic Digital Audio-Visual Systems: System Dynamics, Scenarios, and Protocols (Canadian Adoption CAN/CSA-ISO/IEC 16500-2-02)
Comprehensive Technical Specifications for Digital Audio-Visual Systems Architecture and Communication
Scope
IEC 16500-2-02, formally adopted as CAN/CSA-ISO/IEC 16500-2-02, is part of the IEC 16500 series that defines the generic digital audio-visual system (DAVIC) architecture. This part focuses on system dynamics, scenarios, and protocols. It specifies the overall operational behavior of a DAVIC system, including the methods for initiating, controlling, and terminating audiovisual services. The standard applies to both broadband and narrowband networks, covering end-to-end communication between content servers, service providers, and end-user devices such as set-top boxes, digital TVs, and multimedia terminals.
Technical Requirements
The technical requirements in IEC 16500-2-02 establish the baseline for interoperability among DAVIC components. They define the dynamic behavior of the system through scenarios that represent real-world usage cases, such as video-on-demand, interactive television, and data broadcast. Key technical elements include:
- System Scenarios: A set of abstract interaction sequences between users and the system, covering service selection, stream control (play, pause, stop, record), and resource reservation.
- Protocol Stack: A layered communication protocol stack adapted from the ISO/OSI model, with emphasis on session, presentation, and transport layers. The standard mandates the use of TCP/IP and UDP/IP for network transport and defines higher-level streaming protocols for MPEG-2 transport streams.
- Session Management: Procedures for establishing, maintaining, and releasing sessions between clients and servers. This includes authentication, negotiation of Quality of Service (QoS) parameters, and error handling.
- Stream Control: The Digital Storage Media Command and Control (DSM-CC) protocol is adopted for stream manipulation, ensuring uniform control of video, audio, and data streams across different vendors.
- Resource Management: Mechanisms for network resource allocation, bandwidth reservation, and admission control to guarantee QoS during peak demand.
Key System Parameters
IEC 16500-2-02 defines several parameters that critical for system design and deployment:
| Parameter | Specification | Application |
|---|---|---|
| Maximum Session Duration | Up to 24 hours (configurable) | Ensures service continuity for long playback sessions |
| QoS Class | Class 0–4 (unidirectional to interactive real-time) | Defines latency, jitter, and error rate thresholds |
| Stream Control Protocol | DSM-CC User-to-User / User-to-Network | Provides VCR-like control over MPEG-2 streams |
| Maximum Number of Sessions | Determined by server capacity | Scales with network and hardware resources |
| IP Multicast Support | Required for data broadcast scenarios | Reduces bandwidth consumption in distribution |
Note on IP Multicast: Implementations of IEC 16500-2-02 must be aware that multicast group management (IGMP) is mandatory for efficient bandwidth usage in broadcast services. Misconfiguration can lead to network congestion.
Implementation Highlights
Adopting IEC 16500-2-02 in a DAVIC deployment involves integrating several modules: the Session Controller, Stream Controller, Resource Manager, and Protocol Stack. The standard recommends the following implementation practices:
- Modular Architecture: Separate the system into independent functional blocks (e.g., session control, resource management) to facilitate upgrades and testing.
- Compliance with MPEG-2 Standards: Ensure that the underlying MPEG-2 TS is fully compliant with ISO/IEC 13818-1, as the standard references DAVIC specifications built on MPEG-2.
- Safe Handling of Dynamic Events: Implement robust error handling for abnormal session termination, resource release, and network failures. The standard defines default actions for unexpected events, such as forced session termination with resource cleanup.
- Interoperability Testing: Use reference scenarios defined in Annex A of the standard to verify correct interaction between client and server devices. Testing must cover all mandatory protocol exchanges, especially during session setup and teardown.
Implementation Tip: Many successful DAVIC systems rely on a middleware layer that abstracts the DSM-CC protocol complexities. This reduces development time and eases maintenance.
Critical Consideration: IEC 16500-2-02 requires that all servers implement admission control to prevent oversubscription. Failing to enforce proper resource limits can degrade the entire system’s performance.
Compliance Notes
Compliance to IEC 16500-2-02 (CAN/CSA-ISO/IEC 16500-2-02) is verified through a combination of conformance testing and self-declaration. Standards bodies such as the Digital Audio-Visual Council (DAVIC) provide test suites that validate key protocol sequences and scenario behavior.
Certification bodies typically check the following aspects:
- Session Establishment Sequence: The client-server handshake must comply with the defined flow, including authentication token exchange and QoS negotiation.
- Stream Command Execution: All DSM-CC commands (Play, Pause, Stop, Jump) must be recognized and executed with the specified tolerance (e.g., stop within 1 second of receiving the command).
- Resource Cleanup: When a session ends normally or abnormally, all allocated resources (bandwidth, memory, stream handles) must be released within a defined timeout.
- Interworking with Network Layers: The protocol stack must respect the underlying network technology (e.g., ATM, Ethernet, or xDSL) as specified in the DAVIC system profiles.
Compliance Testing Note: When aiming for CSA mark certification in Canada, ensure that the product is tested by an accredited laboratory using the latest test suite from IEC 16500-2. The Canadian adoption often includes minor modifications from the original ISO/IEC standard; consult the CAN/CSA-ISO/IEC 16500-2-02 document for exact requirements.
Manufacturers should also be aware that conformance to IEC 16500-2-02 does not automatically guarantee interoperability with non-DAVIC systems. Additional integration work may be required for multi-standard environments.
Q: What is the relationship between IEC 16500-2-02 and the DAVIC specifications?
A: IEC 16500 is essentially the international standard ratification of the DAVIC 1.0 and 1.1 specifications. Part 2 specifically covers system dynamics and protocols. The Canadian adoption CAN/CSA-ISO/IEC 16500-2-02 aligns with the international version with minimal changes to suit the Canadian regulatory environment.
A: IEC 16500 is essentially the international standard ratification of the DAVIC 1.0 and 1.1 specifications. Part 2 specifically covers system dynamics and protocols. The Canadian adoption CAN/CSA-ISO/IEC 16500-2-02 aligns with the international version with minimal changes to suit the Canadian regulatory environment.
Q: Is IEC 16500-2-02 still relevant given modern streaming protocols like HLS and DASH?
A: While modern adaptive streaming protocols are widely used, IEC 16500-2-02 remains important for legacy DAVIC installations, scientific research, and regions where DAVIC systems are still deployed. It also provides foundational concepts for session management and resource allocation that older digital systems require.
A: While modern adaptive streaming protocols are widely used, IEC 16500-2-02 remains important for legacy DAVIC installations, scientific research, and regions where DAVIC systems are still deployed. It also provides foundational concepts for session management and resource allocation that older digital systems require.
Q: What is the typical bandwidth requirement for a DAVIC system conforming to this standard?
A: The standard does not mandate a specific bandwidth, as it depends on the service (e.g., standard definition ~2–6 Mbps, high definition ~15–25 Mbps). However, the resource management protocols ensure that enough bandwidth is reserved end-to-end to meet the negotiated QoS.
A: The standard does not mandate a specific bandwidth, as it depends on the service (e.g., standard definition ~2–6 Mbps, high definition ~15–25 Mbps). However, the resource management protocols ensure that enough bandwidth is reserved end-to-end to meet the negotiated QoS.