JP2004046801A - Image forming apparatus and program stopping method - Google Patents

Abstract

An object of the present invention is to provide an image forming apparatus and a program stopping method that can easily prevent reusable use of a recording medium that can be inserted and removed.
An image forming apparatus having a program for performing processing using hardware resources and a slot (125) into which a recording medium (126) can be inserted and removed, wherein a state monitoring unit (123) monitors the insertion and removal of the recording medium (126) from the slot (125). , 124, the recording medium 126 inserted into the slot 125 is made accessible, and the recording medium starting means 121 is made inaccessible, and the recording medium 126 removed from the slot 125 is made accessible. A program activating means 52 for reading and starting the program from the recording medium 126 and stopping the program read and activated from the recording medium 126 when the removal of the recording medium 126 from the slot 125 is notified. Solves the above problem.
[Selection] Fig. 8

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to an image forming apparatus and a program stopping method, and more particularly to an image forming apparatus and a program stopping method for stopping a program started from a removable recording medium.
[0002]
[Prior art]
2. Description of the Related Art In recent years, an image forming apparatus (hereinafter, referred to as a multifunction peripheral) in which functions of respective apparatuses such as a printer, a copier, a facsimile, and a scanner are housed in one housing has become known. This multifunction machine includes a display unit, a printing unit, an imaging unit, and the like in one housing, and four types of software corresponding to a printer, a copier, a facsimile, and a scanner, respectively. It operates as a copy, facsimile and scanner. Patent Literature 1 describes an example of the above-described fusion machine.
[0003]
After turning on the power of such a multifunction peripheral, a BIOS (Basic Input / Output System) and a boot loader (Boot Loader) are activated. The boot loader expands a kernel (Kernel) and a root file system on a RAM (Random Access Memory) to activate the kernel. Then the kernel mounts the root file system. Here, mounting means starting the file system, peripheral devices, and the like in an accessible state.
[0004]
After the kernel is started, an application / service starting program for starting an application (hereinafter referred to as an application) and various services is started. The application / service startup program is a process that is first started in the MFP, mounts a file system according to a predetermined setting file, and starts a service layer and an application process required for the operation of the MFP according to the predetermined setting file. I was
[0005]
In such a conventional multifunction peripheral, a program of an application to be started is recorded in a hard disk device, a ROM, or the like. Patent Literature 2 discloses an example of an image processing apparatus that adds a program of an application to be started to a hard disk device, a ROM, or the like.
[0006]
Also, when an SD card is inserted into a slot as an example of a recording medium, the application / service activation program mounts a file system according to a setting file recorded on the SD card, and executes an application process recorded on the SD card. Was started according to a predetermined setting file. In a conventional multifunction machine, by starting an application from a recording medium such as an SD card that can be hot-swappable, it is possible to easily add a new application, upgrade the application, and expand functions.
[0007]
[Patent Document 1]
JP-A-2002-84383
[0008]
[Patent Document 2]
JP 2001-76125 A
[0009]
[Problems to be solved by the invention]
However, conventional multi-function devices can easily add new applications, upgrade applications, and expand functions. Therefore, there is a possibility that a multi-function device can use a hot-swappable recording medium such as an SD card. There was a problem of being expensive. Therefore, it has been necessary to provide a function of preventing a conventional multifunction device from using a recording medium such as an SD card that can be hot-swapped and used by a plurality of multifunction devices.
[0010]
SUMMARY An advantage of some aspects of the invention is to provide an image forming apparatus and a program stopping method that can easily prevent re-use of a recording medium that can be inserted and removed.
[0011]
[Means for Solving the Problems]
In order to solve the above problem, the present invention provides an image forming apparatus having a program for performing processing related to image formation using hardware resources, and a slot in which a recording medium can be inserted and removed. State monitoring means for monitoring the insertion / removal of a medium, recording medium activation means for setting a recording medium inserted in the slot to an accessible state, and for making a recording medium removed from the slot inaccessible, While reading and starting the program from the recording medium in the enabled state, when the state monitoring unit notifies the user that the recording medium is extracted from the slot, the program read from the recording medium and started is stopped. And a program activating means.
[0012]
The present invention also provides an image forming apparatus having a program for performing processing related to image formation using hardware resources, and a slot in which a recording medium can be inserted and removed, wherein a state in which the recording medium is inserted into and removed from the slot is monitored. Monitoring means, recording medium starting means for making the recording medium inserted into the slot accessible, and making the recording medium removed from the slot inaccessible, reading and starting from the recording medium Then, when the removal of the recording medium from the slot is notified, after stopping inter-process communication with another process, a program that stops itself and a program that is read from the recording medium in the accessible state are read out. On the other hand, when it is notified that the recording medium is removed from the slot, the recording medium activating means is activated to activate the recording medium. And having a program activation unit for the recording medium withdrawn from Tsu preparative inaccessible state.
[0013]
Further, the present invention is a program stopping method for an image forming apparatus having a program for performing processing relating to image formation using hardware resources and a slot in which a recording medium can be inserted and removed, wherein the program is inserted into and removed from the slot. Monitoring the state of the recording medium, stopping the recording medium to make the recording medium extracted from the slot inaccessible, and receiving notification of the removal of the recording medium from the slot, read from the recording medium. And stopping the started program.
[0014]
Further, the present invention is a program stopping method for an image forming apparatus having a program for performing processing relating to image formation using hardware resources and a slot in which a recording medium can be inserted and removed, wherein the program is inserted into and removed from the slot. When the notification of the removal of the recording medium from the slot is notified, the inter-process communication with another process is stopped, and then the program read from the recording medium and started is stopped. The method includes a program stopping step and a recording medium stopping step of making the recording medium extracted from the slot inaccessible.
[0015]
According to the present invention, the program read out from the recording medium and started is stopped according to the removal of the recording medium from the slot, so that the reusable recording medium can be easily reused.
[0016]
BEST MODE FOR CARRYING OUT THE INVENTION
Next, embodiments of the present invention will be described with reference to the drawings.
[0017]
FIG. 1 shows a configuration diagram of an embodiment of a multifunction peripheral according to the present invention. The multifunction device 1 includes a black-and-white laser printer (B & W LP) 11, a color laser printer (ColorLP) 12, hardware resources 13 such as a scanner and a facsimile, a software group 20, and a multifunction device starting unit 50. Further, the software group 20 has an application 30 and a platform 40.
[0018]
The application 30 performs processing unique to user services related to image forming processing such as printer, copy, facsimile, and scanner.
[0019]
The application 30 includes a printer application 31 that is a printer application having a page description language (PDL, PCL) and postscript (PS), a copy application 32 that is a copy application, and a fax application 33 that is a facsimile application. And a scanner application 34 as a scanner application, a network file application 35 as a network file application, and a process inspection application 36 as a process inspection application.
[0020]
Further, the platform 40 interprets a processing request from the application 30 to generate a hardware resource acquisition request, and arbitrates an acquisition request from the control service by managing one or more hardware resources. It is configured to include a system resource manager (hereinafter, referred to as SRM) 43 and an operating system (hereinafter, referred to as OS) 41.
[0021]
The control services include a system control service (hereinafter, referred to as SCS) 42, an engine control service (hereinafter, referred to as ECS) 44, a memory control service (hereinafter, referred to as MCS) 45, an operation panel control service (hereinafter, referred to as OCS) 46, and a fax machine. It is configured to have one or more service modules such as a control service (hereinafter, referred to as FCS) 47 and a network control service (hereinafter, referred to as NCS) 48.
[0022]
Note that the platform 40 is configured to have an application program interface (hereinafter, referred to as an API) that enables a processing request from the application 30 to be received by a predefined function. The OS 41 is, for example, Unix (registered trademark), and executes the software of the platform 40 and the application 30 in parallel as processes.
[0023]
The process of the SRM 43, together with the SCS 42, controls the system and manages hardware resources. For example, the process of the SRM 43 is performed by an upper layer using hardware resources such as an engine, a memory, an HDD file, and host I / O (Centro I / F, network I / F, IEEE1394 I / F, RS232C I / F, etc.). Arbitration is performed according to the request, and execution is controlled.
[0024]
Specifically, the SRM 43 determines whether the requested hardware resource is available (whether it is not used by another request), and if it is available, the requested hardware resource is available. To the upper layer. Further, the SRM 43 performs scheduling for using hardware resources in response to a request from an upper layer, and directly executes the contents of the request (for example, paper conveyance and image forming operation by a printer engine, memory reservation, file generation, etc.). ing.
[0025]
The SCS process performs processes such as application management, operation unit control, system screen display, LED display, hardware resource management, and interrupt application control. The process of the ECS 44 controls the engines of the black and white laser printer 11, the color laser printer 12, the hardware resources 13, and the like.
[0026]
The process of the MCS 45 performs memory control such as acquisition and release of an image memory, use of an HDD, and compression and decompression of image data. The process of the OCS 46 controls an operation panel serving as information transmission means between the operator and the main body control.
[0027]
The FCS 47 process performs facsimile transmission / reception using PSTN or ISDN from each application layer of the system controller, registration / quotation of various facsimile data managed in a backup memory, facsimile reading, facsimile reception printing, fusion transmission / reception. API for the application.
[0028]
The process of the NCS 48 provides a service that can be used in common to applications that require network I / O, and distributes the data received from the network by each protocol to each application, and the data from each application. Mediation when sending to the network side.
[0029]
For example, the NCS 48 controls data communication with a network device connected via a network by HTTP (HyperText Transfer Protocol Daemon) by HTTP (HyperText Transfer Protocol).
[0030]
The multifunction device 1 can perform processing required in common by each application on the platform 40 in a unified manner. Next, the hardware configuration of the MFP 1 will be described.
[0031]
FIG. 2 shows a hardware configuration diagram of an embodiment of the multifunction peripheral according to the present invention. The MFP 1 includes a controller 60, an operation panel 80, an FCU 81, and an engine unit 82. The controller 60 includes a CPU 61, a system memory 62, a north bridge (NB) 63, a south bridge (SB) 64, an ASIC 66, a local memory 67, an HDD 68, a network interface card (NIC) 69, and an SD card. , A USB device 71, an IEEE 1394 device 72, and a Centronics 73.
[0032]
The operation panel 80 is connected to the ASIC 66 of the controller 60. The FCU 81 and the engine unit 82 are connected to the ASIC 66 of the controller 60 via a PCI bus 83.
[0033]
In the controller 60, the local memory 67, the HDD 68, and the like are connected to the ASIC 66, and the CPU 61 and the ASIC 66 are connected via the NB 63 of the CPU chip set. The controller 60 connects the CPU 61 and the ASIC 66 via the NB 63 to cope with a case where the interface of the CPU 61 is not disclosed. The ASIC 66 and the NB 63 are connected via an AGP (Accelerated Graphics Port) 65.
[0034]
As described above, in order to control the execution of one or more processes forming the application 30 and the platform 40 of FIG. 1, the performance degradation is reduced by connecting the ASIC 66 and the NB 63 via the AGP 65 instead of the low-speed PCI bus. I'm preventing.
[0035]
The CPU 61 performs overall control of the multifunction peripheral 1. The CPU 61 activates and executes the SCS 42, the SRM 43, the ECS 44, the MCS 45, the OCS 46, the FCS 47, and the NCS 48 as processes on the OS 41, and the printer application 31, the copy application 32, the fax application 33, and the scanner application 34 which form the application 30. , The net file application 35 and the process inspection application 36 are activated and executed.
[0036]
The NB 63 is a bridge for connecting the CPU 61, the system memory 62, the SB 64, the ASIC 66, the NIC 69, the SD card slot 70, the USB device 71, the IEEE 1394 device 72, and the Centronics 73.
[0037]
The SB 64, NIC 69, SD card slot 70, USB device 71, IEEE 1394 device 72, and Centronics 73 are connected to the NB 63 via a PCI bus 74. The SB 64 is a bridge for connecting the PCI bus 74 to a ROM, peripheral devices, and the like.
[0038]
The system memory 62 is a memory used as a drawing memory or the like of the multifunction peripheral 1. The local memory 67 is a memory used as a copy image buffer and a code buffer.
[0039]
The ASIC 66 is an IC for image processing having hardware components for image processing. The HDD 68 is an example of a storage (auxiliary storage device) that stores image data, document data, programs, font data, forms, and the like.
[0040]
The NIC 69 is an interface device that connects the MFP 1 to a network. The SD card slot 70 is capable of inserting and removing an SD card, and performs an interrupt corresponding to insertion or removal of the SD card to an SD card status monitor driver described later. The USB device 71, the IEEE 1394 device 72, and the Centronics 73 are interfaces conforming to respective standards.
[0041]
The operation panel 80 is an operation unit that receives an input operation from the operator and performs display for the operator. The FCU 81 has a memory. The memory of the FCU 81 is used, for example, to temporarily store facsimile data received when the power of the MFP 1 is OFF.
[0042]
The MFP starter 50 in FIG. 1 is first executed when the power of the MFP 1 is turned on, and starts the platform 40 and the application 30. FIG. 3 is a configuration diagram of an example of the multifunction peripheral starting unit. The multifunction peripheral starting unit 50 has a ROM monitor 51 and a program starting unit 52.
[0043]
The BIOS and the ROM monitor 51 as a boot loader are executed when the power is turned on, and perform initialization of hardware, diagnosis of the controller 60, initialization of software, and the like. The ROM monitor 51 expands the kernel and the root file system on the system memory 62 and activates the kernel. Then the kernel mounts the root file system.
[0044]
The program starting unit 52 as an application / service starting program is called from the kernel, and secures a memory area on the system memory 62 and the local memory 67. The program starting unit 52 is a process that is started first in the MFP 1, and mounts a file system according to a predetermined setting file.
[0045]
The program starting unit 52 reads the application 30 and the platform 40 programs necessary for the operation of the multi-function peripheral 1 from a ROM or the like according to a predetermined setting file, and stores the read programs in the system memory 62 and the local memory 67. And activates the processes of the application 30 and the platform 40.
[0046]
Further, the processing of the program starting unit 52 will be described. The program starting unit 52 reads a predetermined master setting file at the time of starting, and mounts a file system and starts a process according to the read master setting file. For example, in the case of a file tree as shown in FIG. 4, the program starting unit 52 reads “/etc/init.conf” as a master setting file at the time of starting. FIG. 4 shows a configuration diagram of an example of a file tree.
[0047]
If a description of the mount exists in the read master setting file, the program activation unit 52 executes a mount process according to the description of the mount. For example, in the case of a master setting file as shown in FIG. 5, the program starting unit 52 mounts a file system on the SD cards 0 to 3 according to the description of the mount. FIG. 5 shows a configuration diagram of an example of the master setting file.
[0048]
Also, when a predetermined setting file exists at the root of the mounted file system, or when a predetermined directory including a file having a predetermined extension exists at the root of the mounted file system, the program starting unit 52 executes the predetermined setting. A file or a file having a predetermined extension is read and a file system is mounted.
[0049]
For example, when the setting file “init.conf” or “init.cnf” as shown in FIG. 6 exists at the root of the mounted SD card file system, the program starting unit 52 performs the mounting process according to the description of the mount existing in the setting file. Execute. FIG. 6 shows a configuration diagram of an example of the setting file.
[0050]
If the directory “init.d” as shown in FIG. 7 exists at the root of the mounted SD card file system and the directory includes files with the extensions “conf” and “cnf”, Execute the mount process according to the description of the mount existing in. FIG. 7 shows a configuration diagram of an example of a file tree of the SD card.
[0051]
Note that the file system that can be mounted by the program activation unit 52 includes “gzromfs” as shown in FIGS. 5 and 6. The file system “gzromfs” expands the gzip-compressed ROMFS format file on the RAM and mounts it.
[0052]
Hereinafter, an example will be described in which an SD card in which an application is recorded is inserted into the MFP 1 or the SD card is removed from the MFP 1 while the power of the MFP 1 is kept turned on. FIG. 8 is an explanatory diagram of one embodiment of the program stopping method according to the present invention.
[0053]
In the explanatory diagram of FIG. 8, among the configurations of the multifunction machine 1, components necessary for description are shown, and components not required for description are omitted. Further, although the multifunction peripheral 1 of FIG. 8 includes two SD card slots 125 and 127, it may include three or more SD card slots.
[0054]
In the SD cards 126 and 128, a root file system, a service layer, an application, font data, and the like are recorded as a binary file including a header in which module information is stored and ROMFS format data. The SD cards 126 and 128 can be so-called hot-swap while the power of the multifunction machine 1 is kept on.
[0055]
The SD card slots 125 and 127 are capable of inserting and removing the SD cards 126 and 128, and perform an interrupt to the SD card access driver 124 according to insertion or removal of the SD cards 126 and 128.
[0056]
The SD card access driver 124 controls access to the SD card 126, and notifies the SD card status monitor driver 123 of insertion or removal of the SD cards 126, 128 in response to an interrupt from the SD card slots 125, 127. I do.
[0057]
The SD card status monitor driver 123 manages status information of the SD cards 126 and 128, such as insertion, extraction, mounting, and unmounting of the SD cards 126 and 128, and stores the status information of the SD cards 126 and 128 in a program starting unit. Notify 52.
[0058]
The program activating unit 52 activates the SD card check program 121 according to insertion or removal of the SD cards 126 and 128. In addition, the program starting unit 52 starts the programs in the SD cards 126 and 128 according to the status information of the SD cards 126 and 128 from the SD card status monitor driver 123.
[0059]
The SD card check program 121 is for checking whether the partitions of the SD cards 126 and 128 are correct and the state of the file system is correct, and makes the file system 122 usable. The SD card check program 121 has, for example, a check function of the SD cards 126 and 128, a mount function, an unmount function, a status notification function, and the like.
[0060]
Next, the processing procedure of the program stopping method according to the present invention will be described with reference to flowcharts. After activating the application 30 of the MFP 1 and the process of the platform 40, the program activation unit 52 enters an event waiting state. FIG. 9 shows a flowchart of an example of the event waiting process.
[0061]
In FIG. 9, in step S1, the program activation unit 52 determines whether an event has occurred. If it is determined that no event has occurred (NO in S1), the program starting unit 52 repeats the processing in step S1. If it is determined that an event has occurred (YES in S1), the program starting unit 52 proceeds to step S2.
[0062]
For example, when the SD card 126 or 128 is inserted into the SD card slot 125 or 127, the SD card access driver 124 sets the insertion of the SD card 126 or 128 in response to the interrupt from the SD card slot 125 or 127. Notify the monitor driver 123.
[0063]
The SD card status monitor driver 123 notifies the program starting unit 52 of the insertion of the SD card 126 or 128. That is, the program starting unit 52 determines that an event has occurred when the SD card status monitor driver 123 notifies the insertion of the SD card 126 or 128.
[0064]
When the SD card 126 or 128 is removed from the SD card slot 125 or 127, the SD card access driver 124 removes the SD card 126 or 128 in response to an interrupt from the SD card slot 125 or 127. The status monitor driver 123 is notified.
[0065]
The SD card status monitor driver 123 notifies the program starting unit 52 of the removal of the SD card 126 or 128. That is, the program starting unit 52 determines that an event has occurred when the removal of the SD card 126 or 128 is notified from the SD card status monitor driver 123.
[0066]
In step S2, the program starting unit 52 determines the content of the event. If the content of the event is the detection of the insertion of the SD card 126 or 128, the program starting unit 52 proceeds to Step S3. In step S3, an SD card insertion detection process described later is performed. On the other hand, if the content of the event is detection of removal of the SD card 126 or 128, the program starting unit 52 proceeds to step S4. In step S4, an SD card removal detection process described later is performed.
[0067]
FIG. 10 shows a flowchart of an example of the SD card insertion detection process. In step S11, the program starting unit 52 starts the SD card check program 121. Proceeding to step S12 following step S11, the SD card check program 121 mounts the SD cards 126 and 128, notifies the SD card status monitor driver 123 of the fact, and stops the processing.
[0068]
Proceeding to step S13 following step S12, when the program starting unit 52 is notified from the SD card status monitor driver 123 that the SD cards 126 and 128 have been mounted, the program starting unit 52 executes FIG. A setting file such as 12 is read and analyzed.
[0069]
FIG. 11 is a configuration diagram of an example of a setting file recorded on the application activation SD card. FIG. 12 is a configuration diagram of an example of a setting file recorded on the process inspection SD card.
[0070]
The setting file in FIG. 11 includes a process of mounting the gzip-compressed ROMFS format mount target module “printer.mod” to the mount point “/ arch / printer” and executing the mount target module “printer.mod”. The gzip-compressed ROMFS format mount target module “scanner.mod” is mounted on the mount point “/ arch / scanner”, and the mounted mount target module “scanner.mod” is executed.
[0071]
The setting file of FIG. 12 represents a process of mounting the gzip-compressed ROMFS format mount target module “factory.mod” to the mount point “/ arch / factory” and executing the mount target module “factory.mod”. ing.
[0072]
Note that the application starting SD card is an SD card used to add an application to the multifunction device 1, and corresponds to, for example, the SD card 126 in FIG. The process inspection SD card is an SD card used for performing a process inspection of the MFP 1 in a factory or the like, and corresponds to, for example, the SD card 128 in FIG.
[0073]
Proceeding to step S14 following step S13, the program starting unit 52 performs a mounting process according to the description of the mount existing in the setting file as shown in FIG. Proceeding to step S15, the program starting unit 52 reads a module information file (for example, version.txt) as shown in FIGS. 13 to 15 from the mount target module mounted in step S14, and reads the module information file as "/ tmp / Module ID.txt ".
[0074]
FIG. 13 is a configuration diagram of an example of a module information file read from within the printer module. FIG. 14 is a configuration diagram of an example of a module information file read from within the scanner module. FIG. 15 is a configuration diagram of an example of a module information file read from within the process inspection module.
[0075]
13 and 14 are configured to include a module ID and version information. The module information file in FIG. 15 is configured to include a module ID, version information, and license information.
[0076]
Proceeding to step S16, the program activation unit 52 adds the file name of the module to be mounted mounted in step S14 as "MOUNTFILE" in the module information file as shown in FIGS.
[0077]
FIG. 16 is a configuration diagram of an example of a module information file for a printer application to which a file name of a module to be mounted is added. FIG. 17 is a configuration diagram of an example of a module information file for a scanner application to which a file name of a module to be mounted is added. FIG. 18 is a configuration diagram of an example of a module information file for a process inspection application to which a file name of a module to be mounted is given.
[0078]
The module information files in FIGS. 16 and 17 are configured to include the module ID, version information, and the file name of the mounted module to be mounted. The module information file in FIG. 18 is configured to include the module ID, version information, license information, and the file name of the mounted module to be mounted.
[0079]
Then, proceeding to step S17 following step S16, the program starting unit 52 starts the process of the program recorded on the SD cards 126 and 128.
[0080]
Accordingly, even if the SD cards 126 and 128 are inserted while the power is turned on, the MFP 1 can automatically start the process of the application recorded on the SD cards 126 and 128. For example, in the MFP 1 of FIG. 1, applications in the SD cards 126 and 128 are added as one of the applications 30.
[0081]
In the SD card insertion detection processing of FIG. 10, all the setting files as shown in FIG. 11 recorded on the mounted SD card 126 or the setting files as shown in FIG. 12 recorded on the mounted SD card 128 are read out. However, an electronic authentication check may be performed to prevent unauthorized copying of the SD card 126.
[0082]
19 and 20 show a flowchart of an example of an SD card insertion detection process having an electronic authentication check function. Steps S21 and S22 are the same as the processing in the flowchart of FIG.
[0083]
When notified that the SD card 126 or 128 has been mounted from the SD card status monitor driver 123, the program activation unit 52 proceeds to step S23. In step S23, the program starting unit 52 searches the SD card 126 or 128 mounted in step S12 for a setting file.
[0084]
Proceeding to step S24, if the setting file exists in the mounted SD card 126 or 128 (YES in S24), the program activating unit 52 proceeds to step S25. If the setting file does not exist in the mounted SD card 126 or 128 (NO in S24), the program starting unit 52 proceeds to step S32. In step S25, the program activation unit 52 performs an authentication check of the setting file using the electronic authentication check library.
[0085]
The authentication check of the setting file is performed as shown in the flowchart of FIG. FIG. 21 is a flowchart of an example of the process of the authentication check of the setting file.
[0086]
In step S41, the program activation unit 52 determines whether or not the SD card 126 or 128 has a target file used for the authentication check of the setting file. The target file used for the authentication check of the setting file includes a setting file and an electronic signature file created from a message digest of the setting file and the serial ID of the SD card (hereinafter referred to as MD).
[0087]
FIG. 22 is an image diagram of an example of the target file recorded on the SD card. In the example of FIG. 22, “printer.cnf” represents a setting file, “printer.lic” represents an electronic signature file used for authentication check of the setting file, and “printer.mod” represents a module file to be mounted. , “Printer.mac” represents an electronic signature file used for the authentication check of the module to be mounted.
[0088]
If it is determined that there is a target file to be used for the authentication check of the setting file (YES in S41), the program starting unit 52 acquires the setting file and the electronic signature file to be used for the authentication check of the setting file from the SD card 126 or 128. Proceed to step S42.
[0089]
In step S42, the program starting unit 52 acquires the serial ID of the SD card 126 or 128 from the SD card 126 or 128. Proceeding to step S43, the program starting unit 52 creates an MD1 of the setting file obtained in step S41 and the serial ID of the SD card 126 or 128 obtained in step S42. Proceeding to step S44 following step S43, the program activation unit 52 decrypts the electronic signature file acquired in step S41 with the public key to create the MD2.
[0090]
Proceeding to step S45, the program starting unit 52 determines whether the MD1 created in step S43 is equal to the MD2 created in step S44. If it is determined that MD1 and MD2 are equal (YES in S45), the program starting unit 52 proceeds to step S46, and determines that the authentication check of the setting file is OK.
[0091]
On the other hand, if it is determined that MD1 and MD2 are not equal (NO in S45), the program starting unit 52 proceeds to step S47, and determines that the authentication check of the setting file is NG. This is because if MD1 and MD2 are not equal, the file recorded on the SD card 126 or 128 has a high possibility of being illegally copied.
[0092]
If it is determined that there is no target file used for the authentication check of the setting file (NO in S41), the program starting unit 52 proceeds to step S47, and determines that the authentication check of the setting file is NG.
[0093]
Returning to FIG. 19, if the authentication check of the setting file is OK (YES in S25), the program starting unit 52 proceeds to step S26 and analyzes the setting file as shown in FIG. 11 or 12. If the authentication check of the setting file is NG (NO in S25), the program starting unit 52 proceeds to step S27.
[0094]
In step S27, it is determined whether or not the program activation unit 52 has searched for an EOF (End Of File) recorded in one setting file. If it is determined that the EOF has been searched (YES in S27), the program starting unit 52 returns to Step S23. If it is determined that the EOF has not been searched (NO in S27), the program starting unit 52 proceeds to step S28.
[0095]
In step S28, if there is a description of the mount in the setting file, the program starting unit 52 performs an authentication check of the module to be mounted using the electronic authentication check library. The authentication check of the module to be mounted is performed as shown in the flowchart of FIG. FIG. 23 is a flowchart of an example of an authentication check process of the module to be mounted.
[0096]
In step S51, the program starting unit 52 determines whether or not the SD card 126 or 128 has a file to be used for the authentication check of the module to be mounted. The target file used for the authentication check of the module to be mounted includes the module file to be mounted and the electronic signature file created from the MD of the module file and the model information of the MFP 1.
[0097]
If it is determined that there is a file to be used for the authentication check of the module to be mounted (YES in S51), the program activation unit 52 uses the SD card 126 or 128 to check the module file to be mounted and the module file to be mounted. The digital signature file is obtained, and the process proceeds to step S52.
[0098]
In step S52, the program starting unit 52 acquires the model information of the multifunction peripheral 1. Proceeding to step S53, the program starting unit 52 creates an MD1 of the module file acquired in step S51 and the model information of the multifunction peripheral 1 acquired in step S52. Proceeding to step S54, the program starting unit 52 decrypts the electronic signature file acquired in step S51 with the public key to create the MD2.
[0099]
Proceeding to step S55, the program starting unit 52 determines whether the MD1 created in step S53 is equal to the MD2 created in step S54. If it is determined that MD1 and MD2 are equal (YES in S55), the program starting unit 52 proceeds to step S56, and determines that the authentication check of the module to be mounted is OK.
[0100]
On the other hand, if it is determined that MD1 and MD2 are not equal (NO in S55), the program starting unit 52 proceeds to step S57, and determines that the authentication check of the module to be mounted is NG. If MD1 and MD2 are not equal, the file recorded on the SD card 126 or 128 has a high possibility of being fraudulently copied or falsified.
[0101]
If it is determined that there is no target file to be used for the authentication check of the mount target module (NO in S51), the program starting unit 52 proceeds to step S57, and determines that the authentication check of the mount target module is NG.
[0102]
Returning to FIG. 20, if the authentication check of the module to be mounted is OK (YES in S28), the program starting unit 52 proceeds to step S29 and performs the mounting process according to the description of the mount existing in the setting file as shown in FIG. I do.
[0103]
Proceeding to step S30, the program starting unit 52 reads a module information file (for example, version.txt) as shown in FIGS. 13 to 15 from the mount target module mounted in step S29, and reads the module information file as "/ tmp / Module ID.txt ".
[0104]
Proceeding to step S31, the program starting unit 52 adds the file name of the mount target module mounted in step S29 as "MOUNTFILE" in the module information file as shown in FIGS. 16 to 18, and then returns to step S26. Note that the program activation unit 52 repeats the processing of steps S23 to S31 until the authentication check of all the setting files recorded on the SD card 126 or 128 is performed.
[0105]
After performing the authentication check of all the setting files recorded on the SD card 126 or 128, the program starting unit 52 determines that the setting file does not exist on the mounted SD card 126 or 128 (NO in S24). The process proceeds to step S32. In step S32, the program starting unit 52 executes the module mounted in step S29. Note that the module whose authentication check of the mount target module is NG is not executed in step S32 because it is not mounted in step S29.
[0106]
When the SD card 126 or 128 is suddenly removed, the program starting unit 52 needs to unmount the SD card 126 or 128. Therefore, the program starting unit 52 starts the SD card check program 121 to perform the unmount processing of the SD card 126 or 128. Let
[0107]
FIG. 24 shows a flowchart of an example of the SD card removal detection processing. In step S61, the program starting unit 52 starts the SD card check program 121. In step S62, the SD card check program 121 unmounts the SD card 126 or 128, notifies the SD card status monitor driver 123 that the SD card 126 or 128 has been unmounted, and stops the processing.
[0108]
Proceeding to step S63, the program starting unit 52 stops the application executed from the SD card 126 or 128 in step S17 or S32. Then, proceeding to step S64, the program starting unit 52 checks whether or not the act of suddenly removing the SD card 126 or 128 is treated as a service call (hereinafter, simply referred to as SC) by the following SC check processing. The service call refers to a function of notifying a failure or the like detected by the self-diagnosis function of the MFP 1.
[0109]
FIG. 25 is a flowchart illustrating an example of the SC check process. Proceeding to step S71, the program starting unit 52 determines whether or not “/ tmp / module ID.txt” exists in the file tree as shown in FIG.
[0110]
If it is determined that “/ tmp / module ID.txt” is present (YES in S71), the program starting unit 52 proceeds to step S72, and “MOUNTFILE: mnt / sdX / yyy.mod ". Note that “X” included in “MOUNTFILE: mnt / sdX / yyy.mod” indicates an SD card slot number. For example, in the case of the module information file shown in FIG. 16, the program starting unit 52 acquires “MOUNTFILE: mnt / sd1 / printer.mod”.
[0111]
Proceeding to step S73, the program starting unit 52 determines whether or not the SD card slot number obtained in step S72 matches the SD card slot number from which the SD card 126 or 128 has been removed. If it is determined that they match (YES in S73), the program activation unit 52 determines whether or not “LICENSE: FREE” is described as license information in the module information file from which “MOUNTFILE” has been acquired in step S72.
[0112]
If it is determined that “LICENSE: FREE” is described (YES in S74), the program starting unit 52 returns to Step S71. For example, in the case of the module information file as shown in FIG. 18, since “LICENSE: FREE” is described, the process returns to step S71.
[0113]
For example, if “LICENSE: FREE” is described in the module information file of the process inspection application module, the process inspection SD card will not be treated as an SC even if it is removed from the SD card slot 125 or 127. Since the process inspection SD card is used for process inspection performed in a factory or the like, it can be reused in a plurality of the multifunction peripherals 1.
[0114]
If the program starting unit 52 determines that the SD card slot number obtained in step S72 does not match the SD card slot number from which the SD card 126 or 128 has been removed (NO in S73), the process returns to step S71.
[0115]
If the program activation unit 52 determines that “LICENSE: FREE” as the license information is not described in the module information file for which “MOUNTFILE” has been acquired in step S72 (NO in S74), the process proceeds to step S75, where the SC is handled. I do.
[0116]
For example, an application starting SD card does not have “LICENSE: FREE” described in the module information file of the application module, and is therefore treated as SC when removed from the SD card slot 125 or 127. As described above, when the SD card for starting the application is removed from the SD card slot 125 or 127, the application is treated as SC, thereby preventing reuse in a plurality of the multifunction peripherals 1.
[0117]
When determining that there is no “/ tmp / module ID.txt” in the file tree as shown in FIG. 4 (NO in S71), the program activating unit 52 proceeds to step S76 and does not handle the SC.
[0118]
Returning to FIG. 24, in step S65, the program activation unit 52 determines whether or not the action in which the SD card 126 or 128 is suddenly removed is treated as SC. If it is determined by the SC check process that the operation is to be treated as SC (YES in S65), the program starting unit 52 proceeds to step S66, displays SC on the operation panel 80, and ends the process. After the SC is displayed on the operation panel 80, the multifunction peripheral 1 cannot be used.
[0119]
On the other hand, if it is determined in the SC check process that the image is not to be treated as an SC (NO in S65), the program activation unit 52 ends the process. In this case, the MFP 1 can use an application other than the application stopped in step S63.
[0120]
FIG. 26 shows a flowchart of another example of the SD card removal detection processing. FIG. 27 is an explanatory diagram of another example of the SD card removal detection processing. In the SD card removal detection process of FIG. 26, the SC check process is not performed.
[0121]
When the application starting SD card 130 is removed from the SD card slot 129, the SD card status monitor driver 123 notifies the applications 37 to 39 started from the application starting SD card 130 of the removal of the application starting SD card 130. I do.
[0122]
Proceeding to step S81, the applications 37 to 39 activated from the application activation SD card 130 close inter-process communication with the service layer processes (for example, SCS42, OCS46, FCS47, etc.). Proceeding to step S82 following step S81, the applications 37 to 39 terminate themselves.
[0123]
Proceeding to step S83, the program activation unit 52 receives a signal (SIGCHLD) indicating termination of the applications 37 to 39, and knows that at least a part of the applications 37 to 39 has terminated.
[0124]
Proceeding to step S84, the program activation unit 52 determines whether all the applications 37 to 39 activated from the application activation SD card 130 have been terminated. If it is determined that all the applications 37 to 39 activated from the application activation SD card 130 have not been terminated (NO in S84), the program activation unit 52 repeats the processing of steps S83 and S84.
[0125]
If it is determined that all the applications 37 to 39 started from the application start-up SD card 130 have ended (YES in S84), the program starting unit 52 determines
Proceed to step S85.
[0126]
In step S85, the program starting unit 52 starts the SD card check program 121. Proceeding to step S86, the SD card check program 121 unmounts the application activation SD card 130, notifies the SD card status monitor driver 123 that the application activation SD card 130 has been unmounted, and stops the processing.
[0127]
Since the SD card removal detection processing in FIG. 26 is not treated as SC, normal operation can be performed when the application activation SD card 130 is inserted into the SD card slot 129 again.
[0128]
【The invention's effect】
As described above, according to the present invention, a removable recording medium can be easily prevented from being reused by a plurality of image forming apparatuses.
[Brief description of the drawings]
FIG. 1 is a configuration diagram of an embodiment of a multifunction peripheral according to the present invention.
FIG. 2 is a hardware configuration diagram of an embodiment of the multifunction peripheral according to the present invention.
FIG. 3 is a configuration diagram of an example of a multifunction peripheral starting unit.
FIG. 4 is a configuration diagram of an example of a file tree.
FIG. 5 is a configuration diagram of an example of a master setting file.
FIG. 6 is a configuration diagram of an example of a setting file.
FIG. 7 is a configuration diagram of an example of a file tree of an SD card.
FIG. 8 is an explanatory diagram of one embodiment of a program stopping method according to the present invention.
FIG. 9 is a flowchart of an example of an event waiting process.
FIG. 10 is a flowchart illustrating an example of an SD card insertion detection process.
FIG. 11 is a configuration diagram of an example of a setting file recorded on an application starting SD card.
FIG. 12 is a configuration diagram of an example of a setting file recorded on a process inspection SD card.
FIG. 13 is a configuration diagram of an example of a module information file read from within a printer module.
FIG. 14 is a configuration diagram of an example of a module information file read from within a scanner module.
FIG. 15 is a configuration diagram of an example of a module information file read from within a process inspection module.
FIG. 16 is a configuration diagram of an example of a module information file for a printer application to which a file name of a module to be mounted is added.
FIG. 17 is a configuration diagram of an example of a module information file for a scanner application to which a file name of a module to be mounted is added.
FIG. 18 is a configuration diagram of an example of a module information file for a process inspection application to which a file name of a module to be mounted is added.
FIG. 19 is a flowchart (1/2) of an example of an SD card insertion detection process having an electronic authentication check function.
FIG. 20 is a flowchart (2/2) of an example of an SD card insertion detection process having an electronic authentication check function.
FIG. 21 is a flowchart illustrating an example of a setting file authentication check process.
FIG. 22 is an image diagram of an example of a target file recorded on an SD card.
FIG. 23 is a flowchart of an example of an authentication check process of a module to be mounted.
FIG. 24 is a flowchart illustrating an example of an SD card removal detection process.
FIG. 25 is a flowchart illustrating an example of an SC check process.
FIG. 26 shows a flowchart of another example of the SD card removal detection processing.
FIG. 27 is an explanatory diagram of another example of the SD card removal detection process.
[Explanation of symbols]
1 Fusion machine
11 Black and white laser printer
12 color laser printer
13 Hardware resources
20 software groups
30 applications
31 Printer App
32 copy application
33 Fax App
34 Scanner App
35 Net File Application
36 Process inspection application
37-39 apps
40 platforms
41 Operating System (OS)
42 System Control Service (SCS)
43 System Resource Manager (SRM)
44 Engine Control Service (ECS)
45 Memory Control Service (MCS)
46 Operation Panel Control Service (OCS)
47 Fax Control Service (FCS)
48 Network Control Service (NCS)
50 Fusion machine starter
51 ROM monitor
52 Program Launcher
62 System memory
67 Local memory
68 Hard Disk Drive (HDD)
70, 125, 127, 129 SD card slot
80 Operation Panel
82 Engine
121 SD card check program
122 File System
123 SD card status monitor driver
124 SD Card Access Driver
126, 128, 130 SD card

Claims (21)

An image forming apparatus having a program for performing a process related to image formation using hardware resources and a slot into which a recording medium can be inserted and removed,
State monitoring means for monitoring insertion and removal of the recording medium with respect to the slot,
Recording medium activation means for making the recording medium inserted into the slot accessible, and for making the recording medium extracted from the slot inaccessible,
While reading and starting the program from the recording medium in the accessible state, when the state monitoring unit notifies the user that the recording medium has been extracted from the slot, the program read and started from the recording medium is executed. An image forming apparatus, comprising: a program activating means for stopping. The program starting means, when notified of the removal of the recording medium from the slot from the state monitoring means, determines whether or not the removal of the recording medium is treated as abnormal according to predetermined information. The image forming apparatus according to claim 1. 3. The image forming apparatus according to claim 2, wherein the program starting unit determines that the removal of the recording medium is treated as abnormal when the predetermined information does not include license information. The program starting means reads out the program from the recording medium and starts the program, and then obtains a module information file of the program including at least one of module identification information, module version information, and license information. 4. The image forming apparatus according to claim 3, wherein a number of a slot in which the recording medium is inserted is added to an information file and stored. 3. The image forming apparatus according to claim 2, wherein the program starting unit does not determine that the removal of the recording medium is treated as abnormal when the predetermined information includes license information. 4. The image forming apparatus according to claim 3, wherein the program activating unit displays an abnormality on the operation panel when the removal of the recording medium is determined to be treated as abnormal. 4. The image forming apparatus according to claim 3, wherein the program activation unit disables the entire image forming apparatus when it is determined that the removal of the recording medium is treated as abnormal. 2. The image forming apparatus according to claim 1, wherein the status monitoring unit is notified of information on insertion / extraction of the recording medium with respect to the slot, and notifies the program activation unit of the information. An image forming apparatus having a program for performing a process related to image formation using hardware resources and a slot into which a recording medium can be inserted and removed,
State monitoring means for monitoring insertion and removal of the recording medium with respect to the slot,
Recording medium activation means for making the recording medium inserted into the slot accessible, and for making the recording medium extracted from the slot inaccessible,
When read out from the recording medium and activated, when the removal of the recording medium from the slot is notified, after stopping inter-process communication with other processes, a program to stop itself,
While reading and activating the program from the accessible recording medium, when the removal of the recording medium from the slot is notified, the recording medium activation unit is activated to activate the recording medium extracted from the slot. An image forming apparatus, comprising: a program activating unit for making the computer inaccessible. The program activating means activates the recording medium activating means after all the programs read and activated from the recording medium have been stopped to make the recording medium removed from the slot inaccessible. The image forming apparatus according to claim 9, wherein: 10. The status monitoring unit is notified of information on insertion / removal of a recording medium with respect to the slot, and notifies the insertion / removal information to the program starting unit and a program read from the recording medium and started. The image forming apparatus according to any one of the preceding claims. The image forming apparatus according to claim 1, wherein active insertion and removal of the recording medium is possible. A program for performing a process related to image formation using hardware resources, and a program stopping method for an image forming apparatus having a slot into which a recording medium can be inserted and removed,
A state monitoring step of monitoring insertion / removal of a recording medium into / from the slot,
A recording medium stopping step of making the recording medium extracted from the slot inaccessible,
A program stopping step of stopping a program read from the recording medium and started when the removal of the recording medium from the slot is notified. 14. The method according to claim 13, wherein, in the program stopping step, when the removal of the recording medium from the slot is notified, whether or not the removal of the recording medium is treated as abnormal is determined according to predetermined information. Program stop method described. 15. The program stopping method according to claim 14, wherein in the program stopping step, when the predetermined information does not include license information, the removal of the recording medium is determined to be treated as abnormal. When a program is read from the recording medium and activated, a module information file including at least one of module identification information, module version information, and license information is obtained, and the recording medium is inserted into the module information file. The method according to claim 15, further comprising a module information file storing step of adding and storing the number of the slot that has been added. 15. The program stopping method according to claim 14, wherein, in the program stopping step, when the predetermined information includes license information, the removal of the recording medium is not determined to be abnormal. 16. The program stopping method according to claim 15, wherein in the program stopping step, when it is determined that the removal of the recording medium is treated as abnormal, the fact that the recording medium is abnormal is displayed on an operation panel. 16. The program stopping method according to claim 15, wherein in the program stopping step, when the removal of the recording medium is determined to be abnormal, the entire image forming apparatus cannot be used. A program for performing a process related to image formation using hardware resources, and a program stopping method for an image forming apparatus having a slot into which a recording medium can be inserted and removed,
A state monitoring step of monitoring insertion / removal of a recording medium into / from the slot,
When the removal of the recording medium from the slot is notified, after stopping inter-process communication with other processes, a program stop step of stopping the program read from the recording medium and started,
Stopping the recording medium taken out of the slot to make the recording medium inaccessible. 21. The method according to claim 13, wherein active insertion and removal of the recording medium is possible.

Images