Internal Release Notes – Q4 : 24.50.0 OpenTV Video Platform - DRAFT version

Release summary 

This release…  

Product Filter (ENTEL)

Product

Entel offers different products to Customers based on the Customer account profile (country). We do not have an MDS or cdf endpoint that will apply a filter based on the account profile.

A field on the product to indicate which profile it is targeted at.  Management of the field in OpCon / UIC.

[SHB] Watchparty - DWH notifications

Product

This feature is to reformat the RMQ messages raised from the GES module (for watch party) such that they are processed by DWH without any impact to DWH message queue handlers. 

[4iG] Support for consent mgmt platform - Didomi

Product

Consent collection, storage and applying consent details to the collection of activities / apply them to recommendations. 

• Unique ID generation per account that can be shared with Didomi backend. 

• URL Builder options 

• UAV payload information

[ENTEL] TiVO Metadata Ingest with Chile & Peru Ratings Definition (Q3 PI Continuation)

Customer specific

As part of ENTEL project EPG metadata will be from TIVO provided in TVA format using XML and requiring that TVA supplied ratings are split into both Chile and Peru rating schemes where applicable

Google Ad Manager Integration

Product

This feature covers the different aspects of google ad manager integration which are to be supported on the OPF side. The support is expected to be on the following items.

• Ingest the timeOffsets and the ability to turn ads on and off. [ flowing parameters ingested into MDS, CDVR and all variants of live - STCU, StartOver, LTCU )

• OpCon changes required for UI parameters. 

• Consent filterering at DWH and UAV not to store the consentBitMask

Continuation for OPCON (UIC) Push Messaging UI from Q3

Product

This feature is to support a new OpCon (UIC based) section that can control the building and distribution of messages to subscriber devices. OPF DMM will be used as the reference for topic/queue availability.

This will offer an operator the following capabilities:

1. A dedicated UI section in OpCon providing a publication centre for general messaging

2. This new centre is references to DMM to access in order to discover and target messages on-demand towards:

     a. Current topics defined in the deployment

     b. Current individual devices registered for messaging the deployment

     c. All current devices registered for a particular Account user

     d. New topics defined by the operator

3. Messages sent are traceable via DWH reporting / analytics

4. Messages sent can be of a number of forms, including:    Plain Text, HTML with images, HTML with deeplinks to application content and there should be an ability broadly to edit a message sent, via some recall/republish mechanism

[4iG] Granular control of session management

Product

4iG and Entel wish to be able to manage session concurrency based on classification of devices, in addition to the current support which is only at the account level, or restricted to unmanaged devices.

[Entel] User Device Management

Product

Entel wishes to allow their users to manage limited aspects of their devices. This includes:

• Device GET • Including corresponding device-profile info where present • Device PUT  (name only) • Device DELETE - only support for deletion of unmanaged devices.

[ENTEL] Country blocking

Product

An additional option added to geo-blocking to allow the operator to specify that the comparison is made using the location details on the account vs the location details returned from digital element. This is for Geo-blocking only and only applied at sign-on, not playout / content auth. 

[ENTEL] IN/OUT Home & Device Type (Continued)

Product

IN/OUT Home – The feature shall be supported on AndroidTV STB and SmartTVs only for FTTH User type

    • In-home determined by MAC address provided by the client
    • Comparison with HomeIP defined on the account 
    • Enforcement flags on both the account profile and device profile 

[ENTEL] Entel Geo-Targeting On/offnet Filtering

Product

The requirement is to filter by account profile to allow both country and OTT/FTTH filtering and On / Off-Net filtering. 

User-recordings performance improvements - EPG Queue

Internal

This feature is to address the User-Recordings perf issues faced in 4iG Production (for which work-around is provided currently)

Following are the perf issues observed

1. The consumption of EPG queues from MDS is slow. It is identified that auto delete functionality needs performance improvement. 

2. Check if RabbitMQ messages can be processed in parallel.

3. Jiras raised on 4iG will be tracked in this feature

After analysis, the enhancements provided for 2 scenarios.

1. While processing EPG queue - Enhancement for creation of recordings while consuming new episode on all the accounts which have placed the series recording to which this Episode belongs to.

2. While processing Jobs queue - Enhancement needs to be provided for auto-delete of old recordings while processing the validation job to which that event belongs for all the accounts who have placed the recording request on this event.

Only one queue enhancement is taken in Q4. In next release, enhancement for processing EPG queue will be taken.

[HOT]  View products from Node

Product

OpCon supports viewing the nodes and content associated with a product, OpCon supports viewing the products associated with content, OpCon does not support viewing products associated with nodes.

This feature is to support adding view products from the node screen. 

[HOT]  View Node Info

Product

This feature is to provide the ability to view node info without having to explicitly click 'view node'.

[HOT]  Support for Ad Insertion Profiles

Product

This Feature is for the CMS4/ML to provide the ability to add advertising metadata onto content, via association of that content with an Ad Insertion Profile.

[CLB] [PH3] - Update to channel maker and CEX for LKR migration

Customer specific

Claro use a different metadata field for client signalling (nPvrSupport), the proposal is the following:-

Channel maker adds the field ”nPvrSupport” in metadataSet for technical channels.

If in .csv a technical channel is not signalled for nPVR, then “nPvrSupport”=”false” &  “networkPvrSupport”=”false”.

If in .csv a technical channel is signalled for nPVR, then “nPvrSupport”=”true”

    • If the technical channel has “LKR” specified as one of its regions, then “networkPvrSupport”=”true”.
    • If the technical channel does not have “LKR” specified as one of its regions, then “networkPvrSupport”=”false”.
XSLT – Depending on current behaviour.  XSLT may need to only copy “nPvrSupport” flag and ignore “networkPvrSupport”=”false”.

[HOT][Ph2] SRM Validation & Reporting

Customer specific

This feature is to ensure that the SRM will function in an ML environment against SDP, or an OPF environment, against ADM/RMG, and to ensure that the MediaKind VSPP workflows have been validated - in the context of HOT

Altice US JIRA 211 - Q4

Customer specific

Address JIRA's raided by Altice

[ALTICEUS-211] [authFacade] registerDeviceAndGetToken call does not work with old token in request parameters - Jira (atlassian.net) (https://nagra-dtv.atlassian.net/browse/ALTICEUS-211)

[CLB] - Auth Facade API (isContentAuthorised)

Customer specific

Additional APIs are needed the Auth facade to cater for CLB PH4 migration of CAF functionality. 

Auth facade for CLB is extended to include the ML2 service GET /isContentAuthorised.  

Modify CPU/Mem changes for all Apps

Internal

This feature is to modify CPU-MEM, Min/Max PODS limits as per the new recommendations

[Platform] Upgrade Kubernetes to 1.31 and Kubernetes/Istio system components [MUST]

Internal

Keep up with all k8s system component new releases, bugfixes, new features, etc as per the AWS - Kubernetes and AWS EKS release calendar

This feature is to upgrade Kubernetes cluster to 1.31 for OPF. Upgrade all Kubernetes system components to the latest possible release compatible with k8s 1.31.

[k8s] destroy existing k8s cluster and upgrade to new k8s cluster

Internal

There is a risk to have in production, Kubernetes and/or other components no longer supported by AWS. K8s 1.28 will be out of support by November 26, 2024.

This feature is to implement all of the changes to have 1.31 during Q4 2024, and being deployed along.

[CLC] SSO [OPF-7185] - integrate to new CLC SSO API

Customer specific

This feature is to update the AGS to use Claro Columbia's new API for SSO authentication.

Making an A/B Test Result Permanent

Product

This feature is for the operator to decide to make either the A or B test version the permanent template for all users, or all users within the specified segment(s) when the test ends or when a user reviews the results.

A/B Test Targeting OPF Data Points (OPF Segments)

Product

This feature is for the Operator to be able to define segments 

• Use of data on Account and Profile entities (including Billing Address and properties set on Profiles)

• Could apply cross-device - e.g users who have not got a mobile app on their account should be in the segment on SmartTV

• Automatic definition based on segment data passed by the client (could be rolled into above)

• There is no need to support cases without Profiles (in such cases we’d use the Account → Default Profile)

Zapping time part 2: Reduce platform calls (FPS and PR) and SSM Kill with FTA

Internal

This feature is a provides a single interface to allow OTT player clients to obtain a DRM license and teardown and establish SSM sessions in a single API call.

This is a continuation feature for FPS and PR interfaces (Widevine previously delivered)

Genre/Channel based seeded Rail

Product

This feature is to support auto-generating Rails from the following inputs: Genre & Channel

Backend Search History

Product

This feature  is to  record or persist the user's search term and maintain the history. More specifically,

   • Record the user's search term and history.
   • An user/client api for retrieval of user's search history.  

Operator Deployment - Configuration Rationalisation

Internal

This feature to replace the previous Helm deployment and configuration management. This feature will move apps to be deployed using the Operator + Customize model. Goal being to reduce the complexity of managing system configuration particularly around new deployments and upgrades. This will move away from Helm/JQube deployments, managing configuration as follows:

    • Operator service in the cluster to manage deployments and configurations
    • Application definition for resources defined in a single YAML managed by development/devops teams
    • Versioned configuration overrides for customers/labs
    • Clean management of applying infra inc config maps
    • Move away from previous config map definition of Platform/Business/Technical

[Independent Services] CMS (Content Management Service) independent deployment

Internal

As per today, OPF product is deployed as monolithic release that is cut on quarterly basis. All OPF services are bundled and delivered together in an OPF release. Infra deployment code is deploying OPF service as a whole, including infra resources that are exclusively needed for those services.

This feature is to deploy and update OPF Business Services independently (independent deliverables & lifecycle) & owned by the CMS DevOps teams.

[UPVS] Separation of Config and ION Bundle Zip files

Internal

Currently the OPF team is responsible for all maintenance activities on UPVS. This includes provisioning new tenants and updates to the ION Bundle Zip files. 

There have been several cases when the ION team have needed to update the bundled zip files outside of normal UK working hours and this has caused an issue with at least one customer.

The proposal is to separate the UPVS configuration and ZIP file into separate repositories which will allow for different permission to be applied to each, thereby allowing the ION team to make their own updates.

MDS Next Gen - Metamorph : BTV support

Internal

This feature is to complete the implementation of remaining/pending functionality for entire BTV, tested/deployed and release of the API's :: /btv/programmes,  /btv/series,   /btv/products

[HOT]  Associate multiple products with multiple channels

Customer specific

A new mechanism is required in OpCon (and UIC) to be able to associate multiple products with multiple content. The specific case for HOT is the association of multiple products to multiple channels.

This feature is to approach this : :when an operator selects multiple products, they are presented with an option to bulk manage these products - which allows for management of common channels/content.

[cim-go]: AWS tech(rds version v1-v2 migration) stack upgrade

Internal

CIM-GO uses AWS aurora serverless v1 internally and recently amazon have announced the deprecation of v1 and it will no longer be supported by Amazon as of December 31, 2024. 

 There is need to migrate to v2 version, ideally before December 24. 

 This feature is to review the aws access/permissions based on the security guidelines and correct as necessary. 

CIM-NIS to export ingestion errors to DWH

Internal

As of today CIM-NIS reports to DWH only the filename.

This feature is to report as well complementary information about when the ingestion error occurred (e.g. channel not found, etc etc).

Extraction of VOD rules from CPM BRE

Internal

This feature is to extract VOD rules from CPM BRE. This deepens the two-tier CWM model either by extending JGS or building another JGS (leave deletion in MAS for time being)

Requirement is to move all VOD rules out of CPM into JGS or building another JGS which generate VOD jobs, move all customer related VOD rules out of Business rules engine.

Spring Boot upgrade of CWM solution merge to latest CWM

Internal

CWM has been upgraded to latest Spring Boot (3.x.x) version in Q3 2024 and hence all X-ray issues are fixed.

This feature is to merge the Stateless CWM solution, which is present in CWM Spring Boot 2.x.x version into latest CWM where Spring Boot 3.x.x is present.

[Independent Services] CWS (Content Workflow Service) independent deployment

Internal

As per today, OPF product is deployed as monolithic release that is cut on quarterly basis. All OPF services are bundled and delivered together in an OPF release. Infra deployment code is deploying OPF service as a whole, including infra resources that are exclusively needed for those services.

This feature is to deploy and update OPF Business Services independently (independent deliverables & lifecycle) & owned by the CWS DevOps teams.

MDS Next Gen - Metamorph: VOD Support

Internal

Content mappings are partially complete as part of the features in Q224, this feature is to implement the remaining mappings/aggregation/denormalization of contents and complete the data processing required for the following APIs: 

    • vod/editorials
    • vod/series
    • vod/products

[CPM Evolution] Removal of CPM specific business rules

Internal

The goal is to remove the CPM specific business rules entirely from the deployment

As part of CPM evolution we have removed         1. STCU rules from BRE during Q1 PI and  2. LTCU rules from BRE during Q2 PI

IN 24.Q4, CPM specific rules are removed

Replacement of BCM (Config Manager)

Internal

Replacement of BCM that allows runtime config / operator changes  to be upgrade safe.

This feature complements the Shipwright operator deployment good that managed deploy time configuration.

Rails Builder - Content Visibility Indicators

Internal

Currently we can add content to a Rail in the admin UI that's not returned as part of a client response. This is because there are a number of criteria that have to be met for a content to be visible. For example a content has to have at least one technical, be sold via a product etc. 

This feature is to add badges in the UI to indicate to the operator if the content is visible to the end client or not.

This will help the operator make an informed decision about what to add to a Rail and also help operationally with debugging content visibility issues. 

[OPF-7440]: Enhance caching in contentbuilder

Internal

Content Builder is caching failed responses from MDS downstream APIs leading to E2E issues when legit requests are performed.

Content Builder delivers back empty responses coming from the previous wrongly-cached requests.

This is getting 414 Request URI too large errors from MDS. This feature is the Content Builder should never caches this response and discard it from Redis.

[UIC] Channels and Products: Parity

Internal

This feature is for supporting below functionalities which are needed to achieve parity for opui-channels and opui-products with Operator Console.

• Image upload support for channel logo.

• Updating existing channel logo from the set of images across different aspect rations.

• Bulk operations support in datagrid.

• User preferences to be retained across the applications in UIC. 

Filter Live Rail Contents based on Profile Age

Internal

When user performs login with a user profile, the discover rails are not getting filtered according to the profile ratings. contentdelivery/v1/ does not filter rated events based on profile selected.

This feature is that the Discover screen should only show the content strip with kids rating content and hide/filter other strips.

Spill (Q3) A/B Testing Productization

Product

A/B testing feature is delivered early in 24.Q3 for IBC demo's. This feature is to include testing perf and functional and potential re-work/finalization of the A/B Test feature.

Zapping time: Reduce platform calls (Widevine only)

Internal

This feature provides a single interface to allow OTT player clients to obtain a DRM license and teardown and establish SSM sessions in a single API call.
Note:  this is Widevine DRM clients only at this time. 

Badging Entitlements in Rails

Product

Client requests for Rails content shall have an option to view the entitlement state of contents with respect to the Client account caller in Content Builder responses.

This feature is to mark Content items presented to a Client user with indication whether Content is entitled for playout or not.

Scope Calc Removal : Move migration API's from operator domain to admin domain

Internal

As part of the Scope Calc Removal we have implemented the migration api (durint Q3 PI) for the existing data in the production.

The migration API was implemented using operator domain. The scope of this feature is to move the migration api from operator domain to admin domain.

Compatibility matrix

OPF	Q4 : 24.50.STD0
DWH (24 Q4)
SSP (24.48) Q4

List of new issues

The following issues are newly opened in this OPF3_24.xxSTD0 release.

List of known issues

The following issues are still open (not resolved) in this OPF3_24.xxSTD0 release.

List of resolved issues

The following are the Critical & High severity issues resolved as part of the OPF3 (24.xx STD0) release.

Deprecated APIs