OpenTV ENTera & OpenTV Platform Documentation
26.26_Q2 25.52_Q4 25.26_Q2 25.12_Q1 24.50_Q4 24.38_Q3 24.26_Q2 23.50_Q4 23.24_Q2 23.12_Q1 22.50_Q4 22.38_Q3 22.24_Q2
26.26_Q2 25.52_Q4 25.26_Q2 25.12_Q1 24.50_Q4 24.38_Q3 24.26_Q2 23.50_Q4 23.24_Q2 23.12_Q1 22.50_Q4 22.38_Q3 22.24_Q2

Message format – EPG update

Overview

OpenTV Platform can be configured to send notifications to clients to let them know that there have been changes to EPG metadata.

These changes include:

  • Changes to BTV (live) metadata – for example, a change to a description or episode name

  • Rescheduling of live events – for example, the extension of a football match that has gone into extra time, and the rearrangement of subsequent programmes

EPG change notifications do not include the details of the changes. They are just notifications.

The client must call Metadata Server (MDS) or Content Discovery Facade to get the updated event details.

Message format

Example payload of an EPG update message received by a client:

JSON
{
  "data":
  {
    "reference":"GLOBAL_sky_one",
    "referenceType":"EPG_UPDATE",
    "action":"REFRESH",
    "name":"Title change",
    "priority":"HIGH",
    "start": 1454284800.0,
    "end": 2147483647.0
  }
}

The message is delivered as stringified JSON, and is shown here as regular JSON for readability.

When delivered to the client, the above example JSON will be stringified as follows:

JSON
"{\"data\":{\"reference\":\"GLOBAL_sky_one\",\"referenceType\":\"EPG_UPDATE\",\"action\":\"REFRESH\",\"name\":\"Title change\",\"priority\":\"HIGH\",\"start\":1454284800,\"end\":2147483647}}"

See also

Metadata change alerts