CN100545931C - Method and apparatus for reproducing data from data storage medium having information for controlling buffer status of markup document - Google Patents

Abstract

An apparatus for reproducing AV data using a markup document in an interactive mode, comprising: a buffer for buffering the markup document; and a buffer manager for managing the preloading of the markup document and providing buffer status information of the buffer in response to the report signal. The markup document can be provided via a network or from a data storage medium that controls information of a buffer state of the markup document.

Description

Method and apparatus for reproducing data from a data storage medium having information for controlling the buffering status of a markup document

technical field

The present invention relates to a data storage medium with information for controlling the buffering status of a markup document, and more particularly to a method and device for reproducing data from the data storage medium.

Background technique

Interactive DVDs with tagged files to reproduce their contents in an interactive mode have been commercialized in the market. Generally, content recorded on an interactive DVD is reproduced in two modes. One of the two modes is a video mode in which content is displayed in the same manner as data is recorded on a general DVD. Another mode is the interactive mode, in which the content is displayed through a display window defined by the interactive DVD's markup document.

In case the user selects the interactive mode, the web browser installed in the DVD player displays the markup document recorded on the interactive DVD. Displays user-selected content through a display window defined by a markup document. For example, in the case where the content is a movie subtitle, the movie is displayed in a display window on the screen, and various other information such as plot, outline, and photos of actors and actresses may be displayed on the remaining part of the screen. Such other information includes image files and text files.

FIG. 1 shows an interactive DVD on which audio-visual (AV) data is recorded. AV data and a plurality of markup files are recorded on the tracks of the interactive DVD in the form of MPGE bit streams. Here, the markup document may include markup resources including various image files or graphic files to be inserted into the markup document.

FIG. 2 shows discontinuous reproduction of interactive DVD data from FIG. 1. FIG. That is, FIG. 2 shows the occupancy of the buffer memory for buffering AV data and the occupancy of the cache memory for caching network resources.

Referring to FIGS. 1 and 2, a method of loading AV data into a memory and displaying the AV data will be described. The picker device searches the markup document STARTUP.HTM and loads the searched markup document STARTUP.HTM into the cache memory. Thereafter, STARTUP.HTM is activated. At this point, the AV data ① selected by the user is loaded into the buffer memory, and thereafter displayed. Thereafter, AV data ② is loaded into the buffer memory and displayed thereafter. In the case where the buffering of the AV data ② is completed, the pickup device jumps to the position on the interactive DVD where the AV data ③ is recorded and starts buffering the AV data ③. At this point, the user may request a markup document ④A.HTM. In this case, the pickup device stops buffering the AV data ③, searches for the markup file ④A.HTM, and loads the markup file ④A.HTM into the cache memory. When the markup file ④A.HTM is searched for and loaded into the cache memory, the AV data ③ is prohibited from being displayed. Therefore, the amount of data that can be buffered in the buffer memory is drastically reduced as AV data ③ still occupies space in the buffer memory. In the case where the markup file ④A.HTM is activated and the buffering of the AV data ③ is completed, the AV data ⑤ is buffered. Therefore, the pickup device jumps to the position where the AV data ⑥ is recorded. In the above method, all data that has been buffered so far may disappear. In other words, where reproduction of a DVD-Video image from a conventional interactive DVD in synchronization with a markup file is requested, for example, in the context of his or her personal history whenever a particular actor or actress appears on the screen In case display is requested, the pickup device stops buffering AV data and starts searching and caching relevant markup files, and thus images can be reproduced discontinuously.

Contents of the invention

Accordingly, an aspect of the present invention is to provide a data storage medium including control information to control a buffering state of a markup file for reproducing AV data in an interactive mode, and an apparatus and method for reproducing AV data from the data storage medium .

Other aspects and/or advantages of the invention will be set forth in part below and, in part, will be apparent from the description, or may be learned by practice of the invention.

In order to achieve the above and/or other aspects of the present invention, there is provided an apparatus for reproducing AV data using a markup file in an interactive mode, including: a buffer for buffering a markup file; and a buffer manager for managing buffering The buffer marks the document with preload, and outputs buffer status information of the buffer in response to the report signal.

The apparatus may further include a content decoder for interpreting the markup document and outputting a report signal, wherein the buffer manager notifies the content decoder of buffering state information of the buffer in response to the report signal. The content decoder can use an application programming interface (API) to generate the reporting signal.

The API may be used to notify the Content Decoder that the preloading of the markup document has succeeded or failed, or whether the markup document is still being loaded. The API may return a value of 0 if the preload of the markup document was successful, a value of 1 if the preload of the markup document failed, and a value of 2 if the markup document is still being loaded. The buffer manager can use the API to inform the content decoder of the buffering status of the marked document.

The content decoder may generate the report signal using an API including at least one of a file path and an attribute of the markup document as parameters. The API may be an [obj].isCached(URL, resType) API, where URL is a parameter representing the file path of the markup document, and resType is a parameter representing an attribute of the markup document.

The buffer manager may preload the markup document into the buffer in response to the fetch signal. The content decoder may output a fetch signal, and the buffer manager may notify the content decoder whether the command to preload the markup document included in the fetch signal has been successfully received. Content decoders can use APIs to generate fetch signals.

The content decoder can use the API to check whether the preloading of the markup document is complete. API can be [obj].allDone API. The [obj].allDone API may return a value TRUE to the content decoder if preloading of the markup document is complete, and return a value FALSE to the content decoder if preloading of the markup document is not complete.

The buffer manager may transmit the markup document from the buffer to the content decoder in response to the rendering signal.

The content decoder may output a release signal to the buffer manager indicating that the marked document fetched from the buffer in response to the rendering signal is not used.

The buffer manager may delete the marked document from the buffer in response to a discard signal output from the content decoder. A content decoder may generate a discard signal using the discard API.

A content decoder may use the progressNameOfFile API to generate a report signal to determine the filename of the markup document currently being preloaded. A content decoder may use the progressLengthOfFile API to generate report signals to determine how many currently preloaded markup files have been preloaded. Content decoders can use the remainLengthOfFile API to generate report signals to determine how many currently preloaded markup files are still to be preloaded. A content decoder may use the totalLoadingSize API to generate a report signal to determine the total amount of markup documents to be preloaded. A content decoder may use the remainLoadingSize API to generate a report signal to determine how much of the total amount of marked up documents will still be preloaded.

In order to achieve the above and/or another aspect of the present invention, there is provided another device for controlling a buffer for buffering a markup file to reproduce AV data in an interactive mode, including: a buffer manager for managing the buffer to load the markup document, and output buffer information including buffer information of the markup document, wherein the buffer information includes information indicating that the preloading of the markup document was successful, information indicating that the preloading of the markup document failed, and information indicating that the markup document The preloading information is still in progress.

The information of the buffer may also include information indicating whether the command to preload the markup document has been successfully received. The information of the buffer may also include information indicating whether the preloading of the markup document is completed.

In order to achieve the above and/or other aspects of the present invention, there is provided another device for recording and/or reproducing AV data using a markup file in an interactive mode, comprising: an AV buffer for buffering AV data; an AV reproduction engine, for decoding AV data; an Enhanced Audio Video (ENAV) buffer for preloading a markup document to reproduce AV data in interactive mode; an ENAV engine for recognizing the buffer status information of a markup document and decoding the markup document; and A device for obtaining marked-up documents.

The device may use a chunked I/O method in response to obtaining the markup document from the data storage medium and may use a non-blocked I/O method in response to obtaining the markup document from the network.

In order to achieve the above and/or other aspects of the present invention, there is provided a method of reproducing AV data in an interactive mode using a markup file, the method including: buffering the markup file to preload the markup file, and outputting a message of the markup file in response to a report signal Buffer status information. The method may further include reproducing the AV data in an interactive mode using the preloaded markup file.

The output of the buffer status information may include: returning a value of 0 in response to the markup document being preloaded successfully, returning a value of 1 in response to the markup document not being preloaded successfully, and returning a value of 2 in response to the markup document being still being preloaded.

In order to achieve the above and/or other aspects of the present invention, there is provided another method for reproducing AV data in interactive mode using a markup file, the method comprising: issuing a command to preload a markup file using a fetch signal, and receiving an indication indicating whether the Fetches a signal to successfully send the response to the command to preload the markup document. The method may further include reproducing the AV data in an interactive mode using the preloaded markup file.

In order to achieve the above and/or other aspects of the present invention, there is provided another method for reproducing AV data in an interactive mode using a markup file, the method comprising: using an application program interface (API) to inquire whether preloading of the markup file is completed; and A return value of TRUE is received in response to preloading of the markup document being completed, and a return value of FALSE in response to preloading of the markup document not being completed. The method may further include reproducing the AV data in an interactive mode using the preloaded markup file.

In order to achieve the above and/or other aspects of the present invention, there is provided a method of managing a markup file used in reproducing AV data in an interactive mode, the method comprising: buffering the markup file in response to a fetch signal to preload the markup file; outputting a buffering status of the marked document in response to the report signal; staging the marked document for decoding in response to the retrieval signal; and deleting the marked document in response to the discard signal.

The method may also include marking the marked document as a document that is no longer in use in response to the release signal. The method may further include issuing a response indicating whether the command to preload the markup document included in the fetch signal was successfully sent.

The output of the buffer status may include returning a signal indicating whether preloading of the markup document has been completed. The output of the buffer status may include returning a signal indicating whether the preloading of the marked-up document succeeded or failed, or whether the preloading of the marked-up document is still in progress.

In order to achieve the above and/or other aspects of the present invention, there is provided another method of managing a markup file used in reproducing AV data in an interactive mode, the method comprising: generating a fetch signal for preloading a markup file; A report signal for determining the buffer status of the marked document; a retrieve signal for ranking the marked document for decoding; and a discard signal for deleting the marked document.

The method may also include generating a release signal responsive to marking that the document is no longer to be shown. The generating of the report signal may include generating the report signal using an Application Programming Interface (API) to determine one of whether the preloading of the markup document was successful, whether the markup document is still preloading, and whether the preloading of the markup document has been completed or more.

In order to realize the above and/or other aspects of the present invention, another computer-readable medium is provided, which is encoded with operation instructions executed by a computer for implementing one or more methods above.

In order to achieve the above and/or other aspects of the present invention, there is provided a method in a computer system for processing AV data in an interactive mode using a markup document, the method comprising: controlling a content decoder to generate buffer status information for determining the markup document and, in response to the report signal, controlling the buffer manager to issue a response indicating whether the preloading of the markup document succeeded or failed, or whether the preloading of the markup document is still in progress.

In order to achieve the above and/or other aspects of the present invention, there is provided another method in a computer system for processing AV data in an interactive mode using a markup document, the method comprising: controlling a content decoder to generate a preloaded markup document fetching a signal; and in response to the fetching, controlling the buffer manager to issue a response indicating whether the command to preload the marked-up document was successfully received.

In order to achieve the above and/or other aspects of the present invention, there is provided another method in a computer system for processing AV data in an interactive mode using a markup document, the method comprising: controlling a content decoder to generate a preloaded and in response to the query, the control buffer manager sends a response indicating whether the preloading of the marked document is complete.

In order to achieve the above and/or other aspects of the present invention, there is provided a data storage medium including: AV data; a markup file provided to reproduce the AV data in an interactive mode; and control information provided to identify the Buffering status information for loaded markup documents.

The control information may include an application programming interface (API) that generates a reporting signal identifying the buffering status of the markup document. The API may be an [obj].isCached(URL, resType) API that generates a report signal, where URL is a parameter representing the file path of the markup document, and resType is a parameter representing an attribute of the markup document.

The control information may include returning a value of 0 in response to successful preloading of the marked-up document, returning a value of 1 in response to a failed preloading of the marked-up document, and returning a value of 2 in response to the pre-loading of the marked-up document still in progress.

The control information may include APIs that generate signals for issuing commands to preload markup documents. The API may return a response indicating whether the command to preload the markup document was successfully sent using signaling.

The control information may include an API for determining whether preloading of markup documents is completed.

In order to achieve the above and/or other aspects of the present invention, there is provided a data storage medium encoded with program codes executed by a computer for realizing a method for reproducing AV data in an interactive mode using a markup document, the data storage medium comprising: A first program code for performing buffering of the markup document to preload the markup document; and a second program code for outputting information indicating whether the buffering of the markup document is completed.

In order to achieve the above and/or other aspects of the present invention, there is provided another data storage medium encoded with a program code executed by a computer for implementing a method for reproducing AV data in an interactive mode using a markup document, the data storage medium comprising : first program code that issues a command to preload a markup document using a fetch signal; and second program code that notifies whether the command to preload a markup document was successfully issued using a fetch signal.

In order to achieve the above and/or other aspects of the present invention, there is provided another data storage medium encoded with a program code executed by a computer for implementing a method for reproducing AV data in an interactive mode using a markup document, the data storage medium comprising : the first program code, which is used for the content decoder to check whether the buffer manager has completed the preloading of the markup document by using the application program interface (API); and the second program code, which responds to A value TRUE is returned to the Content Decoder on success by the Buffer Manager for preloading of the Markup Document, otherwise a value FALSE is returned to the Content Decoder.

Description of drawings

The above and/or other aspects and advantages of the present invention will become more clear through the following description of the present invention in conjunction with the accompanying drawings, wherein:

FIG. 1 is a diagram showing an interactive DVD on which AV data is recorded;

FIG. 2 is a diagram showing discontinuous data reproduction from the interactive DVD shown in FIG. 1;

3 is a block diagram of an apparatus for reproducing data from a data storage medium performing a preload or delete operation on a marked document;

FIG. 4 is a diagram illustrating a directory structure of a DVD 300 supporting preloading or deletion of marked files;

FIG. 5 is a diagram illustrating a volume space of a DVD 300 supporting preloading or deletion of marked files;

Figure 6 is a flowchart illustrating a method of preloading or deleting a marked document;

FIG. 7 is a flowchart illustrating a method of interpreting preloaded information, ie, operation 602 in FIG. 6;

FIG. 8 is a flowchart illustrating a method of preloading an object file, that is, operation 603 in FIG. 6;

FIG. 9A is a flow chart illustrating another method of preloading an object file, that is, operation 603 in FIG. 6;

FIG. 9B is a flowchart illustrating another method of preloading an object file, that is, operation 603 in FIG. 6;

FIG. 10 is a flowchart illustrating a method of deleting at least one object file preloaded and stored in a memory;

FIG. 11 is a flowchart illustrating a method of deleting a file from a cache memory, namely, operation 1002 in FIG. 10;

FIG. 12 is a diagram showing the impact of the preloading technique described with respect to FIGS. 3 to 11, wherein AV data and HTML documents are recorded onto the interactive DVD in the same manner as in FIG. 1;

13 and 14 are block diagrams of an apparatus for reproducing data from a data storage medium according to an embodiment of the present invention;

FIG. 15 is a diagram illustrating a method of managing a cache state of a marked document in a cache memory using a cache manager according to an embodiment of the present invention;

16 is a flowchart illustrating a method of controlling the buffering state of a markup document using a content decoder and a cache manager according to an embodiment of the present invention;

17 is a diagram showing an interactive DVD on which AV data and markup files are recorded according to an embodiment of the present invention;

FIG. 18 is a diagram showing a directory structure of the interactive DVD shown in FIG. 17;

FIG. 19 is a diagram showing a volume structure and a file structure of the interactive DVD shown in FIG. 17;

as well as

FIG. 20 is a diagram illustrating a method of reproducing a markup document and AV data from the interactive DVD illustrated in FIG. 17 according to an embodiment of the present invention.

Detailed ways

Embodiments of the present invention will now be described in detail with reference to the accompanying drawings, examples of which are shown, in which different reference numerals refer to the same elements throughout. The embodiments are described below in order to explain the present invention by referring to the figures.

An apparatus and method for preloading data and deleting the preloaded data are disclosed by the present applicant in Korean Patent Application No. 2002-57393 filed on September 19, 2002. With the disclosure of that publication being incorporated herein by reference, the following description of that publication is presented to illustrate the present invention.

FIG. 3 is an apparatus for reproducing data from a data storage medium performing a preload or delete operation on a marked document. The device supports an interactive mode in which an AV data stream is reproduced from a data storage medium such as DVD 300 by decoding AV data recorded on DVD 300 and then displaying the decoded data in a display window defined by a markup file. The device includes a reader 1 , a first memory 2 , a second memory 3 , an AV decoder 4 , and a projection engine 5 . During interactive mode, the AV screen is displayed while being embedded in the markup screen. The markup document is displayed in the markup screen, and the AV screen is obtained by reproducing AV data.

Presentation Engine 5 supports extensions to linkmarks, JavaScript, or Java Applets, thereby interpreting and executing preloaded information written using linkmarks, JavaScript application programming interfaces (APIs), or Java Applet APIs and delete information.

Reader 1 reads tag files or AV data from DVD 300. For example, the first memory 2 is a buffer memory, and buffers AV data read by the reader 1 . For example, the second memory 3 is a cache memory, and caches received preloaded files. 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 markup document read by the reader 1, and sends a request to the reader 1 or an Internet server (not shown) based on the interpreted preload information so that the file is preloaded. Loaded into the second memory 3. In order to synchronize the display of the file and AV data, the preloaded file is read from the second memory 3 and displayed together with the AV data stream output from the AV decoder 4 . By interpreting the deletion information, the file is deleted from the second memory 3 .

The DVD 300 includes audio data or AV data, and a tag file with preload information and/or deletion information. Additionally, a preload list file and/or a delete list file may be recorded on the DVD 300.

The preload list file includes a list of files to be preloaded and the size of each file to be preloaded. The files to be preloaded represent markup files reproduced in synchronization with corresponding AV data. Files to be preloaded can be recorded on DVD 300. However, the files to be preloaded can also be stored in an Internet server accessible through the Internet.

The preload information includes commands to read a file to be preloaded from DVD 300, for example, and store the file in cache memory 3 thereafter. Preload information can be specified by using a link tag including a path and an attribute of a preload list file and inserted into a header tag. On the other hand, using the JavaScript application program interface (API) or the Java Applet API that has the path and/or attribute of the preload list file as the function parameter and allows the reproduction of the preload list file, the preload information can be specified. In the case where the preload list file is not necessary, use the JavaScript API or Java Applet API which has as a function parameter the path and/or properties of each file to be preloaded and allows the reproduction of the file, preload Load information can also be specified.

The deletion list file includes a list of files to be deleted, which has location information of each file to be deleted, that is, a file name and a path of each file to be deleted. This delete information represents a command to delete a file from the second storage 3 . Deletion information can be designated using JavaScript API or JavaApplet API having location information of a delete list file as a function parameter and allowing deletion of files listed on the delete list file. On the other hand, in the case where deletion list files are not necessary, deletion information can be specified using JavaScript API or Java Applet API which has position information of each file to be deleted as a function parameter and allows deletion of files .

FIG. 4 is a diagram showing the directory structure of DVD 300. Referring to FIG. 4, the root directory includes a DVD video directory VIDEO_TS having AV data and a DVD interactive directory DVD_ENAV having data supporting an interactive function.

About header information VIDEO_TS.IFO of all video titles recorded on the DVD 300, navigation information VTS_01_0.IFO for the first video title, and AV data VTS_01_0.VOB, VTS_01_1.VOB, .. . is recorded in the DVD-Video directory VIDEO_TS. A detailed description of the structure of the DVD-Video directory VIDEO_TS is disclosed in the DVD-Video standard (DVD-Video for ROM Disc 1.0).

Navigation information DVD_ENAV.IFO and a start file STARTUP.HTM about the entire interactive information are recorded in the DVD interactive directory DVD_ENAV. In addition, a preload list file STARTUP.PLD, a file A.HTM to be preloaded, and a graphic file A.PNG inserted into A.HTM are also provided in the DVD interactive directory DVD_ENAV. Other files to be preloaded or graphic files inserted thereinto may also be recorded in the DVD interactive directory DVD_ENAV.

Figure 5 shows the volume space of DVD 300. Referring to FIG. 5, the volume space includes a control information area including control information for the volume space of the DVD 300 and files recorded on the DVD 300, a DVD-Video data area recorded with video title data, and provided during the interactive mode. to reproduce the DVD-interactive data area of AV data.

Files stored in the DVD-Video directory VIDEO_TS of FIG. 4, ie, VIDEO_TS.IFO, VTS_01_0.IFO, VTS_01_0.VOB, VTS_01_1.VOB, . . . , are recorded in the DVD-Video data area. Files stored in the DVD-interactive directory DVD_ENAV, namely, STARTUP.HTM, STARTUP.PLD, A.HTM, and A.PNG are recorded in the DVD-interactive data area.

FIG. 6 illustrates a method of reproducing data from a data storage medium. In operation 601, the reader 1 reads an HTML document as a markup document recorded on the DVD 300 from the DVD 300 in which the interactive mode is selected. In operation 602, the presentation engine 5 interprets the preload information included in the HTML document, and requests the reader 1 or the Internet server to preload the file. In step 603, the file to be preloaded is stored in the second memory 3 in response to the request.

In operation 604, the reader 1 reads AV data corresponding to the HTML document read in operation 601 from the DVD 300, and stores the read AV data in the first memory 2 as a buffer memory. In operation 605, the AV decoder 4 decodes the AV data stored in the first memory 2 into an AV data stream. In operation 606 , the show engine 5 reads the preloaded file from the second storage 3 , and displays the decoded AV stream in the display window defined by the HTML document read by the reader 1 in operation 601 .

FIG. 7 illustrates a method of interpreting preloaded information, ie, a method corresponding to operation 602 in FIG. 6 . In operation 701, the show engine 5 identifies a path of a preload list file included in an HTML document, and in operation 702 reads the preload list file by following the identified path. In operation 703, the show engine 5 identifies the files to be preloaded listed in the preload list file. Here, the identification of the file to be preloaded means identification of the path and attribute of the file to be preloaded.

FIG. 8 illustrates a method of preloading files, that is, a method corresponding to operation 603 in FIG. 6 . In operation 801, the show engine 5 identifies the path recorded in the link flag of the preload list file, and extracts the preload list file. In operation 802, the show engine 5 interprets the preload list file including the preload flag having the path and attribute of the file to be preloaded as parameters, and performs preloading of the file.

FIG. 9A shows another method for preloading files, that is, a method corresponding to operation 603 in FIG. 6 . In operation 901a, the show engine 5 interprets the API inserted into the body tag using the parameter designating the path of the file to be preloaded, and reads the file to be preloaded using the API. In operation 901b, the show engine 5 performs preloading by interpreting a preloading list file including paths and attributes of files to be preloaded. Since the presentation engine 5 determines the attributes of the files to be preloaded, it can process the files to be preloaded based on their attributes and store the processed files into memory.

FIG. 9B shows another method for preloading files, that is, a method corresponding to operation 603 in FIG. 6 . In operation 901b, the show engine 5 preloads the file to be preloaded into the memory by using the API inserted into the body flag and having the path and attributes of the file to be preloaded as parameters. Since the attribute of the file to be preloaded is recognized, the presentation engine 5 can process the file to be preloaded in consideration of the attribute thereof, and thereafter store the file to be preloaded in the memory.

Figure 10 illustrates a method of deleting one or more preloaded files stored in memory. In operation 1001, the show engine 5 interprets deletion information included in the HTML document, identifies a file to be deleted based on the deletion list file, and deletes the identified file from the second storage 3 in operation 1002. Although the preload list file and delete list file are integrated into a single file, namely STARTUP.PLD, it should be understood that the list of files to be preloaded and the list of files to be deleted could be implemented as two separate files instead of being integrated into a single file.

FIG. 11 illustrates a method of deleting one or more files from the cache memory, ie a method corresponding to operation 1002 in FIG. 10 . A list of files to be deleted may be recorded in a delete list file. In operation 1101, a file is deleted from the second storage 3 using an API having a path of a delete list file as a parameter. Here, the deletion of the file can be the process of physically removing the file from the second storage 3, which will mean that the file can be deleted from the second storage 3, or the file can be overwritten by other data instead of being removed from the second storage 3 A flag to physically remove a file includes a process in the file.

FIG. 12 shows the effect of preloading processing on an interactive DVD in which AV data and HTML documents are recorded in the same manner as in FIG. 1 . That is, FIG. 12 shows the occupancy of the first memory 2 in which MPEG-encoded AV data is buffered and the occupancy of the second memory 3 in which network resources are cached. Referring to FIGS. 1 and 12 , the reader 1 searches and reads STARTUP.HTM, and the show engine 5 interprets the preload information included in STARTUP.HTM so that ④ A.THM is preloaded into the second memory 3 . In the case where STARTUP.HTM loaded into the second memory 3 is activated, ① AV data is loaded into the first memory 2 and thereafter displayed. Thereafter, ② AV data is loaded into the first memory 2 and thereafter displayed. In the case where ② the buffering of AV data is completed, the reader 1 jumps to the position where ③ AV data is recorded and starts buffering ③ AV data. At this moment, in case the user requests ④A.HTM, the presentation engine 5 reads ④A.THM from the second memory 3 and displays ④A.THM. In this case, the reader 1 does not need to stop ③ buffering of AV data, search for the DVD 300 for ④ A.THM, and thereafter load the file ④ A.THM into the second memory 3. Therefore, the reader 1 can continue buffering ③ AV data. In the case where the reader 1 completes buffering of ⑤ AV data and jumps to a position in which ⑥ AV data is recorded, the amount of data buffered in the first memory 2 is reduced. However, the amount of data already buffered in the first memory 2 is sufficient so that lack of buffered data does not occur. In other words, even in the case where an HTML document needs to be displayed synchronously with a DVD-Video image reproduced from an interactive DVD during the interactive mode, the reader 1 does not have to stop buffering of AV data, and the HTML document is not searched and cached thereafter. document. This is because the HTML document has been preloaded into the second memory 3 . For example, simultaneous display may be used where a particular actor or actress' personal history needs to be displayed when he or she appears on screen.

In addition, the above-mentioned apparatus, storage medium and process of preloading data and deleting preloaded data are taught by the present applicant in Korean Patent Application No. 02-57393 filed on September 19, 2002. In the following, a data storage medium and a method and apparatus for reproducing data from the data storage medium according to the present invention will be described.

FIG. 13 shows a block diagram of an apparatus for reproducing data from a data storage medium according to an embodiment of the present invention. The device in Figure 13, similar to the device in Figure 3, reproduces data from a data storage medium. In addition, the device of FIG. 13 supports an interactive mode, performs preloading, and includes an AV buffer 20 , an AV reproduction engine 40 , an enhanced audio video (ENAV) buffer 30 , and an ENAV engine 50 .

The AV buffer 20 corresponding to the first memory 2 of FIG. 3 buffers AV data read from a storage medium such as the disc 100, or from a network such as the Internet. The AV playback engine 40 decodes the buffered AV data to output an AV stream. For example, the ENAV buffer 30 is a cache memory corresponding to the second memory 3 of FIG. 3 . The EVAN buffer 30 buffers markup documents read from the disk 100 or the network. The ENAV engine 50 corresponding to the show engine 5 of FIG. 3 performs preloading, and controls the buffering status of markup documents stored in the ENAV buffer 30 . In addition, the ENAV engine 50 interprets or decodes markup documents stored in the ENAV buffer 30 . The ENAV engine 50 allows the AV stream output from the AV reproduction engine 40 to be reproduced in interactive mode.

FIG. 14 shows a detailed block diagram of the EVAV engine 50 of FIG. 13 according to an embodiment of the present invention. The ENAV engine 50 includes a buffer manager 51 that controls the ENAV buffer 30 and a content decoder 52 that interprets markup documents.

Content decoder 52 may include an interpretation engine that parses and interprets the markup document, and a browser that retrieves the markup document from the interpretation engine and/or the network. Here, the markup document corresponds to Java programs referred to by various markup resources such as image data, audio data, or markup documents ranging from markup text data written in HTML, CSS, or JAVASCRIPT to binary data. Markup files are fetched from disk 100 or the network by buffer manager 51 in ENAV engine 50 .

Regarding preloading or deletion of markup documents, the buffer manager 51 manages the buffering status of markup documents in a predetermined manner according to the present invention. According to an embodiment of the present invention, the buffer manager 51 responds to a signal output from the content decoder 52 . For example, buffer manager 51 may operate differently in response to different signals output from content decoder 52 . For example, signaling may include a fetch signal, a reproduce signal, a release signal, a drop signal, and a report signal.

FIG. 15 shows the buffer manager 51 that manages the buffering status of markup documents processed by the ENAV buffer 30 according to an embodiment of the present invention. For example, 5 different signals, namely fetch signal, reproduce signal, release signal, discard signal, and report signal, may be input from content decoder 52 into buffer manager 51 .

The fetch signal is used to preload the markup document into the ENAV buffer 30. In case a markup file has been preloaded into ENAV buffer 30, the I/O manager may prevent the corresponding markup file from being read from disk or network. The I/O manager represents a reader (not shown) that reads data from a disk, or a network data receiver/transmitter (not shown) that receives data from a network. The reader reads files from the disk, and the network data receiver/sender receives predetermined data from and/or transmits predetermined data to the network using, for example, HTTP protocol.

Referring to FIG. 15, the I/O manager may be configured to operate in the following manner. In cases where HTTP requests are issued, the I/O manager uses non-blocked I/O. Where requests are issued for files on disk, the I/O manager uses block I/O. To render markup documents from the network, the I/O manager takes a non-chunked approach to receive multiple markup documents at a given time. However, where multiple marked documents are read from the disc at a given time, a picker device (not shown) in the reader is required to move between positions where marked documents are recorded. Therefore, the speed of reading the corresponding markup document can be reduced several times. Therefore, sequential block I/O processing is employed where multiple markup files are to be read from disk, wherein multiple markup files are read sequentially from disk.

The reproduction signal is used to issue a request to transfer data from the ENAV buffer 30 to the content decoder 52 . In a case where predetermined data is read from a disc or downloaded from a network, the content decoder 52 may be blocked from operating until the reading or downloading of predetermined data is completed.

The release signal indicates that the predetermined data transferred from the ENAV buffer 30 to the content decoder 52 in response to the above-mentioned reproduction signal is no longer necessary. For example, in the case where the markup document is scheduled to be referenced 5 times in response to the reproduction signal, the release signal is generated 5 times. The count value is increased when the reproduction signal is generated, and is decreased when the release signal is generated. In the case where the count value corresponding to the predetermined markup document reaches 0, that is, in the case where all reproduced markup documents are released, the released markup document is deleted from the ENAV buffer 30 in response to a discard signal described below.

The discard signal indicates that predetermined markup documents stored in the ENAV buffer 30 may be deleted from the ENAV buffer 30, for example, because they will no longer be used. Accordingly, the predetermined markup document is deleted from the ENAV buffer 30 in response to the drop signal.

According to an aspect of the present invention, in a case where a markup document is associated with another application and a reproduction signal has been generated but a release signal has not been generated, even in a case where a discard signal has been generated by a predetermined application, the markup document is cannot be deleted from the ENAV buffer 30.

For example, the report signal is used to check whether the markup files read in response to the fetch signal were successfully loaded into the ENAV buffer 30, whether at least some of the corresponding markup files could not be read due to an error, and/or or whether the corresponding markup document is being read.

According to an embodiment of the present invention, the above and/or other signals of the present invention are provided using, for example, APIs corresponding to scripts written in markup documents. The following, without limitation, are examples of APIs for generating various signals utilized in the present invention.

<[obj].preload(URL, resType)>

describe:

This API is used to preload a file, or to read a file and store it in the ENAV buffer 30 . The parameters of the API include the location information of the preload list file or the location information of the file to be preloaded, and the attributes of the file to be preloaded. This API generates fetches and is applicable to all files readable from disc (disc://) or network (http://). It should be understood that the API can be used to preload files.

parameter:

URL=: the path of the preload list file or the path of the file to be preloaded

ResType=: attribute of the file to be preloaded

return value:

In case the preload command was executed successfully, a value of 0 is returned. Otherwise, the value -1 is returned. For example, in case the preload command was not successfully executed, a value of -1 is returned.

example:

The Navigator.preload("disc://dvd_enav/a.htm", "text/xml") request refers to a request to load a file from "disc://dvd_enav/a.htm". The files to be preloaded are text files written in XML.

Navigator.preload("disc://dvd_enav/a.pld", "xml/preload") request refers to loading the files listed in the preload list file from "disc://dvd_enav/a.pld" request. The files listed in the preload list file are preload files written in XML.

<[obj].discard(URL, resType)>

describe:

This API is used to delete files from the ENAV buffer 30 . The parameters of the API include the location information of the deletion list file or the location information of the file to be deleted, and the attributes of the file to be deleted. This API generates a discard signal. It should be understood that the API can be used to delete files.

parameter:

URL=: the path of the delete list file or the path of the file to be deleted

ResType=: attribute of the file to be deleted

return value:

In case the delete command was executed successfully, a value of 0 is returned. Otherwise, the value -1 is returned. For example, in case the delete command was not successfully executed, a value of -1 is returned.

example:

The Navigator.discard("disc//dvd_enav/a.htm", "text/xml") request refers to a request to delete a file from "disc//dvd_enav/a.htm". The file is a text file written in XML.

The Navigator.discard("disc//dvd_enav/a.pld", "xml/preload") request refers to deleting from the cache the files listed in the delete list file "disc//dvd_enav/a.pld" request. This file is a list file written in XML.

<[obj].isCached(URL, resType)>

describe:

This API is used to check, for example, whether the file has been loaded into the ENAV buffer 30 successfully. The parameters of the API include location information of a list file or location information of a file to be searched/checked, and attributes of a file to be checked. This API generates report signals and can be applied to all files read from disc (disc://) or network (http://). It should be understood that the API can be used to check the status of a file.

parameter:

URL=: path to the list file or the path to the file that will be checked

ResType=: attribute of the file to be checked

return value:

In case the file listed in the list file or the file to be checked was successfully stored/loaded into the ENAV buffer 30, a value of 0 is returned. In the case where the checked file was not successfully loaded, ie, the preloading of the file failed, a value of 1 is returned. A value of 2 is returned in case files are still being read/loaded, or in case every failure occurs during preloading of files and at least one file is still being read/loaded.

example:

The Navigator.isCached("disc//dvd_enav/a.htm", "text/xml") request refers to a request to check whether the "disc//dvd_enav/a.htm" file has been stored. The file is a text file written in XML.

The Navigator.isCached("disc//dvd_enav/a.pld", "xml/preload") request refers to a request to check whether the file indicated by the list file "disc//dvd_enav/a.pld" has been stored. This file is a list file written in XML.

<[obj].progressNameOfFile>

describe:

This API is used to return, for example, the Universal Resource Identifier (URI) of the file currently being preloaded.

Return value: file path or URI.

<[obj].progressLengthOfFile>

describe:

This API indicates how many files currently being preloaded have been preloaded.

Return value: the value expressed in bytes.

<[obj].remainLengthOfFile>

describe:

This API indicates how many files currently being preloaded will be preloaded.

Return value: the value expressed in bytes.

<[obj]. totalLoadingSize>

Description: This API indicates eg the total amount of files to be preloaded.

Return value: the value expressed in bytes.

<[obj].remainLoadingSize>

describe:

This API indicates eg how much of the total amount of files to be preloaded is still to be processed.

Return value: the value expressed in bytes.

<[obj].allDone>

describe:

This API indicates, for example, whether a device for reproducing data from a data storage medium has completed preloading.

Return value: In the case that the device has successfully completed preloading, the API returns a value of TRUE (true). Otherwise, the return value is FALSE (false). For example, in case preloading has not been completed, ie, in case preloading has failed or is in progress, the value FALSE is returned.

As described above, according to an aspect of the present invention, a reproduction signal and a release signal are generated when a corresponding markup document is used. For example, the content decoder 52 uses the display device ( not shown) displays the image "disc//dvd_enav/a.png". Also, in the case where the presentation of the corresponding image is completed, the content decoder 52 generates a release signal.

FIG. 16 illustrates a method of controlling a buffer state performed by the content decoder 52 and the buffer manager 51 according to an embodiment of the present invention. In operation 1601, the content decoder 52 generates a fetch signal in response to a preload command. In operation 1602, the buffer manager 51 starts reading the specified markup document in response to the fetch signal. At operation 1603, the content decoder 52 determines, for example, whether all of the markup document has been read, and/or generates a report signal to determine, for example, the buffering status of the markup document. In operation 1604, in the event of an error, the error is handled. In operation 1605, the buffer manager 51 returns a signal representing the buffering status of the markup document in response to the report signal. In operation 1606, the content decoder 52 generates a retrieval signal to use the markup document. In operation 1607, the buffer manager 51 transmits the designated markup document to the content decoder 52 in response to the retrieval signal. In operation 1608, the content decoder 52 presents the designated markup document. In operation 1609, the content decoder 52 generates a release signal in case the specified markup document is no longer used. In operation 1610, the buffer manager 51 decrements the current count value by 1 to represent, for example, usage of a corresponding one/more of the specified markup documents. In operation 1611, the content decoder 52 generates a discard signal to delete the specified markup document. In operation 1612, the buffer manager 51 deletes the specified markup document from the ENAV buffer 30 in response to the drop signal.

FIG. 17 shows a data storage medium such as a disc on which AV data and markup files are recorded according to an embodiment of the present invention. The data storage medium also includes control information for identifying buffer status information for markup documents to be preloaded. For example, the start file STARTUP.HTM includes a preload list file STARTUP.PLD to seamlessly reproduce files ranging from A.HTM to D.HTM.

The control information may include APIs that return a value of 0 in response to successful preloading of the markup document, return a value of 1 in response to preloading failure of the markup document, and return a value of 2 in response to preloading of the markup document still in progress. The control information may also include APIs that generate signals to issue commands to preload markup documents. This API may return a response indicating whether the command to preload the markup document was successfully sent. The control information may also include an API used to determine whether the preloading of the markup document is complete. This API may return a value TRUE in response to the preloading of the markup document being completed and a value of FALSE in response to the preloading of the markup document not being complete.

FIG. 18 shows a directory structure of the disc in FIG. 17 according to an embodiment of the present invention. Referring to FIG. 18, reference files of the start file STARTUP.PLD are included in the directory DVD_ENAV.

FIG. 19 shows a volume structure and a file structure of the disc in FIG. 17 according to an embodiment of the present invention. Referring to FIG. 19, a reference file of STARTUP.PLD is recorded in the DVD interactive data area.

FIG. 20 shows a predetermined order in which markup files and AV data recorded on the disc in FIG. 17 are reproduced. For example, at the beginning of each scene, use the IsCashed API to check whether the reference file to the preload list file corresponding to that scene has been read. In a case where the reading of the reference file has been successfully completed, the HTM document is read and reproduced. Thereafter, use the Discard API to delete marked documents that have been reproduced.

For example, in order to seamlessly reproduce data from STARTUP.HTM, A.HTM, and D.HTM, STARTUP.PLD is defined 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://dvd_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>

By using the above STARTUP.PLD, STARTUP.HTM is displayed on the screen, indicating the start of the interactive show. An example of STARTUP.HTM processed by the device in Fig. 15 is as follows.

<? 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 eventif(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")==2||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(); location.href="disc://dvd_enav/discerr.htm"; }//to read c.pld is OK.location.href="disc://dvd_enav/a.htm"; //jump to c.htm }br eak;} }]]></script></head><body id="docbody" 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>

According to an aspect of the invention, the markup documents A.HTM and B.HTM may include images. According to an aspect of the present invention, with reference to Figures 18 and 20, a markup file required for a show, such as A.HTM, that is, a markup file in A.PLD and called a file to be preloaded, is downloaded from ENAV after the show. Buffer 30 is deleted.

<? 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.HTMidplayer.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 eventif(e.parm2==1)//begin combat{while(navigator.isCached(″disc://dvd_enav/c.pld″,”xml/ preload")==2); //during//readng; 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" style="left:110px;top:80px;width:500px ;height:200px"data="dvd:video_ts"id="idplayer"/><img style="position:abs olute; left:539px; top:38px; width:140px; height:70px "src = "disc://dvd_enav/b1.png" type = "image/png"/><img style = "position:absolute; left :560px; top:200px; width:120px; height:50px″src="disc://dvd_enav/b2.png"type="image/png"/><img style="position:absolute; left:610px; top:280px; width:100px; height:50px "src = "disc://dvd_enav/b3.png" type = "image/png"/></body></html>

It should be understood that systems using the present invention also include permanent or removable storage, such as magnetic and optical disks, RAM, ROM, carrier media, etc., on which the processes and data structures of the present invention can be stored and distributed. Operations may also be distributed via, for example, downloading over a network such as the Internet.

While certain embodiments of the present invention have been shown and described, it will be understood by those skilled in the art that changes may be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined herein. as defined in the appended claims and their equivalents.

Industrial availability

For example, according to the present invention, when content is processed using a method that enables determination of the preloaded content state, even in cases where a physical defect of the disk or a connection interruption results in an unsuccessful or incomplete preloading of the file into the buffer , or you can project images using only preloaded files. Therefore, the reliability of reproduced content is improved. That is, according to an aspect of the present invention, even if a markup document is not completely preloaded or an error occurs during preloading of the markup document, AV data can be projected in an appropriate manner in an interactive mode.

Claims (57)

1. An apparatus for reproducing AV data using a markup file in an interactive mode, comprising: Buffer, for buffering markup documents; and The buffer manager manages the buffer to preload the markup document, and outputs buffer status information of the buffer in response to the report signal. 2. The apparatus of claim 1, further comprising a content decoder for interpreting the markup document and outputting a report signal, wherein the buffer manager notifies the content decoder of buffering status information of the buffer in response to the report signal. 3. The apparatus of claim 2, wherein the content decoder generates the report signal using an Application Programming Interface (API). 4. The apparatus of claim 3, wherein the API is for notifying the content decoder that the preloading of the markup document has succeeded or failed, or whether the markup document is still being loaded. 5. The device of claim 4, wherein the API returns a value of 0 if the preloading of the markup document is successful, a value of 1 if the preloading of the markup document fails, and a value of 1 if the markup document is still in the Returns a value of 2 if loaded. 6. The apparatus of claim 2, wherein the content decoder generates the report signal using an API including at least one of a file path and an attribute of the markup document as a parameter. 7. The apparatus of claim 2, wherein the content decoder generates the report signal using [obj].isCached(URL, resType) API, wherein URL is a parameter representing the file path of the markup document, and resType is a parameter representing Parameters for the properties of the markup document. 8. The apparatus of claim 2, wherein the buffer manager notifies the content decoder of the buffering status of the markup document using the API. 9. The apparatus of claim 1, wherein the buffer manager preloads the markup document into the buffer in response to the fetch signal. 10. The apparatus of claim 9, further comprising a content decoder that interprets the markup document and outputs a fetch signal, wherein the buffer manager includes in the fetch signal whether a command to preload the markup document has been successfully executed Receive notification content decoder. 11. The apparatus of claim 10, wherein the content decoder generates the fetch signal using the API. 12. The apparatus of claim 11, wherein the buffer manager notifies the content decoder whether the command has been successfully received using the API. 13. The apparatus of claim 1, further comprising a content decoder interpreting the markup document, wherein the content decoder checks whether preloading of the markup document is completed using an API. 14. The device of claim 13, wherein the API is the [obj].allDone API. 15. The device of claim 14, wherein the [obj].allDone API returns a value true to the content decoder if preloading of the markup document is complete, and if preloading of the markup document is not complete In case return value false to content decoder. 16. The apparatus of claim 1, further comprising a content decoder that interprets the markup document, wherein the buffer manager transmits the markup document from the buffer to the content decoder in response to the reproduction signal. 17. The apparatus of claim 1, further comprising a content decoder for interpreting the markup document, wherein the content decoder outputs a release signal to the buffer manager representing the markup document fetched from the buffer in response to the reproduction signal Not used. 18. The apparatus of claim 17, wherein the content decoder outputs the release signal to the buffer manager in response to the markup document being no longer displayed in the screen of the display device. 19. The apparatus of claim 1, further comprising a content decoder that interprets the markup document, wherein the buffer manager deletes the markup document from the buffer in response to a drop signal output from the content decoder. 20. The apparatus of claim 19, wherein the content decoder generates the drop signal using a drop API. 21. The apparatus of claim 2, wherein the content decoder uses the progressNameOfFile API to generate the report signal to determine the filename of the markup document currently being preloaded. 22. The device of claim 2, wherein the content decoder uses the progressLengthOfFile API to generate a report signal to determine how many markup files currently being preloaded have been preloaded. 23. The device of claim 2, wherein the content decoder uses the remainLengthOfFile API to generate a report signal to determine how many markup files currently being preloaded are still to be preloaded. 24. The apparatus of claim 2, wherein the content decoder uses the totalLoadingSize API to generate a report signal to determine the total amount of markup documents to be preloaded. 25. The device of claim 2, wherein the content decoder uses the remainingLoadingSize API to generate a report signal to determine how much of the total amount of marked up documents is still to be preloaded. 26. An apparatus for controlling a buffer for buffering a markup file to reproduce AV data in an interactive mode, comprising: a buffer manager for managing a buffer to preload a markup file, and outputting buffer information including the markup file The buffer information, where the buffer information includes: A message indicating that the preloading of the markup document was successful; a message indicating that preloading of the markup document failed; and Indicates that preloading of markup documents is still in progress. 27. The apparatus of claim 26, wherein the buffer manager outputs the information of the buffer using an API. 28. The apparatus of claim 26, wherein the information of the buffer further includes information indicating whether the command to preload the markup document has been successfully received. 29. The apparatus of claim 26, wherein the information of the buffer further includes information indicating whether the preloading of the markup document is completed. 30. An apparatus for recording and/or reproducing AV data using a markup file in an interactive mode, comprising: AV buffer for buffering AV data; AV reproduction engine for decoding AV data; Enhanced Audio Video ENAV buffer for preloading markup files to reproduce AV data in interactive mode; an ENAV engine for identifying buffer state information for a markup document and decoding the markup document; and Means for obtaining marked up documents. 31. The device of claim 30, wherein the device uses a chunked I/O method in response to obtaining the markup document from the data storage medium and uses a non-blocked I/O method in response to obtaining the markup document from the network . 32. A method of reproducing AV data in an interactive mode using a markup document, the method comprising: buffer markup documents to preload markup documents, and Buffering status information of the marked document is output in response to the report signal. 33. The method of claim 32, further comprising generating a report signal to determine buffer status information for the markup document. 34. The method of claim 33, wherein the generating of the report signal comprises generating the report signal using an Application Programming Interface (API). 35. The method of claim 34, wherein the API includes at least one of a file path and an attribute of the markup document as a parameter. 36. The method of claim 34, wherein the API is used to determine whether buffering of the markup document for preloading the markup document succeeded or failed, or whether the markup document is still being buffered. 37. The method of claim 33, wherein generating the report signal includes generating the report signal using the [obj].isCached(URL, resType) API, where URL is a parameter representing the file path of the markup document, and resType is a parameter representing an attribute of the markup document. 38. The method of claim 32, wherein outputting buffer status information includes returning a value of 0 in response to the markup document being successfully preloaded, returning a value of 1 in response to the markup document being unsuccessfully preloaded, and returning a value of 1 in response to The markup document is still being preloaded and returns a value of 2. 39. The method of claim 32, further comprising reproducing the AV data in an interactive mode using a preloaded markup file. 40. A method of reproducing AV data in an interactive mode using a markup document, the method comprising: Use signal fetch to issue a command to preload the markup document; and Receives a response indicating whether the command to preload the markup document was successfully sent using the signal fetch. 41. The method of claim 40, wherein issuing the command to preload the markup document includes using an application programming interface (API) to generate a fetch signal. 42. The method of claim 40, wherein the receiving of the response comprises receiving, using the API, a response indicating whether the command included in the signal fetch has been successfully received. 43. The method of claim 40, further comprising reproducing the AV data in an interactive mode using a preloaded markup file. 44. A method of reproducing AV data in an interactive mode using a markup document, the method comprising: Querying whether the preloading of the markup document is complete using the Application Programming Interface API; and A return value of TRUE is received in response to completion of preloading of the markup document, and a return value of FALSE in response to incomplete preloading of the markup document. 45. The method of claim 44, wherein the API is [obj].allDone API. 46. The method of claim 44, further comprising reproducing the AV data in an interactive mode using a preloaded markup file. 47. A method of managing a markup file used in reproducing AV data in an interactive mode, the method comprising: buffering the markup document to preload the markup document in response to fetching the signal; outputting a buffering status of the marked-up document in response to the report signal; rating the marked document for decoding in response to the retrieval signal; and The marked document is deleted in response to the drop signal. 48. The method of claim 47, further comprising marking the marked document as a document no longer in use in response to the release signal. 49. The method of claim 47, further comprising issuing a response indicating whether the command to preload the markup document included in the signal fetch has been successfully sent. 50. The method of claim 47, wherein outputting the buffer status includes returning a signal indicating whether preloading of the markup document has been completed. 51. The method of claim 47, wherein outputting the buffer status includes returning a signal indicating whether the preloading of the markup document succeeded or failed, or whether the preloading of the markup document is still in progress. 52. A method of managing a markup file used in reproducing AV data in an interactive mode, the method comprising: generate fetch signals for preloading marked-up documents; generating a reporting signal for determining the buffering status of the marked-up document; generating a retrieval signal for grading the marked document for decoding; and Produces a discard signal for deleting marked documents. 53. The method of claim 52, further comprising generating a release signal responsive to marking that the document is no longer to be projected. 54. The method of claim 52, wherein generating the report signal comprises generating a report signal using an application programming interface API to determine whether the preloading of the markup document was successful, whether the markup document is still being preloaded, and whether the markup document One or more of the preloads have already been completed. 55. A method in a computer system for processing AV data in an interactive mode using a markup document, the method comprising: controlling the content decoder to generate a report signal for determining buffer status information for the marked-up document; and In response to the report signal, the control buffer manager issues a response indicating whether the preloading of the marked-up document succeeded or failed, or whether the preloading of the marked-up document is still in progress. 56. A method in a computer system for processing AV data in an interactive mode using a markup document, the method comprising: controlling the content decoder to generate a fetch signal for preloading the marked-up document; and In response to the signal, the control buffer manager issues a response indicating whether the command to preload the marked-up document was successfully received. 57. A method in a computer system for processing AV data in an interactive mode using a markup document, the method comprising: controlling the content decoder to generate a query for determining whether preloading of the marked-up document is complete; and In response to the query, the control buffer manager issues a response indicating whether preloading of the marked document is complete.

Images