Device-specific purchases

OpenTV Video Platform supports device-specific products – that is, the ability to:

Specify that a product purchased on a device may only be consumed on that device, or
Specify that a particular product can only be consumed on particular classes of device (for example, only on mobile devices)

To enable a device-specific product:

Enable device-specific products in OpCon. Go to Platform > Device Specific Products > Feature Configuration and click Enabled.
See Device specific products.
For each class of device that you want to restrict consumption of the product to, add a device class in OpCon.
1. Go to Platform > Device Specific Products > Device Class.
2. For each class you want to add, click ADD FIELD and fill in the name of the class.
3. When you are finished, click SAVE CHANGES.
See Device specific products.
Assign the correct device class to each device:
- Open devices:
  - Ensure that when the device signs into the platform for the first time, it specifies one of the device classes that you specified above as the playoutDeviceClass in the deviceInformation section of the request body.
    See Authentication token and First time and n-th time sign on.
    Note: When an open device is created in OPF, a device profile is automatically assigned to it based on the provided deviceInformation.
  - Devices that are already registered will require a software update to take advantage of this functionality.
- Managed devices are pre-provisioned and so their device class cannot be changed. Make sure you use the appropriate class in step 2 above.
Edit the relevant product(s) and specify the device class(es) that each product should be constrained to. (Or specify the class(es) when creating a product.)
You can only specify the classes that were added above.
See Products (in OpCon).
Note: If a product is added by ingesting it (see Content import), the device class(es) that can be specified for the product must be from the list of classes added in step 2.
If products may be consumed on any device of the specified class (rather than only on the specific device on which the product was purchased), the CRM must modify the relevant entitlements.
By default, the entitlement includes the ID of the purchasing device. When the client makes the content authorisation call required for playback, the token that it receives includes the device ID to ensure that the content can only be played on the device with the matching ID.
If you want to remove this constraint, the CRM should:
- Modify the appropriate entitlements to remove the device ID.
  See the PUT /rmg/v1/entitlements endpoint in the CRM Gateway API documentation.
  This is a bulk operation and can be used, for example, to update all the entitlements for a specified product (by filtering on product ID).
- When creating an entitlement, make sure that a device ID is not set.
  See Managing entitlements.

See also