JP2007294104A - Information medium for recording stream data, recording method, reproducing method, and reproducing device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an information medium in which stream data are efficiently recorded and managed, a recording method, a reproducing method, and a reproducing device. <P>SOLUTION: The medium has a data area in which stream data including I-picture information of MPEG are recorded using a stream packet and a management area in which management information concerning the stream data is recorded, wherein a boundary of the I-picture information and information being adjacent to the I-picture information is indicated by start time information (SOB_S_APAT) of a part corresponding to the boundary or its finish time information (SOB_E_APAT) out of the stream data. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a method for recording video data transmitted by digital broadcasting or the like or stream data transmitted with a packet structure, a data structure of stream data suitable for this recording method, and information recording using this data structure. It relates to information media.

  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 the 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.

When a DVD-RAM disk is used as the information storage medium, data is recorded in units of sectors organized every 2048 bytes. On the other hand, the digital TV broadcast employs an MPEG transport stream, and stream data including video information is collectively transmitted for each 188-byte transport packet as a minimum unit of the transport stream. The size of this transport packet differs depending on the digital TV broadcast station. For example, there is a digital TV broadcast station that transmits in units of 130 bytes. When the received transport packet is recorded as it is in sector units on an information storage medium such as a DVD-RAM disk, the following problems occur. That is,
1. Since the 2048 bytes of the sector size is not an integral multiple of the transport packet size (for example, 188 bytes), the method of recording the transport packet in the sector becomes a problem.

  Specifically, when transport packets are sequentially arranged in a sector from the beginning and the remaining fraction generated in this sector is treated as a padding area, a lot of useless padding areas are generated for each sector. To do. Therefore, the amount of stream data that can be recorded on the information storage medium is reduced by the padding area for each sector. As a result, the substantial recording capacity of the information storage medium is reduced.

  2. Stream data that has been compressed in accordance with the MPEG standard needs to be decoded by the decoder after being reproduced from the information storage medium, but the time interval transferred to the decoder for each transport packet was received from a digital TV broadcast station It is necessary to maintain the immediately following time interval. Therefore, time interval information transferred to the decoder for each transport packet is required.

  3. Since each transport packet recorded on the information storage medium does not have identification information for individually identifying each transport packet, there is no means for designating a specific transport packet during search or search.

  4). When a DVD-RAM disk is used as the information storage medium, recording is performed in units of sectors of 2048 bytes, so that partial erasure processing in units of transport packets is difficult.

  5. Since stream data transmitted by digital TV broadcasting is compressed according to the MPEG standard, it is necessary to start decoding from the I picture position. Accordingly, when partial erasure is performed at a specific video position, it is substantially necessary to partially erase the I picture start position at the head thereof as a boundary position. However, partial erasure processing with the I picture start position as the boundary position is difficult with information obtained by sequentially recording transport packets in a sector.

  The present invention has been made in view of the above circumstances, and an object thereof is to provide a recording method capable of efficiently recording stream data.

  Another object of the present invention is to provide a data structure capable of efficiently managing stream data.

  An information medium according to an embodiment of the present invention includes a data area in which stream data including MPEG I picture information is recorded using a stream packet, and a management area in which management information regarding the stream data is recorded. . Here, a boundary between the I picture information and information adjacent to the I picture information is indicated by start time information (SOB_S_APAT) or end time information (SOB_E_APAT) of a portion corresponding to the boundary of the stream data. Can do.

  Stream data can be recorded efficiently.

  A stream data recording method and data structure thereof according to an embodiment of the present invention will be described below with reference to the drawings.

  FIG. 1 is a view for explaining the data structure of stream data according to an embodiment of the present invention.

  Stream data recorded on the information medium is recorded as a stream object for each content of video information in the stream data or for each video recording unit.

  FIG. 1H illustrates a stream object recorded on an information medium such as a DVD-RAM disk. Here, the last part of the stream object # A298 and the stream object # B299 recorded subsequently are shown.

  When this stream data is recorded on a DVD-RAM disk or the like, as shown in FIG. 1 (d), it is recorded with a sector of 2048 kbytes as a minimum unit. As shown in FIGS. 1C and 1E, each sector is divided into a recording area for pack headers (or packet headers) 11 to 15 and a data area for recording stream data.

As shown in FIGS. 1F and 1G, time stamps and transport packets are sequentially packed in each data area. This can be done as follows. That is,
1. Time stamps and transport packets are sequentially recorded in locations other than the pack headers 11 to 15 in the sector, and the time stamp breaks or stream data breaks recorded for each transport packet are different from the sector boundary positions. In some cases, either time stamps or transport packets are arranged and recorded across adjacent sectors.

  Specifically, in FIG. 1, when the time stamp and the transport packet are sequentially packed, the data area No. 1 and a part of the transport packet 1k is data area no. It will protrude from 1. In this transport packet 1k, data area No. The portion protruding from 1 is the next sector No. 2 data area no. Continue recording at the top position of 2.

  2. A group of one-time video recording performed by a user or the like, or a group of identical contents such as one program is defined as a stream object. If the last transport packet position of the stream object recorded on the information storage medium is different from the sector boundary position, the padding area is set after the last transport packet position only within the corresponding sector. .

  Specifically, in the example of FIG. 1 (k), video recording ends with the transport packet 321a, which is the actual final position of the stream object # B299. At this time, the transport packet 321a is stored in the data area No. 1 of FIG. In the case of being arranged in the middle of 321, the data area No. Only 321 is assumed to be the padding area 21 thereafter.

  By using the data structure as described above, a packet having a size larger than the sector size can be efficiently recorded.

  FIG. 1 also shows the data structure related to 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. 1H and 1I, the stream object (SOB) # B · 299 is composed of a plurality of stream blocks (SOBU) # α to # γ.

  In the example of FIGS. 1 (h) and (i), the data size of each of the stream blocks (SOBU) # α to # γ constituting SOB # B • 299 is composed of 2 ECC blocks and has a size of 32 sectors. . That is, each of the first stream block sizes 261 to 264 (FIG. 1 (l)) in the time map information 252 (FIG. 1 (m)) has 32 sectors (64 kbytes).

  The stream block (SOBU) # α (FIG. 1 (i)) at the head of SOB # B.299 (FIG. 1 (h)) has a sector No. 1 (FIG. 1 (d)). No. 1 included in data area No. 1 1 (FIGS. 1E, 1F, and 1J) is recorded with a time stamp 1a (FIGS. 1G and 1K).

  The subsequent stream block (SOBU) # β (FIG. 1 (i)) of SOB # B • 299 (FIG. 1 (h)) is a data area No. 33 (FIG. 1 (j)) and data area No. In 33, a transport packet 33a (FIG. 1 (k)) accompanied by a time stamp 33a is recorded.

  As shown in FIG. 1 (k), the time stamp value [0] of the first stream data (transport packet 1a) of the stream block (SOBU) # α is the time stamp 1a, and the next stream block (SOBU) # The time stamp value [28] of the stream data (transport packet 33a) in β is the time stamp 33a.

  The value [30] of the first stream block time difference 266 in FIG. 1 (l) is the difference value ([28]-[0]) between the time stamp 33a and the time stamp 1a and is a predetermined number of significant digits (here, valid). It is given by rounding (rounding up) by one digit) ([28] − [0] ≈ [30]).

  The time map information 252 in FIG. 1 (m) may be handled as including the access data unit AUD in the stream object information SOBI described later with reference to FIG. The SOBU including information (desired I picture information, etc.) desired to be accessed can be specified by the information (access unit start map AUSM, etc.) included in this AUD.

  In the notation method of FIG. 1, the sector number of the first sector of stream object # B299 is set to 1, and the sector number is sequentially increased. The sector number and data area number are matched, and the time stamp number and transport packet number are set accordingly. That is, the first time stamp and transport packet set arranged in the data area in the 33rd sector is “33a”, and the next set in the same data area is “33b”, “33c”,. ... and set the number. Here, the time stamp or the number of the transport packet straddling the next data area without completely entering the previous data area like the transport packets 32j and 320k is displayed according to the previous data area number. . Also, the actual value of the time stamp is illustrated in square brackets [] in FIG.

  As shown in FIGS. 1A to 1C, in the information in the pack header (or packet header) 11-15, the sector common information 41 includes a pack header size 51, a time stamp size 52, a transport packet. Size 53 is listed.

  Here, the sector number of FIG. Taking the example of 1, the first time stamp value 54 in the sector in the search information 42 in FIG. 1B means the value of the time stamp 1a [= 0] in FIG. In the search information 42, the last time stamp value 55 in the sector means the value of the time stamp 1k (not shown).

  By the way, in many dictionaries, the first and last words of the corresponding page are described in the footnote or header position for each page to facilitate the search. Similarly, retrieval of stream data is facilitated by the above two pieces of information (first time stamp value 54 and last time stamp value 55 shown in FIG. 1A).

  Since the same time stamp or transport packet can be arranged across adjacent sectors, the first time stamp position information is required when accessing each sector independently. The first access point 56 shown in FIG. 1A means the number of bits from the position immediately after the packet header to the first time stamp position. However, this embodiment is not limited thereto, and for example, the number of bits up to the first transport packet head position may be included as information (corresponding to the first access point 56).

  In this embodiment, by specifying a value larger than the size of the data area as the value of the first access point 56, the start position of the time stamp can be specified even for a packet having a size larger than the sector size. Can be done.

  For example, in the data structure shown in FIGS. 1 to sector no. 2 and the time stamp for the packet is No.2. 1 is recorded at the first position in the data area, 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 56 of “1” is “data area size of sector No. 1 + T”. The value of the first access point of 2 is “T”.

  Sector No. 1 as the value of the first access point 56. By setting a value larger than the size of the data area 1, sector no. It is indicated that the time stamp position corresponding to the packet next to the packet recorded in 1 exists in the next and subsequent sectors.

  When partial erasure is performed in units of sectors (see FIG. 9), final position information 57 of a set of substantially effective time stamps and transport packets that does not span the next sector (FIG. 1A) Is required.

  In this embodiment, it is described by the number of pairs of time stamps and transport packets recorded in a complete form (not arranged across other sectors), but not limited to this, for example, the final position address, etc. It is also possible to record information (as final position information 57).

  As shown in FIGS. 1A and 1B, the bitmap information 43 relating to each transport packet includes an I picture position flag 58, a picture head position flag 59, and encryption information 60. The information of the I picture position flag 58 and the picture head position flag 59 in FIG. 1A can be created using information of a random access indicator 303 and a payload unit start indicator 301 described later with reference to FIG. In addition, information used for copy protection is appropriately recorded in the encryption information 60.

  From the intra-sector common information 41 and the search information 42 in FIG. 1B, the number of transport packets in the sector can be known. Each transport packet is made to correspond one bit at a time in the order of arrangement, and a “1” flag can be set for the transport packet that satisfies the condition. As shown in FIGS. 1B and 1C, bitmap information 43 relating to each transport packet in which this flag is set is also recorded in the pack header.

  In digital broadcasting, video information that is compressed in accordance with the MPEG2 standard is transferred. In digital broadcasting, as shown in FIG. 5C, a multiplexing / demultiplexing method corresponding to a multi-program called a transport stream is adopted, and the size of one transport packet b322 is 188 bytes (or 183 bytes). There are many.

  As described above, one sector size is 2048 bytes, and even if various header sizes are subtracted, about 10 transport packets for digital broadcasting can be recorded in one data area. On the other hand, in a digital communication network such as ISDN, a large long packet with a packet size of 4096 bytes may be transferred.

  If the data structure of FIG. 1 is adopted, not only a plurality of transport packets are recorded in one data area such as digital broadcasting, but also a packet having a large packet size such as a long packet is recorded. One packet can be recorded so as to continuously span a plurality of data areas. A transport packet for digital broadcasting, a long packet for digital communication, and the like can be recorded without any fraction in a stream block (SOBU in FIG. 1 (i)) regardless of the packet size.

  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, as shown in FIG. 3D, real-time video recording area 221 and stream recording area 222 can be mixedly recorded. (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 (eg, SOBI # B • 243) in FIG. 3G can include stream object general information (SOBI_GI) 251, time map information 252, and others, 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 FIGS. 9 (k) (l) and SC_S_APAT shown in FIG. 14) 283, and corresponding cell end time (described later). 9 (k) (l) and FIG. 14 (corresponding to SC_E_APAT) 284 and entry point information (SC_EPI) 285 can be included.

  The entry point information (SC_EPI) 285 is information that can be used as a tool for partially skipping recorded contents. The entry point information (SC_EPI) 285 has two formats (type A and type B) depending on the presence / absence of primary text information (PRM_TXTI), as shown in FIG.

  Here, the entry point indicates a position that enters the program in the case of the original PGC, and a position that enters a part of the program in the case of the user-defined PGC. Each PGC can have its own set of entry points. These entry points are recorded as part of cell information (SCI). These entry points can be used when part of the recorded content is skipped during playback of the recorded content.

  All entry points can be specified by application packet arrival time (APAT) indicating where to start outputting data. The application packet arrival time of this entry point is indicated by EP_APAT in FIG.

  The time map information 252 of FIG. 3H included in the SOBI # B of FIG. 3G includes a stream block number 260, a first stream block size 261, and a second stream block, as shown in FIG. .., And a first stream block time difference 266, a second stream block time difference 267,.

A specific example of the stream block time difference 266 constituting the time map information 252 is shown in FIG. 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.

  The 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. Can do. The 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 bottom of FIG. 4 and FIGS. 3E and 3F).

  The management information (STREAM.IFO105) for each stream object # A • 298 and # B • 299 in FIG. 4 is stored in the stream file information table (SFIT) 232 as shown in FIGS. Stream 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 PGC 290 (ORG_PGCI 233 in FIG. 3 (f)) that can continuously reproduce all stream data recorded in VRO (SR_TRANS.SRO) 106, and a place and order in which the user desires to reproduce is arbitrary. 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.

  Each cell can be specified by specifying the start time and end time. That is, before the partial deletion or editing (immediately after the recording of the stream data), the start time 283 of the corresponding cell of the original cell # 2 • 292 and the end time 284 of the corresponding cell (FIG. 3 (h)) According to the example of FIG. 1 (k), the value of the first time stamp 1a and the value of the last time stamp 321a in the corresponding stream object # B299 are used.

  On the other hand, the time range designation in the user-defined cell # 11/294 in FIG. 4 can designate an arbitrary time, and the time stamp value corresponding to the designated transport packet indicates the start time of the relevant cell and the relevant cell. Set to end time value.

In this embodiment, the access method to the stream data to be reproduced within the stream object is as follows: (1) A method of accessing the accumulated recording data amount from the recording start position of each stream object;
(2) Corresponding to video compression by the MPEG method, two methods are possible: a method of accessing with consideration of the decoding timing by the decoder.

  As apparent from FIG. 1 (g), time stamp information is appended to all transport packets, and each transport packet can be accessed using this time stamp information.

  When a DVD-RAM disk is used as the information storage medium, an ECC block is configured for every 16 sectors. Therefore, in the embodiment of the present invention, stream data is grouped for every integral multiple (for example, twice) of the ECC block, and a table of elapsed time for each group is provided. "Access by" is enabled. The above-mentioned (2) “access in consideration of decoding timing” will be described in detail in the description of FIG.

  In the embodiment of the present invention, a table of elapsed time for each group is used as time map information 252. The time map information 252 is recorded in a part of the stream object information (# A • 242; # B • 243) corresponding to each stream object, as shown in FIGS.

  In the embodiment of the present invention, the above group (sectors grouped every 2 ECC blocks) is called a stream block (or a data unit called SOBU) (see the upper part of FIG. 4 or FIG. 1 (i)).

  There is a case where a time stamp is not arranged at the start position of the sector arranged at the head of each stream block (SOBU). In this case, it is difficult to define the elapsed time for each stream block (SOBU).

  The countermeasures include the following.

  A) A time stamp value arranged at a specific position for each stream block is set as a stream block unique time.

  Specifically, the time stamp value arranged at the beginning of each stream block (and not recorded across the previous sector) is set as the start time of each stream block.

  B) A difference time between unique times (for example, start time) for each stream block is defined as an elapsed time for each stream block.

  C) The elapsed time (difference time) information is recorded in the time map information 252.

  There is a merit that the amount of data is reduced by displaying the difference time (elapsed time). However, the embodiment of the present invention is not limited thereto, and each stream block specific time can be recorded in the time map information 252.

  D) The rounded value of the elapsed time (difference time) information is recorded in the time map information 252.

  By rounding the calculation result of the elapsed time (difference time) information (rounding up or rounding down the value with a lower number of digits), omitting the value with the lower number of digits, and recording this rounded value in the time map information 252, data The size can be reduced.

  E) The stream block boundary position set at the time of initial recording is kept unchanged for the stream data after partial erasure.

  Although the sector size of each stream block can be set variously, as a preferred embodiment, a stream of a constant size (64 kbytes) is composed of 2 ECC blocks (32 sectors) as in stream block # μ in 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 stream packs and application packet groups in the streams pack). For example, when accessing an intermediate position of a certain SOBU # k (not shown), 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 is set. You can specify.

  FIG. 5 is a diagram for explaining the correspondence between digital broadcast content, video data transfer mode 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. In digital broadcasting, as shown in FIG. 5C, a multiplexing / demultiplexing method corresponding to a multiprogram called a transport stream is adopted, and the size of one transport packet b322 is 188 bytes (or 183 bytes). There are many cases.

  As shown in FIG. 5B, the transport packet includes a transport packet header 311 and a payload 312 in which a data body of recording information is recorded.

  As shown in FIG. 5A, the transport packet header 311 includes a payload unit start indicator 301, a packet ID (PID) 302, a random access indicator 303, a program clock reference 504, a reproduction time stamp (PTS) 305, and the like. Has been.

  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 303 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 301 of FIG.

  The information of the random access indicator 303 and the payload unit start indicator 301 can be used to create the information of the I picture mapping table and the B and P picture start position mapping table.

  For example, with respect to the transport packet in which the flag “1” is set in the payload unit start indicator 301 shown in FIG. 5A, the bit at the corresponding position in the B and P picture start position mapping table is set to “1”. Become.

  In digital broadcasting, video information and audio information are transferred in different transport packets. Each information is identified by a packet ID (PID) 302 in FIG. Using the information of the PID 302, a video packet mapping table and an audio packet mapping table can be created.

  As shown in FIG. 5 (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 311 and the payload (recording information) 312 in FIG. 5B is transferred by the transport packet b322 and the transport packet e325 of the program 2 shown in FIG.

  In IEEE 1394, as shown in FIGS. 5E and 5F, the IEEE isochronous headers 343 and 344 include an isochronous packet header 351 and a common isochronous packet header 352, respectively. A format-dependent reserved area is set in the common isochronous packet header 352.

  In the embodiment of the present invention, as shown in FIG. 5 (g), a source ID 361, data block size information 362, and an I picture start position flag 363 are stored in a format-dependent reserved area in the common isochronous packet header 352. Is stored. By setting the I picture start position flag 363 in the format-dependent reserved area in this manner, when the stream data is transferred in the isochronous mode, the I picture position designation in the stream data (that is, the start position of the I picture is set at the same time). (Designation of the corresponding transport packet). This is a major feature of this embodiment.

  In FIG. 5H, the first half 346 of the transport packet b of the program 2 is not recorded at the end of the application packet area, but the end of the application packet area may be a blank space. In this case, the end of the application packet area is not a partial packet, but is a stuffing area with a reserved number of bytes (no time stamp at the beginning).

  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, partial packets divided at the boundary of two adjacent stream packs (FIG. 5 (j)) (if each packet has 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).

  Further, the position of the time stamp immediately after the first partial packet in FIG. 5 (i) can be specified by the first access point 56 in FIG. 1 (a) or FIRST_AP_OFFSET in FIG. 10 (c).

  FIG. 6 is a diagram for explaining a sector structure for storing stream object data.

  FIGS. 6A to 6D show the contents corresponding to FIGS. 1H to 1K. In the example of FIG. 6, all stream blocks (SOBU) # α to # γ are configured with a fixed size (32 sectors / 2 ECC blocks = 64 kbytes). Among them, the last sector No. of the stream block (SOBU) # γ. n, and the sector No. immediately preceding it. The pack structure constituting n-1 (FIG. 6E) is illustrated in FIGS. 6F to 6J.

  Each sector of the stream block (SOBU) # γ is the last sector number. Except n, it has a similar data structure. For example, sector No. As for n-1, it is as shown in FIG.

  That is, sector no. n-1 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 in FIG. 6F can be configured in the same manner as that shown in FIGS. 5H and i (the packet in FIGS. 5H and i is replaced with the application packet in FIG. 6).

  The application packet area is composed of application packet groups each having an application time stamp (ATS) at the head (except for the stuffing area of FIG. 5 (h) and the partial packet of FIG. 5 (i)). 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 bytes shown in FIG. 6 (f) can be used to always keep the stream pack at a predetermined length (2048 bytes).

  Last sector number of stream block (SOBU) # γ. n is as shown in FIGS. 6 (g) to (j). That is, as shown in FIG. n is composed of a pack header and a padding packet. As shown in FIG. 6 (h), this padding packet includes a padding area 21 (corresponding to the padding area 21 in FIG. 1 (k)) in its application packet area.

  In the case of the first application packet area (first stuffing packet) in the padding area 21, as shown in FIG. 6 (i), a stuffing packet with an application time stamp (ATS) (zero byte having no substantial recorded contents). Data). If the padding area 21 has a length corresponding to a plurality of sectors, the second and subsequent application packet areas (subsequent stuffing packets) in the padding area 21 are stuffing packets without ATS as shown in FIG. It is filled with (zero byte data).

  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 shown in FIGS. 6 (i) and 6 (j) 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.

A stuffing packet has 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).

  FIG. 7 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. 7, 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 501 that does not include time difference information, a B picture 503 and 504 that includes time difference information, and a P picture 502.

  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 511, and the I picture information It is recorded as 521. In the P picture 502, only difference information 512 with respect to the I picture 501 is recorded as P picture information 522. In addition, difference information 513 and 514 for the I picture 501 and the P picture 502 are recorded as B picture information 523 in the B picture 503, and difference information 515 and 516 in the B picture 504 are B picture information 524. As recorded.

  As shown in FIG. 7, the compression information 511 of the I picture 501 is recorded in the transport packets 1a, 1b,... As the I picture information 521, and the difference information 513, 514 of the B picture is the transport packet 33a as the B picture information 523. ,... Are recorded in the transport packet 41d as B picture information 524, and the P picture difference information 512 is transport packet (TP) 48h to 298g as P picture information 522. To be recorded. Thus, each I, B, P picture information is recorded in different transport packets.

  At the time of video reproduction, a screen cannot be generated by the P picture 502 or the B pictures 503 and 504 alone, and each picture screen can be generated only after the I picture 501 screen is generated. Each picture information 521 to 524 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 521 to 524 and the boundary positions between the transport packets are recorded so as to always coincide as shown in FIG.

  In the first transport packet 1a in which the I picture information 521 is recorded, a flag “1” is set in the random access indicator 303 (FIG. 5A). In the first transport packets 33a, 41d, and 48h of the B and P picture information 523, 524, and 522, a flag “1” is set in the payload unit start indicator 301 (FIG. 5A). The information of the random access indicator 303 and the payload unit start indicator 301 is used to create the information of the I picture position flag 58 and the picture head position flag 59 of FIG. Similarly, information such as encryption information 60 used for copy protection is also recorded as bitmap information 43 (FIG. 5B) relating to individual transport packets.

  The position information (I picture position information) of the I picture (501) in FIG. 7 includes entry point information (SCI) (# 1, 272 etc.) in the original cell information (SCI) as shown in FIGS. SC_EPI) 285.

  As shown in FIGS. 7A and 7B, the data structure in the entry point information 285 is an entry point position (first entry point position (EP_APAT)) indicating individual I picture position information existing in the same stream object. 531, second entry point position 532, third entry point position 533,..., Last entry point position 535).

  As the information content of the entry point position (EP_APAT) 531, as shown in FIG. 7A, the value of the time stamp 1a corresponding to the transport packet 1a in which the first information of the I picture information 521 is recorded. It is recorded. Similarly, the information contents of the individual entry point positions (EP_APAT) 532, 533, and 535 include the time stamps 87f, 183d, and 298g corresponding to the transport packet in which the first information of each corresponding I picture information is recorded. The value is recorded.

  For example, the information on the start time and / or end time of the corresponding cell for the user-defined cell # 11/294 shown in FIG. 4 is recorded in the user-defined PGC information table 234 of FIG. In this case, when it is desired to reproduce from the B picture information 524 of FIG. 7, the time stamp 41d can be set as the start time of the corresponding cell. As described above, the information on the start time of the corresponding cell or the end time of the corresponding cell can be set by any time stamp information regardless of the I picture position.

  On the other hand, the start / end time of the stream object in this embodiment is set in consideration of the I picture position. That is, as the information contents of the stream object general information 251 shown in FIGS. 3 (h) and 7 (d), as shown in FIG. 7 (c), a recording time (SOB_REC_TM) 541 indicating a recording start time, A stream object start time (SOB_S_APAT) 542 and a stream object end time (SOB_E_APAT) 543 are recorded.

  This stream object start time (SOB_S_APAT) 542 must be set to the value of the time stamp 1a corresponding to the transport packet 1a in which the head of the I picture information 521 is recorded. Similarly, the stream object end time (SOB_E_APAT) 543 needs to be set to the value of the time stamp 298g corresponding to the transport packet 298g immediately before the I picture information.

  When the transport packet of FIG. 7 is recorded on a streamer (an optical disk device 415 of FIG. 11 described later), the content of the transport packet is transferred to a packet with a time stamp (application packet) called an application time stamp (ATS). It is done.

  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. The stream PES packet includes 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. .

  FIG. 8 is a diagram for explaining a method for setting the time map information 252 shown in FIG. 1 and others.

  As shown in FIG. 1 (g) or FIG. 8 (b), the stream data in which the time stamp (TMS) and the transport packet (TP) (or application packet AP) are sequentially packed is recorded as shown in FIG. As shown in (a), for example, the stream blocks (SOBU) # α, # β, # γ, and ˜ # λ are configured by being divided every 2 ECC blocks (32 sectors).

  A time stamp (TMS) 1a is arranged at the head position of the stream block (SOBU) # α. This time stamp 1a indicates the arrival time (SOBU_S_APAT) of the first packet of SOBU # α. The value [0] of this time stamp 1a becomes the start time of SOBU # α.

  For the other stream blocks (SOBU # β to SOBU # λ), the values of the time stamps 33a, 65a, 98a,. [28], [63], [98], [297]) are the start times of the stream blocks (SOBU # β to SOBU # λ).

  The last time stamp 300a immediately before the last packet of each stream block, for example, the last SOBU # λ, indicates the arrival time (SOBU_E_APAT) of the last packet of SOBU # λ. The value [300] of the time stamp 300a is the end time of SOBU # λ.

  When a margin is generated at the end of the last SOBU # λ, the margin is set as a padding area 21 without actual data (see FIG. 1 (k) or FIGS. 6 (h) to (j)).

  As shown in FIG. 8B, the start times of the stream blocks (SOBU # α to SOBU # λ) are set to 0, 28, 63, 98,. These times are: (a) seconds, (b) field or frame / picture count (eg 30 pictures / second for NTSC, 60 fields / second, 25 pictures / second for PAL, 50 fields / second), and (c ) It can be displayed in either of the counts by the reference clock of 27 MHz or 90 kHz.

In the examples of FIGS. 8A and 8B, the elapsed time of the first stream block (SOBU # α) is [28] − [0] = [28] (2 significant digits). Even if the expression is coarser, the practicality is not impaired, so the first digit of this elapsed time value [28] is rounded (rounded up) to [30].

  The elapsed time of the second stream block (SOBU # β) is [63]-[30] when the rounding calculation result [30] is used. Similarly, the first digit is rounded (rounded up) [40]. And Similarly, the elapsed time of subsequent stream blocks (SOBU # γ to SOBU # λ) is expressed by a numerical value rounded up (rounded up) to one significant number.

  Since the stream block (SOBU # λ) and the subsequent blocks are not accessed, the time difference value for the last stream block is intentionally blanked as shown in FIG. 8C.

  The relationship between the rounding calculation result and the time map information 252 is shown in FIG.

  By the way, since there is no stream block after the stream block (SOBU # λ), the same differential time calculation as other stream blocks cannot be performed. Therefore, in this embodiment, only the last time stamp value (SOBU # λ) recorded in the time stamp value (the time stamp 300a value [300] in the example of FIG. 8B) is included. And the difference between the time stamp value recorded first in the last stream block (SOBU # λ) (the value [297] of the time stamp 321a in the example of FIG. 8B) is rounded up. It is also possible to set the value to the time difference value. This is shown in FIG.

  Note that there are two possible ways of calculating the time difference value of the last SOBU # λ in FIG. First, the value [300] before rounding of the last time stamp 300a (SOBU_E_APAT of SOBU # λ) and the value [297] of the first time stamp 321a before rounding are used, and the difference result [3] is rounded up. Thus, the time difference value [10] is obtained. Second, the rounding value [300] of the last time stamp 300a and the rounding value [300] of the first time stamp 321a are used, and a rounding error [10] is added to the difference result [0] to obtain a time difference value [10]. It is a method to ask for.

  In the second method, all the numerical values are grouped with the number of significant digits 1 excluding “0” in the last digit, the rounding error is set to [1], and the last digit of the other numerical values is deleted. You can also think about it.

  FIG. 9 is a diagram for explaining how the stream object information and the original cell information change before and after erasure when a part of a recorded stream object is partially erased.

  The series of information description methods described above can also be applied to partially erased stream objects. FIG. 9 (k) shows a state before partial erasure. The stream data structure, original cell range, and stream object range for the stream object immediately after recording (FIG. 1 (h) other SOB # B • 299) are shown in FIG. a) to (e).

  In the following, a process will be described after the range from the time stamp 97c to the time stamp 224k is excluded as the actual display range, and the front and back of the range are partially erased.

  In this embodiment, partial erasure is performed on a sector basis. However, in order to perform playback of another stream object immediately after playback of a stream object after partial erasure and to enable seamless playback without causing screen distortion at the joint of these stream objects, MPEG It is necessary to perform partial deletion while maintaining the GOP boundary position of the bitstream.

  Assume that the I-picture head position immediately before the transport packet 97c corresponding to the time stamp 97c is present in the transport packet 87f as indicated by the second entry point position 532 in FIG. In this case, the sector number including the transport packet 87f. 87 is left, all the sectors before the previous sector are partially erased, and the value of this time stamp 87f is set to the stream object start time (SOB_S_APAT) 542 of the stream object after the partial erase (see FIG. 9L).

  As a result, for example, the size of the stream block # γ originally 32 sectors is reduced to 30 sectors.

  At the same time, the value of the stream block time difference described in the time map information 252 correspondingly decreases from 40 to 30, for example. Since the boundary positions of the stream blocks # δ to # η are kept unchanged before and after partial erasure, the information in the time map information 252 related to the portion does not change.

  Although omitted in FIG. 7, if the head position of the I picture starts with the transport packet 225e, the sector number of FIG. 9 (i) including the transport packet 225d is included. Leave to 225 and erase all subsequent sectors.

  The stream object end time (SOB_E_APAT) 543 in FIG. 9J can be set by the time stamp 225d of the transport packet 225d.

  As shown in FIG. 9 (i), the start time (SC_S_APAT) 283 / end time (SC_E_APAT) 284 of the corresponding cell after partial erasure is set to a time stamp 97c and time stamp 224k according to the actual designated range of partial erasure. Is done.

  The feature of this embodiment is that time map information (or stream object information SOBI / original cell information SCI) is created by such a method.

  Note that the start time and / or end time changes before and after the partial erase, but the SOBU size remains unchanged (for example, 64 kbytes for 32 sectors is constant).

  In partial erasing, it is also possible to erase in units of SOBU. In this case, the first (or last) time stamp TMS in the original cell is always in the first (or last) SOBU in the SOB. To be included.

  FIG. 10 is a diagram for explaining the data structure of the stream pack shown in FIG. 5 and others.

  Each stream pack has a data structure as shown in FIG. That is, a 14-byte pack header 11, a 6-byte PES header 601, a 1-byte substream ID, a 9-byte application header, an optional application header extension used as necessary, and, if necessary, One stream pack is composed of an optional stuffing byte to be used and an application packet group including one or more application packets with an application time stamp ATS (see FIG. 6F).

  As shown in FIG. 10G, the pack header 11 includes pack start code information, system clock reference (SCR) base information, SCR extension information, program multiplexing rate information, pack stuffing length information, and the like. Contains. The SCR base is composed of 32 bits, and the 32nd bit is set to zero. Further, for example, 10.08 Mbps is adopted as the program multiplexing rate.

  As shown in FIG. 8 (f), the PES header includes packet start code prefix information, stream ID (private stream 2) information, and PES packet length information.

  Further, the substream ID has contents for specifying stream recording data, as shown in FIG. Specifically, substream ID = “00000010b” indicates that the data stored in the stream pack is stream recording data. When the stream ID is “10111110b”, it is indicated that the stream pack is used for a padding packet (see FIG. 6G).

  As shown in FIG. 10C, the application header of FIG. 10D includes version information, the number of application packets AP_Ns, the time stamp position FIRST_AP_OFFSET of the top 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.

  FIRST_AP_OFFSET in FIG. 10C corresponds to the first access point 56 in FIG. 10B or FIG. As shown in FIG. 10A, the first access point 56 is stored in the search information 42 (see FIG. 1B) in the pack header (or application header).

  The stuffing byte and application packet group in FIG. 10D constitute an application packet area as shown in FIG. A partial application packet is recorded at the head of this application packet area. Thereafter, a plurality of pairs of application time stamp ATS and application packet are sequentially recorded. Then, as shown in FIG. 5H, a partial application packet (or a stuffing area for reserved bytes) is recorded at the end of the application packet area.

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

  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. 10D, 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 two transport packets 1k shown in FIG. 1 (g) or the partial application packets shown in FIGS. 5 (h) and (i) indicate application packets 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 as shown in FIG.

  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. 10 can be applied to other than the last sector of the corresponding stream object (SOB), but is not necessarily applied to the last sector. The packet structure shown in FIGS. 6 (i) and (j) is applied to the last sector.

  FIG. 11 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.

  Hereinafter, the internal structure of the stream data recording / reproducing apparatus according to the embodiment of the present invention will be described 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.

  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, delimiter information for dividing stream data into stream blocks (or SOBUs) is created, and cell delimiter information and program delimiter information corresponding to the delimiter information, and also PGC delimiter information Is created.

  The formatter / deformatter unit 413 converts the stream data sent from the STB device 416 into a stream pack sequence (see FIG. 5J, etc.), and inputs the converted stream pack sequence to the D-PRO unit 410. To do. 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 A reception information selector unit 423 that selects information on a specific program (desired by the user) (transport packet of program 2 in FIG. 5 as an example) from data is provided.

  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 through the data transfer interface unit 420 by IEEE1394 transfer.

  In the data transfer interface unit 414 in the optical disk device 415, the stream data transferred by the IEEE1394 is temporarily returned to the form shown in FIG. 5D, and the set of the time stamp and the transport packet shown in FIG. Are sequentially packed and recorded on the information storage medium 201.

  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 reproduced, the stream data sent from the optical disk device 415 to the STB device 416 via the IEEE1394 serial bus is multiplexed by the decoder unit 402 via the selector unit 423. Sent to the categorized 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 can be taken into the personal computer 435 or the like 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.

  In the optical disc apparatus 415 (streamer) of FIG. 11, a set of time stamps and transport packets (FIG. 5 (h) (i)) is recorded on the information storage medium 201 as it is.

  For example, when the user intends to record the second program in FIG. 5C on the information storage medium (201 in FIG. 3A), the reception information selector 423 in the STB device 416 shown in FIG. Only the transport packets b and e of program 2 are extracted. At that time, in the STB device 416, as shown in FIG. 5D, time information when the transport packets b522 and e525 are received is added in the form of time stamps 331 and 332, respectively.

  Thereafter, when data is transferred to the formatter / deformatter unit 413 in FIG. 11 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. 11, the stream data transferred by the IEEE 1394 from the STB device 416 is temporarily returned to the form of FIG. 5D (corresponding to the form of FIG. 1G). Then, a bit stream in the format of FIG. 5D (stream pack sequence of FIG. 5J) 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. 5 (j) and the like).

  A plurality of time stamps and transport packets (FIG. 1 (g)) are sequentially packed in the data area (FIG. 1 (f)), but one transport packet (packet 1k in FIG. 1 (g)); In (d), the packet b) of program 2 can be recorded across a plurality of sectors (No. 1 and No. 2 in FIG. 1 (e); partial packets in FIGS. 5 (h) and (i)). It has become. Here is one of the features.

  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. 5C, 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, one sector size is 2048 bytes, and even if various header sizes are subtracted, about 10 transport packets for digital broadcasting can be recorded in one data area (FIG. 1 (f)). 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 order to record not only a plurality of transport packets in one data area (FIG. 1 (f)) such as digital broadcasting but also a packet with a large packet size such as a long packet, By using a data structure that makes use of the above features (a feature that allows one packet of data to be recorded across a plurality of packets), one packet is recorded so as to continuously straddle a plurality of data areas. 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.

  Looking at the device configuration of FIG. 11 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.

  Next, processing at the time of recording stream data in the apparatus of FIG. 11 will be described. As shown in FIG. 5 (c), in digital broadcasting, a plurality of program information are time-division multiplexed in one transponder. As shown in FIG. 5D, a transport packet for only a specific program is extracted in the reception information selector unit 423 for the information.

  The “reception time management unit” temporarily stores necessary program information in the memory unit 426 in the multiplexed information demultiplexing unit 425 and simultaneously measures the reception time for each transport packet. ) As a time stamp for each transport packet. The added time stamp information is recorded in the memory unit 426.

  In the “stream data content analysis unit”, information in the transport packet recorded in the memory unit 426 is analyzed. Specifically, each picture boundary position is extracted from the transport packet sequence, and reproduction time stamp (PTS) information is extracted. As described above, there are two methods for extracting each picture boundary position, and the method is selected according to the contents of the stream data. Similarly, the PTS information 53 in the picture header information 41 is extracted. Next, the stream data temporarily stored in the memory unit 426 is recorded on the information storage medium 201.

  When the time stamp value is designated as the playback start position from the STB device 416, the time map information 252 is information for calculating the corresponding stream block. As shown in FIGS. 3E to 3H, the time map information 252 includes the STREAM. It is recorded as part of the stream object information 243 in the IFO 105.

  As shown in FIG. 3I, only time stamp difference time information for each stream block is recorded in the time map information 252. Therefore, the time difference value of each stream block in the time map information 252 is sequentially added for each stream object information 242 and 243, and whether or not the sequentially added value reaches the time stamp time designated on the STB device 416 side is compared. There is a need to. Based on the comparison result, it is determined whether the time designated by the STB device 416 matches the time stamp value included in which stream block in which stream object.

  Next, an embodiment relating to partial erasure of stream data already recorded on the information storage medium 201 will be described.

  In the stream data recording / reproducing apparatus, the above-described partial erasure process is controlled by the STB control unit 404, and among these, a sequential program called a stream data partial erasure control unit is mainly executed.

  In the STB control unit 404 in FIG. 11, before partial erasure is performed, STREAM. Information of the IFO 105 is read and temporarily stored in the work RAM memory unit 407. When the partial erase process is completed, the sector to be partially erased is the STREAM. Removed from VRO (or SR_TRANS.SRO) 106. Thereafter, the management information (STRI including SOBI and SCI) is changed to the content shown in FIG. 9 (l), and the STREAM. Data in the IFO 105 is rewritten.

  Next, an access method “corresponding to the video compression by the MPEG system and being aware of the decoding timing by the decoder” will be described as an access method to the stream data to be reproduced within the stream object.

  In the embodiment of the present invention, stream data is transferred from the STB device 416 in isochronous mode, and at the same time, I picture information is transferred in real time, and the information records stream data as shown in FIG. STREAM. Recorded in the VRO 106 file. Further, in the embodiment of the present invention, this information includes the STREAM. It is also recorded in the IFO 105.

  For example, when the B picture information 504 in FIG. 7 is to be reproduced and displayed on the STB device 416 side shown in FIG. 11, the time stamp 1a corresponding to the transport packet 1a located at the head of the I picture information 501 existing immediately before that is displayed. Is notified to the optical disk device 415.

  The optical disk device 415 uses the information of the time map information 252 having the structure shown in FIG. 1 or FIG. 3 to determine the sector position where playback is started, accesses a predetermined position on the information storage medium 201, and stores stream data to be played back. Transfer to the STB device 416. Then, the decoder unit 402 of the STB device 416 starts decoding from the I picture information 501 and starts displaying from the designated B picture information 504.

  In the transport packet 41d (FIG. 7) in which the start information of the B picture information 504 is recorded, as shown in FIGS. 5A and 5B, reproduction indicating the display start time in the transport packet header 311 is performed. Information of a time stamp (presentation time stamp) PTS 305 is recorded. The decoder unit 402 reads this PTS 305 and sets the playback start time.

  The method for extracting the I picture position by the decoder unit 402 in FIG. 11 has been described above. However, depending on the digital TV broadcasting station, each picture position information may be transmitted at the transmission stage. Each picture position information already recorded at the stage of transmission will be described below.

  In the embodiment of the present invention, the stream block boundary position set at the time of initial recording is kept unchanged even for stream data after partial erasure, and the remaining part is redefined as a new stream object with the partial erasure part as a boundary. I am doing so. In this case, the size of the first and last stream blocks in the stream object may be smaller than the sizes of other stream blocks. Therefore, as shown in FIG. 1 (l) or FIG. 3 (i), individual stream block size information is also recorded in the time map information 252.

  In this embodiment, not limited to the above, for example, it is possible to have only the first and last stream block size information, and to record only other common stream block size information.

  FIG. 12 is a flowchart for explaining how the alignment of an application packet and a stream object and the padding process at the end of the stream object are performed when the information recording of the bit stream is performed by the system of FIG. .

  In the optical disk device (streamer) 415 of FIG. 11, the bit stream to be recorded (the contents of the transport packet) is distributed to the application packet area in the stuffing packet (step ST10).

  The first byte of the application time stamp (ATS) of the first application packet (this is A) and the start of the application packet area in the first stream packet at the start of the stream object (SOB) where the bitstream is recorded The part (this is referred to as B) is compared (step ST12).

  When the first byte (A) of the ATS and the start portion (B) of the application packet area in the first stream packet do not match (No in step ST14), for example, a necessary number of stuffing bytes are provided in the stream packet, The first byte (A) and the start part (B) are matched (aligned) (step ST16).

  When the first byte (A) of the ATS matches the start part (B) of the application packet area in the first stream packet (Yes in step ST14), or the first byte (A) matches the start part (B) ( Between the end of the last application packet (referred to as C) including the actual data of the bitstream to be recorded and the end of the SOB where the bitstream is recorded (referred to as D). It is checked whether there is a margin equal to or larger than one stream packet (one sector) (step ST18).

  When there is a margin of one stream packet (one sector) or more between the end of the application packet (C) and the end of the SOB (D) (Yes in step ST18), this margin includes one ATS. It is filled with the above stuffing packet (step ST20).

  When there is no margin between the end of the application packet (C) and the end of the SOB (D) (No in step ST18), or the margin between the end of the application packet (C) and the end of the SOB (D) is stuffing After being filled with packets, one or more application packet groups (which may include stuffing packets or stuffing area bytes as appropriate) including the contents of the bitstream to be recorded are recorded on the information medium 201 (step ST22).

  Thereafter, the management information (STRI) is written corresponding to the recording information (step ST24).

  In the recording step ST22, the following processing is appropriately performed.

  (10) When there is a margin part at the end of the application packet area, a stuffing area (padding area 37 in FIG. 5 (h) or FIG. 19 (j)) of a predetermined number of bytes (without a time stamp) is added to this margin part. Provide.

  In the recording steps ST22 to ST24, the following processing is performed as appropriate.

(11) The stream data (SOB) is composed of a plurality of data units (SOBU # α ... # λ in FIG. 8A),
Each of the data units (SOBU # α ... # λ) is composed of one or more data packets (TP / AP in FIG. 8B) in which predetermined time stamp (TMS) information is recorded,
Among the plurality of data units (SOBU # α ... # λ), at least a first time stamp (TMS1a) recorded in the first data unit (SOBU # α) and a second data unit (SOBU #). A time difference value (rounded up value in FIGS. 8C and 8D) corresponding to the difference from the second time stamp (TMS33a) recorded in β) is stored in the management area (STRI or STREAM.IFO / SR_MANGR.IFO). ).

(12) Record information of one or more cells (FIG. 18) in the stream data (SOB),
In the management area (STRI or STREAM.IFO / SR_MANGR.IFO), record information of a program chain (PGC) describing a collection of one or more cells (FIG. 3 (f) or PGCI in FIG. 13),
When a part of the recorded content of the stream data (SOB) is skipped during reproduction, information (SC_EPI) of an entry point (EP) that can be used as a mark of the skip position is recorded in the management information (STRI).

  (13) The management information (STRI) includes stream data (SOB) recording time information (SOB_REC_TM), data packet arrival time (SOB_S_APAT) at the beginning of the stream data (SOB), and end of the stream data (SOB). The stream object general information (FIG. 7D or SOBI_GI in FIG. 15) including at least one of the partial data packet arrival times (SOB_E_APAT) is written.

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

  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, 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 disk) 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. SC_S_APAT shown in FIG. 9, stream cell end APAT (SC_E_APAT shown in FIG. 9), and erase start APAT (ERA_S_APAT) indicating the start APAT of the temporary erase cell when the cell is in the temporary erase state (TE = 10b) ) And erase end APAT (ERA_E_APAT) indicating the end APAT of the temporary erase cell when the cell is in the temporary erase state (TE = 10b).

  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 the 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 and the number of sectors SOBU_SIZ per SOBU.

  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 the 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. 10D can exist in the real-time data of the corresponding SOB. 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 the correspondence between the access unit start map (AUSM) and the stream object unit (SOBU).

  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 is a diagram illustrating a correspondence relationship between an access unit start map (AUSM) and an access unit end map (AUUM) and a stream object unit (SOBU).

  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)]. In other words, AU # i ends when AU # i + 1 starts 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.

  SO_APAT of SOB or SOBU is defined in relation to the time stamp recorded in the payload (see FIG. 5B) 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 in which the arrival time interval of SOBU of the SOB is described. In other words, the address system realized by the time map information 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.

  Each entry point (EP # i, EP # k) illustrated in FIG. 18 can be specified by an application packet arrival time (APAT) indicating where to start outputting data. The application packet arrival time of this entry point is indicated by EP_APAT in FIG.

  By using this entry point, for example, at the time of reproduction from cell # 1 from SOBU # 1, SOBU # 2 to SOBU # (i-1) are skipped, and the designated position (entry point EP # i of SOBU # i) is skipped. ) Can start playback.

  FIG. 19 is a diagram for explaining the data structure of stream data according to another embodiment of the present invention.

  Stream data recorded on an information storage medium such as a DVD-RAM disk is collected as a stream object (SOB) for each content of video information in the stream data. Each SOB is formed by stream data obtained by one real-time continuous recording.

  FIG. 19F shows one SOB # A · 298 among one or more stream objects. When this stream data is recorded on a DVD-RAM disc, each is recorded with a sector of 2048 kbytes 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 is configured in units of one or a plurality of ECC blocks, and recording or partial erasure of stream information is performed in units of the stream blocks.

  In this embodiment, how many ECC blocks form a stream block can be determined according to the transfer rate of the stream data to be transferred. For example, in the example of FIG. 19 (e), the stream block # 1 is composed of two ECC blocks # α and # β, and the stream block # 2 is composed of three ECC blocks # γ, # δ, and # ε. Yes. In a DVD streamer, one ECC block (32 sectors) constitutes one stream block (stream object unit SOBU).

  Each ECC block is composed of 16 sectors as shown in FIG. Accordingly, as can be seen from FIGS. 19D and 19E, 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 contents of each sector correspond to a stream pack (see FIGS. 5, 6, and 10 for details). For example, sector No. As shown in FIG. 19C, the stream pack corresponding to 0 (FIG. 19D) includes a pack header 1x, a PES header 6x, a stream block header 11x, and a data area 21x. Also, sector No. As shown in FIG. 19C, the stream pack corresponding to 1 (FIG. 19D) includes a pack header 2x, a PES header 7x, a sector data header 12x, and a data area 22x.

  As shown in FIG. 19B, the data area 21x in FIG. 19C has a pair of time stamps and transport packets (time stamp a, transport packet a, time stamp b,... Port packet d). Similarly, the data area 22x includes another arrangement of time stamp and transport packet pairs. On the other hand, the rear data area 23x includes a transport packet f, an end code 31x, and a padding area 36x, as shown in FIG. 19B.

  A plurality of pairs of time stamps and transport packets shown in FIG. 19B form a bit stream having an arrangement as shown in FIG.

  The data structure of stream block # 1 (FIG. 19 (e)) ahead of SOB # A.298 (FIG. 19 (f)) is as shown in FIGS. 19 (d) to 19 (b). The data structure of stream block # 2 (Fig. 19 (g)) behind is as follows.

  That is, the rear sector number of the last ECC block # ε of the stream block # 2. 78 (FIG. 19 (h)) includes a pack header 3x, a PES header 8x, a sector data header 13x, and a data area 24x, as shown in FIG. 19 (i). Also, the last sector number of ECC block # ε. 79 (FIG. 19 (h)) includes a pack header 4x and a padding packet 40x as shown in FIG. 19 (i).

  Sector No. As shown in FIG. 19J, the 78 data area 24x includes a transport packet z, an end code 32x, and a padding area 37x. Also, the last sector No. The padding packet 40x of 79 includes a PES header 9x and a padding area 38x as shown in FIG.

  The contents of the padding area 37x can be composed of one or more time stamp / packet pairs and a reserved byte stuffing area (the stuffing area has no time stamp), as shown in FIG. 5 (h). . In this case, stream data is not recorded in the stuffing area.

  On the other hand, as shown in FIGS. 6I and 6J, the contents of the padding area 38 can be configured by an application packet area including a stuffing packet (an application time stamp ATS is attached only to the head).

The present invention can also employ a data structure having the following characteristics:
A) A data structure in which a pack header / packet header is provided for each sector / stream pack and information necessary for each sector / stream pack is recorded in the pack header / packet header (FIGS. 1A to 1C, FIG. 5 (a)-(b), FIG. 10 (a)-(g) reference).

  B) A data structure for recording time information related to a time interval at which each transport packet / application packet is transferred to the decoder as time stamp information on the information storage medium together with each transport packet / application packet (see FIG. 1 (k) to (m), see FIGS. 5 to 10).

  C) A data structure in which a time stamp and a transport packet / application packet are sequentially packed in a place other than a pack header / packet header in a sector / stream pack. If the break of the time stamp or the break of the stream data recorded for each transport packet / application packet is different from the boundary position of the sector / stream pack, either the time stamp or the transport packet / application packet is A data structure arranged and recorded across adjacent sectors / stream packs (see FIGS. 1D to 1G and FIGS. 5E to 5J).

  D) A group of one recorded video performed by the user or the like is a stream object (SOB), and the last transport packet / application packet position (one stream object) recorded on the information storage medium in one video recording In the case where the last transport packet / application packet position) is different from the sector / stream pack boundary position, the padding area extends from the last transport packet / application packet position only within the corresponding sector / stream pack. (See FIGS. 1G and 1K, FIGS. 6G to 6J, and FIG. 19J).

  E) In addition to the file (STREAM.VRO or RTR_MOV.VRO) for recording stream data on the information storage medium, a management file (STREAM.IFO or RTR.IFO) for managing the stream data in the file is provided and streamed A data structure that facilitates data retrieval and / or editing.

  F) In a management file (STREAM.IFO or RTR.IFO) for managing stream data, STREAM. VRO file or RTR_MOV. A data structure in which the time stamp value recorded in the VRO file is used for identification / designation for each individual transport packet / application packet (see FIGS. 8B to 8D).

  G) In order to facilitate time search, a unit called a stream block (or a data unit called a stream object unit SOBU) is configured on a management file by collecting a plurality of sectors, and has time information for each stream block (SOBU). A data structure for providing time map information in this management file (STREAM.IFO or RTR.IFO) (see FIGS. 8A to 8D).

  Note that at least the data sizes of the first and last stream blocks (SOBU) in the stream object may be recorded in the time map information in the management file (STREAM.IFO or RTR.IFO) (FIG. 3 (i)). )reference).

  H) The management file (STREAM.NET) uses the value of the first time stamp (excluding the time stamp recorded across the previous stream block) in each stream block (SOBU) as the start time of each stream block (SOBU). Data structure managed in IFO or RTR.IFO) (see FIGS. 8A to 8D).

  Specifically, the value of the time stamp (for example, TMS1a in FIG. 8B) first arranged in each stream block (SOBU) is recorded in the time map information in the management file.

  In the stream data recording method according to the present invention, an information storage medium capable of recording information for each first recording unit (sector or stream pack) is used and divided into second recording units (transport packets / application packets). Stream data is recorded.

  In the first recording area (stream recording area 222 in FIG. 3 (d)) where stream data is recorded in the second recording unit (transport packet / application packet), the first recording unit (sector / stream) is recorded. Packet header (or pack header) information provided for each pack), time stamp information having time information related to stream data of the second recording unit (transport packet / application packet), and the second recording Stream data for each unit (transport packet / application packet) is recorded.

  When the break of the time stamp information or the break of stream data recorded for each second recording unit (transport packet / application packet) is different from the boundary position of the first recording unit (sector / stream pack) The stream data recorded for each of the time stamp information or the second recording unit (transport packet / application packet) is arranged across a plurality of the first recording units (sector / stream pack). (Refer to the first half 346 and the second half 347 of the transport packet b of the program 2 in FIG. 5E and FIGS. 5H to 5J).

  In the stream data recorded last on the information storage medium, the final position of the second recording unit (transport packet / application packet) is different from the boundary position of the first recording unit (sector / stream pack). In this case, a padding area (FIG. 1 (k)) is placed after the last position of the first recording unit (sector / stream pack) or the second recording unit (transport packet / application packet) recorded last. Alternatively, as 21) in FIG. 6 (h), predetermined data (for example, all 1 bits or all 0 bits) is recorded (see FIGS. 6 (i) and 6 (j)).

  A second recording area (STREAM.IFO or RTR.IFO) for storing management information relating to the data recorded in the first recording area (stream recording area 222) is recorded (FIG. 3 (d) (e) )reference).

  A plurality of the first recording units (sectors / stream packs) are collected for the third recording area (stream file information) in which the time information related to the first recording area (stream recording area 222) is recorded. 3 recording units (stream block / SOBU) are configured (see FIGS. 6B to 8E and FIGS. 8A to 8B).

  A difference value between time stamp information arranged at the head of each third recording unit (stream block / SOBU) with respect to stream data recorded in the first recording area (stream recording area 222) is a time map. Information is recorded (see FIGS. 1 (i) to (m) and FIGS. 8 (a) to 8 (d)).

  An information storage medium having a data structure in which stream data is recorded by the above method is also a feature of the present invention.

  Further, as a method for enabling partial erasure in units of transport packets while considering the I picture start position, there are the following methods.

  I) The stream object is newly divided before and after the partial erase location.

  J) STREAM. VRO file or RTR_MOV. The management file (STREAM.IFO or RTR.IFO) has stream file information information describing information on the VRO file and reproduction unit information (cell information) used when reproducing the stream data.

  K) STREAM. In which stream data is recorded. VRO file or RTR_MOV. Partial erasure processing is performed for each VRO file in units of sectors.

  L) On the management file (STREAM.IFO or RTR.IFO), the stream object is divided according to the I picture start position.

  Specifically, stream object start time information (SOB_S_APAT 542 in FIG. 7C) and stream object end time information (in FIG. 7C) in the stream file information (SOBI_GI · 251 in FIG. 7D). SOB_E_APAT 543), and after partial erasure, the value of the time stamp (1a in FIG. 7) corresponding to the transport packet (1a in FIG. 7) in which the I picture start position is recorded is the stream object start time (SOB_S_APAT 542). Corresponding to the transport packet (TP298g in FIG. 7) immediately before the transport packet in which the I picture start position that comes immediately after the stream data including the partial erasure boundary position is recorded. Time stamp (TMS298g in Fig. 7 Changing the value of the value of the stream object end time (SOB_E_APAT543) (or additional recording).

  M) On the management file (STREAM.IFO or RTR.IFO), the start / end positions in the cell information are set in correspondence with the transport packet designated for partial erasure.

  Specifically, the range of partial erasure is designated in units of transport packets, and among the remaining transport packets for the designated range, the time stamp corresponding to the first transport packet (TMS 97c in FIG. 9 (j)). ) As the start time (SC_S_APAT 283 in FIG. 9 (l)) of the corresponding cell of the new original cell, and the value of the time stamp corresponding to the last transport packet (TMS 224k in FIG. 9 (j)) as the new original The cell is changed (or added) in the management file (STREAM.IFO or RTR.IFO) as the end time of the corresponding cell (SC_E_APAT284 in FIG. 9 (l)).

  An information medium to which the above-described partial erasing method can be applied is a medium on which information can be recorded for each first recording unit (sector). This medium has a first recording area (STREAM.VRO or RTR_MOV.VRO) in which stream data is recorded, and a second recording area (in which management information relating to data recorded in the first recording area is recorded). STREAM.IFO or RTR.IFO). In the first recording area (STREAM.VRO or RTR_MOV.VRO), packet header information given for each first recording unit (sector) and stream data of the second recording unit (transport packet) Time stamp information having related time information and stream data for each second recording unit (transport packet) are packed and recorded. A plurality of the first recording units (sectors) are collected to constitute a third recording unit (stream block). Then, a fourth recording unit (stream object) that is composed of a plurality of the third recording units (stream blocks) and indicates a large collection of data with respect to the stream data is configured. In the second recording area (STREAM.IFO or RTR.IFO), time information (time map information) for each third recording unit (stream block) and start of the fourth recording unit (stream object) The data size information of the third recording unit (stream block) at the end position is recorded.

  The stream data recorded in the first recording area (STREAM.VRO or RTR_MOV.VRO) can be partially erased in the first recording unit (sector). Then, after partial erasure, a fourth recording unit (stream object) having a new size is formed, and at the start position or end position in the fourth recording unit (stream object) having the new size. At least one of the data size and time information in the third recording unit (stream block) is rewritten in the second recording area (STREAM.IFO or RTR.IFO) or new To be recorded.

  The effects obtained by the implementation of the present invention are summarized as follows.

1. In order to record the time information for each transport packet together with each transport packet as time stamp information on the information storage medium,
a) The timing at which the transport packet is transferred to the STB according to the time stamp value is known.

    b) Since the transport packet can be transferred to the decoder at a timing corresponding to the time stamp value, even if there is no buffer on the decoder side, decoding and screen display can be performed stably without failure.

    c) Since individual transport packets can be identified and sorted using the time stamp value, it is easy to specify an arrival position at the time of access and a range at the time of editing.

  2. Time stamps and transport packets are sequentially packed and recorded in the remaining part excluding the packet header in the sector, and the time stamp breaks or stream data breaks recorded for each transport packet differ from the sector boundary position. In this case, either the time stamp or the transport packet is arranged and recorded across the adjacent sectors, and the padding area is set only in the sector at the video recording end position (the last position of the stream object). Therefore, stream data can be efficiently recorded on the information storage medium. As a result, at the time of recording and recording the stream data divided for each transport packet, it is possible to record without substantially reducing the execution capacity of the information storage medium.

  3. Time stamps and transport packets are sequentially packed and recorded in the remaining part excluding the packet header in the sector, and the time stamp breaks or stream data breaks recorded for each transport packet differ from the sector boundary position. In this case, either the time stamp or the transport packet is arranged and recorded across the adjacent sectors, and the padding area is set only in the sector at the video recording end position (the last position of the stream object). Therefore, a transport packet having a size larger than the sector size (2048 kbytes) can be recorded.

  4). According to the embodiment of the present invention, the time stamp does not always come immediately after the packet header in each sector. Therefore, as a method for extracting time information for each stream block, in the embodiment of the present invention, the first time stamp arranged in each stream block (excluding the time stamp recorded across the previous stream block) Is handled as the start time of each stream block, so that time map information in the management file (STREAM.IFO or RTR.IFO) can be created. Then, access to a predetermined transport packet using this time map information becomes easy.

  5. STREAM. VRO file or RTR_MOV. When partial erasure can be performed on the stream data in the VRO file in units of sectors, the STREAM. VRO file or RTR_MOV. Partial release of a VRO file is possible. As a result, STREAM. VRO file or RTR_MOV. Effective use such as recording computer data later on the sector released from the VRO file becomes possible.

  In addition, as a partial erase unit different from the above contents, for example, when partial erase is performed only in stream block (SOBU) units (partial release of the STREAM.VRO file or the RTR_MOV.VRO file), the user has a small range of about the sector size. Even if partial erasure is specified at STREAM. VRO file or RTR_MOV. VRO file partial opening does not occur. As a result, there is a risk that the designated area for partial erasure in a fine range designated by the user cannot be used for other data recording, and there is a risk that the useless area in which information is not recorded on the information storage medium substantially increases. However, the present invention does not exclude the use of partial erasure in units of SOBU.

  6). In addition to the file (STREAM.VRO or RTR_MOV.VRO) for recording stream data on the information storage medium, a management file (STREAM.IFO or RTR.IFO) for managing stream data in the file is provided, and the management file The cell information in which the information about the cell indicating the reproduction unit at the time of reproducing the stream data is recorded is recorded. By providing start / end position information regarding the cell as time information corresponding to the time stamp, a transport packet represented by a time stamp value can be designated. As described above, by describing the cell start / end position information with time information, the reproduction range after partial erasure can be substantially specified in units of transport packets.

7). In addition to the file (STREAM.VRO or RTR_MOV.VRO) for recording stream data on the information storage medium, a management file (STREAM.IFO or RTR.IFO) for managing stream data in the file is provided and further managed. Stream object start time and stream object end time information is included in the stream file information existing in the file. After partial erasure, the time stamp value corresponding to the transport packet in which the I picture start position is recorded is reset to the value of the stream object start time, or I immediately after the stream data including the partial erasure boundary position. By setting the time stamp value corresponding to the transport packet immediately before the transport packet in which the picture start position is recorded to the value of the stream object end time, the stream data with the I picture start position as the boundary position is set. Partial erasure (division) is possible. as a result,
a) Since the decoder can always start decoding from the I picture position, display can be started from an arbitrary position in units of frames.

    b) When the I-picture position is always known from the information in the management file (STREAM.IFO or RTR.IFO), and the stream data is divided with the I-picture start position as a delimiter, so that a plurality of different stream objects are continuously played back In addition, the video can be reproduced continuously and seamlessly without distorting the screen at the break (change) of the stream object.

  8). By providing a flag indicating the I picture position in the isochronous packet headers 343 and 344, the I picture position information can be notified in real time simultaneously with the transfer of the stream data (transport packet) from the STB device 416 to the optical disk device 415. As a result, the I picture position information can be easily recorded in real time in the stream data recording file (STREAM.VRO or RTR_MOV.VRO), and the I picture position can be easily stored in the management file (STREAM.IFO or RTR.IFO). Can record information.

  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.

FIG. 1 is a view for explaining the data structure of stream data according to an embodiment of the present invention. It is a figure explaining the directory structure of the data file which concerns on one embodiment of this invention. It is a 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. It is a figure explaining the relationship between the stream object (SOB) in this invention, a cell, a program chain (PGC), etc. It is a figure explaining the relationship of the video data transfer form in digital broadcasting, IEEE1394, and a streamer. It is a figure explaining the sector structure which stores the data of a stream object. It is a figure explaining the relationship between the video information compression method in MPEG and a transport packet. It is a figure explaining the setting method of the time map information shown by FIG. 1 others. It is a figure explaining how stream object information and original cell information change before and after erasure when a part of a recorded stream object is partially erased. 5 is a diagram for explaining the data structure of the stream pack shown in others. It is a figure explaining the structure of the stream data recording / reproducing system (optical disc apparatus / streamer, STB apparatus) concerning one embodiment of this invention. FIG. 12 is a flowchart for explaining how alignment of an application packet and a stream object and padding processing at the end of the stream object are performed in the case of recording bitstream information by the system of FIG. 11. FIG. 4 is a diagram illustrating an internal data structure of streamer management information (corresponding to STREAM.IFO in FIG. 2 or 3). It is a figure explaining the internal data structure of PGC information (ORG_PGCI / UD_PGCIT of FIG. 3 or PGCI # i of FIG. 13). It is a figure explaining the internal data structure of a stream file information table (SFIT). It is a figure which illustrates the correspondence of an access unit start map (AUSM) and a stream object unit (SOBU). It is a 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). It is a 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. It is a figure explaining the data structure of the stream data which concerns on other embodiment of this invention.

Explanation of symbols

201: Information storage medium / information storage medium (DVD-RAM disk, etc.); 415 ... Optical disk device; 416 ... Set top box device.

Claims (4)

An information medium having a data area in which stream data including MPEG I picture information is recorded using a stream packet, and a management area in which management information regarding the stream data is recorded,
When the stream 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 object data called a stream object is expressed as a third data unit,
The stream data to be 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,
An information medium on which information indicating whether or not the access unit data exists is recorded in the management area when the data related to the access unit to the I picture information is the access unit data. An information medium having a data area in which stream data including MPEG I picture information is recorded using a stream packet and a management area in which management information relating to the stream data is recorded, wherein the stream packet is a first data unit. The second data unit including one or more first data units when the data unit of stream block or stream object unit is expressed as the second data unit and the object data of stream object is expressed as the third data unit. The stream data to be recorded in the data area is formed by the stream object of the third data unit configured to include one or more, and data relating to an access unit to the I picture information is represented as access unit data. The recording method using the configuration information medium as information indicating whether the access unit data is present is recorded in the management area when the,
A recording method for recording the stream data in the data area and recording the management information in the management area. An information medium having a data area in which stream data including MPEG I picture information is recorded using a stream packet and a management area in which management information relating to the stream data is recorded, wherein the stream packet is a first data unit. The second data unit including one or more first data units when the data unit of stream block or stream object unit is expressed as the second data unit and the object data of stream object is expressed as the third data unit. The stream data to be recorded in the data area is formed by the stream object of the third data unit configured to include one or more, and data relating to an access unit to the I picture information is represented as access unit data. In reproducing method using the configuration information medium as information indicating whether the access unit data is present is recorded in the management area when the,
A reproduction method for reproducing the management information from the management area and reproducing the stream data from the data area. An information medium having a data area in which stream data including MPEG I picture information is recorded using a stream packet and a management area in which management information relating to the stream data is recorded, wherein the stream packet is a first data unit. The second data unit including one or more first data units when the data unit of stream block or stream object unit is expressed as the second data unit and the object data of stream object is expressed as the third data unit. The stream data to be recorded in the data area is formed by the stream object of the third data unit configured to include one or more, and data relating to an access unit to the I picture information is represented as access unit data. The reproducing apparatus using the configuration information medium as information indicating whether the access unit data is present is recorded in the management area when the,
A reproduction apparatus comprising: means for reproducing the management information from the management area; and means for reproducing the stream data from the data area.

Images