Configuring Media Workflow Resources · 7-6 Cisco Virtualized Video Processing Controller User Guide Chapter 7 Configuring Media Workflow Resources Configuring Policies Note For a

Cisco

C H A P T E R 7
Configuring Media Workflow Resources
This chapter provides procedures for configuring media workflow resources – the channels, policies, profiles, templates, archives, and other resources that can be referenced from multiple media workflows. Media workflows bind policies, templates and other resources together to ingest and package assets for one or more media sources.

Configuring Media Sources

Configuring an ATS Channel

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

Step 2 Click Add (+) to add a new channel. The Create ATS Channel dialog opens.

Figure 7-1 Create ATS Channel Dialog

7-1Virtualized Video Processing Controller User Guide

Chapter 7 Configuring Media Workflow ResourcesConfiguring Media Sources

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

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

Note ABR profiles are not sharable among ATS channels. If you use the V2PC GUI to create ABR profiles within an ATS channel and then delete the ATS channel, the ABR profiles associated with the channel are also deleted. However, if you create ABR profiles outside the V2PC GUI and then share them among multiple ATS channels, you cannot delete the shared ATS channels from within the V2PC GUI.

Step 4 Click OK.

Configuring an ATS Channel Lineup

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

Step 2 Click Add (+) to add a new channel lineup. The ATS Channel Lineups page opens.

Figure 7-2 ATS Channel Lineups Page

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

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

Step 5 Click Save.

7-2Cisco Virtualized Video Processing Controller User Guide


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 ArchivesMedia archives are storage locations for stream segments that have reached a predefined archive time. Segments stored in media archives can be reconstituted for later use and then re-archived.

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

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

Figure 7-3 Media Archives Page

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.

Step 4 Click Save.

Configuring NAS Media Sources

Step 1 From the navigation menu, 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 page opens.

Figure 7-4 NAS Media Sources Page

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 are uppercase and lowercase letters, numbers, periods (.), dashes (-), and underscores (_). The name must not begin with a period (.) and 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.

Step 4 Click Save.


Chapter 7 Configuring Media Workflow ResourcesConfiguring Policies

Configuring Policies

Configuring HTTP Header PoliciesThe HTTP header policies control the HTTP headers for publishing content.

Step 1 From the navigation menu, 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.

Figure 7-5 HTTP Header Policies Dialog


• Name – Name of the HTTP header policy (required). The name is a string of any length. Acceptable characters are 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.


Chapter 7 Configuring Media Workflow ResourcesConfiguring Policies

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 OK.

HTTP Header Policy Examples

• Chunk http 1.1 Cache-control max-age=3600 (recommended for VOD; 0 for Live)

• Manifest http 1.1 Cache-control max-age=3600 (recommended for VOD; 0 for Live)

Configuring Asset Lifecycle PoliciesAsset lifecycle policies control the Time-Shift TV (TSTV) window for Live capture.

Step 1 From the navigation menu, 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.

Figure 7-6 Asset Lifecycle Policies Dialog


• 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.


Chapter 7 Configuring Media Workflow ResourcesConfiguring Profiles

• 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.

• Policy Rules – Specify the following:

– Match Tags – Indicates whether the rules apply to an entire asset or only to a 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 OK.

Configuring Profiles

Configuring Auth ProfilesAuthorization (auth) profiles are profiles that point to an auth provider. To set up an auth profile:

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

Step 2 Click Add (+) to add a new auth profile. The Auth Profile dialog opens.

Figure 7-7 Auth Profile Dialog




• 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.

Step 4 Click OK.

Configuring ESAM ProfilesThe Event Signaling and Management (ESAM) profiles define ESAM multi-screen ad insertion.

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

Step 2 Click Add (+) to add a new ESAM Profile. The ESAM Profile dialog opens.

Figure 7-8 ESAM Profile Dialog




• 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 OK.

Configuring Key ProfilesThe key profiles define encryption profiles.

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

Step 2 Click Add (+) to add a new key profile. The Key Profile dialog opens.



Figure 7-9 Key Profile Dialog


• Key Profile Name – Required name for the key profile. 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.

• Description – Optional description for 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.

• 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. Valid DRM types are VGC-HLS and CENC-DASH CENC. Choose CENC-DASH to enable Common Encryption Scheme (CENC) for DASH.

• Key Service URI – Optional key service URI used to acquire the key profile.

• CENC Priority – Required when CENC DASH is enabled (DRM Type = CENC-DASH). Choose Widevine or PlayReady as appropriate.

• Widevine – Choose Enable or Disable as appropriate.

• License Acquisition URL – Required if Widevine is enabled; optional if Widevine is disabled.

• Widevine Provider – Optional field used to identify the provider for Widevine, if used.

• Playready – Choose Enable or Disable as appropriate for PlayReady content protection.

Step 4 Click OK.


Chapter 7 Configuring Media Workflow ResourcesConfiguring Storage

Configuring StorageCisco Cloud Object Storage (COS) provides virtual object-based storage for V2P media workflows. COS storage nodes are organized into clusters to provide a distributed, scalable, and resilient storage solution.

Configuring COS Stores

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

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

Figure 7-10 COS Stores Page


• COS Store Name – Specify a name to identify the COS Store. The name must be unique.

• Container – Specify the container.

• Auth Profile – Choose the auth profile from the drop-down list.

• Description – Enter a name.

Step 4 Click Save.

Configuring Network-Attached Storage

Step 1 From the navigation menu, choose Media Workflow Manager > Resources > Storage > Network-Attached Storage (NAS).

Step 2 Click Add (+) to add a new NAS store. The Network-Attached Storage (NAS) page opens.


Chapter 7 Configuring Media Workflow ResourcesConfiguring Templates

Figure 7-11 Network-Attached Storage (NAS) Page


• Name – Name of the NAS store (required). The name is a string of up to 30 characters. Acceptable characters are uppercase and lowercase letters, numbers, periods (.), dashes (-), and underscores (_). The name must not begin with a period (.) and is not case-sensitive.

• Description – Description of the NAS store. The description is a string of up to 100 characters, and can include uppercase or lowercase letters, numbers, and any special characters.

• Share Path – Share path used by the NAS store on the network.

• NFS Version – Version of the Network File System (NFS) used by the NAS store. Valid versions are 3.0 and 4.0.

• Start and End IP Address – The first three bytes of the Start IP Address must match those of the End IP Address. For example, 1.1.1.1 to 1.1.1.2 is a valid start and end IP address range, but not 1.1.1.1 to 1.1.2.2. For a single server, the Start IP Address and the End IP Address are the same.

Step 4 Click Save.

Configuring Templates

Configuring Publishing Templates

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

Step 2 Click Add (+) to add a new publishing template. The Publishing Templates dialog opens.

Figure 7-12 Publishing Templates Dialog




• 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, and DASH-MP4.

• Segment Duration – 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.

• Key Rotation – Number of seconds to wait before using a new encryption key.

• DVB Bitmap Pass Through – Only applicable to HLS package format. Enables passthrough of DVB bitmap subtitle PID to downstream applications. The DVB bitmap subtitle data in the source is retained in the TS segments.

• DVB Bitmap To ID3 – Only applicable to HLS package format. Transforms DVB bitmap subtitles to SMPTE Timed Text (SMPTE-TT) format. SMPTE-TT XML files containing subtitle images are tagged by the ID3 tag and embedded as timed metadata in TS segments.

• Subtitle Policy – Subtitle policy associated with the template.

Step 4 Specify the following Package options:

• Stream Configuration – Configure the stream as described in Stream Configuration, page 7-14. The stream can be HLS, HSS, CIF, or CIF-DASH-TS based on user requirements. Choose HLS for Apple clients, HSS for Microsoft players, or CIF as appropriate.

• Variants – Enables you to provide a subset of video and audio bit rates to specific devices. For example, you could create a variant called mac and assign three top bit rates to it, and then create another variant called ipad and assign three lower bit rates to it.



– Name – Name of the variant (required). The name is a string of any length, and can include uppercase or lowercase letters, numbers, and any special characters.

– Selective Publish – Supports selective publishing of DASH video profiles as detailed in –If you configure 1.05 MB and 2.9 MB, both 1 MB and 3 MB are displayed in the manifest because both are within 5% of an actual bit rate., page 7-15. When set to False, no video is filtered and the system appends these profiles to the manifest. When set to True but without specifying any video streams, no video is filtered.

Note Selective Publish is supported for HLS content through the VMP Service Manager GUI. For details, see the Cisco Virtual Media Packager User Guide for your VMP release.

– Default Audio Stream (PID) – Name of the default audio stream associated with the variant.

– Enable SMPTE-TT – Enables (if True) or disables (if False) SMPTE Timed Text format for the variant.

– Enable WEBVTT – Enables (if True) or disables (if False) Web Video Text Tracks format for the variant.

– Enable CC608 – Provides the option to disable or enable pass-through of CEA-608 closed captions.

– Enable CC708 – Provides the option to disable or enable pass-through of CEA-708 closed captions.

• Video Streams – Identifies the individual variants by bit rate in bits per second and resolution in pixels.

• Content Protection – Specifies the DRM method.

• Transport – Specifies the HTTP transport policy.

Step 5 Click OK.

Stream Configuration

The Stream Configuration table in the Publishing Templates dialog displays the following parameters for each stream associated with the selected variant:

• Type – Type selections are Audio, Subtitle, Video, ID3, UserConfig (required).

• Action – Update or Disable Stream Configuration (required).

• Language – Language used for the stream, such as en for English.

• PID/ID – ID of the PID.

• Codec – Format of the stream, such as AAC, DD/AC-3, DD+/EC-3.

• Bitrate (bps) – This column is available when the order of the variant is BITRATE. The bit rate that you enter must be within 5% of an actual bit rate. The output manifest will include these profiles with the order user specified.

• Name – Name of the output stream. The name is a string of any length, and can include uppercase or lowercase letters, numbers, and any special characters.

• Language – Language used for the output stream, such as en for English (required).

Click the appropriate icon to add, edit or delete, then click Save to save your settings or Cancel.

When configuring bit rates for video and audio streams, keep the following considerations in mind:



• The order in which you configure the bit rates is the order in which they are displayed in the manifest.

• The bit rates must be within 5% of an actual output stream generated by the source. Otherwise, the system excludes that bit rate from the manifest.

• If none of the bit rates in a list is within 5% of an actual bit rate, the VMP generates a 404 error code when you request a manifest.

• If you do not specify a list of bit rates, then the VMP includes all of the bit rates generated by the source in the manifest.

For example, if you have a Digital Content Manager (DCM) that generates video bit rates of 1MB, 2MB, 3MB, 4MB, and 5MB:

– You can configure video bit rates of 1 MB, 4 MB, and 5 MB to display them in the manifest in descending order, or of 5 MB, 4 MB, and 1 MB to display them in ascending order.

– If you configure 1.5 MB and 4 MB, only 4 MB is displayed in the manifest. 1.5 MB is not within 5% of an actual bit rate.

– If you configure 1.5 MB and 3.5 MB, the VMP generates a 404 error code because neither bit rate is within 5% of an actual bit rate.

– If you configure 1.05 MB and 2.9 MB, both 1 MB and 3 MB are displayed in the manifest because both are within 5% of an actual bit rate.

Configuring Selective Publishing

Selective publishing lets you configure DASH I-frame video stream assets in a selection of video profiles, or variants, to tailor the resolution and frame rate of the stream to specific TV and mobile display devices. Only assets matching the specified filter conditions are published.

Variants for mobile devices support HE-AAC audio profiles only. Variants configured for TV delivery support either HE-AAC or AC3 audio profiles.

Regarding filter conditions, either resolution or bit rate, or both, can be specified. If resolution is specified, only assets that exactly match are published. If resolution and bit rate are both specified, the settings should be compatible. In the event of a conflict, resolution takes priority over frame rate.

To enable selective publishing for a DASH video asset from the V2PC GUI:

Step 1 From the V2PC GUI navigation menu, choose Media Workflow Manager > Resources > Templates > Publishing.

Step 2 Choose DASH-MP4 as the Package Format.

Step 3 Choose Publish Template > Package > Variant.

Step 4 In the DASH publish template, choose True for Selective Publish.

Step 5 In Video Streams, add the required resolution (in pixels) and bit rate (in bits per second) filter conditions.

Note If there are filters specified in video streams but no video assets match them, no video is output. If there are multiple filters specified in video streams, video assets matching any filter are published.




Documents

Configuring Media Workflow Resources · 7-6 Cisco Virtualized Video Processing Controller User Guide Chapter 7 Configuring Media Workflow Resources Configuring Policies Note For a