Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 16500-9:2002 – The Usage Information Protocol for Generic Digital Audio-Visual Systems
Understanding the Scope, Technical Specifications, and Compliance of the Usage Information Protocol (UIP) Standard
The ISO/IEC 16500 series provides a comprehensive framework for generic digital audio-visual systems, covering everything from system architecture to communication protocols. ISO/IEC 16500-9:2002 (also adopted as CAN/CSA-ISO/IEC 16500-9-02 in Canada) specifically defines the Usage Information Protocol (UIP), a critical component for collecting, reporting, and exchanging usage information in such systems. This article offers a detailed technical examination of the standard, its scope, requirements, implementation guidance, and compliance aspects.
Scope of ISO/IEC 16500-9:2002
The standard specifies the protocol for the transfer of usage information between entities in a generic digital audio-visual system. Usage information refers to data related to the consumption of AV content, such as viewing times, content selections, and user interaction events. The scope includes:
- Definition of message types for usage reporting (e.g., start/stop of playback, channel changes, selection of supplementary services).
- Message structure and encoding rules using ASN.1 (Abstract Syntax Notation One) with packed encoding rules.
- Transport layer binding (typically over TCP/IP), though the standard remains transport-agnostic at the core.
- Security considerations for protecting the integrity and authenticity of usage data.
The standard applies to any system component that generates, collects, or processes usage information — including end-user devices, servers, network elements, and monitoring nodes. It does not define the business logic for processing usage data but ensures interoperability in the formatting and exchange of that data.
Technical Requirements
ISO/IEC 16500-9:2002 mandates a structured approach to usage information messaging. The two primary message categories are Usage Record Messages (carrying measurement data) and Control Messages (for session management and acknowledgments).
Message Structure
Every UIP message consists of a header followed by one or more protocol data units (PDUs). The header includes fields for version, message type, length, and a timestamp. The PDU for a usage record contains fields such as:
- userID – identifier of the user or device initiating the action.
- contentID – identifier of the AV content consumed.
- actionType – e.g., start, pause, stop, channel change, volume change.
- actionTime – absolute or relative time with a defined resolution (typically seconds since epoch).
- duration – length of the action if applicable (e.g., watching duration).
- optionalAttributes – vendor-specific or system-specific extensions.
| Message Type | Code | Description | Usage |
|---|---|---|---|
| UsageStart | 0x01 | Indicates beginning of usage activity (e.g., content start). | Sent by client to server at start of AV session. |
| UsageStop | 0x02 | Indicates termination of usage activity. | Sent at end of session or upon user interrupt. |
| UsageEvent | 0x03 | Represents an intermediate event (e.g., channel change, pause). | May be transmitted in real-time or batched. |
| UsageAck | 0x10 | Control message acknowledging receipt of a usage report. | Used by server to confirm successful delivery. |
| UsageNak | 0x11 | Negative acknowledgment indicating an error or rejection. | May include error codes for security, duplicate, or malformed records. |
Encoding and Delivery
UIP messages are encoded using Packed Encoding Rules (PER) of ASN.1 to reduce overhead. Each message is delivered as a single TCP segment or equivalent. The standard mandates a maximum message size of 65535 bytes, with smaller messages preferred for real-time usage. Timestamps must be synchronized to a common reference time base, and the specification recommends using NTP for clock synchronization in distributed systems.
Security
ISO/IEC 16500-9:2002 incorporates optional security mechanisms including message authentication codes (MAC) to protect against tampering, and the ability to encrypt payload fields. The standard itself does not define cryptographic algorithms but references ISO/IEC 16500-6 for security provisions. Implementers should consider applying TLS for transport security when running over IP networks.
Implementation Highlights
Tip: When implementing UIP on resource-constrained devices, consider batching multiple UsageEvent messages into a single TCP segment to reduce network overhead and power consumption. The standard permits aggregation of events within the same session as long as timestamp ordering is maintained.
Developers integrating UIP into AV systems should pay attention to the following key areas:
- Session management: A UIP session is established implicitly by the first UsageStart message and remains open until a corresponding UsageStop or connection teardown. No explicit handshake is required, simplifying implementation.
- Reliability: Though the protocol tolerates loss of some usage records, the standard strongly recommends using TCP as the underlying transport to ensure ordered, reliable delivery. Acknowledgments (UsageAck) are optional but encouraged for critical data.
- Scalability: The standard supports high-load scenarios by allowing servers to respond with UsageNak with a back-pressure indicator, causing clients to throttle their reporting frequency.
- Extensibility: The optionalAttributes field allows proprietary extensions without breaking interoperability. However, all such extensions must be registered according to annex guidelines.
Warning: While timestamps are mandatory, their granularity (seconds) may be insufficient for certain interactive applications requiring sub-second accuracy. Implementers should evaluate whether the standard’s default resolution meets their requirements and consider using the optional high-resolution timestamp extension available since the 2002 revision.
Best Practice: Always test UIP implementations against the conformance criteria defined in Annex A of the standard. Even if certification is not required, adherence reduces integration issues with third-party systems and ensures future-proofing.
Compliance Notes
ISO/IEC 16500-9:2002 compliance is typically part of a broader certification for systems claiming conformance to the ISO/IEC 16500 series. Key compliance points include:
- Mandatory features: All implementations must support the message types UsageStart, UsageStop, and at least one form of UsageEvent. The minimum timestamp resolution of 1 second is mandatory.
- Optional features: Security extensions (MAC, encryption), high-resolution timestamps, and certain control messages (UsageAck, UsageNak) are optional but recommended for enhanced functionality.
- Conformance testing: Test suites are available through ISO/IEC or national standards bodies. Devices that fail to correctly encode or decode the defined messages (using PER) will not pass verification.
- Regional adoption: In Canada, CAN/CSA-ISO/IEC 16500-9-02 is the adopted version. It is identical in technical content to the international edition but includes Canadian foreword material. Compliance with either version ensures mutual recognition.
Non-Compliance Risk: Failure to correctly implement the Packed Encoding Rules (PER) can lead to misalignment of field boundaries, causing message parsing failures. This is especially common when integrating with systems expecting the older Unaligned PER variant. Verify alignment settings (aligned vs. unaligned) in your ASN.1 compilation toolchain to avoid interoperability problems.
For organizations seeking certification, it is advisable to engage an accredited testing laboratory that specializes in the ISO/IEC 16500 series. The compliance process typically includes review of implementation documents, message trace analysis, and functional tests with reference servers.
Frequently Asked Questions (FAQ)
Q: Is ISO/IEC 16500-9:2002 still relevant today given the emergence of newer streaming protocols like MPEG-DASH and HLS?
A: Yes, the UIP standard remains relevant as a common format for usage reporting in systems that need a standardized, non-proprietary method to collect usage information. Many legacy AV systems and some current deployments in broadcasting and digital signage rely on this protocol. It complements, rather than replaces, modern transport protocols.
A: Yes, the UIP standard remains relevant as a common format for usage reporting in systems that need a standardized, non-proprietary method to collect usage information. Many legacy AV systems and some current deployments in broadcasting and digital signage rely on this protocol. It complements, rather than replaces, modern transport protocols.
Q: Can I use UIP over HTTP or WebSocket?
A: The standard specifies TCP as the transport in its implementation guide. However, it is technically feasible to tunnel UIP messages over HTTP or WebSocket by embedding the ASN.1-encoded payload. Doing so requires careful attention to session semantics and may affect timing. Such use is not officially standardized but has been applied in practice for firewall traversal.
A: The standard specifies TCP as the transport in its implementation guide. However, it is technically feasible to tunnel UIP messages over HTTP or WebSocket by embedding the ASN.1-encoded payload. Doing so requires careful attention to session semantics and may affect timing. Such use is not officially standardized but has been applied in practice for firewall traversal.
Q: How does UIP handle user privacy?
A: The standard does not mandate encryption of usage data, but it provides optional mechanisms for both payload encryption and authentication (via ISO/IEC 16500-6). Implementers should apply these mechanisms to protect sensitive user information. Additionally, national data protection laws (e.g., GDPR) must be addressed at the application layer.
A: The standard does not mandate encryption of usage data, but it provides optional mechanisms for both payload encryption and authentication (via ISO/IEC 16500-6). Implementers should apply these mechanisms to protect sensitive user information. Additionally, national data protection laws (e.g., GDPR) must be addressed at the application layer.
Q: What is the relationship between CAN/CSA-ISO/IEC 16500-9-02 and the international standard?
A: The Canadian adoption (CAN/CSA-ISO/IEC 16500-9-02) is technically identical to ISO/IEC 16500-9:2002. It includes minor editorial changes and a Canadian foreword. Compliance with either version is considered equivalent.
A: The Canadian adoption (CAN/CSA-ISO/IEC 16500-9-02) is technically identical to ISO/IEC 16500-9:2002. It includes minor editorial changes and a Canadian foreword. Compliance with either version is considered equivalent.