License Acquisition - MDRMM/SDP

This page applies to licence acquisition in both direct and non-direct modes.

This page describes the request that the MDRMM makes to the SDP/third-party portal and the response that it receives.

API Call

The MDRMM makes a content authorisation request to the SDP/portal. The actual request that it makes depends on whether it is calling SDP or a third-party portal and whether licence pre-delivery is required – seeMultiple portals, below.

Variant cases

Multiple portals

The MDRMM decides which portal to send the request to based on the value of the portal key that it received inside applicationData.

If the request should be sent to the SDP, the MDRMM calls MdrmService.isContentAuthorised.
If the request should be sent to a third-party portal that implements the IPortal interface, the MDRMM calls /Authorization/isContentAuthorized.

If pre-delivery is being used, the MDRMM makes a getContentRights request instead:

For SDP, it calls /Authorization/getContentRights.
For a third-party portal, it calls: MdrmService.getContentRights

STB vs open device

MdrmService.isContentAuthorised

For STBs, in deviceSpecification:

opaqueData is not mandatory.
The value of secretId is the nuid of the STB.
The value of secretParams is the cts value from the STB's call to /client/getEntitlements.
device does not need to include isPlatformCompromised or deviceTime.

For open devices, in deviceSpecification:

opaqueData is mandatory.
The other fields are not mandatory.

Response

The structure of the response is different between the SDP and the third-party portal APIs but the content is similar.

If the usageRules do not contain a value for isStorageAllowed, the default of false is assumed.

Variant cases

STB vs open device

If the request is sent to a third-party portal, the /Authorization/isContentAuthorized response varies depending on whether hwPRM or swPRM is used:

The credentialsId returned in the usageRules part of the response is mandatory for hwPRM, but not for swPRM.