FLUTE File Delivery Table Presentation Attribute

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The combination of FLUTE file delivery protocol and multimedia presentation technologies, such as SMIL, poses challenges in identifying and rendering presentation files within file delivery sessions, particularly in determining which files constitute a presentation without examining their contents.

Innovation Solution

The introduction of a new 'Presentation' attribute in the File Delivery Table (FDT) schema or using pre-defined naming conventions allows receivers to identify presentation files, enabling efficient delivery and rendering of multimedia presentations by indicating the presence of a presentation file or specifying the type of content and receiver device compatibility.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If FLUTE file delivery protocol is used for multimedia presentation delivery, then file delivery capability is improved, but the ability to identify and render presentation files is worsened

Engineering Contradiction:
Improvefile delivery capabilityVSAvoidpresentation file identification
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent introduces a File Delivery Table (FDT) as an intermediary data structure that mediates between the FLUTE file delivery protocol and multimedia presentation rendering. The FDT contains specific attributes (such as 'presentation' indicator, 'media type', 'duration') that enable receivers to identify presentation files without examining their contents, thus resolving the contradiction between general file delivery capability and specific presentation file identification difficulty

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If receivers examine file contents to determine presentation files, then identification accuracy is improved, but processing time and complexity are worsened

Engineering Contradiction:
Improvepresentation file identification accuracyVSAvoidprocessing time
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-marking presentation files with specific identifiers (such as a 'presentation' attribute or reserved filename patterns) before delivery. This allows receivers to identify presentation files immediately upon reception based on these pre-established markers, eliminating the need to examine file contents and significantly reducing processing time while maintaining identification accuracy

Inventive Principle:
Principle #10Preliminary action

3Ease of manufacture

If FLUTE protocol delivers files without content indication, then delivery simplicity is improved, but receiver processing complexity is worsened

Engineering Contradiction:
Improvedelivery simplicityVSAvoidreceiver processing complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent applies local quality by introducing selective metadata attributes (such as 'presentation' indicator, 'media type', 'duration') specifically for presentation files within the FLUTE delivery stream. This allows the delivery system to maintain simplicity for general files while adding targeted information only where needed for presentation files, thus increasing receiver processing capability without fundamentally complicating the overall delivery mechanism

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS8819702B2File delivery session handling
Publication Date: 2014.08.26 NOKIA TECHNOLOGIES OY
  • US8819702B2 patent drawing
  • US8819702B2 patent drawing
  • US8819702B2 patent drawing

AI summary

Embodiments described herein may include sending transport objects that include content; sending presentation objects that include instructions for providing a presentation of the content; and sending a delivery object that lists at least one of transport object and indicates the content of the transport object. In some embodiments the delivery object may include data identifying the presentation objects; the instructions may include a start time and an end time for the presentation of the content, and a receiver class identifier indicating a group of targeted receivers that have particular receiver capability factors. Some embodiments may include in response to receiving the presentation objects, selecting one of the presentation objects at least partly based on the terminal class identifier; and providing a presentation of the content as defined by the selected presentation object.