Session control with SSM
Overview
OpenTV Platform uses the Secure Session Management (SSM) service, part of NAGRAVISION's Security Services Platform (SSP), to limit the number of concurrent streams consumed by client apps.
A number of different kinds of session limit can be defined (in OpCon):
An account-level session limit is defined in an account profile and applies to all the accounts that have the account profile assigned to them.
A device group session limit applies a session limit to groups of devices (for example, only to mobile devices) for all accounts.
IP session limits are defined in an account profile and apply to all the accounts that have the account profile assigned to them.:
A limit on the number of different IP addresses from which an account can initiate sessions
A limit on the number of sessions allowed per IP address
Channel group session limits – groups of channels can be defined and a session limit applied for each such channel group.
The effect for the client is the same in each case – when the client attempts to set up a new playback session, SSM enforces these limits. If the new session would exceed any of the defined session limits, the request will fail.
While playing content, the app must send keep-alive requests at regular intervals. If it fails to do so, SSM will end the session and playback will stop.
After playback, the app must tear down the session. This allows SSM to decrement the session count.
The following client use cases are supported:
Sending keep-alive calls:
To integrate against SSM, you will need to refer to the SSM API documentation. This is part of the SSP portal – to get access, please contact your NAGRAVISION representative.
CONNECT Player
If you are using CONNECT Player, use its built-in methods for working with SSM. See:
See also
Managing playback sessions in the Subscriber Management Integration Guide
Device Management in the OpCon documentation
Account profiles in the OpCon documentation