JP2009032342A - Information storage medium, information reproducing apparatus, and information reproducing method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a technique for reproducing data according to the needs of users. <P>SOLUTION: In an information reproducing method, setting sharing information is stored for sharing reproduction control setting (language, voice, angle, caption, and so forth) among a plurality of contents, and the contents are reproduced on the basis of the setting sharing information. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to an information storage medium such as an optical disk, an information playback apparatus for playing back such an information storage medium, and an information playback method for playing back such an information storage medium.

With the widespread use of video playback devices, various playback functions useful for users have been proposed. For example, a technique has been proposed in which a viewing interruption location is stored in response to a viewing interruption operation, a digest video is dynamically created, and a digest video is presented in response to a viewing resumption operation (see Patent Document 1).
JP-A-8-292965

  Currently, the rapid transition from DVD to its successor standard, HD DVD, is in progress, and many HD DVD contents are being produced and sold. Among them, one of the content forms that will increase in the future is a series (such as a continuous TV drama), and common reproduction control for such contents is desired.

  However, even when reproduction in the same language is requested across a plurality of contents, it is necessary to set a desired language for each content reproduction. Setting the desired language each time is troublesome for the user.

  In addition, when viewing the next work at a later time after appreciation of the previous series, it is desirable to be able to view the digest video up to the previous work before playing the main part of the next work. Also, if you want to continue watching the previous and next series of the same series, it is not necessary to play the digest video up to the previous one.

  However, no technology has been proposed for controlling the playback of digest video according to such playback conditions.

  An object of the present invention is to provide a technique that enables reproduction according to user needs.

  An information storage medium according to an embodiment of the present invention stores setting sharing information for sharing reproduction control settings among a plurality of contents.

  An information reproducing apparatus according to an embodiment of the present invention includes a recording unit that records setting sharing information for sharing a reproduction control setting among a plurality of contents, and a content based on the setting sharing information recorded in the recording unit. And reproducing means for reproducing.

  The information reproducing method according to an embodiment of the present invention records setting sharing information for sharing reproduction control settings among a plurality of contents, and reproduces the contents based on the recorded setting sharing information.

  A data processing method according to an embodiment of the present invention records setting sharing information for sharing a reproduction control setting among a plurality of contents, and reproduces the content based on the recorded setting sharing information.

  A reproduction control program according to an embodiment of the present invention includes a procedure for recording setting sharing information for sharing reproduction control settings among a plurality of contents, and a procedure for reproducing contents based on the recorded setting sharing information. And let the computer run.

  A data transfer method according to an embodiment of the present invention collects reproduction history information from a player, selects content based on the reproduction history information, and transfers the selected content to the player.

  ADVANTAGE OF THE INVENTION According to this invention, the technique which enables the reproduction | regeneration according to a user's needs can be provided.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram showing an outline of an HD DVD.

  HD DVD is the next-generation standard for DVD and features high-quality video and audio, improved interactivity, and network support. Supporting video and audio codecs (compression formats) and a wealth of APIs (a collection of properties and functions defined by the standard) make content creators more attractive and diverse. It is possible to do. Because of these advantages, the transition from current DVD to HD DVD is progressing rapidly.

  FIG. 2 is a diagram illustrating an example of discrimination between standard content and advanced content.

  The HD DVD standard defines two types of content called standard content and advanced content. Standard content is positioned as an extended version of the current DVD standard, and the data structure is similar to the current one, and it is considered that it is easily accepted by studios that have been producing conventional DVDs. However, it has features such as higher quality of video and audio and expansion of usable navigation commands (instruction groups used in title jumps and menus). On the other hand, the advanced content is completely different from the current DVD. In advanced content, in addition to improving the quality of video and audio that can also be seen in standard content, the playback control information is expressed in programming languages such as XML and ECMA scripts, just like a homepage on the Internet. . Also, in the past, all data required for content playback had to be read from the disc, but HD DVD advanced content was read from persistent storage (nonvolatile memory for information storage) in addition to the disc, Data can be downloaded from the network and used for playback.

  In this way, two types of content are defined for HD DVD, and the data structure and the like are different. The present invention targets advanced content of these two types of content.

  Since the HD DVD defines two types of content, standard content and advanced content, the HD DVD player takes a procedure of determining which content is the target content as a start process during content playback. When a disc is inserted, it is first checked whether there is a file describing an advanced content ID or the like called DISCID.DAT (ST2-1). If it exists (ST2-1, YES), the target content is identified as advanced content (ST2-2). If DISCID.DAT does not exist (ST2-1, NO), then it is confirmed whether the standard content ID information VMG_ID is valid (ST2-3). If it is valid (ST2-3, YES) It is determined as standard content (ST2-4), and if it is not valid (ST2-3, NO), it is determined as an unknown content (one that is neither advanced content nor standard content of HD DVD), and the subsequent operation is It depends on the player (ST2-5). Since the present invention targets the advanced content of HD DVD, the following description will be made assuming that the inserted disc is determined to be advanced content.

  FIG. 3 is a diagram showing a data structure of HD DVD advanced content. The data structure of HD DVD advanced content is as follows.

  Play list: A playback control file written in XML language.

  ・ DISCID.DAT: Setting file that describes disk ID and provider ID.

  Primary video set: Consists of primary audio video including data such as video and audio used for playback. The primary audio video is composed of main video (main video), main audio (main audio), sub video (sub video), sub audio (sub audio), sub picture (subtitle), and the like.

  Secondary video set: Consists of data such as video and audio intended to replace the primary video set. There are three types of secondary video sets: substitute audio video (replace main video and main audio), substitute audio (replace main audio), and secondary audio video (replace sub video and sub audio).

  -Advanced application: Data for an application for placing menu buttons on the screen or performing trick play. Manifest (XML file that defines what data is used in the application), markup (XML file that defines button arrangement and timing processing), script (playback control file written in ECMA script), image file, It consists of effect audio (sound file for sound effect), font (open type font used when displaying a message on the screen, etc.) and the like.

  Advanced subtitle: A subtitle that can be described as an application in XML, separately from a subtitle (sub-picture) adapted to the video stream. An advanced subtitle markup is used in which the markup for the advanced application is specialized for subtitles.

  FIG. 4 is a diagram showing the directory and file structure of HD DVD advanced content.

  First, the root directory of advanced content is divided into three areas. The first is an HVDVD_TS directory area for storing the primary video set. The second is an ADV_OBJ directory area for storing data such as playlists, DISCID.DAT, advanced applications, advanced subtitles, and secondary video sets. The third is another user-defined area. As shown in the example in the figure, it is possible to further dig a directory for advanced content under the ADV_OBJ directory. DISCID.DAT must be placed directly under the ADV_OBJ directory. Further, in the case of content that needs to read a playlist from the disc (details will be described later), at least one playlist file must exist immediately under ADV_OBJ.

  FIG. 5 is a diagram showing start-up processing for advanced content playback. That is, FIG. 5 is a diagram illustrating the startup process after the content is determined to be the advanced content.

  ・ S1: Read the DISCID.DAT file. After processing, go to B1.

  -B1: Branch processing is performed depending on whether the display is defined. If defined, go to B2 branch processing. If not defined, go to B4 branch processing.

  -B2: Branch processing based on whether SEARCH_FLG (a flag indicating whether or not to search the initial playlist from the persistent storage. Details of the data structure of DISCID.DAT will be described later) specified in the DISCID.DAT file is 1. Do. If 1, the process proceeds to S3, and if 0, the process proceeds to S2.

  S2: A playlist file (VPLST $$$. XPL) under a specific directory in all persistent storages is searched. After processing, go to S3.

  S3: A playlist file (VPLST $$$. XPL) directly under the ADV_OBJ directory in the disc is searched. After processing, go to B3.

  -B3: Branch processing is performed depending on whether one or more VPLST $$$. XPL is found. If one or more are found, go to S4. If not found, go to B4.

  S4: Start playback with the largest playlist in VPLST $$$. XPL as the initial playlist.

  B4: Branch processing is performed based on whether SEARCH_FLG (a flag indicating whether or not to search the initial playlist from the persistent storage. The details of the data structure of DISCID.DAT will be described later) specified in the DISCID.DAT file is 1. Do. If 1, the process proceeds to S6, and if 0, the process proceeds to S5.

  S5: Search for a playlist file (APLST $$$. XPL) under a specific directory in all persistent storages. After processing, go to S6.

  S6: A playlist file (APLST $$$. XPL) directly under the ADV_OBJ directory in the disc is searched. After processing, go to B5.

  -B5: Branch processing is performed depending on whether one or more APLST $$$. XPL is found. If one or more are found, go to S7, otherwise go to S8.

  S7: Start playback with the largest playlist in APLST $$$. XPL as the initial playlist.

  ・ S8: Startup process failed. The subsequent operation depends on the player.

  FIG. 6 is a diagram showing an outline of the HD DVD advanced content player.

  The HD DVD advanced content player reads the advanced content from the disc 2, reads it from the persistent storage (nonvolatile memory for storing information) 1, or downloads it from the network 3. Data according to the HD DVD format in these data sources is distributed to the navigation manager 5, the data cache 7, and the presentation engine 8 through a part called data access manager 6 that controls data access. The navigation manager 5 is a part responsible for playback control, and receives player settings and settings related to playback from a setting storage unit 4 that stores settings related to player settings and playback. Playback control files (playlists, manifests, markups, scripts, etc.) written in XML or ECMA script are sent from the data access manager 6 to the navigation manager 5 (not directly but once loaded into the data cache 7) The contents are interpreted. A command based on the interpreted reproduction control information is output to the presentation engine 8 and used for reproduction control. It is also the role of the navigation manager 5 to receive user operations such as button operations on the remote controller, process them into playback control commands, and output them to the presentation engine 8. The data cache 7 is a memory for temporarily storing data used for reproduction. The presentation engine 8 determines the actual video and audio output based on the playback control command and the data used for playback (primary video set, secondary video set, etc.), and plays the video and audio data It is a part that converts it into information that can be used. The data for reproduction originally stored on a disk or the like is multiplexed with video and audio and cannot be used for reproduction as it is. Therefore, first, the presentation engine 8 selects data such as video / audio necessary for reproduction, and performs a process of returning the multiplexed data (referred to as demax). Since the data created by the above process is encoded by various codecs (compression methods), it is decoded. Based on the data thus created and the playback control command from the navigation manager 5, the presentation engine 8 sequentially outputs the playback data and the like to the AV renderer 9, which is a part that performs video overlay processing and audio mixing processing. To go. Then, according to the signal from the AV renderer 9, video and audio flow from the television monitor and the speaker, respectively.

  FIG. 7 shows the data structure of DISCID.DAT. DISCID.DAT is a setting file for setting the content ID and where the playlist is read from.

  ・ CONFIG_ID: ID of the configuration file. It is described as “HDDVD-V_CONF” in ISO8859-1 character code. 12 bytes.

  -DISC_ID: ID of the disk described in binary representation. When not using the network, fill it with “1b”. 16 bytes.

  -PROVIDER_ID: Provider ID described in binary representation. If the provider ID directory in the persistent storage is not used, fill it with “1b”. 16 bytes.

  -CONTENT_ID: ID of the content described in binary representation. If the provider ID directory in the persistent storage is not used, fill it with “1b”. 16 bytes.

  SEARCH_FLG: A flag indicating whether or not to search in the persistent storage when searching for an initial playlist in the startup process. Enter “0b” if not searching, and “1b” if searching. 1 byte.

  • reserved: 67 bytes are left as a reserved area.

  The playlist will be described with reference to FIGS.

  The playlist is a reproduction control file for describing information related to initial system settings, synchronization information between objects used for reproduction, and the like. The playlist is described in the XML language, and stores playback control information such as when to play back the primary video set, secondary video set, advanced application, advanced subtitle, and the like as shown in FIG.

  As shown in FIG. 9, the sentence <? Xml ...?> Described in the first line is a description called an XML declaration. This declaration indicates that "this document is written in XML language". In XML, each element is held in a tree shape. The root element of the playlist (the root element of the tree) is a playlist element. The playlist element is described as a portion surrounded by <Playlist ...> and </ Playlist>. In this example, <Configuration> (structure information), <MediaAttributeList> (media attribute information), and <TitleSet> (title information) are described as child elements of the playlist element. The structure information describes information related to system settings, and the media attribute information includes information related to video and audio codecs (compression methods) used for playback. In the title information, object mapping information such as which video is played at which timing is described.

  FIG. 10 is a diagram illustrating a data structure of title information.

  The title information is configured by describing one or more <Title> elements as child elements of the <TitleSet> element. Also, as a child element of the <TitleSet> element, playlist application element information can be described in addition to the <Title> element (details will be described later). Information related to each title (referred to as title element information) is described in the <Title> element.

  As shown in FIG. 11, the title element information includes object mapping information (object allocation information in title reproduction), resource information (resource information such as an image used in a title), and playback sequence information (a unit called chapter). Information for dividing titles), track navigation information (information for assigning video and audio tracks), schedule control information (information for pausing and generating events at a certain timing), etc. Is included.

  As shown in FIG. 12, object mapping information, which is a kind of title element information, includes information on the playback start / end times of objects such as video, audio, advanced application, and advanced subtitle, and information on files used for playback thereof. Is described.

  As shown in FIGS. 12 to 14, elements that can be described as object mapping information include <PrimaryAudioVideoClip> element (such as a primary audio video playback start / end time and a URI indicating the location where the object is stored as a file). Information), <SubstituteAudioVideoClip> element (including information such as the start / end time of the substitute audio video playback and URI indicating the location where the object is stored as a file), <SubstituteAudioClip> element (sub (Including information such as the start / end time of the state audio playback and URI indicating the location where the object is stored as a file), <SecondaryAudioVideoClip> element (the playback start / end time of the secondary audio video and the object ), <AdvancedSubtitleSegment> element (describes information such as advanced subtitle display start / end time and URI indicating the advanced subtitle manifest file), < ApplicationSegment> element (describes information such as execution start / end time of the advanced application and URI indicating the manifest file of the advanced application).

  An advanced application described as object mapping information of title element information is called a title application. The title application is valid only during playback of the title (strictly speaking, only during the playback start / end time specified by the <ApplicationSegment> element during playback of the title). On the other hand, an advanced application that is effective during reproduction of the playlist is called a playlist application. As shown in FIG. 15, information about the playlist application can be described in the form of a <PlaylistApplication> element as a child element of the <TitleSet> element.

  FIG. 16 is a diagram illustrating a data structure of a manifest.

  In the <ApplicationSegment> element of the playlist, specify the manifest file used in the application. The manifest is initialization information for the advanced application. The player activates the advanced application according to the information described in the manifest. In the manifest, information on the markup executed first, information on the script (s) executed in the application start process, and the like are described in the XML language.

  The root element of the manifest is an <Application> element. In a child element of the <Application> element, a region element <Region>, a script element <Script>, a markup element <Markup>, and a resource element <Resource> can be described. Multiple <Script> and <Resource> can be described, one <Region> is required, and <Markup> must be 0 or 1.

  The <Region> element specifies a region on the application canvas. The <Script> element specifies a script file (details will be described later) used in the application. In the <Markup> element, specify the markup file to be used in the application. In the <Resource> element, all resources used in the application (including the above script file and markup file in addition to image data and font data) are specified.

  FIG. 17 is a diagram showing a basic structure of a markup description sentence.

  Markup is a playback control file described in XML language. Markup is used to place buttons or display messages on the screen. A plurality of markups cannot be reproduced simultaneously for one advanced application.

  As shown in FIG. 17, the root element of the markup is <root>, and timing information, styling information, content information, and the like are described in the child. Content information is information about buttons and objects used in an application, such as <button> element, <object> element, <input> element, and the like. Timing information is information related to the operation when the button is pressed, and includes <animate> element, <event> element, <set> element, and the like. Styling information is information used to specify the button layout and font display size, and is realized by setting various attributes (style: fontSize, style: backgroundColor, etc.) of the <style> element Can be made.

  18 and 19 are diagrams for explaining the script.

  The script is a playback control file described by an ECMA script. In HD DVD, a property (value that can be referred to by name: eg Player.countryCode property contains the player's country code) or a function (processing: eg Player.playlist.pause () function is called. In addition to the paused playback), you can use HD DVD specific properties and functions. A set of properties and functions that can be used is called an API.

  As shown in FIG. 18, there are the following 12 types of APIs specific to HD DVD.

・ Application API
Defines objects that can be used in applications.System API
Defines string arrays and timers that can be used with the HD DVD systemFile IO API
Specified I / O functions for persistent storage
Mainly defines objects used for debugging during player development
Regulations on remote control keys and mouse cursors, etc.Drawing API
Defines functions used to draw figures on the screen.Network API
Provides functions for downloading playback data from the Internet-Data Cache API
Defines properties for obtaining the size of the data cache (temporary storage memory)-Player API
Specified playback control functions such as fast-forward, title jump, video size conversion, etc.-Persistent Storage API
Defines properties for acquiring information related to persistent storage. XML API
Specified functions for manipulating information written in XML language such as markupAnimated Property API
Specifies functions for getting / setting elements and attributes described in markup. By using these APIs, one frame of the video being played is saved as a still image in the persistent storage. Various things can be realized, such as drawing pictures and changing the text of messages displayed in markup.

  For example, when an event called “captureEvent” is issued (the event issuance can be described in a playlist or set by markup so that it is issued when a button is pressed), playback is paused. Then, the video image displayed at that time is captured as a still image and stored in a file cache (temporary storage memory). After that, the size of the still image is changed to 1/2 and displayed on the screen (the area defined as CaptureDisplayWindow in the markup).

  FIG. 20 is a diagram showing an outline of language setting sharing among a plurality of contents.

  Information about playback control settings for one content is stored using a script variable storage area or a storage area called a system parameter in the HD DVD player, but the former information is used when content is replaced. In the latter case, the usage and data structure are clearly defined in the standard. For this reason, neither mechanism area can be used to hold setting sharing information for sharing playback control settings among a plurality of contents.

  Therefore, in this embodiment, the persistent storage 1 and the network server 3 are used as a medium for holding the setting shared information. This realizes sharing of playback control settings among a plurality of contents. As a result, the user can enjoy the same language setting and sound setting throughout the series without resetting the playback control. Furthermore, it is possible to easily realize multi-story content according to the playback status up to the previous series.

  Next, language setting sharing among a plurality of contents will be described.

  In advanced content of HD DVD-Video, the language setting is stored in a system parameter (storage area) called SPRM (21), which is copied to a system parameter called SPRM (0) at the start of content playback. Assigned to the HD DVD-Video API property Player.menuLanguage. SPRM (21) retains the value without being reset even if the content playback is stopped or the content to be played is replaced, so when the user restarts playback or plays another content, You can watch content with the same language setting without re-setting the language. However, SPRM (21) cannot hold the language setting for each series. For example, if the viewing of a series is temporarily interrupted and other contents are viewed in another language setting, the language must be set again when the viewing of the series is resumed. In this example, the content of the series is taken as an example, but this is the same even when it is desired to divide the language for each content provider.

  Therefore, in the present embodiment, a method and apparatus for holding a language setting for each series or each content provider and sharing the language setting among a plurality of corresponding contents is proposed.

Approach 1: Player side approach The existing HD DVD player has only one system parameter (SPRM (21)) as a language setting holding area. The player of this embodiment includes a setting storage unit 4 as shown in FIG. 6, and the setting storage unit 4 includes a language setting holding area for each series in addition to the SPRM (21) as shown in FIG. . Alternatively, the persistent storage 1 or the network server 3 includes a language setting holding area for each series. The information in the language setting holding area can be edited by the user, and the information in the language setting holding area includes at least information about what content is to be set (generally a list of multiple contents) and information on the language to be set. Including. As shown in FIG. 20, since it is considered that it is convenient to set the title of the series at the time of re-editing, information may be added in this way. A user interface in which the player acquires information on the released content via a network or the like so that the user can edit the target content list, discloses the information to the user, and the user selects from among the information. Implement.

  FIG. 21 is a flowchart at the start of content playback when sharing language settings held for each series among a plurality of contents.

  Before starting normal playback, the navigation manager 5 checks whether or not the playback content is included in the target content for language setting (ST21-1), and if not included (ST21-1, NO), do nothing as it is. Normal playback (ST21-3), if included (ST21-1, YES), SPRM (21) is updated to the set language (ST21-2), and normal playback is started (ST21). -3). In this way, by adding the processing before the normal reproduction, it is not necessary to make any changes to the normal reproduction part.

Approach 2: Content Side Approach FIG. 22 is a diagram illustrating an example of adding a language setting sharing application to content. The approach 1 is to add a convenient function to the player, but another method to devise on the content side (information storage medium side storing the content) is also proposed. In this method, it is possible to share language settings among a plurality of contents by playing back an information storage medium storing a language setting sharing application without any changes on the player side.

  In this embodiment, an application for holding the language setting in the persistent storage is added to the content. However, to add an application, a language setting sharing application may be prepared and added, or a description for language setting sharing may be added to an existing application. The target application may be a title application (set by an application segment) or a playlist application.

  FIG. 23 shows an example of language setting sharing pseudo code described in an application script. In Example 1, when a system event application_end issued at the end of an application is picked up, the language setting at that time is saved in a language setting sharing file on the persistent storage. In Example 2, the language setting at that time is saved in the language setting sharing file on the persistent storage every 10 seconds by the timer. However, in the case of Example 2, it is wasteful to save every 10 seconds, so it is judged whether the saved language setting information is the same as the current language setting, and overwritten only when it is different. Yes. In both Example 1 and Example 2, when the application is started, it is determined whether or not the language setting information related to the content being played back is saved in the language setting sharing file. If saved, the playback language setting is saved. Update information.

  By adding the algorithm shown in the pseudo code for language setting sharing like the above example to the script, the language setting can be shared among a plurality of contents. However, although a 10-second timer or an application_end event is used here as an example, this is not limited to 10 seconds, and is not limited to the application_end event. Also, three examples of the format of the language setting sharing file are shown in FIG. 24. Regarding the format, only the series name and the setting language information may be used as in Example 1, or the audio setting and subtitle setting may be set as in Example 2. It may be stored in the same file as the above, or only minimal information about the setting language may be used as in Example 3. In other words, any format can be used as long as the setting language information can be uniquely specified between the contents for which the language setting is to be shared. For example, a method of specifying the file name without describing anything in the file itself can achieve the same effect. it can. In addition, setting an ID for each user, dividing a file, and the like are also conceivable.

  Next, sharing of audio settings among a plurality of contents will be described.

  In the advanced content of HD DVD-Video, the audio settings (which audio track to select as the audio to be played back) are held in a system parameter called Selected Audio Track Number, which is the HD DVD-Video API called Player.track.selectedAudioTrackNumber. Copied to property. During content playback, these system parameters and API properties work together to maintain the same value. The Selected Audio Track Number system parameter is not reset even when content playback is stopped or the content to be played is replaced, so the user generally retains the value when resuming playback or playing back another content. In addition, it is possible to view the content with the same audio setting without resetting the audio. However, the selected audio track number system parameter cannot hold the audio setting for each series. For example, if the appreciation of a series is interrupted and other contents are viewed with other audio settings, the audio must be set again when resuming the appreciation of the series. In this example, the content of the series is taken as an example, but this is the same even when it is desired to divide audio for each content provider.

  Therefore, this embodiment proposes a method and apparatus for holding audio settings for each series or content provider and sharing the audio settings among a plurality of corresponding contents.

Approach 1: Player Side Approach Existing HD DVD players have only one system parameter (Selected Audio Track Number) as an audio setting holding area. The player of the present embodiment includes a setting storage unit 4 as shown in FIG. 6, and the setting storage unit 4 as shown in FIG. 25 is for each series in addition to one system parameter (Selected Audio Track Number). A voice setting holding area is provided. Alternatively, the persistent storage 1 or the network server 3 includes an audio setting holding area for each series. The information in the audio setting holding area for each series can be edited by the user, and the information in the audio setting holding area for each series is at least information indicating what content is to be set (generally a list of multiple contents) ) And the audio information to be set. As shown in FIG. 25, it can be considered that it is more convenient to re-edit if the title of the series is set, so information may be added in this way. A user interface in which the player acquires information on the released content via a network or the like so that the user can edit the target content list, discloses the information to the user, and the user selects from among the information. Implement.

  FIG. 26 is a flowchart at the start of content reproduction when the audio settings held for each series are shared among a plurality of contents.

  Before starting normal playback, the navigation manager 5 checks whether or not the playback content is included in the audio setting target content (ST26-1). If not included (ST26, NO), the navigation manager 5 does nothing. Is included in the normal playback (ST26-3), and if included (ST26-1, YES), the selected audio track number is updated to the set sound (ST26-2) and normal playback is started (ST26-). 3). In this way, by adding the processing before the normal reproduction, it is not necessary to make any changes to the normal reproduction part.

Approach 2: Content Side Approach FIG. 27 is a diagram illustrating an example of adding an audio setting sharing application to content. The approach 1 is to add a convenient function to the player, but another method to devise on the content side (information storage medium side storing the content) is also proposed. In this method, voice settings can be shared among a plurality of contents by playing back an information storage medium storing a voice setting sharing application without any changes on the player side.

  In the present embodiment, an application for holding the audio setting in the persistent storage is added to the content. However, to add an application, a voice setting sharing application may be prepared and added, or a voice setting sharing description may be added to an existing application. The target application may be a title application (set by an application segment) or a playlist application.

  FIG. 28 is a diagram illustrating an example of the voice setting sharing pseudo code described in the script of the application. In Example 1, when the system event application_end issued at the end of the application is picked up, the voice setting at that time is saved in the voice setting sharing file on the persistent storage. In Example 2, the voice setting at that time is stored in the voice setting sharing file on the persistent storage every 10 seconds by the timer. However, in the case of Example 2, it is wasteful to save every 10 seconds, so it is judged whether the saved voice setting information and the current voice setting are the same, and overwritten only when they are different. Yes. In both Example 1 and Example 2, when the application is started, it is determined whether the audio setting information related to the content being played is saved in the audio setting sharing file. If saved, the playback audio setting is saved. Update information.

  The voice setting can be shared among a plurality of contents by adding the algorithm shown in the pseudo code for voice setting sharing like the above example to the script. However, although a 10-second timer or an application_end event is used here as an example, this is not limited to 10 seconds, and is not limited to the application_end event. Also, three examples of the format of the audio setting sharing file are shown in FIG. 29. As for the format, only the series name and the set audio information may be used as in Example 1, and the language setting and subtitle setting as in Example 2 may be used. It may be stored in the same file as the above, or only the minimum information related to the set voice as in Example 3 may be used. In other words, any format can be used as long as the set audio information can be uniquely specified between the contents for which the audio settings are to be shared. For example, the same effect can be obtained by specifying the file name without describing anything in the file itself. it can. In addition, setting an ID for each user, dividing a file, and the like are also conceivable.

  Next, sharing of angle settings between a plurality of contents will be described.

  HD DVD-Video supports multi-angle, which allows you to enjoy video from various angles by switching video tracks. In advanced content, the angle setting (which video track to select as the playback angle) is held in a system parameter called Selected Video Track Number, which is copied to the HD DVD-Video API property called Player.track.selectedVideoTrackNumber . During content playback, these system parameters and API properties work together to maintain the same value. Since the Selected Video Track Number system parameter is not reset even when content playback is stopped or the content to be played is replaced, the user generally retains the value when resuming playback or playing back another content. In addition, content can be viewed with the same angle setting without resetting the angle. However, the selected video track number system parameter cannot hold the angle setting for each series. For example, if the viewing of a series is temporarily interrupted and other content is viewed at another angle setting, the angle must be set again when resuming the viewing of the series. In this example, the content of the series is taken as an example, but this is the same even when it is desired to divide the angle for each content provider.

  Therefore, this embodiment proposes a method and apparatus for holding an angle setting for each series or each content provider and sharing the angle setting among a plurality of corresponding contents.

Approach 1: Player Side Approach Existing HD DVD players have only one system parameter (Selected Video Track Number) as the angle setting holding area. The player of the present embodiment includes a setting storage unit 4 as shown in FIG. 6, and the setting storage unit 4 as shown in FIG. 30 is for each series in addition to one system parameter (Selected Video Track Number). An angle setting holding area is provided. Alternatively, the persistent storage 1 or the network server 3 includes an angle setting holding area for each series. The information of the angle setting holding area for each series can be edited by the user, and the information of the angle setting holding area for each series is at least information indicating what content is to be set (generally a list of multiple contents) And the angle information to be set. As shown in FIG. 30, it is considered that it is more convenient to re-edit if the title of the series is set, so information may be added in this way. A user interface in which the player acquires information on the released content via a network or the like so that the user can edit the target content list, discloses the information to the user, and the user selects from among the information. Implement.

  FIG. 31 is a flowchart at the start of content reproduction when the angle setting held for each series is shared among a plurality of contents.

  Before starting normal playback, the navigation manager 5 checks whether the playback content is included in the angle setting target content (ST31-1). If not included (ST31-1, NO), the navigation manager 5 Without normal playback (ST31-3), if included (ST31-1, YES), the Selected Video Track Number is updated to the set angle (ST31-2) and normal playback is started (ST31-2). ST31-3). In this way, by adding the processing before the normal reproduction, it is not necessary to make any changes to the normal reproduction part.

Approach 2: Content Side Approach FIG. 32 is a diagram illustrating an example of adding an angle setting sharing application to content. The approach 1 is to add a convenient function to the player, but another method to devise on the content side (information storage medium side storing the content) is also proposed. In this method, angle settings can be shared among a plurality of contents by playing back an information storage medium storing a voice setting sharing application without any changes on the player side.

  In this embodiment, an application for holding the angle setting in the persistent storage is added to the content. However, to add an application, an application for sharing an angle setting may be prepared and added, or a description for sharing an angle setting may be added to an existing application. The target application may be a title application (set by an application segment) or a playlist application.

  FIG. 33 is a diagram showing an example of the angle setting sharing pseudo code described in the script of the application. In Example 1, when the system event application_end issued at the end of the application is picked up, the angle setting at that time is saved in the angle setting sharing file on the persistent storage. In Example 2, the angle setting at that time is stored in the angle setting sharing file on the persistent storage every 10 seconds by the timer. However, in the case of Example 2, it is wasteful to save every 10 seconds, so it is determined whether the saved angle setting information and the current angle setting are the same, and overwritten only when they are different. Yes. In both Example 1 and Example 2, when the application is started, it is determined whether the angle setting information related to the content being played is saved in the angle setting sharing file. If saved, the playback angle setting is saved. Update information.

  By adding the algorithm shown in the pseudo code for sharing the angle setting as in the above example to the script, the angle setting can be shared among a plurality of contents. However, although a 10-second timer or an application_end event is used here as an example, this is not limited to 10 seconds, and is not limited to the application_end event. Also, three format examples of the angle setting sharing file are shown in FIG. 34. Regarding the format, only the series name and the setting angle information may be used as in Example 1, or the language setting and subtitle setting may be set as in Example 2. It may be stored in the same file as the above, or only the minimum information regarding the setting angle may be used as in Example 3. In other words, any format can be used as long as the setting angle information can be uniquely specified between the contents for which the angle setting is to be shared. For example, the same effect can be obtained by specifying the file name without describing anything in the file itself. it can. In addition, setting an ID for each user, dividing a file, and the like are also conceivable.

  Next, sharing of subtitle settings among a plurality of contents will be described.

  In the advanced content of HD DVD-Video, the subtitle setting (which subtitle track is selected as the subtitle to be played back) is held in the system parameter called Selected Subtitle Track Number, which is the HD DVD-Subtitle API called Player.track.selectedSubtitleTrackNumber. Copied to property. During content playback, these system parameters and API properties work together to maintain the same value. The Selected Subtitle Track Number system parameter is not reset even when content playback is stopped or the content to be played is replaced, so the user generally retains the value when resuming playback or playing back another content. In addition, content can be viewed with the same subtitle setting without resetting the subtitle. However, the selected subtitle track number system parameter cannot hold subtitle settings for each series. For example, if the viewing of a series is temporarily interrupted and other contents are viewed with other subtitle settings, the subtitles must be set again when resuming the viewing of the series. Here, series content is used as an example, but this is the same even when subtitles are to be divided for each content provider.

  Therefore, this embodiment proposes a method and apparatus for holding subtitle settings for each series or content provider and for sharing subtitle settings among a plurality of corresponding contents.

Approach 1: Player Side Approach Existing HD DVD players have only one system parameter (Selected Subtitle Track Number) as a subtitle setting holding area. The player of this embodiment includes a setting storage unit 4 as shown in FIG. 6, and the setting storage unit 4 as shown in FIG. 35 is for each series in addition to one system parameter (Selected Subtitle Track Number). A caption setting holding area is provided. Alternatively, the persistent storage 1 or the network server 3 includes a caption setting holding area for each series. The information of the subtitle setting holding area for each series can be edited by the user, and the information of the subtitle setting holding area for each series includes at least information indicating what content is to be set (generally a list of multiple contents). Contains subtitle information to be set. As shown in FIG. 35, since it is considered that it is more convenient to re-edit the title of the series, information may be added in this way. A user interface in which the player acquires information on the released content via a network or the like so that the user can edit the target content list, discloses the information to the user, and the user selects from among the information. Implement.

  FIG. 36 is a flowchart at the start of content reproduction when the subtitle settings held for each series are shared among a plurality of contents.

  Before starting normal playback, the navigation manager 5 checks whether or not the playback content is included in the target content for subtitle setting (ST36-1), and if not included (ST36-1, NO), Without normal playback (ST36-3), if included (ST36-1, YES), the selected subtitle track number is updated to the set subtitle (ST36-2) and normal playback is started (ST36-2). ST36-3). In this way, by adding the processing before the normal reproduction, it is not necessary to make any changes to the normal reproduction part.

Approach 2: Content Side Approach FIG. 37 is a diagram illustrating an example of adding an angle setting sharing application to content. The approach 1 is to add a convenient function to the player, but another method to devise on the content side (information storage medium side storing the content) is also proposed. In this method, it is possible to share subtitle settings among a plurality of contents by playing back an information storage medium storing an angle setting sharing application without any changes on the player side.

  In the present embodiment, an application for maintaining the caption setting in the persistent storage is added to the content. However, to add an application, a special application for sharing caption settings may be prepared and added, or a description for sharing caption settings may be added to an existing application. The target application may be a title application (set by an application segment) or a playlist application.

  FIG. 38 shows an example of subtitle setting sharing pseudo code described in an application script. In Example 1, when the system event application_end issued at the end of the application is picked up, the subtitle setting at that time is saved in the subtitle setting sharing file on the persistent storage. In Example 2, the subtitle setting at that time is saved in the subtitle setting sharing file on the persistent storage every 10 seconds by the timer. However, in the case of Example 2, it is wasteful to save every 10 seconds, so it is determined whether the saved subtitle setting information is the same as the current subtitle setting, and overwritten only when it is different. Yes. In both Example 1 and Example 2, when the application is started, it is determined whether or not the caption setting information related to the content being played is saved in the caption setting sharing file. If saved, the playback caption setting is saved. Update information.

  By adding the algorithm shown in the pseudo code for subtitle setting sharing like the above example to the script, the subtitle setting can be shared among a plurality of contents. However, although a 10-second timer or an application_end event is used here as an example, this is not limited to 10 seconds, and is not limited to the application_end event. In addition, FIG. 39 shows three format examples of the subtitle setting sharing file. As for the format, only the series name and the set subtitle information may be used as in Example 1, or the language setting and subtitle setting may be performed as in Example 2. May be stored in the same file as the above, or only the minimum information regarding the set subtitles may be used as in Example 3. In other words, any format can be used as long as the set subtitle information can be uniquely specified between the contents for which the subtitle settings are to be shared. For example, the method of specifying the file name without describing anything in the file itself can achieve the same effect. it can. In addition, setting an ID for each user, dividing a file, and the like are also conceivable.

  Next, playback control for controlling the playback of a digest video according to the playback situation up to the previous work will be described.

  When watching series of content continuously, it may be in the way of the viewer that the digest video up to the previous work flows every time. Therefore, the navigation manager 5 stores reproduction history information indicating “how far the reproduction has been performed” or the like in the persistent storage 1 or the setting storage unit 4 during the reproduction of the content. The navigation manager 5 reads the reproduction history information and controls the reproduction of the digest video in the reproduction of the next work.

  Although the present embodiment is not limited to the content reproduction of the series, here, the content reproduction of the series is taken as an example, and an expression such as “nth content in the series” is used.

  When viewing of the series up to the (n-1) th is completed and the time is close to the nth playback start time, the playback of the digest video at the start of the nth playback may be an obstacle. Also, if the appreciation has not progressed to the end of the (n-1) th, it may be a problem if a digest video that can understand the contents of the scene that has not been viewed is suddenly played back. I don't intend to go back to seeing it, so sometimes I want you to play a digest that understands the content. Thus, a mechanism in which the digest reproduction method is branched according to the reproduction situation up to the previous work is useful.

In order to realize this, in this embodiment,
During playback, the playback history information including the information about the playback progress indicating how far the playback has progressed and the time at that time is stored in the persistent storage 1 or the setting storage unit 4. The persistent storage 1 or the setting before digest playback The playback history information stored in the storage unit 4 is acquired, and digest playback is controlled according to the playback history information.

  Therefore, as shown in FIG. 40, a description for digest reproduction control is added to the playlist and application. FIG. 41 is a diagram illustrating a description example of a playlist and a script. A description that events are sequentially issued as playback progresses is added to the playlist. In the present embodiment, an event indicating that the title has been played to the end is issued just before the end of each title. In the application script, the event is picked up, the time information at that time is stored in the persistent storage 1 or the setting storage unit 4, and the series stored in the persistent storage 1 or the setting storage unit 4 is reproduced. Update progress. When digest playback control information (playback history information) is stored in the persistent storage 1 or the setting storage unit 4 at the beginning of the next digest playback, the digest playback control information (playback history information) is stored. The digest reproduction method is branched from the reproduction progress and the viewing time information included in the information for reading and digest reproduction control (reproduction history information). However, this is only an example, and the playback progress and time information may be updated every 10 seconds with a timer instead of an event, or an application_end event issued when the application ends may be used. FIG. 42 shows three format examples for storing the playback end time. Any format can be used as long as the playback end time can be shared between contents. For example, the same effect can be achieved by specifying the file name without describing anything in the file itself. In addition, setting an ID for each user, dividing a file, and the like are also conceivable.

  By adding the above mechanism, it is possible to control the playback of the digest video according to the playback status up to the previous work.

  Next, a description will be given of playback control that suppresses playback when an attempt is made to watch the current work without watching the previous work.

  In general, when viewing content of a series, it is often more enjoyable to view content up to the (n-1) th content before viewing the nth content. This embodiment implements a mechanism that prevents the nth content from being viewed until all the content up to the (n-1) th content is viewed. The navigation manager 5 updates the reproduction history information as the content is reproduced. Further, the navigation manager 5 controls the reproduction of content based on the reproduction history information. That is, the navigation manager 5 restricts (suppresses) the reproduction of the nth content based on the information that has not been reproduced until the (n−1) th content included in the reproduction history information.

  FIG. 43 is a diagram illustrating an example of adding a mechanism for suppressing playback to a playlist and an application. Add a mechanism to issue an event to the playlist when you want to save what you have already watched. In the application, a mechanism for picking up the event and setting a flag indicating that the event has already been viewed is added to the reproduction progress information of the persistent storage 1 or the setting storage unit 4. As a result, the reproduction progress information is sequentially updated as the reproduction proceeds. Then, another application reads the playback progress information in the persistent storage 1 or the setting storage unit 4 at the beginning of content playback, and branches the playback according to the information (normal playback or forced playback). Add a mechanism). As a result, the playback progress of the contents up to the (n−1) th can be stored, and the nth playback can be controlled by the information. An application for adding these mechanisms may be a title application or a playlist application.

  FIG. 44 is a diagram illustrating a pseudo code example of a mechanism to be added. In this embodiment, a mechanism is added in which events tt1end and tt2end are issued just before the end of the title 1 and title 2 of the playlist. On the application side, those events are picked up, and reproduction history information including information indicating that reproduction up to title 1 and title 2 has been completed is stored in persistent storage 1 or setting storage unit 4. Thereby, the playback progress can be sequentially stored. Also, if the playback progress information included in the playback history information of the persistent storage 1 or the setting storage unit 4 is acquired in the code executed at the start of the application, and all the flags are set up to the end of the previous work Adds a mechanism to suppress playback, such as normal playback, otherwise forced stop or displaying the message “Please play after watching the previous work”. The event issue timing of the playlist may not be just before the end of the title as in this embodiment, and the method of saving the playback progress in the persistent storage 1 or the setting storage unit 4 may not be in the flag format. However, it is not necessary that the reproduction suppression branching method, the message content, and the like are all as described in this embodiment.

  Next, a privilege grant process for giving a privilege to a user when all the series (all contents in the same series) are viewed will be described.

  This embodiment provides a mechanism for giving a privilege to a user who has watched the entire series. In order to achieve this, the playback progress is stored sequentially, and the mechanism for creating information to determine whether the user has watched the entire series, and when judging from that information and judging that all have been watched Need a mechanism to give benefits For example, the navigation manager 5 sequentially stores the playback history (playback progress) in the persistent storage 1 or the setting storage unit 4 and performs a specific operation (privilege) based on the completion of playback of all the content of the same series determined from the playback history. ). The details will be described below.

  FIG. 45 is a diagram illustrating an example in which a mechanism for sequentially storing reproduction progress information is added to content. As shown in FIG. 45, for each point, a mechanism for issuing an event indicating that it has been played is added to the playlist. A mechanism for picking up the event and sequentially updating the reproduction progress information of the persistent storage 1 or the setting storage unit 4 is added to the application side. The application may be a title application or a playlist application.

  FIG. 46 is a diagram showing pseudo code of an example script for saving information related to a playlist that issues a scheduled event indicating that playback has been performed up to title 1 and title 2 and playback progress in the persistent storage 1 or the setting storage unit 4. It is. In the present embodiment, an event called tt1end and tt2end is issued immediately before the end of title 1 and title 2, respectively, and the application (script) side picks up these events to detect persistent storage 1 or The playback progress information in the setting storage unit 4 is updated. With such a mechanism, the playback progress information of the series is sequentially updated, and it is possible to create information necessary for the final determination for determining whether or not to give a privilege.

  FIG. 47 is a diagram illustrating an example in which a mechanism for giving a privilege to a user who has watched all the series is added to the content. In the present embodiment, a mechanism for determining whether or not the user has viewed the entire series and a mechanism for giving a privilege when all of the series have been viewed are added to the playlist and application of the last work of the content of the series. In the playlist, a description for issuing an event at the end of the main part reproduction (timing to start determination) is added. On the application side, a mechanism is added that picks up the event, determines whether all the events have been viewed, and gives a privilege to the user if so. The application may be a title application or a playlist application, and the event issuance timing may not be the last part of the main part.

  FIG. 48 is a diagram illustrating a description example of a playlist and a script of a mechanism for granting a privilege. In the present embodiment, a description for issuing an event “series_end” is added to the playlist immediately before the end of the title 2 of the content composed of the titles 1/2 (that is, at the end of the main part of the series). On the application side, the series_end event is picked up, whether or not the reproduction progress information of the series is stored in the persistent storage 1 or the setting storage unit 4, and if it is stored, all the series of the playback progress information are viewed. It is determined whether the completed flag is set, and if both are yes, a mechanism for giving a privilege to the user is added. As a method of giving a privilege, jump to a bonus title (Example 1), display a keyword for receiving a present (Example 2), and display a screen for registering an address name and the like and transmitting it to a network server (Example 3) Various examples are conceivable, but other than these three examples may be used.

  By introducing the mechanism as described above, it is possible to determine whether or not the entire series has been viewed and to give a privilege to the user if it has been viewed.

  Next, selection of HD DVD-Video content distribution using a WEB server will be described.

  In this embodiment, by transmitting necessary information to the WEB server at a certain timing, the content provider can select the content according to the reproduction status of the user and deliver the most effective one to the user. It is.

  For example, consider a case where a trailer of content in a series is provided from a network to a user. With the recent increase in disk capacity, the time for content recorded on one disk has also increased. In such an environment, if there is no playback status information from the user for content that has already been sold, content that is provided only at a granularity that provides the trailer of the next disc for each disc is provided. Cannot be selected. In such a case, it is necessary to create a trailer so that it does not affect whether you are watching only the first half of the disc or after watching the second half, and provide an effective trailer for each user. Is difficult. Therefore, there is a great advantage that the content provider can freely select the content to be played back according to the playback status of the user.

  FIG. 49 is a flowchart showing playback of HD DVD-Video content using a WEB server.

  If there is previous playback information stored in the persistent storage 1 before the content playback (ST49-1, YES), the navigation manager 5 of the player shown in FIG. 6 transmits the previous playback information to the server (ST49-). 2). As shown in FIG. 42, the previous playback information has a playback end time and various types of information that the content provider considers valid (chapter number, title number, user ID for specifying who is playing, etc.). Have. Furthermore, the navigation manager 5 of the player transmits a request for playback content (ST49-3).

  When the server has received the previous playback information, the server selects the content based on the previous playback information and the playback content request and transmits it to the player. When the previous playback information has not been received, the server selects the content based on the playback content request. Select and send to the player (ST49-4).

  The navigation manager 5 of the player reproduces the notice bias transmitted from the server side (ST49-5), and reproduces the main part (ST49-6). In addition, after the main part is started to be played, necessary information is recorded in the persistent storage 1 every 10 seconds (ST49-9) or necessary information is recorded for each event (application_end event, etc.). (ST49-9). As a result, the content to be transmitted can be selected using the information on the server side when the next reproduction is resumed.

  FIG. 50A is a diagram illustrating an image of information stored in the server. In the example shown in FIG. 50A, four contents are selected. In the playlist included in the actual content, the URL (http://www.contentprovider.org/cm.MAP) of the resource as described in the 13th line in FIG. 51 is described. As shown in FIG. 50B, the server receives the reproduction request URL (ST50B-1), selects content based on the previous reproduction information sent earlier (ST50B-2), and requests the requested file name, In this case, it is renamed to cm.MAP and sent to the playlist (ST50B-3). As a result, even if the URL recorded on the disc is the same, the most effective content can be reproduced for the user according to the reproduction status of the player.

  FIG. 52 is a diagram showing a playback process for starting playback by jumping to the previous playback time point.

  If there is previous playback information stored in the persistent storage 1 before content playback (ST52-1, YES), the player navigation manager 5 shown in FIG. 6 transmits the previous playback information to the server (ST52-). 2). As shown in FIG. 42, the previous playback information has a playback end time and various types of information that the content provider considers valid (chapter number, title number, user ID for specifying who is playing, etc.). Have. Furthermore, the navigation manager 5 of the player transmits a request for playback content (ST52-3).

  When the server has received the previous playback information, the server selects the content based on the previous playback information and the playback content request and transmits it to the player. When the previous playback information has not been received, the server selects the content based on the playback content request. Select and send to the player (ST52-4).

  The player's navigation manager 5 reproduces the notice bias transmitted from the server side (ST52-5), and uses the information at the end of the previous reproduction in the persistent storage 1 in the same manner as the resume function of the player. Playback is started from that point (ST52-6) (ST52-7).

  The resume function of the player cannot hold the value once the disc is taken out. However, in this case, as long as the information in the persistent storage 1 exists, the playback can be resumed from the same time as when the previous playback was finished. This is very effective when a player is used by a plurality of users.

  Furthermore, if an ID or the like for identifying each user is added to the information stored in the persistent storage 1, finer settings can be made even when a plurality of people view the same content.

  If the information stored in the persistent storage 1 is increased, for example, the content to be transmitted on the server side is selected by language setting, audio setting, subtitle setting, etc., the content to be reproduced is changed, or the markup to be used is changed. By doing so, it is possible to automatically provide the user with content in accordance with each language, audio, subtitles, and the like.

  After reproduction of the main part is started, necessary information is recorded in the persistent storage 1 every 10 seconds as described above (ST50-10), or necessary information is recorded for each event (such as an application_end event) ( ST50-10). As a result, the content to be transmitted can be selected using the information on the server side when the next reproduction is resumed, and jump reproduction can be performed on the player side.

  According to the present embodiment described above, it is possible to share information among a plurality of contents, and users who can watch the contents of the series with the same audio setting without the trouble of resetting, or who have watched all the contents of the series Can be given benefits, and playback control according to the playback status of content up to the previous work can be realized.

  Note that the present invention is not limited to the above-described embodiment, and various modifications can be made without departing from the scope of the invention in the implementation stage. In addition, the embodiments may be appropriately combined as much as possible, and in that case, the combined effect can be obtained. Further, the above embodiments include inventions at various stages, and various inventions can be extracted by appropriately combining a plurality of disclosed constituent elements. For example, even if some constituent requirements are deleted from all the constituent requirements shown in the embodiment, the problem described in the column of the problem to be solved by the invention can be solved, and the effect described in the column of the effect of the invention Can be obtained as an invention.

It is a figure which shows the outline | summary of HD DVD. It is a figure which shows an example of discrimination | determination of a standard content and an advanced content. It is a figure which shows the data structure of HD DVD advanced content. It is a figure which shows the directory and file structure of HD DVD advanced content. It is a figure which shows the startup process of advanced content reproduction | regeneration. 1 is a diagram showing an outline of an HD DVD advanced content player. FIG. It is a figure which shows the data structure of DISCID.DAT. It is a figure regarding a play list. It is a figure regarding a play list. It is a figure regarding a play list. It is a figure regarding a play list. It is a figure regarding a play list. It is a figure regarding a play list. It is a figure regarding a play list. It is a figure regarding a play list. It is a figure which shows the data structure of a manifest. It is a figure which shows a markup description sentence basic structure. It is a figure for demonstrating a script. It is a figure for demonstrating a script. It is a figure which shows the outline | summary of the language setting sharing between several content. It is a figure which shows an example of the reproduction | regeneration processing at the time of language setting sharing. It is a figure which shows the example which adds the application for language setting sharing to a content. An example of pseudo code for language setting sharing written in an application script is shown below. It is a figure which shows the example of a format of the file for language setting sharing. It is a figure which shows the outline | summary of audio | voice setting sharing between several content. It is a figure which shows an example of the reproduction | regeneration processing at the time of audio | voice setting sharing. It is a figure which shows the example which adds the application for audio | voice setting sharing to a content. An example of pseudo code for sharing voice settings described in an application script is shown. It is a figure which shows the example of a format of the file for audio | voice setting sharing. It is a figure which shows the outline | summary of the angle setting sharing between several content. It is a figure which shows an example of the reproduction | regeneration processing at the time of angle setting sharing. It is a figure which shows the example which adds the application for angle setting sharing to a content. An example of the pseudo code for sharing the angle setting described in the application script is shown below. It is a figure which shows the example of a format of the file for angle setting sharing. It is a figure which shows the outline | summary of subtitle setting sharing between several content. It is a figure which shows an example of the reproduction | regeneration processing at the time of subtitle setting sharing. It is a figure which shows the example which adds the application for subtitle setting sharing to a content. An example of pseudo code for sharing caption settings described in an application script is shown below. It is a figure which shows the example of a format of a file for subtitle setting sharing. It is a figure which shows the outline | summary of digest reproduction | regeneration control. It is a figure which shows the example of a description of the play list and script for implement | achieving digest reproduction | regeneration control. It is a figure which shows the example of a format of reproduction | regeneration end time preservation | save. It is a figure which shows an example of the mechanism addition for reproduction | regeneration suppression to a play list and an application. It is a figure which shows the example of a description of the play list and script for reproduction | regeneration suppression implementation | achievement. It is a figure which shows the example which added to the content the mechanism which preserve | saves reproduction progress information sequentially. It is a figure which shows the pseudo code of the example of a script which preserve | saves the playlist which issues the scheduled event which shows having reproduced | regenerated to the title 1 and the title 2, and the information regarding a reproduction progress in a persistent storage. It is a figure which shows the example which added the structure which gives a privilege to the user who watched all the series to content. It is a figure which shows the example of a description of the play list and script of the structure which provides a privilege. It is a flowchart which shows reproduction | regeneration of HD DVD-Video content using a WEB server. It is a figure which shows the image of the information stored in a server. It is a flowchart which shows the transmission process of the reproduction | regeneration content by a server. It is a figure which shows the example of a description of a play list. It is a figure which shows the reproduction | regeneration processing which jumps to the last reproduction | regeneration time and starts reproduction | regeneration.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Persistent storage, 2 ... Disk, 3 ... Network, 4 ... Setting storage part, 5 ... Navigation manager, 6 ... Data access manager, 7 ... Data cache, 8 ... Presentation engine, 9 ... AV renderer

Claims (19)

  An information storage medium storing setting sharing information for sharing reproduction control settings among a plurality of contents.   The information storage medium according to claim 1, wherein the setting sharing information includes information for sharing at least one setting of a language, audio, angle, and subtitle among a plurality of contents. Recording means for recording setting sharing information for sharing playback control settings among a plurality of contents;
Playback means for playing back content based on the setting shared information recorded in the recording means;
An information reproducing apparatus comprising:   The information reproducing apparatus according to claim 3, wherein the setting sharing information includes information for sharing at least one setting of a language, audio, angle, and subtitle among a plurality of contents. Recording means for recording the reproduction history of the content in a predetermined storage location;
Playback control means for controlling playback of content based on the playback history recorded by the recording means;
An information reproducing apparatus comprising:   6. The information reproducing apparatus according to claim 5, wherein the reproduction control unit controls reproduction of a digest based on the reproduction history recorded by the recording unit.   The reproduction control means restricts reproduction of second content in the same series as the first content based on non-reproduction of the first content determined from the reproduction history recorded by the recording means. An information reproducing apparatus described in 1.   6. The information reproducing apparatus according to claim 5, wherein the reproduction control unit performs a specific operation based on completion of reproduction of all contents of the same series determined from the reproduction history recorded by the recording unit. Record setting sharing information for sharing playback control settings among multiple contents,
An information reproduction method for reproducing content based on the recorded setting shared information.   10. The information reproducing method according to claim 9, wherein the setting sharing information includes information for sharing at least one setting of a language, audio, angle, and subtitle among a plurality of contents. Record content playback history,
An information reproduction method for controlling reproduction of content based on the recorded reproduction history.   The information reproduction method according to claim 11, wherein digest reproduction is controlled based on the recorded reproduction history.   12. The information reproduction method according to claim 11, wherein reproduction of second content in the same series as the first content is restricted based on non-reproduction of the first content determined from the recorded reproduction history.   12. The information reproduction method according to claim 11, wherein a specific operation is executed based on completion of reproduction of all contents of the same series determined from the recorded reproduction history. Record setting sharing information for sharing playback control settings among multiple contents,
A data processing method for reproducing content based on the recorded setting sharing information. Record content playback history,
A data processing method for controlling reproduction of content based on the recorded reproduction history. A procedure for recording setting sharing information for sharing playback control settings among a plurality of contents;
Replaying content based on the recorded setting sharing information;
Reproduction control program for causing a computer to execute. Procedure to record content playback history,
A procedure for controlling playback of content based on the recorded playback history;
Reproduction control program for causing a computer to execute. Collect playback history information from the player,
Select content based on the playback history information,
A data transfer method for transferring the selected content to the player.

Images