Image processing device and method for displaying history information

Abstract

To provide an image processing device and the like capable of improving convenience for a user who operates the image processing device by preferentially displaying setting history associated with the recognized user on the basis of the recognition result of the user located near the image processing device.SOLUTION: An image processing device includes a job execution unit that executes a job related to image processing, a storage unit capable of storing history information related to execution of a job in association with a user executing the job, a display unit capable of displaying history information, a recognition unit that recognizes the execution user, and a control unit, and when the recognition unit recognizes the execution user before authentication of the execution user, the control unit preferentially displays the history information associated with the recognized execution user on the display unit.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present disclosure relates to an image processing device and the like. [Background technology]

[0002] 2. Description of the Related Art Some image processing devices, such as multifunction peripherals, store setting values ​​related to jobs executed in each mode, such as copy mode, fax mode, and scan mode, as history information.

[0003] Attempts are being made to make it easier to call up setting history on a per-user basis and to execute jobs using re-used setting history by storing user identification information (e.g., user name, user ID, etc.) in association with history information (hereinafter referred to as setting history in this disclosure) that stores setting values ​​related to job execution.

[0004] For example, Patent Document 1 discloses that when a logged-in user authenticated by an image forming apparatus performs an operation to display the setting history, only the setting history corresponding to the logged-in user is displayed. [Prior art documents] [Patent documents]

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

[0006] The technology disclosed in Patent Document 1 is configured to display only the setting history corresponding to the logged-in user who has been authenticated by the image forming device, thereby preventing unauthorized use by other users and the leakage of personal information such as destination information to the outside.

[0007] However, with the technology disclosed in Patent Document 1, it is not possible to give priority to displaying the setting history associated with a user until the user is authenticated as a logged-in user. In this case, a user who is located near an image forming device in order to operate the image forming device must log in to the image forming device and then search for and display the setting history associated with the user, which is not very convenient for the user.

[0008] The present disclosure aims to provide an image processing device, etc., that can improve the convenience of a user operating the image processing device by preferentially displaying setting history associated with a recognized user based on the recognition result of the user located near the image processing device. [Means for solving the problem]

[0009] In order to solve the above problem, the image processing device of the present disclosure includes a job execution unit that executes a job related to image processing, a memory unit that can store history information related to the execution of the job in association with the executing user of the job, a display unit that can display the history information, a recognition unit that recognizes the executing user, and a control unit, and is characterized in that when the recognition unit recognizes the executing user before authenticating the executing user, the control unit displays the history information associated with the recognized executing user on the display unit as a priority.

[0010] Furthermore, the method for displaying history information according to the present disclosure is characterized by comprising a job execution step of executing a job related to image processing, a storage step of storing history information related to the execution of the job in association with the executing user of the job, a display step of displaying the history information, a recognition step of recognizing the executing user, and a control step of, if the executing user is recognized in the recognition step before authentication of the executing user, preferentially displaying the history information associated with the recognized executing user. [Effects of the Invention]

[0011] According to the present disclosure, the convenience of a user operating an image processing device can be improved by preferentially displaying the setting history associated with the recognized user based on the recognition result of the user located near the image processing device. [Brief explanation of the drawings]

[0012] [Figure 1] 1 is an external perspective view of a multifunction peripheral according to a first embodiment; [Figure 2] FIG. 2 is a functional configuration diagram of the multifunction peripheral according to the first embodiment. [Figure 3] FIG. 2 is a diagram illustrating an example of a data structure of history information. [Figure 4] FIG. 10 is a diagram illustrating an example of the configuration of a history-user management table. [Figure 5] FIG. 2 is a diagram illustrating an example of a data structure of history information. [Figure 6] 1 is a flowchart illustrating a processing flow according to the first embodiment. [Figure 7] 1 is a flowchart illustrating a processing flow according to the first embodiment. [Figure 8] FIG. 2 is a diagram illustrating an example of operation of the first embodiment. [Figure 9] FIG. 2 is a diagram illustrating an example of operation of the first embodiment. [Figure 10] FIG. 2 is a diagram illustrating an example of operation of the first embodiment. [Figure 11] FIG. 2 is a diagram illustrating an example of operation of the first embodiment. [Figure 12] FIG. 2 is a diagram illustrating an example of operation of the first embodiment. [Figure 13] FIG. 2 is a diagram illustrating an example of operation of the first embodiment. [Figure 14] FIG. 2 is a diagram illustrating an example of operation of the first embodiment. [Figure 15] 10 is a flowchart illustrating a processing flow according to a second embodiment. [Figure 16] FIG. 10 is a diagram illustrating an example of operation of the second embodiment. [Figure 17] FIG. 10 is a diagram illustrating an example of operation of the second embodiment. [Figure 18] 10 is a flowchart illustrating a processing flow according to a third embodiment. [Figure 19] FIG. 10 is a diagram illustrating an example of operation of the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In this disclosure, a multifunction peripheral capable of executing jobs in each mode, such as copy mode, fax mode, and scan mode, will be described as one form of an image processing device. Note that the following embodiment is an example for explaining the present disclosure, and the technical scope of the description set forth in the claims is not limited to the following description.

[0014] [1 First Embodiment] The first embodiment is a mode in which, based on the recognition result of a user located near a multifunction peripheral as an image processing device, the setting history associated with the recognized user is preferentially displayed.

[0015] [1.1 Functional Configuration] Fig. 1 is an external perspective view illustrating the overall configuration of a multifunction device 10 according to a first embodiment. Fig. 2 is a functional configuration diagram of the multifunction device 10. The multifunction device 10 includes a control unit 11, a display unit 13, an operation input unit 15, a communication unit 17, an image forming unit 19, an image reading unit 21, a recognition unit 23, and a storage unit 25.

[0016] The control unit 11 controls the entire multifunction device 10. The control unit 11 is configured, for example, with one or more arithmetic units (CPUs (Central Processing Units) and the like). The control unit 11 realizes its functions by calling and executing various programs stored in the storage unit 25.

[0017] The display unit 13 displays various types of information to the user, etc. The display unit 13 can be configured, for example, by an LCD (Liquid Crystal Display), an organic EL (Electro-luminescence) display, or the like.

[0018] The operation input unit 15 accepts information input by a user or the like. The operation input unit 15 can be configured with hard keys (for example, a numeric keypad), buttons, etc. The operation input unit 15 can be configured as a touch panel that allows input via the display unit 13. In this case, the input method of the touch panel can be, for example, a resistive film type, an electromagnetic induction type, or a capacitance type.

[0019] The communication unit 17 has a wired / wireless interface or both for communicating with other devices via a network (NW) such as a LAN (Local area network), WAN (Wide area network), the Internet, a telephone line, a fax line, etc.

[0020] Image forming unit 19 forms an image based on image data on paper as a recording medium. Image forming unit 19 feeds paper from paper feed unit 27, forms an image based on the image data on the paper, and then discharges the paper to paper discharge unit 29. Image forming unit 19 can be configured, for example, by a laser printer that uses an electrophotographic method. Image forming unit 19 forms an image using toner supplied from toner cartridges (not shown) that correspond to toner colors (e.g., cyan, magenta, yellow, black, etc.).

[0021] The image reading unit 21 generates image data by scanning and reading the document image to be read. The image reading unit 21 can be configured as a scanner device equipped with an image sensor such as a CCD (Charge Coupled Device) or a CIS (Contact Image Sensor). There are no limitations on the configuration of the image reading unit 21 as long as it is configured to generate image data by reading a reflected light image from the document image with an image sensor.

[0022] The recognition unit 23 is not particularly limited as long as it is capable of acquiring and outputting image information, audio information, and the like, related to a person (user) located near the multifunction peripheral 10 as recognition information. The recognition unit 23 may be, for example, a camera mounted on the multifunction peripheral 10, an indoor monitoring camera, or the like, which is capable of acquiring and outputting image information related to person recognition, such as a face, line of sight, movement of the corners of the mouth, body shape (skeleton), posture, movement, behavior, gait, and distance and path to the multifunction peripheral 10. The recognition unit 23 may also be a sound collection and recording device that records the voice emitted by a person. Furthermore, wireless communication functions (e.g., Bluetooth (registered trademark), Wi-Fi (registered trademark), NFC (Near Field Communication)) and location information transmission and acquisition functions (e.g., GPS (Global Positioning System), beacons, etc.) provided by a terminal device such as a smartphone may be used to use the individual identification information and location information of the terminal device obtained by these functions as recognition information for the person carrying the terminal device.

[0023] The storage unit 25 stores various programs and various data necessary for the operation of the multifunction device 10. The storage unit 25 can be configured with a storage device such as a RAM (Random access memory), an HDD (Hard disk drive), an SSD (Solid state drive), or a ROM (Read only memory).

[0024] In the first embodiment, the memory unit 25 stores a job execution program 251, a user recognition program 252, a history information processing program 253, a user authentication program 254, and a display processing program 255, and reserves a setting value file memory area 256, a setting history memory area 257, a job history memory area 258, and a user information memory area 259.

[0025] The job execution program 251 is a program that is read by the control unit 11 to execute jobs in each mode, such as copy mode, fax mode, and scan mode. The control unit 11 that has read the job execution program 251 executes jobs by controlling the job execution units involved in the execution of jobs in each mode, such as the display unit 13, operation input unit 15, communication unit 17, image forming unit 19, and image reading unit 21. Furthermore, the control unit 11 that has called the job execution program 251 can execute various jobs based on setting values ​​contained in a setting value file associated with setting history, which is history information.

[0026] The user recognition program 252 is a program loaded by the control unit 11 when recognizing an original user located near the multifunction peripheral 10 as the operating user. Here, the original user according to the present disclosure refers to a user who has previously operated the multifunction peripheral 10 and executed jobs in various modes, such as copy mode, fax mode, and scan mode. The setting history generated upon execution of the job is associated with the original user's user identification information. Furthermore, the operating user according to the present disclosure refers to an original user who operates or has the potential to operate the multifunction peripheral 10. The control unit 11, which has loaded the user recognition program 252, recognizes an original user located near the multifunction peripheral 10 as the operating user using image information, audio information, or individual identification information of a terminal device owned by the user acquired by controlling the recognition unit 23. The control unit 11 can recognize the operating user by, for example, using image information acquired via the recognition unit 23 as input values ​​and comparing the input image information converted into feature quantities. Furthermore, the control unit 11 can recognize a person uttering a specific keyword (e.g., print, copy, etc.) as the operating user based on the analysis results of audio acquired by a sound collection / recording device, etc. Furthermore, unlike the biometric recognition described above, when user recognition is performed using the individual identification information and location information of the terminal device, the control unit 11 also controls the communication unit 17, etc., to perform communication required to acquire the individual identification information, etc. of the terminal device. The control unit 11 can also recognize the operating user by using machine learning that uses as input values ​​the above-described accumulation of recognition information, user operation information accompanying the recognition result, date and time information, and schedule information of the executing (operating) user.

[0027] The history information processing program 253 is a program that the control unit 11 reads, for example, when acquiring setting values ​​related to job execution, generating a setting history, and performing various processes on the setting history and generating a job history. The control unit 11, which has called the history information processing program 253, acquires setting values ​​related to job execution and generates a setting value file containing the setting values. The control unit 11 then associates the generated setting value file with the setting history and stores it in the setting value file storage area 256. The control unit 11 also manages the setting history by associating it with the user name or user ID of the executing user who executed the job corresponding to the setting history.

[0028] Furthermore, the control unit 11 that has read the history information processing program 253 performs a process of selecting display candidates for the setting history to be displayed on a setting history display screen (to be described later) based on the user recognition result. The process of selecting display candidates will be described later.

[0029] The user authentication program 254 is a program that the control unit 11 loads when authenticating the current user or other users who log in to the multifunction device 10. When the user authentication function is on, the control unit 11 that has loaded the user authentication program 254 displays a login screen, which will be described later. For example, the control unit 11 can perform login authentication of a user by previously storing a login user name and a login password in association with each other, and comparing the login user name and the login password entered via the login screen. Note that login authentication can be performed using knowledge authentication based on the input of a login user name and a login password, as well as possession authentication using a token, key, IC card, smartphone, etc., or biometric authentication such as fingerprint authentication, palm print authentication, or blood vessel authentication.

[0030] The display processing program 255 is a program that is loaded by the control unit 11 when controlling a display screen to be displayed via the display unit 13. The control unit 11 that loaded the display processing program 255 displays, on the display unit 13, a setting history display screen that displays the setting history, a setting screen for receiving input of various setting values ​​related to job execution, or a home screen that receives instructions to switch between each (operation) mode, etc. Furthermore, the control unit 11 that loaded the display processing program 255 displays, on the setting history display screen, a setting history selected based on the result of a selection process for selecting display candidates for the setting history.

[0031] The setting value file storage area 256 is a storage area for storing setting value files generated by the control unit 11 that has read the history information processing program 253. The setting values ​​include, for example, setting values ​​set by the user, such as color mode, size, double-sided copying, (copy) magnification, tray, and staple, as well as setting values ​​such as device initial values ​​that the multifunction peripheral 10 itself holds from the factory. The control unit 11 that has called the job execution program 251 can obtain a setting value file associated with the setting history of the job to be executed from the setting value file storage area 256, and execute the job based on the setting values ​​included in the setting value file.

[0032] The setting history storage area 257 is a storage area for storing the setting history generated by the control unit 11 that has read the history information processing program 253. The setting history stored in the setting history storage area 257 is called up as appropriate during the selection process for displaying setting history candidates and the display process on the setting history display screen.

[0033] The job history storage area 258 is a storage area that stores job execution records as job histories. The job histories are generated by the control unit 11 that has read the history information processing program 253. Unlike the setting history, the job history is information that records the job execution history, and therefore can be generated at any timing, such as before or after the execution of a job or before or after the generation of the setting history.

[0034] The user information storage area 259 is a storage area for storing information related to user authentication, such as the login user name and login password of an original user attempting to log in to the multifunction device 10 and other users. The user information storage area 259 also stores a history-user management table for managing setting history in association with the original user. Furthermore, the user information storage area 259 can store various information (e.g., feature amounts for user recognition, etc.) used to recognize an original user located near the multifunction device 10 as the operating user.

[0035] Here, the setting history and setting value file according to the present disclosure will be described. Fig. 3(a) is a diagram illustrating an example of the data structure of the setting history stored in the setting history storage area 257. Fig. 3(b) is a diagram illustrating an example of the data structure of the setting value file stored in the setting value file storage area 256.

[0036] The setting history shown in FIG. 3A includes a history ID, an execution date and time, a job type, a display setting value, and a setting value file name.

[0037] The history ID is an identifier for uniquely identifying the setting value history. The history ID is assigned to the generated setting history. The history ID may be a serial number, as shown in the example of Figure 3(a), or may include a specified string of characters, symbols, etc. The execution date and time indicates the date and time when the job was executed and the setting history was generated. The job type indicates the type of job executed (e.g., simple copy job, simple scan job, etc.). The display setting value indicates part of the setting value (content) to be displayed on the setting history display screen when displaying the setting history. The setting value file name indicates the file name of the setting value file associated with the setting history.

[0038] For example, the setting history associated with history ID "001" represents the setting history for the job type "simple copy" executed on "2020 / 02 / 22 20:20." This job is a simple copy job executed based on the setting values ​​contained in the setting value file "001.config," and is an example in which display setting values ​​such as "Number of copies: 1, Color mode: Automatic, Size: A4, Duplex (copy): Simplex, Magnification: 100x, Tray: Tray 1, Staples: No Staples" are set. Note that the display setting values ​​set according to each setting history are merely examples, and the setting values ​​displayed on the setting history display screen are not limited to those shown in FIG. 3(a).

[0039] 3(b) is a diagram illustrating an example of the data structure of the setting value file "001.config" associated with the setting history with history ID "001" in FIG. 3(a). The setting value file can be configured, for example, as a text file containing setting values ​​corresponding to each setting. Note that if there is no need for the file to be user-readable, the setting value file can also be configured as binary data.

[0040] For example, Figure 3(b) is an example of a setting value file for a simple copy job, which contains the various setting values ​​for executing the simple copy job (e.g., number of copies: 1, color mode: automatic, size: A4, double-sided copying: simplex, magnification: 100%, tray: tray 1, staple / punch: no staples, copy density: automatic, etc.).

[0041] Next, we will explain the history-user management table managed by the control unit 11. Fig. 4 is a diagram illustrating an example of the data structure of the history-user management table stored in the user information storage area 259. The history-user management table illustrated in Fig. 4 includes a history ID, a user name, and a user ID.

[0042] The history ID is the same as the history ID described in FIG. 3(a). The history-user management table stores the history ID in association with the user name and / or user ID of the executing user. The user name is the user name of the executing user who executed the job related to the setting history indicated by the history ID. The user ID is an identifier for identifying the executing user. The history ID can be associated with either the user name or the user ID, or both.

[0043] For example, the history ID "001" shown in Fig. 4 is associated with an executing user with the user name "aaaaa" and user ID "0001@sample." Note that for convenience of explanation, Fig. 4 shows an example in which the same executing user (user name "aaaaa" and user ID "0001@sample") is associated with all the illustrated history IDs ("001" to "010"), but the setting history indicated by the history ID is associated with each executing user who executed the job corresponding to that setting history.

[0044] Fig. 5 is a diagram illustrating an example of the data structure of a job history stored in the job history storage area 258. The job history illustrated in Fig. 5 includes a job ID, an execution date and time, a job type, a user name, and a status.

[0045] The job ID is an identifier for uniquely identifying an executed job. A job ID is generated each time a job is executed. The job ID may be a serial number, as shown in the example of Figure 5, or may include a predetermined string of characters, symbols, etc. The execution date and time indicates the date and time when the job was executed. The job type indicates the type of job executed (e.g., simple copy job, simple scan job, etc.). The user name indicates the name of the executing user who executed the job. The status indicates the processing status of the job.

[0046] For example, the job history for job ID "001" represents the job history for the job type "simple copy" executed at "2020 / 02 / 22 20:20." The job was executed by an executing user with the user name "aaaaa," and the status of the job is "completed."

[0047] Unlike the setting history, the job history is information that records the execution history of a job, and there are no particular restrictions on when it can be generated. For example, it can be generated at any time, such as before or after the execution of a job or before or after the generation of the setting history.

[0048] [1.2 Processing flow] Next, the flow of processing according to the first embodiment will be described. Fig. 6 is a flowchart illustrating the overall processing by the multifunction device 10. The processing described here is processing executed by the control unit 11 by reading a job execution program 251, a user recognition program 252, a history information processing program 253, a user authentication program 254, a display processing program 255, etc.

[0049] For example, when the power is turned on or when the device is restored from a sleep state, the control unit 11 reads the setting history in conjunction with the start-up process (step S10).

[0050] Next, the control unit 11 loads the user recognition program 252. The control unit 11 controls the recognition unit 23 to determine whether or not the regular user located near the multifunction peripheral 10 has been recognized as the operating user (step S20).

[0051] When an operating user located near the multifunction device 10 is recognized, the control unit 11 reads the history information processing program 253 to extract the setting history related to the job executed by the operating user (step S20; Yes → step S30).

[0052] On the other hand, if the control unit 11 does not recognize the operating user located near the multifunction device 10, the control unit 11 displays a login authentication screen if the user authentication function is on, or displays an initial screen (e.g., a home screen) if the user authentication function is off, and waits until the operating user is recognized (step S20; No).

[0053] After extracting the setting history of the recognized operating user in step S30, the control unit 11 determines whether the number of extracted setting histories exceeds the maximum number that can be displayed on the setting history display screen (step S40).

[0054] If the number of extracted setting histories exceeds the maximum number that can be displayed on the setting history display screen, the control unit 11 performs a process of selecting display candidates for setting histories to be displayed on the setting history display screen based on the usage tendency (usage frequency) of the recognized operating user (step S40; Yes → step S50). Here, the usage tendency (usage frequency) in the present disclosure is a concept that encompasses the setting history of the job type that the executing user uses (re-) when executing a job, and the usage tendency, frequency, number of times, etc. of the setting items (setting values) included in the setting history.

[0055] After the display candidate selection process, the control unit 11 displays the selected display candidate of the setting history on the setting history display screen (step S60).

[0056] If the number of extracted setting histories does not reach the maximum number that can be displayed on the setting history display screen, the control unit 11 displays the extracted setting histories on the setting history display screen (step S40; No→step S60).

[0057] When a user selects a setting history displayed on the setting history display screen and executes a job based on that setting history, the control unit 11 generates a setting history based on the executed job. The control unit 11 then stores the generated setting history in the setting history storage area 257 and ends the process (step S70 → step S80).

[0058] In addition, if the number of setting histories stored in the setting history storage area 257 reaches the upper limit, it is possible to delete setting histories with old execution dates and times or setting histories that are considered to be used infrequently, and store newly generated setting histories.

[0059] Next, a process will be described in step S50 of FIG. 6 when the number of extracted setting histories exceeds the maximum number that can be displayed on the setting history display screen.

[0060] In the present disclosure (first embodiment), a display candidate selection process will be described in which display candidates are determined based on the usage tendency (usage frequency) of the recognized operating user. Display candidates based on the usage tendency of the operating user can be determined based on the results of machine learning using setting values ​​in the setting history as input values. In this case, it is also possible to take into consideration information on the date and time when the job was executed by the operating (executing) user, schedule information of the operating (executing) user, etc.

[0061] FIG. 7 is a flowchart illustrating a process for determining display candidates using machine learning.

[0062] First, the control unit 11 calculates the similarity between the setting histories using the setting items of the setting histories as feature quantities (step S510).

[0063] The control unit 11 classifies the setting items included in the setting history (setting value file) into setting items that are difficult to change and setting items that are easy to change, and calculates the similarity by calculating a score value from the following items (note that the higher the item, the greater the weighting). Differences in settings that are difficult to change Match > 1 difference > 2 differences > ... > Mismatch Differences in settings that are easy to change Match > 1 difference > 2 differences > ... > Mismatch -Does not take into account the execution date and time -Set weight for each setting item

[0064] Here, setting items that are difficult to change refer to setting items (e.g., skip blank pages, sort, etc.) that are not directly displayed on the setting screen for executing a job in each mode (e.g., copy mode), but can be changed after a screen transition occurs by operating tabs or buttons for advanced settings (or similar wording).

[0065] On the other hand, setting items that are easy to change refer to setting items that are displayed directly on the setting screen for executing jobs in each mode (for example, number of copies, color mode, etc.) Note that setting items that are displayed directly on the setting screen also include destinations in fax mode and scan mode, but because changing destinations requires effort, they are treated as an exception and are difficult to change.

[0066] Next, the control unit 11 determines whether the similarity calculated in step S510 exceeds a predetermined threshold value (step S520).

[0067] If it is determined that the similarity exceeds the predetermined threshold, the control unit 11 stores the similar setting histories as a cluster (step S520; Yes→step S530).

[0068] Next, the control unit 11 calculates a representative element from the elements in the cluster (step S540). The control unit 11 calculates the representative element by calculating a score value from the following items (note that the higher the item, the greater the weighting). Matching setting history Many > few Differences from the default settings Many > few

[0069] Then, the control unit 11 calculates the score of the representative element (step S550). The control unit 11 calculates the score of the representative element by calculating the score value from the following items (note that the higher the item, the greater the weighting). Number of elements included in the cluster (= number of similar histories) Many > few Document style similarity (when OCR is performed) High > Low Destination (when entering destination) Match > Mismatch Element execution date and time New > Old Job type (set to have minimal impact) Image transmission jobs > Copy jobs

[0070] The control unit 11 sorts the representative elements in descending order of the calculated scores (step S560), and then selects the top representative elements as display candidates based on the sorting results (step S570).

[0071] 6, if the number of extracted setting histories does not reach the maximum number that can be displayed on the setting history display screen, setting histories associated with other users other than the recognized operating (executing) user can also be displayed. The setting histories associated with other users to be displayed can be selected according to the process of determining display candidates using machine learning described above. Also, for example, it is possible to extract setting histories associated with other users in a number that meets the maximum number that can be displayed according to a predetermined criterion (for example, setting histories that are in line with the usage trends of the recognized operating user, setting histories that are not in line with the usage trends of the recognized operating user, or simply setting histories with the most recent job execution), and display them together with the setting histories of the recognized operating user.

[0072] [1.3 Example of operation] Next, an operation example of the first embodiment will be described. FIG. 8 is a diagram illustrating one configuration of a user authentication screen W10 that the control unit 11 displays on the display unit 13. The user authentication screen W10 can be configured as a login screen that the control unit 11 displays on the display unit 13 after reading the user authentication program 254 when the login authentication function is on. In the first embodiment, when the user authentication screen W10 is displayed and the recognition unit 23 recognizes the operating user before an authentication request is made by the regular user or another user, the setting history corresponding to the recognized operating user can be preferentially displayed. Note that when the user authentication function is off, the control unit 11 displays a home screen (not shown) on the display unit 13, and when the recognition unit 23 recognizes the operating user, the setting history corresponding to the recognized operating user is preferentially displayed.

[0073] The user authentication screen W10 includes a login user name input box Bx10, a login password input box Bx12, an authentication destination designation button B10, an OK button B12, and a cancel button B14.

[0074] The login user name input box Bx10 is an input box that accepts input of a login user name. The current user or another user attempting to log in to the multifunction device 10 inputs a login user name into the login user name input box Bx10. The login user name can be selected from a separately provided user name list.

[0075] The login password input box Bx12 is an input box that accepts input of a login password corresponding to a login user name. The original user or another user attempting to log in to the multifunction device 10 inputs the login password along with the login user name.

[0076] The authentication destination designation button B10 is a button for accepting designation of the user authentication destination. The user authentication destination may be a device alone, or, for example, an authentication server or the like separately provided on a network (NW) can also be designated. When authentication on a device alone is designated as the user authentication destination, the control unit 11 performs user authentication by comparing the input login user name and login password with pre-prepared authentication information (for example, a combination of a user name and a password). On the other hand, when an authentication server or the like provided on the network (NW) is used, the control unit 11 can also perform user authentication by transmitting the input login user name and login password to the authentication server and receiving the authentication result from the authentication server.

[0077] The OK button B12 is an input button that accepts a user's input to confirm an input operation. The user presses the OK button B12 to confirm the input into the login user name input box Bx10 or the login password input box Bx12, or the designation of the user authentication destination via the authentication destination designation button B10. The cancel button B14 is an input button that accepts a user's input to cancel an input operation.

[0078] Next, an example of the operation of the process for determining display candidates using machine learning will be described. For ease of explanation, the maximum number of setting histories that can be displayed on the setting history display screen will be described as five. In step S20 of FIG. 6, the user name of the regular user recognized as the operating user will be "aaaaa," and the ten setting histories with history IDs "001" to "010" shown in FIG. 3 will be associated with the regular user (see the history-user management table in FIG. 4). The number of setting histories associated with the regular user (10) is merely an example, and the number of setting histories is not limited to that described here.

[0079] Fig. 9 shows an example of a configuration of a history table that compiles each setting item (setting value) used for machine learning for each setting history, which corresponds to the setting history of the user name "aaaaa" extracted by the control unit 11 in step S30 of Fig. 6. Each setting item shown in the history table of Fig. 9 is used as an input value for machine learning.

[0080] The history table shown in FIG. 9 shows setting items that are easy to change (setting values ​​that are difficult to change are omitted) and default setting items.

[0081] For example, the setting history for history ID "001" shows the current settings as (job type: simple copy, number of copies: 1, color: automatic, size: A4, double-sided (copy): single-sided, magnification: 100%, tray: tray 1, staples: no staples, ...).

[0082] On the other hand, the default settings for the job type: simple copy are (number of copies: 1, color: automatic, size: A4, duplex (copy): simplex, magnification: 100%, tray: automatic, staple: none, ...). Therefore, for history ID "001," the settings for the tray and staple have been changed from the default settings.

[0083] The control unit 11 performs a display candidate determination process by using the history table illustrated in Fig. 9 as an input value and calculating the score value of the representative element described in the flowchart of Fig. 7. An example of an operation related to the calculation of the score value of the representative element using the setting history illustrated in Fig. 9 will be described.

[0084] In step S510 of FIG. 7, the similarity of the setting history in the example of FIG. 9 is calculated as follows: Exactly matching setting history: (History ID: 001, 010) and (History ID: 005, 009), 1 item difference: (History ID: 001, 006, 010) and (History ID: 002, 005, 009), 2 item difference: (History ID: 003, 007) · · It is calculated as follows.

[0085] Based on the similarity calculation results, the setting history in the example of Figure 9 can be classified into clusters of (history ID: 001, 006, 010), (history ID: 002, 005, 009), (history ID: 003, 007), (history ID: 4), and (history ID: 8).

[0086] In step S540 of FIG. 7, the control unit 11 calculates a representative element from the classified clusters. Cluster (History ID: 001, 006, 010) Matching setting history: (History ID: 001, 010) Difference from default setting: (History ID: 001, 010) = (History ID: 006) Therefore, the control unit 11 calculates the representative element as (history ID: 001, 010). Cluster (History ID: 002, 005, 009) Matching setting history: (History ID: 005, 009) Difference from default setting: (History ID: 005, 009) > (History ID: 002) Therefore, the control unit 11 calculates the representative elements as (history ID: 005, 009). Cluster (History ID: 003, 007) Matching configuration history: None Difference from default settings: (History ID: 007) Therefore, the control unit 11 calculates the representative element as (history ID: 007).

[0087] In step S550, the control unit 11 calculates the scores of the representative elements. Representative element (history ID: 001, 010) Number of cluster elements: 3 Latest execution date and time: (History ID: 001) Type: Copy job Representative element (history ID: 005, 009) Number of cluster elements: 3 Latest execution date and time: (History ID: 005) Type: Copy job Representative element (history ID: 007) Number of cluster elements: 2 Latest execution date and time: (History ID: 007) Type: Image transmission job

[0088] If we sort the representative elements in descending order, the score value of the representative element will be (History ID: 001, 010) > (History ID: 005, 009) > (History ID: 007). Note that (History ID: 004) and (History ID: 008) are displayed in order of most recent execution date and time.

[0089] 10 shows an example of the configuration of a display table that determines the display order of setting histories determined as display candidates. Note that the display priority within a representative element is such that setting histories with the most recent execution date and time are displayed first.

[0090] As shown in Figure 10, based on the results of the display candidate determination process, the control unit 11 displays the setting history of the current user "aaaaa" in the following display order: ID: "001" > History ID "005" > History ID "007" > History ID "004" > History ID "008".

[0091] Fig. 11 is an example of a display configuration of a setting history display screen W20 that displays the setting history shown in the display table of Fig. 10. The setting history display screen W20 can be displayed in response to an input from a display instruction button provided on, for example, a home screen (not shown) or a setting screen corresponding to each job type.

[0092] The setting history display screen W20 includes a setting history display area R10 and a slider bar SB10. The setting history display area R10 is a display area that displays the setting history shown in the display table of FIG.

[0093] 11 is an example of the setting history associated with the executing user "aaaaa" as the operating user, displayed in the setting history display area R10 in the following display order: ID: "001" > history ID "005" > history ID "007" > history ID "004" > history ID "008". In the setting history display area R10, the setting history is displayed based on the usage tendency (frequency of use) of the recognized operating user, so the operating user can understand their own usage tendency for the setting history and efficiently reproduce jobs based on that setting history.

[0094] The slider bar SB10 is configured to be slidable up and down. The slider bar SB10 accepts instructions to display hidden areas in the setting history display area R10. For example, by performing operations such as moving the slider bar SB10 up and down, pressing an arrow button, or flicking within the setting history display area R10, the hidden areas can be displayed in the setting history display area R10.

[0095] In the explanation of the operation example according to the first embodiment, it was explained that the maximum number of setting histories that can be displayed on the setting history display screen W20 is five. However, it is also possible to display more than five setting histories by, for example, providing an operable slider bar SB10 on the setting history display screen W20.

[0096] Next, a description will be given of an example of operation when the number of extracted setting histories does not reach the maximum number that can be displayed on the setting history display screen in step S40 of Fig. 6. In this case, the control unit 11 displays setting histories associated with other users together with the setting history of the executing user recognized as the operating user.

[0097] Fig. 12(a) shows an example of the configuration of a history table in the case where the user name of the actual user recognized as the operating user in step S20 of Fig. 6 is "aaaaa," and the actual user is associated with two setting histories with history IDs "001" and "003" shown in Fig. 3. Fig. 12(b) shows an example of the configuration of a history table for setting histories associated with users other than the actual user.

[0098] The control unit 11 adds the setting histories of other users so that (maximum number to display) = (number of setting histories of the executing user) + (number of setting histories of other users). The selection of the setting histories associated with other users to be displayed can be performed according to the process of determining display candidates using the machine learning described above. Also, for example, it is possible to extract the setting histories associated with other users in accordance with a predetermined criterion (for example, setting histories that are in line with the usage trends of the recognized user, setting histories that are not in line with the usage trends of the recognized user, or simply setting histories with the most recent job execution), and display them together with the setting histories of the recognized user.

[0099] FIG. 13 shows an example of the configuration of a display table that determines the display order of setting histories (setting histories of the current user and setting histories of other users) determined as display candidates.

[0100] 13, in addition to the setting histories with history IDs "001" and "002" associated with the executing user recognized as the operating user, setting histories with history IDs "011", "012", and "014" associated with other users are added so as to satisfy the maximum number of items to be displayed. Note that if the maximum number of items to be displayed cannot be satisfied even after adding the setting histories associated with other users, the display table is displayed as is.

[0101] FIG. 14 shows an example of the display configuration of the setting history display screen W20 that displays the setting history shown in the display table of FIG.

[0102] 14 shows an example in which the setting history display area R10 displays the setting histories of other users, history ID "011", history ID "012", and history ID "014", in this order, following the setting histories associated with the executing user "aaaaa" as the operating user, history ID "001" and history ID "003". In this way, if the number of extracted setting histories does not reach the maximum number that can be displayed on the setting history display screen, the display area of ​​the setting history display screen W20 can be effectively utilized by adding setting histories associated with other users so as to reach the maximum number.

[0103] As described above, according to the first embodiment, the convenience of the user operating the multifunction device can be improved by preferentially displaying the setting history associated with the executing user recognized as the operating user based on the recognition result of the user located near the multifunction device.

[0104] [2 Second Embodiment] The second embodiment is a form in which a plurality of regular users are located near the multifunction peripheral 10. [2.1 Functional Configuration] The functional configuration of the multifunction device according to the second embodiment can be substantially the same as the functional configuration of the multifunction device 10 according to the first embodiment. Therefore, the multifunction device according to the second embodiment will be referred to as the multifunction device 10, and detailed description of the functional configuration will be omitted.

[0105] [2.2 Processing flow] 15 is a flowchart illustrating the overall processing of the multifunction peripheral 10 according to the second embodiment. The processing described here is executed by the control unit 11 by reading a job execution program 251, a user recognition program 252, a history information processing program 253, a user authentication program 254, a display processing program 255, etc. Note that the same steps as those described in FIG. 6 of the first embodiment are denoted by the same step numbers.

[0106] For example, when the power is turned on or when the device is restored from a sleep state, the control unit 11 reads the setting history in conjunction with the start-up process (step S10).

[0107] Next, the control unit 11 loads the user recognition program 252. The control unit 11 controls the recognition unit 23 to determine whether or not the regular user located near the multifunction device 10 has been recognized (step S90).

[0108] When the control unit 11 recognizes an execution user located near the multifunction device 10, the control unit 11 reads the history information processing program 253 to extract the setting history related to the job executed by the execution user (step S90; Yes → step S100).

[0109] On the other hand, if the control unit 11 does not recognize a user located near the multifunction device 10, if the user authentication function is on, it displays a login authentication screen, and if the user authentication function is off, it displays an initial screen (e.g., a home screen) and waits until it recognizes the user (step S90; No).

[0110] Next, the control unit 11 determines whether or not the regular user who is closest to the multifunction device 10 has been identified as the operating user (step S110).

[0111] If the actual user who is closest to the multifunction peripheral 10 can be identified as the operating user, the control unit 11 displays the setting history in display pattern 1 (step S110; Yes → step S120). Here, display pattern 1 is a display pattern that displays the setting history associated with the identified operating user (including multiple users), and is the display mode of the setting history exemplified in Fig. 6 etc. of the first embodiment.

[0112] On the other hand, if the regular user closest to the multifunction peripheral 10 cannot be identified as the operating user, the control unit 11 displays the setting histories of all recognized regular users extracted in step S100 as display pattern 2 (step S110; No → step S130). In this case, the control unit 11 may, for example, display the setting histories of all recognized regular users in chronological order from most recent to least recent, or may calculate and display display candidates from the setting histories of all recognizable users. Note that, in calculating display candidates for the setting histories to be displayed, the display candidates can be narrowed down by slightly weighting setting histories with the same score value according to the distance between the multifunction peripheral 10 and the user, etc.

[0113] Next, the control unit 11 determines whether the identified operating user has changed (step S140). That is, the control unit 11 determines whether the regular user identified as the operating user located near the multifunction peripheral 10 has been replaced with another regular user.

[0114] If it is determined that the operating user closest to the multifunction device 10 has changed, the control unit 11 switches the display to the setting history associated with the changed executing user (step S140; Yes → step S150). Then, when a job is executed based on the displayed setting history, the control unit 11 stores the setting history related to the job and ends the process (step S70 → step S80).

[0115] On the other hand, if it is determined that the operating user closest to the multifunction device 10 has not changed, the control unit 11 proceeds to step S70 (step S140; No→step S70). Then, when a job is executed based on the displayed setting history, the control unit 11 stores the setting history related to the job and ends the process (step S70→step S80).

[0116] [2.2 Example of operation] Next, an operation example according to the second embodiment will be described. Figures 16 and 17 show an example of the display configuration of the setting history display screen (display pattern 1) displayed by the control unit 11 when the original user who is closest to the multifunction peripheral 10 can be identified as the operating user in step S110 of Figure 15.

[0117] In the second embodiment, the following two display modes can be applied in the vicinity of the multifunction peripheral 10 according to the degree of identification of the operating user among a plurality of recognized regular users. The closest regular user to the multifunction device 10 is identified as the operating user, and the setting history of that operating user is displayed. If the closest operating user is replaced by another regular user, the display of the setting history is also changed accordingly. If multiple users are located near the MFP 10 and the accuracy of identifying the operating user is low, only the setting history of the operating user is displayed, excluding the setting history related to job types related to sending and saving. If the operating user who operates the MFP 10 is clearly identified, the setting history of that operating user is displayed without any restrictions.

[0118] 16(a) shows an example of the display configuration of the setting history display screen W20 in which the actual user "aaaaa" is identified as the operating user and the setting history of the operating user "aaaaa" is displayed. Note that the setting history display screen W20 can have the same configuration as the setting history display screen W20 illustrated in FIG. 11 according to the first embodiment.

[0119] 16(b) shows an example of the display configuration of the setting history display screen W40 that displays the setting history of user "bbbbb" identified as the operating user when the operating user located near the multifunction peripheral 10 is replaced with, for example, regular user "bbbbb" from the display state shown in FIG. 16(a). In this way, when the operating user located closest to the multifunction peripheral 10 is replaced with another regular user, the control unit 11 can also change the display of the setting history accordingly.

[0120] 17(a) shows an example of the display configuration of a setting history display screen W50 that displays only the setting history of the actual user "aaaaa" (User A), excluding the setting history related to job types related to sending and saving, when multiple actual users are located near the multifunction device 10 and the accuracy of identifying the operating user is not high. Also, FIG. 17(b) shows an example of the display configuration of a setting history display screen W60 that displays only the setting history of the actual user "bbbbb" (User B), excluding the setting history related to job types related to sending and saving, in the same example.

[0121] 17(a) and 17(b), if the accuracy of identifying the operating user is not high and it is not possible to clearly identify either of the original users as the operating user, the setting history is displayed excluding the setting history related to the transmission / save job types of both original users. This allows either the original user (User A) or the original user (User B) located near the multifunction peripheral 10 to efficiently use their own setting history even if the accuracy of identifying the operating user is not high. In this case, the setting history related to the transmission / save job types is not displayed to the original user, which has the advantage of preventing, for example, the risk of destination information such as a fax number or email address being leaked to third parties, including other original users.

[0122] As described above, according to the second embodiment, in addition to the effects of the first embodiment, even if multiple actual users are located near the multifunction device 10 and the accuracy of identifying the operating user is not high, the actual user can efficiently use his or her own setting history.

[0123] [3 Third embodiment] The third embodiment is an embodiment in which, after the display candidates of the setting history described in the first embodiment have been determined, if a specific operation is performed, the display candidates are recalculated.

[0124] [3.1 Functional Configuration] The functional configuration of the multifunction device according to the third embodiment can be substantially the same as the functional configuration of the multifunction device 10 according to the first embodiment. Therefore, the multifunction device according to the third embodiment will be referred to as the multifunction device 10, and detailed description of the functional configuration will be omitted.

[0125] [3.2 Processing flow] 18 is a flowchart illustrating the overall processing of the multifunction peripheral 10 according to the third embodiment. The processing described here is processing that is executed by the control unit 11 by reading the job execution program 251, user recognition program 252, history information processing program 253, user authentication program 254, display processing program 255, etc. Note that the description here will be given as processing after the setting history display processing relating to steps S10 to S60 in FIG. 6 according to the first embodiment has been executed.

[0126] 6, the control unit 11 determines whether or not OCR has been performed (step S200). If it is determined that OCR has been performed, the control unit 11 determines whether or not a setting history with a similar document style exists (step S200; Yes → step S210). Here, the document style refers to a document style formed by a document, a chart, a layout, etc. represented by image data generated by reading an original image with the image reading unit 21 in a fax job, a scan job, etc.

[0127] If it is determined that a setting history with a similar document style exists, the control unit 11 updates the display candidates (step S210; Yes → step S240). Then, the control unit 11 displays the setting history based on the update result and ends the process (step S60).

[0128] On the other hand, if it is determined that OCR has not been performed (step S200; No), or if it is determined that there is no setting history with a similar document style (step S210; No), the control unit 11 determines whether a destination has been entered for a sending / storage job type (step S220).

[0129] If it is determined that a destination has been input for a transmission / storage job type, the control unit 11 proceeds to step S240 (step S220; Yes→step S240). On the other hand, if it is determined that a destination has not been input for a transmission / storage job type, the control unit 11 determines whether a file name has been input for the transmission / storage job type (step S220; No→step S230).

[0130] If it is determined that a file name has been input for a transmission / storage job type, the control unit 11 proceeds to step S240 (step S230; Yes→step S240). On the other hand, if it is determined that a file name has not been input for a transmission / storage job type, the control unit 11 displays the setting history without updating the display candidates (step S230; No→step S60).

[0131] [3.3 Example of operation] Next, an example of operation according to the third embodiment will be described. Fig. 19(a) is an example of a display configuration example of a setting history display screen W70 showing the result of recalculating display candidates for setting history when a setting history with a similar document style exists as a result of OCR execution in steps S200 and S210 of Fig. 18. Note that the description will be made assuming that the setting history display screen W20 exemplified in Fig. 11 has been displayed by the processing up to step S60 before OCR execution.

[0132] If, as a result of OCR execution, the setting history with a similar document style is the setting history related to a simple fax job and a simple scan job, the control unit 11 switches the display candidates for the setting history to the setting history related to a simple fax job and a simple scan job, as shown within the dotted frame in Figure 19(a).

[0133] Figure 19(b) is an example of the display configuration of the setting history display screen W80, which shows the results of recalculating the display candidates for the setting history when a destination is entered for a sending / storage job type in step S220 of Figure 18.

[0134] In the case of a job type of a transmission / storage type, when "Yamada@sample.com" is input as the destination, the control unit 11 switches the display candidate of the setting history to the setting history related to the simple scan job, as shown in the dotted line frame in FIG. 19(b).

[0135] Similarly, Figure 19(c) is an example of the display configuration of the setting history display screen W90, which shows the results of recalculating the display candidates for the setting history when a file name is entered for a sending / storing job type in step S230 of Figure 18.

[0136] When a file name to be saved is entered for a transmission / save job type, the control unit 11 switches the display candidates for the setting history to the setting history related to the scan save job and the simple scan job, as shown within the dotted frame in Figure 19(c).

[0137] As described above, according to the third embodiment, after the display candidates for the setting history described in the first embodiment are determined, if a specific operation is performed, the display candidates are recalculated, so that an appropriate setting history can be displayed depending on the specific operation performed.

[0138] The present invention is not limited to the above-described embodiments, and various modifications are possible. In other words, embodiments obtained by combining technical means that are appropriately modified within the scope of the gist of the present invention are also included in the technical scope of the present invention.

[0139] Furthermore, although the above-described embodiments are described separately for the sake of convenience, they may of course be combined and executed within the scope of technical feasibility.

[0140] In addition, the programs that run on each device in the embodiments are programs that control the CPU, etc. (programs that make a computer function) so as to realize the functions of the above-described embodiments. Information handled by these devices is temporarily stored in a temporary storage device (e.g., RAM) during processing, and then stored in various storage devices such as ROMs (Read Only Memories) and HDDs, and is read, modified, and written by the CPU as needed.

[0141] Here, the recording medium for storing the program may be any of semiconductor media (e.g., ROM, non-volatile memory card, etc.), optical recording media / magneto-optical recording media (e.g., DVD (Digital Versatile Disc), MO (Magneto Optical Disc), MD (Mini Disc), CD (Compact Disc), BD (Blu-ray (registered trademark) Disc, etc.)), magnetic recording media (e.g., magnetic tape, flexible disk, etc.). Furthermore, not only are the functions of the above-described embodiments realized by executing the loaded program, but the functions of the present invention may also be realized by processing in cooperation with an operating system or other application programs, etc., based on instructions from the program.

[0142] Furthermore, when distributing the program on the market, the program can be stored on a portable recording medium and distributed, or transferred to a server computer connected via a network such as the Internet. In this case, the storage device of the server computer is of course included in the present invention. [Explanation of symbols]

[0143] 10 Multifunction device 11 Control section 13 Display section 15 Operation input section 17 Communications Department 19 Image forming unit 21 Image reading unit 23 Recognition part 25 Memory section 251 Job Execution Program 252 User Awareness Program 253 History Information Processing Program 254 User Authentication Program 255 display processing program 256 setting file storage area 257 Setting history storage area 258 Job History Storage Area 259 User information storage area 27 Paper feed section 29 Paper output section

Claims

1. a job execution unit that executes a job related to image processing; a storage unit capable of storing history information relating to the execution of the job in association with the user who executed the job; a display unit capable of displaying the history information; a recognition unit for recognizing the original user; a control unit; The control unit is characterized in that, when the recognition unit recognizes the regular user before the login authentication process for the regular user to the image processing device via the authentication screen, the control unit displays the history information associated with the recognized regular user on the display unit in priority to displaying the authentication screen.

2. The image processing device according to claim 1, characterized in that, when the number of pieces of history information associated with the regular user displayed on the display unit exceeds the maximum number of pieces to be displayed, the control unit determines the history information to be displayed on the display unit based on usage trends of the history information associated with the regular user.

3. The image processing device according to claim 2, characterized in that the control unit uses the history information associated with the current user as an input value and determines the history information to be displayed on the display unit based on a score value of a representative element obtained from machine learning including processes related to similarity calculation and clustering.

4. The image processing device according to claim 2, characterized in that, when the number of pieces of history information associated with the regular user displayed on the display unit is less than the maximum number of pieces to be displayed, the control unit displays, in addition to the history information associated with the regular user, history information associated with other regular users other than the regular user recognized by the recognition unit.

5. The image processing device according to claim 1, characterized in that, when there are multiple regular users within a range recognizable by the recognition unit, the control unit recognizes the regular user who is closest to the image processing device as the operating user operating the image processing device, and displays the history information associated with that operating user on the display unit with priority.

6. The image processing device according to claim 1 , wherein the control unit, upon detecting a specific operation by the original user, recalculates display candidates for the history information to be displayed on the display unit.

7. The image processing device according to claim 1 , wherein the recognition unit recognizes the regular user by utilizing a communication function provided in a terminal device possessed by the regular user.

8. The image processing device according to claim 1 , wherein the recognition unit recognizes the regular user through biometric recognition.

9. a job execution step of executing a job related to image processing; a storage step of storing history information relating to the execution of the job in association with the user who executed the job; a display step of displaying the history information; a recognition step of recognizing the original user; a control step of displaying the history information associated with the recognized user in priority to the display of the authentication screen if the user is recognized in the recognition step before the login authentication process for the image processing device of the user via the authentication screen.

Images