JP2002197808A - Stream information processing system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To improve processing for recording stream information. SOLUTION: A stream information processing system employs an information medium that has a data area to store stream data subjected to MPEG(Moving Picture Expert Group) encoding and a management area to store management information with respect to the stream data. The data area is configured to store the stream data subjected to MPEG encoding together with I picture information having information of a reproduction time stamp (PTS) in the unit of data packets. Furthermore, the management information is configured to store a time relation table (2) with respect to data transfer time information (4) of the reproduction time stamp (PTS) and the I picture.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an information storage medium for recording video data transmitted in digital broadcasting or the like and stream data transmitted in a packet structure, and a data structure of management information relating to the stream data recorded in the medium. And a recording method and a reproducing method of the management information.

[0002]

2. Description of the Related Art In recent years, TV broadcasting has entered the age of digital broadcasting. Along with this, a device for storing digital data of digital TV broadcasting as digital data regardless of the content, that is, a so-called streamer has been demanded.

[0003] In digital TV broadcasting currently being broadcast, an MPEG transport stream is employed. It is considered that the MPEG transport stream will be used as a standard in the field of digital broadcasting using moving images.

[0004] In this digital broadcasting, the content to be broadcast (mainly video information) is time-divided into data packets of a predetermined size (for example, 188 bytes) called transport packets. Is transmitted.

[0005] As a streamer for recording the digital broadcasting data, a commercially available streamer is currently known as DV
There is a home digital VCR such as HS (digital VHS). In the streamer using the D-VHS, a broadcasted bit stream is directly recorded on a tape. Therefore, a plurality of programs are multiplexed and recorded on the video tape.

[0006] At the time of reproduction, all data is directly sent from the VCR to a set-top box (digital TV receiving apparatus: hereinafter abbreviated as STB) even when reproducing from the beginning or when reproducing 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).

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

[0008] As a promising candidate which can solve such disadvantages of tape (random access difficulty), DVD-
A streamer using a large-capacity disk medium such as a RAM is conceivable. In this case, considering random access and trick play, it is necessary to record management data together with broadcast data.

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

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

For example, in a digital interface using IEEE 1394, in order to guarantee the transfer of digital broadcast reception data in real time, time stamp data indicating the reception time is added to each transport packet. Is being done.

The received data of the digital broadcast recorded on an information storage medium such as a DVD-RAM is
In order to guarantee uninterrupted playback in real time on TB,
On the information storage medium, the time stamp data is recorded simultaneously with each transport packet data.

[0013]

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

In digital TV, video data is MPEG
The information is broadcast in a form where information is compressed using a digital compression method called "2." According to the MPEG2 system, P picture information has only difference information for I pictures, and B picture information has only difference information for I pictures and P pictures. Therefore, a B picture or a P picture cannot be reproduced alone, and reproduction from an I picture is required to reproduce them.

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

The present invention has been made in view of the above circumstances, and has as its object to improve the stream information recording process.

[0017]

In order to achieve the above object, in an embodiment of the present invention, a data area for storing MPEG-encoded stream data (FIG. 3).
(E) STREAM. VRO) and a management area (STREAM.IFO in FIG. 3E) for storing management information on the stream data (STRI in FIG. 3E).
An information medium having the following (201 in FIGS. 3 and 7) is used. Here, the data area (STREAM.VR)
O) is information of a reproduction time stamp (PTS) (FIG. 1)
The MPEG-encoded stream data is stored in units of data packets (transport packets in FIG. 1 (g)), including information on I pictures having (53) in (k) (31 in FIG. 1 (i)). It is configured to The management information (STRI) includes a time relation table (FIG. 3 (h), FIG. 20 (b)) relating to the reproduction time stamp (PTS) and the data transfer time information (4 in FIG. 20 (b)) of the I picture. 2) is configured to be stored.

[0018]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Referring to the drawings, a stream data storage medium according to an embodiment of the present invention, a data structure of management information relating to stream data recorded on the medium, and recording of the management information will be described below. A method, a reproducing method, and the like will be described.

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

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

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

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

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

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

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

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

Each ECC block is composed of 16 sectors as shown in FIG. Therefore, FIG.
As can be seen from (c) to (e), a stream block (or SOBU) # composed of two ECC blocks
1 is 32 sectors (sector No. 0 to sector No. 3)
This corresponds to 1).

That is, if 1 sector = 2 kbytes,
A stream block (SOBU) is 64 kbytes (3
The present invention can be implemented with a fixed size of 2 sectors).

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

At this time, at the beginning of each sector, FIG.
As shown in FIG. 1, pack header 1 in which system clock information (system clock reference SCR) and the like are recorded
1 and 12 and PES headers 13 and 14 are arranged. PE
Immediately after the S header 14, a sector data header 17 is recorded, but only in the first sector of each stream block (or SOBU), a stream block header 16 is recorded instead of a sector data header.

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

The sector data header 17 shown in FIG.
The data array information in the data areas 22 and 23 is shown.

As shown in FIG. 1G, the data areas 21, 22 (or 23) in FIG. 1F have time stamps (corresponding to the ATS shown in FIGS. 20, 29 and others).
And transport packets (corresponding to the packet in FIG. 22 or 23 or the application packet AP in FIG. 29) are sequentially packed.

FIG. 1 (g) shows an example in which one transport packet d is recorded over a plurality of sectors (No. 0 and No. 1). Such a transport packet d corresponds to the partial packet of FIG. 22 or FIG.

By the way, in digital broadcasting, a multiplexing / demultiplexing method corresponding to a multiprogram called a transport stream is adopted, and the size of one transport packet is 188 bytes (or 183 bytes).
Often.

On the other hand, as described above, one sector size is 2
048 bytes, and one data area 21, 22, 23 (FIG. 1)
In (f)), about 10 transport packets for digital broadcasting can be recorded.

FIG. 1 (h) shows the inside of the transport packet.
As shown in FIG.
4 (corresponding to 511 in FIG. 23B described later) and payloads 71 to 75 (FIG.
(Corresponding to 512 in (b)).

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

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

As shown in FIG. 1 (j), each piece of picture information 31-34 divided and recorded in the payloads 71-75 has, at the beginning, picture header information 41
And picture compression information 42 which is substantial picture information
(For I picture information 31, I picture compression information 4
2) is recorded.

Each picture header information 41
As shown in FIG. 1 (k), header identification information 5
1. Picture identification information 52 enabling identification of each I, B, and P picture, PTS (presentation time stamp) information 53 indicating display timing of a decoder output, and DTS indicating a timing at which the decoder starts decoding. (Decode time stamp) information 54 is recorded. These picture header information 4
1 is included in the received information of the digital broadcast in advance.

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

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

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

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

The DVD_RTR (DVD_RTAV) directory 102 contains a data file 1 having the following contents.
03 is stored.

That is, as a group of management information (navigation data), RTR. IFO (or VR_
MANGR. IFO) 104 and STREAM. IFO
(SR_MANGR.IFO / SR_MANGR.BU
P) 105 and SR_PRIVT. DAT / SR_PR
IVT. BUP 105a is stored.

As the data body (content information), STREAM. VRO (or SR_TRANS.
SRO) 106 and RTR_MOV. VRO (VR_M
OVIE. VRO) 107 and RTR_STO. VRO
(Or VR_STILL.VRO) 108 and RTR
_STA. VRO (or VR_AUDIO.VRO)
109 are stored.

Root directory 1 above the subdirectory 101 containing the data file 103
00 is a subdirectory 1 for storing other information.
10 can be provided.

The contents of this subdirectory include a video title set VIDE containing a video program.
There are an O_TS 111, an audio title set AUDIO_TS 112 containing an audio program, a subdirectory 113 for storing computer data, and the like.

For data transmitted in a packet structure on a wired or wireless data communication path, data recorded on an information storage medium while maintaining the packet structure is
Called "stream data".

The stream data itself is STRE
AM. VRO (or SR_TRANS.SRO) 10
The files are collectively recorded with a file name of 6. A file in which management information for the stream data is recorded is STREAM. IFO (or SR_MANGR.
IFO and its backup file SR_MANGR.
BUP) 105.

Also, a VCR (VTR) or a conventional TV
A file in which analog video information handled by, for example, digitally compressing and recording based on the MPEG2 standard is recorded as RTR_
MOV. VRO (or VR_MOVIE.VRO) 1
07, and a file that collects still image information including after-recording audio or background audio is RTR_STO. VRO (or VR_STILL.
VRO) 108, and the post-recording audio information file is RTR_STA. VRO (or VR_AUDIO.
(VRO) 109.

FIG. 3 is a diagram for explaining a recorded data structure (in particular, management information structure) on an information medium (DVD recording / reproducing disk) according to one embodiment of the present invention.

As shown in FIG. 3B, a lead-in area is provided between the end of the information storage medium 201 in the inner circumferential direction 202 and the end of the information storage medium 201 in the outer circumferential direction 203 of FIG. 2
04, volume & file structure information 206 in which file system information is recorded, and data area 207
Then, there is 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.

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.

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, the real-time video recording area 221 has the RTR shown in FIG. Navigation data RTR. IFO (VR_MANGR.IFO)
104 and movie real-time video object R
TR_MOV. VRO (VR_MOVIE.VRO) 1
07 and the still picture real-time video object RTR_STO. VRO (VR_STILL.VR
O) 108 and an audio object RTR_STA. VRO (VR_AUDI
O. VRO) 109 is recorded.

As shown in FIG. 3 (e), the stream recording area 222 contains the streamer navigation data STREAM. IFO (SR_
MANGR. IFO / SR_MANGR. (BUP) 10
5 and transport bit stream data STRE
AM. VRO (SR_TRANS.VRO) 106 is recorded.

Although not shown in FIGS. 3D and 3E, the stream recording area 222 stores the navigation data SR_PR unique to the application shown in FIG.
IVT, DAT / SR_PRIVT. The BUP 105a can also be recorded.

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

[0061] STREAM. IFO (or SR_MANGR.IF
O) 105 has a data structure as shown in FIGS.

That is, as shown in FIG.
REAM. IFO (or SR_MANGR.IFO)
105 is a video manager (VMGI or STR_
VMGI) 231, a stream file information table (SFIT) 232, and original PGC information (ORG
_PGCI) 233, a user-defined PGC information table (UD_PGCIT) 234, a text data manager (TXTDT_MG) 235, 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.

As shown in FIG. 3G, the stream file information table (SFIT) 232 in FIG.
Stream file information table information (SFITI) 2
41 and one or more stream object information (SOB
I) # A · 242, # B · 243,..., Original PGC information general information 271, and one or more pieces of original cell information # 1, 272, # 2, 273,. It has become.

As shown in FIG. 3 (h), each stream object information (eg, SOBI # A · 242) shown in FIG.
I_GI) 251, time map information 252, and the like.

As shown in FIG. 3 (h), each original cell information (for example, # 1, 272; which will be described later and corresponds to the SCI shown in FIG. 14) of the cell type 281 ( Although described later, it corresponds to C_TY shown in FIG. 14), cell ID 282, and corresponding cell start time (SC_S_AP shown in FIG.
AT) 283 and the corresponding cell end time (SC_E_APAT shown in FIG.
284), a PTS offset 9 and a time relation table 2.

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

FIG. 3A included in SOBI # A of FIG.
As shown in FIG. 3I, the time map information 252 of (h) includes a stream block number 261, a first stream block size 262, a first stream block time difference 263, a second stream block size 264, and a second stream block size 264.
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.

FIG. 4 is a diagram for explaining the relationship between a stream object (SOB), a cell, a program chain (PGC) and the like in one embodiment of the present invention.
Hereinafter, the relationship between the SOB and the PGC will be described with reference to FIG.

The stream data (STREAM.VRO)
Or SR_TRANS. The stream data recorded in the (SRO) 106 constitutes a stream block as a group of one or more ECC blocks, and recording, partial erasure processing, and the like 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).

STREAM. VRO (SR_TRAN
S. 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 SRO) 106 includes navigation data STREAM. I
FO (SR_MANGR.IFO) 105 (see the lowermost part of FIG. 4 and FIGS. 3E and 3F).

Each stream object # A · 2 in FIG.
98, # B • 299 (STREAM.IF
O105) includes stream object information (SOBI) # A · 242, # in the stream file information table (SFIT) 232, as shown in FIGS.
B.243.

Stream object information (SOBI)
Each of # A · 242 and (SOBI) # B · 243 contains time map information 252 mainly describing the data size and time information of each stream block.

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

The PGC includes STREAM. VRO (SR
_TRANS. SRO) 106 that can continuously reproduce all stream data recorded in the original P
GC290 (ORG_PGCI · 23 in FIG. 3F)
3) and user-defined PGCs # a • 293, # b •
296 (corresponding to the contents of UD_PGCIT • 234 in FIG. 3F).

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.

On the other hand, user-defined cells # 11-294, # 12-295, #
31.297 is one stream object #A.
Any position can be set within the range of 298 or # B · 299.

Although the sector size of each stream block can be variously set, a preferred embodiment is 2 EC as in stream block # 1 in FIG.
Stream object unit (SOBU) with C block (32 sectors) and fixed size (64 kbytes)
May be adopted as a stream block.

If the stream block is fixed to the SOBU having a fixed size (for example, 2 ECC blocks = 32 sectors = 64 kbytes), the following advantages can be obtained:
(01) Even if the stream data is erased or rewritten in SOBU units, the ECC block of the SOBU is
It does not affect the ECC blocks of the SOBU other than those to be erased or rewritten. Therefore, ECC associated with erasing or rewriting (for SOBUs not subject to erasing or rewriting)
(02) The access position to the recording information in an arbitrary SOBU is determined by the number of sectors (or another parameter corresponding to the number of sectors; for example, the stream pack shown in FIG. Internal application packet group information). For example, a certain SOBU # k
Is accessed at the 16th sector (or 16th sector) from the boundary between SOBU # k-1 and SOBU # k.
The position of the application packet corresponding to the sector number)
Should be specified.

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

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

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

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

Also, SOB # A · 298 (FIG. 5 (g))
The stream block # 2 (FIG. 5 (f)) following the sector No. 32 (FIG. 5 (e)) and sector N
o. Data area 311 included in 32 (FIG. 5D)
A time stamp p (FIG. 5 (c)) is recorded at the head of.

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

The first stream block time difference 263 shown in FIG. 5B (the stream block time difference 26 shown in FIG.
3) is given by the difference between the time stamp p and the time stamp a ([time stamp p]-[time stamp a]).

The time map information 25 shown in FIG.
2 can be handled as including an access data unit AUD in the stream object information SOBI described later with reference to FIG. Information contained in this AUD (Access unit start map AUSM, etc.)
Thus, the SOBU including the information to be accessed can be specified.

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

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

On the other hand, user-defined cell # 12.2
In the time range specification in 95 (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 replaced by the values of the start time 331 of the corresponding cell and the end time 332 of the corresponding cell. Can be set as

FIG. 6F shows that stream object (SOB) #A 298 is composed of two stream blocks #
1 illustrates an example in which the configuration includes # 1 and # 2.

In the example shown in FIGS. 6E and 6G, the stream block # 1 has 32 sectors (sector Nos. 0 to 3).
1), and the stream block # 2 is composed of 48 sectors (sector Nos. 32 to 79).

[0092] First sector N of stream block # 1
o. 0 indicates a pack header 1, a PES header 6, and a stream block header 1 as shown in FIGS.
1, a data area 21 and the like.

Further, the backward sector No. of the stream block # 2 is set. Reference numeral 78 denotes a pack header 3, a PES header 8, and a sector data header 1 as shown in FIGS.
3, data area 24 and the like.

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.
(G) Sector No. 33, a sector data header 321, a data area 312 and the like are recorded as shown in FIG.

As shown in FIGS. 6C and 6I, the data area 21 in FIGS. 6D and 6H has a time stamp a.
And a transport packet a or a time stamp d and a transport packet d.

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,
A padding area 37 is recorded.

Further, as shown in FIG. 6 (i), the data area 22 of FIG. 6 (h) includes a transport packet d including the contents subsequent to the transport packet d of the data area 21. That is, in this example, the contents of the transport packet d are recorded in the data area 21 and the data area 22 separately.

The first half (the data area 21 side) of the transport packet d in FIG.
Corresponding to the last partial packet of (f), the latter half of the transport packet d of FIG.
Side) corresponds to the leading side partial packet in FIG.

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

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

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

The cell end time 332 (FIG. 6 (j)) 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. This cell end time 332 can be expressed as a cell end APAT.

The above cell start time (cell start APAT)
331 and cell end time (cell end APAT) 332
Is the user-defined cell information # 1 as shown in FIG.
2.295.

This user-defined cell information # 12 · 295
Is a user-defined PGC shown in FIG.
It can be recorded in the information table 234.

The above is the description of the user-defined cell information (user-defined P
Regarding the cell start / end time information regarding the GC information), the cell start / end time information regarding the original cell information (original cell information) can be exemplified as follows.

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 corresponding cell can be indicated by the tail time stamp z in FIG. Can be.

The start time 283 of the corresponding cell in FIG.
Is the cell start APAT (stream cell start APAT)
(SC_S_APAT) or erase start APAT (ER
A_S_APAT).

The end time 2 of the corresponding cell in FIG.
Reference numeral 84 denotes a cell end APAT (stream cell end APA).
T (SC_E_APAT) or erase end APAT (E
RA_E_APAT).

The above cell start time (cell start APAT)
283 and cell end time (cell end APAT) 284
Is the original cell information # 1 as shown in FIG.
• Recorded inside 272.

This original cell information # 1, 272 is
It can be recorded in the original PGC information 233 shown in FIG.

FIG. 7 shows a recording data structure (in particular, reproduction end position information / resume information, VMGI) on an information medium (DVD recording / reproducing disk) according to another embodiment of the present invention.
FIG. 3 is a diagram for explaining management information / recording time information and the like);

The data structure of FIGS. 7A to 7F is shown in FIG.
Since they are the same as (a) to (f), their description is omitted.

The video manager (STR_) shown in FIG.
As shown in FIG. 7G, the VMGI 231 includes reproduction end position information (resume information) 6110, video manager management information (VMGI_MAT) 6111, and the like.

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

The video manager management information (VMG
I_MAT) 6111 is a time zone (TM_ZON)
E) 6240.

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

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

Time zone (TM_ZONE) 6240
Is the recording time (REC_T) as shown in FIG.
M).

Information on the recording time (REC_TM) is
A time zone type (TZ_TY) that identifies whether C_TM is due to Universal Time Coordination (UTC) or a specific local time;
A time zone offset (TZ_OF) describing the date and time of the time offset of REC_TM from UTC in minutes.
FSET).

The recording time (REC_TM) is shown in FIG.
(B) Cell start time (SC_S_APAT), etc.
Or the reproduction time of the cell (presentation time PTM).

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

Here, the time at which the stream object (SOB) corresponding to the original cell is recorded is represented by SO
Indicated by B_REC_TM.

A playlist is a partial list of a program. The playlist allows the user to define an arbitrary playback sequence (with respect to the contents of the program). The time when such a playlist is created is indicated by PL_CREATE_TM.

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

The PES header 601 shown in FIG.
As shown in (b), it includes a packet start code prefix 602, a stream ID 603, a reproduction time stamp 604, and the like. The PES header 601 corresponds to the PES header shown in FIGS. 1F, 5D, 6D, and the like.

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

When the PES header in FIG. 1F has the internal structure of the PES header 601 shown in FIG.
According to the EG standard, the stream ID 6
03 (FIG. 8B) is “10111110”,
It is defined that a packet having this PES header is a padding packet (see FIG. 12 (g) described later).

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

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

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

The stream block header 11 is shown in FIG.
As shown in (a), it has contents corresponding to the substream ID, application header, application header extension, stuffing byte, and the like.

The 1-byte application header extension (optional) has a 1-bit AU_ST
ART, 1-bit AU_END, and 2-bit CO
PYRIGHT is described.

When AU_START is set to “1”, the associated application packet (for example, FIG.
9 AP) is shown to include a random access entry point (start of random access unit) in the stream.

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

[0135] COPYRIGHT describes the copyright status of the related application packet.

The stream block header 11 is shown in FIG.
As shown in (b), the transport packet information 61
1, stream block information 612, sector data header information 613, and the like.

The transport packet information 611 in FIG. 9B is the transport packet information 61 in FIG. 9C.
Refers to the same as 1.

The stream block information 61 in FIG. 9B in which information on the entire stream block is recorded.
2 is the recording time 622 (the information storage medium 20) in FIG.
1), the transport packet attribute 623 (attribute information on the transport packet), the stream block size 624 (the data size of the corresponding stream block (for example, the number of ECC blocks can be described)), the stream Block time difference 6
25 etc.

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

Also, the sector data header information 613 in FIG. 9B includes the first access point 626 and the transport packet connection flag 627 in FIG.
Corresponding to The sector data header information 613 includes the same information as the sector data header 12 in FIG. 10 described later.

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

The number of application packets in FIG. 9D corresponds to the number of packets AP_Ns in FIG. 10C or FIG. 11 described later.

The number 631 of transport packets (application packets) in FIG. 9D is, as shown in FIG. 9E, the I-picture mapping table 641,
A B and P picture mapping table 642 can be included.

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

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

For example, when n transport packets (application packets) are recorded in one stream block, the number of transport packets (the number of application packets) shown in FIG.
The value of 31 is "n".

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

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

For example, the sector data header 17 shown in FIG. 1 (f) indicates the data arrangement information in the data areas 22 and 23, and the sector data header 17 shown in FIG.
0 (corresponding to the application header of 0 (d)).

The sector data header 12 is as shown in FIG.
As shown in (1), it has an internal structure including a first access point 651 and a transport packet connection flag 652.

By the way, as shown in FIG.
One stream pack having the same size as a sector and having a size of 2048 bytes includes a pack header and a stream PE.
It is composed of an S header. And this stream P
In the ES packet, the sector data header 12 shown in FIG. 10A or the stream block header 1 shown in FIG.
1 includes an application packet header corresponding to a part of the application packet header.

This application packet header is
As shown in FIG. 10C, the following are included: * Version description of application packet header format; * Number of application packets (transport packets) starting in the corresponding stream pack AP_Ns; * Corresponding stream pack , Where the time stamp position of the first application packet starting within the field is described as a relative value from the first byte of the stream pack.
T_AP_OFFSET; * Extension header information EXTENSION_HEADER_IFO indicating whether or not a header extension and / or stuffing byte exists; * Identifier SERV of the service that generated the corresponding stream
ICE_ID.

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

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

In the example of FIG. 1 (g), 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 (bit unit). Expression) has been.

The sector No. shown in FIG. 1 (or its corresponding stream pack) is assigned the first access point value of sector No. 1. 1 data area 22 (FIG. 1)
It can be set to a value larger than the size of (f)). 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.

In one embodiment of the present invention, the value of the first access point 651 is
By making it possible to specify a value larger than the size of 22 or 23, it is possible to specify the time stamp head position even for a packet having a size larger than the sector size (or stream pack size = 2048 bytes). .

For example, in the data structure of FIG.
Packets are sector Nos. 0 to sector No. It is assumed that the data 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 arranged at the T-th bit in the second data area.

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

FIG. 11 is a diagram for explaining another example of the time map information 252 in the embodiment of the present invention.

[0161] The time map information 252 corresponds to
(H) This is another example different from the time map information 252 of (i). For each stream block (first stream block, second stream block, ...), the stream block size, the stream block time difference, and the number of packets ( AP_Ns).

Using the time map information 252 shown in FIG.
It is assumed that the total number of transport packets (or the total number of application packets AP_Ns) has been designated (from the STB side) to access a predetermined screen (picture). Then, (on the disk device side) the number of transport packets (A
P_Ns), and accesses the stream block at the time when the specified value is reached.

FIG. 12 shows a stream block (SOB
FIG. 4 is a diagram illustrating an example of an internal configuration of a sector (U) including a stream pack including an application packet and a stream pack including a stuffing packet.

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

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

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

As shown in FIG. 12B, the first stream block (SOBU) # 1 of SOB # A · 298
Sector No. 0 to sector No. 31 (32 sectors / 64
k bytes).

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

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

The stream PES packet includes a 6-byte PES header, a 1-byte sub-stream ID,
And a stream data area of 027 bytes.

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

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

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

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

The stuffing byte shown in FIG.
This can be used to always keep the stream pack at a predetermined length (2048 bytes).

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

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.

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

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

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

The AP_Ns of the application header is
This describes the number of application packets that start 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.

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 no application packet starts in the stream packet, FIRS
“0” is described in T_AP_OFFSET.

EXTENSION_HEADER_IN
The FO describes whether an application header extension and / or a stuffing byte exists in the corresponding stream packet.

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

EXTENSION_HEADER_IN
If the content of the FO is 10b, it indicates that an application header extension is present after the application header, but no stuffing byte is present.

EXTENSION_HEADER_IN
If the content of the FO 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.

EXTENSION_HEADER_IN
The content of the FO is not allowed to be 01b.

The stuffing byte (optional) in front of the application packet area is “EXTENSE”.
ION_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.

[0189] SERVICE_ID describes the ID of a service that generates a stream. If this service is unknown, 0x00 is set in SERVICE_ID.
00 is described.

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

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

Stated another way, a partial application packet can exist at the start position of the application packet area. At the end position of the application packet area, a partial application packet or a stuffing area of a reserved number of bytes can exist.

The application time stamp (ATS) placed before each application packet is 32
It consists of bits (4 bytes). This ATS is divided into two parts, a basic part and an extended part. The basic part is the part called 90 kHz unit value,
The extension is a fine value measured at 27 MHz (less signifi
cant value).

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

Therefore, the data field of the application header indicates that the optional application header extension exists in the stream data area (EXTENSION_HEADER described above).
_INFO).

At the time of recording a stream, the first byte of the application time stamp ATS of the first application packet is the stream object SO
It must be aligned with the start position of the application packet area in the first stream packet at the beginning of B.

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.

FIG. 22 or FIG.
The partial application packet shown in (g) indicates an application packet generated by this division (split).

The byte offset of the first application timestamp starting in the stream packet,
And the number of application packets started in the stream packet is described in the application header.

In this way, in a certain stream packet, the stuffing before the first application time stamp and after the last application packet is automatically performed.

That is, by the above-mentioned automation mechanism,
"Applications do their own stuffing"
Is realized. Due to this automatic stuffing, stream packets always have the required length.

The application header extension (optional) is composed 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.

The 1-byte application header extension (option) has a 1-bit AU
_START, 1-bit AU_END, and 2-bit COPYRIGHT are described.

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

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

[0206] COPYRIGHT describes the copyright status of the related application packet.

The packet structure shown in FIG.
It can be applied to other than the last sector of A · 298, but is not necessarily applied to the last sector.

For example, the end of SOB # A · 298 is the sector No. shown in FIG. When this sector is composed of padding packets 40 as shown in FIG. 12 (g), the padding area 38 (FIG.
The content of (h)) is different from that of FIG.

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

In the pack including the head of the stuffing packet, this application packet area has a 4-byte application time stamp ATS and 2 bytes.
It is composed of 014 bytes of zero byte data (data having substantially no recorded content).

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

By the way, when recording at a very low bit rate is performed, the time map information (25 in FIG.
2; or stuffing is required to ensure the recovery (reproduction) of the later-described MAPL in SOBI (FIG. 15). The stuffing packet in FIG.
It is defined as a conceptual unit for that purpose.

[0213] The purpose of this stuffing packet is achieved by making each SOBU including at least one stuffing area include at least one ATS value.

A stuffing packet is subject to the following conditions: * One or more stuffing packets always start with the application packet area of the pack after the pack containing the actual application packet data; The stuffing packet is one 4
It consists of a byte ATS and zero byte data (following the ATS) necessary to fill the application data area of the remaining pack of the SOBU.
Now, the number of sectors per SOBU is represented by SOBU_SI
Assuming that Z is 0 ≦ n ≦ SOBU_SIZ−1, the total length of the stuffing packet is “4 + 2014”.
+ N × 2018 ”bytes.

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

All the packs including the stuffing packet or a part of the stuffing packet are configured as follows: * The SCR of the pack header is "2"
048 x 8 bits {10.08 Mbps]; * PES packet header and substream ID are
Same as for all other PES packets; * Application header (see FIGS. 10 (c) (d))
Within, AP_Ns = 0, FIRST_AP_OF
FSET = 0, EXTENSION_HEADER_I
FO = 00b, SERVICE_ID = 0 (other parameters in the application header are also 0).

FIG. 13 shows streamer management information (STREAM.IFO or SR_MANGR.IFO in FIG. 2).
FIG. 7 illustrates an internal data structure of FIG.

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

This streamer information STRI is shown in FIG.
(F) Or, as shown in FIG. 13, the streamer video manager information STR_VMGI, the stream file information table SFIT, and the original PGC information OR
G_PGCI (more generally, PGC information PG
CI # i) and a user-defined PGC information table UD_P
GCIT and text data manager TXTDT_M
G and an application private data manager APDT_MG.

Streamer video manager information STR_
VMGI includes STR, STR_ as shown in FIG.
Video manager information management information VTSI_MAT in which management information related to VMGI is described, and a playlist search pointer table (PL_S) in which a search pointer for searching a playlist in a stream is described.
RPT).

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

Stream file information table SFIT
Contains 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.

Original PGC information ORG_PGCI
Is a portion in which information about the original PGC (ORG_PGC) is described. ORG_PGC indicates navigation data describing a program set. ORG_
PGC is a chain of programs.
Alternatively, it includes stream data recorded in a “.SRO” file (SR_TRANS.SRO 106 in FIG. 2) described later in FIG.

Here, the program set indicates the entire recorded contents (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 is an original PGC (OR
G_PGC).

A program is a logical unit of recorded contents 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.

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

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.

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

Note that the program chain (PGC) indicates a higher-level conceptual unit. In the original PGC,
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.

The user-defined PGC indicating a part of the chain of the program includes only navigation data. Part of each program is an original PGC
Is referred to.

User defined PGC information table U in FIG.
D_PGCIT 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.

User-defined PGC information table information UD_
PGCITI is UD_PG indicating the number of user-defined PGC search pointers UD_PGC_SRP (not shown).
C_SRP_Ns and user-defined PGC information table U
UD_PGCIT indicating the end address of D_PGCIT
_EA.

UD_PGC_SRP_Ns indicates UD_
The number of PGC_SRPs is based on the user-defined PGC information (UD_
PGCI) and the number of user-defined PGCs (UD
_PGC). This number can be up to "9
9 "is allowed.

UD_PGCIT_EA is the corresponding UD_P
The end address of the GCIT is described by the relative byte number (F_RBN) from the first byte of the UD_PGCIT.

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

Original PGC information ORG_PGCI or user-defined PGC information table UD_PGCIT
PGCI # i, which generally represents user-defined PGC information UD_PGCI, will be described later with reference to FIG.

The text data manager TXT shown in FIG.
DT_MG is supplementary text information. This TX
TDT_MG is the primary text information PR in FIG.
Along with M_TXTI, it can be stored in playlists and programs.

Although not shown, the application private data manager APDT_M shown in FIG.
DT_GI and one or more APDT search pointers APD
T_SRP # n and one or more APDT areas APADT
A # n.

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

FIG. 14 shows PGC information (ORG_P in FIG. 3).
GCI / UD_PGCIT or PGCI # in FIG.
It is a figure explaining the internal data structure of i).

The PGC information PGCI # i shown in FIG.
No. 3 original PGC information ORG_PGCI or user-defined PGC information UD_PGCI in the user-defined PGC information table UD_PGCIT.

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

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

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

Here, the program type PG_TY is
Contains information indicating the status of the program. In particular, it includes a flag indicating whether the program is protected from erroneous erasure or the like, that is, a protect flag.

When the protect flag is "0b", the program is not protected, and when it is "1b", the program is protected.

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.

For example, if program # 1 in PGC is C
_Ns = 1, and if program # 2 has C_Ns = 2, the first stream cell information S of the PGC
The CI is associated with the program # 1, and the second and third SCIs are associated with the program # 2.

Primary text information PRM_TXTI
In order to make the information storage medium (DVD-RAM disk) 201 available worldwide, one common character set (ISO / IEC646: 1983 (ASCII
Code)) describes text information.

Item text search pointer number I
T_TXT_SRPN describes a search pointer number for the item text (text data corresponding to the program) IT_TXT. If the program does not have item text, IT_T
XT_SRPN is set to "0000h".

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

Each stream cell information SCI (for example, S
CI # 1) includes stream cell general information SC_GI,
One or more stream cell entry point information SC_E
PI # n.

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

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

That is, cell format C_TY1 = “01”
“0b” is described in the format of all stream cells (the stream cell and other cells can be distinguished by C_TY1 = “010b”).

On the other hand, if the flag TE is "00b", it indicates that the corresponding cell is in a normal state. If the flag TE is "01b" or "10b", the corresponding cell is in a state of temporary erasure. Is shown.

The flag TE = "01b" indicates that the corresponding cell (cell in the provisionally erased state) starts after the first application packet starting in the SOBU, and the same SOB
It shows a case where the processing ends before the last application packet in U.

The flag TE = “10b” indicates that the corresponding cell (cell in the temporarily erased state) has at least one SO
The case where a BU boundary is included (the first application packet or the last application packet starts in the SOBU) is shown.

Note that the program protect flag
It cannot be set at the same time as the TE flag of a cell in the program. Therefore, (a) none of the cells in the program in the protected state can be set to the temporary erase state; (b) a program including one or more cells in the temporary erase state cannot be set to the protected state.

The number SC_EPI_Ns of the stream cell entry point information is equal to the corresponding stream cell information SC.
It describes the number of stream cell entry point information included in I.

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

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 the entry point type EP_TY1 = “00”
b ".

The type B SC_EPI is the type A E
Primary text information PRM_TXTI is included in addition to P_TY and EP_APAT. Type B is indicated by the entry point type EP_TY1 = "01b".

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

Stream Object Number SOB_N
Describes the number of the SOB to which the corresponding cell refers.

Stream cell start APAT (SC_S_
APAT) describes the start APAT of the corresponding cell.

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

Erasure start APAT (ERA_S_APA)
T) is the first SOBU including the head in the temporary erased cell including at least one SOBU boundary (the TE field of the C_TY is “10b”).
Describes the arrival time (APAT) of the first application packet that starts within.

Erasure end APAT (ERA_E_APA)
T) is the arrival of the first application packet starting in the SOBU containing the application packet immediately following the provisionally erased cell in the temporarily erased cell containing at least one SOBU boundary (its TE field of C_TY is "10b"). Time (APAT) is described.

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

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

[0272] Stream file information table information SF
ITI is an information storage medium (DVD-RAM disk) 2
01, the number of stream file information SFI_Ns on
Number of stream object stream information following SFITI SOB_STI_Ns, end address SFIT_EA of SFIT, start address SFI_S of SFI
A.

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

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

Each stream object stream information SOB_STI includes three types of parameters. Each parameter can have a unique value for each bitstream record. However, these parameter sets can usually be equal in many bitstream recordings. Therefore, SOB_STI is
It is stored in a table different 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). Therefore, the SOB is usually smaller than the number of SOBs.
The number of B_STIs is smaller.

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

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.

[0278] 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 the new stream object (new SOB) is replaced with a new AP_SIZ. Is started with At that time, both the current SOB and the new SOB belong to the same program in the original PGC information (ORG_PGCI).

[0279] SERV_ID_Ns describes the number of service IDs included in the subsequent parameter.

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

AP_DEV_UID describes a unique device ID unique to the application device that supplied the recorded bit stream.

The stream file information SFI is shown in FIG.
, The stream file general information SF_GI
And one or more stream object information (SOB information) search pointers (SOBI_SRP) #n and one or more SOB information (SOBI) #n.

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.

Here, SOBU_SIZ describes the size of SOBU by the number of sectors, and this size is 32
(32 sectors = 64 kbytes). This means that in each time map information (MAPL), the first entry relates to the 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.

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

Each SOB information (for example, SOBI # 1)
Are stream object general information SOB_GI,
It consists of time map information MAPL and access unit data AUD (optional).

Stream Object General Information SOB_
GI is a stream object type SOB_TY
And stream object recording time SOB_REC_
TM, stream information number SOB_STI_N of the stream object, access unit data flag AUD_FLAGS, and start application packet arrival time SOB_S_APA of the stream object
T, the end object packet arrival time SOB_E_APAT of the stream object, the head stream object unit SOB_S_SOBU of the stream object, and the number of entries MAPL_ENT_Ns of the time map information.

Stream Object Type SOB_
TY is a bit indicating a temporary erase state (TE state) and / or
Alternatively, it is a part in which bits of the copy generation management system can be described.

Stream Object Recording Time SOB_
REC_TM is an associated stream object (SO
B) describes the recording time.

[0290] The stream information number SOB_STI_N of the stream object describes the index of the SOB_STI valid for the stream object.

Access unit data flag AUD_F
The LAGS describes whether or not access unit data (AUD) exists for the stream object, and if so, what kind of access unit data it is.

If access unit data (AUD) exists, some characteristics of the AUD are described by AUD_FLAGS.

The access unit data (AUD) itself includes, as shown in FIG.
U_GI and access unit end map AUEM
And a reproduction time stamp list PTSL.

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

Access unit end map AUEM
Is a bit array of the same length as AUSM (if present), and terminates the bit stream segment associated with the access unit of the corresponding SOB with any SOBU.
Indicates whether or not

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

An access unit (AU) refers to an arbitrary single continuous portion 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.

Here, the description returns to the contents of SOB_GI.

AUD_FLAGS is a flag RTAU_
FLG, flag AUD_FLG, and flag AUEM_
FLG and a flag PTSL_FLG.

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

When flag RTAU_FLG is 1b,
The AU flag (AU_) described in the application header extension of FIG. 9A or FIG.
START, AU_END) can be present in the real-time data of the corresponding SOB. This state is also allowed when AUD_FLG below is 0b.

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

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

When the flag AUEM_FLG is 0b,
This indicates that AUEM does not exist in the corresponding SOB.

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

When flag PTSL_FLG is 0b,
This indicates that PTSL does not exist in the corresponding SOB.

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

[0308] SOB_S_APAT describes the start application packet arrival time of the stream object. That is, SOB_S_APAT indicates the arrival time of the first application packet belonging to the SOB.

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

[0310] 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.

[0311] SOB_S_SOBU describes the head stream object unit of the stream object. That is, SOBU_S_SOBU indicates the SOBU including the start portion of the head application packet of the stream object.

[0312] MAPL_ENT_Ns is SOBI_G
It describes the number of entries of time map information (MAPL) following I.

The time map information MAPL is shown in FIG.
Has the content corresponding to the time map information 252.

One of the relationships between the contents shown in FIGS. 13 and 15 can be summarized as follows: The streamer information STRI included in the management information 105 is a stream object SOB constituting a part of the contents of the stream data.
And a stream file information table SFIT for managing This SFIT includes stream object information SOBI for managing the SOB. This SOBI includes access unit general information AU_GI including management information (access unit start map AUSM) and management information (PT
SL).

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

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

As shown, the bit “AUSM”
1 ”is the access unit (A
U) is included.

Now, the ith (1 ≦ i ≦ AU_Ns) bit position where the bit is set in AUSM is set to AUSM
_Pos (i). Then, the position of the access unit AU is as follows.

(1) If SOBU # i, indicated by AUSM_pos (i), contains one or more start AUs (which are described by AU_START and AU_END marks (if any) in the stream), AUSM_pos ( i) is assigned to the first AU starting in SOBU # i. Here, SOBU #
i is the S described by AUSM_pos (i) and AUEM_pos (i) (if AUEM is present)
These are arranged in OBUs.

(2) The AU ends with the AU_END mark that appears first after the start of the AU, and the AU ends with the last SOBU indicated by the assigned AUEM element (if an AUEM is present).

In any access unit data, it is not possible to describe two or more accessible access units for each SOBU of the SOB.

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

AUEM is the AUS (if any)
It is a bit array of the same length as M. The bit of AUEM indicates which SOBU includes the end of the bit stream segment attached to the access unit of the corresponding SOB.

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

Now, the i-th (1 ≦ i ≦ AU_Ns) bit position where a bit is set in AUSM is set to AUSM
_Pos (i), and the ith (1 ≦ i ≦ AU_Ns) bit position where the bit is set in the AUEM is AUE
Look at M_pos (i). In this case, there is the following relationship.

(1) 1 ≦ AUSM_pos (i) ≦ AU
EM_pos (i) ≦ MAPL_ENT_Ns; (2) AUSM_pos (i + 1)> AUEM_pos
(I); (3) If i == AU_Ns or AUSM_pos
If (i + 1)> 1 + AUEM_pos (i), AU #
i ends with SOBU # [AUEM_pos (i)] (1 ≦ i ≦ AU_Ns); (4) If AUSM_pos (i + 1) == 1 + AUE
If M_pos (i), AU # i becomes SOBU # [AU
EM_pos (i)]. Or SOBU #
[1 + AUEM_pos (i)] == SOBU # [Au
SM_pos (i + 1)]. That is, AU # i ends where AU # i + 1 starts in the SOBU (1 ≦ i ≦ AU_Ns).

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

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

The user-defined PGC does not include a program, and is constituted by a chain of cells corresponding to a part of the program in the original PGC.

An example of such a user-defined PGC is shown in FIG. In this example, a user-defined PGC is created so that cells in the PGC refer to SOBs in the original PGC.
This shows a case where GC # n has been created.

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

A solid line arrow from a cell in the user-defined PGC to the original PGC (to the SOBI time map information) indicates a reproduction 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.

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.

S_APAT of SOB or SOBU
Is the payload of the stream pack of the corresponding SOB (FIG. 1)
(H), see FIGS. 22 and 23).

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

The APAT of the first application packet of the SOB is stored as SOB_S_APAT. 4 least significant bytes of all APATs
bytes) are pre-fixed for the corresponding application packet in the "~ .SRO" file.

In order to reproduce SOB or SOBU data, the reference clock in the streamer is set to S.
It is set to the CR value, after which 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 SOB or SOBU are
Be executed.

An arbitrary stream cell (SC) has its S
SOB_S_APAT and SO of SOB pointed by C
When a stream cell start APAT (SC_S_APAT) having an arbitrary value between B_E_APAT is specified, an address for finding an SOBU including an application packet with a desired APAT is required.

Although the number of stream packs per SOBU is constant, the interval between arrival times captured by each SOBU is flexible. Therefore, each SOB
Has time map information (MAPL) in which the SOBU arrival time interval of the corresponding SOB is described. That is, 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.

FIG. 19 is a diagram showing a stream data recording / reproducing system (optical disc apparatus / optical disc apparatus) according to an embodiment of the present invention.
FIG. 2 is a diagram illustrating a configuration of a streamer and an STB device.
In this embodiment, the information storage medium 201 is a DV
A recordable / reproducible optical disk such as a D-RAM disk is assumed.

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

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

As the peripheral device, the video mixing unit 4
05, a frame memory unit 406, an external speaker 433,
Personal computer (PC) 435, monitor TV4
37, D / A converters 432 and 436, I / F unit 43
1, 434 and the like.

The optical disk device 415 includes a recording / reproducing unit 409 including a disk drive, and a data processor unit (hereinafter referred to as D-processing unit) for processing stream data to the recording / reproducing unit 409 (or stream data from the recording / reproducing unit 409).
PRO section 410), a temporary storage section 411 for temporarily storing stream data overflowing from the D-PRO section 410, a recording / reproducing section 409 and a D-PRO section.
An optical disk device control unit 412 that controls the operation of the PRO unit 410 is provided.

The optical disk device 415 further receives stream data transmitted from the STB device 416 via IEEE 1394 or the like (or IEEE 1394).
And the like, which converts the stream data received by the data transfer interface unit 414 into a signal format to be recorded on the information storage medium (RAM disk) 201 (or the medium). And a formatter / deformatter unit 413 for converting the stream data reproduced from the data stream 201 into a signal format such as IEEE1394.

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

[0347] Based on the above time information, partition information for partitioning the stream data into stream blocks (or SOBUs) is created, and cell partition information and program partition information corresponding to the partition information are further created. Create PGC separation information.

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

Here, in the recording / reproducing unit 409, the medium 2
01 is not ready for recording, D-PRO
The unit 410 transfers the recording data to the temporary storage unit 411 and temporarily stores the data, and waits until the recording / reproducing unit 409 is ready for data recording.

When the recording / reproducing section 409 is ready for recording, the D-PRO section 410 transfers the data stored in the temporary storage section 411 to the recording / reproducing section 409. Thereby, recording on the medium 201 is started. Temporary storage unit 4
11 is completed, the subsequent data is transmitted from the formatter / deformatter unit 413 to the D-
The data is seamlessly transferred to the PRO unit 410.

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.

Incidentally, the formatter / deformatter unit 4
The time stamp information attached to the recording bit stream via 13 can be obtained from a reference clock generator (STC) 440.

In addition, the formatter / deformatter unit 4
The time stamp information (SCR) extracted from the playback bitstream via S13 can be set in the STC 440.

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

That is, in order to reproduce SOB or SOBU data, a streamer (optical disk device 41) is used.
The reference clock (STC 440) in 5) is adjusted to the system clock reference SCR described in the first stream pack from which reproduction is started. After that, S
The count up of the TC 440 is automatically performed.

[0356] STB section 416 demodulates the contents of the digital broadcast wave received by satellite antenna 421, and provides demodulator 422 for providing demodulated data (stream data) in which one or more programs are multiplexed, and demodulator 422.
A reception information selector 42 for selecting information of a specific program (desired by the user) (a transport packet of program 2 in the case of FIG. 23 described later as an example) from the data demodulated in step (1).
3 is provided.

When the information (transport packet) of the specific program selected by the reception information selector unit 423 is recorded in the information storage medium 201, the selector unit 423 operates according to the instruction of the STB control unit 404. The stream data including only the packet is transferred to the IEEE 1394 through the data transfer interface unit 20.
By the transfer, the data is sent to the data transfer interface unit 414 of the optical disk device 415.

In the case where the user simply views and listens to the information (transport packet) of the specific program selected by the reception information selector 423 without recording, the STB controller 404
The selector 423 sends stream data including only transport packets of a specific program to the multiplexed information separator 425 of the decoder 402 in accordance with the instruction.

On the other hand, when a program recorded on the information storage medium 201 is reproduced, stream data sent from the optical disk device 415 to the STB device 416 via the IEEE 1394 serial bus is supplied to the decoder unit 423 via the selector unit 423. The multiplexing information is sent to the multiplexing information separation unit 425 of the unit 402.

[0360] The multiplexed information separating section 425 is
Various packets (video packets, audio packets, sub-picture packets) included in the stream data sent from the storage device 23 are classified on the internal memory unit 426 by the ID of each packet. Then, the divided packets are distributed to corresponding decoding units (video decoding unit 428, sub-picture decoding unit 429, and audio decoding unit 430).

The video decoder 428 decodes the (MPEG-encoded) video packet sent from the multiplex information separator 425 to generate moving image data. At this time, a reduced image (thumbnail picture) representing the recorded content from the I picture in the MPEG video data
Video decoding unit 4 in order to have a function of generating
28 has a built-in representative image (thumbnail) generation unit 439.

The moving picture decoded by the video decoding section 428 (and / or the representative picture generated by the generating section 439), the sub-picture decoded by the sub-picture decoding section 429 (information on subtitles, menus, etc.) The audio decoded by the decoding unit 430 is supplied to the video mixing unit 405 via the video processor unit 438.
Sent to

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

The digital video from the video mixing section 405 is transmitted to the personal computer 435 via signal lines such as the I / F section 434 and IEEE 194.
Is taken in as appropriate.

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

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

[0367] Instructions and the like (operation control of each internal configuration of the STB device 416) by the STB control unit 404 described above are executed by a control program stored in the program memory unit 404a. At that time, the work memory unit 407 is appropriately used in the control process by the STB control unit 404.

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

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

Looking at the device configuration in FIG. 19 by function, ST
In the B device 416, a “reception time management unit”, a “stream data content analysis unit”, and a “stream data transfer unit”
And a "time-related information generation unit".

Here, the “reception time management section” includes a demodulator (demodulation section) 422, a reception information selector section 423,
It is composed of a multiplexed information separation unit 425, an STB control unit 404, and the like. This “reception time management unit” includes a satellite antenna 42
In step 1, a digital TV broadcast is received, and the reception time of each transport packet in the received broadcast information is recorded.

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

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

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

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

In the NTSC system, which is one of the TV display systems, 30 screens / pictures (frames) are displayed on a TV monitor screen as video signals per second. In a normal TV, an interlaced system is used, so that every other scanning line of one screen is first scanned and displayed on every other screen, and then every other shifted image is scanned every other line. In this way, a single screen (picture) is displayed by filling the space between the previous screens. The image displayed every other line is called a field.

In the NTSC system, 30 frames per second / 6
0 field is displayed. This NTSC system is a display system mainly used in Japan and the United States. In contrast, the PAL system, which is mainly used in Europe,
The display is performed at 25 frames / 50 fields per second.

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

Display time (reproduction time) of screen / picture 1
(B) “PTS (presentation time stamp;
Or reproduction time stamp) ".

The PTS may be at 27 MHz and / or 90
It is possible to use a method of expressing the display time by a counter value that always increments (counter value increases by 1) using a kHz reference clock. For example, 27
The value of the counter when each screen / picture (frame) is indicated by a counter that increments with a reference clock of MHz (or 90 kHz) is used as the value of PTS.

[0381] In the received signal information of the digital TV, the PTS value of each picture includes the picture header information 41 (Fig. 1).
(J)).

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

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

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

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

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

As illustrated in FIG. 20B, the time relation table 2 stores each PTS value (PTS No. 1, PTS No.
No. 2, PTSNo. 3,...), The corresponding data transfer time information (I picture transfer start time 4), data transfer time information (I picture transfer end time 5), and the total number of packets 10 from the head of the cell to the target I picture are described. Have been.

For example, PTS No. 1, the time stamp (ATS) # 1 of the row of the data transfer time information (I picture transfer start time 4) is shown in FIG.
(C) Top packet (AP) of I picture a information 7
The time stamp (ATS) # 2 of the row of the data transfer time information (I picture transfer end time 5) corresponds to the time stamp (ATS) # 1 of # 1, and the I picture a in FIG.
It corresponds to the time stamp (ATS) # 2 of the end packet (AP) # 2 of the information 7. Here, I picture a
Is the first picture, so PTSNo. The total number of packets 10 for one I picture a is “1” as shown in FIG.

Similarly, PTS No. 2, the time stamp (ATS) # 3 of the row of the data transfer time information (I picture transfer start time 4) is shown in FIG.
(C) Top packet (AP) of I picture i information 8
The time stamp (ATS) # 4 of the row of the data transfer time information (I picture transfer end time 5) corresponds to the time stamp (ATS) # 3 of the I picture i of FIG.
This corresponds to the time stamp (ATS) # 4 of the end packet (AP) # 4 of the information 8. Here, I picture i
Is 85100 frames after the first I picture a, so that the PTS No. The total number of packets 10 for the I picture i of 2 is “85101” as shown in FIG.
Becomes PTSNo. The same applies to the third and subsequent steps.

The time relation table 2 as shown in FIG. 20 (b) is stored in the stream data (FIG. 1 (a), FIG. 20 (c)).
Other STREAM. VRO 106) is recorded in an area where the management information (SFIT in FIG. 15) is recorded, and by using this time relation table, the user can specify the screen position in picture units.
There is a significant feature of the present invention.

Here, the time relation table 2 shown in FIG.
The corresponding relationship with the reproduction time stamp list PTSL shown in FIG.

Assuming that the time stamp shown in FIG. 1 (g) and others is ATS, the value of PTS included in the reproduction time stamp list PTSL of FIG. 15 and the ATS have the following relationship: (1) ) A cell (stream cell) refers to a part of a recorded bit stream; (2) an AU (usually an I picture) is a continuous part of a recorded bit stream (AU is one of the cells) (3) which SOBU contains the AU (I picture corresponding to a part of the cell) is indicated by the access unit start map AUSM in FIG. 15 (see FIG. 16); (4) The value of the PTS is the playback time (display time; or presentation time PTM) of the corresponding AU (AU
(5) The cell start APAT (SC_S_APAT) is the arrival time of the transport packet or application packet AP of the corresponding cell (SC_S_APAT).
(6) The transport packet or the application packet AP is accompanied by a time stamp ATS at the beginning of the transport packet or the application packet AP (see FIGS. 22 and 29 (g)); (7) The value of PTS is included in PTSL (see FIG. 15); (8) From the above (3) to (7), P
The value of TS corresponds to ATS through mediation of AUSM, SC_S_APAT, and the like.

Therefore, the reproduction time stamp list PTS
L is the start time (SC_S_AP) of the AU (I picture)
AT) and a “time relation table (FIG. 20B)” including information (PTS value) indicating the relation (relation regarding the reproduction time) between the time stamp ATS of the packet included in the bit stream.

Alternatively, PTSL (time relation table)
Can also be said to be information indicating the correspondence between the value of the PTS and the ATS.

By the way, in order to display a B picture or a P picture, it is necessary to always start by displaying (decoding) an I picture. For this reason, FIG.
The time relation table 2 shown in FIG. 2 shows a list of display time information corresponding to the time stamp at the I picture position.

[0396] Here, "PTS" is used as display time information.
Information (PTS value) "," the number of difference fields from the specific reference screen (picture) "," year / month / day / time information ", etc. can be used.

Note that difference information between I pictures (for example, information on the number of fields inserted between I pictures) is used as display time information instead of displaying an absolute value as shown in FIG. 20B. It is also possible. (The time relationship table using the number of fields will be described later with reference to FIG. 28.) In FIG. 20B, “PTS information” is used as display time information, but various inventions are possible. In the embodiment, the present invention is not limited to this method. Instead, “the number of difference fields from the specific reference screen (picture)” or “year / month / day / time information” can be used.

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

For this reason, fast forward playback (fast forward FF) or fast reverse playback (fast reverse F)
When performing special reproduction such as R, “time stamp (ATS) # 1 to # 2” and “time stamp (A
TS) # 3 to # 4, "," time stamp (AT
S) By specifying the transport packet position (or application packet position) of the I picture to be reproduced, such as "from # 5 to # 6", the I picture information (or access unit AU information) is read from the information storage medium 201. It is possible to reproduce, decode, and display only.

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

[0401] Specifically, as shown in FIG.
The display start picture of the original cell is B picture f, and the PTS value at that time is PTS No. 5 is assumed. The display time of the I picture a immediately before that is set to PTSNo. Assuming that the value of the PTS offset 9 is “PTS No. 5 −
PTSNo. 1 ”.

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

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

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

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

The stream data (STR) shown in FIG.
EAM. VRO) 106 is the information storage medium 2 shown in FIG.
01, the content (SOB or SOBU) of the stream data 106 is stored in a data area (STREAM.V) of the medium 201 in a predetermined data recording unit (transport packet or application packet).
RO / SR_TRANS. SRO). At this time, the management information (STR
I) is also the management area (STREAM.IFO) of the medium 201.
/ SR_MANGR. IFO).

[0407] The management information (STRI) includes first management information (ATS corresponding to the I picture transfer start time; AUSM) used for accessing the stream data 106 (access to the I picture information or the access unit AU). ) And the first management information (AUSM), which is different from the first management information (AUSM), and is used for accessing the stream data.
S; or SC_S_APAT) is recorded as third management information (time relationship table; or PTSL).

Here, the stream data 106 is the MPE
A bit stream compressed based on the G standard, and the second management information includes a playback time (PT
S).

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

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

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

[0412] When a time stamp value is designated as the reproduction start position by the STB device 416 in FIG.
The information for calculating the stream block (SOBU) corresponding to the specified time stamp value is shown in FIG.
18 (or the time map information MAPL in FIG. 15 or the time map information in FIG. 18).

[0413] In the example of FIG.
STREAM.52 is a management information recording area for stream data. It is recorded as a part of the stream object information (SOBI) 242 in the IFO 105. Also in the example of FIG. 15, the time map information MAPL is S
Recorded as part of OBI.

[0414] The time map information 252 shown in FIG.
Only the time stamp difference time information for each stream block is recorded therein. In this case, the value of the time difference 263, 265 of each stream block in the time map information 252 is sequentially added for each stream object information (SOBI) 242, 243. And
It is necessary to compare whether the successively added value has reached the time stamp time designated by the STB device 416 side. Based on the comparison result, the stream object (SO
It is determined which stream block (SOBU) in B) matches the time stamp value included in the stream block.

[0415] As shown in Fig. 21C, the boundary position of each piece of picture information 6010 to 6030 does not always coincide with the boundary position of a stream block (SOBU).

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

That is, from the time relation table 2 (internal configuration is the same as in FIG. 20B) in FIG. 21B, the PTS No. 2 and I
It is necessary to start reproduction from a stream block (SOBU) #A head position including the head transport packet # 2 in which the picture i information 6010 is recorded.

[0418] However, a stream block (SOBU)
Until the reproduction proceeds from the #A start position to the position of the desired P picture o, the image information during that time (from picture i to picture n in FIG. 21A) is not output to the external monitor (TV).

[0419] Fig. 22 shows the relationship between the video information compression method in MPEG and the transport packet, and the MPE.
FIG. 3 is a diagram illustrating a relationship between a transport packet in G and an application packet in a streamer.

[0420] As shown in Fig. 22, a signal compression method called MPEG2 is employed for broadcast signal information in digital TV. In the signal compression method by MPEG, TV
Each screen (picture) for display includes an I picture 551 containing no time difference information and a B picture 55 containing time difference information.
3, 554 and a P picture 552.

[0421] An I picture exists alone without being affected by previous and subsequent screen (picture) information, and after DCT transforming one screen (picture), quantized information becomes I picture compression information 561. It is recorded as I picture information 31. In the P picture 552, only the difference information 562 for the I picture 551 is recorded as the P picture information 32, and the B pictures 553 and 554 are the I pictures 55
Difference information between 1 and P picture 552 is recorded as B picture information 33 and 34.

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

When the transport packet shown in FIG. 22 is recorded on the streamer (optical disk device 415 shown in FIG. 19), the contents of the transport packet are transferred to a packet (application packet) with a time stamp called an application time stamp (ATS). Can be replaced.

Then, a group of application packets with ATS (usually around 10 packets) is
It is stored in the application packet area in the S packet.

[0425] The stream PES packet added with a pack header forms one stream pack.

A stream PES packet includes 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 above-described ATS-attached application packet group. Is composed.

FIG. 23 shows the contents of digital broadcasting and I
FIG. 3 is a diagram illustrating a correspondence relationship between a video data transfer form in EEE1394 and a stream pack in a streamer.

[0428] In digital broadcasting, video information compressed according to the MPEG2 standard is transferred in transport packets. In this transport packet,
As shown in FIG. 23 (b), it is composed of a transport packet header 511 and a payload 512 in which a data body of recording information is recorded.

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

[0430] The 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 is recorded, a flag of “1” is set in the random access indicator 503 in FIG. Also,
In the first transport packet of each of the B and P picture information, a flag of “1” is set in the payload unit start indicator 501 in FIG.

[0431] These random access indicators 5
03 and payload unit start indicator 501
The information of the I picture mapping table (641 in FIG. 9 (e)) and the information of the B and P picture start position mapping tables (642 in FIG. 9 (e)) are created by using the information of FIG.

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

In digital broadcasting, video information and audio information are transferred in different transport packets. And the distinction of each information is shown in FIG.
3 (a) is identified by the packet ID (PID) 502. Using the information of the PID 502, a video packet mapping table (643 in FIG. 9E) and an audio packet mapping table (644 in FIG. 9E)
Is created.

[0434] As shown in Fig. 23 (c), in digital broadcasting, a plurality of programs (program 1 to program 3 in this example) are packetized and transmitted to one transponder in a time-division manner. .

For example, the transport packet header 511 and the payload (recording information) 5 shown in FIG.
Twelve pieces of information are transferred by transport packets b · 522 and e · 525 of program 2 shown in FIG.

When the user wants to record the second program shown in FIG. 23C on the information storage medium 201, for example, the reception information selector 4 in the STB device 416 shown in FIG.
23, transport packets b and e of program 2
Only those are extracted.

At this time, the STB device 416
As shown in (d), each transport packet b5
22 and the time information when e525 was received
31 and 532 are added.

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

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

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

Data areas 21, 22, and 23 (FIG. 1)
(F)) is sequentially packed with a plurality of time stamps and transport packets (FIG. 1 (g)), but one transport packet (packet d in FIG. 1 (g); program in FIG. 23 (d)) The packet b of No. 2 includes a plurality of sectors (No. 0 and No. 1 in FIG. 1E);
(F) and (g) are recorded over partial packets.
Here, there is one of the features of the present invention.

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

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

As described above, one sector size is 2048.
Approximately 10 transport packets for digital broadcasting can be recorded in one data area 21, 22, 23 (FIG. 1 (f)) even if various header sizes are subtracted.

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.

[0446] In addition to recording a plurality of transport packets in one data area 21, 22, 23 (Fig. 1 (f)) as in the case of digital broadcasting, a large packet size such as a long packet is used. In order to be able to record even in the case of a packet, a data structure (1
One packet is recorded so as to continuously straddle a plurality of data areas 21, 22, and 23 by using the feature that packet data can be straddled over a plurality of packets.

[0447] In this way, all packets, such as transport packets for digital broadcasting and long packets for digital communication, can be recorded in a stream block without depending on the packet size.

Although a normal packet has a time stamp, the time stamp can be omitted from a partial packet as shown in FIG.

In this manner, the partial packet divided at the boundary between two adjacent stream packs (FIG. 23 (h)) (if the packet size is 188 bytes, the size of the partial packet is 1 to 187 bytes; Less than 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 one time stamp).

The position of the time stamp immediately after the leading packet in FIG. 23 (g) is the first access point 625 in FIG. 10 (b) or FIG. 10 (c).
Can be specified by FIRST_AP_OFFSET.

In the optical disk device 415 (streamer) shown in FIG. 19, the set of the time stamp and the transport packet (FIGS. 23F and 23G) is recorded on the information storage medium 201 as it is.

[0452] Fig. 24 is a flowchart for explaining a stream data recording procedure according to an embodiment of the present invention. The processing at the time of recording the stream data will be described with reference to FIG. This processing is performed in ST ST shown in FIG.
It can be executed by a processing program stored in the program memory unit 404a of the B control unit 404.

As shown in FIG. 23C, a plurality of pieces of program information are time-division multiplexed in one transponder.

[0454] In the reception information selector 423 of FIG.
A transport packet of only a specific program is extracted from the packet sequence of the time-division multiplexed plural program information (step S01).

[0455] "Reception time management unit (demodulation unit 42 in FIG. 19)
2. Received information selector 423, multiplexed information separator 42
5, STB control unit 404 etc.)), the necessary program information is temporarily stored in the memory unit 426 of the multiplexed information separation unit 425 (step S02).

At the same time, the reception time of each transport packet is measured, and the measured value is shown in FIG.
As shown in (1), a time stamp (ATS) is added to each transport packet (or application packet). The time stamp information thus added is recorded in the memory unit 426 (Step S
03).

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

More specifically, picture boundary positions are extracted from a transport packet (application packet) sequence, and PTS information (well, corresponding field number information) is extracted from picture header information 41 for each packet. (Step S04).

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

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

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

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

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

[0464] Thus, the optical disk device 415
The stream data temporarily stored in the memory unit 426 is
It is recorded on the information storage medium 201 (step S0
7).

Until the transfer of the stream data to the optical disk device 415 is completed (No in step S08), the processing in steps S06 to S07 is repeated.

[0466] When the stream data transfer to the optical disk device 415 has been completed and the recording process has been completed (step S0)
8 Yes), the work memory unit 40 of the STB control unit 404
The information of the time relation table 2 (or the reproduction time stamp list PTSL) temporarily recorded in the storage device 7 is transferred to the optical disk device 415 (step S10).

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

[0468] In the process of step S11, the recording time of the stream object, which is the content of the recorded stream data (SOB_REC_T in FIG. 7 (i)).
M) to the management information recording area (STREAM.IFO) 1
05 (TM_ZONE) 6240 (FIG. 7H).

[0469] By the way, when recording stream data, there is a case where encrypted stream data is recorded for the purpose of protecting the copyright of the content provider. When encryption is performed in this manner, all transport packets are encrypted, and the time stamp transfer process between the STB device 416 and the optical disk device 415 is prohibited. In this case, when recording the (encrypted) stream data on the information storage medium 201, the optical disk device 415 needs to independently add a time stamp.

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

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

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

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

Thus, the time relation table (or PT
After the creation of the SL), or when the time relation table (or PTSL) is already in the work memory 407 of the STB control unit 404 (step S50: YES), the STB device 416 sends the encrypted data to the optical disc device 415 (encrypted). ) The stream data is transferred, and the stream data is recorded on the information storage medium 201 (step S51).

[0475] Until the recording of the (encrypted) stream data is completed (No in step S53), the processing in step S51 is continued. This stream data recording step S51 includes steps S01 to S03 in FIG.
The processing content is the same as that of S06.

[0476] The processing in step S52 may be executed in parallel with the processing in step S51.

When the recording of the (encrypted) stream data is completed (YES in step S53), ST
A reference clock synchronization process is performed between the B device 416 and the optical disk device 415 (step S54).

The reference clock synchronization process can be performed, for example, as follows.

[0479] That is, each time a specific number (for example, 10,000 or 100,000) of transport packets (application packets) is transmitted / received at the time of stream data transfer, the transmission / reception time is determined by the STB device 416 and the optical disk device 415. They are recorded in the work memory unit 407 and the temporary storage unit 411, respectively.

Thereafter, a transmission time list is sent each time a specific number of transport packets (application packets) are transmitted from the STB device 416 to the optical disk device 415. Then, the optical disc device 415 compares the sent list with the list created in advance by the optical disc device 415, thereby calculating a reference clock synchronization shift amount between the two.

After that, the time relationship table 2 (or PTS) is sent from the STB device 416 to the optical disk device 415.
L) is transferred (step S55).

The time relation table 2 (or PTSL) transferred from the STB device 416 to the optical disk device 415 in this manner is based on the information on the reference clock synchronization deviation calculated in the reference clock synchronization process in step S54.
It is corrected (step S56).

The time relation table 2 (or PTSL) corrected by the reference clock synchronization deviation amount in this manner is stored in the management information area of the information storage medium 201 (STRE of FIG. 3E).
AM. This is recorded in the IFO 105; or SFIT in FIG. 15 (step S57).

With the above, recording / reproduction of stream data (in an encrypted state) becomes possible.

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

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

In this case, as information in the time map information 252, instead of the data structure shown in FIG. 3 (i), as shown in FIG. 11, the number of transport packets (or Application packet number AP_Ns) 633 is provided.

When the total number of transport packets (the total number of application packets) is designated by the STB unit 416 to access a predetermined screen (picture), the optical disk unit 415 sets the first stream block shown in FIG. , The transport packet (application packet) number 633 is sequentially added, and the stream block (or SOBU) at the time when the addition result reaches the specified value is accessed.

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

The user can select the desired reproduction start time and / or
Or, set the playback end time to "Difference time (hours, minutes, seconds) based on the display start time of the specified original cell"
Can be specified in the form The specified reproduction start time and reproduction end time, for example, are designated by ST
The STB control unit 404 in the B device 416 receives (step S21).

The STB control unit 404 stores the received playback start time and playback end time information in the
The difference PTS value from the display start time of the original cell is calculated by converting into the clock count value of MHz and / or 90 kHz.

[0492] The STB control unit 404
15 to read the time relation table 2 (or PTSL) recorded in the stream data management information recording area (STREAM.IFO 105) and temporarily record it in the work memory unit 407 (step S2).
2).

The STB control section 404 controls the optical disk device 415 to read the information of the time map information 252 (or MAPL) recorded in the stream data management information recording area (STREAM.IFO 105), 407 is temporarily recorded (step S23).

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

Further, the value of the PTS offset 9 shown in FIGS. 3 (h) and 20 (a) is read, and (a) the value (PTS offset 9) and (b) immediately before the display start time of the original cell PTS value (PTS No. 1) at the I picture-a position (in the case where the display start picture f of the original cell is immediately after the I picture a as shown in FIG. 20A), and (c) check in step S24. The PTS values of the reproduction start time and the reproduction end time specified by the user are calculated by adding the difference PTS values (PTS No. 5-PTS No. 1) (step S25).

Next, the PTS value of the I picture i and the value of the time stamp # 2 immediately before the reproduction start position specified by the user are checked using the time relation table 2 (step S2).
6) Notify the optical disk device 415.

[0497] The optical disc apparatus converts the data of the time map information 252 (Fig. 3 (i)) shown in Fig. 3 (h) into a stream including the head position of the I picture i information 6010 (Fig. 21 (c)). The value of the first time stamp (ATS) # 1 of the block (SOBU) #A is checked, and the location (address) of the first sector # α to be accessed is checked.
Is determined (step S27).

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

[0499] Next, the STB control unit 404 of FIG. 19 sends to the decoder unit 402 a PTS value (PT in FIG. 21A) indicating the display start time of the information whose reproduction has been started in step S28.
SNo. 6) is notified (step S29).

With this notification, the optical disk device 415
Transfers the information started to be reproduced in step S28 to the STB device 416 side (step S30).

Subsequently, the STB control unit 404 sends the picture identification information 52 from the memory 426 in the decoder unit 402.
(FIG. 1 (k)), and discards (or ignores) the data preceding the input I picture (a part of the information transferred from the optical disk device 415) (step S).
31).

Next, the video decoding unit 428 shown in FIG.
Is the I picture input in step S31 (FIG. 21).
In (a), decoding is started from the head position of the I picture i), and display (video output) is started from the PTS value (PTS No. 6 in FIG. 21A) specified by the notification in step S29. (Step S32).

Thereafter, the same processing as in steps S24 to S28 is repeated, and the information storage medium 20 corresponding to the reproduction end time is repeated.
Then, the address above the first address is checked, and the reproduction is continued up to the end address corresponding to the reproduction end time (step S33).

At the stage where the above-described series of reproduction is completed, FIG.
The reproduction end position information 6110 shown in (g) is used as resume information in the management information recording area (ST shown in FIG. 7E).
REAM. Video manager information 2 in IFO 105)
31 (FIG. 7F).

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

Although the time information 6230 is recorded as a time stamp value, a PTS value (or the total number of fields from the cell reproduction start position) may be recorded as the time information 6230.

When the reproduction end position information is to be reproduced again from the position of the (resume) information 6110, the reproduction start position can be obtained by the processing of FIG. 27 described later.

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

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

[0510] Fast forward playback (fast forward FF)
Alternatively, when performing special reproduction such as fast reverse reproduction (first reverse FR), only I picture information recorded on the information storage medium 201 is extracted and reproduced, and decoded and displayed.

In this case, STC section 424 (FIG. 19) and D
The TS unit 54 sets the "special playback mode" for the decoder unit 402 so as to synchronize with the TS information 54 (FIG. 1 (k)) and decode in the free mode (step S4).
1).

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

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

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

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

For example, at the time of special reproduction, FIG.
Only the I picture information 6010 to 6050 of FIG. 8B is decoded and displayed. This I picture information 6010
The positions of 〜 to 6050 can be obtained by using the information of the time relation table 2 and the time map information 252.

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

Next, in the decoder unit 402 of FIG. 19, the picture identification information 52 (FIG. 1 (k)) in the data transferred to the memory unit 426 of the multiplex information separation unit 425 is read, and this information 52 is read. Data other than the I picture is discarded based on the data (step S47).

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

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

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

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

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

[0524] In Fig. 20B, "PTS information" is used as display time information. However, in various possible embodiments of the present invention, the present invention is not limited to this method. The "number of difference fields from the screen (picture)" or "year / month / day / time information" can be used. An example of this case is the time relation table 6 in FIG.

[0525] As shown in Fig. 28 (b), each group of pictures (GOP) indicates a group of pictures starting from a certain I picture position and immediately preceding the next I picture. In the data structure of the time relation table 6 shown in FIG.
The number of display fields for each is recorded.

In the time relationship table 6, the number of occupied stream blocks (SOBU) for each GOP is also described. Thus, without using the time map information 252 shown in FIG. 3 (h), the given display time information is directly sent to the stream block (SOBU) in which the head position of the I picture information is recorded. Will be accessible.

GOP # 2 and GOP in the example of FIG.
At the boundary position of OP # 3, the switching position of the GOP matches the switching position of the stream block (SOBU). Thus, the boundary of the adjacent GOP and the adjacent SOBU
When the GOP end matching flag in the time relation table 6 shown in FIG.
1 ". By doing so, the stream block position (SOB
(U position) identification accuracy is improved.

Also, at the time of special reproduction such as FF or FR described above, since the rear end position of I picture information is used, each GOP is stored in the time relation table 6 of FIG.
Is also provided.

FIG. 29 is a diagram showing a packet (A) in stream data (SOBU) according to an embodiment of the present invention.
It is a figure explaining how P) is reproduced.

FIG. 29 exemplifies a case where the stream blocks ## 1, # 2,... Of FIG. 1C are all composed of SOBUs # 1, # 2,. I have.

[0531] Fig. 29 (f) shows the start sector No. of SOBU # 1. 0 (FIG. 29 (e)) and the SOBU
# 1 of the last sector of SOBU # 2 adjacent to # 1. 63
It shows the data structure of FIG. Although not shown, the sector No. 0 to sector No. 62 has a similar concept.

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

Now, it is assumed that the picture to be reproduced (the picture specified by the user at the reproduction time) is located in the middle of SOBU # 2 (in FIG. 16, for example, the position indicated by AU # 1). The picture specified by the user for the playback time is the cell start application packet arrival time SC_S_A
Corresponds to PAT.

In this case, the disk drive (not shown) included in the recording / reproducing unit 409 of FIG.
Cannot directly access the middle of SOBU # 1
And access the boundary position between SOBU # 2 and SOBU # 2. And
The stream data (STREAM.VR) shown in FIG.
O) The reproduction of 106 starts from the boundary position between SOBU # 1 and SOBU # 2.

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

The application packet existing between the boundary position between SOBU # 1 and SOBU # 2 and the reproduction start position (the position corresponding to SC_S_APAT) is
Decoding is performed, but playback output is not performed (not displayed on the screen). This corresponds to the process in step S31 in FIG.

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

Here, the relationship between the time relation table and the reproduction time stamp list PTSL shown in FIG. 15 will be summarized again.

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

Therefore, the reproduction time stamp list PTS
L is the start time (SC_S_AP) of the AU (I picture)
FIG. 20B is a “time relation table (FIG. 20B)” including information (PTS value) indicating the relation (relation regarding the reproduction time) between the time stamp ATS of the packet included in the bit stream and the time stamp ATS.

Alternatively, PTSL (time relation table)
Can also be said to be information indicating the correspondence between the value of the PTS and the ATS.

Lastly, the meaning of some terms used in the description of each embodiment will be summarized: * A stream object (SOB) indicates data of a recorded bit stream. SR_TRANS. SR
Up to 999 SOBs can be recorded in the O file.

* Stream Object Unit (SO
BU) is a basic unit organized in SOB. That is, each SOB is composed of a SOBU chain. In particular, after editing, the SOBU at the beginning and / or end of the SOB may include data that does not belong to the effective part of the SOB.

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

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

* Access unit start map (AUS
M) indicates which SOBU of the corresponding SOB contains AU.

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

* Application time stamp (AT
S) is arranged before each AP and consists of 32 bits (4 bytes). The ATS is composed of a basic part of 90 kHz and an extended part of 27 MHz.

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

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

* Stream cell entry point information (SC_EPI) is used as a tool for skipping a part of recording,
C).

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

* End object packet arrival time of stream object (SOB_E_APAT)
Indicates the arrival time of the last AP belonging to the relevant SOB.

* The start application packet arrival time of the stream cell (SC_S_APAT) is
The arrival time of the first AP belonging to

* The end application packet arrival time of the stream cell (SC_E_APAT) is
The arrival time of the last AP belonging to

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

* Playlist (PL) is a list of program portions that allow the user to arbitrarily define a playback sequence. PL is described as a user-defined PGC.

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

* The program chain (PGC) is a high-level conceptual unit. For original PGC, PGC
Indicates a chain of programs corresponding to the program set. On the other hand, in the case of a user-defined PGC, the PGC corresponds to a play list and indicates a partial chain of a program.

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

* Program chain number (PGCN)
Is a serial number (1 to 9) assigned to the user-defined PGC.
9).

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

* The program set indicates the entire recorded contents of the disk (recording medium) composed of all programs. If no edits have been made to any of the programs that change the playback order relative to the original record,
When reproducing the program set, the same reproduction order as the recording order of the program is used.

[0564] * Real-time recording means that, when the buffer memory size is limited, as long as any stream data coded at the limited transfer rate is transferred at the limited transfer rate, the buffer memory is This refers to recording in which the stream data can be recorded on a disk (recording medium) without overflow.

The effects of each embodiment of the present invention are summarized as follows: Time stamp data (ATS) recorded in the stream data and display time information (PTS) for the user
Or, information (time relationship table or PTSL) indicating the relationship with the management information (SFI)
By providing a part of T), reproduction / screen display can be started with high accuracy from the display time designated by the user.

[0566] 2. At the time of editing, the user specifies a partial erasure range of recorded stream data or a specified range of rearrangement by display time on the monitor TV.

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

[0568] 3. Since the stream data has a time relation table (or PTSL) as described in “1.” above, either one of the time stamp data (ATS) and the display time information (PTS) is stored in the reproduction end position. The reproduction start position at the time of restarting the streamer (resume reproduction start position) can be accurately set only by describing the information (resume information).

[0569] 4. Playback end position information (resume information)
Is recorded as time stamp data (ATS), when accessing a specific position on the information storage medium, the address to be accessed can be quickly known using the time map information 252.

[0570] 5. It is necessary to start reproduction of MPEG compressed data from an I picture. Time stamp data (ATS) and display time information (PT) at the start position of each I picture (or the start position of the access unit AU)
S or field information) to record the information (time relation table),
Access control to a picture (desired AU) can be performed at high speed using the time map information 252.

[0571] 6. By recording information (time relation table) indicating the relation between time stamp data (ATS) at each I picture start position (start position of each AU) and display time information (PTS or field information),
In combination with the time map information 252, a stream block (or SOB) including an I picture (AU)
U) The location address is known. Therefore, it is possible to perform special reproduction processing such as first forward FF or first reverse FR for reproducing / displaying only I pictures.

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

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

[0574]

As described above, according to the present invention,
It is possible to improve stream information recording processing.

[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 information medium (DV) according to an embodiment of the present invention;
FIG. 4 is a view for explaining a recorded data structure (in particular, a structure of management information) on a D recording / reproducing disk.

FIG. 4 shows a stream object (S) according to the present invention.
FIG. 2 is a diagram for explaining a relationship between an OB), a cell, a program chain (PGC), and the like.

FIG. 5 is a diagram for explaining the contents of a stream block size, a stream block time difference, and the like 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 information medium (D) according to another embodiment of the present invention.
FIG. 4 is a view for explaining a recording data structure on a VD recording / reproducing disc (in particular, a structure of reproduction end position information / resume information, VMGI management information / recording time information, etc.).

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

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

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

FIG. 11 is an exemplary view for explaining another example of time map information according to the embodiment of the present invention;

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

FIG. 13 shows streamer management information (STREA in FIG. 2).
M. IFO or SR_MANGR. FIG. 3 is a diagram for explaining an internal data structure of an IFO.

14 shows PGC information (ORG_PGCI / UD in FIG. 3)
FIG. 14 is a view for explaining the internal data structure of _PGCIT or PGCI # i) of FIG. 13;

FIG. 15 shows a stream file information table (SFI).
The figure explaining the internal data structure of T).

FIG. 16 is a diagram exemplifying a correspondence relationship between an access unit start map (AUSM) and a stream object unit (SOBU).

FIG. 17 is a diagram exemplifying a correspondence relationship between an access unit start map (AUSM) and an access unit end map (AUEM) and a stream object unit (SOBU).

FIG. 18: Original PGC or user-defined PGC
And the SOBU corresponding to these cells
FIG. 7 is a diagram illustrating how the items are related by time map information.

FIG. 19 is a diagram illustrating a stream data recording / reproducing system (optical disc apparatus / streamer,
FIG. 2 illustrates a configuration of an STB device.

FIG. 20 is a view for explaining a time relation table showing a relation between a display time and a data transfer time in one embodiment of the present invention.

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

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

FIG. 23 shows digital broadcasting contents and IEEE139.
FIG. 4 is a view for explaining a correspondence relationship between a video data transfer mode in FIG. 4 and a stream pack in a streamer.

FIG. 24 is a flowchart illustrating a recording procedure of stream data according to an embodiment of the present invention.

FIG. 25 is a flowchart illustrating a recording procedure of encrypted stream data according to the embodiment of the present invention.

FIG. 26 is a flowchart illustrating a procedure for reproducing stream data according to an embodiment of the present invention;

FIG. 27 is a flowchart for explaining a procedure of trick play of stream data according to the embodiment of the present invention.

FIG. 28 is a diagram illustrating a time relation table indicating a relation between a display time and a data transfer time in another embodiment of the present invention.

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

[Explanation of symbols]

201 ... information medium, 415 ... optical disk device, 416 ...
STB equipment.

──────────────────────────────────────────────────の Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) H04N 5/92 H04N 5/92 H (72) Inventor Kazuyuki Uyama 2-199, Midori-cho, Kumagaya-shi, Saitama LM301 No. (72) Inventor Yuji Ito 5-22-1-302 Chuo, Ota-ku, Tokyo (72) Inventor Shinichi Kikuchi 4-23-1 Yokodai, Isogo-ku, Yokohama-shi, Kanagawa Prefecture Shock Villa Yoko V-202 F-term ( Reference) 5C052 AA04 AB03 AB04 AB09 CC06 CC11 DD04 5C053 FA20 FA25 GB06 GB08 GB37 JA22 LA05 5D044 AB05 AB07 BC06 CC04 DE02 DE03 DE39 DE48 GK07 5D077 AA30 BB11 DC03 5D110 AA17 AA26 AA28 DA17 DB02 DE01

Claims (6)

[Claims] An information medium having a data area for storing MPEG-encoded stream data and a management area for storing management information related to the stream data, wherein the data area is an I picture having reproduction time stamp information. And the MPEG-encoded stream data is stored in units of data packets, and the management information includes the reproduction time stamp and the I
An information medium characterized by storing a time relation table relating to data transfer time information of a picture. 2. A method configured to record the stream data on the medium of claim 1. 3. The method according to claim 1, wherein the management information is read from the medium according to claim 1, and the recorded content of the data area is read based on the content of the read management information. 4. An apparatus using an information medium having a data area for recording MPEG-encoded bit stream data including I picture information and a management area, wherein the data area of the information medium includes
Means for recording encoded bit stream data; and means for recording a time relationship table relating to a reproduction time stamp and data transfer time information of the I picture in the management area of the information medium. Bit stream data recording device. 5. An apparatus using an information medium having a data area in which MPEG-encoded bit stream data including I picture information is recorded, and a management area in which a time relation table relating to the bit stream data is recorded. Means for setting a reproduction mode; means for reading the time relation table from the management area of the information medium; and setting of the information medium in the special reproduction mode based on the contents of the time relation table. Means for reproducing, from the data area, only the information of the I picture out of the MPEG-encoded bit stream data, a bit stream data reproducing apparatus. 6. An apparatus or system configured to record information or reproduce recorded information by using the medium according to claim 1.