Aura –

Docs:

Mon, 01 Jan 0001 00:00:00 +0000

TV search use case

Global use case developed by Aura Platform Team that allows users to search specific TV content in Aura

Introduction

The TV search use case is a global experience designed and developed by Aura Global Team that allows Telefónica customers to ask Aura for TV content using a vocal interface.

Find additional information in following the documents:

Discover the TV search specifications and the particularities of the use case development.
Learn how to configure the generic-dialog for TV search use case.
Access to the TV search plugin.
Discover which are the resources used by the TV search use case.
Find out the NLP configuration for each OB for the TV search use case.

Specifications

Kernel API

In order to resolve the user’s search request, Aura uses Video Contents normalized Kernel API.

Request-response model

TV search use case is adapted to the new request-response normalized model v3.

Available channels

Once TV search v3 use case is fully normalized, it will be available for any channel that implements normalized v3 request-response model including TV related data.

Search features

Currently, the normalized TV search use case includes basic search features and smart answers for entertainment content:

Search by title
Search by genre (movie, series, documentaries, programs, short films and games)
Search by subgenre (action, scare, love, etc)
Search by actor or director

In addition to these search features, the use case includes a contingency or fallback search mode used in case the Video Contents API does not provide any answer to Aura request. The contingency or fallback search mode could be deactivated by configuration.

🆕 As a novelty in the current release, the use case is able to provide the users with smart answers features, meaning that the entities included in the user’s requests can be included in the answer.

Therefore, the answer could be of this type: “That’s what I’ve found about [$title, $participant, $genre, $subgenre]

For example:

The user asks for a specific title: “Play a film starring Brad Pitt”
In previous versions, Aura sends the content provided by the API as “That’s what I’ve found for you”
Now, the entity can be included in the answer, giving the user a most personalized answer: “That’s what I’ve found about Brad Pitt”

Current limitations

Currently, the TV search use case does not include these features:

Request for a specific season o episode of a TV Series.
Search content from third-parties (content must belong to Aura’s catalog).
Search including temporary entities or time intervals.
Search sport content based on entities.

Use case development

The TV search use case development includes these components:

Understanding features

TV search use case intent: intent.tv.search
TV search use case entities:

Entity	Example
`ent.audiovisual_film_title`	“Busca La princesa prometida”
`ent.audiovisual_documental_title`	“Busca ABBA Forever”
`ent.audiovisual_tvshow_title`	“Busca Late Motiv”
`ent.audiovisual_tvseries_title`	“Busca Hierro”
`ent.audiovisual_subgenre`	“Busca una comedia”
`ent.audiovisual_genre`	“Busca una película”
`ent.audiovisual_actor`	“Busca algo de Brad Pitt”
`ent.audiovisual_director`	“Busca algo de Almodóvar”

⚠️ Other entities in the user’s request are not taken into account in the searching process.

In order to understand users’ requests (utterances), Aura is trained with:

NLP expression to recognize the user’s utterance and detect her intention.
TV catalog in order to understand TV content (titles, actors, director) in the user’s utterance and detect them as Aura entities.
Other content like genre or subgenre.

Use case logic

Once Aura has recognized the user’s utterance based on NLP components, the use case should be resolved based on:

Aura Bot dialog:

TV search is built over the generic-dialog-v3.
- Check the section Configuration of the generic-dialog for TV search use case in order to know the required configuration for the TV search experience.
CLF Plugin:

Complex Logic Framework is used for the recognition of the user’s request.
- Check here the TV search plugin.

Docs:

Mon, 01 Jan 0001 00:00:00 +0000

TV display use case

Global use case developed by Aura Platform Team that allows users to display specific TV channels in Aura

Introduction

The TV display use case is a global experience designed and developed by Aura Global Team that allows Telefónica customers to ask Aura for a TV channel or other entities using a vocal interface.

Find additional information in following the documents:

Discover the TV display specifications and the particularities of the use case development.
Learn how to configure the generic-dialog for TV display use case.
Access to the TV display plugin.
Discover which are the resources used by the TV display use case.
Find out the NLP configuration for each OB for the TV display use case.

Specifications

Kernel API

In order to resolve the user’s display request, Aura uses Video Contents normalized Kernel API.

Request-response model

TV display use case is adapted to the new request-response normalized model v3.

Available channels

Once TV display v3 use case is fully normalized, it will be available for any channel that implements normalized v3 request-response model including TV related data.

Display features

Currently, the normalized TV display use case includes the following display features:

Display by channel (both for Brazil and Spain OBs)
Display by content: title, genre, subgenre, actor or director (for Spain OB)

Therefore, the answer could be of this type: “This is what they are broadcasting now on that channel”

Use case development

The TV display use case development includes these components:

Understanding features

TV display use case intent: intent.tv.display
TV display use case entities: Entities vary across the OBs where this experience is available: Check NLP configuration by OB.

In order to understand users’ requests (utterances), Aura is trained with:

NLP expression to recognize the user’s utterance and detect her intention.
TV catalog in order to understand TV content (channels, titles, genres, subgenres, actors, directors) in the user’s utterance and detect them as Aura entities.

Use case logic

Once Aura has recognized the user’s utterance based on NLP components, the use case should be resolved based on:

Aura Bot dialog:

TV display is built over the generic-dialog-v3.
- Check the section Configuration of the generic-dialog for TV display use case in order to know the required configuration for the TV display experience.
CLF Plugin:

Complex Logic Framework is used for the recognition of the user’s request.
- Check here the TV display plugin.

Docs:

Mon, 01 Jan 0001 00:00:00 +0000

TV content get info use case

Global use case developed by Aura Platform Team that allows users to get content info specific TV channels in Aura

Introduction

The TV content get info use case is a global experience designed and developed by Aura Global Team that allows Telefónica customers to ask Aura for a TV channel information using a vocal interface.

Find additional information in following the documents:

Discover the TV content get info specifications and the particularities of the use case development.
Learn how to configure the generic dialog for TV content get info use case.
Access to the TV content get info plugin.
Discover which are the resources used by the TV content get info use case.
Find out the NLP configuration for each OB for the TV content get info use case.

Specifications

Kernel API

In order to resolve the user’s request, Aura uses Video Contents normalized Kernel API.

Request-response model

TV content get info use case is adapted to the new request-response normalized model v3.

Available channels

Once TV content get info v3 use case is fully normalized, it will be available for any channel that implements normalized v3 request-response model including TV related data.

Currently, STB channels in ES are already available.

Display features

Currently, the normalized TV content get info use case includes basic get content information features for channels:

Content get info by channel

Therefore, the answer could be of this type: “This is what they are broadcasting now on that channel”

Use case development

The TV content get info use case development includes these components:

Understanding features

TV content get info use case intent: intent.tv.content_get_info
TV content get info use case entities:

Entity	Example
`ent.audiovisual_channel`	“What’s on in channel 1?”

⚠️ Other entities in the user’s request are not taken into account in the get content info process.

In order to understand users’ requests (utterances), Aura is trained with:

NLP expression to recognize the user’s utterance and detect her intention.
TV catalog in order to understand TV content (channels) in the user’s utterance and detect them as Aura entities.

Use case logic

Once Aura has recognized the user’s utterance based on NLP components, the use case should be resolved based on:

Aura Bot dialog:

TV content get info is built over the generic dialog v3.
- Check the section Configuration of the generic dialog for TV content get info use case in order to know the required configuration for the TV content get info experience.
CLF Plugin:

Complex Logic Framework is used for the recognition of the user’s request.
- Check here the TV content get info plugin.

Docs:

Mon, 01 Jan 0001 00:00:00 +0000

TV move backwards use case

Global use case developed by Aura Platform Team that allows users to move the content backwards on the TV by using Aura

Introduction

The TV move backwards use case is a global experience designed and developed by Aura Global Team that allows Telefónica customers to move the content backwards on the TV using a vocal interface.

Find additional information in following the documents:

Learn how to configure the generic dialog for TV move backwards use case.
Discover which are the resources used by the TV move backwards use case.
Find out the NLP configuration for each OB for the TV move backwards use case.

Specifications

Request-response model

TV move backwards use case is adapted to the new request-response normalized model v3.

Available channels

Once TV move backwards v3 use case is fully normalized, it will be available for any channel that implements normalized v3 request-response model including TV related data.

Currently, STB channel in ES is available for channelData V1. And channelData V3 is suitable for STB in Brazil with time entity recognition: ent.time_length_hour.

Display features

Currently, the normalized TV move backwards use case includes basic move backwards features for some entities:

Move the TV content backwards
Move backwards by specifying the desired time

This UC also includes specific verbs without entities. For AP repository the key verbs are: “retroceder”, “retornar” and “rebobinar”. For Brazil, they are “recuar” and “retroceder”.

Therefore, the answer could be of this type: “Okay, I’ll rewind the TV content.”

Use case development

The TV move backwards use case development includes these components:

Understanding features

TV move backwards use case intent: intent.tv.move_backwards
TV move backwards use case entities:

Entity	Example
`ent.audiovisual_genre`	“Move the movie backwards”
`ent.time_length_hour`	“Move the movie backwards 2 hours”
`ent.time_length_min`	“Move the movie backwards 2 minutes”
`ent.time_length_sec`	“Move the movie backwards 2 seconds”
`ent.time_instant`	“Move it backwards now”

⚠️ Other entities in the user’s request are not taken into account in the move backwards process.

In order to understand users’ requests (utterances), Aura is trained with:

NLP expression to recognize the user’s utterance and detect the user’s intention.

Use case logic

Once Aura has recognized the user’s utterance based on NLP components, the use case should be resolved based on:

Aura Bot dialog:

TV move backwards is built over the generic dialog v3.
- Check the section Configuration of the generic dialog for TV move backwards use case in order to know the required configuration for the TV move backwards experience.

Docs:

Mon, 01 Jan 0001 00:00:00 +0000

TV move forwards use case

Global use case developed by Aura Platform Team that allows users to move the content forwards on the TV by using Aura

Introduction

The TV move forwards use case is a global experience designed and developed by Aura Global Team that allows Telefónica customers to move the content forwards on the TV using a vocal interface.

Find additional information in following the documents:

Learn how to configure the generic dialog for TV move forwards use case.
Discover which are the resources used by the TV move forwards use case.
Find out the NLP configuration for each OB for the TV move forwards use case.

Specifications

Request-response model

TV move forwards use case is adapted to the new request-response normalized model v3.

Available channels

Once TV move forwards v3 use case is fully normalized, it will be available for any channel that implements normalized v3 request-response model including TV related data.

Currently, MH and STB channels in ES are already available for channelData V3 version and MP is available for channelData V1. But for these channels, time entity recognition: ent.time_length_hour is not yet available. It would be available for STB in Brazil.

Display features

Currently, the normalized TV move forwards use case includes basic move forwards features for some entities:

Move the TV content forwards
Move forwards by specifying the desired time

This UC also includes specific verbs without entities. For AP repository the key verbs are: “avanzar” and “adelantar”. For Brazil, they are “adiantar” and “avançar”.

Therefore, the answer could be of this type: “Ok, I’ll fast forward the content a little”

Use case development

The TV move forwards use case development includes these components:

Understanding features

TV move forwards use case intent: intent.tv.move_forwards
TV move forwards use case entities:

Entity	Example
`ent.audiovisual_genre`	“Move the movie forwards”
`ent.time_length_hour`	“Move the movie forwards 2 hours”
`ent.time_length_min`	“Move the movie forwards 2 minutes”
`ent.time_length_sec`	“Move the movie forwards 2 seconds”
`ent.time_instant`	“Move it forwards now”

⚠️ Other entities in the user’s request are not taken into account in the move forwards process.

In order to understand users’ requests (utterances), Aura is trained with:

NLP expression to recognize the user’s utterance and detect the user’s intention.

Use case logic

Once Aura has recognized the user’s utterance based on NLP components, the use case should be resolved based on:

Aura Bot dialog:

TV move forwards is built over the generic dialog v3.
- Check the section Configuration of the generic dialog for TV move forwards use case in order to know the required configuration for the TV move forwards experience.

Docs:

Mon, 01 Jan 0001 00:00:00 +0000

TV VOD EPG information use case

Global use case developed by Aura Platform Team that allows users to get VOD EPG information about the playing content.

Introduction

The TV VOD EPG information use case is a global experience designed and developed by Aura Global Team that allows Telefónica customers to ask Aura about what they are watching on TV at that specific moment using a vocal interface. The use case answers with the name of the TV content being broadcasted.

A user interacts with Aura through a normalized video channel
She asks about the content currently playing: “What am I watching?”, “What’s on?”
Aura recognizes the request and provides back to the channel the information required to answer the request

Find additional information in following the documents:

Discover the TV VOD EPG information specifications and the particularities of the use case development.
Learn how to configure the generic dialog for TV VOD EPG information use case.
Find out the NLP configuration for each OB for the TV VOD EPG information use case.

Specifications

Kernel API

In order to resolve the user’s request, Aura uses Video Contents normalized Kernel API.

Request-response model

TV VOD EPG information use case is adapted to the new request-response normalized model v3.

Available channels

TV VOD EPG information use case could be available for any channel that implements normalized v3 request-response model including TV related data.

Currently, STB channels in BR are already available.

Display features

Currently, the normalized TV VOD EPG information use case includes basic VOD EPG information features for content:

VOD EPG information by content

Therefore, the questions could be of this type: “What am I watching?” “Which actors are involved?”

Use case development

The TV VOD EPG information use case development includes these components:

Understanding features

TV VOD EPG information use case intent: intent.tv-vod_epg_information
TV VOD EPG information use case entities:

Entity	Example
`ent.device_tv`	“¿Qué estoy viendo en la tele?”
`ent.device_mobile`	“¿Qué estoy viendo en el móvil?”
`ent.device_phone`	“¿Qué estoy viendo en el teléfono?”

In order to understand users’ requests (utterances), Aura is trained with:

NLP expression to recognize the user’s utterance and detect the user’s intention.

Use case logic

Once Aura has recognized the user’s utterance based on NLP components, the use case should be resolved based on:

Aura Bot dialog:

TV VOD EPG information is built over the generic dialog v3.
- Check the section Configuration of the generic dialog for TV VOD EPG information use case in order to know the required configuration for the TV VOD EPG information experience.

Docs:

Mon, 01 Jan 0001 00:00:00 +0000

TV none use case

Global use case developed by Aura Platform Team that allows searching content related with the user’s utterance when the intent is intent.tv.none

Introduction

The TV none use case is a global experience designed and developed by Aura Global Team that allows Telefónica customers to ask Aura using a vocal interface.

Find additional information in following the documents:

Discover the TV none specifications and the particularities of the use case development.
Learn how to configure the generic dialog for TV none use case.
Access to the TV none plugin.
Discover which are the resources used by the TV none use case.
Find out the NLP configuration for each OB for the TV none use case.

Specifications

Kernel API

In order to resolve the user’s request, Aura uses Video Contents normalized Kernel API.

Request-response model

TV none use case is adapted to the new request-response normalized model v3.

Available channels

Once TV none v3 use case is fully normalized, it will be available for any channel that implements normalized v3 request-response model including TV related data.

Currently, STB channels in BR are already available.

Display features

Currently, the normalized TV none use case includes basic search features for content/channels:

none search content/channels with user normalized utterance

Therefore, the answer could be any provided by the recognized intent: intent.tv.none

Use case development

The TV none use case development includes these components:

Understanding features

TV none use case intent: intent.tv.none
TV none use case entities: Ignore the entities for search content/channels, use normalized utterance for contigency search.

In order to understand users’ requests (utterances), Aura is trained with:

NLP expression to recognize the user’s utterance and detect her intention.
TV catalog in order to understand TV content (channels) in the user’s utterance and detect them as Aura entities.

Use case logic

Once Aura has recognized the user’s utterance based on NLP components, the use case should be resolved based on:

Aura Bot dialog:

TV none is built over the generic dialog v3.
- Check the section Configuration of the generic dialog for TV none use case in order to know the required configuration for the TV none experience.
CLF Plugin:

Complex Logic Framework is used for the recognition of the user’s request.
- Check here the TV none plugin.

Docs:

Mon, 01 Jan 0001 00:00:00 +0000

Audiovisual App Opening use case

Global use case developed by Aura Platform Team that allows users accessing third-party apps

Introduction

The Audiovisual App Opening use case is a global experience designed and developed by Aura Global Team that allows Telefónica customers to open different third-party apps that are considered audiovisual apps.

A user interacts with Aura through a normalized video channel
The user requests: “I want to put this <app> on the TV”, where <app> is a third-party app
Aura recognizes the request and provides back to the channel the information required to open this app

For example:

“Open Amazon Prime Video app”
“Access TikTok”
“Put Disney on TV”

Find additional information in the following documents:

Discover the Audiovisual App Opening specifications and the particularities of the use case development.
Learn how to configure the generic-dialog for Audiovisual App Opening use case.
Discover the resources used by the Audiovisual App Opening use case
Find out the NLP configuration for each OB for the Audiovisual App Opening use case.

Specifications

Kernel API

In order to resolve the user’s request, Aura uses Video Contents normalized Kernel API.

Request-response model

Audiovisual App Opening use case is adapted to the request-response normalized model v3.

Available channels

STB (aura-nlpdata-br-stb)
GVP (aura-nlpdata-ap)

Use case development

The Audiovisual App Opening use case development includes these components:

Understanding features

Audiovisual App Opening use case intent: intent.tv.app_open
Audiovisual App Opening use case entities:

Entity	Example
`ent.audiovisual_app`	“Open Disney”

In order to understand users’ requests (utterances), Aura is trained with:

NLP expression to recognize the user’s utterance and detect its intention.
TV catalog in order to understand audiovisual apps in the user’s utterance and detect them as Aura entities.

Use case logic

Once Aura has recognized the user’s utterance based on NLP components, the use case should be resolved based on:

Aura Bot dialog:

Audiovisual App Opening is built over the generic-dialog-v3.
- Check the section Configuration of the generic-dialog for Audiovisual App Opening use case in order to know the required configuration for the experience.

Docs:

Mon, 01 Jan 0001 00:00:00 +0000

Change language use case

Global use case developed by Aura Platform Team that allows users to change the language on TV

Introduction

The Change language use case is a global video experience designed and developed by Aura Global Team that allows Telefónica customers to change the language on TV.

A user interacts with Aura through a normalized video channel
The user requests: “Change subtitles to English”
Aura recognizes the request and provides back to the channel the information required

For example:

“Change subtitles to English”
“Put the movie in the original version”

Find additional information in the following documents:

Discover the Change language specifications and the particularities of the use case development.
Learn how to configure the generic-dialog for Change language use case.
Discover the resources used by the Change language use case.
Find out the NLP configuration for each OB for the Change language use case.

Specifications

Kernel API

In order to resolve the user’s request, Aura uses Video Contents normalized Kernel API.

Request-response model

Change language use case is adapted to the request-response normalized model v3.

Available channels

STB (aura-nlpdata-br-stb)
GVP (aura-nlpdata-ap)

Use case development

The Change language use case development includes these components:

Understanding features

Change language use case intent: intent.tv.language_change

Use case logic

Once Aura has recognized the user’s utterance based on NLP components, the use case should be resolved based on:

Aura Bot dialog:
Change language is built over the generic-dialog-v3. Check the section Configuration of the generic-dialog for Change language use case in order to know the required configuration for the experience.

Docs:

Mon, 01 Jan 0001 00:00:00 +0000

Section Show use case

Global use case developed by Aura Platform Team that allows users accessing sections

Introduction

The Section Show use case is a global experience designed and developed by Aura Global Team that allows Telefónica customers to open different sections and navigate through them.

A user interacts with Aura through a normalized video channel
The user requests: “I want to put this <section> on the TV”
Aura recognizes the request and provides back to the channel the information required to open this section

For example:

“Open aventura”
“Access Kids”
“Put films on TV”

Find additional information in the following documents:

Discover the Section Show specifications and the particularities of the use case development.
Learn how to configure the generic-dialog for Section Show use case.
Discover the resources used by the Section Show use case.
Find out the NLP configuration for each OB for the Section Show use case.

Specifications

Kernel API

In order to resolve the user’s request, Aura uses Video Contents normalized Kernel API.

Request-response model

Section Show use case is adapted to the request-response normalized model v3.

Available channels

STB (aura-nlpdata-br-stb)
GVP (aura-nlpdata-ap)

Use case development

The Section Show use case development includes these components:

Understanding features

Section Show use case intent: intent.navigation.section_show
Section Show use case entities:

Entity	Example
`ent.section`	“Open Films”

In order to understand users’ requests (utterances), Aura is trained with:

NLP expression to recognize the user’s utterance and detect its intention.
TV catalog in order to understand audiovisual sections in the user’s utterance and detect them as Aura entities.

Use case logic

Once Aura has recognized the user’s utterance based on NLP components, the use case should be resolved based on:

Aura Bot dialog:

Section Show is built over the generic-dialog-v3.
- Check the section Configuration of the generic-dialog for Section Show use case in order to know the required configuration for the experience.

Docs:

Mon, 01 Jan 0001 00:00:00 +0000

Subtitles remove use case

Global use case developed by Aura Platform Team that allows users to remove the subtitles

Introduction

The Subtitles remove use case is a global experience designed and developed by Aura Global Team that allows Telefónica customers to remove the subtitles.

A user interacts with Aura through a normalized video channel
The user requests: “Remove subtitles from the film”.
Aura recognizes the request and provides back to the channel the information required

For example:

“Remove subtitles from the movie”
“Remove subtitles from this episode”

Find additional information in the following documents:

Discover the Subtitles remove specifications and the particularities of the use case development.
Learn how to configure the generic-dialog for Subtitles remove use case.
Discover the resources used by the Subtitles remove use case.
Find out the NLP configuration for each OB for the Subtitles remove use case.

Specifications

Kernel API

In order to resolve the user’s request, Aura uses Video Contents normalized Kernel API.

Request-response model

Subtitles remove use case is adapted to the request-response normalized model v3.

Available channels

STB (aura-nlpdata-br-stb)
GVP (aura-nlpdata-ap)

Use case development

The Subtitles remove use case development includes these components:

Understanding features

Subtitles remove use case intent: intent.tv.subtitles_remove

Use case logic

Once Aura has recognized the user’s utterance based on NLP components, the use case should be resolved based on:

Aura Bot dialog: Subtitles remove is built over the generic-dialog-v3. Check the section Configuration of the generic-dialog for Subtitles remove use case in order to know the required configuration for the experience.

Docs:

Mon, 01 Jan 0001 00:00:00 +0000

Global resources for TV use cases

This document describes the global resources shared among global TV use cases

Introduction

Apart from the specific resources for each TV-related use case, there are two types of global resources that can be used by any global experience for TV channels, which are described below:

Aura Platform global resources
Common resources for video use cases

Aura Platform global resources

The Aura Platform global resources that can be used by global TV experiences are:

Aura Platform Global resources	Definition	Example	Managed by	Scope
`core:core.model-validation.request.error`	Error generated in the validation of input fields of the request-response v3 model	Lo siento, ha ocurrido un error inesperado	aura-bot	Used by all Aura global use cases
`core:core.model-validation.answer.error`	Error generated in the validation of output fields from the request-response v3 model	Lo siento, ha ocurrido un error inesperado	aura-bot	Used by all Aura global use cases
`core:core.cancel`	Error generated when the request is adapted to normalized format but the triggered dialog is not migrated to v3	Vaya, parece que no soy capaz de entenderte. Inténtalo de nuevo	aura-bot	Used by all Aura global use cases
`core:core.model-validation.version.error`	Error generated when the request is sent with a format version not supported by the channel	Lo siento, ha ocurrido un error inesperado	aura-bot	Used by all Aura global use cases
`core:flc.answer.error`	Error generated by aura-bot in case the CLF API does not respond	Lo siento, ha ocurrido un error inesperado	aura-bot	Used by Aura global use cases using the Complex Logic Framework

Common resources for video use cases

The general video use cases resources that can be used by global TV experiences are:

Common resources for video use cases	Definition	Example	Managed by	Scope
`tv:video.model-validation.request.error`	Error generated when the input request validation fails	Algo no ha ido bien, inténtalo de nuevo	CLF	Used by global video use cases
`tv:video.api.answer.error`	Error generated when API request fails	Lo sentimos, ha ocurrido un error inesperado	CLF	Used by global video use cases

Docs:

Mon, 01 Jan 0001 00:00:00 +0000

Legacy Video API for Spain

Description of Legacy Video API.

Download swagger file

Docs:

Mon, 01 Jan 0001 00:00:00 +0000

Adapter request-response model v1 to v3

This document describes the adapter use cases with request-response model v1 and v3.

Introduction

Adapter use cases allow to work with request-response model v1 to adapt to systems that do not support v3 yet.

Mainly, this adapter receives a request in v1 format and internally transforms it to v3 format to process it with the corresponding TV CLF plugin. Then, the response in v3 format is transformed back to v1 format to send the response.

Dialog Configuration

Specific configuration

The adapter use case is triggered by the generic dialog v1. For this use case, the required specific configuration is set below:

Configuration for Spain OB in STB channel.

{
    "id": "generic-dialog-v1",
    ...
}

Adapter use cases

The adapter use case is intended to work with the following TV use cases: