JP2019185450A - Image forming device and control method thereof - Google Patents

Abstract

To provide an image forming device capable of protecting an HDD from frequent accesses of an application and extending a hard disk life compared to a case where the HDD is not protected, and a control method thereof.SOLUTION: When accepting an access from an application (1), an application layer 401 notifies a driver layer 402 of an access to an HDD. Upon receiving the notification, the driver layer 402 shifts the HDD to a LOAD state, sequentially receives data from each application, for example, WRITE data, from the application layer 401, and performs a write operation on the HDD. The application layer 401 is set with a reception time from the application on the basis of LOAD time, and can accept a plurality of application accesses within the reception time. WRITE/READ to the HDD for the plurality of application accesses received within the reception time can be performed with one LOAD.SELECTED DRAWING: Figure 5

Description

  The present invention relates to an image forming apparatus having a nonvolatile storage unit and a control method thereof.

  2. Description of the Related Art A MULTIIFACTION PERIPHERAL (MFP) is known that includes an image reading device, a printing device, an image storage device, and a communication device, and an image processing application device such as copying, printing, scanning, and FAX transmission / reception. Also, these MFPs employ and incorporate hard disk drives (hereinafter referred to as HDDs) as large-capacity storage devices.

  The functions of the apparatus, such as copying, printing, scanning, and FAX transmission / reception, are increasing, and operations for users who use it are becoming complicated.

  Application software customized to assist the user's operation and to easily obtain the information desired by the user can be installed in the MFP. These application software are designed to improve convenience by using HDDs.

JP2008-140492A

  Non-volatile memories, such as HDDs, have usage restrictions, and if they are used beyond the specifications, the HDDs may fail or fail to operate as expected.

  For example, some application software that uses the HDD frequently accesses the HDD. The HDD has a physical and electrical mechanism. For this reason, there is a limit on the number of times of access assumed. There is a problem that it is necessary to protect the HDD from frequent access of applications.

  One aspect of the present invention has been made in view of at least one of the above-described problems.

  Non-volatile storage means, specifying means for specifying an application in which the number of accesses to the non-volatile storage means within a predetermined time is greater than or equal to a predetermined value, and restricting access of the application specified by the specifying means to the non-volatile storage means An image forming apparatus including a restricting unit is disclosed.

  According to one aspect of the present invention, there is an effect that the nonvolatile memory can be efficiently controlled. According to another aspect of the present invention, for example, there is an effect that the HDD can be protected from frequent access of an application, and the life of the hard disk can be extended as compared with the case where it is not protected.

2 is a diagram illustrating an example of a controller unit of the image forming apparatus. FIG. 2 is a schematic diagram of the internal structure of an HDD 113. FIG. FIG. 10 is a diagram illustrating an example of operation description when access to the HDD 113 occurs. It is a figure which shows the outline of the software structure figure of an operating system (OS). It is a figure which shows the time table of the application layer 401 and the driver layer 402. FIG. It is a figure which shows the flowchart which counts the number of times of LOAD / UNLOAD. It is a figure which shows the specific flowchart of the software which accesses frequently. It is explanatory drawing about the supplementary information of OS. It is a figure which shows the means to store incidental information. It is a figure which shows the flowchart when incidental information is produced. It is a figure which shows the added flowchart.

  Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating an example of a controller unit 100 of an image forming apparatus in which a large-capacity HDD system is incorporated.

  The controller unit 100 communicates with a document conveyance device control unit that controls the document conveyance device based on an instruction from the operation unit or an external computer, and an image reader control unit that controls the image reader, and acquires image data of an input document. To do. The controller unit 100 also communicates with a printer control unit that controls the printer unit, and prints image data on a sheet.

  Further, the controller unit 100 communicates with a folding device control unit that controls the folding device and a finisher control unit that controls the finisher, and realizes a desired output such as stapling or punch holes on the printed sheet. The external I / F 151 is an interface connected to an external computer. For example, the external I / F 151 is connected via an external bus such as a network or USB, and develops and outputs print data from an external computer to an image, and transmits image data in the HDD 113 to the external computer.

  The controller unit 100 includes a CPU 101 and executes an operating system (hereinafter referred to as OS) program or the like to realize the function of the OS. A bus bridge 104 is connected to the CPU 101, and the initial startup program is read from the ROM 102 storing the initial startup program of the CPU 101 via the bus bridge 104. The CPU 101 is also connected via a bus bridge 404 to a RAM 103 used as a work area for computations associated with control and a storage control unit 112 that controls storage devices.

  The storage control unit 112 is a hardware module that performs read / write control of storage devices such as HDDs and SSDs, and a serial ATA (SERIAL ATTACHCHMENT: hereinafter referred to as SATA) interface is used for connection with the storage devices. The HDD 113 is used for storing a main program including an OS program of the CPU 101, image data acquired from an image reader or an external I / F 151, a storage when an image is edited by an operation unit, and a storage destination of an application program.

  The HDD 113 is also used as a storage location for application programs and user preference data. The SSD 113 is configured to be accessible from the CPU 101.

  Further, an external I / F control unit 105 that controls a network and a USB interface and an operation unit control unit 106 that controls an operation unit are connected to the bus bridge 104.

  The device control unit 111 is connected to and controls the document transport device control unit, the image reader control unit, the printer control unit, the folding device control unit, and the finisher control unit.

  When the CPU 101 executes processing based on a program stored in the ROM 102 or the like, part of the processing shown in the figure or the flowchart in the figure described later is realized.

  FIG. 2 shows a schematic diagram of the internal structure of the HDD 113. A disk 201 is a disk portion for recording data. A magnetic head 201 reads and writes data on the disk.

  Reference numeral 203 denotes a storage location (ramp 203) of the magnetic head when it is not being accessed.

  When access occurs, the magnetic head 202 moves to the disk 201 side and enters the LOAD state. When the access is completed, the magnetic head 202 moves to the ramp 203 and enters the UNLOAD state. Access to the HDD 113 is performed by repeating LOAD / UNLOAD of the magnetic head 202. As described above, the number of times of LOAD / UNLOAD is limited, and operation exceeding the assumption of the specification may cause a failure or the like.

  FIG. 3 shows an example of operation description when access to the HDD 113 occurs. When accessed from the storage control unit 112, the magnetic head 201 enters the LOAD state and maintains the LOAD state for 15 seconds. During this time, data is exchanged. After 15 seconds, the state shifts to the UNLOAD state and waits for the next access. When accessed again from the storage control unit 112, the magnetic head 201 enters the LOAD state and maintains the LOAD state for 15 seconds. By repeating this, data exchange is established. That is, when there is one access, the LOAD state is set for 15 seconds. Inadvertent access increases the number of LOAD / UNLOAD and shortens the life of the HDD. The LOAD time of 15 seconds is generally a numerical value and may vary depending on the specifications of the HDD manufacturer.

  FIG. 4 shows an outline of a software structure diagram of the operating system (OS) when the application program accesses the HDD 113. The OS has an application layer 401 that manages an interface with a plurality of applications, for example, the applications (1) to (4). The application layer 401 receives various requests from each application, for example, an access request to the HDD 113, and performs arbitration to each application and actual data exchange.

  The driver layer 402 issues a control command to the storage control unit 112 in accordance with a request from the application layer 401 and accesses the HDD 113.

  FIG. 5 shows a time table of the application layer 401 and the driver layer 402 based on data movement. When the application (1) and the application (2) request access at the same time, the application layer 401 permits access sequentially, for example, the application (1) and the application (2) by arbitration.

  When the application layer 401 accepts access from the application (1), the application layer 401 notifies the driver layer 402 of access to the HDD 113.

  Upon receiving the notification, the driver layer 402 shifts the HDD 113 to the LOAD state, sequentially receives data from each application, such as WRITE data, from the application layer 401, and performs a write operation on the HDD 113. The application layer 401 is set with a reception time from an application based on the LOAD time, and can receive a plurality of application accesses within the reception time.

  A plurality of application accesses received within the reception time can be written / read to the HDD 113 by one LOAD. After the LOAD time has elapsed and the transition to UNLOAD has occurred, for example, when the application (3) issues an access request, the above-described process is repeatedly executed.

  As described above, the application accesses the application layer 401 three times, but the actual number of LOADs of the HDD 113 is two. That is, the access count number of the application and the number of LOAD / UNLOAD of the HDD 113 do not match.

  It is necessary to monitor the number of accesses to the HDD 113 with respect to the application software that uses the HDD 113, and to suppress access to the application software that frequently accesses the HDD 113. As one means, it is also effective to count the access count of each application to the application layer 401 and suppress access based on the count. On the other hand, in order to accurately determine the lifetime, it is necessary to accurately count the number of LOAD / UNLOAD. The means for accurately counting the number of LOAD / UNLOAD will be described below.

  FIG. 6 shows a flowchart for counting the number of LOAD / UNLOAD times. The procedure shown in the flowchart is stored in one of the storage means of the ROM 102, RAM 103, and HDD 113 and executed by the CPU 101. As shown in the figure, the flowchart proceeds while independent programs of the application layer and the driver layer exchange commands and data. The application layer flowchart of FIG. 6 starts executing in response to power ON. In response to the driver layer program receiving the command sent in S604, the processing from S605 onward is started. The CPU 101 controls the HDD 113 via the storage control unit 112.

  The program of the application layer 401 starts, and the CPU 101 determines whether there is an access request to the HDD 113 from each application to the application layer 401 in S601. If not, repeat S601. If there is an access request, the process proceeds to S602. In step S <b> 602, the CPU 101 identifies the requested application and stores the information in a memory, for example, the RAM 103. That is, the access information data 603 is stored in the RAM 103. The access information data 603 may be stored in the ROM 102. For example, the information stored here is the application name and the time when the access request is issued. In step S <b> 604, the CPU 101 starts a counter that counts the application reception time to the application layer 401. At the same time, a command for starting the program of the driver layer 402 is sent, and the process proceeds to S613. The application layer may be implemented using Java (registered trademark), Lua Script, or the like. The application layer includes a VM (virtual machine) that interprets and executes bytecode. The application layer is also a platform for arbitrating and executing the applications 1 to N. Sometimes called an application platform. The application layer can also detect accesses from the applications 1 to N.

  The CPU 101 starts LOAD of the magnetic head in the program S605 of the driver layer 402. In step S606, the CPU 101 starts a counter that counts the LOAD time. In this embodiment, the LOAD time is 15 SEC, but it depends on the specifications of the HDD used. In step S <b> 607, the CPU 101 counts up the LOAD count value in order to count the LOAD count. In step S <b> 608, the CPU 101 determines whether the LOAD count value exceeds a threshold value, that is, the LOAD / UNLOAD count limit value. If exceeded, the process proceeds to S609, and if not exceeded, the process proceeds to S611.

  When the number of times of LOAD / UNLOAD exceeds the limit value, the risk of failure increases, and countermeasures are required. When the process proceeds to S609, the CPU 101 performs UNLOAD of the magnetic head and stops access to the HDD.

  In step S610, the CPU 101 performs HDD improvement processing, and the flow ends.

  The improvement measures are, for example, causing the operation unit control unit 106 to display an error code and a service man call on the operation unit to prompt the user to repair.

  In S <b> 613 of the application layer, the application data received by the application layer 401 is transferred to the driver layer 402. In step S616, the CPU 101 determines whether the application reception time has ended. If it is determined that the program has ended, the process returns to S601 to start the program again. If it is determined that the process has not ended, the process advances to step S617. If the process has proceeded to S617, the CPU 101 determines whether there is an access from the application.

  If there is no access, the process returns to S616 and it is determined whether the application reception time is reached. If there is an access, the process proceeds to S618. In step S <b> 618, the CPU 101 specifies the application that requested access and stores the information in a memory, for example, 603 in the RAM 103. The CPU 101 returns to S613, transfers the application data received in the application layer 401 to the driver layer 402, and waits for application data reception from the application layer in S611 of the driver layer 402 to continue processing. If the application data has been received, the process proceeds to S612. In S612, the CPU 101 transfers the received application data to the HDD, and proceeds to S614. In step S614, the CPU 101 determines whether the LOAD time has ended. If the CPU 101 determines that the load time has ended, the process advances to step S615.

  If it is determined that the process has not been completed, the process returns to S611 and continues. In step S615, the CPU 101 unloads the magnetic head, the processing flow ends, and the program ends.

  The access information recorded by the process of FIG. 6 is confirmed by the process of FIG. FIG. 7 illustrates a means for monitoring the number of accesses to the HDD 113 for application software that uses the HDD 113 and identifying application software that frequently accesses the HDD 113 with reference to a flowchart. The procedure shown in the flowchart is stored in one of the storage means of the ROM 102, RAM 103, and HDD 113 and executed by the CPU 101. The program starts, and the CPU 101 starts an interval timer in S701. The processing in FIG. 7 may be executed by the application layer 401, or an application of the same layer as the applications 1 to 4 called the application X may be mounted and executed.

  This is an interval timer for measuring the access frequency at a certain interval when measuring the access frequency. The interval is determined by the specifications of the HDD. In step S702, the CPU 101 determines whether a necessary interval has elapsed. If it has not elapsed, the process returns to S701, and if it has elapsed, the process proceeds to S703.

  In step S703, the CPU 101 acquires access information of each application. The acquisition destination is data acquired in the flowchart of FIG. 6 (603). In the access information data, the application name and the access time are sequentially stored. In step S704, the CPU 101 calculates the access frequency of each application to the HDD 113 from the acquired data.

  The access frequency is obtained by dividing the number of accesses of each application by the interval time. In step S <b> 705, the CPU 101 determines whether there is an application whose access frequency to the HDD 113 exceeds a threshold value. The threshold is determined by the HDD specifications. If there is no access frequency exceeding the threshold, the process proceeds to S710, and if there is an access frequency exceeding the threshold, the process proceeds to S710.

  In step S710, the CPU 101 initializes the access information data 603 and returns to step S701. Prepare for the next interval. If there are a plurality of applications exceeding the threshold value in step S706, the CPU 101 lists them.

  In step S <b> 707, the CPU 101 determines whether the access interval to the HDD 113 is a periodic access exceeding the application reception time for each listed application. If the access is made a plurality of times within the application reception time, the access is completed with one LOAD, so the access exceeding the application reception time is counted.

  If there is no periodic access exceeding the application reception time, the process proceeds to S710 and the process is repeated.

  If it is determined that there is a periodic access exceeding the application reception time, the process proceeds to S708.

  If there are a plurality of periodic accesses exceeding the application reception time in S708, the CPU 101 lists them up. In step S709, the CPU 101 performs stop processing for each listed application. Alternatively, it is only necessary to notify that the operations of the applications 1 to N need to be stopped without forcibly stopping them. At this time, only basic applications such as copy and fax that were not specified applications may be allowed to operate. In addition, it is possible to stop the functions of the multifunction peripheral that can be controlled by the application layer program.

  Applications that are frequently accessed to the HDD 113 are monitored because the number of LOAD / UNLOAD is inadvertently increased and affects the service life.

  After the processing of S709, the CPU 101 proceeds to S710 and prepares for the next interval.

  As the application accesses the HDD 113, the OS creates incidental information and writes it to the HDD 113. The incidental information is information managed by the OS related to each application, and is information such as a time stamp and an access log, for example.

  FIG. 8 shows an explanatory diagram thereof. For example, when the application (1) requests access, the application layer 401 permits the access of the application (1), for example.

  When the application layer 401 accepts access from the application (1), the application layer 401 notifies the driver layer 402 of access to the HDD 113. Upon receiving the notification, the driver layer 402 shifts the HDD 113 to the LOAD state, receives data from the application, such as WRITE data, from the application layer 401, and performs a write operation on the HDD 113.

  The OS may create incidental information based on the application itself after receiving access from the application. The incidental information is stored in the HDD 113 like the application data. If the incidental information is created within the reception time, the access is completed within one LOAD. However, depending on how the incidental information is created, the OS may generate the next LOAD and complete the access.

  LOAD may occur twice even though the access from the application is once.

  That is, the access count number of the application and the number of LOAD / UNLOAD of the HDD 113 do not match. It is necessary to store in the HDD 113 without generating unnecessary LOAD / UNLOAD. The incidental information is a time stamp, an access log, and the like, and is not information that affects the operation from the application or the OS. That is, there is no problem when writing is performed, and there is no time restriction.

  FIG. 9 is an explanatory diagram of a means for storing incidental information in the HDD 113 without causing unnecessary LOAD / UNLOAD. The incidental information to be created is written in the HDD 113, but when a new LOAD occurs, it is stored and accumulated in the RAM 103, for example. For example, when the application (1) requests access, the application layer 401 permits the access of the application (1), for example. When the application layer 401 accepts access from the application (1), the application layer 401 notifies the driver layer 402 of access to the HDD 113. Upon receiving the notification, the driver layer 402 shifts the HDD 113 to the LOAD state.

  After receiving access from the application, the OS calculates the amount of data from the newly created incidental information and the incidental information stored and accumulated in the RAM 103, for example.

In the case of the following conditions, data from the application and data from the incidental information are written during 1 LOAD. Data amount writable in one LOAD time> Application data amount + Attached information data amount That is, by inserting the incidental information data into the LOAD caused by application access, unnecessary LOAD of only the incidental information data is suppressed.

  FIG. 10 shows a flowchart when the incidental information is created. In FIG. 10, by adding a new flowchart A between S611 and S612 in the flowchart shown in FIG. 6, it is possible to cope with the increase in the number of LOAD / UNLOAD even if incidental information is created. Hereinafter, although the description will focus on the differences of the above-described embodiments, the above description can be used unless otherwise specified.

  FIG. 11 shows a flowchart A. In step S <b> 1001, the CPU 101 determines whether new incidental information is created for the transfer target application data in step S <b> 611. When new incidental information is created, the process proceeds to S1002. When new incidental information is not created, the process proceeds to S1003.

  In step S1002, the CPU 101 stores the created new incidental information in the ROM 102 and adds it to the existing incidental information. Hereinafter, the supplementary information may be stored in the RAM 103. In step S <b> 1003, the CPU 101 determines whether there is incidental information 1010 stored in the ROM 102. If the ROM 102 has the accompanying information 1010, the process proceeds to S1004.

  If there is no supplementary information 1010 in the ROM 102, the flowchart A is exited.

  In step S1004, the CPU 101 totals the total data amount of the incidental information from the information stored in the ROM 102 (S1008) (FD). In step S1005, the CPU 101 totals the total data amount from the application (AD). In step S1006, the CPU 101 totals the total data amount of the incidental information and the total data amount from the application, and calculates the total transfer data amount (SUM).

  In step S1007, the CPU 101 determines whether the total transfer data amount can be transferred with 1 LOAD.

  If it is determined that transfer is possible, the process proceeds to S1008. If it is determined that transfer is not possible, the process proceeds to S1009. In step S <b> 1008, the CPU 101 performs transfer setting of incidental information from the ROM 102 after transferring application data, and exits the chart A. In step S1009, the CPU 101 cancels the transfer setting of the incidental information from the ROM 102 after the application data is transferred, and exits the chart A.

  With this setting, priority is given to the transfer of application data to the HDD 113, and the incidental information is transferred when there is room for transfer.

  The MFP 1000 has been described as an example of an image forming apparatus. The HDD 113 has been described as an example of the nonvolatile storage unit. The CPU 101 identifies an application in which the number of accesses to the HDD 113 within a predetermined time is greater than or equal to a predetermined value. The applications are the applications 1 to 4 shown in FIG. Then, the CPU 101 restricts access of the identified application to the HDD 113. The access count is the number of accesses caused under the control of the device driver called by the application. An example of the device driver is the driver layer 402.

  Also, access to the HDD 113 is executed once under the control of the application, and incidental information by the operating system or the like is issued according to the access. As a result, incidental information is written to the HDD 113. As a result, when the access to the HDD 113 is caused within a predetermined time from the time when the access occurred, the following may be performed. That is, the CPU 101 may count the number of accesses as one at a time.

  Further, the CPU 101 detects an access to the application HDD 113.

  In addition, the MFP 1000 has a timer that resets after counting for a certain time in accordance with the detection of access by the CPU 101. The timer may be built in the CPU 101 or may be built in the storage control unit. During the timer operation, the CPU 101 may mask access detection by the CPU 101. Further, the CPU 101 counts the number of times that the timer has entered the count state. When the number of counts exceeds a predetermined threshold, the CPU 101 controls to prohibit access to the HDD 101.

  As described above, according to the present invention, by monitoring the access to the HDD by an application, extremely unnecessary access is blocked and consumption of the number of loads / unloads is suppressed.

101 CPU
102 ROM
103 RAM
104 Bus Bridge 105 External Interface Control Unit 106 Operation Unit Control Unit 111 Device Control Unit 112 Storage Control Unit 113 Hard Disk Drive

Claims (8)

In the image forming apparatus,
Non-volatile storage means;
Specifying means for specifying an application in which the number of accesses to the nonvolatile storage means within a predetermined time is greater than or equal to a predetermined value;
Restricting means for restricting access to the nonvolatile storage means of the application specified by the specifying means;
An image forming apparatus comprising:   The image forming apparatus according to claim 1, wherein the number of accesses is the number of accesses caused under the control of a device driver called by the application.   The number of times of access is that the access to the nonvolatile storage means is executed once under the control of the application, and incidental information by the operating system is issued and written to the nonvolatile storage means in response to the access. The image forming apparatus according to claim 1, wherein when the access to the nonvolatile storage unit is caused within a predetermined time from the time when the access occurs, the image forming apparatus counts as one time. Detecting means for detecting access to the nonvolatile storage means of the application;
According to the detection of access by the detection means, a timer that resets after counting for a certain period of time,
Means for masking detection of access by the detection means during the timer operation;
Counting means for counting the number of times the timer is in a counting state;
The image forming apparatus according to claim 1, further comprising a control unit that controls to prohibit access to the non-volatile storage unit when the number of counts exceeds a predetermined threshold. In a control method of an image forming apparatus having a nonvolatile storage means,
A specifying step of specifying an application in which the number of accesses within a predetermined time to the nonvolatile storage means is equal to or greater than a predetermined value;
A restricting step of restricting access to the nonvolatile storage means of the application specified in the specifying step;
A control method comprising:   The image forming apparatus according to claim 5, wherein the number of accesses is a number of accesses caused under control of a device driver called by the application.   The number of times of access is that the access to the nonvolatile storage means is executed once under the control of the application, and incidental information by the operating system is issued and written to the nonvolatile storage means in response to the access. The control method according to claim 5, wherein when the access to the nonvolatile storage means is caused within a predetermined time from the time when the access occurred, the control method is counted as one time. A detection step of detecting access to the nonvolatile storage means of the application;
According to the detection of access by the detection means, a timer that resets after counting for a certain period of time,
Masking the detection of access by the detection means during the timer operation;
A counting step for counting the number of times the timer is in a counting state;
The control method according to claim 5, further comprising a control step of performing control so as to prohibit access to the non-volatile storage unit when the number of counts exceeds a predetermined threshold value.

Images