JP3569248B2 - Stream information processing system - Google Patents

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention generates (encodes) bit stream information such as digital broadcasting or stream data transmitted with a packet structure, records the encoded stream data on an information medium, and decodes or records the encoded stream data. The present invention relates to a method of partially erasing (provisionally erasing / mainly erasing) stream data that has been erased.
[0002]
[Prior art]
In recent years, TV broadcasting has entered the age of digital broadcasting. Accordingly, there has been a demand for a device for storing digital data of digital TV broadcasting as digital data regardless of its content, that is, a so-called streamer.
[0003]
In digital TV broadcasting currently being broadcast, an MPEG transport stream is employed. In the field of digital broadcasting using moving images, the MPEG transport stream will be used as a standard in the future.
[0004]
As a streamer for recording the digital broadcast data, a home digital VCR such as a D-VHS (digital VHS) is currently on the market. In the streamer using the D-VHS, the broadcasted bit stream is directly recorded on a tape. Therefore, a plurality of programs are multiplexed and recorded on the video tape.
[0005]
At the time of playback, all data is sent from the VCR to a set-top box (digital TV receiving apparatus: abbreviated as STB hereinafter) as it is when playing 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 is played (playback of video + audio or the like).
[0006]
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 and reproduce it.
[0007]
A streamer using a large-capacity disk medium such as a DVD-RAM can be considered as a promising candidate that can solve such a disadvantage of a tape (difficulty of random access). In this case, considering random access and trick play, it is necessary to record management data together with broadcast data.
[0008]
[Problems to be solved by the invention]
In general, when a DVD-RAM disk is used as an information storage medium, an ECC block is configured for every 16 sectors, and data interleaving (rearrangement) and an error correction code are added in the ECC block. Therefore, in order to erase or rewrite only a specific sector in an ECC block, and to additionally write data, the following complicated processing is required.
[0009]
That is, once all data in the ECC block is read (read) and rearranged (deinterleaved) in the buffer memory, data for a specific sector is erased or rewritten, and additional writing is performed (modify). In this case, a process called "read-modify-write" is required in which an interleave (rearrangement) and an error correction code are added and recorded again.
[0010]
This process is very time-consuming, and has a problem that recording and partial erasure of stream data cannot be performed in real time.
[0011]
The present invention has been made in view of the above circumstances, and an object of the present invention is to improve stream information recording processing.
[0012]
[Means for Solving the Problems]
In order to achieve the above object, in an embodiment of the present invention, an optical disc having a data area for recording stream data and a management area for recording management information of the stream data, When a data packet called a transport packet or an application packet is expressed as a first data unit, a data unit called a stream block or a stream object unit is expressed as a second data unit, and object data called a stream object is expressed as a third data unit Wherein the third data unit includes one or more second data units including one or more first data units. The stream object forms the stream data recorded in the data area. Further, the second data unit includes header information, and the header information includes information on the time of the first data unit. Header information including information on the time is recorded in the data area different from the management area.
[0013]
BEST MODE FOR CARRYING OUT THE INVENTION
Hereinafter, a method for generating stream data, a method for recording the stream data, a method for partially deleting recorded stream data, and the like according to an embodiment of the present invention will be described with reference to the drawings.
[0014]
FIG. 1 is a diagram illustrating a data structure of stream data according to an embodiment of the present invention.
[0015]
Stream data recorded on an information storage medium such as a DVD-RAM disk is organized as a stream object (hereinafter abbreviated as SOB as appropriate) for each content of video information in the stream data. Each SOB is formed by stream data obtained by one real-time continuous recording.
[0016]
FIG. 1F shows one SOB # A · 298 among one or more stream objects. When this stream data is recorded on a DVD-RAM disk, each is recorded with a sector of 2048 kbytes as a minimum unit. Further, 16 sectors are combined into one ECC block, and interleaving (reordering of the data arrangement order) and addition of a correction code for error correction are performed in the same ECC block.
[0017]
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 this stream block. Here are the features of the present invention.
[0018]
In this embodiment, how many ECC blocks constitute 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. 1E, the stream block # 1 is composed of two ECC blocks # α and # β, and the stream block # 2 is composed of three ECC blocks # γ, # δ and # ε. I have. In the DVD streamer, one stream block (stream object unit SOBU) is composed of two ECC blocks (32 sectors).
[0019]
Each ECC block is composed of 16 sectors as shown in FIG. Therefore, as can be seen from FIGS. 1D and 1E, a stream block (or SOBU) # 1 composed of two ECC blocks corresponds to 32 sectors (sector No. 0 to sector No. 31).
[0020]
That is, if 1 sector = 2 kbytes, the present invention can be implemented with a stream block (SOBU) having a fixed size of 64 kbytes (32 sectors).
[0021]
The content of each sector corresponds to a stream pack (details will be described later with reference to FIG. 9 and the like). Then, for example, the sector No. As shown in FIG. 1C, the stream pack corresponding to 0 (FIG. 1D) includes a pack header 1, a PES header 6, a stream block header (described later with reference to FIG. 11) 11, and And a data area 21. Also, the sector No. As shown in FIG. 1C, the stream pack corresponding to 1 (FIG. 1D) includes a pack header 2, a PES header 7, a sector data header (described later with reference to FIG. 12) 12, a data And an area 22.
[0022]
An example of the internal configuration of the PES headers 6 and 7 in FIG. 1C will be described later with reference to FIG.
[0023]
As shown in FIG. 1 (b), the data area 21 of FIG. 1 (c) is an array of pairs of a time stamp and a transport packet (time stamp a, transport packet a, time stamp b,. Port packet d). Similarly, the data area 22 includes another arrangement of pairs of time stamps and transport packets. On the other hand, the rear data area 23 includes a transport packet f, an end code 31, and a padding area 36, as shown in FIG.
[0024]
A plurality of pairs of a time stamp and a transport packet in FIG. 1B become a bit stream having an arrangement as shown in FIG.
[0025]
The data structure of stream block # 1 (FIG. 1 (e)) in front of SOB # A · 298 (FIG. 1 (f)) is as shown in FIGS. 1 (d) and 1 (b). The data structure of stream block # 2 (FIG. 1 (g)) subsequent to is as follows.
[0026]
That is, the backward sector No. of the last ECC block # ε of the stream block # 2. 78 (FIG. 1 (h)) includes a pack header 3, a PES header 8, a sector data header 13, and a data area 24, as shown in FIG. 1 (i). In addition, the last sector No. of the ECC block # ε. 79 (FIG. 1 (h)) includes the pack header 4 and the padding packet 40 as shown in FIG. 1 (i).
[0027]
Sector No. The data area 24 includes a transport packet z, an end code 32, and a padding area 37, as shown in FIG. In addition, the last sector No. The padding packet 79 includes the PES header 9 and the padding area 38 as shown in FIG.
[0028]
The contents of the padding area 38 will be described later with reference to FIG.
[0029]
FIG. 2 is a diagram illustrating a directory structure of a data file according to an embodiment of the present invention.
[0030]
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.
[0031]
A data file 103 having the following contents is stored in the DVD_RTR (DVD_RTAV) directory 102.
[0032]
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.
[0033]
Also, as the data body (content information), 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.
[0034]
A sub-directory 110 for storing other information can be provided in the root directory 100 at a higher level than the sub-directory 101 including the data file 103.
[0035]
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, and a subdirectory 113 for storing computer data.
[0036]
For data transmitted in a packet structure on a wired or wireless data communication path, data recorded on an information storage medium while retaining the packet structure is referred to as “stream data”.
[0037]
The stream data itself is STREAM. VRO (or SR_TRANS.SRO) 106 is collectively recorded with a file name. The file in which the management information for the stream data is recorded is STREAM. IFO (or SR_MANGR.IFO and its backup file SR_MANGR.BUP) 105.
[0038]
A file in which analog video information handled by a VCR (VTR) or a conventional TV is digitally compressed based on the MPEG2 standard and recorded is RTR_MOV. VRO (or VR_MOVIE.VRO) 107, which is a file in which still image information including after-recorded audio or background audio is collected is RTR_STO. VRO (or VR_STILL.VRO) 108 whose dubbing audio information file is RTR_STA. VRO (or VR_AUDIO.VRO) 109.
[0039]
FIG. 3 is a diagram for explaining a recording data structure on an information medium according to an embodiment of the present invention, for example, a rewritable optical disk 201 such as a DVD-RAM disk.
[0040]
As shown in FIG. 3B, a lead-in area 204 includes a lead-in area 204, which is located between an end in the inner circumferential direction 202 and an end in the outer circumferential 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 includes an embossable and rewritable data zone, and the lead-out area 205 includes a rewritable data zone. The data area 207 is also composed of a rewritable data zone.
[0041]
In the data area 207, as shown in FIG. 3C, computer data and audio & video data can be mixedly recorded. In this example, an audio & video data area 210 is sandwiched between the computer data area 208 and the computer data area 209.
[0042]
In the audio & video data area 210, as shown in FIG. 3D, mixed recording of a real-time video recording area 221 and a stream recording area 222 is possible. (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. 3E, in the real-time video recording area 221, the navigation data RTR. IFO (VR_MANGR.IFO) 104 and a 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.
[0043]
Similarly, as shown in FIG. 3 (e), the stream recording area 222 includes the 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.
[0044]
Although not shown in FIGS. 3D and 3E, in the stream recording area 222, the application-specific navigation data SR_PRIVT, DAT / SR_PRIVT. The BUP 105a can also be recorded.
[0045]
The SR_PRIVT and DAT 105a are navigation data unique to each application connected (supplied) to the streamer, and need not be recognized by the streamer.
[0046]
STREAM. The IFO (or SR_MANGR.IFO) 105 has a data structure as shown in FIGS.
[0047]
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, an 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. An application private data manager (APDT_MG) 236 that manages the DAT 105a.
[0048]
The stream file information table (SFIT) 232 in FIG. 3F includes, as shown in FIG. 3G, the 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 original cell information # 1,272, # 2,273.
[0049]
Each stream object information (for example, SOBI # A · 242) in FIG. 3F can include stream object general information (SOBI_GI) 251, time map information 252, and the like as shown in FIG. .
[0050]
Also, as shown in FIG. 3 (h), each original cell information (for example, # 1 · 272; described below, which corresponds to the SCI shown in FIG. 28) of the original cell information shown in FIG. 28, a cell ID 282, a corresponding cell start time (corresponding to SC_S_APAT described later in FIG. 15 (l), FIG. 28 and others), and a corresponding cell end time (corresponding to FIG. 15 described later). (L), corresponding to SC_E_APAT shown in FIG. 28 and the like) 284.
[0051]
The information content of FIG. 3F will be described later with reference to FIG.
[0052]
The time map information 252 of FIG. 3H included in the SOBI # A of FIG. 3G includes a stream block number 261, a first stream block size 262, and a first stream block, as shown in FIG. The time difference 263, the second stream block size 264, the second stream block time difference 265,... The content of each stream block time difference constituting the time map information 252 will be described later with reference to FIG.
[0053]
FIG. 4 is a diagram for explaining the relationship between a stream object (SOB), a cell, a program chain (PGC) and the like in the present invention. Hereinafter, the relationship between SOB and PGC in the present invention will be described using the example of FIG.
[0054]
The stream data recorded in the stream data (STREAM.VRO or SR_TRANS.SRO) 106 constitutes a stream block as a group of one or more ECC blocks, and recording and partial erasure processing are performed in units of this stream block. The stream data forms a unit called a stream object for each content of information to be recorded (for example, for each program in digital broadcasting).
[0055]
This STREAM. The 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 includes navigation data STREAM. IFO (SR_MANGR.IFO) 105 (see the bottom of FIG. 4 and FIGS. 3E and 3F).
[0056]
As shown in FIGS. 3F and 3G, the management information (STREAM.IFO 105) for each stream object # A • 298 and # B • 299 in FIG. It is recorded as object information (SOBI) # A · 242 and # B · 243.
[0057]
The inside of each of the stream object information (SOBI) # A · 242 and (SOBI) # B · 243 includes time map information 252 mainly describing data size, time information, and the like for each stream block.
[0058]
At the time of reproducing stream data, information of a program chain (PGC) composed of a series of one or more cells (corresponding to PGCI # i in FIG. 28 described later) is used. Stream data can be reproduced according to the setting order of the cells constituting the PGC.
[0059]
PGC includes STREAM. An original PGC 290 (ORG_PGCI · 233 in FIG. 3 (f)) capable of continuously reproducing all stream data recorded in the VRO (SR_TRANS.SRO) 106, and a place and an order desired by the user to be reproduced are arbitrary. There are two types of user-defined PGCs # a • 293 and # b • 296 (corresponding to the contents of UD_PGCIT • 234 in FIG. 3F).
[0060]
The original cells # 1, 291 and # 2, 292 constituting the original PGC 290 basically exist in one-to-one correspondence with the stream objects #A, 298 and #B, 299.
[0061]
On the other hand, user-defined cells # 11-294, # 12-295, and # 31-297 constituting the user-defined PGC are located at arbitrary positions within the range of one stream object # A-298 or # B-299. Can be set.
[0062]
Although the sector size of each stream block can be variously set, a preferred embodiment is a stream block of 2 ECC blocks (32 sectors) and a fixed size (64 kbytes) as in stream block # 1 in FIG. An object unit (SOBU) may be adopted as a stream block.
[0063]
Fixing the stream block to a fixed-size (for example, 2 ECC blocks = 32 sectors = 64 kbytes) SOBU has the following advantages:
(01) Even if stream data is erased or rewritten in SOBU units, the ECC block of the SOBU does not affect the ECC blocks of SOBUs other than those to be erased or rewritten. Therefore, de-interleaving / re-interleaving of ECC (for SOBUs not subject to erasing or rewriting) due to erasing or rewriting does not occur;
(02) The access position to the recording information in an arbitrary SOBU can be specified by the number of sectors (or another parameter corresponding to the number of sectors; for example, information of a stream pack and an application packet group in FIG. 9 described later). For example, when accessing the intermediate position of a certain SOBU #k, the 16th sector from the boundary between SOBU # k-1 and SOBU #k (or the position of the application packet corresponding to the 16th sector) may be specified.
[0064]
FIG. 5 is a diagram illustrating the contents of the stream block size and the stream block time difference in the time map information. Hereinafter, the contents of each data in the time map information 252 will be described with reference to FIG.
[0065]
As exemplified in FIGS. 5F, 5G, and 5H, the stream object (SOB) # A · 298 is composed of two stream blocks # 1 and # 2.
[0066]
In the example of FIGS. 5F and 5H, the data size of the stream block # 1 constituting the SOB # A · 298 is composed of 2 ECC blocks (# α, # β) and corresponds to 32 sectors (FIG. 5E). (I)). That is, the first stream block size 262 (FIG. 5 (j)) in the time map information 252 (FIGS. 5 (a) (k)) is 32 sectors (64 kbytes).
[0067]
The stream block # 1 (FIG. 5 (f)) at the head of SOB # A • 298 (FIG. 5 (g)) has a sector No. 0 (FIG. 5 (e)) and the sector No. A time stamp a is recorded at the head of the data area 21 (FIG. 5D) included in 0.
[0068]
Further, the stream block # 2 (FIG. 5 (f)) subsequent to the SOB #A 298 (FIG. 5 (g)) has a sector number. 32 (FIG. 5 (e)), and has a sector No. A time stamp p is recorded at the head of the data area 311 (FIG. 5D) included in the P.32.
[0069]
As shown in FIG. 5C, the time stamp value of the first stream data of stream block # 1 is time stamp a, and the time stamp value of the first stream data of next stream block # 2 is time stamp p. Has become.
[0070]
The value of the first stream block time difference 263 in FIG. 5B (corresponding to the stream block time difference 263 in FIG. 3I) is a difference value between the above time stamp p and time stamp a ([time stamp p]-[ Time stamp a]).
[0071]
The time map information 252 in FIG. 5A can be handled as including the access data unit AUD in the stream object information SOBI described later with reference to FIG. The information (such as the access unit start map AUSM) included in the AUD can specify the SOBU including the information to be accessed.
[0072]
FIG. 6 is a diagram illustrating a method of specifying a cell range in an original cell and a user-defined cell.
[0073]
The range of each cell can be specified by specifying the start time and end time.
[0074]
Specifically, the start time 283 of the corresponding cell and the end time 284 of the corresponding cell in the original cell before the execution of the partial erasure (just after the recording of the stream data) described later with reference to FIG. The value of the first time stamp a and the value of the last time stamp z (FIG. 6 (c)) in the corresponding stream object # A · 298 (FIG. 6 (f)) are used as the time.
[0075]
On the other hand, in the time range specification in the user-defined cell # 12.295 (FIG. 6 (k)), an arbitrary time can be specified. For example, as shown in FIGS. 6 (i) and 6 (j), the values of the time stamps d and n corresponding to the specified transport packets d and n are changed to the values of the start time 331 of the corresponding cell and the end time 332 of the corresponding cell. Can be set as
[0076]
FIG. 6F illustrates a case where the stream object (SOB) # A · 298 is composed of two stream blocks # 1 and # 2.
[0077]
In the examples of FIGS. 6E and 6G, the stream block # 1 is composed of 32 sectors (sectors No. 0 to No. 31), and the stream block # 2 is 48 sectors (sectors No. 32 to No. 79). It is composed of
[0078]
The head sector No. of the stream block # 1. 0 includes a pack header 1, a PES header 6, a stream block header 11, a data area 21, and the like as shown in FIGS.
[0079]
Also, the backward sector No. of the stream block # 2. Reference numeral 78 includes a pack header 3, a PES header 8, a sector data header 13, a data area 24, and the like, as shown in FIGS.
[0080]
Further, the sector No. shown in FIG. 6 includes a pack header 2, a sector data header 12, a data area 22, and the like as shown in FIG. 6 (h). 33, a sector data header 321, a data area 312 and the like are recorded as shown in FIG.
[0081]
As shown in FIGS. 6C and 6I, the data area 21 shown in FIGS. 6D and 6H has a pair of a time stamp a and a transport packet a or a time stamp d and a transport packet d. Pairs are recorded.
[0082]
In the area of the data area 24 shown in FIG. 6D, a plurality of pairs of a time stamp and a transport packet, an end code 32 following a pair of the last time stamp z and the transport packet z, and a padding area 37 (Corresponding to the padding area 37 in FIG. 1 (j)).
[0083]
The data area 22 in FIG. 6H includes a transport packet d including the contents subsequent to the transport packet d in the data area 21 as shown in FIG. 6I. That is, in this example, the contents of the transport packet d are recorded separately from the data area 21 and the data area 22.
[0084]
The first half (the data area 21 side) of the transport packet d in FIG. 6 (i) corresponds to the last partial packet in FIG. 8 (f) described later, and the second half of the transport packet d in FIG. 6 (i). The (data area 22 side) corresponds to a leading partial packet in FIG.
[0085]
Further, as shown in FIG. 6I, a pair of a time stamp n and a transport packet n and other similar pairs are recorded in the data area 312 of FIG. 6H.
[0086]
Here, the start time 331 (FIG. 6 (j)) of the cell corresponding to the place where the user or the like has designated the reproduction start time is a time stamp d for the entire two transport packets d divided into the data areas 21 and 22. (FIG. 6 (i)).
[0087]
When the transport packet is read as an application packet and the application packet arrival time is APAT, the cell start time 331 can be expressed as a cell start APAT.
[0088]
The end time 332 (FIG. 6 (j)) of the cell corresponding to the place where the user or the like has designated the reproduction end time is specified by the time stamp n (FIG. 6 (i)) for the transport packet n in the data area 312. Is done. This cell end time 332 can be expressed as a cell end APAT.
[0089]
The above-described cell start time (cell start APAT) 331 and cell end time (cell end APAT) 332 are recorded in the user-defined cell information # 12.295 as shown in FIG.
[0090]
This user-defined cell information # 12 • 295 can be recorded in the user-defined PGC information table 234 shown in FIG.
[0091]
The above is the cell start / end time information relating to the user-defined cell information (information of the user-defined PGC). it can.
[0092]
That is, the start time 283 of the corresponding cell in FIG. 6B can be indicated by the head time stamp a in FIG. 6C, and the end time 284 of the cell can be indicated by the tail time stamp z in FIG.
[0093]
The start time 283 of the corresponding cell in FIG. 6B can correspond to a cell start APAT (including a stream cell start APAT (SC_S_APAT) or an erasure start APAT (ERA_S_APAT) described later).
[0094]
The end time 284 of the corresponding cell in FIG. 6B can correspond to a cell end APAT (including a stream cell end APAT (SC_E_APAT) or an erasure end APAT (ERA_E_APAT) described later).
[0095]
The cell start time (cell start APAT) 283 and cell end time (cell end APAT) 284 are recorded in the original cell information # 1, 272 as shown in FIG. 6A.
[0096]
This original cell information # 1 272 can be recorded in the original PGC information 233 shown in FIG.
[0097]
The cell start APAT and the cell end APAT will be described in detail later with reference to FIGS. 18 to 21 and FIGS. 30 to 33.
[0098]
FIG. 7 is a diagram illustrating a configuration of a stream data recording / reproducing apparatus (streamer) according to an embodiment of the present invention.
[0099]
Hereinafter, the internal structure of a stream data recording / reproducing apparatus (streamer) as a preferred embodiment of the present invention will be described with reference to FIG.
[0100]
The stream data recording / reproducing apparatus according to this embodiment includes an encoder unit 401, a decoder unit 402, an STB unit 403, a main MPU unit 404, a V (video) mixing unit 405, a frame memory unit 406, a key input unit 407, and a display unit 408. 409, a data processor (D-PRO) unit 410, a temporary storage unit 411, an A / V (audio / video) input unit 412, a TV tuner A section 413 is provided.
[0101]
The stream data recording / reproducing apparatus further includes an interface (I / I / I) for transmitting a digital video signal from the satellite antenna 421 connected to the STB unit 403, the system time counter (STC) unit 424, and the V mixing unit 405 to the personal computer (PC) 435. F) 434, and a D / A converter 436 for an analog TV 437.
[0102]
Here, the V mixing unit 405 has a function of appropriately mixing the digital video signal from the V-PRO unit 438 of the decoding unit 402 and the digital video signal 423 from the STB unit 403. With this mixing function, for example, a broadcast image from the STB unit 403 can be displayed on the left side of the display screen of the TV 437, and an image reproduced from the disc 201 can be displayed on the right side of the display screen of the TV 437.
[0103]
Alternatively, the broadcast image from the STB unit 403 and the reproduced image from the disc 201 can be displayed on the monitor screen of the PC 435 so as to overlap the overlapping window.
[0104]
In the above configuration, the encoder unit 401 selects the video / audio A / D converter 414, the digital video signal from the A / D converter 414 or the digital video signal 423 from the STB part 03, and performs video encoding. Selector 415 to be sent to the section 416, a video encoding section 416 for encoding a video signal from the selector 415, an audio encoding section 417 for encoding an audio signal from the A / D conversion section 414, and a closed caption (cc) from the TV tuner section 413. It comprises an SP encoder 418 for encoding a signal or a teletext signal into a sub-picture (SP), a formatter 419, and a buffer memory 420.
[0105]
On the other hand, in the decoding unit 402, a separating unit 425 including a memory 426, a video decoding unit 428 including a reduced image (thumbnail picture) generating unit 439, an SP decoding unit 429, an audio decoding unit 430, a TS packet transfer unit 427, It comprises a video processor (V-PRO) unit 438 and an audio D / A conversion unit 432.
[0106]
The digital audio signal decoded by the decoding unit 430 can be externally output via an interface (I / F) 431. A speaker 433 is driven by an analog audio signal obtained by converting the digital audio signal into an analog signal by the D / A converter 432 via an external audio amplifier (not shown).
[0107]
The D / A conversion section 432 is configured to be able to perform D / A conversion of the digital audio signal 422 from the STB section 403 as well as the digital audio signal from the audio decoding section 430.
[0108]
When transferring the reproduction data from the disc 201 to the STB unit 403, the TS packet transfer unit 427 changes the reproduction data (bit stream) from the separation unit 425 into a transport packet (TS packet), and transmits the data from the STC 424. The TS packet may be sent to the STB unit 403 by adjusting the transfer time to the time information.
[0109]
The main MPU unit 404 in FIG. 7 includes a work RAM 404a as a working memory, a control program named stream data creation control unit 404b, a control program named stream data reproduction control unit 404c, and a partial erase / It includes a control program named temporary erase control unit 404d.
[0110]
Here, in order to read and write the file management area (navigation RTR.IFO 104, STREAM.IFO 105 in FIG. 2 or FIG. 3 (e)), the main MPU unit 404 provides a dedicated microcomputer to the D-PRO unit 410. Connected via a bus.
[0111]
The control at the time of recording in the stream data recording / reproducing apparatus is performed by the main MPU unit 404 using the control program (sequential control program).
[0112]
First, the flow of a video signal during recording in the apparatus shown in FIG. 7 will be described. At the time of recording, a series of processing is performed according to a sequential program named a stream data creation control unit 404b in the main MPU unit 404.
[0113]
That is, the stream data transmitted from the STB unit 403 to the encoding unit 401 via the transmission path conforming to the IEEE 1394 standard is first transferred to the formatter unit 419.
[0114]
The IEEE 1394 receiving side of the formatter unit 419 reads the time from the start of the stream data transfer based on the time count value of the STC 424. The read time information is sent to the main MPU unit 404 as management information and stored in the work RAM unit 404a.
[0115]
The main MPU unit 404 creates delimiter information for separating stream data into stream blocks (each VOBU in a real-time RTR recorder, and each SOBU in a streamer) based on the time information, and generates a cell corresponding to the delimiter information. And the PGC separation information are created and sequentially recorded in the work RAM unit 404a in the main MPU unit 404.
[0116]
The formatter unit 419 converts the stream data sent from the STB unit 403 in the form of FIG. 1A according to the instruction from the stream data creation control unit 404b of the main MPU unit 404, as shown in FIGS. The stream is converted into a shape (a stream pack sequence shown in FIG. 8H described later), and the converted stream pack sequence is input to the D-PRO unit 410. The input stream pack has the same fixed size of 2048 bytes as the sector. The D-PRO unit 410 collects the input stream packs in units of 16 sectors into ECC blocks and sends the ECC blocks to the disk drive unit 409.
[0117]
Here, when the disk drive unit 409 is not ready for recording on the RAM disk (information storage medium) 201, the D-PRO unit 410 transfers the recording data to the temporary storage unit 411 and temporarily stores the data. It waits until the disk drive unit 409 is ready for data recording.
[0118]
When the disk drive unit 409 is ready for recording, the D-PRO unit 410 transfers the data stored in the temporary storage unit 411 to the disk drive unit 409. Thus, recording on the disk 201 is started. When the data stored in the temporary storage unit 411 is recorded, the subsequent data is seamlessly transferred from the formatter unit 419 to the D-PRO unit 410.
[0119]
Here, the temporary storage unit 411 is assumed to be a large-capacity memory in order to enable high-speed access and hold recording data for several minutes or more.
[0120]
Next, data processing during reproduction will be described. The control at the time of reproduction in the stream data recording / reproducing apparatus is performed by the main MPU unit 404 in accordance with a sequential program named stream data reproduction control unit 404c.
[0121]
First, stream data is reproduced from the RAM disk (information storage medium) 201 by the disk drive unit 409. The reproduced stream data is transferred to the decoder unit 402 via the D-PRO unit 409.
[0122]
Inside the decoder unit 402, the separation unit 425 receives the transport packet in the reproduced stream data.
[0123]
The separation unit 425 transfers video packet data (MPEG video data) to the video decoding unit 428 and transfers audio packet data to the audio decoding unit 430 according to a stream ID 603 and a sub-stream ID described later with reference to FIG. The sub-picture packet data is transferred to the SP decoding unit 429.
[0124]
The video data decoded by the video decoding unit 428 is converted into an analog TV signal via the V mixing unit 405 and the D / A conversion unit 436, and is transferred to the TV 437 for image display.
[0125]
At the same time, the audio signal decoded by the audio decoding unit 430 is also sent to the D / A conversion unit 432, where it is converted into digital audio data. The converted digital audio data is transferred to a digital input of an external audio device (not shown) via the I / F 431. Alternatively, the converted digital audio data is converted into an analog audio signal by the D / A converter 432, and sent to the speaker 433 via an audio amplifier (not shown).
[0126]
The signal flow in the stream data recording / reproducing apparatus (streamer) according to the embodiment of the present invention has been described above.
[0127]
As described above, the stream data to be recorded on the DVD-RAM disk (information storage medium) 201 is converted into the structure shown in FIGS. The stream data recording procedure focusing on this conversion process will be described later with reference to the flowchart of FIG.
[0128]
The procedure for reproducing the stream data will be described later with reference to the flowchart in FIG.
[0129]
FIG. 8 is a diagram for explaining the correspondence between digital broadcast contents, video data transfer modes in IEEE 1394, and stream packs in the streamer.
[0130]
In digital broadcasting, video information compressed according to the MPEG2 standard is transferred in transport packets. As shown in FIG. 8B, the transport packet includes a transport packet header 511 and a payload 512 in which a data body of recording information is recorded.
[0131]
As shown in FIG. 8A, the transport packet header 511 includes a payload unit start indicator 501, a packet ID (PID) 502, a random access indicator 503, a program clock reference 504, and the like.
[0132]
MPEG-compressed video information includes I picture information, B picture information, and P picture information. In the first transport packet in which I picture information (571 in FIG. 9 described later) is recorded, a flag of “1” is set in the random access indicator 503 in FIG. 8A. Also, in the first transport packet of each of the B and P picture information (573, 574, 572 in FIG. 9 described later), a flag of “1” is set in the payload unit start indicator 501 in FIG. 8A.
[0133]
Using the information of the random access indicator 503 and the payload unit start indicator 501, an I-picture mapping table (641 in FIG. 11 described later) and a B, P-picture start position mapping table (642 in FIG. 11 described later) Information is created.
[0134]
For example, for a transport packet in which the flag of "1" is set in the payload unit start indicator 501 shown in FIG. 8A, a corresponding location in the B, P-picture start position mapping table (642 in FIG. 11) is used. Becomes "1".
[0135]
In digital broadcasting, video information and audio information are transferred in different transport packets. Then, the distinction of each information is identified by the packet ID (PID) 502 in FIG. Using the information of the PID 502, a video packet mapping table (643 in FIG. 11 described later) and an audio packet mapping table (644 in FIG. 11 described later) are created.
[0136]
As shown in FIG. 8C, in digital broadcasting, a plurality of programs (program 1 to program 3 in this example) are packet-divided and transmitted to one transponder in the form of packets.
[0137]
For example, the information of the transport packet header 511 and the payload (recording information) 512 of FIG. 8B are transferred by the transport packets b · 522 and e · 525 of the program 2 shown in FIG. 8C.
[0138]
Now, it is assumed that the program 2 shown in FIG. 8C is recorded on the information storage medium 201 shown in FIG. 3 or FIG. 7 by, for example, an operation of a digital broadcast receiver (a user of the STB in FIG. 7). Try. In this case, the STB unit 403 in FIG. 7 extracts only the transport packets b and e of the program 2 in FIG. 8C.
[0139]
At this time, in the STB unit 403, as shown in FIG. 8D, the time information when the transport packets b 522 and e 525 are received is added in the form of time stamps 531 and 532.
[0140]
Thereafter, when data is transferred from the STB unit 403 of FIG. 7 to the formatter unit 419 according to the IEEE 1394 transfer method, the set of the time stamp 531 and the transport packet 522 is fine as shown in FIG. It will be split and transferred.
[0141]
The formatter unit 419 of FIG. 7 converts the stream data transferred from the STB unit 403 by IEEE1394 into the format of FIG. 8D (the shape of FIG. 1A or the format of FIGS. 8F, 8G, and 8H). (Corresponds to the shape) once. Then, a bit stream in the format of FIG. 1A or FIG. 8F, FIG. 8G, or FIG. 8H (the stream pack sequence of FIG. 8H) is recorded on the information storage medium 201.
[0142]
Specifically, in one embodiment of the present invention, at the beginning of each sector (FIGS. 1 (d) and (h)), pack headers 1, 2, 3, and 4 in which system clock information and the like are recorded PES headers 6, 7, 8, and 9 are arranged (see FIGS. 1 (c) (i) and 6 (d)). Immediately after that, sector data headers 12 and 13 (FIGS. 1 (c) (i) and 6 (d)) are recorded, but only the first sector of each stream block is not a sector data header but a stream block header. 11 is recorded (FIGS. 1C and 6D).
[0143]
A plurality of time stamps and transport packets (FIG. 1A) are sequentially packed in the data areas 21, 22, 23, and 24 (FIGS. 1C and 1I). 1 (b); packet d; packet b in FIG. 8 (e) spans a plurality of sectors (No. 0 and No. 1 in FIG. 1 (d); partial packets in FIG. 8 (f) (g)). Recorded. Here, there is one of the features of the present invention.
[0144]
By using a data structure taking advantage of this feature, a packet having a size larger than a sector size (for example, 2048 bytes) can be recorded. This will be further described.
[0145]
In digital broadcasting, as shown in FIG. 8C, a multiplexing / demultiplexing method corresponding to a multiprogram called a transport stream is adopted, and the size of one transport packet b.522 is 188 bytes (or 183 bytes). Often.
[0146]
As described above, one sector size is 2048 bytes, and even if various header sizes are subtracted, a digital broadcasting transformer is included in one data area 21, 22, 23, 24 (FIG. 1 (c) (i)). About 10 port packets can be recorded.
[0147]
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.
[0148]
In addition to recording a plurality of transport packets in one data area 21, 22, 23, 24 (FIGS. 1 (c) (i)) as in digital broadcasting, the packet size is not limited to long packets. In order to record even a packet having a large size, a data structure utilizing the above-mentioned feature (a feature that can record one packet of data over a plurality of packets) is used, so that one packet can be divided into a plurality of data areas 21, 22,. 23 and 24 are continuously recorded.
[0149]
Then, all packets such as transport packets for digital broadcasting and long packets for digital communication can be recorded in the stream block without depending on the packet size.
[0150]
Although a normal packet has a time stamp, the time stamp can be omitted from a partial packet as shown in FIG.
[0151]
In this manner, the partial packet divided at the boundary between two adjacent stream packs (FIG. 8 (h)) (the size of the partial packet is 1 to 187 bytes if each packet is 188 bytes; the average is 100 bytes) Can be used effectively for information recording. In addition, the storage capacity of the medium 201 can be increased by the time stamp omitted for the partial packet (for example, 4 bytes per time stamp).
[0152]
Note that the position of the time stamp immediately after the head part packet in FIG. 8G can be specified by a first access point 625 in FIG. 12B or a FIRST_AP_OFFSET in FIG. 12C described later.
[0153]
By the way, when a surplus portion occurs in the stream block, padding data (information that can be recognized as an area where data is not recorded) is recorded. For example, as shown in FIG. 1B, the end code 31 is arranged after the last transport packet f in the stream block # 1, and the remaining part is a padding area. The padding areas 37 and 38 in FIG. 1 (j) are similar padding data areas.
[0154]
The specific internal data structure of the padding area will be described later with reference to FIG.
[0155]
FIG. 9 is a diagram for explaining the relationship between the video information compression method in MPEG and the transport packets, and the relationship between the transport packets in MPEG and the application packets in the streamer.
[0156]
As described above, in digital broadcasting, video information is compressed and transferred according to the MPEG2 standard.
[0157]
As shown in FIG. 9, the compressed information 561 of the I picture 551 is recorded as I picture information 571 in transport packets a, b,. The difference information 563 and 564 of the B picture 553 are recorded as B picture information 573 in the transport packets d,. The difference information 565, 566 of the B picture 554 is recorded as B picture information 573, 574 in the transport packets d, f,. Then, the difference information 562 of the P picture 552 is recorded as P picture information 572 in the transport packets h,.
[0158]
As described above, each of the I, B, and P picture information is recorded in different transport packets.
[0159]
When such a transport packet is recorded in the streamer, the contents of the transport packet are transferred to a packet with a time stamp called an application time stamp (ATS) (application packet).
[0160]
Then, a group of ATS-attached application packets (usually around 10 packets) is stored in the application packet area in the stream PES packet.
[0161]
One obtained by adding a pack header to this stream PES packet is one stream pack illustrated in FIG.
[0162]
The stream PES packet is composed of a PES header, a substream ID, an application header, an application header extension (optional), a stuffing byte (optional), and an application packet area for storing the ATS-attached application packet group. You.
[0163]
The contents of the PES header (stream PES packet header) will be described later with reference to FIG. The application header (corresponding to the stream block header 11 or the sector data header 12) will be described later with reference to FIGS.
[0164]
FIG. 10 is a diagram for explaining the internal structure of the PES header shown in FIG. 1, FIG. 8, FIG. 9, and the like.
[0165]
As shown in FIG. 10B, the PES header 601 in FIG. 10A includes a packet start code prefix 602, a stream ID 603, a reproduction time stamp 604, and the like. The PES header 601 corresponds to the PES headers 6 to 9 in FIGS. 1C, 1I, and 1J, the PES headers 6 to 7 in FIG. 8H, the PES header 6 in FIG.
[0166]
The stream PES header in FIG. 10D includes a packet start code prefix, a stream ID (private stream 2), a PES packet length, a substream ID, and the like. This stream PES header is the same as the stream PES header in FIG. 9 and has contents corresponding to the PES header 601 in FIG.
[0167]
When the PES header 9 in FIG. 1J has the internal structure of the PES header 601 shown in FIG. 10A, according to the MPEG standard, the stream ID 603 (FIG. 10B) of the PES header is “10111110”. , The packet having the PES header is defined as a padding packet 40 (FIG. 1 (i)).
[0168]
On the other hand, when the stream ID 603 (substream ID in FIG. 10C) is “00000010”, the packet with the PES packet includes stream recording data.
[0169]
In the stream block # 1 of FIG. 1E, the last transport packet f (FIG. 1A) is the last sector No. 31 (FIG. 1D). However, in stream block # 2 (FIGS. 1 (e) and (g)), the last transport packet z (FIG. 1 (j)) has the sector No. 1 because the recording has been stopped halfway by the user or the like. 78 (FIG. 1 (h)). 79 (FIG. 1 (h)) is an empty area where no stream data is recorded. Therefore, the sector No. 79 is recorded as the padding packet 40 (FIG. 1 (i)).
[0170]
FIG. 11 is a view for explaining the internal structure of the stream block header shown in FIG.
[0171]
As shown in FIG. 11A, the stream block header 11 has contents corresponding to the substream ID, application header, stuffing byte, and the like in the lower part of FIG.
[0172]
As shown in FIG. 11B, the stream block header 11 includes transport packet information 611, stream block information 612, sector data header information 613, and the like.
[0173]
The transport packet information 611 in FIG. 11B indicates the same as the transport packet information 611 in FIG.
[0174]
The stream block information 612 in FIG. 11B in which information on the entire stream block is recorded includes a recording time 622 (date and time information recorded in the information storage medium 201) and a transport packet in FIG. Attributes 623 (attribute information on transport packets), stream block size 624 (data size of the corresponding stream block (for example, can be described by the number of ECC blocks)), stream block time difference 625, and the like.
[0175]
Here, taking FIG. 1B as an example, the time range information in the corresponding stream block is [stream block time difference] = [first time stamp value in stream block # 2] − [time stamp a Value]. This [stream block time difference] is the stream block time difference 625.
[0176]
Further, the sector data header information 613 in FIG. 11B corresponds to the first access point 626 and the transport packet connection flag 627 in FIG. 11C. The sector data header information 613 includes information similar to the sector data header 12 in FIG. 12 described later.
[0177]
As shown in FIG. 11D, the transport packet information 611 in FIG. 11C includes the number of transport packets (the number of application packets) 631, the transport packet mapping table 632, and the like (FIG. 11). (The number of application packets in d corresponds to AP_Ns in FIG. 12C described later).
[0178]
The number 631 of transport packets (application packets) in FIG. 11D can include an I picture mapping table 641, a B and P picture mapping table 642, and the like, as shown in FIG. 11E.
[0179]
Also, the transport packet mapping table 632 in FIG. 11D can include a video packet mapping table 643, an audio packet mapping table 644, a program specific information mapping table 645, and the like.
[0180]
Each mapping table (FIG. 11E) in the transport packet mapping table 632 is configured in a bitmap format.
[0181]
For example, when n transport packets (application packets) are recorded in one stream block, the value of the number of transport packets (number of application packets) 631 in FIG. 11D is “n”. It becomes.
[0182]
Further, each of the mapping tables 643 to 645 is composed of “n-bit data”, and one bit is assigned to each transport packet (application packet) arranged in the stream block from the front.
[0183]
FIG. 12 is a view for explaining the internal structure of the sector data header shown in FIG.
[0184]
The sector data headers 12 and 13 shown in FIGS. 1C and 1I indicate data arrangement information in the data areas 21, 22, 23 and 24. As shown in FIG. 12, the first access point 651 and the transport packet connection It has an internal structure including a flag 652.
[0185]
As shown in FIG. 12D (and the lower part of FIG. 9), one stream pack having the same size of 2048 bytes as one sector is composed of a pack header and a stream PES header. The stream PES packet includes an application packet header corresponding to the sector data header 12 in FIG. 12A or a part of the stream block header 11 in FIG. 11A.
[0186]
This application packet header includes, as shown in FIG. 12 (c):
* Application packet header format version description;
* The number AP_Ns of application packets (transport packets) starting in the corresponding stream pack;
* First application packet time stamp position FIRST_AP_OFFSET in which the time stamp position of the first application packet starting in the corresponding stream pack is described by a relative value from the first byte of the stream pack;
* Extension header information EXTENSION_HEADER_IFO indicating whether a header extension and / or a stuffing byte exists;
* Identifier SERVICE_ID of the service that generated the stream.
[0187]
FIRST_AP_OFFSET included in the application packet of FIG. 12D corresponds to the first access point 651 included in the sector data header 12 of FIG.
[0188]
As shown in FIG. 1B, the transport packet d is recorded over two sectors. Here, when the last time stamp in the sector or the transport packet crosses over to the next sector, the transport packet connection flag 652 is set to “1”. Further, in the example of FIG. 1B, the address in the data area 22 at the head position of the time stamp that comes next to the transport packet d straddling the next sector is recorded in the first access point 651 (expressed in units of bits). Have been.
[0189]
The sector No. shown in FIG. 1 (or its corresponding stream pack), the sector number of the first access point. The value can be set to a value larger than the size of one data area 22 (FIG. 1C). By doing so, the sector No. This indicates that the position of the time stamp corresponding to the packet following the packet recorded in 1 exists in the next and subsequent sectors.
[0190]
In one embodiment of the present invention, a value larger than the size of the data areas 21, 22, 23, and 24 can be specified as the value of the first access point 651, so that the sector size (or stream pack size = 2048 bytes) Even for a packet having a larger size, the time stamp start position can be specified.
[0191]
For example, in the data structure of FIG. 0 to sector No. It is assumed that the information is recorded over two. Further, the time stamp for the packet is the sector number. 0 is recorded at the first position in the data area 21 and the time stamp for the next packet is set to the sector number. Consider a case where it is located at the T-th bit in the data area No. 2.
[0192]
In this case, the sector No. The value of the first access point of “0” is “0”, The value of the first access point of the sector No. 1 is “data area 22 size of sector No. 1 + T”, The value of the first access point of “2” is “T”.
[0193]
FIG. 13 is a flowchart illustrating a stream data encoding procedure and a recording procedure according to an embodiment of the present invention.
[0194]
First, in the encoding unit 401 of FIG. 7, the packetized data is transferred to the buffer memory unit 420 together with the time stamp (the time stamp of FIG. 1B and FIG. 8F or the ATS of FIG. 9). (Step S01).
[0195]
In other words, in step S01, the area of the reproduction data stored in the sector of the continuous stream block (SOBU) by the apparatus (streamer) in FIG. 7 is a transport packet with a time stamp (ATS) (application packet). ). The local clock value obtained from the STC unit 424 in FIG. 7 is used for the time stamp added here.
[0196]
Next, the bit string of the time stamp and the packet data temporarily stored in the buffer memory unit 420 is separated for each stream block (or SOBU) (step S02).
[0197]
In this embodiment, as shown in FIG. 1B, the same transport packet (d) can be prohibited from being recorded over different stream blocks (# 1, # 2). In this case, in the step of S02 in which the time stamp and the packet data temporarily recorded in the buffer memory unit 420 of FIG. 7 are separated for each stream block, the set of the time stamp and the transport packet completely fits in one stream block. It is necessary to perform the division as follows.
[0198]
At the end of the data in each of the divided stream blocks (SOBU), an end code (FIG. 1 (j)) and, if necessary, a padding area are added (step S03).
[0199]
In the buffer memory unit 420, the time stamp and the bit string of the packet data divided for each stream block (SOBU) are further divided for each sector (or for each stream pack of 2048 bytes) (step S04).
[0200]
In this embodiment, the same transport packet (d) can be recorded over different sectors (No. 0 and No. 1 in FIG. 1D). In this case, in the step of S04 in which the data area is divided for each sector, the data areas 21, 22, 23, and 24 are randomly divided in accordance with a predetermined size.
[0201]
Thereafter, information of the pack header and the PES header as shown in FIG. 1C, FIG. 9 and others are inserted into the head position of each sector (stream pack) in the buffer memory unit 420 (step S05).
[0202]
The information of the pack header and the PES header inserted in step S05 is also information of a sequence header arbitrarily output by the device (application device) that has generated the transport packet (application packet).
[0203]
Next, it is checked whether the last padding area size in the stream block (SOBU) is larger than the sector recording size (stream pack size of 2048 bytes) (step S06).
[0204]
For example, in the last stream block # 2 of the stream object #A 298 in FIG. 1F, there is a possibility that the recording end processing is performed at an arbitrary position by the user or the like. Therefore, the size of the stream data to be recorded may be significantly smaller than the size of the recordable area in the stream block # 2.
[0205]
In this case, as a result of the determination in step S06, the situation is such that the total padding area size is larger than the sector recording size. (In the examples of FIGS. 1F to 1J, the stream data is recorded up to the middle of the sector No. 78 and is not substantially recorded in the sector No. 79. In this case, FIG. (The total size of the padding areas 37 and 38 in j) becomes larger than the size in sector No. 79.)
In this case (step S06 YES), the value of the stream ID 603 in FIG. 10B is set to “10111110” as described above, and the sector No. 79 (sectors entirely filled with padding areas) are converted into padding packets 40 (step S07).
[0206]
If it is determined in step S06 that the padding area size is equal to or smaller than the sector recording size (NO in step ST06), or if conversion processing into padding packets is completed in step S07, a stream block (SOBU) recorded in the buffer memory unit 420 Is analyzed. From this analysis result, related information of the transport packet information (FIGS. 11B to 11E and FIGS. 12B to 12D) is created. Then, the stream block 11 of FIG. 11A is inserted immediately after the PES header of the first sector in the stream block (step S08).
[0207]
Alternatively, the application header shown in FIG. 9, FIG. 11, etc. is inserted after the PES header of the first sector (first stream pack) in the stream block (SOBU) (step S08).
[0208]
Further, the sector data header 12 shown in FIG. 12A is inserted immediately after the PES header into all the sectors except the head sector and the padding packet in the stream block (step S09).
[0209]
Alternatively, for the first sector (first stream pack) in the stream block (SOBU) and all the sectors (stream packs) except for the padding area, the application header shown in FIGS. Is inserted (step S09).
[0210]
The header insertion in steps S08 and S09 is performed in the buffer memory unit 420.
[0211]
The bit stream (stream information having a data structure created on the buffer memory unit 420) encoded by the above steps (steps S01 to S09) is converted into an information storage medium (DVD-RAM disk or the like) by the apparatus shown in FIG. This is recorded in 201) of FIG. 3 or FIG.
[0212]
In step S08, the entire transport packet header 511 (FIG. 8B) in the stream block (SOBU) is searched, and the values of the payload unit start indicator 501, PID 502, and random access indicator 503 in FIG. , Each data in the transport packet mapping table 632 of FIG. 11E can be created.
[0213]
Further, the difference between the value of the first time stamp in the next stream block (SOBU) and the value of the first time stamp in the current stream block (SOBU) is calculated, and the stream shown in FIG. The value of the block time difference 625 can also be determined.
[0214]
FIG. 14 is a flowchart illustrating a stream data decoding procedure and a playback procedure according to an embodiment of the present invention.
[0215]
Hereinafter, from the stream information recorded on the information storage medium (DVD-RAM disk) 201 in the structure shown in FIG. 1 (c) (i) or FIG. A description will be given of a procedure for reproducing the stream data with a focus on the extraction process.
[0216]
The range to be reproduced is specified by the user or the like by the time information. At the time of reproduction in this case, processing for searching for a stream block (or SOBU) to be reproduced corresponding to the designated time information is required.
[0219]
First, the RAM disk (information storage medium in FIG. 3 or FIG. 7) 201 on which information is recorded by the method illustrated in FIG. 13 is loaded into the disk drive unit 409 in FIG. After that, for example, it is assumed that the device user has designated a desired reproduction range by “reproduction start time” and “reproduction end time”. It is assumed that the play key (play button) of the key input unit 407 (or a remote controller not shown) in FIG. 7 is pressed after this designation is made.
[0218]
Then, the main MPU unit 404 of FIG. 7 accesses the stream file information table (SFIT) 232 of FIG. 3F according to the control program “stream data reproduction control unit 404c”, and obtains the time map information of FIG. 252 is read. From the read information content, the main MPU unit 404 determines the number of the stream block (SOBU) including the position of the specified “reproduction start time” (reproduction start time position) and the start position address of the stream block (SOBU). Is determined (step S11).
[0219]
Here, in the embodiment of FIG. 3I, only the difference time information for each stream block is recorded in the time map information 252. In this case, the stream data reproduction control unit (reproduction control program) in the main MPU unit 404 outputs the stream object information (SOBI) 242 and 243 (FIG. 3 (g)) for each stream block in the time map information 252. The values of the time differences (see FIG. 5B) 263 and 265 are sequentially added, and a comparison is made as to whether the time reaches the time designated by the user. Based on the comparison result, it is determined which stream object (SOB) and which stream block (SOBU) in the stream object (SOB) match the time stamp value included in the time specified by the user. As a result, the start position address of the stream block (SOBU) to be accessed can be determined.
[0220]
Alternatively, when stream object information (SOBI) having a data structure as shown in FIG. 29 described later is used, access is performed using information (time map information MAPL, the number of MAPL entries MAPL_ENT_Ns, etc.) included in the SOBI. The start position address of the stream block (SOBU) to be obtained can be determined.
[0221]
The head position address determined in step S11 is notified to the disk drive unit 409. The desk drive unit 409 having obtained the address information of the access destination accesses the head position of a predetermined stream block (SOBU) corresponding to the address information. Then, starting from the beginning of the stream block (SOBU), the disk drive unit 409 reads recorded stream data from the loaded disk 201 in stream block (SOBU) units (step S12).
[0222]
By the processing in step S12, individual transport packets (or application packets) with a packet arrival time (or an application packet arrival time APAT) are searched, and the searched packets can be collected (the recorded contents can be reproduced). .
[0223]
The stream data thus read is transferred from the disk drive unit 409 to the separation unit 425 in the decoding unit 402 via the D-PRO unit 410. The transferred stream data is temporarily stored in the internal memory 426 of the separation unit 425 (Step S13).
[0224]
When the amount of stream data stored in the internal memory 426 of the separation unit 425 exceeds a certain amount, packets in the padding area (37, 38, etc. in FIG. 1 (j)) are automatically searched therefrom. Whether the packet is a padding packet can be determined by checking the substream ID in FIG.
[0225]
When a padding packet is found on the internal memory 426 of the separation unit 425, the padding area including the padding packet is deleted on the internal memory 426 of the separation unit 425 (Step S14).
[0226]
Various headers (pack header, PES header, stream block header, sector data header, etc.) are deleted from the stream data from which the padding packet has been removed on the internal memory 426 of the separation unit 425. Thus, the stream data on the internal memory 426 of the separation unit 425 is converted into column information (bit stream) consisting of only a time stamp (ATS) and packet data (step S15).
[0227]
Next, it is checked whether it is necessary to transfer the converted bit stream data to an external device (such as the STB unit 403 in FIG. 7) using a communication line (such as an IEEE 1394 serial bus) (step S16).
[0228]
The check in step S16 can be performed by, for example, the following method. That is, when the device user of FIG. 7 selects “Yes” on the setting screen (not shown) of “Transfer the reproduced bit stream to an external device? ... Yes / No” in the initial setting of the device, It can be determined based on whether the yes flag is set.
[0229]
If it is necessary to send the stream data reproduced from the information storage medium 201 to the STB unit 403 in FIG. 7 (step S16: Yes), the reproduced stream is synchronized with the time stamp attached to each transport stream. The data is sequentially transferred to the STB unit 403 (step S17). When IEEE1394 is used as a transfer unit to the STB unit 403, the reproduced stream data is converted into a data structure as shown in FIG. 8E and transferred.
[0230]
If the IEEE 1394 transfer is unnecessary (No in step S16), or after the IEEE 1394 transfer is performed, the time stamp (ATS) is deleted from the bit stream converted in step S15 on the internal memory 426 of the separation unit 425, It is converted into a data string of only packet data (step S18).
[0231]
The packet data in the data string thus converted includes video packets, sub-picture (SP) packets, audio packets, and the like according to the contents at the time of recording. A data pack containing these packets has a pack header, and the type of data (video, sub-picture, audio, etc.) can be distinguished by the stream ID (not shown) in the pack header.
[0232]
By referring to the contents of the stream ID, the video packet is transferred to the video decoding unit 428 in FIG. 7, the sub-picture packet is transferred to the SP decoding unit 429, and the audio packet is transferred to the audio decoding unit 430. Thus, the corresponding recorded contents are individually decoded in the respective decoding units (428 to 430) (step S19).
[0233]
When the decoding of the various information (video, sub-picture, audio, etc.) recorded as described above is individually started, based on the reproduction time stamp set in the STC (system time counter) 424 in FIG. The video information, the sub-picture information, and / or the audio information are reproduced at a predetermined timing (displayed on a monitor TV or reproduced from a speaker by sound) (step S20).
[0234]
Here, as the reproduction time stamp in step S20, the one stored in the PES header illustrated in FIGS. 1, 10, and the like (604 in FIG. 10B) can be used.
[0235]
Alternatively, an SCR (system clock reference) base (not shown) in the pack header illustrated in FIG. 8H and the like can be used as the reproduction time stamp in step S20.
[0236]
FIGS. 15 and 16 are diagrams illustrating a method of partially deleting stream data according to an embodiment of the present invention.
[0237]
FIG. 15 shows details of the apparent first-half remaining area 743 after partial erasing, and FIG. 16 shows details of the apparent second-half remaining area 744 after partial erasing.
[0238]
FIGS. 22 and 24 illustrate a method of partially erasing stream data according to another embodiment of the present invention. Each stream block is composed of a stream object unit SOBU having a fixed size (32 sectors, 64 kbytes). Is shown.
[0239]
FIG. 22 shows details of the apparent first-half remaining area 743 after partial erasing, and FIG. 24 shows details of the apparent second-half remaining area 744 after partial erasing.
[0240]
FIGS. 23 and 25 illustrate a method of temporarily erasing stream data according to another embodiment of the present invention. Each stream block is composed of a stream object unit SOBU having a fixed size (32 sectors, 64 kbytes). Is shown.
[0241]
FIG. 23 illustrates a data structure in a case where the erasure areas (741, 742) in FIGS. 22 (g), (h) are temporary erasure areas (747, 748). FIG. 25 exemplifies a data structure in a case where the erasure areas (741, 742) in FIGS. 24 (g), (h) are temporary erasure areas (747, 748).
[0242]
Hereinafter, a case where a part of the stream data already recorded on the information storage medium 201 in FIG. 3 or FIG. 7 is partially erased (or temporarily erased) will be described.
[0243]
In the stream data recording / reproducing device (streamer), the partial erasure process (temporary erasure process) is executed by the control program “stream data partial erasure / temporary erasure control unit” 404d of the main MPU unit 404 in FIG.
[0244]
In one embodiment of the present invention, data erasure (or temporary erasure) is always performed in stream block units (or SOBU units). Further, using the time information (cell start APAT (SC_S_APAT / ERA_S_APAT); cell end APAT (SC_E_APAT / ERA_E_APAT)) specifying the original cell range, the user can specify a fine partial erase range (or a temporary erase range). I have to. This is another feature of the present invention.
[0245]
In one embodiment of the present invention, as shown in FIGS. 1B and 1J, the end of a stream block (or SOBU) is defined as padding areas 36 and 38, and the same transport packet is used for different stream blocks (SOBU). The structure is such that recording cannot be performed over the straddle.
[0246]
In this case, since the break of the transport packet always matches the break of the stream block (SOBU), partial erasure in units of stream blocks (SOBU) can be easily performed.
[0247]
FIG. 17 is a flowchart illustrating a procedure for partially erasing stream data (a procedure for completely erasing part of recording information) according to an embodiment of the present invention. The procedure of temporary erasure (the procedure of changing the management information as if part of the recorded information has been erased, but leaving the information itself without erasing) will also be described using this flowchart.
[0248]
Although not shown in FIG. 17, when a control program called “stream data partial erasure / temporary erasure control unit” 404d is started by the main MPU unit 404 in FIG. From the information storage medium 201, STREAM. Information of the IFO 105 (see FIGS. 2 and 3E) is read. The read management information is temporarily stored in the work RAM unit 404a in the main MPU unit 404.
[0249]
On the information storage medium 201 loaded in the disk drive unit 409 in FIG. 7, a stream object (SOB) #B 299 is recorded as a state before erasure (or before temporary erasure). This SOB #B is composed of stream blocks (or SOBUs) # 3 to # 5, and it is assumed that all transport packets (or application packets) recorded therein are in a reproducible state.
[0250]
In the erasing process in this case, the original cell information # 2.273 (FIG. 3G) corresponding to SOB # B.299 is stored in the management information STREAM.IFO105 temporarily stored in the work RAM unit 404a. The following specifications are made as the specification range of (partly included):
(1a) The time of the start time 751 (FIG. 15 (l) or FIG. 22 (l)) of the corresponding cell is set to the time of the time stamp r corresponding to the transport packet r (FIG. 15 (k) or FIG. 22 (k)). (Representing the arrival time of the transport packet r),
(2a) The time of the end time 756 (FIG. 16 (l) or FIG. 24 (l)) of the corresponding cell is changed to the time of the time stamp w corresponding to the transport packet w (FIG. 16 (k) or FIG. 24 (k)). (Representing the arrival time of the transport packet w).
[0251]
On the other hand, in the case of the temporary erasure processing, the following specification is made as the specification range of the original cell information # 2.273 (FIG. 3G; a part of the STREAM.IFO 105) corresponding to SOB # B.299. :
(1b) The time of the start time 752 (FIG. 23 (l)) of the corresponding cell is set to the time of the time stamp rr corresponding to the transport packet rr (FIG. 23 (k)) (representing the arrival time of the transport packet rr). Specify,
(2b) The time of the end time 758 (FIG. 25 (l)) of the corresponding cell is set to the time of the time stamp j (representing the arrival time of the transport packet j) corresponding to the transport packet j (FIG. 25 (k)). specify.
[0252]
In the following description of the partial erase procedure (or the temporary erase procedure), the STREAM. IFO 105 and STREAM. How the contents of the VRO 106 change will be described with reference to FIGS. 15 and 16 and FIGS.
[0253]
First, the case of partial erasure will be described, and then the case of temporary erasure will be described.
[0254]
[Partial erase]
Now, assume that the central part of the stream object (SOB) #B 299 shown in FIG. 15 (f), FIG. 16 (f), FIG. 22 (f) or FIG. 17) on the assumption that an apparent erase area 741 is set as shown in FIG. 16 (g), FIG. 22 (g) or FIG. 24 (g).
[0255]
First, a partial erasure range is designated by a user or the like based on time information (partial erasure start time and partial erasure end time) (step S21).
[0256]
By this designation, the range of “apparent erased area 741” shown in FIG. After the erasure range designation operation, the apparent first-half remaining area 743 and the apparent second-half remaining area 744 remain in the SOB # B 299 in FIG. 15F or the like (FIG. 15G, FIG. g), FIG. 22 (g) or FIG. 24 (g)).
[0257]
When the range of the “apparent erase area 741” is specified in step S21, the main MPU unit 404 executing the stream data partial erase / temporary erase control unit 404d of FIG. ) Or SOBI in FIG. 29 described later) is read out. On the basis of the contents of the read time map information, a stream block (one or more SOBUs or an SOB including one or more SOBUs; a stream block that is completely included in the range of partial erasure specified by the user; typically, a stream block = SOBU) is retrieved. Then, the searched stream block (in other words, all the transport packets or application packets included in the corresponding SOB before the erase end position) are erased (step S22).
[0258]
The stream block (or SOBU) thus erased is stored in the file STREAM.IFO according to the management information (STREAM.IFO / SR_MANGR.IFO) 105 shown in FIG. Treated as not in VRO 106 (ie, file system ignores erased stream block / SOBU).
[0259]
A directory other than the DVD_RTR directory 102 in FIG. 2 (where the management information 105 cannot participate, for example, in FIG. 2) is located at the physical address position on the information storage medium 201 where the information of the erased stream block / SOBU is recorded. Another file existing under the computer data storage subdirectory 113) can be recorded. Also in this case, the physical recording location on the information storage medium 201 on which another file existing under the subdirectory 113 is recorded is the file STREAM. Removed from VRO 106.
[0260]
Next, the stream object (SOB) is divided into the first half remaining area 743 and the second half remaining area 744 for the partial deletion range shown in FIG. Subsequently, SOB information (SOBI) for a new stream object (SOB # B * 745, SOB # C · 746 in FIG. 15 (h) or the like) generated by this division is created, and the created SOBI is shown in FIG. It is temporarily stored in the work RAM unit 404a in the main MPU unit 404. At this time, time map information for new SOB # B * 745 and SOB # C · 746 is also created by transcribing the corresponding location in time map information 252 recorded for SOB # B before division. (Step S23).
[0261]
A specific object of the content change (transfer / create) of the time map information is, for example, the various information (261 to 265) shown in FIG. 3 (i) or the content (MAPL) of the stream object information (SOBI) shown in FIG. , MAPL_ENT_Ns, etc.).
[0262]
When the time map information (MAPL) is shortened by the partial erasure, the “one or more subsequent SOBIs and all subsequent information tables” following the SOBI including the shortened time map information (MAPL) are changed. (Shortened) SOBI. This can prevent a gap from occurring between adjacent SOBIs.
[0263]
In this case, the SOBI_SRP # and a part of the SFIT in FIG. 29, and the STR_VMGI (all the start addresses of the information table after the SFIT) in FIG. 3F or FIG. 27 are also modified in accordance with the SOBI alignment.
[0264]
The processing content of step S23 will be further described.
[0265]
The main MPU unit 404 in FIG. 7 executes processing according to the sequential program related to the stream data partial erasure / temporary erasure control unit 404d, and issues a data read instruction to the disk drive unit 409. As a result, the file STREAM. From the VRO (or SR_TRANS.SRO) 106 (FIG. 2), the data of the stream block # 5 ((i) to (l) in FIG. 16 or FIG. 24) is reproduced, and the data is transferred to the work in the main MPU unit 404. It is temporarily stored in the RAM unit 404a.
[0266]
Next, the main MPU unit 404 searches the temporarily stored data, and obtains a time stamp having a value closest to the start time of the apparent second half remaining area 744 shown in FIG. 16 (g) or FIG. 24 (g). Find the value of
[0267]
As shown in FIGS. 16 (i) to 16 (k), the search result indicates the sector No. If the value matches or approximates the value of the time stamp k in the cell 112 (or the time stamp k in the sector No. 144 as shown in FIGS. 24 (i) to (k)), The value of k is set to the value of the start time 752 of the corresponding cell in the original cell information # 3 · 762.
[0268]
The start time (such as SC_S_ATAP) 752 of the corresponding cell set in this way is temporarily stored in the work RAM unit 404a in the main MPU unit 404, and the stream data management information STREAM. IFO (or SR_MANGR.IFO) 105 is added.
[0269]
Similarly, as the value of the end time (SC_E_ATAP etc.) 756 of the corresponding cell of the original cell information # 3 · 762, the value of the end time 756 of the corresponding cell of the original cell information # 2 · 273 before partial erasure is transcribed. .
[0270]
By the way, in the embodiment of FIG. 15, FIG. 16, FIG. 22, or FIG. 24, since stream block # 4 is completely included in the range of partial erasure, that part is substantially erased as substantial erase area 742. Is done.
[0271]
At this time, the stream block # 3 and the stream block # 5 remain as they are without being substantially erased, but as shown in FIG. 15, FIG. 16, FIG. 22, or FIG. A part on the tail side of the stream block # 3 and a part on the head side of the stream block # 5 are included in an apparent erasure area 741 specified by a user or the like.
[0272]
In one embodiment of the present invention, the stream object (SOB # B) is divided / separated in the first half remaining area 743 and the second half remaining area 744 for the partial erasure range 741, and the original cell range is also correspondingly divided.・ Is separated.
[0273]
In correspondence with this division / separation, in the embodiment of FIG. 15, FIG. 16, FIG. 22, or FIG. 24, the position of stream block # 5 is newly defined as stream object #C 746.
[0274]
On the other hand, the time map information described in the stream object information (SOBI) #B 243 (FIG. 3 (g)) corresponding to the stream object (SOB) #B 299 before the erasure (the content is shown in FIG. ), Corresponding to the contents of SOBI in FIG. 29), the values of the stream block size and the stream block time difference for stream block # 5 do not change before and after partial erasure.
[0275]
Therefore, as shown in step S23 in FIG. It is transcribed as time map information information in stream object information #C corresponding to stream object #C 746 (FIG. 16 (h), FIG. 24 (h), etc.) newly created in IFO 105.
[0276]
The display range specified by the partially deleted original cell information # 3.762 (FIG. 16 (m) or FIG. 24 (m)) corresponding to the newly defined stream object # C.746 is specified by the user. It matches the range of the apparent second half remaining area 744.
[0277]
When the creation of the time map information is completed by the processing of step S23, the original cell information for the newly defined SOB (SOB ## B *, SOB # C) is created (step S24).
[0278]
In creating the original cell information, the designated range of the corresponding original cell # 3.762 (FIG. 16 (m), FIG. 24 (m)) is set.
[0279]
This setting is performed by adjusting the start time of the cell to the partial erase end time specified by the user or the like (or by adjusting the end time of the cell to the partial erase start time specified by the user or the like). .
[0280]
Specifically, taking the illustration in the lower part of FIG. 31 described later as an example, a cell # k + 1 of a new SOB after complete erasure (after partial erasure is completely executed) (cell # k + 2 before complete erasure) The start time (SC_S_APATk + 1) is adjusted to the erase end time (SC_E_APATk + 1 of cell # k + 1 before complete erasure) specified by the user or the like.
[0281]
Alternatively, the end time (SC_E_APATk) of the cell #k of the SOB after complete erasure (the cell #k before complete erasure) is set to the erase start time (SC_S_APATk + 1 of the cell # k + 1 before complete erasure) specified by the user or the like. May be.
[0282]
In the illustrated example in the lower part of FIG. 31, the start time (SC_S_APATk) and the end time (SC_E_APATk) of the cell #k which is not changed before and after complete erasure are not changed.
[0283]
By the processing in step S24, the above-mentioned “SOBI alignment” is performed (this makes it possible to prevent a gap from occurring between adjacent SOBIs).
[0284]
Next, the information (time map information and the like) relating to the original (before erasure) stream object information (SOBI) # B · 243 (FIG. 3 (g)) is rewritten (step S25).
[0285]
Specifically, a portion of the substantial erase area 742 (FIGS. 16 (h) and 24 (h)) and a portion of the newly defined SOB area 746 (FIGS. 16 (h) and 24 (h)) The time map information is rewritten to the content obtained by removing from the original time map information.
[0286]
The reason for this is that after the partial erasure, the only stream block constituting SOB # B * 745 (FIG. 15 (h), FIG. 22 (h)) is # 3, so that SOBI # B · 243 before the partial erasure is used. This is because it is necessary to delete the part of the stream block # 4 that has been substantially erased and the information of the stream block # 5 to which another stream object (SOB # C) belongs from the time map information in. .
[0287]
This information deletion is the information rewriting process in step S25. This deletion process is performed on the management information (STREAM.IFO / SR_MANGR.IFO) 105 temporarily stored in the work RAM unit 404a in the main MPU unit 404 in FIG.
[0288]
Also in the rewriting of information (time map information and the like) in step S25, the above-described “SOBI alignment” is performed (this can prevent a gap from occurring between adjacent SOBIs).
[0289]
Next, a process of changing the information content regarding the original cell information # 2 · 273 before erasure is performed. Here, the same processing as the creation of the original cell information # 3.762 in step S24 is executed.
[0290]
First, the time range of the original cell corresponding to the SOB whose time map information has been rewritten is changed (step S26).
[0291]
This change is made by adjusting the end time of the cell to the partial erase start time specified by the user or the like (or by adjusting the start time of the cell to the partial erase end time specified by the user or the like). .
[0292]
Specifically, taking the illustration in the lower part of FIG. 31 described later as an example, the end time (SC_E_APATk) of cell #k (cell #k before complete erasure) is changed to the erase start time (complete erasure) specified by the user or the like. (SC_S_APATk + 1 of the previous cell # k + 1).
[0293]
Alternatively, the start time (SC_S_APATk + 1) of cell # k + 1 after complete erasure (cell # k + 2 before complete erasure) may be set to the erase end time (SC_E_APATk + 1 of cell # k + 1 before complete erasure) specified by a user or the like. Good.
[0294]
Next, the main MPU unit 404 in FIG. 7 executes processing according to the sequential program related to the stream data partial erasure / temporary erasure control unit 404d, and issues a data read instruction to the disk drive unit 409. As a result, the file STREAM. From the VRO (or SR_TRANS.SRO) 106 (FIG. 2), the data of the stream block # 3 ((i) to (l) in FIG. 15 or FIG. 22) is reproduced, and the data is transferred to the work in the main MPU unit 404. It is temporarily stored in the RAM unit 404a.
[0295]
The main MPU unit 404 searches the temporarily stored data, and obtains a time stamp value having a value closest to the end time of the apparent first-half remaining area 743 shown in FIG. 15 (g) or FIG. 22 (g). To search.
[0296]
As shown in FIG. 15 or (i) to (k) of FIG. If the value of the time stamp v matches or approximates the value of the time stamp v in the original cell information # 2 761 (FIG. 15 (m), FIG. 22 ( m)) is set as the value of the end time 757 (FIG. 15 (l), FIG. 22 (l)) of the corresponding cell.
[0297]
The value thus set is added to the management information (STREAM.IFO / SR_MANGR.IFO) 105 temporarily stored in the work RAM unit 404a in the main MPU unit 404.
[0298]
The value (SC_S_APAT) of the start time 751 of the corresponding cell of the original cell information # 2 · 761 after the partial erasure is the value (SC_S_APAT) of the start time 751 of the corresponding cell of the original cell information # 2 · 273 before the partial erasure. Therefore, the value is left unchanged in the management information (STREAM.IFO / SR_MANGR.IFO) 105 without being changed.
[0299]
When a series of processes described above is completed, the main MPU 404 sends the disk drive 409 based on the information of the stream data management information (STREAM.IFO / SR_MANGR.IFO) 105 changed in the work RAM 404a of FIG. Is instructed.
[0300]
Thereby, the STREAM. IFO / SR_MANGR. The information in the IFO 105 is rewritten (step S27).
[0301]
As a result of this information rewriting, the deleted stream block (SOBU) is ignored from the file system (DVD_RTAV file system) in FIG.
[0302]
Finally, the information of the volume & file structure information 206 (FIG. 3B) recorded on the information storage medium 201 in S28 is rewritten, and the file system information is updated (Step S28).
[0303]
The specified range of the original cell information indicating the reproduction range corresponding to the specified range by the stream object information (SOBI) in which the data size and the time information (time difference) of each stream block are recorded is equal to or smaller than the specified range. Alternatively, it can be narrowed (see FIGS. 15, 16, 22, and 24 (f) to (h)). In this manner, the user can partially erase the recorded SOB information in an arbitrary range that is apparently smaller than the stream block.
[0304]
By adding the data size of each stream block, the position (= address information) where a specific stream block is recorded can be calculated.
[0305]
When reproduction is performed from the information storage medium 201 after performing the partial erasure processing as described above, the original cell # 2 and the original cell # 3 are continuously reproduced in one original PGC 290 as shown in FIG. .
[0306]
That is, when a user or the like reproduces the information from the information storage medium 201 on which the partial erasure process has been performed, the start time 751 of the corresponding cell in the original cell information # 2 · 761 (FIG. 15 (m) or the like) starts. Immediately after the cell is reproduced up to the end time 757, the cell is continuously (usually seamlessly) reproduced from the position of the start time 752 of the corresponding cell in the original cell information # 3.762 (FIG. 16 (m) or the like). Begins.
[0307]
[In case of temporary deletion]
In the DVD streamer, two types of erasing are possible. The first is to completely erase a part of the stream described above, and the second is to temporarily erase a part of the stream described below (temporary erase or temporary erase; this is abbreviated as TE as appropriate). is there.
[0308]
For temporary erasure:
(11) The temporary erase portion of the stream can be completely reconfigured;
(12) The start position and the end position of the temporarily erased portion can be marked with time information with the accuracy of the application packet arrival time (APAT) (the streamer user cannot recognize internal information such as SOB, SOBU, SOBI / MAPL, etc.) However, the recording time can be recognized, so that the user can mark the range of the temporary erasure, that is, the start position and the end position of the temporary erasure portion on a time basis.);
(13) During recording, the temporary erased portion can be completely erased without regard to the format of the streamer in the stream (this enables the temporary erased portion to be recycled in real time).
[0309]
The above (11) to (13) correspond to the protection included in the stream cell information SCI (FIG. 28) in the original PGC (not the user-defined PGC) shown in FIG. 3 (f), FIG. 4, FIG. 27 or FIG. This can be realized by using the flag TE (FIG. 28). This TE flag indicates a temporarily erased cell.
[0310]
Next, it is assumed that the central part of the stream object (SOB) #B 299 shown in FIG. 23 (f) or FIG. 25 (f) is temporarily erased, as shown in FIG. 23 (g) or FIG. 25 (g). The description of the flowchart of FIG. 17 will be started on the assumption that the apparent temporary erasure area 747 is set.
[0311]
In the temporary erasure process, the procedure of the processing content is the same as that of the “partial erasure range” or “erasure range” in steps S21 to S23 of FIG. Also, in steps S27 to S28 in FIG. 17, the processing procedure is the same for partial erasure and temporary erasure.
[0312]
Hereinafter, with respect to steps S24 to S26 in FIG. 17, a procedure in the case of temporary erasure will be described with reference to FIG. 23 and FIG.
[0313]
When the creation of the time map information is completed by the processing of step S23, the original cell information for the newly defined SOB (SOB ## B *, SOB # C) is created (step S24).
[0314]
In creating the original cell information, a designated range of the corresponding original cell is set.
[0315]
Specifically, taking the illustration of FIG. 30B described below as an example, the start time of the cell # k + 1 in which the temporary erase flag TE is set to “10b” is the temporary erase start time specified by the user or the like. (ERA_S_APAT; temporary erase start mark). The end time of the cell # k + 1 for which the temporary erase flag TE is set to "10b" is the temporary erase end time (ERA_E_APAT; temporary erase end mark) specified by the user or the like.
[0316]
Alternatively, taking the illustration in the upper part of FIG. 31 described later as an example, the start time of the cell # k + 1 in which the temporary erasure flag TE is set to “10b” is SC_S_APATk + 1, and the end time of the cell # k + 1 is SC_E_APATk + 1.
[0317]
Next, the information (time map information and the like) relating to the original (before temporary erasure) stream object information (SOBI) is rewritten in the same manner as the partial erasure described above (step S25).
[0318]
In this temporary erasing, the data to be temporarily erased is not erased, but only the management information of the data to be erased is rewritten to the “temporarily erased” state. However, when the data to be temporarily erased (the data of cell # k + 1 in the example of FIG. 30B or the upper part of FIG. 31) is completely erased, the following processing is performed.
[0319]
First, the time range of the original cell corresponding to the SOB whose time map information has been rewritten is changed (step S26).
[0320]
Specifically, taking the illustration of FIG. 30 described later as an example, the start time (ERA_S_APAT) of the temporarily erased cell # k + 1 in FIG. 30B is the end of the cell #k after the complete erase in FIG. The end time (ERA_E_APAT) of the temporarily erased cell # k + 1 in FIG. 30B is adjusted to the time (SC_E_APAT), and the cell # k + 1 after complete erase (cell # K + 2 before complete erase) in FIG. 30C is started. It will be adjusted to the time (SC_S_APAT).
[0321]
The summary of the above-described provisional erasure process is as follows.
[0322]
(A) The temporary erase start time (ERA_S_APAT) and the temporary erase end time (ERA_E_APAT) are used to temporarily determine a part of the bit stream information (the temporary erase area 747 in FIG. 23 or 25) included in the stream object (SOB). (In step S21, "partial erasure range" is replaced with "temporary erasure range").
[0323]
A stream block containing a transport packet (application packet) with a start time (SC_S_APAT) when the start time (SC_S_APAT) matches the beginning of a transport packet (application packet) starting in the stream block (SOBU). The start time (ERA_S_APAT) of the temporary erasure is adjusted to the start time (SC_S_APAT) of the first one of the transport packets (application packets) starting in (SOBU) (in step S26, the “partial erasure” is replaced with the “temporary erasure”). To "). Then, the streamer information (STREAM.IFO / STRI) is rewritten (step S27).
[0324]
(B) Alternatively, a part of the bit stream information included in the stream object (SOB) (the temporary erasure area 747 in FIG. 23 or 25) according to the temporary erase start time (ERA_S_APAT) and the temporary erase end time (ERA_E_APAT). (In step S21, "partial erasure range" is replaced with "temporary erasure range").
[0325]
A stream block containing a transport packet (application packet) accompanied by a start time (SC_S_APAT) when a cell (TE cell) corresponding to a portion where a temporary erasure range is specified includes the head of a stream object (SOB) The start time (ERA_S_APAT) of the temporary erasure is adjusted to the start time (SC_S_APAT) of the first one of the transport packets (application packets) starting in (SOBU) (in step S26, the “partial erasure” is replaced with the “temporary erasure”). To "). Then, the streamer information (STREAM.IFO / STRI) is rewritten (step S27).
[0326]
(C) Alternatively, part of the bit stream information included in the stream object (SOB) (the temporary erasure area 747 in FIG. 23 or 25) according to the temporary erase start time (ERA_S_APAT) and the temporary erase end time (ERA_E_APAT). (In step S21, "partial erasure range" is replaced with "temporary erasure range").
[0327]
Another stream block (SOBU # 2 in FIG. 30 (b)) immediately followed by a stream block (SOBU # 3 in FIG. 30 (b)) containing a transport packet (application packet) with a start time (SC_S_APAT) The temporary erase start time (ERA_S_APAT) is matched with the start time (SC_S_APAT) of the first one of the transport packets (application packets) that start in (S26). In step S26, “partial erase” is replaced with “temporary erase”. ). Then, the streamer information (STREAM.IFO / STRI) is rewritten (step S27).
[0328]
(D) Alternatively, a part of the bit stream information included in the stream object (SOB) (the temporary erasure area 747 in FIG. 23 or 25) according to the temporary erase start time (ERA_S_APAT) and the temporary erase end time (ERA_E_APAT). (In step S21, "partial erasure range" is replaced with "temporary erasure range").
[0329]
In a stream block (SOBU # 1 of cell # k + 1 in FIG. 30 (c)) that includes a transport packet (application packet) immediately following a cell (TE cell) corresponding to the portion where the provisional erasure range is specified. The temporary erase end time (ERA_E_APAT) is matched with the start time (SC_S_APAT) of the first one of the transport packets (application packets) starting at step (in step S26, "partial erase" is replaced with "temporary erase") . Then, the streamer information (STREAM.IFO / STRI) is rewritten (step S27).
[0330]
FIG. 18 is a diagram illustrating a method of setting time management information for MPEG-encoded video data (before partial erasure or temporary erasure).
[0331]
FIG. 19 is a view for explaining the relationship between time information and field information in original cell information (before partial erasure or before temporary erasure) corresponding to the video data in FIG.
[0332]
In the above-described embodiment, substantial partial erasure is performed for each stream block (SOBU) divided for each specific data size (for example, 32 sectors / 64 kbytes), and the detailed apparent partial erasure range is changed to the original cell size. It can be defined by a range.
[0333]
However, the present invention is not limited to this. Any method that divides and manages specific data such as video data into units or blocks, erases the data in units or blocks, and specifies the range of playback information (cells, etc.) so that the user can specify a detailed playback range The present invention can be applied to
[0334]
For example, the management information file RTR. In the IFO 104 (FIG. 2), as shown in FIG. 18, a portion from an I picture peculiar to MPEG2 moving image compression to a portion immediately before the next I picture is handled as a unit. This unit is called a video object unit (VOBU). This VOBU can be considered in association with a stream object unit (SOBU).
[0335]
According to the NTSC TV standard, about 30 images (frames) are displayed per second. Each image is called a picture, and in the interlace method, one picture (frame) is represented by two field scans (odd field scan and even field scan).
[0336]
In a streamer, time stamp information in which time information when stream data reaches a receiver is used as time (time) information. However, in one embodiment of the present invention, for video information, time (time) information can be represented by the number of fields counted from the first I picture a shown in FIG.
[0337]
The time map information in this embodiment is managed as a unit for each VOBU (or SOBU). For example, the data size of one VOBU (or SOBU) corresponds to the stream block size 262 in FIG. Further, as the time information corresponding to the stream block time difference 263, the number of fields included in one corresponding VOBU (or SOBU) applies.
[0338]
At this time, the information of the start time (SC_S_APAT or ERA_S_APAT) 753 of the corresponding cell and the information of the end time (SC_E_APAT or ERA_E_APAT) 758 of the corresponding cell in the information (SCI in FIG. 28) 763 (FIG. 19) of the original cell # 1 are as shown in FIG. Can be represented by the number of fields counted from the first I-picture a of.
[0339]
For example, the time information of the n-th picture in FIG. 18 can be expressed as a 2n-th field.
[0340]
FIG. 20 is a diagram illustrating a method of setting time management information for MPEG-encoded video data (after partial erasure or temporary erasure).
[0341]
FIG. 21 is a view for explaining the relationship between time information and field information in original cell information (after partial erasure or after temporary erasure) corresponding to the video data in FIG.
[0342]
When the partial erasure process is performed on the video information of FIG. 18, only VOBU # 2 (SOBU # 2) is substantially partially erased as shown in FIG. The range of the fine partial erasure specified by the user or the like can be defined by the cell range setting as in the case of the partial erasure of the stream data described with reference to FIG. 15 and others.
[0343]
That is, in FIG. 20, when the user or the like designates partial erasure from B picture f to B picture s, VOBU # 2 (SOBU # 2) completely included in the partial erasure designation range is completely erased. At this time, VOBU # 1 (SOBU # 1) and VOBU # 3 (SOBU # 3), which are partially included in the designated range of partial erasure, substantially remain in VOBU units (SOBU units).
[0344]
As in the case of the stream data, the VOB (or SOB) is divided before and after the partially erased portion to become VOB # 1 (SOB # 1) and VOB # 2 (SOB # 2). Correspondingly, the cell before partial erasure is divided into original cell # 1 and original cell # 2.
[0345]
At this time, as shown in FIG. 21, the 2f-th field corresponding to the B picture f is specified as the end time (SC_E_APAT or ERA_E_APAT) 759 of the corresponding cell of the information (SCI) 764 of the original cell # 1, The second (sq) field corresponding to the B picture s can be designated as the start time (SC_S_APAT or ERA_S_APAT) 754 of the corresponding cell of the second information (SCI) 765.
[0346]
For example, the time information of the f-th picture in FIG. 20 can be expressed as a 2f-th field.
[0347]
In the embodiments of FIGS. 20 and 21, the number of fields is always represented by the number of fields counted from the first picture of the VOB for each VOB (SOB). Further, the corresponding VOB (SOB) can be designated by the number of fields in the cell information (SCI). Here is a feature of this embodiment.
[0348]
FIG. 26 is a diagram illustrating an example of an internal configuration of a sector that forms a stream block (SOBU) (a stream pack including an application packet and a stream pack including a stuffing packet).
[0349]
The stream object (SOB) # A · 298 in FIG. 26D is composed of a plurality of stream blocks # 1, # 2,... As shown in FIGS.
[0350]
Each of the stream blocks # 1, # 2,... Is composed of a stream object unit (SOBU) having a size of 2 ECC blocks (= 32 sectors = 64 kbytes).
[0351]
In this way, for example, even if stream block (SOBU) # 2 is deleted, the ECC block of stream block (SOBU) # 1 is not affected by this deletion.
[0352]
The first stream block (SOBU) # 1 of SOB # A • 298 has a sector No. as shown in FIG. 0 to sector No. 31 (32 sectors / 64 kbytes).
[0353]
Each sector of the stream block (SOBU) # 1 has a similar data structure. , For example, sector No. Regarding 0, it is as shown in FIG.
[0354]
That is, the sector No. 0 is constituted by a stream pack of 2048 bytes (2 kbytes). This stream pack is composed of a pack header of 14 bytes and a stream PES packet of 2034 bytes.
[0355]
The stream PES packet includes a 6-byte PES header, a 1-byte substream ID, and a 2027-byte stream data area.
[0356]
The stream data area includes a 9-byte application header, an application header extension (optional), a stuffing byte (optional), and an application packet area.
[0357]
The application packet area is composed of a group of application packets each having an application time stamp (ATS) at the top.
[0358]
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.
[0359]
In stream recording, the application that generates the recorded content 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 treated as having a required length (for example, 2048 bytes).
[0360]
The stuffing bytes in FIG. 26A can be used to always keep the stream pack at a predetermined length (2048 bytes).
[0361]
When 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.
[0362]
On the other hand, for a subsequent stream packet in the SOB, the application packet may be split (split) at an adjacent stream packet boundary. The partial packet illustrated in the lower part of FIG. 9 indicates an application packet generated by this division (split).
[0363]
The byte offset of the first application timestamp starting in the stream packet and the number of application packets starting in the stream packet are described in the application header.
[0364]
In this way, in a certain stream packet, stuffing before the first application time stamp and after the last application packet is automatically performed. Due to this automatic stuffing, the stream packet always has the required length.
[0365]
Although not shown, the pack header in FIG. 26A includes pack start code information, SCR base information, SCR extension information, program maximum rate information, marker bits, pack stuffing length information, and the like.
[0366]
The SCR base is composed of 32 bits, and the 32nd bit is set to zero. As the program maximum rate, 10.08 Mbps is adopted.
[0367]
The PES header and the substream ID in FIG. 26A have the contents as shown in FIG.
[0368]
As shown in FIG. 12C, the application header of FIG. 26A includes version information, the number of application packets AP_Ns, the time stamp position FIRST_AP_OFFSET of the first application packet, extension header information EXTENSION_HEADER_IFO, service ID, and the like. .
[0369]
Here, the version describes the version number of the application header format.
[0370]
AP_Ns in the application header describes the number of application packets starting in the corresponding stream pack. When the first byte of the ATS is stored in the corresponding stream pack, it can be considered that the application packet starts in this stream pack.
[0371]
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.
[0372]
EXTENSION_HEADER_INFO describes whether an application header extension and / or stuffing byte exists in the corresponding stream packet.
[0373]
If the content of the EXTENSION_HEADER_INFO is 00b, it indicates that neither the application header extension nor the stuffing byte exists after the application header.
[0374]
When the content of the EXTENSION_HEADER_INFO is 10b, it indicates that the application header extension is present after the application header, but no stuffing byte is present.
[0375]
If the content of EXTENSION_HEADER_INFO is 11b, it indicates that an application header extension exists after the application header, and that a stuffing byte also exists after the application header extension.
[0376]
It is forbidden that the content of the EXTENSION_HEADER_INFO becomes 01b.
[0377]
The stuffing byte (optional) before the application packet area is activated by “EXTENSION_HEADER_INFO = 11b”. By doing so, it is possible to prevent "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.
[0378]
SERVICE_ID describes the ID of a service that generates a stream. If this service is unknown, 0x0000 is described in SERVICE_ID.
[0379]
The application packet area in FIG. 26A can be configured in the same manner as shown in the lower part of FIG. 9 (the packet in FIG. 9 is replaced with an application packet in FIG. 26).
[0380]
That is, a partial application packet is recorded at the head of the application packet area, and thereafter, a plurality of pairs of the application time stamp ATS and the application packet are sequentially recorded, and the partial application packet is recorded at the end.
[0381]
Stated another way, a partial application packet can be present at the start of the application packet area. At the end position of the application packet area, a partial application packet or a stuffing area of a reserved number of bytes can exist.
[0382]
The application time stamp (ATS) arranged before 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 a 90 kHz unit value, and the extended part shows a small value measured at 27 MHz (less significant value).
[0383]
In FIG. 26A, the application header extension can be used to store information that may differ between application packets. Such information is not necessary for all applications.
[0384]
Therefore, the data field of the application header is defined so that the presence of the optional application header extension in the stream data area can be described (in the above described EXTENSION_HEADER_INFO).
[0385]
When 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.
[0386]
On the other hand, for a subsequent stream packet in the SOB, the application packet may be split (split) at an adjacent stream packet boundary. The partial application packet shown in FIG. 8 (f) (g) or FIG. 9 indicates an application packet generated by this division (split).
[0387]
The byte offset of the first application timestamp starting in the stream packet and the number of application packets starting in the stream packet are described in the application header.
[0388]
In this way, in a certain stream packet, stuffing before the first application time stamp and after the last application packet is automatically performed.
[0389]
That is, "the application performs stuffing by itself" is realized by the automation mechanism. Due to this automatic stuffing, the stream packet always has the required length.
[0390]
The application header extension (optional) consists of a list of entries. Here, there is one entry of one 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.
[0391]
In the 1-byte application header extension (option), 1-bit AU_START, 1-bit AU_END, and 2-bit COPYRIGHT are described.
[0392]
If 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.
[0393]
When AU_END is set to “1”, it indicates that the associated application packet is the last packet of the random access unit.
[0394]
COPYRIGHT describes the copyright status of the related application packet.
[0395]
The packet structure in FIG. 26A can be applied to other than the last sector of SOB # A · 298, but is not necessarily applied to the last sector.
[0396]
For example, the end of SOB # A · 298 is the sector No. in FIG. When the sector is composed of padding packets 40 (see FIG. 1 (i)) as shown in FIG. 26 (g), the contents of the padding area 38 (FIG. 26 (h)) are 26 (a).
[0397]
That is, as shown in FIG. 26 (i), the stuffing packet as the padding packet 40 includes a pack header of 14 bytes, a PES header of 6 bytes, a substream ID of 1 byte, an application header of 9 bytes, It consists of an application packet area of 2018 bytes.
[0398]
In the pack including the head of the stuffing packet, this application packet area is composed of a 4-byte application time stamp ATS and 2014 bytes of zero-byte data (data having substantially no recorded content).
[0399]
On the other hand, in the pack including the subsequent stuffing packet, the application packet area is configured with 2018 bytes of zero-byte data (no ATS).
[0400]
When recording at a very low bit rate is performed, stuffing is required to ensure recovery (reproduction) of time map information (252 in FIG. 3H; MAPL in SOBI in FIG. 29). The stuffing packet in FIG. 26 (i) is defined as a conceptual unit for that. The purpose of this stuffing packet is achieved by ensuring that each SOBU, including the stuffing area, contains at least one ATS value.
[0401]
A stuffing packet has the following conditions:
* One or more stuffing packets always start in the pack's application packet area after the pack containing the actual application packet data;
* One or more stuffing packets are composed of one 4-byte ATS and zero byte data (following the ATS) necessary to fill the application data area of the remaining pack of the SOBU. Now, assuming that the number of sectors per SOBU is SOBU_SIZ and 0 ≦ n ≦ SOBU_SIZ−1, the total length of the stuffing packet is “4 + 2014 + n × 2018” bytes.
[0402]
The ATS of the stuffing packet is set as follows:
* In a SOBU where at least one pack contains the actual application packet data, the ATS of the stuffing packet is set to the ATS of the application packet preceding the stuffing packet;
* Within an SOBU that does not include actual application packet data, the ATS of a stuffing packet is determined according to the contents of time map information and the like.
[0403]
All packs containing 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;
* PES packet header and substream ID are the same as for all other PES packets;
* AP_Ns = 0, FIRST_AP_OFFSET = 0, EXTENSION_HEADER_IFO = 00b, and SERVICE_ID = 0 in the application header (see FIGS. 12C and 12D) (other parameters in the application header are also 0).
[0404]
FIG. 27 is a view for explaining the internal data structure of streamer management information (corresponding to STREAM.IFO or SR_MANGR.IFO in FIG. 2).
[0405]
STREAM.COM which is the management information (navigation data) shown in FIG. The IFO (SR_MANGR.IFO) 105 includes streamer information STRI, as shown in FIG.
[0406]
As shown in FIG. 3 (f) or FIG. 27, the 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.
[0407]
As shown in FIG. 27, the streamer video manager information STR_VMGI includes video manager information management information VTSI_MAT in which management information related to STR and STR_VMGI is described, and a play pointer in which a search pointer for searching a playlist in a stream is described. And a list search pointer table (PL_SRPT).
[0408]
Here, the playlist is a partial list of the program. The playlist allows the user to define an arbitrary playback sequence (with respect to the contents of the program).
[0409]
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.
[0410]
The original PGC information ORG_PGCI is a portion in which information on the original PGC (ORG_PGC) is described. ORG_PGC indicates navigation data describing a program set. ORG_PGC is a chain of programs, and includes stream data recorded in the “.SRO” file in FIG. 2 or FIG. 32 (SR_TRANS.SRO 106 in FIG. 2).
[0411]
Here, the program set indicates the entire recorded content (all programs) of the information storage medium 201. In the reproduction of the 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 its reproduction order is changed with respect to the original recording. This program set corresponds to a data structure called an original PGC (ORG_PGC).
[0412]
A program is a logical unit of recorded content that is recognized or defined by a user. The program in the program set is composed of one or more original cells. The program is defined only in the original PGC.
[0413]
Further, a cell is a data structure indicating a part of a program. A cell in the original PGC is called an “original cell”, and a cell in a user-defined PGC described later is called a “user-defined cell”.
[0414]
Each program in the program set is composed 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.
[0415]
On the other hand, in a streamer, only a stream cell (SC) is defined. Each stream cell refers to a part of the recorded bit stream. In the embodiment of the present invention, a “cell”, if not otherwise specified, means a “stream cell”.
[0416]
Note that the program chain (PGC) indicates a higher-level 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 part (chain) of a program corresponding to the playlist.
[0417]
A user-defined PGC indicating a part of a chain of a program includes only navigation data. Then, a part of each program refers to stream data belonging to the original PGC.
[0418]
The user-defined PGC information table UD_PGCIT in FIG. 27 can 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.
[0419]
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.
[0420]
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 "99".
[0421]
UD_PGCIT_EA describes the end address of the UD_PGCIT in terms of the relative number of bytes (F_RBN) from the first byte of the UD_PGCIT.
[0422]
Here, F_RBN indicates the relative number of bytes from the first byte of the defined field in the file, and starts from zero.
[0423]
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.
[0424]
The text data manager TXTDT_MG in FIG. 27 is supplementary text information. This TXTDT_MG can be stored in a playlist and a program together with the primary text information PRM_TXTI of FIG.
[0425]
Although not shown, the application private data manager APDT_M in FIG. 27 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.
[0426]
Here, the application private data APDT is a conceptual area in which an application device connected to the streamer can store any non-real-time information (more desired information in addition to real-time stream data).
[0427]
FIG. 28 is a view for explaining the internal data structure of PGC information (ORG_PGCI / UD_PGCIT in FIG. 3 or PGCI # i in FIG. 27).
[0428]
The PGC information PGCI # i in FIG. 28 generally represents the original PGC information ORG_PGCI in FIG. 27 or the user-defined PGC information UD_PGCI in the user-defined PGC information table UD_PGCIT.
[0429]
As shown in FIG. 28, PGC information PGCI # i includes PGC general information PGC_GI, one or more program information PGI # m, one or more stream cell information search pointer SCI_SRP # n, and one or more stream cell information SCI #N.
[0430]
The PGC general information PGC_GI includes the number PG_Ns of programs and the number SCI_SRP_Ns of stream cell information search pointers SCI_SRP.
[0431]
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 a search pointer number IT_TXT_SRPN of the item text.
[0432]
Here, the program type PG_TY includes information indicating the state of the corresponding program. In particular, it includes a flag indicating whether the program is protected from erroneous erasure or the like, that is, a protect flag.
[0433]
When the protect flag is "0b", the corresponding program is not protected. When the protect flag is "1b", the program is protected.
[0434]
The number of cells C_Ns indicates the number of cells in the corresponding program. Throughout the entire program and all cells of the PGC, cells are (implicitly) associated with the program in their ascending order.
[0435]
For example, if the program # 1 has C_Ns = 1 and the program # 2 has C_Ns = 2 in the PGC, the first stream cell information SCI of the PGC is attached to the program # 1, and the second, The third SCI is associated with program # 2.
[0436]
The primary text information PRM_TXTI describes text information having one common character set (ISO / IEC646: 1983 (ASCII code)) so that the information storage medium (DVD-RAM disc) 201 can be used worldwide. It was done.
[0437]
The item text search pointer number IT_TXT_SRPN describes the search pointer number for the item text (text data corresponding to the program) IT_TXT. If the corresponding program has no item text, IT_TXT_SRPN is set to “0000h”.
[0438]
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 the PGCI.
[0439]
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.
[0440]
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, and a stream cell start APAT (FIG. 6 and others, SC_S_APAT shown in FIG. 6 and others, stream cell end APAT (SC_E_APAT shown in FIG. 6 and others), and erase start APAT indicating the start APAT of the temporarily erased cell when the cell is in the temporary erase state (TE = 01b). (ERA_S_APAT shown in FIG. 6 and others) and an erase end APAT (ERA_E_APAT shown in FIG. 6 and others) indicating the end APAT of the temporarily erased cell when the cell is in the temporary erase state (TE = 10b). I have.
[0441]
The cell type C_TY describes the format of the corresponding stream cell and its temporary erasure state.
[0442]
That is, the cell format C_TY1 = "010b" is described in all stream cell formats (the stream cell and the other cells can be distinguished by the C_TY1 = "010b").
[0443]
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. .
[0444]
The flag TE = "01b" indicates a case where the corresponding cell (cell in the temporary erase state) starts after the first application packet starting in the SOBU and ends before the last application packet in the same SOBU. .
[0445]
Further, the flag TE = “10b” indicates a case where the corresponding cell (cell in the temporarily erased state) includes at least one SOBU boundary (the first application packet or the last application packet starts in the SOBU).
[0446]
The program protect flag and the TE flag of a cell 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 a temporarily erased state cannot be set to a protected state.
[0447]
The number SC_EPI_Ns of stream cell entry point information describes the number of stream cell entry point information included in the corresponding stream cell information SCI.
[0448]
Each stream cell entry point information SC_EPI (for example, SC_EPI # 1) in FIG. 28 has two types (type A and type B).
[0449]
The 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 the entry point type EP_TY1 = "00b".
[0450]
The type B SC_EPI includes primary text information PRM_TXTI in addition to the type A EP_TY and EP_APAT. Type B is indicated by the entry point type EP_TY1 = "01b".
[0451]
In any stream cell, an entry point can be used as a tool for skipping a part of the recorded content. All entry points can be specified by the application packet arrival time (APAT). With this APAT, it is possible to specify where data output starts.
[0452]
The stream object number SOB_N describes the number of the SOB referenced by the corresponding cell.
[0453]
The stream cell start APAT (SC_S_APAT) describes the start APAT of the corresponding cell.
[0454]
The stream cell end APAT (SC_E_APAT) describes the end APAT of the corresponding cell.
[0455]
The erase start APAT (ERA_S_APAT) is the first erase start in the first SOBU including the head of the temporary erase cell in the temporary erase cell including at least one SOBU boundary (the TE field of the C_TY is “10b”). It describes the arrival time (APAT) of the application packet.
[0456]
The erasure end APAT (ERA_E_APAT) is the first erasure cell that includes at least one SOBU boundary (the TE field of its C_TY is “10b”) and starts in the SOBU that includes the application packet immediately following the erasure cell. It describes the arrival time (APAT) of the application packet.
[0457]
FIG. 29 is a view for explaining the internal data structure of the stream file information table (FIG. 3F or SFIT in FIG. 27).
[0458]
As shown in FIG. 29, the stream file information table SFIT includes stream file information table information SFITI, one or more stream object stream information SOB_STI # n, and stream file information SFI.
[0459]
The stream file information table information SFITI includes the number SFI_Ns of stream file information on the information storage medium (DVD-RAM disc) 201, the number SOB_STI_Ns of stream object stream information following the SFITI, the end address SFIT_EA of the SFIT, and the start of the SFI. It is composed of an address SFI_SA.
[0460]
SFIT_EA describes the end address of SFIT by the relative number of bytes (F_RBN) from the first byte of SFIT.
[0461]
The SFI_SA describes the start address of the SFI with the number of bytes relative to the first byte of the SFIT (F_RBN).
[0462]
The stream object stream information SOB_STI includes three types of parameters. Each parameter can have a unique value for each bitstream record. However, these parameter sets can usually be equal in many bitstream recordings. Therefore, the SOB_STI is stored in a separate table from the table of stream object information (SOBI), and it is recognized that some stream objects (SOB) share the same SOB_STI (that is, point to the same SOB_STI). I have. Therefore, the number of B_STIs is usually smaller than the number of SOBs.
[0463]
Each stream object stream information SOB_STI (eg, SOB_STI # 1) in FIG. 27 includes an application packet size AP_SIZ, the number of service IDs SERV_ID_Ns, a service ID (SERV_IDs), and an application packet device unique ID (AP_DEV_UID). .
[0464]
AP_SIZ is the byte length of the packet in the bit stream transferred from the application device to the streamer, and describes the application packet size.
[0465]
In the DVD streamer, the application packet size is fixed in each bit stream recording. Therefore, if the application packet size changes during each uninterrupted recording, the current stream object (current SOB) is terminated there and a new stream object (new SOB) is added with a new AP_SIZ. Started. At that time, both the current SOB and the new SOB belong to the same program in the original PGC information (ORG_PGCI).
[0466]
SERV_ID_Ns describes the number of service IDs included in the subsequent parameters.
[0467]
SERV_IDs describes a list of service IDs in an arbitrary order.
[0468]
AP_DEV_UID describes a unique device ID unique to the application device that has supplied the recorded bit stream.
[0469]
As shown in FIG. 29, stream file information SFI includes stream file general information SF_GI, one or more stream object information (SOB information) search pointer (SOBI_SRP) #n, and one or more SOB information (SOBI) #n. It is composed of
[0470]
The stream file general information SF_GI includes the number of SOBIs SOBI_Ns, the number of sectors per SOBU SOBU_SIZ, and MTU_SHFT, which is a type of time map information.
[0471]
Here, SOBU_SIZ describes the size of the SOBU 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 included in the first 32 sectors of the SOB. Similarly, the second entry relates to the application packet contained in the next 32 sectors. The same applies to the third and subsequent entries.
[0472]
Each SOB information search pointer (for example, SOBI_SRP # 1) includes a start address SOBI_SA of SOBI. This SOBI_SA describes the start address of the related SOBI by the relative byte number (F_RBN) from the first byte of the stream file information SFI.
[0473]
Each SOB information (for example, SOBI # 1) includes stream object general information SOB_GI, time map information MAPL, and access unit data AUD (optional).
[0474]
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. Of the end application packet SOB_E_APAT, the head stream object unit SOB_S_SOBU of the corresponding stream object, and the number of entries MAPL_ENT_Ns of the time map information.
[0475]
The stream object type SOB_TY is a portion in which a bit indicating a temporary erasure state (TE state) and / or a bit of the copy generation management system can be described.
[0476]
The stream object recording time SOB_REC_TM describes the recording time of the related stream object (SOB).
[0477]
The stream information number SOB_STI_N of the stream object describes an index of the SOB_STI valid for the stream object.
[0478]
The access unit data flag AUD_FLAGS describes whether or not access unit data (AUD) exists for the stream object, and if so, what kind of access unit data.
[0479]
If the access unit data (AUD) exists, AUD_FLAGS describes some characteristics of the AUD.
[0480]
As shown in FIG. 29, 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.
[0481]
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 of the SOBUs belonging to the SOB includes the access unit.
[0482]
The access unit end map AUEM (if present) is a bit array of the same length as AUSM, and indicates which SOBU includes the end of the bit stream segment associated with the access unit of the corresponding SOB.
[0483]
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 a reproduction time stamp (PTS) of the corresponding access unit.
[0484]
Note that an access unit (AU) refers to an arbitrary single continuous part of a 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.
[0485]
Here, the description returns to SOB_GI.
[0486]
AUD_FLAGS includes a flag RTAU_FLG, a flag AUD_FLG, a flag AUEM_FLG, and a flag PTSL_FLG.
[0487]
When the flag RTAU_FLG is 0b, it indicates that there is no access unit flag in the real-time data of the SOB.
[0488]
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. 26A can exist in the real-time data of the SOB. This state is also allowed when AUD_FLG below is 0b.
[0489]
When the flag AUD_FLG is 0b, it indicates that there is no access unit data (AUD) for the corresponding SOB.
[0490]
When the flag AUD_FLG is 1b, it indicates that access unit data (AUD) may exist for the corresponding SOB.
[0490]
When the flag AUEM_FLG is 0b, it indicates that there is no AUEM in the corresponding SOB.
[0492]
When the flag AUEM_FLG is 1b, it indicates that AUEM exists in the corresponding SOB.
[0493]
When the flag PTSL_FLG is 0b, it indicates that no PTSL exists in the corresponding SOB.
[0494]
When the flag PTSL_FLG is 1b, it indicates that PTSL exists in the corresponding SOB.
[0495]
SOB_S_APAT describes the arrival time of the start application packet of the stream object. That is, SOB_S_APAT indicates the arrival time of the first application packet belonging to the SOB.
[0496]
This packet arrival time (PAT) is divided into two parts, a basic part and an extended part. The basic part is a part called a 90 kHz unit value, and the extended part shows a small value measured at 27 MHz (less significant value).
[0497]
SOB_E_APAT describes the arrival time of the end application packet of the stream object. That is, SOB_E_APAT indicates the arrival time of the last application packet belonging to the relevant SOB.
[0498]
SOB_S_SOBU describes the head stream object unit of the corresponding stream object. That is, SOBU_S_SOBU indicates the SOBU including the start portion of the head application packet of the stream object.
[0499]
MAPL_ENT_Ns describes the number of entries of time map information (MAPL) following SOBI_GI.
[0500]
The time map information MAPL has contents corresponding to the time map information 252 in FIG.
[0501]
FIG. 30 shows an example of the relationship between cells and corresponding time information (SC_S_APAT / SC_E_APAT; ERA_S_APAT / ERA_E_APAT) when part of a certain program #j is partially erased (temporary erase and main erase) (part 1). FIG.
[0502]
As described above with reference to FIG. 17, the streamer according to one embodiment of the present invention partially erases a part of a stream completely and temporarily erases a part of a stream (temporary erase; TE). And can be handled.
[0503]
Now, as shown in FIG. 30A, it is assumed that a program #j of an original program (corresponding to SOB #n) is composed of a cell #k, and this cell #k is composed of SOBU # 1 to SOBU # 6. I do. At this time, the start time of cell #k is indicated by SC_S_APAT, and its end time is indicated by SC_E_APAT.
[0504]
In such a program #j, as shown in FIG. 30B, the streamer user sets an area (starting from SC_S_APAT and ending with SC_E_APAT) completely including SOBU # 3 to SOBU # 4 as a temporary erased cell # k + 1. Suppose you set it. At this time, the temporary erasure flag TE of the cell # k + 1 becomes “10b”.
[0505]
In this case, the portion corresponding to SOBU # 1 to SOBU # 2 of the cell #k before the temporary erasure (FIG. 30A) remains the cell #k even after the temporary erasure (FIG. 30B). The portion corresponding to SOBU # 5 to SOBU # 6 after SOBU # 3 to SOBU # 4 included in the temporary erase cell (TE cell) # k + 1 is the cell # after the temporary erase (FIG. 30B). k + 2.
[0506]
As shown in FIG. 30B, the temporary erased cell (TE cell) # k + 1 includes an SOBU boundary formed between SOBU # 3 and SOBU # 4. In this case, the application packet arrival time of the first application packet starting in SOBU # 3 is indicated by ERA_S_APAT of TE cell # k + 1. Further, the application packet arrival time of the first application packet starting in SOBU # 5 including the application packet immediately following TE cell # k + 1 is indicated by ERA_E_APAT of TE cell # k + 1.
[0507]
When TE cell # k + 1 is truly erased (completely erased) from program #j in FIG. 30B, program #j belonging to SOB # n in the original program (FIG. 30A) becomes As shown in c), it is divided into SOB # n and SOB # n + 1.
[0508]
In this case, SC_E_APAT of cell #k after complete erasure can be matched with ERA_S_APAT of TE cell # k + 1. Also, SC_S_APAT of cell # k + 1 after complete erasure can be matched to ERA_E_APAT of TE cell # k + 1.
[0509]
The reason why not only SC_S_APAT and SC_E_APAT but also ERA_S_APAT and ERA_E_APAT are used will be described below.
[0510]
A TE cell can have two special APATs: SC_S_APAT / SC_E_APAT and ERA_S_APAT / ERA_E_APAT. This is because the SOBU (SOBU # 3 to SOBU # 4 in FIG. 30B) in the TE cell can be reused during recording.
[0511]
In other words, when the medium (DVD-RAM disk) 201 becomes full during recording, the streamer completely erases the TE cell to newly record an unrecorded SOBU (SOBU in FIG. 30B). # 3 to SOBU # 4), and the recording is continued without interruption using this SOBU.
[0512]
For the purpose of "acquisition of a new unrecorded SOBU", the TE cells SC_S_APAT and SC_E_APAT alone are not enough. This is because in the search via the time map information (MAPL), there are two possible search positions in the assigned SOBU. However, if ERA_S_APAT and ERA_E_APAT are used, the exact SOBU position can be specified without any involvement in the stream.
[0513]
FIG. 31 is a view for explaining a relationship example (part 2) between cells and corresponding time information (SC_S_APAT / SC_E_APAT) when a part of a certain program #j is partially erased (temporarily erased and main erased). It is.
[0514]
In FIG. 31, the program #j of the original recording is composed of the cell #k (the start time is SC_S_APAT; the end time is SC_E_APAT) with the TE flag of “00b”.
[0515]
Here, it is assumed that the temporarily erased cell does not include the SOBU boundary (ERA_S_APAT / ERA_E_APAT).
[0516]
When provisional erasure is performed on a part of this program #j (range from APAT = A to APAT = B), cell #k of the original recording becomes cell #k (TE flag is "00b"). Start time is SC_S_APATk; end time is SC_E_APATk); cell # k + 1 (TE flag is “10b”; start time is SC_S_APATk + 1; end time is SC_E_APATk + 1); and cell # k + 2 (TE flag is “00b”; start time is SC_S_APATk + 2; the end time is divided into three: SC_E_APATk + 2).
[0517]
After the temporary erasure (TE) is performed, when the original cell is rearranged, as shown in the middle part of FIG. 31, the program #j again returns to the cell #k whose TE flag is “00b” (start time is SC_S_APAT; end time is SC_E_APAT). It becomes.
[0518]
Here, the temporary erasure (TE) operation does not affect the content of the original PGC information, and the content of the stream file information SFI is left unchanged.
[0519]
On the other hand, the user-defined PGC information is not changed or can be modified so that the user-defined cell does not refer to the TE cell.
[0520]
The main operation of the temporary erase is executed in the program #j. The temporary erasure is performed by dividing the cell of the program #j into a normal stream part (a part that has not been erased) and a part that covers the temporary erasure part.
[0521]
If the contents of the user-defined PGC information are left unchanged without any change, the navigation data does not change from the state before the temporary deletion even after the reconfiguration of the TE operation.
[0522]
When the unrecorded area of the information storage medium 201 has been used up and the recording space is insufficient, the temporarily erased cell # k + 1 is completely erased. Then, as shown in the lower part of FIG. 31, the cell #k at the time of temporary erasure remains as a cell #k even after complete erasure, but the cell # k + 2 at the time of temporary erasure becomes cell # k + 1 after complete erasure.
[0523]
FIG. 32 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.
[0524]
The user-defined PGC does not include its own SOB, but refers to the SOB in the original PGC. Therefore, a user-defined PGC can be described only by using PGC information. This means that an arbitrary reproduction sequence can be realized without any manipulation of the SOB data.
[0525]
The user-defined PGC does not include a program and is composed of a chain of cells corresponding to a part of the program in the original PGC.
[0526]
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 cells in the PGC refer to SOBs in the original PGC.
[0527]
In FIG. 32, PGC #n has four cells # 1 to # 4. Two of them refer to SOB # 1, and the other two refer to SOB # 2.
[0528]
A solid arrow from a cell in the user-defined PGC to the original PGC (to the SOBI time map information) indicates a playback period for the cell. The cell playback order in the user-defined PGC may be completely different from the playback order in the original PGC.
[0529]
The reproduction of an arbitrary SOB and its SOBU is specified by the start APAT (S_APAT) and the end APAT (E_APAT) in FIG.
[0530]
S_APAT of SOB or SOBU is defined in relation to a time stamp recorded in the payload (see FIG. 8B) 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).
[0531]
The APAT of the first application packet of the SOB is stored as SOB_S_APAT. The 4 least significant bytes of all APATs are ~. Pre-fixed for the corresponding application packet in the SRO file.
[0532]
In order to reproduce 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 (in the pack header) at which reproduction starts. Based on this clock, reproduction and output of all subsequent application packets from the SOB or SOBU are executed.
[0533]
If any stream cell (SC) specifies a stream cell start APAT (SC_S_APAT) with any value between SOB_S_APAT and SOB_E_APAT of the SOB to which the SC points, the application packet with the desired APAT Is needed to find the SOBU that contains.
[0534]
The number of stream packs per SOBU is constant, but the interval between arrival times captured by each SOBU is flexible. Therefore, each SOB has time map information (MAPL) in which the arrival time interval of the SOBU of the SOB is described. In other words, the address method realized by the time map information (MAPL) converts an arbitrary APAT into a relative logical block address in a file and points to a SOBU where a desired application packet can be found.
[0535]
FIG. 33 is a diagram exemplifying how the contents of the SOBU constituting each stream object (SOB) are recorded in the data area 207 in FIG. 3 (the data areas 21 to 23 in FIG. 1). Here, how the SOB is allocated when the SOB is recorded will be described.
[0536]
In order to effectively utilize the free space of the information storage medium (DVD-RAM disk) 201, as shown in FIG. 33, the SOB can be allocated in a data area dispersed throughout the medium (disk).
[0537]
When such an SOB is read from a medium (disk), the data supply from the medium (disk) is interrupted while jumping from one data area to the next data area. Even in such a case, in order to guarantee continuous supply of SOB data, SOB data is allocated under the following conditions.
[0538]
That is, the SOB is allocated in a chain of continuous data areas (hereinafter abbreviated as CDA as appropriate). A CDA is basically a sequence of consecutive physical sectors in a medium (disk).
[0539]
The minimum length of the DCA and the data allocation in the CDA are limited by a playback device model that can continuously play each SOB.
[0540]
A continuous data area (CDA) is a continuous physical sector in a medium (disk). The CDA is composed of a plurality of ECC blocks. In the CDA, SOB data is continuously allocated unless some physical sectors are skipped during recording in the CDA.
[0541]
The limitations when SOB data is recorded in CDA are as follows: (21) SOB data and other data are not recorded in the same ECC block;
(22) Even if a defective sector is encountered during the recording of SOB data, replacement processing (linear replacement) is not used.
[0542]
Here, a supplementary description will be given of reproduction in the case where a cell start APAT is included in a certain SOBU including a plurality of application packets.
[0543]
A cell may have a cell start APAT or cell end APAT that does not match the SOBU boundary. Now, consider a case where there are two consecutive SOBU # K-1 and SOBU # k, and there is a cell start APAT in an intermediate part in SOBU # k.
[0544]
When starting the reproduction of a series of application packets from the application packet specified by the cell start APAT, first, it is necessary to access SOBU # k including the target application packet (corresponding to the desired APAT). The reason why the target application packet is not immediately accessed is that it is assumed that the address method based on the time map information (MAPL) gives only the start address of the SOBU.
[0545]
In order to find a desired APAT, all application packets in the SOBU # k must be scanned from the beginning (the boundary between SOBU # k-1 and SOBU # k). If a desired APAT is found by this scan, reproduction and output of application packets from the found position are started according to the time stamp (ATS) of those application packets.
[0546]
As described above, the effects of the embodiment of the present invention are summarized as follows.
[0547]
1. Stream data to be recorded on the information storage medium is composed of a stream block of a predetermined size (or SOBU) and recorded / erased in units of the stream block. Access control at the time becomes easier. (At the time of reproduction, as shown in S12 of FIG. 14, reproduction is started from the stream block head position.)
2. Stream data to be recorded on the information storage medium is composed of stream blocks of a predetermined size (for example, 32 kbytes, 64 kbytes), and time stamps and data packets (transport packets) can be recorded across different sectors in the same stream block. , A data packet (transport packet) larger than the sector size (2048 kbytes) can be recorded.
[0548]
3. When a DVD-RAM disk is used as an information storage medium, an ECC block is configured for every 16 sectors, and data interleaving (rearrangement) and an error correction code are added in the ECC block. Therefore, in order to erase, rewrite, or additionally write only a specific sector in the ECC block, all data in the ECC block is once read (read) and rearranged (deinterleaved) in the buffer memory. After that, it is necessary to perform a process of erasing or rewriting data for a specific sector, performing additional writing (modify), recording again with interleaving (rearranging) and adding an error correction code (read-modify-write). Become. This process is very time-consuming, and there is a problem that recording and partial erasure of stream data cannot be performed in real time.
[0549]
On the other hand, the stream block size is set to an integral multiple of the ECC block size (for example, SOBU = 2 ECC block size), and recording and partial erasure are performed in stream block units (SOBU units). For this reason, the read-modify-write process is not required, and it is possible to directly overwrite the information storage medium in ECC block units. As a result, processing of recording or partial erasure of stream data can be performed at high speed, and real-time processing (real-time processing) can be performed.
[0550]
4. By providing unique header information (stream block header or application header) for each stream block, it becomes possible to start reproduction from the head position of the stream block when reproducing stream data. Therefore, the stream data recording / reproducing apparatus (streamer) can easily process the reproduced stream data by reading the stream block header at an early stage.
[0551]
5. As described above, the reproduction is basically started from the head position of the stream block. In rare cases, the reproduction may be started from the head position of the second and subsequent ECC blocks in the stream block.
[0552]
As shown in the example in FIG. 1 where the same transport packet d is recorded over two sectors (sector No. 0 and sector No. 1), reproduction is started from the head position of the second and subsequent ECC blocks. In such a case, it is necessary to know where the next time stamp information is recorded.
[0553]
Unique header information (sector data header or application header) is arranged at the head position of each sector, and the first access point 651 (or FIRST_AP_OFFSET in FIG. 12C) is recorded in the header information. The reproduction can be easily started from the head position of the ECC block after the third.
[0554]
6. As shown in FIG. 1 (j), an end code 32 is attached to the end of the stream data recorded in the stream block # 2. However, when the end code 32 cannot be read due to an error correction error for each ECC block or a data transfer error in the stream data recording / reproducing apparatus when reproducing data from the information storage medium, the stream data is also recorded in the padding area 38. There is a danger that the wrong image will be displayed because it is misinterpreted.
[0555]
The stream ID 603 (or sub-stream ID) of the PES header 601 (or stream PES packet header) in FIG. If 79 is used as the padding packet 40, the encoding unit (video encoding unit 416, audio encoding unit 417, SP encoding The unit 418) understands the padding packet 40 and skips it.
[0556]
By setting the padding packet 40 (or the stuffing packet in FIG. 26 (i)) as described above, even if the padding area 38 is erroneously recognized without being able to read the end code 32, the risk of displaying an incorrect image is greatly increased. Can be reduced.
[0557]
7. The area range specified by the original cell is equal to or smaller than the area range specified by the stream object. By specifying the reproduction range in the remaining stream object after partial erasure in this way, the user can apparently set an arbitrary range as the partial erasure range with high accuracy.
[0558]
The present invention is not limited to the above embodiments, and various modifications and changes can be made at the stage of implementation without departing from the scope of the invention. In addition, the embodiments may be implemented in appropriate combinations as much as possible, and in that case, the effect of the combination is obtained.
[0559]
Further, the 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 components are deleted from all the components described in the embodiment, if at least one of the effects of the present invention or the effects accompanying the implementation of the present invention is obtained, this component is required. The deleted configuration can be extracted as an invention.
[0560]
【The invention's effect】
As described above, according to the present invention, it is possible to improve the stream information recording process.
[Brief description of the drawings]
FIG. 1 is an exemplary view for explaining a data structure of stream data according to an embodiment of the present invention;
FIG. 2 is an exemplary view for explaining a directory structure of a data file according to the embodiment of the present invention;
FIG. 3 is an exemplary view for explaining a recording data structure on an information medium (DVD recording / reproducing disk) according to one embodiment of the present invention;
FIG. 4 is a view for explaining a relationship between a stream object (SOB), a cell, a program chain (PGC) and the like in the present invention.
FIG. 5 is a view for explaining the contents of a stream block size and a stream block time difference in the time map information.
FIG. 6 is a view for explaining a method of specifying a cell range in an original cell and a user-defined cell.
FIG. 7 is an exemplary view for explaining the configuration of a stream data recording / reproducing apparatus (streamer) according to one embodiment of the present invention;
FIG. 8 is a view for explaining the correspondence between digital broadcast contents, video data transfer modes in IEEE 1394, and stream packs in a streamer.
FIG. 9 is a view for explaining a relationship between a video information compression method and a transport packet in MPEG, and a relationship between a transport packet in MPEG and an application packet in a streamer.
FIG. 10 is a view for explaining the internal structure of the PES header shown in FIGS. 1, 8, and 9;
FIG. 11 is a view for explaining the internal structure of the stream block header shown in FIG. 1;
FIG. 12 is a view for explaining the internal structure of a sector data header shown in FIG. 1;
FIG. 13 is a flowchart for explaining a stream data encoding procedure and a recording procedure according to the embodiment of the present invention.
FIG. 14 is a flowchart illustrating a procedure for decoding and reproducing stream data according to an embodiment of the present invention.
FIG. 15 is a diagram (example 1) for explaining a method of partially deleting stream data according to an embodiment of the present invention;
FIG. 16 is a diagram (Example 2) illustrating an explanatory diagram of a method of partially deleting stream data according to another embodiment of the present invention.
FIG. 17 is a flowchart for explaining a procedure for partially deleting stream data according to an embodiment of the present invention;
FIG. 18 is a view for explaining a method of setting time management information for MPEG-encoded video data (before partial erasure or temporary erasure).
FIG. 19 is a view for explaining the relationship between time information and field information in original cell information (before partial erasure or before temporary erasure) corresponding to the video data of FIG. 18;
FIG. 20 is a view for explaining a method of setting time management information for MPEG-encoded video data (after partial erasure or temporary erasure).
FIG. 21 is a view for explaining a relationship between time information and field information in original cell information (after partial erasure or after temporary erasure) corresponding to the video data in FIG. 20;
FIG. 22 is a modified example of FIG. 15, and illustrates an example of a method of partially erasing stream data in a case where all stream blocks are composed of SOBUs of a fixed size (32 sectors = 2 ECC blocks).
FIG. 23 is a modified example of FIG. 22 and illustrates an example of a method of temporarily erasing stream data in a case where all stream blocks are composed of SOBUs of a fixed size (32 sectors = 2 ECC blocks).
FIG. 24 is a diagram illustrating a modification of FIG. 16, illustrating another example of a method of partially erasing stream data in a case where all stream blocks are formed of SOBUs of a fixed size (32 sectors = 2 ECC blocks).
FIG. 25 is a modified example of FIG. 24, illustrating another example of a method of temporarily erasing stream data in a case where all stream blocks are composed of SOBUs of a fixed size (32 sectors = 2 ECC blocks).
FIG. 26 is a view for explaining an example of an internal configuration of a sector forming a stream block (SOBU) (a stream pack including an application packet and a stream pack including a stuffing packet).
27 is a view for explaining the internal data structure of streamer management information (corresponding to STREAM.IFO or SR_MANGR.IFO in FIG. 2).
28 is a view for explaining the internal data structure of PGC information (ORG_PGCI / UD_PGCIT in FIG. 3 or PGCI # i in FIG. 27).
FIG. 29 is a view for explaining the internal data structure of a stream file information table (SFIT in FIG. 3 or FIG. 27).
FIG. 30 shows an example of the relationship between cells and corresponding time information (SC_S_APAT / SC_E_APAT; ERA_S_APAT / ERA_E_APAT) when a part of a certain program #j is partially erased (temporarily erased and main erased) (part 1) FIG.
FIG. 31 is a view for explaining an example (part 2) of a relationship between cells and corresponding time information (SC_S_APAT / SC_E_APAT) when a part of a certain program #j is partially erased (temporarily erased and main erased). .
FIG. 32 is a view exemplifying how cells specified by an original PGC or a user-defined PGC and SOBUs corresponding to these cells are related by time map information.
FIG. 33 is a view showing an example of how the contents of an SOBU constituting each stream object (SOB) are recorded in a data area 207 in FIG. 3 (data areas 21 to 23 in FIG. 1).
[Explanation of symbols]
201: Information medium, 401: Encoding unit, 402: Decoding unit, 404: Main MPU, 409: Disk drive unit

Claims (5)

In an optical disc having a data area for recording stream data and a management area for recording management information of the stream data, a data packet called a transport packet or an application packet is expressed as a first data unit, and a data block called a stream block or a stream object unit. When a 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 recorded in the data area is formed by the stream object of the third data unit including one or more of the second data units including one or more of the first data units ,
The second data unit includes header information;
The header information includes information on a time of the first data unit,
An optical disc configured to record the header information including the information on the time in the data area different from the management area. In a recording method using an optical disk having a data area for recording stream data and a management area for recording management information of the stream data, a data packet called a transport packet or an application packet is expressed as a first data unit, When a data unit called a stream object unit is expressed as a second data unit, and object data called a stream object is expressed as a third data unit,
Forming the stream data recorded in the data area 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 ;
In the second data unit, header information including information on the time of the first data unit is stored,
A recording method configured to record the stream data on the optical disc including the header information including the information on the time. An optical disc having a data area in which stream data is recorded and a management area in which management information of the stream data is recorded, wherein a data packet called a transport packet or an application packet is expressed as a first data unit, and a stream block or a stream When a data unit called an object unit is expressed as a second data unit, and object data called a stream object is expressed as a third data unit, the data unit includes one or more second data units including one or more first data units. It formed the stream data recorded in the data area by the stream object constituted the third data unit, the second data units, including information about the time of the first data unit Header information is stored, including the header information including information on the time, a method of reproducing recorded information from the optical disc in which the stream data is recorded,
Reading the management information from the management area,
A reproduction method configured to read the stream data from the data area in units of the second data. A recording apparatus using an optical disc having a data area for recording stream data and a management area for recording management information of the stream data, wherein a data packet called a transport packet or an application packet is expressed as a first data unit, Alternatively, when a data unit called a stream object unit is expressed as a second data unit, and object data called a stream object is expressed as a third data unit,
Forming the stream data recorded in the data area 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 ; Means for storing header information including information on the time of the first data unit in a data unit;
Means for recording the stream data on the optical disk including the header information including the information on the time. A reproducing apparatus using an optical disk having a data area in which stream data is recorded and a management area in which management information of the stream data is recorded, wherein a data packet called a transport packet or an application packet is expressed as a first data unit, When expressing a data unit called a stream block or a stream object unit as a second data unit, and expressing object data called a stream object as a third data unit, the second data unit including one or more of the first data units 1 above include the stream data recorded in the data area by the stream object constituted the third data unit is are formed, about the time of the first data unit in the second data units That the header information including the information is stored, in the apparatus for reproducing recorded information from the optical disc in which the stream data including the header information is recorded, including information on the time,
Means for reading the management information from the management area,
Means for reading the stream data from the data area in units of the second data.

Images