JP2001169246A - Data recording method and data reproduction method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve a problem involved in a conventional data recording method and data reproduction method that complicated processing procedures has been required because it is required to transfer two files for stream data being part of an original scene and its management information if the stream data corresponding to a user scene defined by a user is copied or transferred to a network due to the absence of concept of nondestructive edit caused by e.g. one user scene consisting of one independent file despite of the necessity of reproduction management information for each user scene or due to the reproduction management information intensively recorded on a disk as a file separately from a file of stream data even when the nondestructive edit is preconditioned. SOLUTION: Information relating to a user scene is recorded in a header position of each data unit in stream data so as to manage reproduction information together with the stream data and even a data transfer destination can control a reproduction start and end from an optional frame position.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for recording and reproducing a moving image file, and more particularly to a method for recording reproduction management information when performing non-destructive editing.

[0002]

2. Description of the Related Art With the spread of multimedia in recent years, there has been an increasing demand for recording various multimedia data such as video, music, and still images on a recording medium. Among recording media, tape media such as video tapes and audio tapes have conventionally been the mainstream, but in recent years, recording on disk media such as hard disks and magneto-optical disks has been increasing. MDs for music, DVD Video for video, and the like are generally known as those using disk media, and are widely used because of their random access characteristics.

Here, a description will be given of a case where stream data obtained by multiplexing video data and audio data encoded by MPEG is recorded on a disc. For example, stream data recorded on a disc is managed as a file in units of management such as stop or pause from the start of recording. With the random accessibility of the disk, 1
It is not necessary that stream data corresponding to one file be continuously recorded on the disk. I mean
Even if a series of data managed by one file is recorded on the disk as divided data, by reading those divided data sequentially from the disk, the data is read to the next position on the disk where the next data is read at each dividing point. Although seeks and track jumps that move the head of the disk drive occur, the data read interruption time is negligible compared to tape media, so the same effect is obtained as if the corresponding data was read from the disk continuously. Can be

Hereinafter, in this embodiment, a series of stream data recorded from the start to the end or paused by the user is referred to as an original scene, and the stream data in which the user has selected an arbitrary portion of the original scene by an editing operation is referred to as a user. It is called a scene. Also, a management unit combining all original scenes is called an original program, and a management unit combining an arbitrary number of user scenes in an arbitrary order is called a user program.

[0005] The random accessibility of a disc is also effective in editing. A case in which stream data recorded on a disk medium is edited will be described.
When a video camera or the like is considered, not all the stream data of the captured original scene is necessarily desired to be viewed. For example, an unnecessary portion may be included at the beginning of the original scene. By performing an editing operation, it is possible to select a necessary arbitrary portion from the original scene and define it as a user scene. Using random accessibility, non-destructive editing is performed by sharing the stream data on the disc without copying or modifying the stream data of the original scene, which is the material data. Reproduction becomes possible based on the above positional information. As described above, a user scene defined by referring to stream data on a disc corresponding to an original scene is managed as a virtual file.

[0008] As shown in FIG. 24, an example in which stream data corresponding to three original scenes are recorded on a disk, and an arbitrary portion is selected in each original scene to define three user scenes will be described. I do. In this example, the stream data of the original scene on the disk is managed by associating the file names OS0001.MPG, OS0002.MPG, and OS0003.MPG with the recording positions on the disk by the logical file system.

On the other hand, user scenes are stored as virtual files US0001.MPG and US0002.MP by the logical file system.
G, US0003.MPG. The management information of the logical file system of the virtual file is a set of information for specifying the file of the referenced original scene and a start point and a length indicating a selected location on the disk of the stream data. Arbitrary portions of the original scene can be extracted from the virtual file pointer information and handled as a virtual file.

[0008] Since the management information of the file and the virtual file is of the logical file system hierarchy, the user can access the information via the device driver even though the original scene data is recorded on the disc. From the viewpoint of the system, the data corresponding to the user scene managed by the virtual file is treated as being recorded on the disk virtually separately. That is,
By passing an instruction to read the virtual file US00001.MPG from the disk to the device driver, the data at the selected location in the original scene constituting the user scene is automatically read.

By managing the original scene as a file and the user scene as a virtual file in this way, a computer connected via a network such as IEEE1394 can be used, for example, to give an edited user scene or a user program to another person. For example, it is possible to transfer only by Get or Put of a file which is a basic command of transfer. This is achieved by specifying a file name for specifying an original scene to be transferred or a virtual file name for specifying a user scene and performing transfer.

However, a problem may arise when managing an MPEG stream in the framework of a file or a virtual file. In MPEG technology, when compressing the amount of data, an intra-frame coded image (I picture) that is independently coded only with the data of the video frame, and an inter-frame forward direction that is coded based on the information of the forward frame Efficiently reduces data volume by using three types of image compression methods: predictive coded images (P pictures) and bidirectional predictive coded images (B pictures) that encode based on forward and backward frames are doing.

That is, when it is desired to reproduce a P picture or a B picture, it cannot be decoded without the data of the reference I picture or the P picture.
In order to solve such a problem, in MPEG, a GOP (Group of Pictu
res) is provided. This GOP structure is GO
In P, there must be at least one I picture. Therefore, if access is performed in units of a GOP structure, since the I picture which is a reference of each P picture and B picture included in the GOP is included, it is guaranteed that the target frame is decoded. .

As described above, when random access is performed for MPEG stream data, it is necessary to perform the random access in units corresponding to the GOP structure. In other words, the minimum management unit of stream data managed by files and virtual files is GO
This is a management unit corresponding to P, and the stream data constituting a file or a virtual file has a structure in which an integer number of management units of stream data corresponding to the GOP structure are collected.

If one GOP is composed of 15 frames of video data, the stream data managed by a file or virtual file is stream data of a unit of 15 frames. Is performed, this GOP unit is reproduced.

However, in general, a user scene to be reproduced by a user rarely starts from the beginning of a GOP, and there is a problem that unnecessary frames are also reproduced. Generally, as shown in FIG. 25, there is a method of recording user scene information as a header at the head of the stream data itself. In this case, the user scene as a result of editing by the user is not managed in a virtual file, but is managed in an independent real file for each user scene. In other words, independent stream data is recorded on the disk for each user scene as an editing result, and disk space is consumed more than when a part of a real file is used as a virtual file. This is not the non-destructive editing assumed by the present invention.

As shown in FIG. 26, on the premise of nondestructive editing, stream data recorded on a disc is managed in one real file, and details in the stream data are recorded on the disc as another real file. There is a method to manage with management information. In the example shown in the figure, two files, a real file in which playback information is stored, and a real file in which stream data is stored, and the file name and the data recording position on the disc are used as management information of the logical file system. File management information to be associated is recorded on the disc. Here, the reproduction information is information for specifying which part of the data managed in the file the stream data corresponding to each user scene is, and as described above, reading from the disc is
Since this is a unit corresponding to a GOP, it is information for specifying a frame at which playback is started and stopped.

[0016]

With respect to a user scene defined by nondestructive editing performed by referring to an arbitrary portion of an original scene, stream data on a corresponding disk is copied to another device or transferred to a network. Considering that such operations are performed, the method can be realized by the method described in the related art.

However, when copying or transferring a user scene to select and extract an arbitrary portion of the stream data on the disc recorded by the MPEG technology to another device or the like, the corresponding stream data is stored in the GOP as described above.
Needs to be performed for each management unit corresponding to. Therefore, if there is no management information indicating the reproduction range in units of frames at the transfer destination, it is only possible to perform reproduction in units of GOPs actually copied or transferred. In general, if only a simple video playback is performed at the transfer destination, it is sufficient to simply use the stream data. Various processing can be performed in addition to simple reproduction.

As described above, the reproduction management information is required for each user scene. In the conventional method, for example, one user scene is composed of one independent file and there is no concept of non-destructive editing (FIG. 25). ), Even when non-destructive editing is premised, necessary reproduction management information is intensively recorded on the disk as a file separate from the stream data (FIG. 26). Therefore, if stream data corresponding to a user scene defined by a user is copied or transferred over a network, it is necessary to transfer two files, that is, stream data that is a part of the original scene and its management information. The reason why stream data and management information are separated into two files at the transfer destination is that, for example, if the transfer destination is a PC and the user deletes the management information file by mistake, the playback information may be lost. Problem.

Therefore, when performing copying or network transfer, it is desirable to carry out the related data as one file as much as possible. But)
It is necessary to perform a process of extracting reproduction information relating to a target user scene from management information centrally managed as one file and adding it as header information of stream data to be copied or transferred. Therefore, when copying or transferring a user scene or the like over a network, there is a problem that pre-processing is required and the processing procedure becomes complicated.

Therefore, according to the present invention, by recording information on the user scene at the header position of each data unit in the stream data, the reproduction information can be managed together with the stream data. Start playback from any frame position,
It is possible to control the end, and to perform not only simple reproduction but also various processes.

[0021]

According to the first aspect of the present invention, a unit (one or more GOP data and corresponding audio data and auxiliary data (Unit Header)) on a recording medium is provided. VU / PRU) file (EU
S) is a data recording method in a recording / reproducing apparatus that records video data as a file and reads and writes video data in file units, and the auxiliary data (Unit Header) of a head unit (VU / PRU) of the file. The above problem is solved by recording reproduction information (indicating a reproduction start position and an end position) of the file.

According to the second aspect of the present invention, a unit (VU / PRU) composed of one or a plurality of GOP data, corresponding audio data, and auxiliary data (Unit Header) is recorded on a recording medium. A method for recording video data as a file (EUS), which is a set of data, and a data recording method in a recording / reproducing apparatus for reading and writing video data in file units, wherein all or some of the units in the recorded file As a virtual file (for example, Virtual Fi
le Descriptor, etc., and the above-mentioned problem is solved by recording the reproduction information (indicating the reproduction start position and the end position) of the file in the auxiliary data (Unit Header) of the head unit of the virtual file.

According to the third aspect of the present invention, video data is stored as a file (EUS) which is a set of units (VU / PRU) composed of one or more GOP data and corresponding audio data, and auxiliary data. Is a data reproducing method in a recording / reproducing apparatus for reading and writing video data in file units on a recording medium on which
The reproduction information (indicating the reproduction start position and the end position) recorded in the auxiliary data (Unit Header) of the head unit (VU / PRU) of the read file is read, and read based on the reproduction information. The above-mentioned problem is solved by controlling the reproduction of the selected file.

[0024]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of a file management method according to the present invention will be described in detail with reference to the drawings. In the present embodiment, it is assumed that a video camera using a portable disk as a recording device and the video data to be recorded on the disk is MPEG. Further, as for a disk device, the present embodiment can be applied as it is even if a stationary video deck or a recording medium is a hard disk or a semiconductor memory.

Hereinafter, in the description of the present embodiment, a file for managing original data on the disc corresponding to the original scene recorded on the disc is called a real file, and a user scene constituted by referring to the original data is referred to as a real file. The file to be managed is called a virtual file, and will be described separately.

The original scene from the start of recording to the stop or pause taken by the user is treated as a real file in the logical file system, and the stream of the original scene is copied on the disk without copying or modifying the original data. In a form of sharing data (so-called non-destructive editing), a user scene defined by selecting an arbitrary part of an original scene is managed by a virtual file of a logical file system. This is called a virtual file because any part of data already managed as a real file on the disk is shared.

FIG. 1 shows an example of a system configuration diagram of the present invention. The description will be made in conjunction with the flow of processing during recording and during reproduction. First, the recording will be described. Upon receiving a recording request from the user, the control unit 1 issues a control signal to each processing unit and controls the entire system. The video and audio inputs from the camera unit 2 are first encoded in the MPEG encoder 3. Each encoded data is MPEG
Video and audio are multiplexed in the system unit 4,
It will be shaped into a stream configuration such as the EG PES stream. This stream data is temporarily stored in the buffer memory 5. Then, the ECC signal processing unit 6 processes the stream data stored in the buffer memory 5.
Performs signal processing such as adding an ECC (Error Correction Code) code. The stream data on which signal processing such as ECC has been performed is formatted by modulation / demodulation / sector codec unit 7 in accordance with the modulation and sector structure in order to be recorded on disk 9, and servo control unit 8 controls disk 9. Will be recorded.

Next, the processing at the time of reproduction will be described. Upon receiving a reproduction request from the user, the control unit 1 issues a control signal to each processing unit and controls the entire system. When the target stream data is read from the disk 9 under the control of the servo control unit 8, the modulation / demodulation / sector codec unit 7
The demodulated stream data is stored in the buffer memory 5. The stream data stored in the buffer memory 5 is subjected to error correction by an ECC code or the like added at the time of recording by an ECC signal processing unit 6, and an extra code or the like is removed. When it comes to the stage of actual playback, the video and audio data multiplexed in the MPEG system unit 4 are separated, and this data is decoded in the MPEG decoder unit 3 and output to an output device (not shown) such as an actual monitor screen. Will be displayed.

Next, an example of the configuration of an MPEG stream handled in this embodiment will be described. In the stream configuration of FIG. 2, an EUS (Editable Unit Sequence) is composed of a plurality of EUs (Editable Units), and a REC Start
(Record start) to Rec Stop (Record stop) or Rec Pau
This is a unit corresponding to se (recording suspension). The stream data corresponding to the original scene shown in FIG.
Corresponds to S.

EU is the minimum unit in destructive editing. Destructive editing means editing involving movement or deletion on the disk, and the minimum unit of destructive editing means that movement or deletion on the disk can be performed only in EU units. The EU includes one or more VUs (Video Units) and zero or one PRU (Post Recording Unit), and one EU must be continuously recorded on a disk. Note that it is also possible to define a stream configuration without a PRU, and this is shown in FIG. In this example, one EU is composed of one VU. Post Recording means post-recording. The PRU is a data area for Post Recording that is played back in synchronization with video data in the EU, so at least
There must be an area that can record data corresponding to the presentation time of EU video data. VU is Unit H
This is a unit in which the eader, video data of 1 GOP or more, and corresponding audio data are put together.

The EUS is divided into fixed-length blocks of 2048 bytes. One block is stored in one logical block, and one block is basically composed of one packet. The packet here conforms to the PES Packet defined in ISO / IEC13818-1, and this packet is recorded on the disk.

FIG. 4 shows a relationship between an EUS having a PRU and a block, and FIG. 5 shows a relationship between an EUS having no PRU and a block. In the figure, PRU is UH-BLK (Unit Header Bloc
k), A-BLK (Audio Block), P-BLK (Padding Block)
It consists of. UH-BLK is a packet storing header information related to PRU, A-BLK is an audio packet specified by ISO / IEC13818-3, and P-BLK is a padding packet specified by ISO / IEC13818-1. Is done.

The VU is UH-BLK (Unit Header Bloc)
k), A-BLK (Audio Block) and V-BLK (Video Block). UH-BLK is a packet storing header information related to VU, A BLK is an audio packet specified by ISO / IEC13818-3, and V-BLK is a packet storing video data specified by ISO / IEC13818-2. Are respectively stored. UH-BLK is a packet storing header information related to PRU or VU.

The Unit Header is a so-called auxiliary data area relating to the unit. FIG. 6 shows the configuration of this Unit Header packet. In the table of FIG. 6, BP means Byte Position, information indicating the start position of the corresponding management item viewed from the top, Length represents the size of the management item in Byte,
Field Name indicates a management item name, and Contents indicates what format the management item must be recorded. Uint among data types used in Contents
8 is unsigned 8-bit integer, Uint16 is unsigned 16-bit integer, Ui
nt32 is an unsigned 32-bit integer, String is a data type for storing a character string, and Timestamp is a type for storing date and time information.

The Unit Header packet has a packet-start-code-prefix indicating that the packet starts,
Stream-id indicating ID, PES-p indicating length of this PES Packet
acket-length, indicating the state of the Unit that contains this Packet
Unit Property, Length of Unit that indicates the length of the Unit that includes this Packet, Start RLBN of Video Data that indicates the number of relative logical blocks from the beginning of the unit that includes this Packet to the first block that includes video data, pack
All I Picture and P Pic in units included in et
End RLBN of IPPictures indicating the last address on the disc containing the I Picture and P Picture in the unit included in the packet,
Numb indicating the number of VUs contained in the EU containing this packet
er of VU, Start RLBN of Data for VU indicating the relative number of logical blocks from the beginning of the PRU of the data in the PRU corresponding to each VU included in the EU included in this packet, Number indicating the number of scenes to be managed of Scenes, and SceneInformation that manages management information about scenes.
The details of Scene Information will be described later.

Here, the upper limit of the number of scene information that can be managed is set. For example, if the upper limit is 20 scenes, the Unit Header has 20 Scene Inf
The area that can be recorded by ormation shall be secured. This is because when Scene Information records the stream data on the disc and creates a user scene, the Scene In
This is to prepare the data area in advance to rewrite only the formation part. When recording stream data on a disc for the first time, for example, 0 is recorded in Number of Scenes, and FF is recorded in hexadecimal in all areas for recording 20 pieces of Scene Information.

The Unit Header block is aligned in units of logical blocks, and the head of the Unit Header Block is configured to always coincide with the head of the logical block, so that it can be easily accessed.

As described above, the original scene managed by the real file and the user scene managed by the virtual file when the MPEG stream is recorded on the disc are a set of stream data corresponding to a GOP in MPEG as described above. Must be in VU units. This is because, when a frame starting to be reproduced from the middle of the MPEG stream data is a P picture or a B picture, in order to actually decode the frame, the I picture or the P
This is because decoding cannot be performed without picture data. Further, in the stream configuration in which a PRU exists in the above-described embodiment, a file or virtual file is further divided into EU units including an arbitrary number of VUs, which are sets of stream data corresponding to the GOP structure, and PRU areas. Must be treated. This is a PRU for all VUs in the EU
Are continuously allocated, and each VU and PR in the EU
This is because it is difficult to manage U separately.

In the case of a stream configuration having no PRU, a file or a virtual file is created for each VU. Therefore, a file or virtual file that manages an original scene or a user scene is a management unit in which an integer number of EUs or VUs on a disk are collected, depending on whether stream data in which a PRU exists is targeted.

FIG. 7 shows a relationship between a real file as an original scene and a virtual file as a user scene.
In this example, the original scene is the real file OS0001.MPG
And is managed by the management information of the file. OS00
01. The MPG is recorded on the disc by being divided into three continuous areas. When reading the original scene from the disk, the user system sends the file to the device driver.
By specifying the reading of OS0001.MPG, the device driver divides based on the position information (start address and length) of the divide 1A, divide 2A, and divide 3A on the disk managed by the logical file system management information. 1A, split 2A, split
Read data from disk in 3A order.

Here, the relationship between the data on the disk managed by the real file and the management information of the logical file system is shown.
See Figure 9. In the example shown in the figure, data recorded as three separate files as one real file and file management information for managing the data are recorded on the disk. With this file management information, the recording position of the data recorded on the disc can be specified from the file name.
The file management information is information that is normally used by a device driver for accessing a disk, and is information that cannot be directly seen from a user system. That is, the user system issues a data read command to the device driver by designating a file name. In the present invention, file management information for managing a real file
Call it escriptor.

Next, a user scene defined by editing the original scene and selecting EU # 1 to EU # 7 in FIG. 7 will be described. User scene is virtual file US
0001.MPG, and refers to the original data on the disk by the position information (start address and length) of the division 1B, division 2B, and division 3B in the management information of the logical file system. Here, from the EU # 0 on the disc
Only one piece of video data corresponding to EU # 9 is recorded, but partial data can be read out by specifying the virtual file in the user system based on the location information of any location referenced in the virtual file Becomes

FIG. 10 shows the relationship between the data on the disk managed by the virtual file and the management information of the logical file system. In the example shown in the figure, data recorded on a disk is managed by one real file, and a position on the disk is managed by a virtual file by referring to an arbitrary part of data managed by the real file. On the disk, file management information of a real file and a virtual file is recorded. With these file management information, it is possible to specify the recording position of the data recorded on the disc from the file name. In the file management information of the real file, the position information of the data recorded on the disk is managed, and in the file management information of the virtual file,
It manages position information of an arbitrary portion of data recorded on a disk managed by an actual file. The file management information of the real file and the file management information of the virtual file have information for distinguishing each. In the present invention, file management information for managing a virtual file is called a Virtual File Descriptor.

As described above, the virtual file refers to the data of the original scene recorded on the disk. Also, the virtual file can refer to the same original scene in a plurality of user scenes.
FIG. 8 shows a virtual file for managing two user scenes. In this example, EU # 0 to EU # 9 are original scenes, and EU # 1 to EU # 7 are user scenes 1 (US000
1.MPG), EU # 6 to EU # 9 are user scene 2 (US0002.M
PG). That is, EU # 6 and EU # 7 are referred to in two user scenes.

FIG. 11 shows a relationship between a real file as an original scene and a virtual file as a user scene in the case of stream data in which a PRU area is not defined.
See Figure 12. The difference from FIGS. 7 and 8 is that EU is only VU, and therefore the description is omitted.

It is assumed that a user scene managed in such a form is transferred to a PC or another AV device via a network using IEEE1394 or the like. In order to copy an original scene or a user scene or to perform network transfer, a corresponding file or virtual file is designated to perform file copy or file transfer. For example, when it is desired to transfer the user scene US0001.MPG managed by the virtual file to the PC in FIG. 24, the PC issues an instruction to acquire US0001.MPG using a transfer application.

FIG. 13 shows an example of a system configuration diagram. In this figure, the video camera and the PC are connected by IEEE1394. In each system, a device driver is prepared based on a logical file system that manages a disk medium. That is, each user system can access the disk in file units via each device driver. Each system is provided with a driver for using IEEE1394.

For example, if the user system B (7) on the PC side is IEEE
Via the 1394 driver B (8), the IEEE1394
When a stream data acquisition request is issued to the driver A (3) by specifying a virtual file name for managing the user scene, the IEEE1394 driver A (3) transmits the virtual file designated to the device driver A (2). Issue a read command. As a result, the stream data on the disk (6) is read from the disk, and the stream data is read from the PC via the IEEE1394 driver A (3).
Transferred to the side. The transferred data passes through the IEEE 1394 driver B (8) on the PC side and the disk on the PC side via the device driver B (9) with the file name specified by the user system B (7).
(12) will be recorded above.

When reproducing the transferred stream data, the transferred stream data is read by using an application program to be reproduced on a PC.
Conventionally, if the stream data read from the disc is reproduced from the end to the end in order, the reproduction is performed in EU or VU units as described above. However, in reality, it is highly possible that a user scene defined by editing by a user starts playback from a frame in the middle of an EU or VU, and ends playback in a frame in the middle of the last EU or VU. .

In FIG. 14, the reproduction range of the user scene designated by the user is from the sixth video frame (frame number 5) in VU # 3 in EU # 0 to VU # 121 in VU # 121 in EU # 20. The example up to the twelfth frame (frame number 11) is shown. In other words, the stream data on the destination disk is
EU # 0 to EU # 20, and when this entire stream data is reproduced, it differs from the reproduction range of the user scene specified by the user.

Therefore, in the present embodiment, information for accurately reproducing a user scene is expressed by a unit on the stream.
By recording in the Header, only stream data,
It is possible to specify a reproduction range in frame units.

As information for accurately reproducing the user scene in the Unit Header packet, Number of Scenes and Sc
There is ene Information. Scene Information is Number o
f The number of Scenes will be recorded. Scene Inform
The details of the ation are shown below.

[0053] Scene Name stores the name of the scene.
ene Creation Date is the date and time the scene was created, Scene Data Si
ze stores the data size of the file that manages the defined scene. This data size represents the actual data size after reading from the disk.

The Scene Start VU Number manages the number of the VU including the video frame whose reproduction is to be started in the stream data managed as a file, with a value based on the first VU of the stream data. In the case of a stream in which there is no PRU, this value is always 0, and in the case of a stream in which a PRU exists, the number of the VU containing the frame in the EU whose reproduction is to be started is managed.

The Scene Number of VU is
Information to indicate the number of VUs, Scene Start VU Numbe
It manages the number of VUs from the VU managed by r to the VU including the frame to stop playback.

The Scene Start Frame Number manages the number of the frame at which playback is started. Frame number is Scene
This is the frame number within the playback start VU number managed by Start VU Number. In other words, the video frame from which playback is started is the Scen in the stream data read from the disc.
e Start VU Number Scene Start Frame Numbe in the VU of the eye
r.

The Scene End Frame Number manages the number of the frame at which playback is stopped. Frame number is Scene St
A frame number in the playback end VU corresponding to a value obtained by subtracting 1 from the value obtained by adding the Scene Number of VU, which is the number of VUs in the user scene, to the playback start VU number managed by the art VU Number.

By using the Unit Header as described above, it is possible to accurately reproduce the user scene.
It is possible to include management information on the user scene. Actually, the stream data always starts at the Unit Header regardless of whether the stream has a PRU or not. Therefore,
By reading the head header of the stream data to be reproduced from now on, it is possible to grasp the reproduction information of the user scene. In other words, when the VU comes first in the stream data managed by the virtual file (when the PRU is not defined)
Records Scene Information in the Unit Header corresponding to the VU, and if the PRU is placed at the top, the Unit H corresponding to the PRU
The scene information will be recorded in the eader.

In the example of FIG. 14, the stream data in which the PRU is defined is managed by the virtual file US0001.MPG, and since the PRU is located at the top, the data in the Unit Header at the top of the PRU The scene information is stored in the scene information. In this example, a Scene that manages the VU number that contains the frame to start playback
Start VU Number is 3, Sc managing the number of VUs in the scene
118 is stored in the ene Number of VU, 5 is stored in the Scene Start Frame Num that manages the playback start frame number, and 11 is stored in the frame number to stop the playback. Also figure
Stream data with no PRU in virtual file U
The state managed by S0001.MPG is shown. In this example, 1EU is composed of 1VU because PRU is not defined.The head of the stream data managed by the virtual file is the Unit Header existing at the head of VU # 0, and this user header is This stores scene management information.

In such a configuration, a plurality of user scenes may start reproducing from the same EU. In such a case, for example, as shown in FIG.
When 01.MPG and US0002.MPG start playback from the same EU, it is unclear which Scene Information stored in the Unit Header should be used. So, Scene Info
It is possible to say that the user is presented with the name of the scene in the rmation and the playback information is selected. For example, it is possible to use the file name of the virtual file as the scene name,
In this case, if the file name of the virtual file is changed, consistency of the correspondence cannot be maintained. In the case of a stream in which no PRU is defined, the user scene is configured not in EU units but in VU units, and it is sufficient to replace all EUs in FIG. 16 with VUs.

When it is desired to automatically select the reproduction information corresponding to the scene, the data size of the file managed by the transferred file system and the scene information
By comparing the values of the Scene Data Size in the above, it is possible to select the desired reproduction information. In the example of FIG. 16, the user scene US0001.MPG is composed of EU # 0 to EU # n, and the virtual file for managing the user scene has a file size of 256000 KB. Also, the user scene US0002.M
The PG is composed of EU # 0 to EU # n-3, and the file size for managing the user scene is 20480 KB. The corresponding Scene Info is checked by checking if the Scene Data Size of the SceneInformation recorded in the Unit Header has a field recorded with 256000KB and 20480KB, respectively.
rmation can be extracted automatically.

Here, as a specific process, a case where an original scene is shot by a video camera and an original scene is recorded as a file on a disc will be described. The procedure from the recording of the original scene on the disc to the creation of the above-described File Descriptor of the logical file system is the same as in the related art, and will not be described. Here, the processing unique to the present invention after the file is recorded will be described with reference to the flowchart in FIG.

In step S10, when there is a request to create an original scene and the creation of a file for managing stream data is completed, in step S11, a response to the stream data managed by the file is performed based on the position information on the disk. The first logical block of the stream data to be read is read. A logical block is a minimum read / write unit managed by the file system. Here, the read logical block is a Unit in which the Unit Header arranged at the head of the original scene is recorded.
Header packet. The playback information of the original scene is recorded in this Unit Header.

In step S12, Nu in the Unit Header
Set 1 for mber of Scene. In step S13, the scene name is set to Scene Name in Scene Information, and the creation date and time of the original scene is set. In step 14, Scen
Set the file size of the original scene managed by the file system, that is, the data size of the file recorded in the File Descriptor, in Scene Data Size in e Information.

In step 15, Scene Information
0 for the Scene Start VU Number in the
The value of the number of VUs in the original scene to the Scene Start Fram
Set e to 0 and Scene End Frame Number to the last frame number of the last VU in the original scene. The frame number is a number in the VU and is a number starting from 0. In step S16, the content updated in steps S12 to S15 is updated on the disk, and the process ends. At this point, the UnitHead at the beginning of the original scene
This means that reproduction information as an original scene has been created in er.

Next, a case where a user defines a user scene using an original scene as a material will be described. The video data corresponding to the user scene ranges from an arbitrary frame in the first unit of the virtual file to an arbitrary frame in the last unit of the virtual file. Therefore, when the user specifies an arbitrary scene, first, a unit from the unit including the first frame to the unit including the last frame is defined as a virtual file. The definition of this virtual file is the same as above,
A ual File Descriptor is created. Virtual File Desc
The processing after the riptor is created will be described below with reference to the flowchart in FIG.

In step S20, when there is a user scene creation request and creation of a virtual file for managing the corresponding stream data (creation of a file descriptor) is completed, in step S21, the stream data of the stream data managed by the virtual file is managed. The head logical block of the corresponding stream data is read based on the position information on the disk. The read logical block is a Unit Header packet in which the Unit Header arranged at the head of the user scene is recorded. The reproduction information of the user scene is recorded in this Unit Header.

In step S22, Nu in the Unit Header
Add 1 to the value of mber of Scene. In step S23,
Set the scene name in Scene Name in the corresponding Scene Information, and set the creation date and time of the user scene. In step S24, Sce
The file size of the user scene managed by the file system (Virt
ual File Descriptor).

In step S25, Scene Information
Set the VU number including the frame to start the reproduction in the stream data of the user scene in the Scene Start VU Number in. The VU number is a relative value based on the head of the stream data of the user scene. Step S2
In 6, Scene Number of VU in Scene Information
Is set to the value of the number of VUs to be reproduced in the user scene. In step S27, the Scene Star in the Scene Information
Set the number of the frame to start playback to t Frame Number. The frame number is a frame number in the VU managed by the Scene Start VU Number set in step S25, and is a relative value with respect to the head of the VU. In step S28, the Scen in the Scene Information
e End Frame Number is the last number displayed in the user scene.
Set the frame number in the VU. The VU number including the last frame to be displayed is a value obtained by adding the value -1 of the Scene Number of VU set in step S26 to the Scene Start VU Number set in step S25. In step S29, the contents of the Unit Header updated in steps S22 to S28 are updated on the disk, and the process ends.

FIGS. 14 and 15 show a state in which reproduction information relating to a user scene is recorded based on the flowchart of FIG. 18 described above.

The stream data corresponding to the user scene managed by the virtual file is transmitted to a PC via a network or the like.
An accurate method of reproducing the user scene on the transfer destination PC when the data is transferred to the destination PC will be described with reference to the flowchart shown in FIG. Of course, the same applies to reproduction in the case where transfer is not performed.

When a request to reproduce a user scene occurs in step S30, the logical block at the head of the stream data is read from the position information on the disk of the file for managing the user scene in step S31. The read logical block is Unit He equivalent to Unit Header.
ader packet. Numbe from the read Unit Header
Understand the value of r of Scenes. In step S32, Un
If Number of Scenes in it Header is 0, step S
At 33, the display start frame is set to the first display frame in the stream data, and the display end frame is set to the last display frame in the stream data. That is,
All video frames in the stream data will be displayed. The case where the value of Number of Scenes is 0 is an illegal situation where scene information was not correctly recorded for some reason when a user scene was created. In step S35, data is read from the stream data, decoded, and reproduced. Here, all frames are reproduced.

At step S32, Nu in the Unit Header
If mber of Scenes is 1, the display start frame is set to Scene Start V in Scene Information in step S34.
The frame indicated by the Scene Start Frame Number in the VU indicated by U Number, and the display end frame
The value is set to the frame indicated by the Scene End Frame Number in the VU of the value -1 obtained by adding the art Flame Number and the Scene Number of VU.

In step S35, display control is performed on the stream data read from the disk based on the reproduction information set in step S34, and the process ends. Specifically, stream data read from a disk is read in EU units, decoded in VU units, and played back from a start frame based on playback control information.

In step S32, Nu in the Unit Header
If mber of Scenes is 2 or more, in step S36
Determines whether all Scene Information in the Unit Header has been checked. In step S36, all S
If the scene information check has not been completed, the file size of the user scene managed in the file system is compared with the scene data size in the scene information read out in step S31 in step S37. In step S38, the file size of the file managing the user scene and the Scene Information
If the Scene DataSizes in the scene information match, the display start frame is
Scene Start Fram in VU indicated by ne Start VU Number
Set the frame indicated by e Number to the end frame
e Scene Number in Scene Start VUNumber in Information
Scene End Frame N in the VU of the value minus one of the VUs
Set as umber. In step S35, step S34
The display control is performed on the stream data read from the disk based on the reproduction information set in the step, and the processing ends.

At step S38, the file size of the virtual file managing the user scene and the Scene Info
If the Scene Data Sizes in the rmation do not match, the process returns to step S36, and the same processing is repeated for the next Scene Information. In Step S36, all Scene Infor
When the mation check is completed, there is no corresponding scene, so it is illegal, but as an example, S39
It is also possible to let the user select Scene Information in. Alternatively, error processing may be performed at the stage of S39, and the processing may end.

Next, a case where the reproduction information described in the first embodiment as the second embodiment is stored in an MPEG standard compliant header area without using a user-defined header packet will be described.

The stream data encoded by MPEG1 and MPEG2 has a hierarchical structure such as a sequence layer, a GOP layer, a picture layer, a slice layer, a macroblock layer, and a block layer as shown in FIG. Header information is added to each layer. Here, attention is paid to the sequence layer and the GOP layer.

FIG. 21 shows the definition of the video stream sequence in the MPEG2 standard. As shown in this figure, in the sequence layer, information (sequential
ence-header () 20), sequence extension (se
After quence-extension () 21), user data (exten
It is possible to record sion-user-data (0) 22).
FIG. 22 shows the processing contents of extension-user-data (). Here, it is determined whether the user-data-start-code 30 is recorded. user-data-start-code is 000001B2 in hexadecimal. The content of the user data shown in FIG. 23 can store information in units of 8 bits * n and can be recorded until 000001 in hexadecimal, that is, until the start code 40 of the next information appears. Also GOP
In the layer, information of the GOP header (group-of-pictures-hea
After der () 23), user data (extension-user-data (1) 24) can be recorded in the same manner as in the sequence layer. The form of the user data is the same as that of the sequence layer.

As described above, it is possible to record user-defined information in the sequence layer and the GOP layer. Here, the reproduction information described in the first embodiment is
Consider storing in the user data area instead of the t Header.

Here, when it is considered that this reproduction information is required in GOP units, it is necessary to place some restrictions on the stream configuration. First, G in the MPEG2 standard
Although it is possible to define a stream having no OP layer header information, in the present embodiment, there is always a restriction that one GOP layer header information is added to one GOP.

In the present embodiment, a case where reproduction information is stored in user data in the GOP layer will be described. The playback information is stored in the extension-user-data (1) in the GOP layer described above. Since the reproduction information itself is the same as the configuration described in the first embodiment, the description is omitted. Specifically, Unit H
the value of Number of Scenes and Scene Information in the eader
It will be recorded in the GOP layer user data.

S that can be recorded in the user data of the GOP layer
Set the upper limit of the number of scene information. For example, the upper limit
When the stream is recorded for the first time, the number of user data in the GOP layer is set as Scene Info.
Reserve an area where 20 rmations can be recorded in advance. By recording dummy data, for example, FF in hexadecimal, in this area when recording a stream for the first time, it is possible to prevent that there is no data area to record when adding playback information by user editing later Becomes

It is assumed that the video stream data and the audio stream data thus defined are multiplexed and random access is performed for each management unit corresponding to the GOP structure. The virtual file for managing the user scene may manage the position information for each management unit corresponding to the GOP structure including the reproduction start and end frames of the user scene.

Here, when this stream data is recorded on a disk, each GOP is recorded as in the first embodiment.
If the header information of the layer is controlled so as to be aligned with the logical block of the disk, the GOP header is read and updated by reading the first logical block of the virtual file managing the user scene. Can be done easily. However, when the header information of each GOP in the stream is not aligned with the logical block of the disk, even if the first logical block of the virtual file managing the user scene is read, the header of the GOP header of interest is not necessarily read. The information is not always at the beginning of the read logical block. In other words, we are paying attention
It is also conceivable that the information of the immediately preceding GOP is at the beginning of the read data.

Further, when actually recording MPEG stream data on a disc, it is common practice to format it into a packet format such as a PES stream or a PS stream which is an MPEG system standard. Recording in the form of PES or PS packets basically means that stream data obtained by multiplexing a video stream and an audio stream is divided into arbitrary size packets, and header information is attached to each packet. It is.

In such a case, the read stream data is viewed in order from the beginning, extra header information is skipped, and the extension-use
Search until r-data (1) is found. Specifically, 000001B2 in hexadecimal as user-data-start-code
Search until is found. The area for recording the reproduction information specified by the search operation is read or updated.

The processing procedure for writing the reproduction information and the like are basically the same as those described in the first embodiment, so that the description is omitted.

Although the first and second embodiments have been described on the assumption that the user scene is managed by the virtual file,
As in the conventional method shown in FIG. 26, position information on a disc corresponding to an arbitrary portion of an original scene referred to by a user scene is managed as one management information file, and Scene Information which is playback information is referenced. You may make it put in the head header of stream data. According to such a method, the present invention can be implemented even in a system having no virtual file function. In this case, when the user scene is to be copied or transferred to another device or the like, the position where the stream data is read from the disk is specified and transferred based on the position information on the disk of the user scene managed in the management information file. . At the transfer destination, stream data whose playback information is stored in the Unit Header at the head of the stream data is managed as a file.

[0090]

According to the present invention, since the information indicating the reproduction start position and the reproduction end position can be stored in the auxiliary data of the unit in which the video data and the audio data are recorded, a part of the original scene can be stored. In the case of a user scene, by storing the reproduction information in the auxiliary data at the head of the user scene, it is possible to perform reproduction start and reproduction end control from an arbitrary position in the unit, and
There is no need to manage the reproduction information in another file, for example.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a configuration of a device targeted by an embodiment of a data management method of the present invention.

FIG. 2 shows a PRU handled in an embodiment of the data management method of the present invention.
FIG. 3 is a diagram showing a configuration of an MPEG stream in which is defined.

FIG. 3 is a PR used in the embodiment of the file management method of the present invention.
FIG. 3 is a diagram illustrating a configuration of an MPEG stream in which U is not defined.

FIG. 4 shows a PRU used in the embodiment of the data management method of the present invention.
FIG. 3 is a diagram showing a relationship between an MPEG stream and blocks defined as follows.

FIG. 5 shows a PRU used in the embodiment of the data management method of the present invention.
FIG. 4 is a diagram showing a relationship between an MPEG stream and a block for which no is defined.

FIG. 6 is a diagram illustrating a unit handled in the embodiment of the data management method of the present invention.
It is a figure showing the content of Header.

FIG. 7 shows a first embodiment of the data management method according to the present invention.
FIG. 7 is a diagram showing a state in which two virtual files refer to data of an original scene (in the case where there is a PRU).

FIG. 8 shows a second embodiment of the data management method of the present invention.
FIG. 7 is a diagram showing a state in which two virtual files refer to data of an original scene (in the case where there is a PRU).

FIG. 9 is a diagram showing a relationship between management information of a logical file system of a real file recorded on a disk and data managed by the real file in the embodiment of the data management method of the present invention.

FIG. 10 is a diagram showing a relationship between management information of a logical file system of a virtual file recorded on a disk and data referenced by the virtual file in the embodiment of the data management method of the present invention.

FIG. 11 is a diagram showing a state in which one virtual file refers to data of an original scene in the embodiment of the data management method of the present invention (when there is no PRU).

FIG. 12 is a diagram showing a state in which two virtual files refer to data of an original scene in the embodiment of the data management method of the present invention (when there is no PRU).

FIG. 13 is a diagram showing a system configuration in an embodiment of the file management method of the present invention.

FIG. 14 is a diagram showing a relationship between stream data managed by a virtual file and a reproduction range actually specified by a user in the embodiment of the data management method of the present invention (in the case where there is a PRU).

FIG. 15 is a diagram showing a relationship between stream data managed by a virtual file and a reproduction range actually specified by a user in the embodiment of the data management method of the present invention (in the case where there is no PRU).

FIG. 16 is a diagram showing a state of a virtual file whose reproduction is started from the same EU in the embodiment of the data management method of the present invention.

FIG. 17 is a flowchart illustrating a flow of processing performed when an original scene is created in the data management method according to the embodiment of the present invention.

FIG. 18 is a flowchart showing the flow of processing performed when creating a user scene in the embodiment of the data management method of the present invention.

FIG. 19 is a flowchart showing a flow of processing performed when a user scene is reproduced in the embodiment of the data management method of the present invention.

FIG. 20 is a diagram showing the hierarchical structure of MPEG handled in the second embodiment of the data management method of the present invention.

FIG. 21 is a diagram illustrating processing of an MPEG video sequence handled in the second embodiment of the data management method of the present invention.

FIG. 22 is a diagram showing MPEG extension and user data processing handled in the second embodiment of the data management method of the present invention.

FIG. 23 is a diagram showing processing of MPEG user data handled in the second embodiment of the data management method of the present invention.

FIG. 24 is a diagram showing a relationship between a real file and a virtual file in a conventional technique.

FIG. 25 is a diagram showing a state in which reproduction information is provided for each user scene and is managed as a real file in the related art.

FIG. 26 is a diagram showing a state in which stream data according to the related art is managed in a real file, and reproduction information of a user scene that refers to an arbitrary portion of the stream data is recorded as management information in a real file.

[Explanation of symbols]

 Reference Signs List 1 control unit 2 camera unit 3 MPEG encoder 4 MPEG system unit 5 buffer memory 6 ECC signal processing unit 7 modulation / demodulation / sector codec unit 8 servo control unit 9 disk

──────────────────────────────────────────────────続 き Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) H04N 5/91 G11B 27/02 A

Claims (9)

[Claims] 1. One or more GOPs on a recording medium
A data recording method in a recording / reproducing apparatus that records video data as a file that is a set of units composed of data and corresponding audio data, and auxiliary data, and reads and writes video data in file units, A data recording method characterized by recording reproduction information of the file in auxiliary data of a head unit of the file. 2. One or a plurality of GOPs on a recording medium
A data recording method in a recording / reproducing apparatus that records video data as a file that is a set of units composed of data and corresponding audio data, and auxiliary data, and reads and writes video data in file units, A data recording method which manages all or a part of units of a recorded file as a virtual file, and records reproduction information of the file in auxiliary data of a head unit of the virtual file. 3. The data recording method according to claim 1, wherein the reproduction information includes information indicating a frame to start reproduction and a frame to end reproduction. 4. The data recording method according to claim 1, wherein the reproduction information includes a file size of the file or the virtual file. 5. The apparatus according to claim 1, wherein the unit is one GOP unit, and the reproduction information is recorded in a user data area of a GOP layer in an MPEG format.
The data recording method according to any one of the above. 6. On a recording medium on which video data is recorded as a file which is a set of one or a plurality of GOP data, corresponding audio data, and auxiliary data, read out the video data in file units. And a data reproducing method in a recording / reproducing apparatus for performing writing, wherein the reproducing information recorded in the auxiliary data of the head unit of the read file is read, and the read file is read out based on the reproducing information. A data reproduction method comprising performing reproduction control. 7. The data reproduction method according to claim 6, wherein the reproduction information includes information indicating a frame to start reproduction and a frame to end reproduction. 8. The reproduction information includes a file size of the file recorded in a management area, selects reproduction information that matches a file size of a file to be reproduced, and reproduces the reproduction information based on the selected reproduction information. 8. The data reproducing method according to claim 6, wherein control is performed. 9. The apparatus according to claim 6, wherein the unit is one GOP unit, and the reproduction position management information is recorded in a user data area of a GOP layer in an MPEG format. Data recording method.