KR100553881B1 - Optical recording medium containing preload information, apparatus and method for reproducing therefor - Google Patents

Abstract

The present invention relates to an information storage medium having preload information recorded therein, a playback apparatus and a playback method thereof.

An information storage medium according to the present invention comprises AV data; And preload information for instructing to preload a preload target file corresponding to the AV data before the AV data is reproduced, wherein the preload target file is synchronously reproduced or displayed when the content data is displayed. It is characterized in that the file to be reproduced at the request of. As a result, the AV screen is not interrupted when the AV data is reproduced in the interactive mode.

Description

Optical recording medium containing preload information, apparatus and method for reproducing therefor}

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 apparatus according to a preferred embodiment of the present invention;

4A is a reference diagram illustrating an example of a file structure of a DVD 300;

4B is a reference diagram showing another example of the file structure of the DVD 300;

5A is a schematic diagram of a volume space of the DVD 300,

5B is another schematic diagram of a volume space of the DVD 300;

6 is a reference diagram for explaining a preloading method according to the present invention from a user interface perspective;

7 is a flowchart illustrating a reproducing method according to a preferred embodiment of the present invention;

8 is an example of implementation of the preload information interpretation step 702 of FIG.

FIG. 9 is an embodiment of a preload execution step (703) of the preload target file of FIG.

FIG. 10A illustrates another implementation of the preload execution step (703) of the preload target file of FIG. 7; FIG.

FIG. 10B is another embodiment of the preload execution step (703) of the preload target file of FIG.

11 is a flowchart for explaining a method of preloading when a size of a preload target file is included in a preload list file;

12 is a flowchart for describing a method of deleting at least one of preloaded preloaded files;

FIG. 13 is an embodiment of a delete execution step (1202) of FIG. 12; FIG.

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

15 is a partial detailed view of the playback device of FIG. 3;

16 to 17A, 17B, 17C, 17D, 17E, and 17F are memory maps for explaining a method of managing the memory management table 31 and the data space 32 through preload / delete or garbage collection;

18 is a state diagram in which AV data is loaded and consumed in the first memory 2,

19 is a data alignment diagram of a preload list file and a corresponding preload target file,

20A is a schematic view of the disc, FIG. 20B is a partial detail view of FIG. 20A,

21 is a state diagram of the first memory 2 and the second memory 3 according to the above-described example;

22 is a flowchart for explaining a recording method according to a preferred embodiment of the present invention.

The present invention relates to an information storage medium having preload information recorded therein, a reproduction apparatus and a reproduction method thereof. More particularly, the present invention relates to an information storage medium having a markup document having preload information together with contents, and a reproduction device thereof. It relates to a regeneration method.

DVDs having recorded markup documents together with 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 embedded in 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 content selected by the user is displayed on the display window defined by the markup document.

For example, when the content is a movie having AV data, the movie may be displayed on the display window of the markup document, and various additional information such as a script, a storyline, a photograph of the actor, and the like may be displayed on the remaining part. 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 in which the AV data is buffered and the state of the cache memory in which markup resources are 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, an object of the present invention is to provide an information storage medium, a reproducing apparatus, and a reproducing method, in which a disconnection phenomenon does not occur when a predetermined content is reproduced on a display window defined by a markup document.

Another object of the present invention is to record a markup document such that a predetermined markup document to be reproduced is loaded into the cache memory or deleted from the cache memory so that a truncation does not occur when the predetermined content is reproduced through the markup document. To provide an information storage medium, a reproducing apparatus and a reproducing method thereof.

Still another object of the present invention is to provide information that can be preloaded more efficiently by providing attribute information on a preload target file in advance so that a disconnection does not occur when playing predetermined content on a display window defined by a markup document. A storage medium, a reproducing apparatus and a reproducing method thereof are provided.

It is still another object of the present invention to provide a method for ensuring that a situation in which the data remaining in the memory is insufficient even when preloading is performed during the reproduction of the content does not occur.

Yet another object of the present invention is to provide a method of managing a memory so that stable preloading and erasing is performed.

The object is, in accordance with the invention, an AV data comprising audio and / or video data; And a markup document that displays the decoded and reproduced AV data and has preload information inserted therein for instructing to read and store in the memory a preload target file for AV data that is guaranteed to be seamlessly reproduced. The target file is achieved by an information storage medium, characterized in that the file to be reproduced in synchronization with the content data or to be reproduced at the request of the user.

The information storage medium further includes navigation data for the AV data, wherein the AV data is decoded into an AV data stream with reference to the navigation data.

It is effective to further include a preload list file in which the preload target file is recorded, and at least one preload target file.

The preload information may be implemented as a link tag in which position information of the preload list file is recorded and inserted into a head tag, or as an API (Application Program Interface) having position information and attributes of the preload list file as parameters. It is preferred to be implemented. The preload list file records the location information and the attributes of the preload target file.

The object may also include AV data comprising audio data or video data; And a markup document in which the preload information is inserted which instructs to display the AV data decoded and reproduced in the AV data stream, and to read and store in the memory a preload target file for AV data guaranteed to be seamlessly reproduced. It is also achieved by an information storage medium, characterized in that it comprises.

The preload information is implemented as an application program interface (API) having location information and attributes of the preload list file as parameters, and the location information is represented by a path of the preload list file, and the memory is included in the path. Preferably, a resource locator indicating any one of the information storage medium and the Internet server is added.

Further, the markup document may include a deletion list file in which a deletion list is recorded; And deletion information for instructing deletion of the deletion target file recorded in the deletion list from the memory.

According to another aspect of the present invention, the above object is a method for reproducing AV data recorded on an information storage medium in an interactive mode, comprising: (a) interpreting preload information included in a read markup document; (b) calling a preload target file for AV data guaranteed to seamless playback according to the analyzed preload information and storing it in a cache memory; (c) reading the AV data and storing the AV data in a buffer memory; And (d) reading the AV data from the buffer memory, reading the preload target file from the cache memory, and playing the file in an interactive mode.

Preferably, the step (a) is to identify the path and attributes of the preload target file (a1), and the step (a1) recognizes the path of the preload list file recorded in the link tag in the head tag. More preferably.

Step (b) may include: (b1) reading the preload target file from the identified path; And (b2) processing and storing the read preload target file according to the identified attribute.

According to another aspect of the present invention, an object of the present invention is to provide an interactive mode for reproducing AV data recorded on an information storage medium, the apparatus comprising: a reading unit configured to read a markup document or AV data; A memory for storing the received preload target file or AV data; An AV decoder for decoding AV data stored in the memory; And requesting that a preload target file according to preload information for seamlessly guaranteed AV data, which is interpreted by interpreting preload information included in the read markup document, to be first stored in the memory, and then the AV data. And a presentation engine for requesting that is read and stored in the memory, and reading the preload target file from the memory and displaying the file with the AV data output from the AV decoder. .

The memory includes a buffer memory for storing the AV data; And a cache memory for storing the preload target file.

The presentation engine may determine a path and an attribute of a preload target file based on the preload information, call a preload target file from the identified path, and store the preload target file in the cache memory so as to correspond to the attribute.

The presentation engine requests the preload target file from the reader or the Internet server, and the presentation engine compares the size of the remaining space of the cache memory with the size of the preload target file to determine the remaining size of the cache memory. If the size of the space is smaller, an error event is generated. When the resource locator pointing to the cache memory is added to the path of the preload list file, the presentation engine requests a corresponding preload target file from the cache memory. If the preload target file does not exist in the cache memory, an error event is generated.

On the other hand, according to another field of the present invention, the above object is a method for performing a preload, (a) finding a read speed of the preload target file; (b) finding a condition for buffering to be performed so that the corresponding AV data is reproduced without interruption; And (c) performing a preload at a point in time meeting the found condition.

A method of recording data on an information storage medium, the method comprising: (a) recording a preload target file; (b) finding a read speed of the recorded preload target file; (c) finding a condition for buffering to be performed so that the corresponding AV data is reproduced without interruption; And (d) recording source code for preloading to be performed at a time point that satisfies the determined condition.

Also, a memory management method for preloading, the method comprising: (a) recording a memory management table including state information of a preload target file; And (b) deleting the preload target file based on the state information.

The memory management method for preloading may further include (c) performing garbage collection on the preload target file based on the state information.

The step (b) preferably includes displaying as status information that the file is not in use and can be deleted when the preload target file is completed.

Step (c) may include: (c1) physically deleting the preload target file if the preload target file is not in use and can be deleted; And (c2) indicating that the deleted preload target file is deleted and does not exist, and (c3) rearranging another preload target file recorded in the memory. More preferably.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. As used herein, a "markup document" refers to a markup resource that covers not only a markup document but also a file inserted or linked to the markup document. Further, "~ .HTM" is used to mean a document written in markup languages such as XML and SGML that can be displayed by a web browser as well as HTML.

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

Referring to FIG. 3, the playback apparatus can decode and reproduce AV data recorded on the DVD 300 according to the present embodiment as an AV data stream, and then display it through a display window defined by a markup document. A device supporting the apparatus includes a reader 1, a first memory 2, a second memory 3, an AV decoder 4, and a presentation engine 5. 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 target 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 or to be reproduced at the request of the user. However, the preload target file may be stored in an internet server accessible through the internet.

"Preload information" according to the present invention is information for instructing a preload target file to be read and stored in a 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.

An attribute or property is information that acts as a sort of Multi-Purpose Internet Mail Extensions (MIME) header. In other words, the property informs the data structure of the preload target file. Knowing the data structure allows you to process the file more efficiently. For example, in the case of a web file, if the tags are interpreted in advance when preloading, the file can be displayed immediately without going through the file analysis procedure. In case of image file, header information can be removed and saved when preloading. This makes efficient use of the memory space and speeds up the search for the file. Audio files can be resampled and saved at a higher rate when preloaded. In the case of font files, only necessary font resources can be extracted and stored. By knowing the attributes of the preload target file, you can execute the preload more flexibly and efficiently.

The path tells you where the file was written. A resource locator may be added to the paths of the preload list file and the preload target file. Indeed, the markup resource may reside in a server that is recorded in the DVD 300 or cached in the second memory 3 or connectable via the Internet. Thus, the resource locator is divided into a DVD resource locator pointing to the DVD 300, a cache resource locator pointing to the second memory 3, and an internet resource locator pointing to the Internet server. Resource locators may be indicated as follows in the order mentioned.

disk0: //

lid: //

http: //

Therefore, the path used when the preload target file A.HTM recorded in the DVD 300 is called is indicated by disk0: //DVD_ENAV/A.HTM, and is preloaded cached in the second memory 3. When calling the target file A.HTM, it is displayed as lid: //DVD_ENAV/A.HTM. When calling the preload target file A.HTM stored on the Internet server, http://www.samsung.com/DVD_ENAV It is displayed as /A.HTM. Furthermore, when multiple DVDs 300 are loaded, the resource locators of each DVD may be represented as disk0: // (or dvd: //), disk1: //, disk2: //, disk3: //, ... have.

When the resource locator is added to the path indicating the location of the preload target file If the target file does not exist at the location indicated by the resource locator, the presentation engine 5 generates an error event and terminates the preload operation. However, if no resource locator is added, the second memory 3 is searched first, and if the second memory 3 does not exist, the DVD 300 is searched.

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, the path and / or attributes of the file to be deleted are directly parameterized and implemented as a JavaScript API or a Java applet API that deletes the file to be deleted. In this case, the delete list file does not exist.

4A and 4B are reference diagrams showing the file structure of the DVD 300 according to the present embodiment.

Referring to Fig. 4A, 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.

However, referring to FIG. 4B, when the preload information included in the markup document is directly implemented as an API for preloading the preload target file with the path and attributes of the preload target file as parameters, the preload list file STARTUP.PLD does not exist.

5A and 5B are schematic diagrams of a volume space of the DVD 300 according to the present embodiment.

Referring to FIG. 5A, 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. Contains the 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.

Similarly, referring to FIG. 5B, when the preload information included in the markup document is directly implemented as an API that takes the path and attributes of the preload target file as parameters and preloads the preload target file, the preload list file STARTUP .PLD does not exist.

6 is a reference diagram for explaining the preloading method according to the present invention from the perspective of an interactive screen (a markup screen and an AV screen).

Referring to Fig. 6, there is shown an AV screen obtained by reproducing AV data, and an interactive screen displayed when the AV data is reproduced in the interactive mode. The interactive screen is composed of an AV screen and a markup screen.

The AV data can be divided into data that is guaranteed to be seamless and data that is not. For example, when there is AV data constituting a war movie title divided into 1 part, 2 parts, and 3 parts, 1 part is the default part constituting the war movie title and 2 parts and 3 parts are each different story by user's choice. The first part is data that is guaranteed to be seamlessly reproduced, and the second and third parts are called data which is not guaranteed to be seamlessly reproduced from the perspective of the first part. However, if 2 or 3 copies are selected and playback starts, 2 and 3 copies must be seamlessly played. Therefore, when the second part is selected, the first part and the third part are data for which seamless reproduction is not guaranteed from the viewpoint of the second part, and when the third part is selected, the first part and the second part are data for which the seamless reproduction is not guaranteed.

The markup documents required to play Part 1 in interactive mode are STARTUP.HTM and A.HTM, and the markup documents required to play Part 2 or 3 in interactive mode are OTHER1.HTM and OTHER2.HTM, respectively. The preload target file to be preloaded based on the preload information according to the present invention indicates a markup document necessary for reproducing AV data for which seamless reproduction is guaranteed in the interactive mode. That is, the preload target files are STARTUP.HTM and A.HTM when one copy is played, the preload target file is OTHER1.HTM when two copies are played, and the preload target file is OTHER2.HTM when three copies are played. .

Referring to the reproduction method according to the present invention by the above configuration as follows.

7 is a flowchart for explaining a playback method according to a preferred embodiment of the present invention.

Referring to FIG. 7, when the interactive mode is selected, the reader 1 reads the HTML document according to the present embodiment as a markup document recorded on the DVD 300 (step 701), 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 702). Thus, the preload target file is stored in the second memory 3 which is the cache memory (step 703).

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 704). The AV decoder 4 decodes the AV data stored in the first memory 1 (step 705), 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 X) is displayed on the display window defined by the HTML document (step 706).

8 is an example of implementation of the preload information interpretation step 602 of FIG. 7.

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

FIG. 9 is an example of implementation of a preload step (703) of the preload target file of FIG. Referring to FIG. 9, 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 901). 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 902).

FIG. 10A illustrates another implementation of the preload execution step (703) of the preload target file of FIG. Referring to FIG. 10A, 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 1001a). 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 1001b).

FIG. 10B is another example of the preload execution step (703) of the preload target file of FIG. Referring to FIG. 10B, the presentation engine 5 is inserted into 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 a memory (step 1001b). . 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.

FIG. 11 is a flowchart for describing a method of preloading when a size of a preload target file is included in a preload list file.

Referring to FIG. 11, when the interactive mode is selected, the reader 1 reads the HTML document according to the present embodiment as a markup document recorded on the DVD 300, and the presentation engine 5 reads the HTML document. The preload information included in the file is interpreted, and the read unit 1 reads the preload list file (step 1101). The presentation engine 5 interprets the preload list file (step 1102). The presentation engine 5 recognizes the size of the preload target file and compares it with the remaining capacity of the cache memory (step 1103). If the size of the preload target file is smaller than the remaining capacity of the cache memory, the preload is executed (step 1104). If the size of the preload target file is larger than the remaining capacity of the cache memory, an error event is generated and terminates as it is (step 1105).

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

Referring to FIG. 12, the presentation engine 5 interprets deletion information included in an HTML document (step 1201), and deletes a deletion target file recognized from a deletion list file from the second memory 3, which is a cache memory. (Step 1202). 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. 13 is an exemplary embodiment of the deleting execution step 1202 of FIG. 12.

Referring to FIG. 13, the delete target file recorded in the delete list file as a parameter of the delete list file is executed by an API for deleting from the second memory 3 which is the cache memory (step 1301). 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 involves notifying.

On the other hand, the source code of the above-described STARTUP.HTM and STARTUP.PLD may be configured as follows.

※ STARTUP.HTM example 1

<? 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> STARTUP PAGE </ title> <link rel =" preload "src =" dvd: // dvd_enav \ startup.pld "OnError =" err_preload ( ) "OnAbort =" err_preload () "> <!-If preloading is failed, call err_preload-> <script language =" ecmascript "> <!-Function html_discard () {navigator.Discard (" dvd: // dvd_enav \ startup.htm ", 0);} function err_preload () {navigator.Discard (" ", 2); if (! navigator.Preload (" dvd: // dvd_enav \ startup.pld ", 1)) {alert ("insufficient memory. it will chanage interactive mode to raw mode.") DvdVideo.SetVideoMode ()}} </ script> </ head> <body bgcolor = # ffffff OnUnload = "html_discard ()"> <!-if document unload, call html_discard-> <object height = "50%" width = "60%" data = "dvd:"> <script language = "ecmascript"> <!-DvdVideo.Play () </ script> <a href="lid:\\dvd_enav\a.htm"> click to preloaded A.HTM </a> </ body> </ html>

In the source code above, preload information implemented through the link tag inserted in the head tag is inserted. In addition, the deletion information implemented by the JavaScript API is inserted.

※ Example 2 of STARTUP.HTM

? 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> STARTUP PAGE </ title> script language =" ecmascript ">!-Function html_discard () {navigator.Discard (" dvd: // dvd_enav \ startup.htm " , "text / xml");} function err_preload () {navigator.Discard ("", ""); if (! navigator.Preload ("dvd: // dvd_enav \ startup.pld", "text / preload &amp;amp;amp;quot;)) {alert ("insufficient memory. it will chanage interactive mode to raw mode."); DvdVideo.SetVideoMode (); }} / script> / head> body bgcolor = # ffffff OnUnload = "html_discard ()"> <!-if document unload, call html_discard-> object height = "50%" width = "60%" data = " dvd: "> script language =" ecmascript ">!-if (! navigator.Preload (" dvd: // dvd_enav \ startup.pld "," text / preload &amp;amp;amp;quot;)) {err_preload () ;} DvdVideo.Play (); / script> a href = "lid: \\ dvd_enav \ a.htm"> click to preloaded A.HTM </a> / body> / html>

The above source code contains the deletion information and preload information implemented by the JavaScript API.

※ Example 1 of STARTUP.PLD

<? 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 "-> <preload cachesize =" 128KB "> <filedef type =" text / xml "src =" dvd: //dvd_enav//a.htm "/> <filedef type =" image / png "src =" dvd: //dvd_enav//a.png "/> </ preload>

The above source code is an XML document that records the size of the preload target file and the path and properties of the preload target file.

Meanwhile, the API for preload / discard used in the above-described source code will be described in more detail as follows.

Navigator.Preload (URL, flag)

It is an API that reads pre-loaded target files to the second memory 3 in advance. The parameter used indicates location information of the preload list file and the preload target file.

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

flag =: 1 for preload list file, 0 for preload target file

Return value:

* 111 Returns true if preload succeeds, false otherwise.

Yes:

 navigator.Preload ("http://www.holeywood.com/tom.pld", 1) // on the internet

// Preload target files which read and instruct preload list file of "http://www.holeywood.com/tom.pld"

// read ahead into cache memory

2. navigator.Preload (URL, resType)

It is an API that reads pre-loaded target files to the second memory 3 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.

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

resType =: attribute of the target file

Return value:

Returns true if preload succeeds, false otherwise.

Yes:

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

navigator.Preload ("http://www.holeywood.com/tom.htm", "text / html") // read the file "http://www.holeywood.com/tom.html" on the Internet come. The file is a text file and an xml file.

3. navigator.Discard (URL, flag)

It is an API for deleting the indicated deletion target files in the second memory 3. The parameter indicates location information of the deletion list file and the deletion target file.

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

flag =: 1 for delete list file, 0 for delete target file, 2 to delete all contents loaded in cache memory

Return value:

Returns true if the delete is successful, false otherwise.

Yes:

navigator.Discard ('http://www.holeywood.com/tom.htm',0) // on the internet

 // If the delete target file indicated by 'http://www.holeywood.com/tom.htm' exists in the cache memory, delete it.

4. navigator.Discard (URL, resType)

It is an API for deleting the indicated deletion target files in the second memory 3. The parameter indicates a deletion list file, location information of the deletion target file, and attributes of the deletion target file.

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

resType =: attribute of the target file

Return value:

Returns true if the delete is successful, false otherwise.

Yes:

navigator.Discard ("dvd: //dvd_enav/a.htm", "text / xml") // delete the target file of "dvd: //dvd_enav/a.htm" from the dvd if it is in cache memory . The file is a text file and an xml file.

navigator.Discard ("dvd: //dvd_enav/a.pld", "application / preload") // delete the target file of "dvd: //dvd_enav/a.pld" from dvd if it is in cache memory . The file is a list file to be deleted.

navigator.Discard ("http://www.holeywood.com/tom.htm", "text / xml &amp;amp;amp;quot;) //" http://www.holeywood.com/tom. htm "deletes the file to be deleted if it exists in cache memory. It is a text file and an xml file.

Meanwhile, in the above-described embodiment, only the API implemented by JavaScript is described, but the same result can be obtained by using a Java applet or the like.

FIG. 14 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.

In Fig. 14, the state of the first memory 2 in which MPEG coded AV data is buffered and the state of the second memory 3 in which markup resources are cached are shown. 1 and 14, the AV data is loaded and displayed. Referring to FIG. 1, the reading unit 1 searches for and reads STARTUP.HTM, and the presentation engine 5 includes preload information inserted in 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. That is, for DVDs that support interactive mode, even if the DVD-Video image and the HTML document must be viewed in synchronization with each other (for example, when a specific actor appears, the bio about that 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.

Hereinafter, a method of managing the second memory 3 to perform stable preloading / deleting and a situation in which the situation in which the content remaining in the first memory 2 is exhausted in performing the preloading will not occur. Explain the specific method.

15 is a partial detailed view of the playback device of FIG. 3.

Referring to FIG. 15, a memory management table area 31 and a data area 32 are provided in the second memory 3. The memory management table 31 is a table in which information for managing / recording / deleting data recorded in the data area 32 is recorded. Preloaded markup documents and the like are recorded in the data area. The presentation engine 5 may be classified into a JavaScript analysis engine 51 and an execution module 52. The execution module 52 is composed of a preload / deletion module 521 and a garbage collection module 522. The garbage collection module 522 will be described later.

In this embodiment, the JavaScript analysis engine 51 calls an API written in JavaScript. The preload / delete module 521 or garbage collection module 522 performs preload / delete or garbage collection.

16 to 17 are memory maps illustrating a method of managing the memory management table 31 and the data space 32 through preload / delete or garbage collection.

Referring to FIG. 16, the memory management table 31 includes state information of a preload target file, a path in which a preload target file is stored, a data pointer, and data size information. "in use" indicates whether it is currently in use or not, "discardable" indicates whether it can be deleted, "URI" indicates path information, "data pointer" indicates the starting address of the data, and "size" indicates the size of the data. Indicates. It can be seen that a.htm, c.htm and b.htm are currently loaded in the data area 32.

Referring to FIG. 17A, if you are currently using a.htm and preloaded b.htm, c.htm, and d.htm, since a.htm is currently in use, the "in use" value of a.htm is 1 and the remaining files are Since it is not open, its "in use" value is all zeros.

Referring to FIG. 17B, since the use of a.htm is terminated and b.htm is in use, the "in use" value of a.htm is changed to 0, and the "in use" value of b.htm is changed to 1.

Referring to FIG. 17C, garbage collection is performed on a.htm. When garbage collection is performed, a.htm is deleted from the data area 32 and b.htm, c.htm and d.htm are rearranged. The "data pointer" value in a.htm is represented by -1. This means that the file does not exist in the data area 32.

Referring to Fig. 17D, it indicates that f.htm is in use. f.htm is placed in place of a.htm in Fig. 16C in the memory management table 31, and the 'data pointer' value actually points to the start address where f.htm is recorded.

Referring to Fig. 17E, deletion of b.htm, c.htm, and d.htm is performed. Thus, the "discardable" values of b.htm, c.htm, and d.htm all change to one.

Referring to FIG. 17F, garbage collection for b.htm, c.htm, and d.htm is performed. Therefore, the values of "data pointer" of b.htm, c.htm, and d.htm are all -1. B.htm, c.htm, and d.htm recorded in the data area 32 are all deleted, and the remaining f.htm is rearranged.

As such, the second memory 3 can be properly managed through preload / deletion and garbage collection.

18 is a state diagram in which AV data is loaded and consumed in the first memory 2.

Referring to FIG. 18, the AV data is not filled but is consumed while the jump is performed to the angle block or the like in the section a, and thus the data is reduced at the speed Vo. An angle block refers to a block in which data photographing the same scene at various angles is recorded. One angle is selected and played back, and the data shot at the remaining angles is skipped, which inevitably causes jumps in the angle block. When the jump is completed and the AV data is read, the data is filled again. As recorded in the section b, if the AV data is continuously read at the speed Vr and consumed at the speed Vo, the AV data is actually filled with the speeds Vr-Vo. When preloading of the markup document is performed in the interval c, the reading unit 1 must stop reading the AV data and preload the corresponding markup document, so that the data is reduced at the speed Vo. In the section d, the AV data is filled again, so as in the section b, the AV data is filled at the speed Vr-Vo. The dotted line represents the minimum amount of AV data that should be filled in.

Based on this, in order to properly exhibit the buffering function of the first memory 2 while performing the preload according to the present invention (to prevent data shortage of the first memory from occurring), in the period c in which the preload is performed, It can be seen that the amount of data remaining must be greater than the amount of data being reduced.

On the other hand, in order to ensure seamless reproduction, the reading unit 1 should read the preload target file as continuously as possible. Therefore, the file system of the playback apparatus has a structure in which one PLD file nests another PLD file so that the preload target file, that is, the PLD file, can be read continuously. Data alignment is effective.

20A and 20B are schematic views of the disc 300 in which the PLD file of Fig. 18 is recorded.

20A and 20B, the reading unit 1 buffers the AV data VTS_01_1.VOB in the second memory 3 and then preloads the target files A.HTM, A1.JPG, specified in the preload list file A.PLD. And preload A2.JPG, further preload up to the preload list file B.PLD, and then buffer VTS_01_1.VOB again.

Here, Tj means access time for the preload target file. That is, Tj = Tj1 + Tj2 is the sum of the time taken to jump from VTS0_1.VOB to the preload target file A1.JPG and the time Tj2 taken to jump to VTS_01_1.VOB after preloading the B.PLD file again. De represents the data size of the preload target file. That is, De = De1 + De2 + De3 is the sum of the data size De1 of A.HTM, the data size De2 of A1.JPG, and the data size De3 of A2.JPG. Tk represents the internal jump time when the preload target file is read. That is, as Tk = Tk1 + Tk2, Tk1 indicates the time taken to jump from A1.JPG to A2.JPG, and Tk2 indicates time taken to jump from A2.JPG to B.PLD.

On the other hand, the relationship between the access distance of the AV data recorded on the disc and the access time can be set as follows. N is the number of sectors.

access distance (sector) 0 to 210 to 5000 to 10,000 to 15,000 to 20,000 over 20,000 access time (msec) 1.4 x N 310 360 390 410 1500

According to the present invention, the condition for preventing the shortage of AV data in the first memory 2 is expressed by the following equation.

Vo: The speed at which the AV data exits from the first memory 2 or

    The data consumption rate of the AV decoder 4,

Tp: time taken to perform preload in interval c,

Vr: Speed of reading data from disk 300

tN_ecc: Total number of ECC blocks to read before loading preload target file

Ta: Total time for jumping in angle blocks

Bs: Minimum data size to be reserved in the first memory 2 (here memory size 221 sectors specified in the DVD-Video standard 1.0)

In Equation 1, Vo × Tp represents the amount of data that is reduced due to preloading in a section c. On the other hand, tN_ecc × 2048 × 8 × 16 is the length of the data (number of sectors) read in the section b, and Vr is the data read rate, so tN_ecc × 2048 × 8 × 16 / Vr is the time of the section b. That is, (Vr-Vo) × (tN_ecc × 2048 × 8 × 16 / Vr) represents the amount of data increased in the interval b. On the other hand, Vo x Ta represents the amount of data that is reduced due to the angle block jump or the like in the interval a. Bs represents the minimum amount of data to be secured. On the other hand, Tp means 2xTj + De / Vr + Tk. The meanings of Tj, De, Vr and Tk have been described above.

The time Tp required to preload the preload target files specified in the preload list files A.PLD, B.PLD, and C.PLD of FIG. 18 was calculated, and the following results were obtained.

Vr = 22 Mbps,

Target files of A.PLD (De = 1611KB): Tp = 3600msec (= 1500msec × 2 + 1611KB × 8/22000000 + 0)

Target files of B.PLD (De = 2685KB): Tp = 4000msec (= 1500msec × 2 + 2685KB × 8/22000000 + 0)

Target files of C.PLD (De = 269KB): Tp = 3100msec (= 1500msec × 2 + 269KB × 8/22000000 + 0)

If the target file of A.PLD, the target file of B.PLD, and the target file of C.PLD must be opened in order during the playback of VTS_01_1.VOB, the following value should be calculated.

Vo value in the buffering section of VTS_01_1.VOB before reading target files of A.PLD = Va

Vo value in the buffering section of VTS_01_1.VOB before reading the target files of B.PLD = Vb

Vo value in the buffering section of VTS_01_1.VOB before reading the target files of C.PLD = Vc

Furthermore, if there is no jump like an angle block in each section and Bs is 221 sectors (s14 ECC block), and the number of ECC blocks and Va, Vb, and Vc are calculated in relation to each section, the AV screen does not break. You can find out where the target files for PLD, B.PLD, and C.PLD can be loaded.

For example, assuming Va = 8 Mbps, Vb = 6 Mbps, and Vc = 4 Mbps, tN_ecc can be obtained using Equation 1. If you get it,

At least 187 ECC blocks must be loaded before the target files of A.PLD can be loaded.

At least 140 ECC blocks must be loaded before reading the target files of B.PLD.

At least 72 ECC blocks must be loaded before the target files of C.PLD can be loaded.

21 is a state diagram of the first memory 2 and the second memory 3 according to the above-described example.

Referring to Fig. 21, when STARTUP.HTM is activated, the data amount of the first memory 2 increases at the speed of Vr-Va. When preloading the target files of A.PLD is performed, the data amount of the first memory 2 decreases at the speed of Va. When preloading of target files of A.PLD is completed and A.HTM is activated, the amount of data increases at the speed of Vr-Vb. Again, when preloading of the target files of B. PLD is performed, the data amount of the first memory 2 decreases at the speed of Vb. When preloading of target files of B.PLD is completed and B.HTM is activated, the data amount increases at the speed of Vr-Vc. On the other hand, the reason why the amount of data is drastically reduced at the point where the second memory 3 has been preloaded is because garbage collection is performed because the deletion of the previously preloaded target file is required.

22 is a flowchart for explaining a recording method according to a preferred embodiment of the present invention.

Referring to FIG. 22, the content producer finds out a read speed of a preload target file (step 2201). The condition for buffering is performed in the first memory 2 so as to reproduce the corresponding AV data without interruption (step 2202). The conditions are as described above in detail. The source code for preloading is recorded so that the preloading is performed at a time point matching the found condition (step 2203). That is, by loading the minimum time of AV data after the API is called and performing the preload, the AV memory is buffered in the first memory 2 so that the preload can be performed without interruption of the AV screen.

As described above, according to the present invention, when the AV data recorded on the information storage medium such as a DVD is reproduced and displayed through the markup document, the information storage medium having the markup document recorded thereon to prevent the disconnection of the moving picture screen, A reproducing apparatus and a reproducing method thereof are provided. Furthermore, since the attributes of the preload target file and the delete target file can be known, more efficient preloading and deletion can be performed.

Claims (42)

delete delete Content data including audio and / or video data; And And a markup document in which preload information is inserted to instruct to preload a preload target file corresponding to the content data before the content data is reproduced. The preload target file is a file to be reproduced synchronously or at the request of a user when the content data is displayed, The markup document is an information storage medium, characterized in that the content data decoded and reproduced is embedded. The method of claim 3, The preload target file is an information storage medium, characterized in that a file required for playing back the content data in which the seamless playback is guaranteed in an interactive mode. The method of claim 3, Further comprising navigation data for the content data, And the content data is decoded into a content data stream with reference to the navigation data. The method of claim 3, And at least one preload target file. The method of claim 3, And a preload list file in which the preload target file is recorded. The preload information is an information storage medium, characterized in that implemented as a tag that can refer to the position information of the preload list file. The method of claim 7, wherein And the tag is a link tag inserted in the head tag. The method of claim 7, wherein The location information is represented by a path of the preload list file, wherein the path is added with a resource locator indicating any one of a memory, the information storage medium, and an internet server. The method of claim 3, The preload information is an information storage medium, characterized in that implemented as an API (Application Program Interface) having the position information of the preload list file as a parameter. The method of claim 10, The API is an information storage medium, characterized in that the JavaScript API or Java Applet API. The method of claim 10, The location information is represented by a path of the preload list file, wherein the path is added with a resource locator indicating any one of a memory, the information storage medium, and an internet server. The method of claim 10, And the preload list file includes location information and attributes of the preload target file. The method of claim 13, And the size information of a memory necessary for storing the preload target file is further recorded in the preload list file. The method of claim 3, The markup document An information storage medium comprising: deletion information instructing to delete a file to be deleted from memory. The method of claim 15, The deletion information is an information storage medium, characterized in that implemented as an API (Application Program Interface) having the position information of the deletion list file in which the deletion list is recorded. The method of claim 15, And the deletion information includes a path of the deletion target file. delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete delete

Images