JP5664692B2 - Electronic device, image forming apparatus, information processing method, information processing program, and recording medium - Google Patents

Description

The present invention relates to an electronic apparatus including an image forming apparatus such as a copy / printer / scanner / facsimile / multifunction machine / multifunction machine, and a terminal device such as a personal computer, an information processing method, an information processing program, and an SD card / CD-ROM. It relates to the medium.

  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. These softwares can be switched. 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.

  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 electronic device having a new application management mechanism.

In order to achieve the above object, an electronic apparatus according to the present invention is an electronic apparatus having a first application and a second application having screen information for generating a screen displayed on a display unit used by the electronic apparatus. And detecting means for detecting the first application selected based on an operation screen for performing a predetermined operation on the first application displayed on the display unit; and the detected first the application, the management means for imparting Viewing permission to view the screen on the display unit, the first screen based on the first screen information that the application has to said display permission is granted, the display unit a display control unit for displaying, when said error or rule violation in the first application has occurred, the display control means, before Displaying the second screen based on the screen information having the second application on the display unit.

In order to achieve the above object, an information processing method according to the present invention includes an electronic device having a first application and a second application having screen information for generating a screen displayed on a display unit used by the electronic device. A detection step of detecting the first application selected based on an operation screen for performing a predetermined operation on the first application displayed on the display unit. If, on the sensed first application, the based on the management step and the first screen information that the application has to said display permission is granted to grant Viewing privileges for displaying the screen on the display unit 1 screen has a display control step of displaying on the display unit, error or Lou in the first application If a violation occurs, the display control step displays the second screen based on the screen information having the second application on the display unit.

As described above, the present invention proposes an electronic apparatus having a new application management mechanism.

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 screen figure of an error occurrence display dialog. FIG. 10 is a class diagram related to a thread group setting process. It is a sequence diagram concerning an error occurrence display process. It is a screen figure of a rule violation display dialog. It is a sequence diagram concerning a rule violation display process. FIG. 10 is a diagram for describing image forming processing that can be executed by the multi-function peripheral. 1 represents a PC corresponding to an embodiment of the present invention. It is a class diagram of the JSDK application and JSDK platform in the PC. It is a figure for demonstrating the execution procedure of the preparation process of the remote operation performed within a multi-functional machine.

  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 a rule has been violated 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 as an interface between the C language and the Java (registered trademark) language, 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 and SimpleOcr, and SimpleCopy and SimpleOcr occupy 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 of 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. Then, 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) Error application The error application 513 in FIG. 5 will be described.

  The error application 513 is a JSDK application that displays information indicating that an error has occurred when an error occurs in another JSDK application. Information indicating that an error has occurred is displayed in such a manner that an error occurrence display dialog 601A is displayed on the forefront of the operation panel 202 of the multi-function peripheral 101 as shown in FIG. 21A. In the error occurrence display dialog 601A, an error message 611, an error type 612, an error occurrence location 613, and the like are displayed as information relating to the error occurrence. When the OK button 614 is pressed, the error occurrence display dialog 601A is closed. When the Detail button 615 is pressed, the screen moves to the error occurrence display dialog 601B of FIG. 21B. In the error occurrence display dialog 601B, error details 616 and the like are displayed as information relating to the occurrence of the error. When the Close button 617 is pressed, the error occurrence display dialog 601B is closed. Such information may be notified to an external device via a network. For example, the service center may be notified so that the service center can be supported.

  Here, an exception (exception) of Java (registered trademark) is handled as an error. Here, the error application 513 displays information indicating that the thrown exception was not caught when the exception thrown from another JSDK application was not caught. Here, a thread group of Java (registered trademark) is used for exchanging the exception. If an exception thrown from a thread belonging to the thread group is not caught in the thread group, a thread group. There is a function that the uncaughtException method is called. The thread group further has a function that each thread can access information related to other threads belonging to each thread group. The thread group further has a function that a parent-child relationship (tree structure) can be set between the thread groups. The thread group further has a function of registering the name of each thread group.

  FIG. 22 is a class diagram related to the thread group setting process.

  When the JSDK Manager 533 generates each Manager such as the Multi Xlet Manager 532, the JSDK Manager 533 assigns a thread group to each Manager such as the Multi Xlet Manager 532 (S1). Each Manager such as the Multi Xlet Manager 532 generates a thread using the thread group. By using this, the Multi Xlet Manager 532 manages the life cycle of the Xlet Manager 531 and the like.

  The Multi Xlet Manager 532 gives a thread group to each Xlet Manager 531 when generating each Xlet Manager 531 (S2). Each Xlet Manager 531 generates a thread using the thread group. By using this, the Xlet Manager 531 manages information related to the state of the Xlet such as the user application 501, the life cycle, and the like.

  When the Xlet such as the user application 501 generates a sub thread, the Xlet Manager 531 gives a thread group to the Xlet such as the user application 501 (S3). The Xlet such as the user application 501 generates a thread using the thread group.

  In this way, a tree structure of thread groups is formed. The apex of the thread group tree structure is managed by the JSDK Manager 533.

  FIG. 23 is a sequence diagram related to the error occurrence display process.

  First, when the error application 513 is activated (S11), the error application 513 requests the JSDK Manager 533 to notify the JSDK Manager 533 that the JSDK Manager 533 notifies the error application 513 that an error has occurred. (S12).

  Next, when an error occurs (S21), the CVM 555 causes the JSDK Manager 533 to read ThreadGroup. The uncaightException method is called (S22). Next, the error application 513 is notified from the method of the JSDK Manager 533 according to the notification registration to the error application 513 (S23). Next, the error application 513 requests the Multi Xlet Manager 532 to display the error occurrence display dialog 601 on the forefront (S24). Next, the error occurrence display dialog 601 is displayed on the forefront by the Multi Xlet Manager 532 (S25).

2) Rule Application The rule application 514 in FIG. 5 will be described.

  The rule application 514 is a JSDK application that displays information indicating that there is a rule violation when there is a rule violation in a processing request of another JSDK application. Information indicating that there is a rule violation is displayed in a format in which a rule violation display dialog 602 is displayed on the forefront of the operation panel 202 of the multi-function peripheral 101 as shown in FIG. The rule violation display dialog 602 displays a rule violation message 621, a rule violation type 622, a rule violation location 623, and the like as information relating to the rule violation. When the OK button 624 is pressed, the rule violation display dialog 602 is closed. Such information may be notified to an external device via a network.

  Here, the rule violation of the service request from the JSDK application to the JSDK API 551 is handled as the rule violation. Specific examples of service request rule violations include rule violations related to thread limit, rule violations related to file open limit, color / monochrome settings related to print processing, rule violations such as paper size and number of sheets, and scanning. Examples include color / monochrome settings relating to processing, and violation of rules such as paper size and number of sheets. Here, the rule application 514 displays information indicating that there is a rule violation when a service request from another JSDK application to the JSDK API 551 is in violation. Here, a Java (registered trademark) thread group is used to monitor rule violations.

  FIG. 25 is a sequence diagram relating to rule violation display processing.

  First, when the rule application 514 is activated (S31), the notification registration that the Multi Xlet Manager 532 notifies the rule application 514 that there is a rule violation when the rule is violated is sent from the rule application 514 to the Multi application. The Xlet Manager 532 is requested (S32).

  Next, when there is a service request from the JSDK application to the JSDK API 551 (S41), the JSDK API 551 acquires information on the thread group of the service request source (S42). Next, the JSDK API 551 requests the Multi Xlet Manager 532 for information on whether or not the service request source thread is authorized to receive the service (S43). Next, the Multi Xlet Manager 532 identifies the service request source thread based on the thread group (S44). Next, the Multi Xlet Manager 532 checks whether the service request source thread has the authority to receive the service (S45). Next, when the service request source thread does not have the authority to receive the service, the Multi Xlet Manager 532 notifies the rule application 514 that the service request from the JSDK application to the JSDK API 551 has violated the rule (S46). ) Next, the rule application 514 requests the Multi Xlet Manager 532 to display the rule violation display dialog 602 on the forefront (S47). Next, the rule violation display dialog 602 is displayed on the forefront by the Multi Xlet Manager 532 (S48).

3) Image Forming Process FIG. 26 is a diagram for explaining an image forming process that can be executed by the multifunction machine 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.

(emulator)
FIG. 27 shows a PC (personal computer) 701 corresponding to an embodiment of the present invention. A PC 701 in FIG. 27 is connected to the MFP 101 in FIG. 1 via a network 801, and functions as an emulator of the MFP 101 in FIG.

  27 includes a PC main body 711, a keyboard 712, a mouse 713, a display 714, and the like. The PC main body 711 includes a CPU, ROM, RAM, NVRAM, HDD, MODEM, NIC, and the like. The keyboard 712 and the mouse 713 serve as hardware (operation unit) for an operator to input instead of the operation panel 202 of the multi-function peripheral 101. The display 714 replaces the operation panel 202 of the multifunction machine 101 and becomes hardware (display unit) for an operator to obtain output.

  FIG. 28 is a class diagram of the JSDK application 147 and the JSDK platform 148 in the PC 701 in FIG. A JSDK application 147 and a JSDK platform 148 similar to those of the multifunction machine 101 of FIG. 1 are also present in the PC 701 of FIG. Refer to FIG. 5 for the class diagram of the JSDK application 147 and the JSDK platform 148 in the MFP 101 of FIG. Hereinafter, the difference between FIG. 5 and FIG. 28 will be described.

  First, the Panel Manager 544 in FIG. 5 is replaced with the Panel Manager Emulator 744 in FIG. Second, the JSDK Session 553 in FIG. 5 is replaced with the Emulator JSDK Session 753 in FIG. Third, the Native JSDK Session 554 in FIG. 5 is replaced with the Event Emulator 754 in FIG. Fourth, CVM 555 in FIG. 5 is replaced with JVM 755 in FIG.

  The Panel Manager Emulator 744 is a class that emulates the Panel Manager 544 and converts the operation of the operation panel 202 into the operation of the keyboard 712 or the mouse 713. The Emulator JSDK Session 753 is a class that executes communication path establishment processing. The Event Emulator 754 is a class that emulates the operation of the compound machine 101. The JVM 755 is a Java (registered trademark) virtual machine for executing the JSDK application 147 and the JSDK platform 148.

  The starting procedure of the JSDK system in the PC 701 is the same as that shown in FIG. The GUI of the JSDK system in the PC 701 is the same as that shown in FIG. The GUI is an operation screen or task bar for the user application 501 in the multi-function peripheral 101 or the PC 701 and is displayed by the JSDK GUI Manager 511 to Task Bar Manager 512 in the PC 701. The operation unit is a keyboard 712 and a mouse 713, and the display unit is a display 714.

  FIG. 29 is a diagram for explaining the execution procedure of the remote operation preparation process executed in the multi-function peripheral 101 of FIG.

  First, a session is established (S1) between the Server / Client Manager 546 in the MFP 101 and the Server / Client Manager 546 in the PC 701.

  Next, the Server / Client Manager 546 in the multi-function peripheral 101 inquires of the JSDK Manager 533 in the multi-function peripheral 101 whether or not it can shift to remote operation, and determines whether or not it can shift to remote operation (S2).

  Next, if the server / client manager 546 in the multi-function peripheral 101 can shift to remote operation, the server / client manager 546 sends a request for a message necessary for the remote operation to the PC 701 via the send manager 541 in the multi-function peripheral 101 (S3). Then, a response related to the message required for the remote operation is received from the PC 701 via the Event Manager 542 in the multi-function peripheral 101 (S4).

  Next, the server / client manager 546 in the multi-function peripheral 101 transmits a request to transfer information for remote operation to the PC 701 to the panel manager 544 (S5).

  Finally, a notification that the remote operation preparation process has been completed is exchanged between the Server / Client Manager 546 in the MFP 101 and the Server / Client Manager 546 in the PC 701 (S6). As a result, remote control of the multi-function peripheral 101 from the PC 701 becomes possible.

(Modification)
1 corresponds to an embodiment of the present invention (image forming apparatus), and information processing executed in the MFP 101 of FIG. 1 corresponds to an embodiment of the present invention (information processing method). . The JSDK GUI Manager 511, the Task Bar Manager 512, the error application 513, and the rule application 514 in FIG. 5 correspond to the embodiments of the present invention (information processing program), respectively, and the JSDK GUI Manager 511, the Task Bar Manager 512, the error application 513, and the like in FIG. Each of the SD card and the CD-ROM in which the rule application 514 is recorded corresponds to an embodiment of the present invention (recording medium). As these utilization modes, download of these information processing programs, option sales of these recording media, and the like are conceivable.

  27 corresponds to an embodiment of the present invention (terminal device), and information processing executed in the PC 701 of FIG. 27 corresponds to an embodiment of the present invention (information processing method). The JSDK GUI Manager 511, the Task Bar Manager 512, the error application 513, and the rule application 514 in FIG. 28 correspond to examples of the present invention (information processing program), respectively, and the JSDK GUI Manager 511, the Task Bar Manager 512, the error application 513, and the like in FIG. Each of the SD card and the CD-ROM in which the rule application 514 is recorded corresponds to an embodiment of the present invention (recording medium). As these utilization modes, download of these information processing programs, option sales of these recording media, and the like are conceivable.

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
601 Error occurrence display dialog 602 Rule violation display dialog 611 Error message 612 Error type 613 Error location 614 OK button 615 Detail button 616 Details of error 617 Close button 621 Rule violation message 622 Rule violation type 623 Rule violation location 624 OK button 631 RAW file 632 FFS file 701 PC
711 PC main body 712 Keyboard 713 Mouse 714 Display 744 Panel Manager Emulator
753 Emulator JSDK Session
754 Event Emulator
755 JVM
801 network

JP 2002-84383 A

Claims (21)

An electronic device having a first application and a second application having screen information for generating a screen displayed on a display unit used by the electronic device,
Detecting means for detecting the first application selected based on an operation screen for performing a predetermined operation on the first application displayed on the display unit;
The detected first application, and management means for imparting Viewing permission to view the screen on the display unit,
The first screen based on the first screen information that the application has to said display permission is granted, a display control unit for displaying on the display unit,
If an error or rule violation occurs in the first application,
Wherein the display control unit, an electronic apparatus to display a second screen based on the previous SL screen information having the second application on the display unit.   The electronic device according to claim 1, wherein the display control unit causes the second screen to be superimposed on a screen being displayed on the display unit.   The electronic device according to claim 1, wherein the second screen is a dialog screen including information indicating that the predetermined condition is not satisfied. The second application has screen information including information on the error when an error occurs in the first application,
The management means notifies the second application of the occurrence of the error when an error occurs in the first application,
The electronic device according to any one of claims 1 to 3, wherein the display control unit causes the display unit to display an error occurrence display dialog screen based on the screen information of the notified second application. The second application has screen information including information on the predetermined rule violation when there is a predetermined rule violation in the processing executed by the first application,
When the predetermined rule is violated in the processing executed by the first application, the management unit notifies the second application that the predetermined rule has been violated,
4. The electronic device according to claim 1, wherein the display control unit causes the display unit to display a rule violation display dialog screen based on the screen information of the notified second application. 5.   When the predetermined operation is a switching operation, the display control unit causes the display unit to occupy and display a first screen based on screen information included in the first application to which the display authority is granted. Item 6. The electronic device according to any one of Items 1 to 5.   The electronic device according to claim 6, wherein the display control unit displays an error message display screen including a reason why the state is abnormal when the state of the first application to which the display authority is granted is abnormal. . The first application has identification information for identifying whether or not the first application has a predetermined GUI.
The electronic device according to claim 6, wherein the display control unit displays a screen based on the identification information when the state of the first application to which the display authority is given is normal.   The display control unit displays a screen based on the predetermined GUI when the identification information included in the first application to which the display authority is granted has a predetermined GUI, and the identification information is determined in advance. The electronic device according to claim 8, wherein a screen on which information indicating characteristics of the first application is displayed is displayed when indicating that the GUI is not provided.   The first screen when the predetermined operation is a switching operation includes a task bar for switching to the first screen based on screen information of another first application. The electronic device as described in.   When the predetermined operation is a start operation for starting the first application, the display control unit displays the first screen based on the screen information included in the first application to which the display authority is given as the operation. The electronic device according to claim 1, wherein the electronic device is displayed while being superimposed on a screen.   When the predetermined operation is an end operation for ending the first application being executed, the display control means displays a first screen based on screen information of the first application to which the display authority is given. The electronic device according to claim 1, wherein the electronic device is displayed so as to be superimposed on the operation screen.   When the predetermined operation is an installation operation for installing the first application, the display control means displays the first screen based on the screen information included in the first application to which the display authority is given as the operation. The electronic device according to claim 1, wherein the electronic device is displayed so as to be superimposed on a screen.   The display control means, when the predetermined operation is an uninstall operation for uninstalling the first application, a first screen based on screen information possessed by the first application to which the display authority is granted, The electronic device according to claim 1, wherein the electronic device is displayed so as to be superimposed on the operation screen.   The electronic device according to claim 1, wherein the first application and the second application are Xlet. The electronic device according to claim 1, wherein the error is an error that has occurred in the first application that is being activated.   The electronic device according to any one of claims 1 to 16, wherein the rule violation is a rule violation for a process executed by the first application. An image forming apparatus having a first application and a second application having screen information for generating a screen displayed on a display unit used by the image forming apparatus,
Detecting means for detecting the first application selected based on an operation screen for performing a predetermined operation on the first application displayed on the display unit;
The detected first application, and management means for imparting Viewing permission to view the screen on the display unit,
The first screen based on the first screen information that the application has to said display permission is granted, a display control unit for displaying on the display unit,
If an error or rule violation occurs in the first application,
Wherein the display control unit, an image forming apparatus to display a second screen based on the screen information and the second application has the display unit. An information processing method executed by an electronic device having a first application and a second application having screen information for generating a screen displayed on a display unit used by the electronic device,
A detection step of detecting the first application selected based on an operation screen for performing a predetermined operation on the first application displayed on the display unit;
The detected first application, the management step to grant Viewing privileges for displaying the screen on the display unit,
The first screen based on the first screen information that the application has to said display permission is granted, anda display control step of displaying on the display unit,
If an error or rule violation occurs in the first application,
Wherein the display control step, the information processing method for displaying a second screen based on the screen information and the second application has the display unit. An information processing program for causing a computer to execute the information processing method according to claim 19 . A computer-readable recording medium on which an information processing program for causing a computer to execute the information processing method according to claim 20 is recorded.

Images