TMS KDM Manager
TMS KDM Manager – KDM Logs
The KDM Logs tab provides a historical view of all KDM (Key Delivery Message) ingestion activities across your TMS environment. It helps operators verify whether KDM files were correctly processed and ingested into the appropriate screen servers.
📋 Interface Overview
| Field | Description |
|---|---|
| UUID | Unique identifier of the ingested KDM file |
| Title | CPL or feature title associated with the KDM |
| Task Stat | Status of the ingest process: Success (green) or Failed (red) |
| Screen | Screen or auditorium where the KDM was applied |
| Timing | Timestamp of the ingestion attempt |
🔎 Usage
- Search by Title or UUID using the top-right search bar to quickly locate specific ingests.
- Paginate through thousands of records for long-term tracking (TMS stores complete key history).
🛠️ Troubleshooting Failures
- KDM does not match the IMB serial number (common with incorrect cert types).
- Server not powered on or projector in standby mode (if IMB is embedded in the projector).
- Expired or corrupted file.
- Attempting to ingest legacy MPEG or SMS-cert KDMs on modern SMPTE servers.
✅ Tip: Prefer SHA256-signed, cert-type KDMs when targeting modern SMPTE-compatible DCPs. Avoid uploading multiple incompatible KDMs (e.g., chain.sms, chain.mpeg) to reduce playback risk.
🧾 Log Retention & Audit
KDM Logs serve as an audit trail for content security compliance. They help:
- Verify ingest timelines for distributor requirements.
- Prove decryption key presence during playback investigations.
- Confirm which screen received which version of the key.
This makes the KDM Logs an essential tool in managing encrypted content securely and efficiently within the cinema ecosystem.
| Section | Description |
|---|---|
| Playback Status | Shows the SPL currently playing or idle status. Playback progress bar is included. |
| Server Status | Real-time server condition, storage usage, and scheduling mode. |
| Projector Status | Indicates projector online state, lamp, and dowser (shutter) state. |
| Sound Status | Displays sound processor state, fader level, and audio format (e.g., PCM, 5.1, ATMOS). |
| Actions & Statuses | Provides quick access to macros, details, and displays alert icons when errors are detected or ingest progress. |
Icon Color Codes
Each icon in the Server, Projector, and Sound columns uses color indicators for immediate visual diagnosis:
| Color | Meaning |
|---|---|
| 🟢 Green | Normal / Operational |
| ⚪ Grey | Offline / No connection |
| 🟡 Yellow | Warning or degraded state |
| 🔴 Red | Critical failure or error condition |
These apply to:
- Server connection
- Projector status
- Lamp status
- Storage usage
- Sound processor status
- Error indicators in the Action column
Actions / Status Column Icons
| Icon | Function |
|---|---|
| ⚙️ Macro Button | Open automation macro execution |
| 📋 Screen Details | Show full screen log/status modal |
| ⚠️ Warning Alert | Devices error messages |
| ⬇️ Ingest Task Failure | On Going Transfer/Ingest into Screen |
✅ Summary
The TMS Dashboard is your central control panel — offering live feedback and one-click access to all key auditorium functions. Each tile reflects:
- Current playback
- Health of connected equipment
- Scheduling consistency
- Alerts and recommended actions
By using this layout, operators can monitor and act across 16+ screens with ease, while maintaining awareness of upcoming risks or performance issues.
If you have any questions please contact our support team.
TMS KDM Manager – File Upload
The KDM File Upload tab is where decryption keys (KDMs) are added into the TMS for distribution to the LMS and playback servers. It supports bulk uploads, drag-and-drop actions, and screen-targeted distribution for secure DCP playback.
🖥️ Interface Overview
| Element | Description |
|---|---|
| Drag & Drop / File Select Area | Upload .xml KDM files by dragging them here or clicking to select |
| Upload All | Trigger LMS and Screen ingest for all files in queue |
| Clean Logs | Clears the upload history display (does not delete actual files) |
| UUID | Unique identifier of the KDM |
| Ingest LMS | Status of ingesting to central storage (LMS) |
| Upload to Screen | Retry button to push KDM to screen if it previously failed |
| Ingest Screen | Status of ingest into target screen’s server (IMB/DSP) |
📂 How It Works
- Upload the File:
- Drag and drop
.xmlKDM files - Or click Click to Select File to browse locally
- Drag and drop
- Auto Detection:
- The TMS parses each file to identify which Screen it belongs to
- It will ingest to LMS first, then the corresponding Screen
- Retry Uploads:
- If screen was offline or projector IMB powered off, use the Upload button to retry
- Auto Push When Online:
- If a required KDM is already in LMS, it will automatically be pushed to the screen when it comes online and a scheduled session needs it
🔐 KDM Handling in TMS: Accepted vs. Blocked Types
The TMS employs intelligent filtering to ensure only valid and compatible KDMs are ingested, thereby preventing playback issues caused by incompatible or redundant keys.
✅ Accepted KDMs
SMPTE KDMs utilizing SHA-256 certificates are the industry standard for modern digital cinema systems. These KDMs are compatible with JPEG 2000 DCPs and are recommended for their enhanced security and compatibility.
Example Filename:
KDM_TelagaSuriramFinal_FTR_S-239_MSA-EN_MY_51_2K_FP_20250422_FP_SMPTE_VF@ims-xxx.cert.sha256.pem.kdm.xmlExample KDM’s that is accepted – Consist of cert.sha256
Key Characteristics:
- Conform to SMPTE ST 430-2 standards.
- Use SHA-256 hashing algorithms.
- Target specific IMBs (e.g.,
@ims-xxx). - Ensure secure and reliable playback
⛔ Blocked KDMs
⚙️ Actions / Alerts
…@imb-xxx.chain.mpeg.pem.kdm.xml
…@imb-xxx.chain.sms.pem.kdm.xml
…@imb-xxx.cert.sms.pem.kdm.xml
In this example, the cert.sms , chain.mpeg, chain. sha256, chain.sms will be blocked by the TMS. It will accept the cert.mpeg and cert.sha256 KDM’s the rest will fail.
Reasons for Blocking:
- SHA-1 is now considered insecure and deprecated.
- MPEG/Interop KDMs are incompatible with modern JPEG 2000 DCPs.
- Ingesting multiple KDM types can cause conflicts within the IMB, leading to playback errors.
📊 KDM Compatibility Diagram
The following diagram illustrates the compatibility of different KDM types with modern digital cinema systems:
| KDM Type | Certificate Type | Compatibility |
|---|---|---|
| SMPTE KDM | SHA-256 | ✅ Accepted |
| Interop KDM | SHA-1 (MPEG) | ❌ Blocked |
| SMS KDM | SMS Certificates | ❌ Blocked |
| SMPTE Chain KDM | SHA-256 Chain | ❌ Blocked |
| Interop Chain KDM | SHA-1 (MPEG) | ❌ Blocked |
| SMS Chain KDM | SMS Chain | ❌ Blocked |
⚠️ Important Notes
- SHA-256/SMPTE KDMs are used by all modern digital cinema servers.
- Avoid uploading SHA-1/MPEG/Interop KDMs to prevent playback issues.
- The TMS will automatically ingest valid KDMs into the LMS and attempt to distribute them to the appropriate screens.
- If a screen is offline or its IMB is powered off, the TMS will queue the KDM and automatically ingest it once the screen becomes available