Workflows

NAGRA PRI supports the following workflows to capture an asset, retrieve its status, and finally delete (purge) it when it is no longer needed. If there is a change in the capture metadata, the asset can be updated using the PUT API, but only before the capture process is started by the PRI server.

Asset capture

This workflow triggers the encoder to capture a scheduled event (future) or extract an asset (live/in the past) from the pre-recorded rolling buffer.

The capture is based on the channel/stream identifier and the event start and end times.

Note that the channel/stream identifier must be synchronised between the PRI client (CMS) and PRI server (recorder).

The NAGRA PRI client may provide an asset identifier to uniquely identify the resulting asset. This name may be used to define the asset delivery URL depending on the encoder behaviour.

The delivery URL will depend on the network type associated with the source channel. In the case of OTT, it will be a URL. In the case of cable, it will be an asset ID and the source channel ID.

This operation can be asynchronous. The NAGRA PRI client will poll the asset status (see asset validation workflow below).

The NAGRA PRI client will be configured to trigger the capture at the appropriate moment (e.g., right after event start, or wait until event end, etc.) depending on the HE requirements.

The capture request can include optional parameters to profile the asset, including encryption schema and DRM signalling.

In the there is a change in the schedule after the capture request has been issued to the PRI server but before the actual recording has started, then the PRI client can use the PUT API to update the capture request using the asset ID.

Asset validation

Queries the HE vendor using the asset identifier given above to retrieve the status of a captured asset as well as the delivery URL to access it.

Status values are defined in the API: Scheduled, InProgress, Completed, Failed, Cancelled, Expired.

This operation may be synchronous. The NAGRA PRI client will poll/re-try this API to wait for a final status (COMPLETED/FAILED).

Asset update

Instructs the HE vendor to update the details of a previously issued capture request for a scheduled asset capture, based on the asset identifier. This operation should be synchronous.

Asset purge

Instructs the HE vendor to purge a previously captured asset or cancel a scheduled/ongoing asset capture, based on the asset identifier.

This operation should be synchronous. Nevertheless, the NAGRA PRI client may re-try this API or poll the asset status to let the PRI server complete the purging of the asset and delete the related metadata.

Lifecycle:

Asset packaging

Triggers the HE vendor to package a captured scheduled event (future) or extract an asset (live/in the past) from a pre-recorded rolling buffer or harvested asset.

Based on the channel/stream identifier plus event start and end times.

Note that the channel/stream identifier must be synchronised between PRI client (CPM) and PRI Server (Recorder).

The NAGRA PRI client may provide an asset identifier to uniquely identify the resulting asset. This name may be used to define the asset delivery well-known URL depending on encoder behaviour.

The delivery URL will depend on the network type associated to the source channel. In the case of OTT, it will be a URL. In the case of cable, it will be an asset ID and the source channel ID.

This operation can be asynchronous. The NAGRA PRI client will poll the asset status (see asset validation workflow below).

The NAGRA PRI client will be configured to trigger the capture at the appropriate moment (e.g., right after event start, or wait until event end, etc.) depending on the HE requirements.

The packaging request can include optional parameters to profile the asset, including encryption schema and DRM signalling.

In the there is a change in the schedule after the capture request has been issued to the PRI server but before the actual recording started, then the PRI client can use the PUT API to update the packaging request using the asset ID.