TV LLM Recommend UC

• 1: Dialog configuration
• 2: TV Recommend plugin
• 3: TV LLM Recommend UC resources
• 4: AI configuration by OB

1 - Dialog configuration

Configuration of the generic-dialog for TV Recommend use case

Specific configuration

The TV Recommend use case is triggered by the generic-dialog-v3.
For this use case, the required configuration is:

{
  "id": "generic-dialog-v3",
  "channelDataVersion": "v3",
  "triggerConditions": [
    {
      "intent": "intent.tv.recommend",
      "settings": {
        "locales": {
          "error": [
            "core:flc.answer.error"
          ]
        },
        "needTvResolution": true,
        "payloadType": "tv"
      }
    }
  ]
}

2 - TV Recommend plugin

TV Recommend plugin

Introduction

The TV Recommend plugin resolves requests from a user to obtain personalized recommendations for audiovisual content from Telefónica catalogs.

• Intent: intent.tv.recommend
• Main result intents: MEDIA.SEARCH (default), CHANNEL.PLAY (when zapping to a live channel).

Validate input request

This step validates that the input request fulfills all the requirements from the input schema.

If the input data is invalid, the resource returned is:

• tv:video.model-validation.request.error.

Entities used for search

The plugin works with the following entity types:

Multiple entities & values:
You can repeat the same entity type multiple times and/or provide several values in a single entity using the \|\| separator.

Building the search query

The plugin constructs two query strings:

1. search_query → technical query sent to Kernel API:

   • Group query and channel entities in parentheses.
   • Joins different entity types with AND.
   • Query: split on ||, trim each value, and join with OR inside the parentheses (no quotes).
   • Channel: trim each value, wrap each value in quotes, and join with OR inside the parentheses.
   • Person: trim each value, wrap each value in quotes, and join with AND (no group parentheses).
   • Example:

     ("La 1" OR "La 2") AND "Brad Pitt" AND (mystery OR series)
     

2. search_query_response → a simplified, user-readable query string included in the payload and telemetry.

If no entities are present, the plugin returns a no results response.

API video query (Handler 4P)

Plugin calls Handler4P.tv_4p_handler.get_user_content_search(...) with the following parameters:

• user_id: data[aura_user][user_id]
• administrative_number: data[app_context][user][account_number]
• access_token: data[aura_user][access_token]
• scopes: data[aura_user][scopes]
• purposes: data[aura_user][purposes]
• device_type: data[app_context][device][type]
• catalog_types:
  • Default: VOD, LIVE, L7D
  • Allowed: VOD, LIVE, L7D, LCH, LSR
  • Filtered according to allowed_catalog_types of the device
• search_query: built as explained above
• show_series: series
• profile: data[app_context][user][video_profile_name] (optional; only if present to avoid API 501 errors)
• commercialization_types: [SVOD]
• max_quality: data[app_context][device][max_quality] (optional)
• current_region: data[app_context][location][currentRegion] (optional)
• order: personal

Response logic

Depending on the number and type of results, the plugin builds different responses:

1. No results

• Plays negative sound unless the channel is disabled in the sound_disabled_channels configuration
• result_intent: MEDIA.SEARCH
• Resource: tv:video.recommend.no-results
• Status: SUCCESS.NO_CONTENT

2. One result

• Live channel:
  • Payload: { type: details, data: <channel info> }
  • Action: REMOTEON.ZAPTO (with params channelId and deviceId)
  • Plays positive sound unless the channel is disabled in the sound_disabled_channels configuration
  • result_intent: CHANNEL.PLAY
  • Resource: tv:video.recommend.display.single-result
• Non-live content (VOD, L7D, etc.):
  • Payload: details of the single item
  • Plays positive sound
  • result_intent: MEDIA.SEARCH
  • Resource: tv:video.recommend.by-default.simple-result

3. Multiple results

• Payload: content list and search_query (search query response string)
• Plays positive sound unless the channel is disabled in the sound_disabled_channels configuration
• result_intent: MEDIA.SEARCH
• Resource: tv:video.recommend.multiple-results (with param query_displayed)

Resources returned

The TV Recommend plugin may return the following resources:

• tv:video.model-validation.request.error → input validation error
• tv:video.api.answer.error → API Video error
• tv:video.recommend.no-results → no content found
• tv:video.recommend.by-default.simple-result → one non-live result
• tv:video.recommend.multiple-results → multiple results
• tv:video.recommend.display.single-result → one live channel (tune channel)

Payload and actions

• Payload:

  • type: details (single item) or content_list (multiple items)
  • data: item(s) from Kernel API
  • For multiple results: includes search_query (human-readable string)

• Actions:

  • Sound feedback (positive/negative)
  • For a single live channel: {"name": "REMOTEON.ZAPTO", "params": {"channelId": "$channelId", "deviceId": "$deviceId"}, "target": "stb"}

Status codes

• status: Final status request. This field includes the following parameters:
  • code: Status code with value: SUCCESS, SUCCESS.NO_CONTENT or ERROR.INTERNAL.
  • message: Status message, which describes the status code.
  • params: Parameter that sends details of status. This field does not appear if it is empty.

Example behavior

• “Recommend me something”
  • for a single live channel result → CHANNEL.PLAY tune channel with live channel.
  • for a multiple results → MEDIA.SEARCH with tv:video.recommend.multiple-results.
  • for any results → tv:video.recommend.no-results.

3 - TV LLM Recommend UC resources

TV LLM Recommend UC resources

Introduction

The TV LLM Recommend UC will use three different types of resources:

• Aura Platform global resources
• Common resources for video use cases
• Specific resources for the use case: TV LLM Recommend

Specific resources for the use case: TV LLM Recommend

The resources associated to the TV LLM Recommend plugin are defined below:

4 - AI configuration by OB

AI configuration by OB

The following information applies to both Spain and Brazil; there will not be separate blocks for each OB.

Introduction

LLMs UCs are configured and located within the aura-config-provision repository. See the TV LLM Search Preset (notice that in the url, the field [ob] needs to be replaced by [es] or [br]) LLM use cases have been designed to provide a fallback mechanism for user requests that currently return a ‘None’ intent or zero results, offering a second chance for classification and response generation.

Intent

• intent.tv.recommend: This intent will be returned when the user seeks TV content recommendations and explicitly refers to entities such as genres, subgenres, titles, sports-related content, directors, or actors. Example: “¿Qué documentales me recomiendas?”.

Entities

Three different entities can be returned if mentioned by the user:

• entities.channel: This entity will be returned whenever there is a mention of a TV channel or a third-party TV platform in the user’s request.
• entities.person: This entity will be returned whenever a proper name belonging to an actor, actress, director, driver, boxer, or other public figure is mentioned in the user’s request.
• entities.query: This entity will be returned when any relevant information for performing a search on the platform is mentioned in the user’s request. (e.g., TV titles, genres, subgenres)

LLM output format

Examples: