JP2006216103A - Information storage medium, information recording medium, and information reproducing method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To realize control of a video object which is reproduced by a different method from existing reproduction sequence for the contents recorded in a read-only information storage medium for and its reproduction order. <P>SOLUTION: Information of a play list reproduced first is recorded, when the information storage medium has advanced content. The information of this play list is constituted, by including object mapping information included for each title and mapped on a time base of this title, and reproduction information or the like for each title described by the time base. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to an information storage medium such as an optical disk, a method for recording information on the information storage medium, and a method for reproducing the information storage medium.

  In recent years, DVD video discs having high image quality and high functions and video players that play back the discs have become widespread, and peripheral devices that play back the multi-channel audio also have a wider selection. A home theater can be realized in close proximity, and an environment in which movies and animations with high image quality and high sound quality can be freely viewed at home is being prepared. In addition, as shown in Patent Document 1, a playback apparatus has also been proposed that can display various menus in a superimposed manner by changing the color of characters on a playback video from a disc.

However, with the improvement of image compression technology over the past few years, both users and content suppliers have voiced hope for higher image quality. In addition to the above-mentioned high image quality, the content of menu screens and special videos, including the main title, is more attractive to users by expanding the content, such as more colorful menus and improved interactiveness. Content providing environments are desired by content suppliers. Furthermore, users want to enjoy content freely by playing back still image data captured by the user, subtitle text obtained through Internet connection, etc., by freely specifying the playback position, playback area, or playback time by the user. Etc. are increasing.
Japanese Patent Laid-Open No. 10-50036

  As described above, in addition to the realization of high-quality images in the main title, content such as menu screens and privilege videos can be enhanced by enhancing the contents of the content, such as more colorful menus and improved interactivity. There is a demand for an attractive content provision environment.

  On the other hand, production of a menu rich in color and highly interactive content requires a technology different from conventional content production, and therefore, it is necessary to spend a lot of time to acquire the technology. For this reason, there is also a need for a content providing environment that can be manufactured by the conventional manufacturing technique (although it may not be functionally different from the conventional one), and that improves the quality of the main title.

  Further, in a conventional DVD video disc (ROM disc), which is set by a content creator and is determined based on program chain (Program Chain: PGC for short) information recorded on the disc. The video object to be played (called VOB or EVOB) and / or its playback order. However, the video objects to be played back and their playback order are determined when the disc is manufactured, and this cannot be changed after the disc is manufactured. That is, as a content creator, when it is desired to change the video object to be played back and the playback order thereof, it is necessary to newly regenerate management information of the DVD video disc and record the changed PGC on the new disc. As a user, it was necessary to purchase a DVD video disc in which the changed PGC was recorded.

  The present invention has been made in view of the above points, and one of the problems of the present invention is to use reproduction control information realized by a markup language or the like for content recorded on a conventional DVD video disc. This is to realize control of a video object to be reproduced and its reproduction order.

  In other words, it provides an environment that realizes control of a video object that is played back by a method different from an existing playback sequence and the playback order of content recorded on a playback-only information storage medium such as a DVD video disk. That is.

  An information storage medium (1) according to an embodiment of the present invention includes a management area (30) for recording management information (HDVMG), and an object area (HDVTS, AHDVTS) for managing the management information (HDVTS). 40, 50) and an advanced content recording area (21) including information (21A-21E) different from the recording contents (30-50) of the video data recording area (20). And a file information area (11) for storing file information (FIG. 2) corresponding to the recorded contents of the data area (12). Here, when the information storage medium has the advanced content, information of a playlist to be played first (prior to playback of the advanced content) (Object Mapping Information; Playback Sequence; Configuration Information, etc. in FIG. 236), The data area (211A and 215A in FIG. 50e) can be stored.

  By practicing the present invention, it is possible to provide an information storage medium capable of realizing various expressions and constructing attractive contents, and a reproducing apparatus thereof.

  Hereinafter, an information storage medium, an information reproduction method, and an information reproduction apparatus according to an embodiment of the present invention will be described with reference to the drawings as appropriate. FIG. 1 is a diagram for explaining information contents recorded on a disk-shaped information storage medium according to an embodiment of the present invention. An information storage medium 1 shown in FIG. 1A is a high density optical disk (High Density or High Definition Digital Versatile Disc: HD_DVD for short) using, for example, a red laser with a wavelength of 650 nm or a blue laser with a wavelength of 405 nm (or less). Can be configured.

  As shown in FIG. 1B, the information storage medium 1 includes a lead-in area 10, a data area 12, and a lead-out area 13 from the inner periphery side. The information storage medium 1 employs an ISO9660 and UDF bridge structure for the file system, and has an ISO9660 and UDF volume / file structure information area 11 on the lead-in side of the data area 12.

In the data area 12, as shown in FIG. 1C, a video data recording area 20 for recording DVD video content (also referred to as standard content or SD content) and another video data recording area (advanced content is recorded). In this case, a mixed arrangement of the advanced content recording area) 21 and the general computer information recording area 22 is permitted. (Here, the plural expression “content” includes the contents of the singular expression “content”. The content also includes the meaning of “single singular content”.)
In the video data recording area 20, as shown in FIG. 1 (d), an HD video manager (HDVMG: High Definition compatible video) in which management information related to the entire HD_DVD video content recorded in the video data recording area 20 is recorded. Maneger) HD video title set (HD VTS: Video Title Set: Standard VTS corresponding to High Definition) in which recording area 30 and management information and video information (video object) for each title are recorded together. A recording area 40, and an advanced HD video title set (AHDVTS: also called advanced VTS) recording area 50.

  In the HD video manager (HDVMG) recording area 30, as shown in FIG. 1E, HD video manager information (HDVMGI: Video Manager Informaiton corresponding to High Definition) indicating management information relating to the entire video data recording area 20. Area 31, HD video manager information backup (HDVMGI_BUP) area 34 in which the same information as HD video manager information area 31 is recorded, and a top menu screen showing the entire video data recording area 20. The video object (HDVMGM_VOBS) area 32 is included.

  In one embodiment of the present invention, a menu audio object (HDMENU_AOBS) area 33 is provided in the HD video manager recording area 30 in which audio information to be output in parallel during menu display is recorded. Furthermore, in one embodiment of the present invention, the language selection menu VOBS (FP_PGCM_VOBS) 35 for the first play PGC executed at the first access immediately after the disc (information storage medium) 1 is loaded in the disc drive is provided in the area. In addition, a screen on which a menu description language code or the like can be set can be recorded.

  In one HD video title set (HDVTS) recording area 40 in which management information and video information (video object) for each title are recorded together, management information for all contents in the HD video title set recording area 40 is stored. HD video title set information (HDVTSI) area 41 in which is recorded, HD video title set information backup (HDVTSI_BUP) area 44 in which exactly the same information as HD video title set information area 41 is recorded as backup data, and video Menu video object area (HDVTSM_VOBS) 42 in which information on the menu screen in units of title sets is recorded, and a video object data (title video information) in the video title set. It is configured to include a Le video object (HDVTSTT_VOBS) area 43.

  FIG. 2 is a diagram for explaining an example of a file system for managing content recorded on a disc-shaped information storage medium according to an embodiment of the present invention. Each area (30, 40) in FIG. 1 constitutes a separate file in a file system having a bridge structure of ISO9660 and UDF. Conventional (standard SD) DVD video contents are collectively arranged under a directory named “VIDEO_TS”. On the other hand, a file according to an embodiment of the present invention handles an HVDVD_TS directory storing an information file for handling high definition video and an advanced object under the root directory, as illustrated in FIG. An ADV_OBJ directory for storing information files is arranged.

  In the HVDVD_TS directory, there are roughly divided a file group belonging to a menu group used for menus and a file group belonging to a title set group used for titles. The file group belonging to the menu group includes a video manager information file (HVI00001.IFO) that contains information for managing the entire disc, its backup file (HVI00001.BUP), and a menu used as a menu background screen. Stores playback data files (HVM00001.EVO to HVM00003.EVO) of the extended video object set.

  The file group belonging to the group of title set #n (such as title set # 1 group) includes an information file for video title set (HVIxxx01.IFO: xxx = 001 to 999) having information for managing title set #n. The backup file (HVIxxx01.BUP: xxx = 001 to 999) and the playback data file of the extended video object set for title set #n used as the title (HVTxxxyy.EVO: xxx = 001 to 999, yy = 01 to 99) is stored.

  In addition, the file group belonging to the advanced title set group includes a video title set information file (HVIA0001.IFO) having information for managing the advanced title set, a backup file (HVIA0001.BUP), and a title file. Advanced title set extended video object set playback data file (HVTAxxyy.EVO: xx = 01 to 99, yy = 01 to 99) and advanced title set time map information file (HVMAxxxx.MAP:xxxx=0001 to 999) and the backup file (HVMAxxxx.BUP: xxxx = 0001 to 9999, not shown) and the like are stored.

  In the ADV_OBJ directory, a startup information file (STARTUP.XML), a loading information file (LOAD001.XML), a playback sequence information file (PBSEQ001.XML), a markup language file (PAGE001.XML), video data, Animation data, still image data files, audio data files, font data files, and the like are stored. Here, the contents of the startup information file include, for example, moving image data, animation data, still image data, audio data, font data, and data activation information such as a markup language for controlling the reproduction of these data. Become. The loading information file stores loading information (information that can be described in Markup language / Script language / StyleSheet, etc.) in which information relating to the file to be loaded into the buffer in the playback apparatus is described.

  The playback sequence information file (PBSEQ001.XML) contains playback sequence information that defines which section of the playback data file of the advanced title set extended video object set in the advanced title set group is to be played (also in Markup language, etc.). Etc.) are recorded.

  Here, the markup language (Markup language) is a language that describes character attributes in accordance with predefined commands, and gives the type, size, color, etc. of the font as attributes. be able to. In other words, a markup language is a text structure (headings, hyperlinks, etc.) or modification information (character size, This is a description language that describes the state of composition, etc.) in a sentence.

  Documents written using the markup language become text files, so they can be read normally by a human using a text editor, and of course can be edited. Typical markup languages include SGML (Standard Generalized Markup Language), HTML (HyperText Markup Language) developed from SGML, TeX, and the like.

  FIG. 3 shows an example of the detailed data structure in the HD video manager information (HDVMGI) area 31 shown in FIG. In this area 31, an HD video manager information management table (HDVMGI_MAT) 310 that collectively records management information common to the entire HD_DVD video content recorded in the video data recording area 20 is arranged at the head, and thereafter in order. Title search pointer table (TT_SRPT) 311 in which information useful for searching for each title existing in the HD_DVD video content (detecting a cue position) is recorded, and menus arranged separately for each menu description language code for displaying a menu HD video manager menu program chain information unit table (HDVMGM_PGCI_UT) 312 in which screen management information is recorded, information for managing video that is shown to children and video that cannot be shown as parental information Rental management information table (PTL_MAIT) 313, HD video title set attribute information table (HDVTS_ATRT) 314 collectively recorded with respect to title set attributes, Text data manager (TXTDT_MG) collectively recorded with text information to be displayed to the user 315, HD video manager menu cell address table (HDVMGM_C_ADT) 316 in which information useful for searching the start address of the cells constituting the menu screen is recorded, and VOBU address information indicating the minimum unit of the video object constituting the menu screen is recorded HD video manager menu video object unit address map (HDVMGM_VOBU_ADMAP) 317, and HD menu audio object Kutosetto information table (HDMENU_AOBSIT) 318 are stored. Management data for an object in the menu audio object (HDMENU_AOBS) area 33 is recorded in an HD menu audio object set information table (HDMENU_AOBIT) 318 in the HD video manager information (HDVMGI) area 31.

  Here, the data structure from the HD video manager information management table (HDVMGI_MAT) 310 to the HD video manager menu video object unit address map (HDVMGM_VOBU_ADMA) 317 matches the management information of the conventional DVD video.

  In one embodiment of the present invention, the newly added HD menu audio object set information table (HDMENU_AOBIT) 318 is divided from the portion that matches the management information of the conventional DVD video, and is arranged thereafter. . By doing so, the description of the conventional control program using the management information of the conventional DVD video can be used in the embodiment of the present invention (the description of the control program using the management information having the same data structure as that of the conventional DVD video). Can be used for both the conventional and the present invention). Thereby, it is possible to simplify the creation of the control program of the information reproducing apparatus corresponding to the embodiment of the present invention.

  FIG. 4 shows an example of the detailed data structure in HD video manager information management table (HDVMGI_MAT) 310 of FIG. In this management table 310, information of the first play PGCI (FP_PGCI) in which management information for the language selection menu for the user is recorded, head address information of HDMENU_AOBS (HDMENU_AOBS_SA), head address information of the HDVMGM_AOBS information table ( HDMENU_AOBSIT_SA), HDVMGM graphic unit stream number information (HDVMGM_GUST_Ns), HDVMGM graphic unit stream attribute information (HDVMGM_GUST_ATR), and the like.

  In addition, in the HD video manager information management table (HDVMGI_MAT) 310, an HD video manager identifier (HDVMG_ID), an HD video manager end address (HDVMG_EA), an HD video manager information end address (HDVMGI_EA), an HD_DVD video standard Version number (VERN), HD video manager category (HDVMG_CAT), volume set identifier (VLMS_ID), adaptation identifier (ADP_ID), number of HD video title sets (HDVTS_Ns), provider-specific identifier (PVR_ID), POS code (POS_CD) , HD video manager information management table end address (HDVMGI_MAT_EA), first play program Start information (FP_PGCI_SA), HDVMGM_VOBS start address (HDVMGM_VOBS_SA), TT_SRPT start address (TT_SRPT_SA), HDVMGM_PGCI_UT start address (HDVMGM_PGCI_UT_SA), PTL_MA_IT_IT_IT_IT_IT_IT_IT_IT_IT_IT_IT_IT_IT_IT_IT_IT_IT_IT TXTDT_MG start address (TXTDT_MG_SA), HDVMGM_C_ADT start address (HDVMGM_C_ADT_SA), HDVMGM_VOBU_ADMAP start address (HDVMGM_VOBU_ADMAP_SA), HDVMGMTR GHD_VMGM_HD GM number of audio streams (HDVMGM_AST_Ns), HDVMGM audio stream attribute of (HDVMGM_AST_ATR), various kinds of information of a sub-picture stream number of HDVMGM (HDVMGM_SPST_Ns), and HDVMGM sub-picture stream attribute (HDVMGM_SPST_ART) is recorded.

In FIG. 4, the HD video manager category (HDVMG_CAT) includes RMA # 1, RMA # 2, RMA # 3, RMA # 4, RMA indicating reproduction availability information in each region determined by dividing the countries of the world into predetermined regions. # 5, RMA # 6, RMA # 7, RMA # 8, and an application type indicating the category of VMG. Where Application Type is
Application Type = 0000b: Includes standard VTS only
= 0001b: Includes only advanced VTS
= 0010b: Contains values including both advanced VTS and standard VTS. That is, when the Application Type is “0000b”, this information storage medium is an information storage medium (content type 1 disc) including only the standard VTS, and when the Application Type is “0001b”, this information storage medium is This indicates that the information storage medium (content type 2 disc) includes only the advanced VTS, and when the Application Type is “0010b”, the information storage medium is an information storage medium (content type 2) including both the standard VTS and the advanced VTS. Disk) (details will be described later).

  FIG. 5 exemplifies the internal structure of the title search pointer table (TT_SRPT) 311 shown in FIG. The title search pointer table (TT_SRPT) 311 includes title search pointer table information (TT_SRPTI) 311a and title search pointer (TT_SRP) information 311b. One or more title search pointer (TT_SRP) information 311b in the title search pointer table (TT_SRPT) 311 can be set according to the number of titles included in the HD_DVD video content. Common search information of the title search pointer table (TT_SRPT) 311 is recorded in the title search pointer table information (TT_SRPTI) 311a. The number of title search pointers (TT_SRP_Ns) included in the title search pointer table (TT_SRPT) 311 The end address (TT_SRPT_EA) information of this title search pointer table (TT_SRPT) 311 in the file (HD_VMG00.HDI in FIG. 2) in the HD video manager information (HDVMGI) area is recorded.

  In one title search pointer (TT_SRP) information 311b, the title playback type (TT_PB_TY), the number of angles (AGL_Ns), the number of part of titles (PTT: Part_of_Title) (PTT_Ns) related to the title indicated by the search pointer, Title parental ID field (TT_PTL_ID_FLD) information, HDVTS number (HDVTSN), HDVTS title number (HDVTS_TTN), and various information of the head address (HDVTS_SA) of this HDVTS are recorded.

  FIG. 6 shows an example of the internal structure of HD video manager menu PGCI unit table (HDVMGM_PGCI_UT) 312 shown in FIG. The HD video manager menu PGCI unit table (HDVMGM_PGCI_UT) 312 includes HD video manager menu program chain information unit table information (HDVMGM_PGCI_UTI) 312a in which common management information in the HD video manager menu PGCI unit table (HDVMGM_PGCI_UT) 312 is recorded. In addition, an HD video manager menu language unit (HDVMGM_LU) 312c or the like in which management information related to menu information is recorded is recorded for each menu description language code for displaying the menu. There are as many information of HD video manager menu language units (HDVMGM_LU) 312c as the number of menu description language codes supported by the HD_DVD video content. In the HD video manager menu PGCI unit table (HDVMGM_PGCI_UT) 312, each HD video manager menu language unit (HDVMGM_LU) is provided to facilitate access to the HD video manager menu language unit (HDVMGM_LU) 312 c for each menu description language code. The information 312b of the HD video manager menu language unit search pointer (HDVMGM_LU_SRP) having the head address information of 312c is provided by the number of each HD video manager language unit (HDVMGM_LU) 312c.

  The HD video manager menu PGCI unit table (HDVMGM_PGCI_UT) 312a includes the number of HD video manager menu language units (HDVMGM_LU_Ns) information and the HD video manager information (HDVMGI) area file (HD_VMG00.HDI in FIG. 2). It has end address (HDVMGM_PGCI_UT_EA) information of the HD video manager menu PGCI unit table (HDVMGM_PGCI_UT) 312.

  The HD video manager menu language unit search pointer (HDVMGM_LU_SRP) information 312b includes the HD video manager menu PGCI unit table in the HD video manager information (HDVMGI) area file (HD_VMG00.HDI in FIG. 2) as described above. (HDVMGM_PGCI_UT) Not only has differential address information (HDVMGM_UT_SA) from the start position of 312 to the start position of the corresponding HD video manager menu language unit (HDVMGM_LU) 312c, but also the corresponding HD video manager menu language unit (HDVMGM_LU) 312c Information of the HD video manager menu language code (HDVMGM_LCD) indicating the menu description language code and the corresponding HD video management Menu Language Unit (HDVMGM_LU) 312c is also a presence (HDVMGM_EXST) information HD video manager menu indicating whether with a menu screen to be displayed to the user as a video object (VOB or EVOB).

  FIG. 7 illustrates a detailed data structure in the HD video manager menu language unit #n (HDVMGM_LU # n) 312c (FIG. 6) recorded in the HD video manager menu PGCI (HDVMGM_PGCI_UT) 312 shown in FIG. ing. The HD video manager menu language unit (HDVMGM_LU) 312c includes HD video manager menu language unit information (HDVMGM_LUI) 312c1 in which common management information related to menus in the HD video manager menu language unit (HDVMGM_LU) 312c is recorded, and FIG. HD video manager menu program chain information (HDVMGM_PGCI) 312c3 and HD video manager menu language unit (HDVMGM_LU) in the HD video manager information (HDVMGI) area file (HD_VMG00.HDI) in FIG. Difference address from 312c head position to head position of each HD video manager menu program chain information (HDVMGM_PGCI) 312c3 With each information HDVMGM_PGCI search pointer (HDVMGM_PGCI_SRP # 1~ # n) of information 312c2 indicating.

  The HD video manager main language unit information (HDVMGM_LUI) 312c1 arranged in the first area (group) in the HD video manager menu language unit #n (HDVMGM_LU # n) 312c includes information on the number of HDVMGM_PGCI_SRP (HDVMGM_PGCI_SRP_Ns) and HDVMGM_LU End address (HDVMGM_LU_EA) information. Also, information 312c2 of the HDVMGM_PGCI search pointer (HDVMGM_PGCI_SRP # 1 to #n) has the head address (HDVMGM_PGCI_SA) information and HDVMGM_PGC category (HDVMGM_PGC_CAT) information of HDVMGM_PGCI.

FIG. 8 is a diagram exemplifying recorded contents of the HDVMGM_PGC category (HDVMGM_PGC_CAT) shown in FIG. In the HDVMGM_PGC category information (HDVMGM_PGC_CAT) in the HDVMGM_PGCI search pointer #n (HDVMGM_PGCI_SRP # n) 312c2, selection information of audio information to be reproduced simultaneously when the HD content menu according to the embodiment of the present invention is displayed on the screen, An audio information selection flag (Audio Selection information) indicating start / end trigger information of audio information reproduction is recorded. As audio data to be played back simultaneously when the HD content menu in one embodiment of the present invention is displayed on the screen,
<1> Audio data recorded in the menu video object area (HDVMGM_VOBS) 32 shown in FIG. 1 (e) (not shown but distributedly recorded in the Audio Pack), or <2> FIG. Audio data that exists in the menu audio object area (HDMENU_AOBS) 33 shown in (e) and in which one or more menu AOBs (HDMENU_AOB) are arranged in order as shown in FIG. 19 can be selected.

  Here, when “00b” of the audio information selection flag (Audio Selection information) is selected, the audio data <1> is reproduced, and the audio reproduction is interrupted when the menu is switched. When “10b” or “11b” of the audio information selection flag (Audio Selection information) is selected, the menu AOB (HDMENU_AOB) existing in the menu audio object area (HDMENU_AOBS) 33 shown in <2>. Audio data is played back. When reproducing the audio data shown in <2>, if the audio information selection flag designates “11b”, the audio data starts reproduction from the beginning every time the menu screen is changed, and designates “10b”. In such a case, the reproduction of the audio data is continued regardless of the switching of the menu screen.

  In the embodiment of the present invention, a plurality of types of menu AOBs (HDMENU_AOB) can be stored in the menu audio object area (HDMENU_AOBS) 33 as shown in FIG. The audio information number (Audio Number information) shown in FIG. 8 can be used as selection information for a menu AOB (HDMENU_AOB) to be played back simultaneously when the corresponding menu display PGC is displayed. As the selection candidates for the menu AOB, among the menu AOBs arranged as shown in FIG. 19, “how many AOBs to select from the top” can be selected by this audio information number.

  In addition, the HDVMGM_PGC category (HDVMGM_PGC_CAT) information in FIG. 8 includes entry type information for determining whether or not the entry PGC is included, menu ID information indicating menu identification (for example, a title menu), block mode information, Block type information, PTL_ID_FLD information, and the like can be recorded.

  FIG. 9 shows an example of the data structure in the parental management information table (PTL_MAIT) 313 shown in FIG. As illustrated in FIG. 9, the parental management information table 313 includes parental management information table information (PTL_MAITI) 313a, one or more parental management information search pointers (PTL_MAI_SRP # 1 to #n) 313b, The number of parental management information (PTL_MAI # 1 to #n) 313c corresponding to the search pointer is included. Here, information such as the number of countries (CTY_Ns), the number of HDVTSs (HDVTS_Ns), the end address of PTL_MAIT (PTL_MAIT_EA), etc. is recorded in the parental management information table information (PTL_MAITI) 313a. In (PTL_MAI_SRP) 313b, information such as the country code (CTY_CD) and the start address (PTL_MAI_SA) of PTL_MAI is recorded.

  FIG. 10 shows an example of the data structure in parental management information (PTL_MAI) 313c shown in FIG. The parental management information 313c includes one or more parental level information (PTL_LVLI) 313c1. Each parental level information (PTL_LVLI) 313c1 includes information of an HDVMG parental ID field (PTL_ID_FLD_HDVMG) 313c11 and an HDVTS parental ID field (PTL_ID_FLD_HDVTS) 313c12. The parental ID field for PGC selection (PTL_ID_FLD) can be stored in the information of each parental ID field for HDVTS (PTL_ID_FLD_HDVTS) 313c12.

  FIG. 11 shows an example of the data structure of HD video title set attribute information table (HDVTS_ATRT) 314 shown in FIG. As shown in FIG. 11, the HD video title set attribute information table 314 includes HD video title set attribute table information (HDVTS_ATRTI) 314a having HDVTS number (HDVTS_NRT) and HDVTS_ATRT end address (HDVTS_ATRT_EA) information; and HDVTS_ATR; HDVTS video title set attribute search pointer (HDVTS_ATR_SRP) 314b in which information of the start address (HDVTS_ATR_SA) is recorded; HDVTS_ATR end address (HDVTS_ATRT_EA), HD video title set category (HDVTS_CAT), and HD video title set HDVTS video title having attribute information (HDVTS_ATRI) information Tsu door attribute (HDVTS_ATR) configured to include a and 314c.

  FIG. 12 shows an example of the data structure of text data manager (TXTDT_MG) 315 shown in FIG. As shown in FIG. 12, the text data manager 315 includes text data manager information (TXTDT_MGI) having information on a text data identifier (TXTDT_ID), a number of TXTDT_LU (TXTDT_LU_Ns), and an end address (TXTDT_MG_EA) of the text data manager. Text data language unit search pointer (TXTDT_LU_SRP) 315b in which various information of the text data language code (TXTDT_LCD), character set (CHRS), and TXTDT_LU start address (TXTDT_LU_SA) is recorded; and text data language unit (TXTDT_LU) ) 315c.

  FIG. 13 illustrates an internal data structure of the text data language unit (TXTDT_LU) 315c. In this text data language unit 315c, as shown in FIG. 13, the text data language unit information (TXTDT_LUI) 315c1 in which the end address (TXTDT_LU_EA) information of TXTDT_LU is recorded; Item text search pointer search pointer for volume (IT_TXT_SRP_SRP_VLM) 315c2; Title item text search pointer search pointer (IT_TXT_SRP_SRP_SRP_TT) 315T3T3c3D and text data 315c3; Contains various information It is configured.

  FIG. 14 illustrates an internal data structure of text data (TXTDT) 315c4. In this text data 315c4, as shown in FIG. 14, text data information (TXTDTI) 315c41 having information of the number of IT_TXT_SRPs (IT_TXT_SRP_Ns); an item text identifier code (IT_TXT_IDCD) and the head address (IT_TXT_SA) of IT_TXT Various information of item text search pointer (IT_TXT_SRP) 315c42 in which information is recorded and item text (IT_TXT) 315c43 is recorded.

  FIG. 15 shows an example of the data structure of HD video manager menu cell address table (HDVMGM_C_ADT) 316 shown in FIG. In this HD video manager menu cell address table 316, as shown in FIG. 15, HD video manager menu cell address table information (HDVMGM_C_ADT_EA) having information on the number of VOBs in HDVMGM_VOBS (HDVMGM_VOB_Ns) and the end address of HDVMGM_C_ADT (HDVMGM_C_ADT_EA). HDVMGM_C_ADTI) 316a; HDVMGM_CP VOB_ID number (HDVMGM_VOB_IDN), HDVMGM_CP Cell_ID number (HDVMGM_C_IDN), HD_GMGM_CP start address (HDVMGM_CP_SA) information( DVMGM_CPI) 316b various kinds of information are recorded ( "CP" is cell piece of HDVMGM_CP).

  FIG. 16 shows an example of the data structure of HD video manager menu video object unit address map (HDVMGM_VOBU_ADMAP) 317 shown in FIG. In this HD video manager menu video object unit address map 317, as shown in FIG. 16, HDVMGM_VOBU_ADMAP end address (HDVMGM_VOBU_ADMAP_EA) information HD video manager menu video object unit address map information (HDVMGM_VOBU_ADAPI) 317a and HDVMGM_ Various information of the start address (HDVMGM_VOBU_AD # 1 to #n) 317b is recorded.

  FIG. 17 shows the contents of management information for the menu audio object (HDMENU_AOB) itself, and the HD menu audio object set shown in FIG. 3 existing in the HD video manager information (HDVMGI) area 31 shown in FIG. The internal data structure of the information table (HDMENU_AOBIT) 318 is illustrated. As shown in FIG. 17, HD menu audio object set information table information (HDMENU_AOBSITI) 318a arranged at the beginning of the HD menu audio object set information table 318 includes HDMENU_AOB_Ns and HDMENU_AOBSIT which are AOB number information in HDMENU_AOBS. End address information (HDMENU_AOBIT_EA) exists. In one embodiment of the present invention, a plurality of types of menu audio objects (audio data) can be recorded in the information storage medium 1.

  In the HD menu audio object set information table 318 of FIG. 17, one or more HD menu audio object information (HDMENU_AOBI) 318b is arranged following the HD menu audio object set information table information 318a. Each HD menu audio object information (HDMENU_AOBI) 318b indicates management information for each menu audio object (audio data). Each of the HDMENU_AOB playback information (HDMENU_AOB_PBI), HDMENU_AOB attribute information (HDMENU_AOB_ATR), and HDMENU_AOB ## HDMENU_AOB) start address information (HDMENU_AOB_SA) and HDMENU_AOB # n (corresponding HDMENU_AOB) end address information (HDMENU_AOB_EA).

  FIG. 18 shows an example of the data structure in the menu video object area (HDVMGM_VOBS) 32 shown in FIG. 1 (e) stored together in a file “HD_VMG01.HDV” (not shown, but HD_VMG01). The .HDV file can be a file in the menu group of FIG. In the menu video object area 32, as shown in FIG. 18, menu screens (video objects) in which the same menu screen is recorded with different menu description language codes are arranged side by side. In this way, a plurality of menu screens in a plurality of languages are prepared, and one or more of them can be arbitrarily selected and displayed on the menu screen. For example, if only one Japanese menu VOB is selected, a Japanese menu can be displayed, and if only one English menu VOB is selected, an English menu can be displayed. Alternatively, when the display screen is configured to be capable of multi-window display, the Japanese menu and the English menu VOB can be displayed simultaneously by selecting the Japanese menu VOB and the English menu VOB. You can also.

  FIG. 19 is a diagram illustrating a data structure of a menu audio object area (HDMENU_AOBS) 33 recorded in the HD video manager (HDVMG) recording area. In one embodiment of the present invention, a plurality of types of menu audio objects (audio data) can be recorded in the information storage medium 1. The recording location of the audio object for menu (AOB) is, for example, in the audio object area for menu (HDMENU_AOBS) 33 in the HD video manager recording area (HDVMG) 30 as shown in FIG. The (HDMENU_AOBS) 33 constitutes one file having a file name “HD_MENU0.HDA”, for example (not shown, but the HD_MENU0.HDA file can be a file in the menu group of FIG. 2). Each menu audio object (AOB) is sequentially arranged as shown in FIG. 19 in a menu audio object area (HDMENU_AOBS) 33 constituting one file having a file name “HD_MENU0.HDA”. Are recorded.

  FIG. 20 is a diagram illustrating a data structure of HD video title set information (HDVTSI) 41 recorded in each HD video title set (HDVTS # n) recording area. This HD video title set information 41 is, for example, in the “HVI00101.IFO” and / or “HVIA0001.IFO” file (or another file in the DVD video content “VTS00100.IFO” not shown) shown in FIG. Are recorded together. The HD video title set information (HDVTSI) area 41 shown in FIG. 1F includes an HD video title set information management table (HDVTSI_MAT) 410, an HD video title set PTT search pointer table (see FIG. 20). HDVTS_PTT_SRPT) 411, HD video title set program chain information table (HDVTS_PGCIT) 412, HD video title set menu PGCI unit table (HDVTSM_PGCI_UT) 413, HD video title set time map table (HDVTS_TMAPT) 414, HD video title set menu cell address table (HDVTSM_C_ADT) 415, HD video title set menu video object unit Divided into Tsu preparative address map (HDVTSM_VOBU_ADMAP) 416, HD video title set cell address table (HDVTS_C_ADT) 417, HD video title set video object unit each area (management information group) of the address map (HDVTS_VOBU_ADMAP) 418.

  In the HD video title set information management table (HDVTSI_MAT) 410, management information common to the corresponding video title set is recorded. By arranging this common management information (HDVTSI_MAT) in the first area (management information group) in the HD video title set information (HDVTSI) area 41, the video title set can be immediately set (before the object playback is started). Since the common management information can be read, the reproduction control process of the information reproduction apparatus can be simplified and the control process time can be shortened.

  FIG. 21 is a diagram illustrating a data structure of an HD video title set information management table (HDVTSI_MAT) recorded in HD video title set information (HDVTSI). The management information related to the graphic unit included in the HDVTS (Video Title Set according to the embodiment of the present invention) is the first area (HDVTSI) area 41 shown in FIG. HD video title set information management table (HDVTSI_MAT) 410 (see FIG. 20) arranged in the group. The specific management information content is as shown in FIG. That is, the graphic unit stream number information and attribute information are divided into a menu screen and a title (display video) in the HDVTS, and the HDVTSM graphic unit stream number information (HDVTSM_GUST_Ns) and HDVTSM graphic unit stream attribute information (HDVTSM_GUST_ATR), respectively. ), HDVTS graphic unit stream number information (HDVTS_GUST_Ns), and HDVTS graphic unit stream attribute table information (HDVTS_GUST_ATR).

  In addition, as shown in FIG. 21, in the HD video title set information management table (HDVTSI_MAT) 410, HD video title set identifier (HDVTS_ID), HDVTS end address (HDVTS_EA), HDVTSI end address (HDVTSI_EA) ), HD_DVD video standard version number (VERN), HDVTS category (HDVTS_CAT), HDVTSI_MAT end address (HDVTSI_MAT_EA), HDVTSM_VOBS start address (HDVTSM_VOBS_SA), HDVTSTT_VOBS start address (HDVTSTT_VTSPTV) HDVTS_PGCIT The start address (HDVTS_PGCIT_SA), the start address of HDVTSM_PGCI_UT (HDVTSM_PGCI_UT_SA), the start address of HDVTS_TMAP (HDVTS_TMAP_SA), the start address of HDVTSM_C_ADT (HDVTSM_C_ADT_SA), the start address of HDVTSM_VOBU_ADMAP (HDVTSM_VOBU_ADMAP_SA), the start address of HDVTS_C_ADT (HDVTS_C_ADT_SA), the start address of HDVTS_VOBU_ADMAP (HDVTS_VOBU_ADMAP_SA), HDVTSM video attribute (HDVTSM_V_ATR), HDVTSM audio stream count (HDVTSM_AST_Ns), HDVTSM audio Stream attribute (HDVTSM_AST_ATR), the start address of the HDVTSM sub-picture stream number (HDVTSM_SPST_Ns), the HDVTSM sub-picture stream attribute (HDVTSM_SPST_ATR), the HDVTTS video attribute (HDVTS_V_ATR), the HDVTS audio stream number (HDVTS_ASTVTS, NTS) Various information of the stream attribute table (HDVTS_AST_ATRT), the number of HDVTS sub-picture streams (HDVTS_SPST_Ns), the HDVTS sub-picture stream attribute table (HDVTS_SPST_ATRT), and the HDVTS multi-channel audio stream attribute table (HDVTS_MU_AST_ATRT) are recorded. Has been.

  FIG. 22 shows an example of the data structure in HD video title set PTT search pointer table (HDVTS_PTT_SRPT) 411 shown in FIG. This HD video title set PTT search pointer table 411 includes HDVTS TTU number (HDVTS_TTU_Ns) and HDVTS_PTT_SRPT end address (HDVTS_PTT_SRPT_EA) information, and PTT search pointer table information (PTT_SRPTI) 411a; TTU start address (TTU_SA) The title unit search pointer (TTU_SRP) 411b in which information is recorded and various information of the PTT search pointer (PTT_SRP) 411c having the program chain number (PGCN) and program number (PGN) information are included. .

<Location of information for managing suspend information or resume information>
FIG. 23 is a diagram illustrating a data structure of an HD video title set program chain information table (HDVTS_PGCIT) recorded in HD video title set information (HDVTSI). In the embodiment of the present invention, as shown in FIG. 23, an update permission flag (RSM permission Flag) for resume information is provided in the HDVTS_PGC category in the HDVTS_PGCI search pointer 412. Information of the HDVTS_PGCI search pointer 412 is stored in the HD video title set program chain information table (HDVTS_PGCIT) 412 shown in FIG. 20 existing in the HD video title set information (HDVTSI) area 41 shown in FIG. Is placed inside. In the HD video title set program chain information table (HDVTS_PGCIT) 412, as shown in FIG. 23, HD video title set PGCI including the number of HDVTS_PGCI_SRP (HDVTS_PGCI_SRP_Ns) and HDVTS_PGCIT end address (HDVTS_PGCIT_EA) is also included. Information of the information table (HDVTS_PGCITI) 412a is recorded. In addition, in the HDVTS_PGCI search pointer (HDVTS_PGCI_SRP) 412b, the HDVTS_PGC category (HDVTS_PGC_CAT) and the information on the start address (HDVTS_PGCI_SA) of HDVTS_PGCI are recorded.

FIG. 24 is a diagram illustrating recording contents of the HDVTS_PGC category (HDVTS_PGC_CAT). The resume information update permission flag (RSM permission Flag) shown in FIG. 24 indicates whether the content of the resume information (Resume Information) is updated when the playback of the corresponding HDVTS_PGC is started (resume according to the playback status of the corresponding PGC). Specify whether to update information sequentially. That is, the above flag
If RSM permission Flag = “0b”, update resume information,
When RSM permission Flag = “1b”, resumption information is not updated, and reproduction interruption information of HDVTS_PGC (corresponding program chain in the video title set according to the embodiment of the present invention) reproduced before that is held. Keep it,
The process is performed. In addition, in the HDVTS_PGC category (HDVTS_PGC_CAT), there are other entry type information for determining whether or not it is an entry PGC, title number information in the VTS (video title set) indicated by the corresponding PGC, block mode information, and block type information. , PTL_ID_FLD information and the like can be recorded.

  FIG. 25 shows an example of the data structure in HD video title set menu PGCI unit table (HDVTSM_PGCI_UT) 413 shown in FIG. The HD video title set menu PGCI unit table 413 includes HD video title set menu program chain information unit table information (HDVTSM_PGCI_UTCI_UTCI_UTCI_UTCI_UTCI_UTCI_UT_EA). HD video title set menu language unit (HDVTSM_LCD), HD video title set menu presence / absence (HDVTSM_EXT), and HDVTSM_LU start address (HDVTSM_UT_SA) information recorded therein HD video title set menu language unit search pointer (HDVTSM) LU_SRP) 413b and; is configured to include a variety of information of HD video title set menu language unit (HDVTSM_LU) 413c.

  FIG. 26 shows an example of the data structure in the HD video title set menu language unit (HDVTSM_LU) 413c. This HD video title set menu language unit 413c is, as shown in FIG. 26, HD video title set menu language unit information (HDVTSM_LUI) 413c1 having information on the number of HDVTSM_PGCI_SRP (HDVTSM_PGCI_SRP_Ns) and the end address of HDVTSM_LU (HDVTSM_LU_EA); HDVTSM_PGCI_PGCI_Search pointer (HDVTSM_PGCI_SA) in which HD video title set menu program chain information (HDVTSM_PGCI) 413c3 having the same data structure as above is recorded; Is configured) 413C2 contain.

  In one embodiment of the present invention, as a setting location of information for referring to (specifying) the above-described menu AOB (HDMENU_AOB), as shown in FIG. #N) Arranged in HDVTSM_PGC category information (HDVTSM_PGC_CAT) in 413c2.

  FIG. 27 is a diagram illustrating recording contents of the HDVTSM_PGC category (HDVTSM_PGC_CAT). The AOB Number information in the HDVTSM_PGC category information (HDVTSM_PGC_CAT) shown in FIG. 27 corresponds to the AOB number #n to be reproduced in HDMENU_AOBS (AOB for menus (HDMENU_AOB) arranged as shown in FIG. 19). This means AOB number information (AOB Number) for designating. Also, the audio selection information (Audio Selection information) indicates selection information of audio information to be reproduced at the same time when the HD content menu is displayed on the screen and start / end trigger information of audio information reproduction in the embodiment of the present invention. This means an audio information selection flag (Audio Selection information).

  Here, when “00b” of the audio information selection flag (Audio Selection information) is selected, the audio data recorded in each menu video object is reproduced, and the audio reproduction is interrupted when the menu is switched. Also, when “10b” or “11b” of the audio information selection flag (Audio Selection information) is selected, audio data of the menu AOB (HDMENU_AOB) existing in the menu audio object area (HDMENU_AOBS) 33 is reproduced. . When reproducing the menu audio data (AOB), when “11b” is designated, the audio data starts to be reproduced from the beginning every time the menu screen is changed, and when “10b” is designated, the menu screen is switched. The audio data continues to be reproduced continuously. In the embodiment of the present invention, as shown in FIG. 19, a plurality of types of menu AOBs (HDMENU_AOB) can be stored in the menu audio object area (HDMENU_AOBS) 33.

  The audio information number (Audio Number information) shown in FIG. 27 indicates selection information of the menu AOB (HDMENU_AOB) that is played back simultaneously when the corresponding menu display PGC is displayed. Based on the audio information number as the menu AOB selection information, the “number of AOB to be selected from the top” in the menu AOB arranged in FIG. 19 is selected by the number information. In addition, the HDVTSM_PGC category (HDVTSM_PGC_CAT) includes entry type information for determining whether or not an entry PGC, menu ID information indicating menu identification (for example, a title menu), block mode information, block type information, PTL_ID_FLD information and the like are recorded.

  FIG. 28 shows an example of the data structure in HD video title set time map table (HDVTS_TMAPT) 414 shown in FIG. The HD video title set time map table 414 includes an HD video title set time map table information (HDVTS_TMAPTI) 414a in which various information of the number of HDVTS_TMAP (HDVTS_TMAP_Ns) and the end address of HDVTS_TMAPT (HDVTS_TMAPT_EA) is described; and HDVTS_TMAP; HD video title set time map search pointer (HDVTS_TMAP_SRP) 414b having information of the start address (HDVTS_TMAP_SA) of the time; the length (TMU) of the time unit (seconds) as a reference in the map entry, the number of map entries (MAP_EN_Ns), and HD video tightness with various information recorded in the map entry table (MAP_ENT) It is configured to include a variety of information of the set time map (HDVTS_TMAP) 414c.

  FIG. 29 shows an example of the data structure in HD video title set menu cell address table (HDVTSM_C_ADT) 415 shown in FIG. As shown in FIG. 29, the HD video title set menu cell address table 415 includes HD video title set menu cell address table information (HDVTSM_AD_TA) having information on the number of VOBs in HDVTSM_VOBS (HDVTSM_VOB_Ns) and the end address of HDVTSM_C_ADT (HDVTSM_C_ADT_EA). HDVTSM_CP VOB_ID number (HDVTSM_VOB_IDN), HDVTSM_CP Cell_ID number (HDVTSM_C_IDN), HDVTSM_CP start address (HDVTSM_CP_SA), and HDVTSM_CP end address (HDVTSM_CP_A set) It is configured to include a variety of information over the scan information (HDVTSM_CPI) 415b.

  FIG. 30 shows an example of the data structure of HD video title set menu video object unit address map (HDVTSM_VOBU_ADMAP) 416 shown in FIG. The HD video title set menu video object unit address map 416 includes HDVTSM_VOBU_ADMAP end information (HDVTSM_VOBU_ADMAP_EA) HD video title set menu video object unit address map information (HDVTSM_VOBU_ADAPI) 416a and OVTSM as shown in FIG. The information includes the information of the HD video title set menu video object unit address (HDVTSM_VOBU_AD) 416b having the information of the first address (HDVTSM_VOBU_SA).

  FIG. 31 shows an example of the data structure in HD video title set cell address table (HDVTS_C_ADT) 417 shown in FIG. As shown in FIG. 31, the HD video title set cell address table 417 includes HD video title set cell address table information (HDVTS_C_ADTI) having information on the number of VOBs in HDVTS_VOBS (HDVTS_VOB_Ns) and the end address of HDVTS_C_ADT (HDVTS_C_ADT_EA). 417a; HDVTS_CP VOB_ID number (HDVTS_VOB_IDN), HDVTS_CP Cell_ID number (HDVTS_C_IDN), HDVTS_CP start address (HDVTS_CP_SA), HD_VTS_CP end address (HDVTS_CP_EA) HD_V ) 417b information included In it is configured.

  FIG. 32 shows an example of the data structure in HD video title set video object unit address map (HDVTS_VOBU_ADMAP) 418 shown in FIG. As shown in FIG. 32, the HD video title set video object unit address map 418 includes HD video title set video object unit address map information (HDVTS_VOBU_ADAPI) 418a having HDVTS_VOBU_ADMAP end address (HDVTS_VOBU_ADMAP_EA) information; and HDVTS_VOBU units. It includes various information of an HD video title set video object unit address (HDVTS_VOBU_AD) 418b in which information of a start address (HDVTS_VOBU_SA) is recorded.

  FIG. 33 shows a data structure of program chain general information (PGC_GI) included in program chain information (PGCI: corresponding to, for example, one of HDVTS_PGCI in FIG. 23), and a PGC graphic unit stream control table (in this PGCI). It is a figure which illustrates the recording content of PGC_GUST_CTLT) and a resume / audio object category (RSM & AOB_CAT).

In one embodiment of the present invention, resume information update permission flag (RSM permission Flag) information and audio information selection flag (Audio Selection information) / audio information number (Audio Number information), which are part of characteristic elements in the embodiment of the present invention, In the example described above, it is provided in the search pointer information of PGCI (see FIG. 26, FIG. 27, etc.). However, the present invention is not limited to this, and update permission flag information of resume information, voice information selection flag / It is also possible to have a voice information number. This example is shown in FIG. The PGCI information shown in FIG.
B) HD video manager menu language unit (HDVMGM_LU) 312 of FIG. 6 existing in the HD video manager menu PGCI unit table (HDVMGM_PGCI_UT) 312 (FIG. 3) in the HD video manager information (HDVMGI) area 31 of FIG. HD video manager menu program chain information (HDVMGM_PGCI) 312c3 shown in FIG.
B) HD video title set menu language in FIG. 25 in the HD video title set menu PGCI unit table (HDVTSM_PGCI_UT) 413 in FIG. 20 showing the data structure in the HD video title set information (HDVTSI) area 41 in FIG. HD video title set menu program chain information (HDVTSM_PGCI) 413c3 shown in FIG. 26 arranged in the unit (HDVTSM_LU) 413c;
C) HDVTS_PGCI 412c (FIG. 23) in the HD video title set program chain information table (HDVTS_PGCIT) 412 in FIG. 20 showing the data structure in the HD video title set information (HDVTSI) area 41 in FIG.
Correspond to each other (the PGCI information shown in FIG. 33 can be arranged at any one or more of the three locations (A) to (C)).

  As shown in FIG. 33, program chain information (PGCI) includes program chain general information (PGC_GI) 50, program chain command table (PGC_CMDT) 51, program chain program map (PGC_PGMAP) 52, and cell playback information table (C_PBIT) 53. And 5 areas (5 management information groups) such as a cell position information table (C_POSIT) 54.

  As shown in FIG. 33, RSM & AOB category information (RSM & AOB_CAT) is recorded at the end of program chain general information (PGC_GI) 50 arranged in the first area (management information group) in PGCI. In this RSM & AOB category information (RSM & AOB_CAT), a resume information update permission flag (RSM permission information: RSM permission information), a sound information selection flag (audio selection information: Audio Selection information), and a sound information number (audio number information: Audio) Number information) exists. This RSM permission information means exactly the same contents as described in FIG. The contents of the voice information selection flag and the voice information number are the same as those described with reference to FIG. Further, in the RSM & AOB category information (RSM & AOB_CAT), entry type information, block mode information, block type information, and PTL_ID_FLD information for determining whether or not the entry PGC is recorded.

  As shown in FIG. 33, information in the PGC graphic unit stream control table (PGC_GUST_CTLT) in which control information related to a stream of graphic units arranged in the PGC is recorded includes four types of images (16: 9 HD images, 16: 9 SD image, 4: 3 SD image, letterbox SD image), and PGC_GUST_CTL (PGC_GUST # 0) area of HD graphic unit stream # 0, which is a separate area, and SD wide graphic PGC_GUST_CTL (PGC_GUST # 1) area of unit stream # 1, PGC_GUST_CTL (PGC_GUST # 2) area of 4: 3 (SD) graphic unit stream # 2, graphic unit for letterbox (SD) Stream # 3 of PGC_GUST_CTL (PGC_GUST # 3) area, are recorded separately.

  In addition to the above information, the program chain general information (PGC_GI) 50 includes PGC contents (PGC_CNT), PGC playback time (PGC_PB_TM), PGC user operation control (PGC_UOP_CTL), PGC audio stream control table (PGC_AST_CTLT), PGC subpicture Stream control table (PGC_SPST_CTLT), PGC navigation control (PGC_NV_CTL), PGC sub-picture palette (PGC_SP_PLT), PGC_CMDT start address (PGC_CMDT_SA), PGC_PGMAP start address (PGC_PGMAP_SA), C_PBIT start address PO_ITB start address PO Various information of (C_POSIT_SA) There has been recorded.

  FIG. 34 is a diagram illustrating a data structure of a program chain command table (PGC_CMDT) included in the program chain information (PGCI). The command information applied to each PGC is collectively arranged in a program chain command table (PGC_CMDT) 51 as shown in FIG. As described in the explanation of FIG. 33, the places where the PGCI information is arranged can be arranged at three locations (A) to (C). The resume (RSM) command sequence (or Resume Sequence) is recorded in the program chain command table (PGC_CMDT) 51 as shown in FIG. The information content of the Resume Sequence (resume command sequence) in one embodiment of the present invention is described in a form in which RSM commands (RSM_CMD) 514 arranged in the area of the command table 51 are sequentially arranged. One RSM command (RSM_CMD) 514 described in one column in FIG. 34 means one command that can be specified in the HD_DVD video content in the present invention, and in the resume (RSM) command sequence area. The arranged RSM commands (RSM_CMD) 514 are executed sequentially (sequentially) from the top.

  In the embodiment of the present invention, the array of cell commands (C_CMD) 513 described in FIG. 34 also means a sequential command sequence. That is, it means that command processing is executed sequentially from the top in accordance with the arrangement order of the cell commands (C_CMD) 513 shown in FIG. As will be described separately with reference to FIG. 37, the cell command for each cell in a series of cell command processing procedures designated from cell command # 1 (C_CMD # 1) to cell command #k (C_CMD # k). A part of the processing procedure (first cell command number for starting cell command sequential processing and execution range of cell command sequential processing for each cell) can be designated.

  In FIG. 34, an RSM command (RSM_CMD) 514 returns to the corresponding PGC from the menu screen, for example, and shows a part of the command procedure executed immediately before “playing from the middle of the PGC” where playback was interrupted previously. On the other hand, the pre-command (PRE_CMD) 511 means a command executed immediately before the corresponding “PGC is reproduced immediately from the beginning”. A command executed after reproduction of the corresponding PGC is a post command (POST_CMD) 512. In FIG. 34, the number of pre-commands (PRE_CMD) 511 and the number of post commands (POST_CMD) 512, the number of cell commands (C_CMD) 513, the RSM command (RSM_CMD) that can be arranged in one program chain command table (PGC_CMDT) 51. Each of the numbers 514 can be freely set (any number of commands to be described may be “0”). However, in one embodiment of the present invention, the number of pre-commands (PRE_CMD) 511 and the number of post commands (POST_CMD) 512 that can be placed in one program chain command table (PGC_CMDT) 51, cell commands (C_CMD) 513 And the total number of RSM commands (RSM_CMD) 514 is defined as 1023. Therefore, for example, when the number of pre-commands (PRE_CMD) 511, the number of post commands (POST_CMD) 512, and the number of RSM commands (RSM_CMD) 514 are all “0”, the number of cell commands (C_CMD) 513 is set to 1023 at maximum. It is possible to set up to pieces.

  FIG. 35 is a diagram illustrating the contents of program chain command table information (PGC_CMDTI) and the contents of each resume command (RSM_CMD) included in the program chain command table (PGC_CMDT). The number of pre-commands (PRE_CMD) 511 that can be arranged in one program chain command table (PGC_CMDT) 51 is PRE_CMD_Ns, the number of post commands (POST_CMD) 512 is POST_CMD_Ns, and the number of cell commands (C_CMD) 513 The number information C_CMD_Ns and the number information RSM_CMD_Ns of the RSM command (RSM_CMD) 514 are recorded in the program chain command table information (PGC_CMDTI) 510 as shown in FIG.

  A specific data structure in the RSM command (RSM_CMD) 514 recorded in the program chain command table (PGC_CMDT) 51 will be described below. Here, a specific data structure in the RSM command (RSM_CMD) 514 will be described. The specific data structure in 514 is exactly the same. The specific data structure in the RSM command (RSM_CMD) 514 is only to allocate an area of “8 bytes” for each command, as shown in FIG. In the “8 bytes” area, one of the command contents described separately with reference to FIG. 43 is selected and recorded. In any of these commands, the data of “command ID-1” shown in FIG. The data contents of the bits after that vary depending on the value of “command type” shown in FIG. 42, but information such as “comparison I flag (I-flag)” and “Compare Field” shown in FIG. Regardless of what you have.

  FIG. 36 illustrates a data structure in a program chain program map (PGC_PGMAP) 52 and a cell location information table (C_POSIT) 54 arranged in program chain information (PGCI: Program Chain Information). In the program chain program map (PGC_PGMAP) 52, program entry cell number 520 information in which the entry cell number (EN_CN) indicating the cell number corresponding to each entry is recorded is arranged for the number of entries. Further, in the cell location information table (C_POSIT) 54, cell location information (C_POSI) 540 configured by combining information of a cell VOB_ID number (C_VOB_IDN) and a cell cell ID number (C_IDN) is sequentially arranged. Have a structure.

  34, a part of the cell command processing procedure for each cell in a series of cell command processing procedures designated from cell command # 1 (C_CMD # 1) to cell command #k (C_CMD # k). It has been described that the structure is such that (the first cell command number for starting cell command sequential processing and the execution range of cell command sequential processing) can be specified for each cell. FIG. 37 shows execution range information of sequential processing of cell commands that can be set for each cell. As described above with reference to FIG. 33, the above-described places where the PGCI information is arranged can be arranged in three places (A) to (C). As shown in FIG. 37, management information related to individual cells constituting the PGC is recorded in cell playback information (C_PBI) 530 in the cell playback information table (C_PBIT) 53 in PGCI which is management information of the corresponding PGC. Is done.

  In the series of cell command processing procedures specified from cell command # 1 (C_CMD # 1) to cell command #k (C_CMD # k) shown in FIG. 34, the cell command specified for each cell. Information on the first cell command number for starting the sequential processing is recorded in the cell command start number information (C_CMD_SN) in the cell playback information (C_PBI) 530 as shown in FIG. At the same time, cell command continuation number information (C_CMD_C_Ns) indicating the number of commands that continuously execute command processing including the cell command (C_CMD) 513 specified by the cell command start number information (C_CMD_SN) is cell reproduction information (C_PBI). ) Is recorded in 530, and the execution range of the sequential processing of the cell command executed by the corresponding cell is designated from both pieces of information. In one embodiment of the present invention, after the reproduction of the corresponding cell is completed, a series of commands in the range specified by the cell command start number information (C_CMD_SN) and the cell command continuous number information (C_CMD_C_Ns) in FIG. A procedure (command sequence) can be executed.

  FIG. 37 is a diagram illustrating a data structure of a cell playback information table (C_PBIT) included in program chain information (PGCI). In FIG. 37, the following information can be stored in the cell playback information (C_PBI) 530. That is, if the corresponding cell constitutes an interleaved block that supports multi-angle or part of a general continuous block, or part of an interleaved block that supports multi-angle Cell category (C_CAT) indicating whether it corresponds to the first cell or the last cell of the interleaved block; cell playback time (C_PBTM) indicating the playback time required when playing back the entire corresponding cell; start address of the first VOBU of the cell Location information (C_FVOBU_SA); cell end ILVU end address location information (C_FILVU_EA); cell last VOBU start address location information (C_LVOBU_SA); cell last VOBU end address location information (C_LVOBU_EA) It is possible.

  FIG. 38 is a block diagram illustrating an example of the internal structure of a reproducing apparatus for a disk-shaped information storage medium (such as an optical disk) according to an embodiment of the present invention. 38, HD_DVD video content according to an embodiment of the present invention is recorded on the information storage medium 1. The disk drive unit 1010 reproduces HD_DVD video content from the information storage medium 1 and transfers it to the data processor unit 1020. In the HD_DVD video content, a VOB (Video Object) that is video data is composed of a collection of VOBUs (Video Object Units) that are basic units as shown in FIG. 44 (c). Navi pack a3 is arranged. Further, video data is distributed in a video pack a4, audio data is in an audio pack a6, and sub-picture data is distributed in a sub-picture (SP) pack a7, thereby having a multiplexed structure.

  In the embodiment of the present invention, graphic unit data is newly provided, and this data is distributed and recorded in the graphic unit (GU) pack a5. The VOB in which these various types of data are multiplexed are packet-divided by a separation unit (demultiplexer) 1030 in FIG. 38, and the video data recorded in the video pack a4 is sent to the video decoding unit 1110, and the sub-picture pack The sub video data recorded in a7 is transferred to the sub video decoder unit 1120, the graphic data recorded in the graphic unit pack a5 is transferred to the graphic decoder unit 1130, and the audio data recorded in the audio pack a6 is transferred. Transfer to the audio decoder 1140. The various data sent are decoded by the decoder units 1110 to 1140, and are appropriately combined in the video processor unit 1040, then converted to analog signals by the D / A converters 1320 and 1330, and output. A series of these processes are managed by the MPU unit 1210 in an integrated manner, and data that needs to be temporarily stored during the process is temporarily stored in the memory unit 1220. A processing program processed by the MPU unit 1210 and fixed information set in advance are recorded in the ROM unit 1230. In FIG. 38, the information input from the user to the information reproducing apparatus is illustrated as being performed by key input at the key input unit 1310. However, the key input unit 1310 is not limited to this and is a general remote controller. Also good.

  FIG. 39 is a diagram for explaining in detail the internal structure of the graphic decoder unit 1130 shown in FIG. The graphic unit data separated and extracted by the separation unit 1030 is temporarily stored in the graphic unit input buffer 1130a. The graphic unit data, which will be described later with reference to FIG. 45, includes highlight information, graphic data, and / or mask data. This highlight information is transferred to the highlight decoder 1130b and the highlight information is decoded. The graphic data and mask data are decoded into 256-color screen information in the graphic decoder 1130e.

  Further, the decoded graphic data and / or mask data is appropriately subjected to selection of a color palette and highlight processing (for example, processing for changing a part of graphic data to be highlighted into a conspicuous color), and then the mixer unit 1130d. Decoded graphics / mask combined with highlight data decoded in step (for example, image data with emphasized frame pixels at the position to be highlighted and transparent pixels at other positions) and appropriately modified with the highlight data Data is sent to the mixer 1140a. In the mixer 1140a, the decoded graphic / mask data is combined with the video data from the video decoder unit 1110 and the sub-picture (sub-picture) data from the sub-picture decoder unit 1120 to become a video output. Here, the mixer 1140a of FIG. 39 is included in a part of the video processor unit 1040 of FIG.

  In the configuration of FIG. 39, the palette selection unit 1130g and / or the highlight processing unit 1130h are controlled by the decode output of the highlight decoder 1130b, so that the highlight modification is directly added to the decode output of the graphic decoder 1130e. (In this case, the mixer 1130d may be omitted).

  FIG. 40 is a diagram for explaining the concept of the virtual video access unit IVAU. A virtual video access unit (IVAU) according to an embodiment of the present invention will be described with reference to FIG. A moving image (Movie) VOB in a conventional SD DVD video content is divided into VAUs (Video Access Units) as shown in FIG. Here, seamless playback between different VOBs is made possible by matching the boundary positions of adjacent VOBs with the boundary positions of adjacent VAUs.

  In HD_DVD video according to an embodiment of the present invention, as shown in FIG. 40 (b), VAU1 including an I-picture in which a still image is recorded and I-picture in which a still image to be displayed next is recorded. “Virtual access units” IVAU2 to IVAUn (2 to n of Imaginary Video Access Units) are set in the period between the VAUs 1 to include. This is a feature of one embodiment of the present invention. As a setting method of the access unit, the I-picture (including VAU1) where the still picture starts and the next I-picture (including VAU1) are set in units of a video frame period or an integer multiple of the video frame. The interval between them is virtually finely divided for each period of the access unit. A DTS (Decoding Time Stamp) indicating the timing input to the still image decoder and a PTS (Presentation Time Stamp) indicating the timing when the still image is displayed are set in advance for each still image, and each video frame period. Is determined by the NTSC (National Television System Committee) system and the PAL (Phase Alternation by Line) system, the timing of the boundary position of the “virtual access unit” is obtained by calculation, and the obtained timing is shown in FIG. ) As shown in FIG. Then, it can be regarded (virtually) that a still image is repeatedly reproduced and displayed for each virtual access unit.

  In the embodiment of the present invention, as shown in FIG. 40D, an integer number of “virtual access units” is set to form one VOBU. As a result, in one embodiment of the present invention, the VOBU display period of each still image is an integral multiple of the video frame. In FIG. 40 (c), there is one I-picture indicating a still picture in a VAU (Video Access Unit), but no I-picture is included in an IVAU (Imaginary Video Access Unit). There will be no video data. That is, only one I-picture exists in the VOBU composed of VAU1 to IVAU15 and the VOBU composed of VAU16 to IVAU30. On the other hand, the video data (I-picture) is not included in the VOBU composed of IVAU30 to IVAU45.

  In the embodiment of the present invention, it is possible to define a VOBU having no video data inside. In one embodiment of the present invention, it is prohibited to have a plurality of I-pictures in the same VOBU, and one VOBU must always have one or less (including 0) I-pictures. Stipulated (restricted). In the embodiment of the present invention, as can be seen from the position comparison in FIGS. 40 (c) and 40 (d), the VAU is always (virtually) arranged before the IVAU in the same VOBU. Structure is adopted. As shown in FIG. 40 (e), the first VOBU in an ILVU (Interleaved Unit) always has video data (I-picture in which a still image is recorded).

  FIG. 41 is a diagram for explaining a specific example of system parameters used in one embodiment of the present invention. In the system block diagram in the information reproducing apparatus shown in FIG. 38, an area for storing system parameters from “0” to “23” shown in FIG. The current menu language code information (language code that can be changed by user and / or command) is recorded in “SPRM0”, and the initial menu language code information (reproduction that can be changed and set only by the user) is recorded in “SPRM21”. Device setting language code) is recorded. The information stored in other system parameters includes an TT_DOM audio stream number (ASTN) in SPRM (1) and a TT_DOM sub-picture stream number (SPSTN) in SPRM (2), respectively. : Sub-picture stream number) and on / off flag, angle number (AGLN) for TT_DOM in SPRM (3), title number (TTN: TT_DOM) in SPRM (4) Title number), SPRM (5), TT_DOM VTS title number (VTS_TTN: VTS Title number), SPRM (6) TT_DOM title PGC number (TT_PGCN: Title PGC number), SPRM (7) Part of tie for one sequential PGC title (One_Sequential_PGC_Title) Part number (PTTN: Part_of_Title number), highlighted button number for selection state (HL_BTNN: Highlighted Button number) in SPRM (8), and navigation timer (NV_TMR: Navigation Timer) in SPRM (9) ), TT_PGCN for NV_TMR in SPRM (10), Player Audio Mixing Mode for Karaoke (P_AMXMD) in SPRM (11), and Country (or region) for parental management in SPRM (12) ) Code (CTY_CD: Country Code), parental level (PTL_LVL) in SPRM (13), video player configuration (P_CFG) in SPRM (14), SPRM (15) P_CFG for audio, SPR AST initial language code (INI_LCD) in M (16), AST initial language code extension (INI_LCD_EXT) in SPRM (17), and SPST in SPRM (18) In the INI_LCD, SPRM (19), the SPST INI_LCD_EXT, SPRM (20) is the player region code.

  FIG. 42 is a diagram illustrating a command list used in the embodiment of the invention. The command ID-1 “000” to “110” is the same as the command used in the previous DVD video, but the command “Call INTENG” with the command ID-1 “111” uses this interactive engine. This command is newly introduced in the practice of the invention.

  FIG. 43 shows an example of a command list used in HD_DVD video content according to an embodiment of the present invention. The “Compare Field” shown in FIG. 43A is used to compare the value in the navigation parameter with the specific value defined by the command operand. If the comparison result is true, the subsequent instruction is executed, and if the comparison result is doubtful, the subsequent instruction is skipped. This instruction is used in combination with other instruction groups. In FIG. 43 (a), EQ means Equal, NE means Not Equal, GE means Greater than or equal to, and GT is Greater than. , LE means less than or equal to, LT means less than, and BC means bitwise compare.

  “Go To Option” in “Branch Field” shown in FIG. 43B is used to change the execution order of navigation commands in the pre-command area or post-command area, or resume command area or cell command area. Used. Here, “GoTo” means transition to another navigation command, and “Break” means the end of execution of the navigation command in the pre-command area or post-command area, or the resume command area or cell command area. is doing. “SetTmpPML” means confirmation of temporary change of the parental level, change of the parental level, and transition to a specific navigation command if possible.

  “Link Option” in “Branch Field” shown in FIG. 43C is used to start reproduction specified in one domain. Here, “LinkPGCN” means that the program chain number (PGCN) is directly specified and playback of the corresponding PGC is started, and “LinkPTTN” is the part of title number (PTTN) is directly specified and the corresponding PTT (or "LinkPGN" means to directly specify the program number (PGN) and start reproduction of the corresponding PG, and "LinkCN" directly specifies the cell number (CN). This means that the specified cell is started to be reproduced.

  “Jump Option” in “Branch Field” shown in FIG. 43 (d) is used to start specific reproduction when moving between spaces. Here, “Exit” means end of playback, “JumpTT” means start of title playback (when title number TTN is used), and “JumpVTS_TT” means start of title playback within the same VTS. “CallSS” means the start of PGC playback in the system space in which resume information is stored, “JumpSS” means the start of playback of a part of title included in a specific title in the same VTS, and “CallINTENG” FIG. 83 shows a control transition from the DVD video playback engine to the interactive engine (details are shown in FIG. 83).

  “SetSystem Field” shown in FIG. 43 (e) is used to set the mode and value of the system parameter value and the general parameter. Here, “SetSTN” means the setting of the stream number (target parameters to be set are SPRM (1), SPRM (2), SPRM (3)), and “SetNVTMR” is the condition setting of the navigation timer (target parameter to be set) Means SPRM (9), SPRM (10)), “SetHL_BTNN” means setting of the highlighted button number for the selected state (target parameter to be set is SPRM (8)), and “SetAMXMD” Means the setting of the audio mixing mode of the playback device for karaoke (the target parameter to be set is SPRM (11)), and “SetGPRMMD” is the mode and value setting of the general parameters (the target parameters to be set are GPRM (0) to GPRM) (15)), “SetM_LCD” sets the menu description language code (the parameter to be set is S RM (0)), “SetRSMI” updates resume information (resume information is CN, NV_PCK address, PGC control status, VTSN (Video Title Set Number), SPRM (4), SPRM (5), SPRM (6), SPRM (7), SPRM (8)).

The Set Field shown in FIG. 43 (f) is used to execute a calculation based on a specific value and a general parameter specified by the operand. There are two types of this calculation:
1) Arithmetic operation
2) Bitwise operation
The above calculation results are re-stored as general parameters. In FIG. 43 (f), “Exp” means calculation of power, “Div” means division, and “Add” means addition.

  FIG. 44 is a diagram illustrating an arrangement of the graphic units GU in the video object. The HD_DVD video content used in an embodiment of the present invention also complies with the MPEG system layer multiplexing rule. That is, the graphic unit data is also divided into 2048-byte packs and arranged separately. At the time of reproduction, as shown in FIGS. 44C and 44D, graphic unit (GU) packs distributed in the information storage medium 1 are collected and reassembled into one graphic unit stream. As a graphic unit, it is possible to support graphic data corresponding to 16: 9 HD images, 16: 9 SD images, 4: 3 SD images, and letterbox SD images, as shown in FIG. In addition, separate streams are formed corresponding to four types of images (16: 9 HD image, 16: 9 SD image, 4: 3 SD image, and letterbox SD image).

  FIG. 45 is a diagram illustrating a data structure in the graphic unit. As shown in FIG. 45, the data structure in the graphic unit includes header information b1, highlight information b2, mask data b3, and graphic data b4. The highlight information b2 includes general information b21, color palette information b22, and button information b23.

  FIG. 46 is a diagram illustrating the header information contents and the general information contents in the graphic unit. As shown in FIG. 46, the contents of the header information include graphic unit size (GU_SZ) information, highlight information start address (HLI_SA) information, and graphic data start address (GD_SA) information. Among these, the graphic unit size (GU_SZ) information indicates the overall size of the graphic unit shown in the lower left of FIG. Further, the start address (HLI_SA) information of the highlight information means an address up to the start position of the highlight information b2 with reference to the start position of the graphic unit (the start position of the header information b1) shown in the lower left of FIG. The data start address (GD_SA) information means an address up to the head position of the graphic data b4 with reference to the head position of the graphic unit shown in the lower left of FIG. 45 (head position of the header information b1).

  In FIG. 45, general information b21 in the highlight information b2 includes reproduction end time (GU_PB_E_PTM) information, button offset number (BTN_OFN) information, button number (BTN_Ns) information, and number of number selection buttons (NSL_BTN_Ns) information. , Forced selection button number (FOSL_BTNN) information, forced determination button number (FOAC_BTNN) information, and the like. 44, the graphic unit data is distributed and arranged as a graphic unit (GU) pack as described in FIG. 44, but the graphic unit data is graphic in this graphic unit pack (to be precise, in the packet header in the graphic unit packet included therein). PTS (Presentation Time Stamp) information for starting playback of the unit is recorded in advance. Using this PTS information and the reproduction end time (GU_PB_E_PTM) information of the graphic unit, the display time of the graphic unit and the valid time during which (command) can be executed (the start / end time of both coincide completely) Set. Since the PTS / PTM is used for the start / end time information, the time range can be set with very high accuracy.

  FIG. 47 is a diagram for explaining an image example of mask data and graphic data in the graphic unit. As the graphic data, as shown in FIG. 47, image information (bitmap data or compressed data for the bitmap) of one screen capable of assigning 8 bits per pixel and expressing 256 colors is recorded. The mask data indicates a position range on the screen where the user can specify command execution. One bit is assigned to each pixel, and only the screen area is set. Since the mask data specifies an area in a bitmap format in units of pixels, as shown in FIG. 47, not only can a plurality of areas arranged at positions apart from each other be masked at the same time, but also for any shape area The masking screen area can be specified in detail in pixel units. This is another feature of this embodiment. A plurality of mask data can be set, and a plurality of menu options can be supplied to the user (7 illustrates three user selection branches).

  FIG. 48 is a diagram illustrating an example of video composition including a mask pattern. The screen displayed to the user includes a main image (A) recorded in the video pack a4 in FIG. 44 (c), a graphic pattern (B) recorded as the graphic data, and a plurality of mask data (C) that can be set. Can be synthesized and created as shown in FIG.

  In one embodiment of the present invention, as shown in FIG. 45, the number n of mask data in the same graphic unit and the number n of button information recorded in highlight information are the same, and each mask data #n And button information #n have a one-to-one correspondence. That is, in m satisfying 1 ≦ m ≦ n, the m-th mask data from the top corresponds to the m-th button information from the top. For example, when the user highlights (designates) an area designated by the mth mask data on the screen by operating a cursor key of a remote controller (not shown), the corresponding information is recorded in the mth button information b23. The button command b234 is executed. As described above, each button information #n is linked to each mask data #n, but in order to further facilitate access control to the mask data, the corresponding mask data #n is included in the button information #n. The data size information b232 of the mask data #n corresponding to the start address (address from the start position of the header information in the lower left of FIG. 45 to the nth mask data start position) information b231 is recorded. In addition, adjacent button position information b233 is recorded in the button information b23.

  Next, the data structure in the color palette information b22 in the highlight information b2 in FIG. 45 will be described. The color information of the button when the menu screen is first displayed to the user (before user selection) is stored in the normal color palette b221. When the user selects (designates) a specific button, the display color of the button changes on the screen. The display color of the button at the time of the change is recorded in the selection color palette b222. Further, when the button is confirmed and the button command b234 corresponding to the button is executed, the display color of the button can be set to change to a color indicating “confirm”. The display color of the button at the time of determination is given to the determination color palette b223.

  FIG. 49 shows another example of the data structure of the graphic unit. The embodiment of FIG. 49 is characterized in that hot spot information is used instead of using mask data. Correspondingly, in the example of FIG. 49, a plurality of normal color palettes e221, selection color palettes e222, and confirmation color palettes e223 can be set. Further, as an area designation method for each button information e23, an area on the screen can be designated by hot spot position information e233 instead of using mask data. Further, in the example of FIG. 49, by making it possible to set a plurality of hot spot position information e233 for the same button information e23, a plurality of areas on the screen separated from each other can be associated with the same button information e23. I am doing so.

  FIG. 50 is a diagram for explaining an example of the recorded content in the advanced content recording area among the information content recorded on the disc-shaped information storage medium (optical disc or the like) 1 according to another embodiment of the present invention. As shown in FIG. 50 (d), the advanced content recording area 21 in FIG. 50 (c) includes a moving picture recording area 21B for recording moving picture data, an animation / still picture recording area 21C for recording animation data and still picture data, and audio. An audio recording area 21D for recording data, a font recording area 21E for recording font data, and a markup for recording information for controlling the reproduction thereof (this is composed of Markup language / Script language / StyleSheet, etc.) / Script language recording area 21A is included (the recording order of these areas is the first area 21A as shown).

  Information for controlling the reproduction (recorded contents of the area 21A) includes advanced content (including audio, still image, font / text, moving image, animation, etc.) and / or DVD video content reproduction method. (Display method, playback procedure, playback switching procedure, selection of playback target, etc.) are described using Markup language, Script language, and style sheet (StyleSheet). For example, HTML (Hyper Text Markup Language) / XHTML (eXtensible Hyper Text Markup Language) and SMIL (Synchronized Multimedia Integration Language) as markup languages, ECMA (European Computer Manufacturers Association) Script and JavaScript (Java is a registered trademark) ), A Script language such as CSS, and a StyleSheet such as CSS (Cascading Style Sheet).

  The Makrup / Script language recording area 21A includes a startup recording area 210A for recording startup information, a loading information recording area 211A for recording information on a file to be loaded into a buffer in the playback apparatus (see FIG. 90), a Markup language and a Script. A playback sequence information recording area 215A for defining a video playback order when playing back HD_DVD video stored in the extended video object set of the advanced title set using a language, a markup recording area 212A for recording the aforementioned markup language, It includes a Script recording area 213A for recording the aforementioned Script language and a StyleSheet recording area 214A for recording the aforementioned StyleSheet.

  Note that the loading information recording area 211A and the reproduction sequence information recording area 215A in FIG. 50 (e) can be used as areas for storing playlist information to be described later with reference to FIG.

  FIG. 51 is a diagram for explaining an example of the recorded contents of the advanced HD video title set recording area among the information contents recorded on the disc-shaped information storage medium (optical disc or the like) 1 according to another embodiment of the present invention. is there. The advanced HD video title set (AHDVTS: advanced VTS) shown in FIG. 51 (d) is a video object specialized to be referred to from the Makrup language, which is one of the aforementioned advanced contents.

  The advanced HD video title set (AHDVTS) recording area 50 includes an advanced HD video title set in which management information for all contents in the advanced HD video title set recording area 50 is recorded as shown in FIG. An information (AHDVTSI) area 51, an advanced HD video title set information backup area (AHDVTSI_BUP) 54 in which the same information as the advanced HD video title set information area 51 is recorded in the backup data, and an advanced HD video title set It includes an advanced title video object area (AHDVTSTT_VOBS) 53 in which video object (title video information) data is recorded.

  FIG. 52 is a diagram illustrating a data structure of advanced HD video title set information recorded in the advanced HD video title set recording area. The advanced HD video title set information (AHDVTSI) area 51 shown in FIG. 51 (e) is collectively recorded in the HVIA0001.IFO (or VTSA0100.IFO not shown) file shown in FIG. As shown, advanced HD video title set information management table (AHDVTSI_MAT) 510, advanced HD video title set PTT search pointer table (AHDVTS_PTT_SRPT) 511, advanced HD video title set program chain information table (AHDVTS_PGCIT) 512, advanced HD video title set Divided into each area (management information group) of cell address table (AHDVTS_C_ADT) 517 and time map information table (TMAPIT) 519 There.

  Here, the time map information table (TMAPIT) 519 is a part of the advanced HD video title set information (AHDVTSI) area 51 but is the same file as the advanced HD video title set information area 51 (HVIA0001.IFO in FIG. 2). As a file independent of the advanced HD video title set information area 51 (for example, HVM00000.MAP).

  In the advanced HD video title set information management table (AHDVTSI_MAT) 510, management information common to the corresponding video title set is recorded. By placing this common management information in the first area (management information group) in the advanced HD video title set information (AHDVTSI) area 51, the common management information in the video title set can be read immediately, so that information reproduction It is possible to simplify the reproduction control processing of the apparatus and shorten the control processing time.

  FIG. 53 shows the data structure of the advanced HD video title set information management table (AHDVTSI_MAT) recorded in the advanced HD video title set information (AHDVTSI) and the recorded contents of the category information (AHDVTS_CAT) stored in this management table. It is a figure illustrated. The advanced HD video title set information management table (AHDVTSI_MAT) 510 can store the following information as common management information in the video title set. That is, as shown in FIG. 53, the advanced HD video title set information management table includes an advanced HD video title set identifier (AHDVTS_ID), an advanced HDVTS end address (AHDVTS_EA), an advanced HDVTSI end address (AHDVTSI_EA), and HD_DVD video. Standard version number (VERN), AHDVTS category type (AHDVTS_CAT), end address of AHDVTSI_MAT (AHDVTSI_MAT_EA), start address of AHDVTSTT_VOBS (AHDVTSTTT_VOBS_SA_), start address of AHDVTS_PTT_SRPT_AHDVTS_PTT_SRPT_AHDVTS_PTT_SRPT CIT_SA), AHDVTS_C_ADT start address (AHDVTS_C_ADT_SA), video object angle attribute (ATR1_AGL_Ns) having attribute information 1 (ATR1), video object video attribute (ATR1_V_ATR), attribute information 1 (ATR1) ), The number of audio streams of the video object (ATR1_AST_Ns), the audio stream attribute table (ATR1_AST_ATRT) of the video object having attribute information 1 (ATR1), and the number of sub-picture streams of the video object having attribute information 1 (ATR1) (ATR1_SPST_Ns) , Sub-picture stream attribute table (ATR1_ of video object having attribute information 1 (ATR1)) PST_ATRT), the attribute information 1 (multichannel audio stream attribute table of the video object having the ATR1) (ATR1_MU_AST_ATRT) (hereinafter, the attribute information 2, various information of the attribute information 3 follow) are configured to be stored.

  Of the information that can be stored in the management table (AHDVTSI_MAT) in FIG. 53, the HDVTSM_VOBS start address (HDVTSM_VOBS_SA) that exists in the standard VTS does not have to exist (or is reserved) in the advanced VTS because there is no HDVTSM_VOBS. Can be an area). Further, the head address (HDVTSM_PGCI_UT_SA) of HDVTSM_PGCI_UT existing in the standard VTS may not exist (or may be a reserved area) in the advanced VTS because there is no HDVTSM_VOBS. The head address (HDVTSM_C_ADT_SA) of HDVTSM_C_ADT existing in the standard VTS may not exist (or may be a reserved area) because there is no HDVTSM in the advanced VTS. The head address (HDVTSM_VOBU_ADMAP_SA) of HDVTSM_VOBU_ADMAP existing in the standard VTS may not exist (or may be a reserved area) because there is no HDVTSM in the advanced VTS. Further, the head address (HDVTS_VOBU_ADMAP_SA) of HDVTS_VOBU_ADMAP existing in the standard VTS may not exist (or may be a reserved area) because there is an alternative time map information table in the advanced VTS.

Here, the information (AHDVTS_CAT) indicating the category of the advanced VTS stored in the advanced HD video title set information management table (AHDVTSI_MAT) 510 of FIG. 53 is defined as follows:
AHDVTS_CAT = 0000b: AHDVTS category is not specified AHDVTS_CAT = 0001b: Reserved AHDVTS_CAT = 0010b: Advanced VTS with advanced content
AHDVTS_CAT = 0011b: Advanced VTS without advanced content
AHDVTS_CAT = Others: Reservation Here, “AHDVTS_CAT = 0010b” indicates the category “advanced VTS with advanced content”, which basically indicates an advanced VTS configured with the Markup language. In other words, in this category, the content creator assumes “advanced VTS controlled by the Markup language”, and playback is permitted only in accordance with control of the Markup language, and playback by the advanced VTS alone is not allowed. For example, when a content creator describes a markup language that allows playback of an advanced VTS in a certain section only under a specific condition, if the playback of the advanced VTS alone is permitted, this section is determined as the specific condition. It will be possible to play even other than. Such playback is prohibited in the advanced VTS in the category of “AHDVTS_CAT = 0010b”.

  “Advanced VTS without advanced content” whose category is indicated by “AHDVTS_CAT = 0011b” basically indicates an advanced VTS that can be played back only by the advanced VTS without the Markup language. This assumes an advanced VTS for maintaining reproduction compatibility of another recording standard (referred to as VR standard) such as DVD-VR / HDDVD-VR and a reproduction-only standard (referred to as video standard) in the embodiment of the present invention. is doing. Because the video standard and the VR standard are different from each other (the video standard focuses on interactiveness, and the VR standard focuses on editing functions), the standards are different. Here, by sharing the structurally simplified advanced VTS in two standards, reproduction compatibility can be achieved in two different standards. For example, in a recording device conforming to the VR standard, an information storage medium recorded in the advanced VTS mode can be played back on all playback devices.

  FIG. 54 shows an example of the data structure in advanced HD video title set PTT search pointer table (AHDVTS_PTT_SRPT) 511 shown in FIG. The advanced HD video title set PTT search pointer table (AHDVTS_PTT_SRPT) 511 has PTT search pointer table information (PTT_SRPTI) 511a having information of the end address (AHDVTS_PTT_SRPT_EA) of AHDVTS_PTT_SRPT in the AHDVTS; and PTT having program number (PGN) information. The search pointer (PTT_SRP) 511c includes various information.

  Here, HDVTS_TTU_Ns representing the number of HDVTS TTUs existing in the standard VTS may not exist (or a fixed value is recorded even if it exists) because the number of TTUs is fixed to 1 in the advanced VTS. . Further, the advanced VTS can be configured so that there is only one title (TT). In that case, the “title unit search pointer (TTU_SRP) 411b in which the information of the TTU start address (TTU_SA) information is recorded” 411b (see FIG. 22) that existed in the standard VTS does not exist because there is only one TTU. (Or a fixed value is recorded even if it exists).

  FIG. 55 is a diagram illustrating a data structure of an advanced HD video title set program chain information table (AHDVTS_PGCIT) recorded in advanced HD video title set information (AHDVTSI). As shown in FIG. 55, the advanced HD video title set program chain information table (AHDVTS_PGCIT) 512 includes the number of AHDVTS_PGCI_SRP (AHDVTS_PGCI_SRP_Ns) and information on the end address of AHDVTS_PGCIT (AHDVTS_PGCIT_EA). Information of table information (AHDVTS_PGCITI) 512a is recorded. In addition, in the AHDVTS_PGCI search pointer (AHDVTS_PGCI_SRP) 512b, information on the head address (AHDVTS_PGCI_SA) of AHDVTS_PGCI is recorded together with the AHDVTS_PGC category (AHDVTS_PGC_CAT) described above.

  Here, in the advanced VTS, a plurality of PGCs can be prepared, but it does not have a function of controlling a connection relation at the time of reproduction using a navigation command. Therefore, there is basically only one PGC, and one sequential playback of the advanced VTS is managed. In this case, the value of AHDVTS_PGCI_SRP_Ns is fixed at 1, and there is one search pointer (AHDVTS_PGCI_SRP) 512b and one PGC information (AHDVTS_PGCI) 512c.

  FIG. 56 is a diagram illustrating a data structure of program chain general information (PGC_GI) included in program chain information (for example, corresponding to AHDVTS_PGCI in FIG. 55). As shown in FIG. 56, the program chain information (PGCI) recorded in the PGC information (AHDVTS_PGCI) 512c includes program chain general information (PGC_GI) 50, a program chain program map (PGC_PGMAP) 52, and a cell playback information table (C_PBIT). 53, including four areas (four management information groups) called a cell position information table (C_POSIT) 54. Note that the program chain command table (PGC_CMDT) 51 that exists in the PGCI of the standard VTS (FIG. 34) does not have to exist in the advanced VTS (or becomes a reserved area).

  As shown in FIG. 56, in the program chain general information (PGC_GI) 50, PGC contents (PGC_CNT), PGC playback time (PGC_PB_TM), PGC audio stream control table (PGC_AST_CTLT), PGC sub-picture stream control table (PGC_SPST_CTLT) , PGC navigation control (PGC_NV_CTL), PGC sub-picture palette (PGC_SP_PLT), PGC_PGMAP start address (PGC_PGMAP_SA), C_PBIT start address (C_PBIT_SA), C_POSIT start address (C_POSIT_SA), and the like.

  Here, the PGC user operation control (PGC_UOP_CTL) existing in the standard VTS does not exist because the user operation control is performed in the markup language in the advanced VTS (or even if it exists, PGC_UOP_CTL has “00 ... 00b”. Is recorded as a fixed value). Also, the PGC graphic unit stream control table (PGC_GUST_CTLT) that exists in the standard VTS does not exist because there is no graphic unit in the advanced VTS (may be a reserved area). In addition, since the command (PGC_CMDT) does not exist in the advanced VTS, the start address (PGC_CMDT_SA) of PGC_CMDT existing in the standard VTS does not exist (or becomes a reserved area).

  In the example of PGCI_GI in FIG. 56, RSM & AOB_CAT is illustrated at the end. However, the RSM & AOB category information (RSM & AOB_CAT), that is, the RSM permission information, the voice information selection flag, and the voice information number that existed in the standard VTS are controlled by the markup language in the advanced VTS, and there is no voice (Audio) information. Therefore, it is not necessary (or it becomes a reserved area).

FIG. 57 shows an example of the data structure in advanced HD video title set cell address table (AHDVTS_C_ADT) 517 shown in FIG. In the advanced HD video title set cell address table (AHDVTS_C_ADT) 517, the number of VOBs in the AHDVTS_VOBS (AHDVTS_VOB_Ns) and the end address of the AHDVTS_C_ADT (AHDVTS_C_ADT_EA) TS_A_AD_A_HD_A_TS_A_HD_A_TS_A_HD_TS_A_HD AHDVTS_CP's VOB_ID number (AHDVTS_VOB_IDN), AHDVTS_CP's Cell_ID number (AHDVTS_C_IDN), AHDVTS_CP start address (AHDVTS_CP_SA), and AHDVTS_CP's end address (AHDVTS_CP_EA) HD set of various types of information Rupisu information (AHDVTS_CPI) 517b
It is comprised including various information.

  FIG. 58 shows an example of the data structure in time map information table (TMAPIT) 519 shown in FIG. The time map information table (TMAPIT) 519 includes time map information table information (TMAPITI) 519a, a time map information search pointer (TMAPI_SRP) 519b, and time map information (TMAPI) 519c. The time map information table information (TMAPITI) 519a includes the number of time map information (TMAPI) 519c included in the time map information table (TMAPIT) 519 and information on the end address of the time map information table (TMAPIT) 519. Consists of. The time map information search pointer (TMAPI_SRP) 519b exists as many as the number of time map information (TMAPI) 519c, and describes the head address where the time map information (TMAPI) 519c is recorded.

  FIG. 59 shows an example of the data structure of time map information (TMAPI) 519c shown in FIG. The time map information (TMAPI) 519c includes a time map general information (TMAP_GI) 519c1, a time entry table (TM_ENT) 519c2, a VOBU entry table (VOBU_ENTT) 519c3, an ILVU_ADR entry table (ILVU_ADR_ENTT) 519_VNTB ENT_VNT table, and an ENT_VNT table. ) 519c5.

  The time map general information (TMAP_GI) 519c1 includes the TMAP_TYPE indicating the type of the block (Block) constituting the time map information (TMAPI) 519c, and the start address of a continuous block (Contiguous Block) or an interleaved block (Interleaved Block). BLK_ADR to indicate, TMU indicating the length of time of the time entry (Time Entry), VOB_Ns indicating the number of VOBs referred to by the time map information (TMAPI) 519c, and reference to the time map information (TMAPI) 519c ILVU_Ns indicating the number of ILVUs per VOB, and VOBU_ENT_Ns indicating all the VOBU numbers referred to by this time map information (TMAPI) 519c are configured.

  In the TMAP_GI of FIG. 59, when the block constituting the time map information TMAPI is configured to include a Contiguous Block, “0b” is recorded in TMAP_TYPE, and the block configuring the TMAPI is configured to include an Interleved Block. In this case, “1b” is recorded in TMAP_TYPE. The time length of the time entry is constant in the time map information and can be set to a value such as TMU = 10 seconds.

  Further, VOB_Ns indicating the number of VOBs referred to by TMAPI indicates the number of VOBs constituted by continuous blocks when the blocks constituting TMAPI are continuous blocks (that is, when TMAP_TYPE = 0b), and blocks constituting the TMAPI. Is an Interleaved Block (that is, when TMAP_TYPE = 1b), it indicates the number of VOBs constituting the Interleved Block.

  FIG. 60 shows an example of the data structure of time entry table (TM_ENT) 519c2 shown in FIG. The time entry table (TM_ENT) 519c2 includes one or more time entries (TM_EN_Ns) 519c21 and one or more time entries (TM_EN) 519c22. Here, the time entry is arranged for each VOB. Specifically, in the example of FIG. 60, the VOB # 1 time entry (TM_EN) 519c22 group, the VOB # 2 time entry (TM_EN) 519c22 group, ......... the VOB # p time entry (TM_EN) 519c22 group Thus, they are arranged in ascending order of VOB # p.

  TM_EN_Ns indicating the number of time entries (TM_EN) 519c22 in one VOB is recorded as the number of time entries (TM_EN_Ns) 519c21. The time entry (TM_EN) 519c22 includes VOBU_ENTN indicating the number of the VOBU entry (VOBU_ENT) 519c31 indicated by the time entry, TM_DIFF indicating the time difference between the time of the time entry calculated by the TMU and the start time of the VOBU indicated by the time entry. , TM_EN_ADR indicating an offset address from the head of “Block (a VOB section in which TMAPI is valid)”.

  FIG. 61 shows an example of the data structure of VOBU entry table (VOBU_ENTT) 519c3, ILVU_ADR entry table (ILVU_ADR_ENTT) 519c4, and ENT_VOBN table (ENT_VOBNT) 519c5 shown in FIG. As shown in FIG. 61, the VOBU entry table (VOBU_ENTT) 519c3 includes a VOBU entry (VOBU_ENT) 519c31. A VOBU entry (VOBU_ENT) 519c31 is a 1STREF_SZ indicating the size (which can be indicated by the number of packs) of the 1st Reference Picture (that is, the first I-picture or the equivalent) included in the VOBU, and the playback of the VOBU It includes VOBU_PB_TM indicating time and VOBU_SZ indicating the size of VOBU (which can be indicated by the number of packs).

  The ILVU_ADR entry table (ILVU_ADR_ENTT) 519c4 includes an ILVU_ADR entry (ILVU_ADR_ENT) 519c41. The ILVU_ADR entry (ILVU_ADR_ENT) 519c41 is configured to include ILVU_ADR indicating an offset address from the head of the Interleved Block for the address of each ILVU.

  The ENT_VOBN table (ENT_VOBNT) 519c5 indicating a list of VOBs to which the time map information (TMAPI) 519c is referenced includes an entry VOB number (ENT_VOBN) 519c51. The entry VOB number (ENT_VOBN) 519c51 is configured to include ENT_VOBN indicating the VOB number to be referred to. Here, ENT_VOBN is described in the order of VOBs referred to by the time map information (TMAPI) 519c, and indicates which VOB the corresponding time map corresponds to using a VOB number.

  FIG. 62 is a flowchart for explaining an example of a playback procedure of an advanced VTS (AHDVTS in FIGS. 51, 74, 79, etc.) corresponding to the content of information (Application Type) included in management information (for example, AHDVTS_CAT in FIG. 53). It is. When playback of the advanced VTS is designated, the playback device (FIG. 72, etc.) checks the value of AHDVTS_CAT in AHDVTSI_MAT 510. When AHDVTS_CAT = 0011b (Yes in step ST620), since playback of this advanced VTS is a video object not accompanied by advanced content, that is, the playback control is not the Markup / Scrip language but the advanced HD video title set recording area 50 ( Since it is controlled only by AHDVTS data, playback can be performed based on the AHDVTS data (advanced VTS single playback process).

  When the value of AHDVTS_CAT is a value other than “0011b” (for example, when it is “0010b”) (NO in step ST620), this is a video object with advanced content, so that this video object is controlled. Playback must be based on the Markup / Script language. Otherwise, the playback of this video object will be different from what the content creator intended. Therefore, the playback device (FIG. 72, etc.) searches for a Markup / Script language file associated with the video object, and if the file is found (Yes in step ST622), the playback device (FIG. 72, etc.) uses the Markup / Script language description of the file. Then, the video object is played back (Markup / Script language execution process). If the Markup / Script language file associated with the video object is not found (NO in step ST622), the data is not prepared enough to control playback, and the process ends without performing playback.

  FIG. 63 shows the configuration of the navigation pack (NV_PCK) arranged at the head of each EVOBU in the enhanced video object (EVOB) referenced from the advanced VTS according to the embodiment of the present invention. The navigation pack includes a presentation control information packet (PCI_PKT) and a data search information packet (DSI_PKT), and the information shown in FIGS. 64 and 65 is stored in each packet.

  FIG. 64 exemplifies the contents of presentation control information (PCI) that is playback control information. This includes playback control general information (PCI_GI), non-seamless angle position information (NSML_AGLI) that includes head position information of each angle and does not require seamless playback when switching angles, and recording information (RECI). The Here, in the recording information (RECI), specific codes such as a country code, a copyright holder code, a recording date, and a recording number can be recorded regarding the contents of the recorded video, audio, and sub-picture.

  The reproduction control general information (PCI_GI) indicates control pack position information (NV_PCK_LBN) indicated by the logical block number (LBN) from the head of the VOBS, EVOBU category information (EVOBU_CAT) including analog copy control information, and the EVOBU reproduction start time. Information (EVOBU_S_PTM), information indicating the playback end time (EVOBU_E_PTM), EVOBU playback sequence end time information (EVOBU_SE_E_PTM) indicating the information of the playback end time when the video playback ends in the EVOBU, and EVOBU Cell elapsed time information (C_ELTM) indicating the elapsed time in the cell.

  In the playback control general information (PCI_GI), “EVOBU playback start time information (EVOBU_S_PTM)”, “EVOBU playback end time information (EVOBU_E_PTM)” and “cell elapsed time information (C_ELTM)” shown in parentheses are: Both are optional information and can be deleted depending on the embodiment.

  FIG. 65 illustrates the contents of data search information (DSI) that is data search information. Among them, data retrieval general information (DSI_GI), seamless reproduction information (SML_PBI) that is information for continuously reproducing interleaved interleaved units (ILVU) without interruption, and reproduction without interruption during angle switching Seamless angle position information (SML_AGLI) describing the jump destination address of each angle interleaved unit (ILVU) as information for switching, and synchronization indicating position information of audio packs and sub-picture packs reproduced in synchronization with video It includes information (SYNCI).

  The data search general information (DSI_GI) includes control pack playback time information (NV_PCK_SCR) indicated by system clock reference (SCR) -based time information, and control pack position information (NV_PCK_LBN) indicated by a logical block number (LBN) from the beginning of the VOBS. ), EVOBU conformance information (EVOBU_ADP_ID) that is information indicating whether the applicable disc of the applicable standard is a read-only disc of DVD-ROM or a writable disc such as DVD-R, and the EVOB containing the relevant DSI EVOBU_EVOB number information (EVOBU_EVOB_IDN: not shown) indicating an ID number, EVOBU cell number information (EVOBU_C_IDN) indicating an ID number of a cell including the corresponding DSI, and an attribute of the EVOB to which the corresponding EVOBU belongs Configured to include an EVOBU attribute number information indicating the number of broadcast (EVOBU_ATRN) and the cell elapsed time information indicating the cell elapsed time EVOBU (C_ELTM).

  In the data search general information (DSI_GI), “cell elapsed time information (C_ELTM)” shown in parentheses is optional information, and can be deleted depending on the embodiment of the present invention.

  FIG. 66 is a diagram illustrating a configuration example of the advanced VTS (AHDVTS). Since the advanced VTS is basically controlled by the Markup language, it needs to have a simplified structure so that it can be easily controlled by the Markup language. FIG. 66 shows an example of the structure. In this example, the advanced VTS is composed of only one VTS, the VTS is composed of only one title (Title), the Title is composed of only one PGC, and the PGC is composed of one or more PTTs. And one or more cells (Cell). Also, the video object VTS_EVOBS is referred to in a one-to-one correspondence by the cell.

  Here, there is no navigation command that can be recorded in VTSI or NV_PCK in the advanced VTS. This makes it possible to avoid the content production process and the production load of the playback device that are complicated by the simultaneous control of the markup language and the control of the navigation command in the advanced VTS.

  Further, in the standard VTS, the video object is accessed using the VOBU search information existing in the NV_PCK. However, in the advanced VTS, the VOBU search information of the NV_PCK is not used (it does not need to exist). Even when the time map information is added to the video object and the video object is accessed in accordance with an instruction of the Markup language, the time map information can be used to perform accurate access from any location.

  In FIG. 66, the attribute number “#n” for identifying the attribute (Attribute # n) assigned to each of the plurality of EVOBUs corresponding to each EVOB is specified by the EVOBU attribute number information (EVOBU_ATRN) shown in FIG. it can.

  FIG. 67 collectively shows the components of the time map according to the embodiment of the present invention. That is, the time element of the time map includes the starting point of description (unit of time map). For the PGC, the head of the PGC can be used as the starting point, and for the VOB, the head of the VOB can be used as the starting point. The time interval of the time map is fixed to 600 video fields (corresponding to 10 seconds) in NTSC, or if it is variable, the time interval of the time map is set in the time unit (for example, 1 to 255 seconds in 1 second increments) )do it. Furthermore, when an ILVU is configured, a time map can be described only in the path of the leading ILVU (for example, only the path after the angle number in the multi-angle block), or the time map can be described in all ILVUs.

  For the offset address of the time map, the start address of each VOB can be described. Specifically, the offset address can be described by the relative logical block number from the first logical block of VTSTT_VOBS, or the offset address can be described by the relative logical block number from the first logical block of the corresponding file (in this case, the current file is Depending on the set time map, it may be divided into a plurality of files as appropriate). Furthermore, the VOBU number quoted in the time map can be associated with a VOBU entry, and this VOBU entry can be used as acquisition information of the corresponding I picture and / or time information of this I picture.

  FIG. 68 collectively illustrates specific components of the time map according to the embodiment of the present invention. The block address (BLK_ADR) designates the head address of a continuous block (Intertiguous Block) or an interleaved block (Interleaved Block) with an offset address from the head of VTSTT_VOBS. The time entry address (TM_EN_ADR) can be specified by an offset address from the block head for a continuous block (single VOB), and by an offset address from the block head for an interleaved block (multiple VOBs). Time entry tables can be described as many as the number of VOBs specified (the same treatment as in the case of a single VOB). The time unit (TMU) is fixed to a constant value (for example, 10 seconds) within one VTSS_VOBS.

  As for the interleaved unit address (ILVU_ADR), the address of each ILVU can be specified by an offset address from the head of the interleaved block. Further, for the VOBU size (VOBU_SZ), the size of each VOBU can be described by the number of packs in the corresponding VOBU, and for the first reference picture size (1STREF_SZ), the size of the I picture of each VOBU can be described by the number of packs.

  FIG. 69 is an example having different reproduction paths for explaining the time map according to the embodiment of the present invention. As shown in the figure, it is assumed that two different playback paths (A) and (B) are recorded on the disc 1. (A) is, for example, a director's cut version of a movie, and (B) is, for example, a theatrical release version. In this example, the introductory chapter (VOB # 1) and the final chapter (VOB # 4) of (A) and (B) are exactly the same, and this chapter (VOB # 2 or VOB # 3) is different. At this time, in order to actually improve the recording efficiency on the disc, the introduction (VOB # 1) and the end (VOB # 4) are used as a common playback path, and objects (VOB # 2 and VOB) having different playback paths are used. # 3) is recorded individually. However, if recording is performed as it is, either one of (A) and (B) may not be read in time for reproduction, and the reproduction may be interrupted depending on the recording method. In order to solve this problem, as shown in the lower part of the figure, each VOB (VOB # 2 or VOB # 3) is divided into pieces and recorded alternately, so-called interleaved recording is performed, so that seamless playback is performed. Is realized. The unit of this interleaved recording is an interleaved unit (ILVU: Interleaved Unit).

  Here, a section where playback data of VOB # 1 or VOB # 4 is continuously arranged is defined as a continuous block (Contiguous Block), and a section where playback data of VOB # 2 and VOB # 3 are alternately arranged is interleaved. It is defined as a block (Interleaved Block).

  FIG. 70 is a diagram for explaining a time map of an ILVU section. Here, in order to construct a time map of the ILVU section (section of VOB # 2 and VOB # 3 in FIG. 70A) recorded in the interleave manner described in FIG. 69, VOB # 2 and VOB that are the respective playback paths. For # 3, time entries (VOB # 2, 2-1, 2-2,..., And VOB # 3, 3-1, 3 at predetermined time intervals (for example, every 10 seconds) from the beginning of # 3 -2, ...) (FIG. 70 (b)), and holds the address indicated by each time entry. Then, after the interleaved arrangement, the address indicated by each time entry is designated again as an offset address from the head of the interleaved block (FIG. 70 (c)).

  FIG. 71 shows an example in which the time map including the interleaved block section described in FIG. 70 is generalized. As shown in the figure, the VTSTT_VOBS of the playback object includes a continuous block of VOB # p, an interleaved block composed of VOB # q and VOB # r, and a continuous block of VOB # s (FIGS. 70 to 72). In this example, VOB # p = VOB # 1, VOB # q = VOB # 2, VOB # r = VOB # 3, and VOB # s = VOB # 4).

  This time map is configured for each block. Therefore, first, the head address of each block is indicated as an offset address (BLK_ADR) from the head of VTSTT_VOBS. By doing this, the position information of the time map of each block is described starting from the head of each block, and the information constituting the time map is indicated by completion within the block.

  Next, the address of each time entry (TM_EN #) indicated by a predetermined time interval (TMU) (for example, 10 seconds) is indicated by an offset address (TM_EN_ADR) from the head of each block, and a time entry table (not shown). ). At this time, if the block is an interleaved block, the time entries are divided by the number of VOBs constituting the block (in this example, TM_EN # q1, # q2,..., TM_EN # r1, # r2,. ) Store in each time entry table (not shown).

  Here, when the block constituting the time map is an interleaved block, the start address (ILVU_ADR) of each interleaved unit alternately arranged in the interleaved block is indicated by an offset address from the block head. With this information, the head of each ILVU can be easily found, and seamless switching playback between ILVUs to be continuously played back is possible (each ILVU size (ILVU_SZ) is not shown, but for example TMAP_GI in FIG. 59). Can be described in).

  Also, as information on VOBU in which actual reproduction information is stored, each time map includes the number of all VOBUs stored in each block (VOBU_Ns; not shown), the size of each VOBU (VOBU_SZ), The playback time (VOBU_PB_TM: not shown), end address information (1STREF_SZ) of the first reference picture (first I picture) stored in the VOBU, and the like are used to access the target data. In addition to the first reference picture, the end address information of the second reference picture (I and P pictures other than the first reference picture) and the third reference picture (I and P pictures other than the first and second reference pictures) ( 2NDREF_SZ and 3RDREF_SZ (none of which are shown) may be included in the time map.

  FIG. 72 is a block diagram illustrating an example of the internal structure of a playback apparatus (advanced VTS-compatible DVD video player) according to another embodiment of the present invention. This DVD video player reproduces and processes the recorded content (DVD video content and / or advanced content) from the information storage medium 1 shown in FIG. 1, FIG. 50, FIG. 51, FIG. 73, FIG. In addition, advanced content is fetched from a communication line such as the Internet and processed.

  72 includes a DVD video playback engine (DVD_ENG) 100, an interactive engine (INT_ENG) 200, a disc unit (disc drive) 300, a user interface unit 400, and the like. The DVD video playback engine 100 plays back and processes the MPEG2 program stream (DVD video content) recorded on the information storage medium 1. The interactive engine (INT_ENG) 200 plays and processes advanced content. The disc unit 300 reads DVD video content and / or advanced content recorded on the information storage medium 1. The user interface unit 400 transmits an input (user operation / user operation) by a user of the player to the DVD video player side as a user trigger.

  Basically, when playing a standard VTS (standard VTS playback state), user input is transmitted to the DVD video playback engine, and when playing an advanced VTS (advanced VTS playback state), user input is transmitted to the interactive engine. Is done. However, even when the advanced VTS is played back, a predetermined user input can be directly transmitted to the DVD playback engine.

  The interactive engine (INT_ENG) 200 includes an Internet connection unit. The Internet connection unit functions as a communication unit for connecting to the server unit 500 or the like via a communication line such as the Internet. Further, the interactive engine (INT_ENG) 200 includes a buffer unit 209, a parser 210, an XHTML / SVG / CSS layout manager 207, an ECMAScript interpreter / DOM manipulator / SMIL interpreter / timing engine / object (interpreter unit) 205, an interface handler 202, media It includes a decoder 208a / 208b, an AV renderer 203, a buffer manager 204, an audio manager 215, a network manager 212, a system clock 214, a persistent storage 216, and the like.

  72, the DVD video playback control unit 102, DVD video decoder 101, DVD system clock 103, interface handler 202, parser 210, interpreter unit 205, XHTML / SVG / CSS layout manager 207, AV renderer 203, The media decoder 208a / 208b, buffer manager 204, audio manager 215, network manager 212, system clock 214, etc. are microcomputers (and / or hardware logics) that perform the function of each block configuration by an embedded program (firmware) not shown. ). A work area used when executing the firmware can be obtained by using a semiconductor memory (not shown) in each block configuration (and a hard disk if necessary).

  The DVD video playback engine (DVD_ENG) 100 is a device for playing back DVD video content recorded on the information storage medium 1 shown in FIG. 1 or the like. The DVD video playback engine (DVD_ENG) 100 decodes the DVD video content read from the disc unit 300. It includes a video decoder 101, a DVD video playback control unit 102 that controls playback of DVD video content, a DVD system clock 103 that determines decoding and output timings in the DVD video decoder, and the like.

  The DVD video decoder 101 decodes the main video data, audio data, and sub-video data read from the information storage medium 1 shown in FIG. 1 and the like, and decodes the decoded video data (main video data and sub-video data are combined). Etc.) and audio data respectively. That is, the player shown in FIG. 72 can reproduce data such as video and audio having an MPEG2 program stream structure in the same manner as a normal DVD video player.

  In addition to this, the DVD video playback control unit 102 is configured to control playback of DVD video content in accordance with a “DVD control” signal output from the interactive engine (INT_ENG) 200. Specifically, the DVD video playback control unit 102 responds to the interactive engine (INT_ENG) 200 when a certain event (for example, menu call or title jump) occurs in the DVD video playback engine 100 during DVD video playback. The “DVD trigger” signal indicating the playback status of the DVD video content can be output. At that time (at the same time as the output of the DVD trigger signal or at an appropriate timing before and after the DVD trigger signal), the DVD video playback control unit 102 sets the property information of the DVD video player (for example, the audio language and sub-picture subtitle language set in the player). , A “DVD status” signal indicating a playback operation, a playback position, various time information, a disc content, and the like can be output to the interactive engine (INT_ENG) 200.

  The interface handler 202 receives a “user trigger” from the user interface unit 400 corresponding to a user operation (menu call, title jump, playback start, playback stop, playback pause, etc.). After that, the interface handler 202 transmits the received user trigger to the interpreter unit 205 as a corresponding “event”. For example, the Markup language provides the following instructions for this “event”.

1 → Issues a “command” corresponding to a user operation. That is, the same command as the user operation is transmitted to the DVD video playback engine as a DVD control;
2. Issue a “command” different from the user operation. In other words, the user operation is replaced with another action according to the Markup language instruction;
3 → Ignore user trigger. In other words, user events are prohibited for reasons such as the possibility of playing DVD videos unintended by the content provider.

  The contents of the user trigger signal transmitted to the interface handler 202 may be transmitted to the AV renderer 203 as an “AV output control” signal. Thus, for example, when the user changes the content or window size or shifts the display position by operating the cursor key of a remote controller (not shown), the user trigger signal by this operation is used as the corresponding AV output control signal. And output to the AV renderer 203. In addition, by sending a user trigger indicating switching between video / audio output from the DVD video playback engine 100 and video / audio output from the interactive engine 200 to the AV renderer 203, video / audio output by a user operation can be performed. Switching can be performed.

  The interface handler 202 transmits / receives a “DVD status” signal, a “DVD trigger” signal and / or a “DVD control” signal to / from the DVD video playback control unit 102, or a “user” to / from the user interface unit 400. Send and receive “trigger” signals. The interface handler 202 is further configured to send and receive “event”, “property”, “command”, and “control” signals to and from the interpreter unit 205.

That is, the interface handler 202 performs the following:
1. A “DVD trigger” signal indicating the operation of the DVD video playback engine 100 from the DVD video playback engine 100 or a “user trigger” indicating a user operation from the user interface unit 400 is transmitted to the interpreter unit 205 as an “event”. To do.

  2. A “DVD status” signal indicating the playback status of the DVD video playback engine 100 from the DVD video playback engine 100 is transmitted to the interpreter unit 205 as “property”. At this time, the DVD status information is stored in the property buffer 202a of the interface handler 202 as needed.

3. According to the content of the “command” signal from the interpreter unit 205,
A “DVD control” signal for controlling playback of the DVD video playback engine 100 is output to the DVD video playback engine 100, and an “AV output control” signal for switching video and audio is output to the AV renderer 203, A “buffer control” signal for reading the buffer 209 and erasing the buffer 209 is output to the buffer manager 204, and an “update control” signal for downloading the update audio data is output to the audio manager 215. A “media control” signal for instructing the decoders 208a / 208b to decode various media is output.

  4). Information of the DVD system clock 103 in the DVD video playback engine 100 is measured by the DVD timing generator 202b of the interface handler 202, and the measurement result is transmitted to the media decoders 208a / 208b as a “DVD timing” signal. That is, the media decoders 208a / 208b can decode various media in synchronization with the system clock 103 of the DVD video playback engine 100.

  As described above, the interface handler 202 has a function of converting control signals and the like between the DVD video playback engine 100 and the interactive engine 200 after analyzing and interpreting the advanced content.

  The interface handler 202 exchanges the first signal on the basis of the contents analyzed by the parser 210 and interpreted by the interpreter unit 205 or a user trigger from an input device (such as a remote controller). It is configured to perform the exchange. In other words, the interface handler 202 determines the AV based on at least one of the first signal exchanged with the DVD video playback control unit 102 and the second signal exchanged with the interpreter unit 205. It can also be said that it controls the output state of the video / audio signal by the renderer 203.

  The first signal is a signal relating to the reproduction status of the information storage medium 1, and corresponds to a “DVD control” signal, a “DVD trigger” signal, a “DVD status” signal, and the like. The second signal is a signal related to the contents of advanced content, and corresponds to an “event” signal, a “command” signal, a “property” signal, a “control” signal, and the like.

  Here, the interface handler 202 is configured to execute processing corresponding to the user trigger according to the Markup language. Then, the AV renderer 203 synthesizes the video / audio data generated by the media decoder 208a / 208b with the video / audio data played back by the DVD video playback engine 100 based on the execution result of the processing corresponding to the user trigger. And output. Alternatively, the AV renderer 203 selects one of the video / audio data generated by the media decoder 208a / 208b and the video / audio data reproduced by the DVD video reproduction engine 100 based on the execution result of the “command” in the interface handler 202. It can be said that it is configured to select and output.

  Generally speaking, the parser 210 performs syntax analysis of Markup language indicating playback control information included in advanced content obtained from the information storage medium 1 or advanced content obtained from the Internet or the like. Here, the markup language is composed of a combination of the above-mentioned markup languages such as HTML / XHTML and SMIL, Script languages such as ECMAScript and JavaScript, and StyleSheet such as CSS. The parser 210 has a function of transmitting the ECMAScript module to the ECMAScript interpreter of the interpreter unit 205, the SMIL module to the SMIL interpreter, and the XHTML module to the XHTML / SVG / CSS layout manager 207 according to the result of language analysis.

  The ECMAScript interpreter interprets the aforementioned ECMAScript module and follows its instructions. That is, the ECMAScript interpreter responds to an “event” signal sent from the interface handler 202 or a “property” signal read from the property buffer 202 a of the interface handler 202 with a “command” signal for controlling each function in the interactive engine 200. Is issued to the interface handler 202. At this time, the ECMAScript interpreter issues a “command” signal to the DVD video playback engine 100 at a timing indicated by the Markup language according to the time measured by the system clock 214, or sends a “media control” signal to the media decoder 208a / Issued to 208b. This enables control of the DVD video playback engine 100 and various media controls (sound, still image / animation, text / font, moving image decoding control, etc.).

  The SMIL timing engine interprets the aforementioned SMIL module and follows the interpreted instructions. That is, the SMIL timing engine sends a “control” signal to the interface handler 202 or the “event” signal sent from the interface handler 202 or the “property” signal read from the property buffer 202 a of the interface handler 202 according to the system clock 214. It has a function of issuing to the media decoder 208a / 208b. This makes it possible to control the DVD video playback engine 100 and decode various media (sound, still image / animation, text / font, moving image) at a desired timing. That is, the SMIL timing engine can operate based on the system clock 214 in accordance with the description of the Markup language, and can also operate based on the DVD system clock 103 from the DVD timing generator 202b.

  The XHTML / SVG / CSS layout manager 207 interprets the aforementioned XHTML module and follows its instructions. That is, the XHTML / SVG / CSS layout manager 207 outputs a “layout control” signal to the AV renderer 203. The “layout control” signal contains information about the screen size and position of the output video (may include information about display time such as display start / end / continuation), and information about the level of output audio (output start / end)・ It may include information about output time such as continuation). The text information for display included in the XHTML module is sent to the media decoder 208a / 208b, and is decoded and displayed using a desired font.

  The specific method for parsing and interpreting Markup language and Script language may be the same method as parsing and interpretation in known technologies such as HTML / XHTML, SMIL, ECMAScript, and JavaScript. May be the microcomputer described at the beginning of the description of FIG. 72). However, the commands and variables described in the script are different because the control targets are different. In the Markup language used when implementing the present invention, specific commands and variables related to the reproduction of DVD video content and / or advanced content are used. For example, a command for switching the playback content of DVD video content or advanced content in response to a certain event is specific to the Markup language or Script language used in one embodiment of the present invention.

  Other examples of commands and variables specific to the Markup language and the Script language include changing the size of the video from the DVD video playback engine 100 and / or the interactive engine 200 and changing the arrangement of the video. The change of the size of the video is instructed by a command for instructing the size change and a variable for specifying the changed size. The video layout change is instructed by a command to change the display position and a variable that specifies the coordinates after the change, etc. When the display target overlaps on the screen, the vertical position relationship of the overlap, A variable that specifies the transparency is also added.

  Alternatively, as another example of commands and variables specific to the Markup language and the Script language, there are those that change the audio level from the DVD video playback engine 100 and / or the interactive engine 200 and select the audio language to be used. The change of the sound level is instructed by a command for changing the sound level and a variable for designating the sound level after the change. The selection of the used speech language is instructed by a command for instructing the change of the used speech language and a variable for designating the type of language after the change. Some control user triggers from the user interface unit 400.

  Based on the Markup and Script language commands / variables as exemplified above, the “layout control” signal is sent to the XHTML / SVG / CSS layout manager 207 (some functions may be performed by the SMIL timing engine 206). ) To the AV renderer 203. The “layout control” signal is the layout on the screen of the video to be displayed on an external monitor device (not shown), the video size, the video output timing, the video output time, and / or the audio to be reproduced from an external speaker (not shown). Is a signal for controlling the volume level, audio output timing, and audio output time.

  The media decoder 208a / 208b decodes data of advanced content such as audio, still image (including background image) / animation, text / font, and moving image included in the advanced content. That is, the media decoder 208a / 208b includes an audio decoder, a still image / animation decoder, a text / font decoder, and a moving image decoder corresponding to the decoding target. For example, audio data in advanced content encoded by MPEG, AC-3, or DTS is decoded by an audio decoder and converted into uncompressed audio data. Still image data and background image data encoded by JPEG, GIF, and PNG are decoded by a still image decoder and converted into uncompressed image data. Similarly, moving images and animation data encoded by, for example, MPEG2, MPEG4, MacromediaFlash, and SVG (Scalable Vector Graphics) are decoded by a moving image decoder or animation decoder and converted into uncompressed image data. The text data included in the advanced content is text data that can be superimposed on a moving image or a still image by being decoded by a text / font decoder using font data (for example, OpenType format) included in the advanced content. Is converted to Video / audio data including the decoded audio data, image / animation data, moving image data, and text image data as appropriate is sent from the media decoder 208a / 208b to the AV renderer 203. These advanced contents are decoded in accordance with an instruction of a “media control” signal from the interface handler 202, and synchronized with a “DVD timing” signal from the interface handler 202 or a “timing” signal from the system clock 214. Decoding is performed.

  The AV renderer 203 has a function of controlling video / audio output. Specifically, the AV renderer 203 determines, for example, the video display position, display size, and the display timing and display time in accordance with the “layout control” signal output from the XHTML / SVG / CSS layout manager 207. Depending on the type of monitor specified and / or the type of video to be displayed, and the volume of the audio (which may include the output timing and output time). The pixel conversion is performed. The video / audio output to be controlled is output from the DVD video playback engine 100 and the media decoders 208a / 208b. Furthermore, the AV renderer 203 has a function of controlling mixing (mixing) and switching (switching) of DVD video content and advanced content in accordance with an “AV output control” signal output from the interface handler 202.

  72 includes an interface for sending the markup language in the advanced content read from the information storage medium 1 to the parser 210 via the buffer unit 209, and the read advanced content. An interface is provided for sending the data (sound data, still image / animation data, text / font data, moving image data, etc.) to the media decoder 208a / 208b via the buffer unit 209. These interfaces constitute an interface (first interface) different from the Internet connection unit of FIG.

  72 receives an advanced content from a communication line such as the Internet, and an interface for sending the markup language in the received advanced content to the parser 210 via the buffer unit 209, and in the received advanced content. Are provided for sending the data (audio data, still image / animation data, font / text data, moving image data, etc.) to the media decoder 208a / 208b via the buffer unit 209. These interfaces constitute the Internet connection unit (second interface) of FIG.

  The buffer unit 209 stores the advanced content downloaded from the server unit 500 and includes a buffer for storing the advanced content read from the information storage medium 1 by the disk unit 300. The buffer unit 209 reads the advanced content in the server unit 500 and downloads the advanced content via the Internet connection unit under the control of the buffer manager 204 based on the Markup language / Script language.

  Further, the buffer unit 209 reads the advanced content recorded in the information storage medium 1 under the control of the buffer manager 204 based on the Markup language / Script language. At this time, if the disc unit 300 is a device capable of high-speed access to the disc, the advanced content is simultaneously read from the information storage medium 1 while reproducing the DVD video content, that is, reading the DVD video data from the information storage medium 1. Can be read.

  When the disc unit 300 is not a device that can be accessed at high speed, or when the playback operation of the DVD video content is completely guaranteed, it is necessary not to interrupt the playback of the DVD video content. In this case, the advanced content is read from the information storage medium 1 in advance and stored in the buffer before the reproduction is started. As a result, the DVD video content is read from the information storage medium 1 and at the same time, the advanced content is read from the buffer, so that the disc unit 300 is not burdened. Therefore, it is possible to simultaneously reproduce the DVD video content and the advanced content without interrupting the reproduction of the DVD video content.

  As described above, the advanced content downloaded from the server unit 500 is also stored in the buffer unit 209 in the same manner as the advanced content recorded in the information storage medium 1, so that it can be read and reproduced simultaneously with the DVD video content and the advanced content. It becomes possible.

  Further, the storage capacity of the buffer unit 209 has a limit. That is, the data size of advanced content that can be stored in the buffer unit 209 is limited. For this reason, under the control of the buffer manager 204 (buffer control), advanced content that is less necessary (for example, content that cannot be reused) is deleted, or advanced content that is highly necessary (for example, content that can be reused) is stored. It is possible to do. The above-described control for storage and the above-mentioned control for erasure can be automatically performed by the buffer unit 209.

  Further, the buffer unit 209 loads the content requested by the buffer manager 204 from the disk unit 300 or the server unit 500 to the buffer unit 209 and informs the buffer manager that the advanced content designated by the buffer manager 204 has been loaded into the buffer. Has functions (preload end trigger, load end trigger).

The buffer manager 204 can send the following instructions as “buffer control” to the buffer unit 209 (even during playback of the DVD video content) by an instruction in the Markup language:
→ Read a specific file or a part of a file from a server → Read a specific file or a part of a file from a disk → Erase a specific file or a part of a file from a buffer.

  Furthermore, the buffer manager 204 instructs the buffer unit 209 to load the advanced content according to the loading information described in the markup language (or described in the file indicated by the markup language). In addition, it has a function of requesting that a specific advanced content described in the loading information is loaded into the buffer unit 209 (buffer control).

  When the above-mentioned specific advanced content is loaded into the buffer unit 209, the buffer unit 209 notifies the buffer manager 204 of this, and the buffer manager notifies this to the interface handler 202 (preload end trigger, load end trigger).

  The audio manager 215 has a function of instructing the buffer unit 209 to load the update audio data (audio commentary data) from the information storage medium 1 of the disk unit 300 or the server unit 500 according to the Markup language instruction (update control).

  The network manager 212 controls the operation of the Internet connection unit. In other words, when a connection to or disconnection from the network is instructed as a “command” by the Markup language, the network manager switches connection / disconnection of the Internet connection unit. The network manager 212 has a function of checking the connection status to the network, and can download advanced content according to the connection status to the network using the Markup language.

  The persistent storage 216 is an area for recording information about the information storage medium 1 (information set by the user, etc.), and is composed of a nonvolatile storage medium such as a hard disk or a flash memory. That is, this information is retained even if the DVD player is turned off.

  As information related to the information storage medium to be played, realized by Markup instructions (storage control), for example, the playback position of DVD video content and advanced content, user information required for user authentication realized by advanced content, and advanced content By recording information such as the game score of the game to be played, the next time the information storage medium is played, it is possible to continue playing from the previous time. In addition, when the information storage medium is reproduced, the advanced content downloaded from the server unit to the buffer is recorded in the persistent storage 216, so that the information storage medium can be reproduced from the next time without being connected to the network. It becomes possible.

  The components of the interactive engine 200 in FIG. 72 can be summarized as follows when the expression is changed. In other words, the interactive engine 200 includes the following.

・ Parser 210
Parser 210 parses the contents of the Markup language.

Interpreter unit 205, XHTML / SVG / CSS layout manager 207
An interpreter unit 205 and an XHTML / SVG / CSS layout manager 207 configured to include an ECMAScript, SMIL timing engine, and the like interpret the analyzed module.

Interface handler 202
The interface handler 202 handles the control signal from the interpreter unit 205 and the control signal from the DVD video playback control unit 102.

Media decoder 208a / 208b
The media decoder 208a / 208b corresponds to data such as audio, still image / animation, text / font, and moving image included in the advanced content in synchronization with the system clock 103 of the DVD playback engine 100 or the system clock 214 of the interactive engine 200. Generated video / audio data.

・ AV renderer 203
The AV renderer 203 combines the video / audio data generated by the media decoder 208a / 208b with the video / audio data reproduced by the DVD video reproduction engine 100 based on the execution result of the “command” in the interface handler 202. Output. Alternatively, the AV renderer 203 selects one of the video / audio data generated by the media decoder 208a / 208b and the video / audio data reproduced by the DVD video reproduction engine 100 based on the execution result of the “command” in the interface handler 202. Output.

Buffer unit 209
The buffer unit 209 temporarily stores the advanced content acquired from the server unit 500 via the disk unit 300 or the Internet connection unit.

Buffer manager 204
The buffer manager 204 reads the advanced content data into the buffer unit 209 or deletes it from the buffer unit 209 according to the instruction of the interface handler 202 (markup language instruction) and according to the description of the loading information (see FIG. 90).

・ Network manager
Controls connection / disconnection to the network and investigates the connection status according to the Markup language instructions.

Persistent storage 216
Information related to information storage media such as content playback position and user information, and advanced content downloaded from the server unit 500 are held.

  FIG. 73 shows an example of an information storage medium that can be produced by a conventional production technique and that records only content (standard content) for the purpose of improving the quality of the main title. Here, this information storage medium is called a “content type 1 disc”. The content type 1 disc is an HD video manager recording area 30 recorded in the video data recording area 20 (in this case, the Application Type in HDVMG_CAT in the area 30 indicates that the information storage medium 1 includes only the standard VTS “0000b”. "Is recorded), an advanced HD video title set recording area 50 including one or more HD video title set recording areas 40 and recorded in the video data recording area 20, and advanced content recording This is an information storage medium in which there is no advanced content recorded in the area 21.

  When reproducing the information storage medium 1, the FP_PGCI recorded in the HD video manager information management table 310 is referred to, and the reproduction is started according to the description of the FP_PGCI. This is the same procedure as conventional DVD video.

  When reproducing the information storage medium 1, the data supplied from the information storage medium 1 in FIG. 72 showing the configuration example of the DVD player is processed only by the DVD video playback engine 100. The interactive engine 200 does not perform any processing. That is, the video / audio data processed and output by the DVD video playback engine 100 is output through the AV renderer 203.

  FIG. 74 shows contents (advanced contents) for the purpose of improving menus with rich colors and interactivity in contents such as menu screens and privilege videos in addition to the realization of high image quality of the main title. This is an example of an information storage medium on which only is recorded. Here, this information storage medium is referred to as “content type 2 disc (consisting of only advanced VTS)”. A content type 2 disc (consisting of only an advanced VTS) has one HD video manager recording area 30 recorded in the video data recording area 20, one advanced HD video title set recording area 50, and an advanced content recording area 21. This is an information storage medium that includes advanced content to be recorded and does not have the HD video title set recording area 40 recorded in the video data recording area 20.

  Here, since the menu object is not required in the advanced VTS, the HD video manager recording area 30 of the content type 2 disc includes the advanced HD video manager information recording area (AHDVMGI) 35 and the advanced HD video manager information backup area (AHDVMGI_BUP). 36), and “0001b” indicating that the information storage medium 1 includes only the advanced VTS is recorded in the Application Type in the HDVMG_CAT in the area 30 at this time.

  When reproducing the information storage medium 1 of this “content type 2 disc”, the startup information (STARTUP.XML) recorded in the Markup / Script language recording area is referred to, and the “start” described in this information is referred to. Execute “Markup language file to be a point” and start playback.

  FIG. 75 shows an example of the detailed data structure in advanced HD video manager information (AHDVMGI) area 35 in information storage medium 1 in FIG. In the advanced HD video manager information (AHDVMGI) area 35, advanced HD video manager information management table (AHDVMGI_MAT) information 350 that collectively records management information common to the entire HD_DVD video content recorded in the video data recording area 20 is recorded. In addition, there is advanced title search pointer table (ADTT_SRPT) information 351 in which information useful for searching for each title existing in the HD_DVD video content (detecting a cue position) is recorded.

  FIG. 76 shows an example of the detailed data structure in advanced HD video manager information management table (AHDVMGI_MAT) 350 in FIG. In the HD video manager information management table (HDVMGI_MAT) 310, an HD video manager identifier (HDVMG_ID), an HD video manager end address (HDVMG_EA), an HD video manager information end address (HDVMGI_EA), an HD_DVD video standard version number ( VERN), HD video manager category (HDVMG_CAT) (in this information storage medium, Application Type in HDVMG_CAT is recorded as “0001b”), volume set identifier (VLMS_ID), adaptation identifier (ADP_ID), HD video title set Number (HDVTS_Ns) ("0" is recorded in this information storage medium because there is no standard VTS), provider specific Identifier (PVR_ID), POS code (POS_CD), various information HD video manager information management table end address (HDVMGI_MAT_EA), the start address of TT_SRPT (TT_SRPT_SA) is recorded.

  The first address (FP_PGCI_SA) of the first play program chain information existing on the content type 1 disc, the first address of HDVMGM_VOBS (HDVMGM_VOBS_SA), the first address of HDVMGM_PGCI_UT (HDVMGM_PGCI_UT_SA), the first address of PTL_MAIT, the first address of PTL_MAIT_PT_MAIT HDVTS_ATRT_SA), TXTDT_MG start address (TXTDT_MG_SA), HDVMGM_C_ADT start address (HDVMGM_C_ADT_SA), HDVMGM_VOBU_ADMAP start address (HDVMGM_VOBUHDMGD_GMHD_GMHD_GMHD_GMHD_GMHD_GMHD_GMHD_GMHD_GMHD_GMHD_GMHD_GMP_GMHD_GMHD_GHDMPGVM_GHDMP V_ATR), HDVMGM audio stream number (HDVMGM_AST_Ns), HDVMGM audio stream attribute (HDVMGM_AST_ATR), HDVMGM sub-picture stream number (HDVMGM_SPST_Ns), HDVMGM sub-picture stream attribute (HDVMRT_menu selection) First address PGCI (FP_PGCI), start address information of HDMENU_AOBS (HDMENU_AOBS_SA), start address information of HDVMGM_AOBS information table (HDMENU_AOBSIT_SA), HDVMGM graphic unit stream number information (HDVMGM_GUST_Ns) There does not exist in (or the reserved area).

  FIG. 77 shows an example of the internal structure of advanced title search pointer table (ADTT_SRPT) 351 shown in FIG. The advanced title search pointer table (ADTT_SRPT) 351 includes advanced title search pointer table information (ADTT_SRPTI) 351a and advanced title search pointer (ADTT_SRP) information 351c. Only one advanced title search pointer (ADTT_SRP) information 351c in the advanced title search pointer table (ADTT_SRPT) 351 exists in the information storage medium including the advanced VTS, and does not exist in other information storage media.

  Common title management information of the advanced title search pointer table (ADTT_SRPT) 351 is recorded in the advanced title search pointer table information (ADTT_SRPTI) 351a, and the number of title search pointers (ADTT_SRP_Ns) included in the advanced title search pointer table (ADTT_SRPT) 351 ) Information ("1" is recorded because there is only one advanced VTS in this information storage medium), and this advanced title search pointer table (ADTT_SRPT) in the file of the advanced HD video manager information (AHDVMGI) area ) End address (ADTT_SRPT_EA) information of 351 (only one advanced VTS exists in this information storage medium) A fixed value is recorded).

Further, in one advanced title search pointer (ADTT_SRP) information 351c, various pieces of information such as the number of part of titles (PTT: Part_of_Title) (PTT_Ns) related to the title indicated by the search pointer and the head address (HDVTS_SA) of the corresponding HDVTS are stored. To be recorded. (Here, title playback type (TT_PB_TY), number of angles (AGL_Ns), title parental ID field (TT_PTL_ID_FLD) information, HDVTS number (HDVTSN), HDVTS title number (HDVTS_TTN) existed in the content type 1 disc are present. No or reserved area.)
FIG. 78 is a diagram for explaining a playback model (example 1) of a disc on which an advanced VTS (AHDVTS) is recorded. A reproduction example of a typical content type 2 disc (only the advanced VTS exists) will be described with reference to FIG.

  When playback of the content type 2 disc (only the advanced VTS exists) starts, the interactive engine (INT_ENG) 200 displays the menu page XML for playing back the menu screen described in the Markup / Script language stored in the advanced content recording area. Parse the file.

  For example, when configuring a menu screen that prompts the user to select a button while repeatedly reproducing an impressive scene in a movie image, the menu page XML file includes an advanced VTS in the DVD video playback engine (DVD_ENG) 100. Control processing for repeatedly playing back video data is described in Markup / Script. The interactive engine (INT_ENG) 200 issues a playback command to the DVD video playback engine (DVD_ENG) 100 according to the description (arrow a).

  At the same time, the menu page XML file uses the button image stored in the animation / still image recording area in the advanced content recording area 21 and the font data stored in the font recording area to form a menu screen. Is stored. The interactive engine (INT_ENG) 200 synthesizes the output composed of the screen according to these descriptions and the video output of the advanced VTS by the above-described DVD video playback engine (DVD_ENG) 100 by the AV renderer 203 to realize the playback of the menu screen. To do.

  Next, the user uses a remote controller or the like to select a button for executing playback of the main video from the menu selection buttons arranged on the screen. In the menu page XML file, script processing associated with button selection is described, and a jump to the DVD playback engine control page occurs (arrow b).

  In the DVD playback engine control page, a control process for reproducing the head of the main video is described in Markup / Script. The interactive engine (INT_ENG) 200 issues a playback command to the DVD video playback engine (DVD_ENG) 100 according to the description (arrow c). The DVD playback engine control page uses the button image stored in the animation / still image recording area in the advanced content recording area 21 and the font data stored in the font recording area to reproduce the main video. A description for configuring a menu screen that can be displayed on the screen (for example, configuring a menu on a screen smaller than the main video and making the menu screen transparent and superimposing it on the main video) Stored. In accordance with these descriptions, the interactive engine (INT_ENG) 200 synthesizes the output comprising the screen and the video output of the advanced VTS from the DVD video playback engine (DVD_ENG) 100 by the AV renderer 203 to generate a menu screen and subtitles. Realize playback.

  When the playback of the main video is finished, the interactive engine (INT_ENG) 200 jumps the XML file to be processed to the menu page XML file in order to perform menu screen playback again in accordance with the description in the DVD video playback engine control page XML file. (Arrow d). In the figure, a broken-line arrow marked with a diagonal line indicates that a jump by a navigation command cannot be performed in the advanced VTS.

  79 shows content that can be produced using conventional production technology (standard content) with the aim of improving the quality of the main title, and the menu screen and privilege video in addition to the realization of higher quality of the main title. Is an example of an information storage medium in which both a menu rich in color and content (advanced content) for the purpose of improving interactivity are recorded. Here, this information storage medium is referred to as “content type 2 disc (a mixed type of advanced VTS and standard VTS)”.

  A content type 2 disc in which the advanced VTS and the standard VTS are mixed includes one HD video manager recording area 30 recorded in the video data recording area 20, one or more HD video title set recording areas 40, and one advanced HD video. The title set recording area 50 and the advanced content (21A to 21E) recorded in the advanced content recording area 21 are configured. Here, since the disc including the advanced VTS does not require a menu object, the HD video manager recording area 30 includes an advanced HD video manager information recording area (AHDVMGI) 35 and an advanced HD video manager information backup area (AHDVMGI_BUP). ) 36. At this time, “0010b” indicating that the information storage medium 1 includes both the standard VTS and the advanced VTS is recorded in the Application Type in the HDVMG_CAT in the area 30.

  When the information storage medium (content type 2 disc) 1 is reproduced, the startup information (STARTUP.XML) recorded in the Markup / Script language recording area is referred to, and the “starting point” described in this information is referred to. Execute the “Markup language file” and start playback.

  FIG. 80 shows an example of the detailed data structure in advanced HD video manager information (AHDVMGI) area 35 in the information storage medium of FIG. In the advanced HD video manager information (AHDVMGI) area 35, advanced HD video manager information management table (AHDVMGI_MAT) information 350 that collectively records management information common to the entire HD_DVD video content recorded in the video data recording area 20 is recorded. In addition, there is advanced title search pointer table (ADTT_SRPT) information 351 in which information useful for searching for each title existing in the HD_DVD video content (detecting a cue position) is recorded.

  FIG. 81 shows an example of the detailed data structure in advanced HD video manager information management table (AHDVMGI_MAT) 350 in FIG. The advanced HD video manager information management table 350 includes an HD video manager identifier (HDVMG_ID), an HD video manager end address (HDVMG_EA), an advanced HD video manager information end address (AHDVMGI_EA), and a version of the HD_DVD video standard. A number (VERN), an HD video manager category (HDVMG_CAT: in this information storage medium, Application Type in HDVMG_CAT is “0010b”), a volume set identifier (VLMS_ID), an adaptation identifier (ADP_ID), Number of HD video title sets (HDVTS_Ns), provider-specific identifier (PVR_ID), POS code (POS_CD), Advan And de-HD video manager information management table of the end address (AHDVMGI_MAT_EA), various types of information of the start address (TT_SRPT_SA) of TT_SRPT are recorded.

  The first address (FP_PGCI_SA) of the first play program chain information existing on the content type 1 disc, the first address of HDVMGM_VOBS (HDVMGM_VOBS_SA), the first address of HDVMGM_PGCI_UT (HDVMGM_PGCI_UT_SA), the first address of PTL_MAIT, the first address of PTL_MAIT_PT_MAIT HDVTS_ATRT_SA), TXTDT_MG start address (TXTDT_MG_SA), HDVMGM_C_ADT start address (HDVMGM_C_ADT_SA), HDVMGM_VOBU_ADMAP start address (HDVMGM_VOBUHDMGD_GMHD_GMHD_GMHD_GMHD_GMHD_GMHD_GMHD_GMHD_GMHD_GMHD_GMHD_GMP_GMHD_GMHD_GHDMPGVM_GHDMP V_ATR), HDVMGM audio stream number (HDVMGM_AST_Ns), HDVMGM audio stream attribute (HDVMGM_AST_ATR), HDVMGM sub-picture stream number (HDVMGM_SPST_Ns), HDVMGM sub-picture stream attribute (HDVMGM_SPST_language selection information) First-play PGCI (FP_PGCI), start address information of HDMENU_AOBS (HDMENU_AOBS_SA), start address information of HDVMGM_AOBS information table (HDMENU_AOBIT_SA), HDVMGM graphic unit stream number information (HDVMGM_GUST_Ns), Absent in content type 2 disk) (or the reserved area).

  FIG. 82 shows an example of the internal structure of advanced title search pointer table (ADTT_SRPT) 351 shown in FIG. The advanced title search pointer table (ADTT_SRPT) 351 includes advanced title search pointer table information (ADTT_SRPTI) 351a, standard title search pointer (SDTT_SRP) 351b, and advanced title search pointer (ADTT_SRP) information 351c. Only one advanced title search pointer (ADTT_SRP) information 351c in the advanced title search pointer table (ADTT_SRPT) 351 exists in the information storage medium including the advanced VTS, and does not exist in other information storage media. The standard title search pointer (SDTT_SRP) 351b exists only when the standard VTS is recorded on the information storage medium.

  The advanced title search pointer table information (ADTT_SRPTI) 351a includes the number of title search pointers (ADTT_SRP_Ns) included in the advanced title search pointer table (ADTT_SRPT) 351 as common management information of the advanced title search pointer table (ADTT_SRPT) 351. Information and end address (ADTT_SRPT_EA) information of this advanced title search pointer table (ADTT_SRPT) 351 in the file of the advanced HD video manager information (AHDVMGI) area are recorded.

  In the single advanced title search pointer (ADTT_SRP) information 351c, various information such as the number of parts of title (PTT: Part_of_Title) (PTT_Ns) and the head address (HDVTS_SA) of the corresponding HDVTS are indicated. To be recorded.

  In the information storage medium (content type 2 disc) having the structure shown in FIGS. 79 to 82, the title playback type (TT_PB_TY), the number of angles (AGL_Ns), and the title parental ID fields (content type 2 disc) ( TT_PTL_ID_FLD) information, HDVTS number (HDVTSN), and HDVTS title number (HDVTS_TTN) do not exist (or become a reserved area).

  Further, in one standard title search pointer (SDTT_SRP) information 351b, the title playback type (TT_PB_TY), the number of angles (AGL_Ns), the number of part of titles (PTT) (PTT_Ns) relating to the title indicated by the search pointer, The title parental ID field (TT_PTL_ID_FLD) information, HDVTS number (HDVTSN), HDVTS title number (HDVTS_TTN), and various information of the head address (HDVTS_SA) of the HDVTS are recorded.

  FIG. 83 is a diagram for explaining the relationship between the playback state of the advanced VTS and the playback state of the standard VTS. This figure shows an example of a state machine showing the transition of the playback control module of the content type 2 disc. The playback processing of the content type 2 disc (mixed type of advanced VTS and standard VTS) starts up information (STARTUP.XML) in which the interactive engine (INT_ENG) 200 is recorded in the markup / Script language recording area 21A from the initial state. Interpretation starts playback and shifts to the advanced VTS playback state.

  In the advanced VTS playback state, the interactive engine (INT_ENG) 200 generates character information, button images, and the like that make up the menu screen, and issues a video playback instruction command to the DVD video playback engine (DVD_ENG) 100. By combining the video output output from the playback engine (DVD_ENG) 100 by the AV renderer 203, menu screen playback is realized.

  In the Markup / Script language file that describes the menu page that is interpreted in the advanced VTS playback state, a script (Script) that defines the behavior of an event handler associated with an event such as a button click by the user is described. For example, the event handler associated with the button image indicating the main video playback of the movie video contains a command for shifting to the standard VTS playback state, and the user selects the button indicating the main video playback by operating the remote controller or the like. When executed, the interactive engine (INT_ENG) 200 executes a command to shift to the standard VTS playback state, and the state machine shifts to the standard VTS playback state executed by the DVD video playback engine (DVD_ENG) 100.

  In the standard VTS playback state, the DVD video playback engine (DVD_ENG) 100 performs a cell playback information table (C_PBIT), a program chain command table (PGC_CMDT), etc. in a program chain (PGC) stored in a PGC or the like in the standard VTS. The standard VTS playback control is performed in accordance with the description. In the standard VTS playback state, the interactive engine (INT_ENG) 200 is in a paused state, and the DVD video playback engine (DVD_ENG) 100 is not instructed to perform playback control.

  In the standard VTS program chain command table (PGC_CMDT) or the like, a command for transition to the advanced VTS playback state (such as “CallINTENG” in FIG. 43D) can be described. As a result, when the DVD video playback engine (DVD_ENG) 100 performs command interpretation processing at the end of a series of video playback processing in the standard VTS playback state, the command for transition to the advanced VTS playback state is executed, or DVD video When the playback engine 100 receives an event of a user command such as a menu call, the video playback control can be shifted to an advanced VTS playback state performed by the interactive engine (INT_ENG) 200.

  When the transition from the standard VTS playback state to the advanced VTS playback state is performed, the DVD video playback engine 100 uses the standard VTS immediately before the transition of the playback control occurs in order to realize a temporary calling process of the menu screen. Information such as a video playback position may be temporarily stored to prepare for resume playback processing from the interactive engine (INT_ENG) 200.

  Table A below shows a specific example of a command for shifting from the advanced VTS playback state to the standard VTS playback state in the Markup / Script language file interpreted by the interactive engine (INT_ENG) 200. Is good).

<Table A>
(Command name) (argument)
CallDVDENG_TT Title number
CallDVDENG_PTT Title number, chapter number
CallDVDENG_TM Title number, playback start time position
CallDVDENG_RSM No argument.

  In Table A, “CallDVDENG_TT” is a command for designating the title number of the standard VTS when shifting from the advanced VTS playback state to the standard VTS playback state. The DVD video playback engine (DVD_ENG) 100 reads a standard VTS including a designated title and starts playback from the beginning of the title.

  “CallDVDENG_PTT” is a command for designating the title number and chapter number (PTT number) of the standard VTS when shifting from the advanced VTS playback state to the standard VTS playback state. The DVD video playback engine (DVD_ENG) 100 reads a standard VTS including a specified title, and starts playback from the beginning of the specified chapter number (PTT number).

  “CallDVDENG_TM” is a command for designating the offset of the title number of the standard VTS and the playback start time from the beginning of the title video when the advanced VTS playback state shifts to the standard VTS playback state. The DVD video playback engine (DVD_ENG) 100 reads a standard VTS including a specified title and starts playback from the specified playback time position.

  “CallDVDENG_RSM” is a command for designating execution of the resume process when shifting from the advanced VTS playback state to the standard VTS playback state. When receiving this command, the DVD video playback engine (DVD_ENG) 100 resumes playback according to the playback position information temporarily stored when the previous standard VTS playback state shifts to the advanced VTS playback state. .

  FIG. 84 shows an example of argument definition of a command (CallINTENG command) for shifting from the standard VTS playback state to the advanced VTS playback state among the navigation commands interpreted by the DVD video playback engine (DVD_ENG). In the entire command bit string, a command code is stored in bits b63 to b48, and bits b15 to b0 are allocated to a reserved area for future expansion.

  Bits b47 to b32 are a 16-bit control parameter storage area. Markup interpreted by the interactive engine (INT_ENG) 200 after storing an arbitrary value in a specific playback position or event of the standard VTS interpreted by the DVD video playback engine (DVD_ENG) 100 and moving to the advanced VTS playback state. This is a data area that can be used for any purpose when creating video content, such as being used to assign any process within the description of the / Script language file. b31-b23 is an area for storing a cell number to start reproduction at the time of resume.

Bits b19-16 are areas for storing menu identifiers, and are used for designating the type of menu to be called, particularly when the menu is called when shifting from the standard VTS playback state to the advanced VTS playback state. The types of menu identifiers that can be called are
0010b → Title menu
0011b → Route menu
0100b → Sub picture menu
0101b → Audio menu
0110b → Angle menu
[0111b → Chapter menu, etc.], but may be used to express a more detailed difference in behavior by the above-described control parameter or a combination of a control parameter and a menu identifier.

  FIG. 85 is a flowchart for explaining a user command process switching algorithm. This flowchart exemplifies a process when a module in charge of the process is switched when a user command is generated. When playing a content type 2 disc (a mixed type of advanced VTS and standard VTS), if a user command event associated with a remote controller (not shown) or a button stamp on the front panel occurs, the user operation module displays the current playback state. (Step ST850), and the module for notifying the user event is switched. If the current state is the advanced VTS playback state (YES in step ST850), the interactive engine (INT_ENG) 200 is notified. If the current state is the standard VTS playback state (NO in step ST850), the DVD video playback engine (DVD_ENG) 100 is used. To process the user command.

  FIG. 86 is a diagram showing an example of domain transition of a content type 2 disc. In a typical content type 2 disc (a mixed type of advanced VTS and standard VTS), the VMG menu domain (VMGM_DOM) and the VTS menu domain (VTSM_DOM) are configured by XML files described in the advanced VTS and Markup / Script language, The title domain (TT_DOM) such as the main video is composed of standard VTS.

  Menu videos in the VMG menu domain and VTS menu domain are described in the “XML file” in addition to the text information and button images drawn according to the description of the “XML file for menu” described in the Markup / Script language. This can be realized by reproducing the video stored in the advanced VTS.

  The transition between the VMG menu domain and the VTS menu domain is realized by executing a hyperlink process between the XML files described in the XML file for each menu. At this time, the playback of the advanced VTS may be stopped in accordance with the page transition, and playback may be started from a new position, or playback may be continued as it is.

  The transition to the title domain (TT_DOM) from the VMG menu domain (VMGM_DOM), VTS menu domain (VTS_DOM), etc., is a command (for example, as listed in the table A described above) for starting playback of a standard VTS described in an XML file. CallDVDENG_xxx command) is executed, and DVD playback control is transferred to the DVD video playback engine 100.

  On the other hand, the transition from the title domain (TT_DOM) to the VMG menu domain (VMGM_DOM) defines a new command like the CallINTENG command described above, and stores this new command in the program chain command table (PGC_CMDT) in the standard VTS. It may be realized. Alternatively, the transition from the title domain (TT_DOM) to the VMG menu domain (VMGM_DOM) may occur when the argument of the CallSS command indicates VMGM_DOM. It is also possible to acquire an event in which a root menu button arranged on a remote controller or the like (not shown) is stamped, and to generate a transition from the title domain (TT_DOM) to the VMG menu domain (VMGM_DOM) by acquiring this event. .

  Similarly, the transition from the title domain to the VTS menu domain (VTSM_DOM) is realized by defining a new command like the CallINTENG command described above and storing this new command in the program chain command table (PGC_CMDT) in the standard VTS. Alternatively, this domain transfer may occur when the argument of the CallSS command indicates VTSM_DOM. It is also possible to acquire an event of pressing a title menu button arranged on a remote controller or the like, thereby causing a transition from the title domain to the VTS menu domain.

  FIG. 87 is a diagram for explaining a playback model (example 2) of a disc in which advanced VTS (AHDVTS) and standard VTS (HDVTS) are recorded together. A reproduction example of a typical content type 2 disc (a mixed type of advanced VTS and standard VTS) will be described with reference to FIG.

  When playback of a content type 2 disc (a mixture of advanced VTS and standard VTS) starts, the interactive engine (INT_ENG) 200 plays back a menu screen described in the Markup / Script language stored in the advanced content recording area. Analyzes the menu page XML file.

  For example, when configuring a menu screen that prompts the user to select a button while repeatedly reproducing an impressive scene in a movie image, the menu page XML file includes an advanced VTS in the DVD video playback engine (DVD_ENG) 100. Control processing for repeatedly playing back video data is described in Markup / Script. The interactive engine (INT_ENG) 200 issues a playback command to the DVD video playback engine (DVD_ENG) 100 according to the description (arrow a).

  At the same time, the menu page XML file uses the button image stored in the animation / still image recording area in the advanced content recording area 21 and the font data stored in the font recording area to configure the menu screen. A description is stored. The interactive engine (INT_ENG) 200 synthesizes the output composed of the screen according to these descriptions and the video output of the advanced VTS by the above-described DVD video playback engine (DVD_ENG) 100 by the AV renderer 203 to realize the playback of the menu screen. To do.

  Next, the user uses a remote controller or the like to select a button for executing playback of the main video from the menu selection buttons arranged on the screen. In the menu page XML file, script processing associated with button selection is described, and a jump to the DVD playback engine control page occurs (arrow b).

  In the DVD playback engine control page, a CallDVDENG_TT command having a title number indicating the head of the main video as an argument is described. When this command is executed by the interactive engine (INT_ENG) 200, a transition from the advanced VTS playback state to the standard VTS playback state occurs (arrow c).

  After shifting to the standard VTS playback state, the DVD video playback engine (DVD_ENG) 100 plays back the standard VTS in which the main video is stored. Depending on the video content, it is possible to generate a playback position jump process to a different VTS according to the description of the playback control command stored in the VTS (arrow d). In the figure, a broken-line arrow marked with a diagonal line indicates that a jump by a navigation command cannot be performed in the advanced VTS. On the other hand, in the standard VTS, jumping by a navigation command is possible (arrows d ', d ", etc.).

  When the main video playback process ends, the “Call INTENG command” described in the program chain command table in the program chain (PGC) is executed, and a transition from the standard VTS playback state to the advanced VTS playback state occurs (arrow e). ).

  The interactive engine (INT_ENG) 200 performs processing on the menu page XML file in order to perform menu screen playback again in accordance with the Script description described in the handler of the CallINTENG command generation event in the DVD video playback engine control page XML file. The XML file is jumped (arrow f).

  FIG. 88 shows a relationship between an advanced VTS / standard VTS and a video object (also called EVOB or VOB) in a content type 2 disc in which the advanced VTS and the standard VTS are mixed. In this figure, there are two standard VTSs that constitute an advanced VTS that constitutes a menu and a title (main video), and each VTS refers to a different video object. This is an example where the video for configuring the menu and the video for configuring the title are completely different. When configured as shown in FIG. 88, for example, as described above, when “a menu screen that prompts the user to select a button while repeatedly reproducing an impressive scene in a video” is configured, the main video and the menu video are displayed. Despite being the same, two video objects must be prepared. When it is desired to avoid such “two video objects” overlapping preparation, a “object shared reference model” as shown in FIG. 89 may be referred to.

  FIG. 89 is a diagram for explaining a shared reference model for objects in a disc on which an advanced VTS (AHDVTS) and a standard VTS (HDVTS) are recorded together. If a time map is provided on each of the advanced VTS side and the standard VTS side, as shown in this figure, the advanced VTS and the standard VTS can refer to the same video object, and an arbitrary scene in the main video can be selected. This section can be cut out and used as the background image of the menu screen. As a result, the content creator can reduce the process of producing two video objects (with respect to the object of the part to be shared and referenced) to one, and the necessary capacity of the information storage medium can be reduced by one. As a result, the image quality of the main video can be improved, and a new bonus video can be added.

  When a video object (VOB) shared by the advanced VTS and the standard VTS is played back as an advanced VTS, it is not necessary as a standard VTS during PCI / DSI as shown in FIGS. Information may be included. When reproducing as a standard VTS, reproduction is performed using these pieces of information. However, when reproducing as an advanced VTS, these pieces of information are skipped, that is, reproduction is ignored.

  FIG. 90 is a diagram illustrating a specific example of loading information included in advanced content. The loading information includes a file name and location, a file size, a content type, a reference start time, a reference end time, and the like. The file name and location describe the URL address and the file name when the target file exists on the server unit, and the directory and the file name on the disk when the target file exists on the disk. Describe. The file size describes the file size in bytes. The content type is described as a MIME type. The reference start time is the time at which this file is referenced from the Markup language, etc., and the playback end time is the time at which this file is referenced from the Markup language (i.e. The file can be deleted immediately).

  Basically, a file whose reference is started at time “0” is loaded into a buffer (such as 209 in FIG. 72 and FIG. 91) before starting playback (that is, before starting execution of the Markup language). Need to be. (“Preload”) Other data is stored in the file using the reference start time, reference end time, file size, and communication speed acquired by the playback device. Determine when to start loading. As a result, it is possible to minimize the waiting time of the user until the start of display of advanced content / reproduction of DVD video content.

  FIG. 91 shows the configuration of the buffer manager 204 and its periphery, and FIG. 92 shows the flow when loading data into the V buffer 209. First, when the interactive engine 200 is activated, a startup information file (STARTUP.XML) that is one of the advanced contents recorded on the information storage medium 1 of the disc unit is read (step ST10). Parser 210 analyzes this startup information (step ST12). The analyzed startup information is interpreted by the interpreter unit 205. The interpreter unit 205 operates according to the description of the startup information when an “preload end” event (trigger) occurs (for example, starts reading / execution of the Markup language file INDEX.XML indicating the initial screen configuration), An operation when a “load end” event (trigger) occurs (for example, execution of a user operation that has been prohibited until now) is registered (step ST14).

  The “user operation” can be controlled by the PGC user operation control (PGC_UOP_CTL) in the standard VTS, but the “user operation” can be controlled by the Markup language in the advanced VTS.

  Further, loading information (see FIG. 90) is read (step ST16). This loading information may be described in the above-mentioned startup file, recorded as a single file on the disk 1, or recorded as a single file on the server 500. However, when recorded on the disk 1 or the server 500, the recorded location and its file name are described in the startup file. In accordance with this description, the loading information is read into the interactive engine (ENAV engine) 200 and analyzed by the parser 210 (step ST18). The analyzed loading information is interpreted by the interpreter unit 205, and the buffer manager 204 loads the advanced content into the buffer 209 (step ST20).

  The loading information includes, for one file to be downloaded, the name and location of the file to be downloaded (location where the file exists), the file size of the file to be downloaded, the content type and MIME type of the file to be downloaded ( What kind of data the data is), reference start / end times (time when data is referred to), etc. are described for each file to be downloaded.

  In accordance with this description, the buffer manager 204 loads advanced content whose reference start time is 0 (that is, a file that needs to be stored in the buffer before the start of display of advanced content / reproduction of DVD video content) (step). ST22). At this time, the file to be loaded is loaded from the disk 1 or the server unit 500 in accordance with the order of description of the loading information. At this time, for example, as the advanced content of “preload”, the advanced content (INDEX.XML file and related files) constituting the first page is instructed by the loading information.

  When all the advanced contents to be “preloaded” are loaded into the buffer 209 (YES in step ST24), the buffer 209 sends a “preload end trigger” signal to the buffer manager 204 (step ST26). When the buffer manager 204 receives a “preload end trigger” signal from the buffer 209, it sends a “preload end trigger” signal to the interface handler 202. When the interface handler 202 receives the “preload end trigger” signal from the buffer manager 204, the interface handler 202 sends a “preload end event” signal to the interpreter unit 205 as an event.

  The interpreter unit 205 registers the operation when the “preload end event” occurs as described above, and executes the registered operation (step ST28). For example, as an operation, execution of reading INDEX.XML constituting the first page read into the buffer 209 is registered. Also, INDEX.XML instructs the start of DVD video content playback. As a result, the preloading of the advanced content ends (a “preload end event” occurs), and the display of the advanced content / reproduction of the DVD video content is started.

  Further, in order to advance the playback start time, it is possible to designate only the advanced content constituting the first page as the “preload” advanced content. However, in this case, since advanced content other than the first page is not stored in the buffer 209 at the start of reproduction, it is necessary to prohibit user operations such as fast-forwarding, skipping, and time search.

  While displaying the advanced content and playing the DVD video content, the buffer manager 204 continues to buffer the remaining advanced content (that is, after the start of display of the advanced content / start of playback of the DVD video content) according to the description of the loading information. The file stored in (1) is loaded (step ST30). At this time, the playback device uses information on the reference start time, reference end time, file size, and communication speed acquired by the playback device described in the loading information (for example, priority = reference start time−file size). / Use the value calculated at the communication speed) to determine the time and order to start loading all advanced content.

  For example, it is described that a “preload end trigger” is generated when loading of advanced content constituting the first page is completed, and a “load end trigger is generated when loading of advanced content constituting the second page is completed. Keep it.

  When the advanced content constituting the second page is loaded into the buffer 209 (Yes in step ST32), the buffer 209 sends a “load end trigger” signal to the buffer manager 204. When the buffer manager 204 receives a “load end trigger” signal from the buffer 209, it sends a “load end trigger” signal to the interface handler 202. When the interface handler 202 receives the “load end trigger” signal from the buffer manager 204 (step ST 34), the interface handler 202 sends a “load end event” signal to the interpreter unit 205 as an event.

  The interpreter unit 205 registers the operation when the “load end event” occurs as described above, and executes the registered operation (step ST36). For example, when user operations such as fast-forwarding, skipping, and time search described above are prohibited, an operation that permits the prohibited user operation is registered. That is, since all advanced contents are stored in the buffer 209, it is not necessary to limit user operations.

  FIG. 93 is a diagram for explaining a configuration of an advanced VTS (AHDVTS) having a plurality of PGCs exceptionally. The VTS_EVOBS of the advanced VTS in FIG. 93 includes one interleaved block. For example, as shown in FIG. 69, this interleaved block is used to realize reproduction of the director's cut version and the theater release version. In many cases, these VTS_EVOBS have different playback time lengths than EVOBs in an interleaved block. In the case of such an advanced VTS, information regarding each video reproduction may be managed by a plurality of PGCs in the VTSI.

  The playback sequence is defined by a cell playback information table (C_PBIT, code 53 in FIG. 56) stored in the PGC. Then, according to the cell position information table (C_POSIT, reference numeral 54 in FIG. 56), the cell used for reproduction and the actual number are used by using the EVOB number (EVOB # 1 etc.) and the cell number (Cell # 1 to # 3 etc.) in VTS_EVOBS Associate cells. Furthermore, among the cells in the VTS_EVOBS, the cells configured by interleaved blocks are subdivided in units of interleaved units (ILVU), and are arranged in an interleaved block on the HD_DVD disc.

  In the example of FIG. 93, for example, PGC # 1, which is a director's cut version, is composed of interleaved blocks after reproducing a continuous block composed of EVOB # 1 in VTS_EVOBS. The cell playback information table is configured to play back EVOB # 3 and finally play back a continuous block composed of EVOB # 4. On the other hand, for example, PGC # 2, which is a theatrical release version, reproduces a continuous block composed of EVOB # 1 in VTS_EVOBS, and then converts EVOB # 2 composed of an interleaved block (Interleaved Block). The cell playback information table is configured to play back and finally play back a continuous block composed of EVOB # 4.

  As described above, when describing the playback sequence of the director's cut version or the theatrical release version, the playback time of each cell (EVOB) in the interleaved block section is often different. In such a case, the playback sequence is defined by dividing the PGC as in the example of FIG. By doing so, it becomes easier to manage access to the playback position in time units.

  FIG. 94 is a diagram for explaining a configuration of an advanced VTS (AHDVTS) including an interleaved block but having one PGC. This is an example convenient when the interleaved block forms an angle block, for example.

  In the example of FIG. 94, the playback sequence defined by PGC # 1 is composed of interleaved blocks after playing back a continuous block composed of EVOB # 1 in VTS_EVOBS. The cell playback information table is configured to play back EVOB # 2 and finally play back a continuous block made up of EVOB # 4.

  In this case, it appears that the sequence for reproducing EVOB # 3 constituting another angle is not defined. However, in fact, in the angle block, the EVOB, its cell, and the ILVU boundary forming each angle have the same playback time, and the multiplexed audio is the same, so the ILVU is used. It is configured so that angles can be switched seamlessly on a boundary basis. Accordingly, a parameter indicating the current playback angle is defined for switching the angle, and the angle can be switched based on this value.

  To summarize the above, when defining a playback sequence of an interleaved block that constitutes an angle block, the playback time is uniquely defined by the cell playback information table given by one PGC, and the parameter indicating the playback angle described above It becomes possible to specify the cell of VTS_EVOBS to be actually reproduced by combining with the above.

  Further, in the embodiment of the present invention, it is possible to more flexibly configure the reproduction of the same DVD content by using the reproduction control information described in the Markup / Script language stored in ADV_OBJ of FIG. It is. That is, by using the description of the above-described playback sequence information file (PBSEQ001.XML, etc. in FIG. 2), the VTS_EVOBS (independently of the PGC information recorded from the beginning of the disc 1 and the navigation information in the navigation pack) in the VTS_EVOBS It is possible to realize a function for freely configuring the playback order of stored DVD videos in a predetermined unit.

  FIG. 95 shows a description example of the playback sequence in the playback sequence information file. Assuming that the structure of FIG. 93 is newly defined by the description of the above-described playback sequence information file (PBSEQ001.XML, etc. of FIG. 2), the first line of the description of FIG. 95 is used to uniquely identify the playback sequence. “Directors_cut” is defined as the name, and it is defined that this reproduction sequence is described based on the information of the PGC of PGC number 1 of Title number 1.

  In the second to fourth lines in the description of FIG. 95, three chapters (PTT numbers) constituting the playback sequence of “directors_cut” are defined, and the name for uniquely identifying each is an attribute of “id” Defined. The playback order of chapters (PTT numbers) is defined by “order” attribute information, and the association of which chapter of PGC # 1 in FIG. 93 corresponds to each chapter is defined by the “pgc” attribute (this In the example, the playback order is described by three entries of chapter “order” = “1”, “2”, “3”).

  The definition of the playback sequence in the markup language description in the playback sequence information file as described above is as follows: “Advance VTS is defined as a material for a DVD video divided into chapters (PTT) and used on a menu screen. This is convenient for “redefinition according to the usage, such as a playback sequence used in main part playback and a playback sequence used in bonus content”. Since this playback sequence is written in the Markup language, it can be easily edited later. For example, when a movie content (divided into a plurality of chapters) once burned onto a DVD video disc is used as a material and a different playback sequence is defined later (for example, repeated playback and / or specification of a specific chapter) This also has an advantage in applications such as switching of the playback order of multiple chapters including chapter playback skip.

  FIG. 96 is an example in which the same playback sequence as the playback sequence of FIG. 95 is described in units of cells for the advanced VTS of FIG. When each chapter (PTT number) shown in FIG. 95 corresponds to one cell, it is composed of the same three entries (chapter “order” = “1”, “2”, “3”).

  FIG. 97 shows an example of a playback sequence for expressing a playback sequence that spans multiple PGCs. For example, in FIG. 97, different portions of the director's cut version video and the theater version video, which are composed of interleaved blocks, are continuously played back. Such a configuration is effective when creating content that explains the difference between the director's cut version and the theatrical version, such as DVD bonus content.

  As a difference between the markup languages describing the playback sequence, in the example shown in FIG. 95 and FIG. 96, the PGC number for uniquely specifying the chapter (PTT number) and the cell number is described in the first line. On the other hand, in FIG. 97, the PGC number is included in the markup description indicating the chapter number. As a result, it is possible to configure one reproduction sequence across a plurality of PGCs (in this example, across PGC # 1 and PGC # 2).

  FIG. 98 is an example in which the same playback sequence as the playback sequence of FIG. 97 is described in units of cells for the advanced VTS of FIG. PTT = 3 (PTT # 3) with PGC number = 2 (PGC # 2) is composed of two cells (corresponding to cells # 1 and # 2 of EVOB # 2 in the example of FIG. 93), and is the same. There are two cell entries to represent the playback sequence (in the example of FIG. 98, “cell” = “4” in chapter “order” = “3” and “cell” = in chapter “order” = “4” = It corresponds to “5”).

  The description method in the above playback sequence information file (PBSEQ001.XML, etc. in FIG. 2) can be defined flexibly. By using a definition different from the above example, a more complicated and detailed playback sequence can be defined. You can also describe it. By defining the playback sequence as exemplified above, the playback flow of the advanced VTS stored on the DVD disk can be flexibly changed (after the disk is distributed). For example, once a movie company sells a DVD disc, a new way to enjoy DVD video is devised, a new playback sequence is distributed via the Internet, and the user enjoys playback of the DVD video in the new playback sequence accordingly. Can be used.

  Similarly, it is also possible to provide a usage where the user edits an arbitrary playback sequence by himself and enjoys video playback by connecting favorite scenes (in this case, information on the user editing the playback sequence by himself) (For example, it can be stored in the persistent storage 216 of FIG. 72 or FIG. 100).

  99, prior to playback of the advanced VTS, the playback sequence information file (PBSEQ001.XML, etc. of FIG. 2) is used to initialize the playback sequence of the advanced VTS in the DVD playback engine 100 of FIG. 72 or 100, for example. FIG. 7 is a flowchart showing an example of a processing procedure for converting to a different playback sequence described in the playback sequence information file (for example, a setting based on a default playback sequence is reset to another playback sequence).

  When the playback of the advanced VTS is started, the interactive engine 200 initializes the DVD video player (defines the playback sequence of the object to be played back), for example, according to a predetermined procedure described in the startup information recording area 210A of FIG. To start.

  In the condition determination unit in step ST100, when an instruction to set an advanced VTS playback sequence based on playback sequence information is described in the described initialization procedure (YES in step ST100), the interactive engine 200 generates playback sequence information ( For example, the description of PBSEQ001.XML in FIG. 2) is registered in the DVD playback engine 100 (step ST102). DVD playback engine 100 resets the playback sequence of the advanced VTS according to the playback sequence information registered from interactive engine 200 in step ST102 (step ST104).

  When the command for setting the playback sequence of the advanced VTS based on the playback sequence information is not described in the condition determining unit in step ST100 (No in step ST100), the DVD playback engine 100 uses the program chain information (PGCI) recorded in the advanced VTS. The playback sequence is determined according to the cell playback information (C_PBIT) (step ST106).

  The DVD playback engine 100 controls playback of the advanced VTS according to the playback sequence set by the cell playback information (C_PBIT) in step ST106, or based on the playback sequence set by the description of the playback sequence information file in step ST104. Then, the playback of the advanced VTS is controlled according to the playback command from the interactive engine 200 (step ST108). Thereafter, playback using all advanced VTSs is executed, and then the playback process is terminated.

  In other words, FIG. 99 performs the following processing. That is, it is checked whether there is a playback sequence definition based on playback sequence information (playback sequence information acquired from the Internet or the like if not stored in the playback sequence information recording area) (ST100), and the playback sequence definition based on the playback sequence information is checked. If there is no (NO in ST100), the extended video object (EVOB) is played back (ST106) using the management information (PGCI) in the management area (ST108), and the playback sequence is defined by the playback sequence information (description in markup language) If there is (ST100 YES; playback sequence is initialized), the extended video object is played back based on the playback sequence information (ST102 to ST104) (ST108).

  Alternatively, the processing of FIG. 99 checks whether or not a playback sequence is defined by playback sequence information (ST100). If there is a playback sequence defined by playback sequence information (ST100 YES; playback sequence is initialized), playback is performed. The extended video object is played back by at least one of the sequence of the program chain number defined by the sequence information, the sequence of the cell number, and the sequence of the chapter number (ST102 to ST104). (ST108).

  FIG. 100 is a system configuration diagram illustrating an example of the internal structure of another embodiment realized by a playback device (advanced VTS-compatible DVD video player: another example of the device of FIG. 72) according to another embodiment of the present invention. It is. This DVD video player is based on the information recording medium 1 shown in FIGS. 1, 50, 73, 74, 79 (recording VTSI and VTS_EVOBS as exemplified in FIGS. 93, 94, etc.). The recorded contents (DVD video content and / or advanced content) are reproduced and processed, and advanced content is captured from a communication line such as the Internet / home network.

  In the system configuration of one embodiment shown in FIG. 100, the interactive engine 200 includes a parser unit 210, an advanced object management unit 610, a data cache 620, a streaming management unit 710, an event handler 630, and a system clock 214. , An interpreter unit 205 including a layout engine, a style engine, a script engine, and a timing engine, a media decoder unit 205 including a moving image / animation, still image, text / font, and sound decoder unit, and a graphics superimposing unit 750. A secondary video / streaming playback control unit 720, a video decoder 730, an audio decoder 740, and the like.

  On the other hand, the video playback engine 100 includes a DVD playback control unit 102, a DVD decoder unit 101 including an audio decoder, a main video decoder, a sub video decoder, and the like.

  The DVD video player includes, as functional modules provided to the interactive engine 200 and the DVD playback engine 100, a persistent storage 216, a DVD disk 1, a file system 600, a network management unit 212, a separation unit 700, a video mixer 760, an audio mixer 770, and the like. Is provided. In addition, as a module for the interactive video engine 200 to acquire information and control operations mainly through the system manager 800 with the functions of the DVD video player, NIC, disk drive controller, memory controller, FLASH memory controller, remote controller, keyboard, timer, cursor Etc.

  Examples of the recording location and recording format of advanced content other than the DVD video data handled by the interactive engine 200 include the following (the disc described here as a DVD disc is not only a normal DVD video disc but also the next generation) HD_DVD discs are also included).

1. ... as data in file format on a DVD disc 2. As divided data multiplexed in EVOB on DVD disc. ... as file format data in the persistent storage of the DVD video player. ... as file format data or streaming data on a network server on the Internet / home network.

  The “1.” “file format data on the DVD disc” corresponds to the case where it is stored in the advanced content recording area 21 shown in FIG. The interactive engine 200 reads an advanced content file on a DVD disc via a file system.

  In “2.”, “divided data multiplexed in EVOB on DVD disc” is multiplexed and recorded in VTS_EVOBS recorded in the advanced HD video title set recording area (AHDVTS) indicated by 50 in FIG. Data format. In the multiplexed data, data that is generally duplicated with “1.” “file format data on the DVD disc” is recorded, and is read into the separation unit 700 along with the reading of VTS_EVOBS, and the advanced content If it is divided data, it is sent to the advanced object management unit 610.

  The advanced object management unit 610 temporarily stores the divided data of the advanced content received from the separation unit 700 and stores it in the data cache 620 as the file format data of the advanced content at the timing when data that can be configured as one file is sent. To do.

  The advanced content data multiplexed in the EVOB on the DVD disc is file data obtained by compressing one or a plurality of advanced content files in accordance with a predetermined method for the purpose of data efficiency when multiplexing. May be stored separately. In this case, the advanced object management unit 610 temporarily stores the divided data until the compressed data can be decompressed, and stores the decompressed advanced content data in the data cache 620 at a timing when it can be handled as a file format. .

  “3.” “file format data in the persistent storage 216 provided in the DVD video player” is, for example, in the process of playing back a DVD title including advanced content created by a movie company with the interactive engine 200. For example, an introductory movie of a new movie downloaded from the Internet is stored at a predetermined position on the persistent storage 216.

  For example, when a DVD title including another advanced content created by the same movie company is played back, “The interactive engine 200 searches a predetermined location in the persistent storage 216 according to the description of the markup / script language of the advanced content. If an introductory movie or the like of a saved new movie is found there, it jumps to an XML page for referencing / reproducing it, and if reproduction processing is selected by a user operation, persistent storage 216 is selected. One example is a method of using “playing back an introduction movie of a new movie stored in”.

  Of the “file format data or streaming data on the network server on the Internet / home network” of “4.”, an example of the file format data is the introduction movie of the new movie described above. As an example of streaming data, “If the audio of the DVD video data of the movie on the DVD disc contains only Japanese and English, a new audio data in Chinese will be created by the movie company, and In the case of a connected DVD video player, the audio data in Chinese is downloaded and played back in synchronization with the video data on the DVD disc.

  In the system configuration diagram of FIG. 100, a file system 600, a parser unit 210, an interpreter unit 205, a media decoder unit 208, a data cache 620, a network management unit 212, a streaming control unit 710, a graphics overlay unit 750, a secondary video. / Streaming playback control unit 720, video decoder 730, audio decoder 740, separation unit 700, DVD playback control unit 102, DVD decoder unit 101, etc. are microcomputers that interpret the embedded program (firmware) (not shown) and realize each module function And / or by hardware logic. A work area (including a temporary buffer used for decoding processing) used when executing this firmware can be obtained by using a semiconductor memory (and a hard disk device if necessary) of each module. Further, each module has a communication means for control signals (not shown) for data supply and synchronization processing, so that necessary operation control between modules can be managed. The communication means includes signal lines by hardware logic, event / data notification processing between software, and the like.

  Hereinafter, the behavior for each function of the DVD video player will be described with reference to the system configuration diagram of FIG. DVD video players that play advanced content use XML files and style sheets written in Markup / Script language, etc., to achieve highly expressive menus and more interactive playback controls that were difficult with conventional DVDs To do. For example, consider an example of configuring a menu page that includes button selections that produce animation effects and sound effects upon selection by the user.

  The structure and function of the menu page is described using the Markup / Script language and defined by the menu XML page. The menu XML page is stored on the DVD disk, and the interpreter unit 205 interprets the contents of the menu XML page interpreted by the parser unit 210 according to the description contents, such as a layout engine, a style engine, a script engine, a timing engine, and the like. To hand over.

  The timing engine receives time events from the system clock 214 at predetermined intervals, and issues processing instructions to the layout engine, style engine, and script engine based on the description of the menu XML page arranged in the timing engine. . Each engine refers to the configuration information of the menu XML page managed by each engine, and issues a decoding processing instruction to the media decoder 208 as necessary.

  The media decoder 208 reads media data from a storage area of an advanced object such as the data cache 620 according to an instruction from the interpreter unit 205, and performs a decoding process.

  Out of the data decoded by the media decoder 208, the output results of moving images / animations, still images, texts / fonts related to graphics display are sent to the graphics superimposing unit 750, and the layout and style sheet of the interpreter unit 205 are output. The graphics plane frame data to be output is created according to the description and sent to the video mixer 760.

  The video mixer 760 outputs the output frame of the graphics superimposing unit 750, the output frame of the video decoder output according to the instruction of the secondary video / streaming playback control unit 720, and the DVD decoder 101 output according to the instruction of the DVD playback control unit 102. The output frames of the main video decoder and sub-video decoder, and the cursor function output frame mounted on the DVD video player are superposed according to a predetermined superposition rule and converted into a TV output signal while synchronizing the output frames. And output to the video output signal line.

  The behavior of the secondary video / streaming playback control unit 720 output in synchronization with the output frame of the graphics frame will be described. As the main storage destination of the secondary video data, a DVD disk and a streaming server on the Internet or a home network are assumed.

  In reproducing secondary video data stored on a DVD disk, first, IFO / VOBS (including EVOBS) data is read into the separation unit 700 from the DVD disk. The separation unit 700 identifies various multiplexed data, the data related to the main video playback control to the DVD playback control unit 102, the DVD video main video, sub-video, and audio data to the DVD decoder unit 101. Data related to secondary video playback control is divided and sent to the secondary video / streaming playback control unit 720. If the advanced object data is multiplexed and stored here, the data is sent to the advanced object management unit 610.

  The secondary video / streaming playback control unit 720 performs playback control of the secondary video on the DVD disk based on the playback control signal of the interpreter unit 205. For example, if the interpreter unit 205 instructs to not play the secondary video stored, all the data is discarded here. When reproduction is instructed, data shaped into a shape and data amount suitable for decoding processing is sent to the video decoder 730 and the audio decoder 740. The video decoder 730 and the audio decoder 740 perform decoding processing while synchronizing the output timing with the output of the DVD decoder 101 in accordance with the instruction of the secondary video / streaming playback control unit 720.

  Examples of the control signal instructed by the secondary video / streaming playback control unit 720 include the video position, the degree of scaling, the degree of transparency processing, the instruction for chroma color processing, and the like for the video decoder 730. For the decoder 740, volume control, channel synthesis instruction, and the like can be given.

  When the user instructs fast-forwarding, jumping, or the like with a remote controller or the like, the event handler 630 acquires an event of the remote controller and notifies the script engine of the interpreter unit 205. The script engine operates in accordance with the Markup / Script description of the XML file that controls playback, and checks whether there is an event handler for remote control processing. If an explicit behavior is defined in the XML file that performs playback control, the script engine performs a process according to the description, and if nothing is defined, performs a predetermined process.

  As a result of the user's remote control processing, when fast forward is to be executed, the interpreter unit 205 instructs the DVD playback control unit 102 and the secondary video / streaming playback control unit 720 to perform fast forward. The DVD playback control unit 102 reconfigures the VOBS data reading schedule in accordance with the fast-forward instruction from the interpreter unit 205 and changes the data reading process from the DVD disk of the separation unit 700. Thus, control is performed so that necessary data is supplied without underflow for fast-forward playback of the DVD playback control unit 102 and the DVD decoder unit 101. Since the data to be supplied to the secondary video / streaming playback control unit 720 is stored in accordance with the data arrangement of the main video, it is linked with the DVD playback control unit 102 performing data reading processing necessary for fast-forwarding. Accordingly, secondary video data suitable for fast-forward playback is supplied from the separation unit 700.

  Next, in the reproduction of streaming data by the secondary video / streaming reproduction control, the secondary video / streaming reproduction control unit 720 is located in a predetermined network server with respect to the streaming management unit 710 based on the reproduction control signal of the interpreter unit 205. The streaming data is read and instructed to be supplied to the secondary video / streaming playback control unit 720.

  The streaming management unit 710 requests the network management unit 212 to perform actual streaming data reception protocol control processing, and acquires data from the network server. At this time, when the bit rate of the streaming data is high, the streaming data is pre-read using the streaming buffer area on the data cache 620 previously set by the startup information, and the streaming data reception bit rate is changed. Control such as widening the allowable range can be performed.

  In this case, the streaming management unit 710 temporarily stores the streaming data from the network server in the streaming buffer on the data cache 620, and in response to the streaming data read request from the secondary video / streaming playback control unit 720, the data cache The data stored in the streaming buffer on 620 will be supplied. When the streaming buffer is not secured on the data cache 620, the streaming management unit 710 sequentially sends the streaming data acquired from the network server to the secondary video / streaming playback control unit 720.

  When the secondary video / streaming playback control unit 720 controls playback of streaming data on the network, it is not always necessary to play back in synchronization with video playback of the DVD playback engine 100. Therefore, even when the DVD playback engine 100 is not playing back video, the streaming data is played back, or the playback status of the DVD playback engine 100 (for example, special playback status such as fast-forward status or pause status) is set as the streaming data playback status. There is no need to match.

  In addition, when a reproduction process of streaming data read from a streaming server on the network is performed, there is a possibility that an underflow of data supply occurs. In this case, in the description of the markup / script language of the advanced content, priority processing can be instructed, and the playback processing of the DVD playback engine 100 can be prioritized and DVD video playback can be continued even if streaming data is interrupted, It is possible to flexibly define the behavior such as interrupting the playback of the DVD video when the streaming data is prioritized and the streaming data is interrupted. Further, the data reproduced by the secondary video / streaming reproduction control unit 720 may be only video data or only audio data.

Next, an example of the function of each module constituting the system configuration diagram of FIG. 100 will be described:
Persistent storage 216: Stores generated file data, file data downloaded from the Internet / home network, and the like in accordance with instructions from the interpreter unit 205. The data stored in the persistent storage 216 is retained even when the DVD video player is turned ON / OFF. The interpreter unit 205 can also erase data in the persistent storage 216.

  DVD disc 1: Stores advanced content and DVD video data. Sector data on the DVD disk is read in response to a read request from the file system or the separation unit.

  File system 600: manages a file system for each recording module / device, and provides a file access function for a file data read / write request from an advanced object management unit or the like. As an example of the file system for each recording module / device, when the persistent memory 216 is configured by a FLASH memory, the FLASH memory file system is used to control the memory rewriting to be averaged. The DVD disk 1 is accessed using a UDF or ISO9660 file system. For the files on the network, the network management unit 212 performs actual protocol control such as HTTP and TCP / IP, and the file system itself relays the file access function to the network management unit 212. The data cache 620 is managed as a RAM disk, for example.

  Network management unit 212: The network management unit 212 provides a file system with a function to read (write as necessary) file data provided on an HTTP server on the network. Responsible for the actual protocol control in response to the streaming data sequential read request from the streaming management unit 710, obtains the requested data from the streaming server on the network, and passes it to the streaming management unit 710.

  Separation unit 700: The separation unit 700 stores sector data in which IFO / VOBS data from the DVD playback control unit 102 or (secondary video / streaming playback control unit when only secondary video is played) is stored. According to the reading instruction, the data on the DVD disc is read. As for the read data, the multiplexed data is supplied to an appropriate processing unit. The IFO data is sent to the DVD playback control unit and the secondary video / streaming playback control unit 720. The main video / sub-video / audio data related to the DVD video stored in the VOBS is sent to the DVD decoder unit 101, and the control information (NV_PCK) is sent to the DVD playback control unit 102. Control information and video / audio data related to the secondary video are sent to the secondary video / streaming playback control unit 720. When advanced objects are multiplexed in the VOBS, these data are sent to the advanced object management unit 610.

  Parser unit 210: The parser unit 210 interprets the markup language described in the XML file and outputs the result to the interpreter unit 205.

  Advanced object management unit 610: The advanced object management unit 610 manages advanced object files handled by the interactive engine 200. When the advanced object management unit 610 receives an access request to the advanced object file from the parser unit 210, interpreter unit 205, media decoder unit 208, etc., the advanced object management unit 610 stores the file data of the data cache 620 managed by the advanced object management unit 610. Check the storage status. If the requested file data is stored in the data cache 620, the data is read from the data cache 620, and the file data is sent to the module that has made the read request. If there is no requested data in the data cache 620, the file data is read into the data cache 620 from a DVD disk, a network server on the Internet / home network, etc., where the corresponding data is stored, and at the same time, a read request is made. Send the file data to the module that performed it. Normally, the cache processing to the data cache 620 is not performed for the data stored in the persistent storage 216.

  As another main function of the advanced object management unit 610, when the advanced object data is multiplexed and stored in the VOBS data read by the separation unit 700, those data sent by the separation unit 700 are temporarily stored. And is stored in the data cache 620 at a timing when it can be stored as file data. If the advanced object file stored in the VOBS data is stored in a single file or a compressed format of multiple files, the divided data is temporarily stored until it can be expanded. After being expanded, it is stored in the data cache 620 as file data.

  The advanced object management unit 610 stores the advanced object data in the data cache 620, and in accordance with instructions from the interpreter unit 205 and predetermined rules, files that are no longer necessary for playback of the advanced content of the interactive engine 200 are transferred to the data cache in a timely manner. Delete from 620. By this deletion process, it is possible to effectively use a data cache area having a limited capacity according to the progress of playback of advanced content.

  Interpreter unit 205: The interpreter unit 205 is a module that controls the behavior of the entire interactive engine 200. The interpreter unit 205 performs initialization of the data cache 620 and initialization of the DVD playback control unit 102 in accordance with the startup information, loading information, and playback sequence information interpreted by the parser unit 210. In the advanced content playback process, layout information, style information, script information, and timing information interpreted by the parser unit 210 are delivered to each processing module, and the media decoder 208 and secondary video / streaming playback processing unit 720 are transferred according to the description. Then, a control signal is sent to the DVD playback control unit 102 and the like, and playback control between the modules is performed.

  Layout engine: The layout engine (one of the internal components of the interpreter unit 205) handles information about objects used for graphics output of advanced content. Here, definition and attribute information of objects such as moving images / animations, still images, text / fonts, sounds, and layout information on the screen are managed, and association information with style information related to decoration at the time of drawing is also managed.

Style engine: The style engine (one of the internal components of the interpreter unit 205) manages information related to detailed modification when drawing objects managed by the layout engine.

  Script engine: The script engine (one of the internal components of the interpreter unit 205) manages descriptions related to handler processing related to button press events from user interface devices (U / I devices) such as a remote controller and event notifications from the system manager. To do. The event handler 630 defines the processing contents when a corresponding event occurs, and the script engine follows the description, the graphics drawing object parameters, the DVD playback control unit 102, the secondary video / streaming playback control. The control of the unit 720 and the like is changed.

  Timing engine: The timing engine (one of the internal components of the interpreter unit 205) controls scheduled processing related to the behavior of graphics drawing objects and the reproduction of DVD video and secondary video / streaming data. The timing engine refers to the system clock 214, and when it coincides with the timing of the scheduled control processing, it controls each module to execute the advanced content reproduction processing.

  Media decoder 208: The media decoder 208 performs advanced object decoding processing in accordance with a control signal from the interpreter unit 205. Media handled by the media decoder 208 include cell animation that continuously reproduces still images such as PNG / JPEG as moving image data, vector animation that continuously draws vector graphics, and the like. Still image data can handle JPEG, PNG, GIF, and the like. For drawing text data, drawing of text data instructed by the interpreter unit 205 is mainly performed with reference to font data such as a vector font (open font). As the sound data, sound data such as PCM and MP3 having a relatively short reproduction time is assumed. Used mainly for sound effects associated with events such as button clicks. Among the decoding results of the media decoder 208, the graphics output is sent to the graphics superimposing unit 750. The sound output is output to the audio mixer 770.

  Graphics superposition unit 750: The graphics superposition unit 750 superimposes the output of the graphics drawing object output from the media decoder 208 in accordance with the description of the layout engine or style engine, and generates data of the output image frame. Many of the drawing objects have transparency processing information, and the transparency calculation processing is also performed by the graphics superimposing unit 750. The generated output image frame data is output to the video mixer 760.

  Data cache 620: The data cache 620 is mainly used for two purposes. One is a file cache for advanced object files, and temporarily stores advanced object files on a DVD disk or network. The other is used as a buffer for streaming data, and is managed by the streaming management unit 710. The distribution and size of the data cache used for the file cache and the streaming buffer may be described in startup information and managed for each advanced content, or may be used with a predetermined distribution.

  Streaming management unit 710: The streaming management unit 710 manages the supply of streaming data between the secondary video / streaming playback processing unit 720 and the network management unit 212. When the streaming data is relatively small and it is not necessary to use a streaming buffer, the network management unit 212 is controlled to sequentially supply the streaming data acquired from the streaming server to the secondary video / streaming playback control unit 720.

  When the bit rate of the streaming data is relatively high, the streaming data supply can be controlled by using the streaming buffer explicitly reserved by the creator of the advanced content. The streaming management unit 710 stores the data to be supplied to the secondary video / streaming playback control unit 720 in the streaming buffer secured in the data cache 620 according to the streaming buffer size and the prefetch size instruction interpreted by the interpreter unit 205. . When the prefetch size instructed in the streaming buffer is stored, the streaming management unit 710 starts supplying streaming data to the secondary video / streaming playback control unit 720. At the same time, as soon as a certain size of free space is secured in the streaming buffer, the streaming buffer is efficiently operated by issuing a data acquisition request to the streaming server.

  Secondary video / streaming playback control unit 720: The secondary video / streaming control unit 720 controls playback of streaming data supplied from the streaming management unit 710 and secondary video data supplied from the separation unit 700 from the interpreter unit 205. Playback control is performed according to the signal.

  Video decoder 730: The video decoder 730 reproduces the video data supplied from the secondary video / streaming playback control unit 720 according to the control signal from the secondary video / streaming playback control unit 720. When the video data is the secondary video data supplied from the separation unit 700 or when the streaming data is instructed to synchronize with the DVD video reproduction, the output timing of the DVD decoder 101 and the output timing of the video decoder 730 are synchronized. The video is decoded and output to the video mixer 760.

  A characteristic function of the video decoder 730 is a chroma color processing function for video data. This manages a chroma color area designated by a specific color or a plurality of colors as a transmission area, and constitutes output frame data of the video mixer 760.

  Audio decoder 740: The audio decoder 740 reproduces the audio data supplied from the secondary video / streaming playback control unit 720 according to the control signal from the secondary video / streaming playback control unit 720. When the audio data is secondary video audio data supplied from the separation unit 700, or when the streaming data is instructed to be synchronized with DVD video reproduction, the output timing of the DVD decoder 101 and the output timing of the audio decoder 740 Are decoded and output to the audio mixer 770.

  DVD playback control unit 102: The DVD playback control unit 102 acquires DVD video playback control data from the separation unit 700 based on the playback control signal from the interpreter unit 205, and the main video / sub-video / audio data of the DVD decoder 101. Perform playback control.

  DVD decoder unit 101: The DVD decoder unit 101 includes an audio decoder, a main video decoder, a sub video decoder, and the like, and performs decoding processing and output while synchronizing the outputs of the decoders in accordance with control signals from the DVD playback control unit 102. Manage the process.

  Audio decoder: The audio decoder in the DVD decoder 101 decodes the audio data supplied from the separation unit 700 according to the control signal of the DVD reproduction control unit 102 and outputs the decoded audio data to the audio mixer 770.

  Main video decoder: The main video decoder in the DVD decoder 101 decodes the main video data supplied from the separation unit 700 according to the control signal of the DVD playback control unit 102 and outputs the decoded main video data to the video mixer 760.

  Sub-picture decoder: The sub-picture decoder in the DVD decoder 101 decodes the sub-picture data supplied from the separation unit 700 according to the control signal of the DVD playback control unit 102 and outputs it to the video mixer 760.

  Video mixer 760: The video mixer 760 receives output frames from the graphics superimposing unit 750, the video decoder 730, the main video decoder and the sub video decoder in the DVD decoder 101, and the cursor module, and performs a predetermined superposition rule. To generate an output frame and output a video output signal. In general, each frame data has transparency information at the whole frame data, object, and pixel level, and the video mixer 760 uses these transparency information to realize superposition of output frames from each module.

  Audio mixer 770: The audio mixer 770 receives audio data of the media decoder 208, the audio decoder 740, and the audio decoder in the DVD decoder 101, and generates and outputs an output audio signal according to a predetermined mixing rule.

  System manager 800: The system manager 800 can intervene an interface for status and control of each module mounted on the DVD video player. The interpreter unit 205 and the like can acquire the status of the DVD video player and change the behavior through an application interface (API) provided by the system manager.

  Network connection controller (NIC): NIC is a module for realizing a network connection function, and corresponds to an Ethernet controller (Ethernet is a registered trademark). The NIC provides information such as the network cable connection status via the system manager.

  Disc drive controller: The disc drive controller corresponds to a DVD disc reader. It provides status information such as the presence of a DVD disk on the disk tray and the type of disk.

  Memory controller: The memory controller manages system memory. An area used for the data cache 620 is provided, and access management of work memory used by each software (firmware) module is performed.

  Flash memory controller: The flash memory controller provides an area to be used for the persistent storage 216, and manages access to the FLASH memory in which the execution code of each software module (firmware) is stored.

  Remote controller: The remote controller performs remote control of the DVD video player, and generates a user button press event for the event handler 630.

  Keyboard: The keyboard performs keyboard control of the DVD video player, and generates an event for the event handler 630 of the user's keyboard.

  Timer: The timer supplies a system clock and provides a timer function used by the DVD playback engine.

  Cursor: The cursor generates a pointer screen such as a remote controller, and changes the position of the pointer image in accordance with the pressing of a direction key or the like.

  The interpreter unit 205 in FIG. 100 sends a playback control signal to the DVD playback control unit 102. By adding a new command to the playback control signal to the conventional DVD playback control command, more flexible playback control can be realized. That is, the above-described playback sequence information (for example, information stored in the playback sequence information recording area 215A in FIG. 50 corresponding to the PBSEQ001.XML file in FIG. 2, or playback sequence information imported from the outside via the Internet, etc., or a user In order to define the playback sequence information of the advanced VTS using the playback sequence information generated by the system firmware by freely rearranging the chapter icons and stored in the persistent storage 216, the interactive engine 200 To the DVD playback control engine 100 requires a command to be initialized with the playback sequence information.

  The “InitPBSEQ () command” is a command newly defined for the above purpose, and the interpreter unit 205 notifies the DVD playback control unit 102 of playback sequence information of the advanced VTS to be played back and initializes it. It is a command for. The argument of the “InitPBSEQ command” is given sequence information such as a PGC number and a PTT number as a base of the reproduction sequence (see FIGS. 95 to 98). The PGC number here specifies a PGC to be selected when a plurality of PGCs exist in the advanced VTS. The PTT number here can be defined as the order of chapters to be reproduced by referring to the PGC_PGMAP number in the PGC indicated by the PGC number. Since there is one advanced VTS on the DVD disc and there is one title in the advanced VTS, there is no need to designate them.

  As described above, the playback order can be described in units of cells. In this case, the argument of the “InitPBSEQ command” is array information of the PGC number and the cell number. The cell order can be defined by referring to the C_PBIT number in the PGC designated by the PGC number. When only one PGC exists in the advanced VTS, the argument of the PGC number of the “InitPBSEQ function” may not be used.

  When arranged, the apparatus of FIG. 100 includes the following elements. That is, a video playback engine (100) that plays back an extended video object (EVOB) from the information storage medium (disc 1); information different from the recorded content of the video data recording area from the information storage medium or an external server (for example, FIG. 21A to 21E) having an interactive engine (200) for acquiring advanced content and outputting AV output corresponding to at least one of the playback output of the video playback engine and the content of the advanced content according to the description of the markup language Composed. Here, the processing of the part “output AV output corresponding to at least one of the playback output of the video playback engine and the advanced content according to the description of the markup language” corresponds to ST102 to ST104 + ST108 or ST106 + ST108 of FIG. Can be made.

  FIG. 101 is a diagram illustrating a data structure of an advanced HD video title set program chain information table (AHDVTS_PGCIT) recorded in advanced HD video title set information (AHDVTSI). As shown in FIG. 55, the advanced HD video title set program chain information table (AHDVTS_PGCIT) 512 includes the number of AHDVTS_PGCI_SRP (AHDVTS_PGCI_SRP_Ns) and information on the end address of AHDVTS_PGCIT (AHDVTS_PGCIT_EA). Information of the information table (AHDVTS_PGCITI) 512a is recorded. In addition to this, the advanced HD video title set information (AHDVTSI) includes an AHDVTS_PGCI search pointer (AHDVTS_PGCI_SRP) 512b and program chain information PGC information (AHDVTS_PGCI) 512c, each of which is indicated by AHDVTS_PGCI_SRP_Ns. The The AHDVTS_PGCI search pointer (AHDVTS_PGCI_SRP) 512b includes information on the AHDVTS_PGC category (AHDVTS_PGC_CAT) indicating the type of AHDVTS_PGC and the start address (AHDVTS_PGCI_SA) of AHDVTS_PGCI. The contents of the AHDVTS_PGC category can be configured in the same manner as in FIG.

  FIG. 102 is a diagram showing an example of a plane configuration for superimposing output frames of modules in the video mixer 760 of FIG. In this example, a main video plane MVX output from the main video decoder of the DVD decoder 101 is arranged at the bottom of the superimposed planes. The main video plane MVX generally has no transmission information.

  A secondary video plane SVX is disposed on the main video plane MVX. The output of the secondary video plane SVX includes video data of streaming data (in this embodiment, the video decoding process of the secondary video and streaming data is exclusive, and is not decoded at the same time. To do). The secondary video plane SVX can have a transmission value of the entire plane as a superimposition process with the main video, and a chroma color process can be performed on a pixel area that does not transmit.

  This chroma color processing may be performed in the video decoder 730 and realized in a format including transmission information as output data of the video decoder 730. In this case, for example, the transmission information of the chroma color area is 0% (complete transmission), and the other areas are transmission values applied to the secondary video. Further, the chroma color processing may be performed by the video mixer unit 760. In this case, for example, output data from the video decoder 730 is image frame data including chroma color, chroma color information, and a transmission value for the secondary video plane. Information. The video mixer 760 makes the region designated by the chroma color from the given image frame completely transparent, and performs the other regions with the given transmission value.

  The sub video plane SPX arranged on the secondary video plane SVX is an output of the sub video decoder of the DVD decoder 101. In the sub-picture plane SPX, a transmission value can be applied to a sub-picture drawing object (text and highlight information).

  The graphics plane GRX arranged on the sub-picture plane SPX is an output frame of the graphics overlapping unit, and a transmission value at the pixel level is applied. In general, for advanced objects, the transparency value of the entire object is specified by Markup, and when the drawing object can describe the transparency value by itself like the PNG data at the pixel level, The transmission value obtained by multiplying the transmission value for the object becomes the transmission value at the pixel level of the object image. The graphics overlay unit 750 performs overlay processing and transparency processing of a plurality of drawing objects, and outputs the final pixel level color value and transparency value of the graphics plane GRX as output data to the video mixer 760.

  The cursor plane CUX arranged on the graphics plane GRX is a plane of a pointer image such as a remote control or a mouse, and generally uses a transmission value for the entire pointer image arranged at the top of the image plane.

  In the video mixer 760, the output image frame of each module is superimposed according to the overlay model defined as described above. The above definition is an example of a superposition rule in the video mixer 760, and a superposition order of different planes may be used, or transmission value processing may be applied.

  Next, with reference to FIGS. 103 to 107, another embodiment of the time map information (TMAPI) shown in FIGS. 58 to 61 (example without time entry) will be described. 103 and 104 show an example of a time map configuration for EVOB arranged in a continuous block. FIG. 103 shows an example 1 in which one TMAPI is stored in one TMAP file, and FIG. 104 shows an example 2 in which one or more TMAPIs are stored in one TMAP file. As shown in FIG. 103 and FIG. 104, one EVOB corresponds to one TMAPI and has a structure capable of performing time → address conversion from each TMAPI stored in the file to each EVOB. ing. Each TMAPI is configured to include one or more EVOBU entry information, and this information can be used to access each EVOBU in each EVOB.

  FIG. 105 shows an example of a time map configuration for EVOB that configures angles arranged in an interleaved block so that the angle can be seamlessly switched by the user. As shown in FIG. 105, one angle EVOB corresponds to one TMAPI, and from each TMAPI stored in the file to each EVOB as in the EVOB time map arranged in the continuous block. It has a structure capable of time-to-address conversion. Each TMAPI includes one or more EVOBU entry information and one or more ILVU entry information. By using this information, each ILVU head in each interleaved EVOB and each EVOBU in the ILVU are used. Can be accessed.

  In addition, since each EVOB arranged in the same interleaved block is configured to be stored in one file, all time map information necessary for reproducing the angle section can be acquired. There is no need to search for the necessary files one by one, and the processing efficiency is improved.

  106 and 107 show examples of data structures of time maps that do not include time entries. As shown in FIG. 106, the time map information (TMAPI) table includes TMAP information table information (TMAPITI) indicating the structure of the TMAPI stored in the file, and a TMAP information search pointer that gives a search pointer to each stored TMAPI. A group (TMAPI_SRPs) and a TMAP information group (TMAPIs) that stores EVOBU entry information of each TMAPI are configured.

  The time map information table information TMAPTI includes information indicating the number of TMAPIs stored in the TMAP file (TMAPI_Ns), and whether the EVOB block type stored in the TMAP file is a continuous block (= 0) or an interleaved block ( Block type information (TMAP_TYPE) indicating whether or not the angle type of EVOB stored in the TMAP file is no angle (= 0), non-seamless angle (= 1), or seamless angle (= 2) Angle type information (AGL_TYPE) indicating information, and information (TMAPIT_EA) indicating the end address of the table.

  Each time map information search pointer TMAPI_SRP includes information indicating the start address of the target TMAPI (TMAPI_SA), information indicating the identification number of the EVOB indicated by the target TMAPI (EVOB_IDN), and the start address of the EVOB indicated by the target TMAPI. Information (EVOB_ADR), EVOB playback time indicated by the target TMAPI, for example, information indicating the number of fields (EVOB_PB_TM), information indicating the number of EVOBU entry information stored in the target TMAPI (EVOBU_ENTI_Ns), and storage in the target TMAPI Information indicating the number of ILVU entry information (ILVU_ENTI_Ns: ILVU_ENTI_Ns = 0 if not an interleaved block), and EVOB of the target TMAPI Information indicating the angle number (AGLN: if if not angle block, AGLN = 0) configured to include a.

  As shown in FIG. 107, each time map information TMAPI includes an EVOBU_ENTI group and an ILVU_ENTI group. The EVOBU_ENTI group is composed of one or more pieces of EVOBU entry information (EVOBU_ENTI), and each EVOBU_ENTI is a size (EVOBU_SZ) indicated by the number of packs (EVOBU_SZ) of each EVOBU stored in the EVOB, for example, the number of fields. EVOBU_PB_TM) and the size of the first reference picture (1STREF_SZ) indicated by the number of packs, for example.

  The ILVU_ENTI group is composed of one or more ILVU entry information (ILVU_ENTI). Each ILVU_ENTI is the start address (ILVU_ADR) of each ILVU stored in the EVOB and the size of each ILVU indicated by the number of EVOBUs, for example. (ILVU_SZ).

  FIG. 108 shows a structure example different from the structure of the navigation pack (NV_PCK) shown in FIG. Similar to NV_PCK, the standard control information pack (GCI_PCK) arranged at the head of EVOBU uses the standard GCI_PCK shown in FIG. 5A in the EVOB in the standard VTS. This pack contains general control information (GCI) stored in the general control information packet (GCI_PKT), presentation control information (PCI) stored in the presentation control information packet (PCI_PKT), and data search information packet (DSI_PKT). Data search information (DSI) to be stored is included.

  Further, in EVOB in the advanced VTS, the advanced GCO_PCK shown in FIG. The pack includes general control information (GCI) stored in the general control information packet (GCI_PKT) and data search information (DSI) stored in the data search information packet (DSI_PKT).

  FIG. 109 exemplifies information stored in the general control information (GCI), and states of the stored EVOBU and information on the entire pack (GCI_GI), EVOBU, copy control information in the pack, and display control information Information (DCI_CCI_SS) indicating display ratio, display control information (DCI) indicating aspect ratio, copy control information (CCI) such as CGMS information and analog copy control information, and recording information (RECI) giving copyright information such as ISRC data It is comprised including.

  FIG. 110 shows another embodiment of the data structure of the advanced VTSI 51a. The advanced HD video title set information (AHDVTSI) area 51 shown in FIG. 51 (e) includes an advanced HD video title set information management table (AHDVTSI_MAT) that does not include attribute information such as video and audio as shown in FIG. ) 510a, Advanced HD video title set PTT search pointer table (AHDVTS_PTT_SRPT) 511a used for searching for the beginning of the part of title (PTT) corresponding to the chapter portion of the title, Advanced HD video title set giving the playback procedure of the title Program chain information table (AHDVTS_PGCIT) 512a, advanced HD video title set attribute information table (AHDV) giving attribute information of each EVOB S_ATRIT) 515a, and is divided in the advanced HD video title set expanded video object set information table (AHDVTS_EVOBIT) each of the 516a area (management information group) to give the information of each EVOB.

  FIG. 111 is a data structure example showing the contents of the advanced HD video title set attribute information table (AHDVTS_ATRIT). As shown in FIG. 111, AHDVTS_ATRIT 515a includes advanced HD video title set attribute information table information (AHDVTS_ATRITI), one or more advanced HD video title set attribute information search pointers (AHDVTS_ATRI_SRP), and one or more advanced HD video title set attributes. Information (AHDVTS_ATRI) is included.

  The advanced HD video title set attribute information table information (AHDVTS_ATRITI) includes (AHDVTS_ATRI_SRP_Ns) indicating the number of attribute information (AHDVTS_ATRI_SRP) stored in the table, and (AHDVTS_ATRIT_EA) indicating the end address of the table. Here, the advanced HD video title set attribute information search pointer (AHDVTS_ATRI_SRP) has (AHDVTS_ATRI_SA) indicating the start address of each attribute information. The advanced HD video title set attribute information (AHDVTS_ATRI) indicates attribute information for the corresponding EVOB.

  Specifically, in AHDVTS_ATRT, information (AHDVTS_V_ATR) indicating video attribute information such as MPEG-2, MPEG-4 AVC (H.264) and SMPTE VC-1 stored in EVOB, and audio stream Number of information (AHDVTS_AST_Ns) and the audio stream of DD +, DTS ++, MLP, LPCM, etc. (Dolby Digital DD, Digital Theater System DTS, Medilian Lossless Packing MLP are all registered trademarks) stored in EVOB Attribute information (AHDVTS_AST_ATR), multi-channel audio stream attribute information (AHDVTS_MU_AST_ATR), information indicating the number of sub-picture streams (AHDVTS_SPST_Ns), 2 bits / pixel SD size stored in EVOB, or 2 bits / Pixel Sub-picture stream attribute information (AHDVTS_SPST_ATR) indicating whether it is HD size or 8-bit / pixel SD / HD size, information (AHDVTS_SPST_SDPLT) indicating a color palette for sub-picture SD, and color for sub-picture HD It has information (AHDVTS_SPST_HDPLT) indicating a palette.

  FIG. 112 is a data structure example showing the contents of the advanced HD video title set EVOB information table (AHDVTS_EVOBIT). As shown in FIG. 112, VTS_EVOBIT 516a includes advanced HD video title set EVOB information table information (AHDVTS_EVOBITI), one or more advanced HD video title set EVOB information search pointers (AHDVTS_EVOBI_SRP), and one or more advanced HD video title sets EVOB. Information (AHDVTS_EVOBI) is included.

  The advanced HD video title set EVOB information table information (AHDVTS_EVOBITI) includes information (AHDVTS_EVOBI_SRP_Ns) indicating the number of EVOB information stored in the table (AHDVTS_EVOBI_SRP_Ns), and information indicating the end address of the table (AHDVTS_EVO). . Here, the advanced HD video title set EVOB information search pointer (AHDVTS_EVOBI_SRP) has information (AHDVTS_EVOBI_SA) indicating the start address of each EVOBI. Further, the advanced HD video title set EVOB information (AHDVTS_EVOBI) includes EVOB identification number information (EVOB_IDN) for identifying each EVOB, EVOB attribute information number information (EVOB_ATRN) indicating attributes corresponding to each EVOB, and And information (TMAP_FILE_NAME) indicating a time map file name in which time map information for accessing each EVOB is stored. Here, the number described in EVOB_ATRN is a number indicated by the advanced HD video title set attribute information search pointer (AHDVTS_ATRI_SRP #) in the advanced HD video title set attribute information table (AHDVTS_ATRIT).

  Next, another embodiment of the present invention will be described. The problem of this embodiment is to provide a method for reading out a Movie Object (hereinafter referred to as “Primary”) as a main subject of reproduction and an Advanced Object (hereinafter referred to as “Secondary”) that can be reproduced simultaneously with this Movie Object. There are two methods for solving this problem: a method of multiplexing Primary and Secondary as one program stream (PS) (Multiplex or MUX), and a method of multiplexing as Primary and Secondary 2PS. In the case of 2PS, there are a method of multiplexing in units of packs and a method of multiplexing in units of access units (AU) using the Angle format currently used in DVD-Video. .

  In FIG. 113, one program stream (1PS) in which a primary object (movie object) and a secondary object (advanced object) are multiplexed is recorded on a disc, and an advanced object (secondary object) is recorded on an external communication line (web). It is a figure which illustrates the case (case 1) which exists as an independent separate program stream.

  Case 1 may be a case where each Primary / Secondary is multiplexed (MUX) into 1 PS in pack units. At this time, as shown in FIG. 113, both the primary and secondary objects are managed by video title set information (VTSI: corresponding to the file in HVDVD_TS in FIG. 2, AHDVTSI in FIG. 52, etc.), and the information for secondary is advanced. It is managed by object information (AOBI: corresponding to the file in ADV_OBJ in FIG. 2). FIG. 114 shows a decoding model for this structure.

  FIG. 114 is a diagram for explaining the decoding model of case 1. FIG. The PS sent from the disc (corresponding to the disc 1 in FIGS. 1, 50, 51, 73, 74, 79, etc.) is sent to the first decoder for transmission to the primary and secondary decoders 114n to 114s. Demultiplexed by the multiplexer (DeMUX1) 114a and stored in the Input Buffers 114g to 114m. The Secondary Content sent from the Web is stored once in the Buffer 114f for reproduction in synchronization with the Disc, and then input to the Input Buffers 114k to 114m through the second demultiplexer (DeMUX2) 114b and the switches SW1 and SW2. Sent. By synthesizing (Mixing) the data decoded by the Decoders 114n to 114s, the Primary and Secondary Objects can be displayed simultaneously (synchronized).

  Next, a case where a total of 2 PS is used in the primary of one program stream (1 PS) and the secondary of 1 PS will be described. In FIG. 115, the PS of the primary object and the PS of the secondary object are recorded on the disc as two program streams multiplexed in pack units (PS-1 VOB and PS-2 VOB) and are recorded on the external communication line (Web). It is a figure which illustrates the case where Advanced Object (Secondary Object) exists as another independent PS (case 2-1). This case 2-1 is a structure diagram in which two objects are multiplexed (MUX) in units of Pack.

  FIG. 116 is a diagram for explaining the decoding model of case 2-1. The contents on the disc are divided into primary and secondary streams by the first demultiplexer (DeMUX1) 116a and sent to the corresponding decoders, respectively, so that the second demultiplexer (DeMUX2) 116b and the third demultiplexer (DeMUX3) 116c. Also, since the secondary content is sent from the network (Web), the DeMUX 3116c receives the content via the switch SW3 by selecting the content on the Web if there is content on the Web and the disc if not. Become.

  In FIG. 117, the PS of the primary object and the PS of the secondary object are recorded on the disc as two program streams multiplexed in units of access units (AU), and the advanced object (secondary) is recorded on the external communication line (Web). It is a figure which illustrates the case where (Object) exists as another independent PS (case 2-2). This case 2-2 is a case where the multiplex unit in 2PS is the AU unit. In this case, by configuring in the same manner as the ILVU used in the current DVD-Video, it is possible to display the recorded contents of the Primary and Secondary simultaneously (synchronously) in the form of displaying a plurality of Angles simultaneously.

  In case 2-2, the size of one access unit is larger than in case 2-1. (The pack unit of case 2-1 is as small as 2 kB, but there are a plurality of access units in case 2-2. A relatively large size that encompasses the pack). Therefore, after the object data is stored in the input buffer (for example, 116g in FIG. 116), the supply of the object data to the decoder starts, and then the input buffer data reading speed is the buffering data consumption speed (input buffer data reading). (Speed) may not be able to keep up. The countermeasures are described below.

  FIG. 118 is a diagram for explaining the decoding model of case 2-2. In this model, buffers 118d to 118f for stably supplying data to the second demultiplexer (DeMUX2) 118b and the third demultiplexer (DeMUX3) 118c are respectively provided after the first demultiplexer (DeMUX1) 118a. (The maximum amount of data to be buffered in these buffers, that is, the buffer size to be used can be determined based on a disk or web simulation that may be actually used. In particular, the buffer 118f for the web is If the data transfer from the external communication line is unstable and fluctuates, it should be a large size so that the buffering data will not be exhausted.)

  Next, a method of using stream_id to indicate which content is Primary or Secondary will be described. Each of the demultiplexers (DeMUX1 to 3) performs demultiplexing of the stream using this stream_id (and sub_stream_id as necessary). This Demultiplex is performed in order to send Data to InputBuffers 118g to 118m for inputting the demultiplexed data to the Decoders 118n to 118s.

  The stream_id and sub_stream_id are set in accordance with the method of defining secondary content identifiers (id) in private_stream1 in accordance with the current DVD-Video standard (see FIGS. 119 to 121), and a new private_stream3. There are two methods of establishing a new and having a secondary id (see FIGS. 122 to 125).

  FIG. 119 is a diagram for explaining an example of a stream_id that identifies the contents of the Primary Object and the contents of the Secondary Object (when private_stream1 is used for object identification). This stream_id specifies “110x0 *** b” that specifies the MPEG audio stream *** corresponding to the decoding audio stream number, “11100000b” that specifies the video stream, “10111101b” that specifies private_stream1, and private_stream2 “10111111b” and other (currently unused areas, etc.) are appropriately included.

  FIG. 120 is a diagram illustrating a configuration of sub_stream_id for private_stream1 in the stream_id of FIG. 119. This sub_stream_id is “001 ***** b” for specifying a sub-picture stream, “01001000b” for reservation, “011 ***** b” for extended subpicture, Dolby AC-3 (registered trademark) ”Designates a DTS (registered trademark) audio stream as an option“ 10001 *** b ”, optionally designates an SDDS (registered trademark) audio stream as“ 10010 *** b ” “10100 *** b” designating a linear PCM audio stream, “11111111b” designating a stream defined by a content provider, “10010001b” designating an MPEG2 video stream of Secondary Content, MPEG4 / AVC stream of Secondary Content “10010010b” for designating “10010011b” for designating the VC-1 stream of Secondary Content, “11000 *** b” for designating the Dolby Digital + (registered trademark) stream of Secondary Content, Seco “11001 *** b” to specify the DTSHD (registered trademark) stream of the secondary content, “11010 *** b” to specify the SDDS (registered trademark) audio stream of the secondary content, and the linear PCM audio stream of the secondary content “11100 *** b” and others (uses for future presentation data etc.) as appropriate.

  FIG. 121 is a diagram illustrating a configuration of sub_stream_id for private_stream2 in stream_id of FIG. 119. This sub_stream_id is “00000000b” for specifying a Presentation Control Information (PCI) stream, “00000001b” for specifying a Data Search Information (DSI) stream, “11111111b” for specifying a stream defined by the content provider, etc. (future (Use of navigation data etc.) as appropriate.

  FIG. 122 is a diagram for explaining another example of stream_id for identifying the contents of the Primary Object and the contents of the Secondary Object (when private_stream3 is newly provided for object identification). This stream_id specifies “110x0 *** b” that specifies the MPEG audio stream *** corresponding to the decoding audio stream number, “11100000b” that specifies the video stream, “10111101b” that specifies private_stream1, and private_stream2 “10111111b”, “10110000b” designating private_stream3, and the like (currently unused areas, etc.) are appropriately included.

  FIG. 123 is a diagram illustrating a configuration of sub_stream_id for private_stream1 in stream_id of FIG. This sub_stream_id is “001 ***** b” for specifying a sub-picture stream, “01001000b” for reservation, “011 ***** b” for extended subpicture, Dolby AC-3 (registered trademark) ”Designates a DTS (registered trademark) audio stream as an option“ 10001 *** b ”, optionally designates an SDDS (registered trademark) audio stream as“ 10010 *** b ” "10100 *** b" designating a linear PCM audio stream, "11111111b" designating a stream defined by a content provider, and others (uses for future presentation data, etc.) as appropriate. The sub_stream_id for private_stream1 in FIG. 123 is the content excluding the items related to “Secondary Content” from the sub_stream_id for private_stream1 in FIG.

  FIG. 124 is a diagram exemplifying a configuration of sub_stream_id for private_stream2 in stream_id of FIG. As in the case of FIG. 121, this sub_stream_id is “00000000b” for specifying a PCI stream, “00000001b” for specifying a DSI stream, “11111111b” for specifying a stream defined by the content provider, etc. (future navigation data, etc. Application) as appropriate.

  FIG. 125 is a diagram exemplifying a configuration of sub_stream_id for private_stream3 in stream_id of FIG. This sub_stream_id is “10010001b” that specifies the MPEG2 video stream of Secondary Content, “10010010b” that specifies the MPEG4 / AVC stream of Secondary Content, “10010011b” that specifies the VC-1 stream of Secondary Content, and Dolby Digital + of Secondary Content “11000 *** b” designating a (registered trademark) stream, “11001 *** b” designating a DTSHD (registered trademark) stream of Secondary Content, and “SDDS (registered trademark) audio stream of Secondary Content” designating “ 11010 *** b ”,“ 11100 *** b ”that specifies the secondary content linear PCM audio stream,“ 11111111b ”that specifies the stream defined by the content provider, etc. (use for future presentation data, etc.) as appropriate It consists of The sub_stream_id for private_stream3 in FIG. 125 has contents mainly related to “Secondary Content” in the sub_stream_id for private_stream1 in FIG.

  FIG. 126 is a flowchart for explaining an example of a processing procedure when a primary object and / or a secondary object is reproduced from a disc and / or an external communication line (Web). This figure exemplifies a procedure for reproducing Secondary Content (or Secondary / 2ndary Video Set) using a Markup document. That is, when there is no Markup document on Disc (corresponding to other information storage medium 1 in FIG. 50) (No in step ST202), the player (for example, a playback device configured as shown in FIG. 100) is a Standard VTS (ordinary DVD video). Playback is performed with the content or HDVTS # of FIG. 1 (step ST204).

  If a Markup document exists on the Disc (Yes in step ST202), the player determines whether a NET (Web) connection destination is described in the Markup document. If the connection destination is not described (NO in step ST206), it is confirmed whether or not the Secondary Video Set exists by the Markup document in the Disc (step ST208). When the Secondary Video Set does not exist (No in Step ST210), the Primary Video Set is played back (Step ST212).

  If a NET (Web) connection destination is described in the Markup document (Yes in step ST206), the connection state is confirmed. If the connection is not secured (NO in step ST214), the Markup document in the Disc is used (step ST208) as in the previous step (NO in step ST206), and the Primary Video Set is reproduced (step ST212). Secondary Video Set is played back (step ST224).

  When the NET connection is secured (Yes in step ST214), it is determined whether or not the Secondary Video Set is stored on the NET. Here, if the Secondary Video Set is not stored (NO in step ST216), it is determined whether a Markup document is stored on the NET. If neither the Secondary Video Set nor the Markup document exists on the NET (No in Step ST216 and Step ST218), the Secondary Video Set (Step ST224) or the Primary Video is used using the Markup document in the Disc (Step ST208). Playback of Set (step ST212) is performed.

  If only the Secondary Video Set exists on the NET (Yes in step ST216) and the Markup document does not exist on the NET (No in Step ST226), the Secondary Video Set is read (Step ST230), and the TMAP and VTSI Read the attribute information and the update information of the playback information (step ST232), add these to the current playback control information (navigation data), and play back the Secondary Video Set on the NET at the playback start timing of the Markup document on the Disc. Start (step ST234).

  On the other hand, if the Secondary Video Set does not exist on the NET (NO in step ST216) and only the Markup document exists on the NET (YES in step ST218), the markup document is updated (step ST220), and then the TMAP and Read the update information of the attribute information and playback information in VTSI (step ST222), add these to the current playback control information (navigation data), and change the secondary video set of the Disc according to the playback start timing of the updated Markup document. Playback is started (step ST224).

  At this time, since Secondary Video Set has not been updated, it is not necessary to update TMAP or the like. If both the Markup document and the Secondary Video Set exist (Yes in Step ST216 and Yes in Step ST226), the Markup document is updated (Step ST228), and necessary information is added (Step ST232). Play Secondary Video Set.

  With the processing in FIG. 126, the Secondary Video Set from Disc (step ST224) or the Secondary Video Set from NET (Web) (step ST234) can be appropriately reproduced. At that time, an indicator (not color-coded) is shown to the player so that the user can immediately know whether the Secondary Video Set acquired from the NET connection is being displayed or the Secondary Video Set is being played back based on the information in the Disc. LED, etc.) may be provided, or an on-screen display (OSD) may be displayed on the screen of the monitor TV from where the Secondary Video Set currently being reproduced is obtained.

  Here, whether the Secondary Video Set being reproduced is from Disc or NET is determined by the load attribute described in the Markup document (for example, <object load = in description example 3 in FIG. 132 described later). “Disc” data> or <object load = “net” data>).

  The process in FIG. 126 is focused on the secondary video set playback process, but it is of course possible to simultaneously play the primary video set from the disc in parallel with this process. At that time, it is possible to specify at what timing the Secondary Video Set (from Disc or NET) is to be played back with respect to the Primary Video Set being played back by the Markup document to be used (step ST208, ST220, or ST228). A description example of such a Markup document will be described later with reference to FIGS. 130 to 132.

FIG. 127 is a diagram for explaining a playback path of Primary Object / Primary Content (Primary Video Set) and Secondary Object / Secondary Content (Secondary Video Set) from Disc. In this example, the markup document recorded in Disc describes the secondary content playback time or the playback startable time by user operation. (This “playable start time by user operation” corresponds to a period in which Secondary Content is held in Buffers 114f, 116f, 118f, etc. of FIGS. 114, 116, and 118.)
In FIG. 127, VOB # 2 (Primary Content) and VOB # 3 (Secondary Content) are in ILVU units in interleaved block section T23 after VOB # 1 (Primary Content) recorded in continuous block section T01 of Disc. And VOB # 4 (Primary Content) is recorded in the subsequent continuous block section T04. At this time, assuming that VOB # 2 is Primary and VOB # 3 is Secondary, the playback start time and end time (or playback start possible period) of Secondary Content (VOB # 3) are set in the Markup document of Disc. Yes. The playback start time end time literally refers to the time when playback of VOB # 3 starts and ends. In addition, the playback startable period is a period during which secondary is stored in the buffer and playback can be started by a user operation. For example, if the section T23 in FIG. 127 is a reproducible period, VOB # 3 (Secondary Content) is VOB # 2 (Primary Content) at the timing defined in the TMAP of VOB # 3 anywhere during T23. (Simultaneous playback or synchronized playback).

  FIG. 128 is a diagram for explaining the playback paths of Primary Object / Primary Content (Primary Video Set) from Disc and Secondary Object / Secondary Content (Secondary Video Set) from an external communication line (NET / Web). In FIG. 128, VOB # 2 (Primary Content) and VOB # 3 (Secondary Content) are in ILVU units in interleaved block section T27 after VOB # 1 (Primary Content) recorded in Disc continuous block section T01. And VOB # 4 (Primary Content) is recorded in the subsequent continuous block section T04. However, in this example, it is not VOB # 3 (Secondary Content) from Disc that is played along with VOB # 2 (Primary Content) in section T27, but VOB # 7 (Secondary Content) from NET / Web. It has become.

The example of FIG. 128 is a case where a new VOB # 7 Secondary Video Set, a new Markup document, a VTSI file, and a TMAP file are acquired from the NET. There is no description of VOB # 3 in the new Markup document in this example, and this VOB # 3 is not displayed (even if recorded in Disc). Since the markup document and TMAP are updated when a new markup document is acquired from the NET, the playback period of VOB # 3 defined in FIG. 127 and the playback period of VOB # 7 in FIG. good. (That is, assuming T23 in FIG. 127 = T27 in FIG. 128, the playback period of VOB # 3 and the playback period of VOB # 7 can be arbitrarily set individually within the time range corresponding to section T27.)
FIG. 129 is a diagram illustrating a data structure of a time map information table including a time map type flag (TMAP_TYPE_FL). In this figure, the time map information search pointer 519b in the time map information table 519 described above with reference to FIG. 58 is added with a flag (TMAP_TYPE_FL) for determining whether the corresponding TMAP is primary or secondary. is there. As a result, when the player reads the TMAP from the Disc and develops it, the process of replacing the current TMAP of the player with the new TMAP becomes smooth.

  In the example of FIG. 129, TMAP_TYPE_FL is only “determining whether it is a primary one or a secondary one”, so it can be composed of one bit, but it can be extended to a plurality of bits. For example, when TMAP_TYPE_FL is composed of 2 bits, “00b” identifies the Primary Object TMAP from Disc, “01b” identifies the Secondary Object TMAP from Disc, and “10b” identifies the Secondary Object from NET / Web. It is possible to specify the TMAP for Object and specify the TMAP for Secondary Object from other than “11b”.

  130 to 132 are diagrams illustrating Markup description example 1 to description example 3, respectively. In these description examples, three types of objects are assumed. That is, the first type is Primary Content (for example, <object load = “disc” data = “main.mpg”> in FIG. 130), and the remaining two types are for Secondary. One of them is one that performs playback during the playback time defined by TMAP (for example, <object load = “disc” data = “sec.mpg”> in FIG. 131), and the other is during the playback time of TMAP. In addition, the reproduction is started at the timing of user operation (for example, <object load = “disc” data = “sec2.mpg”> in FIG. 132). These types can be identified by the data attribute of the object tag and the type tag. Further, the server tag (for example, <server url = “http: // dvdrom / dvd_ihd” /> in FIG. 130) indicates the connection destination of the NET connection, and an operation like the flowchart in FIG. 126 is assumed. When there is a markup document at the connection destination, the player replaces the markup document in the disc with the markup document at the NET connection destination and uses it for reproduction.

  In Markup description example 1 in FIG. 130, playback of Secondary Object from Disc during playback time “03:15” to “05:40” (TMAP of evobid = “2”) of EVOB # 2, which is Secondary Object Is to be done.

  Further, in Markup description example 2 in FIG. 131, playback time “03:15” to “05:40” (TMAP of evobid = “2”) of EVOB # 2 which is a secondary object (total 2 minutes 25 seconds) Secondary Object playback from the Disc starts, and during the playback time “04:43” to “07:08” (evobid = “2” TMAP) (total content of 2 minutes 25 seconds) Secondary Object playback from is started. Here, TMAP (<type = “sec_sp” />) of playback times “04:43” to “07:08” is an example in which the playback start timing is specified by a user operation.

Further, in Markup description example 3 in FIG. 132, Primary Object from Disc during playback time “00:00” to “07:10” (TMAP of evobid = “1”) of EVOB # 1, which is Primary Object. On the other hand, the description is rewritten by the Markup document acquired from the NET (<object load = “net” data = “sec2.mpg”>), and the playback times “02:55” to “03: During 58 ”(evobid =“ 3 ”TMAP), playback of the Secondary Object from the NET starts. (In this example, by acquiring a Markup document from NET, for example, <object load = “disc” data = “sec.mpg”> in FIG. 130 becomes <object load = “net” data = “sec2.mpg” in FIG. > Is rewritten.)
In FIG. 133, one program stream (PS) obtained by multiplexing Primary Object (Movie Object) and Secondary Object (Advanced Object) on Disc is recorded, and Advanced Object (Secondary Object) is recorded on the external communication line (NET / Web). ) Is a diagram showing another example of the case (case 1a) in which it exists as an independent separate program stream.

  In the example of FIG. 133, the Secondary Contents before being multiplexed to the Primary Contents are multiplexed in advance to the Secondary Object (Secondary EVOB), and the multiplexed Secondary EVOB is multiplexed to the Primary Contents to become 1PS. It can be seen that the 1PS model in FIG. 113 has been improved in that multistage processing is performed (when the Secondary is multiplexed into the Primary, the already multiplexed Secondary is completed).

  FIG. 134 shows one program stream (PS) in which a primary object (movie object) and a secondary object (advanced object) are multiplexed on a disc, and an advanced object (secondary object) on an external communication line (NET / Web). ) Is a diagram showing still another example of the case (case 1b) in which it exists as an independent separate program stream. FIG. 135 is a diagram for explaining the decoding model of case 1a, and FIG. 136 is a diagram for explaining an example of the operation of the smoothing buffer in the decoding model of case 1a.

  In the case of the Decoding Model in FIG. 114, the entire system operates as a model having the same bit rate. At this time, since the Primary bit rate is considered to be higher than the Secondary bit rate, FIG. 135 shows a decoding model assuming that the system bit rate is 30 Mbps, the Primary is 20 Mbps, and the Secondary is 10 Mbps. Since each of Input Buffers 114g to 114m in the previous stage of decoders 114n to 114s in FIG. 114 may temporarily input data at 30 Mbps of the system even if the average bit rate of Secondary is 10 Mbps, In order to avoid overflow, it was necessary to prepare a buffer of appropriate size. In such a situation, in order for the decoding model of FIG. 135 to operate without contradiction, it is necessary to limit the multiplexing of FIG. 133 or FIG. An example of the Pack structure of the Secondary Video Set when this restriction is provided will be described below.

  FIG. 136 is a diagram for explaining an example of the operation of the smoothing buffer in the decoding model of case 1a. The upper side of FIG. 136 illustrates the Pack structure that is input to the DeMUX1 30 Mbps model, and the lower side of the figure schematically illustrates the Pack structure that is downgraded to 10 Mbps. In the case of absorbing the difference from the 10 Mbps model in the smoothing buffer 135x of FIG. 135, it is necessary to provide at least 2 Pack or more as illustrated in FIG. This is because a buffer overflow occurs, so that the next pack cannot be made to flow before the lower stream in FIG. 136 is output from the smoothing buffer 135x.

  In addition, the system clock reference SCR and presentation time stamp PTS (decoding time stamp DTS) have an interval of (2 KB / 30 × 10 ^ 6 bps) × 3 Pack = 1.599 [ms] when 1 Pack is 2 KB. It will be necessary. The Pack of Primary Video Set can be multiplexed (MUXed) in this opened section, specifically, the SNG section of FIG. Further, the secondary pack may have an interval larger than that, and an interval of 3 packs or more may be provided as in S4 to S5 illustrated in FIG. 136, and the primary may be multiplexed.

  FIG. 137 is a diagram schematically illustrating data types and forms that can be recorded on a Disc used in an embodiment of the present invention. In this figure, “Advanced Navigation” indicates data related to playback control for playback of advanced HD video title sets and advanced content as shown in FIGS. 74 and 79, and is described in Markup / Script language or the like. Indicates the data file that was created.

  “Primary Video Set” indicates data of a main video stream of a DVD as typified by an advanced VTS. “Primary Video Set” shown in FIG. 137 includes IFO data for storing management information of the main video stream, time for each EVOB constituting the main video stream, offset information of the start position of VOBU, which is a unit of playback management, and the like. Are composed of TMAP data composed of the above data tables, EVOB composing one video sequence composing the main video stream, P-EVOBS (Primary EVOBS) composed of a plurality of EVOBs, and the like.

  “Secondary Video Set” is a video stream that is reproduced simultaneously with the main video and different from the main video. Unlike Multi Angle video, which was realized with conventional DVDs, Multi Angle video was played by selecting one of multiple videos, whereas “Secondary Video Set” Another point is that another video stream can be played at the same time as the video is played. S-EVOB (Secondary EVOB) represents the video stream itself of “Secondary Video Set”. In this embodiment, the “Secondary Video Set” is composed of simple video and audio data without the Multi Angle function or subtitle function that was included in the “Primary Video Set”. I will explain it. In this case, IFO information for finely managing playback sequence control and the like is not necessarily required, and TMAP information for specifying the position of a simple playback stream is prepared in association with each “S-EVOB”. The

  “Advanced Element” indicates playback data of HDD players other than “Primary Video Set” and “Secondary Video Set”. Specifically, there are still image data such as JPEG and PNG, audio data used for sound effects to be reproduced when a button is clicked, text data providing character information described by a text subtitle, font data used for rendering, and the like. That's it.

  In FIG. 137, data represented by “multiplexed data structure on disk” is data stored in continuous sectors on the disk, and includes “P-EVOBS”, “S-EVOB”, “ Advanced Element "etc. are arranged in an interleaved manner. This is because when “Secondary Video Set” is played back while “Primary Video Set” is being played back or when “Advanced Element” is stored in the data cache shown in FIG. This is a measure for avoiding a problem that the supply of “P-EVOBS” data of “Primary Video Set” by reading data is not in time.

  In the embodiment of the present invention, the “Multiplexed Data structure” is in a state where “S-EVOB”, “Advanced Element”, etc. are interleaved in the entire sector data constituting “P-EVOBS”. In the data structure of FIGS. 74 and 79, the “Multiplexed Data structure” is arranged at the position of the advanced HD video title set in the video data recording area. Similarly, the “Primary Video Set” IFO and TMAP are also stored at the position of the advanced HD video title set in the video data recording area.

  On the other hand, TMAP of “Secondary Video Set”, S-EVOB of “Secondary Video Set” not interleaved in “Multiplexed Data Structure”, and “Advanced Element” not interleaved in “Multiplexed Data Structure” are advanced It is stored in the content recording area.

  Furthermore, from the viewpoint of the file system as shown in FIG. 2, when viewing the data on these disks, each type of data interleaved in the “Multiplexed Data structure” can be distinguished from the file system. Cannot be done, it is treated as an advanced VTS “.EVO” file. The “Primary Video Set” IFO and TMAP can be accessed as the “.IFO” file and “.MAP” file of the advanced VTS, respectively.

  In addition, “Secondary Video Set” TMAP and S-EVOB data that are not interleaved in the “Multiplexed Data structure”, and “Advanced Element” data that is not interleaved in the “Multiplexed Data Structure” are handled as advanced content, and ADV_OBJ It can be accessed as file data in a directory.

  FIG. 138 is a diagram showing a playback system model of the HD_DVD player according to one embodiment of the present invention in a large unit of functional modules. “Data Source” indicates a data storage location that can be accessed when the HD_DVD player performs playback. “Data Source” may include “Disc”, “Persistent Storage”, “Network Server”, and the like. “Disc” corresponds to the DVD disk 1 of FIG.

  “Persistent Storage” corresponds to the persistent storage in FIG. 100, but NAS (Network Attached Storage) and the like existing on the home network are also included in the category of persistent storage. “Network Server” refers to a server existing on the Internet, and is generally assumed to be operated by a movie company that provides DVD disks.

  “Advanced Content Player” refers to the entire playback system model of the HD_DVD player, and includes “Data Access Manager”, “Data Cache”, “Navigation Manager”, “Presentation Engine”, “User Interface Controller” as large modules. , “AV Renderer”.

  “Data Access Manager” manages the exchange of data between a module in “Advanced Content Player” and “Data Source”. “Data Cache” is a data storage device that temporarily stores data required for reproduction by “Navigation Manager” and “Presentation Engine”.

  “Navigation Manager” reads and interprets “Advanced Navigation”, controls “Presentation Engine”, “AV Renderer”, etc., and manages playback control of the content type 2 or 3 disc. When the disc is inserted, the “Startup File” stored on the disc is read and the HD_DVD player necessary for playback control is set.

  The “Presentation Engine” uses the “Primary Video Set”, “Secondary Video Set” and “Advanced Element” data based on the control commands and signals issued by the “Navigation Manager” according to the playback control information of the “Advanced Navigation”. Using “Access Manger”, read from “Data Source”, read from “Data Cache”, play, and send the output to “AV Renderer”.

  “AV Renderer” performs alpha blending and mix control of video data and audio data output by “Presentation Engine” based on control commands and signals issued by “Navigation Manger” according to playback control information of “Advanced Navigation”. Then, a signal is output from the final HD_DVD player to an external TV monitor or speaker.

  “User Interface Controller” transmits an input signal from a user interface such as a front panel, a remote controller, or a mouse to the Navigation Manager as an event. Also controls the display of the mouse cursor.

  FIG. 139 is a detailed view of FIG. 138 from the viewpoint of data flow. In “Persistent Storage” and “Network Manager”, as a result of playback control of “Advanced Navigation”, all kinds of data can be stored as long as the data storage capacity permits, and can be read and written by HD_DVD players. is there. Generally, “Advanced Navigation”, “Advanced Element”, and “Secondary Video Set” mentioned above can be used as data read by “Advanced Content Player” and used for reproduction. “Primary Video Set” is stored only on Disc, not “Persistent Storage” or “Network Server”.

  The data stored in “Disc” can be “Advanced Navigation”, “Advanced Element”, “Primary Video Set”, and “Secondary Video Set” as shown in FIG. “Disc” is a read-only medium, and no data is written by the playback control of “Advanced Navigation”.

  “Data Access Manager” includes “Persistent Storage Manager”, “Network Manager”, and “Disc Manager”. In general, data access from “Persistent Storage”, “Network Server”, and “Disc” is managed respectively. However, regarding “NAS (Network Attached Storage)” included in “Persistent Storage”, “Persistent Storage Manager” is “ It may be considered that data access is managed using the function of “Network Manager”.

  A line from Disc Manager to Navigation Manager indicates a flow in which “Navigation Manager” reads “Startup File” included in “Advanced Navigation” after discriminating a predetermined disc type when a disc is inserted. The line from Disc Manager to Primary Video Player shows the data flow of Primary Video Set. The line from Disc Manager to Secondary Video Player shows the data flow of Secondary Video Set interleaved in the Multiplexed Data Structure on Disc.

  A line from Disc Manager to File Cache Manager shows the flow of data of Advanced Element interleaved in Multiplexed Data Structure on Disc. The line from Disc Manager to File Cache indicates the data flow of Advanced Navigation, Advanced Element, and Secondary Video Set that are not included in the Multiplexed Data Structure on Disc.

  The line from Persistent Storage or Network Server to File Cache shows the flow of Advanced Navigation, Advanced Element, and Secondary Video Set and vice versa. A line from Persistent Storage or Network Server to Streaming Buffer indicates the flow of Secondary Video Set.

  A line from File Cache to Navigation Manager indicates a flow in which Navigation Manager mainly reads Advanced Navigation. A line from the File Cache Manager to the File Cache indicates a flow of writing Advanced Element data sent from the Disc Manager to the File Cache in the File Cache in units of files. The line from File Cache to Advanced Element Presentation Engine shows the flow of Advanced Element. A line from the File Cache to the Secondary Video Player shows a data flow when reproducing the TMAP or S-EVOB of the Secondary Video Set once stored as file data in the File Cache.

  A line from the Streaming Buffer to the Secondary Video Player indicates a flow in which a large Secondary Video Set stored in the Persistent Storage or Network Server is once read into the Streaming Buffer and then supplied to the Secondary Video Player. This is a measure to absorb the fluctuation of the data reading speed and make it difficult to interrupt the playback of the Secondary Video Set when supplying data from a Data Source whose data reading speed is not constant like a network. is there.

  Dotted lines from Advanced Navigation to Presentation Engine and AV Renderer indicate control signals. In the case of lines to Presentation Engine, text subtitle data stored in Advanced Navigation data composed of Markup / Script is supplied. There may be cases.

  FIG. 140 is a more detailed view of FIG. 139 focusing on data supply from Disc. In FIG. 139, the data handling from the Disc in the Data Access Manager has been described as being handled only by the Disc Manager, but in FIG. 140, the Stream Dispatcher is further included.

  The Stream Dispatcher receives the Multiplexed Data Structure shown in FIG. 137 from the Disc Manager, and the P-EVOBS, S-EVOB, and Advanced Element data interleaved in the Multiplexed Data Structure, respectively, the Demux device in the Primary Video Player, It plays a role of supplying to Secondary Video Player's Secondary Video Playback Engine and File Cache Manager in Navigation Manager.

  When Disc is inserted into the player according to the embodiment of the present invention, Disc Manager supplies Startup File on Disc to Navigation Manager. The Advanced Navigation, Advanced Element, and Secondary Video Set files managed by the file system on the Disc are read into the File Cache according to the result of the Advanced Navigation Engine in the Navigation Manager interpreting the Startup File and Advanced Navigation.

  When the Primary Video Player reproduces the Primary Video Set, the IFO and TMAP data of the Primary Video Set are taken into the DVD Playback Engine from Disc Manager prior to the reproduction. Primary Video Player provides Navigation Manager with a high-level control API (Application Interface) for playing back Primary Video Set. Here, the higher-level control API is a level API such as Play, FF, STOP, and PAUSE. The DVD Playback Engine controls the detailed playback control processing of the Primary Video Set.

  The DVD Playback Engine performs playback control of the Primary Video Set according to a high-level control API from the Advanced Navigation Engine according to the description of “Advanced Navigation”.

  Demux de-multiplexes P-EVOB data, control pack (N_PCK) to DVD Playback Engine, video pack (V_PCK), sub-picture pack (SP_PCK), audio pack (A_PCK), Video Decoder, SP Supply to Decoder and Audio Decoder. Each decoder decodes the acquired PCK data in an appropriate unit.

  When Secondary Video Player plays Secondary Video Set with S-EVOB interleaved on Multiplexed Data Structure on Disc, prior to that playback, Disc Manager sends TMAP data of Secondary Video Set to Secondary Video Playback Engine. take in. The Secondary Video Set managed on the file system can be temporarily stored in the File Cache and then read and played by the Secondary Video Playback Engine.

  Secondary Video Player provides Navigation Manager with a high-level control API for playing Secondary Video Set, similar to Primary Video Player.

  The Secondary Video Playback Engine performs playback control of the Secondary Video Set according to a high-level control API from the Advanced Navigation Engine according to the description of “Advanced Navigation”.

  The Demux in the Secondary Video Player de-multiplexes the S-EVOB data, and supplies the video pack (V_PCK) to the Video Decoder and the audio pack (A_PCK) to the Audio Decoder.

  In this embodiment, the Secondary Video Set is shown as a model having only video and audio packs, but may be structured to include sub-pictures and control packs.

  The File Cache Manager acquires the pack of Advanced Element data output from the Stream Dispatcher, and after the pack data is supplied to the extent that it can be handled as one file data, it is written in the File Cache as one file belonging to the Advanced Element.

  When writing to the File Cache, for example, for large file data such as font data, the data is written to the File Cache before all the data that makes up the font file gathers in the File Cache Manager, and then the data is written sequentially. A simple font file may be configured on the File Cache.

  In addition, it is also possible to interleave after compressing Advanced Element stored in Multiplexed Data Structure. In this case, File Cache Manager performs decompression processing after fetching the compressed Advanced Element data in a size that can be decompressed. As a result, the generated Advanced Element file is written to the File Cache. The compressed Advanced Element data may be compressed for each single file, or an archive of a plurality of Advanced Element files may be compressed.

  The Advanced Element Presentation Engine reads Advanced Element data from the File Cache, and performs Advanced Element decoding processing according to control commands / signals from the Advanced Navigation Engine according to the description of Advanced Navigation.

  FIG. 141 is a more detailed view of FIG. 139 focusing on data supply from the Network Server and Persistent Storage. Devices that realize Persistent Storage can be classified into Fixed Storage and Additional Storage. Fixed Storage is a recording medium fixedly connected to the HD_DVD player, and generally corresponds to a FLASH memory or the like.

  Additional Storage is a recording medium that can be connected to and disconnected from an HD_DVD player, such as a memory card represented by an SD card, a memory device or HDD device via a connection interface such as a USB, or a NAS connected to a network. (Network Attached Storage) can be used.

  As with the supply model from Disc in FIG. 140, data such as Advanced Navigation, Advanced Element, and Secondary Video Set are supplied to File Cache via Network Manager and Persistent Storage Manager.

  When reproducing a Secondary Video Set having an S-EVOB that does not fit in the File Cache, the data is directly supplied directly to the Secondary Video Playback Engine for reproduction. At this time, the Secondary Video Playback Engine can perform playback while temporarily storing data in the Streaming Buffer according to the control described in Advanced Navigation. This is a measure for reducing the possibility of the secondary video set being interrupted when the data supply speed is not constant, such as in a network. In general, it is not necessary to use the Streaming Buffer for playback of the Secondary Video Set captured in the File Cache.

  FIG. 142 is a detailed view of FIG. 139, focusing on the flow of data storage in the persistent storage and the network server. The line from Advanced Navigation to Advanced Element indicates the flow of writing an Advanced Element such as a data file created by the Advanced Navigation Engine using the Script language or the like to the File Cache. In Advanced Navigation, for example, a script language description is used to create a file that records the number of times the Disc is viewed, and the file is stored in Persistent Storage. The data in the file is updated each time the video in the Disc is finished. The number of times can be displayed on the screen, or score data of a game created using the Script language can be created and sent to Network Server to compete for high scores. Data created by the Advanced Navigation Engine is temporarily stored in the File Cache and then copied / moved to an appropriate storage location.

  The line from the Primary Video Player to the Advanced Element indicates that the video currently being played in the Primary Video Set is paused according to the description of the Advanced Navigation Engine or interpretation of the user operation, and the Advanced Element such as an image file that captures the screen is saved as a file. It shows the flow of writing to Cache. For the capture screen created in this way, create an original chapter collection with appropriate explanations, store the data in Persistent Storage, etc., and use the original chapter to select the scene and watch the video from the next time Can be considered. As a capture destination of the capture screen, a Secondary Video Set screen output by the Secondary Video Player, a graphic screen output by the Advanced Element Presentation Engine, an AV Renderer output image obtained by mixing them, or the like may be captured.

  Data created by such Navigation Manager, Presentation Engine, etc. is temporarily stored in the File Cache and then stored in an appropriate Data Source medium according to the description of Advanced Navigation. Similarly, when storing or uploading contents in Persistent Storage, Network Server, or Disc to Persistent Storage, Network Server, or after uploading data to File Cache once according to the description of Advanced Navigation, the appropriate Data Stored on Source media.

  FIG. 143 is a detailed diagram of a composite model for image output. In this figure, output of five image planes is assumed. When describing from the lower plane, they are Primary Video Plane, Secondary Video Plane, Sub-Picture Plane, Graphics Plane, and Cursor Plane.

  The Primary Video Plane is a video output plane of the Primary Video Set. In this model, it is supplied to the AV Renderer through a scaler. In this model, it is not assumed that the α value (value that determines the contrast ratio) is applied to the Primary Video Plane. However, when a background plane or the like is prepared below the Primary Video Plane, the Primary Video Plane Application of α value to is effective in enriching expressive power.

  Secondary Video Plane is a video output plane of Secondary Video Set. In this model, it is supplied to the AV Renderer through a scaler. In this model, the Secondary Video Plane is equipped with a Chroma Effect function to realize the function of extracting the shape of the object in the video and overlaying it on the Primary Video output. This can be realized by painting a portion other than the object to be extracted with a specific color and treating that color portion as a transparent portion.

  The Sub-Picture Plane is a sub-picture image output plane of the Primary Video Set. In this model, it is supplied to AV Renderer through a scaling device. For example, SD-size Sub-Picture is prepared in advance, Sub-Picture for Pan Scan output or Sub-Picture for Letter Box output even in SD size. If a picture is prepared, the scaler does not perform any processing, but outputs the sub-picture data that matches the output from the SP decoder to synthesize it with the entire image.

  Graphics Plane is an image output plane of Advanced Element Presentation Engine. In this model, image data such as JPEG and PNG, image data such as cell animation and vector animation is processed by the Advanced Graphic Decoder, and text image output using font data is processed by the Advanced Text Decoder. Is assumed. The output of the decoding result for each object is sent to Layout / Alpha Control, and layout and α blending are performed according to the control information of Navigation Manager interpreting Advanced Navigation. The layout process also includes object scaling and the like.

  The Cursor Plane is managed and output by the Cursor Manager in the User Interface Controller. In this model, an α value is set for the Cursor object and combined with other planes.

  The output of the above five image data is output from each decoder or the like in a format that matches the final video data output frame rate of the HD_DVD player, and all plane data is the same when imported into the AV Renderer. Supplied in frame rate / format.

  Graphics Composer is a module that manages the composition of the above five image outputs in AV Renderer, and is composed of α Blending Control, Position Control, Chroma Effect, and the like.

  As described above, the Chroma Effect is a functional module for processing a color designated by the Navigation Manger as a transparent color in order to cut out the shape of a predetermined object from the video output of the Secondary Video Player. Actually, the output of Secondary Video may change the color value of the pixel as Chroma Key by using Lossy codec such as MPEG2, so Chroma Key is not a single color and has a certain range. It is effective to install a function for extracting the shape of an object more accurately by designating or performing image processing.

  Position Control supplies an image in which the position where the input video data is arranged with respect to the entire image output size to α Blending Control.

  α Blending Control combines the above-described video data in accordance with an instruction of Advanced Navigation interpreted by Navigation Manger to generate a final video output image.

  FIG. 144 is a diagram illustrating an example of actual image output of the composite model of image output in FIG. 143. The video output of the Primary Video Set of the Primary Video Plane is generally moving image data of the main video of the DVD and is displayed on the entire screen. The video output of the secondary video of the secondary video plane is generally arranged in the primary video plane in a picture in picture format, and is α-blended with respect to the primary video image in accordance with the description of the advanced navigation. Further, as described above, it is also possible to cut out the shape of the object and combine it with the Primary Video Plane.

  The output of Sub-Picture Plane is Sub-Picture image data stored in the Primary Video Set, given a pixel-level α value, and synthesized into a composite image of the Primary Video Plane or Secondary Video Plane that corresponds to the background .

  In the output of the Graphics Plane, the α value at the pixel level is controlled, and the α value of the entire plane is not controlled by the Navigation Manager. For the Graphics Plane, the Navigation Manger controls the α value in units of objects such as button images and text arranged in the Graphics Plane. When controlling the alpha value at the pixel level, it is necessary to use a format in which the image object itself can describe the alpha value at the pixel level. PNG, JPEG2000, etc. can be used for such a format. For text, once the output character image is scaled, the characters may be crushed, making it difficult to read. Therefore, the image data supplied to Layout / α Control should be adjusted to the final output image size beforehand. Therefore, it is possible to avoid deterioration in image quality due to scaling, which is effective.

  The Cursor Plane is a pointer image that moves on the screen in response to an event of a direction key such as a mouse or a remote controller. This pointer image can be replaced with an image of an arbitrary Advanced Element according to the description of Advanced Navigation. The α value can be applied to the Cursor Plane at the object (Plane) level.

  FIG. 145 is a diagram illustrating an audio output mixing model. In this model, three audio outputs are mixed. That is, Primary Audio is an audio output of Primary Video Set. Secondary Audio is an audio output of Secondary Video Set. Here, the Secondary Video Set does not necessarily have to be accompanied by Video output, and there may be a Secondary Video Set only for Audio.

  The Audio Decoder in the Primary Video Player and the Audio Decoder in the Secondary Video Player can interpret the Meta Data in each Audio Elementary Stream and control the mixing level change at the frame level. In this model, Meta Data processing is shown as an example in which each decoder completes. However, Meta Data information may be sent to the Sound Mixer and processed in the Sound Mixer.

  The Sound Decoder in the Advanced Element Presentation Engine outputs a sound effect that sounds when a button is clicked. The audio output mixing process is realized by a sampling rate converter and a sound mixer in the AV Renderer.

  In this model, assuming that the primary video audio output is generally supplied with the best sound quality, the sampling rate of the secondary audio and effect sound is matched to the primary audio, so the output of the primary audio has a sampling rate. Does not have Converter. In order to realize an HD_DVD player at a low price, it is effective to provide a sampling rate converter ahead of the primary audio output when realizing a function that lowers the quality of the audio output.

  Each audio signal is supplied to the sound mixer in a state where the sampling rate is unified by the sampling rate converter. The Sound Mixer mixes and outputs these three audio signals in accordance with the mixing level designated by the Navigation Manager in accordance with the description of Advanced Navigation. If the HD_DVD player has an analog audio output, it is sent to a DA converter, and if it has a digital output, it is sent to an appropriate encoding processor.

  Water Mark Detect is a module for investigating the output audio signal of Sound Mixer and detecting the presence or absence of copyright management information.

  FIG. 146 is a diagram illustrating User Interface processing managed by the User Interface Controller. In this model, Front Panel, Remote Controller, Keyboard, Mouse, and Game Pad are shown as User Input devices. As described above, the Cursor Manager controls the display position of the cursor object on the screen according to the direction keys and movement events of the Remote Controller and Mouse. In addition, button pressing events such as Remote Controller and Keyboard are notified to Navigation Manager as User Interface Events.

  FIG. 147 is a flowchart showing the flow of startup processing after inserting a disc. When the disc is inserted into the HD_DVD player, first the content type is detected. Content type detection can be realized based on the presence or absence of Advanced VTS or the presence or absence of a specific markup file. If the disc is a content type 2 or 3 disc (YES in step ST302), Startup File is read from the disc (step ST304). As the data structure of the content type 2 or 3, there are cases where there are a disk constituted only by Advanced VTS as shown in FIG. 74 and both Advanced VTS and Standard VTS as shown in FIG.

  After interpreting Startup, the player settings are changed according to the description (step ST306... Player system settings: Configure Player System). Information to be changed includes allocation of File Cache and Streaming Buffer of Data Cache, setting of network connection, and the like. Thereafter, an Advanced Navigation file for initial operation described in Startup File is read from Disc, Network Server, Persistent Storage, etc. (step ST308), and Advanced Navigation processing described in Startup File is started. (Step ST310).

  On the other hand, if the disc is of content type 1 (No in step ST302, yes in step ST312), Standard VTS playback processing is performed in accordance with the conventional DVD (step ST314). The content type 1 disc is composed of only Standard VTS as shown in FIG. In the case of other discs (No in step ST302, No in step ST312), each reproduction process is performed according to the media type supported by the individual HD_DVD player that reproduces the disc (step ST316).

<Summary>
An information storage medium (high-definition video desk or the like) according to an embodiment of the present invention has a management area (30) for recording management information and an object area (40, 50) for recording objects managed by the management information. Data for storing a video data recording area (20) including the information and an advanced content recording area (21) including information (21A to 21E) different from the recording contents (30 to 50) of the video data recording area (20) An area (12) and a file information area (11) for storing file information corresponding to the recorded contents of the data area (12) are provided. In this information storage medium, the object area (40, 50) includes an extended video object (an object in HDVTS, which is appropriately abbreviated as EVOBS or VOBS) that is played back and managed in a logical unit called a program chain, and the extended video object. And an advanced object (an object in AHDVTS) recorded separately. The advanced object includes playback sequence information describing the playback order of the extended video object (playback control information realized by the Markup language as exemplified in FIGS. 95 to 98) and playback conditions (playback timing of other advanced objects). , Reproduction control information that gives an image output position, a display size, and the like).

  The above playback conditions (or playback control information, playback sequence information, etc.) can be described using a predetermined language (such as a markup language) by a provider of content recorded on the information storage medium. In addition, by providing a playback device with a markup language that gives playback conditions to a playback device using a network (such as the Internet), the management information that has been recorded on the information storage medium and uniquely determined so far can be updated. It becomes possible.

  Furthermore, for example, playback control information for controlling playback of a video object is distributed after the disc has been manufactured over the Internet or the like, or the disc is recreated simply by adding the above-described playback control information to the manufactured video disc. It becomes possible to produce a new disk without any problems. Specifically, video objects that could not be played at the time of shipment of the DVD video disc can be played under specific conditions using playback control information distributed from the Internet, It is possible to correct the problem by controlling the location where the error occurred at the time of shipment using the reproduction control information.

  From another point of view, according to one embodiment of the present invention, an advanced object and / or an extension is provided with reproduction control information realized by a Markup language or the like at the time of production of an information storage medium (ROM disk) or after its sale. A mechanism is provided in which the playback sequence of video objects can be freely changed and enjoyed.

  In the data area (12), the relationship between the reproduction time (TM_DIFF, etc.) and the recording position (TM_EN_ADR, etc.) is managed by one or more time maps (TMAP # 1, # 2, etc .; corresponding to TMAPIT). A collection of the above primary objects (EVOB # 1, # 2, etc.), which is a primary object set (P-EVOBS) constituting the main video stream, and a playback time (TM_DIFF) and recording by an individual time map (TMAP) It is an object for managing the relationship with the position (TM_EN_ADR), and is configured to store a secondary object (S-EVOB) constituting another video stream that can be reproduced simultaneously with the main video stream.

  Here, the reproduction of the one or more primary objects (EVOB # 1, # 2, etc.) can be managed by the reproduction time by the one or more time maps (TMAP # 1, # 2, etc .; corresponding to TMAPIT). The secondary object (S-EVOB) that can be played back simultaneously with (or synchronously with) any of the objects (EVOB # 1, # 2, etc.) is played back by the individual time map (TMAP). Can manage. At this time, the playback timing and / or playback period of the secondary object that is played back simultaneously (synchronously) with respect to a certain primary object can be freely set using the predetermined language (Markup language or the like).

  FIG. 148 is a diagram for describing an example of the configuration of advanced content. The Advanced Content includes Advanced Navigation for managing Primary / Secondary Video Set output, text / graphic rendering, and audio output, and Advanced Data including these data managed by Advanced Navigation. Advanced Navigation includes Playlist files, Loading Information files, Markup files (for content, styling, timing information) and Script files. Advanced Data includes Primary Video Set (VTSI, TMAP and P-EVOB), Secondary Video Set (TMAP and S-EVOB), Advanced Element (JPEG, PNG, MNG, L-PCM, OpenType font, etc.) and others. Yes.

  Here, the playlist file described in XML (markup language) is arranged on the disc. The playback device (player) of this disc is configured to play this Playlist file first (prior to playback of Advanced content) when the disc has Advanced content.

This Playlist file can include the following information (see FIG. 236 described later):
* Object Mapping Information (information for playback objects in each title and mapped on the timeline of this title)
* Playback Sequence (Playback information for each title described by the title timeline)
* Configuration Information (Information for system configuration such as data buffer alignment)
The Primary Video Set includes Video Title Set Information (VTSI), Enhanced Video Object Set for Video Title Set (VTS_EVOBS), Backup of Video Title Set Information (VTSI_BUP), and Video Title Set Time Map Information (VTS_TMAP). Has been.

  FIG. 149 is a diagram for describing a configuration example of video title set information (VTSI). VTSI describes information for one video title, and attribute information of each EVOB can be described by this information. This VTSI starts with a Video Title Set Information Management Table (VTSI_MAT), followed by a Video Title Set Enhanced Video Object Attribute Information Table (VTS_EVOB_ATRT) and a Video Title Set Enhanced Video Object Information Table (VTS_EVOBIT). Here, each Table is aligned with the boundary between adjacent logical blocks. Because of this boundary alignment, each table can be followed up to 2047 bytes (which can include 00h).

  FIG. 150 is a diagram illustrating a configuration example of a video title set information management table (VTSI_MAT). In this table, VTS_ID first arranged at the relative byte position (RBP) describes “ADVANCED-VTS” for identifying a VTSI file with an ISO646 (a-characters) character set code. The next VTS_EA describes the end address of this VTS as a relative block number from the first logical block of the VTS. The next VTSI_EA describes the end address of this VTSI as a relative block number from the first logical block of the corresponding VTSI. The next VERN describes the version number of the corresponding DVD video standard.

  FIG. 151 is a diagram illustrating a configuration example of a video title set category (VTS_CAT). This VTS_CAT is arranged after VERN in FIG. 150, and includes Application type information bits. By this Application type, it is possible to distinguish between Advanced VTS (= 0010b), Interoperable VTS (= 0011b), and others. After VTS_CAT in FIG. 150, an end address of VTSI_MAT (VTSI_MAT_EA), a start address of VTS_EVOB_ATRT (VTS_EVOB_ATRT_SA), a start address of VTS_EVOBIT (VTS_EVOBIT_SA), a start address of VTS_EVOBS (VTS_EVOBS_SA), and others (Reserved) are placed.

  FIG. 152 is a view for explaining a configuration example of a video title set enhanced video object attribute table (VTS_EVOB_ATRT).

In this table, attribute information defined in each EVOB is described under the Primary Video Set. This table starts with VTS_EVOB_ATRT information (VTS_EVOB_ATRTI), followed by one or more VTS_EVOB_ATR search pointers (VTS_EVOB_ATR_SRPs) and one or more VTS_EVOB attributes (VTS_EVOB_ATRs). One VTS_EVOB attribute (VTS_EVOB_ATR) corresponds to any one or more EVOB attributes under the Primary Video Set.

  FIG. 153 is a diagram for describing a configuration example of the video title set enhanced video object attribute table information (VTS_EVOB_ATRTI). This attribute table information (VTS_EVOB_ATRTI) includes information (VTS_EVOB_ATR_Ns) indicating the number of VTS_EVOB_ATR and an end address (VTS_EVOB_ATRT_EA) of VTS_EVOB_ATRT.

  FIG. 154 is a diagram for explaining a configuration example of the video title set enhanced video object attribute search pointer (VTS_EVOB_ATR_SRP). This attribute search pointer (VTS_EVOB_ATR_SRP) includes the start address (VTS_EVOB_ATR_SA) of VTS_EVOB_ATR.

  FIG. 155 is a diagram for explaining a configuration example of the video title set enhanced video object attribute (VTS_EVOB_ATR). One VTS_EVOB attribute (VTS_EVOB_ATR) includes an EVOB video attribute (EVOB_ATR), an EVOB main video attribute (EVOB_VM_ATR), an EVOB sub-video attribute (EVOB_VS_ATR), an EVOB main audio stream number (EVOB_AMST_Ns), and Main audio stream attribute table (EVOB_AMST_ATRT), EVOB multi-channel main audio stream attribute table (EVOB_MU_ASMT_ATRT), EVOB sub audio stream count (EVOB_ASST_Ns), EVOB sub audio stream attribute table (EVOB_ASST_ATRT), and EVOB Includes sub-picture stream count (EVOB_SPST_Ns), EVOB sub-picture stream attribute table (EVOB_SPST_ATRT), EVOB SD sub-picture palette (EVOB_SDSP_PLT), EVOB HD sub-picture palette (EVOB_HDSP_PLT), etc. It is composed of

  Note that the same VTS_EVOB_ATR can be shared by a plurality of EVOBs (one attribute can be reused by a plurality of EVOBs). Further, when a plurality of multiplexed EVOBs belong to one Interleaved Block for seamless angle switching, the same attribute (VTS_EVOB_ATR) is applied to these plurality of EVOBs.

  FIG. 156 is a diagram illustrating a configuration example of the enhanced video object attribute (EVOB_ATR). With this attribute (EVOB_ATR), it is possible to separately describe whether or not Sub Video stream and Sub Audio stream exist.

  FIG. 157 is a diagram for explaining a configuration example of the main video attribute (EVOB_VM_ATR) of the enhanced video object. Each field of this attribute (EVOB_VM_ATR) has a value (specific example is FIG. 158) that matches (matches) information in the main video stream of the EVOB.

  FIG. 158 is a diagram for describing a specific example of parameters in the main video attribute (EVOB_VM_ATR) of the enhanced video object. In the Video compression mode field of EVOB_VM_ATR, 01b indicates compliance with MPEG-2, 10b indicates compliance with MPEG-4 AVC, and 11b indicates compliance with SMPTE VC-1. Other bit values in this field are reserved for other compression modes.

  In the TV System field, 00b indicates compliance with 525/60 (NTSC), 01b indicates compliance with 625/50 (PAL), and 10b indicates High Definition (HD) / 60 * (525 / Can be used to downconvert to 60), and 11b to be compliant with High Definition (HD) / 50 * (can be used to downconvert to 625/50) .

  In the Aspect ratio field, 00b indicates an aspect ratio of 4: 3, and 11b indicates an aspect ratio of 16: 9. Other bit values in this field are reserved for other aspect ratios.

In the Display mode field, a display mode allowed on a monitor having an aspect ratio of 4: 3 is described. If "Aspect ratio"is' 00b '(4: 3),' 11b 'is written in this field. If "Aspect ratio"is'11b' (16: 9), '00b', '01b 'Or' 10b 'is written. Here, when the Display mode field is 00b, both Both Pan-scan * and Letterbox are shown. When 01b, only Pan-scan * is shown. When 10b, only Letterbox is shown, and when 11b. Is not specified. (*: Pan-scan refers to extracting a window with an aspect ratio of 4: 3 from the decoded image.)
In the CC1 field, 1b indicates that closed caption data for field 1 is recorded in the video stream, and 0b indicates that closed caption data for field 1 is not recorded in the video stream.

  In the CC2 field, 1b indicates that closed caption data for field 2 is recorded in the video stream, and 0b indicates that closed caption data for field 2 is not recorded in the video stream.

In the Source picture resolution field,
0000b indicates 352x240 (525/60 system) or 352x288 (625/50 system)
0001b indicates 352x480 (525/60 system) or 352x576 (625/50 system)
0010b indicates 480x480 (525/60 system) or 480x576 (625/50 system)
0011b indicates 544x480 (525/60 system) or 544x576 (625/50 system)
0100b indicates 704x480 (525/60 system) or 704x576 (625/50 system)
0101b indicates 720x480 (525/60 system) or 720x576 (625/50 system)
0110 to 0111b indicates reserved. Also,
1000b indicates 1280x720 (HD / 60 or HD / 50 system)
1001b indicates 960x1080 (HD / 60 or HD / 50 system)
1010b indicates 1280x1080 (HD / 60 or HD / 50 system)
1011b indicates 1440 × 1080 (HD / 60 or HD / 50 system)
1100b indicates 1920 × 1080 (HD / 60 or HD / 50 system)
1101b to 1111b indicates reserved.

The Source picture letterboxed field describes whether or not the video output is a letterbox. This field is filled with '0b' if "Aspect ratio" is '11b' (16: 9), '0b' or '1b' if "Aspect ratio" is '00b' (4: 3) 'Is written. Here, if the Source picture letterboxed field is 0b, it indicates that it is not a letterbox, and if it is 1b, it indicates that it is a letterbox. (If Source Video picture is letterboxed, sub-pictures can be displayed only in the actual image display area of Letterbox.)
The Source picture progressive mode field describes whether the source picture is an interlaced picture or a progressive picture. In this field, 00b is written for Interlaced picture, 01b is written for Progressive picture, and 10b is written otherwise.

  In the Film camera mode field, source picture mode for 625/50 system is described. This field contains '0b' if "TV system" is '00b' (525/60), '0b' or '1b' if "TV system" is '01b' (625/50) 'Is written and' TV system 'is' 10b' (HD / 60), '0b' is written, 'TV system' is' 11b '(HD / 50) and down-converted to 625/50 '0b' or '1b' is written when used for. Here, when the Film camera mode field is 0b, it indicates that it is camera mode, and when it is 1b, it indicates that it is film mode. The camera mode and film mode are defined in ETS300 294 Edition 2: 1995-12.

  FIG. 159 is a diagram for explaining a configuration example of the sub video attribute (EVOB_VS_ATR) of the enhanced video object. Each field of this attribute (EVOB_VS_ATR) has a value that matches (matches) the information in the sub video stream of the corresponding EVOB (the data structure is the same as in FIG. 157).

  FIG. 160 is a diagram for explaining a configuration example of the number of main audio streams in an enhanced video object (EVOB_AMST_Ns). The number of main audio streams in EVOB described by EVOB_AMST_Ns can be arbitrarily specified between 0 and 8. The number of audio streams other than 0 to 8 is reserved.

  FIG. 161 is a diagram illustrating a configuration example of an attribute table (EVOB_AMST_ATRT) of the main audio stream of the enhanced video object. Each field of this EVOB_AMST_ATRT has a value that matches (matches) information in the main audio stream of the corresponding EVOB. One EVOB_AMST_ATR is described for each Main Audio stream. This EVOB_AMST_ATRT has areas for eight main audio stream attributes EVOB_AMST_ATRs. The stream numbers here are assigned from 0 in accordance with the description order of EVOB_AMST_ATRs (in the example of FIG. 161, stream numbers # 0 to # 7 are assigned). When the number of main audio streams of the corresponding EVOB is less than 8, each bit of EVOB_AMST_ATR for unused streams is filled with “0b”.

FIG. 162 is a diagram for describing a configuration example of attributes (EVOB_AMST_ATR) of the main audio stream of each enhanced video object. Each EVOB_AMST_ATR includes Audio coding mode, Multichannel extension, Audio type, Audio application mode, Quantization / DRC, fs, reserved, Number of Audio channels, Specific code (upper bits), and Specific code ( lower bits), reserved (for Specific code), Specific code extension,
It includes reserved and Application Information.

  FIG. 163 is a diagram for describing a specific example of parameters in the attribute (EVOB_AMST_ATR) of the main audio stream of the enhanced video object.

  Audio coding mode is 000b reserved for Dolby AC-3, 001b shows Packed PCM audio (MLP), 010b shows MPEG-1 or MPEG-2 without extension bitstream, 011b has extension bitstream MPEG-2 extension bitstream is shown, reserved is shown in 100b, Linear PCM audio with sample data of 1/1200 second is shown in 101b, DTS-HD is shown in 110b, and Dolby Digital Plus (DD +) is shown in 111b Is shown.

  In the multichannel extension, 0b indicates that the related EVOB_MU_AMST_ATR is invalid, and 1b indicates that the multichannel extension is linked to the related EVOB_MU_AMST_ATR. When the audio application mode is “Surround mode”, the flag of this multichannel extension is set to “1b”. As for the Audio type, 00b is not used (Not specified), 01b indicates that Language is included, and others are reserved.

  As for the audio application mode, 00b is unused (Not specified), 01b indicates reserved, 10b indicates Surround mode, and 11b indicates reserved.

  In “Quantization / DRC”, “11b” is written when “Audio coding mode” is “110b” or “111b”. On the other hand, when “Audio coding mode” is “010b” or “011b”, a bit indicating the following contents is written in Quantization / DRC. That is, 00b indicates that Dynamic range control data does not exist in the MPEG audio stream, 01b indicates that Dynamic range control data exists in the MPEG audio stream, and 10b and 11b indicate reserved. It has become. Here, when “Audio coding mode” is “001b” or “101b”, a bit indicating the following contents is written in the Quantization / DRC. In other words, 00b indicates the number of quantization bits of 16 bits, 01b indicates the number of quantization bits of 20 bits, 10b indicates the number of quantization bits of 24 bits, and 11b indicates reserved.

  fs indicates a sampling frequency, 00b indicates 48 kHz, 01b indicates 96 kHz, and otherwise indicates reserved.

For Number of Audio channels, 000b indicates 1ch (mono), 001b indicates 2ch (stereo), 010b indicates 3ch, 011b indicates 4ch,
100b indicates 5ch, 101b indicates 6ch, 110b indicates 7ch, and 111b indicates 8ch (3ch to 8ch are multichannel). Here, “0.1ch” in multi-channel is handled as one channel. Accordingly, for example, in the case of 5.1ch, this is set to 6ch, and '101b' is written in Number of Audio channels.

  FIG. 164 is a diagram illustrating a configuration example of the attribute table (EVOB_MU_AMST_ATRT) of the multi-channel main audio stream of the enhanced video object. In this EVOB_MU_AST_ATRT, each main audio attribute for multi-channel is described. This attribute table includes up to eight types of audio attributes EVOB_MU_AMST_ATR (the stream numbers start from 0 to 7). Here, ‘0b’ is written in each bit of an audio stream area in which “Multichannel extension” in EVOB_AMST_ATR is ‘0b’.

  FIG. 165 is a diagram for describing a configuration example of attributes (EVOB_MU_AMST_ATR) of the multi-channel main audio stream of each enhanced video object. This EVOB_MU_AMST_ATR is an Audio mixed flag, ACH0 mix mode, Audio channel contents, Audio mixed flag, ACH1 mix mode, Audio channel contents, Audio mixing phase, ACH2 mix mode, Audio channel contents, Audio channel mixing phase, ACH3 mix mode, Audio channel contents, Audio mixing phase, ACH4 mix mode, Audio channel contents, Audio mixing phase, ACH5 mix mode, Audio channel contents, Audio mixing phase, ACH6 It includes a mix mode, an audio channel contents, an audio mixing phase, an ACH7 mix mode, and an audio channel contents.

  FIG. 166 is a diagram illustrating a configuration example of the number of sub-audio streams in the enhanced video object (EVOB_ASST_Ns). A number between 0 and 2 is described in Number of Audio streams in EVOB_ASST_Ns, and other numbers are reserved.

  FIG. 167 is a diagram illustrating a configuration example of the attribute table (EVOB_ASST_ATRT) of the sub audio stream of the enhanced video object. The value of each field of this EVOB_ASST_ATRT has a value that matches (matches) the information in the sub audio stream of the corresponding EVOB. One EVOB_ASST_ATR is described for each Sub Audio stream. This EVOB_ASST_ATRT has areas for two sub audio stream attributes EVOB_ASST_ATRs. The stream numbers here are assigned from 0 in accordance with the description order of EVOB_ASST_ATRs (in the example of FIG. 167, stream numbers # 0 to # 1 are assigned). When the number of main audio streams of the corresponding EVOB is less than 2, each bit of EVOB_ASST_ATR for unused streams is filled with “0b”.

  FIG. 168 is a diagram for describing a configuration example of attributes (EVOB_ASST_ATR) of the sub audio stream of each enhanced video object. Each EVOB_ASST_ATR includes Audio coding mode, Multichannel extension, Audio type, Audio application mode, Quantization / DRC, fs, reserved, Number of Audio channels, Specific code (upper bits), and Specific code ( lower bits), reserved (for Specific code), Specific code extension, reserved, and Application Information.

  FIG. 169 is a diagram illustrating a configuration example of the number of sub-picture streams in an enhanced video object (EVOB_SPST_Ns). A number between 0 and 32 is described in Number of Sub-picture streams in EVOB_SPST_Ns, and other numbers are reserved.

  FIG. 170 is a diagram for explaining a configuration example of an attribute table (EVOB_SPST_ATRT) of a sub video stream of an enhanced video object. In this EVOB_SPST_ATRT, each sub-picture stream attribute (EVOB_SPST_ATR) for EVOB is described. One EVOB_SPST_ATR is described for each existing sub-picture stream. Up to the number of EVOB_SPST_ATRs described is assigned to the stream numbers in order from 0. When the number of sub-picture streams is less than 32, each bit of EVOB_SPST_ATR for unused streams is filled with '0b'.

  FIG. 171 is a diagram for explaining a configuration example of the attribute (EVOB_SPST_ATR) of the sub video stream of each enhanced video object. Each VTSM_SPST_ATR has Sub-picture coding mode, reserved, HD, SD-Wide, SD-PS, SD-LB, Specific code (upper bits), Specific code (lower bits), reserved ( for Specific code) and Specific code extension.

  FIG. 172 is a view for explaining a specific example of parameters in the attribute (EVOB_AMST_ATR) of the main audio stream of the enhanced video object.

  Sub-picture coding mode is 000b, 2 bits / pixel run-length compression rule (PRE_HEAD value is other than (0000h)), 001b is 2 bits / pixel run-length compression rule (PRE_HEAD value is ( 0000h)) is shown, the run-length compression rule of 8 bits / pixel is shown at 100b, and the others are reserved.

  As for the sub-picture type, 00b is not used (Not specified), Language is indicated by 01b, and others are reserved. In the title, the sub-picture stream having the language code extension of Forced Caption (09h) along the sub-picture stream having the same language code is 1 or less. Also, a Sub-picture stream with a Forced Caption (09h) Language Code extension has a larger Sub-picture stream number than all other Sub-picture streams that do not have a Forced Caption (09h) Language Code extension. Yes.

  When "Sub-picture coding mode" is '001b' or '100b', a bit indicating whether or not an HD stream exists is written in HD (if HD = 00b, there is no HD stream, HD If = 01b, there is an HD stream).

  When “Sub-picture coding mode” is “001b” or “100b”, a bit indicating whether or not an SD-Wide stream (an SD stream having an aspect ratio of 16: 9) exists is written in SD-Wide (When SD-Wide = 00b, there is no SD-Wide stream, and when SD-Wide = 01b, there is an SD-Wide stream).

  In SD-PS, when “Sub-picture coding mode” is “001b” or “100b”, it indicates whether or not an SD Pan-Scan stream (pan-scan SD stream with an aspect ratio of 4: 3) exists. Bits are written (the SD Pan-Scan stream does not exist if SD-PS = 00b, and the SD Pan-Scan stream exists if SD-PS = 01b).

  In SD-LB, when “Sub-picture coding mode” is “001b” or “100b”, there is a bit indicating whether or not an SD Letterbox stream (a letterbox SD stream having an aspect ratio of 4: 3) exists. The SD Letterbox stream does not exist if SD-LB = 00b, and the SD Letterbox stream exists if SD-LB = 01b.

FIG. 173 is a diagram illustrating a configuration example of a palette (EVOB_SDSP_PLT) describing luminance / color difference signals (256 sets) shared by all SD sub-picture streams in each enhanced video object. In this EVOB_SDSP_PLT, color codes from 0 to 255 are assigned in the order of description. Each EVOB_SDSP_PLT includes reserved, Luminance signal (Y), Color difference signal (Cr = R−Y), and Color difference signal (Cb = B−Y). Here, Y, Cr, and Cb can be calculated from the following equations using R, G, and B that take values from 0 to 1:
Y = 16 + 219 x (0.299R + 0.587G + 0.114B)
(16 ≤ Y ≤ 235)
Cr = 128 + 224 × (0.500R-0.419G-0.081B)
(16 ≤ Cr ≤ 240)
Cb = 128 + 224 × (-0.169R-0.331G + 0.500B)
(16 ≤ Cb ≤ 240)
Note that the values of Y, Cr, and Cb are predetermined even when there is no Sub-picture stream in the EVOB or when a set of luminance signal and color difference signal is not used in the EVOB. It is comprised so that it may exist in the range.

  FIG. 174 is a diagram illustrating a configuration example of a palette (EVOB_HDSP_PLT) describing luminance / color difference signals (256 sets) shared by all HD sub-picture streams in each enhanced video object.

In this EVOB_HDSP_PLT, color codes from 0 to 255 are assigned in the order of description. Each EVOB_HDSP_PLT includes reserved, Luminance signal (Y), Color difference signal (Cr = R−Y), and Color difference signal (Cb = B−Y). Here, Y, Cr, and Cb can be calculated from the following equations using R, G, and B that take values from 0 to 1:
Y = 16 + 219 x (0.2126R + 0.7152G + 0.0722B)
(16 ≤ Y ≤ 235)
Cr = 128 + 224 × (0.5000R-0.4542G-0.0458B)
(16 ≤ Cr ≤ 240)
Cb = 128 + 224 × (-0.1146R-0.3854G-0.5000B)
(16 ≤ Cb ≤ 240)
Note that the values of Y, Cr, and Cb are predetermined even when there is no Sub-picture stream in the EVOB or when a set of luminance signal and color difference signal is not used in the EVOB. It is comprised so that it may exist in the range.

  FIG. 175 is a diagram illustrating a configuration example of a video title set enhanced video object information table (VTS_EVOBIT). In this VTS_EVOBIT, information for each EVOB under the Primary Video Set is described. This table starts with VTS_EVOBIT Information (VTS_EVOBITI) and includes one or more VTS EVOBI Search Pointers (VTS_EVOBI_SRPs) and one or more VTS EVOB Information (VTS_EVOBIs).

  FIG. 176 is a diagram for describing a configuration example of the video title set enhanced video object information table information (VTS_EVOBITI). This VTS_EVOBITI includes EVOB_Ns describing the number of EVOBs and VTS_EVOBIT_EA describing the end address of VTS_EVOBIT expressed by the relative number of blocks from the first byte of the VTS_EVOBIT.

  FIG. 177 is a diagram for describing a configuration example of the video title set enhanced video object information search pointer (VTS_EVOBI_SRP). This VTS_EVOBI_SRP is configured to include VTS_EVOBI_SA describing start address of VTS_EVOBI (corresponding to the corresponding EVOB) expressed by the relative number of blocks from the first byte of VTS_EVOBIT.

  FIG. 178 is a view for explaining a configuration example of video title set enhanced video object information (VTS_EVOBI). This VTS_EVOBI includes EVOB_IDN describing EVOB ID number, EVOB_ATRN describing EVOB attribute number, SML_FLG describing Seamless Flag, EVOB_FIRST_SCR reserved for Interoperable VTS, PREV_EVOB_LAST_SCR reserved for Interoperable VTS, EVOB_TMAP_FNAME describing Filename of Time Map for EVOB is included.

  FIG. 179 is a diagram for describing an example of parameters in the video title set enhanced video object information (VTS_EVOBI). SML_FLG in VTS_EVOBI indicates whether or not the corresponding EVOB satisfies seamless playback conditions, SML_FLG = 0b indicates that the corresponding EVOB does not satisfy the conditions for seamless playback from the preceding EVOB, and SML_FLG = 1b It is shown that the corresponding EVOB satisfies the condition for seamless playback from the preceding EVOB.

  The EVOB_FIRST_SCR field is reserved for Interoperable VTS, and the value of this field is set to 'FF FF FF FF FF FFh' in Advanced VTS.

  The field of PREV_EVOB_LAST_SCR is reserved for Interoperable VTS, and the value of this field is set to 'FF FF FF FF FF FFh' in Advanced VTS.

  EVOB_TMAP_FNAME describes the filename of the Time Map referenced by the EVOB.

  FIG. 180 is a time map including time map information (TMAPI) used for converting the playback time in the primary enhanced video object (P-EVOB) into the address of the corresponding enhanced video object unit (EVOBU). It is a figure explaining the structural example of (TMAP). The TMAP starts with TMAP General Information (TMAP_GI), followed by one or more TMAPI Search Pointers (TMAPI_SRPs) and one or more TMAP Informations (TMAPIs), and finally ILVU Information (ILVUI) is arranged.

  FIG. 181 is a diagram for describing a configuration example of time map general information (TMAP_GI). This TMAP_GI includes TMAPI_Ns describing Number of TMAPIs, TMAP_TYPE describing Block Type of this TMAP, AGL_TYPE describing Angle Type of this TMAP, ILVUI_SA describing Start address of ILVUI, and End address of TMAP. It is configured to include the described TMAP_EA.

  Here, when TMAP_TYPE = '0b', TMAPI_Ns is set to '0'. When there is no ILVUI in the TMAP, “FFh” is set in ILVUI_SA. Further, the end address of the corresponding TMAP is represented by TMAP_EA with a relative logical block number from the first logical block of the corresponding TMAP.

  FIG. 182 is a diagram illustrating a configuration example of a time map type (TMAP_TYPE). When this TMAP_TYPE is 0b, it indicates that the current block is a continuous block, and when it is 1b, it indicates that the current block is an interleaved block.

  FIG. 183 is a diagram for describing a configuration example of an angle type (AGL_TYPE). When this AGL_TYPE is 00b, it indicates that the current block is not an Angle Block, when 01b it indicates that the current block is a Non Seamless Angle Block, and when 10b it indicates that the current block is a Seamless Angle Block. 11b is reserved. Here, when the block value in TMAP_TYPE is ‘1b’, ‘01b’ or ‘10b’ may be set in AGL_TYPE.

  FIG. 184 is a diagram for explaining a configuration example of the time map information search pointer (TMAPI_SRP). This TMAPI_SRP is TMAPI_SA that describes start address of the TMAPI with the relative logical block number from the first logical block of the corresponding TMAP, EVOB_IDN that describes the identifier number of EVOB for TMAPI, and relative to the first logical block of the corresponding EVOBS EVOB_ADR describing start address of the EVOB with block number, EVOB_PB_TM describing the playback time of EVOB specified by the number of video fields in the corresponding EVOB, EVOBU_ENTI_Ns describing the number of EVOBU_ENTI for TMAPI, and ILVU_ENTI for TMAPI And IGLU_ENTI_Ns (the value of ILVU_ENTI_Ns is '0' in TMAPI for continuous blocks) and AGLN that describes the angle number for TMAPI.

  FIG. 185 is a diagram for describing a configuration example of information (EVOBSINF) of (one or more) enhanced video objects belonging to the corresponding time map. This EVOBSINF describes EVOB information to which the corresponding TMAP belongs, and is configured to include CON_TY, reserved, EVOBS_TY, VTSN (Upper), and VTSN (Lower). Here, CON_TY is 0b, Advanced Content is indicated, and 1b is Standard Content. Further, EVOBS_TY is 0b, EVOBS for Title is indicated, and 1b is EVOBS for Menu. If the EVOB belongs to Advanced Content (that is, if CON_TY = '0'), EVOBS_TY is set to '0'.

Further, VTSN indicates the VTS number belonging to the corresponding EVOB. When the corresponding EVOB belongs to EVOBS in VMG or belongs to Advanced Content, VTSN is set to '0'.

  FIG. 186 is a diagram illustrating a configuration example of time map information (TMAPI) starting with entry information (EVOBU_ENTI # 1 to #i) of one or more enhanced video object units. TMAP Information (TMAPI), which is an element of Time Map (TMAP), is used to convert the playback time in EVOB into an EVOBU address. This TMAPI is composed of one or more EVOBU Entries. One TMAPI for continuous blocks is stored in one file, and this file is called TMAP. Here, one or more TMAPIs belonging to the same interleaved block are stored in the same file. This TMAPI is configured to start with one or more EVOBU Entry Informations (EVOBU_ENTIs).

  FIG. 187 is a diagram for describing a configuration example of enhanced video object unit entry information (EVOBU_ENTI). This EVOBU_ENTI includes 1STREF_SZ (Upper), 1STREF_SZ (Lower), EVOBU_PB_TM (Upper), EVOBU_PB_TM (Lower), EVOBU_SZ (Upper), and EVOBU_SZ (Lower).

  1STREF_SZ describes the size of the first reference picture of the EVOBU. The size of the first reference picture can be determined by the number of packs from the first pack of the corresponding EVOBU to the pack including the last byte of the reference picture encoded at the beginning of the corresponding EVOBU.

Where “reference picture” can be defined by one of the following:
I-picture encoded as a frame structure;
A pair of I-pictures encoded as a field trap.

  EVOBU_PB_TM describes the playback time of the EVOBU, and this playback time can be indicated by the number of video fields in the EVOBU.

  Further, EVOBU_SZ describes the size of the corresponding EVOBU, and this size can be indicated by the number of packs in the corresponding EVOBU.

  FIG. 188 is a diagram illustrating a configuration example of interleaved unit information (ILVUI) that exists when the time map information is for interleaved blocks. This ILVUI is composed of one or more ILVU Entry Informations (ILVU_ENTIs). This information (ILVUI) exists when TMAPI is for Interleaved Block.

  FIG. 189 is a diagram illustrating a configuration example of interleaved unit entry information (ILVU_ENTI). This ILVU_ENTI is configured to include ILVU_ADR that describes the start address of the corresponding ILVU with a relative logical block number from the first logical block of the corresponding EVOB, and ILVU_SZ that describes the size of the corresponding ILVU. This size can be represented by the number of EVOBUs.

  FIG. 190 is a diagram illustrating a list of pack types in the enhanced video object. This List of pack types includes Navigation pack (NV_PCK) configured to include General Control Information (GCI) and Data Search Information (DSI), and Video data (MPEG-2 / MPEG-4 AVC / SMPTE VC-1 ) Main Video pack (VM_PCK) configured to include), Sub Video pack (VS_PCK) configured to include Video data (MPEG-2 / MPEG-4 AVC / SMPTE VC-1), and Audio data Main Audio pack (AM_PCK) configured to include (Dolby Digital Plus (DD +) / MPEG / Linear PCM / DTS-HD / Packed PCM (MLP) / SDDS (option)) and Audio data (Dolby Digital Plus ( DD +) / MPEG / Linear PCM / DTS-HD / Packed PCM (MLP)) Sub Audio pack (AS_PCK) configured to include Sub-picture data (SP_PCK) ) And an Advanced pack (ADV_PCK) configured to include Advanced Content data.

  Here, Main Video pack (VM_PCK) in Primary Video Set follows the definition of V_PCK in Standard Content. Also, Sub Video pack (VS_PCK) in Primary Video Set follows the definition of V_PCK in Standard Content except for stream_id and P-STD_buffer_size (see FIG. 202).

  FIG. 191 is a diagram for describing an example of limiting the transfer rate for the stream of the enhanced video object. In this transfer rate limit example, EVOB has a limit of 30.24 Mbps for Total streams, and Main Video stream has a limit of 29.40 Mbps (HD) or 15.00 Mbps (SD) for Total streams. One stream is limited to 29.40 Mbps (HD) or 15.00 Mbps (SD), while Main Audio streams are limited to 19.60 Mbps for Total streams and 18.432 Mbps for One stream. There is a restriction, Sub-picture streams are restricted to 19.60 Mbps for Total streams and 10.08 Mbps for One stream.

Note that the following rules can be applied to restrictions on Sub-picture streams in EVOB:
a) For all Sub-picture packs (SP_PCK (i)) with the same sub_stream_ID,
SCR (n) ≤ SCR (n + 100) -T300packs
here,
n: 1 to (number of SP_PCK (i) s-100)
SCR (n): SCR of n-th SP_PCK (i)
SCR (n + 100): SCR of 100th SP_PCK (i) after n-th SP_PCK (i)
T300packs: value of 4388570 (= 27 × 10 ⁶ × 300 × 2048 × 8 / 30.24 × 10 ⁶ )
b) For all Sub-picture packs (SP_PCK (all)) in EVOB that can be seamlessly connected to subsequent EVOBs,
SCR (n) ≤ SCR (last)-T90packs
here,
n: 1 to (number of SP_PCK (all) s)
SCR (n): SCR of n-th SP_PCK (all)
SCR (last): SCR of last pack in EVOB
T90packs: value of 1316570 (= 27 × 10 ⁶ × 8 × 2048 × 90 / 30.24 × 10 ⁶ )
Note that at least the first pack of the subsequent EVOB is other than SP_PCK. T90packs + T1stpack guarantees 10 consecutive packs.

  FIG. 192 is a diagram illustrating a configuration example of the primary enhanced video object (P-EVOB). EVOB (here, Primary EVOB, that is, “P-EVOB”) includes part of Presentation Data and Navigation Data. Navigation Data included in EVOB includes General Control Information (GCI) and Data Search Information (DSI). Presentation data includes Main / Sub video data, Main / Sub audio data, Sub-picture data, Advanced Content data, and the like.

  Enhanced Video Object Set (EVOBS) corresponds to a set of EVOBs as shown in FIG. EVOB can be divided into one or more cells corresponding to one or more (integer) EVOBUs, or can be divided into one or more (integer) EVOBUs (without using cells).

  Each EVOBU is composed of a series of packs (various packs as exemplified in FIG. 192) arranged in the recording order. Each EVOBU starts with one NV_PCK and ends with any pack (or last pack of EVOB) that comes immediately before the next NV_PCK in the same EVOB. Except for the last EVOBU, EVOBU supports a playback time of 0.4 to 1.0 seconds. The EVOBU at the end corresponds to a playback time of 0.4 to 1.2 seconds.

For EVOBU, the following additional rules apply:
1) EVOBU playback time is an integral multiple of video field / frame periods (whether or not EVOBU contains video data);
2) EVOBU playback start and end times are specified in units of 90 kHz. Also, the playback start time of the current EVOBU (excluding the top EVOBU) is made the same as the playback end time of the preceding EVOBU;
3) When EVOBU includes video, the playback start time of EVOBU is the same as the playback start time of the first video field / frame. Also, the EVOBU playback period should be equal to or longer than the video data playback period;
4) When EVOBU includes video, the video data shall indicate one or more PAUs (Picture Access Units);
5) When an EVOBU with video data is followed by an EVOBU without video data (within the same EVOB), a sequence end code (SEQ_END_CODE) is appended to the last coded picture;
6) When the playback period of EVOBU is longer than the playback period of the video contained therein, a sequence end code (SEQ_END_CODE) is appended to the last coded picture;
7) Video data in EVOBU does not have multiple sequence end codes (SEQ_END_CODE);
8) When EVOB contains one or more sequence end codes (SEQ_END_CODE), it is used in ILVU. At this time, the EVOBU playback period is an integral multiple of video field / frame periods. The video data in EVOBU has one I picture for a still image, otherwise there is no video data. EVOBU having one I picture for a still picture has one sequence end code (SEQ_END_CODE). The first EVOBU in ILVU has video data.

Here, the playback period of the video contained in EVOBU is the sum of the following A and B:
A. The difference between the playback time stamp PTS of the last video access unit (in display order) and the playback time stamp PTS of the first video access unit (in display order) in EVOBU;
B. The playback duration (presentation duration) of the last video access unit (in display order).

  Each elementary stream is identified by a stream_ID defined in the Program stream. Audio Presentation Data that is not defined by MPEG is stored in PES packets with stream_ID of private_stream_1. Navigation Data (GCI and DSI) is stored in PES packets with stream_ID of private_stream_2. The first byte of the private_stream_1 and private_stream_2 packets data area is used to define the sub_stream_ID. When stream_id is private_stream_1 or private_stream_2, the first byte in the data area of each packet can be assigned as sub_stream_id.

FIG. 193 is a diagram for describing a restriction example of each element with respect to the stream of the primary enhanced video object. In this element restriction example,
For the Main Video stream,
1) Completed in EVOB,
2) When the video stream has interlaced video, the display configuration starts with the top field and ends with the bottom field.
3) A Video stream may or may not end with a sequence end code (SEQ_END_CODE);
For the Main Video stream,
1) The first EVOBU has video data.

For Main Audio streams,
1) Completed in EVOB,
2) When the audio stream is for Linear PCM, the first audio frame is the beginning of the GOF.

For Sub-picture streams,
1) Completed in EVOB,
2) The last playback time (PTM) of the last Sub-picture Unit (SPU) shall be less than or equal to the time indicated by EVOB_V_E_PTM (video end time)
3) The PTS of the first SPU is EVOB_V_S_PTM (video start time) or more,
4) Within each Sub-picture stream, the PTS of any SPU is larger than the PTS of the preceding SPU with the same sub_stream_id (if any).

For Sub-picture streams,
1) Complete in the cell,
2) Sub-picture playback is effective only in the cell where the SPU is recorded.

FIG. 194 is a diagram for describing a configuration example of the stream id and the stream id extension. In this stream_id and stream_id_extension,
stream_id = 110x 0 *** b, stream_id_extension = N / A, Stream coding = MPEG audio stream for Main *** = Decoding Audio stream number;
stream_id = 110x 1 *** b, stream_id_extension = N / A, Stream coding = MPEG audio stream for Sub
stream_id = 1110 0000b, stream_id_extension = N / A, Stream coding = Video stream (MPEG-2)
stream_id = 1110 0001b, stream_id_extension = N / A, Stream coding = Video stream (MPEG-2) for Sub;
stream_id = 1110 0010b, stream_id_extension = N / A, Stream coding = Video stream (MPEG-4 AVC)
stream_id = 1110 0011b, stream_id_extension = N / A, Stream coding = Video stream (MPEG-4 AVC) for Sub;
stream_id = 1110 1000b, stream_id_extension = N / A, Stream coding = reserved;
stream_id = 1110 1001b, stream_id_extension = N / A, Stream coding = reserved
stream_id = 1011 1101b, stream_id_extension = N / A, Stream coding = private_stream_1
stream_id = 1011 1111b, stream_id_extension = N / A, Stream coding = private_stream_2
stream_id = 1111 1101b, stream_id_extension = 101 0101b, Stream coding = extended_stream_id (Note) Indicates SMPTE VC-1 video stream for Main;
stream_id = 1111 1101b, stream_id_extension = 111 0101b, Stream coding = extended_stream_id (Note) Indicates SMPTE VC-1 video stream for Sub;
Stream_id = Others indicates Stream coding = no use.

  Note: SMPTE VC-1 streams can be identified by using stream_id extensions defined by amendment to MPEG-2 Systems [ISO / IEC 13818-1: 2000 / AMD2: 2004]. When stream_ID is set to 0xFD (1111 1101b), the stream_id_extension field actually defines nature of the stream. The stream_id_extension field is added to the PES header using the PES extension flags existing in the PES header.

FIG. 195 is a diagram illustrating a configuration example of the private stream 1 substream id. This sub_stream_id for private_stream_1
sub_stream_id = 001 * **** b indicates Stream coding = Sub-picture stream * **** = Decoding Sub-picture stream number;
sub_stream_id = 0100 1000b indicates reserved;
sub_stream_id = 011 * **** b indicates reserved;
sub_stream_id = 1000 0 *** b indicates reserved;
sub_stream_id = 1100 0 *** b indicates Dolby Digital plus (DD +) audio stream for Main *** = Decoding Audio stream number;
sub_stream_id = 1100 1 *** b indicates Dolby Digital plus (DD +) audio stream for Sub;
sub_stream_id = 1000 1 *** b indicates DTS-HD audio stream for Main *** = Decoding Audio stream number;
sub_stream_id = 1001 1 *** b indicates DTS-HD audio stream for Sub;
sub_stream_id = 1001 0 *** b indicates reserved (SDDS);
sub_stream_id = 1010 0 *** b indicates Linear PCM audio stream for Main *** = Decoding Audio stream number;
sub_stream_id = 1010 1 *** b indicates Linear PCM audio stream for Sub;
sub_stream_id = 1011 0 *** b indicates Packed PCM (MLP) audio stream for Main *** = Decoding Audio stream number;
sub_stream_id = 1011 1 *** b indicates Packed PCM (MLP) audio stream for Sub;
sub_stream_id = 1111 0000b indicates reserved;
sub_stream_id = 1111 0001b indicates reserved;
sub_stream_id = 1111 0010b-1111 0111b indicates reserved;
sub_stream_id = 1111 1111b indicates Provider defined stream;
sub_stream_id = Others indicates reserved (for future Presentation Data).

FIG. 196 is a diagram illustrating a configuration example of the private stream 2 substream id. In this sub_stream_id for private_stream_2
sub_stream_id = 0000 0000b indicates Stream coding = reserved;
sub_stream_id = 0000 0001b indicates Stream coding = DSI stream;
sub_stream_id = 0000 0010b indicates Stream coding = GCI stream;
sub_stream_id = 0000 1000b indicates Stream coding = reserved;
sub_stream_id = 0101 0000b indicates Stream coding = reserved;
sub_stream_id = 1000 0000b indicates Stream coding = Advanced stream;
sub_stream_id = 1111 1111b indicates Stream coding = Provider defined stream;
sub_stream_id = Others indicates Stream coding = reserved (for future Navigation Data).

  FIG. 197 is a diagram illustrating a configuration example of the navigation pack (NV_PCK) aligned at the head of the enhanced video object unit (EVOBU). The structure of pack and packet is "The system part of the MPEG-2 standard (ISO / IEC13818-1: 2000, ISO / IEC 13818-1: 2000 / COR1: 2002, ISO / IEC 13818-1: 2000 / COR2: 2002, ISO / IEC13818-1: 2000 / AMD1: 2003, ISO / IEC 13818-1: 2000 / AMD2: 2004 and ISO / IEC13818-1: 2000 / AMD3: 2005) ”.

  As illustrated in FIG. 197, the navigation pack (NV_PCK) includes a pack header, a system header, a GCI packet (GCI_PKT), and a PCI packet (PCI_PKT). In this example, GCI_PKT is indicated by stream_id = 1011 1111b (private_stream_2) and sub_stream_id = 0000 0010b, and DSI_PKT is indicated by stream_id = 1011 1111b (private_stream_2) and sub_stream_id = 0000 0001b.

  Note that GCI_PKT in FIG. 197 may be paraphrased as ADV_PKT (Advanced packet).

  FIG. 198 is a diagram for explaining a configuration example of the system header of the navigation pack. FIG. 199 is a diagram for explaining a configuration example of the buffer size boundary (P-STD_buf_size_bound) for the MPEG-2 / MPEG-4AVC / SMPTEVC-1 video elementary stream in the system header of FIG. 198.

  Quality has high-definition HD and standard-definition SD. In Video stream = MPEG-2, Quality = HD is indicated by Value = 1202 (buf_size = 1230848 bytes), and Quality = SD is Value = 232 (buf_size = 237568 bytes). Also, in Video stream = MPEG-4 AVC, Quality = HD is indicated by Value = 1808 (buf_size = 1851392 bytes), and Quality = SD is indicated by Value = 924 (buf_size = 946176 bytes). Furthermore, with Video stream = SMPTE VC-1, Quality = HD is indicated by Value = 1808 (buf_size = 1851392 bytes) or Value = 4848 (buf_size = 4964352 bytes), and Quality = SD is indicated by Value = 924 (buf_size = 946176 bytes) ) Or Quality = SD is indicated by Value = 1532 (buf_size = 1568768 bytes).

  FIG. 200 is a diagram for describing a configuration example of a general control information (GCI) packet. This GCI packet includes packet_start_code_prefix, stream_ID, PES_packet_length (03D4h), Private data area, sub_stream_ID (0000 0010b), and GCI data area.

  FIG. 201 is a diagram illustrating a configuration example of a data search information (DSI) packet. This DSI packet includes packet_start_code_prefix, stream_ID, PES_packet_length (03FAh), Private data area, sub_stream_ID (0000 0001b), and DSI data area.

  FIG. 202 is a diagram for explaining a configuration example of an MPEG-2 or MPEG-4 AVC video packet. An MPEG-2 or MPEG-4 AVC video packet includes stream_ID, P-STD_buffer_scale, and P-STD_buffer_size. Video stream for MPEG-2 is indicated by stream_id = 1110 0000b, and Video stream for MPEG-4 AVC is indicated by stream_id = 1110 0010b. Here, “P-STD_buf_size_bound” for Video stream is defined as follows. That is, for Video stream = MPEG-2, Quality = SD is indicated by Value = 232 (buf_size = 237568 bytes), and for Video stream = MPEG-4 AVC, Quality = SD is indicated by Value = 924 (buf_size = 946176 bytes). .

  FIG. 203 is a diagram illustrating a configuration example of a video packet of SMPTEVC-1. In the SMPTE VC-1 video packet, the stream_id field = 1111 1101b indicates the extended stream identifier for the SMPTE VC-1 stream, the fields '01' = 01b, P-STD_buffer_scale = 1 and P-STD_buffer_size = Note 5 The contents of 4 are shown.

Note 4: Unlike MPEG-2 video, VC-1 transport always requires the following bytes in the VESKT PES packet header:
1 byte including '' PES_extension_flag_2 '';
2 bytes data enabled by '' PES_extension_flag_2 ''. These 2 bytes are '' marker_bit '' (set to'1 '),''PES_extension_field_length''(setto'1'),'' stream_id_extension_flag ' Contains '(set to'0'), and `` stream_id_extension ''.

Note 5: P-STD_buffer_size is defined for SMPTE VC-1 Video elementary streams as follows:
In Video stream = SMPTE VC-1 and Quality = SD,
At Value = 924, the buffer size is buf_size = 946176 bytes,
With Value = 1532, the buffer size buf_size = 1568768 bytes.

  FIG. 204 is a diagram for explaining a configuration example of a linear PCM audio packet. In the Linear PCM audio packet, stream_id field = 1011 1101b indicates private_stream_1, and the contents of Note 2 are indicated by fields ‘01’ = 01b, P-STD_buffer_scale = 1, and P-STD_buffer_size = 392.

  Here, Private data area is sub_stream_id = 1010 0 *** b (*** = Decoding Audio stream number), number_of_frame_headers (Note 3), first_access_unit_pointer (Note 4), audio_emphasis_flag (Note 5), audio_mute_flag (Note 6), reserved, audio_frame_number (Note 7), quantization_word_length (Note 8), audio_sampling_frequency (Note 9), reserved, number_of_audio_channels (Note 10), and dynamic_range_control (Note 11) ing.

  Note 2: In each EVOB, these fields appear in the first packet and are prohibited in subsequent packets in each private_stream_1 packets sequence identified by the same sub_stream_id (note 2 field appears) . The total of target buffers for Presentation Data defined as private_stream_1 is described for P-STD buffer size.

  Note 3: “number_of_frame_headers” describes the number of audio frames that have the first byte in the corresponding A_PKT.

  Note 4: The access unit here is an audio frame. The first access unit is the first audio frame having the first byte of the audio frame, and is specified by the PTS of the corresponding A_PCK. “first_access_unit_pointer” describes the first byte address of the first access unit with the relative block number RBN from the last byte of the corresponding information. If the first byte of this first access unit does not exist, (0000h) is entered in “first_access_unit_pointer”.

  Note 5: "audio_emphasis_flag" describes the state of emphasis (emphasis off at 0b; emphasis on at 1b). For example, if “audio_sampling_frequency” is 96 kHz, “emphasis off” is described in this field. This emphasis applies to all audio samples decoded from the first access unit.

  Note 6: “audio_mute_flag” describes the state of mute while all data in the audio frame is zero (0b mute off; 1b mute on). This mute applies to all audio samples decoded from the first access unit.

  Note 7: “audio_frame_number” describes the frame number (number between 0 and 19) of the first access unit in the Group of audio frame (GOF). If there is no first byte in the access unit, “11111b” is written in “audio_frame_number”.

  Note 8: “quantization_word_length” describes which word-length of audio samples is quantized below.

16 bits at 00b
20 bits at 01b
24 bits in 10b
Reserved in 11b
Note 9: “audio_sampling_frequency” describes the sampling frequency of the audio sample.

48 kHz at 00b
96 kHz at 01b
Reserved in Others
Note 10: “number_of_audio_channels” describes number of Audio channels.

1ch (mono) at 000b
001b 2ch (stereo)
3ch at 010b
4ch at 011b
5ch at 100b
101b 6ch
7ch at 110b
8 channels at 111b
Note 11: “dynamic_range_control” describes a dynamic range control word for compressing the dynamic range from the first access unit. For example, using 8-bit "dynamic_range_control" word [b7 b6 b5 b4 b3 b2 b1 b0], upper 3 bits [b7 b6 b5] are unsigned integer X and lower 5 bits [b4 b3 b2 b1 b0] are unsigned Given an integer Y, the following gain control value is obtained:
Linear display, G = 2 ^{4- (X + Y / 30)}
(0 ≤ X ≤ 7, 0 ≤ Y ≤ 29)
In dB display, G = 24.082-6.0206 X-0.2007 Y
(0 ≤ X ≤ 7, 0 ≤ Y ≤ 29)
When dynamic range control is not applied, the value of “dynamic_range_control” is fixed to “1000 0000b”.

  The dynamic range control value G is preferably applied (unifiedly) to all audio samples decoded from the first access unit.

  FIG. 205 is a diagram for explaining a configuration example of an audio packet of MPEG audio. In MPEG audio audio packet, stream_id field = 1100 0 *** b or 1101 0 *** b indicates MPEG audio stream (*** = Decoding Audio stream number (Note 1)), and '01' , P-STD_buffer_scale, and P-STD_buffer_size fields.

Note 1: For "stream_id" = 1100 0 *** b, the packets contain one of the following:
MPEG-1 audio stream or
If MPEG-2 extension audio stream does not exist, MPEG-2 audio stream or
MPEG-2 main audio stream if MPEG-2 extension audio stream exists.

  When “stream_id” = 11101 0 *** b, the packets include an MPEG-2 extension audio stream.

  FIG. 206 is a diagram illustrating a configuration example of the advanced pack (ADV_PCK). ADV_PCK has a pack header and an Advanced packet (ADV_PKT). Advanced data (Advanced stream) is aligned to logical block boundaries. Only in the final pack of Advanced data (Advanced stream), ADV_PCK can have padding packet or stuffing bytes. Thereby, when the ADV_PCK length including the final data of the Advanced stream is smaller than 2048 bytes, the pack can be adjusted to be 2048 bytes. The stream_id of this ADV_PKT is, for example, 1011 1111b (private_stream_2), and the sub_stream_id is, for example, 1000 0000b.

  FIG. 207 is a diagram for explaining a configuration example of the advanced packet. In this advanced packet, the packet_start_code_prefix field has a value of 00 0001h, the stream_id field has a value of 1011 1111b and indicates private_stream_2, and includes a PES_packet_length field. In addition, Advanced packet has Private data area, sub_stream_id field indicates Advanced stream with a value of 1000 0000b, PES_scrambling_control field has a value of 00b or 01b (Note 1), and ADV_PKT_STATUS field has 00b, 01b or It has a value of 10b (Note 2).

  Note 1: "PES_scrambling_control" describes the copyright status of the pack containing this advanced packet. 00b indicates that the pack does not have a specific data structure for the copyright protection system, and 01b It is shown that the pack has a specific data structure for the copyright protection system.

  Note 2: ADV_PKT_STATUS describes the position of the corresponding packet (advanced packet) in the Advanced stream. 00b indicates that the corresponding packet is neither the first packet nor the last packet in the Advanced stream. It is indicated that it is the first packet in the Advanced stream, and 10b indicates that the corresponding packet is the last packet in the Advanced stream.

  FIG. 208 shows a restriction example of the MPEG-2 video for the main video stream, FIG. 209 shows a restriction example of the MPEG-2 video for the sub video stream, and FIG. 210 shows a restriction of the MPEG-4 AVC video for the main video stream. 211 shows an example of restrictions on MPEG-4 AVC video for sub video streams, FIG. 212 shows an example of restrictions on SMPTEVC-1 video for main video streams, and FIG. 213 shows SMPTEVC- for sub video streams A restriction example of one video is shown.

  FIG. 214 is a time map having time map information (TMAPI) used as a component for converting the playback time in the secondary enhanced video object (S-EVOB) into the address of the corresponding enhanced video object unit (EVOBU). FIG. 215 is a diagram illustrating a list of pack types in the secondary enhanced video object. 216 shows a configuration example of the secondary enhanced video object (S-EVOB), FIG. 217 shows a configuration example of the stream id and the stream id extension, and FIG. 218 shows a configuration example of the private stream 1 substream id. 219 shows a configuration example of the private stream 2 substream id, FIG. 220 shows a JPEG data restriction example, FIG. 221 shows a JPEG marker format configuration example, and FIG. 222 shows PNG data. 223 shows a configuration example of PNG chunk, FIG. 224 shows a configuration example of critical PNG chunk (Critical PNG Chunks), and FIG. 225 shows a configuration of backup PNG chunk (Ancillary PNG Chunks). FIG. 226 shows an example of the configuration of the MNG decoder, and FIG. , FIG. 228 shows a configuration example of a critical MNG control chunk (Critical MNG Control Chunks), and FIG. 229 shows a configuration example of a critical MNG image definition chunk (Critical MNG Image Defining Chunks). 230 shows a configuration example of a critical MNG image display chunk (Critical MNG Image Displaying Chunks), FIG. 231 shows a configuration example of a JNG chunk, and FIG. 232 shows a configuration example of a critical JNG chunk (Critical JNG Chunks). FIG. 233 shows a configuration example of a spare JNG chunk (Ancillary JNG Chunks), and FIG. 234 shows a configuration example of a font system model.

  FIG. 235 is a diagram for explaining the relationship between pieces of information related to the playlist, and illustrates the relationship of Advanced Content arranged on the disc. One Startup file existing in the Advanced Content recording area on the disc determines one from one or more Playlists. The determined playlist has three descriptions: Application (Object Mapping), reference to EVOB TMAP file on disk or network (Playback Sequence), and Player settings (Configuration Information). .

  Also, there is only one playlist specified by Startup, and when the Playlist is changed by Markup in Application, it is completely replaced. The Application specified by Playlist has an XML file for specifying a resource used in Application called Loading Information for each Application.

  FIG. 236 is a diagram for describing a configuration example of a playlist. Object Mapping, Playback Sequence, and Configuration are each described with three areas specified below the root element.

This playlist file can contain the following information:
* Object Mapping Information (information for playback objects in each title and mapped on the timeline of this title);
* Playback Sequence (playback information for each title described by the title timeline);
* Configuration Information (information for system configuration such as data buffer alignment).

  FIG. 237 and FIG. 238 are explanations of the timeline used in the playlist. FIG. 237 exemplifies the arrangement of reproduction objects (Allocation of Presentation Objects) on the timeline. Here, as a unit of the timeline, a video frame unit, a second (millisecond) unit, a 90 kHz / 27 MHz base clock unit, a unit defined by SMPTE, or the like can be used. In the example of FIG. 237, two Primary Video Sets having time lengths of 1500 and 500 are prepared, and these are arranged in one time axis, 500-1500 and 2500-3000 on the timeline. . In this way, each Object can be reproduced without contradiction by placing the objects with the respective time lengths on the timeline that is one time axis. The timeline can be configured to be reset to zero for each playlist used.

  FIG. 238 is a diagram for explaining an example in the case where trick play (chapter jump or the like) is performed on the playback object on the timeline. FIG. 238 shows an example of how the time progresses on the timeline when the playback operation is actually performed. In other words, when playback starts, the time on the Timeline begins to advance * 1. When the Play button is pressed at time 300 on the timeline * 2, the time on the timeline jumps to 500 and playback of the Primary Video Set starts. After that, if the Chapter Jump button is pressed at time 700, * 3 jumps to the start position of the corresponding Chapter (here, time 1400 on the Timeline) and playback starts from there. After that, when the Pause button is clicked at time 2550 (by the player's user) * 4, the playback pauses after the button effect. If the Play button is clicked at time 2550 * 5, playback resumes.

  FIG. 239 is an example of a playlist when EVOB has an interleaved angle. EVOB has a TMAP file corresponding to each, but EVOB4 and EVOB5 which are interleaved angle blocks are written in the same TMAP file. Also, the Primary Video Set is mapped on the Timeline by designating each TMAP file with Object Mapping Information. In addition, Application, Advanced Subtitle, Additional Audio, and the like are mapped on the Timeline according to the description of Object Mapping Information in the Playlist.

  In the figure, Title that does not have Video as App1 (for example, Menu) is defined during time 0-200 on Timeline. Further, Application2 and Primary Video 1-3, Advanced Subtitle1, and Additional Audio1 are set in the period of time 200-800. In the period of time 1000-1700, Primary Video4_5, Primary Video6, PrimaryVideo7, Application 3 and 4, and Advanced Subtitle2 which are composed of EVOB4 and EVOB5 constituting the angle block are set.

  In the Playback Sequence, App1 defines Menu as one Title, App2 configures Main Movie, and App3 and App4 configure Director's cut. In addition, three chapters are defined for Main Movie and one chapter for Director's Cut.

  FIG. 240 is a diagram illustrating a configuration example of a playlist when an object includes a multi story. FIG. 240 shows an image of a playlist when a multi-story is set. By specifying TMAP in Object Mapping Information, these two titles are mapped onto Timeline. In this example, EVOB1 and EVOB3 are used in both titles, and EVOB2 and EVOB4 are interchanged to enable multi-story.

  FIG. 241 is a diagram for describing a description example of object mapping information in a playlist (when an object includes angle information). FIG. 241 is a specific example describing the Object Mapping Information of FIG.

  FIG. 242 is a view for explaining a description example of object mapping information in a playlist (when an object includes multi-story). FIG. 242 is an example in which Object Mapping Information at the time of Multi-Story setting in FIG. 240 is described. Here, the seq element means that its child elements are sequentially mapped on the Timeline, and the par element means that its child elements are simultaneously mapped on the Timeline in parallel. The track element is used to specify each Object, and the time on the Timeline is expressed using the start and end attributes.

  At this time, the end attribute can be omitted if it is continuously arranged on the Timeline as between App1 and App2 in FIG. If there is a gap between App2 and App3, it is expressed using the end attribute. Furthermore, by using the name attribute set in the seq and par elements, it is possible to display the currently playing state on the Player (display panel) or on the external monitor screen. Audio and Subtitle can be identified using the Stream number.

  FIG. 243 is a diagram for explaining a description example of a playback sequence in the playlist (when the object includes angle information), and FIG. 244 illustrates a description example of the playback sequence in the playlist (when the object includes multi-story). It is a figure explaining. FIGS. 243 and 244 are examples of playback sequences for the cases of Angle and Multi-Story of FIGS. 239 and 240, respectively. Here, title is set in the child element of playback-sequence element, and chapter is set in the child. Each period is defined using from and to attributes.

  FIG. 245 is a diagram for describing a description example of configuration information in a playlist. Here, the streaming-buffer attribute is set in Configuration so that the size of the Streaming Buffer prepared by the player (individual playback device) can be set for each Playlist, and the size of the buffer is defined by the attribute size. Naturally, once the size of the streaming buffer is determined, the size of the data cache is also determined. Other setting items include font-cache, display resolution and aspect. The attribute in the display element represents that the content (or content) referred to in the Playlist has a resolution or aspect ratio other than this and is converted into a value set by this attribute and displayed. In addition to this Configuration, you can add what you want to change for each Playlist regarding Player settings.

  FIG. 246 is a diagram for explaining an example (four examples here) of the advanced object type. Types of Advanced objects can be classified into four types as shown in FIG. First, the classification of whether playback is performed in synchronization with the Timeline or asynchronously based on its own playback time. Then, the playback start time on the Timeline is recorded in the Playlist, and the playback starts at that time (scheduled object) and the one that has any playback start time (non-scheduled object) by user operation etc. Is done.

  FIG. 247 is a diagram for describing an example of a playlist in the case of a synchronized advanced object. FIG. 247 is a diagram exemplifying the cases <1> and <2> of the above four classifications that are reproduced in synchronization with the timeline. In the figure, description is made using Effect Audio. Effect Audio1 corresponds to <1> in FIG. 248, and Effect Audio2 corresponds to <2>. Effect Audio1 is a model in which the start time and end time are defined. Effect Audio 2 has its own playback time 600, but has an arbitrary start time by a user operation or the like in a period from 1000 to 1800 that can be played.

  When App3 starts playback from time 1000 and starts playback at time 1050, playback is performed in synchronization with Timeline until time 1650 on Timeline. Similarly, when starting from time 1100, reproduction is performed synchronously until time 1700. However, there is a restriction not to perform playback beyond Application because it causes a contradiction when another Object exists. Therefore, when playback is started at time 1600, the playback time continues up to time 2000, but playback ends at time 1800, which is actually the end time of Application.

  FIG. 248 is a diagram for explaining an example of playlist description in the case of a synchronized advanced object. FIG. 248 is a description example of track elements for Effect Audio 1 and 2 used in FIG. 247 when Object is divided by Type. The choice of whether to synchronize with Timeline can be defined using the sync attribute. Whether the playback period is determined on the Timeline or whether it is selectively started within the playback possible time by a user operation or the like can be defined using the time attribute.

  FIG. 249 is a diagram for explaining an example of a playlist for an advanced object that is not synchronized. FIG. 250 is a diagram for explaining an example of a playlist description for an advanced object that is not synchronized.

  FIG. 249 shows an example of an object that does not synchronize with the timeline, that is, performs reproduction on its own time axis. Effect Audio3 is a type of <3> in FIGS. 246 and 250, and the playback start time is determined on the Timeline. Effect Audio 4 is an example of an object in which the playable time is written in the playlist with the type <4> in FIGS. 246 and 250. In this case as well, as in the case of Effect Audio2 in FIG. 247, when the playback start time is 1050 and 1100, normal playback is played until time 1650 and 1700, but when the start is time 1400, the application end time is 1800. End with. Also, since this Object is not synchronized with Timeine, playback will also end when Timeline reaches time 1800 due to fast-forwarding or the like.

  FIG. 251 is a diagram for explaining a play list for various reproductions of the advanced object. FIG. 251 is a diagram for explaining a solution when it is desired to reproduce to the end in each of cases <1>, <2>, <3>, and <4> in FIG. Hereinafter, each case of <1> and <2> synchronized with Timeline will be described.

  In the case of an object of type <1>, if it is desired to play back to the end, the playback start time is from the end of the application to the previous time (time 1400 in the figure) as much as its own playback time. Similarly, in the case of <2> Type, it is possible to reproduce until the end by setting the reproduction startable time by the previous reproduction time (time 1400 in the figure). Alternatively, it is possible to play the application to the end by extending the application playback time by its own length (time 2600 in the figure).

Next, I will explain the case of <3> and <4> that are not synchronized with Timeline
In the case of <3> and <4>, it can be dealt with by setting the setting time in advance or by setting the Application time longer. However, since it is not synchronized with Timeline, it is necessary to set the guaranteed time in consideration of the case where Timeline has advanced by processing such as fast forward.

  FIG. 252 is a diagram for explaining an example of a play list in object reproduction including bonus content. FIG. 252 is a diagram when a section not assigned as a title is set on the timeline. By making the assignment on the timeline different from the assignment of the title, it becomes possible to reproduce the portion not set as the title. For example, when expressing a bonus track, first, an unassigned portion of the title is expressed (P-Video 5). In this way, it is possible to create contents that cannot jump directly and reproduce only bonus contents.

  In this example, there is a mechanism that sets a flag when the Title is played back, and it can be determined by App3, and if it has all the flags, it can be set to jump to the time 1400 on the Timeline. By doing so, it is possible to realize a content in which only the user who has finished viewing all the playback points can play the bonus content.

  FIG. 253 is a diagram for explaining points to be noted (multiplexing rules) when an application used in an enhanced video object to be reproduced next for seamless reproduction is multiplexed with an enhanced video object currently reproduced. FIG. 254 is a diagram for explaining an example of the physical arrangement of the enhanced video object and the reproduction procedure when the application used in the enhanced video object to be reproduced next is multiplexed on the currently reproduced enhanced video object.

  FIG. 253 and FIG. 254 show an example in which MUX (multiplexing) is performed on the EVOB reproducing the Application used in the next EVOB in order to perform seamless reproduction. In FIG. 253, there are two TitleP-Video1 → 2 → 4 Main Movie and P-Video1 → 3 → 4 Director's Cut. This is represented by the reproduction procedure as shown in the lower part (b) of FIG. When transitioning from EVOB1 to the next EVOB, there are two paths, EVOB2 and EVOB3. This is controlled by describing in Playlist, but considering the physical arrangement on the disk at this time, it is necessary to MUX both App2 for EBOV2 and App3 for EVOB3 in EVOB1.

If both paths subsequently transition to EVOB4, both EBOV2 and EVOB3 must have MUXed App4 for EVOB4.

  FIG. 255 is a diagram for explaining an example in which processing for stopping (or repeating) the progress of the timeline is performed in a playlist (still setting). FIG. 256 is a diagram for explaining a description example of the object mapping information in the playlist when the process of stopping (or repeating) the timeline is performed (still setting).

  FIG. 255 shows an example in which processing for stopping or repeating the progress of Timeline is desired to be performed in Playlist. Title1 in the figure constitutes Menu. At this time, if the Application used in the Menu is executed by user operation, it takes time to analyze the script processing, and the next Title may be played back when the Timeline advances during the execution. It is done. In such a case, as shown in FIG. 256, if a user operation occurs by setting an action attribute or a return attribute for repeated playback for each object or per or seq element, script processing or object playback (Effect It is possible to stop the Timeline during (such as Audio) or return to the beginning if nothing happens until the end of the Timeline.

  FIG. 257 is a diagram for explaining a configuration example of a playlist created separately for each title. FIG. 258 is a diagram for explaining a description example of a playlist created separately for each title.

  FIG. 257 and FIG. 258 are examples in the case where another playlist is created for each title. An object is placed on the Timeline for each Title, and the Playlist has a separate description. FIG. 258 is a description of the playlist. Since it is set for each title, there is no Title element in the Playback Sequence and only the Chapter element.

  In addition, a new API (application interface) is defined to determine what is supported or not supported by Player. Using this, you can diagnose the player status and automatically select one from multiple playlists based on the API return value.

  Furthermore, a player function that displays the playback time can be considered, but if the time on the timeline is displayed as it is, there may be a case where the time cannot be continuously increased depending on the playback path. Therefore, continuous time increase is realized and displayed according to the playback path of the playback sequence. A Title that implements Menu has a process of returning the Timeline to the beginning of the Title when it is played to the end of the Title (see Fig. 256 (c)). The playback time is determined by following.

  The authoring system can create content having a playlist as described above.

  In each embodiment described above with reference to the drawings, the arrangement of information elements (for example, 310 to 318 in the example of FIG. 3) constituting the data structure is arranged in the order shown. . This arrangement can correspond to the order in which information elements are read into the playback device first when the disc 1 is played back.

  The present invention is not limited to the above-described embodiment as it is, and in the present or future implementation stage, based on the technology available at that time, various modifications may be made without departing from the spirit of the invention. Can be For example, the present invention can be applied not only to DVD-ROM videos that are currently widely used worldwide, but also to recordable / reproducible DVD-VRs (video recorders) whose demand is rapidly increasing in recent years. Furthermore, the present invention can also be applied to a playback system or recording / playback system for next-generation HD-DVD, which will soon become popular.

  Furthermore, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the above-described embodiments. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, constituent elements according to different embodiments may be appropriately combined.

The figure explaining the information content recorded on the disk-shaped information storage medium (optical disk etc.) 1 which concerns on one embodiment of this invention. The figure explaining an example of the file system which manages the content recorded on the disk-shaped information storage medium concerning one embodiment of this invention. The figure which illustrates the data structure of HD video manager information (HDVMGI) recorded on a HD video manager (HDVMG) recording area. The figure which illustrates the data structure of the HD video manager information management table (HDVMGI_MAT) contained in HD video manager information (HDVMGI), and the recording content of the category information (HDVMG_CAT) stored in this management table. The figure which illustrates the data structure of the title search pointer table (TT_SRPT) recorded on HD video manager information (HDVMGI). The figure which illustrates the data structure of HD video manager menu PGCI unit table (HDVMGM_PGCI_UT) recorded on HD video manager information (HDVMGI). The figure which illustrates the data structure of each HD video manager menu language unit (HDVMGM_LU # n). The figure which illustrates the recording content of a HDVMGM_PGC category (HDVMGM_PGC_CAT). The figure which illustrates the data structure of the parental management information table (PTL_MAIT) recorded on HD video manager information (HDVMGI). The figure which illustrates the data structure of each parental management information (PTL_MAI # n). The figure which illustrates the data structure of the HD video title set attribute information table (HDVTS_ATRT) recorded on HD video manager information (HDVMGI). The figure which illustrates the data structure of the text data manager (TXTDT_MG) recorded on HD video manager information (HDVMGI). The figure which illustrates the data structure of each text data language unit (TXTDT_LU # n). The figure which illustrates the data structure of text data (TXTDT). The figure which illustrates the data structure of the HD video manager menu cell address table (HDVMGM_C_ADT) recorded on HD video manager information (HDVMGI). The figure which illustrates the data structure of the HD video manager menu video object unit address map (HDVMGM_VOBU_ADMAP) recorded on HD video manager information (HDVMGI). The figure which illustrates the data structure of the HD menu audio object set information table (HDMENU_AOBIT) recorded on HD video manager information (HDVMGI). The figure which illustrates the data structure of the video object area | region for a menu (HDVMGM_VOBS) recorded on a HD video manager (HDVMG) recording area. The figure which illustrates the data structure of the audio object area | region for menus (HDMENU_AOBS) recorded on a HD video manager (HDVMG) recording area. The figure which illustrates the data structure of HD video title set information (HDVTSI) recorded on each HD video title set (HDVTS # n) recording area. The figure which illustrates the data structure of the HD video title set information management table (HDVTSI_MAT) recorded on HD video title set information (HDVTSI). The figure which illustrates the data structure of the HD video title set part of title search pointer table (HDVTS_PTT_SRPT) recorded on HD video title set information (HDVTSI). The figure which illustrates the data structure of the HD video title set program chain information table (HDVTS_PGCIT) recorded on HD video title set information (HDVTSI). The figure which illustrates the recording content of a HDVTS_PGC category (HDVTS_PGC_CAT). The figure which illustrates the data structure of the HD video title set menu PGCI unit table (HDVTSM_PGCI_UT) recorded on HD video title set information (HDVTSI). The figure which illustrates the data structure of each HD video title set menu language unit (HDVTSM_LU # n). The figure which illustrates the recording content of a HDVTSM_PGC category (HDVTSM_PGC_CAT). The figure which illustrates the data structure of the HD video title set time map table (HDVTS_TMAPT) recorded on HD video title set information (HDVTSI). The figure which illustrates the data structure of the HD video title set menu cell address table (HDVTSM_C_ADT) recorded on HD video title set information (HDVTSI). The figure which illustrates the data structure of the HD video title set menu video object unit address map (HDVTSM_VOBU_ADMAP) recorded on HD video title set information (HDVTSI). The figure which illustrates the data structure of the HD video title set cell address table (HDVTS_C_ADT) recorded on HD video title set information (HDVTSI). The figure which illustrates the data structure of the HD video title set video object unit address map (HDVTS_VOBU_ADMAP) recorded on HD video title set information (HDVTSI). Data structure of program chain general information (PGC_GI) included in program chain information (PGCI: corresponding to, for example, one of HDVTS_PGCI in FIG. 23), PGC graphic unit stream control table (PGC_GUST_CTLT) and resume stored in this PGCI The figure which illustrates the recording content of / audio object category (RSM & AOB_CAT). The figure which illustrates the data structure of the program chain command table (PGC_CMDT) contained in program chain information (PGCI). The figure which illustrates the content of the program chain command table information (PGC_CMDTI) contained in a program chain command table (PGC_CMDT), and the content of each resume command (RSM_CMD). The figure which illustrates the data structure of the program chain program map (PGC_PGMAP) contained in program chain information (PGCI), and the data structure of a cell position information table (C_POSIT). The figure which illustrates the data structure of the cell reproduction | regeneration information table (C_PBIT) contained in program chain information (PGCI). 1 is a block diagram illustrating an example of the internal structure of a playback apparatus for a disk-shaped information storage medium (such as an optical disk) according to an embodiment of the present invention. FIG. 39 is a block diagram illustrating a configuration example of each decoder in the apparatus of FIG. 38. The figure explaining the concept of virtual video access unit IVAU. The figure explaining the specific example of the system parameter used by one embodiment of this invention. The figure which illustrates the command list used by one embodiment of this invention. The figure which shows the specific example in each field of the command used by one embodiment of this invention. The figure which illustrates arrangement | positioning of the graphic unit GU in a video object. The figure which illustrates the data structure in a graphic unit. The figure which illustrates the header information content in a graphic unit, and the general information content. The figure explaining the example of a mask data and graphic data in a graphic unit. The figure which shows the example of a video composition containing a mask pattern. The figure explaining an example of the button position information in the graphic unit GU. The figure explaining an example of the recording content of an advanced content recording area among the information content recorded on the disk-shaped information storage medium (optical disk etc.) 1 which concerns on other embodiment of this invention. The figure explaining an example of the recording content of an advanced HD video title set (AHDVTS) recording area among the information content recorded on the disc-shaped information storage medium (optical disc etc.) 1 which concerns on other embodiment of this invention. The figure which illustrates the data structure of the advanced HD video title set information (AHDVTSI) recorded in the advanced HD video title set recording area. The figure which illustrates the data structure of the advanced HD video title set information management table (AHDVTSI_MAT) recorded in advanced HD video title set information (AHDVTSI), and the recording content of the category information (AHDVTS_CAT) stored in this management table. The figure which illustrates the data structure of the advanced HD video title set part of title search pointer table (AHDVTS_PTT_SRPT) recorded on advanced HD video title set information (AHDVTSI). The figure which illustrates the data structure of the advanced HD video title set program chain information table (AHDVTS_PGCIT) recorded in advanced HD video title set information (AHDVTSI). The figure which illustrates the data structure of the program chain general information (PGC_GI) included in the program chain information (PGCI: for example, corresponding to AHDVTS_PGCI in FIG. 55). The figure which illustrates the data structure of the advanced HD video title set cell address table (AHDVTS_C_ADT) recorded on advanced HD video title set information (AHDVTSI). The figure which illustrates the data structure of the time map information table (TMAPIT) recorded on advanced HD video title set information (AHDVTSI). The figure which illustrates the data structure of each time map information (TMAPI) contained in a time map information table (TMAPIT), and the recording content of the time map general information (TMAP_GI) stored in this time map information. The figure which illustrates the data structure of the time entry table (TM_ENT) contained in time map information (TMAPI), the number of time entries (TM_EN_Ns) stored in this time entry table, and the recording contents of the time entry (TM_EN). The figure which illustrates the recording content of the video object unit entry (VOBU_ENT), the recording content of the interleaved unit address entry (ILVU_ADR_ENT), and the recording content of the entry video object number (ENT_VOBN) included in the time map information (TMAPI). The flowchart figure explaining an example of the reproduction | regeneration procedure of advanced VTS (AHDVTS of FIG.51, FIG.74, FIG.79 etc.) according to the content of the information (Application Type) contained in management information (for example, AHDVTS_CAT of FIG. 53). The figure explaining the structure of the navigation pack (NV_PCK) arrange | positioned at the head of the data unit (EVOBU) used with the extended video object (video object in HDVTS) concerning one embodiment of this invention. The figure which illustrates the data structure of the reproduction | regeneration control information (PCI) in the navigation pack (NV_PCK) used with an extended video object. The figure which illustrates the data structure of the data search information (DSI) in the navigation pack (NV_PCK) used with an extended video object. The figure explaining the structural example of advanced VTS (AHDVTS). The figure explaining the component of the time map which concerns on one embodiment of this invention. The figure explaining the specific component of a time map. The figure which illustrates the case where a some object (for example, VOB # 2 and VOB # 3) is reproduced | regenerated using ILVU of an interleaved block. The figure explaining the time map of an ILVU area in the example of FIG. The figure explaining the time map in an interleaved block. The block diagram explaining the example of an internal structure of the reproducing | regenerating apparatus which concerns on other embodiment of this invention. Of the information content recorded on the disc-shaped information storage medium (content type 1 disc) 1 according to another embodiment of the present invention, a part of the recorded content (HDVMG_CAT) in the HD video manager (HDVMG) recording area will be described. To do. Of the information contents recorded on the disc-shaped information storage medium (content type 2 disc example 1) 1 according to another embodiment of the present invention, the data structure of the HD video manager (HDVMG) recording area (the example of FIG. A different AHDVMGI is arranged in the HDVMG). 75 is a diagram exemplifying a data structure of advanced HD video manager information (AHDVMGI) recorded in the HD video manager (HDVMG) in FIG. 74; FIG. The figure which illustrates the data structure of the advanced HD video manager information management table (AHDVMGI_MAT) included in advanced HD video manager information (AHDVMGI), and the recorded contents of the category information (HDVMG_CAT) stored in this management table. The figure which illustrates the data structure of the advanced title search pointer table (ADTT_SRPT) contained in advanced HD video manager information (AHDVMGI). The figure explaining the reproduction | regeneration model (example 1) of the disc in which advanced VTS (AHDVTS) was recorded. Of the information contents recorded on the disc-shaped information storage medium (content type 2 disc example 2) 1 according to still another embodiment of the present invention, the data structure of the video data recording area 20 and the advanced content recording area 21 will be described. To do. 80 is a diagram exemplifying a data structure of advanced HD video manager information (AHDVMGI) that can be recorded in the HD video manager (HDVMG) in FIG. 79; FIG. The data structure of the advanced HD video manager information management table (AHDVMGI_MAT) included in the advanced HD video manager information (AHDVMGI) in FIG. 80 and the recorded contents of category information (HDVMG_CAT) stored in this management table (different from FIG. 76) FIG. FIG. 80 is a diagram illustrating a data structure (contents different from FIG. 77) of an advanced title search pointer table (ADTT_SRPT) included in the advanced HD video manager information (AHDVMGI) in FIG. The figure explaining the relationship between the reproduction state of advanced VTS and the reproduction state of standard VTS. The figure explaining the reproduction control module transfer command on the DVD video reproduction engine side. The flowchart figure explaining the switching algorithm of a user command process. The figure explaining the domain transition model in the content type 2 disk (FIG. 79 etc.) with which advanced VTS and standard VTS are mixed. The figure explaining the reproduction | regeneration model (example 2) of the disc on which advanced VTS (AHDVTS) and standard VTS (HDVTS) were recorded together. The figure explaining the original reference model of the object in the disc by which advanced VTS (AHDVTS) and standard VTS (HDVTS) were recorded together. The figure explaining the shared reference model of the object in the disc by which advanced VTS (AHDVTS) and standard VTS (HDVTS) were recorded together. The figure explaining the specific example of the loading information contained in advanced content. FIG. 73 is a diagram illustrating a configuration of a buffer manager in the interactive engine of the apparatus of FIG. 72. FIG. 73 is a flowchart for explaining an example of device operation when the interactive engine of the device of FIG. 72 is activated. The figure explaining the structural example of advanced VTS with several PGC. The figure explaining the structural example of advanced VTS with one PGC. FIG. 3 is a diagram for explaining a description example (an example using chapter / PTT numbers) of a playback sequence in a playback sequence information file (for example, the PBSEQ001.XML file in FIG. 2). The figure explaining the other description example (example using a cell number) of the reproduction | regeneration sequence in reproduction | regeneration sequence information files (PBSEQ001.XML file etc.). The figure explaining the other description example (example using PGC number and chapter / PTT number) of the reproduction | regeneration sequence in reproduction | regeneration sequence information files (PBSEQ001.XML file etc.). The figure explaining the other description example (example using PGC number and cell number) of the reproduction | regeneration sequence in reproduction | regeneration sequence information files (PBSEQ001.XML file etc.). The playback sequence information file (for example, PBSEQ001.XML file in FIG. 2) is used to initialize the playback sequence of the advanced VTS by the DVD playback engine (playback by the description of the playback sequence information file instead of the playback sequence by the existing PGC information) The flowchart figure explaining an example of the process procedure for the initialization which uses a sequence. The block diagram explaining the example of an internal structure of the reproducing | regenerating apparatus which concerns on other embodiment of this invention. The figure which shows the other example of the data structure of the advanced HD video title set program chain information table (AHDVTS_PGCIT) recorded on advanced HD video title set information (AHDVTSI). FIG. 100 is a diagram exemplifying a plane configuration of overlapping output frames of modules in the video mixer of FIG. 100. The figure explaining the example in the case of one time map information (TMAPI) which does not contain a time entry, and one TMAPI is stored in one TMAP file. The figure explaining the example in case it is time map information (TMAPI) which does not include a time entry, and one or more (here, two examples) TMAPI is stored in one TMAP file. The figure explaining the structural example of the time map information for EVOB which comprises the angle arrange | positioned in an interleaved block. The figure which illustrates the data structure of the time map information table (TMAPIT) which does not contain a time entry. The figure which illustrates the data structure of time map information (TMAPI) which does not contain a time entry. The figure which illustrates the data structure of the control pack (standard GCI_PCK and advanced GCI_PCK) containing general control information (General Control Information: GCI). The figure which illustrates the data structure of general control information (GCI). The figure explaining the other example of the data structure of the advanced HD video title set information (advanced VTSI) recorded in the advanced HD video title set recording area. FIG. 110 is a diagram illustrating a data structure of an advanced HD video title set attribute information table (AHDVTS_ATRIT) stored in the advanced VTSI of FIG. 110. FIG. 110 is a diagram illustrating a data structure of an advanced HD video title set EVOB information table (AHDVTS_EVOBIT) stored in the advanced VTSI of FIG. 110. One program stream in which the primary object (movie object) and secondary object (advanced object) are multiplexed is recorded on the disc, and the advanced object (secondary object) exists as an independent separate program stream on the external communication line (Web) The figure which illustrates the case (case 1) to do. The figure explaining the decoding model of case 1. FIG. Separate program stream in which the program stream of the primary object and the program stream of the secondary object (two program streams multiplexed in pack units) are recorded on the disk and the advanced object (secondary object) is independent on the external communication line (Web) The figure which illustrates the case where it exists as (case 2-1). The figure explaining the decoding model of case 2-1. Another program in which the program stream of the primary object and the program stream of the secondary object (two program streams multiplexed in units of access units) are recorded on the disk, and the advanced object (secondary object) is independent on the external communication line (Web) The figure which illustrates the case where it exists as a stream (case 2-2). The figure explaining the decoding model of case 2-2. The figure explaining an example (when using the private stream 1 for the identification of an object) of stream ID which identifies the content of a primary object, and the content of a secondary object. 119 is a diagram illustrating a configuration of a substream ID for private stream 1 in the stream ID of FIG. 119 is a diagram illustrating a configuration of a substream ID for private stream 2 in the stream ID of FIG. The figure explaining the other example (when the private stream 3 is newly provided for the identification of an object) of stream ID which identifies the content of a primary object, and the content of a secondary object. The figure which illustrates the structure of substream ID for private stream 1 in stream ID of FIG. The figure which illustrates the structure of substream ID for private stream 2 in stream ID of FIG. The figure which illustrates the structure of substream ID for private stream 3 in stream ID of FIG. The flowchart figure explaining an example of the process sequence in the case of reproducing | regenerating a primary object and / or a secondary object from a disc and / or an external communication line (Web). The figure explaining the reproduction | regeneration path | route of the primary object and secondary object from a disc. The figure explaining the reproduction | regeneration path | route of the primary object from a disc, and the secondary object from an external communication line (Web). The figure which illustrates the data structure of the time map information table containing the type flag (TMAP_TYPE_FL) of a time map. The figure explaining the description example 1 of Markup. The figure explaining the example 2 of description of Markup. The figure explaining the example 3 of description of Markup. One program stream in which the primary object (movie object) and secondary object (advanced object) are multiplexed is recorded on the disc, and the advanced object (secondary object) exists as an independent separate program stream on the external communication line (Web) The figure which shows the other example when doing (case 1a). One program stream in which the primary object (movie object) and secondary object (advanced object) are multiplexed is recorded on the disc, and the advanced object (secondary object) exists as an independent separate program stream on the external communication line (Web) The figure which shows the further another example of the case (case 1b) to do. The figure explaining the decoding model of case 1a. The figure explaining an example of operation | movement of a smoothing buffer in the decoding model of case 1a. The figure which illustrates the outline | summary of the advanced content on a disk. The figure which illustrates the outline | summary of the reproduction | regeneration system model of advanced content. The figure explaining an example of the flow of data in the reproduction | regeneration system model of advanced content. The figure explaining the other example of the data flow in the reproduction | regeneration system model of advanced content. The figure explaining the further another example of the data flow in the reproduction | regeneration system model of advanced content. The figure explaining the further another example of the data flow in the reproduction | regeneration system model of advanced content. The figure explaining an example of the synthetic | combination model of the image output in the reproduction | regeneration system model of advanced content. The figure which shows the specific example of the synthetic | combination model of an image output. The figure explaining an example of the mixing model of the audio | voice output in the reproduction | regeneration system model of advanced content. The figure explaining an example of the user interface process in the reproduction | regeneration system model of advanced content. The flowchart figure explaining an example of the flow of the startup process after disk insertion. The figure explaining the structural example of advanced content. The figure explaining the structural example of video title set information (VTSI). The figure explaining the structural example of a video title set information management table (VTSI_MAT). The figure explaining the structural example of a video title set category (VTS_CAT). The figure explaining the structural example of a video title set enhanced video object attribute table (VTS_EVOB_ATRT). The figure explaining the structural example of video title set enhanced video object attribute table information (VTS_EVOB_ATRTI). The figure explaining the structural example of a video title set enhanced video object attribute search pointer (VTS_EVOB_ATR_SRP). The figure explaining the structural example of a video title set enhanced video object attribute (VTS_EVOB_ATR). The figure explaining the structural example of the enhanced video object attribute (EVOB_ATR). The figure explaining the structural example of the main video attribute (EVOB_VM_ATR) of an enhanced video object. The figure explaining the specific example of the parameter in the main video attribute (EVOB_VM_ATR) of an enhanced video object. The figure explaining the structural example of the sub video attribute (EVOB_VS_ATR) of an enhanced video object. The figure explaining the structural example of the number (EVOB_AMST_Ns) of the main audio streams in an enhanced video object. The figure explaining the structural example of the attribute table (EVOB_AMST_ATRT) of the main audio stream of an enhanced video object. The figure explaining the structural example of the attribute (EVOB_AMST_ATR) of the main audio stream of each enhanced video object. The figure explaining the specific example of the parameter in the attribute (EVOB_AMST_ATR) of the main audio stream of an enhanced video object. The figure explaining the structural example of the attribute table (EVOB_MU_AMST_ATRT) of the multi-channel main audio stream of an enhanced video object. The figure explaining the structural example of the attribute (EVOB_MU_AMST_ATR) of the multi-channel main audio stream of each enhanced video object. The figure explaining the structural example of the number (EVOB_ASST_Ns) of the sub audio streams in an enhanced video object. The figure explaining the structural example of the attribute table (EVOB_ASST_ATRT) of the sub audio stream of an enhanced video object. The figure explaining the structural example of the attribute (EVOB_ASST_ATR) of the sub audio stream of each enhanced video object. The figure explaining the structural example of the number (EVOB_SPST_Ns) of the sub video streams in an enhanced video object. The figure explaining the structural example of the attribute table (EVOB_SPST_ATRT) of the sub video stream of an enhanced video object. The figure explaining the structural example of the attribute (EVOB_SPST_ATR) of the sub video stream of each enhanced video object. The figure explaining the specific example of the parameter in the attribute (EVOB_AMST_ATR) of the main audio stream of an enhanced video object. The figure explaining the structural example of the palette (EVOB_SDSP_PLT) which describes the brightness | luminance / color-difference signal (256 sets) shared by all the sub video streams for SD in each enhanced video object. The figure explaining the structural example of the palette (EVOB_HDSP_PLT) which describes the luminance / chrominance signal (256 sets) shared by all the HD sub-picture streams in each enhanced video object. The figure explaining the structural example of a video title set enhanced video object information table (VTS_EVOBIT). The figure explaining the structural example of video title set enhanced video object information table information (VTS_EVOBITI). The figure explaining the structural example of a video title set enhanced video object information search pointer (VTS_EVOBI_SRP). The figure explaining the structural example of video title set enhanced video object information (VTS_EVOBI). The figure explaining the example of the parameter in video title set enhanced video object information (VTS_EVOBI). Time map (TMAP) of time map information (TMAPI) used as a component for converting the playback time in the primary enhanced video object (P-EVOB) into the address of the corresponding enhanced video object unit (EVOBU) The figure explaining the structural example. The figure explaining the structural example of time map general information (TMAP_GI). The figure explaining the structural example of a time map type (TMAP_TYPE). The figure explaining the structural example of an angle type (AGL_TYPE). The figure explaining the structural example of a time map information search pointer (TMAPI_SRP). The figure explaining the structural example of the information (EVOBSINF) of the (one or several) enhanced video object which belongs to a corresponding time map. The figure explaining the structural example of the time map information (TMAPI) which starts with the entry information (EVOBU_ENTI # 1- # i) of one or more enhanced video object units. The figure explaining the structural example of enhanced video object unit entry information (EVOBU_ENTI). The figure explaining the structural example of interleaved unit information (ILVUI) which exists when time map information is for interleaved blocks. The figure explaining the structural example of interleaved unit entry information (ILVU_ENTI). The figure which lists and describes the pack type in an enhanced video object. The figure explaining the example of a restriction | limiting of the transfer rate with respect to the stream of an enhanced video object. The figure explaining the structural example of a primary enhanced video object (P-EVOB). The figure explaining the example of a restriction | limiting of each element with respect to the stream of a primary enhanced video object. The figure explaining the structural example of stream id and stream id extension. The figure explaining the structural example of the substream id for private streams 1. The figure explaining the structural example of the substream id for private streams 2. The figure explaining the structural example of the navigation pack (NV_PCK) aligned at the head of an enhanced video object unit (EVOBU). The figure explaining the structural example of the system header of a navigation pack. The figure explaining the structural example of the buffer size boundary (P-STD_buf_size_bound) for MPEG-2 / MPEG-4AVC / SMPTEVC-1 video elementary stream. The figure explaining the structural example of a general control information (GCI) packet. The figure explaining the structural example of a data search information (DSI) packet. The figure explaining the structural example of the video packet of MPEG-2 or MPEG-4AVC. The figure explaining the structural example of the video packet of SMPTEVC-1. The figure explaining the structural example of the audio packet of linear PCM. The figure explaining the structural example of the audio packet of MPEG audio. The figure explaining the structural example of advanced pack (ADV_PCK). The figure explaining the structural example of an advanced packet. The figure explaining the restriction example of the MPEG-2 video for main video streams. The figure explaining the restriction example of the MPEG-2 video for sub video streams. The figure explaining the example of restrictions of the MPEG-4AVC video for main video streams. The figure explaining the restriction example of the MPEG-4AVC video for sub video streams. The figure explaining the example of a restriction | limiting of the SMPTEVC-1 video for main video streams. The figure explaining the example of a restriction | limiting of the SMPTEVC-1 video for sub video streams. A time map (TMAP) composed of time map information (TMAPI) used for converting the playback time in the secondary enhanced video object (S-EVOB) into the address of the corresponding enhanced video object unit (EVOBU). The figure explaining the structural example. The figure which lists and demonstrates the pack type in a secondary enhanced video object. The figure explaining the structural example of a secondary enhanced video object (S-EVOB). The figure explaining the structural example of stream id and stream id extension. The figure explaining the structural example of the substream id for private streams 1. The figure explaining the structural example of the substream id for private streams 2. The figure explaining the restriction example of JPEG data. The figure explaining the structural example of a JPEG marker format. The figure explaining the example of a restriction | limiting of PNG data. The figure explaining the structural example of a PNG chunk. The figure explaining the structural example of critical PNG Chunks (Critical PNG Chunks). The figure explaining the example of a structure of a reserve PNG chunk (Ancillary PNG Chunks). The figure explaining the structural example of a MNG decoder. The figure explaining the structural example of a MNG chunk. The figure explaining the structural example of a critical MNG control chunk (Critical MNG Control Chunks). The figure explaining the structural example of a critical MNG image defining chunk (Critical MNG Image Defining Chunks). The figure explaining the structural example of a critical MNG image display chunk (Critical MNG Image Displaying Chunks). The figure explaining the structural example of a JNG chunk. The figure explaining the structural example of a critical JNG chunk (Critical JNG Chunks). The figure explaining the structural example of a spare JNG chunk (Ancillary JNG Chunks). The figure explaining the structural example of a font system model. The figure explaining the relationship between each information relevant to a play list. The figure explaining the structural example of a play list. The figure explaining the example of arrangement | positioning (Allocation of Presentation Object) on the timeline. The figure explaining the example in case trick play (chapter jump etc.) of a reproduction | regeneration object is performed on a timeline. The figure explaining the structural example of a playlist in case an object contains angle information. The figure explaining the structural example of a playlist in case an object contains a multi story. The figure explaining the example of description of the object mapping information in a play list (when an object contains angle information). The figure explaining the example of description of the object mapping information in a play list (when an object contains a multi story). The figure explaining the example of a description of the reproduction | regeneration sequence in a play list (when an object contains angle information). The figure explaining the example of a description of the reproduction | regeneration sequence in a play list (when an object contains a multi story). The figure explaining the example of a description of the configuration information in a play list. The figure explaining the example (here 4 examples) of an advanced object type. The figure explaining the example of a play list in the case of a synchronized advanced object. The figure explaining the example of a play list description in the case of a synchronized advanced object. The figure explaining the example of a play list in the case of the advanced object which is not synchronized. The figure explaining the example of a playlist description in the case of the advanced object which is not synchronized. The figure explaining the play list with respect to various reproduction | regeneration of an advanced object. The figure explaining the example of a play list in object reproduction containing bonus contents. The figure explaining the consideration (multiplexing rule) when multiplexing the application used by the enhanced video object reproduced | regenerated next in order to perform seamless reproduction | regeneration to the enhanced video object currently reproduced | regenerated. The figure explaining the example of the physical arrangement | positioning of the enhanced video object, and its reproduction | regeneration procedure in the case of multiplexing the application used with the enhanced video object reproduced | regenerated next to the enhanced video object currently reproduced | regenerated. The figure explaining the example in the case of performing the process which stops progress (or repeats) of a timeline with a play list (still setting). The figure explaining the example of description of the object mapping information in a play list in the case of performing the process which stops progress (or iterates) of a timeline (still setting). The figure explaining the structural example of the playlist produced separately for every title. The figure explaining the description example of the playlist produced separately for every title.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 ... Information storage medium (playback-only or recording / reproducing optical disk); 10 ... Lead-in area; 11 ... Volume / file structure information area (file information area); 12 ... Data area; 13 ... Lead-out area; Data recording area; 21 ... Advanced content recording area; 21A ... Markup / Script language recording area; 21B ... Movie recording area; 21C ... Animation / still picture recording area; 21D ... Audio recording area; 21E ... Font recording area; Computer information recording area; 30 ... High Definition video manager recording area (HDVMG); 31 ... High Definition video manager information recording area (HDVMGI); 34 ... High Definition video manager information backup area (HDVMGI_BUP); 40 ... High Definition video title set Recording area HDVTS # 1- # n); 50 ... Advanced High Definition video title set recording area (AHDVTS); 100 ... Video playback engine; 200 ... Interactive engine; 400 ... User interface part; 500 ... Server part; 211A ... Loading information recording area; 212A ... Markup recording area; 213A ... Script recording area; 214A ... Stylesheet recording area; 215A ... Recording sequence information (PBSEQ001.XML, etc.) recording area .

Claims (4)

A management area for recording management information, a video data recording area including an object area for recording an object managed by the management information, and a recording area for advanced content including information different from the recording contents of the video data recording area In an information storage medium having a data area to be stored and a file information area for storing file information corresponding to the recorded contents of the data area,
An information storage medium configured such that the data area stores information of a playlist that is first played when the information storage medium has the advanced content.   The information of the playlist is included for each title for the object to be reproduced and is mapped on the time axis of the title, the reproduction information for each title described by the time axis, and the reproduction system The information storage medium according to claim 1, wherein the information storage medium is configured to include information indicating a system configuration. A management area for recording management information, a video data recording area including an object area for recording an object managed by the management information, and a recording area for advanced content including information different from the recording contents of the video data recording area A data area to be stored, and a file information area to store file information corresponding to the recorded contents of the data area, wherein the play list describes information of a playlist to be reproduced first when having the advanced content In a method using an information storage medium configured to store information of a list in the data area,
A recording method for recording information of the playlist in a recording area of the advanced content. A management area for recording management information, a video data recording area including an object area for recording an object managed by the management information, and a recording area for advanced content including information different from the recording contents of the video data recording area A data area to be stored, and a file information area to store file information corresponding to the recorded contents of the data area, wherein the play list describes information of a playlist to be reproduced first when having the advanced content In a method using an information storage medium configured to store information of a list in the data area,
Play the file containing the playlist information from the data area,
A reproduction method for reproducing the object from the data area.

Images