Changes

[[Category:Manual]] [[Category:Live TV]] [[Category:MIB3.0MIB React]] [[Category: 4GVP 25.212]]

[[File:CDNLives_3.png|center|1000px1500px|thumb|CDN Lives page]]  

! style="text-align:left;border-left:5px solid red;" | Name

! style="text-align:left;border-left:5px solid red;" | Source

! style="text-align:left;border-left:5px solid red;" | Streaming Type

! style="text-align:left;border-left:5px solid red;" | DRM Type

! style="text-align:left;border-left:5px solid red;" | Quality

! style="text-align:left;border-left:5px solid red;" | Is Low latency| Flag to indicate if it is Ultra Low latency (to deferentiate with legacy ones).| -|-! style="text-align:left;border-left:5px solid red;" | Is External

! style="text-align:left;border-left:5px solid yellow;" | Owner

=== Hashcode Editor DRM Protection ===

Hashcode Editor block allows you Allows to set DRM Protection for that Stream. The user can generate a new key for content encryption. This key will be inserted in the manifest file and validate (via the DRM Issuer) if the user has access/permission to watch the selected mediaor associate with an existing one.<br/>The [[File:GenerateButtonCDNLives_DRMProtection.png|middle1500px|center|thumb|70pxDRM Protection editor]] button generates <br />DRM Protection fields are described below:* '''Profile''' - Pick a profile. Each profile will have a new hashcodeset of Track Types. (Example: Default, which can be used by other cdn lives that points to itSports)* '''Name''' - Name.* '''Date''' - Date.* '''Content ID''' - Content ID.* '''Content Key Base64''' – Content Key Base64* '''Content Key Hexa''' – Content Key Hexa. We have to accept the pop alert* '''Track Type''' - Example: AUDIO, HD, to confirm this actionSD.* '''Enabled''' - Enabled.<br>

* '''PlayReady DRMProfile Selection: '''<br />If This dropdown contains PROFILE options.The available options are dynamically loaded from the DRM Type field is PlayReadybackend, simply click on specifically from the [[File:Regenerate3.png|middle|80px]] button to generate a new set of keys and automatically will generate a set of PlayReady keys that can be used for Live OTT signal encryption:* Playready Key ID - ID for PlayReady Key.* PlayReady Content Key Base64 - Key created profileOptions property in 64 bitsVALUE.* PlayReady Content Key Hexa - Key created in HexadecimalA validation check ensures that these values are properly populated.<br>[[File:HashCodeEditorPlayReadyIt's important to note that the PROFILE field is not part of the MEDIATYPE (GVP_CONTENT_KEYS) of the DrmProtection component but instead belongs to the MainForm (CDN_LIVES).png|800px|center|PlayReady DRM Hashcode editor]]<br>AlternativelyHowever, you can click in the [[File:AddExisting.png|middle|80px]] button. A dialog will be open to select an existing set of keys so you can choose the key you wantwe still need it within DrmProtection for critical backend validations. Take into account that if you link an existing key to this CDN liveTherefore, we always keep it will be unlinked from updated with the previous CDN liveuser's selection.

* '''AES EncryptionNew Generate Key:'''<br />If Enables the Streaming Type field is HLS, simply click on the [[File:Regenerate3.png|middle|80px]] button to generate a new set creation of keys and automatically will generate a new AES key that can be used for Live OTT signal encryption:* HLS Key Seed - The key of Hashcode created.<br>[[File:HashcodeEditorAESHLS.png|600px|center|thumb|AES encryption Hashcode editor]]<br>Alternatively, you can click in the [[File:AddExisting.png|middle|80px]] button. A dialog will be open to select an existing set of keys so you can choose the key you want. Take into account that if you link an existing key to this CDN live, it will be unlinked from the previous CDN live.<br />

*'''DASH EncryptionRemove Button:'''<br />If the Streaming Type field is DASHAVC or DASHHEVC, simply click on the [[File:Regenerate3.png|middle|80px]] button to generate a new set of keys and automatically will generate a new DASH keyS that can be used for Live OTT signal encryption:* DASH Key ID - ID for Dash Key.* DASH Content Key Base64 - Key created in 64 bits.* DASH Content Key Hexa - Key created in Hexadecimal.<br>[[File:HashcodeEditorInfoDash.png|600px|center|thumb|DASH encryption Hashcode editor]]<br>Alternatively, you can click in Use the [[File:AddExistingDeleteRed3.png|middle|80px30px]] button. A dialog will be open to select an existing set of keys so you can choose the remove key you want. Take into account that if you link an existing key to this CDN live, it will be unlinked from the previous CDN live.

To get data information to setup packager content protection, you can click *'''View Button:''' By clicking in the [[File:GetContentProtectionInfoButtonPreview.png|middle|150px30px]]button in each key, you can preview Contents Protection and PSSH Box Content. A pop-up message is displayed with this information.<br>[[File:GetContentProtectionInfoMessage.png|600px|center|thumb|Data information to setup packager content protection]]<br /><br />

[[File:BPointEditor_3.png|800px1500px|center|thumb|BPoint editor]]

=== [[File:New3.png|middle|40px60px]] Create ===CDN lives can be created by most of the operator profiles (EPG Manager, OB Admin). Use the [[File:New3.png|middle|30px60px]] button to create a new CDN live and configure it. Once finished, save changes by using the [[File:Save3.png|middle|30px60px]] in the CDN live page.

=== [[File:BulkEdit3.png|middle|40px60px]] Edit ===

Once finished, save changes by using the [[File:Save3.png|middle|30px60px]] in the CDN live page.

Once finished, save changes by using the [[File:Save3.png|middle|30px60px]] in the CDN live page.

Once finished, save changes by using the [[File:Save3.png|middle|30px60px]] in the CDN live page.