Information processing device, control method thereof, and program

Abstract

To increase the accuracy when recommending and displaying a button.SOLUTION: An image forming apparatus displays an operation screen including a plurality of buttons, and when the image forming apparatus is in a state related to scanning a document and receives a request for displaying the operation screen of the image forming apparatus, displays the operation screen such that a first button, of the plurality of buttons, which has been used in a state for the image forming apparatus to scan the document, is displayed in higher order than a second button in which the number of times it is used in the state for the image forming apparatus to scan the document is smaller than the first button.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present invention relates to an information processing device, a control method therefor, and a program. [Background technology]

[0002] In recent years, it has become common for image forming devices (such as MFPs) installed in offices to have a screen. The screen displays multiple buttons for changing settings. For example, a menu screen displays a list of buttons corresponding to multiple applications (hereafter referred to as "apps") installed on the MFP. By pressing these buttons, the user can call up an app with the default settings, call up an app with specific settings, or execute an app process at the timing of the button press.

[0003] Here, we will refer to the button that calls the app with the initial settings mentioned above as the app button, the button that launches the app with specific settings as the custom button, and the button that executes a process when pressed as the instant execution button.Custom buttons and instant execution buttons can also be registered by the user.

[0004] In this way, many buttons are arranged on the menu screen, and the user has to select the desired button from a large number of buttons, which reduces operability. Therefore, as shown in Patent Document 1, there is a method to make it easier for the user to find the desired button by displaying a recommendation of buttons arranged in order of frequency of use by the user. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Japanese Patent Application Laid-Open No. 2013-145946 Summary of the Invention [Problem to be solved by the invention]

[0006] However, because the buttons desired by users change depending on the situation, even if frequently used buttons are uniformly recommended as in conventional technology, it may not be possible to accurately recommend buttons to users. An object of the present invention is to improve the accuracy of button recommendations to users. [Means for solving the problem]

[0007] An image forming device that displays an operation screen including a plurality of buttons, wherein when the image forming device is in a state related to scanning a document and a display request for the operation screen of the image forming device is received, the image forming device displays the plurality of buttons in such a manner that a first button among the plurality of buttons that has been used in the state in which the image forming device is scanning a document is ranked higher than a second button that has been used less frequently than the first button in the state in which the image forming device is scanning a document. [Effects of the Invention]

[0008] According to the present disclosure, it is possible to improve the accuracy when displaying recommended buttons. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating a configuration of an information processing system according to an embodiment of the present invention. [Figure 2] 1 is a block diagram showing a hardware configuration of an MFP according to an embodiment of the present invention. [Figure 3] FIG. 2 is a block diagram showing the hardware configuration of a file server and a user PC according to the embodiment of the present invention. [Figure 4] FIG. 2 is a block diagram showing the software configuration of the MFP according to the embodiment of the present invention. [Figure 5] 10 is an example of a button information table according to the embodiment of the present invention. [Figure 6-1] 10 is an example of a menu screen according to an embodiment of the present invention. [Figure 6-2] 10 is an example of a menu screen according to an embodiment of the present invention. [Figure 7] FIG. 3 is a sequence diagram showing a series of processing steps of the MFP according to an embodiment of the present invention. [Figure 8] 5 is a flowchart showing the processing of the MFP according to an embodiment of the present invention. [Figure 9] 5 is a flowchart showing the processing of the MFP according to an embodiment of the present invention. [Figure 10] 10 is an example of a utilization point management table according to the present embodiment of the present invention. [Figure 11] FIG. 10 is a flowchart showing a process for updating a utilization point management table according to the present invention. [Figure 12] 10 is a flowchart showing the processing of an MFP in a second embodiment of the present invention. [Figure 13] 10 is an example of a usage point management table in the second exemplary embodiment of the present invention. [Figure 14] 10 is an example of a menu screen according to a second embodiment of the present invention. [Figure 15] 13 is an example of a usage point management table according to the third exemplary embodiment of the present invention. [Figure 16] 10 is a flowchart showing the processing of an MFP according to a third embodiment of the present invention. [Figure 17] 13 is an example of a button information table according to the third embodiment of the present invention. [Figure 18] 10 is an example of a menu screen according to the third embodiment of the present invention. [Figure 19] 10 is a flowchart showing the processing of an MFP in a fourth embodiment of the present invention. [Figure 20] 13 is an example of a usage point management table in the fourth embodiment of the present invention. [Figure 21] 13 is a flowchart showing the processing of an MFP in a fifth embodiment of the present invention. [Figure 22] 10 is an example of an application setting screen according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0010] The best mode for carrying out the present invention will be described below with reference to the drawings. However, the components described in the embodiment are merely examples and are not intended to limit the scope of the present invention.

[0011] (First embodiment) FIG. 1 is a diagram showing an example of the system configuration of an information processing system according to this embodiment. This system is composed of an MFP 101, a file server 102, and a user PC 103, which are connected via a LAN (Local Area Network) 110. The devices on the LAN 110 can communicate with each other. FIG. 1 shows an example of a typical network configuration, and each device may be connected to a WAN (Wide Area Network, not shown) instead of the LAN 110. Furthermore, the number of each device is not limited to one, and the number may be increased or decreased.

[0012] The MFP 101 is an example of an image forming device having scanner and printer functions. The file server 102 is a server having a network folder accessible from the MFP 101 and the user PC 103, and can be a destination of image data scanned by the MFP 101. The user PC 103 is an example of an information processing device, and is not limited to a PC, but may also be a mobile terminal such as a smartphone. The user PC 103 is a PC used by a user to perform work, and can send print data to the MFP 101 using a printer driver or the like through user operation.

[0013] 2 is a block diagram showing the hardware configuration of MFP 101. A control unit 210 including a CPU 211 controls the overall operation of MFP 101. The CPU 211 reads control programs stored in a ROM 212 or HDD 214 and executes various control processes such as reading control and transmission control. A RAM 213 is used as a temporary storage area such as the main memory and work area of ​​the CPU 211. The HDD 214 stores image data and various programs.

[0014] The operation unit I / F 215 connects the operation unit 219 and the control unit 210. The operation unit 219 is equipped with a keyboard, a liquid crystal display that provides an operation screen with a touch panel function, and the like. The printer I / F 216 connects the printer 220 and the control unit 210. Image data to be printed by the printer 220 is transferred from the control unit 210 to the printer 220 via the printer I / F 216, and the printer 220 prints the image on a recording medium. The scanner I / F 217 connects the scanner 221 and the control unit 210. The scanner 221 reads an image on a document, generates image data, and inputs the image data to the control unit 210 via the scanner I / F 217. The network I / F 218 connects the control unit 210 (MFP 101) to the LAN 110. The network I / F 218 transmits and receives various information to and from other devices on the LAN 110.

[0015] FIG. 3 is a block diagram showing the hardware configuration of the file server 102 and the user PC 103. A control unit 310 including a CPU 311 controls the operation of the entire device. The CPU 311 reads control programs stored in a ROM 312 or HDD 314 and executes various control processes. The RAM 313 is used as a temporary storage area such as the CPU 311's main memory or work area. The HDD 314 stores various programs and data. A display unit I / F 315 connects a display unit 318 to the control unit 310. A keyboard I / F 316 connects a keyboard 319 to the control unit 310. The CPU 311 recognizes instructions from the user via the keyboard 319 and transitions the screen displayed on the display unit 318 in accordance with the recognized instructions. A network I / F 317 connects the control unit 310 to the LAN 110. The network I / F 317 transmits and receives various information to and from other devices on the LAN 110.

[0016] 4 is a diagram showing the software configuration of the MFP 101 of this embodiment. The CPU 211 reads out a program stored in the HDD 214 of the MFP 101 into the RAM 213 and executes the program, thereby executing the processing described below.

[0017] The button management unit 401 manages buttons displayed on operation screens, including the menu screen of the MFP 101. The button information table 402 is a table that holds information about buttons displayed on the menu screen of the MFP 101, and is stored in the RAM 213 or the HDD 214. The menu display unit 403 displays a menu screen with buttons arranged on the operation unit 219. The menu display unit 403 displays the menu screen based on the button information held in the button information table 402. The copy application (app) 404 is an application that provides a copy function. The print application 405 is an application that provides a print function. The print application 405 temporarily stores print jobs sent from an external device, such as the PC 103, in response to a user instruction in the HDD 214 rather than printing them immediately upon receipt. The print application 405 has a function to perform print processing by separately receiving instructions from the user on the MFP 101 (hereinafter referred to as "reserved printing"). The transmission application 406 is an application that provides a function to transmit scanned image data. A network folder on the file server 102 can be specified as one of the destinations. A fax application 407 is an application that provides a fax function. The applications 404 to 407 are examples and are not limited to these. Other applications may be installed on the MFP 101. A user authentication unit 409 identifies and authenticates the user who uses the MFP 101.

[0018] Usage point management table 408 manages usage points based on the frequency of use of buttons displayed on the menu screen for each user and for each state of MFP 101. Here, the state of MFP 101 refers to, for example, a state in which MFP 101 holds an unprinted print job (reserved print job), a state in which a document is placed on the scanner of MFP 101, a state in which MFP 101 holds an unprinted print job and a document is placed on the scanner, an initial state (no reserved print job is held and no document is placed on the scanner), etc. The button desired by the user changes depending on such a state of MFP 101. For example, if a document is placed on the scanner of MFP 101, the user is likely to desire an application button related to the process of scanning the document.

[0019] In this embodiment, usage points based on the number of times a button is used are stored for each state of the MFP 101, and buttons with higher usage points in each state are displayed (recommended) at the top of the list. This allows buttons to be recommended to the user more accurately than when buttons are recommended uniformly using only the number of times the button is used without considering the state of the MFP 101. In the following description, the state of the MFP 101 is exemplified by two states: whether or not a document is placed and whether or not there is an unprinted print job, but this is not limiting. For example, the state of the MFP 101 may also be whether or not it holds a received fax document.

[0020] An example of the button information table 402 according to this embodiment is shown in Fig. 5. One button is defined in one line, and in the button information table 500 of Fig. 5, seven buttons are defined in lines 511 to 517 as an example.

[0021] The button information table 402 has four columns, 501 to 504. The button ID 501 column defines an identifier for uniquely identifying a button. The button name 502 column defines a name to be displayed on the button. The call application 503 column defines an application to be called when the user selects the button. The setting value 504 column defines a setting value to be assigned as a parameter when calling the application. A button for which a value is set in the setting value 504 column (for example, row 511) will be referred to as a custom button hereinafter. When the custom button is pressed, the call application 503 is opened with the setting value 504 reflected. A custom button is created, for example, by a user setting a desired setting value and registering it in the MFP 101. On the other hand, a button for which a value for the setting value 504 is not set (for example, row 514) is a button for calling the application in its initial state without assigning a parameter to the application (hereinafter referred to as an application button). These buttons may immediately execute a process when pressed if they are in a state where they can execute a process. The "Send to me" button with button ID B001 is a button for sending a scanned document to one's own PC, etc. The "Print all" button with B006 is a button for batch printing of multiple print jobs sent by the user that are stored in the MFP 101. The information contained in the button information table is not limited to the above and may include other information. If different button information is to be stored for each user, user information may be included, or information indicating an expiration date may be included in the button. In this case, a column may be added to the button information table 402 so that the necessary information can be managed for each button.

[0022] 6-1 and 6-2 show an example of a menu screen of the MFP 101 according to this embodiment.

[0023] Screens 610 and 611 show an outline of the menu screen. When the user authentication unit 409 is able to identify the user of the MFP 101 through login processing or the like, the identified user name is displayed in a user name display area 601. In this embodiment, the menu screen has a two-page configuration, with the first page being screen 610 and the second page being screen 611. To move between pages, the user operates a page scroll bar 602. Button display areas 603-609 are areas in which application buttons or custom buttons with increasing priority are displayed in order from 1, with the button with the highest display priority being displayed in button area 601, and the button with the second highest display priority being displayed in button area 604, in that order.

[0024] The button display priority information will be described using FIG. 10. FIG. 10 shows the usage point management table 408 according to this embodiment, which is used to manage usage points based on the user's button usage history in each state of the MFP 101. Usage points are points that are incremented each time a button is pressed or used and are updated according to a predetermined rule. The higher the usage points, the higher the display priority of the button displayed on the menu screen. Hereinafter, an example will be shown in which there are usage point management tables 408 for each user, and management is performed for each user. However, the usage history of all users may be managed collectively in a single table. The following description will use usage point management tables 1000, 1100, and 1200 as specific examples. (j=0), (j=500), and (j=501) in each table indicate the number of times a job has been executed. Management table 1000 (j=0) is the initial management table in which no job has been executed, and default usage points are set. Management table 1100 (j=500) is the management table in which 500 jobs have been executed.

[0025] The table will be described in detail using management table 1000. Columns STATUS 1001, ORIGINAL PRESENTED 1002, and UNPRINTED 1003 indicate the status of the MFP 101. A "0" in column 1002 indicates that no originals are placed on the MFP 101, and a "1" indicates that an original is placed on the MFP 101. Similarly, a "0" in column 1003 indicates that the MFP 101 does not hold an unprinted print job, and a "1" indicates that it holds a print job. Based on these states, the status of the MFP 101 is defined in column STATUS 1001. For example, as in row 1033, if "no originals placed" and "no unprinted print jobs held" are specified, status s = S00 is defined.

[0026] The columns for buttons 1004-1010 show information about each button, along with usage points based on the number of uses associated with each state. Here, the buttons defined in the button information table of FIG. 5 are shown. When a button is pressed or executed, a predetermined value is added to the usage points for that button in the state of the MFP 101 at the time the button was used. Since the management table 1000 is in its initial state, default usage points are shown. The default usage points may be preset at the time of shipment from the factory, set by the MFP 101 administrator, or set by the user. Buttons with higher usage points, i.e., buttons used more frequently, have a higher display priority. For example, if the MFP 101 state is "Document Loaded" and "No Unprinted Print Jobs Held" (s=S10), buttons that perform scanning operations, such as the "Send to Me" and "Copy Single-Sided Black and White," have a higher default usage point. Since the user has placed a document on the scanner, it is highly likely that the user will desire buttons that perform scanning operations, so these buttons have a higher display priority. In this way, the display priority of the buttons changes depending on the state of the MFP 101, and when the state of the MFP 101 changes, the order of the buttons displayed on the menu screen also changes.

[0027] Using management table 1100 when 500 jobs have been executed as an example, the button display priority when the state of MFP 101 is "original document loaded" and "no unprinted print jobs" (s=S10) will be described. In this case, the button display priority is determined in descending order of usage points, such as "single-sided black and white copy," "send to self," and "copy," and the buttons are arranged in this order from left to right on the menu screen. In this way, the state of MFP 101 manages which buttons are used most frequently, and the buttons are displayed based on this information, allowing for accurate button recommendations to be made to the user.

[0028] Returning to the explanation of FIG. 6, specific examples of menu screens displayed based on the usage point management table 408 are shown. Screens 620 and 621 are menu screens displayed when the MFP 101 status is "no document loaded" and "no unprinted print jobs held" (s=S00) based on the management table 1000 (j=0). Screens 630 and 631 represent menu screens displayed when the status is s=S01 based on the management table 1000 (j=0). Screens 640 and 641 represent examples of menu screens displayed when the status is s=S00 based on the management table 1100 (j=500). The MFP status is the same, but the order of the buttons is different from screens 620 and 621, with the frequently used "Copy" button displayed at the top. Screens 650 and 651 represent examples of menu screens displayed when the status is s=S10 based on the management table 1100 (j=500). Screens 660 and 661 show examples of menu screens that are displayed when the status is s=S10 based on the management table 1200 (j=501). The buttons on the menu screen shown in FIG. 6 correspond to six buttons among buttons 511 to 517 defined in the button information table 402 of FIG. 5. As defined in the button information table 402, buttons 511, 512, 513, and 516 are custom buttons, and buttons 514, 515, and 517 are application buttons. The custom buttons and application buttons are visually differentiated, for example, by displaying or not displaying setting values, to make them easier to distinguish. The visual difference is not limited to this, and the button shape or color may also be changed to make them more distinguishable. In this embodiment, the application buttons display an icon and application name indicating the application, and the custom buttons display an icon and button name indicating the application to be executed, as well as a summary of setting values.

[0029] In this embodiment, a button is used as a component for calling an application, but other components may also be used. For example, a list may be used for display. In this case, the highest priority item is displayed from the top, and items with lower priorities are displayed one level below.

[0030] 22 is an example of a setting screen for an application that is called when the user presses button 512 on the menu screen. Since the calling application 503 of button 512 is defined as "copy application 404," the called application is copy application 404. Also, FIG. 22 shows a state in which the setting value defined in the setting value column 504 of button 512 has been set.

[0031] Label 2001 displays the name of the called application. Areas 2002 to 2006 display the current setting values ​​of copy application 404. Since the setting values ​​defined in the setting value 504 column of button 512 are "1 copy," "black and white," and "double-sided," "1 copy" is set and displayed in area 2005, "black and white" in area 2002, and "double-sided" in area 2006. Default values ​​are displayed for setting values ​​not defined in the setting value 504 column (areas 2003 and 2004).

[0032] In areas 2002 to 2006, if the setting value has been changed from the default value, the frame indicating the area is represented by a double line, making it possible to distinguish it from areas where the default value is set. In FIG. 40, area 2002 (the default value for color selection is "color") and area 2006 (the default value for scanning is "single-sided") have setting values ​​that are different from the default values, so they are represented by a double-line frame. Note that although "1 copy" is set in the setting value 504 column of button 512, the default value for the number of copies is "1 copy," which is the same as the default value, and therefore area 2005 is represented by a single line. Here, the number of border lines around the buttons makes it possible to distinguish them, but the color or shape of the buttons may also make it possible to distinguish them.

[0033] When each of the areas 2002 to 2006 is pressed, a dialog box for changing the corresponding setting value is displayed.

[0034] A reset button 2007 is a button for resetting each setting value to the default value, and a button 2008 is a button for starting a job with the currently set setting values.

[0035] 7 is a sequence diagram showing the flow of a series of processes in this embodiment. It shows an example of processes from registering a button, displaying a menu screen (button), and calling an app by pressing a button. The CPU 211 loads a program stored in the HDD 214 of the MFP 101 into the RAM 213 and executes it, thereby executing the process of the sequence in FIG. 7 and each step of a flowchart described later.

[0036] First, in step S701, each application (404 to 407) issues a button registration instruction to the button management unit 401 in advance. The timing for registering the button may be any timing before the menu screen is displayed, such as when the MFP 101 is started or when the application is started. The button registration instruction includes the registration of information in each column of the button information table 402 (button name, called application, setting value).

[0037] In step S 702 , upon receiving the button registration instruction, the button management unit 401 stores the received button information in the button information table 402 .

[0038] In step S703, menu display unit 403 receives an instruction to display a menu screen from the user. In step S704, menu display unit 403 requests button management unit 401 to acquire button information. At this time, if a user is logged in to MFP 101, button information associated with the logged-in user is acquired. In step S705, button management unit 401 returns the button information to menu display unit 403 as a response to step S704. In step S706, menu display unit 403 displays a menu screen on operation unit 219 based on the button information received in step S705.

[0039] In step S707, menu display unit 403 receives an operation (button press) performed by the user. In step S708, menu display unit 403 determines the application to be called and parameters to be assigned when the application is called, based on the user operation received in step S707. In step S709, the menu display unit calls the application in accordance with the determination made in step S708. In step S710, the called application performs processing in accordance with the parameters assigned when the application is called.

[0040] 8 is a flowchart for explaining the processing of MFP 101 in this embodiment. The processing is described from receiving a menu screen display request from a user to displaying the menu screen on operation unit 219. The flowchart in FIG. 8 corresponds to the processing of steps S703 to S706 in the sequence diagram in FIG. 7.

[0041] In step S801, the menu display unit 403 receives a request to display a menu screen. A request to display a menu screen may be, for example, a user logging in to the MFP 101, a user pressing a button to display a menu screen, or a system notification (for example, displaying the menu screen when there is no user operation for a certain period of time). Next, in step S802, the menu display unit 403 acquires the status of the MFP 101. A usage order list is created by referring to the acquired status of the MFP 101 and the usage point management table 408 shown in FIG. 10. The usage order list is a list in which button IDs are arranged in descending order of usage points.

[0042] For example, let us take the case where a job has been executed 500 times (j=500) and the usage point management table is 1100 in Fig. 10. If the acquired status of MFP 101 is s=S10, row 1041 is referenced and the buttons with the highest usage points are sorted in descending order. The usage order list created here is as follows: Usage order list = {B002,B001,B005,B003,B004,B006,B007}

[0043] The menu display unit 403 acquires the button ID (B002 in this example) with the maximum usage points from the created usage order list.

[0044] Next, in step S803, the menu display unit 403 obtains the information of the button ID obtained in step S802 from the button information table 402. In this example, the button information of the button ID=B002 is obtained from the button information table 402.

[0045] Next, in step S804, the display unit 403 displays the information of the acquired button ID=B002. As a result, the custom button 512 "Make a single-sided black and white copy" is displayed in the first position on the menu screen (button display area 603 in FIG. 6), as shown by 650 in FIG. 6.

[0046] Next, in S805, the display unit 403 checks whether all the information on the button IDs included in the usage order list acquired in step S802 has been acquired. If all the information has been acquired, the process ends, and if all the information has not been acquired, the process proceeds to S806. In this case, only the information on the button ID=B002 has been acquired, so the process proceeds to S806.

[0047] In S806, the display unit 403 acquires the button ID B001 with the next highest usage points. The display unit 403 executes step S803 again, this time acquiring button information for button ID=B001 from the button information table 402. Then, in S804, the display unit 403 displays the acquired information for button ID=B001. As a result, as shown by 650 in FIG. 6, the custom button 511 "Send to me" is displayed in the second position on the menu screen (button display area 604 in FIG. 6). In a similar manner, button IDs are acquired sequentially from the usage order list, and the buttons are displayed in button display areas 605, 606, and 607 in FIG. 6, in turn. After displaying all buttons up to button ID=B007, in step S805 the display unit 403 determines that the entire usage order list has been read, and terminates the process. Through the above flow, a screen such as the menu screen shown in FIG. 6 is displayed. Here, the usage points function directly as priority information, but a configuration in which the display priority is calculated separately using the usage points may also be used.

[0048] Fig. 9 is a flowchart for explaining the processing of the MFP 101 in this embodiment. This explains the processing of detecting a user operation on the menu screen displayed in the flowchart of Fig. 8 and calling an application in response to the user operation. The flowchart of Fig. 9 corresponds to the processing of steps S707 to S710 in the sequence diagram of Fig. 7.

[0049] In step S901, the menu display unit 403 detects a user operation on the menu screen. In step S902, the menu display unit 403 determines whether the user operation detected in step S901 is a button press. If the menu display unit 403 determines that the user operation is a button press, it proceeds to step S903; otherwise, it terminates the processing. In the following description, the button pressed by the user in step S901 will be referred to as the "pressed button."

[0050] In step S903, the menu display unit 403 uniquely identifies the button from the button ID 501 linked to the pressed button, and acquires the button information from the button information table 402. In the following description, when the term "button information" is simply used, it refers to the button information acquired in step S903.

[0051] In step S904, the menu display unit 403 determines whether the push button is a custom button. The determination of whether the button is a custom button is made based on whether a value is defined in the setting value column 504. If the push button is a custom button, the menu display unit 403 proceeds to step S906, and if not, proceeds to step S905.

[0052] In step S905, the menu display unit 403 calls the application corresponding to the pressed button without assigning any parameters. The application to be called is the application defined in the called application column 503 of the button information. The menu display unit 403 then proceeds to step S909. The processing of step S909 will be described later.

[0053] In step S906, the menu display unit 403 determines which area of ​​the button the user pressed in step S901. As an example of the determination, an explanation will be given using button 511 in Fig. 6. If the area pressed by the user is the "setting area" (i.e., the summary display area), the menu display unit 403 proceeds to step S907, and if the area pressed by the user is the "execution area" (i.e., other than the "setting area"), the menu display unit 403 proceeds to step S908.

[0054] In step S907, the menu display unit 403 assigns parameters to the application corresponding to the pressed button and calls it. The application to be called is the application defined in the called application column 503 of the button information. The assigned parameters are the setting value defined in the setting value column 504 of the button information and an instruction to display the setting screen without executing the job when called (execution flag OFF). Thereafter, the menu display unit 403 proceeds to step S909.

[0055] In step S908, the menu display unit 403 assigns parameters to the application corresponding to the pressed button and calls it. The application to be called is the application defined in the called application 503 column of the button information. The assigned parameters are the setting value defined in the setting value 504 column of the button information and an instruction to start execution of the job when called (execution flag ON). Thereafter, the menu display unit 403 proceeds to step S909.

[0056] In step S909, the called application performs processing according to the parameters assigned when it was called. For example, if no parameters are assigned, the application is displayed in its initial state. In other words, a screen with the application's default settings is displayed. The application's default settings can be set by an authorized user, such as an administrator. Furthermore, if a setting value and an execution flag set to OFF are assigned to the parameters, the application displays a settings screen that reflects the setting values. If a setting value and an execution flag set to ON are assigned to the parameters, the application begins executing the job with the passed setting values. In this way, a custom button can be switched between immediately executing processing or opening a settings screen depending on the area that is pressed.

[0057] 11 is a flowchart of the update process for the usage point management table according to this embodiment. A specific example will be given assuming that a user has executed a job 500 times (j=500), the usage point management table is 1011, the device status (s) is "original placed," "no unprinted print jobs held" (S10), and the button with button ID=B001 is pressed. j=500 is an example, and this process is performed regardless of the number of executions, such as j=0, 501, etc.

[0058] In step S1101, when it is detected that a button has been pressed or executed, the button management unit 401 acquires the device state (s)=S10 when the button was pressed and the pressed button ID (b)=B001. Next, in step S1102, it acquires from the usage point management table 408 the usage points (here, management table 1100 is referenced and the usage points=77) for the button ID (b)=B001 corresponding to the device state (s)=S10.

[0059] In step S1103, the usage point management table 408 adds an additional value of 10 to the acquired usage points, updating them to (s)=S10 and usage points=87 for button ID (b)=B001. The usage point management table is now updated to the state (j=501) shown in 1200. With this update, the buttons are rearranged from the menu screens shown by screens 650 and 651 in FIG. 6 to the menu screens shown by screens 660 and 661. As the "Send to self" button, which was displayed second on screen 650, was used, its usage points exceeded those of the "Make single-sided black and white copy" button, which was displayed first, and so the display order of the two buttons on screen 660 has been swapped.

[0060] According to the above embodiment, the number of times a button is used is stored for each state of the MFP, and the buttons that are used most frequently in the detected state of the MFP can be displayed at the top of the list. In other words, the system stores which buttons are frequently used when a user performs certain operations on the MFP, and displays recommended buttons based on this information, allowing for more accurate recommendations than recommendations made uniformly based only on the number of times a button is used.

[0061] (Second embodiment) In the first embodiment, buttons with the highest usage counts in the state of the MFP 101 were displayed with uniform priority based on the usage point management table 408. In this embodiment, instead of uniformly displaying buttons with the highest usage counts, a specific button is displayed with priority regardless of the number of times the button has been used in a specific state of the MFP 101. For example, when the MFP 101 is holding an unprinted print job, buttons for executing the print job are displayed with priority regardless of the number of times the button has been used. This makes it possible to alert the user to the existence of an unprinted print job. In this embodiment, a specific example will be described in which, when the MFP 101 is holding an unprinted print job and no original document is placed (S01), the application button 517 "Print" and the custom button 516 "Print All," which are buttons for executing the print job, are always displayed with the highest priority regardless of their frequency of use. The usage point management table of this embodiment is shown in FIG. 13 (j=1000). The basic configuration of this embodiment is the same as that of the first embodiment, so only the differences will be shown.

[0062] 12 is a flowchart for explaining the processing of the MFP 101 in this embodiment. The processing is described from receiving a menu screen display request from the user to displaying the menu screen on the operation unit 219. Note that this flowchart has the same basic configuration as the flowchart in FIG. 8, so only the differences are shown.

[0063] In step S802, the menu display unit 403 acquires the device status and creates a usage order list. In this case, the device status is s=S01, so the usage order list is created by referencing row 1314 of the usage point management table 1300. Specifically, the usage order list is as follows: Usage order list = {B002,B001,B006,B007,B005,B003,B004}

[0064] The menu display unit 403 obtains the usage order list acquired in step S802 and the button ID=B002 with the maximum usage points, and then proceeds to step S1201.

[0065] In step S1201, the menu display unit 403 determines whether the state (s) acquired in S802 is S01. If it is not S01, the process proceeds to step S803. If the menu display unit 403 determines in step S1201 that the state (s) is S01, the process proceeds to step S1202.

[0066] In S1202, the usage order list is corrected so that the print job execution buttons, application button 517 "Print" and custom button 516 "Print All," are displayed with the highest priority. Specifically, the application button 517 "Print" with button ID = B007 and the custom button 516 "Print All" with button ID = B006 are moved to the top of the usage order list and corrected as follows. Usage order list = {B006,B007,B002,B001,B005,B003,B004}

[0067] Then, the button ID of B006, which is displayed first in the list, is obtained, and the process proceeds to S803.

[0068] According to the above flowchart, a menu screen is displayed in which the button for executing a print job is displayed with priority, as shown in Fig. 14. In this way, when the MFP is in a specific state, buttons are not displayed with priority uniformly based on the button usage history, but a specific button can be displayed with priority regardless of frequency of use. In this way, the user can be notified that the MFP is in a specific state.

[0069] (Third embodiment) If priority display is performed based on the number of times used, as in the first embodiment, a newly registered button will not be displayed with priority because its number of times used is 0. In this example, a newly registered button is displayed with priority even if its number of times used is low. The basic configuration of this embodiment is the same as that of the first embodiment, so only the differences are shown. Figure 16 is a flowchart showing the button registration process in this embodiment.

[0070] The following description will be given taking as an example a case where the user newly registers a [Store Estimate Report] button. For the purpose of the description, the button information table 402 is shown in FIG. 5, and the usage point management table is shown in FIG. 15 (j=1000).

[0071] When the user registers the [Store quotation report] button, the button registration flow shown in FIG. 16 begins. First, in step S1601, the maximum button ID (bmax) = B007 is obtained from the button information table 402 in FIG. 5. Next, in step S1602, a button ID (= B008) is created that is the obtained bmax (B007) + 1. The button ID (= B008) created in S1602 is assigned to the [Store quotation report] button to be registered. The button information table 402 at this point is shown in FIG. 17. As shown in row 1718, the [Store quotation report] button with button ID B008 has been registered.

[0072] Finally, in step S1603, the [Store Estimate Report] button is registered in usage point management table 408. At this time, the maximum usage points for each state are set to button ID=B008. Specifically, when state (s)=S00, point 263 for button ID (b)=B005 is the maximum usage point, so usage point 263 is set for ID=B008. Similarly, when state (s)=S01, point 2534 for button ID (b)=B002 is set. When state (s)=S10, point 87 for button ID (b)=B001 is set. When state (s)=S11, point 404 for button ID (b)=B002 is set. The point management table after the settings are completed is shown in FIG. 15. The newly registered button is indicated by 1504, and its usage points for each state are the maximum among the other buttons. In other words, immediately after registering a new button, the registered button is displayed with the highest priority, regardless of the state of MFP 101.

[0073] An example of displaying buttons using the point management table of Fig. 15 is shown in Fig. 18. For example, if an original is placed and there are no unprinted print jobs (s=S10), the menu screens shown at 1800 and 1801 in Fig. 18 are displayed. If s=00, the screens shown at 1820 and 1821 in Fig. 18 are displayed. In either case, the newly registered button is displayed at the top.

[0074] In this embodiment, an example is shown in which buttons registered by the user are displayed preferentially, but this is not limited to this, and buttons automatically generated by the device or buttons registered by the system administrator may also be displayed preferentially in the same way.

[0075] (Fourth embodiment) In this embodiment, an embodiment will be described in which the sum of the utilization points for each state (s) in the utilization point management table 408 (hereinafter referred to as Psum(s)) is corrected to be constant.

[0076] The basic configuration of this embodiment is the same as that of the first embodiment, so only the differences will be described. Fig. 19 is a flowchart showing the update process of the utilization point management table, and the basic configuration is the same as that of Fig. 11, so only the differences will be described.

[0077] Here, as an example, a correction will be described in which Psum(s) is corrected so as not to exceed PsumMAX (=100).

[0078] A specific explanation will be given assuming that the job has been executed 500 times, the usage point management table is 2000 (j=500 normalized by 100) as shown in Figure 20, the device state (s) is that a document is placed and there are no unprinted print jobs (S10), and button ID=B001 is pressed.

[0079] In step S1102, the button management unit 401 obtains from the usage point management table 2000 usage points of 35 for the button ID (b) = B001 corresponding to the device status (s) = S10.

[0080] In step S1103, the button management unit 401 adds an additional value of 10 to the acquired usage points, updating the usage points in the usage point management table for button ID (b) = B001 in device status (s) = S10 to 45. The usage point management table now becomes 2100 (j = 501 before normalized by 100).

[0081] Next, in step S1901, the usage point management table 408 determines that the total value of usage points for each button in device state (s) = S10, Psum(S10) = 106, is greater than PsumMax (= 100), and proceeds to the next step S1902. Here, if the usage point management table 408 determines in step S1901 that Psum(s) is not greater than PsumMax, no correction is made and processing ends.

[0082] In step S1902, the usage point management table 408 corrects the usage points of each button for the device state (s)=S10 to the following values.

[0083]

number

[0084] For example, if we take the button ID = B001 that was pressed this time, it will look like this: p(S10,B001)=[45x100 / 106]=[42.425…]=42

[0085] Similarly, taking the example of button ID=B002, which has not been pressed this time, the result will be as follows. p(S10,B002)=[39x100 / 106]=[36.792…]=36

[0086] As a result, the usage point management table finally becomes 2200 (j=501 after normalized by 100) shown in FIG. 20, and Psum(S10)=97, which is less than PsumMAX.

[0087] When the menu is displayed based on this update of usage points, the screen display changes from 650, 651 (j=500, s=S10) in FIG. 6 to 660, 661 (j=501, s=S10) according to the flow described above in FIG. 8, and custom button 511 and custom button 512 are swapped as in the first embodiment.

[0088] In this embodiment, the correction to maintain this sum Psum(s) at a certain value or less has the effect of preventing buttons that were used frequently in the past but have recently been used less frequently from being displayed preferentially. In other words, usage points can be set with more emphasis on the recent frequency of button use than the past frequency of button use.

[0089] As mentioned above, the usage points for each button are adjusted to the following values:

[0090]

number

[0091] Since the above correction is performed only when Psum(s10) is greater than PsumMAX, the following inequality holds:

[0092]

number

[0093] Each time a button is pressed, the usage points for that button are multiplied by a number less than 1, so even if a button has been used frequently in the past and has had a high usage point count, the usage points will automatically decrease as the frequency of use decreases. Also, by keeping the Psum value below a certain value, data capacity can be saved compared to when usage points are added without limit.

[0094] As described above, it is possible to reduce the influence of button sorting based on the number of past button uses and weight the button sorting based on the most recent number of uses. This allows for highly accurate recommendations. The method of reducing the influence of button sorting based on the number of past button uses is not limited to the method described above; it is also possible to multiply the usage points of each button by a predetermined constant less than or equal to 1 each time the button is used.

[0095] (Fifth embodiment) When buttons are rearranged based on the state of the MFP 101 and the history of button usage, as in the first embodiment, it is annoying for a user who remembers the button locations to have the order of the buttons changed arbitrarily. Therefore, in this embodiment, even when buttons are rearranged based on the usage history, an example is shown in which buttons are not rearranged within the same page.

[0096] For example, in the case of the usage point management table 1200 of the first embodiment, if the state of the MFP 101 is s=S10, the difference in usage points between the [Send to self] button and the [One-sided black and white copy] button is within the sum value (10), so if the two buttons are used alternately, the two buttons will be swapped each time, which is cumbersome for the user.

[0097] In this embodiment, a usage order list before the addition of usage points is stored, and this is compared with the usage order list after the addition of usage points, and the usage order list is updated only when a rearrangement across pages occurs. The basic configuration of this embodiment is the same as that of the first embodiment, so only the differences will be shown.

[0098] FIG. 21 is a flowchart showing the button display process in this embodiment, and since the basic configuration is the same as the flowchart in FIG. 8, only the differences are shown.

[0099] The following description will be given assuming that the usage point management table is 1200 (j=501) in FIG. 10 and the state of the MFP 101 is s=S10.

[0100] In S802, a state usage order list is acquired. Specifically, the state usage order list to be acquired is as follows: In this embodiment, a maximum of four buttons can be displayed on one page of the menu screen, so page groups of four buttons are separated by [ ]. Created usage order list = {[B001,B002,B005,B003],[B004,B006,B007]}

[0101] In step S2101, the menu display unit 403 determines whether there are any buttons that span pages in the retained usage order list (S10) and the created usage order list. The retained usage order list is, for example, the usage order list acquired last time (j=500), and in this case, it is the usage order list created based on the management table 1100 (s=S10) in Figure 10. The usage order list (S10) held is {[B002, B001, B005, B003], [B004, B006, B007]]

[0102] The held usage order list may be a list of buttons currently displayed on the menu screen in the order of display.

[0103] If the menu display unit 403 determines that there are no changes that span across pages, it advances the process to step S2102. If there are changes that span across pages, it advances to S803. Here, there are no changes that span across pages, so it advances to S2102.

[0104] In step S2102, the created usage order list is overwritten with the stored usage order list. Created usage order list (S10) = {[B002, B001, B005, B003], [B004, B006, B007]] When buttons are displayed based on this usage order list, the buttons are not rearranged before or after they are used. In other words, buttons are not rearranged within the same page, and buttons can only be rearranged when a rearrangement of buttons across pages occurs.

[0105] (Other embodiments) In the above embodiment, the display order of buttons is determined based on usage points. However, this is not limiting, and the display format of buttons may also be determined based on usage points. For example, a configuration may be adopted in which the button with the highest usage points in a certain state of the MFP is displayed largest on the menu screen, and the button with the second highest usage points is displayed second largest on the menu screen. This allows buttons that users frequently use to be displayed large, making it easier for users to find the desired button. The display format of buttons is not limited to size; button shape and color may also be changed, and animation may be added to prioritize display. Furthermore, after changing the display format, priority display may also be applied to prioritize buttons so that they are displayed higher.

[0106] The present invention can also be realized by executing the following process: That is, software (programs) that realize the functions of the above-described embodiments are supplied to a system or device via a network or various storage media, and a computer (or CPU, MPU, etc.) of the system or device reads and executes the program code; or, Alternatively, hardware (ASIC or FPGA) that realizes the functions of the above-described embodiments is installed in the device and executed.

Claims

1. An image forming apparatus that displays an operation screen on which multiple buttons including a button for executing a copy function and a button for executing a scan function can be displayed, When the image forming apparatus is in a state related to scanning a document and a display request for the operation screen of the image forming apparatus is received, a first button among the plurality of buttons that has been used in a state in which the image forming apparatus is scanning a document is displayed in a higher order than a second button that has been used less frequently than the first button in a state in which the image forming apparatus is scanning a document. An image forming apparatus characterized by:

2. The state in which the image forming apparatus is in a state where it can scan a document is determined by the scanner of the image forming apparatus. The original is placed on The image forming apparatus according to claim 1 .

3. The plurality of buttons are used when a document is placed on the scanner of the image forming apparatus. Remember the number of times each item has been used 3. The image forming apparatus according to claim 1, wherein the image forming apparatus is a recording medium.

4. The plurality of buttons are used when a document is placed on the scanner of the image forming apparatus. The number of times each of the images is used is stored in association with the user information currently logged in to the image forming apparatus.

4. The image forming apparatus according to claim 1, wherein the image forming apparatus is a recording medium.

5. The image forming apparatus has a job that is not being printed, and When a display request for the operation screen of the device is received, a button for printing the job is pressed. The number of times the image forming apparatus has been used in a state for scanning a document is equal to or greater than the first number. Even if there are fewer buttons than the first button, the first button is placed in a higher order than the first button. Shows a button to print the job 5. The image forming apparatus according to claim 1, wherein the image forming apparatus is a recording medium.

6. When a new button is registered on the operation screen, the new button is The number of times the forming device has been used in a state for scanning documents is less than the first button. If there is no such button, the new button is selected so that it is ranked higher than the first button. Display 6. The image forming apparatus according to claim 1, wherein the image forming apparatus is a recording medium.

7. The image forming apparatus is in a state related to scanning an original, and the image forming apparatus When a display request for the operation screen of the device is received, the second button is displayed in the form of an image. The number of times that the generating device has been used in a state for scanning documents is less than the first button. Even if the first button and the second button are not displayed on the same page, , the order of the first button and the second button is not changed.

7. The image forming apparatus according to claim 1, wherein the image forming apparatus is a recording medium.

8. An image forming apparatus that displays an operation screen on which a plurality of buttons including a button for executing a copy function and a button for executing a scan function can be displayed, The image forming apparatus has a job that is not being printed, and When a display request for the operation screen of the image forming apparatus is received, if the image forming apparatus is not printing, The first button used in a state where the image forming device has a job that is not being printed A second button that has been used less times than the first button while having a job is selected. are also displayed in the top order. An image forming apparatus characterized by:

9. the plurality of buttons used when the image forming apparatus has a job that is not being printed; Remember the number of times each has been used 9. The image forming apparatus according to claim 8,

10. the plurality of buttons used when the image forming apparatus has a job that is not being printed; The number of times each of the above has been used is stored in association with the user information currently logged in to the image forming apparatus. R 10. The image forming apparatus according to claim 8, wherein the image forming apparatus is a recording medium.

11. When a new button is registered on the operation screen, the new button is The number of times the forming device has been used with a job not printing is determined by the first button. Even if the number of buttons is less than the number of buttons, the new button is assigned a higher rank than the first button. Show Tan 11. The image forming apparatus according to claim 8, wherein the image forming apparatus is a recording medium.

12. The image forming apparatus has a job that is not being printed, and When a display request for the operation screen of the image forming apparatus is received, the second button is The device has been used with unprinted jobs less than the first button. Even if the first button and the second button are not displayed on the same page, In this case, the order of the first button and the second button is not changed.

12. The image forming apparatus according to claim 8, wherein the image forming apparatus is a recording medium.

13. An image forming apparatus that displays an operation screen on which a plurality of buttons including a button for executing a copy function and a button for executing a scan function can be displayed, The image forming device is in a state related to scanning an original and is not printing. a state in which there is a job to be performed and a display request is made to the operation screen of the image forming apparatus; If accepted, the image forming device is in a state related to scanning a document, and The first button used with a job not being printed causes the image forming device to Used in situations involving scanning documents and having jobs that are not printing. The second button, which has been used less times than the first button, is placed in a higher order than the second button. Display on An image forming apparatus characterized by:

14. A control method for an image forming apparatus that displays an operation screen capable of displaying a plurality of buttons including a button for executing a copy function and a button for executing a scan function, comprising: The image forming apparatus is in a state related to scanning an original, and the image forming apparatus When a display request for the operation screen of the device is received, the image of the plurality of buttons is displayed. The first button used in the state where the image forming device is scanning the document is The number of times that the device has been used to scan a document is less than the number of times that the first button has been used. Display it so that it is ranked higher than button 2. A control method comprising:

15. For causing a computer to function as each of the means according to any one of claims 1 to 13 program.

Images