KR20060030608A - Recording mdium, method and apparatus for reproducing data from the recording medium - Google Patents

Abstract

The present invention relates to a recording medium and a method and apparatus for reproducing a recording medium such as a Blu-ray Disc, and more particularly to reproducing a recording medium in which a first title and a second title having different attributes are recorded, respectively. In this case, titles having different attributes are reproduced by respective dedicated reproducing means, and switching to a title having different attributes during reproduction of the specific title stops the reproducing means currently being reproduced and then executes another reproducing means. It is characterized in that it is carried out through, it is possible to efficiently manage and reproduce the recording medium, thereby providing an effect that provides a more convenient function to the user.

Recording media, Blu-ray Disc, BD-ROM, HDMV, Java, Title, Player model

Description

Recording medium, method and apparatus for reproducing the recording medium {Recording mdium, Method and Apparatus for reproducing data from the recording medium}

1A to 1C are diagrams for explaining each title recorded on the recording medium (BD-ROM) of the present invention.

Fig. 2 shows a file structure recorded on an optical disc as a recording medium of the present invention, and a reproduction relationship thereof.

Fig. 3 shows a data recording structure recorded on an optical disc by the present invention.

4A and 4B show a relationship between reproduction of a title and switching between titles according to the present invention.

5A and 5B show a reproducing apparatus for reproducing a recording medium of the present invention.

6A and 6B illustrate a method of reproducing a recording medium according to the present invention, which is performed by switching from an HDMV title to a Java title by a jump instruction.

7A and 7B illustrate a method of reproducing a recording medium according to the present invention, which is performed when switching from a Java title to an HDMV title by a jump instruction.

8A and 8B illustrate a method of reproducing a recording medium according to the present invention, which is performed when switching from a HDMV title to a Java title by a Call instruction.                 

9A and 9B illustrate a method of reproducing a recording medium according to the present invention, which is switched when a resume command is executed from a Java title to an HDMV title.

Fig. 10 shows a reproducing apparatus for reproducing a recording medium of the present invention, in particular an apparatus for receiving and processing a user command.

Fig. 11 shows a reproducing apparatus for reproducing a recording medium of the present invention, particularly an apparatus for managing a graphic plan.

12A and 12B show syntax of an index file according to the present invention.

※ Explanation of code for main part of drawing

11 pickup 12 control unit

13 signal processing unit 15 memory

17: playback processing means 17a: decoder

17b: Player Model

171Module Manager

172: Movie Module

173: Java module (BDJ Module)

174: Playback control engine

175: Presentation engine

171a: user event manager

172a: command processor                 

172b: UO controller

173a: Application Manager

173b: Java VM

174a: Playback control function

174b Player registers

17c: HDMV Planes

17d: Java Planes

The present invention relates to a recording medium, and more particularly to a reproducing method and apparatus for efficiently reproducing data of different attributes recorded in the recording medium.

As a recording medium, an optical disc capable of recording a large amount of data is widely used. Recently, new high-density recording media, such as Blu-ray discs (BDs), which can record and store high-quality video data and high-quality audio data for a long time, have been developed.

Blu-ray Disc (BD), a next-generation recording media technology, is a next-generation optical recording solution that can record data that significantly exceeds existing DVDs. Recently, the world's standard technical specifications with other digital devices have been established.

In relation to this, the development of the optical record player applying the Blu-ray Disc (BD) standard has begun, but it is difficult to develop the finished optical record player because the Blu-ray Disc (BD) standard is not fully completed yet. It is true.

Particularly, data of different attributes can be recorded in the Blu-ray Disc BD. For example, a title on which a moving picture movie recorded by MPEG2 compression is recorded, and a Java program is recorded. An example is a title in which interactive information including a moving picture movie to be executed is recorded, a title recorded in a web language, and the like.

However, the current Blu-ray Disc (BD) standard does not provide a unified standard for reproducing data (i.e., titles) of various attributes as described above, and thus develops an optical Blu-ray Disc (BD) based optical record / playback player. There are many limitations to doing this.

SUMMARY OF THE INVENTION The present invention has been made in view of the above circumstances, and an object of the present invention is to provide a new playback method and apparatus suitable for a recording medium such as a Blu-ray disc (BD).

In a recording medium recorded with various attribute data, it is desired to provide a reproducing method and a reproducing apparatus for recording information identifying the attribute by attribute in a recording medium and reproducing the recording medium using the information.

In the recording medium reproducing method according to the present invention for achieving the above object, in reproducing a recording medium in which the first title and the second title having different attributes are recorded, the titles having the different attributes The playback of the specific title is performed by the dedicated playback means, and the switching to a title having a different attribute during playback of the specific title is performed by stopping the playback means currently being played and then executing another playback means.

Further, the apparatus for reproducing a recording medium according to the present invention, in reproducing a recording medium in which HDMV titles and Java titles having different attributes are recorded, respectively, controls reproduction according to a static scenario recorded in the recording medium. A playback control engine ("Playback control engine 174") and a movie module ("Movie Module 172) for controlling the playback control engine 174 according to a command for playing the HDMV title. And a Java module (" BDJ ") that executes a Java program for playing the Java title and controls the playback control engine 174 when playback is required according to a static scenario recorded in a recording medium. Module 173 ") and a module manager (" Module Manager 171 ") that receives an external control command and controls the execution of the movie module 172 and the Java module 173.

The recording medium according to the present invention further includes a title recording area in which first and second titles having different attributes are recorded, and a management file recording in which a reproduction management file for reproducing each of the titles having different attributes is recorded. And an information for distinguishing between the first title and the second title in the management file recording area.                     

Preferably, the first title is an HDMV title, and the second title is a Java title.

Hereinafter, with reference to the accompanying drawings, a preferred embodiment of a method for reproducing a recording medium and the like according to the present invention will be described in detail.

In addition, the terms used in the present invention was selected as a general term widely used as possible now, but in certain cases, the term is arbitrarily selected by the applicant, in which case the meaning is described in detail in the description of the invention, The present invention is to be understood as the meaning of terms rather than names.

In the present invention, the term " recording medium " in the present invention refers to any medium on which data can be recorded, and encompasses all mediums regardless of a recording method such as an optical disc or a magnetic tape. Hereinafter, the present invention will be described using an optical disc, in particular, a "Blu-ray Disc (BD)" as a recording medium for convenience of explanation, but it is obvious that the technical idea of the present invention is equally applicable to other recording media. something to do.

In addition, in the present invention, "Title" is a playback unit that forms an interface with a user, and each title is linked to a specific object, and the title in the object is controlled. According to the command, the stream related to the title recorded in the disc is played. In relation to this, a detailed description of the relationship between the title recorded in the disc and the file structure in the disc for reproducing the same will be described later in FIG. In particular, in the present invention, for the convenience of explanation, a title recorded with a movie movie and interactive information by MPEG2 compression method among the titles recorded on the disc is particularly referred to as "HDMV title (Title)". The title on which the motion picture movie and the interactive information executed by the Java program will be recorded will be referred to as "Java Title".

In addition, in the present invention, " Object " refers to reproduction management information having a command or program for playing the disc. That is, there are various kinds of objects in the disk, and they are linked to a specific title or interconnected with another object, so that the disk is predesigned as needed or according to the disc author's intention. It is possible to vary the playback scenarios. In this regard, it is possible to have a plurality of objects in one file or to constitute one object in one file, and in particular, an object for playing the above-mentioned "HDMV Title" The object for reproducing the above-mentioned "Java Title" will be called "BD-J Object" or "Java Object" or "BDJ Object" or "BD-J OBJ".

 Figures 1a to 1c are shown to help the conceptual understanding of the present invention, it is shown to show an example of reproduction-only Blu-ray disc (BD-ROM) through the optical record player 10.

In this regard, the "optical recorder 10" of the present invention is an apparatus capable of recording or reproducing optical discs of various standards, and depending on the design, it is possible to record and reproduce only optical discs of a specific standard (for example, BD). In addition, it is also possible to enable playback only without recording, but in particular, the Blu-ray Disc (BD) is reproduced in consideration of the completion of the Blu-ray Disc (BD) standard to be solved by the present invention and its linkage with peripheral devices. A description will be given by taking an example of a player (BD-Player) or a recorder (BD-Recorder) for recording and playing back a Blu-ray disc (BD). In this regard, it is well known that the "optical recorder 10" of the present invention can be applied to a "drive" that can be embedded in a computer or the like.

In addition to the function of reproducing a Blu-ray Disc (BD-ROM), the optical recorder 10 of the present invention reads data in a Blu-ray Disc (BD-ROM) and performs signal processing and decoding according to the read data attribute. Then, it has a function of transmitting this to the user through the display 30 connected to the optical recorder 10.

In particular, Fig. 1A shows a case where all of the titles recorded on the BD-ROM are HDMV titles. Fig. 1B shows a case where all of the titles recorded on the BD-ROM are Java titles. Shows a case where a title recorded on a BD-ROM is recorded by mixing a mixture of HDMV titles and Java titles (also referred to as "full mode" in particular).

The present invention is to provide a standardized disk file structure so that the disc (BD-ROM) in all of the above cases can be reproduced, as well as to provide a player model as a reproducing apparatus for reproducing it.

Fig. 2 shows a file structure (a) recorded in a recording medium of the present invention, i.e., a BD-ROM, and files in each file structure (a) when a specific title is reproduced from the file structure (a). The relationship (b) is shown.                     

First, the file structure (a) of FIG. 2 will be described.

In the reproduction management file structure (a) of the present invention, at least one BD directory exists under one root directory, and interactivity with a user is ensured in the BD directory. General file (parent file) information, including index file ("index") and object file ("MovieObjet.bdmv"), as well as information about the data recorded on the actual disc and how to play it As a directory having, a playlist directory (PLAYLIST), a clip information directory (CLIPINF), and a stream directory (STREAM) are provided, and a Java (JAVA) directory composed of Java program files is provided. Hereinafter, the directory and the files included in the directory will be described in detail.

The stream directory (STREAM) contains AV stream files recorded in a specific format on the disc. For example, the extension of the stream files (01000.m2ts, 02000.m2ts) is used as "* .m2ts". In general, moving picture data is recorded in a stream file.

The clip information directory (CLIPINF) is composed of clip information files (01000.clpi, 02000.clpi) that correspond one-to-one with each stream file. In particular, a clip information file (* .clpi) records attribute information and timing information of a corresponding stream file, and in particular, a clip information file (* .cl2) corresponding to a stream file (* .m2ts) in one-to-one correspondence. clpi) and the BD specification calls it "clip." That is, a corresponding clip information file (* .clpi) must exist for one stream file (* .m2ts).

Playlist directory (PLAYLIST) consists of playlist files (* .mpls), each playlist file (* .mpls) is at least one or more specifying the playing interval (clipping interval) PlayItem contains PlayItem, and PlayItem is the specific clip that you want to play, that is, the playback start time of the clip designated as the clip name (clip_Information_File_name) in PlayItem (PlayItem). IN-Time) and playback end time (OUT-Time).

In other words, the playlist file (* .mpls) becomes a basic playback management file unit in the entire playback management file structure in which a desired clip is played by a combination of at least one PlayItem (PlayItem). In addition, a playlist file (* .mpls) may be provided with a subplayitem (SubPlayItem) for reproducing data different from the reproduction by the playitem (Item), in particular auxiliary data.

In particular, the playlist file (* .mpls) is operated only by a command or a program of the above-described Object. Therefore, in view of the disc playback scenario, the Object is a dynamic scenario. ), The playlist file (* .mpls) performs a static scenario.

The Java directory (JAVA) contains Java program files (for example, PPPPP.jar or QQQQQ.jar), each of which is programmed with a variety of applications, also known as "Xlets". . In relation to this, a Java program file (* .jar) is provided with a "BDJ Object" for executing a Java title. In the end, when a user wants to play a specific Java title, one Java program including the "BDJ Object" is included. The file is executed. The Java program file is processed by a dedicated playback means, which will be described later in FIG. 5B.

2 (b) shows a relation in which a specific title is reproduced by the above-described file structure (a) of FIG. 2, which is related to an index table by an index file. A detailed description will be given of the relation in which the title is reproduced when the user reproduces the title with respect to the specific title provided by the user.

In the index file, "First Playbak" information having information about the first playing screen when the disc is loaded, "Top_Menu" information providing a menu screen, and at least one "Title" (eg Title # 1 to Title # 4) "information. In relation to this, the titles Title # 1 to Title # 4 may be HDMV titles or configurable as either Java titles.

Subsequently, when the user selects playback of a specific title (for example, Title # 1), the specific object controller linked with the title (Title # 1) in the object file (Object) on the file structure (a). According to the command, a specific playlist is played, and the playitem in the playlist plays a specific clip (consisting of "* .clpi" and "* .m2ts").

Relatedly, if the selected title (Title # 1) is an HDMV title, it is played by a specific "Movie Object" in one object file, and if the selected title (Title # 1) is a Java title, the Java directory ( A specific "BDJ Object" in a Java program file (* .jar) in JAVA) is utilized.

In addition, the index file may be configured in such a manner that both the HDMV title and the Java title can be indexed as "index.bdj", or index only the HDMV title as "index.bdmv" for an optical record player capable of playing only HDMV titles. It can also be composed of two index files, including a file.

Fig. 3 briefly shows a form in which information related to the file structure (a) is recorded on the disc. From the inside of the disc, a file system information area as a system information for managing the entire file, and An area in which a playlist file and clip information file is recorded (also referred to as a "database area") for playing a recorded stream (* .m2ts), and a stream area in which a stream consisting of audio / video / graphics or the like is recorded ( You can see that a stream area exists. In particular, in the present invention, it has already been described above that the data recorded in the stream area in the disc can be composed of data having different attributes from each other.

4A and 4B are diagrams showing the relationship between title reproduction in a disc according to the present invention. In particular, the disc played by the present invention is a "Full mode" disc containing both an HDMV title and a Java title.

For example, suppose that a BD-ROM disc has four titles, dual title # 1 and title # 2 are HDMV titles, and title # 3 and title # 4 are Java titles. Likewise, it is linked to a specific object file.

That is, title # 1 and title # 2, which are HDMV titles, are linked with Movie-Object # 2 and Movie-Object # 3, respectively, and title # 3 and title # 4, which are Java titles, are BDJ-Object # 2 and BDJ-Object, respectively. Linked to # 3. Also, for example, "First Platback" in the index table may be linked to Movie-Object # 1, and "Top Menu" may be linked to BDJ-Object # 1, respectively. In this regard, it is also possible to link the "First Platback" to the BDJ-Object or to link the "Top Menu" to the Movie-Object, which means that it can be selectively set by the disk author (Author).

Also, it can be seen that Movie-Object # 4 is linked to another object, Movie-Object # 3, and BDJ-Object # 4 is linked to another object, BDJ-Object # 3.

FIG. 4B shows a movement or transition relationship between titles having different attributes from each other in playing the title in the disc of FIG. 4A.

In this regard, the characteristics of the movement or transition relationship between the HDMV title and the Java title according to the present invention are as follows.

First, direct switching between objects with different mutual attributes is not allowed. That is, it can be seen from FIG. 4A that the object can be switched between objects of the same property. For example, Movie-Object # 3 can be converted to another object, Movie-Object # 4, and BDJ-Object # 3 is You can switch to another object, BDJ-Object # 4. However, direct conversion between Movie-Object and BDJ-Object whose properties are different from each other is not allowed. In this case, only conversion through title change is allowed.

Second, when changing the title, changing from HDMV title to Java title is allowed for both "Jump" and "Call / Resume". The "Jump" command means a command for terminating the current title and switching to another title when the title is changed, and the "Call" command is a command for maintaining the current title and switching to another title when the title is changed. Meaning, the return to the suspended title is made by the "Resume" command. That is, the "Call" and "Resume" commands are commands that correspond in pairs.

For example, change from title # 1 (HDMV title) to title # 3 (Java title) (solid line in the figure) shows that both "Jump" and "Call" change is allowed.

Third, when changing a title, the change from Java title to HDMV title is basically only allowed to be switched by the "Jump" command. That is, for example, it can be seen that only "Jump" is allowed to change from title # 3 (Java title) to title # 1 (HDMV title) (dotted line in the figure).

As described above, by allowing the switching between titles having different attributes, the user can conveniently play various titles when using the disc, while not allowing the switching by the "Call" command when changing from Java title to HDMV title. This is because the Java system does not have a register for sustaining the current playback. However, if you define the concept of a backup register, you can enable the "Call" command to switch from Java title to HDMV title.                     

5A and 5B show an optical recording and reproducing apparatus according to the present invention as an example. In particular, FIG. 5A shows the configuration of the entire optical recording and reproducing apparatus 10, and FIG. 5B shows a title having different attributes. The concrete configuration of the reproduction processing means 17 of the present invention for reproducing a disc is shown.

5A illustrates the overall configuration of the optical recorder 10 of the present invention as follows.

First, the playback received from the pickup section 11, the servo 14 for controlling the operation of the pickup section 11, and the pickup section 11 for reproducing management information including data recorded on the optical disc and reproduction management file information. A signal processor 13 for restoring a signal to a desired signal value or modulating and transmitting a signal to be recorded to a signal recorded on an optical disk, and a memory 15 for storing various necessary information necessary for disc reproduction; The microcomputer 16 for controlling the operation of the component is basically configured. In connection with the above components, it is also referred to as a "recording and playback section 20", the recording and playback section 20 can be provided as a single product.

In addition, the control unit 12 is in charge of the control of the entire component, and in particular, in connection with the present invention, to control the playback of a specific title or a command to switch between titles through an interface with the user.

In addition, the reproduction processing means 17 finally decodes the output data under the control of the controller 12 and provides the same to the user. In particular, the decoder 17a for decoding the AV signal and the reproduction of the specific title described above are provided. In this connection, an object command or program and a player model 17b for analyzing a user command input through the control unit 12 and determining a playback direction are included. However, in some embodiments, the player model 17b may be used to include the decoder 17a. That is, the reproduction processing means 17 of the present invention is also a player model (Fig. 5B, Player Model).

In addition, the encoder 18 converts an input signal into a signal of a specific format, for example, an MPEG2 transport stream under the control of the control unit 12 to perform a function of recording a signal on an optical disc. It is provided to (13).

Fig. 5B shows a detailed configuration of the playback processing means 17. In particular, the player model 17b is a " Module Manager 171 ", " Movie Module 172 ", " BDJ Module " 173) "," Playback control engine 174 "and" Presentation engine 175 ", which will be described in detail as follows.

First, as separate playback processing management means for reproducing the HDMV title and the Java title, the "Movie Module 172" for the HDMV title and the "BDJ Module 173" for the Java title are independently configured. In particular, the "Movie Module 172" and the "BDJ Module 173" have a control function for receiving a command or a program in the above-described object (Movie-Object or BDJ-Object) and processing the same. . As a means for receiving and processing the command, the "Command processor 172a" in the "Movie Module 172" and the "Application manager 173a" and "" in the "BDJ Module 173". Java VM 173b "are provided respectively.                     

In addition, the "Module Manager" not only transmits a user command to the "Movie Module 172" and "BDJ Module 173", but also controls operations of the "Movie Module 172" and the "BDJ Module 173". 171 ", the contents of the playlist file recorded on the actual disc (in particular, constitute a" Static scenario ") in accordance with the playback commands of the" Movie Module 172 "and the" BDJ Module 173 ". A " Playback control engine 174 " is provided for interpreting and performing playback functions accordingly. In addition, a "Presentation engine 175" for displaying in a screen a specific stream managed by the "Playback control engine 174" is provided.

In particular, the " Playback control engine 174 " is a " Playback control function 174a " that manages the actual playback, and the player's playback environment or playback status (" Palyer status registers (PSR) " and " General purpose register " ) &Quot; " is stored in " Player registers 174b ". In some cases, " Playback control function 174a " may mean " Playback control engine 174 ".

In the above-described player model 17b of the present invention, the "Module Manager 171", "Movie Module 172", "BDJ Module 173", and "Playback control engine 174" are software. Processing is possible, and software processing is more useful for design than the actual hardware configuration. However, the "Presentation engine 175", the decoder 17a and the graphic plans 17c and 17d are generally designed in hardware. In particular, the components (for example, 171, 172, 173, 174) that are processed by software may be configured as one part of the controller 12 described above. Therefore, it should be understood that the configuration of the present invention should be understood as its meaning, and is not limited to hardware configuration or software configuration.

In this regard, the features of the player model (FIG. 5B, Player Model) of the present invention are as follows.

First, as described above, the "Movie Module 172" for the HDMV title and the "BDJ Module 173" for the Java title are independently configured, and both modules 172 and 173 are not executed at the same time. In other words, Java titles cannot be played while HDMV titles are playing, and vice versa.

Second, the HDMV title and the Java title each receive a user command in a separate manner, and the method of executing the user command is independent of each other. However, there is a need for a means of receiving a user command and delivering it to one of the "Movie Module 172" and the "BDJ Module 173". This means that the "User Event Manager 171a" in the "Module Manager 171" In charge. Thus, for example, "User Event Manager 171a" transmits the received command to "UO controller 172b" in "Movie Module 172" if the received command is a user command by "User Operation (UO)". If the received command is a user command by "Key event", the command is transmitted to "Java VM 173b" in the "BDJ Module 173" for execution. Detailed description thereof will be described later with reference to FIG. 10.

Third, management of the above-mentioned "Playback control engine 174" (also referred to as "master") is in charge of one of the modules 172 and 173 currently operating. In other words, "Movie Module 172" becomes a master during HDMV title playback, and "BDJ Module 173" becomes a master during Java title playback.

Fourth, the management of the graphic plane is also performed independently. For example, in the HDMV plan 17c, the "Presentation engine 175" becomes the master, and the Java plan 17d described above. The "Java VM 173b" in the "BDJ Module 173" becomes a master. Detailed description thereof will be described later with reference to FIG.

6A to 9B are shown to explain the operation of the player model (Fig. 5B, Player Model) when switching between titles having different attributes as described above with reference to Fig. 4B.

6A and 6B show the steps of performing a switch by " Jump " command from the HDMV title to the Java title. In this regard, some of the detailed descriptions of the player model 17b described above are omitted for convenience of description.

First, in the "Module Manager 171", the contents of the index table provided in the disk are recognized. That is, the index table shows that title # 1 is an HDMV title and title # 3 is a Java title.

Therefore, if a switch instruction by " Jump " is received from the control unit 12 to title # 3 which is a Java title while playing title # 1 which is an HDMV title (step 1), the " Module Manager 171 " First of all, command to end the operation of "Movie Module 172" which is currently managing playback of Title # 1 (step ②), and control by the specific object (Movie-Object) that was being executed by "Movie Module 172". The command and subsequent playback of Title # 1 are all terminated by the "Movie Module 172" (step ③④). "Movie Module 172" also ends after the HDMV title ends. Thereafter, the "Module Manager 171" drives the "BDJ Module 173" to execute the Java title Title # 3 (step 5), and controls the specific object (BDJ-Object) linked with the title # 3. Depending on the command or program, playback of specific title # 3 is performed (step ⑥⑦).

That is, since the player model (FIG. 5B, Player Model) of the present invention does not simultaneously execute titles having different attributes at the same time, in order to switch to a Java title (in particular, "Jump") during HDMV title playback, It is understood that the "BDJ Module 173" should be driven after the current "Movie Module 172" is finished.

7A and 7B show a step of performing a switch by a "Jump" command from a Java title to an HDMV title. Similarly, some of the detailed descriptions of the player model (FIG. 5B, Player Model) described above are omitted for convenience of description.

First, as in the case of Fig. 6A, the contents of the index table provided in the disk are recognized in the "Module Manager 171". That is, the index table shows that title # 1 is an HDMV title and title # 3 is a Java title.

Therefore, if a switch instruction by " Jump " is received from the control unit 12 to title # 1 which is an HDMV title while playing title # 3 which is a Java title (step 1), the " Module Manager 171 " First, a command is given to terminate the operation of the "BDJ Module 173" that is currently managing playback of Title # 3 (Step ②), and a program by a specific object (BDJ-Object) that was being executed by the "BDJ Module 173". And subsequent playback of Title # 3 are also completed by the BDJ Module 173 (step ③④). "BDJ Module 173" also ends after the Java title is finished. Then, the "Module Manager 171" drives the "Movie Module 172" to execute Title # 1, which is the HDMV title (step ⑤), and controls the specific object (Movie-Object) linked with Title # 1. According to the command, playback of specific title # 1 is performed (step ⑥).

That is, since the player model 17b of the present invention does not execute titles of different attributes at the same time as described above, it is currently operating to switch to HDMV title (especially "Jump") during Java title playback. It is understood that the "Movie Module 172" should be driven after the "BDJ Module 173" must be terminated.

8A and 8B show the steps of performing a switch by " Call " command from the HDMV title to the Java title. Similarly, some of the detailed descriptions of the player model 17b described above are omitted for convenience of description.

If playback command of title # 1, which is an HDMV title, is received from the control unit 12 in response to a "Call" change to title # 3, which is a Java title (step 1), the "Module Manager 171" is currently present. Command to end the operation of "Movie Module 172" which is managing playback of Title # 1 (step ②), and a command by a specific object (Movie-Object) that was being executed by "Movie Module 172" ( command) and subsequent playback of Title # 1 are also paused by the "Movie Module 172" (step ③④). That is, since the "Call" switch command is scheduled to return to the current position of Title # 1 currently being played again, differently from the "Jump" switch command (this is performed by the "Resume" command, which is performed by Figs. 9A and 9B. The playback state information is stored in " Player Registers 174b " without deleting all the information on Title # 1 currently being played (step 5). However, the player model (FIG. 5B, Player Model) of the present invention does not simultaneously execute titles of different attributes as described above, so that even when the HDMV title is being played back by the " Call " You must terminate the running "Movie Module 172".

Thereafter, the "Module Manager 171" drives the "BDJ Module 173" to execute the title # 3 which is the Java title (step ⑥), and the program of the specific object (BDJ-Object) linked with the title # 3. In this case, playback of specific title # 3 is performed (step ⑦⑧).

9A and 9B show the execution of the "Resume" command to return to the original HDMV title again after the conversion by the "Call" command from the HDMV title to the Java title is performed by the above-described FIGS. 8A and 8B. The steps are shown. Similarly, some of the detailed descriptions of the player model (FIG. 5B, Player Model) described above are omitted for convenience of description.

If playback command of the Java title Title # 3 is received from the control unit 12 by the "Resume" to the title # 1 which is the HDMV title (step 1), the "Module Manager 171" is currently present. Instructs the title # 3 to end the operation of the "BDJ Module 173" which is being managed for playback (step ②), and the program by the specific object (BDJ-Object) that was being executed by the "BDJ Module 173" and the program. The reproduction of Title # 3 is also completed by the BDJ Module 173 (step ③④). "BDJ Module 173" also ends after the Java title is finished. Then, the "Module Manager 171" drives the "Movie Module 172" to execute Title # 1, which is the HDMV title (step ⑤), and controls the specific object (Movie-Object) linked with Title # 1. According to the command, playback of specific title # 1 is performed (step ⑥). The playback is performed according to the value of the corresponding " Player Registers 174b " by referring to the playback state information stored in " Player Registers 174b " before (Fig. 8A / 8B) (step 7). This means that playback of Title # 1 paused by the "Call" command (Figs. 8A / B) is restarted by the "Resume" command.

In relation to this, the player model (FIG. 5B, Player Model) of the present invention does not simultaneously execute titles of different attributes as described above, so that even when switching from the "Resume" command to the HDMV title while playing the Java title, The currently running "BDJ Module 173" must be terminated.

Fig. 10 shows an example of the player model (Fig. 5B, Player Model) of the present invention, and especially for explaining the second feature of the above-described player model (Fig. 5B).

In relation to this, the second feature of the above-described player model (Fig. 5B) is provided with a "User Event Manager 171a" in the "Module Manager 171" so that upon receiving a user command, the received command is used for the HDMV title. If it is a user command by "User Operation (UO)", it is sent to "UO controller (172b)" in "Movie Module (172)" for execution, and the received command is the user by "Key event" for Java title. If it is a command, this means that it is transmitted to the "Java VM 173b" in the "BDJ Module 173" to be executed.

In other words, since HDMV title mode and Java title mode have mutually independent user command receiving systems, processing of these user commands in a unified manner can be confusing. Therefore, the processing of user commands is performed by "Movie Module (172)". And "BDJ Module (173)", but after receiving the user command, the user to distinguish the user command by what characteristics, and according to the separated result "User" to transfer the user command to the module (172 or 173) Event Manager 171a "

FIG. 11 shows another example of the player model (FIG. 5B) of the present invention, and specifically illustrates the fourth feature of the above-described player model (FIG. 5B).

In relation to this, the fourth feature of the player model (Fig. 5B) described above relates to the management of a graphic plane, for example the HDMV plan 17c is a video / presentation graphic / interactive graphic / text subtitle plan. And these plans are managed by the "Presentation engine (175)" as the master, while the Java plan (17d) is configurable as Java graphics plans and these plans are "BDJ Module (173)". The "Java VM 173b" in the master becomes a master and manages it.

In addition, the HDMV plan 17c and the Java plan 17d may be partially shared with each other. In particular, the interactive graphic plan in the HDMV plan 17c may be shared and applied to the Java plan 17d.

12A and 12B illustrate the syntax of the above-described index file related to the present invention, hierarchically.

Fig. 12A shows syntax for a header portion of an index file (index.bdmv), and the "type_indicator" field includes information for identifying that the file is an index file, for example, an "INDX" character. The code is recorded, information indicating the version of the index file is recorded in the "version_number" field, and the position information at which the "Indexes ()" field starts in the file is recorded in the "Indexes_start_address" field. In the index file (index.bdmv), an "AppInfoBDMV ()" field for providing general information about the author of the disc and an "Indexes ()" field for providing the user with indexed contents recorded on the disc are provided. In detail, the "Indexes ()" field related to the present invention will be described in detail as follows.

FIG. 12B illustrates the syntax of the “Indexes ()” field in the index file index.bdmv, and will be more readily understood with reference to FIGS. 2, 4A and 4B described above. In detail, the size information of the "Indexes ()" field is recorded in the "length" field, and the "FirstPlayback ()" field shows a specific object for the playback screen in order to forcibly show the first playback screen when the disc is loaded. Contains the "FirstPlayback_obj_id_ref" information that loads "obj_id" to specify the. As described above, the "FirstPlayback_obj_id_ref" information may specify both "Movie Objet" or "BDJ Object".

The "TopMenu ()" field also contains "TopMenu_obj_id_ref" information that calls "obj_id" to specify a specific object for that menu screen, in order to provide the menu screen by the user's "Menu Call" command. It is included. As described above, the "TopMenu_obj_id_ref" information may specify both "Movie Objet" or "BDJ Object".

In addition, in the "number_of_Title" field, information about the number of titles existing in the index file is recorded, and there are as many "Title ()" fields as the number based on the number information, and each "Title ()" field. It contains "Title_obj_id_ref" information that calls a specific "obj_id" in the object file holding a playback command or program for playing the title, and is composed of the following additional fields.

That is, the "Title_environment (type)" field indicating the type of title determines whether the title is an HDMV title or a Java title. The title classification information enables the optical record player to drive the player model (Fig. 5B, Player Model) in advance so as to be able to reproduce a title of a specific attribute in advance.

In addition, the "Title_playback_type" field identifies whether the title is a movie title such as a movie or an interactive title such as menu information provided to the user.

In addition, the "Title_link" field indicates whether or not there is another title linked to the title. In particular, by confirming in advance whether to link between titles having different attributes, it is possible to quickly correspond to the player model (Fig. 5B, Player Model).

In addition, the "Title_access_type" field indicates whether or not the title is searchable, which is necessary for controlling the "User Operation (UO)" operation of the HDMA title, and corresponds to information required only in the HDMV title.

In addition, the "Object_type" field identifies whether the title is an HDMV title or a Java title, and makes it possible to execute an object corresponding to each title.

In addition, the "Title_obj_id_ref" field has information for designating a corresponding object in the MovieObject.bdmv file for designating a movie object, and for designating a Java object (BDJ object), for specifying a Java object (BDJ object). The information to be specified includes, for example, a directory path name and a file name for designating a PPPPP.jar or QQQQQ.jar file in FIG. 2, and also includes specific application identifying information in a Java program file, or It can be configured with "Xlet indentifying" information.

In relation to FIG. 12B, only limited attribute information for each title is representatively illustrated, and it will be apparent that various title information may be provided for each title type.

As described above, preferred embodiments of the present invention are disclosed for purposes of illustration, and those of ordinary skill in the art can further various other embodiments within the spirit and technical scope of the present invention disclosed in the appended claims. Improvements, changes, substitutions or additions will be possible.

Through the reproducing method and reproducing apparatus of the recording medium according to the present invention, it is possible to record and provide data having different attributes on one recording medium, and to efficiently manage and reproduce the recording medium. This has the effect of providing more convenient functions to the user.

Claims (29)

In playing back the recording medium on which the first title and the second title each having different attributes are recorded, The titles having different attributes are reproduced by respective dedicated reproducing means, and the switching to the titles having different attributes during reproduction of the specific title is performed by stopping the reproducing means currently being reproduced and executing other reproducing means. Recording medium playback method characterized in that. The method of claim 1, Wherein the first title is an HDMV title, and the second title is a Java title. The method of claim 2, Switching to a title having a different attribute means switching from an HDMV title to a Java title. The method of claim 3, wherein And switching from the HDMV title to a Java title by a jump command. The method of claim 3, wherein And the conversion from the HDMV title to the Java title is by a call command. The method of claim 5, And after switching to the Java title by the Call command, switching to the HDMV title again by the Resume command. The method of claim 2, Switching to a title having a different attribute means switching from a Java title to an HDMV title. The method of claim 7, wherein And the jump from the Java title to the HDMV title is performed by a jump command. The method of claim 2, And an index file for reproducing and managing the HDMV title and the Java title, and providing a screen for selecting a title to the user through the index file. The method of claim 9, And the index file includes an index file including both an HDMV title and a Java title, and an index file including only an HDMV title. The method of claim 9, And the index file includes information (Title-environment) for distinguishing an HDMV title from a Java title. The method of claim 9, And the index file includes link information (Title_link) between titles. The method of claim 9, And the index file includes object information (obj_id) having a command related to reproduction of a specific title. The method of claim 13, And object information (obj_id) for reproducing the HDMV title is Movie-Object. The method of claim 14, And a plurality of Movie-Objects in the recording medium are contained in one object file (MovieObject, bdmv). The method of claim 13, And object information (obj_id) for reproducing the Java title is a BDJ-Object. The method of claim 16, And a BDJ-Object in the recording medium is included in a corresponding Java program file (* .jar), respectively. In reproducing a recording medium on which HDMV titles and Java titles having different attributes are recorded, A playback control engine ("Playback control engine 174") for controlling playback in accordance with a static scenario recorded in the recording medium; A movie module ("Movie Module 172") for controlling the playback control engine 174 according to a command for playing the HDMV title, A Java module for executing a Java program for playing the Java title and controlling the playback control engine 174 when playback according to a static scenario recorded in a recording medium is required ("BDJ Module 173"). ")and, And a module manager ("Module Manager (171)") for controlling the execution of the movie module (172) and the Java module (173) by receiving an external control command. The method of claim 18, A static scenario recorded in the recording medium is managed by a playlist file and a clip information file. The method of claim 18, The playback control engine ("Playback control engine 174"), A playback control function ("Playback control function 174a") that performs playback management, And a player register (" Player registers (174b) ") for storing the playback state. The method of claim 18, And a module manager ("Module Manager (171)") comprises a user event manager ("User event manager (171a)") for managing user commands. The method of claim 21, The user event manager ("User event manager 171a") receives a user command, and transmits the user command to the movie module 172 and the Java module 173, respectively, according to the received user command characteristics. A recording medium reproducing apparatus. The method of claim 22, In the movie module ("Movie Module 172"), a controller ("UO controller 172b) that receives a user command from the user event manager 171a and controls the playback control engine 174 using the same. Recording medium reproducing apparatus comprising: " The method of claim 22, In the Java module ("BDJ Module 173"), a Java command that receives a user command from the user event manager 171a and uses it to play a Java program or controls a playback control engine 174. And a VM (" Java VM 173b "). The method of claim 24, And an application manager ("Application Manager (173a)") in which the Java module ("BDJ Module (173)") separates and manages a plurality of applications in the Java program. The method of claim 18, And a presentation engine ("Presentation engine" for controlling the playback screen of the HDMV title). The method of claim 18, And a decoder (17a) for decoding the HDMV title data. A title recording area in which a first title and a second title having different attributes are recorded respectively, and a management file recording area in which a reproduction management file for reproducing each of the titles having different attributes is recorded; And recording information for distinguishing the first title from the second title. The method of claim 28, And the connection information of the first title and the second title is further recorded in the management file recording area.

Images