JP2008176920A - Digital av information recording medium, and recording and reproducing method and device using the same - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a medium for digital stream recording capable of putting a thumbnail to an entry point. <P>SOLUTION: Information of the thumbnail is held in an area different from that of animation information. A management information includes cell information corresponding to a part of a program, and this cell information includes entry point information showing a position entering the program. This entry point information (C_EPI) is composed to have pointer information (TBN_PT) designating the information of the thumbnail. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a digital AV information recording medium, a recording / reproducing method using the medium, and a recording / reproducing apparatus. In particular, the present invention relates to a medium, method and apparatus capable of digitally recording and reproducing high-definition AV information in real time.

  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. An MPEG transport stream (hereinafter abbreviated as MPEG-TS as appropriate) is employed in digital TV broadcasting currently being implemented. 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 broadcasts, the market needs of streamers that can directly record digital TV broadcast content (without going through digital / analog conversion) are increasing. A typical video stream recorder (D-VHS streamer) called D-VHS (registered trademark R) is a commercially available streamer for recording digital broadcast data (MPEG-TS or the like) as it is. . Some manufacturers also sell a streamer that digitally records and plays back high-definition programs on an optical disk using a blue laser, or a streamer that digitally records and plays back high-definition programs using a large-capacity hard disk.

  The streamer records the broadcast digital stream as it is, and therefore the recorded program is not always reproducible by a simple operation from where each user likes. Therefore, the existing DVD video recorder is configured so that entry points can be entered so that the program can be reproduced from the user's favorite place. This function is also desired for a streamer, and a streamer that allows entry points is also devised (see Patent Document 1).

In Patent Document 1, a status corresponding to the cause of the entry point can be added to the entry point. For this reason, the cause of creating the entry point can be understood, but various extended information cannot be added to the entry point.
JP2003-18549A.

  Even if an entry point is attached to the stream recorded program, it is difficult for the user to know where the entry point corresponds to in the program.

  Alternatively, when there is a shortage of text storage locations corresponding to entry points, it is inconvenient if the text to be entered cannot be entered.

  Alternatively, it is inconvenient that the information attached to the entry point cannot be extended from the current state.

  Or, even if the function is added to a single disc using the vendor information (MNFI) in its own recorder, if the disc is additionally recorded by another company's recorder, the vendor information of the disc and the information from the disc Consistency with the playback information may be lost. However, it is also inconvenient that there is no means to determine whether the disc was used for recording etc. by another company's machine (that is, the user is worried that the reliability of the recorded content of such disc is unknown) ).

  The present invention has been made in view of at least one of the above circumstances, and one of its purposes is to provide index information (such as a reduced image / thumbnail that can be visually recognized by the user) to the entry point. A digital AV information recording medium configured as described above is provided.

  An information medium according to an embodiment of the present invention includes a data area for recording AV information including moving picture information, and a management area for storing management information for managing the AV information recorded in the data area as one or more programs. And have. In this information medium, index image information is provided in a region (HR_THNL.DAT) different from moving image information (HR_STRMx.SRO, etc.). Further, the management information (DVD_HDVR / HR_MANGR.IFO / PGCI) includes cell information (CI) corresponding to a part of the program (PG), and this cell information (CI) is an entry point indicating a position within the program. The entry point information (C_EPI) includes index pointer information (TBN_PT) for designating the index image information.

  Image information for indexing (reduced image / thumbnail or representative image that can be visually recognized by the user) can be assigned to the entry point.

  In broadcasting using cable such as digital TV broadcasting and the Internet, compressed video is broadcast (distributed). The transport stream (TS), which is a common basic format, is divided into a management data portion of a packet and a payload. The payload includes data to be reproduced in a scrambled state. On the other hand, according to ARIB (Association of Radio Industries and Businesses) which is one of digital broadcasting systems, PAT (Program Association Table), PMT (Program Map Table) and SI (Service Information) are not scrambled. Here, various management information can be created using the contents of PMT and SI (SDT: Service Description Table, EIT: Event Information Table, BAT: Bouquet association Table).

  The reproduction target of the digital broadcast content includes MPEG video data, Dolby / AC3 (R) audio data, MPEG audio data, data broadcast data, and the like. Although not directly related to the reproduction target, information (program information, etc.) such as PAT, PMT, SI necessary for reproduction is included in the digitally broadcast content. 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.

  Examples of normal playback procedures in STB (Set Top Box) and the like include the following. That is, for example, when a user determines a program based on EPG (Electronic Program Guide) information, the PAT is read at the start time of the target program, the PID of the PMT belonging to the desired program is determined based on the data, and the PID Accordingly, the target PMT is read out, and the PID of the video and audio packets to be reproduced included therein is determined. Then, the video and / or audio attributes are read by PMT and SI, set to each decoder, and the video and / or audio data are cut out according to the PID and reproduced. Here, PAT, PMT, SI, etc. are transmitted every several hundreds ms to be used for intermediate playback.

  When these data are recorded on a disk medium such as a DVD-RAM, it is advantageous to record the broadcast data as digital data as it is. Therefore, ESR (Extended Stream Recording) is proposed in the present invention as a format for recording a stream as it is, which is different from the existing VR (Video Recording) format. This ESR is obtained by merging conventional SR (stream recording) with VR (video recording), and is compatible with stream recording of digital broadcasting while utilizing existing VR assets.

  Hereinafter, embodiments of the present invention based on the above ESR will be described in detail with reference to the drawings. FIG. 1 is a diagram for explaining a data structure according to an embodiment of the present invention. Examples of the disk-shaped information recording medium 100 (FIG. 1A) include recordable optical disks such as DVD-RAM, DVD-RW, and DVD-R, and recordable magnetic disks such as a hard disk. In the following, description will be continued by taking an optical disk such as a DVD-RAM as an example.

  The disk 100 has a lead-in area 110, a volume / file structure information area 111, a data area 112, and a lead-out area 113 from the inner circumference side toward the outer circumference side (FIG. 1 (b)). A file system is stored in the volume / file structure information area 111. The file system is composed of information indicating which file is recorded where (described later with reference to FIG. 3). The recorded content is stored in the data area 112 (FIG. 1C).

  The data area 112 is divided into an area 120 for recording general computer data and an area 121 for recording AV data. In the AV data recording area 121, an AV data management information area 130 having a file (VMG / ESMG file) for managing AV data and an object data (VOBS) file (VRO file) of the video recording standard are recorded. The VR object group recording area 122 and an Estream object group recording area 131 in which stream objects (ESOBS: Extend Stream Object Set) corresponding to digital broadcasting are recorded (FIG. 1D). That is, in this embodiment, a digital broadcast stream object is recorded as an E stream object 132 (ESOBS), which is a separate file from the VR object (FIG. 1 (e)).

  Each E stream object 132 is configured by collecting one or more data units (ESOBU: Extend Stream Object Unit) 134 as an access unit to the disk 100 (FIG. 1 (f)). Here, one ESOBU is a data unit divided in units of pictures at a constant time interval. Alternatively, one ESOBU may be a data unit delimited by one or more GOPs. Each data unit (ESOBU) 134 is composed of one or more packet groups (Packet_Group) 140 composed of a collection of a plurality of TS packets (FIG. 1 (g)).

  In this embodiment, each packet loop 140 is constituted by a group of, for example, 8 packs (or 8 LBs (Logical Blocks)). If one pack size (or one LB size) is 2 kbytes, the size of each packet group 140 is 16 kbytes. This is 1 / integer of the ECC block size in the video recording standard.

  Each packet group 140 constitutes a packet recording area (DVD-TS packet recording area) 160 in stream recording (ESR) provided by the present invention (FIG. 1 (h)). The DVD-TS packet recording area 160 includes a packet group header 161, a plurality (for example, 85) of MPEG-TS packets 162, and a plurality (for example, 84) of packet arrival time difference information (IAPAT: Incremental Application Packet Arrival Time). (FIG. 1 (i)). The contents of the packet group 140 will be described in detail later with reference to FIG.

  Here, DVD-Video (ROM Video) is divided into VIDEO-TS and DVD-RTR (recording / playback DVD) is divided into DVD-RTAV. Similarly, in the new stream recording (ESR) compatible with digital broadcasting, the recording file is recorded in a directory called DVD_HDVR (see FIG. 3), for example.

  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. The management information (VMG / ESMG file) recorded in the AV data management information recording area 130 in FIG. 1 is playback management information for managing playback procedures of both the recorded content based on the video recording standard and the stream recorded content based on the present invention. Has layer 10.

  That is, one or more cells 13 that are playback units of stream-recorded objects are collected to form a program 12, and one or more cells 13 that are playback units of video-recorded objects are collected to form a program 12. The arrangement (reproduction procedure) of the programs 12 is managed by the management information (PGCI) of the program chain (PGC) 11.

  Here, even when playback is started from the middle of the cell 13 on the stream recording side or when playback is started from the middle of the cell 13 on the video recording side, the user can specify the playback location by the playback time (PTS). It can be done.

That is, when playback is started from the middle of the cell 13 on the stream recording side at the playback time (PTS), the stream object ESOB 132 in the stream object layer 30 is specified via the stream object information ESOBI 21 in the stream object management information layer 20. The stream object unit ESOBU 134 in the stream object layer 30 is specified via the stream object unit information ESOBUI 22 in the stream object management information layer 20. When ESOB 132 and its ESOBU 134 are designated, the playback start location is specified. (ESOBUI here may be paraphrased as global information 22)
The ESOBU 134 is composed of one or more packet groups 140. The ESOBU 134 is a data unit corresponding to one or more GOPs, for example. Alternatively, the ESOBU 134 may be divided in units corresponding to the data amount for a certain playback time. Thereby, overflow of each information field is prevented.

  Each packet group 140 is composed of 8 packs (or 8 LBs) (16384 bytes), has a packet group header 161 at the head, and then a plurality of transport stream packets (TS_Packets) 162 and a plurality of Packet arrival time difference information (IAPAT) 163 is arranged. Recorded contents of stream recording are stored in these TS packets 162.

  On the other hand, when playback is started from the middle of the cell 13 on the video recording side at the playback time (PTS), the video object in the video object layer 35 is transmitted via the video object information VOBI 24 in the video object (VOB) management information layer 23. The VOB 36 is designated, and the video object unit VOBU 37 in the video object layer 35 is designated via the video object unit information VOBUI 25 in the video object management information layer 23. When the VOB 36 and its VOBU 37 are designated, the playback start location is specified. The VOBU 37 is composed of a plurality of packs 38, and recorded contents of video recording are stored in these packs.

  As will be described in detail later, when playback is started from the middle of the cell 13 on the stream recording side, the playback start location can be specified in ESOBU_PB_TM (FIG. 12) in units of the number of fields. In addition, when playback is started from the middle of the cell 13 on the video recording side, the playback start location can be specified by VOBU_PB_TM (not shown) in the time map information (TMAPI) defined by the video recording standard. It has become.

  2 can be summarized as follows. That is, the structure of ESOBS (Extend Stream Object Stream) is composed of one or more ESOBs (Extend Stream Object). This ESOB corresponds to one program, for example. The ESOB is composed of one or more ESOBUs (Extend stream object units), and this ESOBU corresponds to object data for a certain time interval (which varies depending on the value of VOBU / ESOBU_PBT_IVL in FIG. 9) or one or more GOP data. .

  However, when the transfer rate is low, 1 GOP may not be sent within 1 second (1 s) (in DVD-VR which MPEG encodes analog video input inside the device, since it is internal encoding, the configuration of the data unit is It can be set freely, but in the case of digital broadcasting, since the encoding is on the broadcasting station side, there is a possibility that it is unclear what data will come. 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 is increased, and there is a possibility that the entire management information is enlarged. Therefore, it is appropriate to divide the ESOBU according to an embodiment of the present invention by a fixed time interval (the minimum limit is that the delimiter is a picture unit other than the last ESOBU of the ESOB) or one or more GOPs. One ESOBU is composed of one or more packet groups, and each packet group is basically composed of eight packs (1 Pack = 1 sector: 2048 byte size).

  The packet group includes a packet group header, TS packets (85), and IAPAT (Incremental Application Packet Arrival Time) (84). The arrival time of each TS packet is represented by the arrival time of ATS in the packet group header for the first TS packet in the packet group, and the next is a value obtained by adding ATS and IAPAT. From then on, it is expressed as a value obtained by adding IAPAT to the previous arrival time. As described above, since the arrival time of the second and subsequent TS packets is represented by the difference from the previous arrival time, IAPAT can be represented by a small data amount (3 bytes), and the data amount can be saved. .

  FIG. 3 is a view for explaining the file structure according to the embodiment of the present invention. The data in the disk 100 of FIG. 1 includes a volume / file structure information area 111 containing a file system and a data area 112 for actually recording a data file. As shown in FIG. 3, the file system stored in the volume / file structure information area 111 includes information indicating which file is recorded where. The data area 112 is divided into a general computer recording area 120 and an AV data recording area 121. The AV data recording area 121 includes an AV data management information area 130 having a VMG file (including an ESMG file described later in a merged form) for managing the recorded AV data, and object data (VOBS) of the video recording standard. ) A VR object group recording area 122 in which a file (VRO file) is recorded, and an Estream object group recording area 131 in which an object (ESOBS) corresponding to digital broadcasting is recorded.

  Here, DVD-Video (ROM Video) is divided into VIDEO-TS, DVD-RTR (recording / playback DVD) is divided into DVD-RTAV, and the directory for each format is divided into DVD-HDVR, for example, DVD_HDVR. Recorded in the directory.

  That is, as shown in FIG. 3, the DVD_HDVR directory contains a VMG file for managing data, an object file for recording analog AV information such as analog broadcast and analog line input, and a digital broadcast. An SRO file as an object is recorded, and the SRO file is an ESOBS (Extend stream object Set). Then, as shown in FIG. 3, the SR management data is recorded in a VMG file common to the VR, controlled in common with the VR, linked in units of CELL, and designation of the reproduction location is designated in units of reproduction time. .

  Also, a directory called DVD_HDVR contains HR_THNL. A text file added separately from DAT and item text (IT_TXT): HR_TEXT. DAT and HR_EXEP. For storing information added to the entry point (EP). DAT (if the extended entry point EXEP is in the VMG, this HR_EXEP.DAT file is not required).

  Management information (ESFIT in FIG. 4 or RTR_ESMG in FIG. 14) of ESR (Extend stream Recording) is stored in the VMG file (HR_MANGER.IFO) in FIG. 3, and can be managed in the same manner as VR data. In this case, stream management information is stored in an ESFIT (Extend stream File Information table).

  FIG. 4 is a diagram for explaining an example of how a part (RTR_VMGI) of one piece of management information (RTR_VMG) recorded in the AV data management information recording area 130 is configured. Stream recording in this embodiment is abbreviated as ESR (Extend Stream Recording), and video recording is abbreviated as VR (Video Recording). Then, ESR data management information is stored in the RTR_VMG 130 and is managed in the same row as the VR data.

  RTR_VMG 130 includes video manager information (RTR_VMGI) 1310, stream file information table (ESFIT) 1320, (original) program chain information (ORG_PGCI) 1330, and playlist information (PL_SRPT; or user-defined). A program chain information table (UD_PGCIT) 1340, a text data manager (TXTD_MG) 1350, a vendor information table (MNFIT) 1360, and an extended entry point table (EX_EPIT) 1361 are configured.

  The playlist and the user-defined program chain have substantially the same meaning although having different names, and are synonymous with the playlist and the user-defined program chain used in the video recording standard. Therefore, in the following description, playlist-related information (PL_SRP, etc.) and user-defined program chain-related information (UD_PGCIT_SRP, etc.) are written together as appropriate.

   RTR_VMGI.1310 includes disc management identification information (VMG_ID / ESMG_ID) 1311, version information (VERN) 1312, E stream object management information start address (ESFIT_SA) 1313, program chain information start address (ORG_PGCI_SA) 1315, play A list information start address (UD_PGCIT_SA) 1316 is included. The management information of the ESR stream is stored in the ESFIT 1320.

  FIG. 5 is a diagram for explaining an example of how the other part (ESFIT) of one management information (RTR_VMG) is configured in the data structure according to the embodiment of the present invention. The ESFIT 1320 includes ESFIT general information ESFITI_GI (General Information) 1321, ESOBI_VSTI (Video Status Information) 1322, ESOBI_ASTI (Audio Status Information) 1323, and ESFI (Extend Stream File Information) 1324. ESFITI_GI can also be composed of the number of ESOBs, the number of VSTIs, the number of ASTIs, the end address of ESFIT, and the like.

  VSTI and ASTI are attribute information of streams in ESOB, video attribute information can be represented by VSTI, and audio attribute information can be represented by ASTI. In the VR standard, the stream information STI constitutes one STI as a set of VIDEO and AUDIO, but in the case of digital broadcasting, there is a possibility that a plurality of videos and / or audios are included in the broadcast signal. For this reason, the STI is not always represented by the same video / audio pair as in the VR standard. Therefore, if the video and audio are managed as separate attribute information, the total amount of STI information can be reduced. Details of the video attribute information (V_ATR) and the audio attribute information (A_ATR) will be described later with reference to FIG.

  FIG. 6 is a diagram for explaining an example of how the contents of ESFITI_GI and ESFI are configured among the components of the management information (ESFIT) shown in FIG. ESFITI_GI · 1321 includes information 13211 indicating the number of ESOBs, information 13212 indicating the number of ESOB_VSTIs, information 13213 indicating the number of ESOB_ASTIs, and information 13214 indicating the end address of ESFIT. ESFI 1324 includes general information ESFI_GI 13251, one or more stream object information (ESOBI # 1 to #K) 13253, and one or more search pointers (ESOBI_SRP # 1) for these (ESOBI # 1 to #m). To #K) 13252.

  FIG. 7 is a diagram for explaining an example of how the contents of ESOBI_VSTI and ESOBI_ASTI are configured among the components of the management information (ESFIT) shown in FIG.

  There are two types of VSTI attribute information V_ATR · 13221V. In Example 01 of FIG. 7, the compression mode (0 = MPEG1) is compatible with HD (high definition) (although basically having the same bit configuration as the VR standard). 1 = MPEG2; 2 = MPEG4 / H264), TV system (0 = NTSC525 / 60; 1 = PAL625 / 50), aspect ratio (0 = 4: 3; 1 = 16: 9), I / P (Interlace / Progressive) identification flag (0 = interlace; 1 = progressive) and video resolution information (0 = 720 × 480; 1 = 704 × 480; 2 = 352 × 480; 3 = 352 × 240; 4 = 544 × 480; 5 = 480 × 480; 6 = 1280 × 720; 7 = 1920 × 1080).

  On the other hand, Example 02 is configured to use SI (Service Information). That is, the data on SI is set in V_ATR without processing, and the component descriptor value is used as it is for setting the stream content and component type.

  Similarly to V_ATR, ASTI attribute information A_ATR · 13223 is HD-compatible (in principle, has the same bit configuration as VR), and is in compression mode (0 = AC3 (R); 1 = extension). MPEG1 or MPEG2 without bitstream; 2 = MPEG2; 3 = Linear PCM; 4 = MPEG2 · AAC; 5 = DTS (R)) and quantization / dynamic range control (0 = sampling frequency fs48 kHz; 1 = fs96 kHz) The number of audio channels (0 to 7 = 1ch to 8ch; 8 = 2ch dual mono) and the like are added. In Example 12, the value of the SI component descriptor is set as it is to the stream content and component type of A_ATR.

  FIG. 8 is a diagram for explaining an example of how the contents of ESFI_GI and ESOBI are configured in the management information shown in FIG. ESFI_GI includes the number of ESOBI_SRP, APP_NAME, ESOB file name, and the end address of ESFI. Each ESOBI includes stream object general information ESOBI_GI, one or more ESOB elementary stream information, seamless information SMLI, audio gap information AGAPI, time map general information TMAP_GI, and one or more elementary stream map information ES_MAPI. And the number of ES groups and one or more ES group information.

  FIG. 9 is a diagram for explaining an example of how the contents of the stream object general information (ESOB_GI) are configured in the management information shown in FIG. As shown in FIG. 9, the stream object general information ESOBI_GI includes ESOBI type ESOBI_TY, recording start time ESOB_REC_TM / ESOB_REC_TM_SUB, ESOB start PTS (playback time stamp) or ATS (arrival time), and PTS at the end of ESOB. Or either ATS.

  Furthermore, ESOBI_GI includes PCR_PKT_SHIFT indicating the position shift of the PCR packet, the length AP_PKT_SZ of the received stream packet (because it is a current TS packet, 188), the number of received stream packets in the packet group PKT_GRP_SZ (current TS packet) Therefore, 85 packets), number of map groups, APP_NAME, PAT, TS_ID, NETWORK_PID, PID of PMT of recorded stream, PMT, SERVICE PID, FORMAT ID, Version (type of data in case of external input) The value of the registration station descriptor indicating the data type, and in the case of an internal tuner, a tuner-specific data type is set), ESOB_REP_PID (representative SOB to be reproduced) It is also considered as the PID of the stream or the number of the component group.In the case of the representative PID, it is used to create the ESOBI_GI recording start time, ESOB start, ESOB end PTS or ATS), PCR PID, ESOB ES number It is configured.

  Further, ESOBI_GI contains default PID (or component tag) of ESOB video: ESOB_REP_PID, ESOB edited time: ESOB_EDIT_TIME, and the like. Thereby, even if the PID to be reproduced is not described in the cell information CI or the like, the reproduction can be performed according to the ESOB_REP_PID in the ESOBI.

  Furthermore, VOBU / ESOBU_PBT_IVL for changing the time interval of VOBU / ESOBU is set in ESOBI_GI (setting of VOBU / ESOBU_PBT_IVL is also possible in time map general information TMAP_GI).

When the value of VOBU / ESOBU_PBT_IVL is 0, VOBU / ESOBU is 0.4 s to 1.0 s. When the value of VOBU / ESOBU_PBT_IVL is 1, VOBU / ESOBU is 1.0 s to 2.0 s, and VOBU / ESOBU_PBT_IV is In the case of 2, VOBU / ESOBU is 2.0 s to 3.0 s. As a result, even if the recording time increases, the time map information TMAPI can be prevented from becoming extremely large. (However, if the time interval between entries increases, the possibility that double-speed playback or the like cannot be performed smoothly increases.)
Further, it is checked whether ESOB can be analyzed. If the analysis is possible, 0 is set in ESOB_COG / NONCOG, and 1 is set in ESOB_COG / NONCOG if the analysis is impossible. When ESOB_COG / NONCOG is set to 0, TMAPI in the embodiment of the present application is configured, and reproduction or the like is performed. However, when ESOB_COG / NONCOG is set to 1, it has unique management information unique to the manufacturer and manages the content.

  FIG. 10 shows how the contents of the ESOB elementary stream information, time map general information (TMAP_GI), elementary stream map information (ES_MAPI), and ES group information are included in the management information shown in FIG. It is a figure explaining an example of what is done.

  As shown in FIG. 10, ESOB_ESI sets a stream type, a PID of the stream, a VSTI number in the case of Video, an ASTI number in the case of Audio, and 0xffff in other cases. The stream type here is the type written in the PMT.

  As shown in FIG. 10, TMAP_GI is ADR_OFS (start address of SOB start: Logical Block: LB unit), ESOB_S_PKT_POS (start packet number in ESOB LB), ESOB_E_PKT_POS (end packet number in ESOB LB) , ES_MAP number.

  FIG. 11 is a diagram illustrating an example of how the contents of ES_MAP_GI illustrated in FIG. 10 are configured. As shown in FIG. 11, ES_MAPI is composed of ES_MAP_GI and ESOBU entry information. ES_MAP_GI · 1334661 is ES_PID (PID of the corresponding elementary stream) 13243611, ESOBU entry number 13243612, 1ST_ESOBU_S_PKT_POS (TS packet number from the first TS packet of the first ESOBU) 13243613, ESOB type 1324361 It is configured to include the PCR interval 13243615 shown in ESOBU.

  There are three types of ESOBUs: when there is video data, when there is no video data and there is audio data, and only other information. In the example of FIG. 11, the types of ESOBU are 00, 01, and 10, respectively.

  As for the PCR interval, when it is “00”, it indicates that the PCR position immediately before (1 PCR before) the reference picture REF-PIC (I picture) is indicated in ESOB_ENT, and when it is “01” Indicates that the PCR position before 2 PCR of REF-PIC is indicated in ESOB_ENT, and when it is “10”, it indicates that the PCR position before 3 PCR of REF-PIC is indicated in ESOB_ENT. When “11”, other indication states are displayed.

  FIG. 12 is a diagram illustrating an example of how the contents of ESOBU_ENT illustrated in FIG. 10 are configured. FIG. 13 is a diagram illustrating an example of what the ESOBU shown in FIG. 2 has depending on the presence or absence of video data and audio data.

  As shown in FIG. 12 and FIG. 13, there are three types of ESOBUs: a case where video data is present, a case where there is no video data and audio data, and a case where only other information is present, and the types are <1>, <2> and <3>. That is, according to this type, there are the above three types of ESOBU entry information.

  <1> When there is video data, ESOBU entry information includes last address information (LB unit) 1st_Ref_PIC_SZ from the ESOBU head of the first reference picture (I picture or the like) in the entry, and ESOBU playback time (number of fields) ESOBU_PB_TM ESOBU_SZ (number of packet groups in the size represented by the number of packet groups, as shown in FIG. 62 described later) and ESOBU_START (number of packets from the head of the packet group containing the head of ESOBU) ), PCR_POS, and Random_access_flag.

  PCR_POS indicates the position of the PCR indicated by the PCR interval by the number of addresses from the head of ESOBU. If no PCR is present, PCR_POS is 0xffff. The number of LBs in PCR_POS can be expressed by PCR_POS × 2 ^ PCR_POS_SHIFT. Here, the PCR is the position of the PCR several minutes before the reference picture and several minutes before the position indicated by the PCR interval. Random_access_flag is a flag indicating whether or not there is an I picture at the head of the ESOBU. When this flag is 1, there is an I picture, and when this flag is 0, there is no I picture.

Thereby, in the case of time search, ESOBU of the target time can be obtained by accumulating ESOBU_PB_TM, and the reproduction start PTM can be converted by the number of fields from the head of the ESOBU. Here, assuming that ESOBU of the target to be time searched is K and the target address is A, “ESOBU_SZ (N) is accumulated by multiplying the accumulated value from N = 1 to N = K−1 by 8 and adding 1 to it. Value "becomes the target address A. That is,
A = Σ ^k−1 _{N = 1} {ESOBU_SZ (N)} × 8 + 1 (1)
It becomes. Further, the leading packet is a packet having the value of ESOBU_START, and this address is accessed.

  <2> When there is no video data and there is audio data, the last address information from the beginning of ESOBU of the first audio frame in the entry (same as above), ESOBU playback time (number of fields), ESOBU size ( ESOBU entry information is composed of PCR_POS and the same as above.

  <3> In the case of only other information, since entry information is not configured, all are filled with FF.

  FIG. 14 shows which PGC information (original PGC information ORG_PGCI / user definition information table information UD_PGCITI) included in another management information (stream data management information RTR_ESMG) recorded in the AV data management information recording area 130 is. It is a figure explaining an example of how it is comprised. The user definition information table information UD_PGCITI 1340 includes UD_PGCIT · 1341, one or more UD_PGCI_SRP # 1 to # r · 1342, and one or more user definition information UD_PGCI # 1 to # s · 1343.

  FIG. 15 is a diagram for explaining an example of how the components of the program chain information (ORG_PGC information or UD_PGC information) shown in FIG. 14 are configured. The program chain information (PGC information; PGCI) includes program chain general information (PGC_GI) 1331, one or more program information (PGI # 1 to #p) 1332, and one or more cell search pointers (CELL_SRP # 1 to ##). q) 1333 and one or more pieces of cell information (CI # 1 to #q) 1334.

  Program chain general information 1331 includes information on the number of programs 13311 and the number of cell search pointers 13312. Each program information 1332 includes a program type 13321, a cell number 13322 in the program, primary text information 13323, item text search pointer number 13324, representative image information 13325, editor ID 13326, program index number (program absolute number). ) 13327, program update date and time 13328, and vendor information number 13329. Each cell information 1334 includes a cell type 13341, an ESFI number 13342, a corresponding ESOB number 13343, a reference ID 13344, a number of cell entry point information 13345, a cell start PTS / ATS 13346, and a cell end PTS / ATS 13347. And a cell entry point information table (C_EPIT) 13348.

  Here, the date / time information (year / month / day, hour / minute / second) when the program management information is updated is stored in the field of program update date / time 13328. In the field of the MNFI number 13329, the number of the trader information search pointer is described.

  Incidentally, the PGC information in FIG. 15 is reproduction information, and the ORG_PGC information is automatically created by a device (recorder) at the time of recording, and is set in the order of recording, as in the normal VR format. On the other hand, the UD_PGC information is created in accordance with a playback order that is freely added by the user, and is called a playlist (PLAY / LIST). These two formats are common at the PGC level, and FIG. 15 shows the common format of the PGC information.

  The program information (PGI) stores date / time information 13328 at which the program (PG) was updated, and the date / time information indicates when the program was edited. Further, in order to use the MNFI provided to realize the manufacturer-specific function (recorder), the search pointer number (MNFI number) 13329 of the vendor information MNFI is set in the program information PGI. That is, by further setting a PG number (program index number in FIG. 23 described later) in the MNFI information, a link is established between the data in the MNFI information and the data in the PGCI.

  In the cell information 1334 of FIG. 15, the ESOB type is added to the cell type. Further, in the cell information 1334, the corresponding ESOB number is specified, and the cell start time (cell start PTS / ATS) and cell end time (cell end PTS / ATS) are specified. Here, the start time and end time of a cell can be expressed in two types, PTS unit (reproduction time) or ATS unit (transfer time).

  Here, if the time designation is the reproduction time (actual time at the time of reproduction), the same access method as the conventional VR becomes possible, and the user can designate the reproduction time, so that the user's desire is completely reflected. However, this method is a method that can be specified when the contents of the stream can be sufficiently analyzed. If the contents are not sufficiently understood, it must be specified in units of transfer time.

  Note that when the playback time is specified, playback cannot always be started at the head of the I picture. When the playback start frame is not an I picture, decoding is started from the immediately preceding I picture, and display of the playback video is started when the target frame is decoded. As a result, it can be shown to the user as if playback has started from the designated frame.

  Further, the “reference ID” included in the cell information 1334 in FIG. 15 is a component group in the method of setting the PID (or the value of the component tag) of the stream representing the stream to be reproduced and in the case of multi-view TV. A method of setting the ID of can be considered. In addition, when this setting value is 0xffff, there are a method of multi-displaying on a sub-screen and a method of preferentially displaying a previously set group (or default main group) and switching later (during playback).

  In addition, as a new concept, information indicating which manufacturer's device has been edited is added to the PGI by adding “manufacturer ID (editor ID · 13326) of the device (recorder) last edited”. ing. As a result, the usage status of the MNFI information used by each manufacturer can be known. Each device can determine that the information in the MNFI is not reliable when the MNFI area is rewritten by a device of another company. Therefore, after editing with a device of another company, the MNFI needs to be newly constructed. Also, a unique ID number (PG absolute number) 13327 is assigned to the PG so that the PG can be designated by a number that does not change even if the intermediate PG is deleted.

  Further, in the cell entry point information table C_EPIT 13348, a serial number (index number: EP_INDX_NUM in FIG. 18 to be described later) and editing date and time (LAST_TM in FIG. 18 to be described later) of the entry point, and a PTM for specifying a thumbnail belonging to the EP (Position not necessarily the same as the position of EP: EP_PTM in FIG. 18 to be described later), thumbnail number in the thumbnail file (TBN_PT in FIG. 18 to be described later), pointer to text other than PRM_TXT (TXT_NUM in FIG. 18 to be described later) In the case of item text, the item number is added, and in other cases, a pointer in a text data file of another file is added.

In addition, in order to reduce the data amount of the VMG (HR_MANGR.IFO file in FIG. 3), the minimum entry point information is described on the VMG. If this is insufficient, the extended entry point information (in FIG. HR_EXEP.DAT or C_EPIT in FIG. (VMG data must be resident in the device memory for management information that is frequently referred to in device operation. Therefore, if VMG data is large, the necessary work RAM capacity increases accordingly, which ultimately increases the cost of the device. For this reason, the VMG data should have a smaller size.)
Here, the extended entry point information is classified into two methods: a method of appropriately adding after VMG (C_EPIT in FIG. 15) and a method having another file (HR_EXEP.DAT in FIG. 3). In this case, whether or not there is an extended entry point is whether or not the entry point index number (EPL_INDEX in FIG. 22 described later) in the extended entry point information (HR_EXEP.DAT or C_EPIT) matches the number of the target entry point. And you can check it. However, if the flag indicating that the extended entry point information EXEP exists is added to the original entry point information, the process of confirming the existence of the extended entry point is simplified. However, this increases management information, which leads to an increase in the amount of VMG data.

  That is, a data area (131) for recording AV information including moving picture information, and a management area (130) for storing management information for managing the AV information recorded in this data area as one or more programs (PG). The information medium (100 in FIG. 1) is the management information (DVD_HDVR / HR_MANGR.IFO in FIG. 3; VMG in FIG. 4 or ESMG in FIG. 14) is the connection (chain) of the one or more programs (PG). Program chain information (PGCI in FIG. 4 or FIG. 14) for managing reproduction and vendor information (MNFI in FIG. 4 or FIG. 14) that can describe vendor-specific information are configured. PGCI) includes program information (PGI) as management information of the program (PG), and the program (PG There configured to update date information when it is updated, so that it can be stored in both of the program information the skilled information (PGI in FIG. 15) (MNFI in Figure 23).

  FIG. 16 is a diagram for explaining an example of how the content of the text data manager (TXTD_MG) included in the management information recorded in the management information recording area 130 of FIG. 4 or 14 is configured. The text data manager (TXTD_MG) 1350 is configured to include text data information 1351, one or more item text search pointers 1352, and one or more item texts (IT_TXT) 1353. Each item text 1353 can include a program index number 13531, a program update date 13532, and text data 13533.

  Here, for example, PRM_TXT in FIG. 15 is used as text information recorded on the disc 100 in FIG. 1, for example, for a recorded program name, and IT_TXT in FIG. 16 is used to store other text information. In the IT_TXT text data area, other information (for example, if the recorded program is a movie, its director name, leading actor name, etc.) can be stored. In this case, the stored IT_TXT search pointer number is set and linked to the program information PGI in FIG. 15, and the PG number (program index number) is also set in the IT_TXT data in FIG. Here, the 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 other programs PG are deleted.

  Note that by setting PG update date / time information (13532, 13632) in both MNFI in FIG. 23 and IT_TXT in FIG. It is possible to verify whether it has been edited by other recorders.

  FIG. 17 is a diagram illustrating an example of how the contents of the cell entry point information table (C_EPIT) included in the cell information of FIG. 15 are configured. This C_EPIT can have one or more cell entry point information (# 1 to #n) 1333481.

  FIG. 18 is a diagram for explaining an example (EPI of Example 1) of how the contents of the cell entry point information (C_EPI) in FIG. 17 are configured. In this example (example 1), each C_EPI includes an entry point type (EP_TY), an absolute number of entry points (EP_INDX_NUM), a playback time of entry points (EP_PTM), a last edit date (LAST_TM), and a primary text. Information (PRM_TXT), playback time pointer (EP_REP_PIC) of the thumbnail image (still image for index) belonging to the corresponding entry point (program), and thumbnail number (thumbnail pointer TBN_PT) in the thumbnail belonging to the corresponding entry point And the item text number (pointer that refers to another text file) (TXT_NUM) belonging to the entry point.

  That is, a data area (131) for recording AV information including moving picture information, and a management area (130) for storing management information for managing the AV information recorded in this data area as one or more programs (PG). The information medium (100 in FIG. 1) includes index image information (thumbnail or representative image) in a different area (HR_THNL.DAT in FIG. 3) from the moving image information (HR_STRMx.SRO, etc. in FIG. 3). The management information (DVD_HDVR / HR_MANGR.IFO in FIG. 3; ESMG / PGCI in FIG. 14) includes information (CI in FIG. 15) on the cell (C) corresponding to a part of the program (PG). Information (CI in FIG. 15) includes entry point information (C_EPI in FIG. 17) indicating a position entering the program. Point information (C_EPI in Figure 17) is constituted to be able to have an index pointer information specifying the index image information (TBN_PT in Figure 18).

  Alternatively, a data area (131) for recording AV information including moving picture information and a management area (130) for storing management information for managing the AV information recorded in the data area as one or more programs (PG) are provided. The information medium (100 in FIG. 1) includes the management information (DVD_HDVR / HR_MANGR.IFO in FIG. 3; ESMG / PGCI in FIG. 14), the primary text information (PRM_TXTI), and the primary text information (in PGCI) Is one or more item texts (IT-TXT in FIG. 16) stored in another location (HR_TEXT.DAT; VMG / TXTDT_MG), and information on the cell (C) corresponding to a part of the program (PG) ( This cell information (CI in FIG. 15) indicates the position within the program. Entry point information (C_EPI in FIG. 17), and the entry point information (C_EPI in FIG. 17) is one or more (in order to add text information necessary when PRM_TXTI does not fit in C_EPI). Item text pointer information (TXT_NUM in FIG. 18) for designating the item text (IT-TXT in FIG. 16) can be held.

  FIG. 19 is a diagram illustrating an example of how the contents of the entry point type (EP_TY) included in C_EPI of FIG. 18 are configured. This EP_TY can store a thumbnail on / off flag, a primary text on / off flag, an item text on / off flag, and the like.

  Here, when the thumbnail on / off flag is on, TBN_PT in FIG. 18 exists, and when this flag is off, it indicates that TBN_PT does not exist. When the on / off flag of the primary text is on, PRM_TXT in FIG. 18 exists, and when this flag is off, it indicates that PRM_TXT does not exist. Similarly, when the on / off flag of the item text is on, TXT_NUM of FIG. 18 exists, and when this flag is off, it indicates that TXT_NUM does not exist.

  That is, the entry point information (C_EPI in FIG. 18) may include a flag (Thumbnail on / off Flag in FIG. 19) indicating the presence or absence of the index pointer information (TBN_PT). Further, the entry point information (C_EPI) may include a flag (IT_TXT on / off Flag in FIG. 19) indicating the presence / absence of the item text pointer information (TXT_NUM).

FIG. 20 is a diagram for explaining an example (EPI of Example 2) of how the contents of the cell entry point information (C_EPI) in FIG. 17 are configured. In this example (example 2), each C_EPI includes the absolute number of the entry point (EP_INDX_NUM), the playback time of the entry point (EP_PTM), the last edit date and time (LAST_TM), and the main part of the entry point (of the program). The playback time pointer (EP_REP_PIC) of the upper thumbnail image (index still image) can be included. (Example 2 in FIG. 20 can be made smaller in data size than in Example 1 in FIG. 18. Instead, an extended entry point information table is provided as shown in FIG. 21, and information omitted in FIG. Of the extended file HR_EXEP.DAT or each entry point information in the extended entry point information table.)
FIG. 21 shows (or how the extended entry point information table (EX_EPIT) included in the management information recorded in the management information recording area 130 of FIG. 4 or FIG. 14 is managed). It is a figure explaining an example. Here, EX_EPIT is provided at the end of the management information array (after MNFIT). However, the same information as the contents of EX_EPIT is stored in the extended file HR_EXEP. When describing in DAT, it is not necessary to provide EX_EPIT after MNFIT (for this reason, in the note of FIG. 4 etc., “EX_EPIT is described only in the case of EPI of Example 2”).

  FIG. 22 is a diagram illustrating an example of how the contents of the extended entry point information table (EX_EPIT) of FIG. 21 are configured (when the EPI of Example 2 is used). This EX_EPIT includes the total number (EX_EP_NUMS) of extended entry points (EX_EP) and the number of extended entry points (1 to n of EX_EPI) indicated by this EX_EP_NUMS. Each extension entry point (EX_EPI) has the same data field. That is, each EX_EPI includes an absolute number (index number) (EPL_INDEX) of an entry point of a link destination, an entry point type (EP_TY having the same contents as in FIG. 19), primary text information (PRM_TXT), and a thumbnail pointer (TBN_PT). ) And an item text number (IT_TXT_NUM).

  That is, a data area (131) for recording AV information including moving picture information, and a management area (130) for storing management information for managing the AV information recorded in this data area as one or more programs (PG). The information medium (100 in FIG. 1) has index image information (thumbnail or representative image) in an object area (HR_THNL.DAT in FIG. 3) different from the moving image information (HR_STRMx.SRO, etc. in FIG. 3). The management information (DVD_HDVR / HR_MANGR.IFO in FIG. 3; ESMG / PGCI in FIG. 14) includes program information (program index number / PG absolute number in FIG. 15) including the absolute number information of the program (PG) (FIG. 15). 15 PGI) and cell (C) information corresponding to a part of the program (PG) (FIG. 15). I), and the cell information (CI) includes entry point information (C_EPI in FIG. 17) indicating a position entering the program, and the entry point information (C_EPI in FIG. 17) includes the entry point. In the management area (HR_EXEP.DAT in FIG. 3 or EX_EPIT in FIG. 22) different from the management information (DVD_HDVR / HR_MANGR.IFO) in the management information (EP_INDX_NUM in FIG. 18). The entry point extended information (EX_EPI # 1 to #n in FIG. 22) can be held.

  FIG. 23 is a diagram for explaining an example of how the contents of the vendor information (manufacturer information MNFI) included in the management information recorded in the management information recording area 130 of FIG. 4 or FIG. 14 is configured. is there. The trader information (MNFI) 1360 includes trader information table information 1361, one or more MNFI search pointers (# 1 to #k) 1362, and one or more MNFIs (# 1 to #k) 1363. Each MNFI 1363 includes a program index number 13631, an MNFI recording date 13632 *, a program update date 1362, and NMFI data 13633. The vendor information (MNFI) of the DVD recorder configured as described above is released as information that can be freely used for each manufacturer.

  As can be seen from FIG. 16 and FIG. 23, program update date and time information can be set in both MNFI and IT_TXT. As a result, for example, when the menu is displayed, it is possible to verify whether there has been an edit by another manufacturer by checking the coincidence of the times recorded in the update date and time information.

  FIG. 24 is a diagram for explaining an example of how the stream object data unit (ESOBU) shown in FIG. 1 or 2 is configured. One ESOBU 134 is composed of one or more packet groups 140, and each packet group 140 is composed of, for example, 8 packs (1 pack = 1 sector: 2048 bytes).

  Each packet group 140 includes a packet group header (152 bytes) 161, one or more (here, 85) MPEG-TS packets (188 bytes) 162, and one or more (here, 84) IAPAT (Incremental Application Packet). Arrival Time; 3 bytes) 163.

The packet group header 161 includes a synchronization pattern 151, a packet arrival time (ATS) 152, information indicating the validity of the following DCI and CCI (DCI_CCI_SS) 153, display control information (DCI; Display Control Information) 154, Copy generation management information (or copy control information CCI; Copy Control Information) 155; PCR position information (PCRI; Program Clock Reference Information) 156; Manufacturer information (MNI (or vendor information MNFI); Manufacturer's information) 157; It is comprised including. (Note that there may be an embodiment in which the packet group header 161 further includes reproduction time information (PTS)).
Each MPEG-TS packet 162 includes a 4-byte header 170, an adaptation field, and / or a payload 180. Here, the header 170 includes a synchronization byte 171, a transport error indicator 172, a payload unit start indicator 173, a transport priority 174, a packet identifier (PID) 175, and a transport scramble control 176. , And an adaptation field control 177 and a continuity index 178.

  FIG. 25 is a diagram for explaining an example of how the packet arrival time (ATS), validity information (DCI_CCI_SS), and display control information (DCI) included in the packet group header shown in FIG. 24 are configured. It is. Here, for example, 6 bytes are allocated to ATS · 152, the PAT base (for example, 90 kHz counter value) is represented by 38 to 0 bits, and the PAT extent (for example, 27 MHz counter value) is represented by 8 to 0 bits. Yes. The actual arrival time PAT is represented by PAT_base / 90000 Hz + PAT_exten / 27,000, 000 Hz. As a result, the ATS • 152 can be expressed finely in units of video frames, for example.

  On the other hand, the validity information (DCI_CCI_SS) is composed of 1 byte, and 1-bit DCI_SS therein is 0 for invalidity and 1 for validity. The 3-bit CCI_SS is 0 for invalidity, 1 for APS only, 2 for EPN only, and 3 for APS and EPN. 4 indicates that only CGMS is valid, 5 indicates that CGMS and APS are valid, 6 indicates that CGMS and EPN are valid, and 7 indicates that APS, EPN and CGMS are all three. It shows that it is effective.

  Furthermore, 4 bytes are allocated to the display control information (DCI) 154, and DCI for 32 streams is set for each ES. When there is no stream, this DCI field is filled with “0”. The breakdown of the DCI includes ES1 to ES32 aspect flags ("0" indicates an aspect ratio of 4: 3 and "1" indicates an aspect ratio of 16: 9) in order from the top.

  FIG. 26 is a diagram illustrating an example of how copy generation management information (or copy control information CCI) included in the packet group header shown in FIG. 24 is configured. CCI is digital copy control (00 = copy prohibited, 01 = copy allowed once, 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 here, Macrovision (R) is assumed. ICT is image_constraint_token.

  CCI and DCI reflect the values of the digital copy control descriptor, the content use descriptor, and the component descriptor, respectively. In particular, EPNI reflects the value of encryption_mode (0: protect) of the content usage descriptor, and ICT reflects the value of image_constraint_token (0: limit) of the content usage descriptor.

  In the same ES, when CCI and DCI are likely to change within the same packet group, the packet group is temporarily divided, the remaining packs are filled with dummy data, and the next packet group is set. That is, alignment processing is performed so that CCI and DCI do not change within the packet group (this alignment processing will be described later with reference to FIGS. 39 and 40).

  FIG. 27 shows how the packet arrival time increment (IAPAT) and PCR position information (pack number or PCR_LB number number, etc.) included after the packet group header are configured in the packet group shown in FIG. It is a figure explaining an example. Here, for example, 3 bytes are allocated to IAPAT.163, and PAT base (for example, 90 kHz counter value) is represented by 14 to 0 bits, and PAT extent (for example, 27 MHz counter value) is represented by 8 to 0 bits. is doing. Since IAPAT.163 only represents the increment (change) from ATS.152, not the absolute time, the IAPAT data amount may be smaller than the ATS data amount.

  The implementation arrival time PAT in IAPAT.163 is expressed as ATS + PAT_base / 90000 Hz + PAT_exten / 27,000, 000 Hz. As a result, the IAPAT.163 can be expressed finely in units of video frames, for example. As another form, it is also possible to use the difference from the arrival time of the previous TS packet (the new PAT is the previous PAT plus PAT_base / 90000 Hz + PAT_exten / 27,000, 000 Hz) It is. Note that “PAT” in “PAT_base and PAT_exten” does not mean “Program Association Table”, but means “Packet Arrival Time”.

  On the other hand, the PCR position information 156 is expressed by 2 bytes, for example. With these 2 bytes, the PCR pack number can be expressed. This PCR pack number can be represented by the number of packs from the head of ESOBU closest to the head reference picture (for example, head I picture) to the pack with PCR. When no PCR exists, the PCR position information 156 is set to “0xffff”, for example.

  FIG. 28 shows the inside of a thumbnail (or representative image) object file (HR_THNL.DAT; if the EPI of Example 2 is used, a file different from the VMG file) managed in the DVD_HDVR file in the file structure of FIG. It is a figure explaining an example of a structure. This file is composed of the number of thumbnails (NUM_THUM) and one or more thumbnail objects (THUM # 1 to #n). Each thumbnail object (for example, THUM # 1) includes THUM_STI indicating the compression method of the corresponding thumbnail, the data length of the corresponding thumbnail (THUM_END_length), and actual data (THUM_DATA) of the corresponding thumbnail. Here, when THUM_STI is 0, the actual data (THUM_DATA) of the corresponding thumbnail is uncompressed bitmap data, 1 indicates JPEG compression, and 2 indicates MPEG1 compression. 3 indicates that the data is in TIFF format, and 4 indicates that the data is in GIF format.

  FIG. 29 is a diagram for explaining an example of the internal structure of an object file (HR_TEXT.DAT; additional text file) of text data managed in the DVD_HDVR file in the file structure of FIG.

This file is composed of the number of texts (NUM_TEXT) and one or more texts (TEXT # 1 to #n). Each text (for example, TEXT # 1) is composed of TEXT_STI indicating the character code system of the corresponding text, the data length (TEXT_length) of the corresponding text, and actual data (TEXT_DATA) of the corresponding text. Here, when TEXT_STI is 0, the actual data (TEXT_DATA) of the corresponding text is an ASCII code, 1 indicates a JIS code, and 2 indicates a shift JIS code. The case of 3 indicates that it is Unicode.

  Each text (TEXT # 1 to #n) in FIG. 29 is linked by IT_TXT_NUM in the extended entry point information table in FIG. 22 (or in the extended entry point file HR_EXEP.DAT file in FIG. 3). When the text area is insufficient in PRM_TXT in the information, the shortage can be compensated as needed by TEXT_DATA in TEXT # of FIG. 29 linked by IT_TXT_NUM.

<PG (PL) _INDEX>
Any two programs (or playlists) do not have the same program index value (or the same playlist index value). That is, when a new program (or playlist) is created, an unused index value is searched for and described in the program index (or playlist index). This program index (or playlist index) is maintained without change even if other programs (or playlists) are deleted or added.

<PG (PL) _LAST_MOD_TM>
The recorder that has changed the information related to the program (or playlist) is configured to update PG_LAST_MOD_TM (or PL_LAST_MOD_TM), which is one of the management information, simultaneously with the change. At that time, “information related to the program (or playlist)” is examined and specified.

“Information related to a program (or playlist)” means the following:
[Information related to the program]
Any information in the corresponding program information;
Any information in the corresponding cell information (or any information in the corresponding VOBI and / or SOBI).

[Information related to playlists]
Any information in the corresponding playlist search pointer;
Any information in the corresponding user-defined PGC information (or any information in the corresponding VOBI and / or SOBI).

  Here, only the VOB / VOBI or SOB / SOBI referenced by the corresponding program (or playlist) is changed without updating the PG (or PL) related to PGI, CI, PL_SRP, UD_PGCI. Think about it. However, if this happens, PG (PL) _LAST_MOD_TM is updated.

  Note that PG (PL) _INDEX and PG (PL) _LAST_MOD_TM may be option data linked to each PG (PL). A recorder that can handle such option data updates PG (PL) _LAST_MOD_TM in the option data area whenever PG (PL) _LAST_MOD_TM in PGI (PL_SRP) is updated.

  When only option data is updated without updating the information related to PGI (PL), PG (PL) _LAST_MOD_TM in both areas is maintained as it is without being changed.

  If the recorder detects that PG (PL) _INDEX and PG (PL) _LAST_MOD_TM described in the option data area have the same values as those described in PGI (PL_SRP), the recorder It can be recognized that the option data is consistent with the corresponding PG (PL). Otherwise, the recorder will recognize that the option data has lost consistency with the corresponding PG (PL).

  At least in theory, the concept of consistency detection described herein can be applied to other types of objects (eg, VOBs, cells, or entry points). However, when applying it, you must remember to pay attention to the data size and processing speed.

  FIG. 30 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. 30, the apparatus (digital video recorder / streamer) includes an MPU unit 80, a key input unit 103, a remote control receiving unit 103b that receives user operation information from the remote control 103a, a display unit 104, a decoder unit 59, an encoder. Unit 79, system time counter (STC) unit 102, data processor (D-PRO) unit 52, temporary storage unit 53, disk drive unit 51 for recording / reproducing information on / from recordable optical disc 100 such as a DVD-RAM , Hard disk drive (HDD) 100a, video mixing (V mixing) unit 66, frame memory unit 73, analog TV D / A conversion unit 67, analog TV tuner unit 82, terrestrial digital tuner unit 89, and satellite antenna 83a STB (Set Top Box) unit 83 connected to It is more configuration. Further, this apparatus includes a digital I / F 74 such as IEEE1394 in order to support digital input / output as a streamer. Note that the STC unit 102 is configured to perform clock counting on a 27 MHz base in accordance with the PAT_base of FIGS. 25 and 27.

  The STB unit 83 decodes the received digital broadcast data to generate an AV signal (digital), and the AV signal is transmitted to the TV 68 via the encoder unit 79, the decoder unit 59 and the D / A converter 67 in the streamer. The contents of the digital broadcast transmitted and received can be displayed. Alternatively, the STB unit 83 is configured to be able to send the decoded AV signal (digital) directly to the V mixing unit 66 and send the analog AV signal to the TV 68 via the D / A converter 67 therefrom. .

  By the way, since the apparatus of FIG. 30 constitutes a recorder having both video recording and stream recording functions, a configuration unnecessary for video recording (such as IEEE 1394 I / F) or a configuration unnecessary for stream recording (for AV input). A / D converter 84, audio encoding unit 86, video encoding unit 87, etc.).

  The encoder unit 79 includes an A / D converter 84, a video encoding unit 87, an input switching selector 85 to the video encoding unit 87, an audio encoding unit 86, a sub-picture encoding unit, and a formatting unit (not shown). 90 and a buffer memory unit 91.

  The decoding unit 59 also includes a separation unit 60 incorporating a memory 60a, a memory 61a and a video decoding unit 61 incorporating a reduced image (thumbnail or the like) generating unit 62, a sub-picture (SP) decoding unit 63, and a memory 64a. An audio decoding unit 64, a TS packet transfer unit 101, a video processor (V-PRO) unit 65, and an audio D / A converter 70. The analog output (monaural, stereo, or AAC 5.1CH surround) from the D / A converter 70 is input to an AV amplifier (not shown) or the like, and a required number of speakers 72 are driven.

  By the way, in order to display the content being recorded on the TV 68, the stream data to be recorded can be sent simultaneously to the D-PRO unit 52 and simultaneously to the decoder unit 59 for reproduction. 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, for example, every 16 packs (or 32 packs or 64 kbytes) as an ECC group, attaches the ECC, and sends the ECC group to the drive unit 51. However, if the drive unit 51 is not ready for recording on the disc 100, the drive unit 51 transfers it to the temporary storage unit 53, waits until it is ready to record data, and starts recording when it is ready. 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 temporary storage unit 53 can also be constructed using a part of the HDD 100a. The MPU unit 80 is configured to be able to read and write to the D-PRO unit 52 through a dedicated microcomputer bus in order to read and write the file management area and the like.

  In the apparatus of FIG. 30, an optical disk 100 such as a DVD-RAM / -RW / -R / Blue medium (a recordable / reproducible medium using a blue laser) is first assumed as a recording medium, and a hard disk drive ( HDD) 100a (and / or a large-capacity memory card not shown) is assumed.

  Examples of how to use these multiple media are as follows. That is, stream recording is performed on the HDD 100a using the data structure (format) shown in FIGS. Of the stream recording contents recorded on the HDD 100a, the program that the user desires to save is directly stream recorded (direct copy or digital dubbing) on the disc 100 (copying is not prohibited by the copy control information CCI). If). In this way, only desired programs having the same quality as the original digital broadcasting can be collected on the disc 100. Furthermore, since the stream recording content copied to the disc 100 uses the data structure of the present invention, special reproduction such as time search is facilitated regardless of the stream recording.

  A specific example of the digital recorder (streamer / video recorder constituted by a combination of DVD-RAM / -RW / -R / Blue media and HDD) having the above characteristics is the apparatus shown in FIG. The digital recorder shown in FIG. 30 includes a tuner unit (82, 83, 89), a disk unit (100, 100a), an encoder unit 79, a decoder unit 59, and a control unit (80). Has been.

  The satellite digital TV broadcast is broadcast from a broadcasting station through a communication satellite. The broadcast digital data is received and reproduced by the STB unit 83. The STB 83 is a device that decompresses and reproduces scrambled data based on a key code distributed from a broadcasting station. At this time, the scramble from the broadcasting station is released. Here, the data is scrambled in order to prevent a user who has not made a reception contract with the broadcast station from illegally viewing the broadcast program.

  In the STB unit 83, although not shown, the broadcast digital data is received by the tuner system. When the received data is reproduced as it is, the scramble is canceled by the digital decompression unit, the received data is decoded by the MPEG decoder unit, converted to a TV signal by the video encoder unit, and this TV signal is converted to D / A. It is sent to the outside through the converter 67. As a result, the digital broadcast program received by the STB unit 83 can be displayed on the analog TV 68.

  Terrestrial digital broadcasts are received and processed in the same way as satellite broadcasts, except that they do not go through communication satellites (and are not scrambled in free broadcasts). That is, the terrestrial digital broadcast is received by the terrestrial digital tuner unit 89, and when it is reproduced as it is, the decoded TV signal is transmitted to the outside through the D / A converter 67. As a result, the digital broadcast program received by the terrestrial digital tuner unit 89 can be displayed on the analog TV 68.

  The terrestrial analog broadcast is received by the terrestrial tuner unit 82, and when it is reproduced as it is, the received analog TV signal is transmitted to the outside. Thereby, the analog broadcast program received by the terrestrial tuner unit 82 can be displayed on the TV 68.

  The analog video signal analog-input from the external AV input 81 can be sent straight to the TV 68, but is once A / D converted by the A / D converter 84 and then the D / A converter 67. It can also be configured to send back to the external TV 68 side after returning to the analog video signal. With this configuration, even when an analog VCR reproduction signal with a large amount of jitter is input from the external AV input 81, an analog video signal without jitter (digital time base correction) can be output to the TV 68 side.

  A digital video signal digitally input from a digital I / F (IEEE 1394 interface) 74 is sent to the external TV 68 side via a D / A converter 67. Thereby, the digital video signal input to the digital I / F 74 can be displayed on the TV 68.

  A bit stream (MPEG-TS) input from satellite digital broadcast, terrestrial digital broadcast, or digital I / F 74 is a stream object 132 of the disk 100 (and / or HDD 100a) as a stream object 132 in FIG. Stream recording can be performed in the recording area 131 (FIG. 1D). Further, the analog video signal from the terrestrial analog broadcast or the A / V input 81 can be video-recorded in the VR object group recording area 122 (FIG. 1D) of the disc 100 (and / or the HDD 100a).

  Note that the apparatus can be configured so that the analog video signal from the terrestrial analog broadcast or the A / V input 81 is A / D converted and then stream-recorded instead of video-recorded. Conversely, the bit stream (MPEG-TS) input from the satellite digital broadcast, the terrestrial digital broadcast, or the digital I / F 74 is recorded as a video instead of a stream recording (after necessary format conversion). It is also possible to configure the device.

  Recording / playback control of stream recording or video recording is performed by firmware (a control program or the like corresponding to the operations of FIGS. 31 to 72 described later) written in the ROM 80C of the main MPU unit 80. The MPU unit 80 has a management data creation unit 80B for stream recording and video recording, creates various management information using the work RAM unit 80A as a work area, and the created management information is converted into the AV data management information shown in FIG. Records in the recording area 130 as appropriate. Further, the MPU unit 80 reproduces the management information recorded in the AV data management information recording area 130, and performs various controls (FIGS. 31 to 72) based on the reproduced management information. Note that the manufacturer ID information of the apparatus shown in FIG. 30 can be written in the ROM 80C of the MPU unit 80.

  The characteristics of the medium 100 (100a) used in the apparatus shown in FIG. 30 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 group 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 24). On the other hand, the management area 130 has PGC information (PGCI) as information for managing the playback procedure, and the PGC information includes cell information (CI). Further, the management area 130 has information for managing object data (ESOB).

  The apparatus in FIG. 30 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. Also, an attribute information creation unit (not shown; firmware that forms part of the management data creation unit 80B) 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. Wear).

  In the apparatus of FIG. 30, the signal flow during recording is as follows, for example. That is, the TS packet data received by the STB unit (or terrestrial digital tuner) is packet-grouped by the formatter unit and stored in the work (buffer memory unit 91). It is recorded on the disc when the minutes are accumulated. In this operation, when TS packets are received, 85 packets are grouped and a packet group header is created.

  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 (not shown), the video signal is MPEG compressed, and the audio signal is AC3 compressed or MPEG audio. Compression is performed, and the character data is run-length compressed.

  When the compressed data is packetized (or blocked) from each encoder unit, it is packetized (or blocked) to 2048 bytes and input to the formatter unit. In the formatter unit, each packet (or each block) is multiplexed and sent to the D-PRO unit. In the D-PRO unit, an ECC block is formed for every 16 (or 32) packets (or blocks), error correction data is attached, and the drive unit records the data on a disk.

  Here, since the drive unit is in a seek state or a track jump, when it is busy, it is put in the HDD buffer unit and waits until the 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 VOBU (ESOBU) packs (or the number of LBs), the end address of the I picture from the beginning of the VOBU (ESOBU), and the playback time of the VOBU (ESOBU).

  In the recording flow during reproduction, data is read from the disk from the drive unit, error-corrected by the D-PRO unit, and input to the decoding unit. The MPU unit determines whether the input data is VR data or ESR data (can be determined by the cell type), and sets the type in the decoder unit before reproduction. In the case of ESR data, the MPU unit determines the PMT_ID to be reproduced from the cell information CI to be reproduced, determines the PID of each item (video, audio, etc.) to be reproduced from the corresponding PMT, and sets it in the decoder unit. Based on the PID, the decoder unit sends each TS packet to each decode unit by the separation unit. Further, the packet is sent to the TS packet transfer unit, and is transmitted to the STB unit (1394 I / F unit) in the form of a TS packet 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 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.

  The signal flow during recording is as follows: 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 accumulated a certain amount (1 or an integer multiple thereof) (When the CDA is accumulated), it is recorded on the disc.

  FIG. 31 is a flowchart illustrating an example of the overall operation of the apparatus of FIG. 30 (overall operation processing flow). There are five data processings: program setting processing, recording processing, playback processing, data transfer processing (digital output processing), and editing processing.

  For example, when the apparatus of FIG. 30 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 (ST24), a process (ST26) for digital output to the STB is executed in parallel. Alternatively, a new program setting process (ST20) can be processed in parallel during the recording process (ST22) that is not timer reserved recording. Alternatively, the reproduction process (ST24) and the digital output process (ST26) can be performed in parallel during the recording process (ST22) by taking advantage of the high-speed accessible disk recording. It is also possible to perform a disc editing process (step ST28) during recording on the HDD.

  FIG. 32 is a flowchart for explaining an example of interrupt processing (interrupt processing flow) in the operation of the apparatus of FIG. In the interrupt process in the control operation of the MPU unit 80, first, an interrupt factor is checked (step ST30). If the interrupt factor is “because transfer of one pack (or one packet) to the D-PRO unit 52 has been completed”, the number of recording packs is counted up or the number of recording logical blocks LBN is incremented by one. (Step ST301). If the interrupt factor is “by capturing segmentation information from the formatter unit 90”, a segmentation information 1 capture interrupt flag (not shown) is set (step ST302).

  FIG. 33 is a flowchart for explaining an example (editing operation process flow) of the editing process (ST28) shown in FIG. 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. (PGI in FIG. 15, IT_TXT in FIG. 16, MNFI in FIG. 23, LAST_TM in FIG. 18 or 20) are set (step ST284).

  The program update date and time may be set when any one of the program information PGI and cell information CI shown in FIG. 15 or the VOB and ESOB shown in FIG. 2 is changed. Here, when VOBI and / or SOBI are changed, the editing time (EDIT_TIME) of VOBI and / or SOBI can be set to ESOB_EDIT_TIME of FIG.

  Incidentally, in the process of ST284, the manufacturer ID of the device that performed any of the operations of ST282A to ST282D may be set to the editor ID (LAST_MNF_ID) 13326 in FIG. 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, ESOB (or VOB) is changed.

  34 and 35 are flowcharts for explaining an example of the recording operation (recording flow with entry point addition processing) of the apparatus of FIG.

<a1> First, a program to be recorded is determined using an EPG (Electronic Program Guide) in the program setting process, reception is started, and the determined program is recorded;
<a2> When the MPU unit receives a recording command from the key input unit, the management data is read from the drive unit and the area to be written is determined. At this time, the file system is checked to determine whether or not recording is possible. If recording is possible, the recording position is determined. If the recording is not possible, the fact is indicated to the user and the process is stopped.

<a3> Set in the management area to write the determined area, set the video data write start address in the drive unit, and prepare for data recording;
<a4> Reset the time in the STC section. Here, the STC unit performs recording and playback on the basis of this value by a system timer;
<a5> 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) To do. At this time, the PAT and PMT are stored in the work RAM section of the MPU section and written to the management information. The VMG file data is written into the file system, and information necessary for the VMGI is written (step ST110; details are shown in FIG. 36).

<a6> Set the recording to each part. At this time, each data segmentation setting and TS packet reception setting are performed in the formatter unit. At this time, the PID of data to be recorded is set, and only the target video stream is recorded. Also, the buffer is set to start holding TS packets, and the formatter unit starts operation (step ST116);
<a7> VSTI and ASTI are created from the PTM (step ST120; see FIG. 37 for details).

  <a8> When a certain amount of data has accumulated in the buffer, ECC processing is performed through D-PRO and recorded on the disk (step ST130; details are shown in FIGS. 38 to 39).

<a9> During recording, the segmentation information is saved in the work RAM of the MPU unit periodically (before the buffer RAM of the formatter unit becomes full). The segmentation information here is ESOBU segmentation information, such as ESOBU start address, SOBU pack length, I-Pic end address, ESOBU arrival time (ATS), etc .;
After capturing the segmentation information from the <aX> formatter unit, an entry point addition process (step ST147: see FIG. 45 for details) is executed (when this process is set in advance).

<a10> Check if the recording is finished (whether the recording end key has been entered or if there is no remaining capacity). At the end, the remaining segmentation information is taken from the formatter and added to the work RAM. Are recorded in management data (VMGI), and the remaining information is recorded in the file system;
If it is not <a11> end, the process shifts to <a7> to continue to take in and play back data.

  Here, in order to display the content being recorded on the TV, the fetched data is sent to the decoder unit simultaneously with the D-PRO unit and reproduced. In this case, the MPU unit makes settings for reproduction in the decoder unit, and then the decoder automatically performs reproduction. The D-PRO unit collects every 16 packs as an ECC group, attaches the ECC, and sends it to the drive unit. However, if the drive unit is not ready for recording on the disk, it is transferred to the temporary storage unit, waits until it is ready to record data, and starts recording when it is ready. Here, since the temporary storage unit holds recording data of several minutes or more by high-speed access, a large-capacity memory is assumed. However, the MPU 80 is configured to be able to read and write to the D-PRO unit through the microcomputer bus in order to read and write the file management area and the like.

  FIG. 36 is a flowchart for explaining an example of a process (recording pre-processing process flow) before starting recording on the disk-shaped information storage medium (for example, an optical disk using a blue laser) shown in FIG.

<b1> Search for a directory of DVD_HDVR (a directory in which a new VR is to be entered). If this directory does not exist, the directory is created.
<b2> Check if it is recorded in the directory. If it is recorded, the VMGI that is the management information is read into the work, and this equipment supports it from the recorded broadcasting system (APP_NAME). If it is not supported, display that effect and exit.

<b3> If there is no recorded data, create VMGI in the work;
<b4> Check the broadcasting system of data to be recorded. (In the case of an internal tuner, the default method is used in the device. In the case of an external digital input, the Registration_Descriptor value sent from the digital input is examined to determine the recording method).

<b5> If it is different from the broadcasting system on the disc, display that effect and exit;
<b6> Judge whether the broadcasting system of the data to be recorded is a system supported by this equipment, and if it does not support it, display that fact and end.

<b7> Set the broadcasting method in the APP_NAME of VMGI built in the work, and in the case of automatic setting of EP, let the user set the interval time, and proceed to the next processing;
In addition, when a plurality of recording methods (broadcasting methods) are allowed to be mixed in the disc, it is necessary to describe APP_NAME in each ESOBI_GI. However, when a plurality of recording methods are prohibited, ESFI_GI or APP_NAME may be described in VMG_MAT
<b8> Finally, the user is allowed to input a set time (for example, an interval of 10 minutes) when automatically setting entry points (step ST1134), and the pre-recording process ends.

  FIG. 37 is a flowchart for explaining an example (STI setting process flow) of the stream information (VSTI and ASTI) creation process (ST120) shown in FIG.

<c1> Read VSTI and ASTI recorded on the disc into the work;
<c2> Check the PMT and check the number of configured streams;
<c3> Repeat <c4> to <c5> for the number of streams set.

<c4> The stream type is checked from the PMT to determine whether the stream is a video or audio stream. Otherwise, the process proceeds to the next stream check;
<c5> The stream type is divided into MPEG1 video, MPEG2 video, MPEG1 audio, MPEG2 audio, and the like, internal data is checked according to each type, and each attribute information is read out.

<c6> Compared to VSTI and ASTI from attribute information, if there is the same attribute information, set the number to the corresponding ESOB_ESI and move to the next stream check;
<c7> A new VSTI or ASTI is set based on the attribute information, the number is set in the corresponding ESOB_ESI, and the next stream check is performed.

  FIG. 38 is a flowchart for explaining an example (buffer fetch process flow) of the buffer fetch process (ST130) shown in FIG. The recording operation is that when TS packets are received, 85 packets are grouped and a packet group header is created.

<d1> First, a TS packet is received;
<d2> If the captured TS packet has a PCR, the STC is corrected;
<d3> If it is the head of the packet group, set Sync_Pattern: 00ffa5a5, fetch the arrival time from the STC and set it as ATS. If it is not the head, the arrival time of the previous TS packet and the arrival of this TS packet The difference from the time is placed in front of the TS packet as IAPAT.

<d4> DCI and CCI setting processing (step ST1311; see FIG. 39 for details);
<d5> Determine whether the packet group has ended (determine whether 85 TS packets have been grouped). If it has not ended, go to <d1>. Temporary storage in the buffer RAM.

  FIG. 39 is a flowchart for explaining an example of the DCI and CCI setting processing (ST1311) shown in FIG. The DCI and CCI setting processing will be further described.

<e1> Check if there is copy information in the latest PMT and EIT. If there is, configure and set copy information for each stream (maximum 32 ES) based on that information, then move to <e3>;
<e2> If there is no copy information in the received TS packet, the same information as the previous pack is configured as copy information.

<e3> Check whether there is a content usage descriptor in the latest PMT or EIT. If there is, set ICT and EPN for each ES (maximum 32 ES) based on that information, and move to <e5>;
<e4> If there is no copy information in the received TS packet, the same information as the previous pack is configured as ICT and EPN.

<e5> Check whether there is resolution information. If there is no resolution information, configure the resolution information for each ES (maximum 32 ES) based on the same information as the previous pack, if there is,
<e6> Check whether there is a change in CCI or DCI within the same ES within 85 packets. If there is, change this packet group to the TS packet before the change, and fill the rest of the packet group with dammed data. Register the changed packet as a new packet group.

  Here, the PTS is stored by looking inside the TS packet when the head of the picture is included in the group. When there is no video data and only audio data, the CCI is configured according to the audio copy information.

  At the time of reproduction, the pack data read from the disk is analyzed by the separation unit, and if the pack contains TS packets, it is sent to the TS packet transfer unit, and then sent to each decoder for reproduction. . 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 arrived. Then, the STB unit decodes the received stream, generates an AV signal, and displays the AV signal on the TV through the video encoder unit in the streamer.

  FIG. 40 is a diagram illustrating a pack group data structure in the process (pack group align process) of step ST13123 of FIG. When CCI and / or DCI are likely to change within the same packet group in the same ES, the packet group is temporarily divided and the remaining pack is filled with dummy data as shown in FIG. Set. That is, the alignment process is performed so that CCI and DCI do not change in the packet group.

  FIG. 41 illustrates an example of the stream file information (SFI or ESFI) creation process in the recording end process (ST150) shown in FIG. 34 (stream file information creation process flow with ESOB structure setting process and edit date setting process). It is a flowchart.

<f1> To increase the SOBI by one, the search pointer (SRP) is increased and the area is secured;
<f2> Set the recording time to SOB_REC_TM. Here, the clock inside the device (recorder) is set and corrected by TDT (Time Data Table), and an accurate time is always obtained.

<f3> Set the start PTM and end PTM;
<f4> Set PCR_POS_SHIFT according to the recording rate;
<f5> If the stream type is a TS stream (ARIB, DVB), set the packet size AP_PKT_SZ to 188, set the packet group size PKT_GRP_SZ to 8, otherwise set the value appropriate for the broadcasting system To do.

<f6> Set the broadcast system to APP_NAME;
<f7> Set TS_ID, NETWORK_PID, and PMT_ID (PID of PMT used in this ESOB) from PAT;
<f8> Set SERVICE_ID (Program_Number in PMT) and PCR_PID from PMT. Further, with respect to FORMAT_ID and VERSION, the default method is set in the device in the case of an internal tuner, and the value of Registration_Descriptor sent from the digital input is set in the case of external digital input.

<f9> Furthermore, the number of recorded ES is set. (The information on all ESs being broadcast; the 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.)
<f10> Information on which ES and which ES are to be played back as a set is contained in the component group descriptor, so the information of the ES to be paired is grouped. Further, the component tag information of the group is converted into PID by the stream descriptor in the PMT, and the information is stored as group information. (This EIT information may vary depending on the broadcasting system.)
<f11> The LB address at which recording is started is set in ADR_OFS, and a MAPI is created for each stream based on each segmentation information.

<f12> Set the default PID / component tag. The default video PID corresponds to the component tag value of 00, or in the case of multi-view TV, the PID of the stream corresponding to the component tag described in the main component group;
<f13> A process for setting the ESOB structure (step ST1522; see FIG. 42 for details) is performed, and then the editing date and time is set (step ST1524).

  FIG. 42 is a flowchart for explaining an example of the ESOB structure setting process (ST1522) shown in FIG.

<g1> First, check the recorded recording time. If the recording time is 2 hours or less, go to <g2>. If it is 2 to 4 hours, go to <g3>. If it is 4 hours or more, <g4> Move to>
<g2> 0 is set to ESOB_PB_IVL13243118 in FIG. 9, ESOBU_ENT is created so that ESOBU is 0.4 s to 1 s from the segmentation information (0.4 to 1 s information), and the process proceeds to <g5>.

<g3> 1 is set in ESOB_PB_IVL, ESOBU_ENT is created so that ESOBU becomes 1 s to 2 s from the segmentation information (information of 0.4 to 1.0 s), and the process proceeds to <g5>;
<g4> 2 is set in ESOB_PB_IVL, and ESOBU_ENT is created so that ESOBU is 2 s to 3 s based on the segmentation information (information of 0.4 to 1.0 s).

<g5> It is checked whether the data can be analyzed. If the data can be analyzed, ESOB_COG / NONCOG is set to 0 (step ST15227). And it sets so that the ESOB management process of this application may be performed, and this process is complete | finished;
<g6> When analysis is impossible (when encryption cannot be decrypted), ESOB_COG / NONCOG is set to 1, and each manufacturer is set to perform ESOB management processing that is considered private, and this processing ends.

  FIG. 43 is a flowchart for explaining an example (program setting process flow) of a program chain (PGC) creation process (including a program setting process) in the recording end process (ST150) shown in FIG.

<h1> Check if it is the first recording on the disc, create ORG_PGC if it is the first, and add it after the ORG_PGC if it is not the first;
Erase permission: 0 is set in <h2> PG_TY (program type 13321 in FIG. 15), and the number of cells is set in the field of Cell_Ns (number of cells in program 13322 in FIG. 15).

  In case of <h3> ARIB, 0x12 is set in language_code of short format event descriptor in EIT, and in case of "jpn", CHR (character code field) of VMG_MAT is set, and EVENT_NAME is set in the second area of PRM_TXTI. , REP_PICTI (ESOB_REP_PID in FIG. 9, representative PIC information 13325 in FIG. 15, EP_REP_PIC in FIG. 18, etc.) is set.

  <h4> The manufacturer ID of this device is set in LAST_MNF_ID (such as editor ID 13326 in FIG. 15). This value is set so that when the PGI, CI, or VOB is changed, the manufacturer ID of the changed device is set, and the device of the manufacturer that was last edited / recorded is known. This makes it easier to deal with changes in the recorded content of the same disc between devices of different manufacturers.

  When an absolute number of a program is set in <h5> PG_INDEX and the program is referred from other application software, the program can be referred to. Further, program update date / time information is recorded. At this time, if there is an MNFI or IT_TXT supported by this device (matching manufacturer code), the update date / time information of the corresponding data is also set.

<h6> Information unique to each manufacturer is set in the MNFI of FIG. 23;
<h7> Information indicating that it is a streamer is set in the cell type of FIG. 15;
<h8> A reference ESOB number is set, a representative (video) PID or Component_Group_Id is set as an ID to be played, and an EPI number, a playback start PTM, an end PTM, and an EP are set.

FIG. 44 is a flowchart for explaining an example (item text setting process flow) of item text (IT_TXT) creation processing in the program update date and time setting process (ST1704) shown in FIG. IT_TXT is text information that can be freely entered by the device, and it is conceivable that information from the user or text information in the broadcast is entered. In the embodiment of the present application, when there is an extended event descriptor in the EIT, the text information can be put in IT_TXT. Therefore, the IT_TXT setting process is as follows. That is,
<i1> It is checked whether IT_TXT information exists in the disc. If it does not exist, TXTDTI is set. If it exists, IT_TXT information is added.

<i2> Set the PG number of ORG_PGC to which this text belongs, confirm that the language code is “JPN” (if not, end this processing), and save this information as TEXT_DATA . Here is a more detailed description of the program;
<i3> Update the program update date / time information in the PGI, and update the program update date / time information in the IT_TXT and MNFI at the same time.

  FIG. 45 is a flowchart for explaining an example (EP addition process flow) of the entry point addition process (ST147) shown in FIG.

<j1> Check whether the EP automatic setting time has come, and if it is not time, end this processing;
<j2> The STC is checked, the recording time PTM is checked, and the EPI is additionally set according to the value. Here, PTM is set in EP_PTM and REP_PIC, and the absolute number of all EPs in the disc is set in EP_INDEX_NUM.

<j3> Edit and set date and time information to PGI and EPI_LAST_TM;
<j4> Check whether MNFIFI is linked to the PG to which this EP belongs, and if there is a linked MNFIFI, set the PG update date and time in the MNFI.

<j5> Check whether IT_TXT is linked to the PG to which this EP belongs, and if there is linked IT_TXTI, set the PG update date and time in IT_TXTI;
FIG. 46 shows an example of processing for setting a thumbnail (reduced image or representative image) corresponding to the entry point after the entry point has been added by the processing of FIG. 45 (when the entry point has already been added). It is a flowchart explaining reduced image setting processing flow.

<k1> Let the user select an entry point (EP) for adding a reduced image;
<k2> Displays the image of the EP selected by the user. At this time, if the frame specified by PTM is not an I picture, it is decoded from the previous I picture (not displayed) and displayed at the target frame.

<k3> Advance frame from here to let the user choose which reduced image to use;
<k4> The PTM (or the number of frames from the first frame) of the selected frame is set in EP_REP_PIC.

  <k5> The target frame displayed is reduced by the video decoding unit, the data is converted into JPEG, the data is read, and additionally stored in the Thumbnail file. At this time, the EP index number is recorded as Thumbnail data.

  <k6> Confirm with the user whether or not to set another EP, and if continuing, set to confirm from the next EP, and proceed to <k1>.

<k7> Update PGI date and time of PG update;
<k8> Check whether the MNFIFI is linked to the PG to which this EP belongs, and if there is a linked MNFIFI, set the PG update date and time in the MNFI;
<k9> It is checked whether IT_TXT is linked to the PG to which this EP belongs. If there is linked IT_TXTI, the PG update date and time in IT_TXTI is set.

  47 and 48 are flowcharts for explaining an example (reduced image display processing flow) of displaying thumbnails (reduced images or representative images) corresponding to entry points. FIG. 49 is a diagram for explaining an example of how thumbnails (reduced images or representative images) are displayed on the screen in the reduced image display processing of FIG.

<m1> A PG to be reproduced is determined, and an EPI corresponding to the PG is read. At this time, if there is no corresponding EPI, this process is terminated and only the title is displayed;
<m2> The display position is set to the left end (for example, upper left in FIG. 49).

<m3> Read first EPI data and open thumbnail file;
<m4> It is checked whether or not a reduced image is registered in the EP by checking whether there is an EP index number in the thumbnail file. If there is, move to <m7>.

<m5> Play the frame at the PTM location of REP_PIC in EPI, reduce the image to a specified size, and display it at the target location (in the above example, upper left in FIG. 49);
<m6> The reduced video is compressed to JPEG, the data is read, and is additionally recorded in the thumbnail file. At this time, the EP index number is also added and recorded, and the process proceeds to <m8>.

<m7> Read reduced image data and display it at the desired coordinates;
<m8> Check whether there is any other reduced image, and if so, read the next EP information, and if not, proceed to (sub).

<m9> Next, in the case of the fourth sheet, the display position is set to the lower left corner (new line on the display in FIG. 49), and the process proceeds to <m4>
<m10> If the 6th image has not been displayed, shift the display position one step to the right and move to <m4>.

<m11> Display page feed symbol;
<m12> Wait for the user to select an image, and if the page feed symbol is selected (page break in the display of FIG. 49), the next EP data is read and the process proceeds to <m3>;
<m13> The playback is set to start from the EP of the selected image, and this process is terminated.

  50 and 51 are flowcharts for explaining an example of the reproduction operation (overall reproduction operation flow) of the apparatus shown in FIG.

<n1> Check the disc and check if it is rewritable disc (R, RW, RAM). If it is not a rewritable disc, return to that effect and exit;
<n2> Read the file system of the disk and check if there is recorded data. If there is no recorded data, display “Not Recorded” and exit.

  <n3> The VMG file is read, and the program and cell to be played are determined (to be selected by the user). Here, when reproduction in the recording order is selected, reproduction is performed according to ORG_PGCI. When the reproduction for each program is performed (in the order specified by the user), the reproduction is performed according to the UD_PGC of the number corresponding to the program to be reproduced.

<n4> The value of APP_NAME is read out, and it is checked whether or not the broadcasting system can be supported. If the broadcasting system cannot be supported, the fact is displayed and the processing is terminated. (Or move to the next cell.)
<n5> ESOB / VOB to be reproduced is determined from cell information CI to be reproduced, and a file pointer (logical address) to start reproduction is determined from the reproduction start PTM. Further, each decoder unit is set according to the STI value to prepare for reproduction. Also, the APS is set for the video decoder from the CCI in the first packet group header. That is, APS ON / OFF, APS type, etc. are set, and CGMSA is set in the video decoder by digital copy control.

  Further, when there is a digital output (IEEE 1394, Internet, etc.), “0 = scramble on or output prohibited, 1 = output as it is” is set in the output IC according to the value of EPN. If ICT is 0, the resolution of the image is limited, and high definition HD is converted to standard resolution SD. If ICT is 1, the resolution is set as the output IC. At this time, if the frame to start playback is not an I picture, the immediately preceding I picture is read out, decoding is started from there, display is started when the target frame is reached, and normal playback is started.

<n6> Perform processing at the start of playback;
<n7> Perform initial settings for each decoder;
<n8> Cell playback processing (described later) is performed to check whether playback is complete. If it is completed, an error check is performed. If there is an error, a message to that effect is displayed. If there is no error, playback is performed. End processing is performed, and this operation is finished.

<n9> The next cell is determined from PGCI, and it is checked whether or not the decoder setting has been changed. If the decoder has been changed, the change attribute is set in the decoder so that the decoder setting is changed to the next sequence end code. Set
<n10> It is checked whether or not the playback is finished. If the playback is not finished, the process proceeds to <n6>.

  52 and 53 are flowcharts for explaining an example of the process (ST220) at the time of cell reproduction in FIG.

  <p1> The cell start file pointer FP (logical block number) and end file pointer FP are determined from the contents of the map information (such as ES_MAPI 132536 in FIG. 8). Furthermore, the start ESOBU_ENT and the end ESOBU_ENT are determined from the cell start time / end time in the cell information CI in FIG. Then, the data length of the entries up to the target ESOBU_ENT is accumulated in ADR_OFS to obtain the start address (logical block LB = file pointer FP) and end address. The remaining 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.

  <p2> When the ID to be referred to is Oxffff, there are two types of multi-angle display methods: simultaneous display of a small screen and display of a preset group. In the former case, all video PIDs and main audio PIDs are set in the decoder, and are set in the decoder so as to be in the small-screen simultaneous display mode. In the latter case, the group PID set in the cell information CI is set in the decoder. If the CI is not set, a default PID in ESOBI is set.

  <p3> When the ID to be referenced = PID, the group to which the ES to be referenced belongs is specified from the component group descriptor, each PID to be reproduced is determined, and set in the decoder. When the ID to be referred to is a group ID, the PID in the group is specified from the component group descriptor, each PID to be reproduced is determined, and set in the decoder.

<p4> Set to decode within the decoder part;
<p5> Read processing during playback is executed, and the read address and read size are determined from the start file pointer.

  <p6> The read unit size to be read is compared with the remaining cell length. If the remaining cell length is large, a value obtained by subtracting the read unit size to be read from the remaining cell length is set to the remaining cell length. If it is smaller, the read length is set to the remaining cell length, and the remaining cell length is set to 0.

  <p7> Set the read length to the length of the read unit, and set the read address, read length, and read command to the drive unit.

<p8> Wait for 1 ESOBU to accumulate. If it accumulates, move to <p9>;
<p9> Read data in the buffer RAM, perform CCI check, and transfer to the decoder.

  <p10> Inside the decoder unit, the separation unit receives the read packet group data and packetizes it. Then, according to the stream ID and substream ID, video packet data (MPEG video data) is transferred to the video decoding unit, audio packet data is transferred to the audio decoding unit, and sub-picture packet data is transferred to the SP decoding unit. The TS transfer unit converts the transferred data into an element stream, and then sends the data to each decoder via an internal bus to perform decoding processing.

  <p11> During playback, the content of the STC is displayed as the playback time. However, if the STB unit can display the playback time based on the PTS in the video data, it is used.

<p12> Check if the transfer is complete, and if the transfer does not start, go to <p5>;
<p13> The value obtained by adding the read FP and the read length set in <p5> is substituted into the read FP.

<p14> Check whether the transfer is completed. If the transfer is completed, check the remaining cell length. If it is not “00”, proceed to <p2>. If it is “00”, perform this process. To exit;
<p15> If the transfer has not been completed, check the key input, and if special playback is to be performed, set the direction. Then, the read FP is calculated using the map information MAPI (ES_MAPI in FIG. 8), the read process at the time of special reproduction is performed, and this process ends. If not, move to <p8>.

  The special reproduction purpose FP is obtained from the MAPI so as to skip a certain time. Alternatively, it is possible to obtain a FP by skipping a certain number of ESOBUs instead of a certain time. At this time, when the end of the cell is reached, the next cell information is read by PGCI (FIG. 15), the ESOB number and MAPI used by the cell are selected, and the read FP is similarly obtained. If there are no more cells, the process ends there.

  FIG. 54 is a flowchart for explaining an example of the buffer decoder transfer process (ST2217) of FIG.

<q1> The number of packet groups in the buffer RAM is checked. If there is no one packet group, this process is terminated. If there is more than one, set to process the first packet group;
<q2> Read the target packet group from the buffer RAM. The head of the pack group is detected by the pack group length and Sync_Pattern (151 in FIG. 24).

<q3> The CCI in the packet group is read, the ES corresponding to the ES to be reproduced has a CCI setting, and it is checked whether it has changed from the previous time. If there is no change, the process proceeds to <q8>;
<q4> Analog protection (for example, macrovision system) is set in the video decoder according to the value of APS, and when this analog protection is ON, the protection type is set.

<q5> Copy permission / copy prohibition is set in CGMSA by digital copy control. In addition, there is a one-time copy permission. However, in the case of digital broadcasting, since the one-time copy permission is changed to the copy-prohibited at the time of recording, the one-time copy permission is no longer in the status;
<q6> Check EPN, and in case of protection, set digital digital output (IEEE 1394 or Internet) to be scrambled for output or prohibit output. If it is not protected, it is output as it is.

<q7> When ICT is checked and the image output is restricted, the resolution of the analog HD output (D terminal or color difference output) is down-converted from HD to SD and output. If it is not a limit, output as is;
<q8> The DCI in the packet group is read, and the ES corresponding to the ES to be reproduced has the DCI setting, and it is checked whether it has changed from the previous time. If there is no change, the process proceeds to <q10>.

<q9> Set aspect information to video decoder according to aspect information;
<q10> Set to transfer one packet group to the decoder unit.

<q11> Wait until the transfer is completed, check whether the pack group remains in the buffer RAM, and if not, end this processing;
<q12> Set to process the next packet group and move to <q2>;
As described above, fine control operation corresponding to digital broadcasting can be realized.

  FIG. 55 is a diagram for explaining a data structure example of a program map table (PMT) that can be used in the apparatus of FIG. In this PMT, various streams can be identified by an 8-bit stream type 3421. For example, if the stream type is “0x01”, it indicates that it is an MPEG1 video stream, and if the stream type is “0x02”, it indicates that it is an MPEG2 video stream (click here for high-definition). “0x03” indicates that the stream is MPEG1 audio, and “0x04” indicates that the stream is MPEG2 audio (AAC multi-channel audio is here).

  FIG. 56 is a diagram for explaining an example of the contents of a digital copy control descriptor that can be used in the apparatus of FIG. 30, and an example of a copy control process using this descriptor. In this descriptor (ST3000), the “descriptor tag” field is “0xC1”, for example, and the “descriptor length” field indicates the description length. In the “digital recording control” field, “copy generation control data” is described. In the “maximum bit rate flag” field, “whether or not to describe the maximum transfer rate of the service” is described. The flag when not described is, for example, “0”, and the flag when described is, for example, “1”. When “0” is described in the “component control flag” field, for example, the entire program is defined (in the case of PMT). When “1” is described in this field, other states are described. In the “copy control type” field, “copy control data” is described (see FIG. 26).

  When each field of the descriptor is described (step ST3000), the copy control type is checked (step ST3002). When the copy control type is 01 or 11, the analog output control data is determined according to the APS control data (step ST3004). Copy control when the copy control type is other than 01 or 11 is reserved (step ST3006).

  Subsequently, the Maxim bit rate flag is checked (step ST3008). When this flag is 1, the maximum transmission rate is determined according to the maximum bit rate (step ST3010). Subsequently, the component control flag is checked (step ST3012). When this flag is 1, the component control length n is determined according to the component control length (step ST3014).

  Subsequently, fields of a component tag, a digital recording control, a maximum bit rate flag, and a copy control flag are described (step ST3020). Thereafter, steps ST3022 to ST3030 similar to steps ST3002 to ST3010 are continuously executed for the value n determined in step ST3014. If the component control flag is not 1 in step ST3012, the processes in steps ST3014 to ST3030 are skipped, and the process in FIG. 56 ends.

  FIG. 57 is a diagram for explaining an example of how digital copy control is applied to video data. Video data copy control can be broadly divided into three types: “unrestricted copy allowed (copy free)”, “copy prohibited (copy never or no more copy)”, and “only one generation copy allowed (copy once)”. .

  In the case of “unrestricted copy allowed”, the analog copy control is “unrestricted copy permitted”, the digital recording control is “01”, the control type is “00”, and the APS control data is “Don't care”, for example. (Ignore) ”.

  In the case of “copy prohibited”, (1) analog copy control is “copy prohibited (digital copy is not possible, but analog copy is possible without a macrovision (R) type copy prevention pulse)”. 01 ”, the control type is“ 11 ”, for example, and the APS control data is“ 00 ”, for example.

  Alternatively, in the case of “copy prohibited”, (2) analog copy control is “copy prohibited (analog copy and digital copy are not allowed)”, digital recording control is “01”, for example, control type is “11”, and APS The control data is, for example, other than 00.

  In the case of “Copying of only one generation”, (3) Analog copy control is “Copying of only one generation is possible (however, analog copy is possible without copy prevention pulse)”, and digital recording control is “01”, for example. The type is “10”, for example, and the APS control data is “00”, for example.

  Alternatively, in the case of “only one generation can be copied”, (4) analog copy control is “only one generation can be copied (analog copy and digital copy are not possible for subsequent generation copies)”, and the digital recording control is, for example, “01 ", The control type is, for example," 10 ", and the APS control data is, for example, 00.

  FIG. 58 is a diagram for explaining an example of how digital copy control is applied to audio data. There are three types of audio data copy control: “Unrestricted copy allowed (copy free)”, “Only one generation can be copied (copy once)”, and “Copy prohibited (copy never or no more copy)”. .

  In the case of “unrestricted copy permitted”, the digital recording control is “01/11”, for example, and the control type is “00”, for example. In the case of “only one generation can be copied”, the digital recording control is “01/11”, for example, and the control type is “10”, for example. In the case of “copy prohibited”, the digital recording control is “01/11”, for example, and the control type is “11”, for example.

  FIG. 59 is a diagram for explaining an example of the contents of a content usage descriptor that can be used in the apparatus of FIG. In this descriptor, the “descriptor tag” field is “0xDE”, for example, and the “descriptor length” field indicates the description length. “Resolution limit bit” is described in the “image construction token (ICT in FIG. 26) field. When this bit is“ 0 ”, video output is limited (for example, high definition HD video is limited to standard resolution SD). When this bit is “1”, the video is output without restriction, and the “Retention Mode” field describes “Temporary Accumulation Control Bit.” When this bit is “0” Video can be temporarily stored, and temporary storage is prohibited when this bit is “1.” “Retention state” field describes “temporary storage allowable time.” The content of this field is “7. When "", temporary storage of 1.5 hours is permitted, when "6", temporary storage of 3 hours is permitted, when "5", temporary storage of 6 hours is permitted, and when "4" Is 1 Temporary accumulation of time is permitted. When “3”, temporary accumulation of one day is permitted. When “2”, temporary accumulation of two days is permitted. When “1”, temporary accumulation of one week is permitted. Permitted to be stored indefinitely when it is “0” “Output protection bit” is described in the “Encryption mode” field, and when this bit is “0”, high-speed digital I / F output Is protected, and when this bit is “1”, there is no protection (that is, digital output is free).

  FIG. 60 is a diagram for explaining an example of the data structure of an event information table (EIT) that can be used in the apparatus of FIG. This EIT has a recording field of a descriptor 3426a, and a descriptor such as “component group descriptor” can be stored therein.

  FIG. 61 is a diagram for explaining an example of the contents of the extended event descriptor that can be used in the apparatus of FIG. In this descriptor, the “descriptor tag” field is set to “0x4e”, for example, and the descriptor length is indicated in the “descriptor length” field. Descriptor numbers (0 to n) are described in the “descriptor number” field. In the “last descriptor number” field, the last descriptor number (0 to n) is described. In the “0x4dISO — 639_LANGUAGE_CODE” field, for example, a broadcasting system “ARIB: jpn” adopted in Japan is described. In the “length of items” field, for example, “number of items (number of bytes of subsequent items)” is described.

  When the number of items is 1 or more, the following contents are repeated for the number of items. That is, after the item name length (number of bytes of the item name) in the “item description length” field, the item name (8-bit character code) is repeated for the item name length, and the item description length (item description) in the “item length” field The item description (8-bit character code) is repeated for the item name length, and the extended description length (byte length of the extended description) in the “Text length” field is followed by the extended description (8-bit character code). Is repeated for the length of the item name. A set of fields of “item description length”, “item length”, and “Text length” is repeated for the number of items.

FIG. 62 is a diagram for explaining how a target packet is captured from this PTM when a playback time (PTM) is given. A method of obtaining a target packet corresponding to this PTM from a given playback time PTM is as follows. That is,
(1) The ESOBU number to which the PTM belongs is obtained from the given PTM by using the time map TMAP which is management information (by adding the ESOBU playback time);
(2) From the obtained ESOBU number, use TMAP (by adding the ESOBU size) to obtain the packet group number to which the start packet of the ESOBU belongs; and
(3) The start packet of the ESOBU is specified by the ESOBU start packet number in the time map.

  FIG. 63 is a diagram for explaining another example (modified example of FIG. 4) of how one piece of management information (RTR_VMG) recorded in the AV data management information recording area 130 is configured. Here, there is no extended entry point information (EXEPIT) 1361 in FIG. 4, and instead, the extended entry point information is stored in the extended file HR_EXEP. It is given to DAT. In this case, the data structure as in Example 1 in FIG. 18 is adopted for the cell entry point information C_EPI in the PGCI.

  FIG. 64 is a diagram for explaining another example (modified example of FIG. 15) of how the components of the program chain information (ORG_PGC information or UD_PGC information) are configured. Here, entry point information (EPI) 13348X is adopted instead of the entry point information table (C_EPIT) 13348 of FIG. When C_EPIT in FIG. 15 includes only one C_EPI, the cell information 1334X in FIG. 64 is substantially the same as the cell information 1334 in FIG.

  FIG. 65 shows another example of how the contents of the merchant information (manufacturer information MNFI) included in the management information recorded in the management information recording area 130 of FIG. 4 or FIG. 14 is configured (FIG. 23). It is a figure explaining a modification. In FIG. 65, the MNFI data 13633X included in the merchant information (MNFI) 1363X includes the number of reduced images (number of thumbnails) 136331X, the corresponding cell number 136332X, the corresponding entry point number 136333X, When the thumbnail is JPEG compressed, the data length (size) 136334X and the JPEG data main body 136335X of the thumbnail are included.

  FIG. 66 is a flowchart (recording flow without entry point addition processing) for explaining another example of the recording operation of the apparatus of FIG. 30 (modified example of FIG. 35).

<r7> Create VSTI and ASTI from PTM (step ST120);
If a certain amount of data in the <r8> buffer has accumulated (for 1 CDA), ECC processing is performed through D-PRO and recorded on the disk (step ST130).

<r9> During recording, the segmentation information is saved in the work RAM of the MPU unit periodically (before the buffer RAM of the formatter unit becomes full). The segmentation information here is ESOBU segmentation information, such as ESOBU start address, SOBU pack length, I-Pic end address, ESOBU arrival time (ATS), etc .;
<r10> Check the remaining amount, and if the remaining amount is less than a certain level, the remaining capacity is reduced.

<r11> Check if the recording is finished (whether the recording end key has been entered or if there is no remaining capacity). At the end, the remaining segmentation information is taken from the formatter and added to the work RAM. Are recorded in management data (VMGI), and the remaining information is recorded in the file system;
If it is not <r12> end, the process proceeds to <r7>, and the data capture and playback are continued.

  FIG. 67 is a flowchart (pre-recording process flow) for explaining another example of the process before starting recording on the information storage medium (optical disk) (modified example of FIG. 36).

<s1> Search for a DVD_HDVR directory (a directory in which a new VR is to be entered). If there is no directory, the directory is created.
<s2> Check if it is recorded in the directory. If it is recorded, read VMGI, which is the management information, into the work, and support this equipment from the recorded broadcasting system (APP_NAME). If it is not supported, display that effect and exit.

<s3> If there is no recorded data, create VMGI in the work;
<s4> Check the broadcasting system of data to be recorded. (In the case of an internal tuner, the default method is used in the device. In the case of an external digital input, the Registration_Descriptor value sent from the digital input is examined to determine the recording method.)
<s5> If it is different from the broadcasting system in the disc, this is displayed and the process ends.

<s6> Judge whether the broadcasting format of the data to be recorded is a format supported by this device, and if not, display that fact and exit;
<s7> The broadcast method is set in the APP_NAME of the VMGI built in the work, and the process proceeds to the next process.

  FIG. 68 is a flowchart (program setting process flow) for explaining another example of the program chain (PGC) creation process (modified example of FIG. 43).

<t1> Check if it is the first recording on the disc. If it is not the first, create ORG_PGC, and if not, add it after the ORG_PGC;
<t2> Erase permission is set to PG_TY: 0, and the number of cells is set to Cell_Ns.

  <t3> In the case of ARIB, when the language_code of the short format event descriptor in the EIT is “jpn”, CHR of VMG_MAT is set to 0x12, the second area of PRM_TXTI is set to EVENT_NAME, and the representative image is set to REP_PICTI. Set the information.

  <t4> Set the manufacturer ID of this device in LAST_MNF_ID. This value is used to set the manufacturer ID of the changed device when there is a change in PGI, CI, or VOB, and is set to identify the manufacturer that was last edited or recorded. This makes it easier to handle changes made by different manufacturers.

  <t5> An absolute number of PG is set in PG_INDEX, and when referring from other application software, it is possible to refer in units of PG. Further, this PG update date / time information is recorded. At this time, if there is an MNFI or IT_TXT supported by this device (matching manufacturer code), the update date / time information of the corresponding data is also set.

<t6> Information unique to each manufacturer is set in MNFI;
<t7> Set the information indicating that the cell type is a streamer;
<t8> A reference ESOB number is set, a representative (video) PID or Component_Group_Id is set as an ID to be played, and an EPI number, a playback start PTM, an end PTM, and an EP are set.

  FIG. 69 is a flowchart (item text setting process flow) for explaining another example (modified example of FIG. 44) of the item text (IT_TXT) creation process in the program update date and time setting process (ST1700X) shown in FIG.

  IT_TXT is text information that can be freely entered by the device, and it is conceivable that information from the user or text information in the broadcast is entered. Here, it is considered that when there is an extended format event descriptor in the EIT, the text information is put in IT_TXT. Therefore, the IT_TXT setting process is as follows.

  <u1> It is checked whether IT_TXT information exists in the disc. If it does not exist, TXTDTI is set. If it exists, IT_TXT information is added.

  <u2> Set the PG number of ORG_PGC to which this text belongs, confirm that the language code is “JPN” (if not, end this processing), and save this information as TEXT_DATA . Here is a more detailed description of the program.

  FIG. 70 illustrates another example of the process of setting a thumbnail (reduced image or representative image) in the vendor information MNFI corresponding to this entry point when an entry point has already been added (modified example of FIG. 46). It is a flowchart (reduced image setting processing flow). An embodiment in the case where reduced image data corresponding to EP is entered in MNFI for use in menus and the like will be described below.

<v1> Check whether the MNFI information exists in the disk. If it does not exist, set the MNFI, and if it exists, set to add the MNFI information;
<v2> Enter the manufacturer ID of this equipment in the MNFI manufacturer ID. This ID is a default value recorded in the ROM 80B in the MPU 80 of FIG.

<v3> Set MNFI recording time;
<v4> Search for cells in the program, check all entry points EP, and take out the number of EPs and the playback location (actual playback position of the object) where the EP is placed.

<v5> Extract the information of the first EP;
<v6> Plays the frame specified by EP and puts it into the frame memory. At this time, if the frame with the EP is not an I picture (in the case of a B or P picture), the frame is reproduced from the previous I picture and decoded to the target frame to obtain frame data.

<v7> Data in the frame memory is reduced by the decoding unit and JPEG compressed;
<v8> Read the reduced data from the decoding unit, and store it in MNFI_DATA (13633 in FIG. 23 or 13633X in FIG. 65) together with the corresponding cell number and entry point number;
<v9> It is determined whether or not there is an EP that has not been reduced to an image. If there is an EP, information on the next EP is extracted, and the process proceeds to <v6>.

  FIG. 71 is a flowchart (reduced image display processing flow) for explaining another example (modified example of FIG. 47) of displaying the thumbnail (reduced image or representative image) set in the trader information MNFI. Processing when displaying a reduced image with a menu key or the like is as follows.

  <w1> A PG to be reproduced is determined, and the MNFI corresponding to the PG is read. At this time, if there is no corresponding MNFI, this process is terminated and only the title is displayed.

<w2> Read the first EP data;
<w3> Set the display position to the left end.

<w4> Read reduced image data and display it at the desired coordinates;
<w5> Check if there are other reduced images;
If there is <w6>, the next EP information is read.

<w7> Next, for the 4th sheet, set the display position to the lower left corner (line feed) and move to <w4>;
<w8> If the 6th image has not been displayed, shift the display position one step to the left and move to <w4>;
<w9> Display page feed symbol.

<w10> Waits for the user to select an image, and when the page feed symbol is selected (page break), reads the next EP data and proceeds to <w3>;
<w11> The playback is set to start from the EP of the selected image, and this process ends.

FIG. 72 is a flowchart (MNFI reliability check processing flow) for explaining an example of processing for checking the reliability of the vendor information MNFI of FIG. Here, the reliability of the MNFI and IT_TXT is checked when the disc is inserted, and if there is a mismatch, the MNFI or IT_TXT is deleted. (The program editing date and time is set to PGI, IT_TXT, and MNFI when the program is edited. Therefore, if the recorder does not support IT_TXT and MNFI, inconsistency occurs.)
<x1> First, ORG_PGC in the disk is read.

<x2> Read the information of each PG;
<x3> Reads the update date / time information of the PGI, searches for IT_TXT corresponding to the PG, and if there is, reads the update date / time information;
<x4> Find the MNFI corresponding to the PG, and if there is, read the update date / time information.

<x5> The update date / time is compared, and if the date / time information does not match the PGI date / time information, the data (IT_TXT or MNFI) is deleted. (The fact that the update date and time do not match means that the data of that part has been edited by another company's device, and therefore it is unclear where the data is related. For this reason, the data is deleted. )
<x6> Check whether there is a next PG, and if so, set it to the next PG and proceed to <x3>.

<x7> End this process;
As described above, fine control operation corresponding to digital broadcasting can be realized.

<Summary of Embodiment>
(01) The entry point (C_EPI in FIG. 18) also has a pointer to the thumbnail image (TBN_PT, EP_REP_PIC), a pointer to the item text (TXT_NUM), an entry point type (EP_TY in FIG. 19), and the like.

  In other words, various information can be added to the entry point, and it is possible to immediately determine what information is included by EP_TY. Furthermore, since the position of the representative image can be set and held independently of the entry point itself, this representative image can be used for a chapter thumbnail or the like.

  (02) The same search information (information such as the program index number and the program update date and time in FIGS. 15 and 23) is included in both the essential information (PGI) and the extended information (EP_EPIT; option) in the management information (VMG, ESMG). Give it.

  That is, information such as the program index number and the program update date and time that are the same as the essential information (PGI) is stored in the optional extension information (EP_EPIT). When the information related to the program (PG) is changed, the essential information (PGI) and the program index number in the corresponding extension information, the program update date and time, etc. are updated simultaneously (if only the extension information is changed) This simultaneous update is unnecessary).

  If comprised in this way, the extended information regarding a program, a play list, an entry point, etc. can be added and held at any time only as needed. In particular, when the recording content of the disc of the present application is changed in a model (recorder) that does not have the function of processing the extended information, it is possible to detect whether or not the recording information is inconsistent (see FIG. 72). ST4014X and the like). In addition, since extended information can be added later, the amount of essential information in the management information can be minimized, and management information (various extended information such as text information) can be easily added later. Yes (for example, the processing of ST1806 in FIG. 44).

  (03) Display control information (CCI) and / or copy control information (CCI) can be handled for each packet identifier (PID) in packet group units (not packet units) (the packet group header in FIG. DCI and CCI can be included). In the present embodiment, a maximum of 32 PIDs can be supported. When the attribute changes in the middle of a pack group, the pack group is terminated with dummy data so that the boundary position of each pack group is aligned (see FIG. 40).

  Since DCI, CCI, etc. are managed in pack group units (units larger than packet units), the amount of information in the header (packet group header in FIG. 24) can be reduced (compared to the packet unit).

  (04) The default PID of the stream object (SOB) is described in its management information (SOBI in FIGS. 8 to 11). In this way, even if no special PID is described, there is a default PID, so that the target PID is known. Therefore, it is not necessary to describe the PID for each corresponding portion.

  Note that the present invention is not limited to the above-described embodiments as they are, and can be embodied by variously modifying the constituent elements without departing from the scope of the invention in the implementation stage.

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

The figure explaining the 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 a part (RTR_VMGI) of one piece of management information (RTR_VMG) recorded in the AV data management information recording area 130 is configured. The figure explaining an example of how the other part (ESFIT) of one management information (RTR_VMG) is comprised in the data structure which concerns on one embodiment of this invention. The figure explaining an example of how the contents of ESFITI_GI and ESFI are comprised among each component of the management information (ESFIT) shown in FIG. The figure explaining an example of how the contents of ESOBI_VSTI and ESOBI_ASTI are comprised among each component of the management information (ESFIT) shown in FIG. The figure explaining an example of how the content of ESFI_GI and ESOBI is comprised among the management information shown in FIG. The figure explaining an example of how the content of stream object general information (ESOB_GI) is comprised among the management information shown in FIG. Of the management information shown in FIG. 8, how the contents of ESOB elementary stream information, time map general information (TMAP_GI), elementary stream map information (ES_MAPI), and ES group information are configured. The figure explaining an example. The figure explaining an example of how the content of ES_MAP_GI shown in FIG. 10 is comprised. The figure explaining an example of how the content of ESOBU_ENT shown in FIG. 10 is comprised. FIG. 3 is a diagram for explaining an example of what the ESOBU shown in FIG. 2 has depending on the presence or absence of video data and audio data. How is PGC information (original PGC information ORG_PGCI / user definition information table information UDPGCITI) included in another one of the management information recorded in the AV data management information recording area 130 (stream data management information RTR_ESMG)? FIG. The figure explaining an example of how the content of each component of the program chain information (ORG_PGC information or UD_PGC information) shown in FIG. 14 is comprised. The figure explaining an example of how the content of the text data manager (TXTD_MG) contained in the management information recorded on the management information recording area 130 of FIG. 4 or FIG. 14 is comprised. The figure explaining an example of how the contents of the cell entry point information table (C_EPIT) included in the cell information of FIG. 15 are configured. The figure explaining an example (EPI of Example 1) how the content of the cell entry point information (C_EPI) of FIG. 17 is comprised. The figure explaining an example of how the contents of the entry point type (EP_TT) included in C_EPI in FIG. 18 are configured. FIG. 18 is a diagram for explaining an example (EPI in Example 2) of how the contents of the cell entry point information (C_EPI) in FIG. 17 are configured. An example of what file the extended entry point information table (EX_EPIT) included in the management information recorded in the management information recording area 130 of FIG. 4 or 14 is managed (or how it is configured) FIG. FIG. 22 is a diagram illustrating an example of how the contents of the extended entry point information table (EX_EPIT) in FIG. 21 are configured (when the EPI of Example 2 is used). FIG. 15 is a diagram for explaining an example of how the contents of vendor information (manufacturer information MNFI) included in the management information recorded in the management information recording area 130 of FIG. 4 or FIG. 14 is configured. The figure explaining an example of how the data unit (ESOBU) for stream objects shown in FIG. 1 or FIG. 2 is comprised. The figure explaining an example of how the arrival time (ATS), validity information (DCI_CCI_SS), and display control information (DCI) of the packet included in the packet group header shown in FIG. 24 are configured. FIG. 25 is a diagram for explaining an example of how copy generation management information (or copy control information CCI) included in the packet group header shown in FIG. 24 is configured. An example of how the packet arrival time increment (IAPAT) and the PCR position information (pack number or PCR_LB number number, etc.) included after the packet group header are configured in the packet group shown in FIG. Figure. In the file structure of FIG. 3, an example of the internal structure of a thumbnail (or representative image) object file (HR_THNL.DAT; if the EPI of Example 2 is used, a file different from the VMG file) managed in the DVD_HDVR file Illustration to explain. FIG. 4 is a diagram for explaining an example of the internal structure of an object file (HR_TEXT.DAT; additional text file) of text data managed in a DVD_HDVR file in the file structure of FIG. 3. 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 flowchart figure explaining an example of the whole operation | movement of the apparatus of FIG. 30 (whole operation | movement process flow). FIG. 31 is a flowchart for explaining an example of interrupt processing in the operation of the apparatus of FIG. 30 (interrupt processing flow). FIG. 32 is a flowchart (edit operation process flow) for explaining an example of the edit process (ST28) shown in FIG. 31; The flowchart figure explaining an example (the 1) of video recording operation | movement of the apparatus of FIG. FIG. 31 is a flowchart for explaining an example (part 2) of the recording operation of the apparatus in FIG. 30 (recording flow with entry point addition processing). The flowchart figure explaining an example of the process before recording starts on the disk-shaped information storage medium (for example, optical disk using a blue laser) shown in FIG. 1 (recording pre-processing process flow). FIG. 36 is a flowchart (STI setting process flow) for explaining an example of the stream information (VSTI and ASTI) creation process (ST120) shown in FIG. FIG. 36 is a flowchart for explaining an example of a buffer fetch process (ST130) shown in FIG. 35 (buffer fetch process flow). FIG. 39 is a flowchart for explaining an example of DCI and CCI setting processing (ST1311) shown in FIG. The figure which illustrates the data structure of the pack group in the process (pack group align process) of step ST13123 of FIG. FIG. 35 is a flowchart for explaining an example of stream file information (SFI or ESFI) creation processing in the recording end processing (ST150) shown in FIG. 34 (stream file information creation processing flow with ESOB structure setting processing and editing date setting processing). FIG. 42 is a flowchart for explaining an example of an ESOB structure setting process (ST1522) shown in FIG. FIG. 35 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 (ST150) shown in FIG. FIG. 44 is a flowchart (item text setting process flow) for explaining an example of an item text (IT_TXT) creation process in the program update date and time setting process (ST1704) shown in FIG. The flowchart figure explaining an example of the entry point addition process (ST147) shown in FIG. 34 (EP addition process flow). FIG. 45 is a flowchart for explaining an example of processing for setting a thumbnail (reduced image or representative image) corresponding to the entry point after the entry point is added by the processing of FIG. 45 (when the entry point has already been added). (Reduced image setting process flow). The flowchart figure explaining an example of the process which displays the thumbnail (reduced image or representative image) corresponding to an entry point (reduced image display processing flow). The flowchart figure explaining an example of the process which registers the thumbnail (reduced image or representative image) corresponding to an entry point (reduced image registration processing flow). FIG. 48 is a diagram for explaining an example of how thumbnails (reduced images or representative images) are displayed on the screen in the reduced image display processing of FIG. 47; The flowchart figure explaining an example (the 1) of reproduction | regeneration operation | movement of the apparatus of FIG. The flowchart figure explaining an example (the 2) of reproduction | regeneration operation | movement of the apparatus of FIG. 30 (whole reproduction | regeneration operation | movement flow). The flowchart figure explaining an example (the 1) of the process (ST220) at the time of the cell reproduction | regeneration of FIG. The flowchart figure explaining an example (the 2) of the process (ST220) at the time of the cell reproduction | regeneration of FIG. FIG. 54 is a flowchart for explaining an example of buffer decoder transfer processing (ST2217) in FIG. 53. The figure explaining the data structure example of the program map table (PMT) which can be used with the apparatus of FIG. The figure explaining the example of the content of the digital copy control descriptor which can be used with the apparatus of FIG. 30, and an example of the copy control process using this descriptor. The figure explaining an example of how digital copy control is operated with respect to video data. The figure explaining an example of how digital copy control is operated with respect to audio data. The figure explaining an example of the content of the content utilization descriptor which can be used with the apparatus of FIG. The figure explaining the example of a data structure of the event information table (EIT) which can be used with the apparatus of FIG. The figure explaining an example of the content of the extended event descriptor which can be used with the apparatus of FIG. The figure explaining how a target packet is caught from this PTM when reproduction time (PTM) is given. The figure explaining the other example (modification of FIG. 4) how one of the management information (RTR_VMG) recorded on the AV data management information recording area 130 is configured. The figure explaining the other example (modification of FIG. 15) of how the content of each component of program chain information (ORG_PGC information or UD_PGC information) is comprised. Another example of how the contents of the vendor information (manufacturer information MNFI) included in the management information recorded in the management information recording area 130 of FIG. 4 or FIG. 14 is configured (modified example of FIG. 23). Illustration to explain. The flowchart figure explaining the other example (modified example of FIG. 35) of the video recording operation | movement of the apparatus of FIG. 30 (Recording flow without an entry point addition process). FIG. 37 is a flowchart (recording pre-processing flow) for explaining another example of the process before starting recording on the information storage medium (optical disc) (modified example of FIG. 36). The flowchart figure (program setting process flow) explaining the other example (modified example of FIG. 43) of a program chain (PGC) creation process. FIG. 69 is a flowchart (item text setting processing flow) for explaining another example (modified example of FIG. 44) of item text (IT_TXT) creation processing in the program update date and time setting processing (ST1700X) shown in FIG. Flowchart diagram for explaining another example (variation of FIG. 46) of setting a thumbnail (reduced image or representative image) in the merchant information MNFI corresponding to this entry point when an entry point has already been added Image setting process flow). FIG. 48 is a flowchart (reduced image display processing flow) for explaining another example (modified example of FIG. 47) of displaying thumbnails (reduced images or representative images) set in the vendor information MNFI. FIG. 66 is a flowchart for explaining an example of processing for checking the reliability of the vendor information MNFI in FIG. 65 (MNFI reliability check processing flow).

Explanation of symbols

  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 (RTR_VMG / RTR-ESMG); 131 ... Extended stream object 132: Extended stream object (ESOB); 134: Extended stream object unit (ESOBU); 140 ... Packet group; 160 ... DVD transport stream packet recording area; 161 ... Packet group header; 162 ... MPEG transformer Port stream (MPEG-TS); 163 ... Incremental application packet arrival time (IAPAT); 10 ... Playback information management layer; 11 ... Program chain (P C ...; Program (PG); 13 ... Cell; 20 ... Stream object management information layer; 21 ... Extended stream object information (ESOBI); 22 ... Extended stream object unit information (ESOBUI; global information); 24 ... Video object information (VOBI); 25 ... Video object unit entry (VOBUE); 30 ... Stream object (SOB) layer; 35 ... Video object (VOB) layer; 36 ... Video object (VOB) 37 ... Video object unit (VOBU); 38 ... Pack; 51 ... Disc drive unit (optical disc drive using a laser having a wavelength of, for example, 650 nm to 405 nm); 59 ... Decoder unit; 4 ... Digital interface (IEEE 1394 I / F, etc.); 79 ... Encoder part; 80 ... Main MPU part (control part); 83 ... Set top box part (satellite digital tuner); 89 ... Terrestrial digital tuner; Medium (such as a hard disk drive).

Claims (11)

In an information medium having a data area for recording AV information including moving picture information of an MPEG transport stream, and a management area for storing management information for managing the AV information recorded in the data area,
An information medium configured so that the management information includes information indicating a time when a part of the AV information is recorded and information indicating a recording period of the part of the AV information. A part of the recorded AV information is configured to be managed by one or more files,
The management information is configured to include format identifier information, network identifier information, transport stream identifier information, and service identifier information regarding the MPEG transport stream corresponding to a part of the AV information,
2. The information medium according to claim 1, wherein the format identifier information, network identifier information, transport stream identifier information, and service identifier information can be used in file management of a part of the AV information. In an information medium having a data area for recording AV information including moving picture information of an MPEG transport stream, and a management area for storing management information for managing the AV information recorded in the data area,
The management information includes playlist information for managing the AV information, and the playlist information includes text information and vendor information. In an information medium having a data area for recording AV information including moving picture information of an MPEG transport stream, and a management area for storing management information for managing the AV information recorded in the data area,
An information medium configured such that the management information includes pointer information designating a thumbnail as information for managing a thumbnail that is index image information of the recorded AV information. In an information medium having a data area for recording AV information including moving picture information of an MPEG transport stream, and a management area for storing management information for managing the AV information recorded in the data area,
An information medium configured so that the management information includes number information of the thumbnail and data length information of the thumbnail as information for managing a thumbnail which is a still image for indexing of the recorded AV information.   The information medium according to claim 5, wherein the management information includes pointer information designating the thumbnail.   The information medium according to any one of claims 4 to 6, wherein an object file corresponding to the thumbnail is managed in a file under a directory common to the object file corresponding to the AV information.   The recording method using the medium according to claim 1, wherein the AV information is recorded in the data area, and the management information is recorded in the management area.   8. A playback method using the medium according to claim 1, wherein the management information is played back from the management area, and the AV information is played back from the data area.   8. A recording apparatus using the medium according to claim 1, further comprising means for recording the AV information in the data area and means for recording the management information in the management area. Recording device.   8. A playback apparatus using the medium according to claim 1, comprising means for playing back the management information from the management area, and means for playing back the AV information from the data area. Playback device.

Images