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

Abstract

A recording medium and a method and apparatus for reproducing data from a recording medium are provided. The recording medium includes a recording area in which one or more first titles having different attributes and one or more second titles are recorded, and a reproduction management area for reproducing individual titles having different attributes. Static scenarios and dynamic scenarios are recorded in the reproduction management area, static scenarios are commonly applied to the first and second titles, and dynamic scenarios are included in the first and second titles, respectively.

Recording media, static scenarios, dynamic scenarios, individual titles

Description

RECORDING MEDIUM, AND METHOD AND APPARATUS FOR REPRODUCING DATA FROM THE RECORDING MEDIUM}

The present invention relates to a recording medium file structure for efficiently reproducing data having different attributes recorded on a recording medium, in particular, a recording medium file structure and a method and apparatus for reproducing data using the recording medium file structure.

In general, optical disks that operate as recording media capable of recording large amounts of data are widely used. In particular, new high-density optical recording media, such as Blu-ray discs (hereinafter referred to as "BDs"), which can record and store high-quality video data and high-quality audio data for a long time, have been recently developed. have.

BD based on next generation recording media technology is regarded as the next generation optical recording solution that can store more data than conventional DVD. Recently, many developers have been intensively researching international standard technical specifications related to BD with other digital devices.

In particular, the above-described BD has a plurality of data units having different attributes, for example, a first title on which a movie compressed in the MPEG2 format is recorded, and a second on which interactive information including a movie executed by a Java program is recorded. The title and the third title recorded by the web language can be recorded.

However, a preferred recording medium file structure for reproducing the above-described data (e.g., a title) having different attributes and a method for reproducing data from the recording medium using the recording medium file structure is not known to those skilled in the art yet, so BD Many limitations and problems arise in developing a base optical recording and reproducing apparatus.

Accordingly, the present invention is to solve the above-mentioned conventional problems and relates to a recording medium and a method and apparatus for reproducing data from the recording medium.

It is an object of the present invention to provide a reproduction management file structure for managing reproduction of a plurality of data units having different attributes recorded on a recording medium.

Another object of the present invention is to provide a method of recording reproduction scenario information for reproducing data units having different attributes recorded in the reproduction management file structure.

It is another object of the present invention to provide a method and apparatus for reproducing data from a recording medium using the recording medium file structure.

Additional features and advantages of the invention will be apparent from the following detailed description and will be apparent from and understandable. Objects and other advantages of the invention can be realized and obtained by the structure as set forth in the description and claims, as well as the accompanying drawings.

In order to achieve the objects and other advantages of the present invention, in one aspect of the present invention, there is provided an apparatus, comprising: a recording area in which at least one first title and at least one second title having different attributes are recorded; And a reproduction management area for reproducing individual titles having different attributes, wherein a static scenario and a dynamic scenario are recorded in the reproduction management area, the static scenario is commonly applied to the first and second titles, and the dynamic A recording medium is provided, wherein a scenario is included in each of the first and second titles.

Preferably, the first title is an HDMV title and the second title is a Java title. The dynamic scenario includes locator information for specifying a specific playlist file that constitutes the static scenario. The dynamic scenario includes locator information for specifying a specific location included in the playlist file.

In another aspect of the present invention, there is provided a recording apparatus, comprising: a recording area in which one or more titles are recorded; And a reproduction management area for reproducing all titles included in the recording area, wherein a static scenario and a dynamic scenario are recorded in the reproduction management area, and the static scenario includes a plurality of playlist files for reproducing all titles. And the dynamic scenario of the individual titles includes information related to one or more accessible playlist files for playing the titles among the playlist files included in the static scenarios.

In another aspect of the present invention, there is provided a recording apparatus, comprising: a recording area in which one or more titles are recorded; And

A reproduction management area for reproducing all titles included in the recording area, wherein a static scenario and a dynamic scenario are recorded in the reproduction management area, and the static scenario includes a plurality of playlist files for reproducing all titles; And the dynamic scenario of the individual title includes locator information capable of designating one of the playlist files included in the static scenario.

In another aspect of the present invention, a first title and a second title having different attributes are recorded independently of each other, a dynamic scenario included in each of the titles having different attributes is recorded, and the static scenario is the attribute information of the individual title. A method for reproducing data of a recording medium commonly included in the first and second titles, the method comprising: (a) reading the dynamic scenario and the static scenario and specifying the static scenario included in the dynamic scenario; Recognizing locator information that may be present; And (b) playing a specific playlist file capable of constructing the corresponding static scenario specified by the locator information.

In another aspect of the present invention, a first title and a second title having different attributes are recorded independently of each other, a dynamic scenario included in each of the titles having different attributes is recorded, and the static scenario is the attribute information of the individual title. An apparatus for recording and reproducing data on a recording medium recorded in common to the first and second titles, the apparatus comprising: a recording / reproducing unit for reading the dynamic scenario and the static scenario recorded on the recording medium; And a player model that reads locator information capable of designating the static scenario from the dynamic scenario and plays a specific playlist file included in the static scenario specified by the read locator information. do.

The foregoing description and the detailed description of the present invention to be described below are only provided by way of illustration in order to assist in understanding the present invention, and the scope thereof is as defined in the claims.

Embodiments of the present invention will be described below with reference to the accompanying drawings. The features shown in the drawings are by way of example in order to make the description of the embodiments of the invention and the principles and scope of the invention more useful and easy to understand. In this regard, the basic understanding of the present invention and the configuration of the present invention are only for showing the details and no other intention, and the description according to the drawings enables those skilled in the art to implement various embodiments of the present invention. .

1 is a conceptual diagram showing an individual title recorded on a recording medium according to the present invention.

Fig. 2 is a conceptual diagram showing a file structure recorded on an optical disc operating as a recording medium according to the present invention, and the reproduction relationship of data of the file structure.

3 is a structural diagram showing a data recording structure recorded on an optical disc according to the present invention;

4A to 4D are structural diagrams showing individual pile structures according to the present invention.

4E is a conceptual diagram showing a playback relationship using the file structure shown in FIGS. 4A-4D in accordance with the present invention.

5A illustratively illustrates dynamic and static scenarios of playing HDMV titles in accordance with the present invention;

5B is an exemplary diagram illustrating dynamic and static scenarios for playing Java titles in accordance with the present invention.

Fig. 6A is a block diagram showing an optical recording and reproducing apparatus according to the present invention.

6B is a block diagram illustrating a player model according to the present invention.

Hereinafter, with reference to the accompanying drawings will be described in detail the detailed operation and structure of the present invention. It should be noted that reference numerals and like elements among the drawings are denoted by the same reference numerals and symbols as much as possible even though they are shown in different drawings.

Before describing the present invention, the terms used in the present invention were selected as general terms as widely used as possible now, but in some cases, the terms arbitrarily selected by the applicants, and in this case, the meanings are described in detail in the description of the present invention. Since the description has been made, it should be understood that the present invention is to be understood as a meaning of a term rather than a simple name of the term.

The recording medium used in the present invention means all recordable media according to various recording methods, for example, optical disks and magnetic tapes. For ease of explanation and understanding of the present invention, an optical disc such as BD will exemplarily be used as the above-described recording medium of the present invention. The technical idea of the present invention can be applied to other recording media without departing from the scope and spirit of the present invention.

The term " title " is a playback unit which interacts with a user, each title being linked to a particular object such that a stream associated with that title recorded on the disc is played back according to a command or program stored in the object.

The title recorded on the disc and the disc file structure for reproducing the title are described with reference to FIG. In particular, for convenience of description and understanding of the present invention, a first title in which a movie and interaction information is recorded according to the MPEG2 compression scheme is called an HDMV title, and a second title in which a movie and interaction information according to a Java program is recorded. Is called the Java title.

The term " object " means reproduction management information including a command or program for disc reproduction. That is, various objects are present on the disc, linked to a specific title, or linked to other objects. Therefore, the above-described object is designed in advance according to the intention of the producer or author of the disc, which is recorded on the disc and increases the number of scenarios for reproducing the data on the disc. The term "dynamic scenario" means the object described above.

For the convenience of the invention and the understanding of the present invention, the above-mentioned object for playing HDMV title is referred to as "movie object" or "M-OBJ" and the above-mentioned object for playing Java title is referred to as "Java object". Or "J-OBJ".

Navigation information capable of playing a particular stream contained in a disc using a command or program stored in an object is referred to below as a specific term "locator". The locators included in the object "movie object" or "M-OBJ" are called HDMV locators. Locators contained in the object "Java Object" or "J-OBJ" are called Java Locators.

1 is a conceptual diagram showing individual titles recorded on a recording medium according to the present invention. In particular, FIG. 1 shows an example of a BD-ROM used in the optical recording / reproducing apparatus 10. FIG.

1 shows a specific mode in which a title recorded on a BD-ROM is mixed with an HDMV title and a Java title so that a title mixed with an HDMV title and a Java title is recorded. A particular mode is called full mode. The present invention provides a standardized file structure on a disc for reproducing data from a BD-ROM based on the full mode, and provides a method and apparatus for reproducing data from a BD-ROM.

The optical record reproducing apparatus 10 can record and reproduce data on various optical discs having different formats. If necessary, the optical recording / reproducing apparatus 10 can record and reproduce specific data only on a specific optical disk such as BD or can not record data on the optical disk but can reproduce the data. The present invention uses a BD player capable of reproducing data from a BD-ROM based on a BD format as a preferred embodiment for convenience of explanation. The optical recording and reproducing apparatus 10 can also be applied to a driver installed in a specific apparatus such as a computer.

The optical record reproducing apparatus 10 reproduces data from the BD-ROM, reads data from the BD-ROM, performs signal processing and decoding processing on the read data in accordance with attribute information of the read data, and reproduces the optical record The signal processing result and the decoding result are transmitted to the display 30 connected to the apparatus 10 so that the user can view the signal processing result and the decoding result on the display 30.

Fig. 2 is a conceptual diagram showing the relationship (b) between a file structure (a) recorded on an optical disc such as a BD-ROM and a file stored in the file structure (a) when playing a specific title from the file structure (a) according to the present invention. to be.

The file structure a described above shown in FIG. 2 will now be described.

File structure (a) contains one or more BD directories in a single root directory. The BD directory contains the aforementioned objects as well as an index file that acts as a regular file (i.e., a parent file) that can guarantee user interaction. The file structure (a) contains various directories for storing information of the actual data recorded on the disc and other information related to how to reproduce the data, for example, a playlist directory (PLAYLIST), a clip information directory (CLIPINF), and a stream directory. (STREAM) and Java directory (JAVA). Hereinafter, the above-described directory and various files included in the directory will be described.

The stream directory STREAM includes a plurality of AV (audio and video) stream files recorded on a disc according to a specific format. For example, the stream directory STREAM uses the extensions of the stream files 01000.m2ts and 02000.m2ts as the specific extension name "* .m2ts". In general, a stream file records video data.

The clip information (clip info) directory CLIPINF is composed of a plurality of clip info files 01000.clpi and 02000.clpi that correspond one-to-one to the above-described stream directory. In particular, the clip info file (* .clpi) records the attribute information and timing information of the stream file. Clip info files (* .clpi) that correspond one-to-one to stream files (* .m2ts) are generally referred to as "clips". In other words, this means that one stream file (* .m2ts) should correspond to the clip info file (* .clpi).

The playlist directory PLAYLIST includes a plurality of playlist files (* .mpls). Each playlist file (* .mpls) contains one or more PlayItems that specify play intervals during playback of a particular clip. The PlayItem is information related to a specific clip to be played, that is, information related to a play start time (IN-Time) of a clip to be determined by a clip name (Clip_Information_File_name) included in the PlayItem (PlayItem) and a play end time (OUT). -Time) contains other information.

Playlist files (* .mpls) are used as basic playback management file units included in the overall file structure to enable playback of a desired clip using a combination of one or more playitems. The playlist file (* .mpls) may include data different from the playback data formed by the playitem. In particular, the playlist file (* .mpls) may include a sub playitem (SubPlayItem) for playing the auxiliary data.

Playlist files (* .mpls) operate only by the commands or programs of the above-described objects. In terms of disk playback scenario, the object executes the dynamic scenario and the playlist file (* .mpls) executes the static scenario.

The Java directory JAVA records a plurality of Java program files (for example, PPPPP.jar or QQQQQ.jar). Various applications are programmed in separate Java program files and each of the programmed applications may also be referred to by the term "Xlet". The Java program file is executed by a dedicated playback device to be described later in FIG. 6B.

Reference character (b) shown in FIG. 2 indicates a reproduction relationship of a specific title using the above-described file structure (a) of FIG. In particular, the reproduction relationship of a specific title when receiving a title reproduction command from the user in relation to the specific title applied to the index table of the index file is described in FIG. 2 (b).

When the data of the disc is loaded, the index file includes first play information "FIRST PLAY" indicating information related to the first playback picture, top menu information "TopMenu" which can provide a menu picture to a title recorded on the disc, and one. The above title information (for example, title # 1 to title # 4) is included. In particular, the aforementioned title (Title # 1 to Title # 4) may be configured in the form of HDMV title or Java title.

Then, when the user selects a specific title (for example, title # 1), the specific playlist is played according to a specific object command or program linked to the title (title # 1) in the object file of the file structure (a). And a specific clip "* .clip" or "* .m2ts" is played by the playitems included in the playlist.

If the selected title (title # 1) is determined to be an HDMV title, it is reproduced by the specific object "M-OBJ" contained in one object file. On the other hand, if the selected title (title # 1) is determined to be a Java title, it is reproduced by the specific object "J-OBJ".

In particular, the present invention provides a playlist file (* .mpls) that can constitute a static scenario associated with a particular title when the particular title is played by an object (M-OBJ or J-OBJ) included in the dynamic scenario. The feature is that the playlist file name information and the locator information accessible for determination are configured in the dynamic scenario. Detailed description thereof will be described with reference to FIGS. 4A to 6B.

3 is a structural diagram showing an exemplary disc structure for recording information related to the file structure (a) on the disc. As shown in Fig. 3, in view of the internal area of the disc, the above-described disc structure includes a file system information area provided as system information for managing the entire file; A database area for recording an index file, an object file, a playlist file, and a clip info file to reproduce recorded streams (* .m2ts); And a stream area for sequentially recording a plurality of streams composed of audio data, video data, graphic data, and the like. In particular, the data recorded in the stream area of the disc can be determined as data having different attributes as described above.

The predetermined area for recording the HDMV title and the Java title is called the title recording area and corresponds to the above-described stream area shown in FIG. The predetermined area for recording file information for title reproduction is called a reproduction management area and corresponds to a file system information area and a database area. The individual regions illustrated in FIG. 3 are provided to describe one example, and the present invention is not limited to the above-described arrangement structure of the regions illustrated in FIG. 3, and may be applied to other examples if necessary.

4A to 4D are structural diagrams showing individual file structures recorded on the disc according to the present invention. 4E is a conceptual diagram showing a playback relationship using the file structure shown in FIGS. 4A to 4D according to the present invention.

The file structure shown in Figs. 4A to 4D is the same as the file structure of Fig. 2A, and the configuration of the object file managing the dynamic scenario is described.

Referring to FIG. 4A, a first object M-OBJ for playing an HDMV title and a second object J-OBJ for playing a Java title are configured independently of each other. The plurality of first objects "M-OBJ" are included in one movie object file (MovieObject.bdmv). The plurality of second objects "J-OBJ" are included in a corresponding Java program file (* .jar). For example, data "J-OBJ 1" is included in the file "PPPPP.jar" and data "J-OBJ 2" is included in the file "QQQQQ.jar".

Compared with the file structure shown in FIG. 4A, FIG. 4B shows a plurality of J-OBJs that may be included in individual Java program files (* .jar). For example, a plurality of objects (for example, J-OBJ 1, J-OBJ 2, ...) are configured in the file "PPPPP.jar" so that a disc that can use various reproduction scenarios can be produced. In this case, however, the start object must be determined in the file "PPPPP.jar". For example, the first object "J-OBJ 1" is used as a start object for executing the file "PPPPP.jar". The above may also be applied to another file "QQQQQ.jar".

Compared with the file structure of Fig. 4A, the file structure shown in Figs. 4C and 4D is the same way that the object J-OBJ for playing Java titles is the same as the object M-OBJ for playing HDMV titles. Make sure to include it in an additional object file (for example, "JavaObject.bdj).

In particular, Fig. 4C shows a "JavaObject.bdj" file and a "MovieObject.bdmv" file arranged in a BD directory as general files. 4D shows a "MovieObject.bdmv" file arranged in a BD directory as a general file and a "JavaObject.bdj" file arranged in a Java directory.

In another example, one Java object file may be organized according to individual Java titles, which correspond to variations of the present invention as is well known in the art.

4E is a conceptual diagram showing a disc reproduction relationship using the file structure recorded on the disc according to the present invention. The relationship shown in FIG. 4E is shown based on the structure of FIG. 4A and may be applied to other examples of FIGS. 4B, 4C, and 4E. In particular, when using the file structure of FIGS. 4C and 4D, the Java object does not exist in the Java program (* .jar) and may be configured in the form of an additional Java object file.

Disc playback relations according to the file structure of the present invention are mainly classified into four layers, namely, stream layer, static scenario layer, dynamic scenario layer, and user interface layer. The stream layer, static scenario layer, dynamic scenario layer and user interface layer will now be described.

The stream layer represents a predetermined area in which actual data is recorded. The stream layer is a predetermined layer in which the above-described stream file (* .m2ts) is recorded. In particular, the flip info file (* .clpi) included in the clip may be included in the static scenario layer rather than the stream layer.

The static scenario layer indicates a predetermined area in which a fixed reproduction management file capable of reproducing data of the stream layer is recorded, and the predetermined playlist file (* .mpls) and the clip information file (* .clpi) described above are recorded. Of layers. Individual playlist files (* .mpls) contain one or more PlayItems that can determine the play interval while a particular clip is playing. The playitem (Item) includes a play start time (In_time) and a play end time (OUT-time) of a specific clip to be played. The operation of reproducing the disc data using the playlist file (* .mpls) means that the disc data is sequentially reproduced in the order of the playitems according to the static scenario, or the plurality of playitems is randomly reproduced. In connection with the above-described operation, the static scenario layer is characterized in that it includes a fixed scenario for playing back a stream recorded on the disc regardless of the title attribute information.

The dynamic scenario layer is defined by the author of the disc and the disc playback scenario can be defined in a variety of ways. The above object information corresponds to the dynamic scenario layer. That is, the time or condition for executing the playlist file included in the specific static scenario is predefined in the dynamic scenario layer, and the specific clip is played using the playlist file while the predefined condition is satisfied. When reproducing data of a disc including contents such as a game, various streams which are reproduced differently according to game environment setup information or game progression are configured so that the dynamic scenario layer described above is required to manage or control the various reproduction scenarios described above.

The user interface layer provides user interaction and provides the user with title category information and menu information recorded on the disc. The user can select a playback command based on the received information. For example, the index file included in the file structure described above corresponds to a user interface layer.

The user can recognize or control only the user interface layer. The remaining layers other than the user interface layer are previously recorded by the disc author and their data cannot be recognized by the user. Therefore, when the user selects a specific title play command using the user interface layer, the static scenario layer is executed through the dynamic scenario layer and the stream included in the stream layer is played according to the scenario information of the static scenario layer.

Hereinafter, an internal operation of the disc capable of performing a predetermined operation related to a user selected specific title will be described. When a user selects an HDMV title from among a plurality of titles recorded on the disc (for example, HDMV titles # 1 and # 2 and Java titles # 3 and # 4) or a Java title from among titles, different playback scenario flows are established. do. In the following, different playback scenario flows will be described.

If a disc having the file structure of Fig. 4C is inserted into the optical recording / reproducing apparatus 10 and a predetermined title (title # 1) representing an HDMV title is reproduced when receiving a title selection command from the user, it is linked to title # 1. The object "M-OBJ 1" must be executed first. In order to execute the object "M-OBJ 1", specific information "Title_mobj_id_ref" that can load the object linked to Title # 1 must be recorded in the syntax of Title # 1. In connection with the above operation, the object "M-OBJ 1" is included in a single "MovieObject.bdmv" file as described above.

When a disc having the above-described file structure is inserted into the optical recording / reproducing apparatus 10 and a predetermined title (title # 3) representing a Java title is reproduced when a title selection command is received from the user, the object linked to title # 3 is " J-OBJ1 "must be executed first. In order to execute the object "J-OBJ 1", specific information "Title_jobj_id_ref ()" or "Title_bdjo_file_name" that can load the object linked to title # 3 must be recorded in the syntax of title # 3.

In connection with the above operation, according to the file structure shown in Figs. 4A and 4B, the object "J-OBJ 1" is included in a single "PPPPP.jar" as the corresponding Java program file. Therefore, the "Title_jobj_id_ref ()" information is the first information (eg, "Jar_file-name") specifying a Java program file containing the corresponding object "J-OBJ" and the second specifying a specific application (application). Contains information. According to the file structure shown in Figs. 4C and 4D, the "J-OBJ 1" object is used as a Java object file. Therefore, the corresponding Java object file is executed through the "Title_bdjo_file_name" described above. That is, the above-described Java object file includes first information (eg, "jar_file_name") designating a specific Java program file and second information (eg, "App_id") designating a specific application.

Therefore, the command to play the playlist file last is executed by the "M-OBJ" object for the HDMV title and by the specific application designated by the "J-OBJ" object for the Java title.

Hereinafter, a detailed relationship of finally reproducing the stream file using the above-described object information (M-OBJ or J-OBJ) will be described with reference to FIGS. 5A and 5B.

5A is a diagram exemplarily illustrating a dynamic scenario and a static scenario of playing an HDMV title according to the present invention. In particular, FIG. 5A shows a process of executing a playlist file using the movie object "M-OBJ".

For convenience of explanation, the remaining layers other than the user interface layer among the four layers described above shown in FIG. 4E are shown in FIG. 5A. In particular, FIG. 5A illustrates the operation of the movie object "M-OBJ" included in the dynamic scenario layer when the user selects a command to play a specific HDMV title. All the movie objects (M-OBJ) included in the dynamic scenario related to the reproduction of the HDMV title are contained in a single movie object file "MovieObject.bdmv". Each movie object M-OBJ is composed of unique instructions. The movie object M-OBJ includes a command for executing a specific playlist file associated with a specific title, for example, the command "Play. <Playlist_id>". As described above, when playlist # 1 is executed by the "M-OBJ 1" object, playitem # 1 included in playlist # 1 is executed, so that specific clip # 1 starts presentation time (IN-time). Is reproduced for a predetermined interval from the presentation to the presentation end time (OUT-time) specified in PlayItem # 1.

In particular, the disc play command contained in the movie object M-OBJ is also called an HDMV locator. Preferably, the HDMV locator is defined only with the command "Play. <Playlist_id>" described above. Therefore, in order to access playitems or clips lower than the playlist, the static scenario layer described above is required.

5B is a conceptual diagram illustrating a scenario of playing a Java title. In particular, FIG. 5B shows a process of playing playlist files and streams using the Java object "J-OBJ".

For convenience of explanation, the remaining layers except the user interface layer among the four layers described above in FIG. 4E are shown in FIG. 5B. In particular, FIG. 5B illustrates the operation of the Java object "J-OBJ" included in the dynamic scenario layer when the user selects a command to play a particular Java title. The Java object " J-OBJ " included in the dynamic scenario related to the reproduction of the Java title includes specific information capable of executing one or more of the plurality of application programs. Therefore, the specific application program is executed by the Java object "J-OBJ", and navigation information that can specify a specific playlist and a specific playitem is recorded in the application program.

The above-described navigation information recorded in the Java application is called a Java locator or BDJ locator and has the following features.

First, the Java locator basically contains information for specifying a specific playlist file included in the static scenario. That is, in order to execute a Java title, the playlist file name or playlist file number associated with the Java title must be determined. For example, the first application program (Application 1) uses only specific information <playlist_id> "for specifying playlist # 1 as a Java locator. Therefore, the playlist specified by the first application program (Application 1) Depending on the static scenario in # 1, a particular stream will play.

Secondly, the Java locator can directly access the playitems included in the playlist or directly access the clips managed for playback by the playitems. Compared to the HDMV locator (see FIG. 5A), which can execute only playlists, the above-described features of the Java locator shown in FIG. 5B are considered to be inherent features of the present invention.

For example, the second application program (Application 2) may have specific information "<playlist_id> [<playitem_id>]" or "<playist_id> [<playlist_offset>]" for specifying a specific position included in playlist # 2. Represents a specific case of use as a Java locator. Therefore, the specific information "<playlist_id> [<playitem_id>]" or "<playist_id> [<playlist_offset>]" will be played from a specific position lower than the playlist # 2 specified by the second application program (Application 2).

In connection with the above description, the "<playlist_id> [<playitem_id>]" information indicates a Java locator that designates one of a plurality of playitems included in the playlist and can directly access a specific playitem stored in the playlist. . The "<playlist_id> [<playlist_offset>]" information designates an access pointer specified by a specific position different from the forward position of the playlist, for example, the access pointer specified by the playlist mark, and the specific position included in the playlist. Used as a Java locator with direct access to.

For example, the third application program (Application 3) may specify specific information for designating a specific position included in playlist # 3 "<playlist_id> [<playitem_id>] [<component_tag>]" or "<playlist_id> [< component_tag>] "represents a specific case where a Java locator is used. Therefore, the specific information "<playlist_id> [<playitem_id>] [<component_tag>]" or "<playlist_id> [<component_tag>]" indicates that the specific location is lower than the playlist # 2 specified by the second application program (Application 2). Will be played from. In relation to the above-described operation, the " <playlist_id> [<playitem_id>] [<component_tag>] " information indicates a Java locator that can directly access a particular clip played by a specific playitem stored in a playlist.

The "<playlist_id> [<component_tag>]" information is specific information that can directly specify the location of a stream having specific data included in a playlist, for example, a specific language stream, a specific angle stream, or a specific text subtitle stream. Works. The "<playlist_id> [<component_tag>]" information is provided as a Java locator that can directly access the specific location contained in the playlist.

As mentioned above, the Java locator can directly specify a particular playlist or a specific location included in the playlist and can access the specified playlist or location. Disc authors can construct more detailed dynamic scenarios. In order to specify a specific playlist or specific location included in the playlist using a Java locator, accessible playlist information is first required. The above accessible playlist information is referred to as "Table_Of-Accessible_PlayList". "Table_Of_Accessible_PlayList" information is recorded in the Java object. For example, as shown in Fig. 4E, the plurality of playlists # 1, # 2, and # 3 operate as playlists managed by the above-described "Table_Of-Accessible_PlayList" information.

6A and 6B are block diagrams showing the optical recording and reproducing apparatus according to the present invention. Specifically, Fig. 6A is a block diagram showing the optical recording and reproducing apparatus 10 according to the present invention. Fig. 6B is a block diagram showing a reproduction processor 17 for reproducing data of a disc on which a player model or a title having a different attribute is recorded according to the present invention.

Referring to FIG. 6A, the optical recording and reproducing apparatus 10 includes a pickup unit 11, a servo unit 14, a signal processor 13, a memory 15, and a microprocessor 16. The pickup unit 11 reads data recorded in the title recording area of the optical disc and reads out management information including file information recorded in the reproduction management area. The servo unit 14 controls the operation of the pickup unit 11. The signal processor 13 receives the playback signal from the pickup unit 11 and restores the received playback signal to a desired signal value or modulates the signal to be recorded with another signal recorded on the optical disc to recover the restored or modulated result. send. The memory 15 stores information necessary for reproducing the data of the disc. The microprocessor 16 controls the overall operation of the above-described components included in the optical recording and reproducing apparatus 10. In connection with the above-described operation, the combination of the above-described components 11, 14, 13, 15, and 16 may also be called a recording / playback section 20, and the recording / playback section 20 may be manufactured in the form of a single product. have. The controller 12 controls all the components shown in FIG. 6A. In particular, the controller 12 receives a playback command of a particular title by interacting with the user in accordance with the present invention.

The playback processor 17 finally receives the control signal from the controller 12 and decodes the output data and sends the decoded result to the user. The playback processor 17 analyzes the decoder 17a for decoding the AV signal, and the commands or programs contained in the user commands and objects received from the controller 12 in connection with the playback of the specific titles described above, and analyzes the results. And a player model 17b that determines the playback direction based on that. However, in any preferred embodiment, player model 17b may include decoder 17a, and playback processor 17 may correspond to the player model shown in FIG. 6B.

When the encoder 18 receives the control signal from the controller 12, it converts the input signal into a specific format signal (e.g., MPEG2 transport stream) and transmits the converted result to the signal processor 13 to transmit the desired signal to the optical disk. Record it.

6B is a detailed block diagram of a player model according to the present invention. The player model includes a module manager 171, a movie module 172, a BDJ module 173, a playback control engine 174, and a presentation engine 175. 6B shows a player model based on the full mode while a Java title is playing, a detailed description of which will be described below.

The movie module 172 which acts as an additional playback process module capable of playing HDMV titles and the BDJ module 173 which acts as an additional playback process module capable of playing back Java titles are configured independently of each other. The movie module 172 receives a command or a program included in the above-described object "M-OBJ", and the BDJ module 173 receives a command or a program included in the above-described object "J-OBJ" and receives a movie module. 172 and BDJ module 173 process the received command or program.

The movie module 172 includes a command processor 172a and the BDJ module 173 includes an application manager 173a and a Java VM 173b, so that the movie module 172 and the BDJ module 173 have the above-described instructions. Alternatively, the program can be received and processed.

In particular, the application manager 173a analyzes the application program included in the Java program including the above-described Java locator, and controls the Java VM 173b to reproduce the application program. When reading a Java locator that plays a specific playlist file or data at a specific location lower than the playlist, the application manager 173b controls the Java VM 173b to play the stream using the playback control engine 174. do.

The module manager 171 transmits a user command to the movie module 172 and the BDJ module 173 to control the operation of the movie module 172 and the BDJ module 173.

When the playback control engine 174 receives a playback command from the movie module 172 and the BDJ module 173, the playback control engine 174 analyzes the playlist file contents (related to the static scenario) recorded on the disc and performs a playback function based on the analyzed result. Perform. The playback control engine 174 stores a playback control function 174a that manages all playback operations, a player status register (PSR) indicating the player's playback environment or playback status, and a player register 174b that stores general purpose register (GPR) information. ). The playback control function 174a may mean a playback control engine 174 as necessary.

Presentation engine 175 may use the display to perform a predetermined presentation to provide a user with a particular stream whose playback is controlled by playback control engine 174.

The module manager 171, the movie module 172, the BDJ module 173 and the playback control engine 174 included in the player model shown in FIG. 6B may be processed by software. The above described components 171, 172, 173 and 174 are preferably processed by software instead of hardware. Presentation engine 175, decoder 17a and graphics plans 17c and 17d are generally hardware based. Components processed by software (eg, 171, 172, 173 and 174) may be integrated into one unit such that the integrated unit may be installed in the controller 12. Therefore, the above-described components of the present invention should be understood based on their meanings and are not limited to implementation methods such as hardware or software implementation.

The HDMV title and Java title each receive a user command based on a different manner. HDMV titles and Java titles use different ways of performing individual user commands. There is a need for a unit that can receive a user command and send the received user command to the movie module 172 or BDJ module 173. In this case, the above-described operations are performed by the user event manager 171a included in the module manager 171. For example, if it is determined that the received command is a user command input by a user operation (UO), the user event manager 171a sends the user command to the UO controller 172b included in the movie module 172. . If it is determined that the received command is a user command input by the key event, the user event manager 171a transmits the received user command to the Java VM 173b included in the BDJ module 173.

One of the modules 172 and 173 manages the playback control engine 174 described above. Specifically, upon playing an HDMV title, the movie module 172 acts as the master of the playback control engine 174. When playing back the Java title, the BDJ module 173 operates as a master of the playback control engine 174.

Graphics plans are managed independently. For example, the HDMV plan 17c controls the presentation engine 175 to operate as a master, and the Java plan 17d controls the Java VM 173b included in the BDJ module 173 to operate as a master. .

Hereinafter, a method of reproducing data of an optical disc using the above-described optical recording and reproducing apparatus will be described. When the disc recorded with the reproduction management file structure shown in one of FIGS. 2, 4A, 4B, 4C, 4D and 4E is loaded into the optical recording / reproducing apparatus, the microprocessor 16 is loaded using the pickup unit 11. The reproduction management file information recorded on the disc is read out, and the recording management file information read in the memory 15 is stored. Upon receiving a user selection command for playing a specific title from the controller 12, the microprocessor 16 reads the specific data according to the playback scenario corresponding to the selected title and reads the data read in the player model shown in Fig. 6B. send. The player model shown in FIG. 6B then recognizes the playback scenario based on various information of the title, for example, attributes, dynamic scenarios acting as object files, and static scenarios acting as playlist files, and playback scenarios. In response to this, one of the movie module 172 and the BDJ module 173 is driven to reproduce the user-selected title.

In connection with the above-described operation, the object file of the dynamic scenario includes a locator that operates as navigation information that can specify a specific playlist file of the static scenario. In particular, the Java locator for playing the Java title can directly specify a playlist file and a specific position included in the playlist, while the HDMV locator for playing the HDMV title can specify only the playlist file.

As is apparent from the above description, the present invention first reads the above-described locator information (i.e., HDMV locator or Java locator) and finally according to the playback scenario specified by the read locator information (i.e., HDMV locator or Java locator). Play the data on the disc.

Of course, various modifications by those skilled in the art are possible without departing from the spirit or scope of the invention. Therefore, the present invention includes not only the following claims but also modifications within the equivalents of the claims.

Claims (18)

A recording area in which at least one first title and at least one second title having different attributes are recorded; And Playback management area for playing back individual titles with different attributes Including, A static scenario and a dynamic scenario are recorded in the reproduction management area, the static scenario is commonly applied to the first and second titles, and the dynamic scenario is included in each of the first and second titles. Recording media. The recording medium of claim 1, wherein the first title is an HDMV title, and the second title is a Java title. 3. The recording medium of claim 2, wherein the static scenario comprises a playlist file. 4. The recording medium of claim 3, wherein the dynamic scenario for the HDMV title includes a movie object (M-OBJ). 5. The recording medium of claim 4, wherein the dynamic scenario for the HDMV title includes locator information for designating a specific playlist file constituting the static scenario. 4. The recording medium of claim 3, wherein the dynamic scenario for the Java title includes a Java object (J-OBJ). 7. The recording medium of claim 6, wherein the dynamic scenario for the Java title includes locator information for specifying a specific playlist file constituting the static scenario. 7. The recording medium of claim 6, wherein the dynamic scenario for the Java title includes locator information for specifying a specific position included in the playlist file. 9. The recording medium of claim 8, wherein the specific position included in the playlist file specified by the locator information is determined based on the playitems included in the playlist. 9. The recording medium of claim 8, wherein a specific position included in the playlist file specified by the locator information is determined based on a specific stream included in the playlist. 8. The recording medium of claim 7, wherein the locator information is included in a Java application program. A recording area in which one or more titles are recorded; And A reproduction management area for reproducing all titles included in the recording area Including; Static scenarios and dynamic scenarios are recorded in the reproduction management area, wherein the static scenarios include a plurality of playlist files for playing all titles, and the dynamic scenarios of the individual titles are among playlist files included in the static scenarios. And information related to one or more accessible playlist files for playing the title. A recording area in which one or more titles are recorded; And A reproduction management area for reproducing all titles included in the recording area Including; Static scenarios and dynamic scenarios are recorded in the playback management area, wherein the static scenarios include a plurality of playlist files for playing all titles, and the dynamic scenarios of individual titles are playlist files included in the static scenarios. And a locator information capable of designating one of them. The recording medium of claim 13, wherein the locator information is included in a Java application program. The first title and the second title having different attributes are recorded independently of each other, the dynamic scenario included in each of the titles having different attributes is recorded, and the static scenario is the first and the second regardless of the attribute information of the individual titles. A method for reproducing data of a recording medium commonly included in two titles, (a) reading the dynamic scenario and the static scenario and recognizing locator information included in the dynamic scenario to designate the static scenario; And (b) playing a specific playlist file capable of constructing the corresponding static scenario specified by the locator information; Method comprising a. 16. The method of claim 15, wherein the locator information indicates specific information for specifying a specific location included in a specific playlist file of the static scenario. The first title and the second title having different attributes are recorded independently of each other, the dynamic scenario included in each of the titles having different attributes is recorded, and the static scenario is the first and the second regardless of the attribute information of the individual titles. An apparatus for recording and reproducing data on a recording medium recorded in common to two titles, A recording and reproducing section which reads out the dynamic scenario and the static scenario recorded on the recording medium; And A player model that reads locator information that can specify the static scenario from the dynamic scenario and plays a specific playlist file included in the static scenario specified by the read locator information. Apparatus comprising a. 18. The apparatus of claim 17, wherein the locator information indicates specific information for specifying a specific location included in a specific playlist file of the static scenario.

Images