Integration with Key Per Track

1. Guideline on Key Per Track with SSP

1. Key Per Track is considered as activated by SSP if the requested combination of content ID and key ID is associated to track(s) in the system.

2. It is possible to activate Key Per Track on existing contents by creating new key(s) with track(s) or updating existing key(s) with track(s).

3. The activation of Key Per Track can be done per content and encryption scheme.

   1. The encryption method is defined in the key requests sent to the key server

      1. Three possible values, which are considered as independant : cbcs, cenc, unspecified (not set)

   2. It is possible to activate Key Per Track on specific encryption schemes only.

      1. Not setting the encryption method is considered also as an independant value.

4. The keys are filtered per encryption scheme, a single license cannot contain a mix of keys associated to CBCS, CENC and unspecified encryption.

5. The license server delivers all the content keys for which the device is compliant, regardless of whether the key in the license request is part of the response.

   1. If the device doesn’t comply with the requested track, the client must fallback automatically to another track when the license has been delivered without the requested key.

6. The tracks can be associated to specific DRM Usage Rules Profiles (Content Usage Rules for OTT)

   1. Each content tracks shall be associated to DRM Usage Rules profiles with which the device has to be compliant in order to be granted the respective key(s).

   2. When using Content AuthZ tokens, the following hierarchy applies :

      1. The mapping between the Usage Rules profiles and tracks can be defined in the token and it takes precedence over the configuration.

      2. The mapping between the Usage Rules profiles and tracks can be defined in a tenant configuration and will be automatically applied internally.

      3. The content track(s) that are not specifically associated to a Usage Rules profile will be automatically associated to the profile “Default”.

      4. A mix of hierarchy levels can be applied simultaneously

         1. If the same track is associated to several Usage Rules profiles at different levels, precedence applies as above.

   3. When using SSP in extended mode, the following hierarchy applies :

      1. The DRM Usage Rules profiles are assigned to tracks as part of the OTT live channel definition in the IMS and it takes precedence over the configuration.

      2. The mapping between the Usage Rules profiles and tracks can be defined in a tenant configuration and will be automatically applied internally.

      3. The content track(s) that are not specifically associated to a Usage Rules profile will be automatically associated to the profile “Default”.

      4. A mix of hierarchy levels can be applied simultaneously

         1. If the same track is associated to several Usage Rules profiles at different levels, precedence applies as above.