Patent Application
20090087106
This application claims priority under 35 U.S.C. §119 from Japanese Patent Applications No. 2007-258908 filed on Oct. 2, 2007 and No. 2008-178159 filed on Jul. 8, 2008. The entire subject matters of the applications are incorporated herein by reference.
1. Technical Field
The following description relates to one or more techniques to save and manage image data that has been scanned (or transmitted via facsimile), copied, or printed by an image forming device.
2. Related Art
Japanese Patent Provisional Publication No. 2005-210257 discloses a facsimile machine provided with a function of automatically saving a copy of image data transmitted. In the facsimile machine, when a document is set and a command to transmit an image of the document is issued via an operation panel, image data of the document is stored in an image memory and sent to a MODEM. Then, the image data is transmitted to a terminal device as a transmission destination via a public line network.
When a mode for automatically saving image data is previously set, even after facsimile transmission, the image data stored in the image memory is, without being deleted, transmitted to a record control unit, in which data conversion is carried out for the image data to reduce an image thereof. Thereafter, an output from the record control unit is stored into a bitmap memory. At that time, sending source information such as a date and a time of the data transmission is created and stored as header information with the image data. The image data stored (as image data to be saved) in the bitmap memory is saved in a management server. Data left in the image memory are sequentially deleted in an order from a page for which the aforementioned process has been done.
In addition, Japanese Patent Provisional Publication No. 2004-118243 (hereinafter referred to as '243 Publication) discloses a network printing system that includes a print server configured to create and store log information regarding a printing operation based upon print data requested by a client device and user information specifying a user of the client device. Further, '243 Publication discloses that data, which is data into which the print data has been converted and data stored as a print log, can be used for re-printing as needed.
In the meantime, recently, with rising momentum to strengthen internal control in a company, it is required to leave information regarding a predetermined operation and data used in the operation so as to find an improper use of the information and data and/or falsification thereof. Further, by leaving the information regarding the predetermined operation and the data used in the operation, it becomes possible to reuse them.
Here, it is supposed that there is a great deal of data to be handled. Not only in the case where the data is saved in a format to secure quality of the data but also even in the case where a capacity of each data to be saved is reduced, as the number of the data increases, a quantity of the data to be saved is greater consequently. Thus, for instance, a company may have a problem of capacity shortage of the management server.
Aspects of the present invention are advantageous to provide one or more improved management devices, and methods and computer readable media therefor that make it possible to efficiently utilize a storage capacity of a storage unit thereof.
According to aspects of the present invention, a management device is provided, which is configured to be connectable with a storage device configured to store therein image data. The management device includes a determining unit configured to determine whether the image data stored in the storage device satisfies a predetermined condition, and a size reducing unit configured to reduce a size of the image data in accordance with a rule depending on the determination by the determining unit.
Optionally, the predetermined condition may include a condition regarding a storage period during which the image data has been stored in the storage device.
In some aspects of the present invention, when target image data satisfies a predetermined condition (for example, when the image data satisfies a condition where the storage period of the image data exceeds a predetermined period), the size of the image data is reduced in accordance with a predetermined rule. Therefore, it is possible to efficiently utilize a storage capacity of the storage device.
According to aspects of the present invention, further provided is a method to manage image data stored in a storage device, the method which includes a determining step of determining whether the image data stored in the storage device satisfies a predetermined condition, and a size reducing step of reducing a size of the image data in accordance with a rule depending on the determination made in the determining step.
The method configured as above can provide the same effect as the aforementioned management device. Namely, it is possible to efficiently utilize the storage capacity of the storage device.
According to aspects of the present invention, further provided is a computer readable medium having computer readable instructions stored thereon to be executed by a computer connectable with a storage device configured to store therein image data. The instructions cause the computer to perform a determining step of determining whether the image data stored in the storage device satisfies a predetermined condition and a size reducing step of reducing a size of the image data in accordance with a rule depending on the determination made in the determining step.
The computer readable medium configured as above can provide the same effect as the aforementioned management device and method. That is, it is possible to efficiently utilize the storage capacity of the storage device.
It is noted that various connections are set forth between elements in the following description. It is noted that these connections in general and, unless specified otherwise, may be direct or indirect and that this specification is not intended to be limiting in this respect. Aspects of the invention may be implemented in computer software as programs storable on computer-readable media including but not limited to RAMs, ROMs, flash memory, EEPROMs, CD-media, DVD-media, temporary storage, hard disk drives, floppy drives, permanent storage, and the like.
Hereinafter, an embodiment according to aspects of the present invention will be described with reference to the accompany drawings.
The history management server 13 is provided with a control unit 31 that includes a CPU, a ROM, and a RAM, an input unit 32 that includes a keyboard and a mouse, a communication unit 33 configured to communicate with each device on the network, a display unit 34 that includes an LCD monitor, and a storage unit 35 that includes a hard disk drive (HDD) configured to store therein various programs and data.
Meanwhile, the MFP 11 is provided with a control unit 21 that includes a CPU, a ROM, and a RAM, a storage unit 22 configured to store therein setting information, a communication unit 23 configured to communicate with each device on the network, a printing unit 24 configured to form an image on a sheet in a printing method such as a laser printing method and an inkjet printing method, a scanning unit 25 configured to optically scan a document placed on a document loading unit and create image data, an operation display unit 26 that includes various user-operable keys and a display, and a line communication unit 27 configured to perform data communication with external communication devices via a public line.
The MFP 11 is provided with a plurality of functions such as a facsimile function, a scanner function, a printer function, and a copy function. The MFP 11 includes the operation display unit 26 provided at an upper front side of a main body thereof, and the operation display unit 26 includes input keys for inputting a name of a transmission destination, a facsimile number of the transmission destination, and a mail address of the transmission destination. Further, the operation display unit 26 includes a switch button for switching a mode such as a facsimile mode and a printer mode as well as a start button and a stop button. Especially, in the present embodiment, the operation display unit 26 is provided with a significant key for inputting an identifier (an exceptional keyword) for a below-mentioned reduction process for reducing an image size.
In the printer function of the MFP 11, when the control unit 21 receives a print command with print data from a client PC 12 via the network, image data is created based upon the print data, and a printing operation is performed on a sheet by the printing unit 24 in accordance with the print data. In the scanner function, a document placed on the document loading unit is scanned by the scanning unit 25, and image data representing a scanned image of the document is created and stored in a predetermined device on the network.
In the copy function of the MFP 11, a document placed on the document loading unit is scanned by the scanning unit 25, and image data representing a scanned image of the document is created. Then, the image based upon the image data is printed on a sheet by the printing unit 24. In addition, in the facsimile function, when a fax transmission command is inputted via the operation display unit 26, a document is scanned by the scanning unit 25, and facsimile data is created based upon a scanned image of the document and then transmitted from the line communication unit 27 via the public telephone line network. Meanwhile, when facsimile data is received from an external fax machine via the line communication unit 27, the facsimile data received is converted into image data, and the image data is printed on a sheet by the printing unit 24.
The MFP 11 is provided with a file creating program adopted to create a file of image data created in an operation of each function of the MFP 11 and store the created file in a predetermined location of the history management server 13. Meanwhile, the history management server 13 includes a history management program stored therein that is adopted to perform a reduction process in accordance with a predetermined rule in which a storage period during which image data sent by the MFP 11 has been stored in associated with a reduction rate for reducing a size of the image data.
The history management program of the history management server 13 is configured to reduce a size of stored image data by changing a compression ratio of the image data in stages in accordance with a setting as shown in
For example, it is supposed that the identifier “significant” is inputted only for the setting period of 365 days. In this case, the image data is compressed at the compression ratio 80% when a storage period for the image data of 60 days (2 months) has elapsed. However, when a storage period of 365 days (1 year) has elapsed, the compression of the image data at the compression ratio 30% is prohibited owing to the identifier “significant.” Accordingly, until a period of 5 years elapses after a period of 60 days has passed, the image data is saved in a state compressed at the compression ratio 80%. Then, when a period of 5 years has elapsed, the image data is deleted.
Further, when the identifier “significant” is inputted for the setting period of 1825 days, the image data is permanently saved. In this case, when the identifier “significant” is not inputted for any of the other setting periods, the image data is permanently saved after being compressed at a compression ratio of 80% or 30%. For example, unless the identifier “significant” is inputted for the setting period of 60 days, the image data is compressed at the compression ratio 80%. Additionally, unless the identifier “significant” is inputted for the setting period of 365 days, the image data is permanently saved in a state compressed at the compression ratio 30%. It is noted that, when the identifier “significant” is inputted for all the setting periods, the image data is permanently saved without being compressed.
In addition, the MFP 11 is configured to convert the image data into a file with a file name including the identifier “significant not only via the significant key of the operation display unit 26 based upon a user's intention but also automatically (see S115). Specifically, for instance, specific characters “FOR INTERNAL USE ONLY” are stored as a keyword in a predetermined area of the storage unit 22. Then, the control unit 21 determines through a character analysis whether the characters corresponding to the keyword are included in the image data scanned by the scanning unit 25. When it is determined that the characters corresponding to the keyword are included in the image data, the image data is automatically converted into a file with a file name including the identifier “significant” (see S115).
Further, the MFP 1 is configured to automatically convert data stored in a predetermined storage device (a predetermined folder) on the network via the LAN cable 10 into a file with a file name including the identifier “significant” (see S115). Namely, the storage unit 22 stores a predetermined storage location as a keyword in a predetermined area thereof. When the control unit 21 determines, for example, that data to be printed is identical to data stored in the predetermined storage location stored as a keyword in the storage unit 22, the data to be printed is automatically converted into a file with a file name including the identifier “significant” (see S115). Furthermore, an identification symbol is stored as a keyword in a predetermined area of the storage unit 22. The control unit 21 determines whether a file name of the data to be printed includes the identification symbol. When it is determined that the file name of the data to be printed includes the identification symbol, the data is automatically converted into a file with a file name including the identifier “significant” (see S115). It is noted that the data to be printed includes a storage location and a file name as relevant information thereof.
Next, a file creating program to be executed by the MFP 1 will be described.
As described above, the MFP 11 performs a operation of each function such as the copy function. The control unit 21 always monitors the operation. Specifically, the control unit 21 always monitors each of whether a copy operation is performed (S101), whether fax transmission is performed (S102), whether fax data is received (S103), whether a printing operation is performed (S104), and whether a scanning operation is performed (S105). When any of the operations is not recognized (S101-S105: No), the above monitoring is repeatedly carried out.
Meanwhile, either of the operations is recognized, the MFP 11 accesses the history management server 13 via the network. Specifically, the MFP 11 accesses a predetermined one of folders provided as storage locations of image data in the storage unit 35 of the history management server 13.
When performing a copy operation (S101: Yes), the MFP 11 accesses the copy folder 121 of the history management server 13 (S106). When performing fax transmission without executing a copy operation (S102: Yes), the MFP 11 accesses the fax transmission folder 122 of the history management server 13 (S107). When fax data is received without performing a fax transmission as well (S103: Yes), the MFP 11 accesses the copy folder 123 of the history management server 13 (S108). When performing a printing operation without receiving any fax data (S104: Yes), the MFP 11 accesses the print folder 124 of the history management server 13 (S109). When performing a scanning operation without performing a printing operation (S105: Yes), the MFP 11 accesses the scan folder 125 of the history management server 13 (S110).
In the meantime, in the history management server 13, as illustrated in
Subsequently, the MFP 11 converts image data used as target data in a copy operation or a fax operation into a file with a file name attached thereto. In that time, the conversion of the image data into a file is made with conditions or without any condition. Thus, the MFP 11 checks whether any condition is given in each operation (S112 and S113). Specifically, in S112, it is checked whether the significant key of the operation display unit 26 has been pressed in an operation such as a copy operation and fax transmission. Meanwhile, when a document is transmitted via fax, even though the significant key is not pressed, in S113, the control unit 21 determines through the character analysis whether characters corresponding to a keyword stored in the storage unit 22 are included in image data scanned.
Then, in a step of converting the image data into a file after that (S114 or S115), a name of a function performed by the MFP 11 and a three-digit serial number in the present month for each function are added to a name of the file. When the significant key has not been pressed in the copy operation (S112: No), and any keyword stored in the storage unit 22 is not recognized (S113: No), for instance, a file name as shown by files 311 or 313 in
Meanwhile, when the significant key has been pressed in the copy operation (S112: Yes) or a keyword stored in the storage unit 22 is recognized in the image data scanned (S113: Yes), as shown by a file 312 in
Next, the file, into which the image data is converted in S114 or S115, is compressed in a zip format in the present embodiment. The compressed file is stored into a predetermined folder of the history management server 13 as illustrated in
Thus, image data is transmitted as a file with a predetermined file name attached thereto by the MFP 11 to the history management server 13, and sequentially stored into a predetermined folder of the storage unit 35. On the other hand, in the history management server 13, image data stored therein is compressed at a predetermined compression ratio depending on an elapsed period in order to reduce the capacity of the image data in stages. Such a compressing operation is performed by the control unit 31, more specifically, with an image history management program that executes a history management process shown in
In the history management process, firstly, management list information (see a compression list 40 in
Meanwhile, when there is a file of which the storage period exceeds any of the setting periods (S203: Yes), it is determined whether the image data is compressed at a specified compression ratio (S204). The history management server 13 includes the compression list 40 created therein, as shown in
Meanwhile, when it is determined from the compression list 40 that the image data of the target file has not been compressed (S204: No), it is determined whether an identifier is included in a file name of the target file (S205). In the case where the image data is saved as a file of which a file name includes the identifier “significant” as the file 312 shown in
In S207, in order to delete the image data, the corresponding file thereof is deleted. Further, it is determined whether there is any file in the month folder in which the file had been present (S208). When all files have been deleted and the month folder is vacant (S208: Yes), the vacant month folder is also deleted (S209).
In the storage unit 35, a file name list to save therein file names of files deleted in the aforementioned manner is provided. When the image data is deleted in S207, the file name of the image data is additionally recorded into the list. Meanwhile, when there is a file left in the month folder (S208: No), the present process goes back to S203, in which it is determined whether there is a file of which the storage period exceeds any of the setting periods.
Additionally, in S210, the image data is compressed at a compression ratio corresponding to a setting period that the storage period of the image data is determined to exceed in S203. Specifically, when the storage period of the image data exceeds 60 days (2 months), the image data is compressed at the compression ratio 80%. When the storage period of the image data exceeds 365 days (1 year), the image data is compressed at the compression ratio 30%.
As mentioned above, the image data is stored in the history management server 13 as a file compressed in the zip format by the MFP 11. In order to compress the image data, firstly, the zip file is developed and the bitmap image data is extracted therefrom (S301). In a compressing operation corresponding to the setting period of 60 days, the image data of 100% is compressed at the compression ratio 80%. In a compressing operation corresponding to the setting period of 365 days, the image data, which has been compressed at the compression ratio 80%, is compressed to attain the compression ratio 30% (S302). Thus, the image data compressed as above is saved as a file re-compressed in the zip format in the original folder in an overwriting manner (S303).
Each time the compressing operation is performed for a single piece of image data, information on the image data is registered in the compression list 40 shown in
Referring back to
According to the present embodiment, by saving image data copied or faxed, it is possible to utilize the image data when it is needed. For example, when a user attempts to confirm what the image data represents or to fax the image data again, such image data can be utilized. However, in most cases, a utility value (frequency of reuse) of such information decreases as time goes by. For this reason, in the present embodiment, the compression ratio of the image data, of which the utility value declines as time passes, is reduced in stages to lessen a capacity of the image data. Thereby, it is possible to cover shortage of a storage capacity of the history management server 13. On the other hand, in order to reproduce significant image data in a crisp state, the compression of the image data is restricted depending on significance of the image data. Further, when significant image data is handled, the image data is stored such that the compression of the image data is restricted through the automatic recognition of the identifier included in a file name of the image data. Therefore, it is possible to leave the image data, for example, as an evidence of an unauthorized use of the image data.
Hereinabove, the embodiments according to aspects of the present invention have been described. The present invention can be practiced by employing conventional materials, methodology and equipment. Accordingly, the details of such materials, equipment and methodology are not set forth herein in detail. In the previous descriptions, numerous specific details are set forth, such as specific materials, structures, chemicals, processes, etc., in order to provide a thorough understanding of the present invention. However, it should be recognized that the present invention can be practiced without reapportioning to the details specifically set forth. In other instances, well known processing structures have not been described in detail, in order not to unnecessarily obscure the present invention.
Only exemplary embodiments of the present invention and but a few examples of its versatility are shown and described in the present disclosure. It is to be understood that the present invention is capable of use in various other combinations and environments and is capable of changes or modifications within the scope of the inventive concept as expressed herein. For example, according to aspects of the present invention, the following changes and modifications are possible.
In the aforementioned embodiment, the history management server 13 serves as a management server. However, for example, the MFP 11 connected with an external storage device 28 as shown in
Further, in the aforementioned embodiment, image data is converted into a file with a file name including the identifier that provides the restriction in compressing the image data. Alternatively, a list with a flag given thereto as an identifier may be created. For example, when image data is stored in a predetermined folder of the history management server 13 as shown in
Further, in the aforementioned embodiment, when the compression ratio of image data is changed in stages, the zip format is exemplified as a compression format for compressing a file into which the image data is converted. However, the compression format may include other formats such as a lossless compression format in which there is no change found in image quality between before and after a compressing operation or an expanding operation for the image data, and an original image of the image data can completely be restored after the expanding operation and a lossy compression format in which it is possible to attain a lower compression ratio (more compressed image data), yet the original image of the image data cannot completely be restored after the expanding operation. For instance, a JPEG format may be employed as the lossy compression format, and a GIF format may be employed as the lossless compression format.
In order to reduce the size of the image data, a pixel skipping operation may be performed for the image data as well as the compressing operation described in the aforementioned embodiment. For example, in the pixel skipping operation, pixel data is deleted every some lines in each of vertical and horizontal directions of the image data to create new image data. It is noted that, preferably, following the pixel skipping operation, an interpolating operation may be executed. Furthermore, the size of the image data may be reduced by decreasing the number of gray levels (i.e., tone levels) or the number of colors of the image data. For instance, the number of gray levels of the image data may be reduced in stages depending on predetermined setting periods from 1024 shades of gray to 256 shades of gray. Further, the number of colors of the image data may be reduced in stages depending on predetermined setting periods from a color image to a monochrome image. In addition, the size of the image data may be reduced by a combination of various operations. For example, when the storage period of the image data is relatively short, the compressing operation may be performed for the image data. Meanwhile, when the storage period of the image data is relatively long, the pixel skipping operation, the operation of reducing the number of gray levels, or the operation of reducing the number of colors may be performed for the image data. It is noted that the “size” of the image data denotes a data size of the image data, i.e., a data capacity of the image data.
Further, in the above description, the history management server 13 or the storage device 28 connected with the MFP 11 is provided as a storage location to store the image data. However, a client PC 12 on the network may be specified as the storage location. Additionally, the setting periods, the compression ratios, or the number of steps for compressing the image data in stages may be arbitrarily set.
In addition, “significant_a,” “significant_b,” and “significant_c,” may be set as identifiers as shown in
Further, for instance, it is supposed that predetermined storage locations x, y, and z are stored as keywords in the predetermined area of the storage unit 22. In this case, when the storage location x is recognized in the step S113, the image data may be converted into a file with a file name including “significant_a.” Meanwhile, when the storage location y is recognized in S113, the image data may be converted into a file with a file name including “significant_b.” Furthermore, when the storage location z is recognized in S113, the image data may be converted into a file with a file name including “significant_c.” Thereby, depending on the type of the keyword recognized, it is possible to change the setting of the compressing operation.
When identification symbols x, y, and z are stored as keywords in the predetermined area of the storage unit 22, for example, in the case where the identification symbol x is recognized in S113, the image data may be converted into a file with a file name including “significant_a” in the same manner as described above. It is noted that, in S205, it may be determined whether an identifier (“significant_a,” “significant_b,” or “significant_c”) corresponding to a setting period which a storage period of a target file is determined to exceed is included in a file name of the target file.
Further, when “significant_a,” “significant_b,” and “significant_c” are set as identifiers as illustrated in
| Number | Date | Country | Kind |
|---|---|---|---|
| 2007-258908 | Oct 2007 | JP | national |
| 2008-178159 | Jul 2008 | JP | national |
