Method of creating and recording image file

A method of creating an image file to be additionally written is disclosed to prevent logical inconsistency between the image file and existing recorded data in a target information recording medium. The method of creating an image file of target information to be additionally written in an information recording medium includes: a first step of creating image data of the target information; a second step of obtaining identification information of the information recording medium; and a third step of creating an image file having the image data in association with the identification information.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention generally relates to a method of creating and recording an image file and an information recording system, and more particularly to a method of creating an image file to be additionally written in an information recording medium, a method of additionally writing such an image file in an information recording medium, an information recording system having an information recording device and an information processing device, and an information recording medium for storing a program for such an information recording system.

2. Description of the Related Art

Recent technological advances in personal computers (PC) makes it possible to process audio-visual information such as audio information and video information. In general, such audio-visual information includes an enormous amount of data. Thus, there is an increasing interest in CD (Compact Disc) and DVD (Digital Versatile Disc) as high-capacity information recording media for storing audio-visual information. In addition, as optical disk devices become more affordable, the optical disk devices have been more widely used as information recording devices to record information in optical disks.

For example, when user data are recorded in CD-R (CD-Recordable), installed mastering application software (hereinafter which is referred to as “writer software”) is used in general. Conventionally such writer software temporarily creates image data including user data and directory information thereof in a hard disk, and then records the created image data in CD-R. In this case, after recording the image data in CD-R, the image data are automatically deleted from the hard disk.

A conventional multisession recording approach, which is one of recording technologies for CD-R, allows information to be additionally written per session. For example, in order to additionally write user data in CD-R containing at least one session, conventional writer software executes the following steps:1. Read file management information having session volume information recorded in a predetermined area in target CD-R and logical structure information on file data;2. Attach file information on the target user data, which will be additionally written, to the file management information to establish links between the target user data and existing recorded data;3. Create image data having updated file management information and the target data in a hard disk;4. Additionally write the created image data in CD-R; and5. Delete the image data from the hard disk.

In recent years, writer software that can create an image file from image data (hereinafter which is referred to as a “filing function”) and then store the created image file in a hard disk has been available. For example, if a user created an image file from image data and stored the image file in a hard disk before, the user can use such writer software to record the image file on CD-R later.

However, such conventional filing function can record data in only a blank disk. In other words, conventional writer software cannot additionally write data in a non-blank disk. As mentioned above, if image data are multisession recorded, the image data includes file management information. Thus, when the image data are additionally written in another CD-R different from CD-R used in image data creation, logical consistency between the image data and existing data in the different CD-R can fail. As a result, there is a risk that some problems may be caused. For example, although CD-R includes the image data, the image data cannot be accessed. Also, when a user attempts to access the image data, the system is crashed.

SUMMARY OF THE INVENTION

It is a general object of the present invention to provide a method of creating an image file creation method, a method of recording an image file and an information recording system in which one or more of the above-mentioned problems are eliminated.

A first more specific object of the present invention is to provide a method of creating an image file for target data to be additionally written without logical inconsistency between the image file and existing recorded data.

A second more specific object of the present invention is to provide a program for an information recording system having an information recording device and an information processing device without logical inconsistency between the image file and existing recorded data, and a recoding medium for storing the program.

A third more specific object of the present invention is to provide a method of additionally writing data and an information recording system without logical inconsistency between the image file and existing recorded data.

In order to achieve the above-mentioned objects, there is provided according to one aspect of the present invention a method of creating an image file of target information to be additionally written in an information recording medium, including: a first step of creating image data of the target information; a second step of obtaining identification information of the information recording medium; and a third step of creating an image file having the image data in association with the identification information.

According to one aspect of the present invention, for example, if a created image file is additionally written later, it is possible to determine whether the image file can be additionally written in an information recording medium without logical inconsistency between the image file and existing data recorded in the information recording medium by referring to identification information associated with the image file before execution of the additionally write operation. As a result, it is possible to prevent such logical inconsistency between the image file and the existing recorded data.

Additionally, there is provided according to another aspect of the present invention a method of additionally writing image data included in an image file in an information recording medium, including: a first step of obtaining identification information of the information recording medium; a second step of determining whether the identification information of the information recording medium and identification information associated with the image file are the same; and a third step of, only if the identification information of the information recording medium and the identification information associated with the image file are the same based on the determination, additionally writing the image data included in the image file in the information recording medium.

According to one aspect of the present invention, identification information associated with a target image file is referred to before execution of the additionally write operation, and only if the associated identification information and identification information of a target information recording medium are the same, the image file is allowed to be additionally written in the information recording medium. As a result, it is possible to additionally write the image file without logical inconsistency between the image file and existing recorded data.

Additionally, there is provided according to another aspect of the present invention an information recording system for recording information in an information recording medium, including: an information processing device having a file creation part, in response to a request to create an image file of target information to be additionally written in an information recording medium, creating an image file including image data of the target information in association with identification information of the information recording medium; and an information recording device, in response to a recording request from the information processing device, recording the target information in the information recording medium.

According to one aspect of the present invention, for example, if a created image file is additionally written later, it is possible to prevent illegal installation of an unsuitable information recording medium other than specific information recording media into an information recording device without logical inconsistency between the image file and existing data recorded in the information recording medium by referring to identification information associated with the image file before execution of the additionally write operation. As a result, it is possible to prevent such logical inconsistency between the image file and the existing recorded data.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

A first embodiment of the present invention is described with reference toFIG. 1throughFIG. 4.

FIG. 1shows an exemplary structure of an information recording system10according to the first embodiment of the present invention.

Referring toFIG. 1, the information recording system10includes an optical disk device20as an information recording device and a host50as an information processing device to control the optical disk device20. It is noted that illustrated connection lines (solid lines) do not represent all connections between individual blocks. The connection lines are focused on main flow of signals and information.

The optical disk device20includes an optical pickup device23, a signal processing device21, a control device22and a communication interface38. The optical pickup device23emits a laser ray toward a recorded surface, on which spiral or concentric tracks (recording area) are formed, of an optical disk15as an information recording medium. At the same time, the optical pickup device23receives light reflected from the recorded surface. The signal processing device21extracts various kinds of information from output signals supplied from the optical pickup device23to generate write signals corresponding to data to be recorded in the optical disk15. The generated write signals are supplied back to the optical pickup device23. The communication interface38is a bidirectional communication interface between the optical disk device20and the host50. The communication interface38is compliant with a standard interface such as ATAPI (AT Attachment Packet Interface), SCSI (Small Computer System Interface) and USB (Universal Serial Bus). The control device22controls the optical disk device20based on instructions issued by the host50. In this embodiment, a CD-R (Compact Disk-Recordable) information recording medium is used as the optical disk15. Also, an ISO9660 compliant file system is used in this embodiment.

On the other hand, the host50includes a main control device52, RAM (Random Access Memory)53, a hard disk (HDD)54as a recording medium, an input device55, a display device56and a communication interface57. These components are connected to each other via a common bus59.

The main control device52includes a microcomputer (MPU)52aand a main memory52b. The main control device52controls the host50and temporarily stores some data required to control the host50into RAM53.

The communication interface57is a communication interface in compliance with the same standard as the communication interface38of the optical disk device20. The communication interface57is connected to the communication interface38. Here, the communication interfaces38and57may be connected via a communication cable such as a SCSI cable. Alternatively, the communication interface38and57may be connected in wireless such as infrared communication.

HDD54includes programs described in codes that MPU52acan read. A program to create an image file of user data in response to an image file creation request (hereinafter which is referred to as an “image file creation program”) is stored in HDD54. Also, a program to additionally write an image file in the optical disk15in response to an image file additionally write request (hereinafter which is referred to as an “image file additionally write program”) is stored in HDD54. In addition, a plurality of user data files are stored in HDD54.

The display device56includes a display part (not illustrated) such as CRT (Cathode Ray Tube), LCD (Liquid Crystal Display) and PDP (Plasma Display Panel). The display device56displays information supplied from the main control device52.

The input device55includes at least one input medium (not illustrated) such as a keyboard, a mouse, a tablet, a trackball, a stylus pen and a touch panel. The input device55supplies user's input information to MPU52a. Here, such input information may be wireless supplied from an input medium. Alternatively, a touch panel attached CRT, which integrally contains the display device56and the input device55, may be used as the input device55.

An exemplary image file creation operation to create an image file of user data according to the first embodiment is described with reference toFIG. 2andFIG. 3.

FIG. 2is a flowchart of an image file creation operation executed by MPU52aof the information recording system10according to the first embodiment.FIG. 3is a diagram to explain an exemplary image file created in accordance with the image file creation operation shown inFIG. 2.

Referring toFIG. 2, in response to an instruction to create an image file from a user via the input device55, a program implementing the image file creation operation in shown inFIG. 2is loaded from HDD54to the main memory52b. Then, the head address thereof is set in a program counter of the MPU52a, and the image file creation operation is started. In this embodiment, data are recorded in the optical disk15in a multisession fashion. It is supposed that the optical disk15already contains at least one session. In addition, it is supposed that a new session can be additionally written in the optical disk15.

At step401, MPU52adetermines whether user data to be recorded in the optical disk15(hereinafter which are referred to as “target data”) are specified. If the target data are not specified, MPU52adisplays on the display device56a message to prompt the user to designate the target data. When the user determines one of a plurality of user data files stored in HDD54as the target data and designates the target data via the input device55, MPU52adetermines that the target data have been specified at step401, and the process control proceeds to step403. Here, for example, if the host50is connected to a network, the user can select user data located in the network as target data.

At step403, MPU52areads file management information from a predetermined position of the optical disk15via the optical disk device20. Here, the file management information includes pointer information indicative of recorded positions of user data in the optical disk15.

At step405, based on the read file management information, MPU52aconstructs a virtual tree structure indicative of logical relationship of the user data in RAM53.

At step407, by adding information regarding the target data in the tree structure, MPU52aconstructs an updated tree structure.

At step409, MPU52acreates image data of the target data based on the updated tree structure and stores the created image data in HDD54.

At step411, MPU52areads a disk ID recorded at a predetermined position IN the optical disk15via the optical disk device20. In this embodiment, the disk ID is configured as 4-byte data.

At step413, MPU52aadds the disk ID as identification information in an end portion of the image data of the target data in HDD54, as illustrated inFIG. 3.

At step415, MPU52adetermines whether the file name of the image data of the identification information attached target data is specified. If the file name is not specified, MPU52adisplays on the display device56a message to prompt the user to designate the file name. Then, if the user supplies the file name via the input device55, MPU52adetermines that the file name has been determined. Then, the process control proceeds to step417.

At step417, MPU52acreates an image file having the specified file name from the image data of the identification information attached target data.

At step419, MPU52astores the created image file in HDD54and terminates the image file creation operation.

An image file additionally write operation to additionally write an image file in the optical disk15according to the first embodiment is described with reference toFIG. 4.

FIG. 4is a flowchart of an image file additionally write operation executed by MPU52aof the information recording system10according to the first embodiment.

Referring toFIG. 4, in response to an instruction to additionally write an image file from a user via the input device55, a program implementing the image file additionally write operation shown inFIG. 4is loaded from HDD54to the main memory52b. Then, the head address thereof is set in a program counter of the MPU52a, and the image file additionally write operation is started. In this embodiment, it is supposed that a plurality of image files created in the above-mentioned image file creation operation are stored in HDD54.

At step451, MPU52adetermines whether an image file to be recorded in the optical disk15(hereinafter which are referred to as a “target image file”) is specified. If the target image file is not specified, MPU52adisplays on the display device56a message to prompt the user to designate the target image file. When the user determines one of a plurality of image files stored in HDD54as the target image file and designates the target image file via the input device55, MPU52adetermines that the target image file has been specified at step401, and the process control proceeds to step453.

At step453, MPU52areads the disk ID of the optical disk15from a predetermined position in the optical disk15via the optical disk device20.

At step455, MPU52areads the target image file from HDD54, and then extracts 4-byte data (IDa) from an end portion of the target image file.

At step457, MPU52adetermines whether the disk ID of the optical disk15and the 4-byte data IDa are the same. If the disk ID and the data IDa are the same, the process control proceeds to step459.

At step459, the 4-byte data IDa are deleted from the end portion of the target image file.

At step461, MPU52asends to the optical disk device20a recording request command to record the deleted target image file. As a result, it is possible to additionally write the target image file in the optical disk15via the optical disk device20. Then, MPU52aterminates the image file additionally write operation.

On the other hand, if the disk ID of the optical disk15and the data IDa are not the same at step457, the process control proceeds to step463.

At step463, MPU52adisplays on the display device56a message to indicate that the target image file is not suitable for the optical disk15. Then, MPU52aterminates the image file additionally write operation. Thus, the target image file is not additionally written in the optical disk15.

From the above description, it will be understood that a file creation part, a storage part, a determination part and an additionally write request part are implemented by MPU52aand programs executed by MPU52a. Specifically, steps403through417inFIG. 2implement the file creation part. Step419inFIG. 2implements the storing part. Steps453through457inFIG. 4implements the determination part. Steps459through461inFIG. 4implement the additionally write request part. However, the present invention is not limited to the implementation. The above-mentioned embodiment is described for just illustration and explanation. Also, a portion or all of the functional components implemented by the programs may be configured as hardware.

On the other hand, steps403through409inFIG. 2implements a first step of an image file creation method according to the first embodiment. Step411inFIG. 2implements a second step of the image file creation method. Steps413through417implement a third step of the image file creation method. Step419implements a fourth step of the image file creation method.

Also, step453inFIG. 4implements a first step of a recording method according to the first embodiment. Steps455and457implement a second step of the recording method. Steps459and461implements a third step of the recording method.

In this embodiment, among programs installed in HDD54, a program to execute the image file creation operation shown inFIG. 2implements the image file creation program, and a program to execute the image file additionally write operation shown inFIG. 4implements the image file additionally write program.

According to the first embodiment, when the host50is requested to create an image file in order to additionally write user data in an optical disk, MPU52aexecutes the image file creation operation. In this image file creation operation, image data of the user data are created, and the disk ID of the optical disk is obtained as identification information. In order to associate the disk ID with the image data, the disk ID is attached to the image data, resulting in the image file. Thus, for example, when the image file is additionally written later, it is possible to identify the additionally writable optical disk without logical inconsistency between the image file and existing data in the optical disk by referring to the disk ID associated with the image file in advance. As a result, it is possible to prevent such logical inconsistency between the image file to be additionally written and existing data in the optical disk.

Furthermore, when the host50is requested to additionally write an image file created in the image file creation operation, MPU52aexecutes the image file additionally write operation. In the image file additionally write operation, the disk ID of a target optical disk is obtained. Then, the disk ID associated with the image file is obtained, and it is determined whether the disk ID of the target optical disk and the disk ID associated with the image file are the same. Only if these disk IDs are the same, an image file recording request is sent to the optical disk device20. In other words, the disk ID associated with the image file is referred to before execution of the additionally write operation, and only if the disk ID associated with the image file and the disk ID of the target optical disk are the same, the image file additionally write operation is allowed to be executed. As a result, it is possible to additionally write the image file in the optical disk without logical inconsistency between the image file and existing data in the optical disk.

Although the disk ID is attached to the end portion of an image file in this embodiment, the present invention is not limited to the implementation. It is sufficient that the disk ID is included in the image file.

Also, although the disk ID, which is one of disk specific information items, is used as identification information of an optical disk in this embodiment, the present invention is not limited to the implementation. A disk specific information item other than the disk ID may be used. Furthermore, an information item other than the disk specific information items, for example, session information or track information of the optical disk, may be used.

A second embodiment of the present invention is described with reference toFIG. 5andFIG. 6. In the second embodiment, track information is used as identification information.

FIG. 5a flowchart of an image file creation operation executed by MPU52aof the information recording system10according to the second embodiment.

Referring toFIG. 5, MPU52adetermines whether target data are specified at step501as in step401. If the target data are not specified, MPU52adisplays on the display device56a message to prompt a user to designate the target data. When the user designates the target data via the input device55, the MPU52adetermines that the target data have been specified, and the process control proceeds to step503.

At steps503through509, MPU52aperforms the same operation as steps403through409.

At step511, MPU52aobtains the number of tracks recorded in the optical disk15via the optical disk device20.

At step513, MPU52aobtains the track lengths of individual recorded tracks of the optical disk15via the optical disk device20.

At step515, MPU52aconcatenates obtained data of the number of recorded tracks and obtained data of track lengths of individual recorded tracks so as to generate identification information on the optical disk15.

At step517, MPU52aattaches the identification information to an end portion of image data of the target data in HDD54.

At step519, MPU52adetermines whether the file name of the identification information attached image data of the target data is determined. If the file name is not determined, MPU52adisplays on the display device56a message to prompt the user to designate the file name. When the user designates the file name via the input device55, MPU52adetermines that the file name has been determined, and the process control proceeds to step521.

At steps521and523, MPU52aperforms the same operation as steps417and419. Then, MPU52aterminates the image file creation operation.

FIG. 6a flowchart of an image file additionally write operation executed by MPU52aof the information recording system10according to the second embodiment of the present invention.

Referring toFIG. 6, MPU52adetermines whether a target image file is specified at step551as in step451. If the target image file is not specified, MPU52adisplays on the display device56a message to prompt a user to designate the target image file. When the user determines the target image file from a plurality of image files in HDD54and supplies the target image file via the input device55, MPU52adetermines that the target image file has been specified, and the process control proceeds to step553.

At step553, MPU52aobtains the number of tracks recorded in the optical disk15via the optical disk device20.

At step555, MPU52aobtains track lengths of the individual tracks recorded in the optical disk15via the optical disk device20.

At step557, MPU52aconcatenates the obtained track number data and the obtained track length data to generate concatenated data (Da).

At step559, MPU52aobtains the number of bytes N of the concatenated data Da.

At step561, MPU52areads the target image file and extracts N-byte data (Db) from an end portion of the target image file.

At step563, MPU52adetermines whether the concatenated data Da and the N-byte data Db are the same. If the concatenated data Da and the N-byte data Db are the same, the process control proceeds to step565.

At step565, MPU52adeletes the N-byte data Db from the end portion of the target image file.

At step567, MPU52asends to the optical disk device20a recording request command to record the resulting target image file. As a result, it is possible to additionally write the target image file in the optical disk15via the optical disk device20. Then, MPU52aterminates the image file additionally write operation.

On the other hand, if the concatenated data Da and the N-byte data Db are not the same at step563, MPU52adetermines that the concatenated data Da and the N-byte data Db are not the same, and the process control proceeds to step569.

At step569, MPU52adisplays on the display device56a message to indicate that the target image file is not suitable for the optical disk15as in step463. Then, MPU52aterminates the image file additionally write operation. Thus, the target image file is not additionally written.

In the second embodiment, the number of recorded tracks and the track lengths of the individual recorded tracks are used as track information for identification information. However, other information may be used as the track information.

Alternatively, primary volume descriptor (PVD) information may be used as identification information of an optical disk.

A third embodiment of the present invention is described with reference toFIG. 7throughFIG. 9. In the third embodiment, it is supposed that identification information database is stored in HDD54as management information having correspondence between identification information items and image files. For example, the identification information database includes a file name field and an identification information field, as illustrated inFIG. 9A. In this case, it is possible to search records in the identification information database by using the file name as a search key. The illustrated identification information database includes three records.

FIG. 7a flowchart of an image file creation operation executed by MPU52aof the information recording system10according to the third embodiment of the present invention.

Referring toFIG. 7, MPU52adetermines whether target data are specified at step601as in step401. If the target data are not specified, MPU52adisplays on the display device56a message to prompt a user to designate the target data. If the user designates the target data via the input device55, the MPU52adetermines that the target data have been specified, and the process control proceeds to step603.

At steps603through609, MPU52aperforms the same operation as steps403through409.

At step611, MPU52aobtains PVD information from a predetermined position in the optical disk15via the optical disk device20.

At step613, MPU52aextracts a volume identifier VD (for example, VD=Volume04) from the obtained PVD information.

At step515, MPU52aextracts a volume creation data & time DTD (for example, DTD=200301241500) from the obtained PVD information. Here “200301241500” means the data & time “Jan. 24, 2002, 15:00”.

At step617, MPU52aconcatenates the volume identifier VD and the volume creation data & time DTD to generate identification information of the optical disk15. From the PVD information, it will be understood that the identification information is “Volume04200301241500”.

At step619, MPU52adetermines whether the file name of image data of the target data is designated as in step415. When the user designates the file name and supplies the file name via the input device55, MPU52adetermines that the file name has been specified, and the process control proceeds to step621. In this description, it is supposed that the user designates the file name as “file04”.

At step621, MPU52aconverts the image data of the target data into an image file having the designated file name.

At step623, MPU52astores the image file in HDD54.

At step625, MPU52aadds the identification information and the file name as a new record (record4) to the identification information database in HDD54, as illustrated inFIG. 9B. Then, MPU52aterminates the image file creation operation.

FIG. 8is a flowchart of an image file additionally write operation executed by MPU52aof the information recording system10according to the third embodiment of the present invention.

Referring toFIG. 8, MPU52adetermines whether a target image file is specified at step651as in step451. If the target image file is not specified, MPU52adisplays on the display device56a message to prompt a user to designate the target image file. When the user determines the target image file from a plurality of image files in HDD54and supplies the target image file via the input device55, MPU52adetermines that the target image file has been specified, and the process control proceeds to step653. In this description, it is supposed that the file name “file04” is specified.

At step653, MPU52asearches the identification information database by using the file name “file04” of the target image file as a search key so as to determine whether the corresponding record is in the identification information database. Here, since the corresponding record is included in the identification information database, MPU52adetermines that the corresponding record is included in the identification information database, and the process control proceeds to step655.

At step655, MPU52aextracts identification information Dc “Volume04200301241500” from the corresponding record.

At step657, MPU52aobtains PVD information recorded at a predetermined position of the optical disk15via the optical disk device20.

At step659, MPU52aextracts the volume identifier VD from the obtained PVD information.

At step661, MPU52aextracts the volume creation data and time DTD from the obtained PVD information.

At step663, MPU52aconcatenates the volume identifier VD and the volume creation data and time DTD so as to generate concatenated data.

At step665, MPU52adetermines whether the concatenated data and the identification information Dc are the same. If the concatenated data and the identification information Dc are the same, MPU52adetermines that the concatenated data and the identification information Dc are the same, and the process control proceeds to step667.

At step667, MPU52asends to the optical disk device20a recording request command to record the target image file. As a result, it is possible to additionally write the target image file in the optical disk15via the optical disk device20. Then MPU52aterminates an image file additionally write operation.

On the other hand, if the concatenated data and the identification information Dc are not the same at step665, MPU52adetermines that the concatenated data and the identification information Dc are not the same, and the process control proceeds to step669.

At step669, MPU52adisplays on the display device56a message to indicate that the target image file is not suitable for the optical disk15as in step463. Then, MPU52aterminates the image file additionally write operation. Thus, the target image file is not additionally written.

On the other hand, if there is no corresponding record at step653, MPU52adetermines that there is no corresponding record, and the process control proceeds to step671.

At step671, MPU52adisplays on the display device56a message to indicate that the target image file is not under management. Then, MPU52aterminates the image file additionally write operation. Thus, the target image file is not additionally written.

In the third embodiment, the volume identifier and the volume creation data and time are used as PVD information for the identification information. However, PVD information other than the volume identifier and the volume creation data and time may be used. Also, the identification information may be attached to the image file as in the disk ID. Also, a disk ID, session information or track information may be used as the identification information instead of or together with PVD information.

Alternatively, at least two of the disk ID, the track information, the PVD information and the session information may be used as identification information.

In the above-mentioned embodiments, the optical disk15is configured from CD-R. However, the present invention is not limited to this implementation. The present invention is applicable to any optical disk additionally writable in association with existing data. In addition, the present invention is applicable to a so-called “hybrid disk” including a read-only area and a writable or rewritable area.

Also, in the above-mentioned embodiments, the image file creation program and the image file additionally write program are stored in HDD54. However, theses programs may be stored in other type recording media such as CD-ROM (Compact Disk-Read Only Memory), a magneto optical disk, a flash memory and a flexible disk. In such a case, a drive device corresponding to each recording medium is provided to install the image file creation program and the image file additionally write program. In other words, it is sufficient that the image file creation program and the image file additionally write program can be loaded into the main memory52b.

The present application is based on Japanese Patent Priority Application No. 2002-027044 filed Feb. 4, 2003, the entire contents of which are hereby incorporated by reference.