Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 62919: Content Management: Monitoring and Management of Personal Digital Content
IEC 62919 | Engineering Insight Article
Key Insight: IEC 62919 addresses the growing problem of digital content fragmentation across multiple devices by specifying a standardized method for content preservation information gathering, visualization, and management through a unified “my library” interface.
The Challenge of Digital Content Fragmentation
Modern users accumulate digital content — movies, photos, music, e-books, and documents — across a growing number of ICT devices including smartphones, tablets, PCs, hard disk recorders, and e-book readers. As device storage capacities increase and cloud storage services proliferate, digital content becomes scattered across multiple platforms. Users create backup copies, generating multiple generations of digital copies, and content can end up virtually anywhere. The result is a phenomenon the standard calls “content hiding” — users cannot easily locate the content they want, or it takes excessive time to find it.
IEC 62919, developed by IEC TC 100 (Audio, video and multimedia systems and equipment), provides a comprehensive solution to this problem by specifying a system architecture, protocol, and data format for monitoring and managing personal digital content. The standard defines how devices create and send content preservation information to a central server, enabling visualization of all a user’s digital content regardless of where it is stored.
Engineering Challenge: The fragmentation problem is compounded by different file formats, application types, and storage locations. IEC 62919 tackles this by establishing a standardized XML-based content preservation information format that works across diverse device types and content formats.
System Architecture and Data Flow
The standard defines a multi-component system architecture consisting of content devices, a content information server, and personal content monitoring devices. The basic operational flow involves several key steps:
Content Preservation Information Creation: Each device creates content preservation information by reading metadata from stored content — including file name, path, application type, creation time, size, and title. This information is formatted in XML according to the schema defined in the standard.
Server Communication: Devices send content preservation information to the content information server using HTTP or HTTPS protocols. The server receives, stores, and manages this information on a per-user and per-device basis. The standard defines five methods for server communication: register_all (replace all), register (add new), delete, modify, and clear_all.
| Method | Description | Use Case |
|---|---|---|
| register_all | Replace all content preservation information for a device | Initial synchronization, full device rescan |
| register | Add new content preservation information | New content purchased or created |
| delete | Remove specific content preservation information | Content deleted from device |
| modify | Update existing content preservation information | Content edited or metadata changed |
| clear_all | Remove all content preservation information for a device | Device replacement or factory reset |
Visualization: The content information server provides APIs for other servers to extract content information. A web server can then create HTML5-based “my library” views that users can access from any monitoring device. The standard specifically recommends HTML5 for its drag-and-drop capabilities and offline support via local storage.
Engineering Design Insight: The use of standard HTTP/HTTPS protocols means users do not need to change port settings on their broadband routers or gateway routers. This design choice significantly reduces deployment friction compared to proprietary protocols.
Data Format and Metadata Management
The content preservation information format is defined using XML Schema. Each content item includes three categories of information:
Content Meta Information (content_metainfo): Includes method, device ID/name, user ID, family ID, and content IDs. The family ID is a particularly flexible concept — it can identify not just a family group, but also friends, colleagues, or any other sharing group. Content IDs can be supplemented with sub-content IDs that are globally allocated identifiers from content distribution markets, allowing the server to derive rich metadata automatically.
Content Base Information (content_baseinfo): Includes filename, filepath, application type (based on RFC 6838 media types), create time, size, and title. The application type information allows the system to determine which devices are capable of opening specific content types.
Content Extension Information (content_extinfo): Optional detailed metadata that is application-type dependent. This can include the entire file header (meta_body), fixed-length headers (meta_head_1KB through meta_head_64KB), or vendor-specific metadata (meta_vendor_ZZZZ).
| Application Type | File Extension | Application Program |
|---|---|---|
| audio/mpeg | .mp3 | Audio player |
| video/mp4 | .mp4 | Video player |
| image/jpeg | .jpg .jpeg | Image viewer |
| application/pdf | PDF viewer | |
| application/epub+zip | .epub | E-book viewer |
Implementation Note: Privacy is a critical consideration. The standard specifies that the interface should also provide summarized, anonymized information (usage patterns, preferences) without identifying individual user IDs or device IDs, enabling service providers to analyze trends while protecting user privacy.
The standard’s approach to content management represents a practical foundation for personal content ecosystems. By providing a standardized way to catalog, monitor, and manage distributed digital content, IEC 62919 enables the development of universal content management applications that work across device boundaries — a key enabler for the increasingly multi-device lifestyle of modern users.
Frequently Asked Questions
Q1: Does IEC 62919 require proprietary server infrastructure?
No. The standard defines protocols and data formats that can be implemented on standard web servers using HTTP/HTTPS. The content information server can be implemented using common database technologies such as RDB, XML, JSON, or KVS.
Q2: How does the standard handle content across different device types?
Each device creates content preservation information independently in the standard XML format. The content information server aggregates information from all devices associated with a user ID, providing a unified view regardless of device type.
Q3: Can users share content with family members using this system?
Yes. The family ID mechanism enables content sharing within defined groups. Multiple users can share content preservation information, and the server manages access control based on both user IDs and family IDs.
