Content delivery method, scenario data, recording medium, and scenario dat creation method

• US 20040158866A1
• Filed: 12/23/2003
• Published: 08/12/2004
• Est. Priority Date: 06/25/2001
• Status: Abandoned Application

• Current Assignee: Nova Corporation (US Bancorp)
• Original Assignee: Nova Corporation (US Bancorp)
• Inventors: Saruhashi, Nozomu, Uemura, Masahide, Shimamoto, Katsunori, Yasumi, Yu
• Application Number:
  US10/481,767
• Publication Number:
  US 20040158866A1
• Time in Patent Office: Days
• US Class Current: 725/90
• CPC Class Codes: H04N 21/21815 comprising local storage units
• CPC Class Codes: H04N 21/2343 involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements video transcoding H04N19/40; media packet handling at the source H04L65/762
• CPC Class Codes: H04N 21/2402 Monitoring of the downstream path of the transmission network, e.g. bandwidth available traffic monitoring in data switching networks H04L43/00; monitoring data switching networks utilization H04L43/0876
• CPC Class Codes: H04N 21/60 Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client , e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
• CPC Class Codes: H04N 21/6125 involving transmission via Internet transmission by internet of broadcast information H04H60/82
• CPC Class Codes: H04N 21/8153 comprising still images, e.g. texture, background image
• CPC Class Codes: H04N 21/8405 represented by keywords
• CPC Class Codes: H04N 21/854 Content authoring
• CPC Class Codes: H04N 21/8543 using a description language, e.g. Multimedia and Hypermedia information coding Expert Group [MHEG], eXtensible Markup Language [XML] information retrieval of semistructured data, the underlying structure being taken into account, e.g. mark-up language structure data G06F16/80
• CPC Class Codes: H04N 7/16 Analogue secrecy systems; Analogue subscription systems

Abstract

A contents delivery method which eliminates the need for the prior synthesis and storing of delivery contents and thus allows a reduction in memory capacity even when the contents to be delivered consist of a plurality of pieces of material contents which are synthesized. Scenario data for defining the replay order of materials of contents to be delivered, or material contents, along a time axis is used to fetch and deliver material contents specified by the scenario data. The scenario data includes the attribute of delivery contents, and the attributes, replay times, replay modes, replay applications, source terminal operation information, destination terminal operation information, and location information of the material contents specified. There are also provided scenario templates and scenario dictionaries for scenario creation, and a function for creating scenarios automatically.

Claims

1. A contents delivery method for delivering multimedia contents stored in advance to a user terminal by using a communication line, wherein

scenario data for defining replay order of materials of contents to be delivered, or material contents, along a time axis is used to fetch and deliver material contents specified by the scenario data.

2. The contents delivery method according to claim 1, comprising the steps of:

storing the material contents;

storing the scenario data;

fetching the stored scenario data;

fetching material contents specified by the fetched scenario data out of the stored material contents; and

delivering the fetched material contents to the user terminal along with the scenario data.

3. The contents delivery method according to claim 1, comprising the steps of:

storing the material contents;

storing the scenario data;

fetching the stored scenario data;

fetching material contents specified by the fetched scenario data;

synthesizing the fetched material contents based on the scenario; and

delivering the synthesized material contents to the user terminal.

4. Scenario data for use in the contents delivery method according to any one of claims 1 to 3, including attribute information on the contents to be delivered.

5. Scenario data for use in the contents delivery method according to any one of claims 1 to 3, including attribute information on the specified material contents.

6. Scenario data for use in the contents delivery method according to any one of claims 1 to 3, including replay time specification information for specifying the time of replay of the specified material contents.

7. Scenario data for use in the contents delivery method according to any one of claims 1 to 3, including replay mode specification information for specifying whether to replay the specified material contents automatically or at timing designated by the user terminal.

8. Scenario data for use in the contents delivery method according to any one of claims 1 to 3, including replay application specification information for specifying an application for replaying the specified material contents.

9. Scenario data for use in the contents delivery method according to any one of claims 1 to 3, including replay screen specification information for specifying the position and size of the specified material contents to be replayed on-screen.

10. Scenario data for use in the contents delivery method according to any one of claims 1 to 3, including source terminal operation specification information for specifying an operation available to a source terminal, with respect to the specified material contents.

11. Scenario data for use in the contents delivery method according to any one of claims 1 to 3, including destination terminal operation specification information for specifying an operation available to a destination terminal, with respect to the specified material contents.

12. Scenario data for use in the contents delivery method according to any one of claims 1 to 3, including location specification information for specifying a location for storing the specified material contents.

13. Scenario data for use in the contents delivery method according to any one of claims 1 to 3, including replay part specification information for specifying a part of the specified material contents to be replayed.

14. A computer-readable recording medium, on which the scenario data according to any one of claims 4 to 13 is recorded.

15. A computer-readable recording medium, on which the scenario data according to any one of claims 4 to 13 and the material contents specified by the scenario data are recorded.

16. A scenario data creation method, being a method of creating the scenario data according any one of claims 4 to 13, comprising the steps of:

entering a keyword; and

retrieving related material contents based on the entered keyword.

17. A scenario data creation method, being a method of creating the scenario data according any one of claims 4 to 13, comprising the steps of:

providing a scenario dictionary describing relationship between genres for indicating types of delivery contents and the associated information and entering a genre;

consulting the scenario dictionary to retrieve associated information based on the entered genre; and

retrieving related material contents based on the associated information retrieved.

18. A scenario data creation method, being a method of creating the scenario data according any one of claims 4 to 13, comprising the step of:

providing a replay chart displaying a replay time of material contents in the form of a chart and allocating the material contents to the replay chart.

19. A scenario data creation method, being a method of creating the scenario data according any one of claims 4 to 13, comprising the step of:

providing a scenario template describing a basic configuration pattern of scenario data and retrieving material contents settable into the scenario template.

20. A scenario data creation method, being a method of creating the scenario data according any one of claims 4 to 13, comprising the steps of:

providing a scenario dictionary describing a relationship between genres for indicating types of delivery contents and associated information, and a scenario template describing a basic configuration pattern of scenario data, and entering a genre;

consulting the scenario dictionary to retrieve the associated information based on the entered genre;

retrieving related material contents based on the associated information retrieved;

retrieving the scenario template based on the entered genre;

retrieving material contents settable to the retrieved scenario template out of the retrieved material contents; and

transcribing the attribute information on the retrieved material contents to the scenario template.

21. The scenario data creation method according to claim 19 or 20, wherein scenario data created in advance is used as the scenario template.