Skip to main content

Media Content Key Extension

Notice

This document is a machine-translated draft and is currently undergoing review. Some content may be inaccurate or differ from the original Korean version. For the most precise information, refer to the Korean documentation.

Note

The media content key extension feature applies only to unencrypted content. It is not supported for DRM-protected content.

Kollus VOD supports combining a customer-defined Custom ID with an existing media content key. By using this feature, you can control a single physical original file as if it were multiple independent content items within the system.

Core principles​

  • Logical separation: For certain personalization features such as downloads and resume playback, the extended key is recognized as a different content item.
  • Physical integration: Basic content information is commonly managed based on the original media content key.
  • Example: Similar to Gmail's alias feature. When mail is sent to an extended address, the default address (support@kollus.com) receives it.
    • Default address: support@kollus.com
    • Extended addresses: support-cid1@kollus.com, support-cid2@kollus.com

Request specifications​

When calling unencrypted content, connect the original media content key and the Custom ID with a hyphen (-).

Request URL structure​

Since the media content key itself does not contain a hyphen, the Custom ID is distinguished based on the first hyphen.

https://v.kr.kollus.com/{MEDIA_CONTENT_KEY}-{CUSTOM_ID}

Applying to JWT Payload​

When authenticating using the JWT (JSON Web Token) method, enter the extended key directly into the mckey field within the mc array.

{
  "cuid": "user01",
  "expt": 1703980800,
  "mc": [
    {
      "mckey": "{MEDIA_CONTENT_KEY}-{CUSTOM_ID}"
    }
  ]
}

Constraints​

  • Length limit: Within 64 bytes
  • Allowed characters: Only alphanumeric characters and hyphens (-) are allowed
  • Encoding note: Multibyte characters such as Korean are not recommended (be careful not to exceed 64 bytes when UTF-8 encoded)

Features that apply the extended key​

When called via an extended key, the Kollus system creates and manages data separately for each Custom ID for the following items.

  • DRM download callback
  • LMS callback
  • Resume playback
  • Concurrent playback prevention
  • Bookmark

Receiving Callback Data​

When a callback (such as LMS, DRM download, etc.) is triggered from content where an extended key is applied, the extended key is passed directly in the media_content_key parameter of the received data. This allows your system to accurately identify which Custom ID triggered the event and proceed with subsequent processing.

media_content_key="{MEDIA_CONTENT_KEY}-{CUSTOM_ID}"