Client Apparatus XML Metadata Service Discovery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing digital TV services, such as IPTV, face challenges in providing users with an efficient way to search and access various content services from multiple providers, as current systems lack a standardized method for metadata-based service discovery and user interface customization.

Innovation Solution

A client apparatus that receives services from an outside server, featuring a network interface for XML metadata reception and a controller to produce a UI skin based on this metadata, enabling users to easily search and access services from multiple content providers by converting services into XML format and displaying a customized user interface.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple content providers offer diverse services, then service variety increases, but service discovery difficulty increases

Engineering Contradiction:
Improveservice varietyVSAvoidservice discovery difficulty
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent introduces a standardized metadata system as an intermediary between multiple content providers and users. This metadata includes unified service information, provider identifiers, and descriptive attributes that enable systematic organization and searching of services from different providers without requiring users to navigate each provider's unique interface separately

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent transforms service information into standardized metadata parameters that can be systematically searched and filtered. By converting diverse service descriptions into uniform data structures with consistent fields and formats, the system enables efficient service discovery across multiple providers through parameter-based querying

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If each content provider uses its own interface format, then provider autonomy is maintained, but user interface complexity increases

Engineering Contradiction:
Improveprovider autonomyVSAvoiduser interface complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal metadata framework that works across multiple content providers while preserving their individual service characteristics. The standardized metadata structure serves as a common interface layer that handles provider autonomy internally while presenting a unified view to users, eliminating the need for users to adapt to multiple different interface formats

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If service information is provided in non-standardized formats, then provider flexibility is maintained, but search efficiency decreases

Engineering Contradiction:
Improveprovider flexibilityVSAvoidsearch efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent converts flexible, non-standardized service information into standardized metadata parameters that maintain provider flexibility through configurable fields while enabling efficient searching. The standardized parameter structure allows for consistent indexing, filtering, and querying operations that significantly improve search efficiency compared to unstructured formats

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentEP2643937B1Apparatus for receiving services of a plurality of content providers
Publication Date: 2019.01.02 LG ELECTRONICS INC
  • EP2643937B1 patent drawingFigure 1
  • EP2643937B1 patent drawingFigure 2
  • EP2643937B1 patent drawingFigure 3

AI summary

A service providing method providing at least one of service provided from a plurality of contents provider to clients includes receiving metadata related to at least one of service provided from the contents provider; converting the received metadata into the metadata of XML format; and providing the metadata of the XML format to the clients.