JP2005310365A - Information storage medium of stream data, and its recording method, playback method, recording device and playback device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To attain an improvement regarding a stream information recording process. <P>SOLUTION: An information medium having a data area constituted so as to record the stream data and a management area constituted so as to record the management information regarding the above stream data is used for this improvement. In this case, the management information (SFIT/SFI/SOBI) is constituted so as to include the time information (PTSL) corresponding to a specific part of the stream data. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to an information storage medium for recording video data transmitted by digital broadcasting or the like or stream data transmitted with a packet structure, a data structure of management information relating to stream data recorded on the medium, and recording of the management information Method and playback method.

  In recent years, TV broadcasting has entered the era of digital broadcasting. Along with this, there has been a demand for an apparatus for storing digital TV broadcast digital data as it is regardless of the content, so-called streamer.

  An MPEG transport stream is employed in the currently broadcast digital TV broadcast. In the future, MPEG transport streams will be used as standard in the field of digital broadcasting using moving images.

  In this digital broadcasting, the content to be broadcast (mainly video information) is time-divided into a set of data of a predetermined size (for example, 188 bytes) called a transport packet, and broadcast data is transmitted for each transport packet. The

  As a streamer for recording this digital broadcast data, there are digital VCRs for home use such as D-VHS (digital VHS). In the streamer using this D-VHS, the broadcast bit stream is recorded on the tape as it is. Therefore, a plurality of programs are multiplexed and recorded on the video tape.

  At the time of reproduction, all data is sent as it is from the VCR to a set top box (receiver of digital TV: hereinafter abbreviated as STB) even when reproducing from the beginning or from the middle. In this STB, a desired program is selected from the transmitted data by a user operation or the like. The selected program information is transferred from the STB to a digital TV receiver or the like and played back (playback of video + audio etc.).

  In this D-VHS streamer, since a tape is used as a recording medium, quick random access cannot be realized, and it is difficult to quickly jump to a desired position of a desired program for reproduction.

  A streamliner using a large capacity disk medium such as a DVD-RAM can be considered as a promising candidate that can eliminate the drawbacks of such tapes (difficult random access). In that case, when random access and special reproduction are considered, it is inevitably necessary to record management data together with broadcast data.

  Here, between a STB which is a receiver of a digital TV and a streamer using a large-capacity disk medium such as a DVD-RAM, or a streamer using this large-capacity disk medium and another streamer using D-VHS or the like. A digital interface conforming to IEEE 1394 or the like can be used for data transfer to and from.

  In this digital interface, video data / stream data is transferred for each transport packet received by digital broadcasting.

  For example, in a digital interface using IEEE 1394, in order to guarantee real-time transfer of digital broadcast reception data, time stamp data representing reception time is added to each transport packet, and transfer is performed. Yes.

  In addition, in order to guarantee continuous playback in STB real time with respect to the received data of the digital broadcast recorded on an information storage medium such as a DVD-RAM, together with each transport packet data on the information storage medium The time stamp data is also recorded at the same time.

  In the above case, time stamp data is added and recorded for each transport packet as stream data to be recorded on an information storage medium using a large capacity disk medium such as a DVD-RAM. For this reason, time management is performed using this time stamp data.

  In digital TV, video data is broadcast in a compressed form using a digital compression method called MPEG2. According to the MPEG2 system, P picture information has only difference information for I pictures, and B picture information has only difference information for I pictures and P pictures. Therefore, a B picture or a P picture cannot be reproduced independently, and reproduction from an I picture is necessary to reproduce these.

  Here, the video reproduction time viewed from the user indicated by the display time of each picture of I, B, and P is different from the time stamp time. For this reason, when the time management for the stream data recorded on the information storage medium is performed using only the time stamp data, there arises a problem that the display time (video reproduction time) cannot be accurately controlled for the user.

  The present invention has been made in view of the above circumstances, and an object thereof is to improve the processing relating to stream information recording.

  In order to achieve the above object, the embodiment of the present invention is configured to record a data area (STREAM.VRO) configured to record stream data and management information (STRI) related to the stream data. An information medium (201) having a management area (STREAM.IFO) is used. Here, the management information (STRI in FIG. 13 / SFIT in FIG. 15) includes time information (PTSL in FIG. 15) corresponding to a specific portion (AU in FIGS. 16 to 17) of the stream data. Is done.

  The stream data can be composed of data units of a certain size (for example, 64 kB SOBU).

  It is possible to improve the stream information recording process.

  Hereinafter, with reference to the drawings, a stream data storage medium according to an embodiment of the present invention, a data structure of management information related to stream data recorded on the medium, a method for recording and reproducing the management information, and the like will be described. To do.

  FIG. 1 is a view for explaining the data structure of stream data according to an embodiment of the present invention. The data structure of stream data recorded on the information storage medium will be described with reference to FIG.

  Stream data (STREAM.VRO) 106 (FIG. 1A) recorded on an information storage medium such as a DVD-RAM disk (FIG. 3 and others 201) is a stream object for each content of video information in the stream data. (Hereinafter abbreviated as SOB as appropriate). That is, each SOB is formed by stream data obtained by one real-time continuous recording.

  As shown in FIG. 1B, the stream data recorded on the information storage medium is grouped as stream objects (SOB) # A · 298 and # B · 299 for each content of video information in the stream data. It is recorded.

  FIGS. 1B to 1K show details of one SOB # A · 298 among a plurality of stream objects (SOB # A, #B,...).

  When the stream data (STREAM.VRO) 106 is recorded on the DVD-RAM disk, each is recorded with a sector of 2048 bytes as a minimum unit. Further, the 16 sectors are combined into one ECC block, and interleaving (rearranging the data arrangement order) and addition of a correction code for error correction are performed within the same ECC block.

  In this embodiment, a stream block (or stream object unit SOBU) is configured with one or a plurality of (typically two) ECC blocks as a unit, and stream information in stream units (or SOBU units). Recording, partial erasure, editing, etc. are performed.

  In this embodiment, how many ECC blocks form a stream block can be determined according to the transfer rate of the stream data (STREAM.VRO) 106 to be transferred.

  For example, in the example of FIGS. 1C and 1D, the stream block # 1 is composed of two ECC blocks # α and # β, and the stream block # 2 is composed of three ECC blocks # γ, # δ, and # ε. It is configured. In a DVD streamer, one ECC block (32 sectors) constitutes one stream block (or SOBU).

  Each ECC block is composed of 16 sectors as shown in FIG. Therefore, as can be seen from FIGS. 1C to 1E, the stream block (or SOBU) # 1 composed of 2 ECC blocks corresponds to 32 sectors (sector No. 0 to sector No. 31).

  That is, if 1 sector = 2 kbytes, the stream block (SOBU) can be implemented with a fixed size of 64 kbytes (32 sectors).

  The stream data (STREAM.VRO) 106 is recorded on the information storage medium as a set of a time stamp and a transport packet as shown in FIG.

  At that time, pack headers 11 and 12 and PES headers 13 and 14 in which system clock information (system clock reference SCR) and the like are recorded are arranged at the head of each sector, as shown in FIG. The sector data header 17 is recorded immediately after the PES header 14, but only the head sector of each stream block (or SOBU) is recorded with the stream block header 16 instead of the sector data header.

  The stream block header 16 or the sector data header 17 can have contents corresponding to an application header described later (see FIG. 9 or FIG. 10).

  The sector data header 17 in FIG. 1 (f) indicates data arrangement information in the data areas 22 and 23.

  In the data areas 21, 22 (or 23) of FIG. 1 (f), as shown in FIG. 1 (g), a time stamp (corresponding to the ATS shown in FIG. 20, FIG. 29 and others) and a transport packet (FIG. 22 or the packet shown in FIG. 23 or the application packet AP shown in FIG. 29).

  In the example of FIG. 1G, a case where one transport packet d is recorded across a plurality of sectors (No. 0 and No. 1) is illustrated. Such a transport packet d corresponds to the partial packet of FIG. 22 or FIG.

  By the way, in digital broadcasting, a multiplexing / demultiplexing system corresponding to a multi-program called a transport stream is adopted, and the size of one transport packet is often 188 bytes (or 183 bytes).

  On the other hand, as described above, one sector size is 2048 bytes, and even if various header sizes are subtracted, one data area 21, 22, 23 (FIG. 1 (f)) has a transport for digital broadcasting. About 10 packets can be recorded.

  In the transport packet, as shown in FIG. 1H, transport packet headers 61 to 64 (corresponding to 511 in FIG. 23B described later) and payloads 71 to 75 in which data is recorded (described later). (Corresponding to 512 in FIG. 23B).

  In the payloads 71 to 75, MPEG-encoded I picture information 31, B picture information 33 and 34, and P picture information 32 are recorded, as shown in FIG.

  In the first transport packet in which the I picture information 31 is recorded, a flag “1” is set in the random access indicator 503 (see FIG. 23A), and the first transport of each of the B and P picture information 32 to 34 is set. In the port packet, a flag “1” is set in the payload unit start indicator 501 (see FIG. 23A).

  As shown in FIG. 1 (j), each piece of picture information 31 to 34 divided and recorded in the payloads 71 to 75 has a picture header information 41 and a picture compression that is substantial picture information at the head thereof. Information 42 (I picture compression information 42 for I picture information 31) is recorded.

  Further, in each picture header information 41, as shown in FIG. 1 (k), header identification information 51, picture identification information 52 enabling identification of each I, B, and P picture, display of decoder output PTS (presentation time stamp) information 53 indicating timing and DTS (decode time stamp) information 54 indicating timing for the decoder to start decoding are recorded. The picture header information 41 is included in advance in digital broadcast reception information.

  In the stream data recorded on the information storage medium, a specific picture position can be identified using the picture identification information 52 shown in FIG.

  Alternatively, since the PTS information 53 is recorded in the picture header information 41 as shown in FIGS. 1 (j) and (k), the decoder can also start displaying using this value.

  FIG. 2 is a view for explaining the directory structure of the data file according to the embodiment of the present invention. The contents (file structure) of information recorded on the information storage medium according to the embodiment of the present invention will be described with reference to FIG.

  Information recorded on an information storage medium such as a DVD-RAM disk has a hierarchical file structure for each piece of information. The video information and stream data information described in this embodiment are contained in a subdirectory 101 named DVD_RTR directory (or DVD_RTAV) 102.

  In the DVD_RTR (DVD_RTAV) directory 102, a data file 103 having the following contents is stored.

  That is, as a group of management information (navigation data), RTR. IFO (or VR_MANGR.IFO) 104 and STREAM. IFO (SR_MANGR.IFO / SR_MANGR.BUP) 105 and SR_PRIVT. DAT / SR_PRIVT. BUP 105a is stored.

  As the data body (content information), the STREAM. VRO (or SR_TRANS.SRO) 106 and RTR_MOV. VRO (VR_MOVIE.VRO) 107 and RTR_STO. VRO (or VR_STILL.VRO) 108 and RTR_STA. VRO (or VR_AUDIO.VRO) 109 is stored.

  The root directory 100 in the upper hierarchy of the subdirectory 101 including the data file 103 can be provided with a subdirectory 110 for storing other information.

  The contents of this subdirectory include a video title set VIDEO_TS111 containing a video program, an audio title set AUDIO_TS112 containing an audio program, a subdirectory 113 for storing computer data, and the like.

  Data recorded in an information storage medium while retaining the packet structure with respect to data transmitted in the form of a packet structure on a wired or wireless data communication path is referred to as “stream data”.

  The stream data itself is STREAM. A file name VRO (or SR_TRANS.SRO) 106 is recorded together. A file in which management information for the stream data is recorded is STREAM. IFO (or SR_MANGR.IFO and its backup file SR_MANGR.BUP) 105.

  A file recorded by digitally compressing analog video information handled by a VCR (VTR) or a conventional TV based on the MPEG2 standard is RTR_MOV. VRO (or VR_MOVIE.VRO) 107, and a file that collects still image information including after-recording audio or background audio is RTR_STO.VRO. VRO (or VR_STILL.VRO) 108, and the post-record audio information file is RTR_STA.VRO. VRO (or VR_AUDIO.VRO) 109.

  FIG. 3 is a view for explaining the recording data structure (particularly the structure of management information) on the information medium (DVD recording / reproducing disc) according to the embodiment of the present invention.

  As shown in FIG. 3 (b), the area between the end portion in the inner peripheral direction 202 and the end portion in the outer peripheral direction 203 of the information storage medium 201 in FIG. There are volume & file structure information 206 in which file system information is recorded, a data area 207, and a lead-out area 205. The lead-in area 204 is composed of embossed and rewritable data zones, and the lead-out area 205 is composed of rewritable data zones. The data area 207 is also composed of a rewritable data zone.

  In the data area 207, as shown in FIG. 3C, computer data and audio & video data can be recorded together. In this example, an audio & video data area 210 is sandwiched between a computer data area 208 and a computer data area 209.

In the audio & video data area 210, a real time video recording area 221 and a stream recording area 222 can be mixedly recorded as shown in FIG. (It is also possible to use only one of the real-time video recording area 221 and the stream recording area 222.)
As shown in FIG. 3 (e), the real-time video recording area 221 includes the RTR navigation data RTR. IFO (VR_MANGR.IFO) 104 and movie real-time video object RTR_MOV. VRO (VR_MOVIE.VRO) 107 and a still picture real-time video object RTR_STO. VRO (VR_STILL.VRO) 108 and an audio object RTR_STA. VRO (VR_AUDIO.VRO) 109 is recorded.

  Similarly, as shown in FIG. 3E, the stream recording area 222 has streamer navigation data STREAM. IFO (SR_MANGR.IFO / SR_MANGR.BUP) 105 and transport bit stream data STREAM. VRO (SR_TRANS.VRO) 106 is recorded.

  Although not shown in FIGS. 3D and 3E, the stream recording area 222 includes application-specific navigation data SR_PRIVT, DAT / SR_PRIVT. The BUP 105a can also be recorded.

  This SR_PRIVT, DAT 105a is navigation data unique to each application connected (supplied) to the streamer, and is data that does not need to be recognized by the streamer.

  STREAM., Which is management information related to stream data. The IFO (or SR_MANGR.IFO) 105 has a data structure as shown in FIGS.

  That is, as shown in FIG. The IFO (or SR_MANGR.IFO) 105 includes a video manager (VMGI or STR_VMGI) 231, a stream file information table (SFIT) 232, original PGC information (ORG_PGCI) 233, a user-defined PGC information table (UD_PGCIT) 234, A text data manager (TXTDT_MG) 235 and a manufacturer information table (MNFIT) or application-specific navigation data SR_PRIVT. It comprises an application private data manager (APDT_MG) 236 that manages the DAT 105a.

  As shown in FIG. 3G, the stream file information table (SFIT) 232 in FIG. 3F includes stream file information table information (SFITI) 241 and one or more stream object information (SOBI) # A · 242. , # B · 243,..., Original PGC information general information 271 and one or more pieces of original cell information # 1, 272, # 2, 273,.

  Each stream object information (for example, SOBI # A · 242) in FIG. 3G can include stream object general information (SOBI_GI) 251, time map information 252, and the like, as shown in FIG. .

  Further, each original cell information (for example, # 1 and 272; corresponding to SCI shown in FIG. 14 which will be described later) in FIG. 3G is the cell type 281 (which will be described later) as shown in FIG. 14 corresponds to C_TY shown in FIG. 14, cell ID 282, corresponding cell start time (corresponding to SC_S_APAT shown in FIG. 6 (b) described later, FIG. 14 and others) 283, and applicable cell end time (FIG. 6 described later). (B), corresponding to SC_E_APAT shown in FIG. 14 and others) 284, PTS offset 9, and time relation table 2.

  Here, the PTS offset 9 refers to a difference between the PTS (presentation time stamp) value of the display start picture of the original cell (details of the original cell will be described later) and the PTS value of the I picture immediately before (see details) This will be described later with reference to FIG.

  The time map information 252 of FIG. 3H included in the SOBI # A of FIG. 3G includes a stream block number 261, a first stream block size 262, and a first stream block, as shown in FIG. A time difference 263, a second stream block size 264, a second stream block time difference 265, ... can be included. Details of the time difference between the stream blocks constituting the time map information 252 will be described later with reference to FIG.

  FIG. 4 is a diagram for explaining the relationship among stream objects (SOB), cells, program chains (PGC), and the like according to an embodiment of the present invention. Hereinafter, the relationship between SOB and PGC will be described with reference to the example of FIG.

  Stream data recorded in the stream data (STREAM.VRO or SR_TRANS.SRO) 106 constitutes a stream block as a collection of one or more ECC blocks, and recording, partial erasure processing, etc. are performed in units of this stream block. . This stream data creates a group called a stream object for each content of information to be recorded (for example, for each program in digital broadcasting).

  STREAM. Management information (original PGC information 233, user-defined PGC information table 234, etc.) for each stream object (SOB # A, SOB # B) recorded in the VRO (SR_TRANS.SRO) 106 is navigation data STREAM. It is recorded in the IFO (SR_MANGR.IFO) 105 (see the lowermost part in FIG. 4 and FIGS. 3E and 3F).

  The management information (STREAM.IFO 105) for each stream object # A · 298, # B · 299 in FIG. 4 is the stream in the stream file information table (SFIT) 232 as shown in FIGS. Object information (SOBI) # A.242 and # B.243 are recorded.

  Each of the stream object information (SOBI) # A • 242 and (SOBI) # B • 243 includes time map information 252 in which data size, time information, and the like for each stream block are mainly described.

  When reproducing stream data, program chain (PGC) information (corresponding to PGCI # i in FIG. 14 described later) composed of a series of one or more cells is used. Stream data can be reproduced according to the setting order of the cells constituting the PGC.

  PGC includes STREAM. Original PGC290 (ORG_PGCI · 233 in FIG. 3 (f)) that can continuously play back all stream data recorded in VRO (SR_TRANS.SRO) 106, and the location and order in which the user wants to play back There are two types of user-defined PGC # a • 293 and # b • 296 (corresponding to the contents of UD_PGCIT • 234 in FIG. 3F).

  Original cells # 1, 291 and # 2, 292 constituting the original PGC 290 basically exist in one-to-one correspondence with stream objects # A.298 and # B.299.

  On the other hand, user-defined cells # 11 and 294, # 12 and 295, and # 31 and 297 constituting the user-defined PGC can be placed at any position within the range of one stream object # A.298 or # B.299. Can be set.

  Although the sector size of each stream block can be set variously, as a preferred embodiment, a stream of a fixed size (64 kbytes) is composed of 2 ECC blocks (32 sectors) as in stream block # 1 of FIG. An object unit (SOBU) may be employed as the stream block.

If the stream block is fixed to the SOBU of a certain size (for example, 2 ECC block = 32 sectors = 64 kbytes) in this way, the following advantages are obtained:
(01) Even when stream data is erased or rewritten in units of SOBU, the ECC block of the SOBU does not affect the ECC block of SOBUs other than those to be erased or rewritten. Therefore, there is no ECC deinterleaving / releaving (for SOBU that is not subject to erasure or rewriting) associated with erasure or rewriting;
(02) An access position for recording information in an arbitrary SOBU can be specified by the number of sectors (or other parameters corresponding to the number of sectors; for example, information on a stream pack and an application packet group in FIG. 10 described later). For example, when accessing an intermediate position of a certain SOBU # k, the 16th sector (or the position of the application packet corresponding to the 16th sector) from the boundary between SOBU # k-1 and SOBU # k may be specified.

  FIG. 5 is a diagram for explaining the contents of the stream block size and the stream block time difference in the time map information. Hereinafter, the contents of each data in the time map information 252 will be described with reference to FIG.

  As illustrated in FIGS. 5F, 5G, and 5H, the stream object (SOB) # A · 298 is composed of two stream blocks # 1 and # 2.

  In the example of FIGS. 5F and 5H, the data size of the stream block # 1 constituting the SOB # A.298 is composed of 2 ECC blocks (# α, # β), and is equivalent to 32 sectors (FIG. 5E). (I)). That is, the first stream block size 262 (FIG. 5 (j)) in the time map information 252 (FIG. 5 (a) (k)) is 32 sectors (64k bytes).

  The stream block # 1 (FIG. 5 (f)) at the head of SOB # A.298 (FIG. 5 (g)) has a sector No. 0 (FIG. 5 (e)) and sector no. A time stamp a (FIG. 5C) is recorded at the head of the data area 21 included in 0 (FIG. 5D).

  The succeeding stream block # 2 (FIG. 5 (f)) of SOB # A.298 (FIG. 5 (g)) has a sector No. 32 (FIG. 5 (e)) and sector no. 32, a time stamp p (FIG. 5C) is recorded at the head of the data area 311 included in FIG.

  As shown in FIG. 5C, the time stamp value of the first stream data of the stream block # 1 is a time stamp a, and the time stamp value of the first stream data of the next stream block # 2 is a time stamp p. It has become.

  The value of the first stream block time difference 263 in FIG. 5B (corresponding to the stream block time difference 263 in FIG. 3I) is the difference value between the time stamp p and the time stamp a ([time stamp p] − [ Time stamp a]).

  Note that the time map information 252 in FIG. 5A can be handled as including the access data unit AUD in the stream object information SOBI described later with reference to FIG. The SOBU including the information to be accessed can be specified by the information (access unit start map AUSM or the like) included in this AUD.

  FIG. 6 is a diagram for explaining a cell range designation method in the original cell and the user-defined cell. Each cell range can be specified by specifying the start time and end time.

  Specifically, as the time of the start time 283 of the corresponding cell and the end time 284 of the corresponding cell (FIG. 6B) in the original cell immediately after the recording of the stream data, the corresponding stream object # A · 298 (FIG. 6 ( The value of the first time stamp a and the last time stamp z (figure 6 (c)) in f)) are used.

  On the other hand, the time range designation in the user-defined cell # 12 • 295 (FIG. 6 (k)) can designate an arbitrary time. For example, as shown in FIGS. 6 (i) and 6 (j), the values of the time stamps d and n corresponding to the designated transport packets d and n are the values of the start time 331 and the end time 332 of the corresponding cell. Can be set as

  FIG. 6F illustrates a case where the stream object (SOB) # A · 298 is composed of two stream blocks # 1 and # 2.

  6E and 6G, the stream block # 1 is composed of 32 sectors (sector No. 0 to No. 31), and the stream block # 2 is 48 sectors (sector No. 32 to No. 79). It consists of

  The first sector number of stream block # 1. As shown in FIGS. 6E and 6D, 0 is composed of a pack header 1, a PES header 6, a stream block header 11, a data area 21, and the like.

  Also, the rear sector No. of stream block # 2. 78 includes a pack header 3, a PES header 8, a sector data header 13, a data area 24, and the like, as shown in FIGS.

  Further, the sector number of FIG. 1 is recorded with a pack header 2, a sector data header 12, a data area 22, and the like as shown in FIG. 33, a sector data header 321, a data area 312 and others are recorded as shown in FIG.

  In the data area 21 shown in FIGS. 6D and 6H, as shown in FIGS. 6C and 6I, a pair of the time stamp a and the transport packet a or the time stamp d and the transport packet d is stored. Pairs are recorded.

  Further, the area of the data area 24 in FIG. 6D includes a plurality of time stamp and transport packet pairs, an end code 32 following the last time stamp z + transport packet z pair, and a padding area 37. Is recorded.

  Further, the data area 22 in FIG. 6 (h) includes a transport packet d including the subsequent contents of the transport packet d in the data area 21, as shown in FIG. 6 (i). In other words, in this example, the content of the transport packet d is divided and recorded in the data area 21 and the data area 22.

  The first half (data area 21 side) of the transport packet d in FIG. 6 (i) corresponds to the tail side partial packet in FIG. 23 (f) described later, and the second half of the transport packet d in FIG. 6 (i). (Data area 22 side) corresponds to the head side partial packet in FIG.

  Further, in the data area 312 of FIG. 6 (h), as shown in FIG. 6 (i), a pair of the time stamp n and the transport packet n and other similar pairs are recorded.

  Here, the start time 331 (FIG. 6 (j)) of the cell corresponding to the location where the user or the like has specified the playback start time is the time stamp d for the entire two transport packets d divided into the data areas 21 and 22. (FIG. 6 (i)).

  When the transport packet is read as an application packet (AP) and the application packet arrival time is APAT, the cell start time 331 can be expressed as a cell start APAT.

  The end time 332 (FIG. 6 (j)) of the cell corresponding to the location where the user or the like has specified the playback end time is specified by the time stamp n (FIG. 6 (i)) for the transport packet n in the data area 312. Is done. This cell end time 332 can be expressed as cell end APAT.

  The cell start time (cell start APAT) 331 and cell end time (cell end APAT) 332 can be recorded in the user-defined cell information # 12/295 as shown in FIG. 6 (k).

  The user-defined cell information # 12/295 can be recorded in the user-defined PGC information table 234 shown in FIG.

  The above is cell start / end time information related to user-defined cell information (user-defined PGC information), but cell start / end time information related to original cell information (original cell information) is exemplified as follows. it can.

  That is, the start time 283 of the corresponding cell in FIG. 6B can be indicated by the start time stamp a in FIG. 6C, and the end time 284 of the corresponding cell can be indicated by the end time stamp z.

  The start time 283 of the corresponding cell in FIG. 6B can correspond to cell start APAT (including stream cell start APAT (SC_S_APAT) or erasure start APAT (ERA_S_APAT)).

  Further, the end time 284 of the corresponding cell in FIG. 6B can correspond to cell end APAT (including stream cell end APAT (SC_E_APAT) or erasure end APAT (ERA_E_APAT)).

  The above cell start time (cell start APAT) 283 and cell end time (cell end APAT) 284 are recorded in the original cell information # 1 and 272 as shown in FIG. 6 (a).

  The original cell information # 1 and 272 can be recorded in the original PGC information 233 shown in FIG.

  FIG. 7 illustrates the recording data structure (particularly the structure of reproduction end position information / resume information, VMGI management information / recording time information, etc.) on an information medium (DVD recording / reproducing disc) according to another embodiment of the present invention. It is a figure to do.

  Since the data configuration of FIGS. 7A to 7F is the same as that of FIGS. 3A to 3F, description thereof will be omitted.

  The video manager (STR_VMGI) 231 in FIG. 7F includes reproduction end position information (resume information) 6110, video manager management information (VMGI_MAT) 6111 and others, as shown in FIG.

  The reproduction end position information (resume information) 6110 includes original PGC number 6210, original cell number 6220, reproduction end position time (resume time) information 6230, and the like, as shown in FIG. 7 (h).

  The video manager management information (VMGI_MAT) 6111 includes a time zone (TM_ZONE) 6240.

  At the stage where the reproduction of the recorded stream block (or original cell) is completed, the reproduction end position information 6110 is used as resume information in the video manager information 231 in the management information recording area (STREAM.IFO) of FIG. Can be recorded.

  The time information 6230 included in the reproduction end position information 6110 is recorded as a time stamp (ATS) value. However, the time information 6230 is not limited thereto, and the PTS value (or the total number of fields from the cell reproduction start position) is recorded as the time information 6230. You can also

  The time zone (TM_ZONE) 6240 includes information on the recording time (REC_TM) as shown in FIG.

  The recording time (REC_TM) information includes a time zone type (TZ_TY) that identifies whether the REC_TM is based on Universal Time Coordinate (UTC) or a specific local time, and the time offset of the REC_TM from the UTC. And a time zone offset (TZ_OFFSET) that describes the date and time in minutes.

  The recording time (REC_TM) may be described in the cell start time (SC_S_APAT) format shown in FIG. 6B or the like, or the cell playback time (presentation time PTM) format.

  There are two types of recording time (REC_TM). The first is the stream object recording time (SOB_REC_TM), and the second is the playlist creation time (PL_CREATE_TM).

  Here, the time when the stream object (SOB) corresponding to the original cell was recorded is indicated by SOB_REC_TM.

  A playlist is a partial list of programs. This playlist allows the user to define any playback sequence (relative to the program content). The time when such a playlist is created is indicated by PL_CREATE_TM.

  FIG. 8 is a diagram for explaining the internal structure of the PES header shown in FIG. 1 and others.

  As shown in FIG. 8B, the PES header 601 in FIG. 8A includes a packet start code prefix 602, a stream ID 603, a reproduction time stamp 604, and the like. The PES header 601 corresponds to the PES header shown in FIGS. 1 (f), 5 (d), 6 (d), and the like.

  Also, the stream PES header of FIG. 8D includes a packet start code prefix, a stream ID (private stream 2), a PES packet length, a substream ID, and the like, as shown in FIG. 8C. This stream PES header is the same as the stream PES header of FIG. 22 described later, and has contents corresponding to the PES header 601 of FIG.

  When the PES header in FIG. 1 (f) has the internal structure of the PES header 601 shown in FIG. 8 (a), in the MPEG standard, the stream ID 603 (FIG. 8 (b)) of this PES header is “10111110”. Sometimes, it is defined that a packet having this PES header is a padding packet (see FIG. 12G described later).

  On the other hand, when the stream ID 603 (substream ID in FIG. 8C) is “00000010”, the packet with the PES packet includes stream recording data.

  In the stream block # 1 in FIG. 1C, the last transport packet g (FIG. 1G) is a sector number. 0-No. 31 (FIG. 1 (e)). However, in the stream block # 2 (FIGS. 1E and 1G), when the recording is ended halfway by the user or the like, the last transport packet (not shown) is arranged in the sector before the last sector. In some cases, the last sector (not shown) may be an empty area where no stream data is recorded. In this case, the padding packet (padding packet 40 in FIG. 12G described later) is recorded in the last sector.

  FIG. 9 is a diagram for explaining the internal structure of the stream block header shown in FIG.

  As shown in FIG. 9A, the stream block header 11 has contents corresponding to the substream ID, application header, application header extension, stuffing byte, and the like.

  In the 1-byte application header extension (option), 1-bit AU_START, 1-bit AU_END, and 2-bit COPYRIGHT are described.

  When AU_START is set to “1”, it indicates that the associated application packet (eg, AP in FIG. 29) includes a random access entry point (start of random access unit) in the stream.

  When AU_END is set to “1”, it indicates that the associated application packet is the final packet of the random access unit.

  COPYRIGHT describes the copyright status of the related application packet.

  As shown in FIG. 9B, the stream block header 11 includes transport packet information 611, stream block information 612, sector data header information 613, and the like.

  The transport packet information 611 in FIG. 9B indicates the same as the transport packet information 611 in FIG. 9C.

  The stream block information 612 in FIG. 9B, in which information about the entire stream block is recorded, is the recording time 622 (date and time information recorded in the information storage medium 201) in FIG. It corresponds to an attribute 623 (attribute information related to transport packets), a stream block size 624 (data size of the corresponding stream block (for example, can be described by the number of ECC blocks)), a stream block time difference 625, and the like.

  Here, taking FIG. 5B as an example, the time range information in the corresponding stream block is [stream block time difference] = [first time stamp value in stream block # 2] − [time stamp a Value]. This [stream block time difference] becomes the stream block time difference 625.

  Also, the sector data header information 613 in FIG. 9B corresponds to the first access point 626 and the transport packet connection flag 627 in FIG. 9C. The sector data header information 613 includes information similar to the sector data header 12 shown in FIG.

  The transport packet information 611 in FIG. 9C includes the number of transport packets (the number of application packets) 631, the transport packet mapping table 632, and the like, as shown in FIG. 9D.

  Note that the number of application packets in FIG. 9D corresponds to the number of packets AP_Ns in FIG.

  The number 631 of transport packets (application packets) in FIG. 9D can include an I picture mapping table 641, a B, P picture mapping table 642, etc., as shown in FIG. 9E.

  Also, the transport packet mapping table 632 in FIG. 9D can include a video packet mapping table 643, an audio packet mapping table 644, a program specific information mapping table 645, and the like.

  Each mapping table (FIG. 9E) in the transport packet mapping table 632 is configured in a bitmap format.

  For example, when n transport packets (application packets) are recorded in one stream block, the value of the number of transport packets (number of application packets) 631 in FIG. 9D is “n”. It becomes.

  Further, each mapping table 643 to 645 is composed of “n-bit data”, and one bit is assigned to each transport packet (application packet) arranged in the stream block from the front.

  FIG. 10 is a diagram for explaining the internal structure of the sector data header shown in FIG.

  For example, the sector data header 17 in FIG. 1 (f) indicates the data arrangement information in the data areas 22 and 23, and the sector data header in FIG. 10 (a) (corresponding to the application header in FIG. 10 (d)). It corresponds to.

  The sector data header 12 has an internal structure including a first access point 651 and a transport packet connection flag 652 as shown in FIG.

  By the way, as shown in FIG. 10D, one stream pack having a size of 2048 bytes as well as one sector is composed of a pack header and a stream PES header. In this stream PES packet, an application packet header corresponding to a part of the sector data header 12 in FIG. 10A or the stream block header 11 in FIG. 9A is included.

The application packet header includes the following as shown in FIG. 10 (c):
* Application packet header format version description;
* Number of application packets (transport packets) that start in the corresponding stream pack AP_Ns;
* First application packet time stamp position FIRST_AP_OFFSET describing the position of the time stamp of the first application packet starting in the stream pack as a relative value from the first byte of the stream pack;
* Extension header information EXTENSION_HEADER_IFO indicating whether a header extension and / or stuffing byte is present;
* Service identifier of the service that generated the corresponding stream.

  The FIRST_AP_OFFSET included in the application packet in FIG. 10D corresponds to the first access point 651 included in the sector data header 12 in FIG.

  As shown in FIG. 1G, the transport packet d is recorded across two sectors. Here, when the last time stamp in the sector or the transport packet straddles the next sector, the transport packet connection flag 652 is set to “1”.

  In the example of FIG. 1G, the address in the data area 22 at the start position of the time stamp that follows the transport packet d straddling the next sector is recorded in the first access point 651 (expressed in bit units). Has been.

  Sector No. 1 shown in FIG. 1 (or the corresponding stream pack) is assigned the sector No. A value larger than the size of one data area 22 (FIG. 1 (f)) can be set. By doing so, sector no. It is shown that the position of the time stamp corresponding to the packet next to the packet recorded in 1 exists in the next and subsequent sectors.

  In one embodiment of the present invention, a value larger than the size of the data areas 21, 22, and 23 can be designated as the value of the first access point 651, so that the sector size (or stream pack size = 2048 bytes) can be specified. Even for a packet having a large size, the start position of the time stamp can be designated.

  For example, in the data structure of FIG. 0 to sector no. It is assumed that the recording has been performed up to two. Further, the time stamp for the packet is sector no. 0 is recorded at the first position in the data area 21, and the time stamp for the next packet is the sector number. Consider a case where the data is arranged at the T-th bit in the second data area.

  In this case, sector no. The value of the first access point of “0” is “0” and the sector No. The value of the first access point of “1” is “data area 22 size of sector No. 1 + T”, sector no. The value of the first access point of 2 is “T”.

  FIG. 11 is a diagram illustrating another example of the time map information 252 according to the embodiment of the present invention.

  This time map information 252 is an example different from the time map information 252 of FIGS. 3 (h) and 3 (i), and each stream block (first stream block, second stream block,...) This is table information describing the size, stream block time difference, and number of packets (AP_Ns).

  Assume that the total number of transport packets (or the total number of application packets AP_Ns) is designated to access a predetermined screen (picture) using the time map information 252 of FIG. 11 (from the STB side). Then (on the disk device side) the number of transport packets (AP_Ns) is sequentially added from the first stream block of FIG. 11, and the stream block at the time when the designated value is reached is accessed.

  FIG. 12 is a diagram for explaining an example of the internal configuration of a sector constituting a stream block (SOBU) (a stream pack including an application packet and a stream pack including a stuffing packet).

  As shown in FIGS. 12C and 12E, the stream object (SOB) # A · 298 in FIG. 12D is composed of a plurality of stream blocks # 1, # 2,.

  Each stream block # 1, # 2,... Is composed of a stream object unit (SOBU) having a 2ECC block size (= 32 sectors = 64 kbytes).

  In this way, for example, even if stream block (SOBU) # 2 is deleted, the ECC block of stream block (SOBU) # 1 is not affected by this deletion.

  As shown in FIG. 12B, the first stream block (SOBU) # 1 of SOB # A. 0 to sector no. 31 (32 sectors / 64 kbytes).

  Each sector of the stream block (SOBU) # 1 has a similar data structure. For example, sector no. As for 0, it is as shown in FIG.

  That is, sector no. 0 is composed of a stream pack of 2048 bytes (2 kbytes). This stream pack is composed of a 14-byte pack header and a 2034-byte stream PES packet.

  The stream PES packet is composed of a 6-byte PES header, a 1-byte substream ID, and a 2027-byte stream data area.

  The stream data area includes a 9-byte application header, an application header extension (option), a stuffing byte (option), and an application packet area.

  The application packet area is composed of a group of application packets each having an application time stamp (ATS) at the head.

  For example, when a transport packet having a size of 188 bytes is stored in the application packet area as an application packet, about 10 application packets can be stored in the application packet area.

  In stream recording, an application that generates recording contents performs stuffing by itself so that it is not necessary to separately adjust the pack length. For this reason, in stream recording, a stream pack can always be handled as having a required length (for example, 2048 bytes).

  The stuffing byte of FIG. 12A can be used to always keep the stream pack at a predetermined length (2048 bytes).

  Although not shown, the pack header in FIG. 12A includes pack start code information, SCR base information, SCR extension information, program maximum rate information, marker bits, pack stuffing length information, and the like.

  The SCR base is composed of 32 bits, and the 32nd bit is set to zero. Further, 10.08 Mbps is adopted as the program maximum rate.

  The PES header and substream ID shown in FIG. 12A have the contents shown in FIG.

  As shown in FIG. 10C, the application header of FIG. 12A includes version information, the number of application packets AP_Ns, the time stamp position FIRST_AP_OFFSET of the first application packet, extension header information EXTENSION_HEADER_IFO, a service ID, and the like. .

  Here, the version describes the version number of the application header format.

  AP_Ns in the application header describes the number of application packets that start in the corresponding stream pack. When the first byte of ATS is stored in the corresponding stream pack, it can be considered that the application packet starts in this stream pack.

  In FIRST_AP_OFFSET, the time stamp position of the first application packet started in the corresponding stream packet is described in byte units as a relative value from the first byte of this stream packet. If there is no application packet to start in the stream packet, “0” is described in FIRST_AP_OFFSET.

  EXTENSION_HEADER_INFO describes whether an application header extension and / or stuffing byte is present in the corresponding stream packet.

  When the content of EXTENSION_HEADER_INFO is 00b, it indicates that neither an application header extension nor a stuffing byte exists after the application header.

  When the content of EXTENSION_HEADER_INFO is 10b, it indicates that there is an application header extension after the application header, but there is no stuffing byte.

  When the content of EXTENSION_HEADER_INFO is 11b, it is indicated that an application header extension exists after the application header, and a stuffing byte also exists after the application header extension.

  It is prohibited for the content of EXTENSION_HEADER_INFO to be 01b.

  The stuffing byte (option) in front of the application packet area is activated by “EXTENSION_HEADER_INFO = 11b”. By doing so, it is possible to prevent a “packing paradox” from occurring when there is a contradiction between the number of bytes in the application header extension and the number of application packets that can be stored in the application packet area.

  SERVICE_ID describes the ID of the service that generates the stream. If this service is unknown, 0x0000 is described in SERVICE_ID.

  The application packet area in FIG. 12A can be configured in the same manner as shown in the lower part of FIG. 22 described later (the packet in FIG. 22 is replaced with the application packet in FIG. 12).

  That is, a partial application packet is recorded at the beginning of the application packet area, and thereafter, a plurality of pairs of application time stamp ATS and application packet are sequentially recorded, and a partial application packet is recorded at the end.

  In other words, a partial application packet can exist at the start position of the application packet area. At the end position of the application packet area, a partial application packet or a reserved stuffing area can exist.

  An application time stamp (ATS) arranged in front of each application packet is composed of 32 bits (4 bytes). This ATS is divided into two parts: a basic part and an extended part. The basic part is a part called 90 kHz unit value, and the extended part shows a less significant value measured at 27 MHz.

  In FIG. 12A, the application header extension can be used to store information that may differ between application packets and application packets. Such information is not necessary for all applications.

  Therefore, the data field of the application header is defined so as to describe (in the above-described EXTENSION_HEADER_INFO) that an optional application header extension exists in the stream data area.

  At the time of recording the stream, the first byte of the application time stamp ATS of the first application packet needs to be aligned with the start position of the application packet area in the first stream packet at the beginning of the stream object SOB.

  On the other hand, for subsequent stream packets in the SOB, application packets may be divided (split) at adjacent stream packet boundaries.

  The partial application packet shown in FIG. 22 or FIGS. 23 (f) and 23 (g) described later indicates an application packet generated by this division (split).

  The byte offset of the first application timestamp that starts in the stream packet and the number of application packets that start in the stream packet are described in the application header.

  By doing so, stuffing before the first application time stamp and after the last application packet is automatically performed in a stream packet.

  That is, “the application performs stuffing by itself” is realized by the automatic mechanism. This automatic stuffing ensures that the stream packet always has the required length.

  The application header extension (optional) consists of a list of entries. Here, there is one entry of 1 byte length for each application packet starting in the corresponding stream packet. The bytes of these entries can be used to store information that can vary from application packet to application packet.

  The 1-byte application header extension (option) describes 1-bit AU_START, 1-bit AU_END, and 2-bit COPYRIGHT.

  When AU_START is set to “1”, it indicates that the associated application packet includes a random access entry point (start of random access unit) in the stream.

  When AU_END is set to “1”, it indicates that the associated application packet is the final packet of the random access unit.

  COPYRIGHT describes the copyright status of the related application packet.

  The packet structure of FIG. 12A can be applied to other than the last sector of SOB # A · 298, but is not necessarily applied to the last sector.

  For example, the end of SOB # A.298 is the sector number of FIG. When this sector is composed of the padding packet 40 as shown in FIG. 12 (g), the contents of the padding area 38 (FIG. 12 (h)) are different from those in FIG. 12 (a). become.

  That is, as shown in FIG. 12 (i), the stuffing packet as the padding packet 40 includes a 14-byte pack header, a 6-byte PES header, a 1-byte substream ID, a 9-byte application header, It consists of a 2018-byte application packet area.

  In the pack including the head of the stuffing packet, the application packet area is composed of a 4-byte application time stamp ATS and zero-byte data for 2014 bytes (data having no substantial recording content).

  On the other hand, in the pack including the subsequent stuffing packet, the application packet area is composed of 2018 byte zero byte data (no ATS).

  By the way, when recording is performed at a very low bit rate, stuffing is necessary to ensure recovery (reproduction) of time map information (252 in FIG. 3H; or MAPL in SOBI in FIG. 15 described later). become. The stuffing packet in FIG. 12 (i) is defined as a conceptual unit for that purpose.

  The purpose of this stuffing packet is achieved by ensuring that each SOBU, including the stuffing area, contains at least one ATS value.

Stuffing packets have the following conditions:
* One or more stuffing packets always start from the application packet area of the pack after the pack containing the actual application packet data;
* One or more stuffing packets are composed of one 4-byte ATS and as many zero-byte data (following ATS) as are necessary to fill the application data area of the remaining pack of the SOBU. Now, when the number of sectors per SOBU is SOBU_SIZ, if 0 ≦ n ≦ SOBU_SIZ−1, the total length of the stuffing packet is “4 + 2014 + n × 2018” bytes.

The ATS of the stuffing packet is set as follows:
* In an SOBU where at least one pack contains actual application packet data, the ATS of the stuffing packet is set to the ATS of the application packet preceding the stuffing packet;
* In an SOBU that does not include actual application packet data, the ATS of the stuffing packet is determined according to the contents of time map information and the like.

All packs that contain stuffing packets or parts of stuffing packets are structured as follows:
* The SCR of the pack header is obtained by adding “2048 × 8 bits ÷ 10.08 Mbps” to the SCR of the preceding pack;
* The PES packet header and substream ID are the same as for all other PES packets;
* In the application header (see FIGS. 10C and 10D), AP_Ns = 0, FIRST_AP_OFFSET = 0, EXTENSION_HEADER_IFO = 00b, and SERVICE_ID = 0 (other parameters in the application header are also 0).

  13 is a diagram for explaining an internal data structure of streamer management information (corresponding to STREAM.IFO or SR_MANGR.IFO in FIG. 2).

  The management information (navigation data) shown in FIG. 2 or FIG. The IFO (SR_MANGR.IFO) 105 includes streamer information STRI as shown in FIG.

  As shown in FIG. 3 (f) or FIG. 13, this streamer information STRI includes streamer video manager information STR_VMGI, stream file information table SFIT, original PGC information ORG_PGCI (more generally, PGC information PGCI # i ), A user-defined PGC information table UD_PGCIT, a text data manager TXTDT_MG, and an application private data manager APDT_MG.

  As shown in FIG. 13, the streamer video manager information STR_VMGI includes video manager information management information VTSI_MAT in which management information about STR and STR_VMGI is described, and a play in which a search pointer for searching a playlist in the stream is described. A list search pointer table (PL_SRPT).

  Here, the play list is a list of a part of the program. This playlist allows the user to define any playback sequence (relative to the program content).

  The stream file information table SFIT includes all navigation data directly related to the streamer operation. Details of the stream file information table SFIT will be described later with reference to FIG.

  The original PGC information ORG_PGCI is a part describing information related to the original PGC (ORG_PGC). ORG_PGC indicates navigation data describing a program set. ORG_PGC is a series (chain) of programs, and includes stream data recorded in the “.SRO” file (SR_TRANS.SRO 106 in FIG. 2) of FIG.

  Here, the program set indicates the entire recorded contents (all programs) of the information storage medium 201. In reproducing a program set, the same reproduction order as the recording order of the program is used as the reproduction order, unless an arbitrary program is edited and the reproduction order is changed with respect to the original recording. This program set corresponds to a data structure called an original PGC (ORG_PGC).

  A program is a logical unit of recorded content that is recognized by a user or defined by a user. A program in the program set is composed of one or more original cells. The program is defined only in the original PGC.

  Furthermore, the cell is a data structure indicating a part of the program. The cells in the original PGC are called “original cells”, and the cells in the user-defined PGC described later are called “user-defined cells”.

  Each program in the program set consists of at least one original cell. In addition, each part of the program in each playlist is composed of at least one user-defined cell.

  On the other hand, in the streamer, only the stream cell (SC) is defined. Each stream cell refers to a part of the recorded bit stream. In the embodiment of the present invention, “cell” means “stream cell” unless otherwise specified.

  Note that the program chain (PGC) represents a superordinate conceptual unit. In the original PGC, the PGC indicates a chain of programs corresponding to the program set. In the user-defined PGC, the PGC indicates a series (chain) of a part of the program corresponding to the playlist.

  In addition, the user-defined PGC that points to a part of the program chain includes only navigation data. A part of each program refers to stream data belonging to the original PGC.

  The user-defined PGC information table UD_PGCIT in FIG. 13 may include user-defined PGC information table information UD_PGCITI, one or more user-defined PGC search pointers UD_PGC_SRP # n, and one or more user-defined PGC information UD_PGCI # n.

  Although not shown, the user-defined PGC information table information UD_PGCITI includes UD_PGC_SRP_Ns indicating the number of user-defined PGC search pointers UD_PGC_SRP and UD_PGCIT_EA indicating the end address of the user-defined PGC information table UD_PGCIT.

  The number of UD_PGC_SRPs indicated by UD_PGC_SRP_Ns is the same as the number of user-defined PGC information (UD_PGCI) and the same as the number of user-defined PGCs (UD_PGC). This number is allowed up to a maximum of “99”.

  UD_PGCIT_EA describes the end address of the corresponding UD_PGCIT by the relative number of bytes (F_RBN) from the first byte of the UD_PGCIT.

  Here, F_RBN indicates the relative number of bytes from the first byte of the defined field in the file, and starts from zero.

  PGCI # i that generally represents the original PGC information ORG_PGCI or the user-defined PGC information UD_PGCI in the user-defined PGC information table UD_PGCIT will be described later with reference to FIG.

  The text data manager TXTDT_MG in FIG. 13 is supplementary text information. This TXTDT_MG can be stored in the playlist and program together with the primary text information PRM_TXTI of FIG.

  Although not shown, the application private data manager APDT_M of FIG. 13 can include application private data manager general information APDT_GI, one or more APDT search pointers APDT_SRP # n, and one or more APDT areas APADTA # n.

  Here, the application private data APDT is a conceptual area where an application device connected to the streamer can store arbitrary non-real time information (information desired in addition to the real time stream data).

  FIG. 14 is a diagram illustrating an internal data structure of PGC information (ORG_PGCI / UD_PGCIT in FIG. 3 or PGCI # i in FIG. 13).

  The PGC information PGCI # i in FIG. 14 generally represents the original PGC information ORG_PGCI in FIG. 13 or the user-defined PGC information UD_PGCI in the user-defined PGC information table UD_PGCIT.

  As shown in FIG. 14, PGC information PGCI # i includes PGC general information PGC_GI, one or more program information PGI # m, one or more stream cell information search pointers SCI_SRP # n, and one or more stream cell information SCI. #N.

  The PGC general information PGC_GI includes the number of programs PG_Ns and the number of stream cell information search pointers SCI_SRP SCI_SRP_Ns.

  Each program information PGI (for example, PGI # 1) includes a program type PG_TY, the number C_Ns of cells in the program, primary text information PRM_TXTI of the program, and an item text search pointer number IT_TXT_SRPN.

  Here, the program type PG_TY includes information indicating the state of the corresponding program. In particular, a flag indicating whether or not the program is protected from erroneous erasure, that is, a protect flag is included.

  When the protect flag is “0b”, the corresponding program is not protected, and when it is “1b”, it is in a protected state.

  The number of cells C_Ns indicates the number of cells in the program. Throughout all PGC programs and all cells, cells are associated (implicitly) with the program according to their ascending order.

  For example, if the program # 1 has C_Ns = 1 and the program # 2 has C_Ns = 2 in the PGC, the first stream cell information SCI of the PGC is attached to the program # 1, and the second, The third SCI is associated with program # 2.

  The primary text information PRM_TXTI describes text information having one common character set (ISO / IEC646: 1983 (ASCII code)) so that the information storage medium (DVD-RAM disc) 201 can be used all over the world. It is a thing.

  The item text search pointer number IT_TXT_SRPN describes the search pointer number for the item text (text data corresponding to the corresponding program) IT_TXT. When the corresponding program has no item text, IT_TXT_SRPN is set to “0000h”.

  Each stream cell information search pointer SCI_SRP (for example, SCI_SRP # 1) includes SCI_SA indicating the start address of the corresponding stream cell information SCI. This SCI_SA is described by the relative number of bytes (F_RBN) from the first byte of PGCI.

  Each stream cell information SCI (for example, SCI # 1) includes stream cell general information SC_GI and one or more stream cell entry point information SC_EPI # n.

  The stream cell general information SC_GI includes a cell type C_TY including a flag TE indicating a temporary erase (temporary erase; TE) state, the number SC_EPI_Ns of stream cell entry point information, a stream object number SOB_N, a stream cell start APAT (FIG. 6 SC_S_APAT shown in others, stream cell end APAT (SC_E_APAT shown in FIG. 6 others), and erase start APAT indicating the start APAT of the temporary erase cell when the cell is in the temporary erase state (TE = 10b) (ERA_S_APAT shown in FIG. 6 and the like) and erase end APAT (ERA_E_APAT shown in FIG. 6 and others) indicating the end APAT of the temporary erase cell when the cell is in the temporary erase state (TE = 10b). Yes.

  The cell type C_TY describes the format of the corresponding stream cell and its temporary erase state.

  That is, the cell format C_TY1 = “010b” is described in the format of all stream cells (the C_TY1 = “010b” can distinguish the stream cell from the other cells).

  On the other hand, if the flag TE is “00b”, it indicates that the corresponding cell is in a normal state, and if the flag TE is “01b” or “10b”, it indicates that the corresponding cell is in a temporary erase state. .

  The flag TE = “01b” indicates a case where the corresponding cell (a cell in the temporarily erased state) starts after the first application packet that starts in the SOBU and ends before the last application packet in the same SOBU. .

  The flag TE = “10b” indicates a case where the corresponding cell (a cell in the temporarily erased state) includes at least one SOBU boundary (the first application packet or the last application packet starts within the SOBU).

Note that the protect flag of the program and the TE flag of the cells in the program cannot be set at the same time. therefore,
(A) None of the cells in the program in the protected state can be set to the temporary erase state;
(B) A program including one or more cells in the temporary erase state cannot be set to the protected state.

  The number of stream cell entry point information SC_EPI_Ns describes the number of stream cell entry point information included in the corresponding stream cell information SCI.

  Each stream cell entry point information SC_EPI (for example, SC_EPI # 1) in FIG. 14 has two types (type A and type B).

  Type A SC_EPI includes an entry point type EP_TY and an entry point application packet arrival time EP_APAT. Type A is indicated by entry point type EP_TY1 = “00b”.

  Type B SC_EPI includes primary text information PRM_TXTI in addition to type A EP_TY and EP_APAT. Type B is indicated by entry point type EP_TY1 = “01b”.

  In any stream cell, an entry point can be used as a tool for skipping a part of the recorded contents. All entry points can be identified by application packet arrival time (APAT). With this APAT, it can be specified where data output is started.

  The stream object number SOB_N describes the number of the SOB referred to by the corresponding cell.

  Stream cell start APAT (SC_S_APAT) describes the start APAT of the cell.

  Stream cell end APAT (SC_E_APAT) describes the end APAT of the cell.

  The erase start APAT (ERA_S_APAT) is the first start in the first SOBU including the head of the temporary erase cell in the temporary erase cell (the TE field of the C_TY is “10b”) including at least one SOBU boundary. It describes the arrival time (APAT) of the application packet.

  The erase end APAT (ERA_E_APAT) is the first start in the SOBU containing the application packet immediately following the temporary erase cell in the temporary erase cell (the TE field of its C_TY is “10b”) including at least one SOBU boundary. It describes the arrival time (APAT) of the application packet.

  FIG. 15 is a diagram for explaining the internal data structure of the stream file information table (SFIT).

  As shown in FIG. 15, the stream file information table SFIT is composed of stream file information table information SFITI, one or more stream object stream information SOB_STI # n, and stream file information SFI.

  The stream file information table information SFITI includes the number SFI_Ns of stream file information on the information storage medium (DVD-RAM disk) 201, the number SOB_STI_Ns of stream object stream information following SFITI, the end address SFIT_EA of SFIT, and the start of SFI. It consists of an address SFI_SA.

  SFIT_EA describes the end address of SFIT by the relative number of bytes (F_RBN) from the first byte of SFIT.

  SFI_SA describes the start address of SFI by the relative number of bytes (F_RBN) from the first byte of SFIT.

  Each stream object stream information SOB_STI includes three types of parameters. Each parameter can have a unique value for each bitstream recording. However, usually these parameter sets can be equal in many bitstream recordings. Therefore, SOB_STI is stored in a table different from the stream object information (SOBI) table, and it is recognized that several stream objects (SOBs) share the same SOB_STI (ie, point to the same SOB_STI). Yes. Therefore, normally, the number of SOB_STIs is smaller than the number of SOBs.

  Each stream object stream information SOB_STI (eg, SOB_STI # 1) in FIG. 15 includes an application packet size AP_SIZ, a service ID number SERV_ID_Ns, a service ID (SERV_IDs), and an application packet device unique ID (AP_DEV_UID). .

  AP_SIZ describes the application packet size as the byte length of the packet in the bit stream transferred from the application device to the streamer.

  In the DVD streamer, the application packet size is fixed in each bit stream recording. Therefore, if the application packet size may change during each uninterrupted recording, the current stream object (current SOB) is terminated there, and the new stream object (new SOB) is replaced with the new AP_SIZ. It starts with. At that time, both the current SOB and the new SOB belong to the same program in the original PGC information (ORG_PGCI).

  SERV_ID_Ns describes the number of service IDs included in the subsequent parameters.

  SERV_IDs describes a list of service IDs in an arbitrary order.

  AP_DEV_UID describes a unique device ID that is unique to the application device that supplied the recorded bitstream.

  As shown in FIG. 15, the stream file information SFI includes stream file general information SF_GI, one or more stream object information (SOB information) search pointers (SOBI_SRP) #n, one or more SOB information (SOBI) #n, It consists of

  The stream file general information SF_GI includes the number of SOBIs SOBI_Ns, the number of sectors SOBU_SIZ per SOBU, and MTU_SHFT which is a type of time map information.

  Here, SOBU_SIZ describes the SOBU size in terms of the number of sectors, and this size is constant at 32 (32 sectors = 64 kbytes). This means that in each time map information (MAPL), the first entry relates to an application packet contained in the first 32 sectors of the SOB. Similarly, the second entry relates to an application packet included in the next 32 sectors. The same applies to the third and subsequent entries.

  Each SOB information search pointer (for example, SOBI_SRP # 1) includes the SOBI start address SOBI_SA. This SOBI_SA describes the start address of the related SOBI with the relative number of bytes (F_RBN) from the first byte of the stream file information SFI.

  Each SOB information (for example, SOBI # 1) includes stream object general information SOB_GI, time map information MAPL, and access unit data AUD (option).

  The stream object general information SOB_GI includes a stream object type SOB_TY, a stream object recording time SOB_REC_TM, a stream object stream information number SOB_STI_N, an access unit data flag AUD_FLAGS, a stream object start application packet arrival time SOB_S_APAT, and a stream object. End application packet arrival time SOB_E_APAT, the first stream object unit SOB_S_SOBU of the corresponding stream object, and the number of entries of time map information MAPL_ENT_Ns.

  The stream object type SOB_TY is a part that can describe a bit indicating a temporary erase state (TE state) and / or a bit of a copy generation management system.

  The stream object recording time SOB_REC_TM describes the recording time of the related stream object (SOB).

  The stream information number SOB_STI_N of the stream object describes an SOB_STI index that is valid for the stream object.

  The access unit data flag AUD_FLAGS describes whether or not access unit data (AUD) exists for the corresponding stream object, and what kind of access unit data if there is.

  If access unit data (AUD) is present, AUD_FLAGS describes some characteristics of the AUD.

  As shown in FIG. 15, the access unit data (AUD) itself includes access unit general information AU_GI, an access unit end map AUEM, and a reproduction time stamp list PTSL.

  The access unit general information AU_GI includes AU_Ns indicating the number of access units described for the SOB, and an access unit start map AUSM indicating which SOBUs belonging to the SOB include access units.

  The access unit end map AUEM is a bit array of the same length as AUSM (if any) and indicates which SOBU contains the end of the bitstream segment associated with the access unit of that SOB.

  The reproduction time stamp list PTSL is a list of reproduction time stamps of all access units belonging to the corresponding SOB. One PTSL element included in this list includes the playback time stamp (PTS) value of the corresponding access unit.

  The access unit (AU) refers to an arbitrary single continuous portion of the recorded bit stream, and is configured to be suitable for individual reproduction. For example, in an audio / video bit stream, an access unit is usually a portion corresponding to an MPEG I picture.

  Here, the description returns to the contents of SOB_GI.

  AUD_FLAGS includes a flag RTAU_FLG, a flag AUD_FLG, a flag AUEM_FLG, and a flag PTSL_FLG.

  When the flag RTAU_FLG is 0b, it indicates that there is no access unit flag in the real-time data of the SOB.

  When the flag RTAU_FLG is 1b, it indicates that the AU flags (AU_START, AU_END) described in the application header extension of FIG. 9A or 12A can exist in the real-time data of the corresponding SOB. It is. This state is allowed even when the following AUD_FLG is 0b.

  When the flag AUD_FLG is 0b, it indicates that there is no access unit data (AUD) for the corresponding SOB.

  When the flag AUD_FLG is 1b, it indicates that access unit data (AUD) may exist for the corresponding SOB.

  When the flag AUEM_FLG is 0b, it indicates that no AUEM exists in the corresponding SOB.

  When the flag AUEM_FLG is 1b, it indicates that the AUEM exists in the corresponding SOB.

  When the flag PTSL_FLG is 0b, it indicates that there is no PTSL in the SOB.

  When the flag PTSL_FLG is 1b, it indicates that PTSL exists in the corresponding SOB.

  SOB_S_APAT describes the start application packet arrival time of the stream object. That is, the first application packet arrival time belonging to the SOB is indicated by SOB_S_APAT.

  This packet arrival time (PAT) is divided into two parts: a basic part and an extended part. The basic part is a part called 90 kHz unit value, and the extended part shows a less significant value measured at 27 MHz.

  SOB_E_APAT describes the end application packet arrival time of the stream object. That is, SOB_E_APAT indicates the arrival time of the last application packet belonging to the SOB.

  SOB_S_SOBU describes the first stream object unit of the corresponding stream object. In other words, SOBU_S_SOBU indicates the SOBU including the start portion of the first application packet of the stream object.

  MAPL_ENT_Ns describes the number of entries of time map information (MAPL) following SOBI_GI.

  The time map information MAPL has contents corresponding to the time map information 252 of FIG.

Summarizing one of the relevance of the contents of FIGS. 13 and 15 is as follows:
The streamer information STRI included in the management information 105 includes a stream file information table SFIT that manages a stream object SOB that constitutes a part of the content of the stream data. This SFIT includes stream object information SOBI for managing the SOB. This SOBI includes access unit general information AU_GI including management information (access unit start map AUSM) and management information (PTSL).

  Here, the management information (ATS or AUSM) includes information used when transferring stream data, and the management information (PTS or SC_S_APAT) includes information used when displaying the stream data.

  FIG. 16 is a diagram illustrating a correspondence relationship between an access unit start map (AUSM; see FIG. 15) and a stream object unit (SOBU; see FIGS. 1, 4 to 6, and 12).

  As shown in the drawing, the bit “1” portion of the AUSM indicates that the corresponding SOBU includes an access unit (AU).

  Now, the i-th (1 ≦ i ≦ AU_Ns) bit position where the bit is set in AUSM is considered as AUSM_pos (i). Then, the position of the access unit AU is as follows.

  (1) If SOBU # i indicated by AUSM_pos (i) contains one or more starting AUs (this is described by AU_START and AU_END marks, if any) in the stream, then AUSM_pos (i) is , Assigned to the first AU starting in SOBU # i. Here, SOBU # i is arranged in SOBUs described by AUSM_pos (i) and AUEM_pos (i) (if AUEM exists).

  (2) The AU ends with the first AU_END mark that appears after this AU starts, and the AU ends with the last SOBU indicated by the assigned AUEM element (if AUEM exists).

  In any access unit data, two or more accessible access units cannot be described for each SOBU of SOB.

  FIG. 17 illustrates the correspondence relationship between the access unit start map (AUSM; see FIG. 15) and the access unit end map (AUUM; see FIG. 15) and the stream object unit (SOBU; see FIGS. 2, 4, and 11). It is a figure to do.

  AUEM is a bit array of the same length as AUSM (if present). The AUEM bit indicates in which SOBU the end of the bit stream segment attached to the access unit of the SOB is included.

  The number of bits set in AUEM matches the number of bits set in AUSM. That is, each setting bit in AUSM has a bit set correspondingly in AUEM.

  Now, the i-th (1 ≦ i ≦ AU_Ns) bit position where the bit is set in AUSM is AUSM_pos (i), and the i-th (1 ≦ i ≦ AU_Ns) bit position is set in AUEM. View as AUEM_pos (i). In this case, there is the following relationship.

(1) 1 ≦ AUSM_pos (i) ≦ AUEM_pos (i) ≦ MAPL_ENT_Ns;
(2) AUSM_pos (i + 1)> AUEM_pos (i);
(3) If i == AU_Ns or AUSM_pos (i + 1)> 1 + AUEM_pos (i), AU # i ends with SOBU # [AUUM_pos (i)] (1 ≦ i ≦ AU_Ns);
(4) If AUSM_pos (i + 1) == 1 + AUEM_pos (i), AU # i ends with SOBU # [AUUM_pos (i)]. Alternatively, the process ends at SOBU # [1 + AUEM_pos (i)] == SOBU # [AuSM_pos (i + 1)]. That is, AU # i ends at the start of AU # i + 1 in SOBU (1 ≦ i ≦ AU_Ns).

  FIG. 18 is a diagram illustrating how cells specified by an original PGC or user-defined PGC and SOBUs corresponding to these cells are related by time map information.

  The user-defined PGC does not include its own SOB, but refers to the SOB in the original PGC. Therefore, the user-defined PGC can be described only by using PGC information. This means that an arbitrary reproduction sequence can be realized without changing the SOB data.

  The user-defined PGC also includes a series of cells (chain) corresponding to a part of the program in the original PGC without including a program.

  An example of such a user-defined PGC is shown in FIG. This example shows a case where a user-defined PGC # n is created so that a cell in the PGC refers to the SOB in the original PGC.

  In FIG. 18, PGC # n has four cells # 1 to # 4. Two of them refer to SOB # 1, and the remaining two refer to SOB # 2.

  The solid line arrow from the cell in the user-defined PGC to the original PGC (to the SOBI time map information) indicates the playback period for the corresponding cell. The cell playback order in the user-defined PGC may be completely different from the playback order in the original PGC.

  The playback of an arbitrary SOB and its SOBU is specified by the start APAT (S_APAT) and the end APAT (E_APAT) in FIG.

  The SO_APAT of the SOB or SOBU is defined in relation to the time stamp recorded in the payload (see FIGS. 1 (h), 22 and 23) of the stream pack of the SOB.

  During SOB recording, each incoming application packet is time stamped by a local clock reference in the streamer. This is the application packet arrival time (APAT).

  The APAT of the first application packet of SOB is stored as SOB_S_APAT. The 4 least significant bytes of all APATs are fixed in advance for the corresponding application packet in the “˜.SRO” file.

  In order to reproduce the SOB or SOBU data, the reference clock inside the streamer is set to the SCR value, and then the clock is automatically counted. This SCR value is described in the first stream pack (pack header) where reproduction starts. Based on this clock, reproduction / output of all subsequent application packets from the SOB or SOBU is executed.

  An application packet with the desired APAT when any stream cell (SC) defines a stream cell start APAT (SC_S_APAT) with an arbitrary value between the SOB_S_APAT and SOB_E_APAT of the SOB that the SC points to An address is required to find the SOBU that contains.

  Although the number of stream packs per SOBU is constant, the interval between arrival times captured by each SOBU is flexible. Therefore, each SOB has time map information (MAPL) in which the arrival time interval of SOBU of the SOB is described. That is, the address system realized by the time map information (MAPL) points to an SOBU that can find a desired application packet by converting an arbitrary APAT into a relative logical block address in a file.

  FIG. 19 is a diagram for explaining the configuration of a stream data recording / reproducing system (optical disc apparatus / streamer, STB apparatus) according to an embodiment of the present invention. In this embodiment, it is assumed that the information storage medium 201 is a recordable / reproducible optical disc such as a DVD-RAM disc.

  The internal structure of the stream data recording / reproducing apparatus according to an embodiment of the present invention will be described below with reference to FIG.

  This stream data recording / reproducing apparatus includes an optical disk device 415, an STB device 416, and peripheral devices.

  Peripheral devices include a video mixing unit 405, a frame memory unit 406, an external speaker 433, a personal computer (PC) 435, a monitor TV 437, D / A converters 432 and 436, and I / F units 431 and 434.

  The optical disk device 415 includes a recording / playback unit 409 including a disk drive, and a data processor unit (hereinafter abbreviated as a D-PRO unit) that processes stream data to the recording / playback unit 409 (or stream data from the recording / playback unit 409). 410, a temporary storage unit 411 that temporarily stores stream data that has overflowed from the D-PRO unit 410, and an optical disc apparatus control unit 412 that controls the operations of the recording / reproducing unit 409 and the D-PRO unit 410.

  The optical disk device 415 further receives a stream data sent from the STB device 416 via the IEEE 1394 or the like (or sends stream data to the STB device 416 via the IEEE 1394 or the like), and a data transfer interface unit A formatter / deformatter unit 413 that converts the stream data received in 414 into a signal format to be recorded in an information storage medium (RAM disk) 201 (or converts stream data reproduced from the medium 201 into a signal format such as IEEE 1394); It has.

  Specifically, the IEEE 1394 receiver side of the data transfer interface unit 414 reads the time from the start of the stream data transfer based on the time count value of the reference clock generator (system time counter STC) 440.

  Based on the time information, segment information for segmenting stream data for each stream block (or for each SOBU) is created, and cell segment information and program segment information corresponding to the segment information, and also PGC segmentation. Create information.

  The formatter / deformatter unit 413 converts the stream data sent from the STB device 416 into a stream pack sequence (see FIG. 12A, FIG. 23H, etc.), and converts the converted stream pack sequence. Input to the D-PRO unit 410. The input stream pack has a constant size of 2048 bytes which is the same as the sector. The D-PRO unit 410 collects the input stream packs every 16 sectors into ECC blocks, and sends them to the recording / reproducing unit 409.

  If the recording / playback unit 409 is not ready for recording on the medium 201, the D-PRO unit 410 transfers the recorded data to the temporary storage unit 411 and temporarily stores it. Wait until recording is ready.

  When the recording / playback unit 409 is ready for recording, the D-PRO unit 410 transfers the data stored in the temporary storage unit 411 to the recording / playback unit 409. Thereby, recording on the medium 201 is started. When the data stored in the temporary storage unit 411 is recorded, the subsequent data is seamlessly transferred from the formatter / deformatter unit 413 to the D-PRO unit 410.

  Here, the temporary storage unit 411 assumes a large-capacity memory so that it can be accessed at high speed and can hold recording data of several minutes or more.

  Note that the time stamp information attached to the recording bitstream via the formatter / deformatter unit 413 can be obtained from the reference clock generator (STC) 440.

  Further, the time stamp information (SCR) extracted from the reproduction bit stream via the formatter / deformatter unit 413 can be set in the STC 440.

  A reference clock (system clock reference SCR) is recorded in the pack header in the stream data recorded in the information storage medium 201. When reproducing the stream data (SOB or SOBU) recorded on the medium 201, the reference clock generator (STC) 440 is adapted to the reference clock (SCR) reproduced from the medium 201 (the value of SCR is Set to STC440).

  That is, in order to reproduce SOB or SOBU data, the reference clock (STC 440) in the streamer (optical disc apparatus 415) is set to the system clock reference SCR described in the first stream pack from which reproduction is started. Thereafter, the STC 440 is automatically counted up.

  The STB unit 416 demodulates the contents of the digital broadcast radio wave received by the satellite antenna 421 and provides demodulated data (stream data) in which one or more programs are multiplexed, and is demodulated by the demodulator 422 And a reception information selector 423 for selecting information of a specific program (desired by the user) from data (the transport packet of program 2 if FIG. 23 described later is taken as an example).

  When the information (transport packet) of the specific program selected by the reception information selector unit 423 is recorded in the information storage medium 201, the selector unit 423 receives only the transport packet of the specific program according to the instruction of the STB control unit 404. The included stream data is sent to the data transfer interface unit 414 of the optical disc apparatus 415 by the IEEE 1394 transfer via the data transfer interface unit 20.

  When the information (transport packet) of the specific program selected by the reception information selector unit 423 is simply viewed without being recorded, the selector unit 423 performs the transport packet of the specific program according to the instruction of the STB control unit 404. Is sent to the multiplexed information separator 425 of the decoder unit 402.

  On the other hand, when the program recorded in the information storage medium 201 is played back, the stream data sent from the optical disk device 415 to the STB device 416 via the IEEE1394 serial bus is transmitted to the decoder unit 402 via the selector unit 423. It is sent to the multiplexed information separator 425.

  The multiplexed information demultiplexing unit 425 classifies various packets (video packet, audio packet, sub-picture packet) included in the stream data sent from the selector unit 423 on the internal memory unit 426 by the ID of each packet. . Then, the divided packets are distributed to the corresponding decoding units (video decoding unit 428, sub-picture decoding unit 429, and audio decoding unit 430).

  The video decoding unit 428 decodes the video packet (MPEG-encoded) sent from the multiplexed information separation unit 425 to generate moving image data. At that time, the video decoding unit 428 has a built-in representative image (thumbnail) generation unit 439 in order to have a function of generating a reduced image (thumbnail picture) representing the recorded contents from the I picture in the MPEG video data. Yes.

  The video decoded by the video decoding unit 428 (and / or the representative image generated by the generating unit 439), the sub picture (information such as subtitles and menus) decoded by the sub picture decoding unit 429, and the audio decoding unit 430 The audio decoded in step S1 is sent to the video mixing unit 405 via the video processor unit 438.

  The video mixing unit 405 uses the frame memory unit 406 to create a digital image in which captions are superimposed on a moving image. This digital video is converted into an analog video via the D / A converter 436 and sent to the monitor TV 437.

  The digital video from the video mixing unit 405 is appropriately taken into the personal computer 435 via signal lines such as the I / F unit 434 and IEEE194.

  On the other hand, the digital audio information decoded by the audio decoding unit 430 is sent to the external speaker 433 via the D / A converter 432 and an audio amplifier (not shown). The decoded audio information is digitally output to the outside via the I / F unit 431.

  The operation timing in the STB device 416 is determined by the clock from the system time counter (STC) unit 424.

  The above-described instruction or the like by the STB control unit 404 (operation control of each internal configuration of the STB device 416) is executed by a control program stored in the program memory unit 404a. At that time, the work memory unit 407 is appropriately used in the control process by the STB control unit 404.

  The timing of internal operations of the STB device 416 including the STB control unit 404 and the decoder unit 402 can be regulated by a clock from the STC unit 424. Further, by synchronizing the STC 440 of the optical disk device 415 and the STC unit 424 of the STB device 416, the operation timing of the entire streamer system including the optical disk device 415 and the STB device 416 can be regulated.

  As a method of synchronizing the STC 440 and the STC unit 424, a method of setting the STC 440 and the STC unit 424 by the reference clock (SCR) in the stream data transferred between the data transfer interface unit 414 and the data transfer interface unit 420. There is.

  Looking at the device configuration of FIG. 19 by function, the STB device 416 includes a “reception time management unit”, a “stream data content analysis unit”, a “stream data transfer unit”, and a “time related information generation unit”. Can be divided / classified.

  Here, the “reception time management unit” includes a demodulator (demodulation unit) 422, a reception information selector unit 423, a multiplexed information separation unit 425, an STB control unit 404, and the like. This “reception time management unit” receives the digital TV broadcast by the satellite antenna 421 and records the reception time for each transport packet in the received broadcast information.

  The “stream data content analysis unit” includes a multiplexed information separation unit 425, an STB control unit 404, and the like. This “stream data content analysis unit” analyzes the contents of the received stream data, and extracts the I, B, and P picture positions and / or PTS values.

  The “stream data transfer unit” includes a multiplexed information separation unit 425, a reception information selector unit 423, an STB control unit 404, a data transfer interface unit 420, and the like. The “stream data transfer unit” transfers the stream data to the optical disc device 415 while maintaining the difference reception time interval for each transport packet.

  The “time related information generation unit” includes a multiplexed information separation unit 425, an STB control unit 404, a data transfer interface unit 420, and the like. The “time-related information generation unit” includes reception time (time stamp) information recorded by the “reception time management unit”, display time information (PTS value and / or number of fields) extracted by the “stream data content analysis unit”, and Create relationship information between.

  FIG. 20 is a diagram illustrating a time relationship table showing the relationship between the display time and the data transfer time in one embodiment of the present invention. The basic features of the present invention will be described with reference to FIG.

  In the NTSC system, which is one of the TV display systems, 30 screens / pictures (frames) are displayed as video signals on the TV monitor screen per second. Since a normal TV uses an interlace method, the screen is scanned and displayed every other scanning line for all the scanning lines of one screen, and then every other shifted image is scanned. In this way, a single screen (picture) is displayed by filling the space between the previous screens. This image displayed every other line is called a field.

  In the NTSC system, 30 frames / 60 fields per second are displayed. This NTSC system is a display system mainly used in Japan and the United States. On the other hand, the PAL system mainly employed in Europe displays 25 frames / 50 fields per second.

  FIG. 20A is a diagram in which screens / pictures (frames) that change at 30 sheets per second are arranged along display time (presentation time; or reproduction time) 1.

As information indicating the display time (reproduction time) 1 of the screen / picture,
(A) a method represented by “the number of difference fields from a specific screen (picture)”;
(B) There is a method represented by “PTS (presentation time stamp; or reproduction time stamp)”.

  PTS uses a reference clock of 27 MHz and / or 90 kHz, and can be used in a method of representing a display time with a counter value that is always incremented (a counter value is incremented by 1). For example, the value of the counter when each screen / picture (frame) is indicated by a counter that is incremented by a reference clock of 27 MHz (or 90 kHz) is used as the value of PTS.

  In the received signal information in the digital TV, the PTS value for each picture is included in the picture header information 41 (see FIG. 1 (j)).

  In FIG. 20A, the display time of the I picture a is PTSNo. 1 and the display times of I pictures i and q are PTSNo. 2 and PTSNo. It is represented by 3.

  Now, for example, it is assumed that an instruction is received from the user to display a screen (picture) after hours, minutes and seconds of I picture a display. Then, the specified time interval (hours, minutes, seconds) is converted into a count value of 27 MHz and / or 90 kHz. Then, the addition result of the converted value and the PTS value (PTS No. 1) of the I picture a display can be calculated to search for a “screen to be displayed (picture)” instructed by the user.

  Since the stream data recorded on the information storage medium 201 is recorded with a time stamp added to each transport packet as shown in FIG. 1 (g) and others, this time stamp information is used. Time management is performed for stream data.

  However, since this time stamp information cannot be recognized by the user, the user designates a screen (picture) to be viewed using the display time (reproduction time) 1.

  In this case, information indicating the relationship between the time stamp information for time management of the stream data and the display time (reproduction time) 1 information that can be specified by the user is required. Information indicating this relationship is the time relationship table 2 shown in FIG. 20B (or the reproduction time stamp list PTSL in FIG. 15).

  As illustrated in FIG. 20B, the time relationship table 2 includes data transfer time information (I picture transfer start) for each PTS value (PTSNo.1, PTSNo.2, PTSNo.3,...). Time 4), data transfer time information (I picture transfer end time 5), and the total number of packets 10 from the cell head to the target I picture are described.

  For example, PTSNo. As for I picture a of 1, the time stamp (ATS) # 1 of the row of the data transfer time information (I picture transfer start time 4) is the leading packet (AP) of the I picture a information 7 of FIG. Corresponding to the time stamp (ATS) # 1 of # 1, the time stamp (ATS) # 2 in the row of the data transfer time information (I picture transfer end time 5) is the end of the I picture a information 7 of FIG. This corresponds to the time stamp (ATS) # 2 of the side packet (AP) # 2. Here, since I picture a is the first picture, PTSNo. The total number of packets 10 for one I picture a is “1” as shown in FIG.

  Similarly, PTSNo. As for I picture i of 2, the time stamp (ATS) # 3 of the row of the data transfer time information (I picture transfer start time 4) is the leading packet (AP) of the I picture i information 8 of FIG. Corresponding to the time stamp (ATS) # 3 of # 3, the time stamp (ATS) # 4 in the row of the data transfer time information (I picture transfer end time 5) is the end of the I picture i information 8 of FIG. This corresponds to the time stamp (ATS) # 4 of the side packet (AP) # 4. Here, since the I picture i is 85100 after the first I picture a, the PTS No. The total number of packets 10 for I picture i of 2 is “85101” as shown in FIG. PTS No. The same applies to 3 and after.

  An area in which management information (SFIT in FIG. 15) relating to stream data (FIG. 1 (a), FIG. 20 (c) and other STREAM.VRO 106) is recorded in the time relationship table 2 as shown in FIG. 20 (b). The feature of the present invention is that the user can specify the screen position in units of pictures for the user by using the time relation table.

  Here, the correspondence between the time relationship table 2 and the reproduction time stamp list PTSL shown in FIG. 15 will be described.

When the time stamp shown in FIG. 1 (g) and others is ATS, the PTS value included in the reproduction time stamp list PTSL in FIG. 15 and the ATS have the following relationship:
(1) A cell (stream cell) refers to a part of a recorded bit stream;
(2) AU (normal I picture) is a continuous part of the recorded bitstream (AU corresponds to part of the cell);
(3) Which SOBU includes an AU (I picture corresponding to a part of a cell) is indicated by the access unit start map AUSM in FIG. 15 (see FIG. 16);
(4) The PTS value is the playback time (display time; or presentation time PTM) of the corresponding AU (the PTS value corresponding to the AU corresponds to a part of the cell with respect to the playback time);
(5) Cell start APAT (SC_S_APAT) is the arrival time of the transport packet or application packet AP of the cell (SC_S_APAT corresponds to the value of PTS with respect to playback time);
(6) A transport packet or application packet AP is accompanied by a time stamp ATS (see FIG. 22, FIG. 29 (g), etc.);
(7) The value of PTS is included in PTSL (see FIG. 15);
(8) From (3) to (7) above, the value of PTS included in PTSL corresponds to ATS through AUSM, SC_S_APAT, and the like.

    Therefore, the reproduction time stamp list PTSL includes information (PTS value) indicating the relationship between the start time (SC_S_APAT) of the AU (I picture) and the time stamp ATS of the packet included in the bitstream (relationship regarding the reproduction time). It can be said that this is a “time relationship table (FIG. 20B)”.

    Alternatively, it can be said that PTSL (time relationship table) is information indicating the correspondence between the value of PTS and ATS.

  By the way, in order to display a B picture or a P picture, it is necessary to always start from the display (decode) of an I picture. For this reason, the time relationship table 2 shown in FIG. 20B shows the display time information corresponding to the time stamp at the I picture position as a list.

  Here, “PTS information (PTS value)”, “number of difference fields from a specific reference screen (picture)”, “year / month / day / time information”, and the like can be used as the display time information.

As display time information, instead of performing absolute value display as shown in FIG. 20B, difference information between I pictures (for example, information on the number of fields inserted between I pictures) can be used. It is. (The time relationship table using the number of fields will be described later with reference to FIG. 28.)
In FIG. 20B, “PTS information” is used as display time information. However, in various possible embodiments of the present invention, the present invention is not limited to this method. Instead, “specific reference screen (picture The number of difference fields from “)” or “date information” can be used.

  In the time relationship table 2 shown in FIG. 20B, not only the value of the transfer start time 4 for each I picture is recorded in the list as time stamps (ATS) # 1, # 3, # 5, The value of I picture transfer end time 5 is also recorded as time stamps (ATS) # 2, # 4, and # 6.

  Therefore, when performing special playback such as fast forward playback (fast forward FF) or fast reverse playback (fast reverse FR), “time stamp (ATS) # 1 to # 2”, “time stamp (ATS) # 3 From the information storage medium 201 by designating the transport packet position (or application packet position) of the I picture to be reproduced, such as “from time to # 4” and “time stamp (ATS) # 5 to # 6”. Only I picture information (or access unit AU information) can be reproduced, decoded, and displayed.

  In the embodiment of FIG. 20A, the display start picture position (position of B picture f) of the original cell (see FIG. 4) is used as a reference. A difference between the PTS value (PTS No. 5) of the display start picture of the original cell and the PTS value (PTS No. 1) of the I picture a immediately before is the PTS offset 9. The PTS offset value 9 is recorded in the original cell information 272 as shown in FIG.

  Specifically, as shown in FIG. 20A, the display start picture of the original cell is B picture f, and the PTS value at that time is PTSNo. 5 The display time of the I picture a immediately before is set to PTSNo. If it is 1, the value of the PTS offset 9 is obtained by “PTS No. 5−PTS No. 1”.

  When the user designates a specific screen (specific picture frame), it is often designated by a difference display time from the display start position of the original cell. After converting this difference display time into a counter number of 27 MHz and / or 90 kHz, by adding the value of PTS offset 9, the PTS value of the screen (picture frame) designated by the user can be calculated.

  As shown in FIG. 20B, the time relation table 2 records a list of PTS values for each I picture. With reference to this table, a PTS value at an I picture position that is smaller than the calculated PTS value and closest to the calculated PTS value is searched for, and a corresponding time stamp (ATS) value at the I picture transfer start time 4 is designated. Then, access to the information storage medium 201 is started.

  As shown in FIG. 20B, in the time relation table 2, the total number of transport packets 10 (access position information) from the original cell head position to the corresponding I picture is also recorded in parallel with the time stamp. Yes.

  Therefore, according to the embodiment of FIG. 20, the number of transport packets (or the number of application packets AP_Ns) from the original cell head position is specified instead of the time stamp (ATS), and a desired stream data position is accessed. It is also possible.

  When the stream data (STREAM.VRO) 106 in FIG. 20C is recorded on the information storage medium 201 shown in FIG. 3 and the like, the contents (SOB or SOBU) of the stream data 106 are stored in a predetermined data recording unit (transport). Packet or application packet) and recorded in the data area (STREAM.VRO / SR_TRANS.SRO) of the medium 201. At this time, management information (STRI) related to the stream data 106 is also recorded in the management area (STREAM.IFO / SR_MANGR.IFO) of the medium 201.

  First management information (ATS corresponding to the I picture transfer start time; or AUSM) used for accessing the stream data 106 (accessing to the I picture information or the access unit AU) is included in this management information (STRI); This is different from the first management information (AUSM), and indicates the relationship between the first management information and the second management information (PTS; or SC_S_APAT) used for accessing the stream data. Third management information (time relationship table; or PTSL) is recorded.

  Here, the stream data 106 is a bit stream compressed based on the MPEG standard, and the second management information corresponds to the reproduction time (PTS) of the stream data.

  FIG. 21 is a diagram illustrating the relationship between the display time and the data transfer time in one embodiment of the present invention.

  Regarding the data structure in the stream data (FIG. 1, FIG. 2 and other STREAM.VRO 106) recorded on the information storage medium 201, the recording position and stream block (SOBU) of each piece of picture information 6010-6030 will be described with reference to FIG. The arrangement relationship between the two will be described.

  In this embodiment, stream data is recorded in units of stream blocks (SOBU), and time stamp information is used to specify access to a predetermined image (picture).

  When the time stamp value is designated as the playback start position from the STB device 416 in FIG. 19, information for calculating the stream block (SOBU) corresponding to the designated time stamp value is the time in FIG. This is map information 252 (or time map information MAPL in FIG. 15 or time map information in FIG. 18).

  In the example of FIG. 3 (h), the time map information 252 includes the STREAM. It is recorded as a part of stream object information (SOBI) 242 in the IFO 105. Also in the example of FIG. 15, the time map information MAPL is recorded as a part of SOBI.

  In the time map information 252 shown in FIG. 3 (i), only the time stamp difference time information for each stream block is recorded. In this case, for each stream object information (SOBI) 242, 243, the value of the time difference 263, 265 of each stream block in the time map information 252 is sequentially added. Then, it is necessary to compare whether or not this sequential addition value has reached the time stamp time designated by the STB device 416 side. Based on the comparison result, it is determined which number of stream blocks (SOBU) in which stream object (SOB) the time specified by the STB device 416 matches with the time stamp value.

  As shown in FIG. 21C, the boundary positions of the picture information 6010 to 6030 do not necessarily match the boundary positions of the stream blocks (SOBU).

  In this case, for example, as shown in FIG. If playback is to be started from the position of P picture o, which is 6, the following processing is required.

  That is, from the time relationship table 2 in FIG. 21B (the internal configuration is the same as in FIG. 20B), the PTSNo. It is necessary to determine the value of 2 and to start playback from the head position of the stream block (SOBU) #A including the head transport packet # 2 in which the I picture i information 6010 is recorded.

  However, until reproduction proceeds from the start position of the stream block (SOBU) #A to the position of the desired P picture o, the image information during that period (from picture i to picture n in FIG. 21A) is transferred to the external monitor (TV). Not output.

  FIG. 22 is a diagram for explaining the relationship between the video information compression method in MPEG and the transport packet, and the relationship between the transport packet in MPEG and the application packet in the streamer.

  As shown in FIG. 22, a signal compression method called MPEG2 is adopted for broadcast signal information on a digital TV. In the signal compression method based on MPEG, each screen (picture) for TV display is classified into an I picture 551 that does not include time difference information, a B picture 553 and 554 that includes time difference information, and a P picture 552.

  The I picture exists alone without being affected by the preceding and following screen (picture) information, and after DCT conversion is performed on one screen (picture), the quantized information becomes the I picture compression information 561, and the I picture information Recorded as 31. In the P picture 552, only the difference information 562 for the I picture 551 is recorded as the P picture information 32, and in the B pictures 553 and 554, the difference information for the I picture 551 and the P picture 552 is recorded as the B picture information 33 and 34.

  Therefore, at the time of video reproduction, a screen cannot be generated with the P picture 552 and the B pictures 553 and 554 alone, and each picture screen can be generated only after the I picture 551 screen is generated. Each picture information 31 to 34 is divided and recorded in a payload in one or a plurality of transport packets. At this time, the boundary positions of the picture information 31 to 34 and the boundary positions between the transport packets are recorded so as to always coincide.

  When the transport packet of FIG. 22 is recorded on the streamer (the optical disk device 415 of FIG. 19), the content of the transport packet is transferred to a packet with a time stamp (application packet) called an application time stamp (ATS).

  A group of application packets with ATS (usually around 10 packets) is stored in the application packet area in the stream PES packet.

  The stream PES packet with a pack header is one stream pack.

  A stream PES packet is composed of a PES header, a substream ID, an application header, an application header extension (option), a stuffing byte (option), and an application packet area for storing the application packet group with the ATS. The

  FIG. 23 is a diagram for explaining the correspondence between digital broadcast content, video data transfer form in IEEE 1394, and stream packs in a streamer.

  In digital broadcasting, video information compressed in accordance with the MPEG2 standard is transferred on transport packets. As shown in FIG. 23B, the transport packet includes a transport packet header 511 and a payload 512 in which a data body of recording information is recorded.

  As shown in FIG. 23A, the transport packet header 511 includes a payload unit start indicator 501, a packet ID (PID) 502, a random access indicator 503, a program clock reference 504, and the like.

  The MPEG-compressed video information includes I picture information, B picture information, and P picture information. In the first transport packet in which the I picture information is recorded, a flag “1” is set in the random access indicator 503 in FIG. In the first transport packet of each B and P picture information, a flag “1” is set in the payload unit start indicator 501 of FIG.

  Using the information of the random access indicator 503 and the payload unit start indicator 501, the I picture mapping table (641 in FIG. 9E) and the B and P picture start position mapping table (642 in FIG. 9E) Is created.

  For example, for the transport packet in which the payload unit start indicator 501 shown in FIG. 23A is flagged as “1”, the B and P picture start position mapping table (642 in FIG. 9E) The bit at the corresponding location becomes “1”.

  In digital broadcasting, video information and audio information are transferred in different transport packets. Each information is identified by a packet ID (PID) 502 in FIG. Using this PID 502 information, a video packet mapping table (643 in FIG. 9E) and an audio packet mapping table (644 in FIG. 9E) are created.

  As shown in FIG. 23 (c), in digital broadcasting, a plurality of programs (in this example, programs 1 to 3) are time-divided and transferred to one transponder in a packetized form.

  For example, the information of the transport packet header 511 and the payload (recording information) 512 of FIG. 23B is transferred by the transport packets b · 522 and e · 525 of the program 2 shown in FIG.

  For example, when the user intends to record the second program shown in FIG. 23 (c) in the information storage medium 201, the reception information selector 423 in the STB device 416 shown in FIG. , E are extracted.

  At that time, as shown in FIG. 23D, the STB device 416 adds the time information when the transport packets b522 and e525 are received in the form of time stamps 531 and 532, respectively.

  After that, when data is transferred to the formatter / deformatter unit 413 in FIG. 19 using the IEEE 1394 transfer method, the set of the time stamp and the transport packet is finely divided as shown in FIG. Will be transferred.

  In the formatter / deformatter unit 413 of FIG. 19, the stream data transferred by the IEEE 1394 from the STB device 416 is temporarily returned to the form of FIG. 23 (d) (corresponding to the form of FIG. 1 (g)). Then, a bit stream in the format of FIG. 23D (stream pack sequence of FIG. 23H) is recorded in the information storage medium 201.

  Specifically, in one embodiment of the present invention, a pack header in which system clock information and the like are recorded and a PES header are arranged at the head of each sector (see FIG. 23 (h) and the like).

  A plurality of time stamps and transport packets (FIG. 1 (g)) are sequentially packed in the data areas 21, 22, 23 (FIG. 1 (f)), but one transport packet (FIG. 1 (g)) Packet d; packet 2 of program 2 in FIG. 23 (d) is recorded across a plurality of sectors (No. 0 and No. 1 in FIG. 1 (e); partial packets in FIGS. 23 (f) and 23 (g)). Is done. This is one of the features of the present invention.

  By using a data structure that makes use of this feature, a packet having a size larger than the sector size (for example, 2048 bytes) can be recorded. This point will be further described.

  In digital broadcasting, as shown in FIG. 23 (c), a multiplexing / demultiplexing method corresponding to a multi-program called a transport stream is adopted, and the size of one transport packet b · 522 is 188 bytes (or 183 bytes). In many cases.

  As described above, the size of one sector is 2048 bytes, and even if various header sizes are subtracted, 10 transport packets for digital broadcasting are included in one data area 21, 22, 23 (FIG. 1 (f)). You can record back and forth.

  On the other hand, in a digital communication network such as ISDN, a large long packet having a packet size of 4096 bytes may be transferred.

  In the case of a packet having a large packet size such as a long packet as well as recording a plurality of transport packets in one data area 21, 22, 23 (FIG. 1 (f)) as in digital broadcasting However, by using a data structure that makes the best use of the above characteristics (characteristic that can record data of one packet across a plurality of packets), one packet can be continuously recorded in a plurality of data areas 21, 22, and 23. Record to straddle.

  By doing so, transport packets for digital broadcasting, long packets for digital communication, and the like can be recorded without any fraction in the stream block without depending on the packet size.

  In addition, time stamps are attached to normal packets, but time stamps can be omitted from partial packets as shown in FIG.

  In this way, the partial packet divided at the boundary between two adjacent stream packs (FIG. 23 (h)) (if the packet is 188 bytes, the size of the partial packet is 1 to 187 bytes; on average, 100 bytes Can be used effectively for information recording. In addition, the storage capacity for the medium 201 can be increased by the time stamp omitted for the partial packet (for example, 4 bytes per time stamp).

  Note that the position of the time stamp immediately after the first partial packet in FIG. 23G can be specified by the first access point 625 in FIG. 10B or FIRST_AP_OFFSET in FIG. 10C.

  In the optical disk device 415 (streamer) of FIG. 19, a set of time stamps and transport packets (FIGS. 23 (f) and (g)) is recorded on the information storage medium 201 as it is.

  FIG. 24 is a flowchart for explaining a stream data recording procedure according to one embodiment of the present invention. The processing at the time of recording stream data will be described with reference to FIG. This processing can be executed by a processing program stored in the program memory unit 404a of the STB control unit 404 shown in FIG.

  As shown in FIG. 23 (c), a plurality of program information is time-division multiplexed in one transponder.

  In the reception information selector unit 423 of FIG. 19, a transport packet for only a specific program is extracted from the packet sequence of the multiple program information that has been time-division multiplexed (step S01).

  In the “reception time management unit (demodulation unit 422, reception information selector unit 423, multiplexed information separation unit 425, STB control unit 404, etc. in FIG. 19)”, necessary program information is stored in the memory unit of the multiplexed information separation unit 425. It is temporarily stored in 426 (step S02).

  At the same time, the reception time for each transport packet is measured, and the measured value is added to each transport packet (or application packet) as a time stamp (ATS) as shown in FIG. . The time stamp information added in this way is recorded in the memory unit 426 (step S03).

  Next, in the “stream data content analysis unit (multiplexed information separation unit 425, STB control unit 404, etc. in FIG. 19)”, the information in the transport packet (application packet) recorded in the memory unit 426 is analyzed. The

  Specifically, each picture boundary position is cut out from the transport packet (application packet) sequence, and PTS information (or corresponding field number information) is extracted from the picture header information 41 for each packet ( Step S04).

  Here, there are two methods for extracting each picture boundary position, and which method is selected depends on the contents of the stream data.

  The first picture boundary position extraction method detects the I picture position by detecting the flag of the random access indicator 503 (FIG. 23A) in the transport packet header 511 (FIG. 23B), and the payload. This is a method of detecting the B or P picture position from the flag detection of the unit start indicator 501 (FIG. 23A).

  The second picture boundary position extraction method extracts the picture identification information 52 (FIG. 1 (k)) and the PTS information 53 (FIG. 1 (k)) in the picture header information 41 (FIG. 1 (j)). Is the method.

  After the above processing (steps S01 to S04), the “time-related information generation unit (multiplexed information separation unit 425, STB control unit 404, data transfer interface unit 420, etc. in FIG. 19)” uses a time stamp (ATS). As a list showing the relationship between the PTS value and the PTS value, the time relationship table 2 as shown in FIG. 20B (or the reproduction time stamp list PTSL in FIG. 15) is created, and the work memory in the STB control unit 404 is created. This is recorded in the unit 407 (step S05).

  Thereafter, while maintaining the reception time interval in the STB device 416 and the optical disc device 415 (that is, keeping the relationship between the change in the count value of the STC 440 and the change in the count value of the STC 424 in FIG. 19), the multiplexed information separation unit Packet data (stream data) temporarily stored in the memory unit 426 of 425 is transferred to the optical disk device 415 (step S06).

  Thus, the stream data temporarily stored in the memory unit 426 is recorded on the information storage medium 201 by the optical disk device 415 (step S07).

  Until the stream data transfer to the optical disc apparatus 415 is completed (NO in step S08), the processes in steps S06 to S07 are repeated.

  When the stream data transfer to the optical disk device 415 is completed and the recording process is completed (Yes in step S08), the time relation table 2 (or the reproduction time stamp list PTSL) temporarily recorded in the work memory unit 407 of the STB control unit 404. Is transferred to the optical disc device 415 (step S10).

  Then, the information of the time relation table 2 (or the reproduction time stamp list PTSL) is recorded in the management information recording area (STREAM.IFO) 105 of the information storage medium 201 (step S11).

  During the process of step S11, the recording time of the stream object (SOB_REC_TM in FIG. 7 (i)), which is the content of the recorded stream data, is converted into the time zone (TM_ZONE) in the management information recording area (STREAM.IFO) 105. 6240 (can be recorded in FIG. 7H).

  By the way, there are cases where encrypted stream data is recorded for the purpose of protecting the copyright of the content provider when recording the stream data. When encryption is performed in this way, all transport packets are encrypted and time stamp transfer processing between the STB device 416 and the optical disk device 415 is prohibited. In this case, when recording (encrypted) stream data on the information storage medium 201, it is necessary to add a time stamp uniquely on the optical disc apparatus 415 side.

  The STB device 416 side in FIG. 19 performs reception time management for each transport packet (application packet). In this case, a countermeasure against the deviation of the reference clock frequency (specifically, synchronization of the reference clock) is an important issue between the STB device 416 side and the optical disc device 415 side. Therefore, a recording process for encrypted stream data will be described below.

  FIG. 25 is a flowchart for explaining a recording procedure of encrypted stream data according to one embodiment of the present invention. This processing procedure can be executed by a processing program stored in the program memory unit 404a of the STB control unit 404 shown in FIG.

  First, it is checked whether the time relationship table 2 (FIG. 20B) or the reproduction time stamp list PTSL (FIG. 15) exists in the work memory 407 of the STB control unit 404 of FIG. 19 (step S50).

  If there is no time relationship table (or PTSL) (NO in step S50), a time relationship table (or PTSL) is created by the same processing as steps S04 to S05 in FIG. 24 (step S52).

  After the time relationship table (or PTSL) is created in this way, or when the time relationship table (or PTSL) is already in the work memory 407 of the STB control unit 404 (Yes in step S50), the STB device 416 to the optical disk device 415 (Encrypted) stream data is transferred, and this stream data is recorded in the information storage medium 201 (step S51).

  Until the recording of the (encrypted) stream data is completed (No at Step S53), the process at Step S51 is continued. This stream data recording step S51 has the same processing contents as steps S01 to S03 and S06 in FIG.

  Note that the process of step S52 may be executed in parallel with the process of step S51.

  When the recording of the (encrypted) stream data is completed (Yes in step S53), a reference clock synchronization process is executed between the STB device 416 and the optical disk device 415 (step S54).

  This reference clock synchronization processing can be performed, for example, as follows.

  That is, every time a specific number (for example, 10,000 or 100,000) transport packets (application packets) are transmitted / received at the time of stream data transfer, the transmission / reception times of the STB device 416 and the optical disk device 415 are used as work memories. Section 407 and temporary storage section 411.

  Thereafter, a transmission time list is sent each time a specific number of transport packets (application packets) are transmitted from the STB device 416 side to the optical disc device 415 side. Then, on the optical disc apparatus 415 side, the sent list is compared with the list created in advance on the optical disc apparatus 415 side, thereby calculating the reference clock synchronization deviation amount between them.

  Thereafter, the time relationship table 2 (or PTSL) is transferred from the STB device 416 to the optical disk device 415 (step S55).

  The time relationship table 2 (or PTSL) thus transferred from the STB device 416 to the optical disk device 415 is corrected based on the reference clock synchronization shift amount information calculated in the reference clock synchronization processing in step S54 (step S54). S56).

  The time relationship table 2 (or PTSL) thus corrected by the amount of reference clock synchronization deviation is recorded in the management information area (STREAM.IFO 105 in FIG. 3E; or SFIT in FIG. 15) of the information storage medium 201. (Step S57).

  By doing so, it becomes possible to record / reproduce stream data (in an encrypted state).

  Instead of the above-described “correction of reference clock synchronization deviation with respect to encrypted stream data” method, the following method may be used as another method.

  That is, as shown in FIG. 20B, the number of transport packets transferred between each I picture is recorded in the time relation table 2. Then, instead of designating the time stamp value of the playback start screen (as a picture designation method), the total number of transport packets (or application packets) from the beginning of the cell is designated.

  In this case, as information in the time map information 252, the number of transport packets (or the number of application packets) included in each stream block as shown in FIG. 11 instead of the data structure shown in FIG. AP_Ns) 633.

  When the total number of transport packets (total number of application packets) is specified from the STB device 416 side to access a predetermined screen (picture), the optical disk device 415 sequentially transfers from the first stream block shown in FIG. The number of port packets (application packets) 633 is incremented, and access is made to the stream block (or SOBU) at the time when the addition result reaches a designated value.

  FIG. 26 is a flowchart for explaining a stream data reproduction procedure according to an embodiment of the present invention. This processing procedure can be executed by a processing program stored in the program memory unit 404a of the STB control unit 404 shown in FIG. Hereinafter, the reproduction step of stream data will be described with reference to FIG.

  The user can specify the desired playback start time and / or playback end time in the form of “difference time (how many hours and minutes and seconds) based on the display start time of the specified original cell”. The STB control unit 404 in the STB device 416 receives the specified playback start time and playback end time, for example, specified in this way (step S21).

  In the STB control unit 404, the received time information of the reproduction start time and the reproduction end time is converted into a clock count value of 27 MHz and / or 90 kHz, and a differential PTS value from the display start time of the original cell is calculated. .

  The STB control unit 404 controls the optical disk device 415 to read the time relationship table 2 (or PTSL) recorded in the stream data management information recording area (STREAM.IFO 105) and temporarily record it in the work memory unit 407 ( Step S22).

  Further, the STB control unit 404 controls the optical disc device 415 to read the information of the time map information 252 (or MAPL) recorded in the stream data management information recording area (STREAM.IFO 105), and stores it in the work memory unit 407. Temporary recording is performed (step S23).

  Next, the value of the PTS offset 9 shown in FIGS. 3 (h) and 20 (a) is read, and the display start time of the corresponding original cell (corresponding to B picture f in FIG. 20 (a)) and the immediately preceding time are displayed. The difference from the display time of the I picture a (PTS No. 5 -PTS No. 1 in FIG. 20A) is examined (step S24).

Further, the value of the PTS offset 9 shown in FIGS. 3 (h) and 20 (a) is read,
(A) the value (PTS offset 9);
(B) PTS value (PTS No. 1) at the I picture-a position immediately before the display start time of the original cell (PTS No. 1) (As shown in FIG. 20A, the display start picture f of the original cell is immediately after the I picture a. If)
(C) The difference PTS value (PTSNo.5-PTSNo.1) checked in step S24 is added to calculate the reproduction start time and the reproduction end time PTS value designated by the user (step S25).

  Next, the PTS value of the I picture i immediately before the reproduction start location designated by the user and the value of the time stamp # 2 are checked using the time relationship table 2 (step S26), and notified to the optical disk device 415.

  The optical disc apparatus starts from the data of the time map information 252 shown in FIG. 3 (h) (FIG. 3 (i)) and includes a stream block (SOBU) including the head position of the I picture i information 6010 (FIG. 21 (c)). ) The value of the first time stamp (ATS) # 1 of #A is examined, and the location (address) of the first sector # α to be accessed is determined (step S27).

  Based on the address thus determined, the optical disc apparatus 415 reproduces information from the transport packet (AP) # 1 in FIG. 21C from the information storage medium 201 (step S28).

  Next, the STB control unit 404 in FIG. 19 notifies the decoder unit 402 of the PTS value (PTS No. 6 in FIG. 21A) indicating the display start time of the information started to be reproduced in step S28 (step S29). ).

  Along with this notification, the optical disc apparatus 415 transfers the information that has been reproduced in step S28 to the STB apparatus 416 side (step S30).

  Subsequently, the STB control unit 404 reads the picture identification information 52 (FIG. 1 (k)) from the memory 426 in the decoder unit 402, and inputs the I picture (part of the information transferred from the optical disc device 415). The previous data is discarded (or ignored) (step S31).

  Next, the video decoding unit 428 in FIG. 19 starts decoding from the head position of the I picture (I picture i in FIG. 21A) input in step S31, and the PTS value designated by the notification in step S29. Display (video output) is started from (PTS No. 6 in FIG. 21A) (step S32).

  Thereafter, the same processing as steps S24 to S28 is repeated, the address on the information storage medium 201 corresponding to the reproduction end time is checked, and the reproduction is continued until the end address corresponding to the reproduction end time (step S33).

  At the stage where the above-described series of playback is completed, the video manager information in the management information recording area (STREAM.IFO 105 shown in FIG. 7 (e)) is obtained using the playback end position information 6110 shown in FIG. 7 (g) as resume information. 231 (FIG. 7F).

  As the data content of the reproduction end position information 6110, as shown in FIG. 7 (h), the corresponding PGC number 6210, the cell number 6220 therein, and the reproduction end position time information 6230 are recorded.

  Although the time information 6230 is recorded as a time stamp value, the PTS value (or the total number of fields from the cell playback head position) can also be recorded as the time information 6230.

  When the reproduction end position information is started again from the position of the (resume) information 6110, the reproduction start position can be obtained by the process shown in FIG.

  At the time of standard reproduction as described above with reference to FIG. 26, the count value of the STC unit 424, which is the reference clock generation unit in the STB device 416, is the value of the DTS (decode time stamp) information 54 shown in FIG. From the time when the decoder unit 402 starts decoding.

  FIG. 27 is a flowchart for explaining the special reproduction procedure of stream data according to the embodiment of the present invention. This processing procedure can be executed by a processing program stored in the program memory unit 404a of the STB control unit 404 shown in FIG.

  When special playback such as fast forward playback (fast forward FF) or fast reverse playback (fast reverse FR) is performed, only I picture information recorded on the information storage medium 201 is extracted and played back and decoded.

  In this case, “special playback mode setting” is set to the decoder unit 402 so that the STC unit 424 (FIG. 19) and the DTS information 54 (FIG. 1 (k)) are out of synchronization and decoded in the free mode. This is performed (step S41).

  Also during special playback, the information of the time relationship table 2 and the time map information 252 is read from the management information recording area (STRAM.IFO) 105 of the information storage medium 201 and recorded in the work memory unit 407 of the STB control unit 404 (step) S42).

  Next, the time map information 252 of the stream object information (SOBI) 242 corresponding to the corresponding reproduction start location is read and temporarily recorded in the work memory unit 407 in the STB control unit 404 (step S43).

  Next, the time stamp value of the start time / end time at each I picture position (position of each AU # in the example of FIG. 16) is extracted from the time relation table 2 (step S44).

  Next, the stream block (SOBU) including the time stamp value of the corresponding I picture is checked from the time map information 252, and the address of the head sector is checked (step S45).

  For example, during special playback, only I picture information 6010 to 6050 in FIG. 28B described later is decoded and displayed. The positions of the I picture information 6010 to 6050 can be obtained by using the information in the time relationship table 2 and the time map information 252.

  Next, the optical disc device 415 reproduces information in the Zen stream block (SOBU) including each I picture on the information storage medium 201 and transfers the reproduced information to the memory unit 426 in the multiplexed information separation unit 425. (Step S46).

  Next, in the decoder unit 402 of FIG. 19, the picture identification information 52 (FIG. 1 (k)) in the data transferred to the memory unit 426 of the multiplexed information demultiplexing unit 425 is read. Data other than pictures is discarded (step S47).

  That is, in step S47, only I picture information is extracted from the reproduced / transferred stream data using the picture identification information 52, and only the I picture information extracted by the video decoding unit 428 is decoded.

  Next, the I picture data selected (that is, not discarded) in the memory unit 426 of the multiplexed information separation unit 425 in the decoder unit 402 is transferred to the frame memory unit 406 (step S48).

  The I picture data thus transferred to the frame memory unit 406 is sequentially displayed on the display screen of the TV (or video monitor) 437 (step S49).

  FIG. 28 is a diagram for explaining a time relationship table showing the relationship between the display time and the data transfer time in another embodiment of the present invention.

  In the embodiment of FIG. 20, the absolute value is displayed as the display time information as shown in FIG. 20B, but instead, the difference information between each I picture (for example, inserted between each I picture) It is also possible to use field number information).

  In FIG. 20B, “PTS information” is used as display time information. However, in various possible embodiments of the present invention, the present invention is not limited to this method. Instead, “specific reference screen (picture The number of difference fields from “)” or “date information” can be used. An example of this case is the time relationship table 6 of FIG.

  As shown in FIG. 28B, each group of pictures (GOP) indicates a group of pictures from a certain I picture position to the head of the next I picture. In the data structure of the time relationship table 6 shown in FIG. 28C, the number of display fields for each GOP is recorded as display time information.

  Also, the number of stream blocks (SOBU) occupied for each GOP is described in the time relationship table 6. By doing so, without using the time map information 252 shown in FIG. 3 (h), directly from the given display time information to the stream block (SOBU) in which the head position of the I picture information is recorded. Can be accessed.

  At the boundary position between GOP # 2 and GOP # 3 in the example of FIG. 28 (b), the GOP switching position and the stream block (SOBU) switching position are the same. As described above, when the boundary of the adjacent GOP and the boundary of the adjacent SOBU coincide with each other, the GOP end matching flag in the time relationship table 6 shown in FIG. 28C is set to “1”. This improves the identification accuracy of the stream block position (SOBU position) including the I picture information head position.

  Further, since the rear end position of the I picture information is used at the time of the special reproduction such as FF or FR described above, the time relation table 6 in FIG. 28C also includes I picture size information in each GOP. Yes.

  FIG. 29 is a diagram for explaining how a packet (AP) in stream data (SOBU) is reproduced in an embodiment of the present invention.

  29 exemplifies a case where the stream blocks ## 1, # 2,... In FIG. 1C are all configured with SOBUs # 1, # 2,... Having a constant size (2 ECC block size).

  FIG. 29 (f) shows the first sector No. of SOBU # 1. 0 (FIG. 29 (e)) and the last sector number of SOBU # 2 adjacent to SOBU # 1. 63 shows the data structure of 63 (FIG. 29E). Although not shown, sector no. 0 to sector no. 62 has a similar concept.

  As shown in FIG. The system clock reference SCR is recorded in the pack header of the stream pack corresponding to 0, and the sector number. The system clock reference SCR is also recorded in the pack header of the stream pack corresponding to 63.

  Now, it is assumed that a picture to be reproduced (a picture designated by the user with a reproduction time) exists in the middle of SOBU # 2 (in FIG. 16, for example, the position indicated by AU # 1). The picture specified by the user in the playback time corresponds to the cell start application packet arrival time SC_S_APAT.

  In this case, the disk drive (not shown) included in the recording / playback unit 409 in FIG. 19 cannot directly access the middle of SOBU # 2, but accesses the boundary position between SOBU # 1 and SOBU # 2. Then, the reproduction of the stream data (STREAM.VRO) 106 in FIG. 29A starts from the boundary position between SOBU # 1 and SOBU # 2.

  The interval from the boundary position between SOBU # 1 and SOBU # 2 to the playback start position (position corresponding to SC_S_APAT) corresponds to the PTS offset 9 described in FIG.

  The application packet existing between the boundary position between SOBU # 1 and SOBU # 2 and the playback start position (position corresponding to SC_S_APAT) is decoded but not played back (not displayed on the screen). This corresponds to the process of step S31 in FIG.

  FIG. 29 (g) illustrates that the PTS information (PTS value or PTS offset) and the application packet AP to be reproduced are related by the time relationship table 2 of FIG. 20 (a). is there.

  Here, the relationship between the time relationship table and the reproduction time stamp list PTSL shown in FIG. 15 is organized again.

When the time stamp shown in FIG. 1 (g) and others is ATS, the PTS value included in the reproduction time stamp list PTSL in FIG. 15 and the ATS have the following relationship:
(1) A stream cell refers to a part of a recorded bit stream;
(2) AU (normal I picture) is a continuous part of the recorded bitstream (AU corresponds to part of the cell);
(3) Which SOBU includes an AU (I picture corresponding to a part of a cell) is indicated by AUSM (see FIG. 16);
(4) The PTS value is the playback time (display time; or presentation time PTM) of the corresponding AU (the PTS value corresponding to the AU corresponds to a part of the cell with respect to the playback time);
(5) Cell start APAT (SC_S_APAT) is the arrival time of the application packet AP of the corresponding cell (SC_S_APAT corresponds to the value of PTS with respect to playback time);
(6) The application packet AP is accompanied by a time stamp ATS (see FIG. 29 (g), etc.);
(7) The value of PTS is included in PTSL (see FIG. 15);
(8) From the above, the value of PTS included in PTSL corresponds to ATS through AUSM, SC_S_APAT, and the like.

    Therefore, the reproduction time stamp list PTSL includes information (PTS value) indicating the relationship between the start time (SC_S_APAT) of the AU (I picture) and the time stamp ATS of the packet included in the bitstream (relationship regarding the reproduction time). It includes a “time relationship table (FIG. 20B)”.

    Alternatively, it can be said that PTSL (time relationship table) is information indicating the correspondence between the value of PTS and ATS.

Finally, the meaning of some terms used in the description of each embodiment is summarized:
* Stream object (SOB) indicates data of a recorded bit stream. SR_TRANS. A maximum of 999 SOBs can be recorded in the SRO file.

  * A stream object unit (SOBU) is a basic unit organized in an SOB. That is, each SOB consists of a series (chain) of SOBUs. In particular, after editing, the SOBU at the beginning and / or end of the SOB may include data that does not belong to the valid portion of the SOB.

  The SOBU is not characterized by playback time or playback order, but by a fixed size (size for 32 sectors or size for 2 ECC blocks).

  * Access unit (AU) refers to any single continuous portion of a recorded bitstream suitable for individual playback. This AU usually corresponds to an I picture in an MPEG encoded bit stream.

  * The access unit start map (AUSM) indicates which SOBU of the SOB includes AU.

  * An application packet (AP) is a part of a bit stream coming from an application device during recording. Alternatively, the AP is part of a bitstream that goes to the application device during playback. These APs are included in the multiplexed transport and have a certain size (maximum 64574 bytes) during recording.

  * The application time stamp (ATS) is arranged in front of each AP and is composed of 32 bits (4 bytes). The ATS is composed of a basic part of 90 kHz and an extended part of 27 MHz.

  * A cell (or stream cell SC) is a data structure indicating a part of a program. Cells in the original PGC are called original cells, and cells in the user-defined PGC are called user-defined cells. Each program in the program set consists of at least one original cell. Each part of the program in each playlist consists of at least one user-defined cell. In the streamer, the simple cell means a stream cell (SC). Each SC refers to a part of the recorded bit stream.

  * The cell number (CN) is a number (1 to 999) assigned to a cell in the PGC.

  * Stream cell entry point information (SC_EPI) is used as a tool for skipping a part of the recording, and can exist in any stream cell (SC).

  * The start application packet arrival time (SOB_S_APAT) of the stream object indicates the arrival time of the first AP belonging to the SOB. This arrival time is composed of a basic part of 90 kHz and an extended part of 27 MHz.

  * The end application packet arrival time (SOB_E_APAT) of the stream object indicates the arrival time of the last AP belonging to the SOB.

  * The start application packet arrival time (SC_S_APAT) of the stream cell indicates the arrival time of the first AP belonging to the corresponding SC.

  * The end application packet arrival time (SC_E_APAT) of the stream cell indicates the arrival time of the last AP belonging to the corresponding SC.

  * Navigation data is data used when controlling recording, reproduction, and editing for a bit stream (SOB).

  * Playlist (PL) is a list of program parts in which the user can arbitrarily define the playback sequence. PL is described as a user-defined PGC.

  * A program (PG) is a logical unit of recorded content that is recognized or defined by the user. A program in a program set consists of one or more original cells. The program is defined only in the original PGC.

  * The program chain (PGC) is a superordinate conceptual unit. In the case of the original PGC, the PGC indicates a chain (chain) of programs corresponding to the program set. On the other hand, in the case of a user-defined PGC, the PGC corresponds to a playlist and indicates a series (chain) of a part of the program.

  * Program chain information (PGCI) is a data structure indicating the overall reproduction of PGC. PGCI is used for both original PGC and user-defined PGC. The user-defined PGC is composed only of PGCI, and its cell refers to the SOB in the original PGC.

  * The program chain number (PGCN) is a serial number (1 to 99) assigned to the user-defined PGC.

  * The program number (PGN) is a serial number (1 to 99) assigned to the program in the original PGC.

  * The program set refers to the entire recorded contents of a disc (recording medium) composed of all programs. If editing is not performed for any program that changes the playback order with respect to the original recording, the same playback order as the recording order of the program is used for playback of the program set.

  * Real-time recording means that if the buffer memory size is limited, the buffer memory will overflow as long as any stream data encoded at the limited transfer rate is transferred at the limited transfer rate. The recording means that the stream data can be recorded on a disc (recording medium).

The effects of each embodiment according to the present invention are summarized as follows:
1. Information (time relationship table or PTSL) indicating the relationship between the time stamp data (ATS) recorded in the stream data and the display time information (PTS or field information) for the user is part of the management information (SFIT). By providing this, reproduction / screen display can be started from the display time designated by the user with high accuracy.

  2. At the time of editing, the user designates a partial deletion range or rearrangement designation range of recorded stream data by a display time on the monitor TV.

  As described in “1.”, the stream data has a time relationship table (or PTSL) indicating the relationship between the time stamp data and the display time information as part of the management information (SFIT). This makes it possible to accurately set the edit point position (partial deletion range or rearrangement designation range) using this time relationship table (or PTSL). As a result, time management for stream data can be performed using time stamp data (ATS), and accurate editing processing according to a user request can be guaranteed.

  3. As described in “1.” above, since the time-related table (or PTSL) is provided in the stream data, either the time stamp data (ATS) or the display time information (PTS) is used as the reproduction end position. By simply describing it as information (resume information), it is possible to accurately set the playback start position (resume playback start position) when the streamer is restarted.

  4). By recording the playback end position information (resume information) as time stamp data (ATS), when accessing a specific position on the information storage medium, the time map information 252 can be used to quickly know the address to be accessed. it can.

  5). The compressed data by MPEG always needs to start reproduction from the I picture. By recording information (time relationship table) indicating the relationship between time stamp data (ATS) and display time information (PTS or field information) at the start position of each I picture (or the start position of the access unit AU) The access control to the desired I picture (desired AU) can be performed at high speed using the time map information 252.

  6). By recording information (time relationship table) indicating the relationship between time stamp data (ATS) and display time information (PTS or field information) at each I picture start position (start position of each AU), time is recorded. In combination with the map information 252, the address of the stream block (or SOBU) position including the I picture (AU) is known. For this reason, special reproduction processing such as fast forward FF or fast reverse FR for reproducing / displaying only the I picture can be performed.

  The present invention is not limited to the above-described embodiments, and various modifications and changes can be made without departing from the scope of the invention at the stage of implementation. In addition, the embodiments may be implemented in appropriate combination as much as possible, and in that case, the effect of the combination can be obtained.

  Further, the above embodiments include inventions at various stages, and various inventions can be extracted by appropriately combining a plurality of constituent elements disclosed in this application. For example, even if one or more constituent requirements are deleted from all the constituent requirements shown in the embodiment, when at least one of the effects of the present invention or the effects of implementing the present invention is obtained, The deleted configuration can be extracted as an invention.

The figure explaining the data structure of the stream data which concerns on one embodiment of this invention. The figure explaining the directory structure of the data file which concerns on one embodiment of this invention. The figure explaining the recording data structure (especially structure of management information) on the information medium (DVD recording / reproducing disc) concerning one embodiment of this invention. The figure explaining the relationship between the stream object (SOB), cell, program chain (PGC), etc. in this invention. The figure explaining the contents of the stream block size, the stream block time difference, etc. in time map information. The figure explaining the cell range designation | designated method in an original cell and a user-defined cell. The figure explaining the recording data structure (especially structure of reproduction end position information / resume information, VMGI management information / recording time information etc.) on the information medium (DVD recording / reproducing disc) concerning other embodiment of this invention. The figure explaining the internal structure of the PES header shown by FIG. 1 others. The figure explaining the internal structure of the stream block header shown by FIG. The figure explaining the internal structure of the sector data header shown by FIG. The figure explaining the other example of the time map information in one embodiment of this invention. The figure explaining an example of the internal structure (The stream pack containing an application packet and the stream pack containing a stuffing packet) of the sector which comprises a stream block (SOBU). The figure explaining the internal data structure of streamer management information (corresponding to STREAM.IFO or SR_MANGR.IFO in FIG. 2). The figure explaining the internal data structure of PGC information (ORG_PGCI / UD_PGCIT of FIG. 3 or PGCI # i of FIG. 13). The figure explaining the internal data structure of a stream file information table (SFIT). The figure which illustrates the correspondence of an access unit start map (AUSM) and a stream object unit (SOBU). The figure which illustrates the correspondence of an access unit start map (AUSM) and an access unit end map (AUUM), and a stream object unit (SOBU). The figure which illustrates how the cell designated by original PGC or user-defined PGC, and SOBU corresponding to these cells are related by time map information. The figure explaining the structure of the stream data recording / reproducing system (optical disc apparatus / streamer, STB apparatus) concerning one embodiment of this invention. The figure explaining the time relationship table which shows the relationship between display time and data transfer time in one embodiment of this invention. The figure explaining the relationship between display time and data transfer time in one embodiment of this invention. The figure explaining the relationship between the video information compression method in MPEG and a transport packet, and the relationship between the transport packet in MPEG and the application packet in a streamer. The figure explaining the correspondence of the content of digital broadcasting, the video data transfer form in IEEE1394, and the stream pack in a streamer. The flowchart figure explaining the recording procedure of the stream data which concerns on one embodiment of this invention. The flowchart figure explaining the recording procedure of the encrypted stream data based on one embodiment of this invention. The flowchart figure explaining the reproduction | regeneration procedure of the stream data which concerns on one embodiment of this invention The flowchart figure explaining the procedure of the special reproduction | regeneration of the stream data which concerns on one embodiment of this invention. The figure explaining the time relationship table which shows the relationship between display time and data transfer time in other embodiment of this invention. The figure explaining how the packet (AP) in stream data (SOBU) is reproduced | regenerated in one embodiment of this invention.

Explanation of symbols

201: Information medium, 415: Optical disk device, 416: STB device.

Claims (5)

In an information storage medium having a data area for recording stream data including information corresponding to an MPEG I picture and including a transport stream, and a management area for recording management information of the stream data,
When a data packet called a transport packet or application packet is expressed as a first data unit, a data unit called a stream block or stream object unit is expressed as a second data unit, and an object data called a stream object is expressed as a third data unit In addition,
The stream data recorded in the data area is formed by the stream object of the third data unit including one or more of the second data units including one or more of the first data units,
The second data unit includes a plurality of sets of the data packet and time stamp, and the second data unit includes header information.
The header information is configured to be recorded in the data area different from the management area, and the real-time video object data different from the stream data is configured to be recorded in the data area,
The management information file for managing the stream data including the transport stream and the real-time video object data is stored in a single directory, and the header information includes the first data unit as the first data unit. An information storage medium configured to record information relating to the number of data packets. Data having a data area for recording stream data including information corresponding to an MPEG I picture and including a transport stream, and a management area for recording management information of the stream data, data called transport packets or application packets When a packet is expressed as a first data unit, a data unit called a stream block or a stream object unit is expressed as a second data unit, and object data called a stream object is expressed as a third data unit, one or more first data units are represented. The stream data to be recorded in the data area is formed by the stream object of the third data unit including at least one second data unit including the second data unit. The unit is configured to include a plurality of sets of the data packet and the time stamp, and the second data unit includes header information, and the header information is recorded in the data area different from the management area. Real-time video object data that is configured and different from the stream data is recorded in the data area, and the stream data including the transport stream and the management information file for managing the real-time video object data are a single file. In a recording method using an information storage medium configured to be stored in one directory and further configured to record information on the number of data packets as the first data unit in the header information,
Recording the stream data in the data area;
A recording method configured to record the management information in the management area. Data having a data area for recording stream data including information corresponding to an MPEG I picture and including a transport stream, and a management area for recording management information of the stream data, data called transport packets or application packets When a packet is expressed as a first data unit, a data unit called a stream block or a stream object unit is expressed as a second data unit, and object data called a stream object is expressed as a third data unit, one or more first data units are represented. The stream data to be recorded in the data area is formed by the stream object of the third data unit including at least one second data unit including the second data unit. The unit is configured to include a plurality of sets of the data packet and the time stamp, and the second data unit includes header information, and the header information is recorded in the data area different from the management area. Real-time video object data that is configured and different from the stream data is recorded in the data area, and the stream data including the transport stream and the management information file for managing the real-time video object data are a single file. In a reproducing method using an information storage medium configured to be stored in one directory and further recording information on the number of the data packets as the first data unit in the header information,
Read the management information from the management area,
A playback method configured to read the stream data from the data area. Data having a data area for recording stream data including information corresponding to an MPEG I picture and including a transport stream, and a management area for recording management information of the stream data, data called transport packets or application packets When a packet is expressed as a first data unit, a data unit called a stream block or a stream object unit is expressed as a second data unit, and object data called a stream object is expressed as a third data unit, one or more first data units are represented. The stream data to be recorded in the data area is formed by the stream object of the third data unit including at least one second data unit including the second data unit. The unit is configured to include a plurality of sets of the data packet and the time stamp, and the second data unit includes header information, and the header information is recorded in the data area different from the management area. Real-time video object data that is configured and different from the stream data is recorded in the data area, and the stream data including the transport stream and the management information file for managing the real-time video object data are a single file. In a recording apparatus using an information storage medium configured to be stored in one directory, and further configured to record information on the number of data packets as the first data unit in the header information,
Means for recording the stream data in the data area;
A recording apparatus comprising: means for recording the management information in the management area. Data having a data area for recording stream data including information corresponding to an MPEG I picture and including a transport stream, and a management area for recording management information of the stream data, data called transport packets or application packets When a packet is expressed as a first data unit, a data unit called a stream block or a stream object unit is expressed as a second data unit, and object data called a stream object is expressed as a third data unit, one or more first data units are represented. The stream data to be recorded in the data area is formed by the stream object of the third data unit including at least one second data unit including the second data unit. The unit is configured to include a plurality of sets of the data packet and the time stamp, and the second data unit includes header information, and the header information is recorded in the data area different from the management area. Real-time video object data that is configured and different from the stream data is recorded in the data area, and the stream data including the transport stream and the management information file for managing the real-time video object data are a single file. In a playback apparatus using an information storage medium configured to be stored in one directory and further recording information on the number of data packets as the first data unit in the header information,
Means for reading the management information from the management area;
A reproducing apparatus comprising: means for reading the stream data from the data area.

Images