KR100584563B1 - Computer readable medium recoding program code for reproducing Audio-Visual data in interactive mode by preloading markup document - Google Patents

Abstract

The present invention relates to an information storage medium having recorded thereon information for controlling a buffer state of a markup document, a reproduction apparatus and a reproduction method thereof.

In order to perform a method of preloading a markup document according to the present invention and reproducing the AV data in the interactive mode, an information storage medium having recorded thereon program code executable by a computer is provided with buffering for preloading the markup document. First program code for performing; And second program code for outputting information on whether or not buffering of the markup document is completed. Accordingly, when the AV data recorded on the DVD is reproduced and displayed through the markup document, when the markup document associated with the movie screen is to be displayed, the buffering state of the markup document can be examined, thereby preventing physical damage of the disc or When a markup document cannot be buffered due to a network malfunction (disconnection), that is, even when a malfunction such as playback and download delay occurs, an alternative markup document may be utilized or a natural flipping operation may be performed.

Description

A computer readable medium recoding program code for reproducing Audio-Visual data in interactive mode by preloading markup document}

1 is a schematic diagram of an interactive DVD in which AV data is recorded;

FIG. 2 is a reference diagram for explaining a disconnection phenomenon that may occur in the process of playing the interactive DVD of FIG. 1;

3 is a block diagram of a playback device for preloading or deleting;

4 is a reference diagram illustrating a directory structure of a DVD 300 supporting preloading or deleting;

5 is a schematic diagram of a volume space of the DVD 300 supporting preloading or erasing,

6 is a flowchart illustrating a process in which preloading or deletion is performed;

FIG. 7 is an embodiment of preload information interpretation step 602 of FIG. 6;

FIG. 8 is an embodiment of preload execution step (603) of a preload target file of FIG. 6;

FIG. 9A illustrates another implementation of the preload execution step (603) of the preload target file of FIG. 6; FIG.

FIG. 9B is another embodiment of a preload execution step (step 603) of the preload target file of FIG. 6; FIG.

10 is a flowchart illustrating a process of deleting at least one of a preload target file stored in a memory;

FIG. 11 is an embodiment of a deleting execution step (step 1002) of FIG. 10;

12 is a reference diagram for explaining an effect of performing preloading according to the present invention when AV data and HTML document are recorded in the same order as in FIG. 1;

13 and 14 are block diagrams of a playback apparatus according to a preferred embodiment of the present invention;

15 is a conceptual diagram illustrating a process of a buffer manager managing a buffering state of a markup document of an ENAV buffer according to the present invention;

16 is a flowchart for explaining a method of controlling a buffer state executed by a content decoder and a buffer manager according to a preferred embodiment of the present invention.

17 is a schematic diagram of a disc on which AV data and a markup document are recorded according to a preferred embodiment of the present invention;

FIG. 18 is a directory structure diagram of a disk on which AV data and markup documents are recorded as shown in FIG. 17;

19 is a structural diagram showing a volume structure and a file structure of a disk according to FIG. 17;

20 illustrates a process of reproducing markup document data and AV data stored in the disk of FIG. 17 according to the present invention.

The present invention relates to an information storage medium having recorded thereon information for controlling a buffer state of a markup document, a reproduction apparatus and a reproduction method thereof.

DVDs having recorded markup documents along with their contents (hereinafter referred to as "interactive DVD") are sold. Content recorded on an interactive DVD can be played back in two ways. One is a video mode displayed like a normal DVD, and the other is an interactive mode displayed through a display window defined by a markup document. When the interactive mode is selected by the user, the web browser mounted on the PC displays the markup document recorded on the interactive DVD. The display window defined by the markup document displays the content selected by the user.

For example, when a content is a movie having AV data, a movie may be displayed on a display window of a markup document, and various additional information such as a script, a storyline, a photograph of an actor, and the like may be displayed on the remaining portion. The additional information includes an image file or a text file.

1 is a schematic diagram of an interactive DVD in which AV data is recorded.

Referring to Fig. 1, AV data is recorded in an MPEG bitstream and a plurality of markup documents are recorded in a track of an interactive DVD. Here, the markup document refers to a markup resource including various image files, graphic files, and the like inserted into the markup document.

FIG. 2 is a reference diagram for describing a disconnection phenomenon that may occur in the process of playing the interactive DVD of FIG. 1.

Referring to FIG. 2, the state of the buffer memory where the AV data is buffered and the state of the cache memory where the web resource is cached are displayed. Referring to FIGS. 1 and 2, the AV data is loaded into the memory and displayed, and the pickup apparatus searches for, reads, and loads STARTUP.HTM into the cache memory. The loaded STARTUP.HTM is activated. At the same time, ① AV data according to the user's selection is loaded into the buffer memory and then started to be displayed. ② AV data is then loaded and displayed. When the buffering of the AV data is completed, the pickup device jumps to the position where the AV data is recorded and starts buffering. At this time, if the user requests ④ A.HTM, the pickup device stops buffering 3 AV data and searches ④ A.HTM and loads it into the cache memory. In the meantime, since AV data is continuously displayed, the data that can be loaded and displayed in the buffer memory is drastically reduced. ④ A.HTM is activated, ③ AV data is buffered, and then ⑤ AV data is buffered. When the buffering of the AV data is completed, the pickup device jumps to the position where the AV data is recorded. In this case, a phenomenon may occur that all the buffered data is exhausted. That is, in the conventional interactive DVD, when the image of the DVD-Video and the markup document are to be viewed in synchronization with each other (for example, when a specific actor appears, a bio about the actor is displayed), the pickup apparatus is used to display the AV data. The image may be suddenly broken because the buffering must be stopped and the corresponding markup document must be searched and cached.

Accordingly, the applicant has filed on September 19, 2002, Korean Patent Application No. 02-57393, "Information storage medium on which preload information is recorded, its reproducing apparatus, and a reproducing method." Herein, <Preload> is disclosed to prevent content dropout when playing a predetermined content in an interactive mode using a markup document. However, according to the <preload>, there is no problem when preloading the entire preload target file, but if at least a part of the entire preload target file is not properly read, a situation may occur in which all of the preload target files cannot be presented. .

Accordingly, an object of the present invention is to record the control information for controlling the buffering state of the markup document so that the presentation can be properly performed even when at least some of the preload target files are not properly preloaded. An information storage medium, a reproducing apparatus, and a reproducing method thereof are provided.

According to the present invention, there is provided a reproduction apparatus for reproducing AV data in an interactive mode using a markup document, comprising: a buffer for buffering the markup document; And a buffer manager for managing the buffer to preload the markup document, wherein the buffer manager outputs buffering state information of the buffer in response to a report signal.

The playback apparatus further includes a content decoder for interpreting and decoding the markup document and generating the report signal to the buffer manager, wherein the buffer manager informs the content decoder of the buffering status information.

The content decoder generates the report signal using an API, or generates the report signal using an API having at least one of a file path of the markup document and an attribute of the markup document as a parameter. It is preferable to generate the report signal using the [obj] .isCached (URL, resType) API (where URL is a parameter representing a file path of the markup document and resType is an attribute of the markup document). Parameter).

Preferably, the content decoder is informed via an API whether the buffer manager has succeeded, failed, or reading the corresponding markup document.

The API preferably returns 0 if the buffer manager succeeds in reading the corresponding markup document, returns 1 if it fails, and returns 2 if reading.

The buffer manager preferably informs the content decoder of the buffering state information through an API.

On the other hand, according to another aspect of the present invention, the object is a method for preloading the markup document to reproduce the AV data in the interactive mode, the method comprising the steps of: (a) buffering to preload the markup document; And (b) outputting buffering state information of the markup document in response to a report signal.

Step (b) may include: (b1) generating a report signal by a content decoder for interpreting and decoding the markup document to a buffer manager that manages buffering of the markup document; And (b2) the buffer manager notifying the content decoder of the buffering state information.

In the step (b1), the content decoder generates the report signal using an API, or the content decoder uses at least one of a file path of the markup document and an attribute of the markup document as parameters. It is preferable that the report signal is generated by using or the content decoder is the step of generating the report signal by using the [obj] .isCached (URL, resType) API. Parameter indicating a file path, and resType is a parameter indicating an attribute of the markup document).

In the step (b2), the content decoder is notified as the buffering status information whether the reading of the corresponding markup document from the buffer manager is successful, failed, or being read through the API, or the API is the buffer manager. Preferably returns 0 as the buffering state information if the reading of the corresponding markup document succeeds, and returns 2 if the reading fails.

On the other hand, according to another field of the present invention, AV data; A plurality of markup documents for reproducing the AV data in an interactive mode; And control information for retrieving buffering state information for preloading a markup document required for reproducing the AV data in the interactive mode.

The control information is recorded in a predetermined markup document, is recorded using an API for generating a report signal for retrieving the buffering state information, or generates an report signal for retrieving the buffering state information. It is preferably written using the isCached (URL, resType) API (where URL is a parameter representing the file path of the markup document and resType is a parameter representing the attribute of the markup document).

According to another aspect of the present invention, there is provided a reproduction apparatus for reproducing AV data in an interactive mode using a markup document, comprising: a buffer for buffering the markup document; A buffer manager that manages the buffer and preloads the markup document into the buffer; And a content decoder that takes, interprets, and decodes the markup document buffered in the buffer, wherein the buffer manager informs the content decoder whether the buffer has been preloaded. do.

The buffer manager informs the content decoder whether the buffer has completed preloading by using an API, preloads a corresponding markup document into the buffer in response to a fetch signal, or responds to a fetch signal from the content decoder. It is preferable to preload a corresponding markup document to the buffer, or to inform the content decoder whether the preload is completed by a fetch signal from the content decoder.

The content decoder generates the fetch signal using an API, checks whether the buffer has been preloaded to the buffer manager using the API, or checks whether the preload of the corresponding markup document is completed. It is preferable to use the [obj] .allDone API to check whether the preload is completed or not.

More preferably, the [obj] .allDone API returns success if the current success is completed, and otherwise returns failure.

On the other hand, according to another aspect of the present invention, the object is a method for preloading the markup document to reproduce the AV data in the interactive mode, the method comprising the steps of: (a) buffering to preload the markup document; And (b) outputting information on whether or not buffering of the markup document is completed.

Step (a) preferably includes buffering in response to a fetch signal indicating a preload.

The step (b) is performed in response to an API for checking whether the buffering of the markup document is completed, or in response to an [obj] .allDone API for checking whether the buffering of the markup document is completed. desirable.

According to another aspect of the present invention, the above object is a method of preloading a markup document and reproducing the AV data in an interactive mode, the method comprising: (a) indicating a preload of the markup document using a fetch signal; step; And (b) receiving a response indicating whether the preload instruction is successful by the fetch signal.

In the step (a), it is preferable that the content decoder generates an fetch signal to a buffer manager which preloads the markup document using an API.

In the step (b), the buffer manager for preloading the markup document informs the content decoder whether the preload instruction is successful by using an API.

In addition, the object of the present invention is a method of preloading a markup document and playing back AV data in an interactive mode, the method comprising: (a) checking, by a buffer manager, whether a content decoder has completed a current preload using an API; And (b) returning success to the content decoder if the buffer manager has successfully completed the current preload operation using the API; otherwise, returning a failure to the content decoder. It is also achieved by

Preferably, the API is [obj] .allDone API.

On the other hand, according to another field of the present invention, an object of the present invention is to provide an information storage medium in which a program code executable by a computer is recorded for performing a method of preloading a markup document to reproduce AV data in an interactive mode. First program code for performing buffering to preload the markup document; And a second program code for outputting information on whether or not buffering of the markup document is completed.

Preferably, the first program code is executed in response to a fetch signal indicating a preload.

The second program code is executed in response to an API for checking whether the buffering of the markup document is completed or in response to an [obj] .allDone API for checking whether the buffering of the markup document is completed. This is preferable.

In addition, the above object is an information storage medium in which program code executable by a computer is recorded for performing a method of preloading a markup document to reproduce AV data in an interactive mode, by using a fetch signal. First program code indicative of preloading a document; It is also achieved by the information storage medium, characterized in that it comprises a second program code that receives the success or failure of the preload instruction by the fetch signal.

Preferably, the first program code is for a content decoder to generate a fetch signal to a buffer manager that preloads the markup document using an API.

Preferably, the second program code is for a buffer manager that preloads the markup document to inform the content decoder whether the preload instruction is successful or not using an API.

In addition, the above object is to provide a method for preloading a markup document and playing back AV data in an interactive mode, in an information storage medium in which program code executable by a computer is recorded. First program code for confirming with the buffer manager whether the preload has been completed; And second program code for returning success to the content decoder if the buffer manager has successfully completed the current preload operation using the API, and returning a failure to the content decoder. It is also achieved by a storage medium.

Preferably, the API is [obj] .allDone API.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

For the sake of understanding, a brief description will be given of a playback device and method for performing <preload> and <delete> .

3 is a block diagram of a reproducing apparatus for preloading or erasing.

Referring to FIG. 3, a reproducing apparatus is an apparatus that supports an interactive mode that can decode AV data recorded on a DVD 300 to be reproduced as an AV data stream and then display it through a display window defined by a markup document. The reader 1, the first memory 2, the second memory 3, the AV decoder 4, and the presentation engine 5 are included. The screen displayed in the interactive mode is an interactive screen, and refers to a screen in which an AV screen is embedded in the markup screen. The markup screen is a screen on which a markup document is displayed, and the AV screen is a screen obtained by reproducing AV data.

As described below, the presentation engine 5 may include preload information implemented by a link tag, a JavaScript application program interface, or a Java applet API, or a JavaScript API or a Java applet API. It supports link tag extensions, JavaScript, or Java applets so that delete information can be interpreted and executed.

The reading unit 1 reads markup documents or AV data from the DVD 300. The first memory 2 buffers the AV data read by the reading unit 1 as a buffer memory. The second memory 3 caches the preload file received as cache memory. The AV decoder 4 decodes the AV data stored in the first memory 2 and outputs an AV data stream. The presentation engine 5 interprets the preload information included in the read markup document and reads the read unit 1 or the Internet server (not shown) to be preloaded in the second memory 3 according to the interpreted preload information. Request a preload target file. When the preload target file is to be displayed in synchronization with the AV data, the preload target file is read from the second memory 3 so as to be displayed together with the AV data stream output from the AV decoder 4. Further, the deletion information is analyzed and the file to be deleted is deleted from the second memory 3.

In the DVD 300 according to the present embodiment, AV data including audio data or video data is recorded, while a markup document including preload information and / or deletion information is recorded. Furthermore, the preload list file and / or the delete list file can be further recorded.

In the preload list file, a preload list in which file names to be preloaded are listed and memory size information necessary for storing each preload target file are recorded. The preload target file is recorded on the DVD 300 according to the present embodiment as a markup document to be reproduced in synchronization when the corresponding AV data is displayed. However, the preload target file may be stored in an internet server accessible through the internet.

"Preload information" is information for instructing the preload target file to be read and stored in the cache memory. For example, the preload information may be implemented as a link tag in which a path and / or an attribute of the preload list file is inserted. At this time, the link tag is inserted in the head tag. As another example, it is implemented as a JavaScript API or Java Applet API that takes the path and / or attributes of the preload list file as a parameter and calls the preload list file. As another example, it is implemented as a JavaScript API or Java Applet API that takes the path and / or attributes of the preload target file directly and calls the preload target file. In this case, there is no preload list file.

The deletion list file records a deletion list in which location information (file name and path) of files to be deleted is listed. "Delete information" is information for instructing to delete a file to be deleted from the second memory 3. For example, the deletion information may include the location information of the deletion list file as a parameter and be implemented as a JavaScript API or a Java applet API for deleting a deletion target file recorded in the deletion list file. As another example, it is implemented as a JavaScript API or a Java Applet API that directly takes the path and / or attribute of the file to be deleted as a parameter and deletes the file to be deleted. In this case, the delete list file does not exist.

4 is a reference diagram illustrating a directory structure of a DVD 300 supporting preloading or deleting.

Referring to FIG. 4, the root directory is provided with a DVD interactive directory DVD_ENAV in which data for supporting an interactive function such as a DVD video directory VIDEO_TS containing AV data and a markup document is recorded.

VIDEO_TS records VIDEO_TS.IFO in which the header information of the entire video title is recorded, and VTS_01_0.IFO in which the navigation information for the first video title is recorded. Then, VTS_01_0.VOB, AV data constituting the video title, is recorded. VTS_01_1.VOB, ... are recorded. A more detailed configuration is disclosed in the DVD-Video standard "DVD-Video for Read Only Memory Disc 1.0".

In DVD_ENAV, DVD_ENAV.IFO in which navigation information for the entire interactive information is recorded is recorded, STARTUP.HTM designated as a start document is recorded, and STARTUP.PLD, which is a preload list file according to the present embodiment, is provided. In addition, A.HTM, which is a preload target file, or a graphic file A.PNG to be inserted and displayed in A.HTM, is recorded. Other preload target files and files of various formats for being inserted into and displayed therein may be recorded.

5 is a schematic diagram of a volume space of the DVD 300 supporting preloading or erasing.

Referring to FIG. 5, in the volume space of the DVD 300, a control information area in which control information about a volume and a file is recorded, a DVD-Video data area in which corresponding video title data is recorded, and an interactive mode can be reproduced. It contains a DVD-Interactive Data area.

In the DVD-Video data area, files stored in the DVD-Video directory DVD_TS of FIG. 4, that is, VIDEO_TS.IFO, VTS_01_0.IFO, VTS_01_0.VOB, VTS_01_1.VOB, and the like are recorded. In the DVD-Interactive data area, files stored in the DVD interactive directory DVD_ENAV in Fig. 4, that is, STARTUP.HTM, STARTUP.PLD, A.HTM and A.PNG are recorded.

A process of preloading or deleting is performed based on the above configuration.

6 is a flowchart for explaining a process in which preloading or deletion is performed.

Referring to FIG. 6, when the interactive mode is selected, the reader 1 reads an HTML document according to the present embodiment as a markup document recorded on the DVD 300 (step 601), and the presentation engine 5. Interprets the preload information included in the HTML document and requests a preload to the reader 1 or the Internet server (step 602). Thus, the preload target file is stored in the second memory 3, which is the cache memory (step 603).

On the other hand, the reading unit 1 reads out corresponding AV data from the DVD 300 and stores it in the first memory 2 which is a buffer memory (step 604). The AV decoder 4 decodes the AV data stored in the first memory 1 (step 605), while the presentation engine 5 reads the preload target file from the second memory 3 and the AV decoder 4 The AV data stream decoded by the &lt; RTI ID = 0.0 &gt; 1) &lt; / RTI &gt;

FIG. 7 is an embodiment of the preload information interpretation step 602 of FIG. 6.

Referring to FIG. 7, the presentation engine 5 recognizes a path of a preload list file recorded in an HTML document (step 701), and reads a preload list file from the recognized path (step 702). Next, the preload target file recorded in the preload list file is recognized (step 703). Here, recognizing a preload target file means identifying a path of the preload target file and further, an attribute.

FIG. 8 is an exemplary embodiment of a preload execution step (step 603) of the preload target file of FIG. Referring to FIG. 8, the presentation engine 5 calls the preload list file by recognizing the path of the preload list file recorded in the link tag in the head tag of the HTML document (step 801). Next, the presentation engine 5 analyzes the preload list file including the preload tag having the path and the attribute of the preload target file as variables (step 802).

FIG. 9A illustrates another implementation of the preload execution step (step 603) of the preload target file of FIG. 6. Referring to FIG. 9A, the presentation engine 5 is inserted into a body tag to call an API having a path of a preload list file as a parameter to read a preload list file (step 901a). Next, the presentation engine 5 analyzes the preload list file including the preload tag having the path and attributes of the preload target file as variables (step 901b).

FIG. 9B is another embodiment of the preload execution step (603) of the preload target file of FIG. Referring to FIG. 9B, the presentation engine 5 is inserted in a body tag, and directly calls an API having a path and an attribute of a preload target file as a parameter to store the preload target file in memory (step 901b). . In this case, since the attributes of the preload target file can be identified, the presentation engine 5 may process the preload target file according to the attribute and then store the preload target file in the memory.

10 is a flowchart for describing a process of deleting at least one of preload target files stored in a memory.

Referring to FIG. 10, the presentation engine 5 interprets deletion information included in an HTML document (step 1001), and deletes a deletion target file recognized from a deletion list file from the second memory 3, which is a cache memory. (Step 1002). However, as shown in the following source code, the preload list file and the delete list file in this embodiment are implemented with the same single file, that is, STARUP.PLD. Of course, it can be implemented as two files in which the list of preload target files and the list of delete target files are separately recorded.

FIG. 11 is an exemplary embodiment of a deleting execution step 1002 of FIG. 10.

Referring to FIG. 11, the delete target file recorded in the delete list file as a parameter is deleted by the API for deleting from the second memory 3 which is the cache memory (step 1101). Here, "deletion" means not only garbage collection that physically erases the data, but also that the data can be deleted by using a flag or the like while physically leaving the data as it is, or other data can be recorded there. It includes informing.

FIG. 12 is a reference diagram for explaining an effect of performing preload according to the present invention when AV data and an HTML document are recorded in the same order as in FIG. 1.

FIG. 12 shows the occupancy of the first memory 2 in which the MPEG coded AV data is buffered and the state of the second memory 3 in which the web resources are cached. 1 and 12, the AV data is loaded and displayed. Referring to FIG. 1, the reader 1 searches for and reads STARTUP.HTM, and the presentation engine 5 preloads information inserted into STARTUP.HTM. ④ A.htm preload is executed. ④ A.HTM is preloaded into the second memory 3. On the other hand, the loaded STARTUP.HTM is activated. At the same time, ① AV data according to the user's selection is loaded into the first memory 2 and then started to be displayed. ② AV data is then loaded and displayed. When the buffering of the AV data is completed, the reading unit 1 searches for the AV data and jumps to start buffering. At this time, when the user requests? A.HTM, the presentation engine 5 reads and displays? A.HTM, which is preloaded in the second memory 3. That is, the reading unit 1 does not need to stop buffering 3 AV data and search 4 A.HTM from the DVD 300 to load the second memory 3. Therefore, the read part 1 can perform buffering without interruption. However, the data buffered in the first memory 2 may be reduced while the reading unit 1 finishes buffering the ⑤ AV data and jumps to the ⑥ AV data, but the amount of data already buffered is sufficient. There is no shortage. In other words, in DVDs that support interactive mode, even if the video and the HTML document of the DVD-Video are to be viewed in synchronization with each other (for example, when a specific actor appears, the bio about the actor is displayed). Since it is preloaded in the second memory 3, the reading unit 1 does not need to stop buffering the AV data and search and cache the corresponding HTML document.

<Preload> and <deletion> of the preloaded data are described in Korean Application No. 02-57393 filed on Sep. 19, 2002 by the present applicant. Playback apparatus and playback method.

Hereinafter, according to the present invention, a playback apparatus and method capable of appropriately controlling the buffering state of a markup document so that it can be presented at an appropriate level even when at least some of the pre-loaded target files are not properly read. Describes an information storage medium.

13 is a block diagram of a playback apparatus according to a preferred embodiment of the present invention.

Referring to FIG. 13, the playback apparatus is an apparatus supporting an interactive mode similar to the playback apparatus of FIG. 3, and performs an <preload>, and in particular, in order to manage a buffer state of a markup document according to the present invention, an AV buffer. 20, an AV reproduction engine 40, an ENAV buffer 30, and an ENAV engine 50. As shown in FIG.

The AV buffer 20 corresponds to the first memory 2 of FIG. 3 and buffers the AV data obtained from the disk 100 or the network. The AV reproduction engine 40 decodes the AV data buffered in the AV buffer 20 and outputs an AV stream. The ENAV buffer 30 is a cache memory corresponding to the second memory 3 of FIG. 3 and buffers markup documents obtained from the disk 100 or the network. The ENAV engine 50 corresponds to the presentation engine 5 of FIG. 3, performs <preloading>, and controls the buffering state of markup documents buffered in the ENAV buffer 30. Further, the markup document stored in the ENAV buffer 30 is interpreted or decoded so that the AV stream output from the AV reproduction engine 40 is reproduced in the interactive mode.

14 is a detailed block diagram of the ENAV engine 50 of FIG.

Referring to FIG. 14, the ENAV engine 50 has a buffer manager 51 controlling the ENAV buffer 30 therein and a content decoder 52 for interpreting markup documents.

The content decoder 52 has a parsing engine for parsing and parsing markup documents and a browser for fetching markup documents from a network. A markup document is a markup resource that includes markup text data such as HTML, CSS, and JAVASCRIPT, and binary data referenced by the markup document such as image data, audio data, and a Java program. The markup document is retrieved from the disk 100 or the network by the buffer manager 51 in the ENAV engine 50.

The buffer manager 51 manages the buffering state of the markup document by the ENAV buffer 30 in accordance with the present invention in <preloading> or <deleting> the markup document. More specifically, the buffer manager 51 operates according to five kinds of signals input from the content decoder 52.

15 is a conceptual diagram illustrating a process in which the buffer manager 51 manages the buffering state of markup documents in the ENAV buffer 30 according to the present invention.

Referring to FIG. 15, a signal input from the content decoder 52 to the buffer manager 51 includes 1) a fetch signal, 2) a retrieve signal, 3) a release signal, 4) a discard signal, and 5) a report signal.

1) The fetch signal is a signal to preload the markup document to be used in the ENAV buffer 30. If the designated markup document already exists in the ENAV buffer 30, the data is not read from the disk 100 or the network using the I / O manager. The I / O manager refers to a reader (not shown) that reads data from the disk 100 or a network data transceiver (not shown) for importing data from the network. The reader reads a file from the disk 100, and the network data transceiving unit imports or exports predetermined data from the network using the HTTP protocol.

Referring to FIG. 15, the I / O manager determines that an unsolicited I / O is made for an HTTP request and a blocked I / O is used for a file request on a disk. When importing markup documents from the network, the unblocked method of simultaneously importing multiple markup documents at a time is used. When reading markup documents from the disc 100, when a plurality of markup documents are read at a time, the pick-up unit (not shown) provided in the reader has to move several times to the position where the markup documents are recorded. Since deterioration occurs, when a markup document stored in the disk 100 is read, a sequential blocked I / O method of reading the next markup document after the one markup document is read is selected.

2) The retrieve signal is a signal for requesting to bring data from the ENAV buffer 30 to the content decoder 52. Thus, if data is being read from disk or being downloaded from the network, the content is blocking until all the data has been retrieved.

3) The release signal indicates that the retrieved data is not used. Thus, if a markup document is referenced by a retrieve signal five times, a release signal is also generated five times. If the counter goes up every time the retrieve signal is generated, the counter goes down every time the release signal is generated. When the counter corresponding to the markup document becomes 0 (when all retrieved markup documents are released), as described later, when the discard signal is generated, the counter can be deleted immediately from the ENAV buffer 30.

4) The discard signal means that the markup document is no longer used from the ENAV buffer 30 and may be discarded. Therefore, the markup document data specified in accordance with this signal is discarded in the ENAV buffer 30 (not taking up a memory space). However, even if the discard signal is generated by one application, if the retrieve signal is generated for the corresponding markup document by another application and the corresponding release signal is not generated, the corresponding markup document is deleted from the ENAV buffer 30 only when the release signal is generated. do.

5) Is the report signal loaded correctly in the ENAV buffer 30 according to the fetch signal? Or did the error prevent you from reading at least some markup documents? Or it is a signal to check if you are reading markup documents. Also, the location (file name) of the markup document currently in preload, the amount that has been preloaded so far, the amount that should be preloaded in advance, the amount of preloads of all markup documents allocated to the current preload job, and the preload ahead This is a signal to check the amount of markup files remaining.

The API of the script recorded in the markup document to generate the above signal is as follows.

1. [obj] .preload (URL, resType)

1) Content:

It is an API for instructing to read the predetermined preload target files into the ENAV buffer 30 in advance. The parameter used may indicate a preload list file, location information of the preload target file, and further, attributes of the preload target file. This API generates a fetch signal. This function is applicable to all files read from disk (disc: //) or network (http: //).

2) Parameters:

URL =: path of preload list file or path of preload target file

resType =: attribute of the target file

3) Return Value:

If the preload instruction succeeds, it returns 0. If it fails, it returns -1.

4) Example:

navigator.preload ("disc: //dvd_enav/a.htm", "text / xml") // Read the preload target file of "disc: //dvd_enav/a.htm" on the disc. The file is a text file and an xml file.

navigator.preload ("disc: //dvd_enav/a.pld", "xml / preload") // read the target file referenced in the preload list file of "disc: //dvd_enav/a.pld" on disk come. The file is an xml file as a preload file.

2. [obj] .discard (URL, resType)

1) Content

It is an API that deletes indicated files to be deleted in the ENAV buffer 30. The parameter indicates a deletion list file, location information of the deletion target file, and attributes of the deletion target file. This API generates a discard signal.

2) Parameters:

URL =: path of delete list file or path of delete target file

resType =: attribute of the target file

3) Return Value:

If the delete is successful, it returns 0. If it fails, it returns -1.

4) Example:

navigator.discard ("disc: //dvd_enav/a.htm", "text / xml") // If the file to be deleted from "disc: //dvd_enav/a.htm" on the disc is in the ENAV buffer (30) Delete it. The file is a text file and an xml file.

navigator.discard ("disc: //dvd_enav/a.pld", "xml / preload") // remove the file referenced by the list file of "disc: //dvd_enav/a.pld" from disc in cache memory do. The file is an xml file as a list file.

3. [obj] .isCached (URL, resType)

1) Content:

It is an API that checks whether files to be examined are completely read from the ENAV buffer 30. The parameters indicate the survey list file, the location information of the survey target file, and the attributes of the survey file. This API generates a report signal. This function is applicable to all files read from disk (disc: //) or network (http: //).

2) Parameters:

URL =: path of survey list file or path of survey target file

resType =: attribute of the target file

3) Return Value:

Returns 0 if the file to be examined or the file to be examined is successfully read, 1 if the file fails to be read, or 2 if no file has failed to read and at least one file is being read.

4) Example:

navigator.isCached ("disc: //dvd_enav/a.htm", "text / xml") // Check to see if you have finished reading "disc: //dvd_enav/a.htm" on the disc. The file is a text file and an xml file.

navigator.isCached ("disc: //dvd_enav/a.pld", "xml / preload") // read the target files referenced by the list file of "disc: //dvd_enav/a.pld" on disc Investigate if it is complete. The file is an xml file as a list file.

4. [obj] .progressNameOfFile

1) Content:

Attribute value that returns the URI of the target file that is currently in preload.

2) Return Value:

File pathname or URI

5. [obj] .progressLengthOfFile

1) Content:

The amount of preloading so far in the target file currently in preload.

2) Return Value:

The amount expressed in bytes

6. [obj] .remainLengthOfFile

1) Content:

Remaining amount to be preloaded in the future, except for the one currently preloaded in the target file in progress.

2) Return Value:

The amount expressed in bytes

7. [obj] .totalLoadingSize

1) Content:

The total sum of the preload target file sizes specified by the current preload file.

2) Return Value:

The capacity in bytes

8. [obj] .remainLoadingSize

1) Content:

The sum of all remaining amounts that need to be preloaded in the future, except those that have been preloaded up to the current of the specified preload target file in the current preload file.

2) Return Value:

The amount expressed in bytes

9. [obj] .allDone

1) Content:

Whether or not the current playback device has finished preloading

2) Return Value:

True if successful, false completed or false if in progress

The retrieve or release signal is generated each time the corresponding markup document is used. For example, if the content decoder 52 wants to present an image of "disc: //dvd_enav/a.png", it will interpret <img src = "disc: //dvd_enav/a.png" /> and then retrieve A signal is generated to cause the buffer manager 51 to import an image and then present the image on the screen of the display device (not shown). Similarly, the content decoder 52 ends the presentation of the image on the display screen and then generates a release signal.

16 is a flowchart for explaining a method of controlling a buffering state executed by the content decoder 52 and the buffer manager 51 according to the preferred embodiment of the present invention.

17 is a schematic diagram of a disc on which AV data and a markup document are recorded, according to a preferred embodiment of the present invention. FIG. 18 shows a directory structure of a disc on which AV data and a markup document are recorded. 19 shows the volume structure and file structure of the disk according to FIG. 20 shows a sequence in which markup document data and AV data stored in the disk of FIG. 17 are reproduced.

In order to seamlessly play from STARTUP.HTM to A.HTM to D.HTM, STARTUP.PLD is preferably implemented as follows.

<? xml version = "1.0" encoding = "UTF-8"?> <! DOCTYPE PRELOAD PUBLIC "-// DVD // DTD DVD Preload List 1.0 // EN" "http://www.dvdforum.org/enav /dvd-preload-list.dtd "-> <filedef type =" text / xml "src =" disc: //dvd_enav//a.htm "/> <filedef type =" text / xml "src =" disc : //dvd_enav//a.pld "/> <filedef type =" image / png "src =" dvd: //dvd_enav//a1.png "/> <filedef type =" image / png "src =" dvd : //dvd_enav//a2.png "/> <filedef type =" image / png "src =" dvd: //dvd_enav//a3.png "/> <filedef type =" text / xml "src =" disc : //dvd_enav//b.htm "/> <filedef type =" text / xml "src =" disc: //dvd_enav//b.pld "/> <filedef type =" audio / au "src =" dvd : //dvd_enav//b1.au "/> <filedef type =" image / png "src =" dvd: //dvd_enav//b2.png "/> <filedef type =" image / png "src =" dvd : //dvd_enav//b3.jpg "/> <filedef type =" text / xml "src =" disc: //dvd_enav//c.htm "/> <filedef type =" text / xml "src =" disc : //dvd_enav//c.pld "/> <filedef type =" image / png "src =" dvd: //dvd_enav//c1.png "/> <filedef type =" image / png "src =" dvd : //dvd_enav//c2.png "/> <filedef type =" image / png "src =" dvd: // d vd_enav // c3.png "/> <filedef type =" text / xml "src =" disc: //dvd_enav//d.htm "/> <filedef type =" text / xml "src =" disc: // dvd_enav // d.pld "/> <filedef type =" image / png "src =" dvd: //dvd_enav//d1.png "/> <filedef type =" image / png "src =" dvd: // dvd_enav // d2.png "/> </ preload>

With this STARTUP.PLD, the interactive presentation starts with STARTUP.HTM first appearing on the display screen. The following is an example of STARTUP.HTM implemented to operate according to the concept shown in FIG. 15.

<? xml version = "1.0" encoding = "UTF-8"?> <! DOCTYPE html PUBLIC-// DVD / DTD XHTML DVD-HTML1.0 // EN "" http://www.dvdforum.org/enav /dvdhtml-1-0.dtd "> <html> <head> <title> WAR II STARTUP PAGE </ title> <script language =" ecmascript "> <! [CDATA [function onload_handler () {navigator.preload (" disc: //dvd_enav/startup.pld "," xml / preload "); idplayer.subscribeToEvent (10) idplayer.setTrigger (1," 00: 30: 35: 00 ", 1); idplayer.play (); docbody .addEventListener ("dvdevent", idplayer_handler, true);} function idplayer_handler (e) {switch (e.parm1) {case 10: .// trigger event if (e.parm2 == 1) // begin to die {while (navigator.isCached ("disc: //dvd_enav/a.pld", "xml / preload") == 2 navigator.isCached ("disc: //dvd_enav/b.pld", "xml / preload") Navigator.isCached ("disc: //dvd_enav/c.pld", "xml / preload") == 2 navigator.isCached ("disc: //dvd_enav/d.pld", "xml / preload ") == 2); // during // reading; if (navigator.isCached (" disc: //dvd_enav/a.pld "," xml / preload ") == 1) // failed {idplayer. stop (); l ocation.href = "disc: //dvd_enav/discerr.htm"; } // to read c.pld is OK. location.href = "disc: //dvd_enav/a.htm"; // jump to c.htm} break; }}]]> </ script> </ head> <body id = "docbody" onload = "onload_handler ()"> <object style = "position: absolute; left: 150px; top: 100px; width: 370px; height : 250px "data =" dvd: video_ts "id =" idplayer "/> <img style =" position: absolute; left: 167px; top: 375px; width: 170px; height: 60px "src =" disc: // dvd_enav /s1.png "type =" image / png "/> <img style =" position: absolute; left: 370px; top: 375px; width: 170px; height: 60px "src =" disc: // dvd_enav / s2. png "type =" image / png "/> </ body> </ html>

Meanwhile, the following B.HTM constitutes a screen following A.HTM. While B.HTM is being reproduced, markup documents that have been collected for the presentation of A.HTM, that is, markup documents referred to as preload target files in B.PLD, are removed from ENAV buffer 30. B.HTM records the markup documents necessary for the presentation of A.HTM, that is, code that instructs the markup documents referred to as preload target files in A.PLD to be removed from ENAV buffer 30. It is.

<? xml version = "1.0" encoding = "UTF-8"?> <! DOCTYPE html PUBLIC-// DVD / DTD XHTML DVD-HTML1.0 // EN "" http://www.dvdforum.org/enav /dvdhtml-1-0.dtd "> <html> <head> <title> WAR II B.HTM PAGE </ title> <script language =" ecmascript "> <! [CDATA [function onload_handler () {navigator.discard ("disc: //dvd_enav/a.pld", "xml / preload"); // any longer to use A.HTM idplayer.subscribeToEvent (10) idplayer.setTrigger (1, "50:35:00", 1 ); docbody.addEventListener ("dvdevent", idplayer_handler, true);} function idplayer_handler (e) {switch (e.parm1) {case 10: .// trigger event if (e.parm2 == 1) // begin combat {while (navigator.isCached ("disc: //dvd_enav/c.pld", "xml / preload") == 2); // during // reading; if (navigator.isCached ("disc: // dvd_enav / c.pld "," xml / preload ") == 1) // failed {idplayer.stop (); location.href =" disc: //dvd_enav/discerr.htm ";} // to read a.pld is OK.location.href = "disc: //dvd_enav/c.htm"; // jump to c.htm} break;}}]]> </ script> </ head> <body id = "docbody" onload = " onload_handler () "> <object style =" left: 110px; top: 80px; width: 500px; height: 200px "data =" dvd: video_ts "id =" idplayer "/> <img style =" position: absolute; left: 539 px; top: 38 px; width: 140 px; height: 70px "src =" disc: //dvd_enav/b1.png "type =" image / png "/> <img style =" position: absolute; left: 560 px; top: 200 px; width: 120px; height: 50px "src =" disc: //dvd_enav/b2.png "type =" image / png "/> <img style =" position: absolute; left: 610 px; top: 280 px; width: 100px; height: 50px "src =" disc: //dvd_enav/b3.png "type =" image / png "/> </ body> </ html>

On the other hand, the above-described reproduction method in the interactive mode can be created by a computer program. Codes and code segments constituting the program can be easily inferred by a computer programmer in the art. The program is also stored in a computer readable medium, and read and executed by a computer to implement the playback method in the interactive mode. The information storage medium includes a magnetic recording medium, an optical recording medium, and a carrier wave medium.

As described above, according to the present invention, by applying a method and a procedure of knowing the preloaded situation when the content is produced, a network malfunction such as physical damage of the disk or disconnection occurs and thus the entire preloaded file Even if the data is not preloaded and only at least a part of it is preloaded, the presentation can be performed only with the preloaded files, thereby improving playback durability against errors that may occur in playing the content.

In addition, you can use script code to calculate how much you have preloaded so far and how long you need to wait for the preload process to complete in the future, so that content creators can provide users with preload progress information, Can get rid of boredom.

Claims (9)

An information storage medium having recorded thereon a program code executable by a computer for performing a method of preloading a markup document and playing back AV data in an interactive mode, First program code for performing buffering to preload the markup document; And And a second program code for outputting information on whether or not buffering of the markup document is completed after checking the buffering state of the markup document when the buffering state information of the markup document is requested. Information storage medium. The method of claim 1, The first program code is An information storage medium, characterized in that executed in response to a fetch signal indicating a preload. The method of claim 1, The second program code is And executing the response in response to an API indicating to inspect and return the buffering state of the markup document. The method of claim 1, The second program code is The information storage medium, characterized in that executed in response to the [obj] .allDone API to check whether the buffering of the markup document is completed. An information storage medium having recorded thereon a program code executable by a computer for performing a method of preloading a markup document and playing back AV data in an interactive mode, first program code indicating a preload of the markup document using a fetch signal; And a second program code for receiving whether the preload of the markup document was successfully performed in response to the fetch signal. The method of claim 5, The first program code is The content decoder is configured to generate the fetch signal to a buffer manager that preloads the markup document using an API indicating a file path of the markup document as a parameter. Information storage medium characterized by. The method of claim 5, The second program code is The buffer manager which preloads the markup document uses the API to instruct to preload the markup document with the file path of the markup document as a parameter and return whether the preload is successful or not. The information storage medium, characterized in that to inform the content decoder of the success of the preload instruction. An information storage medium having recorded thereon a program code executable by a computer for performing a method of preloading a markup document and playing back AV data in an interactive mode, First program code for confirming with the buffer manager whether the content decoder has currently completed preloading; And And the buffer manager includes second program code for returning success to the content decoder if the current preload operation is successfully completed and otherwise returning failure to the content decoder. The method of claim 8, The first program code and the second program code is the information storage medium, characterized in that for performing the verification and return using the [obj] .allDone API.

Images