JP2008160592A - Image processor - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an image processor capable of improving performance while suppressing influence on successive erasure for preventing the leakage of information to a minimum. <P>SOLUTION: The image processor has an auxiliary memory for storing image data and erases image data stored in the auxiliary memory after the image data is used by an application. The image processor has a means of determining whether or not there is any unused auxiliary memory when a new application requests the use of auxiliary memory and a means of permitting the use of auxiliary memory to the new application when there is an unused auxiliary memory. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to an image processing apparatus such as an MFP (Multi Function Printer), and more particularly to a technique for controlling execution of an application (application) while an auxiliary storage device such as an HDD (Hard Disk Drive) is being erased.

  In general, an image processing apparatus such as an MFP includes an auxiliary storage device such as an HDD for storing image data to be processed.

  With recent improvements in security awareness, so-called sequential erasure is performed to erase image data from the HDD immediately after image processing in order to prevent information leakage from the HDD (such as discarding or acquiring data from a stolen HDD). Is being carried out.

On the other hand, Patent Document 1 discloses a digital image forming apparatus that improves confidentiality by arbitrarily erasing image data stored in an image memory.
JP-A-9-284518

  As described above, sequential erasure is an effective method for preventing information leakage from the HDD, but sequential erasure requires processing such as repeatedly recording random data in the data recording area of the HDD. Therefore, the time required for processing is long.

  Therefore, when apps such as copy and scan are executed continuously, the probability of encountering during HDD sequential erasure is high, and during that time, sequential erasure is preferentially executed, so that the execution of the subsequent apps is awaited. As a result, the performance of the entire apparatus is degraded.

  Patent Document 1 does not consider performance in an environment where there are a plurality of operation applications.

  The present invention has been proposed in view of the above-mentioned conventional problems, and the object of the present invention is to improve performance while minimizing the effect on sequential erasure for preventing information leakage. An image processing apparatus may be provided.

  In order to solve the above problems, according to the present invention, an auxiliary storage device for storing image data is provided as described in claim 1, and the image data is stored in the auxiliary storage device after use by an application. An image processing device for erasing image data, and when there is a request to use an auxiliary storage device from a new application, means for determining whether there is an unused auxiliary storage device, and an unused auxiliary storage device If there is, the gist of the image processing apparatus includes means for causing the new application to use the auxiliary storage device.

  In addition, as described in claim 2, when there is no unused auxiliary storage device in the image processing device according to claim 1, the security level of the application using the auxiliary storage device being erased and the new A means for comparing the execution level of a new application and a means for interrupting erasure of the auxiliary storage device being erased and causing the new application to use the auxiliary storage device when the level of the new application is high can do.

  According to a third aspect of the present invention, in the image processing device according to the second aspect, an allowable operation is performed based on a security level of an app that uses the auxiliary storage device being erased and an execution level of a new app. A table to be referred to may be provided.

  According to a fourth aspect of the present invention, in the image processing device according to the second aspect of the present invention, a tag in which the security level of an application using the image data is recorded in the image data stored on the auxiliary storage device. Information can be included.

  According to a fifth aspect of the present invention, in the image processing apparatus according to the fourth aspect, the security level of the tag information is evaluated relative to other accumulated data and written to the tag information. it can.

  In addition, as described in claim 6, when there is no unused auxiliary storage device in the image processing device according to claim 1, a means for causing a new application to use the image memory instead of the auxiliary storage device Can be provided.

  According to a seventh aspect of the present invention, in the image processing apparatus according to the sixth aspect, when an unused auxiliary storage device is generated by erasing the auxiliary storage device, the auxiliary storage device includes The image data can be transferred from the image memory.

  Further, as described in claims 8 to 10, it can be configured as an auxiliary storage medium erasing control method.

  In the image processing apparatus of the present invention, performance can be improved while minimizing the effect on sequential erasure for preventing information leakage.

  Hereinafter, preferred embodiments of the present invention will be described.

<System configuration>
FIG. 1 is a diagram illustrating a configuration example of an image processing apparatus according to an embodiment of the present invention.

  In FIG. 1, an image processing apparatus includes an image memory 3 connected to a bus 1 via an image memory controller 2, HDDs 51 and 52 connected to the bus 1 via an HDD controller 4, and a bus 1 A scanner 7 and a plotter 8 connected to each other via an image forming module 6, a CPU (Central Processing Unit) 9, a ROM (Read Only Memory) 10, and a RAM (Random Access Memory) 11 also connected to the bus 1. I have.

  Further, when the applications 13A, 13B, 13C,... Configured by software on the CPU 9, the ROM 10, and the RAM 11, the application control module 12 that controls these applications, and a new application are activated during the execution of deletion And a security management module 14 that determines which should be prioritized based on the security level and the execution level.

  In the figure, two HDDs are used. However, two or more HDDs may be used, and in the case of memory replacement (FIGS. 9 and 10) described later, one may be used.

  FIG. 2 is a diagram showing a data recording state in the HDDs 51 and 52, which is divided into areas 5a used by each application, and tag information 5b is provided at the head of the area 5a. The tag information 5b includes information such as an application used, an erased state (information indicating how far the data has been erased), a security level, an execution level, a start address, and a final address.

  FIG. 3 is a diagram showing an example of the arrangement of image data in the image memory 3 and the HDDs 51 and 52. Image data composed of data portions # 1 to # 3 as shown in FIG. When it is arranged in a VM (Virtual Memory) space managed by the Operating System, it is stored out of order in an empty area as shown in FIG. Access) Inefficient transfer. Therefore, in this embodiment, the image data is stored in the continuous area memory space as shown in (c) in order, and the data arrangement in the HDDs 51 and 52 is also performed in the continuous area as shown in (d). By doing so, the efficiency of DMA transfer and erasure is improved. The securing of the continuous area in the HDDs 51 and 52 can be realized by a raw format in UNIX (registered trademark) or the like. In this case, DMA transfer between the HDDs 51 and 52 and the image memory 3 is performed using raw data.

<Operation>
4 and 5 are sequence diagrams illustrating an example of processing according to the embodiment. In addition, illustration of the response (response) with respect to a request | requirement (request) is abbreviate | omitted. The HDD controller 4 can recognize the status of the subordinate HDDs 51 and 52, and the image forming module 6 can recognize the status of the subordinate scanner 7.

  In FIG. 4, when the application control module 12 activates the application 13A (including application instance generation) (step S1), the application 13A makes an HDD use request (use one) to the HDD controller 4 (step S2). .

  Since both of the HDDs 51 and 52 are unused, the HDD controller 4 makes an HDD use request to one HDD 51 (step S3).

  Next, the application 13A makes an image transfer request to the HDD controller 4 (step S4), and then makes an image transfer request to the image forming module 6 (step S5).

  The image forming module 6 makes an image transfer request to the scanner 7 (step S6), and transfers an image from the scanner 7 to the HDD 51 (step S7). When the image transfer is completed, the image forming module 6 notifies the application 13A of the end of the image transfer. (Step S8).

  The application 13A uses an image such as scan distribution using the image data transferred to the HDD 51 (step S9), and upon completion, issues an HDD erasure request to the HDD controller 4 (step S10).

  The HDD controller 4 issues an HDD erasure request to the HDD 51 (step S11), and the HDD 51 starts erasure and enters erasure (step S12).

  Thereafter, when the application control module 12 activates a new application 13B (including application instance generation) (step S13), the application 13B makes an HDD use request (use one) to the HDD controller 4 (step S14). .

  Since the HDD 51 of the HDDs 51 and 52 is being used (erased), the HDD controller 4 requests the unused HDD 52 to use the HDD (step S15).

  Next, the application 13B makes an image transfer request to the HDD controller 4 (step S16), and then makes an image transfer request to the image forming module 6 (step S17).

  The image forming module 6 makes an image transfer request to the scanner 7 (step S18), and transfers an image from the scanner 7 to the HDD 52 (step S19). When the image transfer is completed, the image forming module 6 notifies the application 13B of the end of the image transfer. (Step S20).

  The application 13B uses an image such as scan delivery by using the image data transferred to the HDD 52 (step S21), and upon completion, makes an HDD erasure request to the HDD controller 4 (step S22).

  The HDD controller 4 issues an HDD erasure request to the HDD 52 (step S23), and the HDD 52 starts erasing and enters erasing (step S24).

  In this way, even if one of the HDDs 51 and 52 is in use, a new application can be executed using an unused HDD, so that it is not necessary to wait for the end of sequential erasure, and performance degradation is prevented. Can do.

  Next, in FIG. 5, when the application control module 12 starts a new application 13C (including generation of an application instance) (step S25), the application 13C makes an HDD use request (use two) to the HDD controller 4. (Step S26).

  The HDD controller 4 is in use (erasing) of the HDDs 51 and 52, and the HDD 51 is not used, but since two HDDs are requested to be used, the application 13B using the HDD 52 and a new application 13B are used. In consideration of the security level and execution level of the application 13C, it is determined whether the erasure is continued as it is to wait for the application 13C, or the erasure is interrupted and the application 13C is executed (details will be described later). Here, if it is determined that the new application 13C is to be executed, an erase interruption request is made to the HDD 52 being erased (step S27), and an HDD use request is made to an unused HDD 51 (step S28).

  Next, the application 13C makes an image transfer request to the HDD controller 4 (step S29), and then makes an image transfer request to the image forming module 6 (step S30).

  The image forming module 6 makes an image transfer request to the scanner 7 (step S31), transfers the image from the scanner 7 to the HDDs 51 and 52 (step S32), and when the image transfer ends, the image forming module 6 ends the image transfer to the application 13C. Is notified (step S33).

  The application 13C uses an image such as scan distribution using the image data transferred to the HDDs 51 and 52 (step S34), and upon completion, makes an HDD erasure request to the HDD controller 4 (step S35).

  The HDD controller 4 issues an HDD erasure request to the HDDs 52 and 51 (steps S36 and S38), and the HDDs 52 and 51 start erasing and enter erasure (steps S37 and S39).

  Thereafter, when the erasure of the HDD 52 is completed, the HDD controller 4 notifies the application 13B of the end of interruption (step S40), and the application 13B makes a request to resume erasure to the HDD controller 4 (step S41). Note that the interruption end notification (step S40) from the HDD controller 4 to the application 13B and the deletion resumption request (step S41) from the application 13B to the HDD controller 4 may be omitted.

  The HDD controller 4 requests the HDD 52 to resume erasure (step S42), and the HDD 52 resumes erasure and enters erasure (step S43).

  In this way, even when the requested number of HDDs is in use and cannot be secured, a new application with a high security level and execution level can be executed. A decrease can be prevented.

  FIG. 6 is a flowchart showing a processing example of the HDD controller 4 at the time of HDD use request from the applications 13A to 13C (S2, S14 in FIG. 4, S26 in FIG. 5).

  In FIG. 6, when the HDD controller 4 receives an HDD use request from the applications 13A to 13C, the HDD controller 4 determines some number of HDDs in use (step S51). The number of used HDDs is determined (step S52), and when the number of used HDDs is two or when the number of used HDDs is one and the number of used HDDs of the new application is two, the number of used apps is further increased. The security level and execution level of the new application are determined (step S53).

  When the number of used HDDs is zero, the operation of the new application by the unused HDD is permitted (step S54). When the number of used HDDs is one and the number of used HDDs of the new application is one, The operation of the new application by the unused HDD is permitted (step S55).

  Also, if the number of HDDs in use is 2 or the number of HDDs in use is 1 and the number of HDDs used by the new application is 2 and the relative level of the new application is low, the new application is deleted. Wait until completion (step S56). If the relative level of the new application is high, the erasure is interrupted and the operation of the new application is allowed (step S57).

  FIG. 7 is a diagram showing an example of operation determination based on the security level and the execution level in S53 of FIG. 6, and the determination is made by referring to the table.

  In the example of FIG. 7, when the security level of the app being deleted is “1 (highest)”, priority is given to deletion regardless of the execution level of the new app, and when the security level of the app being deleted is “2 (medium)” When the execution level of the new application is “L (low)”, priority is given to deletion. When the security level of the application being deleted is “3 (low)”, the security level of the new application is “3” and the execution level is “L”. (Low) "gives priority to deletion, and in other cases, priority is given to execution of the new application. It is also possible to subdivide the level.

  FIG. 8 is a diagram showing an example of rewriting the security level of tag information. That is, the operation determination based on the security level shown in FIG. 7 is obtained for the application being erased from the tag information 5b included in the area 5a of the HDDs 51 and 52 shown in FIG. If it is, it may not accurately represent the relative level between apps.

  Therefore, the security level is evaluated relative to other stored data and written in the tag information 5b, so that the order of erasure can be easily determined.

  In FIG. 8, when the security level of the tag information 5b1 of the area 5a1 of an application is “1” and the security level of the tag information 5b2 of the area 5a2 of another application is “2” as shown in FIG. When another application uses the area, as shown in (b), the security level of the tag information 5b1 in the area 5a1 is "2", the security level of the tag information 5b2 in the area 5a2 is "3", and the tag in the area 5a3 The security level of the information 5b3 is rewritten to “1”.

  9 and 10 are sequence diagrams illustrating another processing example of the embodiment. Although the figure shows a case where there are two HDDs, the present invention can also be applied to a case where there is one HDD.

  In FIG. 9, it is assumed that the application 13A is being erased using the two HDDs 51 and 52 (steps S61 and S62).

  When the application control module 12 starts a new application 13B (including application instance generation) (step S63), the application 13B makes an HDD use request (use one) to the HDD controller 4 (step S64). ).

  Since both the HDDs 51 and 52 are being used (erased), the HDD controller 4 makes an image memory use request to the image memory controller 2 as a memory substitute (step S65), and the image memory controller 2 uses the image memory. 3 is used (step S66).

  Next, the application 13B makes an image transfer request to the HDD controller 4 (step S67), and then makes an image transfer request to the image forming module 6 (step S68).

  The image forming module 6 makes an image transfer request to the scanner 7 (step S69), transfers the image from the scanner 7 to the image memory 3 (step S70), and when the image transfer is completed, the image forming module 6 transfers the memory to the application 13B. The end is notified (step S71). If the capacity is insufficient while the image memory 3 is being used, the processing is temporarily suspended and the end of HDD erasure is waited for.

  Next, in FIG. 10, when the HDD controller 4 finishes erasing any of the HDDs 51 and 52, the HDD controller 4 notifies the image memory controller 2 of the end of erasure (step S72) and transfers the image from the image memory 3 to the HDD 51 ( In step S73), when completed, the image memory controller 2 notifies the application 13B of the end of image transfer (step S74).

  The application 13B uses an image such as scan distribution by using the image data transferred to the HDD 51 (step S75). When the application 13B ends, the application 13B issues an HDD erasure request to the HDD controller 4 (step S76).

  The HDD controller 4 issues an HDD erasure request to the HDD 51 (step S77), and the HDD 51 starts erasure and enters the erasure (step S78).

  As described above, even when the requested number of HDDs is in use and cannot be secured, the image data is temporarily transferred to the image memory 3 and then transferred to the HDD when the HDD becomes unused. Since the transfer is performed, it is not necessary to wait for the end of the sequential erasure, and the performance can be prevented from deteriorating.

<Summary>
As described above, the embodiment of the present invention has the following advantages.
(1) By preparing two HDDs, a new application can operate without degrading performance by using another HDD even when one HDD is sequentially erased.
(2) If a new application wants to use the HDD during the sequential erasure of the HDD, it is necessary to compare the security level of the application being erased with the execution level of the new application to determine the processing order. Realizes security requirements and can operate without compromising performance within that premise.
(3) By determining the processing order by referring to the table, the order can be determined quickly and easily.
(4) If the security level of the data being erased is high, the priority will be given to the erasure regardless of the execution level of the application, thereby realizing the necessary security requirements and operating without compromising performance. can do.
(5) When image data is stored in the HDD, the order of processing can be quickly determined by adding the security level and execution level of the target application as tag information.
(6) If image memory is available even during sequential deletion, a new application is executed using the image memory. After the sequential deletion is completed, image data is transferred from the image memory to the HDD. Copy and continue processing. Thereby, a new application can be executed even while the HDD is being used.
(7) If the capacity becomes insufficient while the image memory is being used, the process is temporarily suspended and the end of erasing of the HDD is awaited. Thereby, necessary security requirements can be realized.
(8) By transferring raw data between the HDD and the image memory to raw data, it can be quickly transferred by DMA transfer.
(9) When waiting for execution of a new application during sequential erasure of the HDD, it can be displayed on the UI to notify the user. As a result, the user can know the reason why the execution is interrupted, and the operation is not questioned.
(10) A security level is set for tag information of image data stored in the HDD, and the security level is evaluated relative to other stored data and written to the tag information, so that the order of erasure can be easily determined. it can.

  The present invention has been described above by the preferred embodiments of the present invention. While the invention has been described with reference to specific embodiments, various modifications and changes may be made to the embodiments without departing from the broad spirit and scope of the invention as defined in the claims. Obviously you can. In other words, the present invention should not be construed as being limited by the details of the specific examples and the accompanying drawings.

It is a figure which shows the structural example of the image processing apparatus concerning one Embodiment of this invention. It is a figure which shows the data recording state in HDD. It is a figure which shows the example of arrangement | positioning with image memory and HDD of image data. It is a sequence diagram (the 1) which shows the process example of embodiment. It is a sequence diagram (the 2) which shows the process example of embodiment. It is a flowchart which shows the process example of the HDD controller at the time of the HDD use request from an application. It is a figure which shows the example of the operation | movement judgment by a security level and an execution level. It is a figure which shows the example which rewrites the security level of tag information. It is a sequence diagram (the 3) which shows the process example of embodiment. It is a sequence diagram (the 4) which shows the process example of embodiment.

Explanation of symbols

1 Bus 2 Image Memory Controller 3 Image Memory 4 HDD Controller 51, 52 HDD
6 Image forming module 7 Scanner 8 Plotter 9 CPU
10 ROM
11 RAM
12 Application control module 13A to 13C Application 14 Security management module

Claims (10)

An image processing apparatus comprising an auxiliary storage device for storing image data, and erasing image data stored in the auxiliary storage device after use of the image data by an application,
Means for determining whether or not there is an unused auxiliary storage device when a new application requests use of the auxiliary storage device;
An image processing apparatus comprising: means for causing a new application to use an auxiliary storage device when there is an unused auxiliary storage device. The image processing apparatus according to claim 1.
If there is no unused auxiliary storage device, means for comparing the security level of the app using the erased auxiliary storage device with the execution level of the new app;
An image processing apparatus comprising: means for interrupting erasure of an auxiliary storage device being erased when a new application level is high, and causing the new application to use the auxiliary storage device. The image processing apparatus according to claim 2,
An image processing apparatus comprising a table for referring to an allowable operation based on a security level of an application using an auxiliary storage device being erased and an execution level of a new application. The image processing apparatus according to claim 2,
An image processing apparatus, wherein the image data stored on the auxiliary storage device includes tag information that records a security level of an application using the image data. The image processing apparatus according to claim 4.
An image processing apparatus, wherein the security level of the tag information is evaluated relative to other stored data and written to the tag information. The image processing apparatus according to claim 1.
An image processing apparatus comprising means for causing a new application to use an image memory instead of an auxiliary storage device when there is no unused auxiliary storage device. The image processing apparatus according to claim 6.
An image processing apparatus, wherein when an unused auxiliary storage device is generated due to completion of erasure of the auxiliary storage device, image data is transferred from the image memory to the auxiliary storage device. An auxiliary storage medium erasing control method in an image processing apparatus, comprising an auxiliary storage device for storing image data, and erasing image data stored in the auxiliary storage device after use of image data by an application,
A step of determining whether or not there is an unused auxiliary storage device when a new application requests use of the auxiliary storage device;
An auxiliary storage medium erasing control method comprising: a step of causing a new application to use an auxiliary storage device when there is an unused auxiliary storage device. The auxiliary storage medium erasing control method according to claim 8,
If there is no unused auxiliary storage device, comparing the security level of the application using the auxiliary storage device being erased with the execution level of the new app;
An auxiliary storage medium erasing control method comprising: suspending erasure of an auxiliary storage device being erased when the level of a new application is high, and causing the new application to use the auxiliary storage device. The auxiliary storage medium erasing control method according to claim 8,
An auxiliary storage medium erasing control method comprising a step of causing a new application to use an image memory instead of an auxiliary storage device when there is no unused auxiliary storage device.

Images