Information processing device, image formation apparatus, information processing method, and information processing program

The information processing device addresses data inconsistency by using access destination tables and synchronized file lists to manage storage transitions, ensuring data integrity and minimizing downtime.

JP2024165653APending Publication Date: 2024-11-28RICOH CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023082017
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-18
Publication Date
2024-11-28

AI Technical Summary

Technical Problem

When switching storages for data writing, the inability to determine which storage holds the latest data can lead to data inconsistency and potential large downtime due to the need to copy all data for consistency.

Method used

An information processing device with multiple operation modes in first and second storages, using access destination tables and synchronized file lists to determine the latest storage and manage data access, minimizing downtime by dynamically changing write and read destinations based on storage usage status.

Benefits of technology

Maintains data integrity and minimizes downtime by ensuring data is written and read from the correct storage, even when storage modes change, through dynamic destination management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024165653000001_ABST
    Figure 2024165653000001_ABST
Patent Text Reader

Abstract

To maintain data consistency by allowing discrimination of a storage holding the latest file, when a plurality of storages for data writing are switchable.SOLUTION: An information processing device has a first device and a second device having a first storage and a second storage, respectively. The first device determines a storage to be accessed by referring to an access destination table in which access storage information is held for each combination of operation modes of the first device and the second device when receiving an access request from an application, and accesses an actual access destination by referring to a synchronization file list in which a preliminary access destination contained in the access request and the actual access destination are associated with each other in the case of an access request of a first importance file for which a writing destination storage changes according to a use situation of the storage.SELECTED DRAWING: Figure 4
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an information processing apparatus, an image forming apparatus, an information processing method, and an information processing program. [Background technology]

[0002] In an information processing device that uses both a hard disk drive (HDD) and a solid state drive (SSD), a technology has been disclosed that reduces the power consumption of the HDD by keeping the HDD in a sleep state except when it is necessary to use the HDD (see, for example, Patent Document 1). Summary of the Invention [Problem to be solved by the invention]

[0003] When the storage device to which data is written is switched, if it is not possible to determine which storage device holds the latest data, it is not possible to identify the storage device from which the data is read, and data consistency may not be maintained. In addition, for example, if all data is copied to maintain data consistency when switching storage devices, there is a problem that a very long downtime may occur depending on the amount of data in the storage device.

[0004] The disclosed technology has been developed in consideration of the above-mentioned problems, and aims to maintain data consistency by making it possible to determine the storage device holding the latest file when it is possible to switch between multiple storage devices to which data is written. [Means for solving the problem]

[0005] In order to solve the above technical problem, an information processing apparatus according to one aspect of the present invention includes a first device including a first storage, having a plurality of operation modes, and capable of executing an application, and a second device including a second storage, having a plurality of operation modes, and capable of transmitting and receiving information to and from the first device, wherein a plurality of types of files held in the first storage and the second storage are classified into a first importance level in which a storage to which the files are written changes depending on a usage status of the first storage or the second storage, and a second importance level in which a storage to which the files are written does not change regardless of a usage status of the first storage and the second storage, and the first device, when receiving an access request from the application, selects the first device to access. The storage to be accessed is determined by referring to an access destination table that holds access storage information indicating the first storage or the second storage for each combination of operating modes of the first device and the second device, and if the determined storage is the second storage, access to the second storage is requested from the second device, and if the access request is an access request for a file of the first importance, the first device or the second device accesses the actual access destination by referring to a synchronized file list that links a virtual access destination and an actual access destination included in the access request, and if the access request is an access request for a file of the second importance, the first device or the second device accesses the virtual access destination. Effect of the Invention

[0006] When it is possible to switch between multiple storage devices to which data is written, data consistency can be maintained by making it possible to distinguish the storage device that holds the latest file. [Brief description of the drawings]

[0007] [Figure 1] 1 is a diagram illustrating an overall configuration of an example of an image forming apparatus according to an embodiment of the present invention. [Diagram 2] 2 is a block diagram showing an example of a hardware configuration of the image forming apparatus in FIG. 1. [Diagram 3]3 is a block diagram showing an example of a hardware configuration of an operation unit in FIG. 2. [Figure 4] 3 is a functional block diagram showing an example of a functional configuration of a controller and an operation unit in FIG. 2. [Diagram 5] 3A to 3C are diagrams illustrating examples of combinations of operational states of the controller and the operation unit in FIG. 2. [Figure 6] 3 is a state transition diagram showing an example of transition of the operational states of the controller and the operation unit in FIG. 2. [Figure 7] 11A and 11B are diagrams illustrating examples of data write destinations according to operation modes for each level of importance of data. [Figure 8] FIG. 8 is a diagram showing an example of change in write destination in response to state transition for data of importance level 2 and importance level 4 in FIG. 7. [Figure 9] 4 is a flow chart showing an example of processing of a controller and an operation unit at the time of starting up the image forming apparatus in FIG. 1. [Figure 10] 11 is a flow diagram showing an example of a process performed by the operation unit when an application reads and writes a file. FIG. [Figure 11] 13 is a diagram showing an example of a synchronized file list used in read / write processing of importance level 2 or importance level 4. FIG. [Figure 12] 8 is a flow diagram showing an example of writing data of importance level 2 shown in FIG. 7 to a storage. FIG. [Figure 13] FIG. 13 is a flow chart showing a continuation of FIG. [Figure 14] 8 is a flow diagram showing an example of reading data of importance level 2 shown in FIG. 7 from a storage. [Figure 15] FIG. 15 is a flow chart showing a continuation of FIG. 14. [Figure 16] 8 is a flow diagram showing an example of writing data with importance level 4 shown in FIG. 7 to a storage. FIG. [Figure 17] FIG. 17 is a flow chart showing a continuation of FIG. 16. [Figure 18] 8 is a flow diagram showing an example of reading data of importance level 4 shown in FIG. 7 from a storage. [Figure 19] FIG. 19 is a flow chart showing a continuation of FIG. 18. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, an embodiment will be described with reference to the drawings. In the following, an example in which the present invention is applied to an image forming apparatus including a plurality of control devices each equipped with a storage will be described, but the present invention may also be applied to an information processing apparatus including a plurality of devices each equipped with a storage. For example, each of the plurality of devices may be a computer device including a processor such as a CPU, and the plurality of computer devices are capable of transmitting and receiving information to and from each other.

[0009] Fig. 1 is an overall configuration diagram showing an example of an image forming apparatus according to an embodiment of the present invention. The image forming apparatus 1 shown in Fig. 1 is, for example, a digital multifunction peripheral (MFP: Multi-Function Printer) having a copy function, a print function, a scanner function, a facsimile function, etc. The image forming apparatus 1 can switch between operation modes that respectively realize the copy function, the print function, the scanner function, and the facsimile function by a user's application switching operation. The image forming apparatus 1 goes into a copy mode when the copy function is selected, goes into a print mode when the print function is selected, goes into a scanner mode when the scanner function is selected, and goes into a facsimile mode when the facsimile function is selected.

[0010] For example, the image forming apparatus 1 includes an automatic document feeder 2 (ADF: Auto Document Feeder), an image reader 3, a writing unit 4, a printer unit 5, a power supply device 11, a controller 100, an operation unit 200, and an image creating unit 300 which is an engine for forming an image. The printer unit 5 includes a photoconductor drum 6, a developing device 7, a conveyor belt 8, and a fixing device 9 included in the image creating unit 300, and a storage space for storing a paper feed tray 10.

[0011] The image creating unit 300 creates a toner image to be transferred to a paper medium or the like based on image information. The image creating unit 300 is an example of an image forming unit that forms an image. Below, a brief description will be given of a case where a document is copied as an example of the flow of forming an image in the image forming apparatus 1.

[0012] When copying an original, multiple sheets of the original to be copied are set in the automatic document feeder 2, or the original to be copied is set on the image reading device 3. When a start button displayed on the screen of the operation unit 200 is pressed, the automatic document feeder 2 feeds the originals one by one to the image reading device 3. The image reading device 3 reads image information of each of the originals sent in sequence from the automatic document feeder 2 or the original set on the image reading device 3. The image information read by the image reading device 3 is processed by, for example, an image processing unit included in the controller 100.

[0013] The writing unit 4 converts the image information processed by the image processing unit into optical information. The photoconductor drum 6 is uniformly charged by a charger disposed opposite the photoconductor drum 6, and then exposed to a laser beam containing the optical information converted by the writing unit 4. An electrostatic latent image is formed on the photoconductor drum 6 by the exposure. The developing device 7 develops the electrostatic latent image on the photoconductor drum 6 to form a toner image on the photoconductor drum 6. The conveyor belt 8 transfers the toner image onto a paper medium or the like. The fixing device 9 fixes the toner image onto the paper medium or the like. The transfer paper on which the image of the original has been copied is then discharged from the discharge section.

[0014] The operation unit 200 has an operation panel having a function of accepting various inputs according to user operations and a function of displaying various information. For example, the information displayed on the operation panel is information indicating the operation for which the input is accepted, information indicating the operating status of the image forming device 1, information indicating the setting state of the image forming device 1, etc.

[0015] The controller 100 controls the overall operation of the image forming apparatus 1, such as controlling the printer unit 5, controlling communications, and controlling input to the operation unit 200, by having a built-in CPU (Central Processing Unit) and the like execute a control program. The controller 100 then executes an image processing program or an information processing program to perform image processing or information processing of image data, etc., form an image to be transferred to a paper medium, etc., and write and read image data, etc. to and from various storage devices.

[0016] The power supply device 11 converts an AC voltage supplied from an AC power source AC such as a commercial power source into a plurality of types of DC voltages (for example, a first DC voltage and a second DC voltage). The power supply device 11 supplies the converted first DC voltage to various loads such as the printer unit 5 of the image forming apparatus 1. For example, the loads include various motors, a charger that charges the photosensitive drum 6, and a developing roller of the developing device 7. The power supply device 11 supplies the converted second DC voltage as an operating power source for a CPU, memory, storage, and the like mounted on the controller 100 and the operation unit 200.

[0017] Fig. 2 is a block diagram showing an example of a hardware configuration of the image forming apparatus 1 in Fig. 1. For example, the controller 100 may have the form of a control board. The controller 100 has a CPU 110, an ASIC (Application Specific Integrated Circuit) 120, a DRAM (Dynamic Random Access Memory) 130, an NVRAM (Non-Volatile Random Access Memory) 150, an SSD 140, and an HDD 160. The image forming apparatus 1 has a hardware configuration as a computer device, and can be operated as an information processing device.

[0018] Furthermore, the controller 100 may have one or both of a USB (Universal Serial Bus) interface 170 (I / F) to which a USB memory 400 can be connected and an SD card interface 180 (I / F) to which an SD card 500 can be connected. A program executable by the CPU 110 may be recorded on a recording medium such as the USB memory 400 or the SD card 500 and transferred to the DRAM 130.

[0019] The CPU 110 is connected to the DRAM 130, the HDD 160, the USB interface 170, the ASIC 120, and the operation unit 200. The CPU 110 executes various programs stored in the DRAM 130 to control the entire image forming apparatus 1. For example, the CPU 110 controls image formation processing, communication processing, input / output of information to / from the operation unit 200, and the like.

[0020] Various programs executed by the CPU 110 may be loaded from the HDD 160 to the DRAM 130. The various programs include an OS (Operating System). The HDD 160 may be used to temporarily store image data on which image processing is performed.

[0021] The ASIC 120 is connected to the CPU 110, the SSD 140, the SD card interface 180, the NVRAM 150, and the imaging unit 300. The ASIC 120 controls the operation of the imaging unit 300, and may write image data to be subjected to image processing, etc., to the SSD 140. The NVRAM 150 may store various parameters used when the ASIC 120 controls the imaging unit 300.

[0022] The operation unit 200 has a CPU (not shown) and controls the GUI (Graphical User Interface) of the operation panel and the operation mode of the image forming apparatus 1. The operation unit 200 mainly operates as a GUI that accepts user operations and shows information to the user, and since comfortable operability is prioritized, an eMMC (Embedded Multi Media Card) 201, which has a faster read / write speed than an HDD, is mounted on the operation unit 200.

[0023] The controller 100 and the operation unit 200 operate on different OSs. The operation unit 200 and the controller 100 may be connected by a serial interface such as a USB. Furthermore, TCP / IP (Transmission Control Protocol / Internet Protocol) may be used for communication between the operation unit 200 and the controller 100.

[0024] The operation unit 200 can write data to the HDD 160 by notifying the controller 100 of various data. By operating the controller 100 and the operation unit 200 independently and in cooperation with each other, it is possible to control writing of data taking into consideration the remaining life spans of the eMMC 201 of the operation unit 200 and the HDD 160 of the controller 100, as described below.

[0025] 2, the storage used by the controller 100 and the operation unit 200 is not limited to the HDD and eMMC, and may be an SSD 140, a USB memory 400, an SD card 500, or the like. However, it is preferable that the controller 100 connected to the imaging unit 300 uses a storage such as an HDD 160, which has a relatively large capacity and is fault-tolerant, in order to store print data for image processing. The controller 100 can grasp the status of each storage by acquiring SMART information from the storage such as the HDD 160. The operation unit 200 can grasp the status of the eMMC 201 by acquiring SMART information from the eMMC 201.

[0026] The following describes reading and writing data from and to the eMMC 201 of the operation unit 200 and the HDD 160 of the controller 100, and synchronization of data between the eMMC 201 and the HDD 160. However, the same can be applied to reading and writing data from and to various other storages such as the SSD 140, the USB memory 400, and the SD card 500 as with the eMMC 201 and the HDD 160. For example, the operation unit 200 may have an SSD instead of the eMMC 201.

[0027] Data is read from and written to the eMMC 201 and the HDD 160 as a file. For this reason, hereinafter, data may be referred to as a file. In the following, unless otherwise specified, data and files have the same meaning.

[0028] Fig. 3 is a block diagram showing an example of a hardware configuration of the operation unit 200 in Fig. 2. The operation unit 200 has a hardware configuration similar to that of a computer device such as a PC (Personal Computer) or a server. The operation unit 200 has an eMMC 201, a CPU 202, a ROM (Read Only Memory) 203, a RAM 204, an operation panel 205, a network interface 206, an external device connection interface 207, an I / O interface 208, and a media interface 209. The eMMC 201, the CPU 202, the ROM 203, the RAM 204, the operation panel 205, the network interface 206, the external device connection interface 207, the I / O interface 208, and the media interface 209 are connected to each other via a bus BUS.

[0029] The eMMC 201 stores an operation log and various data of the operation panel 205. The CPU 202 controls the operation of the entire operation unit 200. The ROM 203 holds a boot loader and the like executed by the CPU 202 when the power of the operation unit 200 is turned on or reset. The RAM 204 is used as a work area for the CPU 202. The operation panel 205 is capable of displaying various information such as a cursor, menu, window, character, or image, and, as described above, accepts various inputs according to user operations and displays various information to the user.

[0030] The network interface 206 is connected to a network NW such as the Internet, and enables communication with the outside of the image forming apparatus 1. Various programs executed by the CPU 202 may be downloaded from the network NW via the network interface 206. The external device connection interface 207 is capable of connecting various external devices via a connector CN.

[0031] The I / O interface 208 can be loaded with a disk 600 such as a DVD (Digital Versatile Disc) and controls reading and writing of various data from and to the loaded disk 600. The media interface 209 can be loaded with a recording medium 700 such as a flash memory and controls reading and writing of various data from and to the loaded recording medium 700.

[0032] Fig. 4 is a functional block diagram showing an example of the functional configuration of the controller 100 and the operation unit 200 in Fig. 2. The controller 100 has, for example, a write control module 101 and an abstraction module 102 that are realized by a storage control program executed by a CPU 110. Note that the write control module 101 and the abstraction module 102 may be realized by hardware such as an FPGA (Field-Programmable Gate Array).

[0033] The operation unit 200 includes, for example, an application 210 which is an application realized by a storage control program executed by the CPU 202, a monitoring module 211, and an abstraction module 212. The monitoring module 211 and the abstraction module 212 may be realized by hardware such as an FPGA.

[0034] The operation unit 200 is an example of a first device that includes an eMMC 201, has multiple operation modes, and can execute applications. The controller 100 is an example of a second device that includes an HDD 160, has multiple operation modes, and can transmit and receive information to and from the operation unit 200.

[0035] The monitoring module 211 detects the state of the eMMC 201 based on SMART information etc. acquired from the eMMC 201, and notifies the abstraction module 212 of the operation mode (normal mode or safety mode SM) of the operation unit 200. The eMMC 201 is an example of a first storage. The operation modes of the operation unit 200 are described in Figs. 5 to 7.

[0036] The abstraction module 212 notifies the abstraction module 102 of the controller 100 of the operation mode received from the monitor module 211 , and receives the operation mode of the controller 100 from the abstraction module 102 .

[0037] The write control module 101 detects the state of the HDD 160 based on SMART information etc. acquired from the HDD 160, and notifies the abstraction module 102 of the operation mode of the controller 100 (normal mode, safety mode SM1 or SM2). The HDD 160 is an example of a second storage. The operation modes of the controller 100 are described in FIG. 5 to FIG. 7.

[0038] The abstraction module 102 notifies the abstraction module 212 of the operation unit 200 of the operation mode received from the write control module 101 , and receives the operation mode of the operation unit 200 from the abstraction module 212 .

[0039] The abstraction modules 102 and 212 switch the storage (HDD 160 or eMMC 201) from which data (file) is read or written, the read / write destination and importance of which are specified by the application 210, to the storage from which data is actually read or written, depending on the operation mode. That is, the abstraction modules 102 and 212 operate in synchronization with each other, and abstract the read / write destination of data specified by the application 210, depending on the operation modes of the controller 100 and the operation unit 200. This makes it possible to maintain data consistency between the controller 100 and the operation unit 200, even when the read / write destination of data is switched due to a change in the operation mode.

[0040] An example of a process of reading and writing data from and to storage by cooperation between the abstraction modules 102 and 212 when a data read or write request is made from the application 210 is described in Figures 10 to 19. For example, an example of a process of writing a file to the HDD 160 or the eMMC 201 is shown in Figures 12 to 15. An example of a process of reading a file from the HDD 160 or the eMMC 201 is shown in Figures 16 to 19.

[0041] Fig. 5 is a diagram showing an example of a combination of the operating states of the controller 100 and the operation unit 200 in Fig. 2. For example, the remaining lifespan of the controller 100 shown in Fig. 5 corresponds to the remaining number of times a file can be written to the HDD 160. For example, the remaining lifespan of the HDD 160 is the remaining number of times a file can be written to the HDD 160. The remaining lifespan of the HDD 160 is determined based on the number of times a file is written, and the more times the file is written, the shorter the remaining lifespan becomes.

[0042] Meanwhile, for example, the remaining life of the operation unit 200 corresponds to the remaining number of times files can be erased from the eMMC 201. In the following, the remaining life of the eMMC 201 is assumed to be the remaining number of times files can be erased from the eMMC 201. The remaining life of the eMMC 201 is determined based on the number of times files have been erased, and the greater the number of times files have been erased, the shorter the remaining life becomes.

[0043] The controller 100 has a normal mode and safety modes SM1 and SM2. The normal mode is set when the remaining life of the HDD 160 is equal to or greater than threshold 1. The safety mode SM1 is set when the remaining life of the HDD 160 is smaller than threshold 1 and equal to or greater than threshold 2. Here, threshold 1 and threshold 2 correspond to the remaining number of writes to the HDD 160, and threshold 2 is smaller than threshold 1. The safety mode SM2 is set when the remaining life of the HDD 160 is smaller than threshold 2.

[0044] The operation unit 200 has a normal mode and a safety mode SM. The normal mode is set when the remaining life of the eMMC 201 is equal to or greater than a threshold. The safety mode SM is set when the remaining life of the eMMC 201 is less than the threshold.

[0045] Operation state 1 is a state when both the controller 100 and the operation unit 200 are in the normal mode. Operation state 2 is a state when the controller 100 is in the normal mode and the operation unit 200 is in the safety mode SM. Operation state 3 is a state when the controller 100 is in the safety mode SM1 and the operation unit 200 is in the normal mode. Operation state 4 is a state when the controller 100 is in the safety mode SM1 and the operation unit 200 is in the safety mode SM. Operation state 5 is a state when the controller 100 is in the safety mode SM2 and the operation unit 200 is in the normal mode. Operation state 6 is a state when the controller 100 is in the safety mode SM2 and the operation unit 200 is in the safety mode SM.

[0046] Fig. 6 is a state transition diagram showing an example of transition of the operating state of the controller 100 and the operation unit 200 in Fig. 2. In Fig. 6, the transition of the operating state is shown as an activity diagram. The operating state transition occurs in response to one or both of wear of the HDD 160 and wear of the eMMC 201.

[0047] Transitions from operating state 1 to operating state 2, from operating state 3 to operating state 4, and from operating state 5 to operating state 6 occur due to wear of the eMMC 201. Also, the eMMC 201 transitions from normal mode to safety mode SM due to wear.

[0048] Transitions from operating state 1 to operating state 3, from operating state 3 to operating state 5, from operating state 2 to operating state 4, and from operating state 4 to operating state 6 occur due to wear of the HDD 160. The HDD 160 also transitions from normal mode to safety modes SM1 and SM2 in sequence due to wear. Because wear of storage is irreversible, there is no transition from safety mode to normal mode.

[0049] 7 is a diagram showing an example of a data write destination according to an operation mode for each level of importance of data. For example, importance is classified into four levels, from importance 1 to importance 4, according to the type of data (importance level 4 being the most important). Then, a plurality of destination storage tables are created that indicate the destination storage to which data is written for each level of importance of data. Information indicating the storage to be accessed, which is held in each destination storage table for each combination of the operation mode of the controller 100 and the operation mode of the operation unit 200, is an example of accessed storage information.

[0050] The multiple storage destination tables are created in advance before starting up the image forming apparatus 1. The multiple storage destination tables created are arranged, for example, in a storage area that can be referenced by the abstraction module 212 of the operation unit 200 and in a storage area that can be referenced by the abstraction module 102 of the controller 100. The storage destination tables may be arranged in a storage area that can be commonly referenced by the abstraction modules 212 and 102.

[0051] Each storage destination table has a plurality of areas for storing information indicating the storage destination to which data is to be written for each combination of the operation mode of the controller 100 and the operation mode of the operation section 200. The storage destination table is an example of an access destination table.

[0052] Data with a level of importance 1 is, for example, an operation log (low importance). Data with a level of importance 2 is, for example, data for each application (medium importance). Data with a level of importance 3 is, for example, user data, print data, and copy data (high importance 1). Data with a level of importance 4 is, for example, data for each application such as startup-related data and system properties (high importance 2).

[0053] Importance levels 2 and 4 are examples of first importance levels where the write destination changes depending on the storage usage. Importance levels 1 and 3 are examples of second importance levels where the write destination does not change regardless of the storage usage. In other words, multiple storage destination tables are classified as having first or second importance levels.

[0054] Data with importance level 1 is written to the HDD 160 only when the controller 100 is in the normal mode. Data with importance level 1 is discarded without being written to the HDD 160 or eMMC 201 in the safety modes SM1 and SM2.

[0055] Data with importance level 2 is written to the HDD 160 when the controller 100 is in normal mode or safety mode SM1. Data with importance level 2 is written to the eMMC 201 when the controller 100 is in safety mode SM2 and the operation unit 200 is in normal mode. This allows data with importance level 2 to be written to the eMMC 201 while avoiding the HDD 160 whose remaining life is shortened. Furthermore, when the controller 100 is in safety mode SM2 and the operation unit 200 is in safety mode SM, data with importance level 2 is discarded without being written to the HDD 160 and eMMC 201.

[0056] Data with importance level 3 is written to HDD 160 regardless of the operation mode. Data with importance level 4 is written to eMMC 201 when operation unit 200 is in normal mode, and is written to HDD 160 when operation unit 200 is in safety mode SM.

[0057] Among importance levels 1 to 4, as shown in FIG. 6, when there is a sequential transition from operating state 1 to operating state 6, data write destinations that change from HDD 160 to eMMC 201 or from eMMC 201 to HDD 160 are those with importance levels 2 and 4.

[0058] Fig. 8 is a diagram showing an example of changes in the write destination in response to state transitions for data of importance levels 2 and 4 in Fig. 7. In Fig. 8, changes in the write destination of data due to transitions in the operating state are summarized in the storage destination table for importance levels 2 and 4 in Fig. 7 in correspondence with the state transitions in Fig. 6.

[0059] 7, importance level 1 is either written to the HDD 160 or discarded, and importance level 3 is always written to the HDD 160. Therefore, importance levels 1 and 3 do not change the storage (HDD 160, eMMC 201) to which they are written, and therefore are omitted from FIG. 8.

[0060] At importance level 2, the data write destination changes from HDD 160 to eMMC 201 only when the operating state changes from 3 to 5. At operating state 5 and onward at importance level 2, the data write destination does not change from eMMC 201 to HDD 160, and data is always written to eMMC 201 unless it is discarded.

[0061] At importance level 4, when the operating state changes from 1 to 2, from 3 to 4, and from 5 to 6, the data write destination changes from eMMC 201 to HDD 160. Operating state 2, operating state 4, and operating state 6 are cases where the operating mode of operation unit 200 is safety mode SM. For this reason, at importance level 4, from operating state 2 onwards, from operating state 4 onwards, and in operating state 6, the data write destination does not change from HDD 160 to eMMC 201, and data is always written to HDD 160 unless it is discarded.

[0062] Since application 210 cannot recognize a change in the data write destination, it uniquely determines the data write destination according to, for example, importance. Therefore, when application 210 requests writing of data with importance 2 and importance 4, whose write destination may be changed, abstraction modules 102 and 212 cooperate with each other to refer to the synchronized file list. Then, abstraction modules 102 and 212 write data to the actual write destination corresponding to the virtual write destination from application 210 described in the synchronized file list.

[0063] If the synchronized file list does not contain a virtual write destination from application 210 and data corresponding to the data to be written is held in a storage that is not a write destination, the data stored in the storage that is not a write destination is copied to the storage that is the write destination. Then, a pair of the virtual write destination and the actual write destination corresponding to the copied data is newly added to the synchronized file list, and then the data write process is performed.

[0064] Similarly, when the application 210 requests the reading of data with importance levels 2 and 4, the abstraction modules 102 and 212 cooperate with each other to refer to the synchronized file list, and read the data from the actual read source corresponding to the virtual read source from the application 210 described in the synchronized file list.

[0065] If the virtual write destination from application 210 does not exist in the synchronized file list and the data to be read is held in a storage that is not the read source, the data saved in the storage that is not the read source is copied to the read source storage. Then, a pair of the virtual read source and the actual read source corresponding to the copied data is newly added to the synchronized file list, and the data read process is performed.

[0066] As described above, the abstraction modules 102, 212 can cooperate with each other to abstract the storage write destination and storage read source, and can synchronize with each other as to which storage the latest data is held, thereby maintaining data consistency.

[0067] Since only the data to be accessed is read from and written to the correct storage according to the importance of the data and the operating state, there is no need to copy all data from one storage to another every time the operating state changes, and this makes it possible to minimize downtime of the image forming device 1 due to copying of data.

[0068] Fig. 9 is a flow diagram showing an example of processing of the controller 100 and the operation unit 200 at the time of starting up the image forming apparatus 1 in Fig. 1. The processing flow in Fig. 9 and subsequent figures is shown by an activity diagram. The flow shown in Fig. 9 may be realized by an information processing method carried out based on an information processing program executed by the CPU 110 of the controller 100 and the CPU 202 of the operation unit 200, respectively.

[0069] When the image forming apparatus 1 is started or reset, in step S101, the write control module 101 of the controller 100 determines an operation mode of the controller 100 based on the remaining life of the HDD 160. The write control module 101 notifies the abstraction module 102 of the controller 100 of the determined operation mode.

[0070] Next, in step S102, the abstraction module 102 stores the operation mode notified from the write control module 101 in a memory or the like in the controller 100. Next, in step S103, the abstraction module 102 notifies the abstraction module 212 of the operation unit 200 of the operation mode of the controller 100. Also, in step S104, when the abstraction module 102 is notified of the operation mode of the operation unit 200 from the abstraction module 212 of the operation unit 200, the abstraction module 102 stores the notified operation mode in a memory or the like in the controller 100.

[0071] On the other hand, when the image forming apparatus 1 is started or reset, in step S201, the monitoring module 211 of the operation unit 200 determines an operation mode of the operation unit 200 based on the remaining life of the eMMC 201. The monitoring module 211 notifies the abstraction module 212 of the operation unit 200 of the determined operation mode.

[0072] The monitoring module 211 does not notify the application 210 of the operation mode of the operation unit 200, and the application 210 does not inquire of the monitoring module 211 about the operation mode of the operation unit 200. Therefore, the application 210 cannot recognize the operation mode of the controller 100.

[0073] Next, in step S202, the abstraction module 212 holds the operation mode notified from the monitoring module 211 in a memory or the like in the operation unit 200. Next, in step S203, the abstraction module 212 notifies the abstraction module 102 of the controller 100 of the operation mode of the operation unit 200. Also, in step S204, when the abstraction module 212 is notified of the operation mode of the controller 100 from the abstraction module 102 of the controller 100, it holds the notified operation mode in a memory or the like in the operation unit 200. Through the above processing, preparation for abstraction processing by the abstraction modules 102, 212 regarding reading and writing from and to storage is completed.

[0074] Fig. 10 is a flow diagram showing an example of processing of the operation unit 200 when the application 210 reads and writes a file. The flow shown in Fig. 10 may be realized by an information processing method performed based on an information processing program executed by the CPU 202 of the operation unit 200.

[0075] When starting to read or write data from or to storage (HDD 160 or eMMC 201), application 210 issues a write request or a read request to abstraction module 212 by specifying the file path and the importance of the data to be read or written. However, even if the read / write destination of data with a certain importance is switched due to deterioration of storage, application 210 cannot recognize the switched read / write destination. A write request and a read request are examples of an access request.

[0076] In step S212, when the abstraction module 212 receives a read / write request from the application 210, the abstraction module 212 performs read / write processing according to the importance included in the read / write request. If the read / write request includes importance 2, the abstraction module 212 performs read / write processing according to importance 2 in step S213. Write processing for importance 2 is shown in Figures 12 and 13. Read processing for importance 2 is shown in Figures 14 and 15.

[0077] When the read / write request includes importance level 4, the abstraction module 212 performs read / write processing according to importance level 4 in step S214. Write processing for importance level 4 is shown in Figures 16 and 17. Read processing for importance level 4 is shown in Figures 18 and 19.

[0078] If the read / write request includes importance 1 or importance 3, the abstraction module 212 performs read / write processing of importance 1 or importance 3 in step S215. Note that in read / write processing of importance 1 or importance 3, the storage to which the file is written and the storage from which the file is read are not changed even if the operation modes of the controller 100 and the operation unit 200 are changed. For this reason, the abstraction modules 212, 102 perform read / write processing according to the path of the target file without performing storage abstraction using the synchronized file list shown in Figs. 12 to 19 described later.

[0079] 11 is a diagram showing an example of a synchronized file list used in read / write processing of importance level 2 or importance level 4. The synchronized file list has an area for holding a "virtual file path" specified by application 210 when reading / writing from / to the storage, and a "real file path" indicating the actual file path on the storage. The synchronized file list is a list that links the "virtual file path" with the "real file path." The "virtual file path" is an example of a temporary access destination, and the "real file path" is an example of an actual access destination.

[0080] The abstraction module 212 or the abstraction module 102 can abstract the storage for reading and writing files and process it transparently by converting the "virtual file path" from the application to a "real file path" according to the synchronized file list. The example shown in Fig. 11 shows that the path (real file path) for reading and writing to the eMMC 201 is used instead of the path (virtual file path) specified by the application 210 for reading and writing a file to the HDD 160.

[0081] For example, a synchronized file list used in a read / write process of importance level 2 is placed in eMMC 201, which is the write destination of a file of importance level 2. For example, a synchronized file list used in a read / write process of importance level 4 is placed in HDD 160, which is the write destination in safety mode SM of operation unit 200, among the write destinations of files of importance level 4. In other words, the synchronized file list is placed in the most reliable storage determined according to the importance and operation mode of the file.

[0082] When reading or writing data of importance level 2 and the controller 100 and the operation unit 200 are in operating state 5, the abstraction module 212 of the operation unit 200 checks the synchronized file list stored in the eMMC 201 corresponding to importance level 2. Then, the abstraction module 212 performs reading or writing to the eMMC 201, which is the storage indicated by the actual file path described in the synchronized file list.

[0083] Furthermore, when reading or writing data of importance level 4, if the controller 100 and the operation unit 200 are in operating state 1, 3 or 5, the abstraction module 102 of the controller 100 checks the synchronized file list stored in the HDD 160 corresponding to importance level 4. Then, the abstraction module 102 performs reading and writing to the HDD 160, which is the storage indicated by the actual file path described in the synchronized file list.

[0084] In read and write processes of importance levels 1 and 3, the virtual file path specified by application 210 becomes the real file path, which is the path on the actual storage, as it is, so the synchronized file list is not used. Therefore, the synchronized file list corresponding to the read and write processes of importance levels 1 and 3 is not arranged in either HDD 160 or eMMC 201.

[0085] Figures 12 and 13 are flow diagrams showing an example of writing data of importance level 2 shown in Figure 7 to storage. The flows shown in Figures 12 and 13 may be realized by an information processing method carried out based on an information processing program executed by the CPU 110 of the controller 100 and the CPU 202 of the operation unit 200, respectively.

[0086] When the abstraction module 212 is requested to write a file by the application 210, in step S221, the abstraction module 212 determines whether or not the operation state is 5. That is, the abstraction module 212 determines whether or not the operation unit 200 is in the normal mode and the controller 100 is in the safety mode SM2.

[0087] If the abstraction module 212 determines that the operating state is not 5, that is, if the abstraction module 212 determines that the operating state is 1-4, it specifies that the data is to be written to the HDD 160. Then, in step S222, the abstraction module 212 notifies the abstraction module 102 of the controller 100 of the file path to be written, and requests the abstraction module 102 to perform a write process to the HDD 160.

[0088] In step S121, the abstraction module 102 that has received the write request requests the HDD 160 to write the file to the file path of the write target. Then, in step S122, the abstraction module 102 writes the file to the file path of the write target in the HDD 160.

[0089] On the other hand, if the abstraction module 212 determines in step S221 that the operating state is 5, writing is to the eMMC 201, and therefore in step S223, the abstraction module 212 reads the synchronized file list on the eMMC 201. Next, in step S224, the abstraction module 212 determines whether or not the file path to be written specified by the application 210 is present in the synchronized file list.

[0090] If the file path to be written exists on the synchronized file list, the file paths have been synchronized between the abstraction modules 102, 212, and the file to be written has been saved from the HDD 160 to the eMMC 201. Therefore, the abstraction module 212 refers to the value of the "actual file path" from the synchronized file list to obtain the file path of the write destination on the eMMC 201, and then performs step S230 in FIG.

[0091] If the file path to be written does not exist on the synchronized file list, the synchronization of the file paths has not been completed between the abstraction modules 102 and 212, so the abstraction module 212 performs step S225. In step S225, the abstraction module 212 notifies the abstraction module 102 of the controller 100 of the file path to be written, and inquires as to whether the file path to be written exists on the HDD 160.

[0092] In step S123, the abstraction module 102 searches the HDD 160, checks whether or not a file with the file path to be written exists on the HDD 160, and responds to the abstraction module 212 as to whether or not a file with the file path to be written exists.

[0093] In step S226, if the abstraction module 212 receives a response that the file path to be written is in the HDD 160, it determines that the file should be saved from the HDD 160 to the eMMC 201, and performs step S227 in Fig. 13. In step S226, if the abstraction module 212 receives a response that the file path to be written is not in the HDD 160, it determines that writing of a new file to the eMMC 201 has occurred, and performs step S229 in Fig. 13.

[0094] 13, the abstraction module 212 requests the abstraction module 102 to copy the file held in the file path of the write target on the HDD 160. Upon receiving the request, the abstraction module 102 copies the file to be written, which is held in the file path of the write target, from the HDD 160, and transfers it to the abstraction module 212, in step S124.

[0095] The abstraction module 212 receives the destination file copied from the HDD 160, copies the received file to a specific area of ​​the eMMC 201 in step S228, and then performs the process of step S229.

[0096] In step S229, when writing of a new file occurs, abstraction module 212 adds a pair of the virtual file path and real file path for the new file to the synchronized file list on eMMC 201, and then performs the process of step S230. Also, when copying a file from HDD 160 to eMMC 201, abstraction module 212 adds a pair of the virtual file path of the copy source and the real file path of the copy destination eMMC 201 to the synchronized file list on eMMC 201. Then, abstraction module 212 performs the process of step S230.

[0097] In step S230, the abstraction module 212 executes the write request from the application to the file path on the eMMC 201 that is expressed in the synchronized file list. As a result, the file to be written is written to the eMMC 201.

[0098] With the above write process, even if the write destination of a file with importance level 2 is changed by switching the operating state, the file can be written to the correct destination storage. Also, even if the file path of the file to be written does not exist in the synchronized file list, the file path can be added to the synchronized file list according to the latest destination. As a result, in subsequent write and read processes, files can be read and written normally based on the synchronized file list.

[0099] When the abstraction module 212 is requested by the application 210 to write a file with importance level 1 or 3, the abstraction module 212 requests the abstraction module 102 of the controller 100 to perform a write process to the HDD 160, as in step S222. The abstraction module 102 that has received the write request requests the HDD 160 to write the file to the file path of the write target, as in step S121. Then, the abstraction module 102 writes the file to the file path of the write target in the HDD 160, as in step S122.

[0100] Figures 14 and 15 are flow diagrams showing an example of reading data of importance level 2 shown in Figure 7 from the storage. The flows shown in Figures 14 and 15 may be realized by an information processing method carried out based on an information processing program executed by the CPU 110 of the controller 100 and the CPU 202 of the operation unit 200, respectively.

[0101] Detailed description of the same processes as those in Figures 12 and 13 will be omitted. Processes with the same step numbers are the same as those shown in Figures 12 and 13. In Figures 14 and 15, processes with the code r added to the end of the step numbers differ from the processes with the same step numbers in Figures 12 and 13 in that they are write processes or read processes.

[0102] When the abstraction module 212 receives a request from the application 210 to read a file and determines in step S221 that the operating state is not 5, it determines that the file is to be read from the HDD 160 and executes step S222r. In step S222r, the abstraction module 212 notifies the abstraction module 102 of the controller 100 of the file path to be read and requests the abstraction module 102 to read the file from the HDD 160.

[0103] In step S121r, abstraction module 102 that has received the read request requests HDD 160 to read a file from the file path of the read target. Then, in step S122r, abstraction module 102 reads the file from the file path of the read target in HDD 160. The subsequent processing is similar to the processing shown in Figs. 12 and 13, except for whether the processing is a file read processing or a file write processing.

[0104] On the other hand, if the abstraction module 212 determines in step S221 that the operating state is 5, reading is from the eMMC 201, and therefore in step S223, the abstraction module 212 reads the synchronized file list on the eMMC 201. Next, in step S224, the abstraction module 212 determines whether or not the file path to be read, specified by the application 210, is present in the synchronized file list.

[0105] If the path of the file to be read exists on the synchronized file list, the file paths have been synchronized between the abstraction modules 102 and 212, and the file to be read has been saved from the HDD 160 to the eMMC 201. Therefore, the abstraction module 212 refers to the value of the "actual file path" from the synchronized file list to obtain the file path of the read source on the eMMC 201, and then performs step S230r in FIG.

[0106] If the file path to be read is not present on the synchronized file list, the synchronization of the file paths between the abstraction modules 102 and 212 has not been completed, and therefore the abstraction module 212 performs step S225. In step S225, the abstraction module 212 notifies the abstraction module 102 of the controller 100 of the file path to be read, and inquires whether the file path to be read exists on the HDD 160. In step S123, the abstraction module 102 searches the HDD 160, checks whether a file with the file path to be read exists on the HDD 160, and responds to the abstraction module 212 as to whether or not the file with the file path to be read exists.

[0107] In step S226, if the abstraction module 212 receives a response that the file path to be read is in the HDD 160, it determines that the file should be saved from the HDD 160 to the eMMC 201, and performs step S227 in Fig. 15. In step S226, if the abstraction module 212 receives a response that the file path to be read is not in the HDD 160, it performs step S229 in Fig. 15. In this case, a request to read a file that does not exist anywhere has occurred.

[0108] 15, the abstraction module 212 requests the abstraction module 102 to copy the file held in the file path of the read target on the HDD 160. Upon receiving the request, the abstraction module 102 copies the file to be read that is held in the file path of the read target from the HDD 160, and transfers it to the abstraction module 212 in step S124.

[0109] In step S228, abstraction module 212 receives the source file copied from HDD 160, copies the received file to a specific area of ​​eMMC 201, and then performs the process of step S229. In step S229, when abstraction module 212 has copied a file from HDD 160 to eMMC 201, abstraction module 212 adds a pair of the virtual file path of the copy source and the real file path of eMMC 201 as the copy destination to the synchronized file list on eMMC 201. Then, abstraction module 212 performs the process of step S230r.

[0110] 14, when a read request for a file that does not exist anywhere is detected, abstraction module 212 adds a pair of dummy file paths to the synchronized file list, and then performs the process of step S230r. For example, abstraction module 212 sets the file path to be read specified by application 210 as a virtual file path. Then, abstraction module 212 adds to the synchronized file list a pair of file paths, including the virtual file path and a file path on eMMC 201 that is a copy destination and has not actually been copied as a real file path.

[0111] In step S230r, the abstraction module 212 executes the read request from the application 210 to the file path on the eMMC 201 that is expressed in the synchronized file list.

[0112] 14, when detecting the occurrence of a read request for a file that does not exist anywhere, abstraction module 212 returns the result of reading from the dummy real file path to application 210. In a typical OS, an error such as ENOENT (Error NO ENTry) indicating that the file cannot be found is returned to application 210, so application 210 can recognize that the file to be read does not exist and can maintain consistency in the read process.

[0113] By the above read process, even if the read process source of a file with importance level 2 is changed by switching the operating state, the file can be read from the correct storage destination. Also, even if the file path of the file to be read does not exist in the synchronized file list, the file path can be added to the synchronized file list according to the latest storage destination. As a result, in the subsequent write process and read process, the file can be read and written normally based on the synchronized file list. Furthermore, if the file to be read does not exist in either the eMMC 201 or the HDD 160, an error can be returned to the application 210 using the OS function.

[0114] When the abstraction module 212 is requested by the application 210 to read a file with importance level 1 or 3, the abstraction module 212 requests the abstraction module 102 of the controller 100 to read the file from the HDD 160, as in step S222r. The abstraction module 102 that has received the read request requests the HDD 160 to read the file from the file path of the read target, as in step S121r. Then, the abstraction module 102 reads the file from the file path of the read target in the HDD 160, as in step S122r.

[0115] Figures 16 and 17 are flow diagrams showing an example of writing data of importance level 4 shown in Figure 7 to storage. The flows shown in Figures 16 and 17 may be realized by an information processing method carried out based on an information processing program executed by the CPU 110 of the controller 100 and the CPU 202 of the operation unit 200, respectively. Detailed description of the same processes as those in Figures 12 and 13 will be omitted.

[0116] 12 and 13, the write destination of the file changes from the HDD 160 to the eMMC 201 upon transition to operating state 5. In contrast, in the write process of a file with importance level 4 shown in Figures 16 and 17, the write destination of the file changes from the eMMC 201 to the HDD 160 upon transition to operating states 2, 4, and 6. Therefore, in Figures 16 and 17, the roles of the abstraction modules 102 and 212 are swapped compared to Figures 12 and 13.

[0117] When the abstraction module 212 is requested to write a file by the application 210, in step S241, the abstraction module 212 determines whether the operation state is 2, 4, or 6. That is, the abstraction module 212 determines whether the operation unit 200 is in the safety mode SM.

[0118] If abstraction module 212 determines that the operating state is not 2, 4, or 6, that is, if abstraction module 212 determines that the operating state is 1, 3, or 5, abstraction module 212 determines that the operation is to be written to eMMC 201. Then, in step S243, abstraction module 212 writes a file to the file path of the write target in eMMC 201.

[0119] On the other hand, if the abstraction module 212 determines that the operating state is 2, 4, or 6, it identifies that the data is to be written to the HDD 160. Then, in step S242, the abstraction module 212 notifies the abstraction module 102 of the controller 100 of the file path to be written, and requests the abstraction module 102 to perform a write process to the HDD 160.

[0120] In step S141, the abstraction module 102 that has received the write request reads the synchronized file list on the HDD 160. Next, in step S142, the abstraction module 102 determines whether or not the file path to be written that is specified by the application 210 is present in the synchronized file list.

[0121] If the file path to be written exists on the synchronized file list, the file paths have been synchronized between the abstraction modules 102, 212, and the file to be written has been saved from the eMMC 201 to the HDD 160. Therefore, the abstraction module 102 refers to the value of the "actual file path" from the synchronized file list to obtain the file path of the write destination on the HDD 160, and then performs step S148 in FIG.

[0122] If the file path to be written does not exist on the synchronized file list, synchronization of the file paths has not been completed between the abstraction modules 102 and 212, and therefore the abstraction module 102 performs step S143. In step S143, the abstraction module 102 notifies the abstraction module 212 of the operation unit 200 of the file path to be written, and inquires as to whether the file path to be written exists on the eMMC 201.

[0123] In step S244, abstraction module 212 searches eMMC 201, checks whether a file with the file path to be written exists on eMMC 201, and responds to abstraction module 102 as to whether a file with the file path to be written exists.

[0124] In step S144, if the abstraction module 102 receives a response that the file path to be written is in the eMMC 201, it determines that the file should be saved from the eMMC 201 to the HDD 160, and performs step S145 in Fig. 17. In step S144, if the abstraction module 102 receives a response that the file path to be written is not in the eMMC 201, it determines that writing of a new file to the HDD 160 has occurred, and performs step S147 in Fig. 17.

[0125] 17, the abstraction module 102 requests the abstraction module 212 to copy the file held in the file path of the write target on the eMMC 201. Upon receiving the request, the abstraction module 212 copies the file to be written that is held in the file path of the write target from the eMMC 201, and transfers the file to the abstraction module 102 in step S245.

[0126] The abstraction module 102 receives the destination file copied from the eMMC 201, copies the received file to a specific area of ​​the HDD 160 in step S146, and then performs the process of step S147.

[0127] In step S147, when writing of a new file occurs, abstraction module 102 adds a pair of the virtual file path and real file path for the new file to the synchronized file list on HDD 160, and then performs the process of step S148. Also, when copying a file from eMMC 201 to HDD 160, abstraction module 102 adds a pair of the virtual file path of the copy source and the real file path of eMMC 201 as the copy destination to the synchronized file list on HDD 160. Then, abstraction module 102 performs the process of step S148.

[0128] In step S148, the abstraction module 102 executes the write request from the application to the file path on the HDD 160 that is expressed in the synchronized file list.

[0129] With the above write process, even if the write destination of a file with importance level 4 is changed by switching the operating state, the file can be written to the correct destination storage. Also, even if the file path of the file to be written does not exist in the synchronized file list, the file path can be added to the synchronized file list according to the latest destination. As a result, in subsequent write and read processes, files can be read and written normally based on the synchronized file list.

[0130] Figures 18 and 19 are flow diagrams showing an example of reading data of importance level 4 shown in Figure 7 from the storage. The flows shown in Figures 18 and 19 may be realized by an information processing method carried out based on an information processing program executed by CPU 110 of controller 100 and CPU 202 of operation unit 200, respectively.

[0131] Detailed description of the same processes as those in Figures 16 and 17 will be omitted. In Figures 18 and 19, processes with the code r added to the end of the step number differ from the processes with the same step numbers in Figures 16 and 17 in that they are write processes or read processes.

[0132] In the above-described read process of a file with importance level 2 shown in Figures 14 and 15, the source from which the file is read changes from the HDD 160 to the eMMC 201 due to a transition to operating state 5. In contrast, in the write process of a file with importance level 4 shown in Figures 18 and 19, the source from which the file is read changes from the eMMC 201 to the HDD 160 due to transitions to operating states 2, 4, and 6. Therefore, in Figures 18 and 19, the roles of the abstraction modules 102 and 212 are swapped compared to Figures 14 and 15.

[0133] When the abstraction module 212 is requested to read a file from the application 210 and determines in step S241 that the operating state is 2, 4, or 6, it determines that the file is to be read from the HDD 160 and executes step S242r. In step S242r, the abstraction module 212 notifies the abstraction module 102 of the controller 100 of the file path to be read, and requests the abstraction module 102 to read the file from the HDD 160.

[0134] In step S141, abstraction module 102 that has received the read request reads the synchronized file list on HDD 160. Next, in step S142, abstraction module 102 determines whether or not the file path to be read that is specified by application 210 is present in the synchronized file list.

[0135] If the file path to be read exists on the synchronized file list, the file paths have been synchronized between the abstraction modules 102, 212, and the file to be read has been saved from the eMMC 201 to the HDD 160. Therefore, the abstraction module 102 refers to the value of the "actual file path" from the synchronized file list to obtain the file path of the read source on the HDD 160, and then performs step S148r in FIG.

[0136] If the file path to be read does not exist on the synchronized file list, synchronization of the file paths between the abstraction modules 102 and 212 has not been completed, and therefore the abstraction module 102 performs step S143. In step S143, the abstraction module 102 notifies the abstraction module 212 of the operation unit 200 of the file path to be read, and inquires as to whether the file path to be read exists on the eMMC 201. In step S244, the abstraction module 212 searches the eMMC 201, checks whether a file with the file path to be read exists on the eMMC 201, and responds to the abstraction module 102 as to whether or not a file with the file path to be read exists.

[0137] In step S144, if the abstraction module 102 receives a response that the file path to be read is in the eMMC 201, it determines that the file should be saved from the eMMC 201 to the HDD 160, and performs step S145 in Fig. 19. In step S144, if the abstraction module 102 receives a response that the file path to be read is not in the eMMC 201, it performs step S147 in Fig. 19. In this case, a request to read a file that does not exist anywhere has occurred.

[0138] 19, abstraction module 102 requests abstraction module 212 to copy a file held in the file path of the file to be read on eMMC 201. Upon receiving the request, abstraction module 212 copies the file to be read that is held in the file path of the file to be read from eMMC 201, and transfers the file to abstraction module 102 in step S245.

[0139] In step S146, abstraction module 102 receives the source file copied from eMMC 201, copies the received file to a specific area of ​​HDD 160, and then performs the process of step S147. In step S147, when abstraction module 102 has copied the file from eMMC 201 to HDD 160, abstraction module 102 adds a pair of the virtual file path of the copy source and the real file path of HDD 160 as the copy destination to the synchronized file list on HDD 160. Then, abstraction module 102 performs the process of step S148r.

[0140] 18, when a read request for a file that does not exist anywhere is detected, abstraction module 102 adds a pair of dummy file paths to the synchronized file list, and then performs the process of step S148r. For example, abstraction module 102 sets the file path to be read specified by application 210 as a virtual file path. Then, abstraction module 102 adds to the synchronized file list a pair of file paths, including the virtual file path and a file path on HDD 160 that is a copy destination and has not actually been copied as a real file path.

[0141] In step S148r, the abstraction module 102 executes the read request from the application 210 to the file path on the HDD 160 that is expressed in the synchronized file list.

[0142] 18, when detecting the occurrence of a read request for a file that does not exist anywhere, the abstraction module 102 returns the result of reading from the dummy real file path to the application 210. In this case as well, as described in FIG 15, an error message indicating that the file cannot be found is returned to the application 210, so that the application 210 can recognize that the file to be read does not exist and can maintain the consistency of the read process.

[0143] By the above read process, even if the read process source of a file with importance level 4 is changed by switching the operating state, the file can be read from the correct storage destination. Also, even if the file path of the file to be read does not exist in the synchronized file list, the file path can be added to the synchronized file list according to the latest storage destination. As a result, in the subsequent write process and read process, the file can be read and written normally based on the synchronized file list. Furthermore, if the file to be read does not exist in either the eMMC 201 or the HDD 160, an error can be returned to the application 210 using the OS function.

[0144] As described above, in this embodiment, even if the write destination of a file with importance level 2 or 4 is changed by switching the operating state according to the storage usage status, the file can be written to the correct destination storage. Also, even if the file path of the file to be written does not exist in the synchronized file list, the file path can be added to the synchronized file list according to the latest destination.

[0145] In addition, even if the source of the read process for a file with importance level 2 or 4 is changed due to switching of the operating state according to the usage status of the storage, the file can be read from the correct storage destination. In addition, even if the file path of the file to be read does not exist in the synchronized file list, the file path can be added to the synchronized file list according to the latest storage destination.

[0146] As a result, in the subsequent write and read processes, files can be read and written normally based on the synchronous file list. In other words, when multiple storage devices to which data is written can be switched, data consistency can be maintained by making it possible to distinguish the storage device that holds the latest file. Furthermore, if the file to be read does not exist in either the eMMC 201 or the HDD 160, an error can be returned to the application 210 using the OS function.

[0147] For example, aspects of the present invention are as follows. <1> a first device including a first storage, having a plurality of operating modes, and capable of executing an application; a second device including a second storage, having a plurality of operation modes, and capable of transmitting and receiving information to and from the first device; The plurality of types of files held in the first storage and the second storage are classified into a first importance level in which a storage to which the files are written changes depending on a usage status of the first storage or the second storage, and a second importance level in which a storage to which the files are written does not change regardless of a usage status of the first storage and the second storage, The first device is when receiving an access request from the application, determining the storage to be accessed by referring to an access destination table that holds access storage information indicating the first storage or the second storage to be accessed for each combination of operation modes of the first device and the second device; If the determined storage is the second storage, requesting access to the second storage from the second device; The first device or the second device is When the access request is a request for accessing a file of the first importance level, accessing the actual access destination by referring to a synchronized file list that associates a virtual access destination included in the access request with an actual access destination; accessing the provisional access destination when the access request is a request to access a file of the second importance; An information processing device comprising: <2> the plurality of operation modes of the first device transition in accordance with a remaining life of the first storage; the plurality of operation modes of the second device transition in accordance with a remaining life of the second storage; The plurality of types of files are classified into the first importance level, whose write destination changes depending on the change in the remaining life, and the second importance level, whose write destination does not change depending on the change in the remaining life; Characterized by <1> The information processing device described in <3> the first device, when the access request is an access request for a file of the first importance, the access storage information held in the access destination table indicates the first storage, and the virtual access destination does not exist in the synchronized file list, adds the virtual access destination and an actual access destination to the synchronized file list, and then accesses the actual access destination of the first storage; Characterized by <1> or <2> The information processing device described in <4> the first device, when the access request is an access request for a file of the first importance, the access storage information held in the access destination table indicates the first storage, and the virtual access destination does not exist in the synchronized file list and the file of the virtual access destination exists in the second storage, copies the file of the virtual access destination from the second storage to the first storage, adds the virtual access destination and the actual access destination to the synchronized file list, and then accesses the actual access destination of the first storage; Characterized by <3> The information processing device described in <5> the second device, upon receiving an access request for the file of the first importance from the first device, adds the virtual access destination and the actual access destination to the synchronized file list when the virtual access destination does not exist in the synchronized file list, and then accesses the actual access destination of the second storage; Characterized by <1> Or <4> 13. The information processing device according to claim 12 . <6> when the second device receives an access request for the file of the first importance from the first device and the virtual access destination does not exist in the synchronized file list and the file of the virtual access destination exists in the first storage, the second device copies the file of the virtual access destination from the first storage to the second storage, adds the virtual access destination and the actual access destination to the synchronized file list, and then accesses the actual access destination of the second storage; Characterized by <5> The information processing device described in <7> <1> Or <6> An information processing device according to any one of claims 1 to 5, an image forming unit that forms an image to be processed by the information processing device; An image forming apparatus comprising: <8> An information processing method implemented by an information processing apparatus having a first device including a first storage, having a plurality of operation modes, and capable of executing an application, and a second device including a second storage, having a plurality of operation modes, and capable of mutually transmitting and receiving information with the first device, The plurality of types of files held in the first storage and the second storage are classified into a first importance level in which a storage to which the files are written changes depending on a usage status of the first storage or the second storage, and a second importance level in which a storage to which the files are written does not change regardless of a usage status of the first storage and the second storage, The first device, a process of determining a storage device to be accessed by referring to an access destination table that holds access storage information indicating the first storage device or the second storage device to be accessed for each combination of operation modes of the first device and the second device when an access request is received from the application; If the determined storage is the second storage, a process of requesting the second device to access the second storage is performed; The first device or the second device, When the access request is a request for accessing a file of the first importance level, a process of accessing the actual access destination by referring to a synchronized file list that associates a virtual access destination included in the access request with an actual access destination; When the access request is a request to access a file of the second importance, a process of accessing the tentative access destination is performed. An information processing method comprising: <9> An information processing program implemented by an information processing device having a first device including a first storage, having a plurality of operation modes, and capable of executing an application, and a second device including a second storage, having a plurality of operation modes, and capable of mutually transmitting and receiving information with the first device, The plurality of types of files held in the first storage and the second storage are classified into a first importance level in which a storage to which the files are written changes depending on a usage status of the first storage or the second storage, and a second importance level in which a storage to which the files are written does not change regardless of a usage status of the first storage and the second storage, The first device, a process of determining a storage device to be accessed by referring to an access destination table that holds access storage information indicating the first storage device or the second storage device to be accessed for each combination of operation modes of the first device and the second device when an access request is received from the application; If the determined storage device is the second storage device, a process of requesting the second device to access the second storage device is performed. The first device or the second device, When the access request is a request for accessing a file of the first importance level, a process of accessing the actual access destination by referring to a synchronized file list that associates a virtual access destination included in the access request with an actual access destination; if the access request is a request to access a file of the second importance, executing a process of accessing the tentative access destination; An information processing program characterized by:

[0148] Although the present invention has been described above based on the embodiments, the present invention is not limited to the requirements shown in the above embodiments. These requirements can be changed without departing from the spirit of the present invention, and can be appropriately determined according to the application form.

[0149] Each function of the above-described embodiments can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a processor programmed to execute each function by software, such as a processor implemented by an electronic circuit, and a device such as an ASIC (Application Specific Integrated Circuit), a DSP (Digital Signal Processor), an FPGA, or a conventional circuit module designed to execute each function described above. [Explanation of symbols]

[0150] 1. Image forming device 2 Automatic document feeder 3. Image Scanning Device 4 Write Unit 5 Printer unit 6 Photoconductor drum 7. Developing device 8 Conveyor belt 9 Fixing device 10 Paper feed tray 11 Power supply 100 Controller 101 Write control module 102 Abstraction Module 110 CPU 120 ASIC 130 DRAM 150 NVRAM 140 SSD 160 HDD 170 USB interface 180 SD card interface 200 Operation section 201 eMMC 202 CPU 203 ROM 204 RAM 205 Operation Panel 206 Network Interface 207 External device connection interface 208 I / O Interface 209 Media Interface 210 Apps 211 Monitoring Module 212 Abstraction Module 300 Image creation section 400 USB memory 500 SD card 600 disks 700 Recording Media BUS CN Connector NW Network [Prior art documents] [Patent documents]

[0151] [Patent Document 1] JP 2018-022440 A

Claims

1. a first device including a first storage, having a plurality of operating modes, and capable of executing an application; a second device including a second storage, having a plurality of operation modes, and capable of transmitting and receiving information to and from the first device; The plurality of types of files held in the first storage and the second storage are classified into a first importance level in which a storage to which the files are written changes depending on a usage status of the first storage or the second storage, and a second importance level in which a storage to which the files are written does not change regardless of a usage status of the first storage and the second storage, The first device is when receiving an access request from the application, determining the storage to be accessed by referring to an access destination table that holds access storage information indicating the first storage or the second storage to be accessed for each combination of operation modes of the first device and the second device; If the determined storage is the second storage, requesting access to the second storage from the second device; The first device or the second device is When the access request is a request for accessing a file of the first importance, accessing the actual access destination by referring to a synchronized file list that associates a virtual access destination included in the access request with an actual access destination; accessing the tentative access destination when the access request is a request to access a file of the second importance; An information processing device comprising:

2. the plurality of operation modes of the first device transition in accordance with a remaining life of the first storage; the plurality of operation modes of the second device transition in accordance with a remaining life of the second storage; The plurality of types of files are classified into the first importance level, in which the write destination changes depending on the change in the remaining life, and the second importance level, in which the write destination does not change depending on the change in the remaining life; 2. The information processing apparatus according to claim 1,

3. the first device, when the access request is an access request for a file of the first importance, the access storage information held in the access destination table indicates the first storage, and the virtual access destination does not exist in the synchronized file list, adds the virtual access destination and an actual access destination to the synchronized file list, and then accesses the actual access destination of the first storage; 2. The information processing apparatus according to claim 1,

4. the first device, when the access request is an access request for a file of the first importance, the access storage information held in the access destination table indicates the first storage, and the virtual access destination does not exist in the synchronized file list and the file of the virtual access destination exists in the second storage, copies the file of the virtual access destination from the second storage to the first storage, adds the virtual access destination and the actual access destination to the synchronized file list, and then accesses the actual access destination of the first storage; 4. The information processing apparatus according to claim 3,

5. the second device, upon receiving from the first device a request to access the file of the first importance, if the virtual access destination does not exist in the synchronized file list, adds the virtual access destination and an actual access destination to the synchronized file list, and then accesses the actual access destination of the second storage; 2. The information processing apparatus according to claim 1,

6. when the second device receives an access request for the file of the first importance from the first device and the virtual access destination does not exist in the synchronized file list and the file of the virtual access destination exists in the first storage, the second device copies the file of the virtual access destination from the first storage to the second storage, adds the virtual access destination and the actual access destination to the synchronized file list, and then accesses the actual access destination in the second storage; 6. The information processing device according to claim 5,

7. An information processing device according to any one of claims 1 to 6, an image forming unit that forms an image to be processed by the information processing device; An image forming apparatus comprising:

8. An information processing method implemented by an information processing apparatus having a first device including a first storage, having a plurality of operation modes, and capable of executing an application, and a second device including a second storage, having a plurality of operation modes, and capable of mutually transmitting and receiving information between the first device, the method comprising: The plurality of types of files held in the first storage and the second storage are classified into a first importance level in which a storage to which the files are written changes depending on a usage status of the first storage or the second storage, and a second importance level in which a storage to which the files are written does not change regardless of a usage status of the first storage and the second storage, The first device, a process of determining a storage device to be accessed by referring to an access destination table that holds access storage information indicating the first storage device or the second storage device to be accessed for each combination of operation modes of the first device and the second device when an access request is received from the application; If the determined storage is the second storage, a process of requesting the second device to access the second storage is performed; The first device or the second device, When the access request is a request for accessing a file of the first importance level, a process of accessing the actual access destination by referring to a synchronized file list that associates a virtual access destination included in the access request with an actual access destination; When the access request is a request to access a file of the second importance, a process of accessing the tentative access destination is performed. An information processing method comprising:

9. An information processing program implemented by an information processing device having a first device including a first storage, having a plurality of operation modes, and capable of executing an application, and a second device including a second storage, having a plurality of operation modes, and capable of mutually transmitting and receiving information with the first device, The plurality of types of files held in the first storage and the second storage are classified into a first importance level in which a storage to which the files are written changes depending on a usage status of the first storage or the second storage, and a second importance level in which a storage to which the files are written does not change regardless of a usage status of the first storage and the second storage, The first device includes: a process of determining a storage device to be accessed by referring to an access destination table that holds access storage information indicating the first storage device or the second storage device to be accessed for each combination of operation modes of the first device and the second device when an access request is received from the application; If the determined storage is the second storage, a process of requesting the second device to access the second storage is performed; The first device or the second device, When the access request is a request for accessing a file of the first importance level, a process of accessing the actual access destination by referring to a synchronized file list that associates a virtual access destination included in the access request with an actual access destination; if the access request is a request to access a file of the second importance, executing a process of accessing the tentative access destination; An information processing program characterized by:

Citation Information

Patent Citations

  • JP2018‐022440A