JP2010011505A - Information recording media, information recording method, information reproducing method, information recorder, and information reproducer - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enable the system to manage information where both information managements on contents recorded and reproduced by users and those on contents distributed by contents providers are intended to be compatible. <P>SOLUTION: The system includes a file structure to manage a first precision video information (HD_DVD-VR;HDVR_VOB/HDVR_SOB) the users can record and a second precision video information (HD_DVD-VIDEO;ADV_OBJ) the contents providers can provide, wherein a management area is configured so as to further include management information (VIDEO_PLAYLIST, VTSI) that manages the reproduction of digital stream signals including the second precision video information (HD_DVD-VIDEO). <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to an information recording medium (or data structure), an information recording / reproducing method, and an information recording / reproducing apparatus suitable for recording and reproducing a digital stream signal used in digital TV broadcasting and the like.

  In recent years, TV broadcasting has entered the era of digital broadcasting in which high-definition programs (high-definition AV information programs) are the main broadcast contents. The BS digital TV broadcast currently being implemented (and the terrestrial digital TV broadcast that will soon be implemented) employs an MPEG2 transport stream (hereinafter abbreviated as MPEG-TS as appropriate). In the field of digital broadcasting using moving images, MPEG-TS will continue to be used as standard. With the start of such digital TV broadcasting, market needs for streamers capable of recording digital TV broadcast content as they are are increasing.

  As an example of a streamer using an optical disk such as a DVD-RAM, there is a “recording / reproducing apparatus” disclosed in Patent Document 1 (Patent Document 1).

JP 2002-84479 A

  For example, if a long-time music program with short news inserted in the middle (such as NHK red-and-white song battle that is BS digital broadcast at the end of the year) was stream-recorded with a news cut (pause recording at the news part), the news was cut. The stream object of the recorded program is divided into two parts. In such a case, the two stream objects are usually continuously adjacent to each other physically on the recording medium, but may be recorded discontinuously at physically separated locations. In this example, although two stream objects are physically continuous, the playback time of the content is logically continuous. The same applies when a movie with a CM inserted is stream-recorded with a CM cut. Even if a physical discontinuity occurs between multiple stream objects at the CM cut portion, the entire movie content is played back. Time is logically continuous.

  On the other hand, for example, when program A of channel X is stream-recorded and program B of channel Y is subsequently stream-recorded, the recording positions of the stream object of program A and the stream object of program B are physically continuous. However, the playback times of these contents are not continuous (logically discontinuous).

  In this way, when stream recording is performed by a plurality of stream objects, logical continuity (continuity of playback time within the same program) is not established between adjacent stream objects, instead of physical continuity. Whether or not there is an effect on the decoding process during playback (system time clock STC setting process, etc.). Specifically, if the STC setting is inappropriately performed without knowing the continuity of the playback time (such as STC reset), the playback moves from the end of the first half stream object of the same program to the beginning of the second half stream object. In addition, there is a possibility that a long waiting time due to the still image display occurs.

  Note that information such as PSI (Program Specific Information) and SI (Service Information) may be included in the recording target (digital broadcasting, etc.), but consideration has been given to cases where PSI or SI is unknown. Not. Various resolutions of video information to be recorded can be included, but no consideration is given to the case where one of the horizontal resolution and the vertical resolution (horizontal resolution) is unknown in the designation of resolution.

  In addition, high-definition content with various added values is expected to be distributed (commercially available) by content providers in the near future, and compatibility (compatibility) with such high-definition content is also expected for future high-definition recorders. Is required.

  One of the problems of the present invention is to enable not only information management of contents recorded and reproduced by a user but also information management aiming at compatibility with contents distributed by a content provider.

  In one embodiment of the present invention, first high-definition video information (HD_DVD-VR; HDVR_VOB / HDVR_SOB) that can be recorded by a user and second high-definition video information (HD_DVD-VIDEO; ADV_OBJ) that can be provided by a content provider are recorded. It has a file structure to be managed (FIG. 79), and records a predetermined digital stream signal including the first high-definition video information (HD_DVD-VR) and the second high-definition video information (HD_DVD-VIDEO). A structured information recording medium (100 in FIG. 1) is used. Here, the information recording medium has a management area and a data area, and the data area is configured so that the data of the digital stream signal can be divided and recorded into a plurality of objects (HDVR_VOB, HDVR_SOB, ADV_OBJ). The management area has management information (ESOB-related file) for each transmission source of the digital stream signal including the first high-definition video information (HD_DVD-VR) or for each broadcasting method of the digital stream signal. Time map information (VSOB-related file in FIG. 79) is included for each transmission source of the digital stream signal including the first high-definition video information (HD_DVD-VR) or for each broadcasting method of the digital stream signal. The management area is further configured to include management information (VIDEO_PLAYLIST, VTSI) for managing reproduction of the digital stream signal including the second high-definition video information (HD_DVD-VIDEO).

  Playback of the digital stream signal including the second high-definition video information (HD_DVD-VIDEO) in addition to the management information (ESOB-related file in FIG. 79) of the first high-definition video information (HD_DVD-VR) in the management area By providing management information (VIDEO_PLAYLIST, VTSI) for managing video content, both content (HD_DVD-VR) recorded and reproduced by the user and content (HD_DVD-VIDEO) provided by the provider can be managed together.

The figure explaining the data structure which concerns on one embodiment of this invention. The figure explaining the relationship between the reproduction | regeneration management information layer in the data structure which concerns on one embodiment of this invention, an object management information layer, and an object layer. The figure explaining the file structure concerning one embodiment of this invention. The figure explaining an example of how some management information (HDVR_MGI) recorded on the AV data management information recording area 130 is comprised. The figure explaining the specific example of DISC_RSM_MRKI. The figure explaining the specific example of EX_DISC_REP_PICI. The figure explaining the specific example of EX_PL_SRPT. The figure explaining an example of how the other part (EX_M_AVFIT) of one management information (HDVR_MG) is comprised in the data structure which concerns on one embodiment of this invention. The figure explaining the specific example of EVOB_TMAP_GI. The figure explaining an example of how EX_M_VOB_STI is comprised. The figure explaining an example of how V_ATR is comprised. The figure explaining an example of how ESTR_FIT is comprised. The figure explaining the specific example of HR_SFIxx.IFO. The figure explaining an example of how ESOBI_GI is comprised. The figure explaining the various information contained in ESOBI_GI. The figure explaining an example of how ESOB_ESI is comprised. The figure explaining an example of how ESOB_V_ESI is comprised, and an example of how the video attribute V_ATTR contained in this ESOB_V_ESI is comprised. The figure explaining an example of how ESOB_A_ESI is comprised, and an example of how the audio attribute AUDIO_ATTR contained in this ESOB_A_ESI is comprised. The figure explaining an example of how ESOB_OTHER_ESI is comprised. The figure explaining the specific example of ESOB_DCNI. The figure explaining an example of how ESOB_GPI is comprised. The figure explaining an example of how ESOB_GPI_GI, GPI_SRP #, and GPI # are comprised. The figure explaining an example of how ESOB_CONNI is comprised. The figure explaining an example of how ESOB_TMAP (type A) is comprised. The figure explaining an example of how ESOB_TMAP (type B) is comprised. The figure explaining an example of how HR_VTMAP.IFO and HR_STMAPx.IFO contained in a DVD_HDVR directory are comprised. The figure explaining an example of how EX_VTMAPTI, each EX_VTMAP_SRP #, and each EX_VTMAPI are comprised. The figure explaining an example of how the contents of each EVOBU_ENT # are comprised. The figure explaining an example of how the various information contained in STMAPT (type A) is comprised. The figure explaining an example of how the various information contained in STMAPT (type B) is comprised. The figure explaining an example (example of type A) how the content of ESOBU_ENT # is comprised. The figure explaining an example of how the PGC information (EX_ORG_PGC information and EX playlist information / EX_UD_PGC information) included in HDVR_VMG is configured. The figure explaining an example of how EX_PGC information is comprised. The figure explaining the specific example of EX_CI. The figure explaining the specific example of C_EPI. The figure explaining an example of how PTM of ESOB (or EVOB) is constituted. The figure explaining an example of how the data unit (ESOBU) for stream objects is comprised. The figure explaining the specific example of PKT_GRP_GI. The figure explaining the example of how copy management information CCI # contained in a packet group header is comprised. The figure explaining the specific example of MNI. The figure explaining an example of how EVOBU is comprised. The figure explaining an example of how GCI of EVOBU is comprised. The figure explaining an example of how EX_PCI of EVOBU is comprised. The figure explaining an example of how EX_DSI of EVOBU is comprised. The figure explaining an example of how EX_RDI in the case of Interoperability VTS / VR_VOB is comprised. The figure explaining the file structure which concerns on other embodiment of this invention. The figure explaining an example of the relationship between ESOB_SZ and ESOB_S_PKT_POS. The figure explaining an example of an ESOBU cluster. The figure explaining an example of the relationship between AT_SOBU and a packet. The figure explaining an example of a relationship with ESOBU_SZ, ESOBU_S_PKT_POS, and ES_LAST_SOBU_E_PKT_POS. The figure explaining an example of a relationship between AT_SOBU_SZ and AT_SOBU_S_PKT_POS. The figure explaining an example of the relationship between TS Packet and Packet Group. The block diagram explaining an example of the apparatus which records and reproduces AV information (digital TV broadcast program etc.) on an information recording medium (optical disc, hard disk, etc.) using the data structure which concerns on one embodiment of this invention. The figure explaining an example of the system model of a recorder. The flowchart figure explaining an example of the whole operation | movement of an apparatus (whole operation process flow). The flowchart figure explaining an example of an edit process (ST28) (edit operation process flow). The flowchart figure explaining an example (the 1) of video recording operation. FIG. 6 is a flowchart for explaining an example (part 2) of the recording operation of the first embodiment. The flowchart (ESOB cut process flow) explaining an example of the ESOB cut process (ST160). The flowchart figure (buffer capture process flow) explaining an example of a buffer capture process (ST130). The flowchart figure (PKT_GRP_GI setting process flow) explaining an example of a packet group general information setting process (ST1340). A flow chart explaining an example of stream information (ESI) creation processing (ST120) (ESI setting processing flow). The flowchart figure explaining an example of the stream file information (ESTR_FI) creation process in a video recording end process (ST150). The flowchart figure explaining an example of GPI setting process ST1530. The flowchart figure explaining TMAP setting process ST1540. The flowchart figure explaining EVOB / ESOB structure setting process ST15400. The flowchart figure explaining CP_CTL_INFO (CCI) creation process ST1220. The flowchart figure (program setting process flow) explaining an example of the program chain (PGC) creation process (a program setting process is included) in a video recording end process (ST150). The flowchart figure explaining an example of reproduction | regeneration operation | movement (whole reproduction | regeneration operation | movement flow). The flowchart figure explaining a decoder setting process (ST217). The flowchart figure explaining an example of the process at the time of cell reproduction | regeneration. The flowchart figure explaining ESOB continuous check processing (ST2201). The flowchart figure explaining an example of the data transfer process from buffer RAM to a decoder. The flowchart figure explaining an example of GP switching processing. The flowchart figure explaining an example of a discontinue process. The flowchart figure explaining an example of a skip process. The figure explaining the other example of FIG. 3 or FIG. The figure explaining the other example of FIG. FIG. 78 is a diagram for explaining another example of FIG. 77. FIG. 25 is a diagram illustrating another example of FIG. FIG. 26 is a diagram illustrating another example of FIG. The figure explaining the example of a TMAP file structure. FIG. 28 is a diagram illustrating another example of FIG. The figure explaining the other example of FIG. The figure explaining the other example of FIG. FIG. 37 is a diagram illustrating another example of FIG. The figure explaining the other example of FIG. The figure explaining the conversion example of interoperable content. The figure explaining the example of the conversion table figure (the 1) from HD_VR to VTSI. The figure explaining the example of the conversion table figure (the 2) from HD_VR to VTSI. The figure explaining the example of the conversion table figure (the 3) from HD_VR to VTSI. The figure explaining the example of the conversion table figure (the 4) from HD_VR to VTSI. The flowchart figure explaining the example of a process timing of interoperable content creation. The flowchart figure explaining an example of an interoperable content creation process. The figure explaining the PGC structural example of HD_VR. The figure explaining the special case of CNT_SEG. The figure explaining an example of the starting position relationship of SOB according to ESOB_CONNI. The figure explaining an example of the start position relationship of SOB according to ESOB_CONNI at the time of editing. The figure explaining an example of the end position relationship of SOB according to ESOB_CONNI. The figure explaining an example of the end position relationship of SOB according to ESOB_CONNI at the time of editing.

  Hereinafter, various embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram for explaining a data structure according to an embodiment of the present invention. As a representative example of a recordable or re-writable information recording medium, a DVD disk (a DVD ± R, DVD having a single recording layer or a plurality of recording layers using a red laser having a wavelength of around 650 nm or a blue-violet or blue laser having a wavelength of 405 nm or less) ± RW, DVD-RAM, etc.) 100. As shown in FIG. 1, the disk 100 includes a volume / file structure information area 111 containing a file system and a data area 112 for actually recording a data file. The file system includes information indicating which file is recorded where.

  The data area 112 includes areas 120 and 122 for recording by a general computer and an area 121 for recording AV data. In the AV data recording area 121, an AV data management information area 130 having a video manager (VMG) file for managing AV data and an object data file conforming to the DVD-Video (ROM Video) standard are recorded. ROM_Video object group recording area 131, VR object group recording area 132 where object data (ESOBS: Extended Video Object Set) files (VRO files) conforming to the video recording (VR) standard are recorded, and digital broadcasting It includes a recording area 133 in which stream object data (ESOBS: Extended Stream Object Set) files (SRO files) in which objects are recorded are recorded. Note that the recording standard for the SRO file is appropriately described as a stream recording (SR) standard.

  Here, DVD-Video (ROM Video) is a video title set (VIDEO-TS), and recording / playback DVD (DVD-RTR) is DVD-RTAV. A new DVD standard file compatible with digital broadcasting to be described is stored in a directory called DVD_HDVR, for example (described later with reference to FIG. 3).

  That is, a VMG file for managing data, a VRO that is an object file for analog recording such as analog broadcasting and line input, and an SRO file that is an object of digital broadcasting are recorded in a directory called DVD_HDVR (FIG. 3). The SRO file becomes ESOBS.

  FIG. 2 is a diagram for explaining the relationship among the reproduction management information layer, the object management information layer, and the object layer in the data structure according to the embodiment of the present invention. As shown in FIG. 2, SR management data is recorded in a VMG file common to VR, SR is controlled in common with VR, SR and VR are linked in units of cells, and designation of playback location is in units of playback time Specified by. This management data is referred to as VR_MANEGER.IFO (see FIG. 3). Here, when making TMAPT into another file, as shown in FIG. 3, HR_VTMAP.IFO and HR_STMAP.IFO and backup files HR_VTMAP.BUP and HR_STMAP.BUP are added.

  The structure of ESOBS is composed of one or more ESOBs 141, and the ESOB corresponds to, for example, one program. The ESOB is composed of one or more ESOBUs (Extended Stream object units), and the ESOBU corresponds to object data for a certain time interval (which varies depending on the value of ESOBU_PB_TM_RNG) or one or more GOP data. However, if the transfer rate is low, 1 GOP may not be sent within 1 s (1 second). In VR, it can be set freely because it is internal encoding. It may be unclear whether or not In addition, there may be a case where the rate is high and I pictures are frequently sent. In that case, the ESOBU is frequently divided, and accordingly, the management information of the ESOBU increases, and there is a possibility that the entire management information is enlarged. Therefore, it is appropriate to divide the ESOBU by a fixed time interval determined by the total recording time (the minimum limit is other than the last ESOBU of the ESOB, where the delimiter is a picture unit: every 1 s for example) or by one or more GOPs.

  When management information is constructed based on PATS when the stream cannot be analyzed, AT_SOBU (Arrival Time based SOBU) is delimited by the time interval indicated by AT_SOBU_TM. There are two types of AT_SOBU_TM: when specified in seconds (see FIG. 25) and when specified with a 27 MHz count value.

  In one embodiment of the present invention, one ESOBU is composed of one or more packet groups, and one packet group is made to correspond to 16 (or 32) logical blocks (1 LB = 2048 bytes; 16 LB = 32640 bytes). it can. Each packet group is composed of a packet group header and TS packets (170 packets). The arrival time (Arrival Time) of each TS packet can be represented by a PATS (Packet Arrival Time Stamp: 4 bytes) arranged before each TS packet.

  Here, the arrival time of the TS packet must be set to 0 (or a predetermined value) at the start of recording and linearly counted up until the end of recording. However, STC and PATS do not always show the same value (due to differences in initial values). However, the count interval of the PATS counter must be synchronized with the count interval of the STC counter corresponding to the interval between the PCR (Program Clock Reference) capture and the next PCR capture in a state where playback synchronization is in effect. is there. The PCR is included in an adaptation field (not shown) in the MPEG-TS. The Packet Group allows up to two ESOBs to be mixed. In other words, it is not necessary to align the Packet Group for each ESOB.

  Here, the management information will be described with reference to FIGS. FIG. 3 is a view for explaining the file structure according to the embodiment of the present invention.

  As shown in FIG. 3, the HDVR directory is composed of HR_MANGER.IFO, which is a DVD management information file, VRO file, which is an analog video input object file, and SRO file for digital broadcasting. That is, stream data management information is stored in a VMG file and is managed in the same way as VR data. Specifically, stream management information is stored in an ESTR_FIT (Stream File Information Table), and a VMG file that is management information includes an ESTR_FIT (Extened Stream File Information table) in the existing DVD-VR standard management information. It has an added form.

  By the way, in a method for broadcasting (distributing) compressed moving images such as digital TV broadcasts and broadcasts using wired lines such as the Internet, the MPEG-TS method, which is a common basic format, has a packet management data portion and a payload. Divided into

  The payload includes data to be reproduced in a scrambled state. According to ARIB, PAT (Program Association Table), PMT (Program Map Table), and SI (Service Information) are not scrambled. Various management information is created using PMT and SI (Service Description Table, EIT: Event Information Table, BAT: Bouquet association Table).

  MPEG video data, Dolby AC3 (R) audio data, MPEG audio data, data broadcast data, etc., which are not directly related to the playback target, but are necessary for playback, such as PAT, PMT, SI, etc. Information (program information, etc.). The PAT includes a PID (Packet Identification) of the PMT for each program, and further, PIDs of video data and audio data are recorded in the PMT.

  Thus, as a normal STB playback procedure, when the user determines a program based on the EPG information, the PAT is read at the start time of the target program, and the PID of the PMT belonging to the desired program is determined based on the data. Determine and read the target PMT according to the PID, determine the PID of the video and audio packets to be played back included therein, read the video and audio attributes by the PMT and SI, set to each decoder, Video and audio data are cut out according to PID and played. Here, PAT, PMT, SI, and the like are transmitted every several hundreds ms to be used for intermediate playback.

  Here, digital broadcasting has a different broadcasting system for each country. For example, DVB (Digital Video Broadcasting) in Europe, ATSC (Advanced Television Systems Committee) in the United States, and ARIB (Association of Radio Industries and Businesses) in Japan.

  In DVB, the video is MPEG2, but the resolution is 1152 * 1440i, 1080 * 1920 (i, p), 1035 * 1920, 720 * 1280, (576, 480) * (720, 544, 480, 352), ( 288, 240) * 352, the frame frequency is 30Hz and 25Hz, the audio is MPEG-1 audio and MPEG-2 Audio, and the sampling frequency is 32kHz, 44.1kHz and 48kHz.

  In ATSC, the video is MPEG2, but the resolution is 1080 * 1920 (i, p), 720 * 1280p, 480 * 704 (i, p), 480 * 640 (i, p), and the frame frequency is 23.976Hz, 24Hz, 29.97Hz, 30Hz, 59.94Hz, 60Hz, audio is MPEG1 Audio Layer 1 & 2 (DirecTV), AC3 Layer 1 & 2 (Primstar), sampling frequency is 48kHz, 44.1kHz, 32kHz.

  In ARIB, the video is MPEG2, the resolution is 1080i, 720p, 480i, 480p, the frame rate is 29.97Hz, 59.94Hz, the audio is AAC (MPEG-2 Advanced Audio Coding), and the sampling frequency is 48kHz, 44.1kHz, 32kHz 24kHz, 22.05kHz, 16kHz.

  In this way, the digital broadcasting system is different depending on the country, and there is a possibility that it differs depending on the broadcasting station. Therefore, in the recorder, it is necessary to record the object as one or a plurality of files according to the method used.

  Therefore, the files added in the embodiment of the present invention to the current VR file structure have “x” in the file names HR_SFIx.IFO and HR_SFIx.bup as shown in FIG. It is configured so that there can be multiple. One or more files configured in this way are added for each broadcasting system.

  For example, when “x” = 00, it can be used when the broadcasting system is unknown or when the recorder does not support the broadcasting system. In this case, a stream whose broadcasting system is unknown or a stream whose broadcasting system is not compatible with the recorder can be stored as a TYPE B stream (SOB_STRB). Therefore, since ESTR_FI that is management information for digital broadcasting is changed for each broadcasting station (or for each broadcasting system), there are a plurality of ESTR_FIs.

  FIG. 4 is a diagram for explaining an example of how a part (HDVR_MGI) of management information (HDVR_MG) recorded in the AV data management information recording area 130 is configured. This HDVR_MGI includes a management information management table (MGI_MAT) and a playlist search pointer table (EX_PL_SRPT). The management information management table (MGI_MAT) includes disk management identification information (VMG_ID), HDVMG file information (HR_MANGER.IFO) end address (HR_MANGER_EA: indicates the address from the beginning of the DHVR_MG file to the end of EX_MNFIT), management Information (HDVR_MGI) end address (HDVR_MGI_EA: indicates the address from the beginning of the DHVR_MG file to the end of HDVR_MGI), version information, disk resume information (DISC_RSM_MRKI), disk representative image information (EX_DISC_REP_PICI), and stream It includes the start address (ESTR_FIT_SA) of the object management information, the start address (EX_ORG_PGCI_SA) of the original program chain information, the start address (EX_UD_PGCIT_SA) of the user-defined program chain information table, and the like.

  FIG. 5 is a diagram for explaining a specific example of resume mark information (DISC_RSM_MRKI) of the entire disc. DISC_RSM_MRKI is a mark pointer MRK_PT (on the target ESOB) that contains the program chain number PGCN, program number PGN, cell number CN, playback start PTM, etc. as information for resuming the interrupted playback when playing through the entire disc. PTM / PATS / S_ESOB_ENT number etc.), ESI number V_ESN of the video stream to be played back, ESI number A_ESN of the audio stream to be played back, main / sub information in case of Dual-Mono (audio main / sub switching flag), its marker The date / time information MRK_TM created (updated) is set.

  FIG. 6 is a diagram for explaining a specific example of representative image information (EX_DISC_REP_PICI) of a disc. EX_DISC_REP_PICI includes a picture pointer PIC_PT (a PTM / PATS / S_ESOB_ENT number etc. on the target ESOB) in addition to the program chain number PGCN, program number PGN, and cell number CN of the representative image and the start PTM of the representative image. ), The ESI number V_ESN of the video stream to be reproduced, the reproduction time and / or the reproduction end time of the representative image, the date / time information PIC_CL_TM when the representative image was created (updated), and the like.

  FIG. 7 is a diagram for explaining a specific example of the playlist search pointer table (EX_PL_SRPT). EX_PL_SRPT has a search pointer (EX_PL_SRP # 1 to #n) to each playlist, and each search pointer (EX_PL_SRP) has a resume marker for each playlist (PL_RSM_MRKI: marker that indicates how much playback was performed when playback was interrupted) Is provided. In this PL_RSM_MRKI, as information for resuming playback, the cell number CN corresponding to the resume marker, the picture pointer PIC_PT corresponding to the resume marker (corresponding to the playback start PTM, etc.), date / time information MRK_TM at which the marker was created, playback ESI number V_ESN of the video stream to be played (default stream), ESI number A_ESN of the audio stream to be played back, and main / sub switching flag of audio information included in the audio stream corresponding to the resume marker (main sub information in the case of Dual-Mono) ) Etc. are set.

  Further, each EX_PL_SRP includes representative image information (PL_REP_PICTI) of the corresponding playlist, and representative image information (marker of an image displayed as a thumbnail in a title menu) is provided for each playlist. In this PL_REP_PICTI, the target cell number CN, the picture pointer PIC_PT on the target EVOB (starting PTM, PATS, S_EVOB_ENT number, etc. of the corresponding representative image), the ESI number V_ESN of the video stream to be played (default stream), the corresponding The reproduction time of the representative image to be reproduced or the reproduction end time thereof, the date / time information PIC_CL_TM at which the corresponding representative image is created (updated), and the like are set.

  FIG. 8 is a diagram for explaining an example of how the other part (EX_M_AVFIT) of one piece of management information (HDVR_MG) is configured in the data structure according to the embodiment of the present invention. In this EX_M_AVFIT, there is movie AV file information (EX_M_AVFI), and M_EVOBI # 1 to #n, which are management information for each EVOB, are present in the number of EVOBs. In M_EVOBI, EVOB_TMAPI for managing the TMAP of EVOB exists as shown in FIG.

  Here, the update date / time information of VTMAPT, which is a TMAP (Time Map) for Video Recoding (VR) that performs analog input self-recording and replaying, is described in EX_M_AVFITI (VTMAP_LAST_MOD_TM) of FIG. 8, and Stream Recoding for digital broadcast recording The update date / time information of STMAPT, which is a TMAP for (SR), can be described in ESTR_FI_GI (STMAP_LAST_MOD_TM) in FIG. Then, these values (VTMAP_LAST_MOD_TM and / or STMAP_LAST_MOD_TM values) are compared with the corresponding update date / time information described in each TMAPT file. Can be configured.

  FIG. 9 is a diagram illustrating a specific example of the general information (EVOB_TMAP_GI) of the EVOB time map. EVOB time map information (EVOB_TMAPI) includes EVOB_TMAP_GI as shown in FIG. In this EVOB_TMAP_GI, general information for managing another file VTMAPT is recorded. That is, EVOB_TMAP_GI is the total number of entries (EVOBU_ENT_Ns) in the EVOB (EVOBU_ENT_Ns), the start address (ADR_OFS) of the EVOB, the size of the EVOB (EVOB_SZ), EVOBU_PB_TM_RNG that determines the time interval of the entry of the EVOB, And the TMAP number (EX_VTMAP_N: if determined one-to-one from the beginning of EVOB, it may be absent).

  In EVOB_TMAP_GI, since TMAP is divided into separate files (see FIG. 26), EVOB information can be obtained without reading the file. In particular, the TMAP file indicates how much data to read from the disk 100 and how much work RAM should be secured from the EVOB start address ADR_OFS, EVOB size EVOB_SZ, and EVOB entry total EVOBU_ENT_Ns in EVOB_TMAP_GI. Knowing before reading the body makes reading preparation easier.

  FIG. 10 is a diagram illustrating an example of how EX_M_VOB_STI is configured, and FIG. 11 is a diagram illustrating an example of how V_ATR is configured. As shown in FIG. 10, when EX_M_VOB_STI is registered, EVOB designates its corresponding EX_M_VOB_STI by a number in M_EVOBI. The structure of EX_M_VOB_STI includes V_ATR, AST_Ns, SPST_Ns, A_ATR0, A_ATR1, and pallet information of SP as in the existing DVD-VR.

  As the EVOB attribute (Attribute), as shown in FIG. 11, a flag indicating whether the image is a progressive image is attached to the Video attribute information (V_ATR), and high definition or high definition (HD) is added to the TV system. The types of resolution are increasing.

  FIG. 12 is a diagram for explaining an example of how the ESTR_FIT is configured. Stream management information is stored in an ESTR_FIT (Extended Stream File Information Table). ESTR_FIT includes a table (ESTR_FI_SRPT) including one or more file information search pointers, one or more file information (ESTR_FI included in HR_SFIxx.IFO in FIG. 13), and another one or more file information (HR_STMAPx in FIG. 26). STMAPIT included in .IFO) etc.

  Here, since ESTR_FI that is management information for digital broadcasting is changed for each broadcasting station (or for each broadcasting system), there are a plurality of ESTR_FIs. Therefore, ESTR_FI_SRPT information exists to specify the ESTR_FI file to be used. As shown in FIG. 12, the structure (ESTR_FI_SRPTI) includes the total number of ESTR_SRPs (ESTR_FI_SRP_Ns) and the end address (ESTR_FI_SRPT_EA) of the table information. Each ESTR_FI_SRP includes ESTR_FI_FN (ESTR_FI_file_name), ESTR_FI_LAST_MOD_TM (ESTR_FI file editing / update time), AP_FORMAT1 (broadcasting system: Major grouping: Japan_ISDB, ATSC, EU_DVB, etc.), Country code (for example, recorded country code: JPN = Japan), PKT_TY (packet type: 1 = MPEG-TS, for example), ESOBI_Ns (number of ESOB or AT_SOB), ESTR_FI_SZ (size of ESTR_FI file), and TOTAL_STMAP_SZ (total size of STMAP) It consists of

  In particular, when the standard has a restriction that TOTAL_STMAP_SZ is 2 MB or less at the maximum, it is necessary to check the file size so as not to exceed it. In other words, it is necessary to configure the MPU work RAM so that STMAP can be expanded within a maximum of 2 MB. Therefore, the TMAP size can be confirmed with TOTAL_STMAPI_SZ.

  Here, the update date / time information (STMAP_LAST_MOD_TM in FIG. 13) is also set in the ESTR_FI file, and when ESTR_FI at the time of editing is changed, the value is also updated. Then, during playback, this value (ESTR_FI_LAST_MOD_TM) is compared with the value in the ESTR_FI file (STMAP_LAST_MOD_TM).

  The number of ESTR_FI is, for example, 4 or less, and the number of ESOBI is, for example, 999 or less. Further, the “nn” portion of ESTR_FI file name: HR_SFInn.IFO is reflected in “nn” of STMAP File Name: HR_STMnn.IFO, so that the STMAP file name can be determined.

  FIG. 13 is a diagram illustrating a specific example of the ESTR_FI file (HR_SFIxx.IFO) structure. ESTR_FI includes ESTR_FI_GI (General Information), one or more ESOBI_SRP (Stream Object Information Search Pointer), and ESOBI (ESOB Information) indicated by the same number (#k) as ESOBI_SRP # k.

  ESTR_FI_GI includes the file name / file number (SFI_ID) of the object managed by the ESTR_FI, the number of ESOBI_SRP (ESOBI_SRP_Ns) in the ESTR_FI, the version number (VERN) of the file, and the packet type (PKT_TY: for example, 1 = MPEG-TS ), Packet group size (PKT_GP_SZ: fixed at 16 Logical Block, for example), number of TS packets in packet group (PKT_Ns: fixed at 170 TS packet, for example 0xAA), STMAP update time (STMAP_LAST_MOD_TM), STMAP size ( STMAP_SZ), packet arrival time status (PATS_SS), and the like.

  A plurality of STR_FIs can be provided corresponding to the number of HR_SFIxx.IFOs, but these STR_FIs are provided for each broadcasting station and / or broadcasting system (Japanese ARIB, US ATSC, European DVB, etc.). be able to. Further, a plurality of time maps (see ETMAPI / STMAPI in FIG. 26) can be provided corresponding to the plurality of STR_FIs provided.

  Here, if the stream can be analyzed (TYPE A STRA), a TMAP can be created based on PTM, but if it cannot be analyzed (if the scramble cannot be solved or the data is different from the assumed broadcasting station) Etc .: TYPE B STRB) can create TMAP based on reception time (PATS) instead of PTM. However, since PATS is not playback time, special playback that is accurate in time cannot be performed, but general special playback (such as fast-forward playback and fast-rewind playback to roughly check the recorded contents) is possible.

  In FIG. 13, PATS_SS is configured with a value indicating the accuracy of PATS. For example, in the apparatus shown in FIG. 53, which will be described later, when data such as a network or IEEE1394 is taken in, there are times when PATS is 4 bytes or PATS is dummy. In order to cope with such a case, as the value of PATS_SS, both “00 = PATS and FIRST_PATS_EXT are valid: precision 6 bytes”, “01 = valid only PATS: precision 4 bytes”, “10 = both PATS and FIRST_PATS_EXT Is invalid: no accuracy) ”.

  Also, in digital broadcasting, one of the features that can be mentioned is that multiple videos represented by multi-view broadcasting can be played simultaneously (time sharing), and only necessary ones can be selected and played. This content is selected according to the user's preference or the like. For example, in the case of multi-angle broadcasting, when the recorder receives a stream of X, Y, Z and U corresponding to rain as a single TS, it may be necessary to select and play the necessary stream at the time of playback and switch freely with keys. . To cope with this, grouping information (GPI) is added to enable this purpose.

  FIG. 14 is a diagram illustrating an example of how ESOBI_GI included in ESOBI in FIG. 13 is configured. ESOBI_GI includes, for example, various pieces of information illustrated in the illustrated order. That is, ESOBI includes ESOBI_GI, ESOB_V_ESI (Extended Video Elementary Information), ESOB_A_ESI (Extended Audio Elementary Information) and / or ESOB_OTHER_ESI (Other Elementary Information), ESOB_DCNI (Discontinuity Information), and ESOB_CONNI (ESOB Connect Information). ), ESOB_ES_GPI (ESOB_ES Group Information), ESOB_TMAP (ESOB Time Map), and the like.

  FIG. 15 is a diagram illustrating various information included in ESOBI_GI. FIG. 15 shows the contents of various types of information in FIG. That is, ESOBI_GI includes ESOB_REC_MODE, ESOB_TY, AP_FORMAT2 (Minor: 1 = ISDB-S: BS / CS broadcasting, 2 = ISDB-T: terrestrial digital broadcasting), recording start date and time (ESOB_REC_TM), recording time (ESOB_DURATION: valid value is ALL 0xff if there is none), including the first Presentation Time (ESOB_S_PTM), end Presentation Time (ESOB_E_PTM), etc., and based on the PSI and SI values, SERVICE_ID, PMT_PID, NETWORK_ID, TS_ID, FORMAT_ID, SERVICE_TYPE, PCR_PID, etc. Record. Furthermore, ESOBI_GI has ESOB_ES_Ns (number of ESs selected for recording), ESOB_V_ES_Ns (number of ESs that made TMAP among recorded video ESs), ESOB_A_ES_Ns (ES that made TMAPs among recorded audio ESs) The recording rate and the like.

  In the case of TYPE_B, the stream may be recorded without being analyzed. In this case, the PSI and SI values are unknown (or unreliable), and SERVICE_ID, PMT_PID, NETWORK_ID, TS_ID, FORMAT_ID, SERVICE_TYPE, PCR_PID, etc. cannot be described. In such a case, a flag that PSI and SI information is invalid can be set in ESOB_TY: b12. In that case, the values of SERVICE_ID, PMT_PID, NETWORK_ID, TS_ID, FORMAT_ID, SERVICE_TYPE, and PCR_PID are invalid.

  Or, instead of indicating the entire flag (b12 of ESOB_TY), set an invalid value (0xff) for each value of SERVICE_ID, PMT_PID, NETWORK_ID, TS_ID, FORMAT_ID, SERVICE_TYPE, and PCR_PID, and set that value if invalid It is also possible to do. However, PSI and SI values may be valid even for TYPE_B.

  ESOB_REC_MODE included in ESOBI_GI indicates the TYPE of the stream, and 00h indicates Type A recording mode, and 01h indicates Type B recording mode. TYPE A is a stream whose stream structure can be analyzed, and management information is managed on a PTM basis. On the other hand, TYPE B cannot analyze the stream structure, so management information is managed on a PATS basis. Therefore, TMAP is also Type A based on PTM and Type B based on PATS. ESOB_TY includes a TE flag indicating whether or not provisional erasure is performed and a Flag indicating validity / invalidity of data created from the PSI and SI.

Here, the relationship between ESOB_ES_Ns and ESOB_V_ES_Ns, and ESOB_A_Es_Ns and ES_TMAP_Ns can be expressed by the following equations:
ESOB_ES_Ns ≧ ESOB_V_ES_Ns + ESOB_A_Es_Ns
ESOB_V_ES_Ns + ESOB_A_Es_Ns ≧ ES_TMAP_Ns
FIG. 16 is a diagram illustrating an example of how ESOB_ESI is configured. As shown in FIG. 16, ESOB_ESI is divided into three types (ESOB_V_ESI in FIG. 17, ESOB_A_ESI in FIG. 18, and ESOB_OTHER_ESI in FIG. 19). In these three types of ESI, ESOB_ES_PID (ES PID), STREAM_TYPE (STREAM type indicated in the PMT), STREAM_CONTENT (STREAM_CONTENT value indicated in the component descriptor), and COMPONENT_TYPE (COMPONENT_TYPE indicated in the component descriptor) ) And Es_Index (example: In the case of ARIB, the COMPONENT_TAG value indicated by the component descriptor and the index number uniquely assigned to the ES in the ESOB) are common, and in V_ESI, V_ATR is further added. .

  FIG. 17 is a diagram for explaining an example of how the ESOB_V_ESI is configured and an example of how the video attribute V_ATTR included in the ESOB_V_ESI is configured. V_ATR includes Video compression mode (compression type: 1 = MPEG1, 2 = MPEG2, 3 = MPEG4_AVC, 4 = VC-1 ...), Aspect Ratio (0 = 4: 3, 1 = 16: 9), Source resolution (0 = 352 * 240 (288), 1 = 352 * 480 (576), 2 = 480 * 480 (576), 3 = 544 * 480 (576), 4 = 704 × 480 (576), 5 = 720 * 480 (576), 8 = 1280 * 720, 9 = 960 * 1080, 10 = 1280 * 1080, 11 = 1440 * 1080, 12 = 1920 * 1080, 16 = 640 * 480 (576), 17 = unspecified (Horizontal ) * 240 (288) (Vertical), 18 = unspecified (Horizontal) * 480 (576) (Vertical), 19 = unspecified (Horizontal) * 720 (Vertical), 20 = unspecified (Horizontal) * 1080 (Vertical), 1fh = unspecified), Source picture progressive mode (0 = Interlace, 1 = Progressive, 3 = unspecified), frame rate (1 = 24 / 1.001, 2 = 24, 3 = 25, 4 = 30 / 1.001, 5 = 30, 6 = 50, 7 = 60 / 1.001, 8 = 60, 0xf = unspecified).

  Here, unspecified is set when the description is made “Unknown” when the inside of the object cannot be examined when it cannot be understood only by the analysis of PSI and SI. In ARIB, only the analysis of the descriptors reveals only the vertical resolution, and the horizontal resolution may be unknown. Therefore, it is possible to describe only the vertical resolution.

  FIG. 18 is a diagram for explaining an example of how ESOB_A_ESI is configured and an example of how the audio attribute AUDIO_ATTR included in ESOB_A_ESI is configured. A_ESI further includes AUDIO_ATR (AUDIO attribute value). This AUDIO_ATR is the audio compression mode (0 = AC-3, 2 = MPEG1 or MPEG2 without extension bitstream, 3 = MPEG2 with extention bitstream, 4 = L-PCM, 0x30 = MPEG2 AAC, 0x3f = unspecified), Sampling frequency (0 = 48kHz, 1 = 96kHz, 2 = 192kHz, 4 = 12kHz, 5 = 24kHz, 8 = 32kHz, 9 = 44.1kHz, 0xf = Unspecified), number of audio channels (0 = 1h (Mono), 1 = 2ch (Stereo) , 2 = 3ch, 3 = 4ch, 4 = 5ch, 5 = 6ch, 6 = 7ch, 7 = 8ch, 9 = 2h (Dual Mono), 0xf = unspecified). These values are set from the values of the audio component descriptor.

  FIG. 19 is a diagram illustrating an example of how ESOB_OTHER_ESI is configured. ESOB_OTHER_ESI includes ES_TY, ES_PID, STREAM_TYPE, and COMPONENT_TAG in the same manner as ESOB_V_ESI in FIG. 17 or ESOB_A_ESI in FIG. In addition, ESOB_OTHER_ESI may have a reserved area, and various information (data encoding identifier, additional information of this identifier, copy control information, etc.) can be appropriately described in this reserved area.

  FIG. 20 is a diagram illustrating a specific example of ESOB_DCNI. This ESOB_DCNI (Discontinue Information) is composed of DCNI_GI and CNT_SEGI # 1 to #n, DCNI_GI is composed of CNT_SEGI number information (CNT_SEGI_Ns), and each CNT_SEGI is CNT_SEG_SZ (CNT_SEG size: number of packet groups) and CNT_SEG_PKT_POS (Packet) This is composed of the number of first CNT_SEG packets in the group). From these pieces of information, it can be shown whether or not the count operation of the system time counter STC of the recording / reproducing apparatus has made one round (wrapped around). Thus, for example, the number of CNT_SEG from the beginning of ESOB is put in the time information PTM, and it can be confirmed in advance that STC Wrap-around has occurred and used for TMAP calculation etc. (See FIG. 36 or FIG. 86).

  FIG. 21 is a diagram illustrating an example of how the ESOB_GPI is configured. In ESOB, there is ESOB_ES_GPI as multi-view broadcasting, rainfall-compatible broadcasting, and simultaneous recording of multiple programs. The GPI (Group Information) includes ESOB_GPI_GI, one or more GPI_SRPs, and one or more GPIs.

  FIG. 22 is a diagram illustrating an example of how ESOB_GPI_GI, GPI_SRP #, and GPI # are configured. ESOB_GPI_GI contains GPI_TY (0 = created in the recorder, 1 = defined during broadcasting) and GPI_SRP_Ns (number of ES_GPI_SRP), and GPI_SRP is composed of GPI_SA (GPI start address), and each GPI has GPI_GI, Each ES_PID is configured, and GPI_GI is configured with PIORITY (priority: 0 if not specified, 1 being the highest priority) and ES_PID_Ns (number of ESs in the group). However, if there is a video PID, it does not belong to the same GP.

  FIG. 23 is a diagram illustrating an example of how ESOB_CONNI is configured. This ESOB_CONNI (ESOB Connect Information) describes a continuous recording flag (ESOB_CONN_SS) indicating whether or not the corresponding ESOB has been continuously recorded from the preceding ESOB. That is, ESOB_CONNI can be regarded as seamless information between consecutive ESOBs before one ESOB. If ESOB_CONN_SS included therein is “1”, it indicates that the previous ESOB was recorded continuously. If it is “0”, it indicates that it is not continuous with the previous ESOB.

  FIG. 24 is a diagram illustrating an example of how ESOB_TMAP (type A) is configured. ESOB_TMAP includes ESOB_TMAP_GI and one or more ES_TMAP_GI. Here, ESOB_TMAP_GI has a one-to-one correspondence with STMAPI_SRP in the STMAP file, and STMAP_SRP has a one-to-one correspondence with STMAPI.

  ESOB_TMAP_GI is ADR_OFS (Packet Group number (or LB address) from the beginning of the file to the beginning of ESOB), and in the case of PTM, ESOBU_PB_TM_RNG (ESOBU playback time range: 1 = 2s or less, 2 = 3s or less, 3 = 1s ESOB_S_PKT_POS (beginning in the first packet group of ESOB: 0 ≦ ESOB_S_PKT_POS ≦ 169), ESOB_E_PKT_POS (end in the first packet group of ESOB: 0 ≦ ESOB_E_PKT_POS ≦ 169), and ESOB_SZ (ESOB Size) and ES_TMAP_GI_Ns (number of ES_TMAPs belonging to the ESOB), ES_TMAP_GI is ESIN (ESI number of the target ES of the TMAP), ADR_OFS (logical address from the beginning of the ESOB file to the beginning of the ES), ES_S_PTM (start PTM), ES_E_PTM (end PTM), ES_ESOBU_ENT_Ns (number of ESOBU_ENT), LAST_ESOBU_E_PKT_POS (position in the packet group of the last ESOBU), STMAP_N (TMAP number in STMAPIT belonging to the ES: in order to each STMAPT If this number is not recorded, Composed in the stomach).

  Here, by setting ESOBU_PB_TM_RNG (the same applies to EVOBU_PB_TM_RNG in FIG. 9), it becomes possible to prevent TMAPI information from becoming extremely large even if the recording time increases. However, since the time interval of each entry increases, there is an increased possibility that playback at 2x speed will not be smooth.

  Note that ESOB_TMAP_GI (FIG. 24) corresponds to STMAP_GI (FIG. 26) in the STMAP file on a one-to-one basis, and ES_TMAP_GI (FIG. 24) belonging to ESOB_TMAP corresponds to ETMAPI (FIG. 26). That is, the number of ES_TMAP_GIs (ES_TMAP_GI_Ns in ESOB_TMAP_GI: FIG. 24) matches the number of ETMAPI_SRPs (or ETMAPI) (ETMAPI_SRP_Ns in STMAPI_GI: FIG. 29).

Therefore, when retrieving (investigating) the TMAP from the video ES PID to be played back in the ESOB, the ESTMAP_GI having the ESI number corresponding to the video ES PID to be played back is checked from the ESTMAP_GI in the ESOB_TMAPI, and the number in the ESOB Remember (order). Then, ETMAPI_SRP is determined in the order in the ESOB in the STMAPI_GI corresponding to ESOB_TMAP_GI, and ETMAPI is specified from the SRP information. However, which ETMAP_SRP belongs to STMAP_GI is obtained by adding the number of ETMAPI_SRP from the top in the number in STMAPI_GI. )
FIG. 25 is a diagram illustrating an example of how ESOB_TMAP (type B) is configured. FIG. 25 (or FIG. 30 described later) is an example of the structure of an actual PATS-based TMAP. In FIG. 25, ESOB_ADR_OFS indicates the number of logical blocks (LBN) from the beginning of the file to the beginning of the ESOB.

ESOB_SZ is the number of packet groups from the packet group to which the AT_SOB head belongs to the packet group to which the last packet group belongs to AT_SOB, ESOBU1_SZ is the number from the first packet group of ESOBU to the last packet group of ESOBU, and each ESOBU_S_PKT_POS is The difference between ESOBU breaks and Packet group breaks is represented by the number of packets.

  Since the time information is based on PATS, ESOB_S_PATS is used as the ESOB start time, and ESOB_E_PATS is used as the end time. However, regarding ESOB_E_PATS, it is the PATS (arrival start time) of the last packet of the last packet group, not the final reception end time. Editing is performed for each ESOBU, and the playback start time (CELL_S_PATS of CELLI) is specified. Because of editing for each ESOBU, ESOB_S_PATS always matches the head of ESOBU.

In the case of PATS base, ESOB_TMAP_GI includes ESOB_ADR_OFS (Packet Group number (or LB address) from the beginning of the file to the beginning of ESOB), AT_SOBU_TM (ESOBU arrival time interval: 0 = 1s, 1 = 2s), ESOB_S_PKT_POS (ESOB Beginning in the first packet group: 0 ≦ ESOB_S_PKT_POS ≦ 169), ESOB_E_PKT_POS (end in the first packet group of ESOB: 0 ≦ ESOB_E_PKT_POS ≦ 169), AT
It consists of _SOBU_ENT_Ns (number of AT_SOBU_ENTs belonging to the ESOB) and ESOB_SZ (ESOB size). Editing is performed in AT_SOBU units, and adjustment is performed in the PATS start / end time (CELLI).

  FIG. 26 is a diagram illustrating an example of how HR_VTMAP.IFO and HR_STMAPx.IFO included in the DVD_HDVR directory are configured. STMAPIT is recorded in an area (separate file) different from EX_VTMAPIT. This STMAPIT (in the case of TYPE A) includes STMAPITI, one or more STMAPI_GIs, one or more ETMAP_SRPs, and the same number of ETMAPIs. On the other hand, STMAPIT (in the case of TYPE B) includes STMAPITI, one or more STMAP_SRPs, and the same number of STMAPIs.

  A normal DVD recorder has time map information (TMAPI) as management information of a video object (VOB). This information is information for dividing EVOB / ESOB for each EVOBU / ESOBU so that playback, special playback, etc. can be performed in that unit, but one piece of information is required every 0.5 s at maximum. Therefore, if the disk capacity increases in the future or if a compression method with high compression efficiency is adopted, TMAPI will increase and it will become complicated when editing is performed. If the time map information is in the management information (.IFO), it is necessary to move or rewrite data in other unrelated areas simply by changing the TMAPI, which is inefficient. In order to improve the situation, TMAPI is recorded in another area (see FIG. 26).

  FIG. 27 is a diagram for describing an example of how EX_VTMAPTI, each EX_VTMAP_SRP #, and each EX_VTMAPI are configured. EX_VTMAPIT is composed of EX_VTMAPITI, EX_VTMAPI_SRPT, and EX_VTMAPI # 1 to #n. EX_VTMAPITI is VMG_ID (same value as VMG_ID at the beginning of VMGI), EX_VTMAPT_EA (VTMAP end address), EX_VERN (TMAP version information), EX_VTMAP_LAST_MOD_TM (TMAPT update date / time information: same value as HR_MANGR.IFO), EX_VTMAPI_SRPNs (Total number of search information). VTMAP_SRPT consists of one or more VTMAP_SRP (search information for each VTMAP), VTMAP_SRP consists of VTMAP_SA (VTMAP start address) and VOBU_ENT_Ns (total number of VOEU_ENT), and VTMAP consists of one or more EVOBU_ENT ing.

  FIG. 28 is a diagram illustrating an example of how the contents of each EVOBU_ENT are configured. Each EVOBU_ENT includes the size 1stREF_SZ of the first reference image (reference picture) in the corresponding entry, the playback time EVOBU_PB_TM of the corresponding EVOBU (can be displayed by the number of fields), and the size EVOBU_SZ of the corresponding EVOBU. Here, the “reference image” refers to picture data that can create (decode) an image of one frame (or field) with only one compressed picture. If MPEG2 is taken as an example, I-picture corresponds to the reference image.

  FIG. 29 is a diagram illustrating an example of how various types of information included in STMAPIT (type A) is configured. FIG. 30 is a diagram illustrating an example of how various information included in STMAPIT (type B) is configured.

  As shown in FIG. 29, STMAPIT of type A based on PTM includes STMAPIT identification information (STM_ID), STMAPIT end address information (STMAPIT_EA), TMAP version information (VERN), and STMAPI update date / time information (STMAPI_LAST_MOD_TM: The same as the value of VMGI), the number of STMAPI_GI (STMAPI_GI_Ns), and the like. STMAPI_GI includes the number of ETMAPI_SRPs (ETMAPI_SRP_Ns) to which it belongs, and ETMAPs belonging to STMAP are determined in numerical order from the beginning. ETMAPI_SRP includes start address information (ETMAPI_SA) to ETMAPI and the number of ESOBU_ENT (ESOBU_ENT_Ns). ETMAPI contains one or more ESOBU_ENT. There may be garbage data between ESOBU_ENT.

  On the other hand, as shown in FIG. 30, PATS-based Type B STMAPITI includes STMAPIT identification information (STM_ID), STMAPIT end address information (STMAPIT_EA), TMAP version information (VERN), and STMAPI update date / time information ( STMAPI_LAST_MOD_TM: same as VMGI value), STMAPI_SRP_Ns (number of TAMP_SRPI = number of TMAPI), etc. STMAPI_SRP includes start address information (STMAPI_SA) to STMAPI and the number of AT_SOBU_ENTs (AT_SOBU_ENT_Ns), and STMAPI includes one or more AT_SOBU_ENTs. Each AT_SOBU_ENT includes an AT_SOBU size (AT_SOBU_SZ) and AT_SOBU_S_PKT_POS in which the number of packets from the beginning to the start position of the corresponding AT_SOBU in the Packet Group is represented.

  FIG. 31 shows an example of how the contents of ESOBU_ENT are configured (example of type A). The PTM-based ESOUB_ENT is the first reference picture (I picture, etc.) size 1st_Ref_PIC_SZ (last address information from the ESOBU head: LB unit), ESOBU playback time ESOBU_PB_TM (number of fields), and ESOBU size ESOBU_SZ (Number of packet groups belonging to the corresponding ESOBU) and ESOBU_S_PKT_POS (number of packets from the head of the packet group including the head of the corresponding ESOBU).

In the case of time search, the ESOBU of the target time is obtained by accumulating ESOBU_PB_TM, and the playback start PTM is converted by the number of fields from the head of the ESOBU. The target address is K for the target ESOBU and A for the target address.
A = ESOB__ADR_OFS + target ES ES_ADR_OFS + Σ ^k−1 _{N = 1} ESOBU_SZ (N) × 16 + 1
In addition, the first packet becomes a packet having a value of ESOBU_S_PKT_POS, and this address is accessed.

  On the other hand, there are two types of AT_SOBU_ENT (FIG. 30) based on PATS, that is, a packet unit and a packet group unit. In the packet unit, more accurate addresses can be obtained, but the AT_SOBU_ENT data increases. In the packet group unit, the AT_SOBU_ENT data is small, but addresses can be taken only in the packet group unit.

  In packet unit, it is composed of AT_SOBU_SZ and AT_SOBU_POS. AT_SOBU_S_PKT_POS indicates the start position of AT_SOBU in Packet_Group by the number of packets.

  For packet group units. It consists of AT_SOBU_SZ, and AT_SOB_S_PKT_POS and AT_SOB_E_PKT_POS are fixed to 0.

  In ESOB_TMAP_GI, ADR_OFS, AT_SOB_SZ, and AT_SOB_E_PKT_POS are described as values related to the entire value of AT_SOB.

AT_ADR_E_OFS = AT_SOB_SZ- (AT_ADR_S_OFS + Σ ^k-1 _{N = 1} AT_SOBU_SZ (N) +1)
Expressions such as AT_SOB_SZ> AT_ADR_S_OFS, AT_SOB_SZ> AT_SOBU_SZ, etc. also hold.

  FIG. 32 is a diagram illustrating an example of how PGC information (EX_ORG_PGC information and EX playlist information / EX_UD_PGC information) included in HDVR_VMG is configured. The playback information is EX_PGC information. Like the normal VR format, the ORG_EX_PGC information is automatically created by the device during recording and set in the order of recording. The UD_EX_PGC information is created according to the playback order that is freely added by the user, and is called a playlist. ing. These two formats are common at the EX_PGC level, and the EX_PGC format is shown in FIGS.

  FIG. 33 is a diagram illustrating a specific example of EX_PGI. Here, in the EX_PG information (each EX_PGI), date information (PG_LAST_MOD_TM) when this EX_PG is updated is stored. Thereby, it is possible to know when the EX_PG was edited. As text information, primary text information (PRM_TXTI) is used for the program name. In order to store other text information, other information (director name, leading name,...) Is stored in the item text (IT_TXT) area, and the search pointer (SRP) number of the stored IT_TXT is stored in the EX_PGI. A program (PG) number (EX_PG number) corresponding to IT_TXT data is also set. Here, the EX_PG number is an absolute number from the beginning of recording on this disc, and is an index number that does not change even if another EX_PG is deleted.

  Furthermore, EX_PG has RSM_MRKI (existing in PL_SRP) as well as the playlist, and has a resume marker for each program (a marker that indicates how far it has been played when playback is interrupted) to resume playback. As information, EX_CELL number, playback start PTM and date / time information when the marker is created, ESI number of the video stream to be played back, ESI number of the audio stream to be played back, and main / sub information in the case of Dual-Mono are set. This is used as a title resume.

  In addition, there is PG_REP_PICTI, which provides representative image information for each PG (image marker to be displayed as a thumbnail in the title menu, etc.), cell number, start PTM, date and time information when the marker was created, and playback The ESI number of the video stream is set.

  Further, in order to use manufacturer information (MNFI or MNI stored in EX_MNFIT in FIG. 4 or the like) provided to realize a manufacturer-specific function, the MNFI search pointer number (not shown) is displayed in EX_PGI in FIG. And EX_PG number can also be set in the MNFI information. Accordingly, EX_PGCI / EX_PGI in FIG. 33 can be linked to data in MNFI information (not shown).

  Furthermore, if PG update date / time information (program update date information at the end in the PGI in FIG. 33) is set in both MNFI and IT_TXT, the time (set update date / time and current time) of the menu is displayed. By checking the match, it is possible to verify whether the editing is performed by a device of another manufacturer.

  FIG. 34 is a diagram illustrating a specific example of EX_CI. In the EX_CELL information (EX_CI), ESOB and AT_SOB types are added to the cell type, and an ESOB number, start time, end time, packet group number (GP number) to be reproduced, and the like can be designated. Here, the start time and the end time can be represented by either a playback time (in the case of PTM) or a PATS time (in the case of PATS).

  Here, when the time designation is set to playback time = actual time at playback, the same access method as that of an existing DVD video recorder (DVD-VR) can be achieved while stream recording is performed by directly recording the transmitted bit stream. Become. Then, since the user can designate the recording location by the reproduction time, the user's desire is completely reflected. However, this method can be adopted when the contents of the stream can be sufficiently analyzed. When the contents of the recorded stream are not sufficiently understood, the stream packet (MPEG-TS packet in digital broadcast recording) It must be specified in units of transfer time.

  When the recording location is designated by the reproduction time in a state where the contents of the recorded stream are not sufficiently understood, reproduction cannot always be started from the head of the I picture. Therefore, when the playback start frame is not an I picture frame, decoding is started from the immediately preceding I picture, and display of the playback video is started when the target frame is decoded. By doing so, it is possible to make it appear to the user as if playback has started from the frame specified by the user.

  By the way, the ID to be referred to at the time of playback processing is specified by the method of setting the PID of the stream representing the stream to be played back, the method of setting the ID of the component group in the case of multi-view TV, etc. (For example, there are a method of describing with 13-bit actual data, a method of describing the order in the PMT, a method of describing the value of the component tag, etc.) . Also, a method of switching by entering a GRP number to be referred to (GRP_SRP number) is conceivable.

  It should be noted that EX_PG and EX_CELL can be specified with numbers that do not change even if a program or cell in the middle is deleted by adding a unique ID number (PG_INDEX: EX_PGI # p in FIG. 34) to EX_PG. In the EX_CELL information (EX_CI), the file number (ESTR_FI number) of the stream to be reproduced and the ESOBI_SRP number of the corresponding ESOB are set. Further, the EX_CELL information includes cell entry point information C_EPI (Entry Point Information) corresponding to a chapter.

  FIG. 35 is a diagram illustrating a specific example of C_EPI. There are two types of C_EPI for each cell type, for a total of six types. M_CELL_EPI_TY_A is composed of PTM with EPI_TY (EPI type information) and EP (entry point), and PRM_TXTI (text information) and REP_PIC_PTM (thumbnail pointer) are further added to M_CELL_EPI_TY_B.

  STR_A_CELL_EPI_TY_A (ESOB TYPE A) is EPI_TY (EPI type information), PTM with EP, corresponding PID and GP number (PID / GP_N), ESI number of ES with that EP, ESI number of audio ES The main / sub information in the case of Dual-Mono. STR_A_CELL_EPI_TY_B further includes PRM_TXTI (text information) and REP_PIC_PTM (thumbnail pointer) (however, TY_B has no PID / GI_N).

  STR_B_CELL_EPI_TY_A (ESOB TYPE B) is composed of EPI_TY (EPI type information) and PATS with EP, and STR_B_CELL_EPI_TY_B further includes PID, PRM_TXTI (text information), and REP_PIC_PATS (thumbnail pointer) with that EP ).

  FIG. 36 is a diagram illustrating an example of how the PTM (Presentation Time) of ESOB (or EVOB) is configured. This time information PTM includes information CNT_SEGN indicating the number of continuous segments CNT_SEG (number of CNT_SEGs from the beginning of ESOB), PMT_base that roughly counts on a 90 kHz basis, and PMT_extension that finely counts on a 27 MHz basis. The actual time by PTM is expressed by the value of PMT_base plus PMT_extension. There are two types of ESOBs: type A, which is played back based on this PTM (PMT_base + PMT_extension), and type B, which is played back based on PATS (Packet Arrival Time).

   Information CNT_SEGN indicating the number of CNT_SEGs from the beginning of the ESOB can be set as follows, for example. That is, in the case of type A ESOB, the value of CNT_SEGN is valid, but in other than ESOB, CNT_SEGN is set to 0. The value of CNT_SEGN when valid is, for example, CNT_SEGN = 4, indicating that there are 0 CNT_SEGs in the corresponding ESOB, CNT_SEGN = 5, indicating that there is 1 CNT_SEG in the corresponding ESOB, and CNT_SEGN = 6 This indicates that there are two CNT_SEGs in the corresponding ESOB, and that CNT_SEGN = 7 indicates that there are three CNT_SEGs in the corresponding ESOB.

  The above is an example in the case of ESOB. However, in the case of EVOB, the PTM can be configured with the same data structure. By putting the number of CNT_SEG (CNT_SEGN) from the beginning of ESOB in PMT, it can be confirmed in advance that STC Wrap-Around has occurred, and this CNT_SEGN can be used for TMAP calculation.

  FIG. 37 is a diagram for explaining an example of how a stream object data unit (ESOBU) is configured. In the Packet Group Header, as shown in FIGS. 37 to 40, Headre_ID (0x00000FA5) is set at the head of the Packet Group, followed by packet group general information PKT_GRP_GI, copy management information CCI or CPI (Copy Control Information or Contents Protection). Information) and manufacturer information MNI (or MNFI: Manufacturer's information).

  The lower 4 bytes unique to each PATS 162 are included in each PATS, but the upper 2 bytes of the first PATS are included in First_PATS_EXT described in the packet group general information (PKT_GRP_GI) in the Packet Group Header 161. It has become. As a result, the data amount can be reduced as compared with the case where the 6-byte packet arrival time is individually described in each PATS.

  FIG. 38 is a diagram illustrating a specific example of PKT_GRP_GI. PKT_GRP_GI is composed of packet type PKT_GRP_TY (1 = MPEG_TS), packet group version number VERSION, packet group status information PKT_GRP_SS, number of valid packets Valid_PKT_Ns in the packet group, upper two bytes FIRST_PATS_EXT of the PATS for the first packet, etc. .

  Furthermore, PKT_GRP_SS is configured to include a bit STUF indicating whether stuffing has been performed (when this STUF bit is set, Valid_PKT_Ns indicates a value other than 0xAA) and PATS_SS. . Here, PATS_SS is a value indicating the accuracy of PATS (for example, when PATS_SS is 00, both PATS and FIRST_PATS_EXT are valid and the accuracy is 6 bytes; when PATS_SS is 01, only PATS is valid and the accuracy is 4 bytes. ; When PATS_SS is 10, both PATS and FIRST_PATS_EXT are invalid and there is no accuracy).

  Note that the PATS extension byte FIRST_PATS_EXT of the first packet is composed of, for example, the upper 2 bytes of the arrival time of the packet at the head of the packet group, and the remaining 4 bytes are appended before each packet. As a result, more accurate time reproduction processing is possible.

  FIG. 39 is a diagram for explaining an example of how CP_CTL_INFO (copy control information: abbreviated as CCI or CPI as appropriate) included in the packet group header is configured. CP_CTL_INFO is in the CCI (or CPI) of the Packet Group Header, and copy control of each Packet Group is performed in the Packet Group Header. The CCI (or CPI) value is set by a digital copy control descriptor and a content use descriptor. The contents are, for example, CGMS (0 = prohibited, 1 = unlimited allowed), APS (0 = no APS, 1 = APS type 1 added, 2 = APS type 2 added, 3 = APS type 3 added) and EPN ( 0 = content protection (Internet output protection), 1 = no content protection) and ICT (0 = resolution limit, 1 = no limit).

  Alternatively, CCI (or CPI) is digital copy control (00 = copy prohibited, 01 = copy allowed, 11 = copy prohibited) and analog copy control (00 = no APS, 01 = APS type 1, 10 = APS type 2, 11 = APS type 3), EPN (0 = content protection, 1 = no content protection) and ICT (0: analog video output resolution limit, 1 = no limit). Here, APS stands for Analog Protection SYSTEM, and in this embodiment, Macrovision (R) is assumed.

  Also, copy control information (CCI or CPI) is placed on the management information side (ESOBI_GI: FIG. 14) and copy management (copyright management) is performed as a whole, or CCI (or CPI) is managed on the management information side and object side (Packet Group). : In both FIG. 37 and FIG. 39), copy management (copyright management) may be considered in two stages with priority given to the object side (Packet Group). Specifically, ESOBI_GI CCI is used in the title menu, and Packet Group can be preferentially processed in actual device operation.

  FIG. 40 is a diagram for explaining a specific example of manufacturer information (MNI or MNFI). MNI or MNFI is composed of MNF_ID and MNF_DATA. NMF_ID is a value representing each manufacturer (maker). Subsequent MNF_DATA is a data area that can be freely set for each manufacturer.

  That is, it is conceivable that the recording device has a unique function that is not described in the DVD format depending on the manufacturer and model, and is differentiated from other companies. In that case, it may be necessary to embed information unique to the manufacturer in the object data. Therefore, in this embodiment, in order to cope with this, MNI (Manufacturer's Information) is provided as an area in the Packet Group Header.

  FIG. 41 is a diagram illustrating an example of how the EVOBU is configured. EVOBU has the following configuration in order to maintain compatibility with HD_DVD-VIDEO and HD_DVD-VR, which are the next generation standards. That is, the configuration of the control pack CLT_PACK to be placed at the head of EVOBU is HD_DVD-VDEO (STD: Standard-VTS / ADV: Advanced-VTS), which is composed of GCI_Packet, EX_PCI_Packet, and EX_DSI_Packet, and is referred to as an NV pack. In the case of VR (INT: Interoperable-VTS / VR), it is composed of GCI_Packet, EX_RDI_Packet, and dummy_Packet and is called an RDI pack.

  FIG. 42 is a diagram for explaining an example of how the EVOBU GCI (General Control Information) in FIG. 41 is configured. The GCI structure commonly used for all streams is composed of GCI_CAT, DCI, CCI (or CPI), and RECI. As shown in FIG. 42, EVCI_CAT is entered in GCI_CAT to indicate the CTL pack type, and it is determined whether the EVOB is an HD_DVD-VR stream or an HD_DVD-VIDEO stream.

  DCI_CC_SS (a flag indicating the presence of DCI and CCI) is composed of DCI_SS and CCI_SS. DCI_SS is “0 = no valid DCI exists, 1 = only valid aspect information exists, 3 = all DCI exists”, and CCI_SS is “0 = no valid CCI exists, 1 = only source information exists” 2 = only APS exists, 3 = only source information and APS exist, 4 = only CGMS exists, 5 = only CGMS and source information exist, 6 = only CGMS and APS exist, and 7 = all exist.

  DCI (Display Control Information) is Aspect_Ration (0 = 4: 3, 1 = 16: 9, 8 = 14: 9 letterbox (center), 4 = 14: 9 letterbox (top), 13 = 16: 9 letter Box (center), 2 = 16: 9 letterbox (top), 11 => 16: 9 letterbox (center), 7 = 14: 9 full) and Subtitling Mode (0 = non-open subtitle, 1 = subtitles in active image area, 2 = subtitles out of active image area), film / camera (0 = camera mode: source is camera, 1 = film mode: source is film).

  CCI (Copy Control Information) or CPI (Contents Protection Information) are CGMS (0 = prohibited, 1 = unlimited allowed) and APS (0 = no APS, 1 = APS type 1 added, 2 = APS type 2 added, 3 = APS type 3 added), -Source (0 = analog pre-encoding media), and -EPN (1 = content protection (protection at home network output), 0 = no content protection).

  RECI (recording information) is an International Standard Recording Code, and the content is the same as DVD-VIDEO.

  FIG. 43 is a diagram for explaining an example of how EX_PCI of EVOBU is configured, and FIG. 44 is a diagram for explaining an example of how EX_DSI of EVOBU is configured. EX_PCI has the same content as the PCI Packet of DVD-VIDEO, and EX_DSI also has the same content as the PCI Packet of DVD-VIDEO.

  That is, as shown in FIG. 43, the general information (PCI_GI) in EX_PCI includes the logical block number (NV_PACK_LBN) of the navigation pack that is the control pack, the information (EVOBU_UOP_CTL) that controls whether or not EVOBU can be operated by the user, It includes a playback start time (EVOBU_S_PTM), an EVOBU playback end time (EVOBU_E_PTM), an end time (EVOBU_SE_E_PTM) at a sequence end in EVOBU, and a cell elapsed time (C_ELTM).

  Further, the non-seamless angle information (NSML_AGLI) in EX_PCI includes jump destination addresses (NSML_AGL_C # 1_DSTA to NSML_AGL_C # 9_DSTA) of a maximum of nine non-seamless angle cells.

  On the other hand, as shown in FIG. 44, the general information (DSI_GI) in EX_DSI includes the SCR base (NV_PCK_SCR) of the navigation pack, the logical block number (NV_PCK_LBN) of the navigation pack, the end address (EVOBU_EA) of EVOBU, and EVOBU End address (EVOBU_1STREF_EA) of the first reference image (E-pic, etc.), end address of the second reference image (EVOBU_2NDREF_EA) in EVOBU, and end address (EVOBU_3RDREF_EA) of the third reference image in EVOBU And EVOBU object ID number (EVOBU_EVOB_IDN) and EVOBU_ADP_ID (compatible disc type: 0 = applied to DVD Read-Only Disc; 1 = applied to DVD-R, DVD-RW Disc) / C_IDN ( CELL ID number including DSI), EVOBU cell ID number (EVOBU_C_IDN), and cell elapsed time (C_ELTM).

  The seamless playback information (SML_PBI) in EX_DSI includes the seamless EVOBU category (EVOBU_SML_CAT), the end address of the interleaved unit (ILVU_EA), the start address of the next interleaved unit (NXT_ILVU_SA), and the next interleaved unit. Size (NXT_ILVU_SZ), video start time in EVOB (EVOB_V_S_PTM), video end time in EVOB (EVOB_V_E_PTM), audio stop time in EVOB (EVOB_A_STP_PTM), and audio gap length in EVOB ( EVOB_A_GAP_LEN).

  The seamless angle information (SML_AGLI) in EX_DSI includes jump destination addresses (SML_AGL_C # 1_DSTA to SML_AGL_C # 9_DSTA) of up to nine seamless angle cells.

  The EVOBU search information (EVOBU_SRI) in EX_DSI describes the start address before and after the playback start time of EVOBU including EX_DSI in a predetermined time unit (for example, an integer multiple of 0.5 seconds). Specifically, the start address before the playback start time of EVOBU including EX_DSI is described in FWDIxx, and the start address after the playback start time of EVOBU including EX_DSI is described in BWDIxx.

  The synchronization information (SYNCI) in EX_DSI is audio and sub-picture address information synchronized with the EVOBU video data including EX_DSI. Specifically, the SYNCI includes a maximum of eight target audio pack addresses (A_SYNCA 0to7) and a maximum of 32 target sub-picture pack addresses (SP_SYNCA 0to31).

  FIG. 45 is a diagram illustrating an example of how EX_RDI is configured in the case of Interoperable VTS / VR_VOB. EX_RDI is composed of RDI_GI and MNFI. Here, RDI_GI describes the PTM (EVOBU_S_PTM) of the first video frame of the EVOBU and the time (EVOBU_RE_TM) when the EVOBU was recorded. The MNFI is composed of a company code and data.

  FIG. 46 is a view for explaining the file structure of HD_DVD-VR according to another embodiment of the present invention (corresponding to FIG. 3 except for an interoperable file). This file DVD_HD directory contains HD_VMG files, EVOB_TMAP files, ESOB_TMAP files, interoperable VTS.IFO files, interoperable VTS.XML (or JAVA (registered trademark)) files, interoperable VTS_TMAP01 files, ... interoperable VTS_TMAPm file, VR object file, SR object file, still video object file (optional), audio object file, interoperable VTS IFO backup file (optional), interoperable VTS.XML backup file, inter Operable VTS_TMAP01 backup file, Interoperable VTS_TMAPm backup file, EVOB_TMAP backup file, ESOB_TMAP backup file, HD_VMG backup file Files are stored.

  Here, “Interoperable VTS (INT-VTS)” is provided as a bridge for playing HD_DVD-VR EVOB data with HD_DVD-VIDEO Player, and created INT-VTS as shown in FIG. In addition, compatibility with HD_DVD-VIDEO Player is possible. This “interoperable VTS (INT-VTS)” can be created by converting the management information of HD_DVD-VR so that it can be matched with HD_DVD-VIDEO.

  FIG. 47 is a diagram for explaining an example of the relationship between ESOB_SZ and ESOB_S_PKT_POS. The relationship among ESOB_SZ, ESOB_S_PKT_POS, ESOB_E_PKT_POS, and the number of packet groups is as shown in FIG. However, in order to simplify the description, the size of one packet group is 4 TS packets.

  In FIG. 47A, the ESOB starts from the middle of Packet group # 1, passes through Packet group # 2, and continues to the middle of Packet group # 3. In this case, ESOB_SZ becomes 2 in Packet group # 1 & 2, and Packet group # 3 is not counted. ESOB_S_PKT_POS is 2 because ESOB starts from the third packet of Packet group # 1, and ESOB_E_PKT_POS is 3 because ESOB continues to 3 packets of Packet group # 3.

  In FIG. 47 (b), the beginning of ESOB matches the beginning of Packet group # 1, so ESOB_S_PKT_POS = 0. In FIG. 47 (c), the end of ESOB matches the end of Packet group # 3. Therefore, ESOB_SZ = 3 and ESOB_E_PKT_POS = 0. In FIG. 47 (d), there is no ESOB, so ESOB_SZ = 0, ESOB_S_PKT_POS = 1, and ESOB_E_PKT_POS = 3.

  In this embodiment, as shown in FIG. 48, the concept of ESOBU_Cluster is introduced. ESOBU_Cluster is usually the same as ESOBU, but if there is no reference image REF-PIC (I picture in MPEG2) in ESOBU, one ESOBU is included until the next REF-PIC appears, including the previous ESOBU. Define as Cluster. In the case of special playback (fast forward / rewind playback), data access is performed in units of this cluster. In other words, an ESOBU that has a REF-PIC (ESOBU where 1ST_REF_SZ is not 0: ENTRY_ESOBU) must be at the beginning of the cluster, and an ESOBU that does not have a REF-PIC (1ST_REF_SZ is 0: NON-ENTRY_ESOBU) will continue .

  Here, the REF-PIC corresponds to the I-PIC in the case of the conventional MPEG2 compression system, and is a picture in which only this picture becomes one frame (field). In the embodiment of the present invention, since it corresponds to a plurality of image compression methods (MPEG4-AVC, VC-1, etc.), it is necessary to define a picture corresponding to I-PIC even in a stream encoded other than MPEG2. Therefore, instead of I-PIC, REF-PIC is used as a high-level concept term.

  FIG. 49 is a diagram for explaining an example of the relationship between AT_SOBU and a packet. As illustrated in FIG. 49, a packet transmitted within a certain time (AT_SOBU_TM value: 1 second in the example of FIG. 49) is stored as ATS_SOBU.

  FIG. 50 is a diagram for explaining an example of the relationship among ESOBU_SZ, ESOBU_S_PKT_POS, and ES_LAST_SOBU_E_PKT_POS. The relationship among ESOBU_SZ, ESOBU_S_POS, ES_LAST_ESOBU_E_PKT_POS, and the number of packet groups is as shown in FIG. In Video_ES # 1 (at least 1Video-ES has ESTMAP), ESOBU_SZ of ESOBU # 1 is from PACKET_GROUP to 3PACKET_GROUP to which the head of ESOBU # 1 belongs, so ESOB_SZ # 1 = 3 and ESOBU_S_PKT_POS is The value of the number of packets from the beginning of Packet_GROUP to the beginning of ESOBU # 1, similarly ESOBU # 2_SZ = 1, and ES_LAST_ESOBU_E_PKT_POS is the ESOBU from the beginning of the PACKET_GROUP to which the last packet of ESOBU # 2 is the last ESOBU The number of packets up to the end of # 2 is set. The top ES_ADR_OFS is the difference value from the top of the ESOB to the top ESOBU of each ES. In FIG. 50, the difference is 1 Packet_Group.

  FIG. 51 is a diagram illustrating an example of the relationship between AT_SOBU_SZ and AT_SOBU_S_PKT_POS. The relationship between AT_SOBU AT_SOBU_SZ and AT_SOBU_S_PKT is as shown in 51. Since AT_SOBU_SZ of AT_SOBU # 1 is from PACKET_GROUP to 3PACKET_GROUP to which AT_SOBU # 1 belongs, AT_SOB_SZ # 1 = 3 and AT_SOBU_S_PKT_POSPack from the top of AT_SOBU_S_PKT_POSPack The number of packets up to the beginning of ESOBU # 1.

  FIG. 52 is a diagram for explaining an example of the relationship between TS Packets and Packet Groups. The relationship between Packet_Group and Ts_Packet is as shown in FIG. In other words, since Packet_Group is a unit for recording on a disc, PATS which is a transmission time is added to TS_Packet, it is recorded in Packet_Group, and is read for each Packet_Gruop at the time of playback and played according to the time of PATS . As a result, it is possible to reproduce while keeping the time interval at the time of reception.

  FIG. 53 illustrates an example of an apparatus for recording and reproducing AV information (digital TV broadcast program, etc.) on an information recording medium (optical disc, hard disk, etc.) using the data structure according to an embodiment of the present invention. It is a block diagram. As shown in FIG. 53, the recording / playback apparatus includes an MPU unit, a display unit, a decoder unit, an encoder unit, a TV tuner unit, an STC unit (System Time Counter), a D-PRO unit, a temporary storage unit, a disk drive unit, Key input unit, V mixing unit, frame memory unit, TV D / A unit, terrestrial digital tuner unit, 1394 I / F unit, Ethernet (registered trademark) I / F unit, remote control receiving unit, STB (BS digital tuner, etc.), emergency broadcast detection unit, HDD unit. In this configuration, a streamer function is added to the recording / playback DVD recorder.

  The encoder unit includes an A / D unit, a video encoding unit, an audio encoding unit, an SP encoding unit, a formatting unit, and a buffer memory unit. The decoding unit is a separation unit, a video decoding unit, an SP decoding unit, and an audio decoding unit. A TS packet transfer unit, a V-PRO unit, and an audio D / A unit. Furthermore, the STB unit has an antenna for receiving digital broadcasts. Note that the STC unit is configured to count on a 27 MHz base.

  The signal flow at the time of recording is that TS packet data received by the STB unit (or terrestrial digital tuner) is packet-grouped by the formatter unit and stored in the temporary storage unit, and is recorded on the disk when a certain amount of data is accumulated. The The formatter unit 90 is connected to an internal counter 90a for PATS. The arrival time of the TS packet is counted by the PATS counter 90a, and the count value is added to the head of each TS packet and buffered. The counter 90a synchronizes by finely adjusting the count interval by PCR (or SCR), but does not load the PCR (or SCR) value unlike STC102.

  In this operation, when TS packets are received, 170 packets are grouped and a packet group header is created.

  In that case, only the upper 2 bytes (First_Pats_Ext) of the PATS of the first packet of the Packet Group are put in the header, and only the lower 4 bytes of the other PATS are stored together with the TS packet (before the TS packet: PATS). An analog signal input from a terrestrial tuner or line input is digitally converted by an A / D unit. The digital signal is input to each encoder unit. The video signal is input to the video encoding unit, the audio signal is input to the audio encoding unit, character data such as teletext is input to the SP encoding unit, the video signal is MPEG-compressed, and the audio signal is AC3 compressed or MPEG audio-compressed. Data is run-length compressed.

  From each encoder unit (for VR), when the compressed data is packed, it is packetized so that it becomes 2048 bytes and is input to the formatter unit. In the formatter unit, each packet is packed, further multiplexed as a program stream, and sent to the D-PRO unit.

  In the D-PRO unit, ECC blocks are formed for every 16 logical blocks, error correction data is attached, and the drive unit records the data on the disk. Here, since the drive unit is in a seek state or a track jump, in the busy state, the drive unit is put in the HDD buffer unit and waits until the DVD-RAM drive unit is ready. Furthermore, the formatter unit creates segmentation information during recording and periodically sends it to the MPU unit (GOP head interrupt, etc.). The segmentation information includes the number of EVOBU (ESOBU) packs, the end address of a Ref_picture (I picture) from the beginning of EVOBU (ESOBU), the playback time of EVOBU (ESOBU), and the like.

  The signal flow during reproduction is read from the disk from the drive unit, corrected by the D-PRO unit, and input to the decoding unit. The MPU unit determines whether the input data is VR data or SR data (determined by Cell TYPE), and sets the type in the decoder unit before reproduction. In the case of SR data, the MPU unit determines the PID to be played based on the ESI number to be played, determines the PID of each item (video, audio, etc.) to be played from the PMT, and sets it in the decoder unit. Based on the PID, the decoder unit sends each TS packet to each decoding unit at the separation unit. Further, the packet is sent to the TS packet transfer unit, and transmitted in the form of a TS packet to the STB unit (IEEE1394 I / F unit) according to the arrival time. Each decoding unit performs decoding, converts the analog signal into a D / A unit, and displays it on the TV. In the case of VR data, the separation unit sends it to each decoding unit according to a fixed ID. Each decoding unit performs decoding, converts the analog signal into a D / A unit, and displays it on the TV.

  During playback, the pack data read from the disk is analyzed by the separation unit. If the pack contains a TS packet, it is sent to the TS packet transfer unit, and then sent to each decoder for playback. Do. When transferring to the STB (or when transmitting to an external device such as a digital TV), the TS packet transfer unit transfers only the TS packet at the same time interval as when it arrives (see FIG. 52). The STB unit performs decoding, generates an AV signal, and displays the AV signal on the TV through the intra-streamer video encoder unit.

  The features of the medium 100 (100a) used in the apparatus shown in FIG. 53 can be summarized as follows. That is, this medium is composed of a management area 130 and a data area 131. In the data area, data is divided into a plurality of object data (ESOB) and each object data is composed of a collection of data units (ESOBU). Is done. One data unit (ESOBU) is composed of a packet group obtained by grouping digital broadcast signals conforming to MPEG-TS into a plurality of packets for each TS packet (see FIGS. 1 and 37). On the other hand, the management area 130 has EX_PGC information (EX_PGCI) as information for managing the playback procedure, and this EX_PGC information includes EX_CELL information (EX_CI). Further, the management area 130 has information for managing object data (ESOB).

  The apparatus shown in FIG. 53 can perform stream recording on medium 100 (100a) having the above data structure in addition to video recording. At this time, in order to extract the program map table PMT and the service information SI from the TS packet stream, the MPU unit 80 uses a service information extraction unit (not shown; firmware constituting a part of the management data creation unit 80B). Configured to have. An attribute information creation unit (not shown; a part of the management data creation unit 80B) that creates attribute information (such as a PCR pack number or a PCR LB number number) based on the information extracted by the service information extraction unit. Configured to have firmware).

  FIG. 54 is a diagram for explaining an example of a system model of the recorder. This system model includes two systems, a recording / reproducing system based on MPEG-PS (VR system) and a recording / reproducing system based on MPEG-TS (SR system). The SR system corresponds to two types of stream recording of type A (PTM base) and type B (PATS base).

  FIG. 55 is a flowchart (overall operation processing flow) for explaining an example of the overall operation of the apparatus shown in FIG. There are five types of data processing here: recording processing, playback processing, data transfer processing (digital output processing to STB, etc.), program setting processing, and editing processing. For example, when the apparatus of FIG. 53 is turned on, the MPU unit 80 performs initial setting (at the time of factory shipment or after setting by the user) (step ST10), performs display setting (step ST12), and the user Wait for operation. When the user inputs a key from the key input unit 103 or the remote controller 103a (step ST14), the MPU unit 80 interprets the contents of the key input (step ST16). Depending on the result of the input key interpretation, the following four data processes are executed as appropriate.

  That is, if the key input is a key operation for setting timer reservation recording, for example, the program setting process is started (step ST20). If the key input is a key operation for starting recording, the recording process is started (step ST22). If the key input is a key operation for starting playback, playback processing is started (step ST24). If the key input is a key operation for digital output to the STB, digital output processing is started (step ST26). If the key operation is an editing process, the editing process is started (step ST28).

  The processes in steps ST20 to ST28 are appropriately performed in parallel for each task. For example, during the reproduction process (step ST24), a process of digital output to the STB (step ST26) is executed in parallel. Alternatively, a new program setting process (step ST20) can be processed in parallel during the recording process (step ST22) that is not timer reservation recording. Alternatively, the reproduction process (step ST24) and the digital output process (step ST26) can be performed in parallel during the recording process (step ST22) by taking advantage of the characteristics of disc recording that can be accessed at high speed. It is also possible to perform a disc editing process (step ST28) during recording on the HDD.

  FIG. 56 is a flowchart (edit operation process flow) for explaining an example of the edit process (step ST28). Upon entering the editing process, four processes (any of A to D) can be entered in accordance with the editing content (step ST280). When entry point editing processing (step ST282A), copy / move processing (step ST282B), deletion processing (step ST282C), or playlist creation processing (step ST282D) is completed, the date and time of program update by this editing is indicated by each management information. (EX_PGI, EX_IT_TXT, EX_MNFI) is set (step ST284).

  The program update date and time may be set when any of program information EX_PGI, cell information EX_CI, EVOB, and ESOB is changed. Here, when EVOBI and / or ESOBI are changed, the editing time (EDIT_TIME) of EVOBI and / or ESOBI can be set to ESOB_EDIT_TIME or the like (not shown). Alternatively, the program update date and time may be set.

  Incidentally, in the process of step ST284, the manufacturer ID of the device that has performed any of the operations of steps ST282A to ST282D may be set to the editor ID (LAST_MNF_ID). This editor ID can be set (or updated) according to the ID information of the device used at that time whenever any of PGI, CI, and SOB (or VOB) is changed.

57 and 58 are flowcharts for explaining an example of the recording operation of the apparatus of FIG. Data processing during stream recording is as follows:
d1) First, a program to be recorded is determined by using an EPG (Electronic Program Guide) in the program setting process, reception is started, and the determined program is recorded;
d2) Upon receiving a recording command from the key input unit 103, the MPU unit 80 reads management data from the disk 100 (or the HDD unit 100a) via the drive unit 51, and determines a writing area. At this time, the file system is checked to determine whether or not recording is possible. If recording is not possible, the fact is indicated to the user and the process is stopped. If recording is possible, pre-recording processing is performed (step ST105 in FIG. 57). Thereby, the MPU unit 80 determines a recording position, creates management information (such as HDVR_MG), and writes necessary information in each management area. At this time, when the recording target is not digital broadcasting (for example, analog video input or analog TV broadcasting) (NO in step ST106), video recording (VR) can be adopted as a recording format instead of stream recording (SR). In this case, the process proceeds to the VR recording process.

d3) When the recording target is digital broadcasting (Yes in step ST106), the MPU unit 80 checks whether the recording target stream can be analyzed. When the analysis is possible (YES in step ST107), the MPU unit 80 performs setting so that the management information is created as a PTM-based type A stream (step ST109A), and when the analysis is impossible (NO in step ST107), the PATS base Is set so that management information is created as a type B stream (step ST109B). Thereafter, the write start address of the stream data (video data) is set in the drive unit 51 to prepare for recording the data (step ST112);
d4) In this preparation stage, the count time is reset for the STC unit 102. Here, the STC unit 102 is a system timer, and recording and / or reproduction is performed based on the STC value.

d5) Read the PAT of the program to be recorded, determine the PID for capturing the PMT of the target program, read the target PMT, and determine the PID of each data (video, audio) to be decoded (recorded) . At this time, PAT and PMT are stored in the work RAM unit 80A of the MPU unit 80, and these (PAT, PMT) are written in the management information (HDVR_MG). At that time, the VMG file data is written in the file system (see FIG. 3 or 46), and the necessary information is written in the VMGI (HDVR_MGI in FIG. 4);
d6) Recording setting is performed for each unit (step ST114). At this time, the setting of the separation of each data and the reception setting of the TS packet are performed in the formatter unit 90. At this time, the PID of data to be recorded is set, and only the target video stream is recorded. Further, the buffer 91 is set to start holding TS packets (step ST116). Then, the formatter unit 90 starts operation as follows.

d7) Create ESOB_ESI from PMT (step ST120 in FIG. 58);
d8) Subsequently, a stream of TS packets to be recorded is taken into the buffer 91 (step ST130). When a certain amount of data in the buffer 91 has accumulated (YES in step ST140), ECC processing is performed through the D-PRO unit 52, and the ECC-processed data is recorded on the disc 100 (and / or 100a) (step ST142). ;
d9) During recording, periodically (before the buffer RAM 91 of the formatter unit 90 becomes full), the segmentation information is stored in the work RAM 80A of the MPU unit 80 (Yes in step ST144; step ST146). The segmentation information here is ESOBU segmentation information, such as the ESOBU head address, ESOBU pack length, I-Pic (reference image) end address, ESOBU arrival time (ATS), and the like.

  d10) After storing the segmentation information in the work RAM 80A (step ST146), or when it is not time to store the segmentation information (NO in step ST144), the MPU unit 80 determines whether to disconnect the ESOB and disconnects (step ST147). Yes) executes ESOB cut processing (FIG. 59).

d11) It is checked whether or not the recording is finished (whether or not the recording end key has been input or the remaining capacity of the disc (100 / 100a) has been exhausted). When the recording is finished (YES in step ST148), the remaining part is separated from the formatter unit 90. Information is captured and added to the work RAM 80A, the data is recorded in the management data (VMGI or HDVR_MGI), the average recording rate at the time of recording is recorded, and the remaining information is recorded in the file system (step ST150). );
d12) If it is not the end (NO in step ST148), the process proceeds to d8), and the data capture and reproduction are continuously performed.

  Here, in order to display the contents of the stream data being recorded on a TV or the like, the stream data to be recorded is transferred to the D-PRO unit 52 and simultaneously sent to the decoder unit 59 for simultaneous recording monitoring. May be. In this case, the MPU unit 80 sets the playback to the decoder unit 59, and then the decoder unit 59 automatically performs the playback process. The D-PRO unit 52 collects stream data to be recorded for every 16 packs as an ECC group, attaches the ECC, and sends the ECC group to the drive unit 51 (and / or the HDD 100a). However, if the drive unit 51 is not ready for recording on the disc 100, it is transferred to the temporary storage unit 53, waits until it is ready to record data, and records to the disc 100 when ready. Start. Here, since the temporary storage unit 53 holds recording data of several minutes or more by high-speed access, a large-capacity memory is assumed. The MPU unit 80 is directly connected to the D-PRO unit 52 through the microcomputer bus in order to read and write the file management area of the disk 100 and the like.

  The signal flow during recording can be summarized as follows. That is, MPEG-TS packet data received by the STB 83 (or the terrestrial digital tuner 89) is packet-grouped by the formatter unit 90 and stored in the buffer 91, and when a certain amount of data is accumulated in the buffer 91 ( When one or an integral multiple of CDA is accumulated, the data is recorded on the disc (100 and / or 100a).

FIG. 59 is a flowchart (ESOB cut process flow) for explaining an example of the ESOB cut process (step ST160). An example of ESOB cut processing is described below:
e1) It is checked whether or not to record continuously, and if not continuously recorded (No in step ST1600), this process is terminated;
e2) When recording continuously (YES in step ST1600), 1 is set in ESOB_CONN_SS (FIG. 23) in ESOBI of the next ESOB (step ST1601);
e3) The ESTR_FI of the ESOB is set (step ST1618), and this process ends.

  FIG. 60 is a flowchart for explaining an example of the buffer fetch process (step ST130) (buffer fetch process when 6 bytes of PATS are managed). At the time of recording, TS packet data received by the STB unit (or terrestrial digital tuner) is packet-grouped by the formatter unit, stored in the work RAM, and when a certain amount of CDA (1 or an integer multiple of CDA) is stored. Is recorded on the disc. In this operation, when TS packets are received, 170 packets are grouped and a packet group header is created. Specifically:

f1) A TS packet is received (step ST1300);
f2) It is checked whether or not the STC has made one round (Wrap-around). If one round has been made (Yes in step ST1301), CNT_SEG is created from the position information of the TS packet at the time of one round. Thereby, the position information CNT_SEG_S_PKT_POS (see FIG. 20) of the TS packet at the time when the time count of the STC unit 102 makes one round is registered in the management information CNT_SEGI (step ST1303). If one round has not been made (STC is continuously counting) (NO in step ST1301), or if registration of CNT_SEGI is completed, the process proceeds to the next process.

f3) If it is the head of the packet group (Yes in step ST1306), Header_ID: 0x00000fa5 is set (step ST1308A), and if it is not the head (No in step ST1306), the process proceeds to f6);
f4) In step ST1308A, the arrival time of the TS packet is set as PATS, the lower 4 bytes of PATS are arranged before the TS packet, and the upper 2 bytes of the first PATS are set as FIRST_PATS_EXT in the Packet Group Header.

  f5) In the TS packet taken into the TS packet data area, the lower 4 bytes of the PATS are added in front of the TS packet (step ST1317C), and set in the packet group data rear (step ST1317D).

  f6) It is determined whether or not the packet group has ended (whether or not 170 TS packets have been grouped). If the packet group has not ended (NO in step ST1322), the process returns to f1). When the packet group ends (YES in step ST1322), PKT_GRP_GI setting processing (step ST1340), CCI or CPI processing (step ST1330), and MNFI processing (step ST1350) are performed, and group data for one packet group is stored in the buffer RAM 91. (Step ST1332).

  FIG. 61 is a flowchart (PKT_GRP_GI setting process flow) for explaining an example of the packet group general information setting process (step ST1340).

g1) The packet type is checked, and in the case of an MPEG-TS packet, PKT_GRP_TY is set to 01. In other cases, a value corresponding to the type is set to PKT_GRP_TY (step ST13400);
g2) A value (for example, “11”) corresponding to the BOOK version of the corresponding standard is set in VERSION, and a STUF bit indicating whether stuffing has been performed (for example, “0”) is set (step ST13400);
g3) When “0” is set in the STUF bit, “0xaa” is set in Valid_PKT_Ns (consisting of the number of valid packets in the packet group and the upper 2 bytes of PATS for the first packet) (step) ST13406).

  FIG. 62 is a flowchart (ESI setting process flow) for explaining an example of the stream information (ESI) creation process (step ST120).

h1) Check PSI and SI, and check the number of set streams (step ST1201);
h2) Repeat h4) to h5) by the number of set streams (in the case of YES in step ST1230);
h3) Check the stream type from PSI and SI (step ST1203), determine whether the stream is a video stream, an audio stream, or any other stream, and shift to the next stream check;
h4) At that time, the stream type is divided into types such as MPEG1 video, MPEG2 video, MPEG1 audio, MPEG2 audio,..., internal data is checked according to each type, and each attribute information is read out.

h5) In the case of a video stream (step ST1213A), ES_TY = 0 is set, each attribute information is set, in particular, resolution data, aspect information, etc. are extracted to create a V_ATR (step ST1213C), and the process proceeds to h8);
h6) In the case of an audio stream (step ST1215A), ES_TY = 0x40. Then, each attribute information is set, in particular, the coding mode, sampling frequency, number of channels, etc. are extracted, A_ATR is created (step ST1215C), and the process proceeds to h8);
h7) For other streams (step ST1217A), set ES_TY = 0x80, set each attribute information (step ST1217C), and move to h8);
h8) It is checked whether there is any other stream for which ESI has not been created, and the process proceeds to the next stream check (in the case of NO in step ST1230).

FIG. 63 is a flowchart for explaining an example of the stream file information (ESTR_FI) creation process in the recording end process (step ST150);
j1) In order to increase ESOBI by 1, the search pointer (ESOBI_SRP) is increased by 1, an area for that is secured, and 0: MPEG_TS is set in PKT_TY (step ST1500);
j2) The recording time is set to ESOB_REC_TM (step ST1502A). Here, the clock inside the apparatus is set and corrected by TDT (Time Data Table), and an accurate time is always obtained;
j3) At that time, ESOB_S_PTM and ESOB_E_PTM are extracted from the stream, the STC discontinuity information (for example, CNT_SEGN in FIG. 36) is checked, and the start PTM and end PTM of the ESOB corresponding to the ESOBI increased in j1) are set. (Step ST1502A).

  j4) When the stream type is a TS stream (ARIB, DVB) (Yes in step ST1506), 188 is set in AP_PKT_SZ and 16 is set in PKT_GRP_SZ (step ST1508A). If not (NO in step ST1506), a value suitable for the broadcasting system is set in AP_PKT_SZ (step ST1510). For example, in step ST1508A, JPN (Japan) is set as country_code and JapanISDB is set as AP_FORMAT1. In step ST1510, the country code (for example, USA) of the corresponding device is set as country_code, and the corresponding broadcasting system (for example, ATSC) is set as AP_FORMAT1.

  j5) It is determined whether or not the PSI and SI information are valid. If they are invalid (that is, unknown stream: NO in step ST1511), ESOB_TY: 1 is set to b12, or each value is set to 0xff (step ST1513), j9 )

j6) When the PSI and SI information is valid (that is, the stream is not unknown: NO in step ST1511), TS_ID, NETWORK_PID, and PMT_ID (PID of PMT used in the ESOB: PID is 13 bits) from PAT. Two methods, a method of describing with actual data and a method of describing the order in the PMT, can be considered) (step ST1514);
j7) Program_Number (SERVICE_ID in PMT), PCR_PID, etc. are set from PMT, and for FORMAT_ID and VERSION, the internal tuner is the default method in the device, and in the case of external digital input The value of Registration_Descriptor sent from the digital input is set. Also, ESOB_TY is set according to the TMAP type (step ST1516A).

j8) Further, the number of recorded ESs, the number of video ESs, and the number of audio ESs are set (step ST1516A). (Information on all ESs being broadcast: number is set in the PMT, but since not all ESs are recorded at the time of recording, the number of recorded ESs is set.)
j9) GPI setting processing (step ST1530), TMAP setting processing (step ST1540), and the like are performed, and a TMAPI is created for each stream based on each segmentation information.

j10) Subsequently, the LB address at which recording is started is set to ADR_OFS, and a default PID is set (step ST1550A). Here, the default video PID is the value of the video with the youngest component tag value, or in the case of multi-view TV, the ESI of the video stream corresponding to the component tag described in the main component group Corresponds to the number;
j11) Then, the edit date is set (step ST1554).

FIG. 64 is a flowchart for explaining an example of the GPI setting process (step ST1530). This GPI setting process can be performed as follows:
k1) Checking the type of stream (step ST15300B);
k2) When multiple programs are made into one stream (Yes in step ST15300B), ESOB_TY is set to GPI, GPI_TY is set to 0, all PRIORITY = 0, one program is configured with 1 GPI, and the number of groups is set (step) ST15302B), moving to k5);
k3) In case of broadcast corresponding to rain (step ST15300B YES) (step ST15304B YES), ESOB_TY is set to GPI, GPI_TY is set to 40h, the higher hierarchy is set to PRIORITY: 1, and the others are set to PRIORITY: 2. Each layer is configured with 1 GPI, the number of groups is set (step ST15306B), and the process proceeds to k5).

k4) In the case of multi-view broadcasting (yes in step ST15308B), ESOB_TY is set to GPI, GPI_TY is set to 40h, the higher hierarchy is set to PRIORITY: 1, and the others are set to PRIORITY: 2, and one view is configured with 1 GPI (step ST15310B). ). If it is not multi-view broadcasting (NO in step ST15308B), 1 is set in ES_TMAP_Ns and no GPI is set in ESOB_TY (step ST15321B). Then, it is determined whether there is another ES to be a group (GP). If yes (step ST15314B YES), the process proceeds to k1). If not (NO in step ST15314B), the number of groups is set, and k5 )
k5) Check if there is another group (GP). If there is, go to k1). If not, create and register a playlist with the currently selected PID group (step ST15316B). Terminate the process;
k6) As a result, when playback is performed in the currently selected group, it is possible to play back the playlist automatically created in step ST15316B.

FIG. 65 is a flowchart for explaining the TMAP setting process (step ST1540). An example of the TMAP setting process is described below:
m1) Determine the structure of ESOB / EVOB (step ST15400);
m2) In the case of ESOB, TMAP_TY is determined (step ST15403). If this ESOB is PTM-based, the number of GPs is taken into consideration, the ES for creating the STMAP is determined, the number of ESs (the number of video ESs) is set as the TMAP number, and the ES_PID created for each TMAP is set. (However, 1TMAP is not necessarily attached to 1GP. If this TMAP is not attached, playback, search, special playback, etc. are performed using other ES_TMAP of the same ESOB.) On the other hand, PATS-based ESOB (AT_ESOB) Alternatively, in the case of EVOB, one TMAP is added (see FIG. 25 for the data structure of PATS-based TMAP);
m3) Set ESOB (PTM base) / EVOB start time / end time, start time / end time for each TMAP, number of entries, arrival time of first packet of ESOB (PATS base), arrival time of final packet, etc. (Step ST15405).

  m4) Add TMAPT, ENTRY information based on the segmentation information (in case of ESOB), 1ST_REF_PIC_SZ for each VIDEO_ES (set end address of the first I-pic of the target VES, set to 0 if there is no I-Pic), Set ESOBU_SZ (indicating ESOBU size in PacketGP units) and ESOBU_S_PKT_POS (start position of SOBU in PacketGP). ENTRY information in the case of AT_SOBU sets AT_SOBU_SZ (indicating the size of AT_SOBU in PacketGP units), AT_SOBU_S_PKT_POS (position in the first packet group of AT_SOBU (in PKT units)). In the ENTRY information in the case of EVOBU, 1ST_REF_PIC_SZ (set the end address of the first I-pic), EVOBU_SZ, the number of playback frames, etc. are set (step ST15407). Here, the TMAPT information is recorded in a separate file.

m5) Update STMAP editing date (step ST15409);
m6) It is determined whether or not the STMAP sum of the STR_FI exceeds 2MB (YES in step ST15411), and set TOTAL_STMAP_SZ to 2MB (or the value obtained by adding ESOB divided by 2MB) and ESOB The STMAP is cut so that it does not exceed 2 MB, a new STR_FI is created, a new ESOB is registered there (step ST15413), and this process ends.

  m7) If not exceeding (NO in step ST15411), the sum of STMAP is set to TOTAL_STMAP_SZ (step ST15415), and this process is terminated.

  With the above processing, the total of STMAP should not exceed 2MB (the upper limit of available memory size) (the total of STMAP is considered to be the previous TOTAL_STMAP_SZ plus the ESOB STMAP_SZ added this time) .

  In addition, as a method of keeping the size of STMAP in 2MB, the method of increasing STR_FI by cutting ESOB in two as in the above processing, the method of increasing STR_FI without cutting ESOB as it is, A method of expanding the STMAP interval by changing ESOBU_PB_TM_RNG is conceivable.

FIG. 66 is a flowchart for explaining EVOB / ESOB structure setting processing (step ST15400). An example of this EVOB / ESOB structure setting process is described below:
n1) The recorded recording time is checked (step ST154000). If the recording time is 2 hours or less, the process shifts to n2). If the recording time is 2 hours to 4 hours, the process shifts to n3). (Step ST154001);
n2) EVOB / ESOB_PB_TM_RNG is set to 0, and EVOBU / ESOBU_ENT is created so that ESOBU becomes 0.4 s to 1.0 s from the segmentation information (information from 0.4 s to 1.0 s) (step ST154002). n5);
n3) 1 is set in EVOB / ESOB_PB_TM_RNG, and EVOBU / ESOBU_ENT is created from the segmentation information (information from 0.4 s to 1.0 s) so that ESOBU is 1.0 s to 2.0 s (step ST154003). n5);
n4) 2 is set in EVOB / ESOB_PB_TM_RNG, and EVOB / ESOBU_ENT is created so that ESOBU becomes 2.0 s to 3.0 s from the segmentation information (information from 0.4 s to 1.0 s) (step ST154004);
n5) This process ends.

FIG. 67 is a flowchart for explaining CP_CTL_INFO (CCI or CPI) creation processing (step ST1220). An example of this CP_CTL_IFO setting process will be described below:
p1) Check whether or not there is copy information (digital copy control descriptor) in the latest PMT and EIT. If there is (YES in step ST12200), the copy control descriptor is extracted (step ST12204), and the CCI is based on the information. (APS, digital copy control information, etc.) are configured and set (step ST12206), and the process proceeds to p3). At this time, PKT_GRP_GI: STUF is set to 1, and the number of valid packets is set to PKT_GRP_GI: VALID_PKT_Ns.

p2) If there is no copy information in the received TS packet (No in step ST12200), the copy is set as free (step ST12202);
p3) Check whether there is a content usage descriptor in the latest PMT or EIT. If there is (Yes in step ST12208), extract the content usage descriptor (step ST12212), and set ICT and EPN based on the information. (Step ST12214A);
p4) If there is no content usage descriptor (NO in step ST12208), ICT and EPN are configured as copy free (step ST12210). Note that ICT, EPN, and the like in step ST12214A or step ST12210 are also described in the description of CCI with reference to FIG.

In addition, another example of the CCI setting process will be explained as follows:
1) Check whether there is copy information in the latest PMT and EIT. If there is, copy information is configured and set based on that information, then move to 3);
2) If there is no copy information in the received TS packet, the same information as the previous pack is configured as copy information;
3) Check whether there is a content usage descriptor in the latest PMT or EIT. If there is a content usage descriptor, if there is a change in the middle of the packet group, the previous packet group is changed from the changed location to a new packet group. Dummy data is inserted, and after the change is made a new packet group, CCI is set based on the information. At this time, PKT_GRP_GI: 1 is set to STUF, and the number of valid packets is set to PKT_GRP_GI: VALID_PKT_Ns;
4) If there is no copy information in the received TS packet, configure CCI or CPI as copy free.

FIG. 68 is a flowchart (program setting process flow) for explaining an example of a program chain (PGC) creation process (including a program setting process) in the recording end process (step ST150). Hereinafter, an example of PGC creation processing will be described:
q1) It is checked whether it is the first recording on the disc. If it is the first (YES in step ST1600Z), a new ORG_PGC is created (step ST1602Z). If it is not the first (step ST1600Z no), an already recorded PGC ( (ORG_PGC) is set to add the program PG (step ST1604Z);
q2) Erase permission is set to PG_TY: 0, the number of CELLs is set to Cell_Ns, and the ESI number of the video is also set (step ST1700Z).

q3) In step ST1700Z, if the digital broadcast to be recorded is ARIB and the language_code of the short format event descriptor in the EIT is "jpn", 0x12 is set in the CHR of VMG_MAT and the second area of PRM_TXTI Set to EVENT_NAME and set representative image information to REP_PICTI;
q4) An absolute number of PG is set in PG_INDEX, and when referring from other application software or the like, reference in units of PG is possible (step ST1702Z). At that time, the start cell number is set in the resume information (PG_RSM_IFO) and the start time (start PTM) is set.

q5) Information indicating a streamer is set in CELL_TY (for example, the cell type included in the cell information EX_CI in FIG. 34) (step ST1704Z);
q6) In the setting of step ST1704Z, an ESOB number to be referred to is set, a representative (video) ESI number (ESIN) is set as an ES to be played back, the number of entry point information EPI (FIG. 35), and playback start PTM , End PTM, and entry point EP are set. Further, the discontinuous segment CNT_SEG as illustrated in FIG. 20 is read, the number of times is set to, for example, CNT_SEGN in FIG. 36, and the block number of the ESOB to be reproduced is set.

  q7) Furthermore, in the setting of step ST1704Z, the head information is set in PG_RSM_INF (playback start PTM, video ESI number, audio ESI number, dual-mono main and sub information, etc.) so that playback can be started from the beginning. In addition, as a factor in automatically adding EP, in the relationship between video and time, the first packet (Unit Start Indicator) of the video frame is set as a condition for a certain period of time and video mode change (when aspect ratio and motion vector are large). A combination of GOP head packets (the head of the sequence header, the head of the I-PIC) is conceivable. Furthermore, in the case of audio, there may be a case where the voice packet (unit start indicator, frame header) is combined with the conditions in the audio change (volume change, etc.) / Audio mode (ST / MONO).

FIG. 69 is a flowchart (overall playback operation flow) for explaining an example of the playback operation. Data processing during playback is for example as follows:
r1) First, check the disc, check whether it is Recordable / Rewritable Disc (R, RW, RAM), and if it is not Recordable / Rewritable Disc, return to that effect and end;
r2) If it is a recordable / rewritable disc, the file system of the disc is read (step ST207), and it is checked whether there is recorded data. If there is no recorded data, “not recorded” is displayed and the process ends. ;
r3) The VMG file is read (step ST207), and the program and cell to be played are determined (determined by default or selected by the user) (step ST208). Here, when playback in the recording order is selected, playback is performed according to ORG_PGCI. When playback is performed for each program (edited by the user), playback is performed according to UD_PGC (play list) of the number corresponding to the program to be played back. I do;
r4) Title information to be played back (set to perform only transfer processing to STB if PSI and SI information are unknown), resume information (PL_RSM_IFO, PG_RSM_IFO), ESOB / EVOB to be played back by cell information (EX_CI), playback A start PTM or the like is determined, and the file pointer (logical address) for starting playback and the ESI of the stream to be played are determined from the playback start PTM. Further, each decoder unit is set according to the values of STI and ESI to prepare for reproduction (step ST211A).

r5) Next, the playback method is determined from AP_FORMAT1, 2 (see FIGS. 12 and 15) (STB to which the playback stream is sent is determined). (Step ST211B)
r6) If the PSI and SI information is valid (YES in step ST211C), a stream to be reproduced is determined from the PSI and SI information, and the PSI and SI information is stored in the work RAM (step ST211D). If the PSI and SI information is not valid (NO in step ST211C), it is set to transmit all streams to the STB (step ST211E).

  r7) Next, the process at the start of reproduction is performed. First, check if the playback target is ESOB. If it is ESOB (YES in step ST213), the decoder setting process is entered (step ST217). If it is not ESOB (NO in step ST213), only TS packet transmission processing is performed (step ST219).

  r8) Subsequently, the cell reproduction process is performed (step ST220), and it is checked whether or not the reproduction is completed. If the reproduction is completed (Yes in step ST230), an error check is performed. If there is an error (YES in step ST240), that fact is displayed (step ST242), and a reproduction end process is performed (step ST244). If there is no error (NO in step ST240), other processing at the end of reproduction is performed (step ST246), and this operation is terminated.

r9) If the reproduction is not finished (NO in step ST230), the next cell is determined from PGCI (step ST232), and the process returns to step ST211A. Then, it is checked whether or not the setting of the decoder unit 59 (step ST217) has been changed. If the setting has been changed, the change attribute is set in the decoder unit 59 so that the decoder setting is changed to the next sequence end code. Do;
r10) Thereafter, the same processing (steps ST211A to ST232) is repeated while checking whether or not the reproduction has ended (step ST230).

FIG. 70 is a flowchart for explaining the decoder setting process (step ST217). Decoder setting examples are described below:
s1) When the reproduction target is ESOB (Yes in step ST2170), a group to be reproduced is determined, and an ES to be reproduced is determined according to GPI (step ST2171). If the playback target is EVOB (NO in step ST2170), step ST2171 is skipped;
s2) Read the attribute information (STI, ESI) of the ESOB (or EVOB) to be played back (step ST2172);
s3) It is checked whether the ESOB (or EVOB) to be played is in a format that can be supported by a recorder (such as the apparatus shown in FIG. 53 or 54). If the response is not possible (No in step ST2173), the device is set not to reproduce, and the display mute is set (step ST2175).

s4) If the video to be played is playable (YES in step ST2173), preparation for playback is made (step ST2174A). In this case, the PID can be used as it is when a 13-bit PID is set, but if it is set in the order in the PMT, the PID is determined with reference to the PMT;
s5) It is checked whether or not the audio to be reproduced is reproducible. If it is possible (YES in step ST2176), preparation for reproduction is performed (step ST2177A). In this case, the PID can be used as it is when a 13-bit PID is set, but when it is set in the order in the PMT, the PID is determined with reference to the PMT. If it is not possible (No in step ST2176), the device is set not to play back and audio mute is set (step ST2178);
s6) For example, copy management processing is performed based on CCI or CPI information including the content created in the processing of FIG. 67 (step ST2179).

FIG. 71 is a flowchart for explaining an example of processing during cell playback. The cell playback process is, for example, as follows:
t1) The EX_CELL start file pointer FP (logical block number LBN) and end file pointer FP (logical block number LBN) are determined from the contents of TMAPI, and the ESOBU_ENTRY that starts from the start time and end time in the EX_CI, and the end ESOBU_ENTRY is determined, the data length of entries up to the target ESOBU_ENTRY is accumulated in ADR_OFS, and the start address (LB = FP) and end address are obtained. The remaining EX_CELL length is a value obtained by subtracting the start address from the end address, and the reproduction start time is set in the STC (step ST2200). Further, the PID to be reproduced is determined and set in the decoder (STB, digital tuner). In this case, the PID can be used as it is when a 13-bit PID is set, but when it is set in the order in the PMT, the PID is determined with reference to the PMT.

t2) ESOB continuous check processing is performed (step ST2201);
t3) A read process during reproduction is executed, and a read address and a read size are determined from the start file pointer (step ST2206);
t4) The read unit size to be read and the remaining cell length are compared. If the remaining cell length is large (Yes in step ST2207), a value obtained by subtracting the read unit size to be read from the remaining cell length is set to the remaining cell length (step ST2208). . If smaller (No in step ST2207), the read length is set to the remaining cell length, and the remaining cell length is set to 0 (step ST2209);
t5) The read length is set to the length of the read unit, and the read address, read length, and read command are set in the drive unit (step ST2210).

  t6) When the data transfer is started (YES in step ST2212), it waits for 1 ESOBU to be accumulated in the buffer. When 1 ESOBU has been accumulated (Yes in step ST2214), data for 1 ESOBU is read from the buffer (step ST2216), and buffer decoder transfer processing is performed (step ST2220). Then, after incrementing the read file pointer FP and setting the MPEG decoder to the normal mode (step ST2224), the process proceeds to t7).

t7) It is checked whether or not the transfer is completed. If it is completed (Yes in step ST2226), the process proceeds to t8);
t8) It is checked whether or not an angle key or the like has been pressed. If it has been pressed (YES in step ST2238), it is checked whether or not there is a GPI. If there is GPI (Yes in step ST2239), GP switching processing is performed (step ST2240), and if there is no (step ST2239 no), the processing proceeds to step ST2228 without doing anything;
t9) If the angle key or the like has not been pressed (NO in step ST2238), it is checked whether Skip SW has been pressed. If Skip SW is pressed (YES in step ST2248), SKIP processing (step ST2250) is performed.

t10) If Skip SW has not been pressed (NO in step ST2248), it is checked whether STOP SW has been pressed. If Stop SW is pressed (Yes in step ST2258), the interruption information (RSM_IFO) is stored in PG_RSM_IFO for title playback, and PL_RSM_IFO for playlist playback, and the termination process is performed (step ST2260A);
t11) If the Stop SW is not pressed (NO in step ST2258), the remaining cell length is checked. If the remaining cell length is not “0”, that is, if the current cell is not the last cell (NO in step ST2228), the process returns to step ST2206. If the remaining cell length is “0” (Yes in step ST2228), this process ends.

FIG. 72 is a flowchart for explaining the ESOB continuous check process (step ST2201). ESOB continuous check processing during playback is as follows, for example:
u1) It is checked whether or not the previous ESOB has been recorded continuously (ESOB_CONNI in FIG. 23). If it has not been recorded continuously (NO in step ST22010), this process is terminated;
u2) When ESOBs are continuously recorded (Yes in step ST22010), settings are made so as to continuously play between ESOBs (processing such as inserting a black screen is stopped until playback is started between ESOBs) ( Step ST22011).

FIG. 73 is a flowchart for explaining an example of data transfer processing from the buffer RAM to the decoder. An example buffer data decoder transfer process is described below:
v1) The number of packet groups in the buffer RAM is checked, and if there is no one packet group, the processing in FIG. 73 is skipped. If there are one or more packet groups in the buffer RAM, the first packet group is set to be processed (step ST22200);
v2) The target packet group is read from the buffer RAM (step ST22201). The head of the packet group is detected by the packet group length and Header_ID (FIG. 37) functioning as Sync_Pattern;
v3) The STUF bit (FIG. 38) of the packet group header is examined, and if 1 is set, a valid packet is extracted according to the value of VALID_PKT_Ns (step ST22202A). If 1 is not set in the STUF bit, it is assumed that 170 Packets is the number of valid packets.

  v4) Set FIRST_PATS_EXT to the upper 2 bytes of the PATS of the first packet in the packet group, and then send each TS packet to the decoder unit (STB unit) at the time calculated as the lower 4 bytes of the immediately preceding PATS (step ST22202B). In other words, the PATS accuracy is detected by PATS_SS, and based on the accuracy information, the TS packet transfer time is calculated from PATS (FIRST_PATS_EXT + PATS of the previous TS packet: accuracy 4 bytes) and PATS_SS. (Step ST22202B), each TS packet is sent to the decoder unit (STB unit) at that time (step ST22203).

  If the precision is 6 bytes, FIRST_PATS_EXT is set to the upper 2 bytes of the PATS of the first packet in the packet group, and the TS packet transfer time is calculated from the lower 4 bytes of the PATS of the immediately preceding TS packet. When the precision is 4 bytes, PATS is calculated in consideration of carry from the previous PATS. If there is no accuracy, when the packet data is extracted, a TS packet is output immediately upon request.

v5) When packet transfer to the decoder unit is completed (Yes in step ST22204), copy control setting (CCI or CPI processing) is performed (step ST22205);
v6) Thereafter, it is checked whether or not there is manufacturer information MNF. If there is, it is determined whether or not the manufacturer ID matches the manufacturer of the corresponding device. If they match, the data is read and predetermined processing is performed. (Process unique to each company) (step ST22270);
v7) Subsequently, a discontinue process is performed (step ST2280);
v8) Wait until the transfer is completed and check whether the pack group remains in the buffer RAM. If no pack group remains in the buffer RAM (NO in step ST22206), this process is terminated;
v9) If the pack group remains in the buffer RAM (YES in step ST22206), the next packet group is set to be processed (step ST22207), and the process returns to step ST22201.

FIG. 74 is a flowchart for explaining an example of the GP switching process. For example, the GP switching process is as follows:
x1) Checking the type of the changeover switch SW (step ST22400X);
x2) Reading the grouping information GPI of the packet group GP currently being reproduced (step ST22401X);
x3) Check whether there is GPI, and if not (No in step ST22403X), end this processing;
x4) If GPI is present (step ST22403X YES), GPI information is read to switch to another GP (step ST22405X), and decoder setting processing is performed (step ST22410).

FIG. 75 is a flowchart for explaining an example of the discontinue process. An example of the discontinue process is described below:
y1) The discontinuity information DCNI is read and checked (step ST22800). If there is a CNT_SEG break at the position being played back (yes in step ST22802), the decoder playback mode is set to the internal clock mode (PTS value is ignored). Then, the reproduction is performed only with the value of the internal clock, and when the PCR has arrived, the operation is shifted to the operation mode for re-enabling the PTS (external synchronization mode) (step ST22804), and this process is terminated;
y2) If there is no CNT_SEG break at the position being played (NO in step ST22802), this process is terminated without any action.

FIG. 76 is a flowchart for explaining an example of the skip process. Skip processing can be done as follows:
z1) Read the entry point information table EPIT (step ST22500);
z2) The direction of SKIP (determined by the type of SKIP key) is checked, and in the case of forward (Yes in step ST22502), the same PID as the currently reproduced PID is obtained at the entry point EP after the currently reproduced position. The stored EP is retrieved and the information is read (step ST22504). On the other hand, in the case of backward (NO in step ST22502), an EP having the same PID as the currently reproduced PID is searched in the EP before the currently reproduced position, and the information is read (step ST22506). ;
z3) ESOBU_ENT to be reproduced is determined from the detected EPI (step ST22508);
z4) The ESOBU_ENT information is read, and the playback start time (STC) is determined (step ST22510). At that time, ESOBU_Cluster (FIG. 48) is searched and playback is started from there.

z5) Check whether or not the target ESOBU_ENT has I-PIC (or reference image) (check whether 1ST_REF_SZ = 0) or not (NO in step ST22512) Read the information of ESOBU_ENT of the same group one before (Step ST22514) and Steps ST22512 to ST22514 are repeated;
z6) If the target ESOBU_ENT has an I-PIC (or reference image) (Yes in step ST22512), the sequence header SH in the ESOBU_ENT is read and set in the decoder (step ST22522). Then, the I-PIC (or reference image) found earlier is read, decoding is started from that position, and the decoder is set to start display from the playback time specified by EP (step ST22514), and normal playback processing is performed. Move to
FIG. 77 is a diagram for explaining another example of FIG. 3 or FIG. In other words, as shown in FIG. 77, a method of managing the EVOB and SOB in each directory in a hierarchical directory is conceivable. This facilitates management for each object, and even when data is converted into HD_DVD-VIDEO, only the HDVR_VOB directory can be targeted.

  Here, HR_MANGER. An IFO is placed, and an HDOB_VOB OBJECT file of EVOB and a TMAP file HR_Vmmmm. MAP (mmmm is the same number as VOB_INDEX: 1 to 1998) is set. The HDVR_SOB includes an ESOB OBJECT file and an ESOB (AT_SOB) management file HR_SFInn. SFI (TYPE_B in the case of nn = 00, TYPE_A in the case of nn = 01 to 0xff), and the TMAP file Snn_mmmm.ES for each ESOB (AT_SOB). SMP (TYPE_B in the case of nn = 00, TYPE_A in the case of nn = 01 to 0xff; mmmm is the same number as ESOB (AT_SOB) _INDEX: 1 to 1998).

  In this case, it is conceivable that the VTMAP structure is made common in order to further increase the affinity with HD_DVD-VIDEO. The changes made in that case will be described below.

  78 is a diagram for explaining another example of FIG. Here, considering the compatibility with HD_DVD-VIDEO, TMAP is filed for each EVOB or ESOB. Therefore, EVOB_INDEX and VTMAP_LAST_MOD_TM are added to the data structure of EVOB_TMAPI in FIG. These pieces of information indicate the INDEX number for specifying the EVOB and the update time of the VTMAP placed at this position because the VTMAP increased for each EVOB. Here, the INDEX number is a number given every time EVOB is generated, and is a number that does not overlap in the DISC. Even if it is deleted, the same number is not used again. That is, the INDEX number is a number for uniquely limiting EVOB.

  80 is a diagram for explaining another example of FIG. 24, and FIG. 81 is a diagram for explaining another example of FIG. That is, ESOB_INDEX and STMAP_LAST_MOD_TM are similarly added to ESOB_TMAPI of TYPE_A, and AT_SOB_INDEX and STMAP_LAST_MODE_TM are similarly added to ESOB_TMAPI of TYPE_B.

  FIG. 82 is a diagram for explaining an example of the TMAP file structure. As shown in FIG. 82, the structure of the TMAP file is composed of TMAP_GI, TMAP_SRP, and TMAPI, corresponding to 1 file-1 EVOB (ESOB or AT_SOB), respectively. In the case of TYPE_A SOB, there may be a plurality of ES_TMAPs (multi-view, rain support, etc.). Other than that, there is only 1TMAPI, but it has the same structure as HD_DVD-VIDEO due to the presence of TMAP_SRP.

  FIG. 83 is a diagram for explaining another example of FIG. 27, and the structure of EX_VTMAP is as shown in FIG. VTMAP_TY, ILVUI_SA, EVOB_ATR_SA, and VTSI_FNAME are added to EX_VTMAP_GI. This is in consideration of compatibility with Video (DVD video and / or HD_DVD video). VTMAP_TY is set to 0x3, and ILVUI_SA and VOB_ATR_SA are set to 0 (there is no interleaved unit and ATR in TMAP) Indicates no information). In VTSI_FNAME, “HR_IVTSI.VTI” and the VTSI file name of the interoperable content are set.

  In EX_VTMAP_SRP, EVOB_INDEX and ILVU_ENT_Ns are added. EVOB_INDEX is an EVOB index number. When TMAP is read, this value and EVOB_INDEX in EVOB_TMAPI in M_AVFIT are referred to. As a result, an EVOB having the same value of EVOB_INDEX is called an EVOB to be the target of this TMAP. Note that ILVU_ENT_Ns is set to 0 (indicating that there is no ILVU_ENT).

  FIG. 84 is a diagram for explaining another example of FIG. As shown in FIG. 84, ESOB_TMAP of ESOB of TYPE_A has ES_TMAPI_SRP_Ns and ESOB_INDEX added to ESOB_TMAP_GI. In ES_TMAPI_SRP_Ns, the number of ESs that created the TMAP is set. This ESOB_INDEX is compared with ESOB_INDEX in the ESOB_TMAPI of ESOB_TMAPI. The ESOB to which ESOB_INDEX having the same value belongs is the ESOB to which the TMAP belongs (similar to EVOB). However, the reason that ESOB_INDEX is in STMAP_GI and not in ES_TMAP_SRP is that ESOB_INDEX is in each ESOB. If ESOB_INDEX is in ES_TMAP_SRP, it may be changed for each ES, so it is included in STMAP_GI.

  FIG. 85 is a diagram for explaining another example of FIG. As shown in FIG. 85, AT-SOB_INDEX of TYPE_B AT-SOB is added to STMAP_GI. AT-SOB_INDEX is compared with AT-SOB_INDEX in ESOB_TMAPIGI of ESOB_TMAPI. Then, the AT-SOB to which the same value AT-SOB_INDEX belongs is the AT-SOB to which the TMAP belongs (similar to EVOB).

  FIG. 96 is a diagram for explaining a special case of CNT_SEG. As shown in FIG. 96, in ESOB_DCNI, special processing is required because the playback order and recording order of pictures are shifted at the beginning and end of ESOB. The upper part of FIG. 96 is the top process, and the lower part is the process at the end. When the recording order is I, B, B, P,... At the beginning of ESOB, the playback order may be B, B, I, P,. At this time, when the carry of PTM occurs in the portion B1, CNT_SEG # 1 with CNT_SEG_SZ = 0 is generated. In the final part of ESOB, when the recording order is B, B, P,..., The playback order may be B, B, P,. At this time, if a PTM carry occurs in the middle of the P picture, CNT_SEG # 1 with CNT_SEG_SZ = 0 is generated.

  The ESOB_CONNI described above with reference to FIG. 23 is information indicating whether or not the current ESOB has been continuously recorded with the previous ESOB, and can be continuously reproduced during reproduction. (However, whether or not this continuous reproduction is seamless depends on the processing capability of the recorder.) Here, the relationship between the position information and the time information of ESOB having a plurality of ESOB_CONNI and ES is as shown in FIGS. become.

FIG. 97 is a diagram for explaining an example of the SOB start position relationship according to ESOB_CONNI. Regarding the head part of ESOB, as shown in FIG. 97, the relationship in the normal case (when ESOB_CONN_SS = 0) is
ESOB_S_PTM = ES_S_PTM # 1
ESOB_S_PTM ≦ ES_S_PTM # 2
ES_S_ADR_OFS # 2 ≧ 0
It is. In the case of ESOB_CONN_SS = 1 (when the current ESOB is in a continuous recording relationship with the previous ESOB), in addition to the above conditions,
ES_S_ADR_OFS # 2 can be negative (expressed in 2's complement) (in this case, 0xffff ffff ffff fffb (-5's 2's complement));
And
ESOB_S_PTM> ES_S_PTM # 2 (ES_S_PTM # 1> ES_S_PTM # 2) is also possible. That is, ESs other than the default ES can be set so as to protrude beyond the continuously recorded SOB.

FIG. 98 is a diagram for explaining an example of the SOB start position relationship according to ESOB_CONNI at the time of editing. When the ESOB before the current ESOB is deleted, as shown in FIG.
Changed to be ES_S_ADR_OFS # 2 ≧ 0 (in this case, the top of ESOBU # 2) and
Change ES_S_PTM # 2 so that ES_S_PTM # 2 ≧ ESOB_S_PTM (in this case, the first value of ESOBU # 2)
Change to be

That is, the ESOBU that protrudes from the ESOB is deleted so that it does not protrude from the ESOB. (To prevent the ESOB from protruding from the ESOB, the ESOBU may be edited to reconstruct the ESOBU_ENT from the ESOB if the next I picture in the ESOBU exists in the ESOB.)
FIG. 99 is a diagram for explaining an example of the SOB end position relationship according to ESOB_CONNI. Regarding the last part of the ESOB, as shown in FIG. 99, the relationship in the normal case (when ESOB_CONN_SS = 0) is
ESOB_E_PTM = ES_E_PTM # 1
ESOB_E_PTM ≧ ES_E_PTM # 2
ESOB_SZ ≧ ES_S_ADR_OFS # 2 + ESOBU_SZ is the total sum. However, in the case of ESOB_CONN_SS = 0 (when there is a relationship of continuous recording with the subsequent ESOB), in addition to the above conditions,
ESOB_SZ <ES_S_ADR_OFS # 2 + ESOBU_SZ can be summed
ESOB_E_PTM <ES_E_PTM # 2 (ES_E_PTM # 1 <ES_E_PTM # 2) is also possible. That is, ESs other than the default ES can be set so as to protrude beyond the continuously recorded SOB.

FIG. 100 is a diagram for explaining an example of the SOB end position relationship according to ESOB_CONNI at the time of editing. When the back ESOB is deleted, as shown in FIG.
Change the ESOBU_SZ total number so that ESOB_SZ ≧ ES_S_ADR_OFS # 2 + ESOBU_SZ. (In this case, delete ESOBU_SZ # 2)
And
Change ES_S_PTM # 2 so that ESOB_E_PTM ≧ ES_E_PTM # 2 (in this case, E_PTM of ESOBU # 1)
Change as follows.

That is, the ESOBU that protrudes from the ESOB is deleted so that it does not protrude from the ESOB. (If it does not protrude from the ESOB, the ESOBU may be edited and the ESOBU_ENT may be reconfigured to fit within the ESOB.)
By doing as described above, all non-default V-ES (video elementary streams) in ESOB are registered in ES-TMAP, and all V-ESs among ESOBs that can be continuously played back are registered. Can be specified. This makes it possible to prevent non-default V-ES playback from being interrupted between ESOBs in content in which a plurality of Video-ESs can be played back between ESOBs that are continuously played back. .

  FIG. 86 is a diagram for explaining another example of FIG. 86 differs from FIG. 36 in the following points. That is, in the example of FIG. 86, CNT_SEGN = 1 indicates that there are 0 CNT_SEGs in the corresponding ESOB, CNT_SEGN = 2 indicates that there is 1 CNT_SEG in the corresponding ESOB, and CNT_SEGN = 3 indicates that the corresponding ESOB. This indicates that there are two CNT_SEGs, and that CNT_SEGN = 4 indicates that there are three CNT_SEGs in the corresponding ESOB.

  FIG. 87 is a diagram for explaining another example of FIG. As shown in FIG. 87, EVOBU_S_PTM4 is added to GCI_GI in the RDI pack in the OBJECT data of the VOB. As a result, the PTM of the first VIDEO of the EVOBU can be known, and when playback is started from the EVOBU in the middle of the EVOB, this value can be read to start playback. As a result, EX_VTMAP can be used for HD_DVD-VIDEO without change, and can be transferred to HD_DVD-Video with less effort, and HDVR data can be applied to DVD-PLAYER.

  FIG. 88 is a diagram for explaining an example of conversion of interoperable content. Creation of management information according to HD_DVD-VIDEO so that playback processing can be performed with DVD-PLAYER is referred to as “interoperable content creation processing”. As shown in FIG. 88, VTSI and VIDEO_PLAYLIST are created and saved from EVOB management information in the HD_DVD-VR management information. Then, information on M_CELLI in PGCI and the PG to which the CELL belongs are extracted, attribute information is extracted from STI, a VIDEO_PLAYLIST file (XML file) is created, and VTSI (HR_IVTSI.VTI) is created from M_AVFIT.

  FIG. 79 is a diagram for explaining another example of FIG. 77. FIG. 79 shows the structure of the file created in the above example.

  The player reads the target EX_VTMAP (HR_Vmmmm.MAP) according to VOB_PALYLIST, determines EVOB based on the value of EVOB_INDEX therein, reads VTSI as management information of EVOB, and reads the EVOB file (HR_MOVIE.VRO according to these management information). ).

  Here, in VR, EVOB to be played is determined from PGCI, EVOB management information and EX_VTMAP to be played back are read from M_AVFIT, and an EVOB file is played according to the information. In the case of HD_DVD-VIDEO, the EVOB to be played back from VIDEO_PLAYLIST is read. EX_VTMAP is determined and read, VTSI is read based on the information of VTMAP, the target EVOB information is read from the management data in VTSI according to the value of EVOB_INDEX in EX_VTMAP, and the EVOB file (HR_MOVIE.VRO) is reproduced. . In this way, the usage of EX_VTMAP is different between HD_DVD_VR and HD_DVIDEO, and each is reverse lookup. Therefore, VTMAP, VMGI, and VTSI have a structure in which reverse lookup is possible. However, as shown in FIG. 93, a plurality of timings for performing the process of creating the interoperable content can be considered.

  FIG. 93 is a flowchart illustrating an example of processing timing for creating interoperable content. The first possible interoperable content creation process timing is a method (step ST32) that is automatically performed after the VR recording process (step ST22) ends, as shown in FIG. 93 (a). In this case, the created disc can always be played back by PLAYER, but the end of the recording process is delayed.

  The second possible interoperable content creation process timing is a method (step ST32) that is automatically performed during the disc ejection process (step ST30) as shown in FIG. 93 (b). In this case as well, the created disc can always be played back by PLAYER, but the ejection process becomes slow.

  As for the third possible interoperable content creation processing timing, options such as DVD-VIDEO compatibility processing are provided as in a DVD video recorder, and the user selects the processing and consciously processes ( It is conceivable to perform step ST32). In this case, the operation time of other processing is not delayed, and the user can wait for the time by selecting this processing. However, in this case, the disc is not necessarily reproducible by PLAYER, and only the disc that has undergone the processing (step ST32) can be replayed by PLAYER.

  Here, precautions for processing during conversion are shown below.

  The VIDEO_PLAYLIST file (XML) is placed under the directory “ADV_OBJ”.

  The file name of the VIDEO_PLAYLIST file is “VPLST000.XPL”.

  -The VTSI file is placed under “DVD_HDVR / HDVR_VOB”.

  ・ The file name of VTSI is “HR_IVTSI.VTI”.

  ・ VOB file and TMAP file are used as they are.

  FIG. 94 is a flowchart for explaining an example of the interoperable content creation processing. Examples of specific conversion processing will be described below with reference to conversion tables 1 to 4 in FIGS. 89, 90, 91, and 92.

  1) It is determined whether or not EVOB is recorded (step ST320). If not recorded (NO in step ST320), this process ends.

2) When EVOB is recorded (Yes in step ST320), VTSI is created from the management information of EVOB according to conversion tables 1 to 4 in FIGS. 89 to 92 by M_AVFIT (step ST322). (The VTMAP and VRO files are compatible and can be used as they are, so nothing is done.)
3) VIDEO_PLAYLIST is created according to the PGCI and STI data (step ST324), and this process is terminated.

  An actual conversion example of VIDEO_PLAYLIST at this time is shown below. Here, the conversion is carried out while paying attention to the following.

  “Title” corresponds to HD_DVD-VR Program (PG) or Play List (PL).

  “Chapter” corresponds to the entry point (M_C_EPI) of HD_DVD-VR. Even when there is no EP, a Chapter element may be added at the beginning or end of the title.

  “DisplayName” in the Playlist matches the Disc Representative Name (DISC_REP_NM) of the HD_DVD-VR.

  “DisplayName” in Title corresponds to Primary Text Information (PRM_TXTI) in HD DVD-VR Program (PG) or Play List (PL).

  “DisplayName” in Chapter corresponds to Primary Text Information (PRM_TXTI) in Entry Point (M_C_EPI: Type EP_B) of HD_DVD-VR.

  “TitleDuration” in the Title is derived from C_V_S_PTM and C_V_E_PTM of HD_DVD-VR.

  “TitleTimeBegin” and “titleTimeEnd” of PrimaryAudioVideoClip are derived from C_V_S_PTM and C_V_E_PTM of HD_DVD-VR.

  “PrimaryAudioVideoClip” “clipTimeBegin” is derived from C_V_S_PTM and VOB_S_PTM of HD_DVD-VR.

  Chapter “titleTimeBegin” is derived from EP_PTM, C_V_S_PTM, and C_V_E_PTM of HD_DVD-VR.

  ・ ESOB and AT-SOB are not covered.

  -Temporary race EVOB is not included in interoperable content.

  -The total number of P-EVOBs is smaller than the total number of EVOBs of HD_DVD-VR.

  FIG. 95 is a diagram for explaining an example of the PGC configuration of HD_VR. Based on the above cautions, first, when a PGCI as shown in FIG. 95 exists, the following VIDEO_PLAYLIST file is created.

<? xml version = "1.0" encoding = "UTF-8" standalone = "yes"?>
<Playlist majorVersion = "1" minorVersion = "0" diplayName = "Disc name (DISC_REP_NM)" type = "Interoperable" xmlns = "http://www.dvdforum.org/2005/HDDVDVideo/Playlist">
<Configuration>
<StreamingBuffer size = "0"/>
<Aperture size = "1920x1080"/>
<MainVideoDefaultColor color = "107F7F"/>
</ Configuration>
<MediaAttributeList>
<VideoAttributeItem index = "1" codec = "AVC"/>
<VideoAttributeItem index = "2" codec = "VC-1"/>
<AudioAttributeItem index = "1" codec = "LPCM"/>
<AudioAttributeItem index = "2" codec = "AC-3"/>
</ MediaAttributeList>
<TitleSet timeBase = "60fps">
<Title id = "Title001" titleNumber = "1" type = "Original" titleDuration = "00: 01: 00: 00" onEnd = "Title002" displayName = "Original Title 1 (PRM_TXTI in PGI # 1)">
<PrimaryAudioVideoClip id = "Clip1" dataSource = "Disc" titleTimeBegin = "00: 00: 00: 00" clipTimeBegin = "00: 00: 00: 00" titleTimeEnd = "00: 01: 00: 00" src = "file: /// dvddisc / DVD_HDVR / HDVR_VOB / HR_V0001.MAP ">
<Video track = "1" mediaAttr = "1"/>
<Audio track = "1" streamNumber = "1" mediaAttr = "1"/>
</ PrimaryAudioVideoClip>
<ChapterList>
<Chapter id = "Chapter0001" titleTimeBegin = "00: 00: 00: 00"/>
</ ChapterList>
</ Title>
<Title id = "Title002" titleNumber = "2" type = "Original" titleDuration = "00: 01: 30: 00" onEnd = "Title003" displayName = "Original Title 2 (PRM_TXTI in PGI # 2)">
<PrimaryAudioVideoClip id = "Clip2" dataSource = "Disc" titleTimeBegin = "00: 00: 00: 00" clipTimeBegin = "00: 00: 00: 00" titleTimeEnd = "00: 01: 30: 00" src = "file: /// dvddisc / DVD_HDVR / HDVR_VOB / HR_V0002.MAP ">
<Video track = "1" mediaAttr = "2"/>
<Audio track = "1" streamNumber = "1" mediaAttr = "2"/>
</ PrimaryAudioVideoClip>
<ChapterList>
<Chapter id = "Chapter0002" titleTimeBegin = "00: 00: 00: 00"/>
<Chapter id = "Chapter0003" titleTimeBegin = "00: 00: 40: 00" displayName = "Chapter name 3 (PRM_TXTI in M_C_EPI)"/>
</ ChapterList>
</ Title>
<Title id = "Title003" titleNumber = "3" type = "UserDefined" titleDuration = "00: 01: 15: 00" displayName = "Play List Title 1 (PRM_TXTI in PL_SRP # 1)">
<PrimaryAudioVideoClip id = "Clip3" dataSource = "Disc" titleTimeBegin = "00: 00: 00: 00" clipTimeBegin = "00: 00: 20: 00" titleTimeEnd = "00: 00: 30: 00" src = "file: /// dvddisc / DVD_HDVR / HDVR_VOB / HR_V0001.MAP ">
<Video track = "1" mediaAttr = "1"/>
<Audio track = "1" streamNumber = "1" mediaAttr = "1"/>
</ PrimaryAudioVideoClip>
<PrimaryAudioVideoClip id = "Clip4" dataSource = "Disc" titleTimeBegin = "00: 00: 30: 00" clipTimeBegin = "00: 00: 15: 00" titleTimeEnd = "00: 01: 15: 00" src = "file: /// dvddisc / DVD_HDVR / HDVR_VOB / HR_V0002.MAP ">
<Video track = "1" mediaAttr = "2"/>
<Audio track = "1" streamNumber = "1" mediaAttr = "2"/>
</ PrimaryAudioVideoClip>
<ChapterList>
<Chapter id = "Chapter0004" titleTimeBegin = "00: 00: 00: 00" displayName = "Chapter name 4 (PRM_TXTI in M_C_EPI)"/>
<Chapter id = "Chapter0005" titleTimeBegin = "00: 00: 50: 00"/>
</ ChapterList>
</ Title>
</ TitleSet>
</ Playlist>
As described above, the transition to DVD-PLAYER can be realized relatively easily.

<Summary>
1. When an STC Wrap-around occurs in a digital recorder (such as a DVD streamer) capable of recording a digital stream, the position is set to ESOBI as CNT_SEG, and CNT_SEG number information from the head of ESOB is added to each PMT.

  2. In a digital recorder (such as a DVD streamer) capable of recording a digital stream, an ESI number used for video at the time of reproduction is added to each representative picture information in order to identify the video stream.

  3. In a digital recorder (such as a DVD streamer) capable of recording a digital stream, in order to identify the stream to be played, each resume information includes an ESI number used in the video during playback, an ESI number used in the audio stream, When the audio is dual mono, the main / sub information is added.

  4). In a digital recorder capable of recording a digital stream (such as a DVD streamer), in order to specify a stream to be played back, each EP information includes an ESI number used for video during playback, an ESI number used for audio stream, If the audio is dual mono, the sub information is added.

  5. As seamless information indicating continuity between ESOBs that are logically connected, an STC continuous flag and / or a PATS continuous flag and its offset value are added in addition to a continuous recording flag.

<Effect of Embodiment>
-It is possible to know whether STC is Wrap-around only by playing information before playing.

・ The continuity between multiple ESOBs can be understood, and if they are continuous, multiple ESOBs can be connected seamlessly. That is, it is possible to reduce the frequency of occurrence of a situation of waiting for reproduction processing (a still image is caught) at a connection portion between a plurality of ESOBs that are known to be continuous as compared with the case where the present invention is not implemented.

<Correspondence Example between Embodiment and Invention>
<Information recording medium (1): TOTAL_STMAP_SZ in FIG. 12>
In an information recording medium (100 in FIG. 1) configured to record a predetermined digital stream signal,
The information recording medium has a management area (111 and 130 in FIG. 1; DVD_HDVR in FIG. 3; HDVR_MG in FIG. 12) and a data area (131 to 133 in FIG. 1), and the data area (131 to 133 in FIG. 1). Is configured so that the data of the digital stream signal can be divided and recorded into a plurality of objects (ESOB, etc.),
The management area (DVD_HDVR in FIG. 3) has management information (for each digital stream signal transmission source (broadcasting station) or for each digital stream signal broadcasting system (Japanese ARIB, US ATSC, European DVB, etc.) HR_SFIxx.IFO in FIG. 3 and time map information (HR_STMAPx.IFO in FIG. 3) for each transmission source (broadcast station) of the digital stream signal or for each broadcasting system of the digital stream signal,
Information indicating the size of the time map information (TOTAL_STMAP_SZ in FIG. 12; recording) in the management information (HDVR_MG in FIG. 12) for each transmission source (broadcast station) of the digital stream signal or for each broadcasting method of the digital stream signal An information recording medium configured to include ST15411) of FIG.

<Information Recording Medium (Part 2) ... TYPE_B / ESOB_TY / b12 in FIG. 15 ... Invalid Value of PSI, SI Information> (PSI = Program Specific Information) (SI = Service Information)
In an information recording medium (100 in FIG. 1) configured to record a digital stream signal that has been MPEG-encoded and transmitted from a broadcasting station,
The information recording medium has a management area (111 and 130 in FIG. 1; DVD_HDVR in FIG. 3; HDVR_MG in FIG. 12) and a data area (131 to 133 in FIG. 1), and the data area (131 to 133 in FIG. 1). Is configured so that the data of the digital stream signal can be divided and recorded into a plurality of objects (ESOB, etc.),
The management area (DVD_HDVR in FIG. 3) stores management information (HR_SFIxx.IFO in FIG. 3) for each broadcasting station or for each broadcasting system of the digital stream signal (Japanese ARIB, US ATSC, European DVB, etc.). And management information of a type (TYPE_B) that does not specify the broadcasting station or the broadcasting system (such as ARIB), and management information of a type (TYPE_B) that does not specify the broadcasting station or the broadcasting system (ESOB_TY in FIG. 15) Includes information (ESOB_TY: b12 = “1” or invalid value of PSI, SI information; ST1513 in FIG. 63 at recording; ST211C in FIG. 69 at reproduction) An information recording medium configured as described above.

<Information Recording Medium (Part 3) ... HDVR_MG in FIG. 8 / EX_M_VOB_STI in FIG. 10 / V_ATR in FIG. 11>
In an information recording medium (100 in FIG. 1) configured to record MPEG transport stream (TS) data and MPEG program stream (PS) data as a predetermined digital stream signal,
The information recording medium has a management area (111 and 130 in FIG. 1; DVD_HDVR in FIG. 3; HDVR_MG in FIG. 8; EX_M_VOB_STI in FIG. 10) and a data area (131 to 133 in FIG. 1).
In the data area (131 to 133 in FIG. 1), the MPEG transport stream (TS) data and the MPEG program stream (PS) data are divided into a plurality of objects (ESOB, EVOB) as separate files (SR Object in FIG. 3). File; VR Object File)
The management area (DVD_HDVR in FIG. 3; HDVR_MG in FIGS. 8 and 12) includes management information (HR_MANGER.IFO) for managing the entire digital stream signal and management information for the MPEG transport stream (TS) data (TS) ( ESTR_FIT in FIG. 12 and management information for the MPEG program stream (PS) data (EX_M_AVFIT in FIG. 8) can be recorded,
In the management information (DVD_HDVR in FIG. 3; V_ATR in FIG. 11), information indicating whether the corresponding digital stream signal is progressive (source image progressive mode) and information indicating whether it is high-vision ( An information recording medium configured to describe at least one of (source image resolution).

<In the case of information recording medium (part 3) where the resolution information of FIG. 17 is only the vertical resolution>
The management information for the MPEG transport stream (TS) data (ESTR_FIT in FIG. 12; ESOBI in FIG. 13; ESOB_ESI in FIG. 16; ESOB_V_ESI / V_ATR in FIG. 17) does not specify the horizontal resolution (unspecified) at the vertical resolution. Contains information specifying the source resolution.

<Information recording medium (part 4)>
A file structure (FIG. 79) for managing the first high-definition video information (HD_DVD-VR; HDVR_VOB / HDVR_SOB) that can be recorded by the user and the second high-definition video information (HD_DVD-VIDEO; ADV_OBJ) that can be provided by the content provider. An information recording medium configured to record a predetermined digital stream signal including the first high-definition video information (HD_DVD-VR) and the second high-definition video information (HD_DVD-VIDEO),
The information recording medium has a management area and a data area, and the data area is configured so that the data of the digital stream signal can be recorded in a plurality of objects (HDVR_VOB, HDVR_SOB, ADV_OBJ),
The management area includes management information (ESOB-related file in FIG. 79 = FIG. 3) for each transmission source of the digital stream signal including the first high-definition video information (HD_DVD-VR) or for each broadcasting method of the digital stream signal. HR_SFIxx.IFO, etc.) and time map information (see FIG. 79) for each transmission source of the digital stream signal including the first high-definition video information (HD_DVD-VR) or for each broadcasting method of the digital stream signal. VSOB related files = HR_Vmmmm.MAP etc.)
The information recording medium configured to further include management information (VIDEO_PLAYLIST, VTSI) for managing reproduction of the digital stream signal including the second high-definition video information (HD_DVD-VIDEO).

<Information recording medium (part 5)>
In an information recording medium configured to record a predetermined digital stream signal,
The information recording medium has a management area and a data area, and the data area is configured so that the data of the digital stream signal can be recorded in a plurality of objects (HDVR_VOB, HDVR_SOB),
The management area has management information for each transmission source of the digital stream signal or for each broadcasting method of the digital stream signal, and time map information for each transmission source of the digital stream signal or for each broadcasting method of the digital stream signal. (HR_Vmmmm.IFO = HR_Vmmmm.MAP, HR_Snn_mmmm.SMP in FIGS. 77 and 82)
An information recording medium configured such that the time map information (HR_Vmmmm.MAP, HR_Snn_mmmm.SMP) includes index information (EVOB_INDEX in FIG. 83, ESOB_INDEX in FIG. 84) for specifying the object (HDVR_VOB, HDVR_SOB).

<Recording method using the information recording medium>
An information recording method for recording the digital stream signal in the data area (FIGS. 57 to 58).

<Reproduction method using the above information recording medium>
An information reproducing method for reproducing the digital stream signal from the data area (FIG. 69).

<Recording apparatus using the information recording medium>
An information recording apparatus (encoder side in FIG. 53) having a configuration for recording the digital stream signal in the data area.

<Reproducing apparatus using the information recording medium>
An information reproduction apparatus (decoder side in FIG. 53) having a configuration for reproducing the digital stream signal from the data area.

  The present invention is not limited to the above-described embodiment, and can be variously modified within the scope of the gist of the present invention or a future implementation stage based on the technology available at that time. It is. In addition, the embodiments may be appropriately combined as much as possible, and in that case, the combined effect can be obtained. Further, the above embodiments include inventions at various stages, and various inventions can be extracted by appropriately combining a plurality of disclosed constituent elements. For example, even if some configuration requirements are deleted from all the configuration requirements shown in the embodiment, the configuration requirement is deleted when the problem to be solved by the invention can be solved and the effect of the invention can be obtained. The configuration can be extracted as an invention.

  DESCRIPTION OF SYMBOLS 100 ... Information recording medium (DVD-RAM disc etc.); 121 ... AV data recording area; 122 ... VR object group recording area; 130 ... AV data management information recording area (HDVR_VMG); 131 ... Stream object group recording area; 134: Stream object unit (ESOBU); 140 ... Packet group; 160 ... DVD transport stream packet recording area; 161 ... Packet group header; 163 ... MPEG transport stream (MPEG-TS) packet; 162 ... Packet arrival time (PATS); 10 ... Playback information management layer; 11 ... Program chain (PGC); 12 ... Program (PG); 13 ... Cell; 20 ... Stream object management information layer; Information (ESOBI); 22 ... Stream object unit information (ESOBUI; Global information); 23 ... Video object management information layer; 24 ... Video object information (EVOBI); 25 ... Video object unit information (EVOBUI); ESOB) layer; 51... Disk drive section (such as an optical disk drive using a laser having a wavelength of, for example, 650 nm to 405 nm); 59... Decoder section; 74 ... digital interface (IEEE1394 I / F etc.); MPU unit (control unit); 83... Set top box unit (satellite digital tuner); 89 .. terrestrial digital tuner; 100a... Information recording medium (hard disk drive or the like).

Claims (5)

In an information recording medium configured to record a predetermined digital stream signal with an apparatus including an information processing unit,
The information recording medium has a management area and a data area, and the data area is configured so that data of the digital stream signal can be divided into a plurality of objects and recorded by a plurality of packets.
The management area has a playback time base type A time map when the digital stream signal can be analyzed, and a time map having a packet arrival time base type B time map when the digital stream signal cannot be analyzed. Including information,
The time map information has index information corresponding to the digital stream signal that can be analyzed or the digital stream signal that cannot be analyzed,
An information recording medium configured such that an information processing unit processes reproduction of the digital stream signal using information in the management area.   2. The recording method using the information recording medium according to claim 1, wherein the digital stream signal is recorded in the data area and the management information is recorded in the management area.   2. The reproduction method using the information recording medium according to claim 1, wherein the management information is reproduced from the management area and the digital stream signal is reproduced from the data area.   A recording apparatus using the information recording medium according to claim 1, comprising: a configuration for recording the digital stream signal in the data area; and a configuration for recording the management information in the management area.   6. A reproducing apparatus using the information recording medium according to claim 5, comprising: a configuration for reproducing the management information from the management area; and a structure for reproducing the digital stream signal from the data area.

Images