Image processing apparatus and display method of history information

Abstract

Provided is an image processing apparatus that, based on a result of recognizing a user located in the vicinity of the image processing apparatus, preferentially displays a setting history corresponding to the recognized user, and that can improve the convenience of a user who operates the image processing apparatus. The image processing apparatus includes a job execution section that executes a job related to image processing; a storage section that can store history information related to execution of the job in association with an execution user of the job; a display section that can display the history information; a recognition section that recognizes the execution user; and a control section that, before authenticating the execution user, causes the display section to preferentially display the history information corresponding to the recognized execution user when the recognition section recognizes the execution user.

Description

TECHNICAL FIELD

[0001] The present application relates to an image processing apparatus. BACKGROUND

[0002] In an image processing apparatus such as a composite machine, relevant setting values of jobs performed in each mode such as a copy mode, a facsimile mode, and a scan mode are stored as history information.

[0003] By associating and storing user identification information (for example, a user name, a user ID, and the like) with history information of setting values related to job execution (hereinafter referred to as setting history in the present disclosure), it is attempted to make it easy to call a setting history by a user unit and to execute a job in which the setting history is utilized.

[0004] For example, in Patent Literature 1, it is disclosed that, in a case where a login user who has been authenticated by an image forming apparatus performs an operation for displaying a setting history, only the setting history corresponding to the login user is displayed.

[0005] PRIOR ART DOCUMENTS

[0006] PATENT LITERATURE

[0007] Patent Literature 1: Japanese Patent Laid-Open No. 2013-062871 SUMMARY

[0008] Technical problem to be solved by the application

[0009] The technology of Patent Literature 1 is configured to display only the setting history corresponding to a login user who has been authenticated by an image forming apparatus, and thus it is possible to prevent improper use by other users and leakage of personal information such as destination information to the outside.

[0010] However, in the technology of Patent Literature 1, the setting history associated with a user cannot be preferentially displayed until the user is authenticated as a login user. In this case, a user who is located in the vicinity of an image forming apparatus for the purpose of operating the image forming apparatus needs to log in to the image forming apparatus after which the setting history associated with himself / herself is searched for and displayed, and it is difficult to say that the user is highly convenient.

[0011] An object of the present disclosure is to provide an image processing apparatus which preferentially displays a setting history associated with a recognized user based on a recognition result of a user located in the vicinity of the image processing apparatus, and which is capable of improving the convenience of a user who operates the image processing apparatus.

[0012] Technical solution for solving the technical problem

[0013] To solve the above problems, the image processing apparatus of the present disclosure is characterized by including: a job execution section that executes a job related to image processing; a storage section that can store history information related to execution of the job in association with an execution user of the job; a display section that can display the history information; an identification section that identifies the execution user; and a control section that, before authenticating the execution user, in a case where the execution user is identified by the identification section, preferentially displays, in the display section, the history information corresponding to the identified execution user.

[0014] Further, the history information display method of the present disclosure is characterized by including: a job execution step that executes a job related to image processing; a storage step that stores history information related to execution of the job in association with an execution user of the job; a display step that displays the history information; an identification step that identifies the execution user; and a control step that, in the identification step, preferentially displays, in a case where the execution user is identified before authenticating the execution user, the history information corresponding to the identified execution user.

[0015] Advantageous Effects

[0016] According to the present disclosure, based on the identification result of the user located near the image processing apparatus, the setting history associated with the identified user is preferentially displayed, and the convenience of the user who operates the image processing apparatus can be improved. BRIEF DESCRIPTION OF DRAWINGS

[0017] Figure 1 is an appearance perspective view of a multifunction peripheral device according to a first embodiment.

[0018] Figure 2 is a functional configuration diagram of the multifunction peripheral device according to the first embodiment.

[0019] Figure 3 is a diagram illustrating one configuration example of a data structure of history information.

[0020] Figure 4 is a diagram illustrating one configuration example of a history-user management table.

[0021] Figure 5 is a diagram illustrating one configuration example of a data structure of history information.

[0022] Figure 6 is a flowchart illustrating a processing flow of the first embodiment.

[0023] Figure 7 is a flowchart illustrating a processing flow of the first embodiment.

[0024] Figure 8is a diagram for explaining an action example of the first embodiment.

[0025] Figure 9 is a diagram for explaining an action example of the first embodiment.

[0026] Figure 10 is a diagram for explaining an action example of the first embodiment.

[0027] Figure 11 is a diagram for explaining an action example of the first embodiment.

[0028] Figure 12 is a diagram for explaining an action example of the first embodiment.

[0029] Figure 13 is a diagram for explaining an action example of the first embodiment.

[0030] Figure 14 is a diagram for explaining an action example of the first embodiment.

[0031] Figure 15 is a flowchart illustrating a processing flow of the second embodiment.

[0032] Figure 16 is a diagram for explaining an action example of the second embodiment.

[0033] Figure 17 is a diagram for explaining an action example of the second embodiment.

[0034] Figure 18 is a flowchart illustrating a processing flow of the third embodiment.

[0035] Figure 19 is a diagram for explaining an action example of the third embodiment. DETAILED DESCRIPTION

[0036] Hereinafter, an embodiment of the present disclosure will be described with reference to the accompanying drawings. In the present application, a multifunction peripheral capable of executing a job in each mode such as a copy mode, a facsimile mode, and a scan mode will be described as one mode of an image processing apparatus. In addition, the following embodiment is an example for explaining the present disclosure, and the technical scope of the application claimed by the claims is not limited to the following description.

[0037] [1 First Embodiment]

[0038] The first embodiment is a mode in which a setting history associated with a recognized user is preferentially displayed based on a recognition result of a user in the vicinity of a multifunction peripheral as an image processing apparatus.

[0039] [1.1 Functional Configuration]

[0040] Figure 1is an external perspective view illustrating the overall configuration of the multifunctional peripheral 10 according to the first embodiment. Figure 2 is a functional configuration view of the multifunctional peripheral 10. The multifunctional peripheral 10 is provided with a control section 11, a display section 13, an operation input section 15, a communication section 17, an image forming section 19, an image reading section 21, an identification section 23, and a storage section 25.

[0041] The control section 11 controls the multifunctional peripheral 10 as a whole. The control section 11 is constituted by one or a plurality of arithmetic devices (CPU (Central Processing Unit) or the like), for example. The control section 11 realizes various functions by calling and executing various programs stored in the storage section 25.

[0042] The display section 13 displays various information to a user or the like. The display section 13 can be constituted by an LCD (Liquid crystal display), an organic EL (Electro-luminescence) display, or the like, for example.

[0043] The operation input section 15 accepts information input by a user or the like. The operation input section 15 can be constituted by hard keys (such as number keys), buttons, or the like. In addition, the operation input section 15 can also be constituted as a touch panel that can be input via the display section 13. In this case, as an input method of the touch panel, a method such as a resistive film method, an electromagnetic induction method, an electrostatic capacity method, or the like can be adopted.

[0044] The communication section 17 includes an interface for communication with other devices via a network (NW) such as a LAN (Local area network), a WAN (Wide area network), the Internet, a telephone line, a facsimile line, or the like, using either or both of a wire and a wireless.

[0045] The image forming section 19 forms an image based on image data on paper as a recording medium. The image forming section 19 is supplied with paper from a paper feed section 27, forms an image based on image data on the paper, and discharges the paper to a paper discharge section 29. The image forming section 19 can be constituted by a laser printer or the like using an electrophotographic method, for example. In this case, the image forming section 19 performs image formation using toner supplied from a non-illustrated toner cartridge corresponding to toner colors (such as cyan, magenta, yellow, and black).

[0046] The image reading section 21 generates image data by scanning and reading a document image of a reading object. The image reading section 21 can be configured as a scanner device provided with an image sensor such as a CCD (Charge Coupled Device), a CIS (Contact Image Sensor), or the like, for example. The image reading section 21 is not limited in structure as long as it is configured to generate image data by reading a reflected light image from a document image with an image sensor.

[0047] The recognition section 23 is not particularly limited as long as it is configured to acquire image information, sound information, or the like related to a person (user) located in the vicinity of the multifunction peripheral 10 as recognition information and output the information. The recognition section 23 is a camera, an indoor monitoring camera, or the like mounted on the multifunction peripheral 10, for example, and is configured to acquire and output image information related to person recognition such as a face, a line of sight, a movement of a corner of the mouth, a body shape (skeleton), a posture, a motion, a manner, a gait, a distance to the multifunction peripheral 10 / guideline, or the like, using a photographing / recording device or the like. In addition, the recognition section 23 can be a sound recording / recording device or the like for recording a sound emitted by a person. Furthermore, individual recognition information, position information, or the like of a terminal device obtained by using a wireless communication function (for example, Bluetooth (registered trademark), Wi-Fi (registered trademark), NFC (Near Field Communication), a position information transmission / acquisition function (for example, GPS (Global Positioning System), a beacon, or the like)) provided by a terminal device such as a smartphone can be used as recognition information of a person who holds the terminal device.

[0048] The storage section 25 stores various programs and various data required for an operation of the multifunction peripheral 10. The storage section 25 can be configured by a storage device such as a RAM (Random Access Memory), an HDD (Hard Disk Drive), an SSD (Solid State Drive), a ROM (Read Only Memory), or the like, for example.

[0049] In the first embodiment, the storage section 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 ensures a setting value file storage area 256, a setting history storage area 257, and a job history information storage area 259.

[0050] The job execution program 251 is a program that the control section 11 reads in order to execute a job in each mode such as a copy mode, a facsimile mode, and a scan mode. The control section 11 that has read in the job execution program 251 executes a job by controlling each section related to the execution of the job such as the display section 13, the operation input section 15, the communication section 17, the image forming section 19, and the image reading section 21. Further, the control section 11 that has called the job execution program 251 can execute various jobs based on the setting values included in the setting value file associated with the setting history as history information.

[0051] The user identification program 252 is a program that the control section 11 reads in when identifying an execution user who is in the vicinity of the multifunctional peripheral 10 as an operation user. Here, the execution user according to the present disclosure indicates a user who has operated the multifunctional peripheral 10 in the past and has experience of executing a job in each mode such as a copy mode, a facsimile mode, and a scan mode. The user identification information of the execution user is associated with the setting history generated in association with the execution of the job. Further, the operation user according to the present disclosure indicates an execution user who has the possibility of operating or having operated the multifunctional peripheral 10. The control section 11 that has read in the user identification program 252 identifies an execution user who is in the vicinity of the multifunctional peripheral 10 as an operation user using image information, sound information, or individual identification information of a terminal device held by the user, and the like, which are acquired by controlling the identification section 23. For example, the control section 11 can identify an operation user by comparing the input image information after converting the image information acquired via the identification section 23 into a feature amount as an input value. Further, based on the analysis result of sound acquired by a radio receiver / recorder or the like, the control section 11 can identify a person who utters a specific keyword (for example, print, copy, and the like) as an operation user. Further, the control section 11, unlike the above-described biometric identification, in the case of identifying a user using individual identification information of a terminal device, position information, and the like, performs communication necessary for acquiring individual identification information of a terminal device and the like by simultaneously controlling the communication section 17 and the like. The control section 11 can also identify an operation user using machine learning in which the above-described identification information, user operation information accompanying an identification result, date and time information, schedule information of an execution (operation) user, and the like are used as input values.

[0052] The setting history information processing program 253 is a program that the control section 11 reads, for example, when acquiring a setting value related to execution of a job, generating a setting history, and performing various processes on the setting history. The control section 11 that has invoked the history information processing program 253 acquires a setting value related to execution of a job and generates a setting value file containing the setting value. Then, the control section 11 stores the generated setting value file in the setting value file storage area 256 associated with the setting history. In addition, the control section 11 manages the setting history in association with the user name or user ID of the user who has executed the execution job corresponding to the setting history.

[0053] Further, the control section 11 that has read the history information processing program 253 performs selection processing of a display candidate of a setting history to be displayed in a setting history display screen described later, on the basis of the user identification result. The selection processing of the display candidate is described later.

[0054] The user authentication program 254 is a program that the control section 11 reads when authenticating an execution user or another user who has logged in to the multifunction peripheral 10. The control section 11 that has read the user authentication program 254 displays a login screen described later in a case where a user authentication function is on. The control section 11 can, for example, store a login user name in association with a login password in advance and perform authentication by collating the login user name and the login password input via the login screen. Further, the authentication of the login user can be performed not only by knowledge authentication such as a login user name and a login password but also by possession authentication using a verification token, a key, an IC card, a smartphone, and the like, biometric authentication such as fingerprint authentication, palm print authentication, blood vessel authentication, and the like.

[0055] The display processing program 255 is a program that the control section 11 reads when controlling a display screen displayed via the display section 13. The control section 11 that has read the display processing program 255 displays a setting history display screen that displays a setting history, a setting screen for receiving input of various setting values related to execution of a job, or a main screen that receives a switching instruction of each (operation) mode, and the like on the display section 13. Further, the control section 11 that has read the display processing program 255 displays a setting history selected as a result of selection processing of a display candidate on the basis of the setting history on the setting history display screen.

[0056] The setting value file storage area 256 is a storage area in which the control section 11 that has read the setting history information processing program 253 stores a generated setting value file. The setting value includes, for example, a color mode, a size, a double-sided copy, a (copying) magnification, a tray, a staple, and the like, which are set by a user, a device initial value that is stored by the multifunction peripheral 10 itself from the time of factory shipment, and the like. The control section 11 that has invoked the job execution program 251 is able to acquire a setting value file associated with a setting history of an execution target from the setting value file storage area 256, and execute a job on the basis of a setting value included in the setting value file.

[0057] The setting history storage area 257 is a storage area in which the control section 11 that has read the history information processing program 253 stores a generated setting history. The setting history stored in the setting history storage area 257 is appropriately invoked at the time of selection processing of a display candidate of a setting history, and display processing in a setting history display screen.

[0058] The job history storage area 258 is a storage area in which an execution record of a job is stored as a job history. The job history is generated by the control section 11 that has read the history information processing program 253. The job history, unlike the setting history, is information that records an execution history of a job, and thus, for example, can be generated at an arbitrary timing before and after execution of a job, before and after generation of a setting history.

[0059] The user information storage area 259 is a storage area in which information involved in user authentication, such as a login user name and a login password of an execution user or another user that attempts to log in to the multifunction peripheral 10, is stored. In addition, the user information storage area 259 stores a history-user management table for managing a setting history in correspondence with an execution user. Further, the user information storage area 259 is able to store various information (for example, a feature quantity for user recognition, and the like) for recognizing an execution user located in the vicinity of the multifunction peripheral 10 as an operation user.

[0060] Here, the setting history and the setting value file involved in the present disclosure are described. Figure 3 (a) of FIG. 8 is a diagram that illustrates one example of a data structure of a setting history stored in the setting history storage area 257. Figure 3 (b) of FIG. 8 is a diagram that illustrates one example of a data structure of a setting value file stored in the setting value file storage area 256.

[0061] Figure 3 The setting history information exemplified in (a) of FIG. 8 includes a job ID, an execution date and time, a job kind, a display setting value, and a setting value file name.

[0062] The history ID is an identifier for uniquely identifying a setting value history. The history ID is given to a generated setting history. As the history ID, for example, a serial number is used. Figure 3As illustrated in (a), it can be a serial number or a history containing specified strings, symbols, etc. Execution date and time indicates the date and time the job was executed and the setting history was generated. Job type indicates the type of job executed (e.g., simple copy job, simple scan job, etc.). Displayed settings indicate a portion of the settings (content) displayed in the setting history display screen when the setting history is displayed. Setting value filename indicates the filename of the setting value file associated with this setting history.

[0063] For example, the configuration history information associated with job ID "001" indicates the configuration history information related to the job type "copy" executed at "2020 / 02 / 22 20:20". Furthermore, this job is a simple copy job executed based on the configuration values ​​contained in the configuration file "001.config", and is an example of displaying configuration values ​​such as "Number of Copies: 1, Color Mode: Auto, Size: A4, Duplex (Copy): Single-sided, Magnification: 100x, Tray: Tray 1, Staples: No Pins". In addition, the displayed configuration values ​​in the corresponding configuration history settings are merely examples, and the configuration values ​​displayed in the configuration history display screen are not limited to... Figure 3 The recorded items in (a).

[0064] Figure 3 (b) is an explanation and Figure 3 The diagram shows an example of the data structure of the setting value file "001.config" associated with the setting history of (a) the historical ID "001". The setting value file can, for example, be a text file containing the setting values ​​corresponding to each setting. Alternatively, if there is no need for user readability, the setting value file can also be composed of binary data.

[0065] For example, Figure 3 (b) is an example of a setting file for a simple copy job, which contains various settings for performing the simple copy job (e.g., number of copies: 1, color mode: automatic, size: A4, duplex copy: single-sided, magnification: 100%, tray: tray 1, staples / punches: needle-free, copy density: automatic, ...).

[0066] Next, the history-user management table managed by the control department 11 will be explained. Figure 4 This is a diagram illustrating one example of the data structure of the history-user management table stored in user information storage area 259. Figure 4 The example of the history-user management table contains history ID, username, and user ID.

[0067] Historical ID and Figure 3The historical ID described in (a) is the same. The History-User Management table stores this historical ID in association with the username and / or user ID of the executing user. The username is the username of the executing user who performed the job associated with the configuration history represented by the historical ID. The user ID is an identifier used to identify the executing user. It is possible to associate either or both of the username and user ID with the historical ID.

[0068] For example, the executing user with username "aaaaa" and user ID "0001@sample" and Figure 4 This corresponds to the historical ID "001" shown in the example. Additionally, in... Figure 4 For ease of explanation, the example shows the same executing user (username "aaaaaaa", user ID "0001@sample") and all its historical IDs. The corresponding examples are linked, but the historical settings represented by the historical ID are associated with the respective users who executed the jobs corresponding to that historical settings.

[0069] Figure 5 This is a diagram illustrating one example of the data structure of the job history stored in job history storage area 258. Figure 5 The example of the job history includes job ID, execution date and time, job type, username, and status.

[0070] A job ID is a unique identifier used to identify the configuration history of the job being executed. A job ID is generated each time a job is executed. A job ID is like... Figure 5 As shown in the example, it can be a serial number, or it can include specified strings, symbols, etc. Execution time indicates when the job was executed. Job type indicates the type of job being executed (e.g., simple copy job, simple scan job, etc.). Username indicates the name of the user who executed the job. Status indicates the processing status of the job.

[0071] For example, the configuration history information associated with job ID "001" indicates the job history related to the job type "simple copy" that was executed at "2020 / 02 / 22 20:20". Furthermore, this job was executed by the user with the username "aaaaa", and its status is "completed".

[0072] Furthermore, job history differs from setting history information; it records the execution history of jobs, and there are no particular restrictions on its generation time. For example, it can be generated at any time, such as before or after job execution, or before or after setting history generation.

[0073] [1.2 Processing Flow]

[0074] Next, a processing flow related to the first embodiment will be described. Figure 6 is a flowchart illustrating a flow of the overall processing of the multifunction peripheral 10. The processing described here is processing performed by the control section 11 by reading in the job execution program 251, the user recognition program 252, the history information processing program 253, the user authentication program 254, the display processing program 255, and the like.

[0075] For example, at the time of power-on, at the time of recovery from a sleep state, and the like, the control section 11 reads the setting history in conjunction with startup processing (step S10).

[0076] Next, the control section 11 reads the user recognition program 252. The control section 11 determines whether or not to recognize an operation user located in the vicinity of the multifunction peripheral 10 as an execution user by controlling the recognition section 23 (step S20).

[0077] In a case where an operation user located in the vicinity of the multifunction peripheral 10 is recognized, the control section 11 extracts the setting history related to a job executed by the operation user by reading the history information processing program 253 (step S20; YES -> step S30).

[0078] On the other hand, in a case where an operation user located in the vicinity of the multifunction peripheral 10 is not recognized, the control section 11 displays a login authentication screen in a case where the user authentication function is on, and displays an initial screen (for example, a home screen) in a case where the user authentication function is off, and stands by until an operation user is recognized (step S20; NO).

[0079] In step S30, after the setting history of the recognized operation user is extracted, the control section 11 determines whether or not the number of the extracted setting histories exceeds the maximum display number that can be displayed in the setting history display screen (step S40).

[0080] In a case where the number of the extracted setting histories exceeds the maximum display number that can be displayed in the setting history display screen, the control section 11 performs selection processing of display candidates of the setting histories displayed in the setting history display screen on the basis of the usage trend (frequency of use) of the recognized operation user (step S40; YES -> step S50). Here, the usage trend (frequency of use) in the present application refers to a concept of the usage trend, frequency, number of times, and the like of the setting history covering (re)used task types, the setting items (setting values) included in the setting history, and the like each time the execution user executes a job.

[0081] After the selection processing of the display candidates, the control section 11 displays the selected display candidates of the setting histories on the setting history display screen (step S60).

[0082] Further, in a case where the number of extracted setting histories is smaller than the maximum displayable number in the setting history display screen, the control section 11 displays the extracted setting histories in the setting history display screen (Step S40; No→Step S60).

[0083] When the user selects a setting history displayed on the setting history display screen and executes a job based on the setting history, the control section 11 generates a setting history based on the executed job. Then, the control section 11 stores the generated setting history in the setting history storage region 257 and ends the process (Step S70→Step S80).

[0084] Further, in a case where the number of setting histories stored in the setting history storage region 257 reaches the upper limit number, for example, a setting history with an older execution time or a setting history considered to have a lower frequency of use can be deleted, and a newly generated setting history record can be stored.

[0085] Next, in Step S50 of FIG. 10, the process in a case where the number of extracted setting histories exceeds the maximum displayable number in the setting history display screen is described. Figure 6

[0086] As the selection process of display candidates, in the present disclosure (first embodiment), a manner of determining display candidates based on the use tendency (frequency of use) of the recognized operation user is described. The display candidates based on the use tendency of the operation user can be determined based on the machine learning result using the setting values of the setting histories as input values. In this case, the execution date and time information of the operation (execution) user for the job, the schedule information of the operation (execution) user, and the like can also be considered.

[0087] Figure 7 is a flowchart illustrating the determination process of display candidates using machine learning.

[0088] First, the control section 11 calculates the similarity between the setting histories with the setting items of the setting histories as feature quantities (Step S510).

[0089] The control section 11 classifies the setting items included in the setting histories (setting value files) into difficult-to-change setting items and easy-to-change setting items, and calculates the similarity based on the following item scores (in addition, the higher the item, the greater the weight).

[0090] • Difference in difficult-to-change setting items

[0091] Consistent > Difference in one item > Difference in two items > ··· > Inconsistent

[0092] • Difference in easy-to-change setting items ​

[0093] Consistency > Difference in one project > Difference in two projects > ... > Inconsistency

[0094] • Execution date and time not considered

[0095] • Assign weights to each specified item.

[0096] Here, settings that are difficult to change are not directly displayed on the settings screen used to perform the job in each mode (e.g., copy mode), but are settings that can be changed after the screen is switched by operating the detailed settings (or similar statements) labels, buttons, etc. (e.g., skip blank paper, sorting, etc.).

[0097] On the other hand, easily changeable settings refer to those displayed directly on the settings screen used to perform tasks in each mode (e.g., number of copies, color mode, etc.). In addition, the destination is also included in the settings displayed directly on the settings screen in fax mode, scan mode, etc., but changing the destination requires effort. Therefore, as an exception, the destination is treated as a setting that is difficult to change.

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

[0099] If the similarity is determined to exceed the specified threshold, the control unit 11 stores the similar setting history as a cluster (step S520; yes → step S530).

[0100] Next, the control unit 11 calculates representative elements based on the elements within the cluster (step S540). The control unit 11 calculates representative elements by deriving scores from the following items (in addition, the higher the item, the greater its weight).

[0101] Consistent historical setting

[0102] More > Less

[0103] Differences from default settings

[0104] More > Less

[0105] Then, the control unit 11 calculates the score of the representative element (step S550). The control unit 11 calculates the score value of the representative element by calculating the score value from the following items (in addition, the higher the item, the greater the weight).

[0106] • The number of elements contained in the cluster (equivalent to a similar number of historical elements)

[0107] More > Less

[0108] • Document style similarity (during OCR execution)

[0109] High > Low

[0110] • Destination (when entering the destination)

[0111] Consistent > Inconsistent

[0112] • Execution date and time of the element

[0113] New>Old

[0114] • Task type (set in a way that minimizes the impact)

[0115] Image sending tasks > photocopying tasks

[0116] The control unit 11 sorts the representative elements in descending order of the calculated scores (step S560). Then, based on the sorting results, the control unit 11 selects the top representative element as a display candidate (step S570).

[0117] In addition, Figure 6 In step S40, if the number of extracted setting histories is less than the maximum number that can be displayed on the setting history display screen, the setting histories corresponding to users other than the identified operation (execution) user can be displayed together. The selection of setting histories associated with other users as display targets can be performed according to the decision processing of display candidates using the aforementioned machine learning. Furthermore, for example, based on predetermined criteria (e.g., setting histories based on the usage trends of the identified operation user, setting histories not based on the usage trends of the identified operation user, or only setting histories where the task is most recently executed, etc.), only setting histories that meet the maximum display number can be extracted and displayed together with the setting histories of the identified operation user.

[0118] [1.3 Action Examples]

[0119] Next, an example of the operation of the first embodiment will be described. Figure 8is a view for explaining a configuration example of a user login screen W10 displayed by the control section 11 of the display section 13. The user authentication screen W10 can be configured such that, in a case where the login authentication function is on, the login screen displayed by the control section 11 of the user authentication program 254 is read and displayed by the display section 13. In the first embodiment, in a case where the user authentication screen W10 is displayed and before the authentication request by the executing user or the other user is executed, in a case where the operation user is recognized by the recognition section 23, the setting history corresponding to the recognized operation user can be preferentially displayed. In addition, in a case where the user authentication function is off, the control section 11 displays a main screen not shown on the display section 13, and in a case where the operation user is recognized by the recognition section 23, the control section 11 preferentially displays the setting history corresponding to the recognized operation user.

[0120] The user authentication screen W10 has 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.

[0121] The login user name input box Bx10 is an input box that accepts the input of the login user name. The executing user or the other user who attempts to log in to the multifunction peripheral 10 inputs the login user name into the login user name input box Bx10. Further, the login user name can be selected from a user name list provided separately.

[0122] The login password input box Bx12 is an input box that accepts the input of the login password corresponding to the login user name. The executing user or the other user who attempts to log in to the multifunction peripheral 10 inputs the login user name together with the login password.

[0123] The authentication destination designation button B10 is a button that accepts the designation of the user authentication destination. The user authentication destination can be the device itself, and can also designate, for example, an authentication server or the like provided separately on the network (NW). In a case where the authentication in the device itself is designated as the user authentication destination, the control section 11 performs user authentication by comparing the input login user name and the login password with the authentication information (for example, a combination of a user name and a password, or the like) prepared in advance. On the other hand, in a case where the authentication server or the like provided on the network (NW) is used, the control section 11 transmits the input login user name and the login password to the authentication server, and performs user authentication by receiving the authentication result from the authentication server.

[0124] The OK button B12 is an input button that accepts a determination instruction input of an input action by the user. The user presses the OK button B12 when determining the input to 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 a button that receives a cancel instruction input of an input action by the user.

[0125] Next, an example of the action of the display candidate determination processing using machine learning will be described. Here, the maximum number of display of the setting histories that can be displayed in the setting history display screen is set to five for easy explanation. Further, in the following description, the setting history display screen is assumed to be displayed on the display 20 of the multifunction peripheral 1. Figure 6 In step S20, the user name of the execution user who is identified as the operation user is "aaaaa", and the 10 setting histories of the history IDs "001" to "010" exemplified in Figure 3 are associated with the execution user (see the history-user management table of Figure 4 ). Note that the number of the setting histories (10) corresponding to the execution user is merely an example, and the number of the setting histories is not limited to the number described here.

[0126] Figure 9 The setting history of the user name "aaaaa" extracted by the control section 11 in step S30 of Figure 6 is one example of a history table in which each setting item (setting value) used in machine learning is aggregated for each setting history. Figure 9 Each setting item shown in the history table of is used as an input value for machine learning.

[0127] In the history table exemplified in Figure 9 , the setting items that are easily changed (the setting values that are difficult to change are omitted) and the default setting items are shown.

[0128] For example, in the setting history related to the history ID "001", as the setting this time, (job type: simple copy, number of copies: 1, color: automatic, size: A4, double-sided (copying): single-sided, magnification: 100%, tray: tray 1, staple: no needle,...) is shown.

[0129] On the other hand, the default setting related to the job type: simple copy is (number of copies: 1, color: automatic, size: A4, double-sided (copying): single-sided, magnification: 100%, tray: automatic, staple: none,...). Therefore, in the history ID "001", the setting items related to the tray and the staple are changed from the default setting.

[0130] The control section 11 calculates the similarity degree in Figure 9 using the history table exemplified in step S30 as the input value.Figure 7 The score value of the representative element described in the flowchart is displayed, whereby the determination processing of the display candidate is performed. The action example of the score value calculation of the representative element using the setting history exemplified in Figure 9 The action example of the score value calculation of the representative element using the setting history exemplified in

[0131] In Figure 7 In step S510 of Figure 9 The similarity of the setting history exemplified below is calculated as follows:

[0132] The setting history that is completely identical: (history ID: 001, 010) and (history ID: 005, 009),

[0133] One item difference: (history ID: 001, 006, 010) and (history ID: 002, 005, 009),

[0134] Two item difference: (history ID: 003, 007)

[0135] ·

[0136] ·

[0137] Based on the calculation result of the similarity, the setting history involved in the example of Figure 9 The setting history classified as (history ID: 001, 006, 010), (history ID: 002, 005, 009), (history ID: 003, 007), (history ID: 4), (history ID: 8) clusters.

[0138] In Figure 7 In step S540 of

[0139] · Cluster (history ID: 001, 006, 010)

[0140] The setting history that is identical: (history ID: 001, 010)

[0141] Difference from the default setting: (history ID: 001, 010) = (history ID: 006)

[0142] Therefore, the control section 11 calculates the representative element (history ID: 001, 010).

[0143] · Cluster (history ID: 002, 005, 009)

[0144] · The setting history that is identical: (history ID: 005, 009)

[0145] · Difference from the default setting: (history ID: 005, 009) > (history ID: 002)

[0146] Therefore, the control section 11 calculates the representative element (history ID: 007).

[0147] • Cluster (history ID: 003, 007)

[0148] • Consistent setting history: No

[0149] • Difference from default setting: (history ID: 007)

[0150] Therefore, the control section 11 calculates the representative element (history ID: 007).

[0151] In step S550, the control section 11 calculates the scores of the representative elements.

[0152] • Representative element (history ID: 001, 010)

[0153] Number of elements of cluster: 3

[0154] Latest execution date and time: (history ID: 001)

[0155] • Type: Copying type job

[0156] • Representative element (history ID: 005, 009)

[0157] Number of elements of cluster: 3

[0158] Latest execution date and time: (history ID: 005)

[0159] • Type: Copying type job

[0160] • Representative element (history ID: 007)

[0161] Number of elements of cluster: 2

[0162] Latest execution date and time: (history ID: 007)

[0163] • Type: Image transmission type job

[0164] If the representative elements are sorted in descending order in the order of the score values of the representative elements from high to low, (history ID: 001, 010) > (history ID: 005, 009) > (history ID: 007). In addition, (history ID: 004) and (history ID: 008) are displayed in the order of the new execution date and time.

[0165] Figure 10 is a constitutional example of a display table that defines the display order of the setting histories determined to be display candidates. In addition, the display priority in the representative element displays the new setting history of the execution date and time first.

[0166] AsFigure 10 As shown, the control section 11 displays the setting history of the user "aaaaa" in the display order of ID: "001" > history ID "005" > history ID "007" > history ID "004" > history ID "008" based on the result of the decision process of the display candidate.

[0167] Figure 11 is an example of the display configuration of the setting history display screen W20 that displays the setting history shown in the display table of Figure 10 . Further, the setting history display screen W20 can accept input of a display instruction button provided on, for example, a main screen, a setting screen corresponding to each job category, and the like, which are not shown, and display.

[0168] The setting history display screen W20 includes a setting history display area R10 and a slider SB10. The setting history display area R10 is a display area that selectively displays setting history information shown in the display table of Figure 10 .

[0169] Figure 11 is an example of displaying the setting history corresponding to the execution user "aaaaa" as the operation user in the display order of ID: "001" > history ID "005" > history ID "007" > history ID "004" > history ID "008" on the setting history display area R10. In the setting history record display area R10, the setting history record is displayed based on the use trend (frequency of use) of the recognized operation user, so the operation user grasps the use trend of the setting history record for himself / herself, and can effectively reproduce the job based on the setting history.

[0170] The slider SB10 is configured to be able to slide up and down. The slider SB10 accepts a display instruction of a non-displayed area in the setting history display area R10. For example, by performing an operation of moving the slider SB10 up and down, pressing an arrow button, or performing a screen drawing operation within the setting history display area R10, it is possible to display a non-displayed area in the setting history display area R10.

[0171] In addition, in the description of the operation example of the first embodiment, a case where the maximum number of displayable setting histories in the setting history record display screen W20 is five was described, but, for example, it is also possible to display more than five setting histories by providing the slider SB10 operable on the setting history record display screen W20.

[0172] Next, in Figure 6In step S40 of FIG. 10, an example of an action in a case where the number of extracted setting histories is insufficient for the maximum display number in the setting history display screen is described. In this case, the control section 11 displays the setting history of the execution user who is identified as the operation user together with the setting history of another user with which the execution user is associated.

[0173] Figure 12 (a) of FIG. 11 is an example of a history table in a case where the username of the execution user who is identified as the operation user in step S20 of FIG. 10 is "aaaaa", and the setting histories of the two setting histories of the history IDs "001" and "003" exemplified in FIG. 10 are associated with this execution user. Figure 6 Figure 3 (b) of FIG. 11 is an example of a history table of setting histories associated with another user who is different from the execution user. Figure 12

[0174] The control section 11 adds the setting histories of other users so that (the maximum display number) = (the number of setting histories of the execution user) + (the number of setting histories of other users). The selection of the setting histories associated with other users as display targets can be performed by the determination processing using the display candidates using the above-described machine learning. Further, for example, based on a predetermined criterion (for example, the setting history according to the use trend of the identified user, the setting history not according to the use trend of the identified user, or only the setting history in which the task is the latest, and the like), it is also possible to extract only the setting histories satisfying the maximum display number, and display them together with the setting histories of the identified user.

[0175] Figure 13 is an example of a display table that defines the display order of the setting histories determined as display candidates (the setting histories of the execution user and the setting histories of other users).

[0176] In FIG. 11, on the basis of the history IDs "001" and "002" of the setting histories associated with the execution user who is identified as the operation user, the setting histories of the history IDs "011", "012", and "014" of the setting histories associated with other users are also added to satisfy the maximum display number. In addition, in a case where the maximum display number cannot be satisfied even if the setting histories associated with other users are added, the display table is directly displayed. Figure 13

[0177] Figure 14 is an example of a display table that defines the display order of the setting histories determined as display candidates (the setting histories of the execution user and the setting histories of other users). Figure 13

[0178] Figure 14 ​​​​An example is shown in which, after the setting histories corresponding to the execution user "aaaaa" who is the operating user, the history ID "001", the history ID "003", the setting histories of other users are displayed in the setting history display area R10 in the order of the history ID "011", the history ID "012", and the history ID "014". In this way, in a case where the number of the extracted setting histories does not satisfy the maximum display number that can be displayed in the setting history display screen, by adding the setting histories corresponding to the other users to satisfy the maximum display number, the display area of the setting history display screen W20 can be effectively utilized.

[0179] As described above, according to the first embodiment, based on the recognition result of the user located in the vicinity of the multifunctional peripheral, the setting history associated with the execution user recognized as the operating user is preferentially displayed, and thus the convenience of the user operating the multifunctional peripheral can be improved.

[0180] [2 Second Embodiment]

[0181] The second embodiment is a mode in a case where a plurality of execution users are located in the vicinity of the multifunctional peripheral 10.

[0182] [2.1 Functional Configuration]

[0183] The functional configuration of the multifunctional peripheral involved in the second embodiment can be configured to be substantially the same as the functional configuration of the multifunctional peripheral 10 involved in the first embodiment. Therefore, the multifunctional peripheral of the second embodiment is denoted as the multifunctional peripheral 10, and detailed description regarding the functional configuration is omitted.

[0184] [2.2 Flow of Process]

[0185] Figure 15 is a flowchart illustrating the flow of the overall process of the multifunctional peripheral 10 of the second embodiment. The process described here is a process performed by the control section 11 by reading in the job execution program 251, the user recognition program 252, the history information processing program 253, the user authentication program 254, the display processing program 255, and the like. Further, the same process as the process described in the first embodiment is denoted by the same step number. Figure 6 The same process as the process described in the first embodiment is denoted by the same step number.

[0186] For example, at the time of power-on, at the time of recovery from a sleep state, and the like, the control section 11 reads the setting histories in conjunction with the startup process (step S10).

[0187] Next, the control section 11 reads the user recognition program 252. The control section 11 determines whether or not the execution user located in the vicinity of the multifunctional peripheral 10 is recognized by controlling the recognition section 23 (step S90).

[0188] In a case where the user located in the vicinity of the multifunction peripheral 10 is identified, the control section 11 extracts the setting history related to the job performed by the user by reading the history information processing program 253 (step S90; YES -> step S100).

[0189] On the other hand, in a case where the user located in the vicinity of the multifunction peripheral 10 is not identified, the control section 11 displays a login authentication screen in a case where the user authentication function is on, and displays an initial screen (for example, a home screen) in a case where the user authentication function is off, and stands by until the user is identified (step S90; NO).

[0190] Next, the control section 11 determines whether the user who is closest to the multifunction peripheral 10 can be determined as the operation user (step S110).

[0191] In a case where the user who is closest to the multifunction peripheral 10 can be determined as the operation user, the control section 11 displays the setting history in display mode 1 (step S110; YES -> step S120). Here, the display mode 1 is a display mode in which the setting history associated with the determined operation user (including a plurality of users) is displayed, and is the display mode of the setting history exemplified in the first embodiment and the like. Figure 6

[0192] On the other hand, in a case where the user who is closest to the multifunction peripheral 10 cannot be determined as the operation user, the control section 11 displays the setting history of all the users identified in step S100 as display mode 2 (step S110; NO -> step S130). In this case, the control section 11 can display the setting history of all the users identified in descending order from the new start in a time series, for example, or can calculate and display display candidates from the setting history of all the users that can be identified. In addition, regarding the calculation of the display candidates of the displayed setting history, the same setting history is slightly weighted according to the distance between the multifunction peripheral 10 and the user, and the like, whereby the display candidates can be narrowed down.

[0193] Next, the control section 11 determines whether a change has occurred to the determined operation user (step S140). That is, the control section 11 determines whether the user determined as the operation user located in the vicinity of the multifunction peripheral 10 is replaced by another user.

[0194] If it is determined that the operation user closest to the multifunction peripheral 10 is changed, the control section 11 switches the display to the setting history associated with the changed user (step S140; YES -> step S150). Then, if a job is performed based on the displayed setting history, the control section 11 stores the setting history related to the job, and ends the processing (step S70 -> step S80). ​

[0195] On the other hand, if it is determined that the operation user closest to the multifunction peripheral 10 has not changed, the control section 11 moves the process to step S70 (step S140; No→step S70). Then, if a job is executed based on the displayed setting history, the control section 11 stores the setting history involved in the job, and ends the process (step S70→step S80).

[0196] [2.2 Action Example]

[0197] Next, an action example of the second embodiment will be described. Figure 16 And Figure 17 is an example of a display configuration of the setting history display screen (display mode 1) displayed by the control section 11 in a case where the execution user closest to the multifunction peripheral 10 can be determined as the operation user in step S110 of Figure 15

[0198] In the second embodiment, in the vicinity of the multifunction peripheral 10, the following two display modes can be applied according to the determination of the operation user among the plurality of execution users recognized.

[0199] (1) The execution user located closest to the multifunction peripheral 10 is determined as the operation user, and the setting history of the operation user is displayed. Also, in a case where the operation user located closest is replaced by another execution user, the display of the setting history is also changed.

[0200] (2) In a case where the plurality of execution users are located in the vicinity of the multifunction peripheral 10, and the determination accuracy of the operation user is not high, only the setting history involved in the job kind excluding the sending system / saving system from the displayed setting history of the execution user is displayed.

[0201] Then, in a case where the operation user operating the multifunction peripheral 10 is determined unambiguously, the setting history of the operation user is displayed without limitation.

[0202] Figure 16 (a) of is an example of a display configuration of the setting history display screen W20 in which the execution user "aaaaa" is determined as the operation user and the setting history of the operation user "aaaaa" is displayed. In addition, the setting history display screen W20 can be configured to be the same as the setting history display screen W20 exemplified in Figure 11

[0203] Figure 16 (b) of is an example of a display configuration of the setting history display screen W20 in which the execution user "aaaaa" is determined as the operation user and the setting history of the operation user "aaaaa" is displayed. In addition, the setting history display screen W20 can be configured to be the same as the setting history display screen W20 exemplified in Figure 16 ​​(a) of FIG. 8 is an example of a display example of a setting history display screen W40 in which the setting history of the user "bbbb" determined as the operating user is displayed, in a case where the operating user located in the vicinity of the multifunctional peripheral 10 is replaced by the other performing user "bbbb", for example. In this way, in a case where the operating user located in the closest position is replaced by the other performing user, the control section 11 can also change following the display of the setting history.

[0204] Figure 17 (a) of FIG. 8 is an example of a display example of a setting history display screen W50 in which the setting history of the performing user "aaa" (User A) displayed is displayed, excluding the setting history related to the job category of the transmission system / saving system, in a case where the determination accuracy of the operating user is not high when a plurality of performing users are located in the vicinity of the multifunctional peripheral 10. In addition, Figure 17 (b) of FIG. 8 is an example of a display example of a setting history display screen W60 in which the setting history of the performing user "bbbb" (User B) displayed is displayed, excluding the setting history related to the job category of the transmission system / saving system, in the same case.

[0205] Figure 17 (a) of FIG. 8 and Figure 17 (b) of FIG. 8, in a case where the determination accuracy of the operating user is not high and it is not possible to determine any of the performing users as the operating user, the setting history related to the job category of the transmission system / saving system of both is excluded from the display. Thereby, even in a state where the determination accuracy of the operating user is not high, any of the performing users (User: A) or the performing user (User: B) located in the vicinity of the multifunctional peripheral 10 can efficiently use his or her own setting history. In this case, since the setting history related to the job category of the transmission system / saving system is not displayed to the performing user, it is possible to obtain an effect in which, for example, the recipient information such as the facsimile number or the mail address is not leaked to a third party including the other performing user.

[0206] As described above, according to the second embodiment, in addition to the effect of the first embodiment, even in a case where a plurality of performing users are located in the vicinity of the multifunctional peripheral 10 and the determination accuracy of the operating user is not high, the performing user can efficiently use his or her own setting history.

[0207] [3. Third Embodiment]

[0208] The third embodiment is a mode in which, after the display candidate of the setting history explained in the first embodiment is decided, recalculation of the display candidate is performed in a case where a specific operation is performed.

[0209] [3.1 Functional Configuration]

[0210] The functional configuration of the composite machine according to the third embodiment can be substantially the same as that of the composite machine 10 according to the first embodiment. Therefore, the composite machine according to the third embodiment is denoted as the composite machine 10, and detailed description of the functional configuration is omitted.

[0211] [3.2 Flow of processing]

[0212] Figure 18 is a flowchart illustrating a flow of overall processing of the composite machine 10 according to the third embodiment. The processing described here is processing performed by the control section 11 by reading in the job execution program 251, the user identification program 252, the history information processing program 253, the user authentication program 254, the display processing program 255, and the like. In addition, the description here is made as a flow of processing after the display processing of the setting history according to the steps S10 to S60 of Figure 6 The processing after the display processing of the setting history according to the steps S10 to S60 of

[0213] After the display of the setting history according to the step S60 of Figure 6 After the display of the setting history according to the step S60 of

[0214] In a case where it is determined that there is a setting history similar in file style (step S210; Yes -> step S240), the control section 11 performs update of the display candidates (step S210; Yes -> step S240). Then, the control section 11 displays the setting history based on the update result and ends the processing (step S60).

[0215] On the other hand, in a case where it is determined that OCR is not performed (step S200: No), or in a case where it is determined that there is no setting history similar in file style (step S210: No), the control section 11 determines whether a destination is input in the job category of the transmission system / saving system (step S220).

[0216] When it is determined that a destination is input in the job category of the transmission system / saving system (step S220; Yes -> step S240), the control section 11 shifts the processing to step S240. On the other hand, when it is determined that a destination is not input in the job category of the transmission system / saving system (step S220; No -> step S230), the control section 11 determines whether a file name is input in the job category of the transmission system / saving system (step S220; No -> step S230).

[0217] When it is determined that a file name is input in the job category of the transmission system / saving system, the control section 11 causes the processing to shift to step S240 (step S230; Yes -> step S240). On the other hand, when it is determined that a file name is not input in the job category of the transmission system / saving system, the control section 11 displays the setting history without updating the display candidates (step S230; No -> step S60).

[0218] [3.3 Action Example]

[0219] Next, an action example related to the third embodiment of the present application will be described. Figure 19 (a) of FIG. 8 is a display example of the setting history display screen W70 of the result of the display candidate recalculation of the setting history, which is performed in steps S200 and S210 of FIG. 7, in a case where the result of the OCR execution is that there is a setting history similar in document style. Figure 18 The setting history display screen W20 exemplified in (a) of FIG. 8 is displayed. Figure 11 The setting history display screen W20 exemplified in (a) of FIG. 8 is displayed.

[0220] As the result of the OCR execution, in a case where the setting history similar in document style is a setting history of a simple facsimile job and a simple scan job, as shown in (a) of FIG. 8, the control section 11 replaces the display candidates of the setting history with the setting history of the simple facsimile job and the simple scan job. Figure 19 The setting history display screen W20 exemplified in (a) of FIG. 8 is displayed.

[0221] Figure 19 (b) of FIG. 8 is a display example of the setting history display screen W80 of the result of the display candidate recalculation of the setting history, which is performed in step S220 of FIG. 7, in a case where a destination is input in the job category of the transmission system / saving system. Figure 18 In the job category of the transmission system / saving system, in a case where "Yamada@sample.com" is input as the destination, as shown in (b) of FIG. 8, the control section 11 replaces the display candidates of the setting history with the setting history related to the simple scan job.

[0222] Figure 19 Similarly, (c) of FIG. 8 is a display example of the setting history record display screen W90 of the result of the display candidate recalculation of the setting history record, which is performed in step S230 of FIG. 7, in a case where a file name is input in the job category of the transmission system / saving system.

[0223] Similarly, (c) of FIG. 8 is a display example of the setting history record display screen W90 of the result of the display candidate recalculation of the setting history record, which is performed in step S230 of FIG. 7, in a case where a file name is input in the job category of the transmission system / saving system. Figure 19 Figure 18

[0224] ​​​In a case where a file name to be saved is input in the job category of the transmitting system / saving system, the control section 11 replaces the display candidate of the setting history with the setting history involved in the scan saving job and the sample scan job, as indicated by the dotted line frame of (c) of FIG. 8. Figure 19

[0225] As described above, according to the third embodiment, in a case where a specific operation is performed after the display candidate of the setting history explained in the first embodiment is decided, since it is a manner in which the display candidate is recalculated, appropriate setting history can be displayed according to the specific operation performed.

[0226] The present application is not limited to the above-described embodiments, and various modifications can be made. That is, embodiments obtained by appropriately changing technical means and combining them within a scope without departing from the scope of the present application are also included in the technical scope of the present application.

[0227] In addition, the above-described embodiments have parts explained separately, but it is needless to say that they can be combined and executed within a technically possible range.

[0228] Further, the program executed in each device of the embodiments is a program that controls a CPU or the like (a program that causes a computer to function) to realize the functions of the above-described embodiments. Also, the information handled by these devices is temporarily stored in a temporary storage device (for example, a RAM) while it is being processed, and thereafter, stored in a storage device such as a variety of ROMs (Read Only Memory), HDDs, and the like, and read, modified, and written by a CPU as necessary.

[0229] Here, as a storage medium that stores the program, any one of a semiconductor medium (for example, a ROM, a nonvolatile memory card, and the like), an optical recording medium / magneto-optical recording medium (for example, a DVD (Digital Versatile Disc), a MO (Magneto Optical Disc), an MD (Mini Disc), a CD (Compact Disc), a BD (Blu-ray (registered trademark) Disk), and the like), a magnetic recording medium (for example, a magnetic tape, a floppy® disk, and the like), and the like can be used. Further, by executing a downloaded program, not only the functions of the above-described embodiments can be realized, but also the functions of the present application can be realized by common processing by an operating system or other application programs and the like based on the instructions of the program.

[0230] In addition, in a case where it is circulated to the market, the program can be saved in a portable recording medium and circulated, or transmitted to a server computer via a network such as the Internet. At this time, the storage device of the server computer is of course included in the present application.​

[0231] Reference Signs List

[0232] 10 complex machine

[0233] 11 control section

[0234] 13 display section

[0235] 15 operation input section

[0236] 17 communication section

[0237] 19 image forming section

[0238] 21 image reading section

[0239] 23 recognition section

[0240] 25 storage section

[0241] 251 job execution program

[0242] 252 user recognition program

[0243] 253 history information processing program

[0244] 254 user authentication program

[0245] 255 display processing program

[0246] 256 setting value file storage area

[0247] 257 setting history storage area

[0248] 258 job history storage area

[0249] 259 user information storage area

[0250] 27 paper feed section

[0251] 29 paper discharge section

Claims

1. An image processing apparatus characterized by comprising: including: a job execution section that executes a job related to image processing; a storage section that stores history information related to execution of the job in association with an execution user of the job; a display section that displays the history information; an identification section that identifies the execution user; an authentication section that authenticates the execution user via an authentication screen; and a control section, in a case where a plurality of execution users including the execution user exist in the vicinity of an image processing apparatus, the control section displays the history information corresponding to an operation user who operates the image processing apparatus in place of a shift to the authentication screen of each of the plurality of execution users, in a case where the identification section identifies the plurality of execution users as the operation user before authenticating the execution user, the control section excludes the history information related to a transmitted or saved job type within the displayed history information of the execution user in a case where a specific accuracy as the operation user is not high, and displays the history information of the operation user without limitation in a case where the specific accuracy as the operation user is high and the operation user is determined.

2. The image processing apparatus according to claim 1, characterized by, the control section determines the history information displayed on the display section based on a usage trend of the history information corresponding to the execution user in a case where a number of displays of the history information corresponding to the execution user in the display section exceeds a maximum number of displays.

3. The image processing apparatus according to claim 2, characterized by, the control section determines the history information displayed on the display section based on a score value obtained from machine learning using the history information corresponding to the execution user as an input value.

4. The image processing apparatus according to claim 1, characterized by, the control section displays the history information corresponding to the execution user together with the history information corresponding to other users in a case where a number of displays of the history information corresponding to the execution user in the display section is less than a maximum number of displays.

5. The image processing apparatus according to claim 1, characterized by, the control section updates the history information displayed by the display section when a specific operation of the execution user is detected.

6. The image processing apparatus according to claim 1, wherein the identification section identifies the execution user using a communication function of a terminal apparatus.

7. The image processing apparatus according to claim 1, wherein the identification section identifies the execution user by biometric identification.

8. A display method of history information, characterized by, including: a job execution step that executes a job related to image processing; a storage step that stores history information related to execution of the job in association with an execution user of the job; a display step that displays the history information; an identification step that identifies the execution user; an authentication step that authenticates the execution user via an authentication screen; and in a case where a plurality of execution users including the execution user exist in the vicinity of an image processing apparatus, the control section displays the history information corresponding to an operation user who operates the image processing apparatus in place of a shift to the authentication screen of each of the plurality of execution users, in a case where the identification section identifies the plurality of execution users as the operation user before authenticating the execution user, the control section excludes the history information related to a transmitted or saved job type within the displayed history information of the execution user in a case where a specific accuracy as the operation user is not high, and displays the history information of the operation user without limitation in a case where the specific accuracy as the operation user is high and the operation user is determined. If the specific precision of the operating user is not high, the historical information related to the types of jobs sent or saved in the historical information of the executing user is excluded. If the specific precision of the operating user is high and the operating user is determined, the historical information of the operating user is displayed without restriction.

Images