Tags:

• use-case-global
• video
• ai

Categories:

• components

TV LLM Recommend UC

Introduction

The video LLM Recommend use case is a global experience designed and developed by Aura Global Team that allows Telefónica customers to ask Aura for content recommendations (live channels and catalog items) using a voice interface.

Find additional information in the following documents:

• Discover the TV LLM Recommend specifications and the particularities of the use case development.
• Learn how to configure the generic-dialog for TV LLM Recommend use case.
• Access the TV LLM Recommend plugin.
• Discover the resources used by the TV LLM Recommend use case.
• Find the AI configuration for each OB for the TV Recommend use case.

Specifications

Kernel API

To resolve the user’s request, Aura uses the normalized Video Contents Kernel API.

Request-response model

The TV LLM Recommend UC is available only when using the normalized request-response model v3.

Available channels

The TV LLM Recommend UC can be enabled in any channel implementing the normalized v3 request-response model and TV-related payloads.

TV LLM Recommend features

The normalized TV LLM Recommend UC includes personalized recommendations:

• Suggest a single live channel (with a zap action).
• Suggest a single catalog item (e.g., VOD).
• Suggest a list of items when multiple results are available.
• Return no content when the API returns no results.

Current limitations

Currently, the TV LLM Recommend UC does not include:

• Fallback/contingency search (as in TV search).
• Filters customized (as persons, genres, participants, …).
• Third-party catalogs outside Aura/Kernel scope.

Use case development

The TV LLM Recommend UC includes these components:

Understanding features

• Intent: intent.tv.recommend

Use case logic

Once Aura recognizes the user’s utterance, the UC is resolved via:

• Aura Bot dialog

  TV LLM Recommend UC is built over generic-dialog-v3.
  See the Dialog configuration for the required settings.

Response

The response follows the standard video plugin response schema.

Where:

• intent: input intent.

• entities: input entities as received.

• result_intent: usually MEDIA.SEARCH; CHANNEL.PLAY is used when returning a single live channel.

• resources: List of response resources that includes three main parameters:

  • type: Type of the response resource.
  • name: Name of the response resource. Example: tv:video.recommend.multiple-results, tv:video.recommend.by-default.simple-result, tv:video.recommend.display.single-result, tv:video.recommend.no-results.
  • params: This field returns any required parameter in the resource. Example: channelId or deviceId for tv:video.recommend.display.single-result.

• payload: Information provided by the Kernel API, when we make the content get info request. If we receive a response, this field includes the following parameters:

  • type: The value of this field depends on the type of data included in the field data (info returned by the API):
    • If it is a value: details
    • If it is a list: content_list
  • data: It returns the information provided by the Kernel API.

• status: Final status request. This field includes the following parameters:

  • code: Status code.
  • message: Status message, which describes the status code.
  • params: Parameter that sends details of status. This field does not appear if it is empty.

• actions: Actions to follow with the result of request. This plugin could include the following actions:

  • REMOTEON.ZAPTO: Used to tune a live channel on STB.

• conditions: conditions for actions to be applied.