Policy Information Point pip
NOTE
This page is deprecated as it applies to the previous version of the API which is no longer recommended for new integrations
The following diagram shows the flow in case the customer opts for the Policy Information Point, in which case CM is merely used for querying the activity and all the access logic is embedded in the client application):
The diagram below illustrates how stream counting works for a user that watches content from 2 devices.
In a nutshell, the usual message flow is as follows:
- Initially, for a user that has never used the service, a web page is loaded / an application is opened, where a Concurrency Monitoring Service instrumented application makes a Session Initialization call.
- The Concurrency Monitoring Service returns the new stream resource for heartbeats, as well as the current user activity.
- During video playback, the instrumented application makes heartbeat calls to the Concurrency Monitoring Service, showing that the user is currently consuming a video.
- At any other point, other instrumented applications can make Status query calls to the Concurrency Monitoring Service, which will return the current user activity.
- At video playback end, the instrumented application can make a heartbeat call with “event=stop”, signifying that the video has stopped, and that the current stream should not be counted as an active stream anymore.
recommendation-more-help
42139a1e-84f9-43e7-9581-d6e1d65973da