Internal Release Notes – 25.Q2 : (25.26.0) OpenTV Video Platform - DRAFT version

Release summary

This release…

User Recordings Enhancement - Series Discovery & Season Filter

Product

This feature is to support series discovery (e.g. what recorded seasons do I have access to) and recordings retrieval by season.

User Recordings Enhancement - Time Window

Product

Placeholder feature to allow User Recordings to support the specification of a time window in the GET request.

Use Case addressed : matching EPG data with UR data to show recording info (14 days of EPG, 90 days of rec) - UR to return list recordings for a given period of time like GET .../cdvr/v2/recordings?fields={“id”, ...}&filter={"period.start":{"$gte":1722933196},"period.end":{"$lte":1724747596}}

[Cost Optimization] Optimize eMDMC profile (based on current production usage)

Internal

Purpose of this feature is to validate optimized eMDMC profile based current production observations, to improve OPF cost efficiency.

Feature will consist of:

Collecting resource & HPA usage on eMDMC production platforms (CLC, 4iG, ...)
Propose eMDMC factory settings recommendations
Update factory settings recommendations into 25.Q1 release
Validate optimized eMDMC factory settings recommendations

[OPF] Upgrade Atlas MongoDB to 8.0 on 23.Q4, 24.Q2, 24.Q3 and 24.Q4 Baselines

Internal

Mongo DB 6.0 will be End of Life by July, 2025 & Mongo DB 7.0 will be End of Life by August, 2026.

This feature is to do the database upgrade based on various factors like bugfixes, taking advantage of new features and most important is to be in line with the official Database Release Support.

[ENTEL] Purchase Service integration

Customer

This feature supports ENTEL requirements to pre-validate Client purchase service requests via a call to an ENTEL purchase authorisation service. Where authorisation is granted the OPF Purchase service will proceed to add the appropriate entitlement for the Client caller OPF Account. If rejected then no OPF entitlement will be added for the OPF Account.

This provides an adapter ahead of standard Nagra Purchase Service to perform the ENTEL specific service requests, and where successful then calls the standard Nagra Purchase Service.

3rd Party Bundling/Add On Integration (Bango)

Product

Support initially Netflix entitlement workflow for 4iG : Signup, Create Entitlement, Update Entitlement, Remove Entitlement, Suspend Entitlement, Token Refresh for Signup, Upsell/Downgrade

Supports generic product implementation to include synchronous and asynchronous use cases from Bango.

A/B Testing XRM Segmentation Integration

Product

The integration with XRM to retrieve user segments

The ability for customers to bulk load segments from CRM systems - how those segments get into OPF.

Import of segments via bulk API or flat file
- Matching of user IDs and properties of the profile
- Could be part of/extension of existing CRM / Profile API’s
Automatic definition of segments from XRoadMedia APIs for segmenting users

The process is/will be that the new service periodically gets segment data from the source XRM or another, The new segment ingest service is then responsible for creating topics. On the call earlier we agreed that the operator does not need to be able to trigger this.

The flow for customer segments would be that the operator adds a segment to the account on the CRM system these new segments are copied over to OPF as part of the normal account creation/update flow

The new segment ingest service (again) is then responsible for periodically checking for new segments added to accounts and updating the segments list, the number of profiles related to a segment and creating notification topics if they don’t exist.

User-recordings performance improvements for 4iG - Jobs queue

Internal

This feature is to address the performance issues observed in 4iG production.

Address the slowness in the consumption of EPG queues from MDS. It is identified that auto delete functionality needs performance improvement.
Process the RabbitMQ messages in parallel.

Operator Deployment - Configuration Rationalization - Q2

Internal

This feature is in continuation of 25.Q1 to complete the implementation of [ODM] Shipwright support & [Eas-Dispatcher] Shipwright support

[NG MDS]: Metamorph & SF integration with Elastic

Internal

Search functionality is moved directly to Search Facade front end using the Elasticsearch that is performance tested with the customer data & use cases.

UIC A/B Testing Get Data

Product

This feature is to display any real AB data in UIC. UIC to replace the calls to the DWH API’s with SQL requests & UIC is able to connect to Redshift with a secure connection user/password service account per operator. UIC displays the A/B test results in the Rails builder screen.

[HOT] ION Export Transformation OPF3->ML

Customer

Phase 1 of the HOT migration replaces CMS4 and LKR with OPF3 services. During this phase, the HOT client devices still interface directly with ML.

HOT may want to utilise an ION application, which means that the metadata present in OPF3 will need to support both existing devices via export to SDP/MDS and ION devices, via ingest of the CMS4 data into a structure suitable for consumption by ION.

The purpose of this feature is to ensure that ML client application still works following addition of support for ION.

[HOT] Support for Ad Insertion Profiles

Customer

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

[HOT] CMS4 data compatibility with ION

Customer

HOT Phase1 migration replaces CMS4 and LKR with OPF3 services. During phase 1, their client devices still interface directly with ML.

[HOT] Extend URLBuilder to generate playback URL for ION

Customer

HOT may want to utilise an ION application. The playback URL isn’t carried within the metadata meaning that URLBuilder is required to generate the playable URL.

Notification of RMG entitlement state changes to Client apps

Product

ION/Client application devices are notified when one of their signed-on Account entitlements change status, either subscribed or unsubscribed.

Secure CAS or Serial number backed sign on

Product

The DAS Integration Effort focuses on securely validating and managing device identities within the platform while ensuring compliance with Android policies. This effort streamlines device onboarding by binding device IDs to user accounts using a secure BLOB and validating them against OPF. To maintain compliance, the effort differentiates between persistent and app-specific IDs while leveraging Android Credential Manager for seamless authentication. It also addresses key security concerns, including device integrity, lifecycle consistency, and regulatory adherence, ensuring a robust and secure authentication framework.

Extraction of VOD rules from CPM BRE

Internal

This feature is a continuation of 25.Q1 and to perform the functional & performance regression tests.

This feature deepens the two-tier CWM model either by extending JGS or building another JGS : move all the VOD rules out of the CPM into JGS & move all customer related VOD rules out of the Business rules engine

[CLB] SCP-305 Bulk Create/Delete of Entitlements

Customer

Claro Brazil have requested changes to allow for Bulk creation of Entitlements & Bulk Deletion of Entitlements.

This solution must work in environments where: CRM-GW is deployed & CRM-GW is not deployed.

Guest (Anon) User Location check

Product

Operator will select countries allowed for guest user in OpCON settings. Anyone in COUNTRIES can sign in on a guest account. Anyone outside COUNTRIES requires a standard account with username and password sign on. Optionally, in COUNTRIES users can sign on rather than use the guest account.

If a user attempts to use the guest account whilst not in the country defined in config then return error code 442, the client will then force the user to sign in with a unique account.

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

Product

Allow the user to set values within the OPF platform as targets for A/B Testing

Example

Device Profile
In-Home
Country from Billing Address
OnNet
Profile filter string
Account Profile Name
Premium or Standard Subscriber (Any paid product = premium)

The Operator must be able to define segments.

DWH Redshift SSO and MFA Sign On - Staging/Prod integration & industrialization

Internal

Feature to track impact on SRE to enable the DWH SSO feature

To deploy a nagra-dwh client into the nagra-opcon realm to integrate with AWS IAM Identity Center.

Deploy MongoFullExtractor for Atlas MongoDB [DWH]

Internal

When customers/GOS team raise bugs related to data missing or mismatch between MongoDB and DWH, SRE runs "Mongofullextract" tool on MongoDB and share the export files with DWH, Data will be synchronized with DWH by importing these exports.
This feature is to run MongFullExtractor when needed (ON demand) from DB Tools triggered by Jenkins Job.

[CPM Evolution] MAS Job Extraction

Internal

The feature aims at removal of all job handling (CWM) interactions in MAS to achieve business service isolation and better job management

[4iG] Change default sort order of UserProfile get responses

Customer

This feature is to change the default sort order of UserProfile response to creation date of candidate userprofiles, for more direct use by Client applications.

RAILS Blueprint / KvP Enhancements

Product

This feature is for RAILS Builder's flexibility in defining key/value pairs and blueprints has enabled various functionalities and entire features without requiring dedicated first-class support in the interface. However, this approach comes with a key requirement: the app(s) must recognize these specialized RAILS and RAIL items and explicitly map them to meaningful representations within the client UI. Historically, there has been no alignment between values used in the apps and as such there is a significant difference in how they expect the RAILs data to be delivered. These specialized RAILS and RAIL items are manually configured for each deployment.

Metamorph REX Transform

Internal

Metamorph now replaces MDS as the publisher of RabbitMQ messages containing metadata for events, channels, content, and series. These messages follow a newly standardized, generic schema designed to support multiple downstream systems such as NCanto and other recommendation engines if required. REX has been enhanced to consume this unified format, transforming it into the appropriate structure for each target system.

Rails Preview Mode - Live View

Product

This feature is to Preview the layout of the rails template.

Show with the look and feel of the client device, Allow time travel forwards (backwards, not really), Selection of device type,

Setting of segments - targeting both A/B and segment level should result in the screen rendered being as per the end users experience.

Show the components (blueprints as they would appear on the client

Rails must be clickable and the preview should support navigating templates (screens)

Standard Rail Blueprints

Product

This feature aims to make default, standardised blueprints (specifically for ION, but also with consideration for 3SS) available out of the box for each deployment, saving time and eliminating the possibility of human error in recreating the same blueprints across multiple environments. These blueprints are intended to be used in all future implementations, and replace any existing configuration currently in place.

Rails Builder Improvements (Bucket)

Internal

This feature is to make several small changes to improve the rails builder user experience.

Visual Search, Review the default number of items for each rail type, Rails builder UX needs topage, Blueprints need localizable text field

Rails Scheduling - Basic

Product

When moving to the UIC version of Rails Builder, we decided to drop the scheduling screens and functionality as it was not in use by any operators. With the introduction of A/B testing, we have added the ability to schedule a rail, importantly, this is individual rail scheduling and not layout scheduling,g which was the previous solution.

This feature sets out to simplify and visualize the process of scheduling a rail in UIC rails builder.

[NG MDS]: Metadata service APIs

Internal

This is the feature for MDS services or APIs, based on metamorph transformations and views.

A new module, within metamorph context, light weight, shipwright based, independently deployable, scalable for APIs. All the existing APIs in MDS should be implemented/supported, compatible.

It should comply with the requirements such as scalability, performance, caching, flexibility, simplified API

Enhancement request for UR AutoDelete

Internal

Auto delete is the functionality available in User-recordings which deletes the oldest unprotected recordings if quota is not available to create new recording. Today, it either deletes the space of oldest episode of series or a normal recording, not the oldest one irrespective or normal/series recording.

In this feature the enhancement is to delete the oldest one irrespective of normal or series recording.

[OPF] Upgrade PostgreSQL RDS Major version from 13.18 to 16.x

Internal

This feature is to upgrade PostgreSQL RDS to latest 16.x version.

Additionally, Explore the procedure to move to 15.x or 16.x version , if possible with no downtime. (This needs to be validated)

The reason being PostgreSQL 14.x will be EOL by Feb, 2027 but 15.x will be EOL by 2028. So sooner we move to higher version better

Self-service OPF logs access for customers (HTTP API access logs)

Product

Today customers and SI teams need strong and supports from the SRE/Ops/R&D teams to diagnostic customer issues.

Proposal is to provide self-service access to our fronting HTTP API access logs, and selection of OPF application transaction logs, so they'll improve their troubleshooting autonomy.

Upgrade RabbitMQ from 3.12.1 to 4.x

Internal

This feature is to upgrade the RMQ as the current RabbitMQ is running on 3.12.1 Community Version which is End of Community Support by Feb, 2024

Note: RabbitMQ Community versions have a short lifecycle, reaching end-of-life (EOL) quickly.

We're also experiencing few PERF Related issues with RMQ stack from Customer Environments
Native AMQP 1.0 in RabbitMQ 4.0 provides significant performance and scalability improvements compared to AMQP 0.9.1 in RabbitMQ 3.13.

[NG MDS]: Metamorph EPG updates/messaging to client devices

Internal

This feature is to support sending/pushing messages to client devices via DMM.

The current MDS uses DMM's REST APIs to send/push messages. For ex: EPG updates are pushed to client devices via DMM.

Instead of REST, this feature is to have rabbit interface at DMM, so that NG MDS can send rabbit messages to DMM, which then does the end user device understandable message transformation before pushing them to client devices.

Upgrade Neo4J DB from 4.4.30 LTS to 5.26.2 LTS

Internal

Currently, Neo4J is running on 4.4.30, which is scheduled to reach its end of life on November 30, 2025.

Given the complicated upgrade schedule of our OPF Customers, it's important to upgrade this at the earliest as part of OPF 25.Q2 Baseline.

Note: 5.26 LTS (Long Term Support) was only released on last December.

User-recordings performance improvements - EPG Queue

Internal

User-recordings is facing some perf issues in 4iG production. This feature is created to address those perf issues.

Following are the perf issues observed

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

Check if RabbitMQ messages can be processed in parallel.

Jiras raised on 4iG will be tracked in this feature

After analysis, the enhancements are provided for 2 scenarios.

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.

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.

[NG CMS] ID Management - Phase 1

Internal

This feature is to

Modify Present CPM v1 and v2 REST API implementation according to ID Management feature's Database Model change.
Update Services implementation as per the need.
Update Cypher Queries as per the need, to handle Compatibility block and new Model fields.
Update RabbitMQ message generation layer to send the "ids" as per the Compatibility block field values.

[HOT] Auto association of episodes to seasons

Customer

HOT manually associate episodes to series/seasons within OpCon. The purpose of this feature is to enable this association to be automated.

[OPF] Upgrade Elasticsearch Cluster (DB) from 6.2 to 8.17.x

Internal

Currently, ElasticSearch DB cluster is running on 6.2 version which is End of Life couple of years ago. This feature is to address this and following related issues:

No authentication access control in current version of Elasticsearch implementation
Data transfer to ES is not secure
Monitoring is not up to date with ES specific metrics or dashboards

[SHB][D+][Disney+] New endpoints and metadata updates

Customer

This feature is to update D+ adapter to new endpoints and change of schema in metadata feed.

D+ are deprecated their current metadata feed endpoints in April 2025. For their new endpoints, D+ have made some changes to their JSON metadata structure, including the existing content IDs. This feature is to update CIM-DPLUS to new JSON metadata model.

Enable caching at Cloudflare level incl. complex caching control (geofiltering, max-age rating, etc.)

Internal

This feature is to Reduce latency and costs by enabling caching at Cloudflare level for APIs that support it.

Activate caching at the Cloudflare level to improve performance and reduce costs.
Ensure that Cloudflare follows the Cache-Control Header from our response.
Work with R&D to test and validate the new caching setup.
OPF3 monitoring provides caching metrics retrieved from Cloudflare

[NG MDS][Compatibility mode]: user-recordings interaction with metamorph

Internal

This feature handles the metamorph implementation of the rabbit messaging compatible with existing user-recordings.

Replacement of BCM (Config Manager)

Internal

This feature is a continuation from 25.Q1 that handles the migration of components from using BCM APIs to Config Manager APIs.

[HOT] Redo Failed Workflows

Customer

This feature is to address the gaps in the OPF3 implementation of job REDO when compared to CMS4.

This feature is for HOT that requires following support:

Ability to perform a REDO of VOD content workflow for content that contains multiple technical versions. Specifically, in the case of HOT, an OTT and a cable technical version.
Required in OPF Versions 24.Q4 (Business Rules) and 25.Q2 (JGS)
Ability to REDO freshly ingested content directly into OPF3, and content migrated from CMS4

Compatibility matrix

OPF	Q2 : 25.26.STD0
DWH (25 Q2 STD1)
SSP (25.26) Q2

List of new issues

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

Issue Type	Key	Component/s	Summary

List of known issues

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

Issue Type	Key	Component/s	Summary

List of resolved issues

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

Issue Type	Key	Component/s	Summary

Deprecated APIs

Component	API	Description	Deprecated in release	Supported until