JP5370530B2 - Information processing apparatus, information processing method, information processing program, and recording medium - Google Patents

Description

  The present invention relates to an information processing apparatus such as a personal computer / server computer or an image forming apparatus such as a copy / printer / scanner / facsimile / multifunction machine / multifunction machine, an information processing method, an information processing program, The present invention relates to a recording medium such as an SD memory card.

  In recent years, multifunction peripherals and multifunction peripherals having a copy function, a printer function, a scanner function, and a facsimile function have come to be marketed. When a multifunction device or multifunction device functions as a copy or a printer, it prints an image on printing paper. When it functions as a copy or a scanner, it reads an image from a read original, and functions as a facsimile. In the case of functioning, images are exchanged with other devices via a telephone line.

  In recent years, various applications are often installed in multifunction peripherals and multifunction peripherals. For this reason, it is not uncommon for users of MFPs and MFPs to be unaware of the existence of convenient applications. As a result, the existence of a convenient application is wasted, and the user of the multi-function peripheral or the multi-function peripheral is continuously burdened. Such a situation is the same for information processing apparatuses other than image forming apparatuses such as multifunction peripherals and multi-function peripherals.

  An object of the present invention is to propose a technique for providing a user of an information processing apparatus with a convenient application regarding the information processing apparatus in which various applications are mounted.

  In order to solve the above problems, the present invention provides an information processing apparatus capable of executing a program, the collecting means for collecting information relating to the usage status of the information processing apparatus, and the information collected by the collecting means. It has a detection means for detecting a program recommended to be used in the information processing apparatus, and a display means for displaying information on the function of the program detected by the detection means on a display device.

  The present invention proposes a method for providing a user of an information processing apparatus with a convenient application regarding the information processing apparatus in which various applications are mounted.

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 functional block diagram concerning COLLECTOR. FIG. 2 is a state transition diagram related to state transition of the multi-function apparatus of FIG. 1. FIG. 2 is a state transition diagram related to state transition of the multi-function apparatus of FIG. 1. FIG. 2 is a state transition diagram related to state transition of the multi-function apparatus of FIG. 1. FIG. 2 is a state transition diagram related to state transition of the multi-function apparatus of FIG. 1. FIG. 2 is a state transition diagram related to state transition of the multi-function apparatus of FIG. 1. FIG. 2 is a state transition diagram related to state transition of the multi-function apparatus of FIG. 1. FIG. 2 is a state transition diagram related to state transition of the multi-function apparatus of FIG. 1. It is a figure for demonstrating a framework and a class library. It is a flowchart figure which concerns on the detection process of a JSDK application. It is a flowchart figure which concerns on the production | generation process of a JSDK application. It is a figure which shows the example of a display of an application state transition screen. It is a figure which shows the example of a display of the application state transition screen of edit mode. It is a figure which shows the example of a display of a state edit screen. It is a figure which shows the example of a display of a transition condition setting screen. It is a figure which shows the example of a display of the application state transition screen in which the edit result was reflected. It is a figure which shows the example of a display of a functional module state transition screen. It is a figure which shows the example of a display of the state edit screen which concerns on the state in a functional module. It is a figure which shows the example of a display of the transition condition setting screen which concerns on the state transition in a functional module. It is a figure which shows the example of a display of a detailed information setting screen.

  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.

(COLLECTOR)
FIG. 5 is a functional block diagram relating to COLLECTOR 401. The COLLECTOR 401 corresponds to the JSDK application 147 installed in the multifunction machine 101 of FIG. The COLLECTOR 401 collects various information related to the usage status of the multi-function peripheral 101 of FIG. 1 and executes various information processing related to the JSDK application 147 of the multi-function peripheral 101 of FIG.

  As illustrated in FIG. 5, the COLLECTOR 401 includes an information collection unit 411, an information acquisition unit 412, an application detection unit 413, an application generation unit 414, and an application notification unit 415. The information collection unit 411 corresponds to a functional block that automatically collects information related to the usage status of the multi-function peripheral 101. The information acquisition unit 412 corresponds to a functional block that automatically acquires information related to the state transition of the multi-function peripheral 101. The application detection unit 413 is a functional block that automatically detects the JSDK application 147 recommended for use in the multifunction machine 101. The application generation unit 414 is a functional block that automatically generates a JSDK application 147 recommended for use in the multifunction machine 101. The application notification unit 415 is a functional block that automatically notifies the user of the existence of the JSDK application 147 recommended for use in the multifunction machine 101.

  6, FIG. 7, and FIG. 8 are state transition diagrams relating to the state transition of the multi-function peripheral 101 of FIG.

  FIG. 6 shows a state transition diagram in the case where the user designates an address and transmits it by e-mail.

  First, when the user turns on the power of the multi-function peripheral 101, the multi-function peripheral 101 transitions to an authentication state 501 (S1). Next, when the user logs into the multi-function peripheral 101, the multi-function apparatus 101 transitions to the function selection state 502 (S2). Next, when the user selects the scan function, the multi-function peripheral 101 transitions to the scan state 503 (S3). Next, when the user completes the scanning operation, the multifunction machine 101 returns to the function selection state 502 (S4). Next, when the user selects the address function, the multi-function peripheral 101 transitions to the address state 504 (S5). Next, when the user completes the addressing operation, the MFP 101 returns to the function selection state 502 (S6). Next, when the user selects the e-mail function, the multi-function peripheral 101 transitions to an e-mail state 505 (S7). Next, when the user completes the e-mail transmission operation, the MFP 101 returns to the function selection state 502 (S8).

  In COLLECTOR 401, the information collection unit 411 collects information related to the usage status of the multi-function peripheral 101. The information is, for example, “log information” that indicates which user has used which function and which setting at which date and time. In the COLLECTOR 401, the information acquisition unit 412 uses the information collected by the information collection unit 411 to acquire information related to the state transition of the MFP 101. The information is, for example, “history information” that indicates how the state of the MFP 101 has changed from S1 to S8. As a result, the COLLECTOR 401 can grasp the state transition process of the multi-function peripheral 101.

  When the user often sends the scan result by specifying an address and sending it by e-mail as the usage status of the MFP 101 in FIG. 1, the state transition “S3- The appearance frequency of “S4-S5-S6-S7-S8” will increase. Therefore, it is convenient if the state transition (SX) from the scan state 503 to the address state 504 and the state transition (SY) from the address state 504 to the e-mail state 505 can be executed as in the state transition of FIG. . This is equivalent to the transition of the operation screen directly from the scan screen to the addressing screen after the completion of the scanning operation, or the transition of the operation screen directly from the addressing screen to the e-mail transmission screen after the completion of the addressing operation. To do.

  1 is assumed to have a JSDK application 147 that can execute the state transition “SV-SW-SX-SY-SZ” in FIG. The JSDK application 147 is a convenient JSDK application 147 that can execute the state transition of FIG. 7 from the above viewpoint. The existence of such a JSDK application 147 can be detected using information related to the state transition of the multi-function peripheral 101 of FIG. Therefore, in the COLLECTOR 401, the application detection unit 413 uses the information acquired by the information acquisition unit 412 (which corresponds to the information collected by the information collection unit 411 if it is the original) and uses such a JSDK application 147. Existence is detected as a JSDK application 147 recommended for use in the multifunction machine 101. Details of the detection method will be described later. Further, in the COLLECTOR 401, the application notification unit 415 notifies the user of the presence of the JSDK application 147 detected by the application detection unit 413 as a JSDK application 147 recommended for use in the multi-function peripheral 101. Details of the notification method will be described later.

  Further, for example, when the scan result is transmitted by e-mail and FAX transmission, after the transition from step S1 to step S5 in FIG. 6 described above, in the address state 504, the user sets the FAX number together with the mail address as an address designation operation. input. Note that as the address designation operation, the user name of the user as the destination may be selected instead of directly inputting the mail address or the FAX number. In this case, a convenient transmission destination may be set for each user. Some users have their email addresses registered as destinations, while others have their fax numbers or both email addresses and fax numbers registered as destinations. When such an addressing operation is completed, the multi-function peripheral 101 returns to the function selection state 502 (S6). Next, when the user selects the e-mail function, the multi-function peripheral 101 transitions to an e-mail state 505 (S7). Next, when the user completes the e-mail transmission operation, the MFP 101 returns to the function selection state 502 (S8). Further, when the user selects the FAX function, the multi-function peripheral 101 transitions to the facsimile state 506 (S9). When the FAX transmission is completed, the MFP 101 returns to the function selection state (S10).

  As described above, when the user frequently performs transmission by e-mail and FAX transmission by specifying the address of the scan result as the usage status of the multi-function peripheral 101, the state transition of FIG. The appearance frequency of “S3-S4-S5-S6-S7-S8-S9-S10” will increase. In such a case, in the COLLECTOR 401, the application detection unit 413 uses the information acquired by the information acquisition unit 412, as shown in “SV-SW-SX-SY-SZ-SY′-SZ ′” illustrated in FIG. 9. The existence of the JSDK application 147 capable of simple state transition is detected as the JSDK application 147 recommended for use in the multi-function peripheral 101.

  When the user transmits the scan result by e-mail and prints it, after the transition from step S1 to step S8 in FIG. 6 described above, in the function selection state 502, the user sets the print function as the print target. select. In response to the user's selection, the MFP 101 transitions to the print state 507 (S11). When the printing of the printing result is completed, the multifunction peripheral 101 returns to the function selection state (S12).

  As described above, when the user frequently transmits and prints the scan result by e-mail as the usage status of the multi-function peripheral 101, the status transition “S3-S4-S5-” of FIG. The appearance frequency of “S6-S7-S8-S11-S12” will increase. In such a case, in the COLLECTOR 401, the application detection unit 413 uses the information acquired by the information acquisition unit 412 to be in a state such as “SV-SW-SX-SY-SZ-SZ ″” illustrated in FIG. The existence of the JSDK application 147 capable of transition is detected as the JSDK application 147 recommended for use in the multi-function peripheral 101.

  In addition, when the user transmits the scan result by e-mail and prints the address of the scan result transmission destination for destination confirmation, the function selection state 502 after the transition from step S1 to step S8 in FIG. The user selects a print function with the address (transmission history) of the transmission destination of the scan result as a print target. In response to the user's selection, the MFP 101 transitions to the print state 507 (S11). When printing of the destination address is completed, the multi-function peripheral 101 returns to the function selection state (S12).

  As described above, when the user frequently transmits the scan result by e-mail and prints the destination address of the scan result as the usage status of the MFP 101, the state transition of FIG. The appearance frequency of “S3-S4-S5-S6-S7-S8-S11-S12” will increase. In such a case, in the COLLECTOR 401, the application detection unit 413 uses the information acquired by the information acquisition unit 412 to be in a state such as “SV-SW-SX-SY-SZ-SY ″” illustrated in FIG. 11. The existence of the JSDK application 147 capable of transition is detected as the JSDK application 147 recommended for use in the multi-function peripheral 101. When the address function module that realizes the address state 504 is updated to a version that has a function of printing a destination address, the application detection unit 413 of the COLLECTOR 401 displays “ The existence of the JSDK application 147 capable of state transition such as “SV-SW-SX-SY-SZ-Sx-Sy” is detected as the JSDK application 147 recommended for use in the multi-function peripheral 101. In FIG. 12, the transition of Sx indicates a transition from the address state 504 to the address print state (address print) 504 ′ inside the address function module. The transition of Sy indicates a transition of return from the address printing state in the address function module.

  Next, details of the log information collection method and the history information acquisition method will be described. Log information is collected at the function level of the multi-function peripheral 101. The copy function is used, the scan function is used, the print function is used, the facsimile function is used, the address function is used, and the e-mail function is used. It is assumed that the application 131 installed in the multifunction peripheral 101 is created based on the function level class (functional module) of the multifunction peripheral 101. The class relating to the scan state 503 (scan function module), the class relating to the address state 504 (address function module), and the class relating to the email state 505 (email function module). This makes it easy to obtain history information related to the state transition of the MFP 101 at the function level (functional module unit) of the MFP 101, and which JSDK application 147 can execute what state transition. It becomes easy to detect at the function level (functional module unit) of the multi-function peripheral 101.

  Details of the detection method of the JSDK application 147 will be described. Even if the JSDK application 147 to be detected is “installed” in the HDD 233 of the multi-function peripheral 101 or the memory card 235 of the multi-function apparatus 101, the JSDK application 147 exists in the media inserted in the multi-function apparatus 101 or in the network connected to the multi-function apparatus 101. It may be “not installed”. The COLLECTOR 401 automatically collects information related to the JSDK application 147 periodically from the HDD 233, the memory card 235, the media, and the network, and manages it as a database as “application information” related to the JSDK application 147 to be detected. Shall be kept. Information related to the state transition of each JSDK application 147 is also registered in the application information. Therefore, the application detection unit 413 uses the information related to the state transition of the multi-function peripheral 101 collected by the information collection unit 411 and the information related to the state transition of each JSDK application 147 stored in the database. JSDK application 147 that recommends is detected.

  Details of the notification method of the JSDK application 147 will be described. The presence of the detected JSDK application 147 is notified to the user by being displayed in the banner area of the operation screen displayed on the touch panel 311 of the multifunction machine 101. When the detected JSDK application 147 is not installed, the presence of the detected JSDK application 147 may be notified after being installed or may be notified without being installed. The JSDK application 147 notified without being installed is assumed to be installed with a pressing operation of the banner area as a trigger.

  As described above, the COLLECTOR 401 of the multi-function peripheral 101 in FIG. 1 uses the information related to the state transition of the multi-function apparatus 101 (if it is the case, it corresponds to the information related to the use status of the multi-function apparatus 101). The presence of the JSDK application 147 recommended for use on the machine 101 is detected and notified to the user. The usage content of how the multi-function peripheral 101 is used is reflected in the detected content of what JSDK application 147 is detected. In this way, the COLLECTOR 401 of the MFP 101 of FIG. 1 can provide a convenient JSDK application 147 to the user.

  The COLLECTOR 401 uses the information related to the usage status of the multi-function peripheral 101 and the information related to the state transition in “user units”, and recommends the JSDK application 147 that recommends the use in the multi-function peripheral 101 in “user units”. Detect presence and notify user. This is because it is more convenient to reflect the characteristics of each user in the recommended JSDK application 147 because the usage of the MFP 101 reflects the individuality of each user. Users are managed by user IDs. As a result, the JSDK application 147 “A” is recommended for the user “Mr. Suzuki” with the user ID “001”, and the JSDK application 147 “B” is recommended for the user “Mr. Sato” with the user ID “002”. The user “Mr. Okubo” with the user ID “003” recommends that the JSDK application 147 “C” is recommended. If the MFP 101 is not subjected to login processing, it may be a device unit instead of a user unit.

  In COLLECTOR 401, instead of “detecting” the JSDK application 147 recommended for use in the multi-function peripheral 101, the application detection unit 413 uses the information acquired by the information collection unit 411 or the information acquisition unit 412. The application generation unit 414 may “generate” the JSDK application 147 recommended for use in the multi-function peripheral 101. Accordingly, it is possible to receive advantages such as eliminating the necessity of preparing the recommended JSDK application 147 and being able to cope with the case where the recommended JSDK application 147 does not exist.

  Details of the method of generating the JSDK application 147 will be described. The COLLECTOR 401 generates the JSDK application 147 from the state transition diagram as shown in FIG. The state transition diagram of FIG. 8 can be generated from log information and history information. The description language of the generated JSDK application 147 is, of course, Java (registered trademark), but XML software may be generated based on XMI in the same manner as the UML drawing tool. Further, the MFP 101 of FIG. 1 has a framework and class library for facilitating generation of the JSDK application 147 as shown in FIG. The framework is semi-completed software that serves as a template for the JSDK application 147 and provides an upper layer of the JSDK application 147. The class library is a library of classes that are parts of the JSDK application 147, and provides a lower layer of the JSDK application 147.

  The framework is composed of a logic framework and a user interface framework. The logic framework is a logic-related framework of the JSDK application 147 and regulates the state transition of the multi-function peripheral 101. The user interface framework is a framework related to the user interface of the JSDK application 147 and regulates the screen transition of the MFP 101.

  The class library is a copy class that is a copy related class, a printer class that is a printer related class, a scanner class that is a scanner related class, a facsimile class that is a facsimile related class, and an operation panel class that is an operation panel related class. The network class is a network-related class.

  The generated JSDK application 147 may be modified by a user or a super user. In addition, regarding the generation method of the JSDK application 147, a similar generation method is disclosed in Japanese Patent Application No. 2004-062413.

  Information relating to the state transition of the JSDK application 147 generated by the application generation unit 414 is included in the application information and registered as a database.

  FIG. 14 is a flowchart relating to the detection process of the JSDK application 147.

  The COLLECTOR 401 first collects log information related to the usage status of the MFP 101 (S101), and acquires history information related to the state transition of the MFP 101 (S102). For example, the log information collection process and the history information acquisition process may be executed every time a predetermined time is reached, or may be executed every time a predetermined time elapses. It may be executed every time.

  Next, the COLLECTOR 401 detects the JSDK application 147 recommended for use in the multi-function peripheral 101 (S103), and notifies the user of the existence of the JSDK application 147 recommended for use in the multi-function peripheral 101 (S104). Become. For example, when the appearance frequency of a specific state transition reaches a specific threshold, the detection process of the JSDK application 147 is executed in such a manner that the JSDK application 147 that can execute the specific state transition is detected. . The notification process of the JSDK application 147 is executed immediately after the detection process of the JSDK application 147 is executed, for example. Since the touch panel 311 of the multi-function peripheral 101 is in principle occupied by one of the applications 131, the notification process of the JSDK application 147 is executed through the application 131.

  FIG. 15 is a flowchart relating to the generation process of the JSDK application 147.

  The COLLECTOR 401 first collects log information related to the usage status of the MFP 101 (S201), and acquires history information related to the state transition of the MFP 101 (S202). For example, the log information collection process and the history information acquisition process may be executed every time a predetermined time is reached, or may be executed every time a predetermined time elapses. It may be executed every time.

  Next, the application generation unit 414 of the COLLECTOR 401 generates a JSDK application 147 recommended for use in the multi-function peripheral 101 (S203), and the application notification section 415 includes the JSDK application 147 recommended for use in the multi-function peripheral 101. Is notified to the user (S204). For example, when the appearance frequency of a specific state transition reaches a specific threshold, the generation process of the JSDK application 147 is executed in the form of generating a JSDK application 147 that can execute the specific state transition. . The notification process of the JSDK application 147 is executed immediately after the generation process of the JSDK application 147 is executed, for example. Since the touch panel 311 of the multi-function peripheral 101 is in principle occupied by one of the applications 131, the notification process of the JSDK application 147 is executed through the application 131.

  In the above description, an example in which the application generation unit 414 automatically generates the JSDK application 147 that can execute the state transition based on the history information related to the state transition of the multi-function peripheral 101 has been described. However, the generation process of the JSDK application 147 in the multi-function peripheral 101 is not limited to this. For example, a new JSDK application 147 may be generated by causing the user to interactively edit the state transition of the JSDK application 147 detected by the application detection unit 413.

  For example, when the application detection unit 413 detects the presence of the JSDK application 147 recommended for use in the multi-function peripheral 101 using information related to the state transition of the multi-function apparatus 101, the application detection unit 413 displays that fact on the touch panel 311 of the multi-function apparatus 101. In the banner area of the operation screen. In the banner area, a button for displaying information related to the state transition of the detected JSDK application 147 is displayed. When the user presses the button, the application notification unit 415 causes the touch panel 311 to display a screen (hereinafter referred to as “application state transition screen”) that displays information related to the state transition of the JSDK application 147.

  FIG. 16 is a diagram illustrating a display example of the application state transition screen. In FIG. 16, the application state transition screen 500 includes an application name display area 510, an edit button 520, a close button 530, a state transition display area 540, and the like.

  The application name display area 510 is an area in which the application name of the JSDK application 147 (hereinafter referred to as “current application”) that is the display target of information related to state transition is displayed. The state transition display area 540 is an area where information related to the state transition of the current application is displayed. In the state transition display area 540, buttons corresponding to the respective states (hereinafter referred to as “state buttons”) are arranged in the order of state transition. In FIG. 16, the state transition according to the state transition diagram shown in FIG. 8 is displayed. That is, the current application in FIG. 16 corresponds to the JSDK application 147 that can execute the state transition shown in FIG. Note that information related to the state transition to be displayed in the state transition display area 540 is included in the application information and databased.

  When the edit button 520 is pressed on the application state transition screen 500, the application notification unit 415 sets the application state transition screen 500 to the edit mode. At this time, in order to prevent unauthorized editing, user authentication may be performed using a user code or an administrator code.

  FIG. 17 is a diagram illustrating a display example of the application state transition screen in the edit mode. In FIG. 17, the same parts as those in FIG. The application state transition screen 500a in the edit mode is different only in that the edit button 520 is not displayed, but the operation when the state button displayed in the state transition display area 540 is pressed is different. For example, when the scan button 541 corresponding to the scan state is pressed, the application generation unit 414 edits a screen (hereinafter referred to as “state edit screen”) for editing the state corresponding to the selected button. 311 is displayed.

  FIG. 18 is a diagram illustrating a display example of the state editing screen. In FIG. 18, the state edit screen 600 includes a current state name display area 610, a transition addition button 620, a state change button 630, a state edit button 640, a state list display area 650, and the like.

  The current state name display area 610 is an area in which the state name of the state currently being edited (current state) is displayed. The transition addition button 620 is a button for newly adding a transition from the current state. The state change button 630 is a button for replacing a different state with a transition position of the current state instead of the current state. The state edit button 640 is a button for editing the internal state transition of the current state. The state list display area 650 is an area in which a list of states that can be realized in the multi-function peripheral 101, that is, a list of functional modules installed in the multi-function peripheral 101, is displayed. A button is arranged for each state (functional module). Has been. However, for a state that cannot be a transition destination from the current state or a state that cannot be replaced with the current state, the button is grayed out and displayed. Whether or not it can be a transition destination from the current state and whether or not replacement with the current state is possible are performed based on definition information indicating the relationship between the states stored in advance in the HDD 233 or the like. In the definition information, for example, a list of states that can be transition destinations for each state is defined. Therefore, the application generation unit 414 searches the definition information using the current state as a key to determine whether it can be a transition destination from the current state, and determines based on the search result. In addition, whether or not the current state can be replaced is determined based on the search result by searching the definition information using the state of the current state transition source (here, the authentication state) as a key.

  Note that the state displayed in the state list display area 650 is not necessarily limited to the state related to the functional module installed in the multifunction peripheral 101. For example, it may be a function module that is not installed in a medium inserted in the multifunction peripheral 101 or a network connected to the multifunction peripheral 101. In this case, the COLLECTOR 401 automatically collects information related to the functional modules from the HDD 233, the memory card 235, the media, and the network periodically, and manages the information in the HDD 233 or the like as a database.

  In the state editing screen 600, for example, when the transition addition button 620 is pressed and then any button in the state list display area 650 is selected, the application generation unit 414 relates to the button selected from the current state. A screen for setting a state transition condition (hereinafter referred to as a “transition condition setting screen”) is displayed on the touch panel 311.

  FIG. 19 is a diagram illustrating a display example of the transition condition setting screen. In FIG. 19, the transition condition setting screen 700 includes a transition source state name display area 710, a transition destination state name display area 720, a transition event setting area 730, a guard condition setting area 740, an end button 750, and the like.

  The transition source state name display area 710 and the transition destination state name display area 720 are areas in which the state name of the transition source state and the transition destination state, which are edit targets in the transition condition setting screen 700, are displayed. FIG. 19 shows an example in which the print state is selected as the transition destination in the state list display area 650 of FIG. The transition event setting area 730 is an area for setting an event that causes a state transition from the transition source state to the transition destination state. “End” is selected in the figure, which indicates that the transition source state, that is, the transition to the transition destination when the scan state is completed is set. The guard condition setting area 740 is an area for setting a condition that does not cause a state transition, that is, a condition that becomes an obstacle to the state transition. For example, when the state transition is suppressed when a fatal error or the like occurs, “fatal error” may be selected. Since “None” is selected in the figure, this indicates that there is no guard condition from the scan state to the print state.

  When the event and guard conditions are set and the end button 750 is pressed, the application generation unit 414 generates a new JSDK application 147 based on the information related to the state transition after editing, and the application state of the JSDK application 147 The transition screen 500a is displayed.

  FIG. 20 is a diagram illustrating a display example of the application state transition screen in which the editing result is reflected. In FIG. 20, the same parts as those in FIG. In the application state transition screen 500a of FIG. 20, a print button 542 is added below the scan button 541. That is, it is indicated that the print state has been added as the scan state transition destination. This indicates that a transition corresponding to the transition Z ″ in FIG. 10 has been added.

  On the other hand, when the state edit button 640 is pressed on the state edit screen 600 of FIG. 18, the application generation unit 414 is for editing the state transition inside the functional module that executes the current state (scan state in FIG. 18). A screen (hereinafter referred to as “functional module state transition screen”) is displayed.

  FIG. 21 is a diagram illustrating a display example of the functional module state transition screen. In FIG. 21, the functional module state transition screen 810 includes a functional module name display area 811 and a state transition display area 812. The function module name display area 811 is an area in which the function module name of the function module (current function module) to be edited is displayed. The state transition display area 812 is an area where information related to the state transition of the current function module is displayed. In the state transition display area 812, buttons corresponding to each state are arranged in the order of state transition. In FIG. 21, the state transition according to the state transition diagram shown in the scan state 503 of FIG. 8 is displayed.

  Based on the functional module state transition screen 810 of FIG. 21, it is possible to edit the state transition of the functional module in the same manner as the state transition editing of the JSDK application 147 described above. For example, when the condition setting button 8121 is pressed in the state transition display area 812, the application generation unit 414 displays the state editing screen with the condition setting state (ready state) as an editing target.

  FIG. 22 is a diagram illustrating a display example of a state editing screen relating to a state in the functional module. In the state edit screen 820 of FIG. 22, a list of buttons corresponding to each state constituting the current function module is displayed. Here, for example, when the execution button 821 is selected, the application generation unit 414 displays a transition condition setting screen for setting a transition condition when the condition setting state is the transition source and the execution state is the transition destination. .

  FIG. 23 is a diagram illustrating a display example of a transition condition setting screen relating to state transition in the functional module. The operation method of the transition condition setting screen 830 of FIG. 23 is the same as that of the transition condition setting screen 700 of FIG.

  By the way, in the state transition display area 540 of the application state transition screen 500 in FIG. 16 that is not in the edit mode, for example, when the authentication button 543 is pressed, the application generation unit 414 sets detailed information for setting detailed information on the authentication state. Display the setting screen.

  FIG. 24 is a diagram illustrating a display example of the detailed information setting screen. In the detailed information setting screen 900 of FIG. 24, it is possible to select a specific means for executing authentication. In the figure, user code, ID card, key counter, biometric authentication, and the like are displayed as options. Note that items other than the user code are grayed out. This is because a functional module for executing authentication other than the user code is not found.

  As mentioned above, although the Example of this invention was explained in full detail, this invention is not limited to the specific embodiment which concerns, In the range of the summary of this invention described in the claim, various deformation | transformation * It can be changed.

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 401 COLLECTOR
411 Information collection unit 412 Information acquisition unit 413 Application detection unit 414 Application generation unit 415 Application notification unit

JP 2002-84383 A

Claims (8)

An information processing apparatus capable of executing a program,
A collecting means for collecting information relating to the usage status of the information processing apparatus;
Using the information collected by the collection means, obtaining means for obtaining information relating to the state transition of the information processing apparatus;
A detection unit that detects information recommended by the information processing apparatus by collating the information acquired by the acquisition unit with information indicating a state transition related to the function of each program;
An information processing apparatus comprising: display means for displaying information on the program detected by the detection means on a display device. The display means causes the display device to display information indicating a state transition related to the function of the program detected by the detection means,
The information processing apparatus according to claim 1, further comprising a generation unit that receives an input of an update instruction regarding information indicating the displayed state transition, and generates a program that realizes the state transition according to the update instruction.   The said detection means uses the information collected by the said collection means for every user, and detects the program which recommends the use with the said information processing apparatus for every user. Information processing device.   4. The detection unit according to claim 1, wherein the detection unit uses the information acquired by the acquisition unit in units of users to detect a program that recommends use in the information processing apparatus in units of users. The information processing apparatus according to one item. An information processing method executed by an information processing apparatus capable of executing a program,
A collection stage for collecting information on the usage status of the information processing apparatus;
Using the information collected in the collecting step, obtaining information related to the state transition of the information processing apparatus;
A detection step of detecting a program recommended for use in the information processing apparatus by collating the information acquired in the acquisition step with information indicating a state transition related to the function of each program;
An information processing method comprising: a display step of displaying information on the function of the program detected in the detection step on a display device. The display step causes the display device to display information indicating a state transition related to the function of the program detected by the detection step,
6. The information processing method according to claim 5 , further comprising a generation step of receiving an input of an update instruction regarding the information indicating the displayed state transition and generating a program that realizes the state transition according to the update instruction. An information processing program for causing a computer to execute the information processing method according to claim 5 or 6 . A recording medium on which an information processing program for causing a computer to execute the information processing method according to claim 5 or 6 is recorded.

Images