Cisco Virtualized Video Processing Controller User Guide - Release 3.2.3

Configuring an ATS Channel

Step 1 From the navigation panel, choose Media Workflow Manager > Media Workflows > Media Sources > ATS Channels.

Figure 6-1 Creating an ATS Channel

Step 2 Click the + icon to add a new channel. The ATS Channel dialog opens.

Step 3 Complete the fields in this dialog by specifying Name, Channel ID, Source Type (UDP or HTTP), and Primary – Target Multicast Address/Source IP.

To add an ABR Profile, click + in the ABR Profiles section.

Step 4 Click OK.

Configuring an ATS Channel Lineup

Step 1 From the navigation panel, choose Media Workflow Resources > Media Sources > ATS Channel Lineups.

Step 2 Click Add to add a new channel lineup. The ATS Channel Lineups dialog opens.

Step 3 Add the desired channel(s) from the right pane to the new channel lineup in the left pane.

Figure 6-2 Configuring an ATS Channel Lineup

Step 4 Specify a Name, Description, and Media Archive for the channel lineup.

Step 5 Click Save.

Note The right pane only displays channels belonging to the media archive currently selected in the drop-down list. If multiple media archives exist, select the desired media archive from the list to make its corresponding channels available in the right pane.

Configuring Media Archives

Step 1 From the navigation panel, choose Media Workflow Resources > Media Sources > Media Archives.

Step 2 Click Add to add a new archival configuration. The Media Archives dialog opens.

Step 3 Specify the following parameters as needed (all are optional):

• Archive Time – Elapsed time after which the stream is put into archive storage.
• Re-archive Time – Time after which the reconstituted stream can be archived again.
• Archive Start Time – Time to start running the archival process for any segment that has passed the Archive Time.
• Archival Duration – How long to run the archival process before taking a break.
• Archival Pause – Pause time between archival runs.

Figure 6-3 Configuring Media Archives

Configuring NAS Media Sources

Step 1 From the navigation panel, choose Media Workflow Manager > Resources > Media Sources > NAS Media Sources.

Step 2 Click Add to add a new NAS Media Source. The NAS Media Sources dialog opens.

Step 3 Specify the following parameters:

• Name – Name of the NAS media source, or content library (required). The name is a string of up to 30 characters. Acceptable characters include uppercase and lowercase letters, numbers, periods (.), dashes (-), and underscores (_). The name must not begin with a period (.), and it is not case-sensitive.
• Description – Description of the NAS media source. The description is a string of up to 30 characters, and can include uppercase or lowercase letters, numbers, and any special characters.
• Share Path – Share path used by the NAS media source on the network (required). The share must be mounted and active on the V2PC system before the files in this path are accessible.
• NFS Version – Version of the Network File System (NFS) used by the NAS media source. Valid versions are 3.0 and 4.0.
• Servers (IP Address Ranges) – Range of servers available to the NAS media source. For a single server, the Start and End IP addresses are the same.

Figure 6-4 Configuring NAS Media Sources

Configuring HTTP Header Policies

The HTTP header policies control the HTTP headers for publishing content.

Step 1 From the navigation panel, choose Media Workflow Manager > Resources > Policies > HTTP Header Policies.

Step 2 Click Add to add a new HTTP Header Policy. The HTTP Header Policies dialog opens.

Step 3 Specify the following parameters:

• Name – Name of the HTTP header policy (required). The name is a string of any length. Acceptable characters include uppercase and lowercase letters and numbers. No special characters are allowed. The name is not case-sensitive.
• Description – Description of the HTTP header policy. The description is a string of up to 70 characters, and can include uppercase or lowercase letters, numbers, and any special characters.
• Request Type – Indicates whether the rule is for a Manifest or Chunk.
• HTTP Version – Version of HTTP request. The only valid value is HTTP 1.1.
• Header Name – HTTP header name. Predefined headers are provided, but can be edited or modified.
• Header Value – HTTP header value.

Note For a Live service, if Request Type is set to Manifest and HTTP Version is set to HTTP 1.1, Header Name must be set to Cache-Control and Header Value must be set to max-age=0. Each HTTP header policy must contain at least one rule.

Step 4 Click Save.

HTTP Header Policy Examples

• Chunk http 1.1 Cache-control max-age=3600
• Manifest http 1.1 Cache-control max-age=3600
• Chunk http 1.1 Cache-control max-age=0
• Manifest http 1.1 Cache-control max-age=0

Configuring Asset Lifecycle Policies

Asset lifecycle policies are used for Time-Shift TV (TSTV) window for Live capture.

Step 1 From the navigation panel, choose Media Workflow Manager > Resources > Policies > Asset Lifecycle Policies.

Step 2 Click Add to add a new Asset Lifecycle Policy. The Asset Lifecycle Policies dialog opens.

Step 3 Specify the following parameters:

• Asset Lifecycle Policy Name – Name of the asset lifecycle policy (required). The name is a string of up to 63 characters. Acceptable characters include uppercase and lowercase letters, numbers, periods (.), dashes (-), and underscores (_). The name must not begin with a period (.), and it is not case-sensitive.
• Type – Type of asset lifecycle policy. The only valid value is DVR Window.
• Description – Description of the asset lifecycle policy. The description is a string of any length, and can include uppercase or lowercase letters, numbers, and any special characters.
• Match Tags – Indicates whether the life cycle policy rules apply to an entire asset (Asset) or only to a segment (Segment). Segment is required for a Live service. MatchTags can be configured for both Segment and Manifest, and can be stored either locally (in virtual memory on CE workers) or remote (in NAS or COS storage).
• Time – Time in seconds after which the specified action is to be taken.
• Action – Action to apply to the asset or segment. Valid values are Move and Purge.
• Storage – NAS store associated with the rule.
• Enabled – Indicates whether the rule is enabled. Valid values are True (enabled) and False (disabled).

Step 4 Click Save.

Configuring Auth Profiles

Auth Profiles are authorization profiles that point to an auth provider. To set up an auth profile:

Step 1 From the navigation panel, choose Media Workflow Manager > Resources > Profiles > Auth Profiles.

Step 2 Click Add to add a new Auth Profile. The Auth Profiles dialog opens.

Step 3 Specify the following parameters:

• Name – Name of the auth profile (required). The name is a string of any length. Acceptable characters include uppercase and lowercase letters, numbers, periods (.), dashes (-), and underscores (_). The name must not begin with a period (.), and it is not case-sensitive.
• Type – Type of auth profile. The only valid value is swauth.
• User ID – User ID for auth profile.
• Access Key – Auth profile access key.
• Auth Server URL – URL for the auth server.
• Token Refresh Interval – Time in seconds after which the auth token is refreshed.
• Description – Description of the auth profile. The description is a string of any length, and can include uppercase or lowercase letters, numbers, and any special characters.

Figure 6-5 Configuring Auth Profiles

Step 4 Click Save.

Configuring ESAM Profiles

The Event Signaling and Management (ESAM) profiles defines ESAM multi-screen ad insertion.

Step 1 From the navigation panel, choose Media Workflow Manager > Resources > Profiles > ESAM Profiles.

Step 2 Click Add to add a new ESAM Profile. The ESAM Profiles dialog opens.

Step 3 Specify the following parameters:

• Name – Name of the ESAM profile (required). The name is a string of any length. Acceptable characters include uppercase and lowercase letters, numbers, and underscores (_). The user ID must not begin with a period (.), and it is not case-sensitive.
• POIS URL – Placement Opportunity Information System (POIS) URL of the ESAM server (required).
• Description – Description of the ESAM profile. The description is a string of up to 235 characters, and can include uppercase or lowercase letters, numbers, and any special characters.
• Version – Version of the ESAM profile. Choose a version from the drop-down list. Valid versions are OC-SP-ESAM-API-I01 and OC-SP-ESAM-API-I03.

Step 4 Click Save.

Configuring Key Profiles

The key profiles defines encryption profile.

Step 1 From the navigation panel, choose Media Workflow Manager > Resources > Profiles > Key Profiles.

Step 2 Click Add to add a new Key Profile. The Key Profiles dialog opens.

Step 3 Specify the following parameters:

• Name – Name of the key profile (required). The name is a string of up to 200 characters. Acceptable characters include uppercase and lowercase letters, numbers, and underscores (_). The user ID must not begin with a period (.), and it is not case-sensitive.
• KMS Type – KMS type used by the key profile. Valid KMS types are VGC (supports DRM types HLS-AES-128) and NAGRA.
• DRM Type – DRM type used by the key profile. The only valid DRM type is VGC-HLS.
• Description – Description of the key profile. The description is a string of up to 235 characters, and can include uppercase or lowercase letters, numbers, and any special characters.
• Key Service URI – Key service URI used to acquire the key profile (optional).
• Client License URI Prefix – optional client license URL prefix.

Step 4 Click Save.

Configuring COS Stores

Step 1 From the navigation panel, choose Media Workflow Manager > Resources > Storages > COS Stores.

Step 2 Click Add to add a new COS Store. The COS Stores page opens.

Step 3 Specify the following parameters:

• COS Store Name – Specify a name to identify the COS Store, must be unique.
• Container – Specify the container.
• Auth Profile – Choose the Auth Profile from the drop-down list.
• Description – Enter a name.

Figure 6-6 Configuring COS Stores

Configuring Publishing Templates

Step 1 From the navigation panel, choose Media Workflow Manager > Resources > Templates > Publishing.

Step 2 Click Add to add a new Publishing Template. The Publishing Templates dialog opens.

Step 3 Specify the following parameters:

• Name – Name of the template (required). The name is a string of up to 63 characters. Acceptable characters include uppercase and lowercase letters, numbers, periods (.), dashes (-), and underscores (_). The name must not begin with a period (.), and it is not case-sensitive.
• Description – Description of the template. The description is a string of any length, and can include uppercase or lowercase letters, numbers, and any special characters.
• Package Format – Package format supported by the template. Valid values are HLS (the default setting), HSS, HDS, CIF, and CIF-DASH-TS.
• Segment Duration (Sec) – For segmented files, maximum time, in seconds, to write to a file before starting a new segment (required). The segment duration must match the encoder boundary Point (EBP) configured on the encoder, or it must be a multiple of the EBP value.
• URL Pass Through – Enables MPE to distinguish common copy from unique copy publishing.
• Key Rotation (Sec) – Number of seconds to wait before using a new encryption key.

Step 4 Specify Package, Content Protection, and Transport parameters as appropriate. For example, package parameters can be HLS, HSS, CIF, or CIF-DASH-TS based on user preferences and requirements. For Package parameters, choose HLS for Apple clients, HSS for Microsoft players, or CIF for Common Intermedia Format.