dvb-i webinar series€¦ · • same challenges facing operators today reconcile requests from...

DVB-I Webinar Series

Part 2 of 31 April 2020

Introduction

Paul Higgs – TM-I Chair - Huawei

• DVB-C, DVB-T, DVB-S Broadcast television services

• HbbTV Add interactive elements and

ondemand content to existing broadcast services

• DVB-IPTV Television services delivered over

managed/private IP networks• DVB-I

Broadcast television services delivered over the Internet

Road to DVB-I• A177 – DVB-I Service Discovery and

Programme Information The “internet channel scan” and EPG

• A168 – DVB-DASH with Low Latency Media format for linear broadband

television services (On Demand also)• A176 – Multicast ABR (DVB-mABR)

Efficient delivery of DVB DASH over IP networks

• A178 – Targeted Advertising (DVB-TA) Personalizing advertisements for

television services

The ecosystem

DVB-I Concepts

Program Info

Service List

(LL) CDN

Service Service Service

Service List

Discovery

DVB-IClientService

DVB-I Service Info

Program Info

Service List

(LL) CDN

Service Service Service

Service List

Discovery

DVB-IClient

Service RelatedInformation

Service

Part 2: Service Lists & Programme Info

Nicholas Frame - TP Vision

• Aggregation of services into service lists

Trust in services and service lists

• Announcement of service lists Different service list discovery methods

• Service list aspects and data model Hybrid service lists, regionalized LCNs, availability window based service switches

• Content metadata endpoints How to use them to create a TV guide experience

Topics

Aggregation of services into service lists

• XML document used by a DVB-I client to configure Access to different services from one or more service providers Using one or more delivery methods (broadcast, broadband)

• Determines ease of access to services Across different types of client device (e.g. hybrid TV, mobile IP-only) Services can be ordered (LCN) and targeted based on availability (location

and periodicity) and subscription Complemented by additional metadata (e.g. logos, event information,

HbbTV apps)

• Service List Provider in control of service aggregation

Service List

• Potential Service List Providers Broadcaster Network Operator Regulator Independent third party (separate from content creation & distribution) Private groups or individuals

• Target different viewers according to region, language, market segment, platform … Horizontal ecosystem (e.g. DTT Free-To-Air TV) Vertical ecosystem (e.g. DTH PayTV) Smaller local ecosystem (e.g. local community group)

Who is the Service List Provider?

• Same challenges facing operators today Reconcile requests from different service providers, regulatory

requirements, user needs, business interests Additional separation between service list delivery and content

delivery

• Guarantor of service authenticity Ensure users get the expected services Ensure services are from the genuine service providers Work with service providers to ensure delivery parameters are accurate

Service List Provider Role

• Service List Provider must be trusted by service providers and client devices

• Means to establish trust include technical tools operational procedures regulation

Establishing Trust

Service (Content) Provider

DVB-I Service List Provider

Viewer

DVB-I Client Device

Service (Content) ProviderService (Content) Provider

trusts

• Ensure Service Lists and other metadata reach the client without tampering from the expected provider privately

• DVB-I builds upon Internet-friendly standards Easier to support as implementations of technical building blocks exist Benefit from existing experience and best practices

• RESTful APIs using HTTPS for all metadata queries/responses• Client support for TLS v1.3 will be required• DNSSEC and DNS over TLS or DNS over HTTPS recommended

Technical tools for trust

Announcement of service lists

3 methods to discover and/or retrieve DVB-I Service Lists

1. Built-in / out-of-band provisioning of a Service List URL – From a known (trusted) Service List Provider – Available at device installation or dynamically on-the-fly

2. Broadcast signalling of Service List URL– URI linkage descriptor in the 1st loop of NIT or the 1st loop of BAT

3. Service List Registry Query for available Service Lists– Parameters include country, language, provider name and whether the

provider is a regulator or not

Discovering Service Lists

• Clients may be privately or pre-provisioned with known Service List URLs or Service List Registry URLs

• These could be defined and provided by National/regional regulator Network operator Broadcaster Manufacturer Other entity running a Central Service List Registry

Service List pre-provisioning

• URI linkage descriptor in 1st loop of NIT or 1st loop of BAT URI linkage descriptor private_data_byte loop contains DVB-I_info()

element with end_point_type– 0x01 = signalled URI links to a DVB-I Service List– 0x02 = signalled URI contains a query to a Service List Registry

Broadcast Service List URL signalling

Service List Registry

Information Model

Service List

Service

Service Instance

Ordered collection of services

Editorial representation of a television service

Network specific delivery parameters

Queryable network function to discover Service Lists

• Clients query a known Service List Registry for available Service Lists https://registry/query?<param>&<param>...

• Queries can be narrowed using one or more parameters (AND) with one or more values (OR) TargetCountry – service lists intended for specific countries Language – service lists containing specific languages ProviderName – service lists provided by a specific organization regulatorListFlag – identified “official” lists of services Genre – service lists containing specific genre*

Service List Registry queries

* TV Anytime ContentCS, FormatCS or DVB-I ContentSubject

https://registry/query? TargetCountry=DEU&Language=EN

Service List query example

</ServiceListRegistryEntity><ProviderOffering>

</Provider><ServiceListOffering>

<ServiceListName xml:lang="de">TV aus Deutschland</ServiceListName><ServiceListName xml:lang="en">TV from Germany</ServiceListName><ServiceListURI contentType="application/vnd.dvb.dvbisl+xml">

<dvbisd:URI>https://dvbi.TVfromTheWorld.com/TVservices_Germany.xml</dvbisd:URI></ServiceListURI><Language>de</Language><Language>en</Language><TargetCountry>DEU</TargetCountry>

</ServiceListOffering>…

</ProviderOffering>…

</ServiceListEntryPoints>

• Service List Registries will have to trust the Service List Providers they reference

• Clients will have to trust Service List Registries

Establishing Trust

Service (Content) Provider

DVB-I Service List Provider

Viewer

Service (Content) ProviderService (Content) Provider

trusts

DVB-I Service List Registry

DVB-I Client Device

trusts

Service list aspects and data model

Describes services, how to receive them and associated metadata

• Identifiers (IDs, names, LCNs)

• Delivery Parameters & Media Format (DASH, broadcast)

• Availability (geolocation-based, time-based)

• Associated Media (logos, out-of-service banners, HbbTV applications)

• Content Guide Source(s) (source for entire list or individual services)

Service List Content

Information Model

Service List

Service

Service Instance

Practical examples to look into the metadata:

1. Hybrid Service Lists

2. Regionalized LCNs

3. Availability window based service switches

Scenarios

Service List example

Service List

Service List exampleDVB-I Service ListVersion @version="1" Mandatory

Name <Name>Italian Example Services</Name> Mandatory

Provider Name <ProviderName>RAI</ProviderName> Mandatory

<tva:MediaUri contentType="image/png">https://dvbi.rai.tv/static/list-logo.png

</tva:MediaUri></tva:MediaLocator>

</RelatedMaterial>

Optional

Region(s)

<RegionName>Italy</RegionName></Region>

</RegionList><TargetRegion>ID-IT</TargetRegion>

Optional

LCN Table(s)

</LCNTable></LCNTableList>

Optional

Service(s) <Service version="1"> ... </Service> Optional

DVB-I Service ListVersion @version="1" Mandatory

</RelatedMaterial>

Optional

Region(s)

Optional

LCN Table(s)

Optional

Facilitate client detection of Service List changes

</RelatedMaterial>

Optional

Region(s)

Optional

LCN Table(s)

Optional

Names of the service offering and providerclients can show in UI

</RelatedMaterial>

Optional

Region(s)

Optional

LCN Table(s)

Optional

Link to a logo that can enrich the client UI

</RelatedMaterial>

Optional

Region(s)

Optional

LCN Table(s)

Optional

Regions the Service List and/or specific Services are targeted at

</RelatedMaterial>

Optional

Region(s)

Optional

LCN Table(s)

Optional

An LCN Table defines a channel list mapping Services to LCNs

</RelatedMaterial>

Optional

Region(s)

Optional

LCN Table(s)

Optional

Service definitionsService definitions

Service example

Service(s)

Service

Service exampleDVB-I Service

Unique Service ID <UniqueIdentifier>tag:rai.it,2019:rai-3</UniqueIdentifier> Mandatory

Service Name <ServiceName>Rai 3</ServiceName> Mandatory

<tva:MediaUri contentType="image/png">https://dvbi.rai.tv/static/rai3/channel-logo.png

</RelatedMaterial>

Optional

Type <ServiceType href="urn:dvb:metadata:cs:ServiceTypeCS:2019:linear"/> Optional

Genre <ServiceGenre href="urn:dvb:metadata:cs:ContentSubject:2019:7.0"/> Optional

Service Instances<ServiceInstance priority="1">...</ServiceInstance>

Optional

</RelatedMaterial>

Optional

Unique ID enables mappingto LCNs and Content Guide metadata

• Required to use a registered URI scheme that allows independent allocation and ensures global uniqueness• Recommended to follow IETF RFC4151

tagURI = "tag:" taggingEntity ":" specific [ "#" fragment ]

Where:taggingEntity = authorityName "," dateauthorityName = DNSname / emailAddressdate = year ["-" month ["-" day]]year = 4DIGITmonth = 2DIGITday = 2DIGITDNSname = DNScomp *( "." DNScomp ) ; see RFC 1035DNScomp = alphaNum [*(alphaNum /"-") alphaNum]emailAddress = 1*(alphaNum /"-"/"."/"_") "@" DNSnamealphaNum = DIGIT / ALPHAspecific = *( pchar / "/" / "?" ) ; pchar from RFC 3986fragment = *( pchar / "/" / "?" ) ; same as RFC 3986

Example: tag:rai.it,2019:rai-3

Unique Service ID URI scheme

</RelatedMaterial>

Optional

Names of the Service and its provider

</RelatedMaterial>

Optional

OptionalLink to a logo that can enrich the client UI

</RelatedMaterial>

Optional

OptionalService type (linear, on demand, data, other)

</RelatedMaterial>

Optional

Genre of programming on this servicee.g. Arts/Culture (without music, general)

</RelatedMaterial>

Optional

Service Instance definitions for each delivery method

Service example – Linked applicationsDVB-I Service

Linked Application

<tva:MediaUri contentType="application/vnd.dvb.ait+xml">https://dvbi.rai.tv/hbbtv/application.ait

</RelatedMaterial>

Optional

Service example – Linked applicationsDVB-I Service

Linked Application

<tva:MediaUri contentType="application/vnd.dvb.ait+xml">https://dvbi.rai.tv/hbbtv/application.ait

</RelatedMaterial>

Optional

3 different types of linear IP service linked applications:1. Application with media in parallel (…:LinkedApplicationCS:2019:1.1)2. Application controlling media presentation

(…:LinkedApplicationCS:2019:1.2)3. Application for outside availability period (…:LinkedApplicationCS:2019:2)

LCN Table example

LCN Table(s)

LCN Table

LCN Table example

Unique Service ID

LCN Table example

Unique Service ID

Logical Channel Number

LCN Table exampleLCN Table

Optional

LCNChannel Number @channelNumber="3" Mandatory

Unique Service ID @serviceRef="tag:rai.it,2019:rai-3" Mandatory

Selectable @selectable="true" Optional

Visible @visible="true" Optional

Optional

Maps channel numbers (LCNs) to services using Unique Service IDs

Optional

Offers control over selectability and visibility of channels

Region and Subscription targetingLCN Table

Region <TargetRegion> ... </TargetRegion> Optional

Subscription <SubscriptionPackage> ... </SubscriptionPackage> Optional

LCN <LCN channelNumber="3" serviceRef="tag:rai.it,2019:rai-3" selectable="true" visible="true"/> Optional

• LCN Tables can be targeted at regions and/or subscription packages

• Region and subscription targeting can also be done at the Service level

LCN TableRegion <TargetRegion> ... </TargetRegion> Optional

Region and Subscription targetingTarget an LCN Table at a

specific region

LCN TableRegion <TargetRegion> ... </TargetRegion> Optional

Region and Subscription targeting

Target an LCN Table at a subscription package

Service Instance example

Service Instance(s)

DVB-S Service Instance exampleDVB-I Service Instance

Priority @priority="2" Optional

Source Type <SourceType>urn:dvb:metadata:source:dvb-s</SourceType> Optional

Delivery Parameters

<DVBSDeliveryParameters><DVBTriplet origNetId="318" tsId="5200" serviceId="3403"/><OrbitalPosition>-5</OrbitalPosition><Frequency>11179</Frequency><Polarization>vertical</Polarization>

</DVBSDeliveryParameters>

Optional

Content Attributes

<ContentAttributes><VideoConformancePoint

href="urn:dvb:metadata:cs:VideoConformancePointsCS:2017:1.1.7" /><AudioAttributes>

<tva:Coding href="urn:dvb:metadata:cs:AudioCodecCS:2007:3.1" /></AudioAttributes>

</ContentAttributes>

Optional

Delivery Parameters

Optional

Content Attributes

Optional

Priority between Service Instances, lower value = higher priority

Delivery Parameters

Optional

Content Attributes

OptionalDelivery type and associated parameters

Delivery Parameters

Optional

Content Attributes

Optional

Attributes characterising content (e.g. encoding, language) clients can use to determine support or priority

DVB-I Service InstancePriority @priority="1" Optional

Source Type <SourceType>urn:dvb:metadata:source:dvb-dash</SourceType> Optional

Delivery Parameters

<DASHDeliveryParameters><UriBasedLocation contentType="application/dash+xml"><URI>https://www.raiplay.it/dvbi/mpd/rai3.mpd</URI>

</UriBasedLocation></DASHDeliveryParameters>

Optional

Content Attributes

<ContentAttributes><VideoConformancePoint

Optional

Related Material

<tva:MediaUri contentType="image/png">https://dvbi.rai.tv/static/rai3/out-of-service.png

</RelatedMaterial>

Optional

DASH Service Instance example

Delivery Parameters

Optional

Content Attributes

Optional

Related Material

</RelatedMaterial>

Optional

Priority between Service Instances, lower value = higher priority

Delivery Parameters

Optional

Content Attributes

Optional

Related Material

</RelatedMaterial>

Optional

Delivery type and associated parameters

Delivery Parameters

Optional

Content Attributes

Optional

Related Material

</RelatedMaterial>

Optional

Attributes characterising content (e.g. encoding, language) clients can use to determine support or priority

Delivery Parameters

Optional

Content Attributes

Optional

Related Material

</RelatedMaterial>

Optional

Link to an out of service banner to enrich the client UI in case service not available

<?xml version="1.0" encoding="UTF-8"?><ServiceList version="1" xmlns="urn:dvb:metadata:servicediscovery:2019" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:schemaLocation="urn:dvb:metadata:servicediscovery:2019 ../dvbi_v1.0.xsd">

<Name>RAI 3 example</Name><ProviderName>RAI</ProviderName><LCNTableList>

</LCNTable></LCNTableList><Service version="1">

<SourceType>urn:dvb:metadata:source:dvb-s</SourceType><DVBSDeliveryParameters>

<DVBTriplet origNetId="318" tsId="5200" serviceId="3403"/><OrbitalPosition>-5</OrbitalPosition><Frequency>11179</Frequency><Polarization>vertical</Polarization>

</DVBSDeliveryParameters></ServiceInstance><ServiceInstance priority="1">

...</ServiceInstance><ServiceName>Rai 3</ServiceName><ProviderName>RAI</ProviderName>

</Service></ServiceList>

Service List metadata example

• A single Service List can target different client device types IP-only (mobile) devices Hybrid TV devices

• Hybrid clients can receive DVB DASH services over IP, as well as DVB terrestrial, satellite or cable services

• A single Service List can define a channel list using a combination of different delivery methods e.g. IP and terrestrial Services can have multiple Service Instances (i.e. multiple delivery methods) Each Service Instance defines a delivery method Hybrid clients match Service Instance delivery parameters and Service metadata

with the services and DVB SI detected on terrestrial, satellite or cable interfaces

Hybrid Service Lists

Hybrid Service List example

<ServiceInstance priority="2"><DVBSDeliveryParameters><DVBTriplet origNetId="318" tsId="5200" serviceId="3403"/><OrbitalPosition>-5</OrbitalPosition><Frequency>11179</Frequency><Polarization>vertical</Polarization>

</DVBSDeliveryParameters></ServiceInstance>

<ServiceInstance priority="1"><DASHDeliveryParameters><UriBasedLocation contentType="application/dash+xml"><URI>https://www.raiplay.it/dvbi/mpd/rai3.mpd</URI>

</ServiceInstance>

</ServiceInstance>

Client matches DVB-I metadata with RF installation Target Country ItalyDelivery System DVB-SDVB Triplet ONID=318 TSID=5200 SID=3403Orbital Position -5Frequency & Polarization 11179VService Name Rai 3

</ServiceInstance>

priority="1"

priority="2"

• A single Service List can target viewers at different geographic levels Different countries Regions

• Regional targeting possible at different metadata levels Entire Service List Specific Service(s) Specific LCN Table(s)

• Service Lists can include Definitions of regions targeted LCN Table for each targeted region

Regionalized LCNs

Service List example with RegionsDVB-I Service ListVersion @version="1" Mandatory

Region(s)

<Region regionID="ID-IT-Piemonte"><RegionName>Piemonte</RegionName><PostcodeRange from="15010" to="15122"/>...<PostcodeRange from="13010" to="13100"/>

</Region><Region regionID="ID-IT-Lombardia"><RegionName>Lombardia</RegionName><PostcodeRange from="24010" to="24129"/>...<PostcodeRange from="23010" to="23100"/>

</Region></Region>

</RegionList>

Optional

LCN Table(s)<LCNTableList>

...</LCNTableList>

Optional

Region(s)

<Region regionID="ID-IT-Piemonte"><RegionName>Piemonte</RegionName><PostcodeRange from="15010" to="15122"/>...<PostcodeRange from="13010" to="13100"/>

</Region><Region regionID="ID-IT-Lombardia"><RegionName>Lombardia</RegionName><PostcodeRange from="24010" to="24129"/>...<PostcodeRange from="23010" to="23100"/>

</Region></Region>

</RegionList>

Optional

LCN Table(s)<LCNTableList>

...</LCNTableList>

Optional

Service List example with RegionsDefinition of the regions to target (IDs and names),

with optionally postcodes and/or coordinatesDefinition of the regions to target (IDs and names),

with optionally postcodes and/or coordinates

LCN Tables on next 2 slides

Regionalized LCN Table example 1/2LCN Table

Region <TargetRegion>ID-IT-Piemonte</TargetRegion> Optional

Optional

Unique Service ID @serviceRef="tag:rai.it,2019:rai-3-piemonte" Mandatory

Viewers in Piemonte get a different variant

Regional variants of the same service are mapped to the same LCN, depending on the client device’s region

Regionalized LCN Table example 2/2LCN Table

Region <TargetRegion>ID-IT-Lombardia</TargetRegion> Optional

Optional

Unique Service ID @serviceRef="tag:rai.it,2019:rai-3-lombardia" Mandatory

… than viewers in Lombardia

Regional variants of the same service are mapped to the same LCN, depending on the client device’s region

• Availability windows can be defined for Service Instances Service availability is linked to delivery methods

• Service Instances can include one or more Availability periods (from start date/time, to end date/time) Availability intervals (on certain days of the week, at a certain time of

day, with a particular recurrence rate)

Service availability windows

Display Name <DisplayName>Rai 3 TGR Piemonte</DisplayName> Optional

Delivery Parameters

<DASHDeliveryParameters><UriBasedLocation contentType="application/dash+xml"><URI>https://www.raiplay.it/dvbi/mpd/rai3_tgr_piemonte.mpd</URI>

Optional

Availability

</Availability>

Optional

Related Material

</RelatedMaterial>

Optional

Delivery Parameters

Optional

Availability

</Availability>

Optional

Related Material

</RelatedMaterial>

Optional

DASH Service Instance exampleHighest priority Service Instance

(the DVB-S instance has @priority=2)

Delivery Parameters

Optional

Availability

</Availability>

Optional

Related Material

</RelatedMaterial>

Optional

Display Name overrides the Service Name when the client plays this Service Instance

Delivery Parameters

Optional

Availability

</Availability>

Optional

Related Material

</RelatedMaterial>

Optional

Available every day from 17:30 to 18:00 UTC

Delivery Parameters

Optional

Availability

</Availability>

Optional

Related Material

</RelatedMaterial>

Optional

Link to an out of service banner

<Service version="1"><UniqueIdentifier>tag:rai.it,2019:rai-3-piemonte</UniqueIdentifier><ServiceInstance priority="2">

<SourceType>urn:dvb:metadata:source:dvb-s</SourceType><DVBSDeliveryParameters>

<DVBTriplet origNetId="318" tsId="5200" serviceId="3403"/><OrbitalPosition>-5</OrbitalPosition><Frequency>11179</Frequency><Polarization>vertical</Polarization>

</DVBSDeliveryParameters></ServiceInstance><ServiceInstance priority="1">

<DisplayName>Rai 3 TGR Piemonte</DisplayName><Availability>

</Period></Availability><SourceType>urn:dvb:metadata:source:dvb-dash</SourceType><DASHDeliveryParameters>

<UriBasedLocation contentType="application/dash+xml"><URI>https://www.raiplay.it/dvbi/mpd/rai3_tgr_piemonte.mpd</URI></UriBasedLocation>

</DASHDeliveryParameters></ServiceInstance><ServiceName>Rai 3</ServiceName><ProviderName>RAI</ProviderName>

</Service>

Service metadata overview

Rai 3DVB-S Instance

Switching during availability window

Rai 3 TGR PiemonteDASH Instance

Rai 3DVB-S Instance

17:30 UTC 18:00 UTC

DVB-I Client switches to the higher priority DASH Service Instance when it becomes available

SWITCH SWITCH

Content metadata endpoints

Service List Registry

Information Model

Service List

Service

Service Instance

Queryable network function to discover Service Lists

Event Information Program information for channel change banner and electronic program guide

• API offering basic and enhanced schedule information• Linear schedule for next 28 days• Catch-up for past 28 days• Specific queries

Now/Next More episodes in a series Content grouping into categories, series and brands allowing for “box set”

user offerings• Deep links to IP streams and applications to play content• Channel and content images

Content Guide Metadata

Content Guide Source exampleContent Guide Source

CGS ID @CGSID="cgs-dvbi-01" Mandatory

Name <Name>A-Z Content Guide</Name> Optional

Provider Name <ProviderName>A-Z Metadata</ProviderName> Mandatory

<tva:MediaUri contentType="image/png">https://cgs.az.metadata/static/cgs/cgs-logo.png

</RelatedMaterial>

Optional

ScheduleInfo Endpoint

<ScheduleInfoEndpoint contentType="application/xml"><URI>https://cgs.az.metadata/schedule</URI>

</ScheduleInfoEndpoint>Mandatory

ProgramInfoEndpoint

<ProgramInfoEndpoint contentType="application/xml"><URI>https://cgs.az.metadata/program</URI>

</ProgramInfoEndpoint>Optional

GroupInfoEndpoint

<GroupInfoEndpoint contentType="application/xml"><URI>https://cgs.az.metadata/group</URI>

</GroupInfoEndpoint>Optional

MoreEpisodesEndpoint

<MoreEpisodesEndpoint contentType="application/xml"><URI>https://cgs.az.metadata/moreeps</URI>

</MoreEpisodesEndpoint>Optional

</RelatedMaterial>

Optional

ProgramInfoEndpoint

GroupInfoEndpoint

Unique ID that can be used to reference the same ContentGuideSource in multiple Service definitions

Content Guide SourceCGS ID @CGSID="cgs-dvbi-01" Mandatory

</RelatedMaterial>

Optional

ProgramInfoEndpoint

GroupInfoEndpoint

Content Guide Source example

Names of the Content Guide and its provider clients can show in UI

Content Guide SourceCGS ID @CGSID="cgs-dvbi-01" Mandatory

</RelatedMaterial>

Optional

ProgramInfoEndpoint

GroupInfoEndpoint

Content Guide Source example

Link to a logo that can enrich the client UI

</RelatedMaterial>

Optional

ProgramInfoEndpoint

GroupInfoEndpoint

Combined schedule, linear and on-demand programme information for a single serviceCombined schedule, linear and on-demand programme information for a single service

</RelatedMaterial>

Optional

ProgramInfoEndpoint

GroupInfoEndpoint

Detailed information on a single programmeDetailed information on a single programme

</RelatedMaterial>

Optional

ProgramInfoEndpoint

GroupInfoEndpoint

On-demand and scheduled content curated into box sets, discovered as curated categories

On-demand and scheduled content curated into box sets, discovered as categories

</RelatedMaterial>

Optional

ProgramInfoEndpoint

GroupInfoEndpoint

More episodes of a single programme More episodes of a single programme

Service List exampleServiceListVersion @version="1" Mandatory

Name <Name>RAI 3 example</Name> Mandatory

Content Guide Source(s)

Optional

Service(s)<Service version="1">...</Service>

Optional

Defines source(s) of Content Guide metadata for the entire Service List or for specific Services

Service exampleService

Unique Service ID <UniqueIdentifier>tag:rai.it,2019:rai-3-piemonte</UniqueIdentifier> Mandatory

Content Guide Source

Optional

Content Guide Service Reference

<ContentGuideServiceRef>tag:rai.it,2019:rai-3</ContentGuideServiceRef> Optional

OptionalDefines a source of Content Guide metadata for the

Service or references a source of Content Guide metadata (@CGSID) defined in the Content Guide Source List

Service exampleService

Unique Service ID <UniqueIdentifier>tag:rai.it,2019:rai-3-piemonte</UniqueIdentifier> Mandatory

Content Guide Source

Optional

Content Guide Service Reference

<ContentGuideServiceRef>tag:rai.it,2019:rai-3</ContentGuideServiceRef> Optional

Optional

Except when a Content Guide Service Reference is defined – which allows the same guide data to be

referenced by multiple services (e.g. regional variants)

Unique ID enables mappingto Content Guide metadata...

Request format:<ScheduleInfoEndpoint>?start=<start_unixtime>&end=<end_unixtime>&sid=<service_id>&image_variant=<variant>

Specific Now & Next request for the current and next future event:<ScheduleInfoEndpoint>?sid=<service_id>&now_next=true

Examples:• Schedule for Rai 3 on 27 March 2020, from 18:00 to 22:00

https://cgs.az.metadata/schedule?sid=tag%3Arai.it%2C2019%3Arai-3&start=1585328400&end= 1585342800

• Now & Next schedule for Rai 3https://cgs.az.metadata/schedule?sid=tag%3Arai.it%2C2019%3Arai-3&now_next=true

Schedule Information request

Request format:<ScheduleInfoEndpoint>?start=<start_unixtime>&end=<end_unixtime>&sid=<service_id>&image_variant=<variant>

Specific Now & Next request for the current and next future event:<ScheduleInfoEndpoint>?sid=<service_id>&now_next=true

Examples:• Schedule for Rai 3 on 27 March 2020, from 18:00 to 22:00

https://cgs.az.metadata/schedule?sid=tag%3Arai.it%2C2019%3Arai-3&start=1585328400&end= 1585342800

• Now & Next schedule for Rai 3https://cgs.az.metadata/schedule?sid=tag%3Arai.it%2C2019%3Arai-3&now_next=true

Schedule Information request

Service to provide schedule programme info for

Clients may request a particular variant for the image assets provided, to better suite

different UI integrations (e.g. 16:9 colour light)

Timeframe of the requested schedule

Schedule Information response data structure

<?xml version="1.0" encoding="UTF-8"?><TVAMain xmlns="urn:tva:metadata:2019" xmlns:mpeg7="urn:tva:mpeg7:2008"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xml:lang="en"xsi:schemaLocation="urn:tva:metadata:2019 ../tva_metadata_3-1.xsd">

<ProgramInformation programId="crid://channel7.co.uk/b01myjsy">...

</ProgramInformation><ProgramInformation programId="crid://channel7.co.uk/b03bhc3n">

...</ProgramInformation>

</ProgramInformationTable><ProgramLocationTable xml:lang="en">

...</ScheduleEvent><ScheduleEvent>

...</ScheduleEvent>

</Schedule><OnDemandProgram>

...</OnDemandProgram>

</ProgramLocationTable></ProgramDescription>

</TVAMain>

ScheduleInfo response example

<ProgramInformation programId="crid://channel7.co.uk/b01myjsy">...

...</ProgramInformation>

</ProgramInformationTable><ProgramLocationTable xml:lang="en">

...</ScheduleEvent><ScheduleEvent>

...</ScheduleEvent>

</Schedule><OnDemandProgram>

...</OnDemandProgram>

</ProgramLocationTable></ProgramDescription>

</TVAMain>

The latest national and international news stories from the BBC News team, followed by weather</Synopsis><Genre href="urn:dvb:metadata:cs:ContentSubject:2019:2.0" type="main"/><RelatedMaterial>

https://img-ctv.mdata.co.uk/channel7/broadcast_news.png

</MediaUri></MediaLocator>

</RelatedMaterial></BasicDescription>

</ProgramInformation></ProgramInformationTable>

ProgramInformationTable

Promotional Still Image

News/Current affairs (general)

Identifier (Content Reference Identifier (CRID)) of the programme

</ProgramInformation></ProgramInformationTable><ProgramLocationTable xml:lang="en">

</ScheduleEvent><ScheduleEvent>

</ScheduleEvent></Schedule><OnDemandProgram>

</OnDemandProgram></ProgramLocationTable>

</ProgramDescription></TVAMain>

</AudioAttributes><AudioAttributes><MixType href="urn:mpeg:mpeg7:cs:AudioPresentationCS:2001:3"/><AudioLanguage purpose="urn:tva:metadata:cs:AudioPurposeCS:2007:6">eng</AudioLanguage>

</AudioAttributes><VideoAttributes><HorizontalSize>576</HorizontalSize><VerticalSize>512</VerticalSize><AspectRatio>16:9</AspectRatio>

</VideoAttributes></AVAttributes>

</InstanceDescription><PublishedStartTime>2019-09-25T12:00:00Z</PublishedStartTime><PublishedDuration>PT30M</PublishedDuration>

</ScheduleEvent></Schedule><OnDemandProgram> ... </OnDemandProgram>

</ProgramLocationTable>

ProgramLocationTable - Schedule

</ProgramInformation></ProgramInformationTable><ProgramLocationTable xml:lang="en">

</ScheduleEvent><ScheduleEvent>

</ScheduleEvent></Schedule><OnDemandProgram>

</ProgramDescription></TVAMain>

<ProgramLocationTable xml:lang="en"><Schedule serviceIDRef="tag:channel7.co.uk,2019:sid3039" start="2019-09-25T11:15:00Z" end="2019-09-25T12:30:00.000Z">…

</Schedule><OnDemandProgram><Program crid="crid://channel7.co.uk/b01myjsy"/><ProgramURL contentType="application/vnd.dvb.ait+xml">https://channel7.co.uk/ait.aitx?pid=b01myjsy</ProgramURL><AuxiliaryURL contentType="application/vnd.dvb.ait+xml">https://channel7.co.uk/ait.aitx?template</AuxiliaryURL><InstanceDescription><Genre href="urn:fvc:metadata:cs:MediaAvailabilityCS:2014-07:media_available" type="other"/><Genre href="urn:fvc:metadata:cs:FEPGAvailabilityCS:2014-10:fepg_unavailable" type="other"/><CaptionLanguage closed="true">eng</CaptionLanguage><AVAttributes><VideoAttributes><HorizontalSize>576</HorizontalSize><VerticalSize>512</VerticalSize><AspectRatio>16:9</AspectRatio>

</InstanceDescription><PublishedDuration>PT1H</PublishedDuration><StartOfAvailability>2019-09-25T12:03:09Z</StartOfAvailability><EndOfAvailability>2019-10-02T09:59:00Z</EndOfAvailability><DeliveryMode>streaming</DeliveryMode><Free value="true" />

ProgramLocationTable – OnDemandProgram

Request format:<ProgramInfoEndpoint>?pid=<program_id>&image_variant=<variant>

Detailed Programme Info request

Request format:<ProgramInfoEndpoint>?pid=<program_id>&image_variant=<variant>

CRID from @programId attribute of a ProgramInformation element or @cridattribute from a ScheduleEvent.Program or OnDemandProgram.Program

Example:• Detailed programme info for the programme with the CRID

crid://channel7.co.uk/b03bhc3nhttps://cgs.az.metadata/program?pid=crid%3A%2F%2Fchannel7.co.uk%2Fb03bhc3n

Detailed Programme Info requestIdentifier (Content Reference Identifier (CRID)) of the programme to provide detailed info for

Request format:<MoreEpisodesEndpoint>?pid=<program_id>&type=ondemand&regionID[]=<region_id_1>&regionID[]=<region_id_2>…&image_variant=<image_variant>

Example:• More episodes of the programme with the CRID

crid://channel7.co.uk/b03bhc3n, available on demand in the region with the ID “uk-england-yorkslincs”

https://cgs.az.metadata/moreeps?pid=crid%3A%2F%2Fchannel7.co.uk%2Fb03bhc3n&type=ondemand&regionID[]=uk-england-yorkslincs

More Episodes request

Request format:<MoreEpisodesEndpoint>?pid=<program_id>&type=ondemand&regionID[]=<region_id_1>&regionID[]=<region_id_2>…&image_variant=<image_variant>

Example:• More episodes of the programme with the CRID

crid://channel7.co.uk/b03bhc3n, available on demand in the region with the ID “uk-england-yorkslincs”

https://cgs.az.metadata/moreeps?pid=crid%3A%2F%2Fchannel7.co.uk%2Fb03bhc3n&type=ondemand&regionID[]=uk-england-yorkslincs

More Episodes request

The region ID of the client’s current region, defined in the RegionList

Identifier (Content Reference Identifier (CRID)) of the programme to provide detailed info for

Thank you for attending

dvb-i webinar series€¦ · • same challenges facing operators today reconcile requests from...

Documents

manual stt ci 8000(27-9-11) - gruppo...

to reconcile production with preservation

modulador digital...

ep 3000 premium dvb-s dvb-s2 dvb-t dvb-h dvb-c mpeg4

dvb-t and dvb-t2 transmitter test challenges - … and...

position overview - batchelor · web view2019-03-06 ·...

equipo de transmoduladores dvb-s/s2 a dvb-t dvb-s/s2 · pdf...

chameleon - wisi.de · pdf filedvb-t dvb-c iptv asi sdi/hsdi...

generic stream encapsulation - dvb€¦ · dvb fact sheet -...

dvb einsteiger 02/2014 - zeitungsbeilage der dvb

dvb-t/dvb-t2 monitoring probe

introducere in dvb-h -...

dvb einsteiger 02/2013 - zeitungsbeilage der dvb

6zbz9 reconcile

dvb rocket -- ip to dvb encapsulator - dveo.com

digital video broadcasting (dvb); dvb specification for ......

introductionto dvb-t2 „second generation digital...

dvb einsteiger 03/2014 - zeitungsbeilage der dvb

dvb einsteiger 01/2014 - zeitungsbeilage der dvb

dvb document a012 june 2015 - dvb - digital video ... video...