Release notes for OpenTV Platform

Release summary

This release…

User Recordings – series handling of 72 hour delay RECORDING state

This feature is to support the deletion of episodes from a series recording with status = RECORDING (and status = RECORDED & status = FAILED) with a broadcast.enddate in the past. Note that in case of Velocix, we assetize recordings after 72h, i.e., the status will change from RECORDING to RECORDED only after this period of time.

User Recordings performance improvements for jobs queue

This feature is to address the below performance issues:

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.

Enhancements are provided for two scenarios: while processing EPG queue and while processing jobs queue.

In-home detection

This feature is to check if a mobile app is within a user's home. It works by performing a network lockup for the already-authenticated STB that is located within the home network of the user. Content is filtered for the open device depending on whether it is in the home or not. Network changes trigger an update of the open device’s in-home status.

See (25.12_Q1) Enabling in-home detection for open devices.

A/B test targeting OPF data points (OPF segments)

This feature allows the operator to use values within the OPF platform as targets for A/B testing, such as:

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 can also define segments.

See Segment targeting.

Blackout rules per event (previous implementation allowed one ruleset only)

This feature is to add the ability for an operator to specify multiple blackout rules and assign them to specific events. The previous implementation allowed a set of rules to be specified at the platform level.

See Blackout Management.

A/B testing XRM segmentation integration

This feature allows user segments to be retrieved from XRM.

Customers can bulk load segments from CRM systems as follows:

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

Because you watched – Rails

This feature allow you to:

Add multiple rails based on your viewing history (like Netflix)
Naming the rail based on the item it's based on

See Add multiple rails based on viewing history.

Rails blueprint/KvP enhancements

This feature covers:

General layout and structuring/navigation to make a cleaner view
Improvement of “configuration” pages
Optimising space in layout page with new “section layout”
Removing “edit properties” and having this collapsed into a single page with content/section details
Blueprint typing - Rail, KVP collection, or Rail section
Standardised key definition
Ability to group blueprints (arbitrary grouping, e.g. branding, cache control, etc.)
Ability to apply multiple blueprints to a template/Rail
Ability to select different values other than image/string
Ability to upload metadata along with images
Ability to filter images and videos by keyword(s)

OpCon A/B testing get data

The feature is to display A/B testing results from DWH in OpCon.

See Segment targeting.

Non-UI locale support (image ingest)

This feature is to prioritise image selection for locales that are not defined in BCM. The current IMDS/images solution in OPF supports locales, as per config defined in BCM.

But while ingesting images via MAS into IMDS that specify a locale that has not been defined in BCM, it is not possible to then influence the selection process using these locales.

For Prime Video (and other third party catalogues), there is very little consistency in the availability of images for a specific locale. While it is true that popular or Prime Video original content has decent metadata/images, the rest of the content is very hit and miss.

This feature allows IMDS to have a configuration (separate from BCM) where the locales can be specified.

See Working with images.

Parental ratings – series/Season finalisation

This feature completes the non-critical impacts for adding parental ratings to series and seasons.

Rails Builder – content visibility indicators – continuation feature

Currently we can add content to a Rail in the Rails Builder that is 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 adds badges in Rails Builder 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.

Continuation for OpCon push messaging UI

This feature is to support a new OpCon 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:

A dedicated UI section in OpCon providing a publication centre for general messaging
This new centre references DMM 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

Messages sent are traceable via DWH reporting/analytics.
Messages sent can be of a number of forms, including:
1. Plain text
2. HTML with images
3. HTML with deep links to application content
The ability broadly to edit a message sent, via some recall/republish mechanism.

See (25.12_Q1) Message Management.

Compatibility matrix

OPF	Q1 : 25.12.STD0
DWH (25 Q1)
SSP (24.48) Q4

List of new issues

TBD

List of known issues

TBD

List of resolved issues

TBD

Deprecated APIs

Component	API	Description	Deprecated in release	Supported until