JP2006222569A - Image forming apparatus, information processing method, information processing program and recording medium - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an image forming apparatus having a new application management system. <P>SOLUTION: The image forming apparatus is equipped with a control means of controlling whether constituent equipment constituting the image forming apparatus is allowed or disallowed to enter power-saving mode. The control means controls whether the constituent equipment, constituting the image forming apparatus, is allowed or inhibited from entering the power-saving mode, based on the execution state of image formation processing and on the execution situation of application for the image forming apparatus. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to an image forming apparatus such as a copy / printer / scanner / facsimile / multifunction machine / multifunction machine, an information processing method, an information processing program, and a recording medium such as an SD card / CD-ROM.

In recent years, multifunction peripherals and multifunction peripherals having functions as a copy, a printer, a scanner, and a facsimile have come to be marketed. Multifunction devices and multifunction devices have hardware such as an imaging unit, printing unit, communication unit, and operation display unit, as well as four types of software corresponding to copying, printers, scanners, and facsimiles. This functions as a copy, printer, scanner, or facsimile. When functioning as a copy or printer, a multifunction device or a multifunction device prints an image on printing paper or the like. When functioning as a copy or scanner, the image is read from a read original and functions as a facsimile. In this case, images are exchanged with other devices via a telephone line or the like.
JP 2002-84383 A

  Various applications are executed in the multifunction peripheral and the multi-function peripheral. As an execution mode of an application in a multifunction peripheral or a multi-function peripheral, “one process and one application” in which one application is executed in one process is the mainstream, but “one process in which a plurality of applications are executed in one process”. “Multiple apps” are also appearing. However, in the case of executing information processing of one process plural applications in a system premised on one process one application, each application of one process plural applications cannot be managed by the application management mechanism for one process one application. An application management mechanism for multiple applications per process is required. As can be understood from this example, the multifunction peripheral or the multifunction peripheral needs an application management mechanism corresponding to the application execution mode.

  Therefore, an object of the present invention is to propose an image forming apparatus including a new application management mechanism.

  The invention according to claim 1 is an image forming apparatus including a control unit that controls whether to permit or prohibit a power saving shift of a component device that constitutes the image forming apparatus. An image forming apparatus that controls whether to permit or prohibit a power saving transition of components constituting the forming apparatus based on an execution state of an image forming process or an execution state of an application for an image forming process is there.

  According to a second aspect of the present invention, the control unit prohibits a power saving shift of a component device used in the image forming process during the execution of the image forming process. An image forming apparatus.

  According to a third aspect of the present invention, when the application for image formation processing installed in the storage device of the image forming apparatus is being executed and cannot be stopped, the control unit performs power saving transition of the storage device. The image forming apparatus according to claim 1, wherein the image forming apparatus is prohibited.

  According to a fourth aspect of the present invention, in the case where there is an application that is being executed and cannot be stopped among the applications for image forming processing installed in the storage device of the image forming apparatus, If there is an application whose installation destination is a storage device in which only a part of the application is loaded into the memory during execution of the application, among the applications that are being executed and cannot be stopped, the installation destination of the application The image forming apparatus according to claim 1, wherein a power saving transition of the storage device is prohibited.

  According to a fifth aspect of the present invention, when the image forming apparatus is in a power saving mode and the image forming process error occurs when the image forming apparatus is in the power saving mode, the control unit permits the power saving transition of the display device of the image forming apparatus. 5. The image forming apparatus according to claim 1, wherein the image forming apparatus is changed to prohibition.

  According to a sixth aspect of the present invention, when the image forming processing error is canceled when the image forming apparatus is in the power saving mode, the control unit prohibits the power saving transition of the display device of the image forming apparatus. The image forming apparatus according to claim 1, wherein the image forming apparatus returns to the permission state.

  The invention according to claim 7 is an image forming apparatus including a control unit that controls whether to permit or prohibit a power saving shift of a component device that constitutes the image forming apparatus. An image forming apparatus that controls whether to permit or prohibit a power saving transition of components constituting the forming apparatus based on a control request from an application for image forming processing.

  The invention according to claim 8 is characterized in that the control means permits, by default, a power saving shift of the component device for which there is no control request from the application for image forming processing. Item 8. The image forming apparatus according to Item 7.

  The invention according to claim 9 is characterized in that the application is batch-translated from a source code to a byte code by a compiler and sequentially executed by a virtual machine. The image forming apparatus described.

  The invention according to claim 10 is the image forming apparatus according to any one of claims 1 to 9, wherein the application is Xlet.

  According to an eleventh aspect of the present invention, there is provided an information processing method executed by an image forming apparatus, comprising a control step of controlling whether to permit or prohibit a power saving transition of a component device constituting the image forming apparatus. In the control step, whether to permit or prohibit the power saving transition of the component devices constituting the image forming apparatus is controlled based on the execution state of the image forming process or the execution state of the application for the image forming process. Is an information processing method characterized by

  According to a twelfth aspect of the present invention, in the control stage, during the execution of the image forming process, the power saving transition of the components used in the image forming process is prohibited. Information processing method.

  According to a thirteenth aspect of the present invention, in the control step, when an image forming processing application installed in the storage device of the image forming apparatus is being executed and cannot be stopped, the power saving transition of the storage device is performed. 13. The information processing method according to claim 11 or 12, wherein the information processing method is prohibited.

  According to a fourteenth aspect of the present invention, in the control stage, when there is an application that is being executed and cannot be stopped among the applications for image forming processing installed in the storage device of the image forming apparatus, If there is an application whose installation destination is a storage device in which only a part of the application is loaded into the memory during execution of the application, among the applications that are being executed and cannot be stopped, the installation destination of the application The information processing method according to claim 11 or 12, wherein a power saving transition of the storage device is prohibited.

  According to a fifteenth aspect of the present invention, in the control step, when an image forming process error occurs when the image forming apparatus is in the power saving mode, the power saving transition of the display device of the image forming apparatus is permitted. 15. The information processing method according to claim 11, wherein the information processing method is changed to prohibition.

  According to a sixteenth aspect of the present invention, when the error of the image forming process is canceled when the image forming apparatus is in the power saving mode in the control step, the power saving transition of the display device of the image forming apparatus is prohibited. The information processing method according to claim 11, wherein the permission is returned to the permission.

  According to a seventeenth aspect of the present invention, there is provided an information processing method executed by an image forming apparatus, comprising a control step of controlling whether to permit or prohibit a power saving transition of a component device constituting the image forming apparatus. In the control step, information processing is controlled based on a control request from an application for image forming processing, whether to permit or prohibit power saving transition of components constituting the image forming apparatus Is the method.

  The invention according to claim 18 is characterized in that, in the control stage, for a component device that does not have a control request from an application for image formation processing, the power saving transition of the component device is permitted by default. Item 18. The information processing method according to Item 17.

  According to a nineteenth aspect of the present invention, in the application, the application is batch-translated from a source code to a byte code by a compiler and is sequentially executed by a virtual machine. The information processing method described.

  The invention according to claim 20 is the information processing method according to any one of claims 11 to 19, wherein the application is Xlet.

  A twenty-first aspect of the invention is an information processing program for causing a computer to execute the information processing method according to any one of the eleventh to twentieth aspects.

  The invention described in claim 22 is a recording medium on which an information processing program for causing a computer to execute the information processing method described in any one of claims 11 to 20 is recorded.

  Thus, the present invention proposes an image forming apparatus having a new application management mechanism.

  FIG. 1 shows a compound machine 101 corresponding to an embodiment of the present invention. The compound machine 101 shown in FIG. 1 includes various hardware 111, various software 112, and a compound machine starting unit 113.

  As the hardware 111 of the multi-function peripheral 101, there are an imaging unit 121, a printing unit 122, and other hardware 123. The imaging unit 121 is hardware for reading an image (image data) from a read original. The printing unit 122 is hardware for printing an image (image data) on printing paper.

  As the software 112 of the multi-function peripheral 101, there are various applications 131 and various platforms 132. These programs are executed in parallel on a process basis by an OS (Operating System) such as UNIX (registered trademark).

  The application 131 includes a copy application 141 that is a copy application, a printer application 142 that is a printer application, a scanner application 143 that is a scanner application, a facsimile application 144 that is a facsimile application, and a network file application. There is a network file application 145.

  The application 131 can be developed using a dedicated SDK (software development kit). An application 131 developed using the SDK is called an SDK application. As the dedicated SDK, “CSDK” for developing the application 131 in C language and “JSDK” for developing the application 131 in Java (registered trademark) language are provided. An application 131 developed using CSDK is called a “CSDK application”, and an application 131 developed using JSDK is called a “JSDK application”. The MFP 101 in FIG. 1 also has a CSDK application 146 and a JSDK application 147. 1 further includes a JSDK platform 148 as software 112 that mediates between the JSDK application 147 written in the Java (registered trademark) language and the other software 112 written in the C language.

  The platform 132 includes various control services 151, a system resource manager 152, and various handlers 153. The control service 151 includes a network control service (NCS) 161, a facsimile control service (FCS) 162, a delivery control service (DCS) 163, an engine control service (ECS) 164, a memory control service (MCS) 165, and an operation panel control service. There are (OCS) 166, a certification control service (CCS) 167, a user directory control service (UCS) 168, and a system control service (SCS) 169. As the handler 153, there are a facsimile control unit handler (FCUH) 171 and an image memory handler (IMH) 172.

  The process of the NCS 161 mediates network communication. The FCS 162 process provides a facsimile API. The process of the DCS 163 performs control related to the distribution processing of the stored document. The process of the ECS 164 performs control related to the imaging unit 121 and the printing unit 122. The process of the MCS 165 controls the memory and hard disk drive. The process of the OCS 166 performs control related to the operation panel. The process of the CCS 167 performs control related to authentication processing and billing processing. The process of the UCS 168 performs control related to management of user information. The process of the SCS 169 performs control related to system management.

  A virtual application service (VAS) 135 exists as software 112 that mediates between the application 131 and the platform 132. The VAS 135 operates as a server process using the application 131 as a client, and also operates as a client process using the platform 132 as a server. The VAS 135 has a wrapping function that hides the platform 132 when viewed from the application 131, and plays a role of absorbing version differences associated with version upgrades of the platform 132.

  The MFP starter 113 is executed first when the MFP 101 is turned on. As a result, an OS such as UNIX (registered trademark) is activated, and the application 131 and the platform 132 are activated. These programs are stored in the hard disk drive or the memory card, and are reproduced from the hard disk drive or the memory card and activated in the memory.

  FIG. 2 is a hardware configuration diagram according to the MFP 101 of FIG. The hardware 111 of the multi-function peripheral 101 includes a controller 201, an operation panel 202, a facsimile control unit (FCU) 203, an imaging unit 121, and a printing unit 122.

  The controller 201 includes a CPU 211, ASIC 212, NB221, SB222, MEM-P231, MEM-C232, HDD (hard disk drive) 233, memory card slot 234, NIC (network interface controller) 241, USB device 242, IEEE 1394 device 243, and Centronics device. 244.

  The CPU 211 is an IC for various information processing. The ASIC 212 is an IC for various image processing. The NB 221 is a north bridge of the controller 201. The SB 222 is a south bridge of the controller 201. The MEM-P 231 is a system memory of the multifunction machine 101. The MEM-C 232 is a local memory of the multifunction machine 101. The HDD 233 is a storage of the multifunction machine 101. The memory card slot 234 is a slot for setting the memory card 235. The NIC 241 is a controller for network communication using a MAC address. The USB device 242 is a device for providing a USB standard connection terminal. The IEEE 1394 device 243 is a device for providing a connection terminal of the IEEE 1394 standard. The Centronics device 244 is a device for providing a Centronics specification connection terminal.

  The operation panel 202 is hardware (operation unit) for an operator to input to the multifunction machine 101 and hardware (display unit) for the operator to obtain an output from the multifunction machine 101.

  FIG. 3 is an external view of the multi-function peripheral 101 of FIG. FIG. 3 shows the position of the imaging unit 121, the position of the printing unit 122, and the position of the operation panel 202. FIG. 3 further illustrates a document setting unit 301 that is a setting destination of a read document, a paper feeding unit 302 that is a printing paper feeding destination, and a paper discharging unit 303 that is a printing paper discharging destination. .

  As shown in FIG. 4, the operation panel 202 includes a touch panel 311, a numeric keypad 312, a start button 313, a reset button 314, a function key 315, and an initial setting button 316. The touch panel 311 is hardware (touch operation unit) for inputting by a touch operation and hardware (screen display unit) for obtaining an output by screen display. The numeric keypad 312 is hardware for inputting numbers by operating keys (buttons). The start button 313 is hardware for performing a start operation by a button operation. The reset button 314 is hardware for performing a reset operation by a button operation. The function key 315 is hardware for displaying an operation screen by the CSDK application 146 or the JSDK application 147 by a key (button) operation. The initial setting button 316 is hardware for displaying an initial setting screen by button operation.

  The document setting unit 301 includes an ADF (automatic document feeder) 321, a flat bed 322, and a flat bed cover 323. The paper feed unit 302 includes four paper feed trays. The paper discharge unit 303 includes a single paper discharge tray.

(JSDK)
FIG. 5 is a class diagram of the JSDK application 147 and the JSDK platform 148 of FIG. The JSDK application 147 and the JSDK platform 148 are executed on the same process as one process as a whole. Each block in the JSDK application 147 and the JSDK platform 148 is executed in parallel (multithread) in units of threads as threads on one process. The JSDK application 147 and the JSDK platform 148 are collectively translated from source code to bytecode by a Java (registered trademark) compiler, and sequentially executed by a Java (registered trademark) virtual machine. The JSDK application 147 and the JSDK platform 148 are implemented based on the Personal Basis Profile of Java (registered trademark) 2 Micro Edition.

  As the JSDK application 147, there are a user application 501, a JSDK GUI Manager 511, a Task Bar Manager 512, an error application 513, a rule application 514, and the like.

  The user application 501 is a JSDK application developed by a user (for example, a vendor) of the MFP 101 using JSDK. The JSDK GUI Manager 511 is a JSDK application that displays an operation screen for other JSDK applications (such as the user application 501). The Task Bar Manager 512 is a JSDK application that displays a task bar that operates on another JSDK application (such as the user application 501). The error application 513 is a JSDK application that displays information or notification that an error has occurred when an error occurs in another JSDK application (such as the user application 501). The rule application 514 is a JSDK application that displays or notifies information indicating that there is a rule violation when there is a rule violation in a processing request of another JSDK application (such as the user application 501).

  Here, the user application 501 is an Xlet that is a Java (registered trademark) application along with a stand-alone application or an applet. Here, the JSDK GUI Manager 511, the Task Bar Manager 512, the error application 513, and the rule application 514 are Xlet (XletEx) with unique extensions.

  The JSDK platform 148, the JSDK Main521, a JSDK Environment522, the Locale Manager523, the Xlet Managers, the Multi Xlet Manager532, a JSDK Manager533, and Send Manager541, and Event Manager542, the System Event Manager543, and Panel Manager544, Install Manager545 And a class such as Server / Client Manager 546 exists.

  The JSDK Main 521 is a class that performs startup setting of the JSDK system. The JSDK Environment 522 is a class for setting the startup environment of the JSDK system. The Local Manager 523 is a class that performs internationalization (language designation).

  The Xlet Manager 531 is a class that manages Xlet on a one-to-one basis. Here, information, life cycle, and the like related to the seven Xlet states are managed by the seven Xlet Managers 531 on a one-to-one basis. Information relating to the state of the Xlet is managed by the Xlet Manager 531, notified from the Xlet Manager 531 to XletEx, and used for display processing and notification processing by XletEx. The Multi Xlet Manager 532 is a class that manages all Xlet Managers 531. Here, the life cycle and the like of seven Xlet Managers 531 are all managed by one Multi Xlet Manager 532. The JSDK Manager 533 is a class that manages the entire JSDK system. For example, the life cycle of Multi Xlet Manager 532, Send Manager 541, Event Manager 542, System Event Manager 543, Panel Manager 544, Install Manager 545, Server / Client Manager 546, etc. is managed by JSD5 33.

  The System Event Manager 543 is a class that manages system events (power mode, etc.) from the platform 132 of FIG. The Panel Manager 544 is a class that performs arbitration when one Xlet occupies the screen of the operation panel 202. The Install Manager 545 is a class that manages installation and uninstallation from SDcard and Web.

  In the JSDK system of FIG. 5, JSDK API 551 and JSDK API 552 are used as APIs. Note that the difference between Xlet and XletEx is that the JSDK API 551 can be used and the JSDK platform 148 can be accessed to access the object. 1 further executes a JSDK Session 553 and a Native JSDK Session 554, which are interfaces of C language and Java (registered trademark), and a JSDK application 147 and a JSDK platform 148 as elements related to the JSDK system of FIG. Therefore, there is a CVM 555 or the like which is a Java (registered trademark) virtual machine.

  FIG. 6 is a diagram for explaining a startup procedure of the JSDK system. In the JSDK system, first, the JSDK Main 521 that is a class having a main () function for starting the JSDK application 147 generates a JSDK Environment 522 (S 1). Subsequently, the JSDK Environment 522 constructs the execution environment of the JSDK system by constructing the native layer (S2) and constructing the language environment (S3). Subsequently, the JSDK Environment 522 generates a JSDK Manager 533 (S4). In the JSDK system, the JSDK Manager 533 generates a system layer Manager (S5-12), and generates an application layer Manager through the Multi Xlet Manager 532 and the Xlet Manager 531 (S13-16).

  FIG. 7 is a diagram for explaining a GUI (Graphical User Interface) of the JSDK system. When the function key 315 (see FIG. 4) of the multi-function peripheral 101 is pressed, S1-16 in FIG. 6 is executed, and the GUI in FIG. 7 is displayed on the touch panel 311 (see FIG. 4) of the multi-function peripheral 101. The GUI in FIG. 7 is an operation screen for which the user application 501 is an operation target, and is displayed by the JSDK GUI Manager 511 activated in S13 in FIG.

  FIG. 7A is a switching operation screen for performing a switching operation of the user application 501 that occupies the screen. FIG. 7B is a start operation screen for performing a start operation of the user application 501. FIG. 7C is an end operation screen for performing an end operation of the user application 501. FIG. 7D is an installation operation screen for performing an installation operation of the user application 501. FIG. 7E is an uninstall operation screen for performing an uninstall operation of the user application 501. FIG. 7A is an initial screen displayed on the touch panel 311 immediately after the function key 315 is pressed, and FIGS. 7A, 7B, 7C, 7D, and 7E are touched to switch, start, end, install, and uninstall buttons, respectively. Will be displayed.

  SimplePrint, SimpleCopy, SimpleOcr, SimpleScan, etc. are user applications 501 respectively. For example, SimplePrint is an application for enabling the electronic document to be printed by inputting the file name of the electronic document. Note that the type of application means whether the application has a GUI.

  The switching operation screen in FIG. 7A will be described. In the switching operation screen of FIG. 7A, a list of user applications 501 that have been installed and are being executed as switching operation targets is displayed.

  When “SimplePrint” is touched on the switching operation screen of FIG. 7A, the ownership of the operation panel 202 is given to SimplePrint, and SimplePrint occupies the screen. Accordingly, the screen shifts from the screen of FIG. 7A to the screen of FIG. 8A. FIG. 8A is a GUI displayed by SimplePrint that occupies the screen.

  When “SimpleCopy” is touched on the switching operation screen of FIG. 7A, ownership of the operation panel 202 is given to SimpleCopy, and SimpleCopy occupies the screen. Accordingly, the screen shifts from the screen of FIG. 7A to the screen of FIG. 8B. As shown in FIG. 7A, since the state of SimpleCopy is “abnormal”, an error message related to SimpleCopy is displayed on the screen as shown in FIG. 8B.

  When “SimpleOcr” is touched on the switching operation screen of FIG. 7A, ownership of the operation panel 202 is granted to SimpleOcr, and SimpleOcr occupies the screen. Accordingly, the screen shifts from the screen of FIG. 7A to the screen of FIG. 8C. As shown in FIG. 7A, since the type of SimpleOcr is “no GUI”, the state of SimpleOcr is displayed on the screen as shown in FIG. 8C.

  8A, B, and C, a task bar for operating the user application 501 is displayed by the Task Bar Manager 512 activated in S14 of FIG. These task bars are switching task bars for performing a switching operation of the user application 501 that occupies the screen.

  When “SC” or “SO” in the switching task bar is touched on the screen of FIG. 8A, ownership of the operation panel 202 is given to SimpleCopy or SimpleOcr, and SimpleCopy or SimpleOcr occupies the screen. Accordingly, the screen shifts from the screen of FIG. 8A to the screen of FIG. 8B or 8C. Touching “JSDK” in the switching task bar on the screen of FIG. 8A returns the screen to the screen of FIG. 7A.

  When “SP” or “SO” in the switching task bar is touched on the screen of FIG. 8B, ownership of the operation panel 202 is given to SimplePrint or SimpleOcr, and SimplePrint or SimpleOcr occupies the screen. Accordingly, the screen shifts from the screen of FIG. 8B to the screen of FIG. 8A or 8C. When “JSDK” in the switching task bar is touched on the screen of FIG. 8B, the screen returns to the screen of FIG. 7A.

  When “SP” or “SC” in the switching task bar is touched on the screen of FIG. 8C, the ownership of the operation panel 202 is given to SimplePrint and SimpleCopy, and SimplePrint and SimpleCopy occupy the screen. Accordingly, the screen shifts from the screen of FIG. 8C to the screen of FIG. 8A or 8B. When “JSDK” in the switching task bar is touched on the screen of FIG. 8C, the screen returns to the screen of FIG. 7A.

  The activation operation screen in FIG. 7B will be described. A list of user applications 501 that have been installed and are not executed as activation operation targets is displayed on the activation operation screen in FIG. 7B.

  When “SimplePrint” is touched on the activation operation screen of FIG. 7B, a confirmation screen (FIG. 9) for confirming whether or not to execute the SimplePrint activation process is displayed. When a product code is input on the confirmation screen of FIG. 9 and “execute” is touched, SimplePrint is activated.

  The end operation screen in FIG. 7C will be described. On the end operation screen in FIG. 7C, a list of installed and executing user applications 501 as the end operation target is displayed.

  When “SimplePrint” is touched on the end operation screen of FIG. 7C, a confirmation screen (FIG. 10) for confirming whether or not to execute the SimplePrint forcible end processing is displayed. When “execute” is touched on the confirmation screen of FIG. 10, SimplePrint is forcibly terminated.

  The installation operation screen in FIG. 7D will be described. By the installation process of the user application 501, the user application 501 that is not registered as a startable user application is registered as a startable user application. On the installation operation screen in FIG. 7D, a list of user applications 501 as installation operation targets is displayed together with the installation status.

  When “SimplePrint” is touched on the installation operation screen of FIG. 7D, a confirmation screen (FIG. 11) for confirming the installation destination of SimplePrint having SDcard as a storage source is displayed. Touching “SDcard” on the confirmation screen of FIG. 11 installs SimplePrint as the installation destination of SDcard, and touching “HDD” on the confirmation screen of FIG. 11 installs SimplePrint as the installation destination of the HDD. It will be.

  The uninstall operation screen in FIG. 7E will be described. As a result of the user application 501 uninstalling process, the registered user application 501 as the startable user application is deregistered as the startable user application. A list of user applications 501 registered as uninstall operation targets is displayed on the uninstall operation screen in FIG. 7E.

  When “SimplePrint” is touched on the uninstall operation screen of FIG. 7E, a confirmation screen (FIG. 12) for confirming whether or not to execute the SimplePrint uninstall process is displayed. When “execute” is touched on the confirmation screen of FIG. 12, SimplePrint is uninstalled.

  FIG. 13 is a diagram for explaining a display procedure of the startup operation screen. When the activation button is touched on the switching operation screen, a list request for installed user applications 501 is transmitted from the JSDK GUI Manager 511 to the Install Manager 545 (S1). In response to this, the Install Manager 545 acquires the JNLP file of the installed user application 501 based on the information related to the storage location of the installed user application 501 (stored in the NVRAM in the MFP 101) ( S2). The JNLP file of the user application 501 in the SD card is acquired from the SD card set in the multi-function peripheral 101. From the HDD in the multi-function peripheral 101, the JNLP file of the user application 501 in the HDD is acquired. The JNLP file has a one-to-one correspondence with the user application 501 and includes information related to the definition of the user application 501. Based on the contents of the JNLP file of the installed user application 501, a list response of the installed user applications 501 is transmitted from the Install Manager 545 to the JSDK GUI Manager 511 (S 3). As a result, the screen moves from the switching operation screen to the activation operation screen.

  FIG. 14 is a diagram for explaining the execution procedure of the startup process. When the selection operation is performed on the activation operation screen and the confirmation operation is performed on the confirmation screen, the activation request for the user application 501 is transmitted from the JSDK GUI Manager 511 to the JSDK Manager 533 (S1). In response to this, an activation request for the user application 501 is transmitted from the JSDK Manager 533 to the Multi Xlet Manager 532 through an authentication process by the Authentication Manager 547 (S2). In response to this, the Multi Xlet Manager 532 activates the Xlet Manager 531 (S3), the Xlet Manager 531 acquires a root window from the Panel Manager 544 (S4), and the Xlet Manager 531 activates the user application 501 (S5). Then, the activation response of the user application 501 is transmitted from the Multi Xlet Manager 532 to the JSDK Manager 533 (S6). Then, the activation response of the user application 501 is transmitted from the JSDK Manager 533 to the JSDK GUI Manager 511 (S7).

  FIG. 15 is a diagram for explaining the display procedure of the installation operation screen. When an installation button is touched on the switching operation screen, a list request for the user application 501 is transmitted from the JSDK GUI Manager 511 to the Install Manager 545 (S1). In response to this, the Install Manager 545 acquires the JNLP file of the user application 501 (S2). The JNLP file of the user application 501 in the SD card is acquired from the SD card set in the multi-function peripheral 101. A JNLP file of the user application 501 in the Web server is acquired from the Web server connected to the MFP 101 via the network. The JNLP file has a one-to-one correspondence with the user application 501 and includes information related to the definition of the user application 501. Then, based on the information related to the installation status of the user application 501 (stored in the NVRAM in the MFP 101) and the contents of the JNLP file of the user application 501, the Install Manager 545 sends the JSDK GUI Manager 511 to the user application 501. A list response is transmitted (S3). As a result, the screen moves from the switching operation screen to the installation operation screen.

  FIG. 16 is a diagram for explaining the execution procedure of the installation process. When a selection operation is performed on the installation operation screen and a confirmation operation is performed on the confirmation screen, an installation request for the user application 501 is transmitted from the JSDK GUI Manager 511 to the Install Manager 545 (S1). In response, the Install Manager 545 installs the user application 501 after passing through the authentication process by the Authentication Manager 547 (S2). Then, the installation response of the user application 501 is transmitted from the Install Manager 545 to the JSDK GUI Manager 511 (S3).

  FIG. 17 shows an example of the syntax of the JNLP file. A JNLP (Java (registered trademark) Network Launching Protocol) file is an XML (extensible Markup Language) file, and the JNLP file format conforms to the JNLP standard. However, since there is a part that is uniquely extended for JSDK, this part will be described below.

  Description 1 is an information element, a title element (description 1A) indicating the application name, a vendor element (description 1B) indicating the vendor name, a telephone element (description 1C) indicating the telephone number of the vendor, and the vendor's fax. A fax element (description 1D) indicating a telephone number and a productID element (description 1E) indicating a product ID of the application are included.

  Description 2 is a security element.

  Description 3 is a resource element, which includes a jsdk element (description 3A) that specifies the JSDK version, a JAR file (application execution file) and a jar element (description 3B) that specifies the version, and a SUB-JNLP file. It includes a sub-jnlp element (description 3C) to be specified.

  Description 4 is an update element and is an element for setting an execution method of the update process. If it is “auto”, the update process of the application is executed by automatic update, if it is “manual”, the update process of the application is executed by manual update, and if “mail”, it is notified when the update process of the application can be executed. An update notification email is delivered.

  Description 5 is an install element, which is an element for setting the execution method of the installation process. If it is auto, the application installation destination is selected by automatic selection, and if it is manual, the application installation destination is selected by manual selection.

  The description 6 indicates whether the application type is “with GUI” or “without GUI”.

  As described in the update element in FIG. 17, the installed JSDK application 147 is a target of update processing. Hereinafter, automatic update processing for automatically updating the installed JSDK application 147 will be described.

  FIG. 18 is a flowchart relating to an automatic update process in which the JSDK application 147 (update target application) in the SD card or HDD is automatically updated to the JSDK application 147 (update application) from the SD card.

  When the update SD card is set in the update SD card slot connected to the multi-function peripheral 101, the JSDK platform 148 acquires the JNLP file of the update application in the update SD card (S101). When the update element of the JNLP file is “auto” and there is an update target application identical to the update application related to the JNLP file (S102 / S103), the JSDK platform 148 determines the version of the update application and The version of the update target application is compared (S104). When the version of the update application is newer than the version of the update target application (S105), the JSDK platform 148 updates the update target application with the update application (S106).

  FIG. 19 is a flowchart relating to an automatic update process in which the JSDK application 147 (update target application) in the SD card or HDD is automatically updated to the JSDK application 147 (update application) from the Web.

  The JSDK platform 148 acquires the JNLP file of the update target application (S201). In the JSDK platform 148, when the update element of the JNLP file is “auto” and the same update application as the update target application related to the JNLP file exists in the Web server connected to the MFP 101 (S202). In S203), the version of the update target application is compared with the version of the update application (S204). If the version of the update application is newer than the version of the update target application (S205), the JSDK platform 148 updates the update target application with the update application (S206).

  Finally, a life cycle such as Xlet that appeared in the description of FIG. 5 will be described.

  FIG. 20 is a state transition diagram of Xlet. The Xlet state includes an initialized state (Loaded), a stopped state (Paused), an activated state (Active), and an end state (Destroyed). The state of Xlet is changed by a method call such as start (initXlet), start (startXlet), stop (pauseXlet), or end (destroyXlet). The life cycle of Xlet is nothing but the state transition of Xlet. However, there may be various variations on what state exists and how the state transitions. The same applies to the Xlet Manager, the Multi Xlet Manager, and other managers.

  The initialization state is a state immediately after the generation of the Xlet instance. The transition to the initialization state is only once. The stopped state is a state in which service provision is stopped, and the activated state is a state in which service is being provided. The transition between the stopped state and the activated state is possible any number of times. The end state is a state immediately after the Xlet instance disappears. The transition to the end state is only once.

  As described in the description of FIG. 5, the life cycle of the JSDK application 147 is managed by the JSDK platform 148. For example, the JSDK application 147 requests the JSDK platform 148 to start, stop, and end itself when it starts, stops, and ends. As an advantage of managing the life cycle of the JSDK application 147 by the JSDK platform 148, for example, it is possible to save memory. In particular, in a multi-thread in which a large number of JSDK applications 147 are executed as threads, it can be said that the existence value of this merit is great. As an advantage of using the JSDK application 147 as an Xlet, for example, the life cycle management of the JSDK application 147 is facilitated.

1) Power control The power control of the multifunction machine 101 will be described.

  The power mode of the multi-function peripheral 101 includes an “ON mode” corresponding to a power-on state and an “OFF mode” corresponding to a power-off state. When using the multifunction machine 101, from the viewpoint of convenience, it is desirable that the multifunction machine 101 is always in the ON mode and is in a standby state for image forming processing. It is not desirable to always set 101 to the ON mode and wait for image forming processing.

  Therefore, in the ON mode, there are various “power saving modes” for saving power consumption during standby of the image forming process in addition to the normal “standby mode” during standby of the image forming process. In the power saving mode, the power source of the portion with high power consumption during standby for image forming processing, such as the heater power source of the fuser of the printing unit 122, the motor power source of the spindle of the HDD 233, and the panel power source of the touch panel 311 enters the power saving state. The power source of the portion with low power consumption during standby for image forming processing, such as the power source of, remains in the standby state. In this way, both convenience and power saving are compatible.

  Examples of power saving modes include the “lights off mode” where the heater power is in standby, motor power is in standby, panel power is in power saving, heater power is in preheat state, motor power is in power saving, panel power is There are a “preheating mode” in which the power is saved, a “night mode” in which the heater power is in the night state, the motor power is in the power saving state, and the panel power is in the power saving state. In any case, the power consumption in the power saving mode is smaller than the power consumption in the standby mode.

  In the standby mode, when a certain time (such as 3 minutes) elapses or a certain time period (such as midnight) arrives, the mode is changed to the power saving mode. When the operation of the multi-function peripheral 101 is executed in the power saving mode, a transition to the standby mode is made. In the power saving mode, when a certain time (such as 3 minutes) elapses or a certain time zone (such as midnight) arrives, the mode changes to the OFF mode. When fax image data, scan data, or print data is received in the OFF mode, a transition is made to the power saving mode. When the power button is turned off, the power mode changes from the ON mode (standby mode or power saving mode) to the OFF mode. When the power button is turned on, the power mode changes from the OFF mode to the ON mode (standby mode).

  FIG. 21 is a diagram for explaining the power control of the multi-function peripheral 101. A problem in executing power control of the multi-function peripheral 101 is which software executes power control of the multi-function peripheral 101. For example, when the application executes power control, the application executes power control in cooperation with the platform. This is not difficult for embedded applications, but is difficult for SDK applications, and it may make development of SDK applications difficult, and may cause power saving standards for the entire device not to be satisfied due to excessive power control. . Furthermore, it is not easy to determine which device should be in which power state when executing a certain image forming process or when executing an application for a certain image forming process. Therefore, it is desirable to let the platform execute power control.

  FIG. 21 shows a JSDK application 147, a JSDK platform 148, and a JSDK API 551 that is an API of the JSDK system. As shown in FIG. 21, the JSDK platform 148 includes a Power Manager 561 and a Machine State Lock 562. The power manager 561 controls whether to allow or prohibit the power saving transition of the component devices constituting the multi-function peripheral 101 based on the execution status of the image formation processing and the execution status of the application for image formation processing (JSDK application 147). Class. The Machine State Lock 562 is a class that controls whether to allow or prohibit the power saving transition of the component devices constituting the multi-function peripheral 101 based on a control request from the image forming processing application (JSDK application 147).

  For power control of the Power Manager 561, the application is passively involved. This eliminates the need for the application to determine which device should be in which power state. For the power control of the Machine State Lock 562, the application will be actively involved. This is used when, for example, an application executes time-consuming processing such as image processing, and when the application needs to prohibit power saving transition by itself.

  Note that the Machine State Lock 562 controls the power saving transition of the component device based on the control request for the component device requested to be controlled by the image formation processing application. For component devices that do not have a request, “default” is allowed for the power saving transition of the component device. For the power control of the Machine State Lock 562, the application need only be actively involved when it is necessary to actively participate.

  FIG. 21 illustrates a scan engine (imaging unit) 121, a print engine (printing unit) 122, an HDD 233, a NIC 241, and a touch panel 311 as examples of components of the multi-function peripheral 101. As shown in FIG. 21, the JSDK API 551 includes a scan service 571, a print service 572, and a file usage class 573 as “application public classes” for executing various processes using the components of the multifunction machine 101. And a network usage class 574 and a panel usage class 575.

  FIG. 22 is a flowchart according to the first specific example of power control of the multi-function peripheral 101.

  In the scan process, the scan engine 121, the HDD 233, and the touch panel 311 are used. Therefore, during the execution of the scan process, the power saving transition of the scan engine 121, the HDD 233, and the touch panel 311 that are components used in the scan process is prohibited. Hereinafter, the power control by the power manager 561 will be described.

  When starting the scan, the user application 501 transmits a scan start request to the scan service 571 (S301). In response to this, the scan service 571 transmits a use notification of each component device used in the scan processing to the power manager 561 (S302). When the power manager 561 receives an inquiry from the SCS 169 through the system event manager 543 after that inquiries to put these constituent devices into the power saving state (S303), the power manager 561 sends a reply that prohibits the power saving transition of these constituent devices. Then, the data is transmitted to the SCS 169 through the System Event Manager 543 (S304).

  When ending the scan, the scan service 571 transmits a release notification of each component device used in the scan process to the power manager 561 (S311) and also transmits a scan end notification to the user application 501 ( S312). When the power manager 561 receives an inquiry from the SCS 169 through the system event manager 543 (S 313) after that from the SCS 169 through the system event manager 543 for an inquiry to set these components to the power saving state, the power manager 561 indicates that the power saving transition of these components is permitted. The response is transmitted to the SCS 169 through the System Event Manager 543 (S314).

  Thus, the power manager 561 prohibits the power saving transition of the component devices used in the scan process during the execution of the scan process. The user application 501 does not need to be aware of this.

  FIG. 23 is a flowchart according to the second specific example of the power control of the multi-function peripheral 101.

  In print processing, the print engine 122, the HDD 233, and the finisher 303 are used. For this reason, during execution of the print process, the power saving transition of the print engine 122, the HDD 233, and the finisher 303, which are components used in the print process, is prohibited. Hereinafter, the power control by the power manager 561 will be described.

  When starting printing, the user application 501 transmits a print start request to the print service 572 (S401). In response to this, the print service 572 sends a usage notification of each component device used in the printing process to the power manager 561 (S402). When the power manager 561 receives an inquiry from the SCS 169 through the system event manager 543 after that inquiries to put these constituent devices in the power saving state (S403), the power manager 561 sends a reply that prohibits the power saving transition of these constituent devices. , And sent to the SCS 169 through the System Event Manager 543 (S404). When an inquiry to set a power saving state for other than these components is received thereafter (S405), a response to permit the power saving transition is transmitted (S406).

  When ending printing, the print service 572 transmits a release notification of each component device used in the printing process to the power manager 561 (S411) and transmits a print end notification to the user application 501 ( S412). When the power manager 561 receives an inquiry from the SCS 169 through the system event manager 543 (S 413) after that from the SCS 169 through the system event manager 543 for an inquiry to set these components to the power saving state, the power manager 561 indicates that the power saving transition of these components is permitted. The response is transmitted to the SCS 169 through the System Event Manager 543 (S414).

  In this way, the power manager 561 prohibits the power saving transition of the component devices used in the printing process during the printing process. The user application 501 does not need to be aware of this.

  FIG. 24 is a flowchart according to the third specific example of the power control of the multi-function peripheral 101.

  The JSDK application 147 is installed in the HDD or SDcard. When the JSDK application 147 is installed in the HDD, a part of the JSDK application 147 is loaded into the memory during the execution of the JSDK application 147. Therefore, if the HDD enters a power saving state while the JSDK application 147 installed in the HDD is being executed, the execution of the JSDK application 147 is not guaranteed. Therefore, it is possible to cause the JSDK application 147 to execute power control of the installation destination HDD or SDcard, but it is difficult for the JSDK application 147 to execute power control of the installation destination HDD or SDcard. Therefore, when the JSDK application 147 installed in the HDD 233 is being executed and cannot be stopped, the JSDK platform 148 prohibits the HDD 233 from transferring power. Hereinafter, the power control by the power manager 561 will be described.

  When the power manager 561 receives an inquiry from the SCS 169 to set the HDD 233 in the power saving state (S501), the power manager 561 checks whether the application public class can be stopped (S502), and whether the running JSDK application 147 can be stopped. Whether or not is confirmed (S503). Whether or not these can be stopped is notified to the Machine State Lock 562 from these. For this reason, the Power Manager 561 checks with the Machine State Lock 562 whether these can be stopped.

  If the application public class cannot be stopped (S502), the power manager 561 sends a response to the SCS 169 to prohibit the power saving transition of the HDD 233 (S511). When there is a JSDK application 147 that cannot be stopped among the running JSDK applications 147 (S503), the power manager 561 checks the installation destination of the JSDK application 147 (S504). The installation destination of the JSDK application 147 is managed by the Install Manager 545. Therefore, the power manager 561 confirms the installation destination of the JSDK application 147 with the install manager 545. When the installation destination of the JSDK application 147 that is being executed and cannot be stopped is the HDD 233 (S504), the power manager 561 transmits a response to the SCS 169 to prohibit the power saving transition of the HDD 233 (S511). When the JSDK application 147 whose installation destination is the HDD 233 is not included in the JSDK application 147 that is being executed and cannot be stopped (S504 and S505), the power manager 561 permits the SCS 169 to shift to the power saving mode of the HDD 233. A response to this effect is transmitted (S512).

  In this way, the power manager 561 prohibits the power saving transition of the HDD 233 when the JSDK application 147 installed in the HDD 233 is being executed and cannot be stopped. It is not necessary for the JSDK application 147 to be aware of this.

  FIG. 25 is a flowchart according to the fourth specific example of the power control of the multi-function peripheral 101.

  The printing process can also be executed in a power saving mode (light-off mode) in which the heater power supply is in a standby state, the motor power supply is in a standby state, and the panel power supply is in a power saving state. That is, the printing process can be executed when the touch panel 311 is in a standby state or a power saving state. However, when a print processing error occurs when the multi-function peripheral 101 is in the power saving mode, the touch panel 311 needs to be changed from the power saving state to the standby state to display that the print processing error has occurred. . For this reason, when a print processing error occurs while the multi-function peripheral 101 is in the power saving mode, the JSDK platform 148 changes the power saving transition of the touch panel 311 from permission to prohibition. Furthermore, when the error is canceled, it is necessary to return the touch panel 311 from the standby state to the power saving state. Therefore, when the error of the printing process is canceled when the multi-function peripheral 101 is in the power saving mode, the JSDK platform 148 returns the power saving transition of the touch panel 311 from prohibition to permission. Hereinafter, the power control by the power manager 561 will be described.

  When starting the printing, the user application 501 transmits a print start request to the print service 572 (S601). In response to this, the print service 572 sends a usage notification of each component device used in the print processing to the power manager 561 (S602). When the power manager 561 receives an inquiry from the SCS 169 through the system event manager 543 after that inquiries about setting these component devices to the power saving state (S603), the power manager 561 returns a response indicating that the power saving transition of these component devices is prohibited. Then, the data is transmitted to the SCS 169 through the System Event Manager 543 (S604). When an inquiry to set the power saving state for devices other than these components is received thereafter, a response to permit the power saving transition is transmitted. Therefore, when an inquiry to set the touch panel 311 to the power saving state is received thereafter (S605), a response to permit the power saving transition is transmitted (S606).

  At this time, it is assumed that the multi-function peripheral 101 is in the power saving mode and the touch panel 311 is in the power saving state. It is assumed that the multi-function peripheral 101 is executing print processing.

  When an error occurs in the print process, the print service 572 transmits an error occurrence notification to the user application 501 (S611) and also transmits an error occurrence notification to the power manager 561 (S612). In response to the error occurrence notification, the power manager 561 transmits a request for changing the power saving transition of the touch panel 311 from permission to prohibition to the SCS 169 through the system event manager 543 (S613).

  When the print processing error is canceled, the print service 572 transmits an error cancellation notification to the user application 501 (S621), and transmits an error cancellation notification to the power manager 561 (S622). In response to the error release notification, the power manager 561 transmits a request for changing the power saving transition of the touch panel 311 from prohibition to permission to the SCS 169 through the system event manager 543 (S623).

  When ending printing, the print service 572 transmits a release notification of each component device used in the printing process to the power manager 561 (S631) and also transmits a print end notification to the user application 501 ( S632). When the power manager 561 receives an inquiry from the SCS 169 through the system event manager 543 (S633) after that inquiries about setting these component devices to the power saving state, the power manager 561 permits the power saving transition of these component devices. The response is transmitted to the SCS 169 through the System Event Manager 543 (S634).

  In this way, the power manager 561 changes the power saving transition of the touch panel 311 from permission to prohibition when the MFP 101 is in the power saving mode and an error such as print processing occurs, and the MFP 101 is in the power saving mode. When an error such as print processing is canceled, the power saving transition of the touch panel 311 is returned from prohibition to permission. It is not necessary for the JSDK application 147 to be aware of these. The JSDK application can execute an error occurrence display without being aware of these.

2) Image Forming Process The image forming process of the MFP 101 will be described.

  FIG. 26 is a diagram for explaining image forming processing that can be executed by the multifunction peripheral 101. In the multi-function peripheral 101, image data for image formation processing is stored in a file in a storage format in which the storage area is continuous and stored in the HDD. Such a file is called a “RAW file”. In the UNIX (registered trademark) file system, data for information processing is stored in a HDD in a storage format in which the storage area is discrete. Such a file is called an “FFS file”. The RAW file is superior in terms of high-speed reading and high-speed writing, but the FFS file is superior in terms of providing the file from the multifunction peripheral 101 to a PC or the like.

  FIG. 26A is a diagram for describing a print process of a scanned image. The scanned image is stored in the HDD as a RAW file 631. In the print process, the image data stored in the HDD as the RAW file 631 is printed.

  FIG. 26B is a diagram for describing scan image storage processing. The scanned image is stored in the HDD as a RAW file 631, converted from the RAW file 631 to the FFS file 632, and stored in the HDD as an FSS file 632.

  FIG. 26C is a diagram for describing a print process of a stored image. The stored image is stored in the HDD as an FFS file 632. In the print processing, image data stored in the HDD as the FFS file 632 is printed.

(Modification)
The MFP 101 in FIG. 1 corresponds to an embodiment of the present invention (image forming apparatus), and information processing executed by the MFP 101 in FIG. 1 corresponds to an embodiment of the present invention (information processing method). The JSDK platform 148 in FIG. 5 corresponds to an embodiment of the present invention (information processing program), and the SDcard or CD-ROM in which the JSDK platform 148 in FIG. 5 is recorded corresponds to an embodiment of the present invention (recording medium). To do.

1 shows a multi-function machine corresponding to an embodiment of the present invention. It is a hardware block diagram concerning the compound machine of Drawing 1. It is an external view which concerns on the compound machine of FIG. Represents the operation panel. It is a class diagram of the JSDK application and JSDK platform of FIG. It is a figure for demonstrating the starting procedure of a JSDK system. It is a figure for demonstrating GUI of a JSDK system. It is a figure for demonstrating the switching operation screen. It is a figure for demonstrating a starting operation screen. It is a figure for demonstrating an end operation screen. It is a figure for demonstrating an installation operation screen. It is a figure for demonstrating the uninstall operation screen. It is a figure for demonstrating the display procedure of a starting operation screen. It is a figure for demonstrating the execution procedure of a starting process. It is a figure for demonstrating the display procedure of an installation operation screen. It is a figure for demonstrating the execution procedure of an installation process. An example of the syntax of a JNLP file is shown. It is a flowchart which concerns on the automatic update process which automatically updates a JSDK application to the JSDK application from SDcard. It is a flowchart concerning automatic update processing for automatically updating a JSDK application to a JSDK application from the Web. It is a state transition diagram of Xlet. It is a figure for demonstrating the power control of a compound machine. It is a flowchart which concerns on the 1st specific example of the power control of a compound machine. It is a flowchart which concerns on the 2nd specific example of the electric power control of a compound machine. It is a flowchart which concerns on the 3rd specific example of the electric power control of a compound machine. It is a flowchart which concerns on the 4th specific example of the power control of a multi-functional machine. FIG. 10 is a diagram for describing image forming processing that can be executed by the multi-function peripheral.

Explanation of symbols

DESCRIPTION OF SYMBOLS 101 Compound machine 111 Hardware 112 Software 113 Compound machine starting part 121 Imaging part 122 Printing part 123 Other hardware 131 Application 132 Platform 133 Application program interface 134 Engine interface 135 Virtual application service 141 Copy application 142 Printer application 143 Scanner application 144 Facsimile Application 145 Network file application 146 CSDK application 147 JSDK application 148 JSDK platform 151 Control service 152 System resource manager 153 Handler 161 Network control service 162 Facsimile control service 163 Delivery control service 164 an engine control service 165 a memory control service 166 operation panel control service 167 a certification control service 168 user directory control service 169 system control service 171 a facsimile control unit handler 172 image memory handler 201 controller 202 an operation panel 203 facsimile control unit 211 CPU
212 ASIC
221 NB
222 SB
231 MEM-P
232 MEM-C
233 HDD
234 Memory card slot 235 Memory card 241 NIC
242 USB device 243 IEEE 1394 device 244 Centronics device 301 Document setting unit 302 Paper feed unit 303 Paper discharge unit 311 Touch panel 312 Numeric keypad 313 Start button 314 Reset button 315 Function key 316 Initial setting button 321 ADF
322 Flatbed 323 Flatbed cover 501 User application 511 JSDK GUI Manager
512 Task Bar Manager
513 Error app 514 Rule app 521 JSDK Main
522 JSDK Environment
523 Local Manager
531 Xlet Manager
532 Multi Xlet Manager
533 JSDK Manager
541 Send Manager
542 Event Manager
543 System Event Manager
544 Panel Manager
545 Install Manager
546 Server / Client Manager
547 Authentication Manager
551 JSDK API
552 JSDK API
553 JSDK Session
554 Native JSDK Session
555 CVM
561 Power Manager
562 Machine State Lock
571 Scan service 572 Print service 573 File usage class 574 Network usage class 575 Panel usage class 631 RAW file 632 FFS file

Claims (22)

An image forming apparatus including a control unit that controls whether to permit or prohibit a power saving transition of components constituting the image forming apparatus,
The control means controls whether to permit or prohibit the power saving transition of the constituent devices constituting the image forming apparatus based on the execution state of the image forming process or the execution state of the application for the image forming process. An image forming apparatus.   The image forming apparatus according to claim 1, wherein the control unit prohibits a power saving shift of a component device used in the image forming process during the execution of the image forming process.   The control unit prohibits a power saving transition of the storage device when an application for image formation processing installed in the storage device of the image forming device is being executed and cannot be stopped. The image forming apparatus according to 1 or 2.   The control means is an application that is being executed and cannot be stopped when there is an application that is being executed and cannot be stopped among the applications for image forming processing installed in the storage device of the image forming apparatus. If there is an application whose installation destination is a storage device in which only a part of the application is loaded into the memory during execution of the application, the power saving transition of the storage device that is the installation destination of the application is performed. The image forming apparatus according to claim 1, wherein the image forming apparatus is prohibited.   The control unit, when an error in image forming processing occurs when the image forming apparatus is in a power saving mode, changes the power saving transition of the display device of the image forming apparatus from permitted to prohibited. Item 5. The image forming apparatus according to any one of Items 1 to 4.   When the image forming process error is canceled when the image forming apparatus is in a power saving mode, the control unit returns the power saving transition of the display device of the image forming apparatus from prohibition to permission. The image forming apparatus according to claim 1. An image forming apparatus comprising a control unit that controls whether to permit or prohibit a power saving transition of components constituting the image forming apparatus,
The control means controls whether to permit or prohibit power saving transition of components constituting the image forming apparatus based on a control request from an application for image forming processing. .   8. The image forming apparatus according to claim 7, wherein the control unit permits, by default, a power saving shift of the component device for a component device that is not requested to be controlled by an application for image formation processing.   The image forming apparatus according to claim 1, wherein the application is batch-translated from a source code to a byte code by a compiler and sequentially executed by a virtual machine.   The image forming apparatus according to claim 1, wherein the application is Xlet. An information processing method executed by an image forming apparatus,
A control stage for controlling whether to permit or prohibit the power saving transition of the constituent devices constituting the image forming apparatus,
In the control step, whether to permit or prohibit the power saving transition of the component devices constituting the image forming apparatus is controlled based on the execution status of the image forming process or the execution status of the application for the image forming process. A characteristic information processing method.   12. The information processing method according to claim 11, wherein in the control stage, during the execution of the image forming process, the power saving transition of the component devices used in the image forming process is prohibited.   The power saving transition of the storage device is prohibited when an application for image formation processing installed in the storage device of the image forming apparatus is being executed and cannot be stopped in the control step. The information processing method according to 11 or 12.   An application that is being executed and cannot be stopped when there is an application that is being executed and cannot be stopped among the applications for image forming processing installed in the storage device of the image forming apparatus in the control step. If there is an application whose installation destination is a storage device in which only a part of the application is loaded into the memory during execution of the application, the power saving transition of the storage device that is the installation destination of the application is performed. The information processing method according to claim 11, wherein the information processing method is prohibited.   The power saving transition of the display device of the image forming apparatus is changed from permission to prohibition when an error of image forming processing occurs when the image forming apparatus is in a power saving mode in the control step. Item 15. The information processing method according to any one of Items 11 to 14.   In the control step, when the error of the image forming process is canceled when the image forming apparatus is in the power saving mode, the power saving shift of the display device of the image forming apparatus is returned from prohibition to permission. The information processing method according to any one of claims 11 to 15. An information processing method executed by an image forming apparatus,
A control stage for controlling whether to permit or prohibit the power saving transition of the constituent devices constituting the image forming apparatus,
An information processing method for controlling whether to permit or prohibit a power saving shift of components constituting the image forming apparatus based on a control request from an application for image forming processing in the control step .   18. The information processing method according to claim 17, wherein, for a component device that does not receive a control request from an application for image formation processing in the control step, power saving shift of the component device is permitted by default.   The information processing method according to any one of claims 11 to 18, wherein the application is batch-translated from source code to byte code by a compiler and sequentially executed by a virtual machine.   The information processing method according to claim 11, wherein the application is Xlet.   An information processing program for causing a computer to execute the information processing method according to any one of claims 11 to 20.   21. A recording medium on which an information processing program for causing a computer to execute the information processing method according to claim 11 is recorded.

Images