JP2007018623A - Information recording medium and reproducing apparatus and reproducing method therefor - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To solve the problem that it is difficult to completely control behavior of synchronous reproduction where a digital stream such as video data and an interactive content are interlocked when reproduction controlling circumstances by an application described by using a new HTML and a script are introduced in a BD-ROM for the image data. <P>SOLUTION: Attribute information showing designation whether synchronous execution of the digital stream such as the video data and the interactive content is set and designation whether synchronous recording at a specified timing is set is introduced in management information for managing the interactive content of the BD-ROM. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to an information recording medium on which video data is recorded, such as a BD-ROM, and a playback apparatus and playback method thereof, and more particularly to an improvement in the case of introducing a programming environment to the development of content including video data and a program.

  A typical information recording medium on which video data is recorded is a DVD (hereinafter referred to as SD-DVD or simply DVD). Hereinafter, a conventional DVD will be described.

  FIG. 1 is a diagram showing the structure of an SD-DVD. As shown in the lower part of FIG. 1, a logical address space is provided on the DVD disc from lead-in to lead-out, and the volume information of the file system is recorded from the head of the logical address space, followed by video / audio, etc. Application data is recorded.

  A file system is ISO9660 or UDF (Universal Disc Format), and is a mechanism for expressing data on a disk in units called directories or files. Even in the case of a personal computer (PC) that is used daily, data recorded on a hard disk in a directory or file structure is expressed on the computer by passing through a file system called FAT or NTFS, thereby improving usability. In the case of SD-DVD, both UDF and ISO9660 are used (sometimes referred to as “UDF bridge” together), and data is read by either UDF or ISO9660 file system drivers (DVDs handled here are This is a ROM disk for package media, and is physically unwritable).

  Data recorded on the DVD can be viewed as a directory or file as shown in the upper left of FIG. 1 through the UDF bridge. A directory called “VIDEO_TS” is placed directly under the root directory (“ROOT” in the figure), and DVD application data is recorded therein. Application data is recorded as a plurality of files, and the main files are as follows.

VIDEO_TS. IFO disc playback control information file VTS_01_0. IFO video title set # 1 playback control information file VTS_01_0. VOB video title set # 1 stream file. . . . .
There are two types of extensions. “IFO” is a file in which reproduction control information is recorded, and “VOB” is a file in which an MPEG stream that is AV data is recorded. The playback control information is information for realizing interactivity (technology for dynamically changing playback in accordance with user operations) adopted by DVD, information attached to titles and AV streams such as metadata. And so on. In DVD, generally, reproduction control information is sometimes referred to as navigation information.

  The playback control information file includes “VIDEO_TS.IFO” for managing the entire disc and individual video title sets (multiple titles for DVD, in other words, different movies and different versions of movies can be recorded on one disc. There is “VTS — 01 — 0.IFO” which is reproduction control information for each. Here, “01” in the file name body indicates the number of the video title set. For example, in the case of the video title set # 2, “VTS — 02 — 0.IFO”.

  The upper right part of FIG. 1 is a DVD navigation space in the DVD application layer, which is a logical structure space in which the above-described reproduction control information is expanded. Information in “VIDEO_TS.IFO” is stored in the DVD navigation space as VMGI (VIDEO Manager Information), “VTS — 01 — 0.IFO”, or playback control information existing for each other video title set is stored in the DVD navigation space as VTSI (Video Title Set Information). Be expanded.

  In VTSI, PGCI (Program Chain Information), which is information of a reproduction sequence called PGC (Program Chain), is described. The PGCI is composed of a set of cells and a kind of programming information called a command. Cell itself is a set of a part or all of a VOB (which is an abbreviation of Video Object and indicates an MPEG stream), and playback of a cell means that a section specified by the cell of the VOB is played back. ing.

  The command is processed by a DVD virtual machine and is similar to a Java (registered trademark) script executed on a browser. However, while Java (registered trademark) scripts control windows and browsers in addition to logical operations (for example, opening a new browser window), DVD commands play AV titles in addition to logical operations. It is different in that it only performs control, for example, specifying a chapter to be played back.

  The Cell has VOB start and end addresses (logical addresses) recorded on the disc as its internal information, and the player reads data using the VOB start and end address information described in the Cell. Execute playback.

  FIG. 1 is a schematic diagram for explaining navigation information embedded in an AV stream. The interactivity, which is the feature of SD-DVD, is not realized only by the navigation information recorded in the aforementioned “VIDEO_TS.IFO”, “VTS — 01 — 0.IFO”, etc. It is multiplexed together with video and audio data in a VOB using a dedicated carrier called a pack (called Navi pack or NV_PCK).

  Here, a menu is described as an example of simple interactivity. Several buttons appear on the menu screen, and each button defines processing when the button is selected and executed. In addition, one button is selected on the menu (the highlight button has a translucent color overlaid on the selection button), and the user can use the up / down / left / right keys on the remote control to move the selected button up / down / left / right. It can be moved to any of the buttons. Using the up / down / left / right keys on the remote control, move the highlight to the button you want to select and execute, and press the enter key to execute the corresponding command program. In general, reproduction of a corresponding title or chapter is executed by a command.

  The upper left part of FIG. 2 shows an outline in NV_PCK.

  NV_PCK includes highlight color information and individual button information. In the highlight color information, color palette information is described, and a semi-transparent color of the highlight displayed on the overlay is designated. The button information includes rectangular area information that is position information of each button, movement information from the button to another button (designation of a destination button corresponding to each of the user's up / down / left / right key operations), and button command information. (Command executed when the button is determined) is described.

  The highlight on the menu is created as an overlay image as shown in the upper right part of the center of FIG. The overlay image is obtained by adding the color palette information color to the rectangular area information of the button information. This overlay image is combined with the background image shown on the right and displayed on the screen.

  As described above, the menu is realized in the DVD. The reason why a part of the navigation data is embedded in the stream using NV_PCK is that the menu information is dynamically updated in synchronization with the stream, for example, during 5 to 10 minutes during movie playback. This is because, even in the case of an application in which synchronization timing is likely to be a problem, such as a menu being displayed only on the screen, it can be realized without any problem.

  FIG. 3 is an image of a DVD VOB. As shown in the figure, data (A stage) such as video, audio, subtitles, etc. is packetized and packed (B stage) based on the MPEG system (ISO / IEC13818-1) standard, and each is multiplexed into one. MPEG program stream (stage C). Further, as described above, NV_PCK including a button command for realizing interactive is also multiplexed together.

  The multiplexing feature of the MPEG system is that each data to be multiplexed is a bit string based on the decoding order, but between the multiplexed data, that is, between video, audio and subtitles, it is not necessarily the playback order, in other words For example, the bit string is not formed based on the decoding order. This is because the MPEG system stream decoder model (generally called System Target Decoder or STD (D stage in FIG. 3)) has a decoder buffer corresponding to each elementary stream after demultiplexing, and by the decoding timing It comes from temporarily accumulating data. This decoder buffer has a different size for each elementary stream, and has 232 kB for video, 4 kB for audio, and 52 kB for subtitles. For this reason, since the data input timing to each decoder buffer is different for each elementary stream, there is a difference between the order in which the bit string is formed as the MPEG system stream and the display (decoding) timing.

  That is, subtitle data multiplexed side by side with video data is not necessarily decoded at the same timing.

The configuration of such a DVD is described in Patent Document 1 below.
Japanese Patent No. 2813245

  By the way, the BD-ROM, which is a next-generation information recording medium, is not only a simple navigation command as described above, but also document data described in a declarative language such as XHTML, a program described in a script, The recording of interactive contents composed of image files etc. is planned.

  These interactive contents can be presented in conjunction with a digital stream such as video data, or the operation and execution state can be switched according to the user's remote control operation, providing a more expressive presentation to the user. It is realized.

  In general, in order for an application to present the interactive content in conjunction with a digital stream such as video data, for example, depending on the state of an AV playback control unit that controls the digital stream such as video data, the playback speed of the digital stream, In order to execute various processes according to the reference destination of the digital stream, a program previously described in a script language is associated with document data.

  As described above, the application can control the presentation of the interactive content according to the playback control state. However, when the digital stream such as video data and the interactive content are presented in time synchronization, the HTML constituting the interactive content is displayed. Since it is necessary to describe the synchronization processing corresponding to the video data at any time in the document with a script, it is difficult to completely control the synchronous playback behavior of the digital stream such as video data and interactive content There is.

  In addition, the application is linked with video data such as a user's remote control operation or an event embedded in a digital stream such as video data at a specific time as a trigger to present content at a specific timing. When interactive content presentation control is performed, depending on the execution state of the AV playback control unit and the application, there is a problem that the operation result intended by the user does not match the execution result of the AV playback control unit and the application.

  In order to solve the above-mentioned problems, an information recording medium according to the present invention starts and executes a resource file such as a document file described in a declarative language constituting interactive content and an image file related to the document. And management information that stores logical configuration information in the content, attribute information of each file, and the like are managed in association with the content.

  As additional information of the management information, identification information indicating whether or not to perform synchronized playback and linked presentation of video data and content is set.

  With the above-described configuration, in the synchronous playback or linked presentation of video data and interactive content, the processing content corresponding to the playback state control of the digital stream such as video data is included in the document described in the declarative language that constitutes the interactive content. It is possible to control the behavior of synchronized playback of video data and content more simply without assuming a script in advance assuming any state.

Example 1
First, a first embodiment of the present invention will be described.

(Logical data structure on disk)
FIG. 4 shows the structure of a BD-ROM (hereinafter also referred to as “BD”), in particular, the structure of a BD disk (104) as a disk medium and data (101, 102, 103) recorded on the disk. FIG. Data recorded on the BD disc (104) is AV data (103), BD management information (102) such as management information related to AV data and an AV playback sequence, and a BD playback program (101) that realizes interactive processing. . In the present embodiment, a BD disc will be described mainly with respect to an AV application for reproducing AV contents such as movies, but the BD disc will be used as a recording medium for computers such as a CD-ROM and a DVD-ROM. Of course, it is also possible.

  FIG. 5 is a diagram showing logical data recorded on the BD disc described above. A BD disc has a spiral recording area from the inner circumference to the outer circumference like other optical discs such as DVDs and CDs, and logical data is transferred between the inner lead-in and outer lead-out. It has a logical address space that can be recorded. Further, inside the lead-in, there is a special area that can be read only by a drive called BCA (Burst Cutting Area). Since this area cannot be read from an application, it is often used for copyright protection technology, for example.

  Application data such as video data is recorded in the logical address space with file system information (volume) at the head. As described in the prior art, the file system is UDF, ISO9660 or the like, and logical data recorded in the same way as a normal PC can be read using a directory and file structure. .

  In the case of this embodiment, the directory and file structure on the BD disc is a BDVIDEO directory placed directly under the root directory (ROOT). This directory is a directory in which data (101, 102, 103 described in FIG. 4) such as AV contents and management information handled by the BD-ROM is recorded.

  The following seven types of files are recorded under the BDVIDEO directory.

BD. INFO (fixed file name)
This is one of “BD management information” and is a file in which information related to the entire BD disc is recorded. The BD player first reads this file.

BD. PROG (fixed file name)
It is one of “BD playback programs” and is a file in which programs related to the entire BD disc are recorded.

XXX. PL ("XXX" is variable, extension "PL" is fixed)
It is one of “BD management information”, and is a file in which play list information for recording a scenario is recorded. I have one file per playlist.

XXX. PROG ("XXX" is variable, extension "PL" is fixed)
It is one of “BD playback programs” and is a file in which a program for each playlist described above is recorded. Correspondence with a playlist is identified by a file body name (“XXX” matches).

YYY. VOB ("YYY" is variable, extension "VOB" is fixed)
It is one of “AV data” and is a file in which VOB (same as VOB described in the conventional example) is recorded. There is one file for each VOB.

YYY. VOBI ("YYY" is variable, extension "VOBI" is fixed)
This is one of “BD management information” and is a file in which management information related to VOB as AV data is recorded. The correspondence with the VOB is identified by the file body name (“YYY” matches).

ZZZ. PNG ("ZZZ" is variable, extension "PNG" is fixed)
It is one of “AV data” and is a file in which image data PNG (an image format standardized by W3C and read as “ping”) for composing subtitles and menus is recorded. There is one file for each PNG image.

(Player configuration)
Next, the configuration of the player that plays the above-described BD disc will be described with reference to FIGS. 6 and 7. FIG.

  FIG. 6 is a block diagram showing a rough functional configuration of the player.

  Data on the BD disc (201) is read through the optical pickup (202). The read data is recorded in a dedicated memory according to the type of each data. The BD playback program (the contents of the “BD.PROG” or “XXX.PROG” file) is stored in the program recording memory (203) in the BD management information (“BD.INFO”, “XXX.PL” or “YYY.VOBI”). Are recorded in the management information recording memory (204), and AV data ("YYY.VOB" or "ZZZ.PNG") is recorded in the AV recording memory (205).

  The BD playback program recorded in the program recording memory (203) is recorded by the program processing unit (206), and the BD management information recorded in the management information recording memory (204) is recorded by the management information processing unit (207). The AV data recorded in the memory (205) is processed by the presentation processing unit (208).

The program processing unit (206) receives event information such as playlist information to be played back and program execution timing from the management information processing unit (207), and processes the program. Also, the program can dynamically change the play list to be played back. In this case, the play list play command is sent to the management information processing unit (207). The program processing unit (206) receives an event from the user, that is, a request from the remote control key, and executes an execution process when there is a program corresponding to the user event.

  The management information processing unit (207) receives an instruction from the program processing unit (206), analyzes the management information of the VOB corresponding to the corresponding playlist and the playlist, and the AV data to be processed by the presentation processing unit (208). Instruct to play. Also, the management information processing unit (207) receives the reference time information from the presentation processing unit (208), instructs the presentation processing unit (208) to stop AV data reproduction based on the time information, and the program processing unit An event indicating the program execution timing is generated for (206).

  The presentation processing unit (208) has a decoder corresponding to each of video, audio, and caption / image, and decodes and outputs AV data in accordance with an instruction from the management information processing unit (207). In the case of video data and subtitles / images, after decoding, the video data and subtitles / images are drawn on the respective dedicated planes, the video plane (210) and the image plane (209), and the video synthesis process is performed by the synthesis processing unit (211). Output to the device.

  As shown in FIG. 6, the BD player has a configuration based on the data configuration recorded on the BD disc shown in FIG.

  FIG. 7 is a detailed block diagram of the player configuration described above. In FIG. 7, the AV recording memory (205) is in the image memory (308) and the track buffer (309), the program processing unit (206) is in the program processor (302) and the UOP manager (303), and the management information processing unit (207). ) Is a scenario processor (305) and a presentation controller (306), and a presentation processing unit (208) is a clock (307), a demultiplexer (310), an image processor (311), a video processor (312) and a sound processor (313). Are corresponding to each.

  The VOB data (MPEG stream) read from the BD disc (201) is recorded in the track buffer (309), and the image data (PNG) is recorded in the image memory (308). The demultiplexer (310) extracts the VOB data recorded in the track buffer (309) based on the time of the clock (307), and sends the video data to the video processor (312) and the audio data to the sound processor (313). The video processor (312) and the sound processor (313) are each composed of a decoder buffer and a decoder as defined by the MPEG system standard. That is, the video and audio data sent from the demultiplexer (310) are temporarily recorded in the respective decoder buffers and decoded by the individual decoders according to the clock (307).

  The PNG recorded in the image memory (308) has the following two processing methods. If the image data is for subtitles, the presentation controller (306) instructs the decoding timing. In order for the scenario processor (305) to receive the time information from the clock (307) once and display the appropriate subtitles, the subtitles are displayed to the presentation controller (306) at the subtitle display time (start and end). Give hidden instructions. The image processor (311) that has received the decode / display instruction from the presentation controller (306) extracts the corresponding PNG data from the image memory (308), decodes it, and draws it on the image plane (314).

  Next, when the image data is for a menu, the program processor (302) instructs the decoding timing. The time when the program processor (302) instructs to decode the image depends on the BD program being processed by the program processor (302), and is not generally determined.

  As described with reference to FIG. 6, the image data and the video data are recorded on the image plane (314) and the video plane (315) after being decoded, and are synthesized and output by the synthesis processing unit (316).

  The management information (scenario, AV management information) read from the BD disc (201) is recorded in the management information recording memory (304), but the scenario information (“BD.INFO” and “XXX.PL”) is stored in the management information recording memory (304). It is read and processed by the scenario processor (305). The AV management information (“YYY.VOBI”) is read and processed by the presentation controller (306).

  The scenario processor (305) analyzes the information of the playlist, and instructs the presentation controller (306) the VOB referenced by the playlist and the playback position thereof. The presentation controller (306) manages the management information of the target VOB. ("YYY.VOBI") is analyzed, and an instruction is issued to the drive controller (317) to read out the target VOB.

  The drive controller (317) moves the optical pickup according to the instruction of the presentation controller (306), and reads the target AV data. The read AV data is recorded in the image memory (308) or the track buffer (309) as described above.

  The scenario processor (305) monitors the time of the clock (307) and throws an event to the program processor (302) at the timing set in the management information.

  The BD program (“BD.PROG” or “XXX.PROG”) recorded in the program recording memory (301) is executed by the program processor 302. The program processor (302) processes the BD program when an event is sent from the scenario processor (305) or when an event is sent from the UOP manager (303). The UOP manager (303) generates an event in the program processor (302) when a request is sent from the user by a remote control key.

(Application space)
FIG. 8 is a diagram showing an application space of the BD-ROM.

  In the application space of the BD-ROM, a play list (PlayList) is one reproduction unit. The playlist has a static scenario composed of a playback sequence of a cell (Cell) and a dynamic scenario described by a program. Unless there is a dynamic scenario by the program, the playlist only reproduces the individual cells in order, and the reproduction of the playlist ends when the reproduction of all the cells is completed. On the other hand, the program can dynamically change the playback target depending on the playback description beyond the playlist, the user selection, or the player status. A typical example is a menu. In the case of a BD-ROM, the menu is to dynamically select a scenario to be played by the user's selection, that is, a playlist.

  The program here is an event handler executed by a time event or a user event.

  The time event is an event generated based on time information embedded in the playlist. The event sent from the scenario processor (305) described in FIG. 7 to the program processor (302) corresponds to this. When a time event is issued, the program processor (302) executes an event handler associated with the ID. As described above, the program to be executed can instruct playback of another playlist. In this case, playback of the currently played playlist is stopped and playback of the specified playlist is started. And transition.

  A user event is an event generated by a user's remote control key operation. User events are roughly divided into two types. The first is a menu selection event generated by operating a cursor key ("Up", "Down", "Left", "Right" key) or a "Determination" key. The event handler corresponding to the event selected from the menu is valid only for a limited period in the playlist (the validity period of each event handler is set as playlist information). A valid event handler is searched when the “down”, “left”, “right” key, or “decision” key is pressed. If there is a valid event handler, the event handler is executed. In other cases, menu selection events will be ignored.

  The second user event is a menu call event generated by operating the “menu” key. When a menu call event is generated, a global event handler is called. A global event handler does not depend on a playlist and is always an effective event handler. By using this function, it is possible to implement a DVD menu call (calling a voice, subtitle menu, etc. during title playback, and executing title playback from the point where it was interrupted after changing the voice or subtitle).

A cell (Cell), which is a unit constituting a static scenario in a playlist, refers to all or part of a playback section of a VOB (MPEG stream). The cell has a playback section in the VOB as start and end time information. The VOB management information (VOBI) paired with each VOB has a time map (Time Map or TM) inside, and the playback and end times of the VOB described above are indicated in the VOB ( That is, it is possible to derive the read start address and end address in the target file “YYY.VOB”). Details of the time map will be described later.
(Details of VOB)
FIG. 9 is a configuration diagram of an MPEG stream (VOB) used in this embodiment. As shown in FIG. 9, a VOB is composed of a plurality of VOBUs (Video Object Units). The VOBU is one playback unit as a multiplexed stream including audio data on the basis of GOP (Group Of Pictures) referred to as an MPEG video stream. A VOBU has a duration of 0.4 to 1.0 seconds, and usually has a playback time of 0.5 seconds. This is because the structure of MPEG GOP is usually derived by 15 frames / second (in the case of NTSC).

  The VOBU has a video pack (V_PCK) and an audio pack (A_PCK) therein. Each pack is composed of one sector, in the case of this embodiment, in units of 2 kB.

  FIG. 10 is a diagram showing the configuration of the pack.

  As shown in FIG. 10, elementary data such as video data and audio data are sequentially entered from the head into a data storage area of a packet called a payload. A packet header is attached to the payload to form one packet. In the packet header, an ID for identifying which stream, video, or audio the data stored in the payload is, and if there are multiple streams of video or audio, which stream is the data (Stream_id) and time stamps DTS and PTS which are decoding time and display time information of the payload are recorded. PTS / DTS is not necessarily recorded in all packet headers, but rules for recording in MPEG are defined. Details of the rules are described in the MPEG system (ISO / IEC13818-1) standard, and therefore will be omitted.

  The packet is further provided with a header (pack header) to form a pack. In the pack header, a time stamp SCR (System Clock Reference) indicating when the pack passes the demultiplexer and is input to the decoder buffer of each elementary stream is recorded.

(VOB interleaved recording)
Next, interleaved recording of a VOB file will be described with reference to FIGS.

  The upper part of FIG. 11 is a part of the player configuration diagram described above. As shown in the figure, the data on the BD disc is input to the track buffer if it is a VOB or MPEG stream through the optical pickup, and is input to the image memory if it is PNG or image data.

  The track buffer is a FIFO, and the input VOB data is sent to the demultiplexer in the input order. At this time, each pack is extracted from the track buffer in accordance with the SCR described above, and the data is sent to the video processor or sound processor via the demultiplexer. On the other hand, in the case of image data, the presentation controller instructs which image to draw. The image data used for drawing is deleted from the image memory at the same time in the case of image data for subtitles, but remains in the image memory in the case of image data for menus. This is because menu drawing may depend on user operations, and the same image may be drawn multiple times.

  The lower part of FIG. 11 is a diagram showing interleaved recording of a VOB file and a PNG file on a BD disc. In general, in the case of a ROM such as a CD-ROM or a DVD-ROM, AV data serving as a series of continuous reproduction units is continuously recorded. As long as continuous recording is performed, the drive only needs to read the data sequentially and send it to the player side. However, if the continuous data is divided and discretely arranged on the disc, seek is performed between individual continuous sections. This is because an operation is entered, and during this time, reading of data is stopped, and supply of data may be stopped. Similarly, in the case of a BD-ROM, it is desirable that the VOB file can be recorded in a continuous area. However, there is data that is reproduced in synchronization with video data recorded in the VOB, such as subtitle data. Similar to the VOB file, it is necessary to read the caption data from the BD disc by some method.

  As one method of reading subtitle data, there is a method of reading subtitle image data (PNG file) all at once before the start of VOB reproduction. However, in this case, a large amount of memory used for temporary recording is required, which is unrealistic.

  Therefore, in this embodiment, a method is used in which the VOB file is divided into several blocks and interleaved with image data. The lower part of FIG. 11 illustrates the interleave recording. By appropriately interleaving the VOB file and the image data, it becomes possible to store the image data in the image memory at a necessary timing without the large amount of temporary recording memory as described above. However, when reading the image data, the reading of the VOB data is naturally stopped.

  FIG. 12 is a diagram for explaining a VOB data continuous supply model using a track buffer that solves this problem.

  As described above, VOB data is temporarily stored in the track buffer. If a difference is provided between the data input rate to the track buffer and the data output rate from the track buffer, as long as data is continuously read from the BD disc, the data storage amount of the track buffer increases. Here, the input rate to the track buffer is Va, and the output rate from the track buffer is Vb. As shown in the upper part of FIG. 12, it is assumed that a continuous recording area of VOB continues from “a1” to “a2” of logical addresses. It is assumed that between “a2” and “a3” is an interval in which image data is recorded and VOB data cannot be read.

  The lower part of FIG. 12 shows the inside of the track buffer. The horizontal axis indicates time, and the vertical axis indicates the amount of data stored in the track buffer. Time “t1” indicates the time when reading of “a1”, which is the starting point of one continuous recording area of the VOB, is started. After this time, data is accumulated in the track buffer at the rate Va-Vb. Needless to say, this rate is the difference between the input and output rates of the track buffer. The time “t2” is the time when the data “a2”, which is the end point of one continuous recording area, is read. That is, the amount of data in the track buffer increases from time “t1” to “t2” at the rate Va−Vb, and the data accumulation amount at time “t2” can be obtained by the following equation. .

B (t2) = (Va−Vb) × (t2−t1) (Formula 1)
After this, since the image data continues until the address “a3” on the BD disc, the input to the track buffer becomes 0, and the data amount in the track buffer decreases at the output rate “−Vb”. Become. This is up to the read position “a3” and “t3” in time.

  What is important here is that if the amount of data stored in the track buffer before time “t3” becomes zero, there is no VOB data to be supplied to the decoder, and there is a possibility that VOB reproduction stops. There is. However, if data remains in the track buffer at time “t3”, this means that VOB playback can be continued without stopping.

  This condition can be expressed by the following equation.

B (t2) ≧ −Vb × (t3−t2) (Formula 2)
That is, it is only necessary to determine the arrangement of the image data so as to satisfy Expression 2.

(Navigation data structure)
The structure of navigation data (BD management information) in the BD-ROM will be described with reference to FIGS. FIG. 13 shows the internal structure of the VOB management information file (“YYY.VOBI”).

  The VOB management information includes stream attribute information (Attribute) and time map (TMAP) of the VOB. Each stream attribute has a video attribute (Video) and an audio attribute (Audio # 0 to Audio # m). Particularly in the case of an audio stream, since a VOB can have a plurality of audio streams at the same time, the presence or absence of a data field is indicated by the number of audio streams (Number).

  The following are the fields that the video attribute (Video) has and the values that each can have.

Compression method (Coding):
MPEG1
MPEG2
MPEG4
Resolution:
1920x1080
1280x720
720x480
720x565
Aspect ratio (Aspect)
4: 3
16: 9
Frame rate
60
59.94
50
30
29.97
25
24

  The following are the fields that the audio attribute (Audio) has and the values that each can have.

Compression method (Coding):
AC3
MPEG1
MPEG2
LPCM
Number of channels (Ch):
1-8
Language attribute:

  The time map (TMAP) is a table having information for each VOBU, and has the number of VOBUs (Number) possessed by the VOB and each VOBU information (VOBU # 1 to VOBU # n). Each VOBU information has a playback time length (Duration) of the VOBU and a data size (Size) of the VOBU.

  FIG. 14 is a diagram for explaining the details of the VOBU information.

  As is widely known, an MPEG stream has two aspects, a temporal aspect and a data size aspect. For example, since AC3, which is a voice compression standard, performs compression at a fixed bit rate, the relationship between time and address can be obtained by a linear expression. However, in the case of MPEG video data, each frame has a fixed display time, for example, in the case of NTSC, one frame has a display time of 1 / 29.97 seconds, but the data size after compression of each frame is picture size. The data size varies greatly depending on the characteristics and the picture type used for compression, so-called I / P / B picture. Therefore, in the case of MPEG video, the relationship between time and address cannot be expressed in a general form.

  As a matter of course, an MPEG system stream in which MPEG video data is multiplexed, that is, VOB, cannot express time and data in a general form. Instead, the time map (TMAP) links the relationship between time and address in the VOB. As shown in FIG. 14, a table having a number of frames in a VOBU and the number of packs in a VOBU as entries for each VOBU is a time map (TMAP).

  The usage of the time map (TMAP) will be described with reference to FIG.

  When time information is given as shown in FIG. 15, first, a search is performed as to which VOBU the time belongs to. This is done by adding the number of frames for each VOBU of the time submap, and the VOBU whose sum of frames exceeds or coincides with the time (converted to the number of frames) becomes the VOBU. Next, the size for each VOBU of the time map is added to the VOBU immediately before the VOBU, and the value is the leading address of the pack to be read in order to reproduce the frame including the given time.

  Next, the internal structure of the playlist information (“XXX.PL”) will be described with reference to FIG.

  The playlist information includes a cell list (CellList) and an event list (EventList).

  The cell list (CellList) is a reproduction cell sequence in the playlist, and the cells are reproduced in the description order of the list. The contents of the cell list (CellList) are the number of cells (Number) and cell information (Cell # 1 to Cell # n).

  The cell information (Cell #) has a VOB file name (VOBName), a valid section start time (In) and a valid section end time (Out) in the VOB, and a caption table (SubtitleTable). The valid section start time (In) and valid section end time (Out) are each expressed by a frame number in the VOB, and the address of VOB data necessary for reproduction is obtained by using the time map (TMAP) described above. I can do things.

  The caption table (SubtitleTable) is a table having caption information that is reproduced in synchronization with the VOB. Subtitles can have multiple languages as well as audio, and the first information of the subtitle table (SubtitleTable) consists of the number of languages (Number) followed by tables for each language (Language # 1 to Language # k). Yes.

  A table (Language #) for each language includes language information (Language), the number of subtitle information (Number) of subtitles displayed individually, and subtitle information of subtitles (Speech # 1 to Speech # j) displayed individually. The caption information (Speech #) is composed of the corresponding image data file name (Name), caption display start time (In) and caption display end time (Out), and caption display position (Position). .

  The event list (EventList) is a table that defines the events listed in the play list. The event list is made up of individual events (Event # 1 to Event # m) following the number of events (Number), and each event (Event #) includes an event type (Type) and an event ID (ID). The event generation time (Time) and the validity period (Duration) are included.

  FIG. 17 is an event handler table (“XXX.PROG”) having event handlers (time events and user events for menu selection) for each playlist.

  The event handler table has a defined number of event handlers / programs (Number) and individual event handlers / programs (Program # 1 to Program # n). The description in each event handler / program (Program #) has the event handler ID (ID) paired with the event handler start definition (<event_handler> tag) and the above-mentioned event ID. It is described between parentheses “{” and “}” following the Function.

  Next, the internal structure of information relating to the entire BD disc (“BD. INFO”) will be described with reference to FIG.

  The entire BD disc information includes a title list (TitleList) and an event table for global events (EventTable).

  The title list (TitleList) is composed of the number of titles (Number) in the disc and the following pieces of title information (Title # 1 to Title # n). Each piece of title information (Title) includes a playlist table (PLTable) included in the title and a chapter list (ChapterList) in the title. The playlist table (PLTable) has the number of playlists in the title (Number) and the playlist name (Name), that is, the playlist file name.

  The chapter list (ChapterList) is composed of the number of chapters (Number) included in the title and individual chapter information (Chapter # 1 to Chapter # n), and the chapter information (Chapter #) is a table of cells included in the chapter (Chapter #). The cell table (CellTable) includes the number of cells (Number) and individual cell entry information (CellEntry # 1 to CellEntry # k). Cell entry information (CellEntry #) is described by the name of the playlist including the cell and the cell number in the playlist.

  The event list (EventList) includes the number of global events (Number) and information on individual global events. It should be noted that the global event defined first is called a first event (FirstEvent), and is the first event called when a BD disc is inserted into a player. The event information for global events has only an event type (Type) and an event ID (ID).

  FIG. 19 is a global event handler program table (“BD.PROG”). This table has the same contents as the event handler table described in FIG.

(Event generation mechanism)
The event generation mechanism will be described with reference to FIGS.

  FIG. 20 is an example of a time event.

  As described above, a time event is defined by an event list (EventList) of playlist information (“XXX.PL”). When an event defined as a time event, that is, when the event type (Type) is “TimeEvent”, the time event having the ID “Ex1” is transferred from the scenario processor to the program processor when the event generation time (“t1”) is reached. Against. The program processor searches for an event handler having the event ID “Ex1” and executes the target event handler. For example, in this embodiment, two button images can be drawn.

  FIG. 21 shows an example of a user event for performing a menu operation.

  As described above, the user event for performing the menu operation is also defined in the event list (EventList) of the playlist information (“XXX.PL”). When an event defined as a user event, ie, an event type (Type) is “UserEvent”, the user event becomes ready when the event generation time (“t1”) is reached. At this time, the event itself has not yet been generated. The event is in a ready state for the period described by the valid standard information (Duration).

  As shown in FIG. 21, when the user presses the “up”, “down”, “left”, “right” key or “decision” key of the remote control key, a UOP event is first generated by the UOP manager and raised to the program processor. The program processor sends a UOP event to the scenario processor, and the scenario processor searches whether there is a valid user event at the time when the UOP event is received. Generate and lift to the program processor. The program processor searches for an event handler having the event ID “Ev1” and executes the target event handler. For example, in the case of the present embodiment, reproduction of playlist # 2 is started.

  The generated user event does not include information on which remote control key is pressed by the user. Information on the selected remote control key is transmitted to the program processor by a UOP event, and is recorded and held in the register SPRM (8) of the virtual player. The event handler program can check the value of this register and execute branch processing.

  FIG. 22 shows an example of a global event.

  As described above, a global event is defined by an event list (EventList) of information (“BD. INFO”) relating to the entire BD disc. When an event defined as a global event, that is, an event type (Type) is “GlobalEvent”, an event is generated only when a user operates a remote control key.

  When the user presses “Menu”, a UOP event is first generated by the UOP manager and raised to the program processor. The program processor sends a UOP event to the scenario processor, and the scenario processor generates a corresponding global event and sends it to the program processor. The program processor searches for an event handler having the event ID “menu” and executes the target event handler. For example, in the case of the present embodiment, reproduction of playlist # 3 is started.

  In this embodiment, it is simply called a “menu” key, but there may be a plurality of menu keys as in a DVD. It is possible to cope by defining IDs corresponding to the respective menu keys.

(Virtual player machine)
The functional configuration of the program processor will be described with reference to FIG.

  The program processor is a processing module having a virtual player machine inside. The virtual player machine is a functional model defined as a BD-ROM and does not depend on the implementation of each BD-ROM player. That is, it is guaranteed that the same function can be executed in any BD-ROM player.

  The virtual player machine has two functions. Programming functions and player variables (registers). The programming function defines two functions described below as BD-ROM specific functions based on Java (registered trademark) Script.

Link function: Stops the current playback and starts playback from the specified playlist, cell, and time Link (PL #, Cell #, time)
PL #: Playlist name Cell #: Cell number time: Playback start time in the cell PNG drawing function: Draws specified PNG data on the image plane Draw (File, X, Y)
File: PNG file name X: X coordinate position Y: Y coordinate position Image plane clear function: Clear specified area of image plane Clear (X, Y, W, H)
X: X-coordinate position Y: Y-coordinate position W: X-direction width H: Y-direction width Player variables include a system parameter (SPRM) indicating the state of the player and a general parameter (GPRM) that can be used for general purposes.

  FIG. 24 is a list of system parameters (SPRM).

SPRM (0): Language code SPRM (1): Audio stream number SPRM (2): Subtitle stream number SPRM (3): Angle number SPRM (4): Title number SPRM (5): Chapter number SPRM (6): Program Number SPRM (7): Cell number SPRM (8): Selection key information SPRM (9): Navigation timer SPRM (10): Playback time information SPRM (11): Karaoke mixing mode SPRM (12): Parental country information SPRM (13): Parental level SPRM (14): Player set value (video)
SPRM (15): Player setting value (audio)
SPRM (16): Audio stream language code SPRM (17): Audio stream language code (extended)
SPRM (18): Language code for subtitle stream SPRM (19): Language code for subtitle stream (extended)
SPRM (20): Player region code SPRM (21): Reserve SPRM (22): Reserve SPRM (23): Playback state SPRM (24): Reserve SPRM (25): Reserve SPRM (26): Reserve SPRM (27): Spare SPRM (28): Spare SPRM (29): Spare SPRM (30): Spare SPRM (31): Spare

  In this embodiment, the programming function of the virtual player is based on Java (registered trademark) Script. However, instead of Java (registered trademark) Script, B-Shell used in UNIX (registered trademark) OS, Other programming functions such as Perl Script may be used. In other words, the present invention is not limited to Java (registered trademark) Script.

(Program example)
25 and 26 are examples of programs in the event handler.

  FIG. 25 shows an example of a menu having two selection buttons.

  The program on the left side of FIG. 25 is executed using the time event at the head of the cell (PlayList # 1. Cell # 1). Here, “1” is first set to GPRM (0), one of the general parameters. GPRM (0) is used to identify the selected button in the program. In the initial state, the initial value is that the button 1 arranged on the left side is selected.

  Next, PNG drawing is performed for each of the buttons 1 and 2 by using a drawing function Draw. The button 1 draws the PNG image “1black.png” with the coordinates (10, 200) as the starting point (left end). The button 2 draws a PNG image “2white.png” with the coordinates (330, 200) as a starting point (left end).

  At the end of this cell, the program on the right side of FIG. 25 is executed using a time event. Here, it is specified to play again from the beginning of the cell using the Link function.

  FIG. 26 is an example of an event handler for a user event for menu selection.

  When the remote control key of “Left” key, “Right” key, or “Determination” key is pressed, a corresponding program is written in the event handler. When the user presses the remote control key, as described in FIG. 21, a user event is generated and the event handler of FIG. 26 is activated. In this event handler, branch processing is performed using the value of GPRM (0) identifying the selection button and SPRM (8) identifying the selected remote control key.

Condition 1) When button 1 is selected and the selection key is the “right” key GPRM (0) is reset to 2, and the button in the selected state is changed to right button 2.

    Rewrite the images of Button 1 and Button 2, respectively.

Condition 2) When the selection key is “OK” and button 1 is selected, playback of playlist # 2 is started. Condition 3) When the selection key is “OK”. When button 2 is selected, playback of playlist # 3 is started. Execution processing is performed as described above.

(Player processing flow)
Next, the processing flow in the player will be described with reference to FIGS.

  FIG. 27 is a basic processing flow up to AV playback.

  When the BD disc is inserted (S101), the BD-ROM player is set to BD. Reading and analysis of INFO file (S102), BD. PROG reading (S103) is executed. BD. INFO and BD. Both PROGs are temporarily stored in the management information recording memory and analyzed by the scenario processor.

  Subsequently, the scenario processor is BD. The first event is generated according to the first event (FirstEvent) information in the INFO file (S104). The generated first event is received by the program processor, and an event handler corresponding to the event is executed (S105).

  It is expected that playlist information to be reproduced first is recorded in the event handler corresponding to the first event. If play list reproduction is not instructed, the player does not reproduce anything and simply waits for acceptance of a user event. In this case, it continues to wait for accepting a user event (S201). When the BD-ROM player receives a remote control operation from the user, the UOP manager raises a UOP event to the program manager (S202).

  The program manager determines whether the UOP event is caused by a menu key (S203). If the UOP event is a menu key, the program manager sends a UOP event to the scenario processor, and the scenario processor generates a user event (S204). The program processor executes an event handler corresponding to the generated user event (S205).

  FIG. 28 is a processing flow from the start of PL playback to the start of VOB playback.

  As described above, play list reproduction is started by the first event handler or the global event handler (S301). The scenario processor reads and analyzes playlist information “XXX.PL” as information necessary for playback of the playlist to be played back (S302), and reads program information “XXX.PROG” corresponding to the playlist (S303). ). Subsequently, the scenario processor starts cell reproduction based on the cell information registered in the playlist (S304). Cell playback means that a request is sent from the scenario processor to the presentation controller, and the presentation controller starts AV playback (S305).

  When the start of AV playback (S401) is started, the presentation controller reads and analyzes the VOB information file (XXX.VOBI) corresponding to the cell to be played back (S402). The presentation controller uses the time map to specify the VOBU to start playback and its address, and instructs the drive controller to specify the read address. The drive controller reads the target VOB data (S403), and the VOB data is sent to the decoder. Playback is started (S404). The VOB playback is continued until the playback section of the VOB ends (S405), and when it ends, the process proceeds to the next cell playback S304. Next, if there is no cell, playback stops (S406).

  FIG. 29 is an event processing flow after the start of AV playback.

  The BD-ROM player is an event-driven player model. When playback of the playlist is started, event processing processes for the time event system, the user event system, and the caption display system are started, and the event processing is executed in parallel.

  The S500 system processing is a time event system processing flow.

  After the play list reproduction is started (S501), the scenario processor confirms whether or not the time event occurrence time is reached (S503) through a step (S502) for confirming whether the play list reproduction is completed. If the time event occurrence time is reached, the scenario processor generates a time event (S504), and the program processor receives the time event and executes the event handler (S505).

  If the time event occurrence time is not reached in step S503, or after the event handler execution process in step S504, the process returns to step S502 again, and the above-described process is repeated. Also, when it is confirmed in step S502 that the play list reproduction has been completed, the time event processing is forcibly terminated.

  The S600 system processing is a user event system processing flow.

  After the play list reproduction is started (S601), the play list reproduction end confirmation step (S602) is performed, and then the process proceeds to the UOP reception confirmation step (S603). When the UOP is accepted, the UOP manager generates a UOP event (S604), and the program processor that receives the UOP event checks whether the UOP event is a menu call (S605). The program processor causes the scenario processor to generate an event (S607), and the program processor executes the event handler (S608).

  If it is determined in step S605 that the UOP event is not a menu call, it indicates that the UOP event is an event by a cursor key or a “decision” key. In this case, the scenario processor determines whether the current time is within the user event valid period (S606), and if it is within the valid period, the scenario processor generates a user event (S607), and the program processor is targeted. The event handler is executed (S608).

  If no UOP is accepted in step S603, if the current time is not in the user event valid period in step S606, or after the event handler execution process in step S608, the process returns to step S602 again to repeat the above-described process. Further, when it is confirmed in step S602 that the play list reproduction has ended, the user event processing is forcibly ended.

  FIG. 30 is a flowchart of caption processing.

  After the play list reproduction is started (S701), the play list reproduction end confirmation step (S702) is followed by the subtitle drawing start time confirmation step (S703). In the case of the caption rendering start time, the scenario processor instructs the presentation controller to render captions, and the presentation controller instructs the image processor to render captions (S704). If it is determined in step S703 that it is not the caption drawing start time, it is confirmed whether it is the caption display end time (S705). If it is determined that the subtitle display end time is reached, the presentation controller instructs the image processor to delete the subtitle and deletes the drawn subtitle from the image plane (S706).

  After the caption drawing step S704 ends, after the caption erasure step S706 ends, or when it is determined that the time is not the same at the caption display end time confirmation step S705, the process returns to step S702 and the above-described processing is repeated. Also, when it is confirmed in step S702 that the playlist reproduction has been completed, the caption display processing is forcibly terminated.

(Example 2)
Next, a second embodiment of the present invention will be described.

  The second embodiment relates to the introduction of an XML / XHTML / HTML-based screen configuration environment and a programming environment using events and scripts in order to realize richer interactivity in the BD-ROM. . Basically, the contents are based on the first embodiment, and the description will be focused on the expansion or different portions. In this embodiment, HTML is used as a language for defining the screen configuration.

(Content control using HTML files)
FIG. 31 shows how the module configuration, control flow, events, etc. related to scenario control using HTML and script are transmitted.

  The user event processing unit is a module that receives a remote control signal and assigns an event to the next module. Events related to playback control such as playback / stop / fast forward / rewind / skip / angle change / audio switching / subtitle switching are sent to the AV playback control unit. Events such as button focus movement (up / down / left / right keys) and determination are sent to the HTML processing unit. Events for title selection and menu call related to title switching are sent to the title control unit. The Index Table is a file listing the titles in the disc, and is obtained by cutting out the Title List portion of FIG. 18 into one.

  The title control unit is a module that performs title switching according to the Index Table when title switching is requested. When the title is defined in HTML, control is performed so that the HTML file associated with the title is read into the HTML processing unit.

  The HTML processing unit is a module that reads an HTML file, configures a screen according to style definition information, and executes related scripts according to events. As a result of executing the script, if AV playback is necessary, the AV playback control unit is controlled to start playback, and if title switching is necessary, the title control unit is controlled.

  The AV playback control unit plays back an AV stream in accordance with an event or an instruction, generates an event when the state of the AV playback control unit changes or the playback position of the AV stream reaches a specific position, and generates an HTML processing unit. Notify

  The event notifying that the state of the player has changed is a playback instruction from the user. When the user event processing unit notifies the AV playback control unit of the playback start request event, the AV playback control unit starts playback. At this time, the event is such that the AV playback control unit notifies the change from the stopped state to the playback state.

  The event notifying the playback position is reached when the end of the AV stream is reached, when the cell boundary is reached, or when there is data indicating a point in time of the AV stream called a mark. It is an event to notify that.

  FIG. 32 shows the operation when a certain title is selected.

  When a certain title defined in the Index Table is selected, an HTML file associated with the title is called. In the HTML file, a script for performing reproduction control and the like is also described. In the example in the figure, the script file is indirectly referenced, but can be described directly in the HTML file. Further, for the sake of explanation, it is described as HTML, but it may be in a format using a unique tag or the like as long as it conforms to the XML format.

  In the “onLoad” attribute described in the HTML file in the figure, a script to be executed when the file is read is defined. In this example, when an HTML file is read, a script “playTitle1” is called, and the script itself is described in the script file.

  In addition, by using an <event> tag, a mechanism for executing a script in response to an event notified from a user event processing unit or an AV playback control unit is also provided. In this example, when the “EndOfStream” event occurs, a script “jumpTitle2” is called. The “EndOfStream” event is an event generated by the AV playback control unit when, for example, AV playback reaches the end of the file.

  Also, an event processing function (for example, a BDIMoviePlaybackEventHandler () function) whose function name is reserved in advance is described in a script tag of an HTML document or a script file, so that a user event processing unit or AV It is also possible to execute a script in response to an event notified from the playback control unit.

  FIG. 33 shows an example in which screen generation is added to the previous example. For example, HTML is called from the Index Table as described above, and the HTML is written when information for generating a menu screen or the like is written. A style sheet such as CSS may be used as the screen configuration style.

  In this example, two buttons are arranged on the screen. When each button is pressed, the corresponding script is executed. When a certain button is selected, a script defined in the “onClick” attribute is executed. When the left button associated with the PNG image file written as TitleA is selected, the “playA” script is executed and jumps to title 1. Similarly, when the Title B button is selected, after a certain AV stream is reproduced, the program jumps to title 2.

  By using the mechanism described so far, it is possible to provide a mechanism in which a menu screen is displayed using an HTML file, and playback of content is started when selection of a certain button is selected.

  Further, by adding a script part and an API executed by the script, more complicated functions such as an application such as an Internet connection or a download service can be executed.

(Resource management)
When the HTML file forms a screen such as a menu screen, a data file such as a PNG image file is referred to. The more sophisticated the menu, the more complicated the graphics to display and the larger the image data size for displaying it.

  An HTML file can be created so that the screen is switched by a user operation. This is the case when selecting an item in the menu screen causes a submenu to appear. In such a case, image data that was not displayed at the first moment when the menu screen is displayed may be required later.

  However, if a video is displayed in the background of the menu screen, that is, if an AV stream is being played back, if you try to read the image data after it is needed, you will seek to the position where the file is on the disc. And then reading it back to the original position, there is a possibility that the playback of the AV stream is temporarily interrupted. A sufficient amount of buffer is loaded, and this can be avoided if the AV stream is pre-read in advance, but the image has high resolution and high image quality, and a high bit rate is required. Therefore, a considerably large-capacity buffer must be prepared, which leads to an increase in cost and is not realistic.

  In addition, with a medium such as a hard disk that has a short seek time and a high reading speed, even a small amount of buffer can be used to read other data without interrupting AV. With this drive, seeking takes time and reading speed is not so fast, so further technical advancement is required for realization.

  Therefore, it is desirable to use a model in which data other than AV is not read once AV playback is started.

  FIG. 34 shows the data life cycle in such a case.

  Before AV playback starts, data files such as HTML files and script files that are necessary for displaying the screen, such as PNG image files referenced from those files, are preloaded on the buffer. .

  Once AV playback is started, the data is not read to the disc.

  Note that when AV playback may be stopped, there is no need to consider them.

  Also, if it is necessary to distinguish between the case where AV playback is not desired to stop and the case where it may be stopped depending on the content, an identifier for distinguishing these two patterns may be prepared in the management information.

  When the HTML processing unit needs data, it is read from the buffer onto the work memory of the HTML processing unit and used for screen display. When the screen is not displayed, the unnecessary data is released from the work memory, and the next necessary data is read from the buffer.

  This work memory may be shared with the buffer.

  Save the memory in the buffer until you no longer need it, and free it when you no longer need it.

(Data life cycle)
As described above, if the timing for reading data into the buffer and the timing for releasing the data from the buffer can be clearly determined, the management of the data life cycle becomes clear and easy to manage.

  If data management becomes easier, it becomes easier for the content creator to determine a content configuration that can be operated by any player, and content creation becomes easier.

  The start timing and end timing of the data life cycle are preferably the timing at which AV playback is stopped, or the timing at which playback is stopped temporarily or even when continuous playback is not required.

  Such timing includes an AV stream switching point, a screen switching point constituted by an HTML file, a title switching timing, and the like, and may be other points as long as the above conditions are satisfied.

  Using the structure described so far, the timing of title switching can be explicitly referred to as static data in the Index Table, and can be easily controlled from the player. Therefore, the data life cycle starts when a certain title starts, and ends when a certain title ends.

  In other words, when a title starts, all the data needed to play that title is preloaded into the buffer and released from the buffer when the title ends, for example when jumping to another title To do.

  FIG. 35 is a timing chart showing the flow of control between each module, the flow of data, and the data life cycle corresponding thereto.

  By defining such a life cycle and buffer size, you can quantitatively determine how much image data can be used when creating a title, and what application can be executed. It becomes very easy to make.

  The release of the buffer may be forcibly performed from the title control unit or a higher-order module, or may be performed by the HTML processing unit.

  When the title is switched during the application execution by the user operation, the title control unit stops the script that is currently being executed and instructs the HTML processing unit to release the buffer. Also, when the title is switched, an instruction is given to read a file related to the next title into the buffer.

(Data reading guarantee)
As described above, it is necessary to preload a file other than the AV stream in the buffer before starting the reproduction of the AV stream. At that time, it takes time to analyze the HTML file and list the necessary files.

  Therefore, as shown in FIG. 36A, a file list in which the files necessary for each title are listed is created for each title, and when a title is selected, all the files listed in the title list are buffered. Just load it into

  Also, if there are many files, it will take time to read each file, so it will cause unnecessary seeks by placing the listed files in one place on the disk. It is also possible to read all necessary files without any problems.

  Alternatively, as shown in FIG. 36B, the files may be grouped together in a ZIP file or the like for each directory structure, and after reading into the buffer, the files may be expanded in the buffer to configure the directory structure or the like. . The file may not be a ZIP file as long as the files can be combined into one and the directory structure can be maintained. Also, it does not have to be a compressed file.

  Alternatively, as shown in FIG. 37, each file of the logical file tree 400 having a directory structure in the production stage or the like is placed flat in a Content Archive File 401 (hereinafter referred to as a CAR file), and is HTTP entity format. Make multi-parts. Furthermore, the directory structure information of the logical file tree 400 may be stored in the Resource List File 402, and this Resource List File 402 may be arranged in the CAR file 401.

(Effect of archive configuration using ZIP file and CAR file 401)
The improvement of the writing efficiency / reading efficiency to the disc that can be realized by adopting the configuration of FIG. 36B and the configuration of FIG. 37 will be described.

  If an HTML file or an image file is individually arranged on the disk, an area (fragmentation) where nothing is written is generated in a sector on the disk where only information relating to one file can be arranged, and the writing efficiency is lowered.

  In reading, the number of HTML files and image files is read, and each time a read is performed, a disc SEEK process occurs, and it takes a long time to read the related file, and the start of the title is slow. Become.

  On the other hand, when the ZIP file or the CAR file 401 is used, the HTML file used for screen presentation, the image file group referred to by the HTML file, and the HTML to be presented next after the document transitions from the HTML file. Since files (contents) related to a series of operations such as files are archived, the total size and number of fragmentation are reduced, the writing efficiency to the disk is increased, and the files are archived in one file. Therefore, only one read process occurs, the SEEK number is suppressed, and the disk can be read quickly.

  In addition, by using such a mechanism, it is possible to provide a mechanism that makes it easier for players to control errors by making it easier to understand mistakes during authoring by managing resources easily for each title and making data reading more efficient It becomes.

(Startup process flow in Resource List File format)
Hereinafter, a more detailed implementation will be described with respect to a mechanism in which archive files such as ZIP files and CAR files described with reference to FIGS. 36 and 37 are applied.

  FIG. 39 shows an example in which a Resource List File using XML is described. The Resource List File is described for each title, and describes the application that is executed when each title is played back.

  In the example described above with reference to FIG. 32, the HTML file is associated with the title defined by the Index Table, but the Resource List File is associated with each title defined by the Index Table, and the Index Table is associated with the Index Table. When a title that is defined is selected, the Resource List File associated with that title is first invoked.

  In the example described above with reference to FIG. 32, the HTML file is associated with the title defined in the Index Table, but the CAR file is associated with each title defined in the Index Table. Furthermore, a Resource List File is stored in the CAR file, and when a certain title defined in the Index Table is selected, the CAR file associated with the title is first called and associated with the CAR file. The Resource List File is then called.

  Note that the S800 system in FIG. 38 shows a flow from the selection of Title to the presentation of the screen by HTML.

  When a title defined in the Index Table is selected (S801), the CAR file associated with the title is called and stored in the buffer for the CAR file (S802). Next, the Resource List File stored in the CAR file is cut out, the Resource List File is analyzed, and the HTML file to be activated is specified (S803). The Resource List File can be quickly cut out by placing the Resource List File at the beginning of the multipart CAR file.

  Next, the HTML file stored in the CAR file is cut out using the Offset value of the HTML file to be activated described in the Resource List File, and the HTML file is analyzed (S804). If Offset is not described, a logical path is constructed by adding the directory name and file name described in the directory structure, and the resource header of each file archived in the ZIP file using this logical path. The HTML file can be identified and cut out by comparing with the resource path described in (1).

If the HTML file refers to a data file such as an image file, the Resource List File is further analyzed, the corresponding data file is cut out, layout processing and script processing are performed, and a screen is presented (S805). )
Furthermore, a processing flow from when the screen is presented to when the document transition processing is generated by a user operation or script processing until the next presentation screen is presented will be described using the S900 system of FIG.

When a document transition occurs due to a user operation or script processing (S901), the specified URI is analyzed to determine whether it belongs to the same title, and if it belongs to another title, the Index Table is analyzed to determine another title. Is started, and the process proceeds to (S801) (S902). If it belongs to the same title, the Resource List File in the pre-loaded CAR file is analyzed to identify the designated HTML file (S903). Next, the HTML file stored in the CAR file is cut out using the Offset value described in the Resource List File, and the HTML file is analyzed (S904). When a data file such as an image file is referred to, the Resource List File is further analyzed, the corresponding data file is cut out, layout processing and script processing are performed, and a screen is presented (S905).
(Structure of Resource List File in XML format)
FIG. 39 shows a description example of the Resource List File in the XML format. An XML-format Resource List File is composed of an XML declaration and four elements: <application>, <entry>, <toppage>, and <linkfile>.

  An application name is described in the name attribute of the <application> element.

  For HTML (hereinafter referred to as Toppage) that needs to be read and analyzed first when executing an application, the file name is described as the src attribute of the <toppage> element.

  The file name of each file constituting the application except Toppage is listed in the URI format as the src attribute of the <linkfile> element.

  In addition, a file group (including Toppage) constituting these applications is recorded on the BD-ROM as an archive file as a whole, and the file name of the archive file is <entry> in the URI format in the Resource List File. > Described as the src attribute of the element.

  In this way, the BD player reads the Resource List File corresponding to the title at the time of playing the title, so that the files constituting the applications arranged together as archive files on the BD-ROM do not cause useless seeks. It can be read in a batch and all file names used in the application can be known.

  Further, by referring to the <Toppage> element in the Resource List File, it is possible to know which file is analyzed first when executing an application described in HTML and script.

  When a title different from the currently playing title is selected, the file described in the Resource List File of the title being played may be released, or the Resource List File associated with the selected title is released. You may release only files that are not listed in. By using the Resource List File in this way, it is possible to manage resources for each title in an easy-to-understand manner, improve the efficiency of data reading, and provide a mechanism that is less prone to errors during authoring and that is easy to control by the player It becomes possible.

In the Resource List File of the present embodiment, the name of the application is described in the name attribute of the <application> element, and the player uses the title name of the inserted BD-ROM Disc and the application name to inform the player. Can be identified. Accordingly, an area for each application may be set in the local storage of the player. Further, only the application can access the application area, and access to other applications may be prohibited.
(Structure of Resource List File in binary format)
The internal structure of the Resource List File in binary format that stores the directory structure information of the file archived in the CAR file will be described with reference to FIG.

<Resource List File>
The Resource List File in binary format is composed of Base Info and Base Directory. In the Base Info, information related to the entire CAR file in which the Resource List File is stored is described.

<Base Directory>
Base Directory describes the directory structure information of files such as HTML files stored in CAR files, and consists of Directories and Files placed one level below, with Information, Number, and CAR files as top directories. The The total number of Directories and Files is the number described in Number. In Information, information related to Base Directory is described.

<Directory>
The Directory is composed of Information, Number, and Directory and File that are arranged one stage below this Directory. The total number of Directories and Files is the number described in Number. In the Information, the name of the Directory and the attribute information of the Directory are described. Further, the directory arranged under the subordinate has the same configuration as that of the present directory.

<File>
File is composed of Information, Offset, and Name. In the Information, attribute information of this File is described. Name is a name. Offset describes the bit length from the beginning of the CAR file of the original file arranged in the CAR file.

(Effects of Resource List File in binary format)
By analyzing the internal directory and file of the Resource List File in binary format, the directory structure of the flat file in the CAR file and the multipart file can be restored, and in the File Since a real file position can be calculated from a CAR file preloaded by a buffer using a certain offset, a target file can be quickly cut out from a huge CAR file of several M to bytes.

(Example 3)
Next, a third embodiment of the present invention will be described.

  In the BD-ROM, the third embodiment is an interactive program composed of a digital stream such as video data, document data written in a declarative language such as HTML, a program written in a script, and an image file. This is a content related to realizing synchronized playback with content. Basically, the contents are based on the first embodiment and the second embodiment, and the explanation will be focused on the expansion or different portions.

(Issues when synchronized playback of video data and interactive content)
The BD-ROM application is an interactive content composed of document data written in a declarative language such as HTML, a program written in a script, an image file, and the like, information set in the BD-ROM, and a BD player. By using these resources, it is possible to realize a presentation that is rich in expressiveness to the user.

  On the other hand, when the digital stream such as video data and interactive content are played back synchronously, depending on the playback control status during special playback such as fast forward, rewind, pause, playback from pause, slow playback, etc. However, the synchronized playback of video data and interactive content may not be realized.

  In addition, when describing the synchronization processing of video data and interactive content in a script in the content, the script describes all synchronization control with video data for all playback control states of digital streams such as video data. There are cases where it is necessary to do this.

  For example, when the playback speed of special playback (fast forward, etc.) is very high (20x speed or higher), the player cannot generate mark events embedded in the video data in advance. In the script, processing corresponding to the mark event is not executed in advance, and there is a possibility that synchronization control with video data cannot be realized.

   FIG. 41 is a diagram showing an example of the configuration of a playback apparatus in the third embodiment according to the present invention.

  An HTML processing unit 3102 reads an HTML file that configures interactive content, configures a screen according to style definition information, and the like, and an event that occurs in response to a user operation received by the event processing unit 3104 or an application is generated It is a module that executes scripts related to each event. The AV playback control unit 3103 is a module that plays back an AV stream recorded on the BD-ROM in response to a control command from the HTML processing unit, a user operation received by the event processing unit 3104, or the like. The AV playback control unit 3103 holds player variables including information on the playback state of the current AV stream. Since the HTML processing unit 3102 and the AV playback processing unit 3103 are basically the same as those described in the first and second embodiments, detailed description thereof is omitted here.

  The management information analysis unit 3101 is a module that analyzes the Resource List File (hereinafter referred to as rcl file) in the Content Archive File (hereinafter referred to as CAR file) described in the second embodiment.

A presentation processing unit 3105 is a module that executes synchronous reproduction of an HTML document processed by the HTML processing unit 3102 and a digital stream such as video data processed by the AV reproduction control unit 3103.

Here, before describing the present embodiment, an operation example in the case of controlling the operation example at the time of special reproduction of video data and interactive content by script description will be described below.

  FIG. 42 describes an example of synchronized playback of video data and interactive content.

  FIG. 43 shows bbbb. html description example 3301 and bbbb. Script file script01.html described as an external file to be read by the html file. This is a description example 3302 of js.

  44 shows cccc. This is a description example 3303 of html.

FIG. 45 is a script file script11.script describing the processing to be executed in response to an event that occurred during fast-forward playback. This is a description example 3304 of js.
As shown in FIGS. 43 and 44, the script file is a file in which the script is written outside, and by specifying the URL using the src attribute in <script>, the script file is simply read and executed. Instead, a method may be used in which a <script> tag is used directly in the HTML file.

  In FIG. 42, after the Play button 3203 is pressed from bbbb.html 3201 which is the TOP screen by the user operation with the remote controller, the cccc. An example of a screen when transitioning to html 3231 and a Fast Forward button 3232 is pressed from the playback screen 3231 is shown.

  Hereinafter, an example of detailed operation of synchronous reproduction of video data and interactive content will be described with reference to FIGS. 41 to 45.

  bbbb. In html 3201, when the cursor or focus is placed on the Play button 3203 by the remote control operation by the user and the determination button is pressed, the event processing unit 3104 generates an HTML event to the HTML processing unit 3102 to generate a button element. A function indicated by the onclick attribute of func2 () is executed.

  The content of processing of func2 () is described separately in the external script file 3302. Note that func1 () is a function specified in the onclick attribute of the menu button element 3202, and func3 () is a function specified in the onclick attribute of the game button element 3204.

  func2 () is an HTML document bbbb. cccc. of URL specified from html. A process for switching the screen to html and starting playback of the title 00001 is described.

  The screen presented after the execution of func2 () is cccc. It includes an html 3211, button elements 3212 representing fast-forward playback, button elements 3213 representing stop, and button elements 3214 for returning to the menu screen. The playback screen of the title 00001 which is an AV stream such as video data is 3221. bbbb. html3201 and cccc. The html 3211 and mono media files such as button images are presented on the interactive graphics plane. An AV stream 3221 such as video data is presented on the moving picture plane. The playback screen 3231 is a presentation of the HTML document 3211 and the AV stream 3221 superimposed on each other.

  The playback screen 3231 is played back in conjunction with the HTML document and the AV stream. Hereinafter, a state in which the HTML document and the AV stream are presented in a superimposed manner is defined as video synchronized playback.

  It should be noted that the content being played back in synchronization with the video may be displayed as an HTML document at any time of the AV stream, or script processing is executed at any time of the AV stream to generate an HTML document or a monomedia file. May be switched and displayed.

  Here, an example of the operation when the fast-forward button on the remote controller is pressed by a user operation while the playback screen 3231 being synchronized with video is being presented is shown below.

When the fast-forward button on the remote controller is pressed, an event such as SpeedChangedEvent indicating that the playback state has changed from normal playback to fast-forward playback is dispatched to the HTML processing unit 3102 from the AV playback control unit 3103 of the player. .
An HTML document 3303 presenting a playback screen 3231 reads an external script file 3304, and an event handler is described in this external script file.

  In the event handler described in the external script file 3304, PlayBackEventHandler () is described. In the PlayBackEventHandler (), processing contents corresponding to the event type and the fast-forward speed are described.

  The HTML document 3303 reading the external script file 3304 changes the button attribute to be presented to “visible” or “hidden” depending on the type of event received.

  The fast-forward speed that is an argument of PlayBackEventHandler () has various patterns depending on the special playback setting of the player and the number of times the fast-forward button on the remote controller is pressed. Describe the processing corresponding to each speed in advance in the script. I have to leave. In the present embodiment, the external script file 3304 describes three patterns of 2x speed or less, 4x speed, and 8x speed, but there are cases where it is necessary to describe more patterns of processing in the event handler. .

  In this example of operation, the case of special playback at the time of fast-forwarding has been described, but other than fast-forwarding, there are rewinding, slow playback, N-times speed playback (N represents an integer), and the like.

  The video synchronized playback screen 3241 during fast-forwarding is a presentation state at the time of fast-forward playback at double speed or lower. In the case of the double speed or less, the HTML document and the video are continuously presented in a synchronized state, and each of the button elements 3242, 3243, 3344 is presented in synchronization with the AV stream being fast-forwarded.

  On the other hand, video synchronized playback 3251 during fast-forwarding is a presentation state during fast-forward playback at 8 × speed. In the case of 8 × speed, a video-only screen 3251 continues to be presented, indicating that HTML documents, button elements, etc. are not presented during fast-forward playback, and as a result, video synchronized playback is not being performed.

  As described above, when controlling the synchronized playback at the time of special playback of an AV stream such as video data and interactive content, it is necessary to set in advance all event processing at the time of special playback in the script file. Yes, it turns out that content creation is more complicated.

  Therefore, in order to solve the above problems, digital data such as video data can be used for interactive contents including document data written in a declarative language such as HTML, a program written in a script, and an image file. A mechanism is provided for setting whether to perform synchronized playback with a stream.

  More specifically, with respect to the directory attribute information included in the internal structure of the resource list file described in the second embodiment and the attribute information of the file, the video when the directory or file has special playback attributes. A function is provided for describing a descriptor capable of setting whether or not to perform synchronous reproduction with data.

  Note that the setting items of the directory attribute information and the file attribute information are validated by overwriting the lowest setting item based on the cascade processing.

(Means for solving the problem)
In order to set whether or not the HTML browser realizes synchronous reproduction with a digital stream such as video data, a video synchronous reproduction permission setting for identifying whether or not synchronous reproduction is realized is added to the Resource List File. To do.

  FIG. 46 is a diagram showing video synchronized playback permission setting information in BaseInfo of the resource list file in the binary format shown in FIG.

  TrickPlayInfo information is assigned to <BaseInfo>. TrickPlayInfo takes a value of only 0FF or ON. If the value of TrickPlayInfo is ON, the HTML browser continues to present interactive contents (resources such as HMTL documents and Monomedia files) during special playback of video data.

  On the other hand, if the value of TickPlayInfo is OFF, the HTML browser does not present video data and interactive content during special playback. In the present embodiment, since the trick play info is introduced into the base info of the resource list file, the value of the trick play info is always valid in the execution of the content archive file content. It is also possible to specify the effective range in units or files.

  FIG. 47 shows an example of the contents of the ContentsArchiveFile (CAR file).

  The Contents ArchiveFile (3500) is composed of one ResourceListFile, one SignatureFile, one HTML File, and seven Mono-Media files.

  The ResourceListFile stores logical configuration information of directories and files that make up the content, and the synchronous playback permission item is set for each directory or file unit.

One HTML file is a document file presented by the HTML processing unit 3102 and is an HTML file having only a frame whose background color is set to be transparent on the interactive plane. (3501)
Seven Mono-media files are image objects arranged on the interactive plane, and indicate button image files arranged in the HTML document. The button image is a jpg image. The Mono-media file indicating the button image or the like may be gif or PNG. The mono-media file constituting the contents in this embodiment includes an image file (3502) of a rewind button, an image file (3503) of a pause button, an image file (3504) of a stop button, and an image file (3505) of a fast forward button. ), A button image file (3506) for transitioning to TopMenu, an image file (3507) of a playback button, an image file (3508) displayed during normal playback, and an image file (3509) displayed during special playback. .

(When the video synchronous playback permission setting is all ON)
Here, FIG. 48 shows an example of synchronous reproduction of video data and content based on the CAR file described in FIG.

  When the user selects a title to view from the TOP menu or an arbitrary screen (S801), the HTML processing unit 3102 selects the content that constitutes the selected title based on the type of event received by the event processing unit 3104. In order to confirm the setting state, the CAR file is preloaded (S802), the resource list file in the preloaded CAR file is expanded on the memory of the player, and the directory attribute information and the file attribute information are interpreted (S803). ).

  The HTML processing unit 3102 reads the HTML document (S804), executes a playback command for the playlist linked to Title1 to the AV playback control unit 3103, and starts synchronized playback of the AV stream and the content ( S805).

  The synchronous playback start processing is a processing sequence from title selection. Here, the processing sequence when the AV playback state changes from the playback state to the fast-forward state by the user operation will be described with reference to FIG. The HTML browser uses the AV playback control unit 3102 to monitor the playback state of the AV stream (S1001). When the special processing event is received by the event processing unit 3104 (S1002), the event processing unit throws a fast-forward event to the HTML processing unit 3102 and the directory attribute information and the file attribute information in the resource list file of the management information analysis unit 3101 are sent. The setting is notified to the HTML processing unit 3102 (S1003). If the setting information is ON, HTML processing is executed (S1004), and the presentation processing unit 3105 presents the HTML document in synchronism with the AV stream (S1005).

  In this embodiment, an HTML file and a Mono-media file are arranged in the first appearing directory, and a setting item for permitting video synchronous playback during special playback (hereinafter referred to as video synchronous playback permission) in the directory attribute information. An example when the setting is ON will be described.

  The processing for interpreting the directory attribute information and the file attribute information may be performed before the execution of the playback command, or the CAR file may be stored in advance in a temporary area such as a player's memory, flash, HDD, or permanent storage area. When preloaded, the setting items set in the resource list file may be interpreted in advance.

FIG. 48 shows the content of a short-distance run in athletics played from time T1 to T4.
Before starting the reproduction of the video data from time T1, the HTML processing unit 3102 performs layout based on the setting of the HTML document of 3500-3509 and the button image in the style sheet set in the HTML document in advance, and the video from time T1. An AV stream such as video data is presented in conjunction with the presentation of data. (Screen 3601)
Between time T1 and time T2, since the user is viewing Title 1 in normal playback, the HTML processing unit 3102 continues to present the screen 3601 continuously. A button image (3508 in FIG. 47) during normal reproduction is displayed at the upper right position of the screen 3601, that is, at the upper right position of the HTML document presented on the interactive graphics plane.

  Here, when the user selects the fast-forward button on the screen 3601 at time T2, the HTML processing unit 3102 calls the control command set in the button image to the AV playback control unit 3103 of the player and executes the fast-forward command. To do.

  The player's AV playback control unit 3103 starts fast-forwarding and raises a special playback (fast-forward) event to the HTML processing unit 3102. The HTML processing unit 3102 receives the special playback event, and the event type is special playback ( In the case of a fast-forward event, the image file currently being played (3508 in FIG. 47) that has been presented until time T2 is replaced with the image file (3509 in FIG. 47) being specially played (fast-forward). The presentation process is performed. A screen example during special playback (fast-forward) is shown on a screen 3602.

  Although the display of the AV stream such as video data is in the fast-forward state, the video synchronous playback permission setting is ON, so the HTML document that constitutes the content and the button image for operation (rewind button 3502, pause button 3503, stop The button 3504, the fast-forward button 3505, and the menu button 3506) are continuously presented even when the AV stream such as video data is in the fast-forward state.

  When the user selects the playback button (3507 in FIG. 47) at time T3, the HTML processing unit 3102 calls the control command set in the button image to the AV playback control unit 3103 of the player, and plays the playback command. Order.

  The AV playback control unit 3103 of the player stops fast-forwarding, starts normal playback, throws a playback event to the HTML processing unit 3102, the HTML processing unit 3102 receives the playback event, and the event type is playback. In the event, the presentation process is performed by replacing the image file (3509 in FIG. 47) being specially reproduced that has been presented until time T3 with the image file (3508 in FIG. 47) being reproduced.

  At time T4, playback of the video data of Title1 ends. As for the operation of the player after the end of playback, the HTML processing unit 3102 may be in the standby state of the user operation with the final presentation screen, or may automatically transition to TopMenu, or the video playback control function The transition event to the designated title from the above may be received, and the termination process may be executed according to the context of the event.

The times T1 to T4 may be internal clocks of the player, may be relative times from the beginning of the clip video currently being played that constitutes the Title, or may be relative to the play item currently being played. It may be.
(When the video synchronized playback permission setting is partly ON)
Next, FIG. 49 shows an example of the case where the video synchronous playback permission setting is ON for the attribute information of a specific file during the synchronous playback of the video data and the interactive content during special playback.

  In this embodiment, the video synchronous playback setting item is ON for the 3500 HTML document file of FIG. 47 and the image file displayed during special playback of 3509, and the attribute information of the files of the other button image files includes The case where the video synchronous playback permission setting item is set to OFF will be described below.

FIG. 48 shows the content of a short-distance run in athletics played from time T1 to T4.
Before starting the reproduction of the video data from time T1, the HTML processing unit 3102 performs layout based on the setting of the HTML document of 3500-3509 and the button image in the style sheet set in the HTML document in advance, and the video from time T1. An AV stream such as video data is presented in conjunction with the presentation of data. (Screen 3611)
Between time T1 and time T2, since the user is viewing Title 1 in normal playback, the HTML processing unit 3102 continues to present the screen 3611. A button image (3508 in FIG. 47) during normal playback is displayed at the upper right of the screen 3611, that is, at the upper right of the HTML document presented on the interactive graphics plane.

Here, when the user selects the fast forward button on the screen 3611 at time T2,
The HTML processing unit 3102 calls a control command set in the button image to the AV playback control unit 3103 of the player and executes a fast-forward command.

  The player's AV playback control unit 3103 starts fast-forwarding and raises a special playback (fast-forward) event to the HTML processing unit 3102. The HTML processing unit 3102 receives the special playback event, and the event type is special playback ( In the case of a fast-forward event, the image file currently being played (3508 in FIG. 47) that has been presented until time T2 is replaced with the image file (3509 in FIG. 47) being specially played (fast-forward). The presentation process is performed. A screen example during special playback (fast forward) is shown by a screen 3612.

  Although the display of the AV stream such as video data is in the fast-forward state, the image file (3509 in FIG. 47) during special playback has the video synchronous playback permission setting ON, so that even if the video data is fast-forwarded, the video file shown in FIG. Like the screens 3612 and 3613, it is possible to continue presenting the Mono-media file on the upper right of the screen.

  However, in the file attribute information of the button image files 3502, 3503, 3505, 3506, and 3507 in FIG. 47, the video synchronized playback permission setting item is set to OFF, and the time 3502 to the time T3 is the 3502 described above. , 3503, 3505, 3506, and 3507 are not displayed during special playback.

  When the user selects the playback button (3507 in FIG. 47) at time T3, the HTML processing unit 3102 calls the control command set in the button image to the AV playback control unit 3103 of the player, and plays the playback command. Order.

  The AV playback control unit 3103 of the player stops fast-forwarding, starts normal playback, throws a playback event to the HTML processing unit 3102, the HTML processing unit 3102 receives the playback event, and the event type is a playback event. If there is, the image file (3509 in FIG. 47) that has been presented until time T3 is replaced with the image file (3508 in FIG. 47) that is being reproduced, and the presentation process is performed.

Further, after time T3, since the playback state is changed from the special playback state to the normal playback state, the button images 3502, 3503, 3504, 3505, and 3506 in FIG. 47 in the previous period are switched from non-display to display. (Screen 3614)
At time T4, playback of the video data of Title1 ends. As for the operation of the player after the end of playback, the HTML processing unit 3102 may be in the standby state of the user operation with the final presentation screen, or may automatically transition to TopMenu, or the video playback control function The transition event to the designated title from the above may be received, and the termination process may be executed according to the context of the event.

  The times T1 to T4 may be internal clocks of the player, may be relative times from the beginning of the clip video currently being played that constitutes the Title, or may be relative to the play item currently being played. It may be.

(When the video synchronous playback permission setting is all OFF)
Next, FIG. 50 shows an operation example when the video synchronous playback permission setting is OFF for the directory additional information during the synchronous playback of the video data and the interactive content during special playback.

  In this embodiment, the case where the video synchronous reproduction permission setting is set to OFF for all the image files 3502 to 3509 in FIG. 47 will be described below.

  FIG. 50 shows the content of a short-distance run in athletics played from time T1 to T4.

Before starting the reproduction of the video data from time T1, the HTML processing unit 3102 performs layout based on the setting of the HTML document of 3500-3509 and the button image in the style sheet set in the HTML document in advance, and the video from time T1. An AV stream such as video data is presented in conjunction with the presentation of data. (Screen 3611)
Between time T1 and time T2, since the user is viewing Title 1 in normal playback, the HTML processing unit 3102 continues to present the screen 3621. A button image (3508 in FIG. 47) during normal playback is displayed at the upper right of the screen 3621, that is, at the upper right of the HTML document presented on the interactive graphics plane.

Here, when the user selects the fast forward button on the screen 3621 at time T2,
The HTML processing unit 3102 calls the extended API set in the button image to the AV playback control unit 3103 of the player and commands a fast-forward command.

  The player's AV playback control unit 3103 starts fast-forwarding and throws a special playback event to the HTML processing unit 3102. The HTML processing unit 3102 receives the special playback event, and the event type is a special playback event. In this case, each image file that has been continuously presented until time T2 is hidden, and the presentation process of the screen 3621 is performed.

  In this case, the display of the video data is fast-forward display, and the image file being specially reproduced is not displayed during the special reproduction period from time T2 to T3 because the video synchronous reproduction permission setting is OFF.

  Here, when the user selects the fast-forward button on the screen 3621 at time T2, the HTML processing unit 3102 calls the control command set in the button image to the AV playback control unit 3103 of the player, and the fast-forward command Execute.

The AV playback control unit 3103 of the player starts fast-forwarding and raises a special playback (fast-forward) event to the HTML processing unit 3102. The HTML processing unit 3102 receives the special playback event, and the event type is special playback (fast-forward). ) If it is an event, each image file that has been continuously presented until time T2 is hidden and the presentation process of the screen 3621 is performed. (Screen 3622)
In this case, the display of the AV stream such as the video data is in a fast-forwarding state. However, the button-image Mono-Media file and the special playback image file are all set to OFF because the video synchronous playback permission setting is OFF. Even during playback, only AV streams such as video data are shown on the video plane as shown in screens 3622 and 3623 in FIG.

  Note that the process of the HTML browser on the interactive graphics plane may be in the kill state, or the HTML browser may continue to go without presenting the file.

  The operation of this embodiment can also be realized in an embodiment in which the HTML document 3501 is switched to another HTML document and displayed at the time T2.

  When the user presses the remote control button playback button or the like at time T3, the event processing unit 3104 receives the remote control key event, and raises the event type to the HTML processing unit 3102 and the AV playback control unit 3103. The AV playback control unit 3103 of the player stops fast-forwarding and starts normal playback, and the HTML processing unit appropriately presents a button image or the like in the CAR file from time T3. (Screen 3624) Display.

  At time T4, playback of the video data of Title1 ends.

  The HTML processing unit 3102 may be in the standby state of the user operation as it is with the final presentation screen, or may automatically transition to TopMenu, or a transition event to a specified title from the video playback control function. The end processing may be executed according to the context of the event received.

  The times T1 to T4 may be internal clocks of the player, may be relative times from the beginning of the clip video currently being played that constitutes the Title, or may be relative to the play item currently being played. It may be.

  In this embodiment, when the video synchronization permission setting of the directory attribute information is set to ON, when the video synchronization permission setting of the directory attribute information is set to OFF, or in a specific file of the file attribute information. In the above example, the video synchronization permission setting is set to ON. However, when the video synchronization permission setting is added to the attribute information of the directory and the attribute information of the file, there are various settings depending on the configuration of the interactive content. Possible methods include setting the video synchronization permission setting to the directory attribute information for each directory for multiple directories, or setting the video synchronization permission setting to the file attribute information for each file for multiple files. You may do it.

  As described above, by setting ON / OFF of the video synchronous playback permission setting for the directory attribute information and the file attribute information in the resource list file in the CAR file, interactive content and AV such as video data are set. Since the presentation method of whether or not to play the stream in synchronization can be set in advance when creating the content, the various states during special playback for each document described in each declarative language constituting the interactive content Depending on (fast forward, rewind, slow playback, N-times playback, etc.), it is obviously easier to produce than writing a script to synchronize interactive content and AV stream such as video data. It is possible to realize flexible presentation to the user.

  In this embodiment, the binary format is used as the structure of the Resource List File that is the management information for managing the application data. However, for example, it may be described in the XML format or in the format using the declarative description language. It may be described.

  In this embodiment, HTML is used as the application description language. However, the present invention is not limited to this. As long as it can be interpreted by the player, for example, it may be an original XML language that defines a screen configuration, may be XHTML, and does not necessarily need to be in XML format.

Example 4
Next, a fourth embodiment of the present invention will be described.

  In the BD-ROM playback environment, the fourth embodiment uses a specific file or video data in an application recorded on the BD-ROM during synchronous playback of an AV stream such as video data and interactive content. The content relates to the function of recording a synchronized scene.

  Basically, the contents are based on the first embodiment, the second embodiment, and the third embodiment, and the description will be focused on the expanded or different portions.

(Problems when recording synchronized scenes of video data and interactive content)
The BD-ROM application is an interactive content composed of document data written in a declarative language such as HTML, a program written in a script, an image file, and the like, information set in the BD-ROM, and a BD player. By using these resources, it is possible to realize a presentation that is rich in expressiveness to the user.

  Also, the BD-ROM application allows the user to record the user's favorite scenes and favorite scenes when viewing the content recorded on the BD-ROM or an application rich in expressiveness. is there.

  Furthermore, when viewing the content recorded on the BD-ROM again, the BD-ROM application displays a list of previously recorded favorite scenes and favorite scenes, and the user-selected favorite scene is displayed. It is possible to provide a function of starting playback from a scene or favorite scene.

  A Bookmark function (hereinafter referred to as “Bookmark”) is provided as a function of a conventional general WEB browser. Bookmark is a function that records the addresses of websites that are frequently accessed by users. As a user's merit, it is not necessary to bother to enter a URL by keeping a bookmark of the user's favorite pages. Also, it is possible to save the trouble of following the links on the WEB page.

  Here, with reference to FIG. 51 and FIG. 52, an example of operation control in the case of performing a book mark by synchronizing a specific scene or interactive content when an AV stream such as video data and interactive content are reproduced in synchronization will be described. .

  FIG. 51 shows a synchronization state between the interactive content and the AV stream.

  On the screen 4301, the HTML browser displays an HTML document 1111. This is a screen presented in synchronism with the interactive content composed of html and MNG file 1 (4302) and the AV stream (4311) reproduced in the section from time T1 to T2.

  The screen 4303 is displayed on the HTML browser 1112. This is a screen presented in synchronism with the interactive content composed of html and MNG file 2 (4304) and the AV stream (4312) reproduced in the section from time T2 to T3.

  The screen 4305 is displayed on the HTML document 1113. This is a screen presented in synchronism with interactive content composed of html and MNG file 3 (4306) and AV stream (4313) reproduced in the section from time T3 to T4.

  In the present embodiment, 4311 to 4313 are set as one list (hereinafter referred to as “PlayList file”) collected as a unit for executing reproduction.

  For AV stream playback, if a PlayList file is specified when the HTML content calls a playback start command, playback of the AV stream linked to the specified PlayList file starts.

  Note that the AV stream to be played back is composed of a section (4311) from time T1 to T2, a section (4312) from time T2 to T3, and a section (4313) from time T3 to T4 as playback units. Also good.

  When the player requests the player to start playing a title at the time T1, the HTML browser receives an event generated by the user's remote control operation by the event processing unit 3104, throws the event to the HTML processing unit 3102, and the HTML content is AV. In order to start playback of the stream, a playback start command is executed to the AV playback control unit 3103, and the AV playback control unit 3103 starts playback of the PlayList file specified in the playback start command.

  Between time T1 and time T2, the AV stream presents a square video (4314), and the HTML content presents an MNG file 1 (4302) representing a face image.

  Between time T2 and time T3, the AV stream presents a round video (4315), and the HTML content presents an MNG file 2 (4304) representing a face image.

  Between time T1 and time T2, the AV stream presents a triangular video (4316), and the HTML content presents an MNG file 3 (4306) representing a face image.

  When the user presses the Bookmark button on the remote control at the time TN, when the bookmark is synchronized with the AV stream such as video data and the interactive content, the HTML content 1112. html (4303) and MNG file 2 (4304) which is a round image (4315) are recorded as favorites in the temporary storage area of the player.

  4401 in FIG. 52 shows a screen of an AV stream such as video data and a interactive content (HTML content) booked by the user.

  On the other hand, when the user displays a list of bookmarked favorite contents from the resident application of the player, the bookmarked HTML document 1112. Since the command specifying which PlayList file is being played is not described in html, the resident application of the player presents the HTML content and the AV stream and displays the favorite list list. There are cases where it can only be presented.

Also, when the user presses the Bookmark button on the remote control at the time TN, the URI identifying the PlayList file currently being played is recorded by the player's resident app, and when the Bookmark is registered based on the URI. The AV stream being reproduced is identified, and the first scene of the AV stream and the book mark HTML document 1112. Overlay html and MNG file 2 (4304)
In the Residential application, when the favorite list is presented, the first scene of the AV stream is displayed as a square image (4314). An example of this screen is shown at 4402 in FIG.

  As described above, when the Bookmark function at the time of synchronous playback of an AV stream such as video data and interactive content is realized, depending on the configuration of the content, the video data intended by the user, the favorite scene of the interactive content, and the player can select the favorite list. When displaying a list, a problem occurs in which favorite scenes to be displayed are different.

  Therefore, in order to solve the above problems, digital data such as video data can be used for interactive contents including document data written in a declarative language such as HTML, a program written in a script, and an image file. Provided is a mechanism (hereinafter referred to as “Bookmark registration permission setting”) for setting whether or not to enable the Bookmark function during synchronized playback of streams.

  More specifically, the directory and file have special attributes for the directory attribute information and the file attribute information included in the internal structure of the resource list file described in the second and third embodiments. Provided is a function for describing a descriptor capable of setting whether or not to perform synchronous reproduction with video data during reproduction.

  Note that the setting items of the directory attribute information and the file attribute information are validated by overwriting the lowest setting item based on the cascade processing.

(Means for solving the problem)
Bookmark function when HTML browser synchronizes and reproduces interactive contents composed of document data and script files written in a declarative language such as HTML and digital files such as video data In order to set whether or not to enable the Bookmark function, a Bookmark registration permission setting for identifying whether or not to enable the Bookmark function is added to the Resource List File.

  FIG. 51 is a diagram showing video synchronized playback permission setting information in the BaseInfo of the Resource List File in the binary format shown in FIG.

BookMarkInfo information is assigned to <BaseInfo>. BookmarkInfo takes a value of only 0FF or ON. If the value of BookmarkInfo is ON, the HTML browser continues to present interactive content (resources such as HMTL documents and Monomedia files) during special playback of video data.
On the other hand, if the value of BookmarkInfo is OFF, the HTML browser does not present video data and interactive content during special playback. In this embodiment, since the BookmarkInfo is introduced into the BaseInfo of the Resource List File, the value of the BookmarkInfo is always valid in the execution of the ContentsArchiveFile content. For example, if the BookMarkInfo information is introduced into the Directory or Information It is also possible to specify the effective range in units or files.

FIG. 54 shows the contents of a certain ContentsAchieveFile.
The Contents ArchiveFile (4500) is composed of one ResourceListFile, one SignatureFile, one HTML File, and seven Mono-Media files. The ResourceListFile stores logical configuration information of directories and files that make up the content, and the Bookmark registration permission setting is set for each directory or file unit.

One HTML file is a document file presented by the HTML processing unit 3102 and is an HTML file having only a frame whose background color is set to be transparent on the interactive plane. (4501) Seven Mono-media files are image objects arranged on the interactive plane, and indicate button image files arranged in the HTML document. The button image is a jpg image. The Mono-media file indicating the button image or the like may be gif or PNG. The Mono-media file constituting the content in this embodiment is a button image file (4502) for transitioning to TopMenu, an image file of a pause button (4503), an image file of a Bookmark registration button (4504), and normal playback The image file (4505), the temple A jpg file (4506), the temple B jpg file (4507), and the temple C jpg file (4508).
(When the bookmark registration permission setting is all OFF)
Here, FIG. 54 shows an example of Bookmark registration based on the CAR file shown in FIG. 53 during synchronized playback of video data and content.

  When the user selects a title to view from the TOP menu or an arbitrary screen (S801), the HTML processing unit 3102 selects the content that constitutes the selected title based on the type of event received by the event processing unit 3104. In order to confirm the setting state, the CAR file is preloaded (S802), the resource list file in the preloaded CAR file is expanded on the memory of the player, and the directory attribute information and the file attribute information are interpreted (S803). ).

  The HTML processing unit 3102 reads the HTML document (S804), executes a playback command for the playlist linked to Title1 to the AV playback control unit 3103, and starts synchronized playback of the AV stream and the content ( S805).

  In the present embodiment, a description will be given of a case where the Bookmark registration permission setting is set to OFF for the directory attribute information of the first appearing Directory.

  The processing for interpreting the directory attribute information and the file attribute information may be performed before the execution of the playback command, or the CAR file may be stored in advance in a temporary area such as a player's memory, flash, HDD, or permanent storage area. When preloaded, the setting items set in the resource list file may be interpreted in advance.

  The Title 1 is a travel program that is played from time T1 to time T4, and is content that introduces temples in each region.

Before starting the reproduction of the video data from time T1, the HTML processing unit 3102 performs layout based on the setting of the style document set in advance in the HTML document and the button image of the above 4500 to 4508, and the video from time T1. The HTML browser that presents interactive content in synchronization with the data continues to present the screen 4511 between time T1 and time T2. The temple A jpg file (4506) is displayed at the lower right of the screen 4511, that is, at the lower right of the HTML document presented on the interactive graphics plane.

  The HTML browser continues to present the screen 4512 from time T2 to time T3. The temple B jpg file (4507) is displayed at the lower right of the screen 4512, that is, at the lower right of the HTML document presented on the interactive graphics plane.

  The HTML browser continues to present the screen 4513 from time T3 to time T4. The temple C jpg file (4508) is displayed at the lower right of the screen 4513, that is, at the lower right of the HTML document presented on the interactive graphics plane.

  Here, when the user presses the Bookmark button on the remote controller at the time TN on the screen 4512 being played (S1001), the HTML browser receives the Bookmark event at the event processing unit 3104 (S1002), and management information The analysis unit 3101 confirms the setting of the attribute information (S1003), and the Bookmark registration permission setting that is the directory attribute information is OFF, so that the HTML content being presented is not recorded in the temporary storage area of the player as the Bookmark ( S1004).

  For this reason, even if the user presents a favorite list with the resident application, the HTML scene and the first scene of the AV stream bookmarked in the travel program are not included in the favorite list (S1005).

  Note that when the Bookmark registration permission setting is OFF, the application displays a panel indicating that the Bookmark function cannot be used for the user, or displays an HTML document as a process when the user presses the Bookmark button on the remote control. A Monomedia file indicating that the Bookmark function cannot be used may be presented in a specific area.

(When the bookmark registration permission setting is partially OFF)
Next, in this embodiment, the Bookmark registration permission setting is set to OFF for the directory attribute information of the first appearing directory, and the file attribute is set for the HTML document 4501 and the jpg file (4506) of the temple A. As information, the case where the Bookmark registration permission setting is set to ON will be described.

  Basically, the contents are based on the embodiment in the case where the above-described Bookmark registration permission setting is OFF, and the description will be focused on the expanded or different portions.

  When the user presses the Bookmark button on the remote controller to register the jpg file (4506) of temple A being played (S1001) as a favorite on the screen 4511, the player receives the Bookmark event at the event processing unit 3104 (S1002). The management information analysis unit 3101 confirms the Bookmark registration permission setting that is the attribute information of the directory (S1003). Since the Bookmark registration permission setting is ON, the HTML content 4501 being presented and the jpg file of the temple A (4506) In the player's temporary storage area.

  Even if the user tries to register the jpg file (4507) of the temple B being played back at the time TN2 on the screen 4512 as a favorite and presses the Bookmark button on the remote controller, the file attribute item of the jpg file of the temple B is “Bookmark”. Since the registration permission setting is OFF, the HTML browser does not record the temple B jpg file in the temporary storage area of the player.

  When the user presents the favorite list with the resident application, of course, the content for which the bookmark registration permission setting is set to OFF is not recorded in the player's temporary storage area, and is therefore displayed in the favorite list. There is nothing.

  Note that when the Bookmark registration permission setting is OFF, a panel indicating that the Bookmark function cannot be used is displayed to the user, or the HTML document is specified as a process when the user presses the Bookmark button on the remote controller. In this area, a Monomedia file indicating that the Bookmark function cannot be used may continue to be presented.

  In this embodiment, the binary format is used as the structure of the Resource List File that is the management information for managing the application data. However, for example, it may be described in the XML format or in the format using the declarative description language. It may be described.

  In this embodiment, HTML is used as the application description language. However, the present invention is not limited to this. As long as it can be interpreted by the player, for example, it may be an original XML language that defines a screen configuration, may be XHTML, and does not necessarily need to be in XML format.

(Example 5)
Next, a fifth embodiment of the present invention will be described.

  In the fifth embodiment, the interactive content in the BD-ROM playback environment when special playback is performed while an AV stream such as video data and the interactive content are synchronized in an application recorded on the BD-ROM. The content relates to the operation control function.

  Basically, the contents are based on the first embodiment, the second embodiment, the third embodiment, and the fourth embodiment, and the description will be focused on the expanded or different portions.

(Problems of motion control during special playback of interactive content linked with video data)
The BD-ROM application is an interactive content composed of document data written in a declarative language such as HTML, a program written in a script, an image file, and the like, information set in the BD-ROM, and a BD player. By using these resources, it is possible to realize a presentation that is rich in expressiveness to the user.

  Specifically, the BD-ROM application receives a document when a mark event that occurs at a specific timing during AV stream reproduction such as video data is received or when a Timer function described in a script file is fired. The transition is performed, the Monomedia file in the HTML document is switched, the menu is displayed, the animation reproduction is started, and the audio reproduction is started.

  In this way, in the synchronous playback of interactive content linked to an AV stream such as video data, when the video changes to the fast forward or rewind state via an application or by a direct instruction from the user, the application Even if all the mark events and timer events have been received, the next mark event and timer event will be received even though the processing to be executed after the reception of a specific event has not been completed. In other words, there is a problem that control of content presentation processing linked to an AV stream such as video data is not completed before reception of the next event.

  Even when some events are received during special playback and the content is controlled, the event handler is executed in the script file according to conditions such as the speed of special playback, the type of event, and the selection method of the acquired event. Since the process must be described, the production of content may be complicated.

  Therefore, in order to solve the above problems, digital data such as video data can be used for interactive contents including document data written in a declarative language such as HTML, a program written in a script, and an image file. A mechanism (hereinafter referred to as an event reception permission setting item) for setting whether or not to realize event synchronized playback with a stream is provided.

(Means for solving the problem)
(When event reception permission setting is OFF)
Whether or not to allow the Resource ListFile to receive events so that the content creator can select whether or not the HTML browser receives events during special playback of an AV stream such as video data and interactive content Add event reception permission setting to identify

  FIG. 56 is a diagram showing event reception permission setting information in BaseInfo of the resource list file in the binary format shown in FIG.

  EventReceiveInfo information is assigned to <BaseInfo>. EventReceiveInfo takes a value of only 0FF or ON. If the value of EventReceiveInfo is ON, the HTML browser will be able to display the event during special playback regardless of whether the operation control processing after receiving the mark event or Timer event is described in the script. Are all received.

  On the other hand, if the value of EventReceiveInfo is OFF, the HTML browser does not receive the special playback event.

  In this embodiment, since EventReceiveInfo is introduced into the BaseInfo of the Resource List File, the value of EventReceiveInfo is always valid in the execution of the CAR content. It is also possible to specify the effective range in units or files.

  By introducing the above mechanism, in synchronous playback of interactive content linked with AV streams such as video data, the application may or may not receive a mark event or special event set by the Timer function during special playback such as fast-forwarding By setting the setting item to OFF, in the presentation of content linked with an AV stream such as video data during special playback, an event that occurs at a specific timing is used as a trigger to control the presentation state of the content. In this case, for example, there is an effect that the presentation state of the content is not significantly impaired such that the image file such as Monomedia is presented in a place that is completely unrelated to the presentation of the video data during the special reproduction.

  Also, on the content side, if you do not want to present interactive content triggered by event reception during special playback, you do not have to describe all the states during special playback in the script. However, since it is only necessary to set ON / OFF of the event reception permission setting information, an effect of improving the ease of content production is expected.

  Note that the special reception speed may be described in the event reception permission setting item so that an event is received in the special reproduction at a speed designated by the content side.

  The event reception permission setting item may describe the priority information of the event to be acquired.

  In the event reception permission setting item, acquisition conditions for the same type of event may be described. The event acquisition conditions include, for example, when the event number is an even number, or acquiring an event other than the user event.

  In this embodiment, the binary format is used as the structure of the Resource List File that is the management information for managing the application data. However, for example, it may be described in the XML format or in the format using the declarative description language. It may be described.

  In this embodiment, HTML is used as the application description language. However, the present invention is not limited to this. As long as it can be interpreted by the player, for example, it may be an original XML language that defines a screen configuration, may be XHTML, and does not necessarily need to be in XML format.

  The information recording medium, the reproducing apparatus, and the reproducing method according to the present invention make it possible to realize a more expressive content at the time of synchronous reproduction between documents linked to a digital stream on the recording medium. It has an effect and is suitable for use in a next-generation disc such as a BD-ROM and a playback device thereof.

DVD configuration diagram Highlight configuration diagram Diagram showing an example of multiplexing on a DVD Data hierarchy diagram of BD-ROM Configuration diagram of logical space on BD-ROM Outline block diagram of BD-ROM player Configuration block diagram of BD-ROM player BD-ROM application space explanatory diagram Configuration diagram of MPEG stream (VOB) Pack configuration diagram The figure explaining the relationship between AV stream and a player structure AV data continuous supply model diagram to track buffer VOB information file configuration diagram Illustration of time map How to get address information using time map Playlist file structure diagram Configuration diagram of program files corresponding to playlists BD disk overall management information file configuration diagram Diagram of the file that records global event handlers Diagram explaining examples of time events Diagram explaining examples of user events Diagram explaining an example of a global event handler Virtual machine configuration diagram Diagram of player variable table Figure showing an example of event handler (time event) Diagram showing an example of event handler (user event) Flow chart of basic processing of player Flow chart of playlist playback processing Event processing flowchart Subtitle processing flowchart Diagram explaining module configuration and control flow Diagram explaining the relationship between Index Table and HTML file Example of an HTML file that displays buttons Explanatory drawing explaining the life cycle of data Timing chart explaining the data life cycle Diagram explaining how to combine data into one Diagram explaining how to combine data into one Flow chart of processing in Title activation and document transition Diagram showing an example of a Resource List File in XML format Resource List File structure diagram in binary format The figure which shows an example of the relationship between an HTML document, AV stream, and an event. Diagram showing an example of synchronized playback of video data and interactive content Diagram showing examples of HTML documents and script files Diagram showing an example of an HTML document Figure showing an example of a script file Structure diagram of Resource List File in binary format Explanatory drawing of Contents ArchiveFile in Example 3 Example of screen when all video synchronized playback permission settings in Example 3 are ON Example of screen when the video synchronized playback permission setting is partially ON in the third embodiment Example of screen when all video synchronized playback permission settings in Embodiment 3 are OFF Structure diagram of Resource List File in binary format Explanatory drawing about the synchronous reproduction of AV stream and content in Example 4 Explanatory drawing about the synchronous reproduction of AV stream and content in Example 4 Explanatory drawing of Contents ArchiveFile in Example 4 Example screen when the bookmark registration permission setting is partially ON in the fourth embodiment Structure diagram of Resource List File in binary format Flowchart of video data and content synchronous playback presentation processing

Explanation of symbols

201 BD disc 202 optical pickup 203 program recording memory 204 management information recording memory 205 AV recording memory 206 program processing unit 207 management information processing unit 208 presentation processing unit 209 image plane 210 video plane 211 composition processing unit 301 program recording memory 302 program processor 303 UOP manager 304 Management information recording memory 305 Scenario processor 306 Presentation controller 307 Clock 308 Image memory 309 Track buffer 310 Demultiplexer 311 Image processor 312 Video processor 313 Sound processor 314 Image plane 315 Video plane 316 Composition processing unit 317 Drive controller 00 of the production stage with the directory structure logic tree 401 Content Archive File
402 Resource List File
3101 Management Information Analysis Unit 3102 HTML Processing Unit 3103 AV Playback Control Unit 3104 Event Processing Unit 3105 Presentation Processing Unit 3201 Example of TOPMENU 3202 MenuButton Image File 3203 PlayButton Image File 3204 GameButton Image File 3211 Interactive Graphic File 3211 StopButton image file 3213 MenuButton image file 3214 GameButton image file 3221 AV stream on the video plane 3231 Screen example during synchronized playback of interactive content and AV stream 3232 StopButton image file 3233 nuButton image file 3234 GameButton image file 3241 Example screen during special playback of interactive content and AV stream 3242 StopButton image file 3243 MenuButton image file 3244 GameButton image file 3251 Example of interactive content AV stream 3301 HTML file (bbbb.html)
3302 Script file (script01.js)
3303 HTML file (cccc.html)
3304 Script file (script11.js)
3500 Example of Content Archive File in Example 3 3501 HTML file 3502 Button image file for rewinding 3503 Button image file for pausing 3504 Button image file for pausing 3505 Return to button image screen 350 for fast forwarding Button image file for playback 3507 Button image file for playback 3508 Image file indicating playback status 3509 Image file indicating fast-forwarding status 3601 Screen example during normal playback in embodiment 3 3602 When attribute item in embodiment 3 is ON 3603 Example of screen when attribute item is ON in Example 33604 Example 3 Example of screen during normal reproduction 3611 Example of screen during normal reproduction in Example 3 3612 Example of screen when attribute item in Example 3 is partially ON 3613 Example of screen when attribute item in Example 3 is partially ON 3614 Example of screen during normal playback in Example 3 3621 Example of screen during normal playback in Example 3 3622 Example of screen when attribute item in Example 3 is OFF 3623 Example of screen when attribute item in Example 3 is OFF 3624 Example of screen during normal playback in Example 3 4301 Example of screen in Example 4 4302 MNG file 4303 Example of screen in Example 4 4304 MNG file 4305 Example of screen in Example 4 4306 MNG file 4311 AV stream 4312 AV stream 4313 AV stream 4314 AV stream Video displayed in 4311 4315 Video displayed in AV stream 4312 4316 Video displayed in AV stream 4313 4401 Example of favorite screen recorded by player and synchronized with video 4402 Favorite recorded in video by player and not synchronized with video Screen Example 4500 Example of Content Archive File in Example 4 4501 HTML file 4502 Button image file for returning to the menu screen 4503 Button image file for pausing 4504 Book mark image file for playback 4505 Message file for playback 4505 File 4507 jpg file 4508 jpg file 4511 Example screen 4 in Example 4 Screen example in screen example 4513 Example 4 in 12 Example 4 S101 disc insertion step S102 BD. INFO reading step S103 BD. PROG reading step S104 First event generation step S105 Event handler execution step S201 UOP reception step S202 UOP event generation step S203 Menu call determination step S204 Event generation step S205 Event handler execution step S301 Playlist reproduction start step S302 Playlist information (XXX.PL ) Reading step S303 Playlist program (XXX.PROG) reading step S304 Cell playback start step S305 AV playback start step S401 AV playback start step S402 VOB information (YYY.VOBI) reading step S403 VOB (YYY.VOB) reading step S404 VOB Playback start step S405 VOB Playback end step S406 Next cell presence determination step S501 Playlist playback start step S502 Playlist playback end determination step S503 Time event time determination step S504 Event generation step S505 Event handler execution step S601 Playlist playback start step S602 Playlist playback end determination step S603 UOP reception determination step S604 UOP event generation step S605 Menu call determination step S606 User event valid period determination step S607 Event generation step S608 Event handler execution step S701 Playlist reproduction end determination step S702 Playlist reproduction end determination step S703 Subtitle drawing start determination step S704 Subtitle rendering step S7 05 Subtitle display end determination step S706 Subtitle deletion step S801 Title activation step S802 CAR file preload step S803 Resource List File reading step S804 HTML file reading step S805 Screen presentation step S901 Document transition operation step S902 Title determination step S903 Lisres Rest read Step S904 HTML file reading step S905 Screen presentation step S1001 Playback state confirmation step S1002 Event reception step S1003 Attribute item determination step S1004 HTML document processing step S1005 Screen presentation step S1006 HTML document processing step S1007 Screen presentation step

Claims (22)

An information recording medium for recording interactive content including a title including a digital stream and a document described in a declarative language,
Information recording medium in which video synchronous playback function attribute information for specifying whether to set synchronous execution of the document described in the title and the declarative language when the interactive content is executed is recorded .   The video synchronized playback function is based on the setting of whether or not to present the interactive content during the special playback of the title including the digital stream in the playback of the interactive content including the title including the digital stream and the document described in the declarative language. The information recording medium according to claim 1, wherein the information recording medium is a function capable of executing reproduction.   The information recording medium has interactive content management information for managing data files constituting interactive content, and the video synchronized playback function attribute information is recorded in the interactive content management information. The information recording medium described in 1. A playback device capable of simultaneously playing back a digital stream recorded on an information recording medium and executing interactive content comprising a document described in a declarative language,
An interactive content execution unit that analyzes, displays, and executes a document described in a declarative language;
A management information analysis unit that analyzes whether or not the interactive content uses a video synchronized playback function implemented in a playback device during special playback of the digital stream;
A display processing unit that executes the video synchronized playback function when the interactive content is executed when the interactive content is analyzed by the management information analysis unit using the video synchronized playback function installed in the playback device; A playback device.   5. The playback apparatus according to claim 4, wherein the management information analysis unit makes a determination based on video synchronous playback function attribute information in interactive content management information recorded on an information recording medium. A reproduction method capable of simultaneously reproducing a digital stream recorded on an information recording medium and executing interactive content including a document described in a declarative language,
Analyzing, displaying and executing a document written in a declarative language;
A management information analysis step for analyzing whether or not the interactive content uses a video synchronized playback function installed in a playback device during special playback of the digital stream;
A step of executing the video synchronized playback function when the interactive content is executed when the interactive information is analyzed using the video synchronized playback function installed in the playback device in the management information analyzing step. How to play. A program capable of simultaneously playing a digital stream recorded on an information recording medium and executing interactive content including a document described in a declarative language,
Analyzing, displaying and executing a document written in a declarative language;
A management information analysis step for analyzing whether or not the interactive content uses a video synchronized playback function installed in a playback device during special playback of the digital stream;
Causing the computer to execute the step of executing the video synchronized playback function when the interactive content is executed when the interactive content is analyzed using the video synchronized playback function installed in the playback device by the management information analyzing step. A program characterized by An information recording medium for recording interactive content including a title including a digital stream and a document described in a declarative language,
Video interactive recording / playback function attribute information for specifying whether or not to set synchronous recording at a specific timing for the document described in the title and the declarative language is recorded when the interactive content is executed. A characteristic information recording medium.   The video synchronized recording / playback function is described in the title and the declarative language when playing the title including the digital stream in the playback of the interactive content including the title including the digital stream and the document described in the declarative language. The information recording medium according to claim 8, wherein the information recording medium has a function capable of reproducing the recorded document based on a setting for whether or not to allow synchronous recording at a specific timing.   The information recording medium has interactive content management information for managing data files constituting the interactive content, and the video synchronous recording / playback function attribute information is recorded in the interactive content management information. 9. The information recording medium according to 9. A playback device capable of simultaneously playing back a digital stream recorded on an information recording medium and executing interactive content comprising a document described in a declarative language,
An interactive content execution unit that analyzes, displays, and executes a document described in a declarative language, and whether or not the interactive content uses a video synchronous recording / playback function implemented in a playback device during special playback of the digital stream A management information analysis unit for analyzing
When the interactive information is analyzed by the management information analysis unit using the video synchronization recording / playback function installed in the playback device, the management information analysis unit includes a presentation processing unit that executes the video synchronization recording / playback function when the interactive content is executed. A reproducing apparatus characterized by that.   12. The playback apparatus according to claim 11, wherein the management information analysis unit makes a determination based on video synchronous recording / playback function attribute information in interactive content management information recorded on an information recording medium. A reproduction method capable of simultaneously reproducing a digital stream recorded on an information recording medium and executing interactive content including a document described in a declarative language,
Analyzing, displaying and executing a document written in a declarative language;
A management information analysis step for analyzing whether or not the interactive content uses a video synchronous recording / playback function implemented in a playback device during special playback of the digital stream;
A step of executing the video synchronized recording / reproducing function when the interactive content is executed when the interactive content is analyzed by the management information analyzing step using the video synchronized recording / reproducing function installed in the reproducing apparatus. A characteristic reproduction method. A program capable of simultaneously playing a digital stream recorded on an information recording medium and executing interactive content including a document described in a declarative language,
Analyzing, displaying and executing a document written in a declarative language;
A management information analysis step for analyzing whether or not the interactive content uses a video synchronized playback function installed in a playback device during special playback of the digital stream;
When the interactive information is analyzed using the video synchronized recording / playback function installed in the playback device by the management information analyzing step, the computer executes the video synchronized recording / playback function when the interactive content is executed. A program characterized by letting An information recording medium for recording interactive content including a title including a digital stream and a document described in a declarative language,
Event recording / playback function attribute information for specifying whether or not to set synchronous presentation of the document described in the title and the declarative language when the interactive content is executed is recorded. .   The event-synchronized playback function is described in the title or the declarative language at the time of special playback of the title including the digital stream in the reproduction of interactive content including a title including the digital stream and a document described in the declarative language. The information recording medium according to claim 15, wherein the information recording medium has a function capable of executing reproduction based on an event reception enable / disable setting linked to a document.   17. The information recording medium has interactive content management information for managing a data file constituting interactive content, and the event synchronized playback function attribute information is recorded in the interactive content management information. The information recording medium described in 1. A playback device capable of simultaneously playing back a digital stream recorded on an information recording medium and executing interactive content comprising a document described in a declarative language,
An interactive content execution unit that analyzes, displays, and executes a document described in a declarative language;
A management information analysis unit that analyzes whether or not the interactive content uses a video synchronized playback function implemented in a playback device during special playback of the digital stream;
A presentation processing unit that executes an event-synchronized playback function when the interactive content is executed when the interactive content is analyzed by the management information analysis unit using the event-synchronized playback function installed in a playback device; A playback device.   19. The playback apparatus according to claim 18, wherein the management information analysis unit makes a determination based on event-synchronized playback function attribute information in interactive content management information recorded on an information recording medium. A reproduction method capable of simultaneously reproducing a digital stream recorded on an information recording medium and executing interactive content including a document described in a declarative language,
Analyzing, displaying and executing a document written in a declarative language;
A management information analysis step for analyzing whether or not the interactive content uses an event-synchronized playback function implemented in a playback device during special playback of the digital stream;
A step of executing the event-synchronized playback function when the interactive content is executed when the interactive content is analyzed using the event-synchronized playback function implemented in the playback device by the management information analyzing step. How to play. A program capable of simultaneously playing a digital stream recorded on an information recording medium and executing interactive content including a document described in a declarative language,
Analyzing, displaying and executing a document written in a declarative language;
A management information analysis step for analyzing whether or not the interactive content uses an event-synchronized playback function implemented in a playback device during special playback of the digital stream;
Causing the computer to execute an event-synchronized playback function when the interactive content is executed when the interactive information is analyzed using the event-synchronized playback function implemented in the playback device by the management information analysis step. A program characterized by   The interactive content management information is prepared for each interactive content, and a file constituting the interactive content is loaded onto a memory of a playback device when a title is selected. The information recording medium according to claim 3, 10, or 17, wherein the information recording medium is a single archive file including management information.

Images