Release Summary
This release comes with the CIM-GO component, allowing operators with Gracenote to deliver new content channel via GN API Key. We have also added the support to push/publish LTCU assets extracted/generated at AWS MediaPackage assets to Lumen CDN, and serve it from there.
We are also bringing several improvements on the image service functionality.
Purge Productisation
Internal, SLA - @User
Needs Description
OPF2 ->OPF3 NPVR migration and metadata alignment
CLC - @User
Claro Columbia migration planning has identified a number of areas where differences in metadata creation may interfere with the operation of Clients in the transition from OpenTV STB. Transition here may mean Accounts that end up with additional ION Open Devices or OpenTV STB Clients that are migrated to use native OPF 3 APIs endpoints. Note that this has implications in other services such as NPVR. More generally in migration, synchronisation of UAV data between devices migrated/unmigrated may also be an issue.
Phase 1 CMS Migration & Ingest Validation - HOT
HOT - @User
For HOT Phase 1 migration (content management & NPVR)
(1) Validation that the CMS4 BTV and VOD data can be migrated correctly to OPF3
(2) Validation that post migration, subsequent BTV and VOD ingests can be successfully ingested into OPF3
HOT analysis is that HOT are using a CMS-4.23 ingest version for BTV and VOD and therefore compatible with OPF3 CIM-NIS.
Phase1 Live and VOD Ingest & Export Performance
HOT - @User
Value Statement - VOD
HOT currently use ML CMS for ingesting VOD metadata and products
HOT will migrate to hybrid OPF3 / ML platform with OPF3 replacing CMS-4 for content management
Requirement to validate the OPF3 CMS components can support HOT production ingest of VOD metadata and products covering both performance, scale and frequency
TBD - determine the current ingest frequency for BTV/VOD to define required performance thresholds.
Value Statement - LIVE
HOT
HOT currently use CMS-4 for LIVE metadata, products & R-EPG
HOT will migrate ML CMS components to OPF CMS components
Requirement to validate performance of CMS-5 for HOT LIVE ingest covering performance & frequency
TBD - determine the current ingest frequency for BTV/VOD to define required performance thresholds.
PRI/VOD VSPP / Aquila Validation against OPF3
HOT - @User
Ingest HOT specific data and test/validate the VSPP/MK Aquila integration.
Test/validate the PRI flows - nPVR recording workflows with VSPP and identify the gaps if any in OPF3.
Test/validate the VOD workflows as below and identify the gaps if any.
-
Transcoding with MK Aquila
-
Packaging with VSPP
nPVR User-Recordings Validation - Phase1
HOT - @User
This feature identifies, corrects and tests deviations from HOT Medialive 2.x NPVR behaviour as observed by a Client when contacting NPVR Locker Facade. The intent to is fully align behaviours prior to specific end-to-end device testing in the following quarter.
Workflow Status
HOT - @User
HOT use CMS4 to manage their VOD/nPVR workflows.
OpCon has a basic workflow screen but doesn't provide any link between related jobs.
Virtual Link Support
HOT - @User
HOT make use of nodes to manage series and season entities.
And, in order to have the same series within multiple parts of a catalogue tree they introduced the concept of virtual links.
They use a virtual to indirectly allow a node to have multiple parents.
Longer-term the aim is to move HOT to use content-groups to represent series/season instead of nodes.
However, shorter-term we will provide OpCon Support for management of these virtual links.
Render images from HOT's image repo in OpCon
HOT - @User @User
Extend the support for images within OpCon.
To include image support against nodes
Deployment of CIM-GO
Product, NCTC, Product Readiness @User
Following on from the development of CIM-GO - we need to actively deploy in the 4 x NCTC customers who use Gracenote EPG data
Altice-US CRM Migration - Phase 2 - OneCAS support
Altice US, SSP - @User
This feature is to track and additional CRM-GW changes required to support this such as:
1) CRM GW Changes to remove SDP
2) CRM GW only send to DLK for DLK-Devices
2a) DLK Device-lookup.
Credit limit logic -Ph2
Altice US - @User
Altice US currently uses an SDP feature to apply a credit limit to customers, this feature allows customer to purchase up to a limit for that day and thereafter the purchase will be rejected.
Nagra are proposing that this feature be implemented by Altice within their PPV service. Currently an ADM account has a creditSpent property, this need to be complimented by two other properties.
-
lastPPVPurchaseDate- String (date-time) -
creditLimit- Integer
Improve verbosity of CPM logs
Internal, Product Quality - @User
This feature is created for addressing CPM impacts.
- Following / Define common logging guidance
- increasing the verbosity of CPM Logs
- refactoring of logs on various level
Image Service Enhancements
Product @User
Improve the image service functionality
Images are the key to driving user interaction with the client, if you show the correct image then the users will consume more.
MongoDB credentials rotation improvement
Internal, OPF Security - @User
There has been some further discussion around the scope of this feature. SRE have identified some issues around Automated Key Rotation so the decision has been made that for the time being keys will manually rotated when a system is upgraded.
As such there is no longer a need to integrate the scripts for Automatic key rotation provided by SRE.
AWS Elemental MediaPackage integration with 3rd Party CDN
Product, Sports - @User
The Live-to-VOD assets or LTCU assets extracted/generated at AWS MediaPackage are directly served from origin/S3 bucket as of today.
The requirement/ask is to push/publish that asset to Lumen CDN and serve it from CDN.
Enable CIM-GO to deliver new content channel
Product, NCTC - @User
Content delivered from GN via the CIM-GO component is controlled by the GN API Key.
There will be occasions when the content delivered via this API Key changes (via contractual discussions between GN and the end-customer).
CIM-ON will need to be "ready" to cater for this change in content such that the impacts on NAGRA downstream systems are known and impacts are automated as much as possible.
OPF Java Heap Settings
Internal, SLA - @User
This feature is to rationalize the settings for heap and k8s pod memory so that the heap is always a % of the overall Pod memory e.g. 60%, this allows enough overhead for the JVM, container OS etc.
Content Discovery Enhancement - filter by device type
Product, Telecolumbus - @User
as a client I only want to return events that are playable on my device, so that it limits the amount of data returned and doesn't require client side filtering, this allows for quicker processing of guide data to be shown to the end user
Compatibility matrix
@User Please update.
|
OPF |
Q4 : 21.50.STD0 |
|---|---|
|
SSP Q4GA (21.48STD1 ) |
|
|
SSP Q1GA (23.10STD1 ) |
NOT STARTED |
|
DWH GIT Details– (https://gitlab.hq.k.grp/dtv-analytics/dtv-analytics/-/tree/DWH_REL_22Q4_STD1 git commit sha e59ebffe1c9f3c5d6183f4bb121d1932036fb298)
|
|
STD0
Deprecated APIs
|
Component |
API |
Description |
Deprecated in release |
Supported until |
|---|---|---|---|---|
|
IAS |
/v2/token |
Replaced by
|
2022 Q3 |
2023 Q1 |
|
IAS |
/v2/signout |
Replaced by
|
2022 Q3 |
2023 Q1 |