How Axinom DRM counts licenses
If a license request is reached to the license server and the license server results in a successful license, that license request will be counted into billing as an individual license request regardless of the Keys. In other words, if the license request reached multiple times to the license server with the same license token due to a refresh browser, the license request is counted as a separate request.
Two ways to minimize the generating license requests are,
-
Using persistence license: If license persistence is allowed from the entitlement message, the license is persistent. It is stored on the client device in the local license store. The client device can reuse the stored license till it expires.
-
Active user model : Refer to this documentation: http://localhost:3000/general/billing/drm/billing-drm#implementing-the-active-users-billing-model
Further, players may send multiple requests to the license endpoints, even when only a single license is being requested. In most cases, there are two types of requests:
-
The actual license request
-
Service certificate request: To protect the user's privacy, the CDM uses this certificate to encrypt certain information in the license request so that only the intended server can read it. This means that the server certificate must be fetched before a real license request can be generated. To identify whether this is a server certificate request or not, you can see the content length of the request from the network tab. If it is 2 bytes long, it is the server certificate request.
Sometimes there can be more requests than these two. Those additional requests can be:
- One or more CORS/OPTIONS requests
If we compare the size of these requests, the actual license request usually has a request body containing more bytes than the others. However, these additional requests will not be counted as separate license requests; only the actual license requests will be counted.